[Q] stuck in boot loop - Thunderbolt Q&A, Help & Troubleshooting

I'm runninng das bamf 3.4 ,have been for couple weeks . love rom. today working at 106 my thunderbolt would not make a call, so I thought I would reboot and now it is stuck in boot loop, I can get to h-boot and hit recovery but it goes to htc screen

Have you tried pulling the battery, then volume down+power to get to hboot?

yes . I can get to h-boot but when I HIT RECOVERY it goes back to bootloop.S orry for capitals

Sorry, mis-read. You could always RUU and start over. Sorry, all I know to do with out recovery.

It reboots in recovery?? If so sounds like a brick. Aka bootloop of death.
Sent from my HTC Thunderbolt

pennie57 said:
I'm runninng das bamf 3.4 ,have been for couple weeks . love rom. today working at 106 my thunderbolt would not make a call, so I thought I would reboot and now it is stuck in boot loop, I can get to h-boot and hit recovery but it goes to htc screen
Click to expand...
Click to collapse
If your recovery is damaged/non-existent and you get stuck on the HTC screen instead (IOW, recovery never loads) and the ROM is bootlooping then try this:
http://forum.xda-developers.com/showthread.php?t=1179386
It should get you a working recovery back on your phone so that you can either then wipe data/cache for the ROM or flash something else.
Made for just such an occasion

Absolute_Zero said:
If your recovery is damaged/non-existent and you get stuck on the HTC screen instead (IOW, recovery never loads) and the ROM is bootlooping then try this:
http://forum.xda-developers.com/showthread.php?t=1179386
It should get you a working recovery back on your phone so that you can either then wipe data/cache for the ROM or flash something else.
Made for just such an occasion
Click to expand...
Click to collapse
Thanks very much for this.
courtesy of my rooted bolt

ruu recovery ,didn't work .Put stock zip on ruu and least got s-on . Still in boot loop , think is toast

pennie57 said:
ruu recovery ,didn't work .Put stock zip on ruu and least got s-on . Still in boot loop , think is toast
Click to expand...
Click to collapse
Might be, I'd hop on here and see what they think just to be sure.

Same thing happened to me, you need to put a recovery .img on sdcard and flash it in recovery. Thought i was dead for me too but turned out for the good
Sent from my ROOTED TBOLT using XDA Premium App

I did that first. Didn't work thanks anyway
Sent from my ADR6400L using XDA Premium App

I for my replacement today about afraid to root this one. I really think the heat and rough treatment was the culprit
Sent from my ADR6400L using XDA Premium App

Related

[Q] Bricked EVO 3D?

