its possible twrp got to the wrong partition somehow,but that doesnt explain why its still there after you flash the stock boot image,or why you are unable to change recoveries in the recovery partition.
nor does it explain why a command that should put the phone into ruu mode takes you to recovery!
there is definatley something kooky going on. have you,per chance,tried any of this from a different PC? if youre using windows 8 or usb 3.0,or even just a bad usb port or cable,lots of wierd things can happen,not to mention some obscure spyware or firewall setting thats interfering with the phone connection.
it sounds crazy but quite a few times ive seen folks unable to do a particular task in adb o fastboot that looked 100% correct,but failed every time,and all of a sudden have success when they borrow or dig out an old laptop
given everything weve done,im starting to think more and more that either:
1)there is something very wrong with the phone
2)what i just mentioned above- some PC variable is for some reason messing hardcore with your attempts to manipulate the phone
as loyal pointed out,hes been in your situation a few times,and been able to recovery without all this nonsense
i actually have not flashed any roms on my m7 yet,only run ruus(wich wipe internal storage,FYI.. unlike other nonremovable sd devices
) so i havent experienced the aroma instability or any hangs/bootloops.
if your attempt to remove aroma fails,only thing really sticking with me,is try a different pc,usb cable,etc. and retry all the stuff youve just done. if you can get into ruu mode,you should hopefully be able to flash the miniruu zip.
if you have a usb 'OTG' cable,you can try renaming the miniruu to PN07IMG and flashing it from HBOOT via an external sd. that kind of thing worked with the one x,but i havent tried it here yet.