So, my wife's Droid Incredible, went into a bootloop. It was completely stock, no modifications done, but while she was using it, it just started rebooting over and over again..it won't get past the first splash screen without rebooting.
At first, I thought it might have overheated, but evidently this is not the problem.
So I've been messing with it..I am able to get it into hboot (version 1.07), which I was able to unlock through hdev. I tried flashing CWM through fastboot, but the phone won't boot into recovery.
So could someone direct me to how to fix it? If I could put a stock image on the sdcard that hboot would install, would that work? Where would I find this image?
Thanks in advance.
Here is the information in hboot:
UNLOCKED
INCREDIBLEC XC SHIP S-ON
HBOOT-1.07.0000
MICROP-0417
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.10.12.20
finitary said:
I tried flashing CWM through fastboot, but the phone won't boot into recovery.
Click to expand...
Click to collapse
So you "tried" flashing CWM through fastboot. What exactly did you do, and what, if any, was the error? And how are you trying to get into recovery?
If you flash the recovery correctly, you should be able to get into recovery.
PonsAsinorem said:
So you "tried" flashing CWM through fastboot. What exactly did you do, and what, if any, was the error? And how are you trying to get into recovery?
If you flash the recovery correctly, you should be able to get into recovery.
Click to expand...
Click to collapse
Okay, I did flash the recovery, with fastboot flash recovery. To boot into recovery, I am going back to the bootloader and selecting recovery. What happens is the device reenters bootloop at that point.
Update: I have now tried using PB31IMG.zip from here http://dinc.does-it.net/Stock_Images/4.08.605.2/ by putting onto Fat32 sd card which then does get installed in hboot. When trying to boot the system, the bootloop is unchanged. However, now when I try to boot recovery, instead of looping, the boot freezes on the htc incredible splash screen.
finitary said:
Okay, I did flash the recovery, with fastboot flash recovery. To boot into recovery, I am going back to the bootloader and selecting recovery. What happens is the device reenters bootloop at that point.
Update: I have now tried using PB31IMG.zip from here http://dinc.does-it.net/Stock_Images/4.08.605.2/ by putting onto Fat32 sd card which then does get installed in hboot. When trying to boot the system, the bootloop is unchanged. However, now when I try to boot recovery, instead of looping, the boot freezes on the htc incredible splash screen.
Click to expand...
Click to collapse
Sounds like your recovery flash didn't take. Try putting this file on the root of a FAT32 formatted sdcrard, and then try to get into recovery.
http://forum.xda-developers.com/showpost.php?p=39092075&postcount=167
PonsAsinorem said:
Sounds like your recovery flash didn't take. Try putting this file on the root of a FAT32 formatted sdcrard, and then try to get into recovery.
http://forum.xda-developers.com/showpost.php?p=39092075&postcount=167
Click to expand...
Click to collapse
Thanks for the help. So I went into hboot, hboot found the file, reflashed the recovery, then tried to boot into recovery but the same bootloop occurs. The splash screen htc incredible splashes, it goes black, vibrates, and splashes again until I pull the battery.
Is there anything else to try? Could I somehow replace the bootloader?
So I've tried a few more things now, still no joy -- using fastboot, I issued the following commands to flash an RUU
fastboot oem rebootRUU
fastboot flash zip <name.zip>
However, the flash always fails.
I have also tried to use fastboot to erase the recovery.
fastboot erase recovery
Strangely, it fails when I do this, although it reports that it works when I tell it to flash a recovery image. Although I still can't boot into recovery.
However, I finally got hboot to flash one of the system roms by putting it on the sdcard (4.08.605.15 ) . Strangely enough, this worked only after I relocked the bootloader with fastboot. However, after this the situation remains unchanged.
Related
hey everyone, i have an sim free desire HD that was rooted and s-off and has been running like that for a while. recently i tried to access clockwork mod to try and flash a new rom but when i did so the recovery does not load. Its just stuck on the htc splash screen, it doesnt even say quietly brilliant. The phone still works but i cannot access recovery. I tried the following procedure in fastboot to re flash the recovery
fastboot erase recovery
fastboot flash recovery recoveryCWM.img
fastboot reboot
after doing this it still has not worked. Any suggestions or a certain fix would be brilliant.
Thanks
You can put the PD98IMG.zip from my downgrade post to your SD card and reboot to bootloader, it will flash you the 1.32 stock ROM and you can start from a clean table.
use an older version of recovery
nemesis2911 said:
hey everyone, i have an sim free desire HD that was rooted and s-off and has been running like that for a while. recently i tried to access clockwork mod to try and flash a new rom but when i did so the recovery does not load. Its just stuck on the htc splash screen, it doesnt even say quietly brilliant. The phone still works but i cannot access recovery. I tried the following procedure in fastboot to re flash the recovery
fastboot erase recovery
fastboot flash recovery recoveryCWM.img
fastboot reboot
after doing this it still has not worked. Any suggestions or a certain fix would be brilliant.
Thanks
Click to expand...
Click to collapse
I had the same problem, with clockwork 3.0.0.6 ... I then flashed 3.0.0.5 (see the bottom of the Rom manager Menu that proposes you to use former recovery roms). I could solve my problem that way.
I have an EVO 4G that's stuck in a bootloop. It was previously rooted (Hboot displays S-off) but there doesn't appear to be any recovery installed. It gets stuck at the white HTC screen and then reboots infinitely.
I tried flashing Amon_Ra via hboot, but when I actually reboot and select recovery, it goes back into a bootloop.
I tried installing clockwork and Amon_Ra via fastboot but it wouldn't work, there was an error about remote commands not being allowed.
I tried reflashing with an RUU (RUU_SuperSonic_S_Sprint_WWE_3.26.651.6_Radio_2.15.00.07.28_NV_1.40_release_140444_signed) and it flashes 100% with no problems, but then goes back into bootloop.
As far as I can remember, I've exhausted most of my known options. Is there any hope for getting this thing out of bootloop, or is it pretty much a softbrick?
SUPERSONIC EVT2-3 SHIP S-OFF
HBOOT-2.10.0001
MICROP-041f
RADIO-2.15.00.07.28
Oct 15 2010,12:07:00
I would try selecting clear storage from the bootloader.
http://www.mediafire.com/?gijd69zb5222w > download the recovery and version you want, name it to PC36IMG, then place on the root of your sd card, and flash in the bootloader.
Thanks for the reply. I tried Clockwork 3 and Recovery 3.70, both still resulted in the bootloop. I guess something is just wrong with this phone's recovery, I've tried several different recoveries. I can't even really unroot it since I can't get into recovery to flash unrevoked s-on.
TWO515TY said:
Thanks for the reply. I tried Clockwork 3 and Recovery 3.70, both still resulted in the bootloop. I guess something is just wrong with this phone's recovery, I've tried several different recoveries. I can't even really unroot it since I can't get into recovery to flash unrevoked s-on.
Click to expand...
Click to collapse
Well what you can do is flash a PC36IMg of a 3.70 ruu, flash in the bootloader, technically unrooted, though you have s-off, then try again.
I can't remember which RUU I used, but it flashed hboot 0.93, which I was able to downgrade to 0.76 for fastboot command support. I've flashed recovery manually using fastboot commands and still no dice. I'm guessing there's some kind of hardware issue with this device that's preventing it from properly flashing and/or loading the recovery.
On another random note, is there any way to get adb via hboot or fastboot? When in fastboot, the phone shows up as "My HTC" under ADB Interface, but only fastboot commands work, not adb commands.
And also, what does the hboot usb driver do? I have it installed, but I can't actually figure out what functionality it has.
Im not able to get in recovery anymore. if i select in bootloader recovery my device hangs in a boot loop.
Is it possible that i have lost root?
Please i need your help.
My device is s-off
hboot is 6.93.1002
xyronx said:
Im not able to get in recovery anymore. if i select in bootloader recovery my device hangs in a boot loop.
Is it possible that i have lost root?
Please i need your help.
My device is s-off
hboot is 6.93.1002
Click to expand...
Click to collapse
Did you try to start with volume-down pressed?
I can get in bootloader and fastboot, but not in clockworkmod recovery.
i have flashed the clockworkmod recovery in fastboot again but with no luck
still get boot loop if i try to get in clockwordmod recovery.
possible that you're flashing a corrupted image
i would recommend 4ext touch recovery as it's just better in many ways.
can you still boot normally into your rom? if so you can install the app from 4ext.net, then let it flash the recovery for you.
alternatively flash the recovery.img from the 4ext thread.
i have downloaded the image many times.
I can boot in my rom, but i get some random reboots with boot loops.
I am going to try the 4ext recovery later.
Thanks!
I have tried the 4ext recovery same result it ends in boot loops.
I have gone back on stock branding rom with s-on.
It seems that the promlem wasnt coused by the custom recovery.
I am still getting random reboots.
When it then reboots it hangs in an boot loop.
It only boots if i remove the battery and wait a few minutes.
Anybody an Idea what couses this problem?
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
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.