Hello everyone. The other day i used revolutionary to Perma-root my evo 3d. Everything was fine, till my text messages were not sending. So i took out the battery and popped it back in, and all i got was the HTC logo, then a dimmed black screen. Yes i can get into hboot, but i have clockworkmod recovery. I seem to be having a difficult time flashing the official sprint evo 3d rom. Any help is appreciated.
Download the pg86100.zip to revert back to stock in the dev section then go into hboot and let it update and you will start back at the stock ROM
Sent from my PG86100 using XDA App
xSpAzzZAttAcK said:
Hello everyone. The other day i used revolutionary to Perma-root my evo 3d. Everything was fine, till my text messages were not sending. So i took out the battery and popped it back in, and all i got was the HTC logo, then a dimmed black screen. Yes i can get into hboot, but i have clockworkmod recovery. I seem to be having a difficult time flashing the official sprint evo 3d rom. Any help is appreciated.
Click to expand...
Click to collapse
try hboot flashing twrp recovery. then if you can boot up update your prl and profile, also make a phone call to see if you got that error 16 thing. Also, did you by chance try to replace your bootanim? If you did, and something like wrong permissions were set, it would still be booting with a black screen, maybe try leaving it alone while it's booting for a bit?
I did the twrp recovery, but i still get the dim black screen. after the dim black screen it goes black for a few seconds, then goes to the HTC logo again. I didnt try to change anything either...
nuggyunlimited said:
Download the pg86100.zip to revert back to stock in the dev section then go into hboot and let it update and you will start back at the stock ROM
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
Above is your best solution. From there you can decide to either root again or wait a bit longer. But that should fix the issue and keep you from a boot loop of just the HTC screen.
Well thats where you are wrong. I am still in the boot loop after doing the stock HTC EVO 3d flash.
So the bootloader scanned and flashed the PG86IMG file and you are still showing just the HTC screen?
Did you follow the directions here http://forum.xda-developers.com/showthread.php?t=1194053
Hi where exactly do the adb and fastboot files go when you start to run commands?
Well no i still get the boot loop. guess i have a bricked phone...
xSpAzzZAttAcK said:
Well no i still get the boot loop. guess i have a bricked phone...
Click to expand...
Click to collapse
A brick is when the phone is completely unresponsive and won't boot or give you a charging led. If you can get to hboot you're not bricked. I would do a factory wipe from hboot menu (choose clear storage), and then either run an RUU with your phone in fastboot usb mode, or use a PG86IMG.zip
of an RUU to flash back to stock. That should hopefully fix the loops.
Sent from my PG86100 using XDA App
**** YES! I used the RUU.exe from sprint and now my phone works.
k2buckley said:
A brick is when the phone is completely unresponsive and won't boot or give you a charging led. If you can get to hboot you're not bricked. I would do a factory wipe from hboot menu (choose clear storage), and then either run an RUU with your phone in fastboot usb mode, or use a PG86IMG.zip
of an RUU to flash back to stock. That should hopefully fix the loops.
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
From past experiences like this, wipe, flash the bare stock rooted ROM in the development section. Do this in recovery mode. Before wiping you could try just flashing the bare Rom over. That usually worked for me.
Sent From My HTC Evo 3D Using Tapatalk On The Now Network From Sprint!
xSpAzzZAttAcK said:
**** YES! I used the RUU.exe from sprint and now my phone works.
Click to expand...
Click to collapse
Sorry, was a min too late. Glad it works again!
Sent From My HTC Evo 3D Using Tapatalk On The Now Network From Sprint!
xSpAzzZAttAcK said:
**** YES! I used the RUU.exe from sprint and now my phone works.
Click to expand...
Click to collapse
Sweet, glad you got it booting. Now that you've ran the RUU, you'll probably need to run Revolutionary again and then flash TWRP recovery. You should be good to go then. I think your hboot will still be S-off after the RUU, but from reports of other people it acts like it's still S-on and won't let you flash anything, so running Revolutionary again is necessary.
Well i cant use revolutionary...
My device is not supported?
And now i cant make calls or text messages, i get error 16.
any help?
xSpAzzZAttAcK said:
Well i cant use revolutionary...
My device is not supported?
And now i cant make calls or text messages, i get error 16.
any help?
Click to expand...
Click to collapse
Call Sprint. . they can fix it. . .it's actually a common problem after the root. Try to make a call. . .you will get the error message. . .you should hang on the line for a few minutes and it will direct you to sprint. They will call you on another line. . that's not your phone, and have you power the phone off. . .they will wait a few minutes then tell you to turn it on and make a test call. . .they may have you go thru a few things, but I didn't. . .and it will work.
http://forum.xda-developers.com/showthread.php?t=1194460 this forum should answer the question
Help!
I feel like such a freakin noob. My EVO3D is not quite bricked but I think i broke my recovery img AND my ROM. All I can do is turn on Hboot. Tried the stock Sprint RUU to go back to stock and i keep getting an error message everytime it tries to update the ROM image. Have no idea what to do now without being able to go into recovery. Suggestions?
My phone is doing the exact same thing, cept running the ruu.exe didn't fix it. Anyone else have some more ideas?
My original thread http://forum.xda-developers.com/showthread.php?t=1281565

Phone stuck on HTC startup screen

