Develop Bugs

[Q] getting back from AOSPA to stock JB

hi all,
i need help getting back to stock rom please.
i have my stock online nandroid backup files tried to flash stock boot.img then proceeding to restore using TWRP 2.4.4 but it fails.
i tried paranoid android 3.10 last night and it looks great with my best feature "swipe to lock/unlock" , unfortunately no wifi , it just can not be turned on, tried another kernel "repacked xm"
and still no wifi and gsm signal,
now i flashed RC19 it is working great , only some issues with notification LED and camera/gallery stability , but i still want to know how to get back to stock.
any help will be appreciated.

Flash the boot.img file from the stock nandroid backup. Enter the recovery and perform a full wipe then restore the backup. Should get you back to stock rom.
Twrp has a different boot.img named boot.emmc.win .....flash it
Fastboot flash boot boot.emmc.win
Fastboot erase cache

Mr Hofs said:
Flash the boot.img file from the stock nandroid backup. Enter the recovery and perform a full wipe then restore the backup. Should get you back to stock rom.
Twrp has a different boot.img named boot.emmc.win .....flash it
Fastboot flash boot boot.emmc.win
Fastboot erase cache
Click to expand...
Click to collapse
thanks, i will try and get back

in the wipe menu i have many choices :
cache - delvik cache - factory reset - system - external storage - android secure
i usually do : cache - delvik cache - factory reset
do i need to do one of the other choices? and why?

I always do all of them except external storage . Just to be sure you have no complications ! There is nothing better then a good cleansweep

still not working, gives me Failed message

Do a fastboot command
Fastboot getvar version-main
Post the outcome please

3.16.415.4

Oke get yourself a new nandroid backup from here
http://forum.xda-developers.com/showthread.php?t=1975140
Its taken with clockworkmod recovery. So flash that first. Look for cwm 5.8.4.0 and flash it. You probably have no touch because of the 3.16 base you are on. Just use the volume and power button.
Download the nandroid and unpack it to the right folder
Clockworkmod\backup\time & date folder\backup files
Then wipe ALL of this
Factory reset
Wipe cache partition
Advanced - wipe dalvik cache
Mounts & storage - format cache, data, system
Restore the nandroid backup and after that you open the command window on the pc and type
adb reboot bootloader (the phone goes from the recovery to the bootloader)
Flash the boot.img from the new nandroid
Fastboot erase cache
Fastboot flash boot boot.img
Fastboot erase cache
Fastboot reboot
This should work fine.

thanks for your great support , one other thing i want to know , how to access the correct directory without having a working system on the device?

ok i managed to access it

Go in the recovery to mounts and storage and select : mount as mass storage device .....it pops up on the pc as a usb diskdrive

Mr Hofs said:
Oke get yourself a new nandroid backup from here
http://forum.xda-developers.com/showthread.php?t=1975140
Its taken with clockworkmod recovery. So flash that first. Look for cwm 5.8.4.0 and flash it. You probably have no touch because of the 3.16 base you are on. Just use the volume and power button.
Download the nandroid and unpack it to the right folder
Clockworkmod\backup\time & date folder\backup files
Then wipe ALL of this
Factory reset
Wipe cache partition
Advanced - wipe dalvik cache
Mounts & storage - format cache, data, system
Restore the nandroid backup and after that you open the command window on the pc and type
adb reboot bootloader (the phone goes from the recovery to the bootloader)
Flash the boot.img from the new nandroid
Fastboot erase cache
Fastboot flash boot boot.img
Fastboot erase cache
Fastboot reboot
This should work fine.
Click to expand...
Click to collapse
hi i have this problem i think. i installed the boot.img via fastboot then in recovery wiped everything then installed the rom and gapps and the wifi just wont turn on. i slide it across and it says turning wifi on but does nothing?

anandyaa98 said:
hi i have this problem i think. i installed the boot.img via fastboot then in recovery wiped everything then installed the rom and gapps and the wifi just wont turn on. i slide it across and it says turning wifi on but does nothing?
Click to expand...
Click to collapse
A nandroid backup NEVER comes together with a install of gapps. Don't know what you are trying to do ? A nandroid backup is restored including flashing the boot.img. that's all to it.

