NONROOTED Tbolt in Boot Loop - Thunderbolt Q&A, Help & Troubleshooting

Hi all,
My friend's T-Bolt is stuck in a boot loop on the white HTC screen. Some Googling has shown that this is not a new issue, but many of the methods to fix don't work on her phone. I've managed to fully boot it up only once in the week I've had it, while it was plugged into the charger (and once I unplugged it, it shut down). I don't believe it's a battery issue, because I'm able to pull up Hboot while it's on battery.
I tried doing a factory reset from the Hboot screen: bootloop
I tried entering recovery: bootloop
I have downloaded PG05IMG.zip from Android Police, moved it to an SD card, then booted into Hboot; it loaded it and everything, but when I boot it it bootloops again.
When I plug it into a computer, guess what it does? Bootloops.
Any other suggestions? I had an old DINC I was able to give her but that's like a step down from the TBolt, so if I can fix hers I would rather do that. I have a DINC2 of my own that I've rooted, so the process is not foreign to me, but I am definitely NOT a programmer.

Related

Strange and interesting boot issues.

as i mentioned a few days ago, i recently rooted some vibrants for a few of my friends.
one of them decided to switch me phones for a few days just to see if he liked my phone (g2) since he wants to upgrade anyways.
so i unlocked his vibrant using this hex editor method. worked like a charm. popped in my sim and at&t came up, all was well with the world.
i was going to do a nandroid backup of his phone so i used rommanager to boot into recovery.
that didn't happen.
his phone hung at the samsung vibrant screen. i figured no big deal, maybe just a hiccup. pulled the battery and attempted to start the phone again normally, but still stuck on vibrant. tried a few more reboots with no new results. next i booted the phone into download mode which worked just fine. dl mode came up normally and was recognized by odin. still feeling creative, i decided to pull the battery while it was in dl mode then undo the usb cable. put the battery back in, turned it on and voila! phone booted like normal!
i was pretty damn confused. i could get it to boot this way about 1 out of every 3 tries. i thought perhaps changing the nv_data.bin file was what screwed it up so i replaced the modified one with the original and re-locked his phone.
so the phone boots up normally, i go to rommanager, tell it to install clockwork recovery, wait for it to finish and attempt to reboot into recovery mode, this time through adb. the phone still got stuck on the vibrant screen BUT adb still recognized that the phone was attached AND in recovery mode.
still confused. i'm assuming perhaps the adb functionality was due to restoring the original nv_data.bin?
so i rebooted his phone via adb and it turned on like normal, told him not to turn the phone off. i was going to take it with me to work today, but we're generally busy on saturdays and i won't have time to mess with it. gonna take it monday and try some more stuff.
so long story short; unlocked phone, wouldn't reboot into recovery, just hung on vibrant screen. put phone in dl mode, pulled battery, attempted boot and it worked. relocked phone, reflashed cwm in rommanager, rebooted via adb, still hung on vibrant screen but recognized by adb.
anyone ever had anything similar to this happen?
This actually happened to me once. Bit once i odin'ed back to stock it fixed it and it never happened again.