Hello,
I have an unlocked EVO 3D with HBOOT 1.5 S-on.
I flashed the phone and replaced InfectedRom with Warm Two Point Three. After installing new rom and reseting, phone is now stuck on HTC startup screen.
Please help!!! I appreciate and welcome all feedback. Thank you
kongfooey said:
Hello,
I have an unlocked EVO 3D with HBOOT 1.5 S-on.
I flashed the phone and replaced InfectedRom with Warm Two Point Three. After installing new rom and reseting, phone is now stuck on HTC startup screen.
Please help!!! I appreciate and welcome all feedback. Thank you
Click to expand...
Click to collapse
Did you wipe all the way? Also what is your software 2.17 or 2.08 ? Did you fastboot boot recovery.img when you flashed?
kongfooey said:
Hello,
I have an unlocked EVO 3D with HBOOT 1.5 S-on.
I flashed the phone and replaced InfectedRom with Warm Two Point Three. After installing new rom and reseting, phone is now stuck on HTC startup screen.
Please help!!! I appreciate and welcome all feedback. Thank you
Click to expand...
Click to collapse
You need to flash boot.img/kernel using fastboot or Flash image GUI or else you will face issues if the ROM uses kernel other than your current one.
This is the limitation of HTC unlock method (S-ON)
mnomaanw said:
You need to flash boot.img/kernel using fastboot or Flash image GUI or else you will face issues if the ROM uses kernel other than your current one.
This is the limitation of HTC unlock method (S-ON)
Click to expand...
Click to collapse
Thank you!
I flashed the boot.img using fastboot as you suggested. Now the phone is stuck in an endless loop between powering off and the HTC startup logo.
It appears that I am getting closer to fixing the problem but I am still stuck. Can you help further please?
Thanks again!
mnomaanw said:
You need to flash boot.img/kernel using fastboot or Flash image GUI or else you will face issues if the ROM uses kernel other than your current one.
This is the limitation of HTC unlock method (S-ON)
Click to expand...
Click to collapse
Thanks for your reply.
I did wipe all the way. How do I tell whether I have 2.08 or 2.17. if the phone not able to start up?
I flashed boot.img using fastboot. I just realized that the bootloader when doing and Hboot tries to load the image indicates no image or wrong image.
I am either missing a step or did something wrong.
Please help!
did you make a backup of Infected before you flashed?
When you say you installed Warm did you install and actually get it fully booted and set up your home screens and all that and it only stuck on the first reboot after? or was it right after you flashed warm?
Really if you made a backup of infected or what you were running before you should be able to restore that via recovery then boot up normal. Then use FlashImageGUI to flash the kernel needed for Warm, then reboot into recovery mode and flash the other portion of the Rom from the custom recovery.
Unfortunately, I did not back up Infected or other previous roms. I didn't know that I should, I only backed up my apps using Titanium. I now know better.
Still stuck in loop mode. I have been searching the forums for some possible solutions but so far nothing has worked.
I am up the creek without a paddle...
kongfooey said:
I used Titanium Backup to back up apps etc. is that the same as backing up the rom (Infected)?
If I had the backup how do I recover using recovery? I have been reading other posts in the forum and have tried some of the suggestions. I wiped the data and cache.
I am up the creek without a paddle...
Click to expand...
Click to collapse
na TiBackup isn't the same as backing up the Rom itself.
Full backups are done from within the custom recovery...
the boot.img you pushed via fastboot earlier. where did you get it from?
Silly me... I realized that Titanium backup was not the correct backup after I posted.
I took the image from the Warm zip file. I initially thought the problem was fixed until I realized that the phone is in an endless loop...
Still looping
kongfooey said:
Silly me... I realized that Titanium backup was not the correct backup after I posted.
I took the image from the Warm zip file. I initially thought the problem was fixed until I realized that the phone is in an endless loop...
Still looping
Click to expand...
Click to collapse
well to be honest I would just go back and start form scratch at this point since pushing the kernel via fastboot somehow didn't take for you nor did clearing cache's after the fact.
after pushing the kernel via fastboot, have you tried doing that again, and then going into recovery and flashing the rom again? If that doesn't work you might as well just go back to stock and push stock kernel flash stock rooted OTA, boot up, and use FlashImageGUI to push the Warm kernel then go back to flashing the Warm rom in recovery...
really before pushing the stock kernel if you wanna test to see if your initial push of Warm kernel even took fully just fully wipe data and try flashing infected again in recovery. If it boots fine then you know your fastboot push didn't take before to begin with...
Edit:
before i even really get more into this. does Warm even use another kernel beside the stock one? If they dont then all of this could of resulted from a bad download of the rom itself being flashed...
Sgt. Slaughter, I salute you...
I played around with your suggestions. Got it working... I flashed a different boot.img and it solved the problem. I may have gotten a bad Warm rom...
Thanks again!!!
Note: if you took/installed the latest update (2.17.651.5) you won't be able to use roms based off earlier firmware/kernels (ie 2.08.651.2 or 651.3) b/c of kernel differences (I think I've read that somewhere).
I believe Warmtwopointthree and Infected are not using the latest base/kernel.
Edit: saw you posted right before me. So what kernel/boot.img did you use?
kongfooey said:
Sgt. Slaughter, I salute you...
I played around with your suggestions. Got it working... I flashed a different boot.img and it solved the problem. I may have gotten a bad Warm rom...
Thanks again!!!
Click to expand...
Click to collapse
Nice good to hear. Fact you had your phone even semi-booting makes solving anything wrong with it usually trial and error and ends up not being so bad to fix...
I used boot.img from OTXE Titan HD ODEXed New Beats!
I need to educate myself a bit more about the differences between kernel and .imgs etc...
Thanks for your response. I greatly appreciate!!
I'm having a very similar issue, I rooted my Evo using Revolutionary and installed CW Recovery and everything was fine so I tried installing ZR3D and part way through the install, my phone turned off and now it wont get past the HTC boot screen. I went into CW Recovery but nothing is working, no matter what option I choose [even Turn off phone or reboot] it gives me the CW logo but nothing happens.
I have HBOOT 1.49.1107 with S-Off
Try reflashing your recovery threw hboot.
#Root-Hack_Mod*Always\
StoneCold448 said:
I'm having a very similar issue, I rooted my Evo using Revolutionary and installed CW Recovery and everything was fine so I tried installing ZR3D and part way through the install, my phone turned off and now it wont get past the HTC boot screen. I went into CW Recovery but nothing is working, no matter what option I choose [even Turn off phone or reboot] it gives me the CW logo but nothing happens.
I have HBOOT 1.49.1107 with S-Off
Click to expand...
Click to collapse
Can you boot into Fast boot? If so, try connecting your phone to a computer and flashing a recovery through there. Then try to install the ROM.
Sent from my PG86100 using Tapatalk 2 Beta-6
coal686 said:
Can you boot into Fast boot? If so, try connecting your phone to a computer and flashing a recovery through there. Then try to install the ROM.
Click to expand...
Click to collapse
Thanks for your help