Mr Hofs said:
A nandroid backup NEVER comes together with a install of gapps. Don't know what you are trying to do ? A nandroid backup is restored including flashing the boot.img. that's all to it.
Click to expand...
Click to collapse
i mean i dont want to back up or go to any other rom i just want to fix whatever i have done. so right now ive installed paranoid android and gapps but wifi wont turn on. how do i fix this? sorry if i posted it in the wrong section just kinda panicking .

anandyaa98 said:
i mean i dont want to back up or go to any other rom i just want to fix whatever i have done. so right now ive installed paranoid android and gapps but wifi wont turn on. how do i fix this? sorry if i posted it in the wrong section just kinda panicking .
Click to expand...
Click to collapse
Don't know really ! If you did all you needed to do there should be no problem. What's your hboot number ?
Wipe ALL again. Flash the boot.img from the paranoid rom. Go to the recovery and install the rom.zip and gapps.zip.....then reboot. Otherwise try another rom

i think it is a kernel issue, that's why i tried to repack with xm kernel , but no use, so i flashed RC19.

Mr Hofs said:
Don't know really ! If you did all you needed to do there should be no problem. What's your hboot number ?
Wipe ALL again. Flash the boot.img from the paranoid rom. Go to the recovery and install the rom.zip and gapps.zip.....then reboot. Otherwise try another rom
Click to expand...
Click to collapse
i think its htc001. yeah its what i do for every rom. ive been off my htc for about 4 months so thought there was something to do with the different version of android jelly bean??? i used to be on ARHD18 which worked perfectly. i did what i said above and this happened. ive tried installing miui from ARHD18 and that failed aswell. it had no lockscreen and stuff generally didnt work.
---------- Post added at 12:41 AM ---------- Previous post was at 12:22 AM ----------
Mr Hofs said:
Don't know really ! If you did all you needed to do there should be no problem. What's your hboot number ?
Wipe ALL again. Flash the boot.img from the paranoid rom. Go to the recovery and install the rom.zip and gapps.zip.....then reboot. Otherwise try another rom
Click to expand...
Click to collapse
sorry thats my CID i think. its 1.31. ive seen a hboot on 1.36 should i upgrade to that and try again? does it require a special cwm?

Mr Hofs said:
Oke get yourself a new nandroid backup from here
http://forum.xda-developers.com/showthread.php?t=1975140
Its taken with clockworkmod recovery. So flash that first. Look for cwm 5.8.4.0 and flash it. You probably have no touch because of the 3.16 base you are on. Just use the volume and power button.
Download the nandroid and unpack it to the right folder
Clockworkmod\backup\time & date folder\backup files
Then wipe ALL of this
Factory reset
Wipe cache partition
Advanced - wipe dalvik cache
Mounts & storage - format cache, data, system
Restore the nandroid backup and after that you open the command window on the pc and type
adb reboot bootloader (the phone goes from the recovery to the bootloader)
Flash the boot.img from the new nandroid
Fastboot erase cache
Fastboot flash boot boot.img
Fastboot erase cache
Fastboot reboot
This should work fine.
Click to expand...
Click to collapse
DONE , thanks alot Mr Hofs for your help and knowledge you share with us, i am learning alot from you , appreciate your time

anandyaa98 said:
i think its htc001. yeah its what i do for every rom. ive been off my htc for about 4 months so thought there was something to do with the different version of android jelly bean??? i used to be on ARHD18 which worked perfectly. i did what i said above and this happened. ive tried installing miui from ARHD18 and that failed aswell. it had no lockscreen and stuff generally didnt work.
---------- Post added at 12:41 AM ---------- Previous post was at 12:22 AM ----------
sorry thats my CID i think. its 1.31. ive seen a hboot on 1.36 should i upgrade to that and try again? does it require a special cwm?
Click to expand...
Click to collapse
Do these 2 fastboot commands :
Fastboot getvar version-main
Fastboot oem readcid
Post them back please !
---------- Post added at 05:56 AM ---------- Previous post was at 05:55 AM ----------
teravers said:
DONE , thanks alot Mr Hofs for your help and knowledge you share with us, i am learning alot from you , appreciate your time
Click to expand...
Click to collapse
Thanks mate ! At least one case solved in here now

