Hello everyone. I got a M8s from a friend wich is stuck in bootloader. The recovery didn't work at the begin, so I flashed twrp-recovery-2.8.6.0-m8s-qlul.img (flashing recovery using htc_fastboot.exe flash recovery theimagename.img) and it worked, then I tried to install a custom ROM Android_Pandora_Rom_1.2_(Discontinued).zip wich went all the steps fine until: Optimizing applications 8 of 204..then phone shat down to black screen. I booted back to bootloader, recovery, wiped and go for a new install, same issue.
After that, I was going to install lineage-13.0-20170715-UNOFFICIAL-m8qlul.zip where the developer of this rom recommends twrp-3.0.2-0-m8ql.img so I tried to flash it (flashing recovery using htc_fastboot.exe flash recovery theimagename.img), then tried to acces recovery, brings me back to bootloader so fast, rebooted bootloader, tried again, same problem. Tried the fasboot erase cache, no help.
The Hboot state is Unlocked and the S is ON. I tried some other recovery images, as stock_signed or 3.0.1, tried the one from M8 ToolKit but all failed and I still can't access recovery, everyting I do, it brings me back to bootloader. I did htc_fastboot boot recoveryfile.img wich works, but useless, the dd if= method to set the recovery permanent load did not work after reboot, /data and /system can't be mountet, it seems the "boot recovery" option is 99% readonly.
Any advice, any help please? It would be much appreciated! Thanks in advance!
Hi McBad,
you could try the following. I also had some problems to access the recovery.
- Again bring the phone into fastboot, flash the 2.8 recovery and access it
- Do a wipe for factory reset, not just only cache
- after that try to flash the twrp-3.0.1-0-m8ql.img version, the other one worked for me neither
- the try to install the custom ROM LOS13
I hope this will help you.
clone
It would be great if that would work, but flashing a recovery does not work. I flash it, success message, try to access it, vibrates and bootloader pops back instantly. That is the problem.
Sorry for double post, but can anyone help me with this? This is the second day I struggle to make it work. Any chance to make the hboot locked again? It didn't work with oem lock command. I would like to lock it so I can put an official zip on sdcard so the hboot to restore it to factory stock, some RUU. Or get it s-off so I can flash a rom from fastboot? The phone does not have any ROM on it, image crc results system 0x0, recovery 0x0. Please, help!
Have you tried sideloading twrp ?
McBad said:
Sorry for double post, but can anyone help me with this? This is the second day I struggle to make it work. Any chance to make the hboot locked again? It didn't work with oem lock command. I would like to lock it so I can put an official zip on sdcard so the hboot to restore it to factory stock, some RUU. Or get it s-off so I can flash a rom from fastboot? The phone does not have any ROM on it, image crc results system 0x0, recovery 0x0. Please, help!
Click to expand...
Click to collapse
Did you use HTC fastboot ?
Yes, I used htc_fastboot. Use sideloading? Like boot the img file directly? Tried that too.
McBad said:
Yes, I used htc_fastboot. Use sideloading? Like boot the img file directly? Tried that too.
Click to expand...
Click to collapse
Is there any way you could flash twrp 2.8 again? Once in that recovery you have sideloading option which you could use to transfer latest recovery onto your device. Are we talking about the same process?
McBad said:
Yes, I used htc_fastboot. Use sideloading? Like boot the img file directly? Tried that too.
Click to expand...
Click to collapse
Sideload as follows ....
McBad said:
Hello everyone. I got a M8s from a friend wich is stuck in bootloader. The recovery didn't work at the begin, so I flashed twrp-recovery-2.8.6.0-m8s-qlul.img (flashing recovery using htc_fastboot.exe flash recovery theimagename.img) and it worked, then I tried to install a custom ROM Android_Pandora_Rom_1.2_(Discontinued).zip wich went all the steps fine until: Optimizing applications 8 of 204..then phone shat down to black screen. I booted back to bootloader, recovery, wiped and go for a new install, same issue.
After that, I was going to install lineage-13.0-20170715-UNOFFICIAL-m8qlul.zip where the developer of this rom recommends twrp-3.0.2-0-m8ql.img so I tried to flash it (flashing recovery using htc_fastboot.exe flash recovery theimagename.img), then tried to acces recovery, brings me back to bootloader so fast, rebooted bootloader, tried again, same problem. Tried the fasboot erase cache, no help.
The Hboot state is Unlocked and the S is ON. I tried some other recovery images, as stock_signed or 3.0.1, tried the one from M8 ToolKit but all failed and I still can't access recovery, everyting I do, it brings me back to bootloader. I did htc_fastboot boot recoveryfile.img wich works, but useless, the dd if= method to set the recovery permanent load did not work after reboot, /data and /system can't be mountet, it seems the "boot recovery" option is 99% readonly.
Any advice, any help please? It would be much appreciated! Thanks in advance!
Click to expand...
Click to collapse
You can't install lineage if you haven't upgraded your device with latest official update. I would try reinstaling twrp 2.8, do a wipe of cache, dalvik cache and system, Sideload CM 12; and see how it goes. As well, while in twrp I would try relocking bootloader but only after an unsuccessful attempt to flash said rom. I don't know what your experience with soft bricked devices is, but sometimes it takes a while, different usb cable or usb slot on your PC, correct files in adb folder, re-download of rom or recovery because it easily gets corrupted while downloading. And obviously a fully charged device. Let us know how it goes.
Related
First of all, I'm running the RUU GPE edition rom for my HTC one M8, I love it. However I want xposed framework, and all of it's goodies too, otherwise imo I should have stuck with Sense version. There is one problem though. I can't seem to boot into recovery, at all. When I attempt to boot into recovery via ADB, or from the bootloader it just shows me the google logo for a while, and restarts back to android homescreen.
Could this be because I may have flashed the wrong recovery? Initially I flashed the "hammerhead" recovery from TWRP, whatever the hell that is(thought I was getting it specific for my HTC one), later once I noticed I did that I simply reflashed the correct recovery. Could this be why, if so, how can I fix that? Can I remove the recovery and reflash it?
Spewed said:
Can I remove the recovery and reflash it?
Click to expand...
Click to collapse
No, flashing a recovery removes the old one, but you should do:
fastboot erase cache
BenPope said:
No, flashing a recovery removes the old one, but you should do:
fastboot erase cache
Click to expand...
Click to collapse
I assumed flashing another recovery merely erased the old one. so I tried "fastboot erase cache", then "fastboot flash recovery openrecovery-twrp-2.7.0.1-m8.img", to no avail, still unable to boot into my recovery by "adb reboot recovery", or any other method. I'm S-off, bootloader unlocked. When I was running sense I had s-off, custom recovery, root and twrp.
Any other ideas?
Spewed said:
I assumed flashing another recovery merely erased the old one. so I tried "fastboot erase cache", then "fastboot flash recovery openrecovery-twrp-2.7.0.1-m8.img", to no avail, still unable to boot into my recovery by "adb reboot recovery", or any other method. I'm S-off, bootloader unlocked. When I was running sense I had s-off, custom recovery, root and twrp.
Any other ideas?
Click to expand...
Click to collapse
Hmm, I assume you don't have a Sprint or Verizon M8?
BenPope said:
Hmm, I assume you don't have a Sprint or Verizon M8?
Click to expand...
Click to collapse
I have the ATT version.
All of this was fine, until I made the switch to GPE, which I was under the impression I actually downloaded the rooted version, seeing as how that is the one I selected. Sadly, no root, so I began the rooting method over, to no avail.
Well, apparently I got twrp on there.
I went ahead and got the HTC One all in one toolkit to see if somehow that might flash the recovery. Of course, the actual transfer of the recovery seemed to hang, and never finish. So I unplugged the phone, it said it failed. I attempted to manually boot into recovery using power and volume down. Of course, it didn't work. Attempted to flash the recovery again using the all in one toolkit. Same scenario, it hangs and fails. Once again, I manually tried to boot into recovery. This time, miraculously it works. What the hell? haha
[Please help]Bootloop, adb "unauthorized, fastboot flash not working, CWN not working
Hi everybody!
First of all, I'm not an Android noob, I've experience with fastboot and adb commands, android app developement and Stock/Custom Roms/recoveries in general.
Also, I extensively used google and the xda search for this issue but unfortunately didn't come any further.
To make things a little shorter, and avoid a wall of text, here are my problems.
- I'm using CM11 and CWM on a rooted Maguro.
- Initial Problem: Device is stuck in a Bootloop and I want to backup my personal data
- Therfore, wiping is not desired.
- I can boot into Downloading Mode (e.g. for Odin) and Bootloader Mode
- I can boot into recovery (CWM 6.0.4.7) through bootloader menu or fastboot
- In recovery, adb recognizes the device but it is displayed as "unauthorized", so I cant pull any files that way
- Afaik, the device should be accessible in recovery mode, so I thought maybe it would be a good idea, if I installed TWRP instead of CWM and see if it works then.
- I tried installing the new recovery (TWRP) through fastboot (fastboot erase recovery, fastboot flash recovery), and fastboot states, that it was successfull. HOWEVER, when I reboot, the recovery is still CWM and untouched.
- I read, that CM11 may under certain circumstances overwrite any recovery with CWM ob boot, so I made sure to direktly boot into recovery from the bootloader after flashing TWRP over fastboot. Still, CWM is untouched.
- I tried installing TWRP over Odin. Odin too states, that flashing the recovery was successful, but again, CWM remains untouched.
- Then I tried erasing and reflashing "bootloader", "radio", "boot" and a stock "system" through fastboot. (I carefully did not erase "userdata"). All finished successfully according to fastboot but a reboot showed the system in the same state as before.
- At this point, I assume, that I don't have write-access to the device anymore, as silly as that sounds.
At this point, I'm stuck at a dead end and don't know how to proceed, so every help you could provide would be incredibly appreciated.
Of course, I'm also willing to go into more details, but in order to keep this post from getting too long, I didn't do it in the first place.
Many thanks in advance for oyu assistance!
Greetings
Jules
i have the same problem
jules.renz said:
Hi everybody!
First of all, I'm not an Android noob, I've experience with fastboot and adb commands, android app developement and Stock/Custom Roms/recoveries in general.
Also, I extensively used google and the xda search for this issue but unfortunately didn't come any further.
To make things a little shorter, and avoid a wall of text, here are my problems.
- I'm using CM11 and CWM on a rooted Maguro.
- Initial Problem: Device is stuck in a Bootloop and I want to backup my personal data
- Therfore, wiping is not desired.
- I can boot into Downloading Mode (e.g. for Odin) and Bootloader Mode
- I can boot into recovery (CWM 6.0.4.7) through bootloader menu or fastboot
- In recovery, adb recognizes the device but it is displayed as "unauthorized", so I cant pull any files that way
- Afaik, the device should be accessible in recovery mode, so I thought maybe it would be a good idea, if I installed TWRP instead of CWM and see if it works then.
- I tried installing the new recovery (TWRP) through fastboot (fastboot erase recovery, fastboot flash recovery), and fastboot states, that it was successfull. HOWEVER, when I reboot, the recovery is still CWM and untouched.
- I read, that CM11 may under certain circumstances overwrite any recovery with CWM ob boot, so I made sure to direktly boot into recovery from the bootloader after flashing TWRP over fastboot. Still, CWM is untouched.
- I tried installing TWRP over Odin. Odin too states, that flashing the recovery was successful, but again, CWM remains untouched.
- Then I tried erasing and reflashing "bootloader", "radio", "boot" and a stock "system" through fastboot. (I carefully did not erase "userdata"). All finished successfully according to fastboot but a reboot showed the system in the same state as before.
- At this point, I assume, that I don't have write-access to the device anymore, as silly as that sounds.
At this point, I'm stuck at a dead end and don't know how to proceed, so every help you could provide would be incredibly appreciated.
Of course, I'm also willing to go into more details, but in order to keep this post from getting too long, I didn't do it in the first place.
Many thanks in advance for oyu assistance!
Greetings
Jules
Click to expand...
Click to collapse
ROM: FML-AOSP-5.0-20141207-maguro.zip (http://forum.xda-developers.com/galaxy-nexus/development/rom-fml-fork-life-06-05-2014-v2-t2764064)
Recovery: CWM V6.0.5.1
majeida said:
ROM: FML-AOSP-5.0-20141207-maguro.zip (http://forum.xda-developers.com/galaxy-nexus/development/rom-fml-fork-life-06-05-2014-v2-t2764064)
Recovery: CWM V6.0.5.1
Click to expand...
Click to collapse
Sorry, but I can't see, how this is supposed to help, since my problem is not "I'm looking for a new ROM"
sorry for the misunderstanding
jules.renz said:
Sorry, but I can't see, how this is supposed to help, since my problem is not "I'm looking for a new ROM"
Click to expand...
Click to collapse
sorry i have the same problem .
I'm using FML-AOSP-5.0-20141207-maguro and CWM V6.0.5.1 on a rooted Maguro.
Your personal data includes what?? Apps or photos and videos?
varadparulekarofficial said:
Your personal data includes what?? Apps or photos and videos?
Click to expand...
Click to collapse
yes
have you tried using the fastboot boot "/path/to/recovery.img-name-here" fastboot option to just directly boot into twrp without installing it? I used to use fastboot boot for different recovery and boot imgs I wanted to test out first before actually installing them. and I had a similar issue to what yours sounds like before in which I was able to use fastboot boot recovery.img when I wasn't able to get different custom recovery to install at the time.
ashclepdia said:
have you tried using the fastboot boot "/path/to/recovery.img-name-here" fastboot option to just directly boot into twrp without installing it? I used to use fastboot boot for different recovery and boot imgs I wanted to test out first before actually installing them. and I had a similar issue to what yours sounds like before in which I was able to use fastboot boot recovery.img when I wasn't able to get different custom recovery to install at the time.
Click to expand...
Click to collapse
I used this method
*I boot into costum temporary recovery "TWRP 2.8.3.0" Then I tried erasing and reflashing "bootloader", "radio", "boot" and new "system" through recovery All finished successfully according to TWRP but a reboot showed the system in the same state as before
G'day guys,
I tried to install the CM 11 Rom on my phone (HTC One X 2012 international model), i unlocked the bootloader on the Htcdev site, rooted the phone successfully,
then i rebooted in recovery using ClockworkMod Recovery v5.8.4.0, made a back-up rom then wipe data/factory reset and installed CM 11 rom (cm-11-20140804-SNAPSHOT-M9-endeavoru.zip) and
it came up with Status 7 error and install aborted.....and now it's stuck in a boot loop, when i reboot it boots back into the Clockwork Mod recovery
I tried turning it off and restarting, i've ran the battery down but it still reboots in cwm recovery...
Is there anyway to fix this or have i stuffed my phone?
Any help would be greatly appreciated.....
Troy67 said:
G'day guys,
I tried to install the CM 11 Rom on my phone (HTC One X 2012 international model), i unlocked the bootloader on the Htcdev site, rooted the phone successfully,
then i rebooted in recovery using ClockworkMod Recovery v5.8.4.0, made a back-up rom then wipe data/factory reset and installed CM 11 rom (cm-11-20140804-SNAPSHOT-M9-endeavoru.zip) and
it came up with Status 7 error and install aborted.....and now it's stuck in a boot loop, when i reboot it boots back into the Clockwork Mod recovery
I tried turning it off and restarting, i've ran the battery down but it still reboots in cwm recovery...
Is there anyway to fix this or have i stuffed my phone?
Any help would be greatly appreciated.....
Click to expand...
Click to collapse
Too old recovery you must to use TWRP6.0.1 or higer to be able to install CM11 becouse is KitKat based rom read the OP in CM11 thread and download correct TWRP or CWM. Try with this CWM6.0.4.8
Thanks, I downloaded the CWM 6.0.4.8 like you said, now i have to try and get it out of the boot loop, I've tried about 6 different sites and their methods to fix it but none of them have worked, its still stuck in recovery mode.
My phone doesnt even register when i plug it into my pc either.
Is there any advice you can give to help with this?
Troy67 said:
Thanks, I downloaded the CWM 6.0.4.8 like you said, now i have to try and get it out of the boot loop, I've tried about 6 different sites and their methods to fix it but none of them have worked, its still stuck in recovery mode.
My phone doesnt even register when i plug it into my pc either.
Is there any advice you can give to help with this?
Click to expand...
Click to collapse
are you flashed boot.img via fastboot?
Thant said:
are you flashed boot.img via fastboot?
Click to expand...
Click to collapse
In the instructions it said to install the ROM and then flash the boot.img.
I didnt get past installing the rom before it bootlooped.
Troy67 said:
In the instructions it said to install the ROM and then flash the boot.img.
I didnt get past installing the rom before it bootlooped.
Click to expand...
Click to collapse
go in fastboot and flash the boot.img. Then try to install the rom again
Thant said:
go in fastboot and flash the boot.img. Then try to install the rom again
Click to expand...
Click to collapse
Tried to flash boot.img, pressed enter and it stayed on "waiting on device".
Got into bootloader on phone and even tried a factory reset and got nowhere.
Everytime i selected an option in bootloader ie. fastboot, recovery, it just reboots into recovery.
Troy67 said:
Tried to flash boot.img, pressed enter and it stayed on "waiting on device".
Got into bootloader on phone and even tried a factory reset and got nowhere.
Everytime i selected an option in bootloader ie. fastboot, recovery, it just reboots into recovery.
Click to expand...
Click to collapse
go in bootloader then select fastboot then connect the phone to computer and flash the boot.img if you don't see your device install the correct drivers for that
Thant said:
go in bootloader then select fastboot then connect the phone to computer and flash the boot.img if you don't see your device install the correct drivers for that
Click to expand...
Click to collapse
I dont know how many times i've tried to do a system restore in cwm recovery this week and failed each time, but tonight i tried and after the 3rd attempt it worked.
My phone is back to normal again.
Will be using the wiki instructions when i try again.
Thanks for your help
Hello all!
I recently flashed the 4.16.xx firmware to my device. I am now stuck on the Bliss Rom bootscreen for some reason. Booting into recovery takes me to stock recovery and the phone isn't being recognized through ADB on several different PC's.
Am I screwed here? Any options?
Thanks for any input.
Try going into the fastboot option from the hboot (or called bootloader to many people. To get to hboot, do power and volume down when the phone is booting up. ) and try flashing your TWRP recovery from there. Also make sure your drivers are working.
If you don't know how to flash recovery just Google it, you should be fine.
Dw, dont panic, it'll be fine xD
Zomb!e said:
I recently flashed the 4.16.xx firmware to my device. I am now stuck on the Bliss Rom bootscreen for some reason. Booting into recovery takes me to stock recovery and the phone isn't being recognized through ADB on several different PC's.
Click to expand...
Click to collapse
Stock recovery is the logical result for flashing firmware, unless the firmware was hacked to remove stock recovery.
adb not working, is also normal. You need to be in OS or recovery to use adb commands (and I don't know whether you can with stock recovery). adb does not work in bootloader.
If you flashed an official firmware with s-on, then not boot is also the expected result.
You need to unlock the bootloader again, flash TWRP back onto the phone, and flash a ROM.
redpoint73 said:
Stock recovery is the logical result for flashing firmware, unless the firmware was hacked to remove stock recovery.
adb not working, is also normal. You need to be in OS or recovery to use adb commands (and I don't know whether you can with stock recovery). adb does not work in bootloader.
If you flashed an official firmware with s-on, then not boot is also the expected result.
You need to unlock the bootloader again, flash TWRP back onto the phone, and flash a ROM.
Click to expand...
Click to collapse
Hey thanks for the reply!
I figured it out finally and forgot to update the post. I ended up finding and flashing a Lollipop RUU from the SDcard and that got me booted up. Then I just had to re-flash TWRP, re-root and flash a new rom.
All is well now. Thanks for trying to help out.
Every time i flash the latest TWRP for the HTC One M8 GPE on the newest update 6.0.1 June security update, when flashed in fastboot, once it completes, it will automatically boot into twrp, i select the option to allow system modifications, and when i reboot into system it boots just fine, but when booting back into the bootloader, and into TWRP I'm greeted with this screen.
any help would be appreciated, i tried searching the forum, but had no luck finding anyone else with this issue
Because you use command
fastboot boot NameOfTWRP.img
To correctly install TWRP, use command
fastboot flash recovery NameOfTWRP.img
ckpv5 said:
Because you use command
fastboot boot NameOfTWRP.img
To correctly install TWRP, use command
fastboot flash recovery NameOfTWRP.img
Click to expand...
Click to collapse
Thanks for the prompt reply!, I'll give it a try when i get home!
So i had success flashing TWRP properly, and can now boot into it, back up my OS etc, however, when i flash the latest version of chainfire root via TWRP i get a boot loop every time, I'm wiping the cache after preforming the flash, have any ideas what i might be doing wrong?
DeathSentinels said:
Showever, when i flash the latest version of chainfire root via TWRP i get a boot loop every time
Click to expand...
Click to collapse
What version number SuperSU are you using exactly? A lot of times, folks use what they think is the "latest", but when asked what version number, we find out its not even close to current (which has the common result of bootloop).