Hiya
I am stuck here with a strange bootloop. I can get to twrp or factory recoveries as I can still flash those but my issue is that no matter what recovery i load/flash it only stays on for about 30 to 40 seconds then it reboots itself. I can use fast boot but my phone screen is blank in bootloader. I tried the three finger flash with factory roms but same applies , it starts but around 30 seconds in it reboots. Any ideas ?? i have an unlock bootloader and the phone is wiped completely . I was using pacrom the second release and all was good until it reboot itself today :crying:
ecvision said:
Hiya
I am stuck here with a strange bootloop. I can get to twrp or factory recoveries as I can still flash those but my issue is that no matter what recovery i load/flash it only stays on for about 30 to 40 seconds then it reboots itself. I can use fast boot but my phone screen is blank in bootloader. I tried the three finger flash with factory roms but same applies , it starts but around 30 seconds in it reboots. Any ideas ?? i have an unlock bootloader and the phone is wiped completely . I was using pacrom the second release and all was good until it reboot itself today :crying:
Click to expand...
Click to collapse
What so you mean it starts? It makes it to flashing then reboots? Place 322 on SD card and try that way. If you can boot twrp just restore a previous nandroid.
Moody66 said:
What so you mean it starts? It makes it to flashing then reboots? Place 322 on SD card and try that way. If you can boot twrp just restore a previous nandroid.
Click to expand...
Click to collapse
I tried 322 and 309 but the problem is that it seems to have a 30 sec window and it will reboot itself no matter what the operation is at the moment. It gets about 5% during factory flash then it reboots itself. Only when its sitting in bootloader it doesnt reboot but the only way I can tell its in bootloader is to check with fastboot devices command as there is only a blank screenon my phone. My bootloader may be corrupted
So I had my phone powered off for about 3 hours and now it seems to come back to life. Currently factory flash at 45 percent. Keeping my fingers crossed. I am not sure why it glitched like that. Is there a odin equivalent we may be able to use for something like this? I hope this never happens again
ecvision said:
So I had my phone powered off for about 3 hours and now it seems to come back to life. Currently factory flash at 45 percent. Keeping my fingers crossed. I am not sure why it glitched like that. Is there a odin equivalent we may be able to use for something like this? I hope this never happens again
Click to expand...
Click to collapse
Nope. Would be nice. You may have experienced the power bug others have seen. When a cable is plugged in during a boot it sometimes hangs. Lost in limbo. So far only way around it was boot recovery then boot recovery again on next boot.
Related
So. I was on 1.4a of CherryBlur. Flashed the newest FULL WIPE with Webtop version 1.4d. Flashed using Tenfar's Recovery and it said flashing was successful. Now, when I turn the phone on, at the motorola logo screen, with "Dual Core Technology" below it, the screen starts flashing after a few seconds (about 20 seconds) and the white "Unlocked" in the top left of the screen is gone during the flashing. What the hell? I can still get into the recovery mode, but none of the options seem to help my problem, even the factory reset.
And a battery pull is the only way to get the screen to stop blinking and restart.
Any ideas? Could the download have been incomplete/corrupted?
Err0xx said:
So. I was on 1.4a of CherryBlur. Flashed the newest FULL WIPE with Webtop version 1.4d. Flashed using Tenfar's Recovery and it said flashing was successful. Now, when I turn the phone on, at the motorola logo screen, with "Dual Core Technology" below it, the screen starts flashing after a few seconds (about 20 seconds) and the white "Unlocked" in the top left of the screen is gone during the flashing. What the hell? I can still get into the recovery mode, but none of the options seem to help my problem, even the factory reset.
And a battery pull is the only way to get the screen to stop blinking and restart.
Any ideas? Could the download have been incomplete/corrupted?
Click to expand...
Click to collapse
Hold the volume down while the phone keeps restarting. Then try to enter recovery and do a wipe.
Ps: are you on tenfars cwm or rom managers cwm? Only tenfars cwm wipes data.
Sent from my MB860 using XDA Premium App
Aye. On Tenfar's and wipe did nothing for me.
Boot into recovery and reflash Cherryblur. Sounds like your other rom you downloaded didnt finish or is corrupted.
As unbelievable as it may sound, tried this. Have 3 different versions of CherryBlur saved on my SD Card. tried reflashing the newest version (1.4d FULL WIPE) about 5 times and even tried older versions (back to 1.2) out of desperation. All result in this same hang at the motorola screen. This is one of the most amazing things that I've seen. Something buggered royally.
Okay about a month ago I root my gf evo 3d , she has hboot 1.5 so I followed the steps on this thread http://forum.xda-developers.com/showthread.php?t=1239821.
Everything has been working fine up until about a week ago , her phone started running hot and the battery would drain really quick with barely any usage. So my plan was to do a factory restart and full wipe and reinstall the rom fresh but when I tried to get into recovery the phone just shuts off , then goes to the boot screen then after the boot screen the phone just restarts itself. I even tried to do a factory reset from the phones menu options and the same things happens. The ways I tried getting into recovery are by using the shutdown menu options (hold power , reboot , recovery) , I've also tried rom manager and last I tried getting to recovery from bootloader and nothing seems to work.
I am completely lost PLEASE! HELP!
unomillionaire said:
Okay about a month ago I root my gf evo 3d , she has hboot 1.5 so I followed the steps on this thread http://forum.xda-developers.com/showthread.php?t=1239821.
Everything has been working fine up until about a week ago , her phone started running hot and the battery would drain really quick with barely any usage. So my plan was to do a factory restart and full wipe and reinstall the rom fresh but when I tried to get into recovery the phone just shuts off , then goes to the boot screen then after the boot screen the phone just restarts itself. I even tried to do a factory reset from the phones menu options and the same things happens. The ways I tried getting into recovery are by using the shutdown menu options (hold power , reboot , recovery) , I've also tried rom manager and last I tried getting to recovery from bootloader and nothing seems to work.
I am completely lost PLEASE! HELP!
Click to expand...
Click to collapse
You should reflash your recovery to TWRP using fastboot. Then boot into recovery using fastboot. From there you should be able to do a complete wipe and flash a ROM. It is outlined in the thread you linked OP and second post. Feel free to come into the d3rp q+a thread in my sig if you need more help.
It worked thanks you
unomillionaire said:
Okay about a month ago I root my gf evo 3d , she has hboot 1.5 so I followed the steps on this thread http://forum.xda-developers.com/showthread.php?t=1239821.
Everything has been working fine up until about a week ago , her phone started running hot and the battery would drain really quick with barely any usage. So my plan was to do a factory restart and full wipe and reinstall the rom fresh but when I tried to get into recovery the phone just shuts off , then goes to the boot screen then after the boot screen the phone just restarts itself. I even tried to do a factory reset from the phones menu options and the same things happens. The ways I tried getting into recovery are by using the shutdown menu options (hold power , reboot , recovery) , I've also tried rom manager and last I tried getting to recovery from bootloader and nothing seems to work.
I am completely lost PLEASE! HELP!
Click to expand...
Click to collapse
unomillionaire said:
It worked thanks you
Click to expand...
Click to collapse
As a heads up to some of the inner workings.
All the methods you listed are correct methods of booting into the recovery. ROM Manager selecting boot recovery, booting into the bootloader and selecting recovery and also adb shell, reboot recovery.
The boot order goes: bootloader -> kernel -> recovery. Once you see the HTC screen or whatever custom splash screen is loaded, you know the device is now booting the kernel. At this point, if the device hangs on the splash screen or reboots again to the splash screen, something is wrong with the kernel "recovery" itself.
If you get this rebooting to splash screen or hanging on splash screen two or three times in a row, that should be sufficient to know, you have correctly booted the device into recovery mode and the next step is to reflash the recovery, essentially reloading it.
We can speculate on how/why the recovery became corrupt on your device, but in the end, these things sometimes just happen to no intentional fault of the user.
Hopefully this doesn't happen again, but if it does, hopefully this extra information will help prevent a bit of frustration the next time around!
joeykrim said:
As a heads up to some of the inner workings.
All the methods you listed are correct methods of booting into the recovery. ROM Manager selecting boot recovery, booting into the bootloader and selecting recovery and also adb shell, reboot recovery.
The boot order goes: bootloader -> kernel -> recovery. Once you see the HTC screen or whatever custom splash screen is loaded, you know the device is now booting the kernel. At this point, if the device hangs on the splash screen or reboots again to the splash screen, something is wrong with the kernel "recovery" itself.
If you get this rebooting to splash screen or hanging on splash screen two or three times in a row, that should be sufficient to know, you have correctly booted the device into recovery mode and the next step is to reflash the recovery, essentially reloading it.
We can speculate on how/why the recovery became corrupt on your device, but in the end, these things sometimes just happen to no intentional fault of the user.
Hopefully this doesn't happen again, but if it does, hopefully this extra information will help prevent a bit of frustration the next time around!
Click to expand...
Click to collapse
So you mean, stuck at the splash screen(HTC with white screen) and reboot again and again is because of the recovery destroyed? My phone stuck at the splash screen for about 10 seconds and then reboot again and again. I have tried to flash many recovery images, includeing twrp 1.0.3, twrp 1.1.1, cwm-1.0.4, cwm-1.0.5, cwm-5.0.2, all failed to boot up into recovery:-(
Thanks in advance!
Here's my situation, maybe someone will find it interesting or know what's going on. I was running the EOS Jelly Bean (EOS-tf201-20120728-31.zip). Everything was running pretty well for a few days, then yesterday the device simply powered off. When I rebooted it got to the splash screen then shut off before it could get any farther. I figured it was a power issue, so I plugged it in and charged it for a while but get the same response. Around this point I started to get suspicious and tried to boot into recovery. It got to "Booting Recovery Kernel Image" then powers off the same way.
So then I proceed to go into fastboot and fastboot works great no power offs. Through that I am able to flash openrecovery-twrp-2.2.1-tf201.blob and the virtuous packaged boot as per this thread http://forum.xda-developers.com/showthread.php?t=1773280 as well as factory reset. I also tried a few other boot/recovery combinations and was able to make it into recovery. In twrp recovery I was able to install the latest Virtuous rom which got me back to stock and I thought good case closed. I even made it all the way into the OS and was able to install apps, wifi worked great, run the apps etc. Eventually the screen went blank though and I was stuck back in the same shutdown on boot scenario as described above. Now I'm able to fairly consistently flash openrecovery-twrp-2.2.1-tf201.blob, reboot, get into teamwin recovery, but now even that appears to be randomly powering off.
So now I'm guessing that it may just be bricked and is probably a hardware issue since the reboots appear so random, the unit was refurbished. At the same time I'm still holding out some hope that it's simply some boot code somewhere that was corrupted and I can flash something and get things back to normal again since I can still access fastboot and occasionally ADB and recovery. I've flashed from fastboot system/recovery/boot, any other thoughts or potential combinations I could try? Also anything I can do with those tools to debug it further and get more data on what may be the root cause?
This is going to be a long story hopefully someone will find the trigger.
My phone has been succussfully been S-off and rooted using the DirtyRacun method for over a year. I have used the recovery and booted different ROMs with no problem. I have found a ROM that I like and have been using it and haven't changed anything recently. The following problem arose from a normal day of usage.
I had my phone turned off because I was not going to be using it and wanted to conserve battery. Upon turning it on it was fine and battery above 60%. Within an hour my phone screen was black and unresponsive although the bottom lights were on. I held the power button to do a soft reset. My phone is now stuck in a bootloop at the white htc screen. I rebooted to the bootloader where upon when it does the image checks NONE of them are found. I tried to boot into recovery. Again it goes to the white htc screen and enters a bootloop. I boot back into bootloader. If I go to the powerdown option my phone turns off. 20 seconds later it turns itself back on without any intervention and goes back to bootloop. I let the battery die and then plugged it in. It charged for a while and then proceeded to start turning itself back into bootloop without any intervention.
I did also try to fastboot flash recovery twp.image It was unsuccessful due to low remote battery. (phone has currently died again. I'm going to let it charge until it starts itself again and retry that step to see if I might have a large enough charge then). The following from the Don't Panic guide is most relevant I believe...
"Bad kernel and or system image and recovery Phone will boot to boot loader, will not boot to OS and selecting recovery will boot to boot loader. All is not lost, simply fastboot recovery and or boot image (for those on HBOOT 1.15 and higher) and then flash ROM from recovery. This happens but it is very unlikely it will happen to you."
HELP....
I am outside of my league on this one.
Any help will be much appreciated
I took it to Sprint. They thout it was the power button, after replacing it and the same I got a refurbashed phone through TEP insurance at no cost. WIN. Except does anyone have S-off suggestions for Hboot 2.09 and mainver 3.17.651.4 dirtyracun which I am familiar with does not apper to work.
m1gramme said:
This is going to be a long story hopefully someone will find the trigger.
My phone has been succussfully been S-off and rooted using the DirtyRacun method for over a year. I have used the recovery and booted different ROMs with no problem. I have found a ROM that I like and have been using it and haven't changed anything recently. The following problem arose from a normal day of usage.
I had my phone turned off because I was not going to be using it and wanted to conserve battery. Upon turning it on it was fine and battery above 60%. Within an hour my phone screen was black and unresponsive although the bottom lights were on. I held the power button to do a soft reset. My phone is now stuck in a bootloop at the white htc screen. I rebooted to the bootloader where upon when it does the image checks NONE of them are found. I tried to boot into recovery. Again it goes to the white htc screen and enters a bootloop. I boot back into bootloader. If I go to the powerdown option my phone turns off. 20 seconds later it turns itself back on without any intervention and goes back to bootloop. I let the battery die and then plugged it in. It charged for a while and then proceeded to start turning itself back into bootloop without any intervention.
I did also try to fastboot flash recovery twp.image It was unsuccessful due to low remote battery. (phone has currently died again. I'm going to let it charge until it starts itself again and retry that step to see if I might have a large enough charge then). The following from the Don't Panic guide is most relevant I believe...
"Bad kernel and or system image and recovery Phone will boot to boot loader, will not boot to OS and selecting recovery will boot to boot loader. All is not lost, simply fastboot recovery and or boot image (for those on HBOOT 1.15 and higher) and then flash ROM from recovery. This happens but it is very unlikely it will happen to you."
HELP....
I am outside of my league on this one.
Any help will be much appreciated
Click to expand...
Click to collapse
Did you upgrade to the new partitions? What ROM had you flashed? The only two S-off methods that I know that work without any problems are rumrunner and firewater.
What HBoot version? What exact version of TWRP are you trying to flash? If you've upgraded to new partitions, you'll need the modified TWRP.
Once you provide a bit more information, it will be easier to tell you what to do next.
fizbanrapper said:
Did you upgrade to the new partitions? What ROM had you flashed? The only two S-off methods that I know that work without any problems are rumrunner and firewater.
What HBoot version? What exact version of TWRP are you trying to flash? If you've upgraded to new partitions, you'll need the modified TWRP.
Once you provide a bit more information, it will be easier to tell you what to do next.
Click to expand...
Click to collapse
My HBOOT is 2.09.4444
I believe my ROM was eiter a rooted sense or BeanStalk 4.3. I honestly don't remember because I haven't changed anything in so long.
I had TWP openrecovery-twrp-2.6.3.0-jewel.img
Again this wasn't a problem that came from trying to change anything. My phone froze I soft-reset it and it was in an unstoppable bootloop. No images were found. Telling it to go to recovery still took it to bootloop. Even after power down from bootloader, after 20 seconds it boots back into bootloop.
The problem I feel most at hand is I can't charge the battery enough to do anything because it appears to not charge in bootloader.
I have had my phone rooted and s-off through Dirty Racun for almost a year now and have been using the same setup without changing for at least 6 months.
The "no image" error you're referring to isn't a error at all. It's normal-the bootloader is scanning for a file named PJ75IMG.zip on the external SD card. Unless you have one on it, you'll get that message. It's normal. Have you tried removing your SD card and seeing if the phone will boot? Also, have you had any luck powering the phone off and letting it charge?
If you're able to and have the proper equipment, I'd test the internal battery with a voltage meter to see if it is even able to hold a charge, will save a lot of frustration.
Magnum_Enforcer said:
The "no image" error you're referring to isn't a error at all. It's normal-the bootloader is scanning for a file named PJ75IMG.zip on the external SD card. Unless you have one on it, you'll get that message. It's normal. Have you tried removing your SD card and seeing if the phone will boot? Also, have you had any luck powering the phone off and letting it charge?
Click to expand...
Click to collapse
Again the hardest part about this is my phone refuses to turn off. I have gone into the bootloader and selected Power Down. The phone turns off and the charge light blinks. Then 20 seconds later without me touching it, it turns on and starts into the bootloop.
I am currently finding some luck by holding the down button so when it starts itself again I can be in bootloader mode and select power down. I have elevated my battery from 3530mv to 3649mv (as per fastboot getvar battery-voltage)
Any suggestion as to where a good number to reach would be helpful.
Magnum_Enforcer said:
The "no image" error you're referring to isn't a error at all. It's normal-the bootloader is scanning for a file named PJ75IMG.zip on the external SD card. Unless you have one on it, you'll get that message. It's normal. Have you tried removing your SD card and seeing if the phone will boot? Also, have you had any luck powering the phone off and letting it charge?
Click to expand...
Click to collapse
See above about "charging" after getting it up a little (and without SD card) I tried booting to recovery (getvar battery-status good) still went to htc bootloop screen. Tried to flash recovery and boot as per
"Bad kernel and or system image and recovery Phone will boot to boot loader, will not boot to OS and selecting recovery will boot to boot loader. All is not lost, simply fastboot recovery and or boot image (for those on HBOOT 1.15 and higher) and then flash ROM from recovery. This happens but it is very unlikely it will happen to you."
in troubleshooting guide. Still continues in bootloop
So a littel update after spending forever with my charging trick I was able to get a little more charge. I was able to run commands of flash recovery it stated it was complete. Still boots to bootloop. I was able to try to run RUU using RUU 3.15.651.16 - HBOOT 2.09
fastboot oem lock
fastboot oem rebootRUU
fastboot flash zip RUU.zip
The whole process worked (said it did)
Still in repeating bootloops at htc screen.
Phone still turns itself on into a bootloop even after selecting power down from bootloader.
I'm beginning to think it's the dreaded brick...
Interesting issue, indeed. There were some problems reported with the 3.15 RUU, but none that should cause the issue you're having. Check out the top link in my sig and go to the bottom of the first post. Hit up the link for VipeRUU. I suggest trying it and returning your phone to stock. If after returning your phone to stock the issue persists, then you most likely have a hardware issue (already sounds like that's likely the case). If you have TEP with Sprint you can take the phone to a Sprint service center and see about getting it replaced.
Sent from my HTC device
My wife had that issue as well but a factory reset fixed
Sent from my EVO LTE using Tapatalk
i had my amaze repaired (power IC, bad data cable caused it to not charge or even boot up or go in bootloader). Now within 30 seconds off booting up it used to restart. and i cant get into the recovery( shows logo and powers off when going into recovery from bootloader). i cleared the cache from bootloader and its now stuck at boot animation( not boot logo) and wont boot completely. before clearing cache after logo it used to show 4ext recovery boot screen then screen off, now it just shows logo and screen off. really need help i got this phone fixed after 1 year. im s-off and running any 4.4.4 rom (dont remember which rom, i think pacman rom)
so basically i can get into bootloader and use fastboot commands (no adb, authorized device). cant do anything else on the phone. is there a way to fix the phone?
Arsalanzahoor said:
i had my amaze repaired (power IC, bad data cable caused it to not charge or even boot up or go in bootloader). Now within 30 seconds off booting up it used to restart. and i cant get into the recovery( shows logo and powers off when going into recovery from bootloader). i cleared the cache from bootloader and its now stuck at boot animation( not boot logo) and wont boot completely. before clearing cache after logo it used to show 4ext recovery boot screen then screen off, now it just shows logo and screen off. really need help i got this phone fixed after 1 year. im s-off and running any 4.4.4 rom (dont remember which rom, i think pacman rom)
so basically i can get into bootloader and use fastboot commands (no adb, authorized device). cant do anything else on the phone. is there a way to fix the phone?
Click to expand...
Click to collapse
reflashed recovery for the 4th time and it worked. it said the cache partition is corrupt. formatted it. phone works now. updating apps caused system ui stopped working error. going to flash other roms.
Arsalanzahoor said:
reflashed recovery for the 4th time and it worked. it said the cache partition is corrupt. formatted it. phone works now. updating apps caused system ui stopped working error. going to flash other roms.
Click to expand...
Click to collapse
Glad you got your phone working--your persistence paid off.
Be sure to make a backup before flashing other ROM's.