[Q] Unable to flash new recovery?

Hey guys, first of all im sorry if its in the wrong section(im a noob).
So, ive recently rooted my phone via the htcdev, everything went well ive flashed cwm and im using cm as my rom but my problem is that i cannot flash a new recovery. I just want to have cwm touch because i want to try out cwm touch recovery. I have tried flashing new recovery and it says its complete and everything went well(via cmd). I've also tried flashing new recovery through rom manager, when im installing cwm touch it says its been complete but doesnt actually do anything, and when im trying to flash cwrp it says installation failed.
What could be the problem?

JacobCob said:
Hey guys, first of all im sorry if its in the wrong section(im a noob).
So, ive recently rooted my phone via the htcdev, everything went well ive flashed cwm and im using cm as my rom but my problem is that i cannot flash a new recovery. I just want to have cwm touch because i want to try out cwm touch recovery. I have tried flashing new recovery and it says its complete and everything went well(via cmd). I've also tried flashing new recovery through rom manager, when im installing cwm touch it says its been complete but doesnt actually do anything, and when im trying to flash cwrp it says installation failed.
What could be the problem?
Click to expand...
Click to collapse
First are your bootloader Unlocked not Relocked
Second use command fastboot flash recovery recovery.img
Third try Philz recovery it is really good.
Four When you flash the recovery after this run the command fastboot erase cache after this restart in recovery and you will see your new recovery

Thant said:
First are your bootloader Unlocked not Relocked
Second use command fastboot flash recovery recovery.img
Third try Philz recovery it is really good.
Four When you flash the recovery after this run the command fastboot erase cache after this restart in recovery and you will see your new recovery
Click to expand...
Click to collapse
Thanks for such a quick response, ive tried your method. I even tried flashing it through terminal on my phone. This is the message i get:

Verify download
Sent from my One X using Tapatalk

and313 said:
Verify download
Sent from my One X using Tapatalk
Click to expand...
Click to collapse
What do you mean? I've downloaded clockworkmod recovery touch 5.8.4.0

JacobCob said:
Thanks for such a quick response, ive tried your method. I even tried flashing it through terminal on my phone. This is the message i get:
Click to expand...
Click to collapse
Are you kidding the recovery must be on the PC in the folader where is your fastboot not on the SD Card on the phone you can't flash recovery from SD Card and ROm Manager not working on S-ON device!!!!

Thant said:
Are you kidding the recovery must be on the PC in the folader where is your fastboot not on the SD Card on the phone you can't flash recovery from SD Card and ROm Manager not working on S-ON device!!!!
Click to expand...
Click to collapse
I did flash it through my pc, it says its complete and that everything is okay but doesnt actually change the recovery.

JacobCob said:
I did flash it through my pc, it says its complete and that everything is okay but doesnt actually change the recovery.
Click to expand...
Click to collapse
after install from the PC run fastboot erase cache and restart the phone to bootloader and go in recovery and be sure your recovery in fastboot folder is not the same you install previous

Thant said:
after install from the PC run fastboot erase cache and restart the phone to bootloader and go in recovery and be sure your recovery in fastboot folder is not the same you install previous
Click to expand...
Click to collapse
okay ive flashed phillz recovery and it works! thank you its way better than clockworkmod mainly the UI!

JacobCob said:
okay ive flashed phillz recovery and it works! thank you its way better than clockworkmod mainly the UI!
Click to expand...
Click to collapse
Good

