Related
Signed up for XDA because I got problems, and you guys seems to know everything when I need to use my googl-fu to solve a problem.
Have lurked for hours trying to figure this out. Nothing solves it.
Phone specs: Phone is babied, never dropped etc. Evo 4g on sprint, rooted unrevoked3 method, was running CM7 nightly95.
Have been running this for several days no issue, (since nightly95 came out.)
Was running a CM7 stable build before this. No issues.
And then the problem: Was just using my phone like normal at work it decided it wanted to reboot on me, once, restarts fine, and about an hour later reboots into a boot loop. It was on a charge cable to wall outlet, not pc when this happened, if that matters.
From the boot loop, just starts, vibrates, shows the htc evo screen maybe 10 seconds and reboots.
I can get into Hboot, (power + vol down) but can not get into recovery. if it's selected the boot looping starts again.
I have tried clearing storage, and flashing a couple PC36IMG.ZIP Since it seems to fix other peoples. Since the most I can figure out is putting the SD card into the computer and try loading files from Hboot.
Last one being this: http://forum.xda-developers.com/showthread.php?t=791019
Still boot looping, no recovery.
Any help is appreciated. But I am noob when it comes to command line adb stuff. Just so you know.
what PC36IMG are you trying to flash exactly?
try this one, its amon ra 2.3, its the one i have as a backup in case mine foks up, just take amonra out of the name so its only
PC36IMG.zip, then put in the root of your sd card, turn on phone while pressing volume down, to go into bootloader let the phone recognize it and select yes when asked to update, if thats gets your recovery up try wiping and restoring a backup
If all else fails, try the attached doc.
First, boot into the bootloader, look at the top of the screen and see if it still displays "S-OFF". If it does not, you need to re-root your device. If it displays "S-ON" then If you have a card reader, connect it to your PC or Mac and copy the contents of the SD card to your computer. Afterwards, re-format the card. Now copy a freshly downloaded rom and a freshly downloaded copy of the PC36IMG.zip file for amon-RA recovery version 2.3 to the root of your SD card (not in any folder). Re-insert the card in your EVO and boot to the bootloader. The PC36IMG.zip file *should* be automatically detected and you *should* be prompted to install it. Follow the prompts to install. Installation will take approximately 10 seconds. Afterwards, boot into your new recovery. Go to the wipe menu and wipe EVERYTHING in it EXCEPT the SD card. After that, flash the rom. Be patient during the initial boot process. You *should* be good to go afterwards.
posting & replying via the XDA Premium app.
HipKat said:
If all else fails, try the attached doc.
Click to expand...
Click to collapse
Tried this a bit ago.
Now it doesn't loop. But it's not any better.
It just boots, htc evo for a few seconds, and then vibrates approx 5 times and screen goes black and the top led flashes green.
Anybody else think this sounds like the bootloop of death? If so, there's no known fix. You can run the PC36IMG, but if that's what it is, you'll never get recovery or any rom to boot up.
I hope I'm wrong, though.
(from... Evo/MIUI/Tapatalk)
this sounds just like what happened to my phone. After spending hours on the forums and PM'ing back with a few people, I diagnosed it as the bootloop of death. Which sounds like exactly your going through....
no fix unfortunately...if your s on you can go back to sprint and get a brand new one. If not (like me) smash it pay the $100 deductible and get a refurb. Sucks I know.
For a more in depth thread search "boot loop + no recovery".
If I understand correctly, it's a problem with a partition size and was common with a certain Hardware version (0002?)
The good ole bootloop of death, that I fear so deeply. I hope this never happens to me. I'm sorry for your luck, but it sounds like plainjane is right. I agree, you got the bootloop of death, and most likely won't recover from it. Do you you have insurance ?
Sent from my PC36100 using XDA App
k2buckley said:
The good ole bootloop of death, that I fear so deeply. I hope this never happens to me.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
My fear, too. Every time I boot up in the morning, I hold my breath a little til the Evo screen goes off and the boot.ani starts...
Well, After HipKat first suggestion I can get to s-on. I may try it again with a different RUU but I think it's dead too.
So, since it will be S-on, hopefully there is a new phone in my future, without any money out of pocket.
Thanks for the help guys. I'll let you know if anything fixes it, or what sprint says.
HipKat said:
My fear, too. Every time I boot up in the morning, I hold my breath a little til the Evo screen goes off and the boot.ani starts...
Click to expand...
Click to collapse
From what I remember reading about a month ago, when this seemed to be happening a lot, was that it was random.
Didn't start when you were trying to boot up, just suddenly, randomly, terrifyingly, and like death in the night....power off, and never to fully boot again. Just typing about it now kinda scares me like a hex. I hope to finish typing this sentance.
@ OP, really sorry about your luck, man. We all feel you.
Sent from my PC36100 using XDA Premium App
Thats crazy, the same exact thing happened to my brother running CM7 lke a month a go.. is this limited to just AOSP ROMs? I know there's always the potential of bricking your phone flashing, but from what I've been reading it seems its happening to lots of people on AOSP ROMs
fergie716 said:
Thats crazy, the same exact thing happened to my brother running CM7 lke a month a go.. is this limited to just AOSP ROMs? I know there's always the potential of bricking your phone flashing, but from what I've been reading it seems its happening to lots of people on AOSP ROMs
Click to expand...
Click to collapse
No, it's not limited to AOSP ROMs, but it does seem that most of the cases were people running CM7 and/or Clockwork Mod. I know there was an argument that it's just that there are so many people running CM that it just seems like CM was the culprit, but it was odd to me, anyhow, how overwhelmingly I saw that it was happening to people running that mod
HipKat said:
No, it's not limited to AOSP ROMs, but it does seem that most of the cases were people running CM7 and/or Clockwork Mod. I know there was an argument that it's just that there are so many people running CM that it just seems like CM was the culprit, but it was odd to me, anyhow, how overwhelmingly I saw that it was happening to people running that mod
Click to expand...
Click to collapse
Yea I was reading this happened a few days ago to a guy who was on Decks 2.3.4.. IDK I told my brother to just flash a radio and pull the battery while flashing to try and get a replacement.. But the whole thing freaked me out lol.. Feel bad cuz it could happen to anyone I suppose
Your lucky to get S-ON, I only read about one other person able to get S ON after bootlooping.....take it to the Sprint Store, they should give you a new one on the spot if they have stock, if not they order one overnight. Could have been way worse...
Right now it says s-off again. But acts likes it's on, can't erase anything through fastboot/adb.
Going to try to repeat the RUU install a few times to see if I can get it back to s-on then take it in.
I was one of the first 3 or so people to report about this on the forum - it happened to me over 4 months ago. Anyways, if you flash a PC36IMG-eng and pull the battery at exactly the right time, while the radio is updating your phone will completely brick - it won't even turn on. Then you can take your phone in and just tell sprint it wont turn on. Note, it took me over 20 battery pulls before it finally wouldn't turn on, but its your best option if you can't get S-ON.
Wow that's crazy. I've never heard of the bootloop of death.
Sent from my PC36100 using Tapatalk
Do a search for Boot loop white screen and you'll find a ton of threads/posts about it
Alright. For starters, xda has been VERY VERY helpful to me over the past few months and I thank everyone who has ever contributed to a question or a discussion I have read. That being said, this is my first post. I watched the newb video, read many forums (both xda and others), google searched, read some more threads, kept reading threads, tried some methods described in some threads, bookmarked some interesting threads for if my phone ever works again, and read some more threads.
I am not saying the answer is not already out there, I am saying I have reached my resourcefulness cap.
Anyway, to the root of the problem: I'm not entirely new to rooting, and am comfortable using recovery and hboot to flash roms. I also had a nandroid backup! for SOME SILLY reason, while in my clockworkmod recovery this morning (maybe slightly due to being half asleep which is why I now recommend being fully awake before entering hboot or recovery or rom manager....etc) I formatted the system on my phone. I THINK.
My phone will now load up to display the bootloader, and go into recovery mode, and flash roms, but when I flash a rom, nothing changes. If I boot my phone up, it will show a notification bar at the top like usual, a stock wallpaper, and that is IT! it will show a message notification and missed call icon since I have them, but the touch screen will not work. The rosie buttons at the bottom do not show up (i.e. phone button or all aps button) no apps appear, no clocks except for in the notification bar... hardkeys have no effect (home button search button menu or back) and volume keys will not work. The lock button will only lock and unlock the screen, not power off or reboot or anything. If plugged in at this point, it is charger only.
So, I can take the micro sd card out and put files on it from my PC via a microsd-usb converter thing...
I have tried putting new roms on the sd and flashing them from recovery, no effect. Tried the RUU_Supersonic_1.32.651.1_Radio_1.39.00.04.26_release_171253.exe program, it always says that my phone has below 30% battery and will not continue (this is not the case as I have two batteries both have been fully charged because the phone will still charge them...)
And I have tried putting PC36IMG.zip files on my sd card to no avail.
I am thinking that the system was wiped because it seems like there is no boot image on the phones internal memory itself. I am currently looking for a way to place a boot image on the sd card to possibly flash it or some sort of update.zip so that my bootloader will ask me to update upon reading it.
Sorry for the long post, and ask any questions I will answer as best I can.
I am posting preemptively to the boot image adventure so that if it does not work, maybe I can have some help finding a solution by then.
I was going to take my evo to the sprint store since it is under warranty but if they go into recovery they will see clockworkmod recovery.
Thanks to all for any form of guidance!
I did just notice in my Bootloader menu (HBOOT-2.10.0001) that it says Supersonice evt2-3 **** S-ON
I don't know how because I thought it was a requirement that it says S-OFF to be rooted and flash roms, but I have definitely flashed roms before and gained su access to applications and such. BUT since it says S-ON would it then be covered by the warranty if it is not rooted?
Thanks again.
I you want to flash a boot image, you can take the boot.img from an RUU for the firmware you are, place it in your adb tools folder, then flash it using the commands:
fastboot flash boot boot.img
fastboot reboot
I'm not sure how to identify what firmware I am. Unless your talking about the Hboot version? and also, I can't place anything in any folder except onto my sd card. I have no access other than that to the phone. On the sd card there are no files except for what I put on there.
...aaand not to mention I don't know what adb is exactly...
Does your phone still go to clockwork when you go to recovery?
Am going to try it right now, but will that work if I cannot tell my phone to allow usb debugging? i remember something about unrevoked needing that to root the phone in the first place. will update as soon as I try it. May not have time right now as I have to leave in about 15 mins. If no reply by 9:45, then I will be back online tomorrow morning. and thanks!
Timeconsumer10 said:
Am going to try it right now, but will that work if I cannot tell my phone to allow usb debugging? i remember something about unrevoked needing that to root the phone in the first place. will update as soon as I try it. May not have time right now as I have to leave in about 15 mins. If no reply by 9:45, then I will be back online tomorrow morning. and thanks!
Click to expand...
Click to collapse
Welcome, but yes, you do need to have had usb debugging enabled, so we'll see how that goes.
SUPER THANKS! S-OFF tool worked perfectly just flashed a rom and now so far so good. Will post tomorrow to let you know if everything works well. So much appreciated =) I would thanks a million times if i could don't know what to do without my evo.
Timeconsumer10 said:
SUPER THANKS! S-OFF tool worked perfectly just flashed a rom and now so far so good. Will post tomorrow to let you know if everything works well. So much appreciated =) I would thanks a million times if i could don't know what to do without my evo.
Click to expand...
Click to collapse
Lol, it'd take you 200,000 days since you can only thank 5 times a day Though glad you're rooted now.
shortydoggg said:
Does your phone still go to clockwork when you go to recovery?
Click to expand...
Click to collapse
Yes it still goes to clockwork because its rooted.. now my screen legitimately does not work in certain areas of the screen (not responding to touch) so I'm going to try and get it stock stock stock unrooted and go for warranty replacement. Any ideas please let me know. Currently trying RUU Supersonic...
So, I got an ERROR [110] message from the RUU package its a file open error... :/ now i dont know what is up. Says I need a complete RUU package. Looking for another one or another option now.
If i boot phone normally now it just goes to a black screen with "htc" in the middle and "!" in a triangle in all four corners. Can't do anything from that screen.
If I boot into bootloader once where it says SHIP S-OFF at the top and instead of recovery and all those options it just says RUU but you cant do anything there... :/ I now, however cannot even get to the bootloader screen.
Could they tell it is rooted?
Maybe I could say I finally decided to do sprints OTA update that I've been denying for a while and this is the result.
Anyone agree disagree?
COCLUSION!
So. Since it has just the HTC logo and four error icons one in each corner... I took it into a sprint repair store. It would not boot into bootloader as a hard reset, so the guys at the store were stumped. They had actually never seen this before =). They asked me if I rooted it and all so I just played dumb. I told em I didn't know what that really was. They kinna explained it and I told em I didn't even have a computer (not a lie actually I sold mine and now use my dads or gfs lol). The logo on the screen was an oooold htc logo from like hero or so. So they just put it in the system as a wont even turn on type of thing and gave me a new phone since I was under warranty =) gonna see if I can live without root juuust for a little bit because work and school are gonna keep me busy for a while. I am certain to return though!
Can't wait to see what the devs can do by then!
Thanks to all for the help!
My daughters HTC Desire (not rooted) seems to have given up.
When I boot it just rendering the "Quietly brilliant" takes around 10-15 seconds. And then after several minutes the boot up sound is played. Then a while later the battery is displayed and the "Connect your charger" text. Even though the charger is connected. I cannot swipe down to unlock the phone as it just sits there. Eventually rebooting.
I have managed to get into recovery but trying to do a factory reset there has left the phone displaying the blue/purple recovery screen for two whole days without doing anything. Just clearing the cache through recovery took around four hours.
Has anyone seen anything similar? Or can the phone just as well be thrown in the bin?
I worry that this could be hardware issue if the battery doesn't seem to know it's charging and it's that slow without rooting.
Last resort would be to try to flash 2.3.3. RUU as PB99IMG.zip
eddiehk6 said:
Last resort would be to try to flash 2.3.3. RUU as PB99IMG.zip
Click to expand...
Click to collapse
I wouldn't even know how to flash it. Is it from recovery? Using adb sideload or something? Do you know the adb command of the top of your head? Also I would assume this requires HTC Desire drivers installed. If this can be done without the phone having to identify itself then maybe there's a chance
kroogar said:
I wouldn't even know how to flash it. Is it from recovery? Using adb sideload or something? Do you know the adb command of the top of your head? Also I would assume this requires HTC Desire drivers installed. If this can be done without the phone having to identify itself then maybe there's a chance
Click to expand...
Click to collapse
The link that you have been provided with has installation instructions, and can answer all of your questions.
Sent using xda-developers app
Chromium_ said:
The link that you have been provided with has installation instructions, and can answer all of your questions.
Click to expand...
Click to collapse
Sorry My bad. I'm at work so I didn't check the link. I just assumed it was a direct link to a zip file
eddiehk6 said:
Last resort would be to try to flash 2.3.3. RUU as PB99IMG.zip
Click to expand...
Click to collapse
Tried this and it went okay... sort of... The actual update went fine. Took about a minute or two. There has not been any problems with booting into bootloader or recovery. The only think it complained about was that it was unable to downgrade the bootloader and skipped that step.
But other than that it behaves as it did before the update. After a while I get the "quietly brilliant" (that actually renders in normal speed now) but after that (and a five minute wait) I'm stuck with the "no service" screen. After an additional couple of minutes I get the "Connect your charger" and after that it's all black
I guess I might as well toss it but I'm intrigued by the fact that flashing the zip is done in what I assume is "normal" speed. Everything else is dead slow...
kroogar said:
Tried this and it went okay... sort of... The actual update went fine. Took about a minute or two. There has not been any problems with booting into bootloader or recovery. The only think it complained about was that it was unable to downgrade the bootloader and skipped that step.
But other than that it behaves as it did before the update. After a while I get the "quietly brilliant" (that actually renders in normal speed now) but after that (and a five minute wait) I'm stuck with the "no service" screen. After an additional couple of minutes I get the "Connect your charger" and after that it's all black
I guess I might as well toss it but I'm intrigued by the fact that flashing the zip is done in what I assume is "normal" speed. Everything else is dead slow...
Click to expand...
Click to collapse
The RUU should be 'clean'
Therefore if it's still playing up, as suspected sounds like hardware fault . On such an old phone, personally probably not worth the hassle anymore
now, i have no idea if this is the actual definition of "soft bricked"... so ill just tell you my story.
ok... so a quick history... phone was never rooted... ota update in november caused the phone to reboot every time the screen went off. had to install "wakelock app" to make it usable... update in december caused the phone to not be able to turn on. im not sure what happened. started the update, let the phone sit for a little while... when i looked at it again... nothing. it was just dead. no buttons would turn it on. had to get a new phone. note 4 was a private purchase, so no warranty options.
after leaving the battery out for a week, it would turn on but get stuck on verizon screen, get real hot, and every 30 seconds, blip a vibrate and a screen flash.... so... i tried clearing cache, tried a FDR... nothing. so i basically tried what is on this page:
https://forum.xda-developers.com/no...mware-firmware-kernel-modem-recovery-t2942937
with the newest firmware through odin... i unzipped the file, put the phone in download mode, connected it, waited for blue box, browsed to tar.md5 in "ap" box, and hit start when ready. got an error, after a while, i pulled the battery, and now when i turn on in download mode it says "your device didnt update successfully. use the verizon software repair assistant on a computer to repair your device and complete the update"
kies does not recognize my phone... i can't find a software repair assistant. if i try to run odin again, it just gives me "complete(write) operation failed"
hoping i can figure out how to salvage this thing. not super hip to phone software. ive managed to root numerous phones in the past. this is the first time ive had an issue, and its with the first phone i didnt root.
thanks in advance. sorry if this is totally newb level stuff. i just really need help, and get lost real quickly trying to do my own research... but trust me, ive tried.
idiggplants said:
now, i have no idea if this is the actual definition of "soft bricked"... so ill just tell you my story.
ok... so a quick history... phone was never rooted... ota update in november caused the phone to reboot every time the screen went off. had to install "wakelock app" to make it usable... update in december caused the phone to not be able to turn on. im not sure what happened. started the update, let the phone sit for a little while... when i looked at it again... nothing. it was just dead. no buttons would turn it on. had to get a new phone. note 4 was a private purchase, so no warranty options.
after leaving the battery out for a week, it would turn on but get stuck on verizon screen, get real hot, and every 30 seconds, blip a vibrate and a screen flash.... so... i tried clearing cache, tried a FDR... nothing. so i basically tried what is on this page:
https://forum.xda-developers.com/no...mware-firmware-kernel-modem-recovery-t2942937
with the newest firmware through odin... i unzipped the file, put the phone in download mode, connected it, waited for blue box, browsed to tar.md5 in "ap" box, and hit start when ready. got an error, after a while, i pulled the battery, and now when i turn on in download mode it says "your device didnt update successfully. use the verizon software repair assistant on a computer to repair your device and complete the update"
kies does not recognize my phone... i can't find a software repair assistant. if i try to run odin again, it just gives me "complete(write) operation failed"
hoping i can figure out how to salvage this thing. not super hip to phone software. ive managed to root numerous phones in the past. this is the first time ive had an issue, and its with the first phone i didnt root.
thanks in advance. sorry if this is totally newb level stuff. i just really need help, and get lost real quickly trying to do my own research... but trust me, ive tried.
Click to expand...
Click to collapse
do a battery pull to shut off your phone then boot into download mode like normal unzip and flash this ( https://www.androidfilehost.com/?fid=24588232905720219 ) in the ap slot.
do a battery pull to shut off your phone then boot into download mode like normal unzip and flash this , link was here, in the ap slot.
OP, did you try this process listed above and did it fix your problem or did you something else? Thank you.
SPIRITJCC98 said:
do a battery pull to shut off your phone then boot into download mode like normal unzip and flash this , link was here, in the ap slot.
OP, did you try this process listed above and did it fix your problem or did you something else? Thank you.
Click to expand...
Click to collapse
nope, didnt work. was pretty pissed at the time. i had to give up and get a lgv20.
Hello!
I purchased a Galaxy S6 two days ago and have yet to really use it...
I wanted to have a fully fresh phone so i flashed the latest firmware available to me (USA, Sprint, sm-g920p, zerofltespr, QB1)
Everything flashed as normal (not my first S6, I'm familiar with ODIN) but upon booting up the first time it goes to a blue screen that says initializing update.. then the progress bar goes to 32% and then says erasing.. then it reboots and i get to optimizing apps (starts at some random number 8 of 33, 13of 33, 12 of 33, etc.) and then reboots and goes back to optimizing apps again... it's maddening!!!
I've tried at least 5 different firmwares, all with the same result. Always to 32% then bootloop on optimizing apps
I've tried using the PIT file for my phone along with flashing the firmwares, same result
When i try to enter recovery to wipe cache or factory reset, i get the blue screen that says initializing update then i get some yellow exclamtion warning for a second and i get to recovery... i wipe cache, reboot... same boot loop result
Back to recovery, factory reset, reboot... same boot loop result trying to optimize apps.
I've tried adb sideloading a couple different ROMS but those just bootloop at the Galaxy S6 logo splash screen.
I've run out of ideas for what to do to fix this.. every great once in awhile ill get to the welcome screen and itll get to Setting up your device for first time use... then itll just reboot and go right back to that screen... i havent been passed that once...
Please any ideas would really be great. Thanks
Saafir said:
Let the phone battery run dead. Then charge 15% and boot it. Problem will likely have fixed itself. [Not joking]
Click to expand...
Click to collapse
Do what @Saafir says, it usually works.
Saafir said:
Let the phone battery run dead. Then charge 15% and boot it. Problem will likely have fixed itself. [Not joking]
Click to expand...
Click to collapse
thanks so much for your response... Just got to work for my 12 hour shift... ill let it boot loop til it dies... im so curious to see if thats what will work..
thanks again!
Edit: just noticed your profile.... GO BLUE!!!!!!!!! (huge Michigan fan here) Aint that right, Koop?
blacksantron said:
thanks so much for your response... Just got to work for my 12 hour shift... ill let it boot loop til it dies... im so curious to see if thats what will work..
thanks again!
Edit: just noticed your profile.... GO BLUE!!!!!!!!! (huge Michigan fan here) Aint that right, Koop?
Click to expand...
Click to collapse
If you get this going, please send me (or post here via file attach) the file: /proc/last_kmsg -- you need to be rooted to get that so hopefully you are. To get this right, you need to copy that file to /sdcard (or somewhere there) and only on the first successful boot.
I want to see what is complaining so I can (hopefully) write a fix for future sufferers that won't require the reboot til dead game.
Sent from my iPad using Tapatalk
tdhite said:
If you get this going, please send me (or post here via file attach) the file: /proc/last_kmsg -- you need to be rooted to get that so hopefully you are. To get this right, you need to copy that file to /sdcard (or somewhere there) and only on the first successful boot.
I want to see what is complaining so I can (hopefully) write a fix for future sufferers that won't require the reboot til dead game.
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
Right on, unfortunately i wont be rooted since Im bootlooping right after flashing stock firmware..
I cant believe that worked!!!!!!!!!!!!!!!!
If you were anywhere near me id buy ya a beer... i swear i tried everything for two days... so many firmwares i downloaded... oh my word...
thanks so much1
blacksantron said:
I cant believe that worked!!!!!!!!!!!!!!!!
If you were anywhere near me id buy ya a beer... i swear i tried everything for two days... so many firmwares i downloaded... oh my word...
thanks so much1
Click to expand...
Click to collapse
If you ever need, I try to keep the latest firmware posted here: https://forum.xda-developers.com/sp...uide-links-files-update-root-restore-t3366862
Hey guys I'm in need of some help, I've flashed my s6 sm-g920p phone about 7 times and it still won't boot up it gets to the lte screen just before startup and keeps rebooting what might be the problem ? Might it be the battery is not good ?