Keep losing recovery

I am s-off with jboot running rezrom 3.4. For some reason for the last two or 3 weeks i have lost amon ra 4 or 5 times. It just randomly disappears and i have to reflash it. Any idea on why this keeps happening?
hardfallen87 said:
I am s-off with jboot running rezrom 3.4. For some reason for the last two or 3 weeks i have lost amon ra 4 or 5 times. It just randomly disappears and i have to reflash it. Any idea on why this keeps happening?
Click to expand...
Click to collapse
This is nearly impossible, what ar you flashing?
I've heard this on moto phones but they would force instal the stock recovery on boot so you had to remove that script
As far as I know HTC phones don't do this
Sent from my ADR6425LVW using Tapatalk 2
its happend with both 3.14 and 3.15. ive never had a problem until a few weeks ago then all of a sudden mysteriously it disappears. i cant figure out whats going on.
I read that happening a couple times but never saw a solution. I decided not to flash jboot and stick with reg hboot
Sent from my ADR6425LVW using Tapatalk 2
Evocm7 said:
I read that happening a couple times but never saw a solution. I decided not to flash jboot and stick with reg hboot
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
The first time I lost it I was not using jboot. I tried to reflash recovery but it would fail everytime so i flashed jboot and it worked, but I still keep randomly losing recovery
Later tonight I'm going to give a shot in making a script the installs a recovery on boot
Sent from my ADR6425LVW using Tapatalk 2
Did you happen to leave an RUU on the SD card? Would only be a problem every time you boot into hboot, but still...
socal87 said:
Did you happen to leave an RUU on the SD card? Would only be a problem every time you boot into hboot, but still...
Click to expand...
Click to collapse
Nope. the very first thing i do after flashing anything is delete the file immediately when i boot back up.
What do you mean "lose" recovery? You can't boot to recovery, as in it just hangs at the splashscreen, or you boot to HTC recovery?
tekhna said:
What do you mean "lose" recovery? You can't boot to recovery, as in it just hangs at the splashscreen, or you boot to HTC recovery?
Click to expand...
Click to collapse
Whether i hit reboot to recovery or manually try to boot to recovery with a battery pull and volume down and power the phone will just boot up normally without ever going to recovery. I then have to reflash amon via fastboot and it works again.
hardfallen87 said:
Whether i hit reboot to recovery or manually try to boot to recovery with a battery pull and volume down and power the phone will just boot up normally without ever going to recovery. I then have to reflash amon via fastboot and it works again.
Click to expand...
Click to collapse
Post the command you are using to flash recovery
Sent from my ADR6425LVW using Tapatalk 2
Would having fastboot checked cause this? Just thinking out loud.
Sent from my ADR6425LVW using xda premium
Fastboot flash recovery (name of file). I can flash it fine it just eventually disappear. And fastboot is not checked.
I'm lost as to what could cause this..... Have you tried CWM recovery and see if same thing happens? I doubt it matters. Just throwing things out there
Sent from my ADR6425LVW using Tapatalk 2
Are you s-off?
Which Rom are you running ?
Sent from my ADR6425LVW using Tapatalk 2
No I haven't tried cwm I'm not a fan of it. I am s off running rezrom 3.4. I've ran it forever with no problems till recently. I'm completely stumped.
That's so odd. Try downloading quick boot from the market and seeing if it will help getting you into recovery. It can't be disappearing completely can it?
Sent from my ADR6425LVW using Tapatalk 2
It'll be there for anywhere from a couple days to a week and then vanish. My nandroid folder will still be there but no recovery
hardfallen87 said:
No I haven't tried cwm I'm not a fan of it. I am s off running rezrom 3.4. I've ran it forever with no problems till recently. I'm completely stumped.
Click to expand...
Click to collapse
I know. I don't like it either. I meant trying it to see if the same thing still happens, not to replace amon ra.
Sent from my ADR6425LVW using Tapatalk 2
I'll try it out tomorrow and twrp to see what happens