JacobCob said:
Hey guys, first of all im sorry if its in the wrong section(im a noob).
So, ive recently rooted my phone via the htcdev, everything went well ive flashed cwm and im using cm as my rom but my problem is that i cannot flash a new recovery. I just want to have cwm touch because i want to try out cwm touch recovery. I have tried flashing new recovery and it says its complete and everything went well(via cmd). I've also tried flashing new recovery through rom manager, when im installing cwm touch it says its been complete but doesnt actually do anything, and when im trying to flash cwrp it says installation failed.
What could be the problem?
Click to expand...
Click to collapse
try flashing philz recovery 5.15.up. this is the best recovery for hox. you can flash roms easily with this. before flashing make sure that your device should meet all the needs.

rudresh128631 said:
try flashing philz recovery 5.15.up. this is the best recovery for hox. you can flash roms easily with this. before flashing make sure that your device should meet all the needs.
Click to expand...
Click to collapse
Are you read the thread the problem been solved before three post!!!

Reading is a gift.....use it !

[Q] ViperOne 5.8 Bootloop HTC One M7

*FIXED*
The problem turned out to be the wrong TWRP version for verizon phones, the correct version is here http://crackflasher.com/openrecovery-twrp-2-7-0-1-m7wlv-img-htc-one-verizon-openrecovery/
Hello, I will not pretend to be an expert in this area but I feel I have most of my bases covered in this case and would appreciate some help.
First, the phone,
Unlocked
M7_WLV PVT SHIP S-OFF RH
CID-11111111
HBOOT-1.56.0000
RADIO-1.13.41.0109_2
OS-3.11.605.1
The Problem:
Whenever I flash the rom via TWRP everything seems to work fine and the install claims it is successful however this is clearly not the case as when i try to boot the phone it bootloops getting only as far as the HTC screen (with the red development only text underneath)
Next, Pre-reqs:
Phone obviously is unlocked S-off and supercid
TWRP 2.7.0.0 is flashed to the phone (when i try 2.6.3.3 the phone only boot loops even recovery loops)
SuperSU installed
Weaksauce installed
Usb-debugging enabled
all htc drivers installed on Pc
adb installed on pc + working
fastboot installed on pc +working
Steps Taken:
I have tried both pushing the Rom.zip and copying the rom.zip to the sdcard on the phone, this has made no difference
I do the factory reset (wipe) before installing
I do the factory reset (wipe) after installing
I have unchecked all the options and made the most basic install I can
I have tried to flash the TWRP version that came on the ROM, this also causes recovery bootloop
I have tried downloading the rom directly to the phone
I have made sure the MD5 codes match
I have tried flashing the boot.img separately via fastboot
My most recent attempts Aroma Log is attached
Any help would be greatly appreciated!!!!!

PblicEnemy said:
Hello, I will not pretend to be an expert in this area but I feel I have most of my bases covered in this case and would appreciate some help.
First, the phone,
Unlocked
M7_WLV PVT SHIP S-OFF RH
CID-11111111
HBOOT-1.56.0000
RADIO-1.13.41.0109_2
OS-3.11.605.1
The Problem:
Whenever I flash the rom via TWRP everything seems to work fine and the install claims it is successful however this is clearly not the case as when i try to boot the phone it bootloops getting only as far as the HTC screen (with the red development only text underneath)
Next, Pre-reqs:
Phone obviously is unlocked S-off and supercid
TWRP 2.7.0.0 is flashed to the phone (when i try 2.6.3.3 the phone only boot loops even recovery loops)
SuperSU installed
Weaksauce installed
Usb-debugging enabled
all htc drivers installed on Pc
adb installed on pc + working
fastboot installed on pc +working
Steps Taken:
I have tried both pushing the Rom.zip and copying the rom.zip to the sdcard on the phone, this has made no difference
I do the factory reset (wipe) before installing
I do the factory reset (wipe) after installing
I have unchecked all the options and made the most basic install I can
I have tried to flash the TWRP version that came on the ROM, this also causes recovery bootloop
I have tried downloading the rom directly to the phone
I have made sure the MD5 codes match
I have tried flashing the boot.img separately via fastboot
My most recent attempts Aroma Log is attached
Any help would be greatly appreciated!!!!!
Click to expand...
Click to collapse
I noticed you said you do the factory reset after you flash Viper? You'll only want to wipe before you flash the rom. I'm guessing that's you're issue if I understood correctly.
Sent from my HTC6500LVW using Tapatalk