[Q] Tried to flash TWRP, now looks bricked :(

Hey guys, Today I just finished downgrading to HBOOT 1.4 and got up and running fine on TWRP 1.1.1 and ViperRom's new ICS build. I wasn't having any issues at all. I started reading about TWRP2 though, and felt like checking it out. So I downloaded GooManager and searched for TWRP and got openrecovery-twrp-2.1.3.blob. I touched it to download and it immediately went into recovery to install. However, as soon as it rebooted, it came up with TWRP 1.1.1's logo and a scrolling status bar. This lasted about 2 seconds and then the phone shut off. I left it as is hoping it would come back for about 10 min but nothing. I removed the battery and put it back in and tried to reboot. Booting to system and booting to recovery give zero response and ADB controls don't seem to recognize the device when plugged into USB. Can anybody help? TWRP2 doesn't seem to have a thread here and their site has limited resources for help.
thanks.
Can you boot into the bootloader (hold power and down on startup)?
no I cannot. Phone is completely unresponsive. I didn't think trying to flash a recovery would cause complete system failure.. wth
Just to be clear, before you call it a brick, did you remover battery for 10 seconds and then try to get to the bootloader. Hold down the volume first then the power button and keep holding both until the bootloader pops up. Just making sure...
yeah I did. Pulled the battery, left it out while I went and ate something, then plugged in the HTC charger and tried to reboot and nothing. Tried putting the battery back in and doing the same thing. I guess It's time to go to sprint and beg for mercy
Same thing happened to me. My phone is completely unresponsive after I tried to update to TWRP 2.1. I was on AOKP milestone 5a. The computer responds when I connect the USB, but the phone will not boot at all.
EDIT: Computer doesn't respond either. Think I'm headed to the nearest Sprint store ASAP.
Connect your device to your computer then go into your adb directory in cmd and type. "adb reboot-bootloader" (without the quotation marks)
Are you s-off ? And does the phone show up as qhusb_dload in device manager ? If it does it is bricked. If you still have s-on it can be fixed if you are s-off i am sorry to say you have to get a new phone. I have a phone now that is s-off and bricked and i cant recover it as of now but i am working on it, if i succeed i will post how to do it.
I would recommend trying to keep the bricked phone in case there is a way to unbrick eventually then you have another phone to play with. I just claimed my insurance and told them i dropped the phone in a porta-john at work and i wasn't about to fish it out. So they told me dont worry about sending the bricked phone in and i got my new one next day.

[q] LG logo loop

Hey everyone,
I successfully rooted and unlocked (through FreeGee) my bootloader. I installed TWRP, booted into the recovery through adb and performed a backup. The phone rebooted itself and now will not power on. The phone was extremely hot. I removed it form the USB port and plugged it into my charger thinking it may drained the 90% battery I had. It will not take Power + Up or Power + down.
Any ideas?
I did NOT try to flash or wipe, just back up.
Any help is greatly appreciated.
Thanks!
EDIT: I was able to get it into Fastboot by taking the SD card out, but can't get it to go any further. I am still researching this, but any help is greatly appreciated!
EDIT 2: Just put the phone into Download Mode and am installing LGNPST. Also downloaded the correct TOT.
EDIT 3: LGNPST is seeing the phone and installing the TOT but gets stuck at 85%, reboots the phone and then doesn't go past that.
EDIT 4: LGNPST finally got to 100%, still blinks the LG Logo and then dies.
EDIT 5: Admitting defeat... going to plea my life to an AT&T rep to see if I can get a replacement, as I don't think I am to blame here.

Boot loop - unable to boot to recovery

Interesting thing happened today which has basically put my phone in a death spiral state. The battery died and after charging it a while I went to power it back on and found it in a boot loop state. I can get into the bootloader, but from there if I select recovery it reboots and the white bar on the right side of the screen fails to fill up, then the phone reboots. I've tried flashing two different versions of TWRP from the bootloader and it still exhibits the same issue.
HBOOT 1.12.1111
RADIO 1.12.11.1210
S-OFF
I was running CM10.1 without much issue until the power issue.
Any thoughts?
Thanks to Zanzibar for helping me work through this on IRC. Eventually the steps outlined here: http://forum.xda-developers.com/showthread.php?t=2338391&highlight=boot+loop did the trick.
fastboot erase cache
fastboot reboot
The device started booting but hung on the CM logo for far too long. I hard rebooted and installed an updated version of TWRP and then wiped and flashed the ROM over again. More updates to follow.
Well the device worked for the night but when I rebooted it this morning it immediately began the boot loop situation again. I RUU'd once and it got stuck in another boot loop. I got it to boot after hard powering down and it loaded the factory ROM. I rebooted back to the bootloader and flashed TWRP 2.5.0.0 and tried to reboot. Another boot loop. Hard power cycling didn't solve it either, so I pushed the RUU for a second time. Now the device refuses to boot into anything other than the boot loader -- the initial issue from this post -- and no amount of hard power cycling makes a difference.
The phone is currently showing as LOCKED in the boot loader so I dropped it off at the Sprint store to see if they could find anything physically wrong etc. More updates as they are discovered in the hopes that if someone else ever experiences this, they have something to reference.
Thanks for posting. Did you solve the problem? I think I'm having something similar.

[Q] EVO 4g LTE Stuck in repeating bootloop FIXED new phone

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

Categories

Resources