So I'm stuck in bootloop (Rooted Evo 3D)

So, I rooted my phone last night and ever since I've been stuck in bootloop. I loaded one rom and it was in bootloop all night until the phone died. I charged the phone up, wiped it and tried another, stuck in bootloop for hours with nothing working. Now, the bigger problem is, I - being an idiot - forgot to do a nandroid backup so there is nothing to restore too, yet when I set it to factory settings it's once again stuck in bootloop.
All my phone now displays is the green HTC logo on the white background, until the phone battery dies.
So... how screwed am I?
EDIT: CDMA, S-on, 1.50, I used HTC dev to root it.
Did you root with HTC dev. You need to flash the boot.IMG using fastboot.
Sent from my HTC Desire S using XDA
MSK01 said:
So, I rooted my phone last night and ever since I've been stuck in bootloop. I loaded one rom and it was in bootloop all night until the phone died. I charged the phone up, wiped it and tried another, stuck in bootloop for hours with nothing working. Now, the bigger problem is, I - being an idiot - forgot to do a nandroid backup so there is nothing to restore too, yet when I set it to factory settings it's once again stuck in bootloop.
All my phone now displays is the green HTC logo on the white background, until the phone battery dies.
So... how screwed am I?
Click to expand...
Click to collapse
We need more info dude.
CMDA or GSM?
what rom did you try to install?
hboot 1.50 or 1.40?
S-On or S-OFF
The more info the more we can help you.
iTzLOLtrain said:
We need more info dude.
CMDA or GSM?
what rom did you try to install?
hboot 1.50 or 1.40?
S-On or S-OFF
The more info the more we can help you.
Click to expand...
Click to collapse
CDMA, S-on, 1.50, I used HTC dev to root it. CM 9 Nightly.
Do what I said. Boot your phone into the boot loader. Select fastboot. Stick the boot.IMG from the Rom you used into the folder on the pc that you used with htcdev.
Connect your device.
Open up command prompt. Navigate to the folder in command prompt where you put the boot.IMG
Type fastboot flash boot boot.IMG
If it works it will say so restart your phone and enjoy.
Sent from my HTC Desire S using XDA
Spazz Monk3y said:
Do what I said. Boot your phone into the boot loader. Select fastboot. Stick the boot.IMG from the Rom you used into the folder on the pc that you used with htcdev.
Connect your device.
Open up command prompt. Navigate to the folder in command prompt where you put the boot.IMG
Type fastboot flash boot boot.IMG
If it works it will say so restart your phone and enjoy.
Sent from my HTC Desire S using XDA
Click to expand...
Click to collapse
If you hadn't said anything I probably would have been running around in circles for the rest of the day. I just did and I'm waiting for it to restart right now. Hopefully it works.
Hopefully it will work. If you flash anymore roms you have to do the same flash boot.img using fastboot since you unlocked with HTC dev.
Sent from my HTC Desire S using XDA
Spazz Monk3y said:
Hopefully it will work. If you flash anymore roms you have to do the same flash boot.img using fastboot since you unlocked with HTC dev.
Sent from my HTC Desire S using XDA
Click to expand...
Click to collapse
Meaning I can just nandroid backup this rom? Or do I have to reflash it then flash the new ones over it?
If you want to flash a new rom do a nandroid backup first and then wipe everything. But everytime you flash a new Rom you have to flash the boot.IMG seperatley that was supplied with the Rom if that makes sense. This also applied when doing a recovery.
Sent from my HTC Desire S using XDA
Spazz Monk3y said:
If you want to flash a new rom do a nandroid backup first and then wipe everything. But everytime you flash a new Rom you have to flash the boot.IMG seperatley that was supplied with the Rom if that makes sense. This also applied when doing a recovery.
Sent from my HTC Desire S using XDA
Click to expand...
Click to collapse
Unless the boot.IMG is automatically with each rom that does not make sense. However, if that means (which I pretty sure it does, I just need that extra clear clarification) that a new boot.IMG is supposed to be supplied with every single new ROM then that would explain why my phone is still in bootloop. No changes since last time I was on, about an hour ago I took the battery out and restarted it.
So it's still in bootloop whenever I try anything.
Help as well...
Stuck in the same problem. Hboot 1.50, S-on, and I'm trying to load Evergreen's CM7 port. I'm also using CWM 4.x (can't remember number, just the non touch version). Whenever I try to start my phone all I get is the white HTC screen with the little vibrate, then the black screen, and then the HTC screen once again and so on. I've tried flashing the boot from the file and then flashing the ROM with and without the boot.img in the .zip file. Help me. Please.
You need to flash the rom first then restart your phone load in to fastboot and flash the boot.img using fastboot. Search the forums there should be a more detailed way on how to do this. But its pretty much the same instructions I gave in previous post.
Try following this if your struggling.
https://www.dropbox.com/s/8qonxj8jsawcesl/Android Fastboot boot.docx
Sent from my HTC Desire S using XDA
If that last reply was meant me, I've already tried that. Doesn't change anything at all.
Ah ok you mentioned you flashed the boot.img first that's all
Also try formatting your sd card or use a spare one and format that and then flashing the Rom and boot.IMG. I had to do that with my desire s.
Sent from my HTC Desire S using XDA
Spazz Monk3y said:
You need to flash the rom first then restart your phone load in to fastboot and flash the boot.img using fastboot. Search the forums there should be a more detailed way on how to do this. But its pretty much the same instructions I gave in previous post.
Try following this if your struggling.
https://www.dropbox.com/s/8qonxj8jsawcesl/Android Fastboot boot.docx
Sent from my HTC Desire S using XDA
Click to expand...
Click to collapse
That worked. Holy ****, that worked! Thank you so much!!
Spazz Monk3y said:
You need to flash the rom first then restart your phone load in to fastboot and flash the boot.img using fastboot. Search the forums there should be a more detailed way on how to do this. But its pretty much the same instructions I gave in previous post.
Try following this if your struggling.
https://www.dropbox.com/s/8qonxj8jsawcesl/Android Fastboot boot.docx
Sent from my HTC Desire S using XDA
Click to expand...
Click to collapse
doesnt work for me :<
Unlocked HBOOT 1.53.0007
rooted with superuser
S-ON
Revolionary CWM v4.0.1.4 (also tried to flash 4EXT but it doesnt work!!:/ )
ROM: cm-9-DevilToast-0.7.5-shooteru.zip
any tips?
sabbath88 said:
doesnt work for me :<
Unlocked HBOOT 1.53.0007
rooted with superuser
S-ON
Revolionary CWM v4.0.1.4 (also tried to flash 4EXT but it doesnt work!!:/ )
ROM: cm-9-DevilToast-0.7.5-shooteru.zip
any tips?
Click to expand...
Click to collapse
Get s-off using the wire trick.
Read, Search, Read again, ... Then Ask with Tapatalk 2