brholt6 said:
I noticed you said you do the factory reset after you flash Viper? You'll only want to wipe before you flash the rom. I'm guessing that's you're issue if I understood correctly.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
I see now I might not have been as clear as I meant to be. When I said that i wiped before and after I meant that I performed both wipes seprately from each other and a third time together. I only tried the wipe after flash because it was a suggestion from another developer website. It would seem that this is not the solution, as the bootloop happens regardles of wipe before, wipe after, or wipe before and after or even no wipe at all. Thanks for the reply!

Try this. Download this recovery http://www.androidfilehost.com/?fid=23329332407584851.
Use fastboot to flash the recovery.
Code:
fastboot erase cache
Code:
fastboot erase recovery
Code:
fastboot flash recovery nameofrecovery.img
Code:
fastboot reboot-bootloader
Go to recovery.
In recovery go to wipe - advanced - check boot, system, data, and cache. Proceed with the wipe.
Flash your rom
Boot up.

cmlusco said:
Try this
Use fastboot to flash the recovery.
Code:
fastboot erase cache
Code:
fastboot erase recovery
Code:
fastboot flash recovery nameofrecovery.img
Code:
fastboot reboot-bootloader
Go to recovery.
In recovery go to wipe - advanced - check boot, system, data, and cache. Proceed with the wipe.
Flash your rom
Boot up.
Click to expand...
Click to collapse
Everything went very well except 2 things. 1: when issuing the "fastboot erase recovery" command in fastboot it failed and came back as "not allowed". 2: the rom installation failed and came back as , error: 7. I tried to boot to system regardless of the error message but the boot loop continues
The new error log is attached again. Thanks for the reply! (and the TWRP update!)

Seems to be an issue with the rom. The log shows everything going fine until the very last step where it tries to change the permissions of an apk and fails, therfore aborting the whole install.
Code:
Setting permissions
ApplyParsedPerms: removexattr of /system/app/BasicDreams.apk to 0 failed: Operation not supported on transport endpoint
script aborted: set_metadata_recursive: some changes failed
I would post that in the roms thread.

cmlusco said:
Seems to be an issue with the rom. The log shows everything going fine until the very last step where it tries to change the permissions of an apk and fails, therfore aborting the whole install.
Code:
Setting permissions
ApplyParsedPerms: removexattr of /system/app/BasicDreams.apk to 0 failed: Operation not supported on transport endpoint
script aborted: set_metadata_recursive: some changes failed
I would post that in the roms thread.
Click to expand...
Click to collapse
I would love to but unfortunately I am not allowed to post there until I have 10 posts and have been cleared by a mod. Do you think it could have anything to do with the temproot i installed (weaksauce) because it works by installing a root every time the phone boots up, or would that be deleted when the wipe is performed?

When you wiped before the rom install it should wipe out everything including weaksauce. The reason it wont boot is because you have no or an incomplete rom. I would just flash another rom in the mean time till you can figure out whats up with viper. Or you could do an ruu if you wanted to be stock.

cmlusco said:
When you wiped before the rom install it should wipe out everything including weaksauce. The reason it wont boot is because you have no or an incomplete rom. I would just flash another rom in the mean time till you can figure out whats up with viper. Or you could do an ruu if you wanted to be stock.
Click to expand...
Click to collapse
I really want viper because of the customization, do you know of any other sources that I could acquire viper from? or would it be possible to install an older version and update it?
*UPDATE* I tried to install Android Revolution HD just now to see if it would work and I end up with the exact same error, seems like a phone problem to me. is there anyway to put my phone completely back to the way i got it out of the box and start over?

Yes you can do an ruu to get back to stock. But you need fastboot to do it. You probably dont have the correct drivers installed on your pc. What version of windows you runing?

