I'm on an HTC Evo 4G rooted running CyanogenMod7 with Tiamat kernel and Clockwork mod. I went to sleep last night and everything was working fine, when I woke up this morning, I rolled over and my phone was stuck in a boot loop. I flashed back to my only backup (UltimateDroid) and it did the same thing. I flashed the stock rom and still no luck. Will a hard reset fix this? but more importantly, what is a possible cause? so I can avoid this happening again.
I don't know what caused the initial bootloop, but before you flash a new rom or restore from a backup, you need to wipe data, cache and dalvik. If you have problems (which is fairly common with ClockworkMod on the Evo) try wiping multiple times. You can also try using something like superwipe or a format all zip.
If the problem persists, Amon Ra is a great alternative to ClockworkMod. Many users have problems with CWM, but switching to Amon Ra usually helps.
(from... Evo/MIUI/Tapatalk)
I wiped everything several times.
I already did the hard reset and it still boot loops. it gets through the stock boot screen ( Sprint, Now Network, 4g, etc) And shows the lock screen, but before I do anything, it reboots again.
When I try to reboot into recovery it shows thoe phone with a red triangle/exclamation point icon
mrbliven said:
I wiped everything several times.
I already did the hard reset and it still boot loops. it gets through the stock boot screen ( Sprint, Now Network, 4g, etc) And shows the lock screen, but before I do anything, it reboots again.
When I try to reboot into recovery it shows thoe phone with a red triangle/exclamation point icon
Click to expand...
Click to collapse
When you boot into the bootloader, are you s-off or s-on? The red triangle means you don't have a recovery. If you're s-on, you're not rooted. When you say you flashed the stock rom, did you flash the stock rooted rom or did you use an RUU?
(from... Evo/MIUI/Tapatalk)
it's an RUU. I ran unrevoked's S tool, S is on. Then I ran the RUU as PC36IMG.zip which is the last thing I did and I'm still in a boot loop.
I downloaded the second one on this list.
http://forum.xda-developers.com/showthread.php?t=884060&highlight=hboot-0.97+ruu
mrbliven said:
it's an RUU. I ran unrevoked's S tool, S is on. Then I ran the RUU as PC36IMG.zip which is the last thing I did and I'm still in a boot loop.
I downloaded the second one on this list.
http://forum.xda-developers.com/showthread.php?t=884060&highlight=hboot-0.97+ruu
Click to expand...
Click to collapse
The RUU is why you don't have a recovery. Since your s-on & on the stock rom, you're safe to take it in to Sprint. Delete any rooting and unrooting stuff from your SD card (back it up to your computer first if you want to save it) before you take it in. Just tell them that you don't know what happened and play dumb. I had a phone that had never been rooted before do something similar, but since I was knowledgeable about my phone, I watched the guy check the bootloader and try to go into recovery. He probably thought I had rooted it. So don't mention any rooting terminology and you should be fine... they can't prove anything anyway.
You can try another RUU again if you want, but if it still won't boot, you'll probably need to get a new phone.
(from... Evo/MIUI/Tapatalk)
Okay thanks! I'll try that. Will I have to pay the $100 deductible for the insurance, or is that covered?
mrbliven said:
Okay thanks! I'll try that. Will I have to pay the $100 deductible for the insurance, or is that covered?
Click to expand...
Click to collapse
Nope. Free of charge as long as you have insurance. The only time you should have to pay the deductible is if it's lost/stolen, if it has water damage, and possibly other physical damage like a busted screen. I'm not sure of the exact policy as it has changed a couple times, but you'll be covered.
(from... Evo/MIUI/Tapatalk)
Should I delete the RUU? (PC36IMG)
mrbliven said:
Should I delete the RUU? (PC36IMG)
Click to expand...
Click to collapse
Definitely. Any roms, kernels, format all zips, etc. You may just want to take the card out since there may be stuff like Titanium Backup backups, etc. They shouldn't look at your SD card, but if they want you to leave the phone with them to work on or test, they may look. If they ask why you took it out, just tell them there's dirty pictures or other personal info you don't want anyone seeing.
(from... Evo/MIUI/Tapatalk)
Okay, thanks for all the help. Took it back today and they're going to replace it (free of charge). Unfortunately the phone is back-ordered, so I'll have to wait till Wednesday.
mrbliven said:
Okay, thanks for all the help. Took it back today and they're going to replace it (free of charge). Unfortunately the phone is back-ordered, so I'll have to wait till Wednesday.
Click to expand...
Click to collapse
That's great! Last time they got me a new phone it was back-ordered. They told me they had no idea when it would be there (probably 4-5 days) but it was there in two. I'd call on Monday or Tuesday and see if it came in early.
It is strange how your phone pooped out randomly. I'm sure there's a reason, it's just odd.
(from... Evo/MIUI/Tapatalk)
I don't know, I'm still googling my ass off trying to figure it out. I think it may have something to do with the kernel. I'm still going to root my new phone, but be sure to keep a back-up of the original.
Related
OK Guys and Gals, Here is what is going on with the radio issue. No Matter WHAT radio combos you may be using. As some of you may know by my earlier posts I live in a huge 4G network and never get anything, but 4G and (3G only for a min on boot) This is why I didn't have ANY issue's until I got curious and wanted to try something. On our tbolts, if you try to make a call while in 3G the 3G will drop out until the call is over. I went back to froyo, got pissed and went strait back to GB (doesn't matter what Rom as all the dev have clearly stated) when I did go back to GB things were tight as usual. worked like a charm. I used it as I normally would and everything was fine. upon a self induced restart, before my phone had a chance to obtain 4G (still in 3G) I decided to make a test call to see if the 3G would drop. It didn't. Quickly after I ended the call the phone booted in to bootloader. Thank God I had removed the GB RUU because I don't have a card reader to remove the RUU. I forgot to mention I do have the latest Rom Mgr and was able to get into recovery and simply reboot. After that reboot I would get to my home screen, but this time the 3G only would come up and then reboot. Time after time of rebooting I tried other things such as toggle radio to just grab 4G, then the phone rebooted again! upon the next full boot I quickly moved the original froyo radio strait to the sd card. And yet another reboot. This time I got a Rom Mgr error and noticed that Rom mgr was no longer flashed!!! I flashed it real quick because I knew another reboot was on its way. Rom mgr flashed and I told it to boot in to recovery. Thank **** I flashed Rom manager because if not I would be in continuous boots like the unfortunate others. Once in recovery I Realized that I had told my phone to go in to recovery via Rom mgr. and if I did a restore, the phone would have booted back up with my froyo rom but with the GB radio! so I told CWR to just reboot so I could tell the phone to go into recovery via the pwr restart option (thus not restarting after I flashed my froyo recovery) Once recovery of my froyo rom was complete I used ADB to reboot bootloader and SUCCESS! Bottom line you can not make a call while on 3G with any of the current GB radios, you gotta be quick, Make sure ROM mgr is actually flashed!!!! and hopefully can dump the froyo radio on to your SD card before an inevitable reboot happens! and have some ADB knowledge. I'm certain this is whats going on! People make a call while in 3G and its all down hill from there. So dont bother with telling radio settings to stick with one band. Once this happens, there is no turning back. Any questions PM me. I'm glad I tried this out before Vaca tomorrow with a FUBAR Tbolt
Hope this helps developers somehow. Good luck!
Also check a couple quotes from the development thread. Remember I'm going on vacation n won't be able to reply to many comments. Maybe just share your experience. Thank you
Sent from my ADR6400L using XDA Premium App
The people with the reboots can't get to Rom manager or recovery or anything. It reboots even if you try to gget in Clockwork.
I live in a 3g only area and make calls all the time on 3g. I have myine set to cdma auto so its always on 3g and mine hasn't done it yet. I'm on the gb radio
Sent from my ADR6400L using Tapatalk
smalltownbird said:
I live in a 3g only area and make calls all the time on 3g. I have myine set to cdma auto so its always on 3g and mine hasn't done it yet. I'm on the gb radio
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
Yes this is true because your phone doesn't try to toggle to the 4g lte radio
Sent from my ADR6400L using XDA Premium App
corenojoe said:
The people with the reboots can't get to Rom manager or recovery or anything. It reboots even if you try to gget in Clockwork.
Click to expand...
Click to collapse
They can't get into rom Mgr because they didn't notice rom manager needed reflashed right before first reboot.
Sent from my ADR6400L using XDA Premium App
I live in a 4G area, was running GB Bamf rom. Made plenty of calls on 3G and on 4G lte. Never had this happen.
dopediculous said:
They can't get into rom Mgr because they didn't notice rom manager needed reflashed right before first reboot.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
OK, first off ROM Manager and Clockwork Recovery are two different things.
ROM Manager is an app and Clockwork is your recovery.
If your phone is bricked you can't get into ROM Manager because the phone will not boot up. They can get into Clockwork for...oh I don't know, maybe 2 - 5 seconds and they the phone reboots again. Ask me how I know
A bootloop is NOT your phone bricking, if it was I would have bricked many, many phones in my time. If when you press power and volume down your phones brings up the bootloader. If you select recovery and your phone brings up your recovery screen without bootlooping you are fine.
refresh my memory, my poor old brain is on overload from all the brick posts....
Aren't the "bricked" phones also unable to stay in hboot for more than a few seconds without rebooting? If so, then what the OP is stating is NOT the same thing others reported because he states he could reflash the radio, suggesting a stable hboot/bootloader.
Seems like if you've got a stable hboot, you're not truy bricked, as the first post here shows....
bp328i said:
Ask me how I know
Click to expand...
Click to collapse
If you have a bricked device please go post in the stickied thread in app/dev.
Oh and OP - Paragraphs are a good thing. Just sayin...
bp328i said:
OK, first off ROM Manager and Clockwork Recovery are two different things.
ROM Manager is an app and Clockwork is your recovery.
If your phone is bricked you can't get into ROM Manager because the phone will not boot up. They can get into Clockwork for...oh I don't know, maybe 2 - 5 seconds and they the phone reboots again. Ask me how I know
A bootloop is NOT your phone bricking, if it was I would have bricked many, many phones in my time. If when you press power and volume down your phones brings up the bootloader. If you select recovery and your phone brings up your recovery screen without bootlooping you are fine.
Click to expand...
Click to collapse
I ment while in rom Mgr to make sure cwr is actually flashed. Mine was then after reboot I noticed cwr was no longer there. In rom Mgr it just said what the current cwr would be if I choose to flash it. If people miss this after a stupid reboot, the next reboot may not be so kind...
Sent from my ADR6400L using XDA Premium App
bp328i said:
OK, first off ROM Manager and Clockwork Recovery are two different things.
ROM Manager is an app and Clockwork is your recovery.
If your phone is bricked you can't get into ROM Manager because the phone will not boot up. They can get into Clockwork for...oh I don't know, maybe 2 - 5 seconds and they the phone reboots again. Ask me how I know
A bootloop is NOT your phone bricking, if it was I would have bricked many, many phones in my time. If when you press power and volume down your phones brings up the bootloader. If you select recovery and your phone brings up your recovery screen without bootlooping you are fine.
Click to expand...
Click to collapse
In fewer words that's exactly what I was saying. Seems like he thinks Rom Manager is recovery.
distortedloop said:
refresh my memory, my poor old brain is on overload from all the brick posts....
Aren't the "bricked" phones also unable to stay in hboot for more than a few seconds without rebooting? If so, then what the OP is stating is NOT the same thing others reported because he states he could reflash the radio, suggesting a stable hboot/bootloader.
Seems like if you've got a stable hboot, you're not truy bricked, as the first post here shows....
Click to expand...
Click to collapse
Mine was a TRUE bricked phone but my bootloader stilled would stay on. The bootloader screen was the only thing that would not bootloop. I was able to flash the stock RUU and stock bootloader and it still would not go past the splash screen.
funkybside said:
If you have a bricked device please go post in the stickied thread in app/dev.
Oh and OP - Paragraphs are a good thing. Just sayin...
Click to expand...
Click to collapse
Mine was bricked last Saturday, I don't have the phone anymore. It's been sent off for repair. Lucky me gets to rock my DInc for the next 2 - 3 weeks, DAMN 3G is slow.
dopediculous said:
I ment while in rom Mgr to make sure cwr is actually flashed. Mine was then after reboot I noticed cwr was no longer there. In rom Mgr it just said what the current cwr would be if I choose to flash it. If people miss this after a stupid reboot, the next reboot may not be so kind...
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
Your phone will still reboot without a recovery. There was an issue awhile back when I had my OG Droid with ROM Manager wiping out recovery. People would try to boot into recovery to fix something and oops no recovery.
You can flash a recovery image via adb.
bp328i said:
Your phone will still reboot without a recovery. There was an issue awhile back when I had my OG Droid with ROM Manager wiping out recovery. People would try to boot into recovery to fix something and oops no recovery.
You can flash a recovery image via adb.
Click to expand...
Click to collapse
yeah, that was annoying. Believe that's when they told everyone to check the "erase recovery" option in the Rom Manager settings and that seemed to help.
PJnc284 said:
yeah, that was annoying. Believe that's when they told everyone to check the "erase recovery" option in the Rom Manager settings and that seemed to help.
Click to expand...
Click to collapse
Really funny thing was that was going on right when the Froyo leak came out for the OG Droid and the first ROM I flashed I hated. So when I went to flash my nan-droid there was no recovery and I did not know about the issue so I ended up sbf'ing back to stock and rerooting again.
I have seen a bootloop on a phone that was not running GB or rooted. A guy I work with brought me his phone a few weeks ago and wanted me to let him use my battery to boot his phone. When I put my battery in and saw what it was doing i booted it into Hboot (of course S-on) so I couldn't do much for him. Of course the Verizon Tech's weren't much help to him either, but they did send him a CLN Device. You can pass this along to jcase as I don't have enough posts to be able to post in the DEV forum yet. I read and rarely post unless I believe I have something useful to add.
So here's the situation. I've been running NoSensi 1.0.4 ROM w/o problems for the past month but all of a sudden tonight my phone started to freeze up. I would take the battery out and turn it back on but after a few minutes the phone would freeze up again. So I decided to try to flash the new version on NoSensi (1.0.8) and the first step was to flash the NoSensi_EXT4_Wipe and it was almost complete in CWM when it froze up and wouldn't respond. Waited a few more minutes to be sure it wasn't just taking a while so I took the battery out and went back into recovery. In CWM, I see the menu options but when I try to select install from SD, the CWM menu would reset every few seconds and leave me at the main screen.
So now I'm stuck with a phone that won't boot cause I don't have a proper ROM on and can't install a new ROM cause CWM is messed up.
Any ideas on how I can reinstall CWM or something?
First off, can you boot to hboot? And next do you have adb set up on your PC or Mac?
I'm gonna be honest with you, I can't really help you all the way but can give you the things you need to get started. And if anyone reads this and knows more about this please help thanks
Sent from my CM7 Nightly HTC Desire HD
Yes, I believe I can get into HBOOT, I get the white screen where the option of going into recovery of HBOOT. I do have adb on my PC, but don't know how to use it unless I have instructions.
Okay I remember going through the threads and saw something on using the PD98 img that has the recovery img inside instead of the system img. Ill look around but probably in the morning since its almost 2 for me. Or if someone knows what I'm talking that'd be great
Sent from my CM7 Nightly HTC Desire HD
bluizzo said:
Okay I remember going through the threads and saw something on using the PD98 img that has the recovery img inside instead of the system img. Ill look around but probably in the morning since its almost 2 for me. Or if someone knows what I'm talking that'd be great
Sent from my CM7 Nightly HTC Desire HD
Click to expand...
Click to collapse
I built a recovery PD98IMG for a user yesterday. It is the recovery I've been using since I rooted. It is v3.0.2.5 with offmode power mod, but It doesn't have any EXT4 support (don't get me started on EXT4).
CWM Recovery v3.0.2.5 in PD98IMG format:
http://hoxnet.com/droid/PD98IMG_cwmrecovery.zip
Rename to exactly "PD98IMG.zip" and place it on the root (top level directory) of your sdcard, then boot to HBOOT and it should pick it up and prompt you to install.
I'm worried that there may be some hardware problem with your device if it keeps freezing up like that. It might just be a loose battery or loose sim holder, but it might be worse. I'd try to install a stock RUU just to be sure. You can install this one:
http://forum.xda-developers.com/showthread.php?t=1191793
It is completely stock and you'll lose root, but not S-OFF so re-rooting is easy. You can instead, install my rooted version of this ROM too. Identical to stock except that the system and boot images are properly rooted and busybox is installed:
http://forum.xda-developers.com/showthread.php?p=16118438#post16118438
If you must send it in for repairs and need to restore to factory settings, I have a tool for that too:
http://forum.xda-developers.com/showthread.php?t=1208507
Good luck and I hope it's just firmware related.
Gene Poole said:
I built a recovery PD98IMG for a user yesterday. It is the recovery I've been using since I rooted. It is v3.0.2.5 with offmode power mod, but It doesn't have any EXT4 support (don't get me started on EXT4).
CWM Recovery v3.0.2.5 in PD98IMG format:
http://hoxnet.com/droid/PD98IMG_cwmrecovery.zip
Rename to exactly "PD98IMG.zip" and place it on the root (top level directory) of your sdcard, then boot to HBOOT and it should pick it up and prompt you to install.
I'm worried that there may be some hardware problem with your device if it keeps freezing up like that. It might just be a loose battery or loose sim holder, but it might be worse. I'd try to install a stock RUU just to be sure. You can install this one:
http://forum.xda-developers.com/showthread.php?t=1191793
It is completely stock and you'll lose root, but not S-OFF so re-rooting is easy. You can instead, install my rooted version of this ROM too. Identical to stock except that the system and boot images are properly rooted and busybox is installed:
http://forum.xda-developers.com/showthread.php?p=16118438#post16118438
If you must send it in for repairs and need to restore to factory settings, I have a tool for that too:
http://forum.xda-developers.com/showthread.php?t=1208507
Good luck and I hope it's just firmware related.
Click to expand...
Click to collapse
Got CWM back with this, thanks so much! I tried doing the same method that was mentioned in this thread http://forum.xda-developers.com/showthread.php?t=1019868 but kept having issues with CWM resetting every 2 seconds which didn't allow me to use it at all. Your file worked and am flashing a ROM on now. Hopefully the random freezing was just random so I'm just going to do a fresh install of a ROM
Gene Poole said:
I built a recovery PD98IMG for a user yesterday. It is the recovery I've been using since I rooted. It is v3.0.2.5 with offmode power mod, but It doesn't have any EXT4 support (don't get me started on EXT4).
CWM Recovery v3.0.2.5 in PD98IMG format:
http://hoxnet.com/droid/PD98IMG_cwmrecovery.zip
Rename to exactly "PD98IMG.zip" and place it on the root (top level directory) of your sdcard, then boot to HBOOT and it should pick it up and prompt you to install.
I'm worried that there may be some hardware problem with your device if it keeps freezing up like that. It might just be a loose battery or loose sim holder, but it might be worse. I'd try to install a stock RUU just to be sure. You can install this one:
http://forum.xda-developers.com/showthread.php?t=1191793
It is completely stock and you'll lose root, but not S-OFF so re-rooting is easy. You can instead, install my rooted version of this ROM too. Identical to stock except that the system and boot images are properly rooted and busybox is installed:
http://forum.xda-developers.com/showthread.php?p=16118438#post16118438
If you must send it in for repairs and need to restore to factory settings, I have a tool for that too:
http://forum.xda-developers.com/showthread.php?t=1208507
Good luck and I hope it's just firmware related.
Click to expand...
Click to collapse
Yay that's what I was looking for, thanks soo much
Sent from my CM7 Nightly HTC Desire HD
so it seems it may be a hardware issue after all... sigh. Going to look to see if I can pick up another one for cheap on craigslist or something now cause mine was also used of CL about 5 months ago.
dtothesquare said:
so it seems it may be a hardware issue after all... sigh. Going to look to see if I can pick up another one for cheap on craigslist or something now cause mine was also used of CL about 5 months ago.
Click to expand...
Click to collapse
HTC warranties the device for a year. I don't think any Inspire is a year old yet so you might want to call them first. Even if not covered by warranty, HTC is pretty reasonable on repairs.
Gene Poole said:
HTC warranties the device for a year. I don't think any Inspire is a year old yet so you might want to call them first. Even if not covered by warranty, HTC is pretty reasonable on repairs.
Click to expand...
Click to collapse
Cool, thanks for the tip, i'll try to get stock by on then call them up
So I'm trying to run the PD98IMG image in HBoot, but its not auto-running anymore. Any ideas on how to manually have it run?
- EDIT: Nvm, it was due to bad sdcard
Gene Poole said:
I built a recovery PD98IMG for a user yesterday. It is the recovery I've been using since I rooted. It is v3.0.2.5 with offmode power mod, but It doesn't have any EXT4 support (don't get me started on EXT4).
CWM Recovery v3.0.2.5 in PD98IMG format:
http://hoxnet.com/droid/PD98IMG_cwmrecovery.zip
Rename to exactly "PD98IMG.zip" and place it on the root (top level directory) of your sdcard, then boot to HBOOT and it should pick it up and prompt you to install.
I'm worried that there may be some hardware problem with your device if it keeps freezing up like that. It might just be a loose battery or loose sim holder, but it might be worse. I'd try to install a stock RUU just to be sure. You can install this one:
http://forum.xda-developers.com/showthread.php?t=1191793
It is completely stock and you'll lose root, but not S-OFF so re-rooting is easy. You can instead, install my rooted version of this ROM too. Identical to stock except that the system and boot images are properly rooted and busybox is installed:
http://forum.xda-developers.com/showthread.php?p=16118438#post16118438
If you must send it in for repairs and need to restore to factory settings, I have a tool for that too:
http://forum.xda-developers.com/showthread.php?t=1208507
Good luck and I hope it's just firmware related.
Click to expand...
Click to collapse
So I tried reverting back to stock via the PD98IMG method with both the gingerbread and complete stock in the post you mentioned. Both them it updates fine but on the reboot it just hangs on the white htc screen. Any recommendations? Would HTC warranty if it's stuck like that?
It sounds like a hardware problem to me. The first and most obvious sign that a phone has been rooted is the S-OFF in the HBOOT screen. They probably won't warranty it if this is still set. Unfortunately, you need a functioning phone to get to the point that you can re-apply S-ON. I'm really not sure what advice I can give you at this point.
Gene Poole said:
It sounds like a hardware problem to me. The first and most obvious sign that a phone has been rooted is the S-OFF in the HBOOT screen. They probably won't warranty it if this is still set. Unfortunately, you need a functioning phone to get to the point that you can re-apply S-ON. I'm really not sure what advice I can give you at this point.
Click to expand...
Click to collapse
I figured as much. Oh well, going to miss the Inspire, really did like it except for that stupid battery door. Picked up a used captivate for cheap to hold me over until my next phone. Thanks for your help!
Missing CWM / No Recovery
Through a long string of mistakes, I'm stuck with an Inspire that will not load Recovery (just get black screen with phone icon and red exclamation point).
This thread was the best match I could find. I used the method above (renamed Gene Pool's file to PD98IMG.zip, placed on SD root), but HBOOT does not seem to find it during the startup scan.
Here is what I've got:
ACE PVT SHIP S-OFF
HBOOT-0.85.0007
I've tried 2 different SD cards - I got into this mess because radio updates were not being found in PD98IMG.zip files either, so feel like its an HBOOT problem.
Any ideas?
ctownj30 said:
Through a long string of mistakes, I'm stuck with an Inspire that will not load Recovery (just get black screen with phone icon and red exclamation point).
This thread was the best match I could find. I used the method above (renamed Gene Pool's file to PD98IMG.zip, placed on SD root), but HBOOT does not seem to find it during the startup scan.
Here is what I've got:
ACE PVT SHIP S-OFF
HBOOT-0.85.0007
I've tried 2 different SD cards - I got into this mess because radio updates were not being found in PD98IMG.zip files either, so feel like its an HBOOT problem.
Any ideas?
Click to expand...
Click to collapse
If you are sure you renamed it correctly (Windows didn't mangle the name with its stupid "hide extensions" feature) and you are S-OFF, then the only other thing it could be is a bad or weak SD Card. Do you have a spare to try?
I solved this. Figured it was not reading my SD cards so I reformatted one (FAT32), redid everything, and was able to re-flash CWM. Bizarre, since the same card has been used successfully several times on this phone.
I had a lunch TB4g and it just bricked today, I was running ShiftAOSP 1.2 (I believe unrelated) and the .802 radio (possible) but it will just go to the HTC screen and reset and keep trying to boot. I can get into HBOOT and FASTBOOT, I have tried to reflash a root friendly RUU but it didnt fix anything and still cant boot. Just giving you a heads up. I had it overclocked to 1.22, I had it in my car on the way home, sent one text, 23% battery and I plugged it into my CPU USB to charge for a little waiting for some friends to show up and that is when it went into bootloop. Heat was not an issue as I had used it minimally the whole day sending small texts. It did sustain a major G shock 2 days prior but no excessive G or roughness today. Since it can get into HBOOT it might be recoverable but thats to the devs to decide, I have the unlocked 1.04 hboot installed.
i doubt the radio caused it, but that sucks man. see if you can talk verizon into a bionic for a replacement.
Does it bootloop in recovery?
Sent from my HTC Thunderbolt
JBO1018 said:
Does it bootloop in recovery?
Sent from my HTC Thunderbolt
Click to expand...
Click to collapse
he wont be able to get to recovery, hes bricked. i had this sorta happen to me weeks ago but my phone recovered on its own. to say the least i put full insurance on it.
fixxxer2008 said:
he wont be able to get to recovery, hes bricked. i had this sorta happen to me weeks ago but my phone recovered on its own. to say the least i put full insurance on it.
Click to expand...
Click to collapse
He said it boots to the splash screen and he can get into hboot. So I'm confused why you would think he couldn't select recovery in hboot and see what happens. If he already flashed a full stock RUU custom recovery will be gone tho.
Sent from my HTC Thunderbolt
JBO1018 said:
He said it boots to the splash screen and he can get into hboot. So I'm confused why you would think he couldn't select recovery in hboot and see what happens. If he already flashed a full stock RUU custom recovery will be gone tho.
Sent from my HTC Thunderbolt
Click to expand...
Click to collapse
if i were him id just replace it. i just hope my tbolt lasts until the vigor ships.
it will boot to hboot and not reboot, but it will not boot to recovery
Have you tried flashing one of the recoveries that were modified to install through hboot? you can take your sd card out, and using a computer, place the PG05IMG.zip (search here @ XDA) and place it on the root of the card, flash through hboot. then using the computer again, remove the PG05IMG.zip from the sd card and go back into hboot and select recovery. i had to do this not too long ago and it worked for me, maybe it will help you.
I pulled the battery and wont plug it in all night to see if it resets some error it maybe had, my new phone is delivered tomorrow so its not a big deal.
fixxxer2008 said:
if i were him id just replace it. i just hope my tbolt lasts until the vigor ships.
Click to expand...
Click to collapse
I would agree. The whole reason I asked about recovery boot looping is because if it is thats pretty much identical symptoms everyone who had the boot loop of death "brick" thing had. If that is what the situation is I would get it s-on and get VZW to replace because I doubt he caused it.
Sent from my HTC Thunderbolt
fillyo said:
All you cheap ****ers trying to get something for free, if he bricked, his loss. Period.
Click to expand...
Click to collapse
Ditto. He probably told insurance he lost the phone and paid his $100 bucks.
People are so greedy these days. All for nothing and nothing for all.
Doesn't sound design like there was much effort to fix it either.
Questioned posted and shortly after a new one is on the the way?
Keep an extra phone around for instances like this.
Not everything is an insurance claim.
Sent from my A500 using XDA Premium App
You wonder why all the major companies are starting to hate people who root phones. Some people will flash a Rom everyday just to do it and if they miss up their phone they don't seem to care. Now do I think a thunderbolt is worth 700 bucks retail hell no it only cost about 125 to build. But people need to hit up these forums to try to fix their phones before they call Verizon. I read a few post of guys who buy bricks phone fix them and sell them so any bricked phone can be fixed as far as he said. Read up and don't be so quick to clear data as first sign of a problem. Always try what got me out of the bootloop of death.
1. Battery pull
2. Power and hold down volume button
3. Never and I mean never keep a radio stored on root of SD card after install this will cause Hboot to install radio and that is not what we want to do here.
4. Go to recovery
5. Under download folders in your SD card always keep a updated ROM of what ever ROM you are currently using or at least a stable build inside that folder if you are using AOSP keep a stable ROM that last worked for you so no data clear is needed if you are using Sense do the same.
6. I never flash a recovery at this point follow this it saved my phone. Clear cache, clear delvik, format system under mounts and storage.
7. Format is most important since it will not delete recovery if you need to try again. Go to install zip file, select zip file, and install your fresh ROM or a stable build I never have flashed a normal ROM or have I flashed back to a down graded GB ROM.
8. Reboot after ROM has flashed and your phone will boot correctly.
I hope this has helped it saved me a few times in boot loop of death. Stop clearing data you lose your recovery and stop flashing old GB ROMs thinking they will save you, it might but message me so I can say I told you so.
****NOTE also make sure you are updated to newest CWM there was a problem with bootlooping after flashing a kernel and maybe Rom. I had the problem with flashing a kernel sent me into a bootloop. Update or roll back.******
Sent from my ADR6300 using XDA App
The OP probably gets into recovery for a few seconds then bootloops randomly. If you are not bootlooping in hboot, you are not bricked. Find the stock ruu file and flash that through hboot. Although you will lose root, the phone should work again.
If it's bricked, throw it to the ground and stomp on it til it breaks and claim insurance..... That should piss some people off here
Seriously tho some guy mentioned something about a HBoot friendly RUU. You should look into it
Sent from my SICKLY INFECTED VirusBolt Synergy 3.0 using XDA Premium App
As far as I have seen the random and sudden boot loop of death thing has happend to rooted and stock phones. Leading people much smarter than me to come to the conclusion it is most likely caused by some kind of hardware defect existent in a lot if not all Thunderbolts. If he bricked it trying to flash an hboot from an Incredible or a bad flash because of not taking 30 seconds to check MD5 sums then I would put the blame on him. I'm not trying to condone fraud but if the situation is what I was thinking it might be he shouldn't have to pay because HTC got cheap on some build lots or had some bad quality control. Bootlooping from a bad flash and being able to get into recovery and restore is NOT the same thing I'm talking about. In the situation I'm refering to the ROM and recovery both bootloop. You can still flash an RUU in hboot but even after that the phone still bootloops.
Sent from my HTC Thunderbolt
JBO1018 said:
As far as I have seen the random and sudden boot loop of death thing has happend to rooted and stock phones. Leading people much smarter than me to come to the conclusion it is most likely caused by some kind of hardware defect existent in a lot if not all Thunderbolts. If he bricked it trying to flash an hboot from an Incredible or a bad flash because of not taking 30 seconds to check MD5 sums then I would put the blame on him. I'm not trying to condone fraud but if the situation is what I was thinking it might be he shouldn't have to pay because HTC got cheap on some build lots or had some bad quality control. Bootlooping from a bad flash and being able to get into recovery and restore is NOT the same thing I'm talking about. In the situation I'm refering to the ROM and recovery both bootloop. You can still flash an RUU in hboot but even after that the phone still bootloops.
Sent from my HTC Thunderbolt
Click to expand...
Click to collapse
He could not get into recovery cause he cleared data, can't get there is there is not one. And it didn't seem to me like he tried to flashed CWM from HBoot either.
Sent from my ADR6400L using XDA App
Grnlantern79 said:
He could not get into recovery cause he cleared data, can't get there is there is not one. And it didn't seem to me like he tried to flashed CWM from HBoot either.
If he can't think of a way to fix it send it to me will have it running in a couple of google searches.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Sent from my ADR6400L using XDA App
I tried to get into recovery a few times before doing anything, it would just go black and reboot to the HTC logo. As a last attempt I tried to load a rooted a ruu, it installed but didnt not boot. I have the 1.04 modded hboot so I dont think I can overwrite recovery. Either way, contrary to your beliefs I will not claim insurance on it, although this is a warranty issue, these phones are dropping left and right. I just moved to tmobile this week and my sensation 4g and G2x are supposed to be delivered today.
Thanks for your ideas but I tried to reflash recovery and it installed through hboot but it will just reset before it loads. I still have s-off and my emmc was the sem08g. I am going to plug it in and just let it boot loop all day while I am at work, maybe it will get out, maybe it wont, either way is it wont hurt anything.
My phone battery died last night, so I plugged it in and let it charge for 10 min then when I went to power it on, after the second samsung logo it shuts off and restarts, I boot into recovery and ive tried doing a factory reset and when it tries to format it crashes, and restarts about 5 seconds after saying formatting...
I was running a embryo rom, cant remember which one...
Any help is appreciated. I've looked around and cant seem to find much to help me so far.
Can you do a fresh install over top the existing ROM? Instead of trying to salvage the existing ROM.
Can you mount the USB in recovery?
Heeter
Heeter said:
Can you do a fresh install over top the existing ROM? Instead of trying to salvage the existing ROM.
Can you mount the USB in recovery?
Heeter
Click to expand...
Click to collapse
When I boot into recovery and try to wipe data/factory reset, it sats wiping data.. Formatting.... then 10 seconds later it reboots and goes into a boot loop.
When I try to install zip from sdcard (embryo 3.1 dist.zip) it says
-- Installing: /sdcard/embryo-3.1-dist.zip
Finding update package...
E: Cant mount /sdcard/embryo-3.1-dist.zip (Installation aborted).
Is there a way to wipe data/factory reset other than in CWM? I am running v5.8.4.3
Can you put the phone in download mode? If so, restore to stock from there. Format your SD cards, internal and external, as well, and make sure to wipe x3 so any damaged remnants are swept away.
T.J. Bender said:
Can you put the phone in download mode? If so, restore to stock from there. Format your SD cards, internal and external, as well, and make sure to wipe x3 so any damaged remnants are swept away.
Click to expand...
Click to collapse
When I plugged it into my computer it went to ODIN mode and says downloading...
I am not sure how I got it there, or what to do from this point. Do you have a link to the instructions on how to do that?
D-Duub said:
When I plugged it into my computer it went to ODIN mode and says downloading...
I am not sure how I got it there, or what to do from this point. Do you have a link to the instructions on how to do that?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1652398
BEFORE YOU DO THAT, a few quick notes and thoughts:
1. Don't ever mess around in recovery/download if you don't know what you're doing. If you're not sure how you "got it there" or "what to do from this point," you don't know what you're doing. Read or brick.
2. Looking back at your first post, a couple of thoughts occur to me. One, are you trying to use recovery while plugged in? That can sometimes cause things to mess up, especially if you're plugged in while going into recovery. Wouldn't cause a bootloop though.
3. CWM 5.8.4.3 was a troublemaker, if I recall correctly. Are you on CWM touch, or CWM button-masher? CWM button-masher has a history of doing bad things to Skyrockets.
4. If your phone is not successfully completing the factory reset and you're not sure which ROM you're running, what in God's name made you think flashing a ROM on top of what's there was a good idea?
99.9999999% this is not a ROM problem. Lots of people are using the Embryo family without bootlooping on a battery charge, so I'm inclined to believe it's something else.
Restore to stock and pray, bud. Too many red flags for me to chalk this up to anything other than user error. Sorry.
@D-duub I do hope yiubread the above
Sent from my HTC Incredible S using xda app-developers app
T.J. Bender said:
http://forum.xda-developers.com/showthread.php?t=1652398
BEFORE YOU DO THAT, a few quick notes and thoughts:
1. Don't ever mess around in recovery/download if you don't know what you're doing. If you're not sure how you "got it there" or "what to do from this point," you don't know what you're doing. Read or brick.
2. Looking back at your first post, a couple of thoughts occur to me. One, are you trying to use recovery while plugged in? That can sometimes cause things to mess up, especially if you're plugged in while going into recovery. Wouldn't cause a bootloop though.
3. CWM 5.8.4.3 was a troublemaker, if I recall correctly. Are you on CWM touch, or CWM button-masher? CWM button-masher has a history of doing bad things to Skyrockets.
4. If your phone is not successfully completing the factory reset and you're not sure which ROM you're running, what in God's name made you think flashing a ROM on top of what's there was a good idea?
99.9999999% this is not a ROM problem. Lots of people are using the Embryo family without bootlooping on a battery charge, so I'm inclined to believe it's something else.
Restore to stock and pray, bud. Too many red flags for me to chalk this up to anything other than user error. Sorry.
Click to expand...
Click to collapse
Not using recovery while plugged in.
Not using CWM touch.
I couldn't recall the ROM when I wrote the OP, its stated in one of my replies. I tried re-flashing the rom that I had on my SD card (the one I had when everything went wrong).
Not sure how it could be user error when I have not messed with anything before my problem and since then all I have tried doing is reinstalling the rom, and when that didn't work I tried wipe data\factory reset.
So far I haven't done anything that was not recommended.
I am downloading the stock firmware now and I will use ODIN to flash and let you all know how it goes.
Thanks for the help so far.
Fixed!
I didn't lose anything, just my rom. Sweet.
I expected to lose my stuff, thats great news.
Thank you very much.
Now to reply to the million messages I got while my phone was down...
When in doubt, restore to stock.
Seriously though, I'm really glad you brought it back. If you're going to flash/mod/whatever, please, for your own sake, read through the stickies here. It'll take you a couple hours or so to do, and it'll save you from turning your phone into a paperweight later. And get rid of that non-touch CWM lol! sk8rwitskiis does a great version of CWM Touch for our Skyrockets, and TWRP is an excellent recovery as well.
T.J. Bender said:
When in doubt, restore to stock.
Seriously though, I'm really glad you brought it back. If you're going to flash/mod/whatever, please, for your own sake, read through the stickies here. It'll take you a couple hours or so to do, and it'll save you from turning your phone into a paperweight later. And get rid of that non-touch CWM lol! sk8rwitskiis does a great version of CWM Touch for our Skyrockets, and TWRP is an excellent recovery as well.
Click to expand...
Click to collapse
Will do. Thanks again.
Does anyone know any way to get the One S back to as close to stock as possible? I'm returning my phone to T-mobile for service and I can't get 'TAMPERED' to disappear from HBoot without the RUU. Also, now having an issue with every time I turn on the phone it has the developer text on the splash screen even though it isn't entering hboot or recovery.
Does anyone have any ideas on either issue? The only threads I can find are people with pretty much the same issue and no solution or pre 2.35 updates.
fbihawk said:
Does anyone know any way to get the One S back to as close to stock as possible? I'm returning my phone to T-mobile for service and I can't get 'TAMPERED' to disappear from HBoot without the RUU. Also, now having an issue with every time I turn on the phone it has the developer text on the splash screen even though it isn't entering hboot or recovery.
Does anyone have any ideas on either issue? The only threads I can find are people with pretty much the same issue and no solution or pre 2.35 updates.
Click to expand...
Click to collapse
Sorry, I should also mention I've loaded a nandroid backup of the stock rom without root and attempted to flash the "stock" recovery. I'm not sure about the recovery because I don't believe it came from the 2.35 software and that's when I started to have issues with the splash screen. Loaded TWRP back on and still same issue.
Also, was having issues after with the device not loading to anything but bootloader until I re-unlocked it then it started fine.
I don't think you're gonna be able to do anything without ruu
mbernusg said:
I don't think you're gonna be able to do anything without ruu
Click to expand...
Click to collapse
That's kind of what I was afraid of. Any ideas on when that could be? Or if HTC would have that file?
from personal experience, dont worry about it, t-mobile wont care.
I had a sidekick that I bricked, and there was no way to even power it on, went to tmobile with custom sw and recovery...
also I had a sensation that i sent back with custom rom and a custom recovery because the phone would not get power, never heard anything about.
I read somewhere online that tmobile returns the phones to stock even before they check them.
if you send it back as is, you SHOULD be fine... ive done it twice.
jahnbodah said:
from personal experience, dont worry about it, t-mobile wont care.
I had a sidekick that I bricked, and there was no way to even power it on, went to tmobile with customer sw and recovery...
also I had a sensation that i sent back with custom rom and a custom recovery because the phone would not get power, never heard anything about.
I read somewhere online that tmobile returns the phones to stock even before they check them.
if you send it back as is, you SHOULD be fine... ive done it twice.
Click to expand...
Click to collapse
That definitely relieves a little stress. Thanks!
fbihawk said:
Sorry, I should also mention I've loaded a nandroid backup of the stock rom without root and attempted to flash the "stock" recovery. I'm not sure about the recovery because I don't believe it came from the 2.35 software and that's when I started to have issues with the splash screen. Loaded TWRP back on and still same issue.
Also, was having issues after with the device not loading to anything but bootloader until I re-unlocked it then it started fine.
Click to expand...
Click to collapse
Could you provide a link for the stock nandroid? It would be much appreciated! I am on CM 10 but can't get back to stock. The stock nandroid I downloaded the other day fails upon restoring everytime.
jaker.the.skater said:
Could you provide a link for the stock nandroid? It would be much appreciated! I am on CM 10 but can't get back to stock. The stock nandroid I downloaded the other day fails upon restoring everytime.
Click to expand...
Click to collapse
I just used the one in the dev section.