Stock (unrooted) Thunderbolt stuck in boot loop

My daughter has a stock Thunderbolt, which has worked since Christmas. All of a sudden a couple weeks ago, she woke up and it was stuck in a boot loop on the HTC splash screen.
I'm still able to get into bootloader, but unable to do a factory reset, or flash a stock RUU. Cannot boot into (stock) recovery. As soon as it tries to load the recovery console, it starts the splash screen looping again. Seems like recovery is corrupt or something
I've tried some unbricking processes, but nothing has worked. If I could get adb to see it, I'd just root it and put cwm on it, but can't get that either.
***LOCKED***
Mecha XD Ship s-on
hboot-1.05.0000
microp-/
radio-1.49.00.0406w_1
eMMC-boot
Jul 19 2011, 14:51:00
Any help is very much appreciated. Verizon store said they can't flash a fresh recovery on it, or the latest RUU...
Nothing? No suggestions?
Maybe something herehttp://androidforums.com/thunderbolt-all-things-root/449138-boot-loop.html will help...
What won't work with the RUU?
It possibly could be caused because of a corrupt sim card and/or a corrupt SD card. Try removing the SD card and see if it will load up. If still nothing, take it to Verizon for another sim card. If you go into a corporate store, they won't charge you for another sim.
Just a couple of my suggestions.
Sent from my ADR6400L using xda premium
I will try that link above.
I brought it into a privately owned verizon store on Thursday, explained to them what was going on, they said they have no idea, and I should bring it to a corporate store, so I did.
I told the guy exactly what was happening. He assumed a read a few things on the internet, so treated me like I've never used a phone before. I have had a G1, Evo, and Evo 3D...all rooted and mega customized, so not like this is my first attempt at using a smartphone.
I've tried booting without the sdcard, same thing. I've tried booting without a sim card, same thing. I tried with another verizon LTE sim card, same thing.
When I try to flash anything, I put the zip on the sdcard, power on to hboot, let it load the zip, then it does nothing, just sits at hboot. I scroll down to recovery to be able to select to restart or power down, press power, it goes to the white HTC splash screen, then the circular arrows above the phone, then to the red X, then back to HTC splash screen and boot loops the splash screen.
I can tell you your recovery is gone. Try downloading the hboot flashable cwm again and flash that in hboot. If you can get into recovery maybe you will be able to flash a rom again. You may also want to reformat your sd card or even try a different one.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
I can tell you your recovery is gone. Try downloading the hboot flashable cwm again and flash that in hboot. If you can get into recovery maybe you will be able to flash a rom again. You may also want to reformat your sd card or even try a different one.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
that's exactly what I told the verizon dude, that recovery is gone and all they need to do is flash it back on, he said that's not possible, handed the phone back to me and said "have a good day".
I knew it was a long shot when I went in there and had to tell them how to boot into hboot, and how to remove the battery.
Don't I have to be S-OFF to flash cwm? Remember, it's stock, unrooted, and S-ON
How didn't the ruu work?
Sent from my ADR6400L using Tapatalk 2
trter10 said:
How didn't the ruu work?
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
Because when hboot loaded it, which took a few minutes to load and verify, it then automatically went into recovery to actually flash it, which put it right back into the boot loop.
d0m1n0 said:
Because when hboot loaded it, which took a few minutes to load and verify, it then automatically went into recovery to actually flash it, which put it right back into the boot loop.
Click to expand...
Click to collapse
Now that I think about it, it shouldn't have to go into recovery to flash it, it should have been just fine from hboot....but...after I flashed the RUU, it did reboot into recovery, and started the loop
So did you remember to clear cache and dalvik cache? That would put you in a boot loop every time.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
So did you remember to clear cache and dalvik cache? That would put you in a boot loop every time.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
They weren't installing a rom
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
So did you remember to clear cache and dalvik cache? That would put you in a boot loop every time.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
No...it's stock, stock recovery, stock rom, S-ON...she brought it to me in this condition. It's not a rooting gone wrong. If I could get the laptop to see it, I'd root the damn thing so I can get cwm on it.
When she brought it to me, it was in this exact state. First thing I tried was to boot into recovery, which didn't work. So I googled for 'thunderbolt boot loop' and started trying things.
Before I go any further, I'd like to thank everyone for their input and thoughts. She's 12, and I really don't want to have to buy her a new phone.
d0m1n0 said:
No...it's stock, stock recovery, stock rom, S-ON...she brought it to me in this condition. It's not a rooting gone wrong. If I could get the laptop to see it, I'd root the damn thing so I can get cwm on it.
When she brought it to me, it was in this exact state. First thing I tried was to boot into recovery, which didn't work. So I googled for 'thunderbolt boot loop' and started trying things.
Before I go any further, I'd like to thank everyone for their input and thoughts. She's 12, and I really don't want to have to buy her a new phone.
Click to expand...
Click to collapse
Try redownloading the ruu
Sent from my ADR6400L using Tapatalk 2
I have the exact same problem, I am using a custom rom, killasense.
It loads to HTC splash when I try to connect to computer or try to go into recovery from revolutionary. It says S-OFF on revolutionary, not sure what it means.
Please update if you find a solution, I am trying to do a factory reset, but cannot.
If it says s off that means the phone has been rooted. You're running killasense which is a custom rom.. If you want to go back to stock simply download the most recent ruu, put it on the root of your sd card and rename the file to PG05img. Reboot into the bootloader press the power button to enter fast boot. It will ask you if you want to update select yes. After it completes make sure you rename the file so it doesn't try running the ruu every time you enter the bootloader. Also check the md5 before you try to run it.
Sent from my ADR6400L using Tapatalk 2
I downloaded the 2.1 mecha ruu and tried to load it in hboot, and it said the existing Rom is older. So that mean I can't flash a newer ruu? Gotta be the same or older?
Since I don't have a thunderbolt, I'm not familiar with ruu versions, any way to tell in hboot so I can download the same or older?
Sent from my PG86100 using xda app-developers app
I put a new rom file (BAMF SoaB) into the SD card and renamed it PG05img, went to Revolutionary it said loading PG05img, but after it loaded it did not show a yes or no prompt. It went back to home screen of revolutionary after saying "No image or wrong image", still stuck on boot loop splash screen.
Eksellent said:
I put a new rom file into the SD card and renamed it PG05img, went to Revolutionary it said loading PG05img, but went back to the revolutionary screen without installing I think, still stuck on boot loop splash screen.
Click to expand...
Click to collapse
That means you need to redownload it.
Try this one http://db.tt/z7zbekNa
Sent from my ADR6400L using Tapatalk 2

Categories

Resources