cmlusco said:
Yes you can do an ruu to get back to stock. But you need fastboot to do it. You probably dont have the correct drivers installed on your pc. What version of windows you runing?
Click to expand...
Click to collapse
Windows 7 64bit. I use fastboot all the time with this phone so I should be able to use it.

Nevermind, i was thinking this was a different thread. Anyways you will need to change your cid back to vzw__001. Then download the ruu from the second post of santods stock rom thread in development section.
fastboot oem rebootRUU
fastboot flash zip ruufilename.zip
(may fail with flush error, do command again)
fastboot reboot

PblicEnemy said:
I really want viper because of the customization, do you know of any other sources that I could acquire viper from? or would it be possible to install an older version and update it?
*UPDATE* I tried to install Android Revolution HD just now to see if it would work and I end up with the exact same error, seems like a phone problem to me. is there anyway to put my phone completely back to the way i got it out of the box and start over?
Click to expand...
Click to collapse
The big problem with Android Revolution is that it isn't made for the Verizon HTC One. Make sure you you're only flashing roms from the Verizon HTC One thread or you've talked to the Dev. Flashing roms meant for other carriers can really screw you up.
Sent from my HTC6500LVW using Tapatalk

Thanks to both of you, good information and helpful, I'm still hoping I can figure out the set_metadata_recursive error, I have another thread going specifically for it!

hboot recovery issue

Hey there guys, I've just unlocked Bootloader as described on the htcdev./ site,
Unfortunately, now when I enter HBOOT, no only do I recieve a "failed to open usb master mode" and "pj46img.zip" fail message, but when I click "Recovery", my phone switches back to fastboot. I need to backup my system to downgrade and root afterwards.. anyways
Anyone experienced this before or has any idea what to do?
The Model is: HTC Endeavor , Android ver. 4.2.2, Sense 5...
and...
What the status bar tells me :
*** UNLOCKED ***
ENDEAVORU PVT SHIP S-ON RL
HBOOT-1.72.0000
CPLD-None
MICROP-None
RADIO-5.1204.167.31
eMMC-bootmode: disabled
CPU-bootmode : disabled
HW secure boot: enabled
MODEM PATH : OFF
Jun 21 2013,18:24:41

Error message is normal because you have the usb connected. Without cable you won't get the message.
Second when you are in the bootloader do the command :
Fastboot erase cache
And you need to flash or boot a custom recovery !
Fastboot boot recovery.img
Or
Fastboot flash recovery recovery.img
The custom recovery has to be named "recovery.img" and be placed in the fastboot folder on the pc !
And what do you want to downgrade ?

Cache erased
Mr Hofs said:
Error message is normal because you have the usb connected. Without cable you won't get the message.
Second when you are in the bootloader do the command :
Fastboot erase cache
And you need to flash or boot a custom recovery !
Fastboot boot recovery.img
Or
Fastboot flash recovery recovery.img
The custom recovery has to be named "recovery.img" and be placed in the fastboot folder on the pc !
And what do you want to downgrade ?
Click to expand...
Click to collapse
Wow, thanks for such a quick answer.. sorry for not coming and thanking sooner...
Anyways.. I erased the Cache as recommended.
The reason why downgrade was because somewhere I read there are problems with rooting my phone on 4.2.2 so I thought downgrading to 4.1.1 would be adequate... Anyways recent research pushed me into believing it is not necessary...
Yeah, so anyway I've been looking for a custom recovery to use as you said...
version-main: 4.18.401.2
cidnum: HTC__032
Do I need to find a recovery for exactly my CIDnumber?

Custom recovery to enable flashing of all roms (sense 5 and kit Kat)
https://www.dropbox.com/s/14c1ikgsp38axwv/twrp-recovery2.img

Thanks again!
Mr Hofs said:
Custom recovery to enable flashing of all roms (sense 5 and kit Kat)
Click to expand...
Click to collapse
Thank you many times! :good:

Stuck... damn it!
Yeah, umm hello there again.
So I used the Cyanogenmod recovery in the end...
Anyways I let myself led by the guide posted by Thömy (http://forum.xda-developers.com/showthread.php?t=2583037)...
Everything went fine, I got the bootloader unlocked (before already), the recovery provided by ClockWorkMod, did a Data wipe, downloaded everything necessary, booted into Recovery... but when I got to flash the CM 11.0.zip (installing from the zip file in recovery) It failed..
So for no reason i decided to simply restart the phone and try whatever will I find then.. I haven't got past the white/green HTC screen though and I'm stuck at it... I can get back to recovery or the Bootloader, but nothing more, nothing less...
Any Idea?.. I'm struggling with it for a few hour now and feel lost

MartyPavelka said:
Yeah, umm hello there again.
So I used the Cyanogenmod recovery in the end...
Anyways I let myself led by the guide posted by Thömy (http://forum.xda-developers.com/showthread.php?t=2583037)...
Everything went fine, I got the bootloader unlocked (before already), the recovery provided by ClockWorkMod, did a Data wipe, downloaded everything necessary, booted into Recovery... but when I got to flash the CM 11.0.zip (installing from the zip file in recovery) It failed..
So for no reason i decided to simply restart the phone and try whatever will I find then.. I haven't got past the white/green HTC screen though and I'm stuck at it... I can get back to recovery or the Bootloader, but nothing more, nothing less...
Any Idea?.. I'm struggling with it for a few hour now and feel lost
Click to expand...
Click to collapse
Use the Recovery that Mr Hofs gave you and flash the CM 11 package. Should work. CWM recovery sometimes gives you errors while flashing since you may have to modify the updater-script with-in the package to flash successful.

Nice, felt some progression
aromerblz said:
Use the Recovery that Mr Hofs gave you and flash the CM 11 package. Should work. CWM recovery sometimes gives you errors while flashing since you may have to modify the updater-script with-in the package to flash successful.
Click to expand...
Click to collapse
Cool :good:
So I used the Recovery from el Maestro and flashed the CM 11 package.
I got to a "Cyanogenmod" booting screen at which I'm stuck...
It updated some files but, that's all and the arrow wheel keeps spinning? any Idea?
btw: I'm really sorry if someone already had this problem,
I swear I spent hours looking for one, but when I found a similar one,
it wasn't really what I was looking for in the end
[EDIT] Also when I try to boot the system with the boot.img file included in cm-11 package, I'm not stuck on the Cyanogenmod screen but all the way back on the HTC logo screen again

Flashed the boot.img from the cm11 zip ?

Flash instead of Boot
Mr Hofs said:
Flashed the boot.img from the cm11 zip ?
Click to expand...
Click to collapse
Yes, I until now was directly booting "fastboot boot boot.img" with cmd on computer.
Now when I flashed it into the device, I cannot even get to the Cyanogenmod screen, hehe

MartyPavelka said:
Yes, I until now was directly booting "fastboot boot boot.img" with cmd on computer.
Now when I flashed it into the device, I cannot even get to the Cyanogenmod screen, hehe
Click to expand...
Click to collapse
The flash command should be "fastboot flash boot boot.img" are you sure you are doing it right?

aromerblz said:
The flash command should be "fastboot flash boot boot.img" are you sure you are doing it right?
Click to expand...
Click to collapse
yep Did it exactly this way ... It now behaves the same as when only booted with the boot.img :/

Did you perform a full wipe within the custom recovery before installing the cm zip ? Seems to me you forgot to wipe something !

MartyPavelka said:
yep Did it exactly this way ... It now behaves the same as when only booted with the boot.img :/
Click to expand...
Click to collapse
Ok try this..
Assuming you already did a full nandroid backup, do the following:
1. Do a FULL wipe on your device.
2. Flash the ROM again
3. Reboot to bootloader
4. Flash the boot.img again
5. Reboot
6.Thank me if it works.
Should work, that's normally the steps I take when flashing ROM's and have never failed me.

If he flashes the boot.img alresdy its a wipe issue. Doesnt matter when you flash it because it's not going to be changed installing a rom or wiping partitions from within the recovery (definitely not on a s-on device)
6: kinda corny to mention that isn't it ! Bit of a desperate call for appreciation......not confident enough you need confirmation

Got past it!
aromerblz said:
Ok try this..
Assuming you already did a full nandroid backup, do the following:
1. Do a FULL wipe on your device.
2. Flash the ROM again
3. Reboot to bootloader
4. Flash the boot.img again
5. Reboot
6.Thank me if it works.
Should work, that's normally the steps I take when flashing ROM's and have never failed me.
Click to expand...
Click to collapse
Well, wow... ok... I got past the logo screen and I now get keyboard failure messages... but wow... thanks... A huge rock fell of my chest... Thanks to both of you... I did a full wipe again.. I guess it was a wipe issue afterall -_- what a noobfailure..

I don't think it "kills to try" like I mentioned at the bottom that's how I usually do mines when am blocked by issues. and NO not desperate for appreciation either.
---------- Post added at 01:33 PM ---------- Previous post was at 01:31 PM ----------
MartyPavelka said:
Well, wow... ok... I got past the logo screen and I now get keyboard failure messages... but wow... thanks... A huge rock fell of my chest... Thanks to both of you... I did a full wipe again.. I guess it was a wipe issue afterall -_- what a noobfailure..
Click to expand...
Click to collapse
Have you flashed the GAPPS?

aromerblz said:
I don't think it "kills to try" like I mentioned at the bottom that's how I usually do mines when am blocked by issues. and NO not desperate for appreciation either.
---------- Post added at 01:33 PM ---------- Previous post was at 01:31 PM ----------
Have you flashed the GAPPS?
Click to expand...
Click to collapse
Yeah... Wrong version

aromerblz said:
and NO not desperate for appreciation either
Click to expand...
Click to collapse
LOL !

MartyPavelka said:
Yeah... Wrong version
Click to expand...
Click to collapse
Just flash the correct one and you should be good to go.. :victory:

Recovery installed, but cant boot into it

Hello.
I would appreciate some help with this ...
I followed the 'How to Install CyanogenMod on the HTC One (M8) ("m8")' on the Cyanogen wiki and everything seemed to be going normally until I get to step 8, 'reboot the device into recovery'. Whenever I do, either by powering down and holding the Volume Down and Power buttons until HBOOT appears, then navigating to Recovery and selecting it - OR by simply navigate to HBOOT > Recovery directly after flashing the recovery, it says it is booting into recovery in pink text but then just goes straight to the Fastboot Menu.
I obtained S-Off using Sunshine and recovery was flashed as a root user in linux - both without any hitches. I tried this with both the twrp-2.8.7.0-m8.img linked to by the Cyanogen wiki and with the latest image from twrp, twrp-3.0.2-0-m8.img, with the same result. USB Debugging is on.
I'm attaching pics of the recovery flash dialogue from the linux terminal and of the fastboot screen that keeps coming up.
What am I doing wrong/missing here guys? Why can't I get into recovery??
Many thanks.

I still can't figure this out. Can anyone help?

krisbo9000 said:
I still can't figure this out. Can anyone help?
Click to expand...
Click to collapse
as your bootloader is outdated it may not enter to recovery. try another low version. and also change CID to super CID. you can flash MM firmware and use twrp 3.0.2-0. what is your current MID?

try fastboot boot recovery twrp.****.img
id also try a different recovery as well as updating firmware as suggested.

I changed the CID to a super CID and then flashed TWRP 3.02-0 and it worked!
Thanks so much for the help.

umesh.lk said:
as your bootloader is outdated it may not enter to recovery.
Click to expand...
Click to collapse
TWRP 2.8.7 should work fine on LP firmware.
---------- Post added at 11:46 AM ---------- Previous post was at 11:45 AM ----------
krisbo9000 said:
I changed the CID to a super CID and then flashed TWRP 3.02-0 and it worked!
Click to expand...
Click to collapse
I don't see what SuperCID would have to do with anything. Possibly a placebo.
Often fastboot erase cache, and installing TWRP again, will fix the random issue of not being able to boot into TWRP.