Related
Ok so my GF's incredible was working just fine, had been with the same rom for a month with no problems.
One hour ago, it just rebooted out of nowhere. Now, it wont boot to rom, it boots to hboot, try recovery and it shows CWM for 1 second and reboots again, tried factory reset, or clear storage, and it reboots and the same as CWM, it shows 1 second and reboots.
It seems like if everytime it loads the kernel, any kernel, recovery or rom one it reboots.
Any thoughts? Oh, also, I flashed the "build-3.26.605.1-release-152016-baseband-2.15.00.07.28-hboot-0.92.0000_PB31IMG.zip" file it flashed fine, rebooted and again with the bootloop. It just shows the white Incredible screen and reboots!
Any suggestions are appriciated
pmcnano said:
Ok so my GF's incredible was working just fine, had been with the same rom for a month with no problems.
One hour ago, it just rebooted out of nowhere. Now, it wont boot to rom, it boots to hboot, try recovery and it shows CWM for 1 second and reboots again, tried factory reset, or clear storage, and it reboots and the same as CWM, it shows 1 second and reboots.
It seems like if everytime it loads the kernel, any kernel, recovery or rom one it reboots.
Any thoughts? Oh, also, I flashed the "build-3.26.605.1-release-152016-baseband-2.15.00.07.28-hboot-0.92.0000_PB31IMG.zip" file it flashed fine, rebooted and again with the bootloop. It just shows the white Incredible screen and reboots!
Any suggestions are appriciated
Click to expand...
Click to collapse
when you say it shows the white screen and it reboots..... what do you mean be the white splash screen always shows up first then it boots.... are you saying it bootloops [which means it starts the whole process over again]? and im asuming you flashed an RUU Through hboot..... how long did you let it try and boot because it takes awhile after flashing back to stock...... give me a liittl more info and i might be able to help.....
Yea the white splash screen that always shows up. IT reboots and it goes to the white splash screen again, and again...In fact wait me a second i will take a video of everything! But, yea after flashing the RUU it does exactly the same, in fact I just flashed the RUU again via fastboot and the same. I will record it anyway, one second.
Lol, and on my evo Qik is force closing, nice! Well, Sorry couldnt record but yea,
normalboot-->white inc screen-->black screen--->reboot
voldownboot---hboot--->recovery--->recovery screen --1sec-->reboot
I'd try to RUU back to stock and re-root.
Sent from my ADR6300 using XDA Premium App
like I said, done the RUU didnt work. !
pmcnano said:
Yea the white splash screen that always shows up. IT reboots and it goes to the white splash screen again, and again...In fact wait me a second i will take a video of everything! But, yea after flashing the RUU it does exactly the same, in fact I just flashed the RUU again via fastboot and the same. I will record it anyway, one second.
Lol, and on my evo Qik is force closing, nice! Well, Sorry couldnt record but yea,
normalboot-->white inc screen-->black screen--->reboot
voldownboot---hboot--->recovery--->recovery screen --1sec-->reboot
Click to expand...
Click to collapse
are you positive the ruu flashed..... when it loaded up did it ask you if you want to update vol + and then it flashes stuff for about 5 mins until it finialy says its done and asks you if you want to reboot....
yep! I did, I even flashed it via fastboot again, same thing happens :S
pmcnano said:
yep! I did, I even flashed it via fastboot again, same thing happens :S
Click to expand...
Click to collapse
Bro it sounds like hardware problem to me.... the only other thing i can think of is to try and get into recovery with adb and try to wipe do a wipe and see what happens.... but if that dont work doug piston is the best around at getting the incredible restored ill give you link to his site if you cant get him tonight he'll answer in the morning
http://dougpiston.com/
you can also talk to him at Droid Forums good luck let me know what it was please and hit that thanks button if i helped
haha yes you did, I really think its a HW problem too
Hey bro let me know what you figure out so I can help people in the future
Sent from my Incredible using XDA App
Ok, finally had a chance to actually read your thread. Looks like you've tried just about everything I suggested via twitter already.
Oddly enough I had someone from this forum contact me about a similar situation about a week ago. If I remember correctly we tried everything and came to the same reboot. He fixed it though we weren't sure on the full solution show I'll discribe what he did and you can give it a shot.
Flash the RUU through Hboot one more time, once it is complete it will ask if you would like to reboot, select no. Once it gets back into hboot pull the battery wait a minute and re-insert the battery leave the device plugged in and powered off for about an hour. Come back and try to reboot.
Like I said I have no clue on how this method recovered the device but it did. It makes no logical sense to me but its worth a shot.
Thanks for all your help doug, Will try in a sec, was playing soccer!
Will let you know from twitter
doug piston said:
Ok, finally had a chance to actually read your thread. Looks like you've tried just about everything I suggested via twitter already.
Oddly enough I had someone from this forum contact me about a similar situation about a week ago. If I remember correctly we tried everything and came to the same reboot. He fixed it though we weren't sure on the full solution show I'll discribe what he did and you can give it a shot.
Flash the RUU through Hboot one more time, once it is complete it will ask if you would like to reboot, select no. Once it gets back into hboot pull the battery wait a minute and re-insert the battery leave the device plugged in and powered off for about an hour. Come back and try to reboot.
Like I said I have no clue on how this method recovered the device but it did. It makes no logical sense to me but its worth a shot.
Click to expand...
Click to collapse
Stuck in a similiar situation. I tried the above instruction and the device booted. I still do not have a working recovery .Tried to root several times but my device will only boot cleanly once and I have to pull the battery and wait atleast ten minutes but nothing works where can I find instructions on wiping thru adb
I think that the nand is ****ed up or i dont know D: mine didnt boot
Hi Guys, Idon't post too often as you can see, but I have had a great time rooting my Evo and learning from all the awesome members here. I do my research, and until now I have not run across a problem I could not fix on my own.
I am running CM7 nightly 26, and out of nowhere today, my phone rebooted and proceeded to get stuck in a boot loop. I am not surprised by that kind of thing at this point, but for the first time ever, I was not able to boot into recovery. If I select that option from the boot loader, I just get the white Evo 4G screen and it proceeds to boot loop.
Ok, I thought, maybe my recovery was corrupted somehow, so I pull the SD card and put Amon Ra 2.3 in the root directory and named it PC36IMG.zip and flashed it. No good. I still can't get into recovery.
I also tried downloading the stock (rooted) sprint ROM, putting on the root of my SD card and naming it PC36IMG.zip. After the bootloader detects it and the progress bar finishes, it says "Parsing PC36IMG.zip", and then it just takes me back to the bootloader main menu without an option to flash anything.
Also, is there a way to get S-ON back (with my only access being to the bootloader) in the event that I have to take it in? The alternative would be to drown it or smash it (as a last resort)
Any ideas? Thanks very much in advance for any help!
Westibone said:
Hi Guys, Idon't post too often as you can see, but I have had a great time rooting my Evo and learning from all the awesome members here. I do my research, and until now I have not run across a problem I could not fix on my own.
I am running CM7 nightly 26, and out of nowhere today, my phone rebooted and proceeded to get stuck in a boot loop. I am not surprised by that kind of thing at this point, but for the first time ever, I was not able to boot into recovery. If I select that option from the boot loader, I just get the white Evo 4G screen and it proceeds to boot loop.
Ok, I thought, maybe my recovery was corrupted somehow, so I pull the SD card and put Amon Ra 2.3 in the root directory and named it PC36IMG.zip and flashed it. No good. I still can't get into recovery.
I also tried downloading the stock (rooted) sprint ROM, putting on the root of my SD card and naming it PC36IMG.zip. After the bootloader detects it and the progress bar finishes, it says "Parsing PC36IMG.zip", and then it just takes me back to the bootloader main menu without an option to flash anything.
Also, is there a way to get S-ON back (with my only access being to the bootloader) in the event that I have to take it in? The alternative would be to drown it or smash it (as a last resort)
Any ideas? Thanks very much in advance for any help!
Click to expand...
Click to collapse
Many of us are racking our brains trying to figure out what is causing this situation. Everyone who are experiencing this were using CM7, like you, and it happened to of nowhere and for no known reason. I don't think anyone has figured out a workaround, but I could be wrong. I haven't ready through the forums today regarding this issue. Just know that you are not alone, my friend....
Well, it doesn't look too hopeful from what I have seen so far, but thanks for the support. It's good to know that I am not alone.
If you can still access the bootloader, you should still be able to run an RUU through fastboot.
It happened to me, I was one of the first on the forum it happened to, in January. Was never able to fix it, you could spend a loonnngggg time, and get no results. If you search for my threads you can see the ones I started about the subject.
Long story short, I was never able to fix the problem or get S-On. However by doing a battery pull while flashing a rom with a different radio, during the radio installation, I bricked my phone to the point that it wouldn't even turn on. So thats basically your only way out that I know of. You'll have to perform the battery pull upwards 20 times probably before you get the phone to fully brick.
I'm on CM7 nightlies. What are the HW specs of those having these problems? I thought it was due to CWM but there have been some on RA experiencing this too. Just wondering if this is more specific to the newer HW builds/hboots or occurs with all phones.
My Evo is hardware version 003 for what it's worth.
Westibone said:
My Evo is hardware version 003 for what it's worth.
Click to expand...
Click to collapse
When you select recovery, what happens?
I had same issue in Jan after flashing miui.
tried the suggestions on this thread..but nothing worked:
http://androidforums.com/evo-4g-support-troubleshooting/267018-struck-boot-loop.html
Had to replace my phone...that seems to be the only way out of this.
This is the reason I have stayed away from CM for so long. I keep seeing these horror stories about bootlooping, etc. I know its awesome when its running, but when it comes to the point where bricking your phone on purpose is a good thing, something is wrong For those that it has happened to above, did you get your new one and go back to CM (or any other AOSP rom)?
teh roxxorz said:
When you select recovery, what happens?
Click to expand...
Click to collapse
When I select recovery, it just goes back to the white Evo 4G screen and proceeds to boot loop. Over and over again
My God, another one. It's weird these seem to be happening more and more...
Westibone said:
When I select recovery, it just goes back to the white Evo 4G screen and proceeds to boot loop. Over and over again
Click to expand...
Click to collapse
http://dl.dropbox.com/u/19699565/3.70 RUU Zip.zip Rename it to PC36IMg. Its 3.70 ruu, flash it in the bootloader, then re-root.
teh roxxorz said:
http://dl.dropbox.com/u/19699565/3.70 RUU Zip.zip Rename it to PC36IMg. Its 3.70 ruu, flash it in the bootloader, then re-root.
Click to expand...
Click to collapse
Hopefully, your RUU will work. Others who have attempted to this this very thing still couldn't make it work. Me, k2buckley and others have yet to figure it out and believe me, we've tried everything within our experience range. A solution will be found, I have no doubt about that, but "when" is the question that I cannot answer.
teh roxxorz said:
http://dl.dropbox.com/u/19699565/3.70 RUU Zip.zip Rename it to PC36IMg. Its 3.70 ruu, flash it in the bootloader, then re-root.
Click to expand...
Click to collapse
Don't know why this keeps happening dude. Just like all the other ones. I promise (unfortunately) that this guy isn't going to be able to recovery. Same as the others. THe RUU won't work, neither will the PC36IMG. I don't know why. THey may appear to complete successfully, but the result will still be hanging at the splash screen. That is my prediction, let's see his results. I hope I'm wrong, truly, I do.
k2buckley said:
Don't know why this keeps happening dude. Just like all the other ones. I promise (unfortunately) that this guy isn't going to be able to recovery. Same as the others. THe RUU won't work, neither will the PC36IMG. I don't know why. THey may appear to complete successfully, but the result will still be hanging at the splash screen. That is my prediction, let's see his results. I hope I'm wrong, truly, I do.
Click to expand...
Click to collapse
I hope you are too, but I have saved 1 person with the RUU, so I can hope to save more, but yea, I don't know what's causing this pandemic cuz I've been flashing the latest nightlies, reflashing my kernel, with no problems...I hope it works.
Same Here
Wow, what a coincidence, this just happend to me last night. I had just finished installing and flashing the new, SavagedZen(MOD)-RC1-Evo4G, Rom. Went to bed and sometime during the night the phone got stuck on restarting on the EVO white screen and turning off and on continusly. I have tried all the efforts of putting the stock ROM back on and everything else mentioned in this thread, but to no avail. Like you said, cant get into recovery or anything, just keeps looping through startin and stopping.
With all that is said so far on this thread, it looks like a new phone is the only way to fix this.
Westibone said:
Hi Guys, Idon't post too often as you can see, but I have had a great time rooting my Evo and learning from all the awesome members here. I do my research, and until now I have not run across a problem I could not fix on my own.
I am running CM7 nightly 26, and out of nowhere today, my phone rebooted and proceeded to get stuck in a boot loop. I am not surprised by that kind of thing at this point, but for the first time ever, I was not able to boot into recovery. If I select that option from the boot loader, I just get the white Evo 4G screen and it proceeds to boot loop.
Ok, I thought, maybe my recovery was corrupted somehow, so I pull the SD card and put Amon Ra 2.3 in the root directory and named it PC36IMG.zip and flashed it. No good. I still can't get into recovery.
I also tried downloading the stock (rooted) sprint ROM, putting on the root of my SD card and naming it PC36IMG.zip. After the bootloader detects it and the progress bar finishes, it says "Parsing PC36IMG.zip", and then it just takes me back to the bootloader main menu without an option to flash anything.
Also, is there a way to get S-ON back (with my only access being to the bootloader) in the event that I have to take it in? The alternative would be to drown it or smash it (as a last resort)
Any ideas? Thanks very much in advance for any help!
Click to expand...
Click to collapse
By some awkward chance, have you tried a full wipe, and then flash a sense rom?
teh roxxorz said:
I hope you are too, but I have saved 1 person with the RUU, so I can hope to save more, but yea, I don't know what's causing this pandemic cuz I've been flashing the latest nightlies, reflashing my kernel, with no problems...I hope it works.
Click to expand...
Click to collapse
There was actually one guy that I was able to help recover. (it was short lived though). After trying like 10 different RUU's, one of them had finally took. The phone booted up into a stock sense rom, and the kid was stoked. About 10 minutes after he was up again, his phone rebooted again. Stuck at the splash screen again (this was stock, and he still had s off, because we couldn't ever turn it on). I had him try flashing a recovery again, and low and behold it worked, and he flashed a sense rom. Things seemed fine, and I didn't hear back from him. A few days later, he PM'd be back, saying that it randomly rebooted again, and was stuck at the same splash screen loops. He ended up exchanging his phone. He was the ONLY one, out of quite a few that I've tried to assist through this problem, that was actually able to boot the phone again. Unfortunately, it wasn't stable for him, and then it ended up doing the same thing. Somehow, some way, I believe that the damage was already done, and he just got lucky to be able to squeeze a few extra days out of his Evo, but it was still a short lived recovery.
It's a very perplexing phenomenon that's going on here.
k2buckley said:
There was actually one guy that I was able to help recover. (it was short lived though). After trying like 10 different RUU's, one of them had finally took. The phone booted up into a stock sense rom, and the kid was stoked. About 10 minutes after he was up again, his phone rebooted again. Stuck at the splash screen again (this was stock, and he still had s off, because we couldn't ever turn it on). I had him try flashing a recovery again, and low and behold it worked, and he flashed a sense rom. Things seemed fine, and I didn't hear back from him. A few days later, he PM'd be back, saying that it randomly rebooted again, and was stuck at the same splash screen loops. He ended up exchanging his phone. He was the ONLY one, out of quite a few that I've tried to assist through this problem, that was actually able to boot the phone again. Unfortunately, it wasn't stable for him, and then it ended up doing the same thing. Somehow, some way, I believe that the damage was already done, and he just got lucky to be able to squeeze a few extra days out of his Evo, but it was still a short lived recovery.
It's a very perplexing phenomenon that's going on here.
Click to expand...
Click to collapse
I hope my case doesn't come back to haunt me. Seems like we got a T Virus of phone crashings going around...those already along their way [like you and I] are imune...the newer ones get sucked in. we haz to fix this soon-ishly.
I need help repairing my dinc. First, let me apologize for the long post, but I wanted to provide as much detail as possible.
My cousin dropped his phone in water and tried to dry it off. I don't know if he tried to turn it on after drying it off. Also, I don't know what attempts he has made to bring the phone back to life, but he has given up and handed the phone over to me. He figured since I am an IT guy and also do hardware repairs I would figure it out.
This is new to me because I've never owned a Smartphone before. He turned off his service on the dinc and used another Verizon phone he had lying around.
I've research different forums for a fix for the past few days, but nothing has worked. I’ve seen posts with similar symptoms, but in all cases they were able to get more functionality from their phone than mine. Also, my issue is related to water and not from a bad ROM upgrade. Here's a summary of things I've already tried:
Dried the phone out with the rice in Ziploc bag trick for 3 days (phone is completely dried)
Reformatted the micro sd card to fat32
Did a system update
Placed PB31IMG.zip into the root of the sd card
md5 checksum: 31bb1611a0fa8197d447c0438426717e
When I remove or rename the PB31IMG.zip file and hold the down button+power, here is the outcome for the following:
Fastboot: Gives me the following options Bootloader, Reboot, Reboot Bootloader, & Power Dwn
Bootloader takes me back to the main HBoot screen.
Reboot would get me stuck on a continuous loop (stuck on the "HTC Incredible" white screen) and freeze
Reboot Bootloader just takes me back to the Fastboot menu
Power Dwn would do the same thing as the Reboot
Recovery: does the same thing as Reboot; it would freeze at the white "HTC Incredible" screen
Clear Storage: does the same thing as above
Factory Reset: does the same thing as above
Each time it gets stuck at the white HTC Incredible boot up screen, I would have to pull the battery. Hitting/holding the power button doesn't seem to do anything.
From what I've been reading, I don't think the phone is bricked, since it still turns on, has limited functions, & I can get to the HBoot screen. The only thing I haven’t tried is reinstalling the OS (not sure if the OS is included in the PB31IMG.zip file)? Also, I was going to try to reformat the hard drive (just in case the partition is damaged).
The phone has never been rooted and I am not trying to root/unroot the phone... just trying to repair the phone. The phone has the S-ON.
I have uploaded a 10 min. YouTube video so you can see what I'm dealing with. Any help would be much appreciated. If there is anything you want me to try or anything you want to know that I may have left out, please don't hesitate to ask. At this point, I'm willing to try anything.
www(dot)youtube(dot)com/watch?v=gHXDJl6G2X4
Sorry, I can't post a link to my video so just replace the (dot) with a "."
You need to do an ruu with a PB31IMG.zip.
You can get the ruu here http://pvillecomp.com/?page_id=22
If you ever want to be able to root you need to use the froyo one as gingerbread cant be rooted if your s-on. Just download, rename exactly PB31IMG.zip, place on your sdcard in no folders, make sure its not connected to a computer, then pull battery and replace then boot into hboot (vol down + power) it should automaticly find the file after a couple secs and then prompt you to press vol up to install. Once its done you will be promptet to reboot , do so and if all is as expected you should boot up normally. Note that the first boot will take a long time so be patient, it may seem like it freezes at the boot animation but give it time.
cmlusco said:
You need to do an ruu with a PB31IMG.zip.
You can get the ruu here pvillecomp(dot)com/?page_id=22
If you ever want to be able to root you need to use the froyo one as gingerbread cant be rooted if your s-on. Just download, rename exactly PB31IMG.zip, place on your sdcard in no folders, make sure its not connected to a computer, then pull battery and replace then boot into hboot (vol down + power) it should automaticly find the file after a couple secs and then prompt you to press vol up to install. Once its done you will be promptet to reboot , do so and if all is as expected you should boot up normally. Note that the first boot will take a long time so be patient, it may seem like it freezes at the boot animation but give it time.
Click to expand...
Click to collapse
I ran the RUU program, which took about 10 min to complete. When it finished the update process, it rebooted the dinc, but I'm now stuck on the white htc incredible screen as demonstrated in my video. How long I'm I suppose to wait as this white screen? It seems as if it's frozen, but I'm not sure. Am I missing something?
Should I rerun it or try to run the PB31IMG.zip file? BTW, I grabbed the PB31IMG.zip file from the same site from your link.
HiJacK69 said:
I ran the RUU program, which took about 10 min to complete. When it finished the update process, it rebooted the dinc, but I'm now stuck on the white htc incredible screen as demonstrated in my video. How long I'm I suppose to wait as this white screen? It seems as if it's frozen, but I'm not sure. Am I missing something?
Should I rerun it or try to run the PB31IMG.zip file? BTW, I grabbed the PB31IMG.zip file from the same site from your link.
Click to expand...
Click to collapse
Have you done a logcat?
HiJacK69 said:
I ran the RUU program, which took about 10 min to complete. When it finished the update process, it rebooted the dinc, but I'm now stuck on the white htc incredible screen as demonstrated in my video. How long I'm I suppose to wait as this white screen? It seems as if it's frozen, but I'm not sure. Am I missing something?
Should I rerun it or try to run the PB31IMG.zip file? BTW, I grabbed the PB31IMG.zip file from the same site from your link.
Click to expand...
Click to collapse
So your saying you did the ruu exe with your pc and it compleeded sucessfully?
dmeadows013 said:
Have you done a logcat?
Click to expand...
Click to collapse
No, I haven't. Can you please explain what this is and how it's done? I'm assuming this will pull up the syslog on the phone?
cmlusco said:
So your saying you did the ruu exe with your pc and it compleeded sucessfully?
Click to expand...
Click to collapse
Yes, but let me explain. When I first turned on my phone it would freeze at the white htc incredible screen. The pc would not recognize the device. The HTC Sync program would also not recognize the device.
I pulled the battery and did pushed the down button+power to get the HBoot. Then I would plug in the usb cable and the device is still not recognized. I would have to select the fastboot option, then bootloader a few times before the ruu program can detect my phone. HTC Sync would still not detect my phone.
After the phone is recognized by ruu I ran the program. I can see a black screen on my phone with big white HTC letters. Then I would see a green scan bar running. The ruu program completed and the phone rebooted. I hit the "finished" button on the ruu program and exit.
The phone rebooted and got stuck on the white htc incredible screen. I waited for 15 mins and it's still stuck on the same screen. If you watch my video, you can see exactly what I'm talking about. I've tried re-running the PB31IMG.zip file, but it's not working.
Any other ideas? You think the partition is damaged or the phone is bricked?
Ok I watched the video. My only other sugestion would be to try and root it with unrevoked so you can get the custom recovery, wipe everything from in recovery, and then try flashing a custom rom such as jermains rooted gingerbread+ rom. If that dosent work i would say there is some type of hardware failure.
cmlusco said:
Ok I watched the video. My only other sugestion would be to try and root it with unrevoked so you can get the custom recovery, wipe everything from in recovery, and then try flashing a custom rom such as jermains rooted gingerbread+ rom. If that dosent work i would say there is some type of hardware failure.
Click to expand...
Click to collapse
When I root it with Unrevoked, can I use the online method where I log on to their site or does matter?
Can I still root the phone even though HTC Sync does not recognize my phone? Yeah, someone from another forum suggested it might be a hardware issue from the water. If my cousin turned the phone on while it was still wet, he could have shorted out some circuits on the motherboard. I told him what he should do if it ever happened to him next time.
Thanks for helping me out!
HiJacK69 said:
When I root it with Unrevoked, can I use the online method where I log on to their site or does matter?
Can I still root the phone even though HTC Sync does not recognize my phone? Yeah, someone from another forum suggested it might be a hardware issue from the water. If my cousin turned the phone on while it was still wet, he could have shorted out some circuits on the motherboard. I told him what he should do if it ever happened to him next time.
Thanks for helping me out!
Click to expand...
Click to collapse
I wasnt aware there was an online method. I'm not sure if unrevoked will work or not but i know you have to uninstall htc sync before you use the downloadable method. Its a pretty simple process and worth a shot. Hardware failure is verry possible though, especially if it was turned on wile still wet. Even if it wasnt turned on wet it probably got droped in the water wile on possibly causing a short right away.
cmlusco said:
I wasnt aware there was an online method. I'm not sure if unrevoked will work or not but i know you have to uninstall htc sync before you use the downloadable method. Its a pretty simple process and worth a shot. Hardware failure is verry possible though, especially if it was turned on wile still wet. Even if it wasnt turned on wet it probably got droped in the water wile on possibly causing a short right away.
Click to expand...
Click to collapse
That's my bad; it's like 2am now and I was thinking about something else. I had to download the unrevoked3 program and run it. You're right, I had to uninstall htc sync. I was unable to use the program because it wanted me to enable usb debugging mode, which I am not able to do with my phone in its current state. It could not detect my device.
Someone from another forum stated that after watching my video, he noticed that the image I flashed contained a VZ radio. He said he's heard of cases where users were waiting up to 2 hours in the htc incredible screen before the update is complete. This seems like a very long time, but I'm willing to try.
He wanted me to make sure my phone is fully charged. Then he wants me to run the update in the bootloader and just let it sit. He says it may take up to 2 hours. He said if it doesn't work then it's a hardware related issue caused by the board getting shorted out.
Thanks for all your help!
HiJacK69 said:
No, I haven't. Can you please explain what this is and how it's done? I'm assuming this will pull up the syslog on the phone?
Click to expand...
Click to collapse
You need to have adb installed. If you don't, google how and there are many in depth tutorials. Then, once adb is installed, cd to your adb directory in terminal/command prompt and type ./adb logcat.
I've seen a couple of threads such as this with no real solution.
I've been happily using my Desire for months without changing roms or whatever (CM7 and s-off) until last night I opened my Dolphin browser and before it loaded the homepage it froze, totally un-responsive. I took the battery out, and to my horror, it was still totally un-responsive. Wouldn't respond to pressing the power button, pressing volume down+power, charger, or usb.
The battery at the time was about 50%, I've had the battery in and out about 100 times now, trying things like leaving the battery out and then trying again, keeping it on 'charge' for a while and trying to get it booted, with no response at all.
This was until an hour ago, I hopefully tried to boot the phone after the battery, sim and sd card had been out for a while and I got a vibration, and then it hung on the flash screen. I had to remove the battery, then tried to boot again with no response, so I left it a while again, put the battery in and got to the bootloader, thought I'd get into recovery and try a nandroid or something, only when I selected recovery it hung on the slash screen again.
Does anyone have any ideas what this is, or how this could be fixed? Damn I hate not being able to use my previously awesome phone!
I apologise for the long post, I'm just trying to give a good explanation of things. I just couldn't see the problem being my battery, only the day before the problem I was telling my friend how great the battery life on my phone is, and that he should give rooting a go and use CM7, this probably hasn't swayed his decision to root his phone.
stevoh84 said:
I've seen a couple of threads such as this with no real solution.
I've been happily using my Desire for months without changing roms or whatever (CM7 and s-off) until last night I opened my Dolphin browser and before it loaded the homepage it froze, totally un-responsive. I took the battery out, and to my horror, it was still totally un-responsive. Wouldn't respond to pressing the power button, pressing volume down+power, charger, or usb.
The battery at the time was about 50%, I've had the battery in and out about 100 times now, trying things like leaving the battery out and then trying again, keeping it on 'charge' for a while and trying to get it booted, with no response at all.
This was until an hour ago, I hopefully tried to boot the phone after the battery, sim and sd card had been out for a while and I got a vibration, and then it hung on the flash screen. I had to remove the battery, then tried to boot again with no response, so I left it a while again, put the battery in and got to the bootloader, thought I'd get into recovery and try a nandroid or something, only when I selected recovery it hung on the slash screen again.
Does anyone have any ideas what this is, or how this could be fixed? Damn I hate not being able to use my previously awesome phone!
I apologise for the long post, I'm just trying to give a good explanation of things. I just couldn't see the problem being my battery, only the day before the problem I was telling my friend how great the battery life on my phone is, and that he should give rooting a go and use CM7, this probably hasn't swayed his decision to root his phone.
Click to expand...
Click to collapse
did you try rebooting it without sdcard?
If you manage to get it running , try to flash a shipped ROM - it should unroot you and fix any software problems . Try taking it back to your carrier as that sounds more like a hardware problem.
you are stuck on HTC screen are you not? Then this is the exact same situation is it not?
bortak's Troubleshooting Guide said:
S-ON
"I'm S-ON, I can't boot recovery, and my phone doesn't boot "
This is a bit of a worse situation, as you cannot flash system critical parts such as the recovery image and just restore a backup. This unfortunately means that you will lose all of your data when you attempt to fix the phone.
[STEP1]- Make sure that you have a goldcard. If not, create one from the tutorial.
[STEP2]- Battery pull. Hold the BACK button and the POWER button to boot into FASTBOOT mode.
[STEP3]- Download the latest WWE RUU from here
[STEP4]- Run the RUU and wait for completion WARNING: DO NOT, BY ANY CIRCUMSTANCES INTERRUPT THE PROCESS - THIS WILL MORE THAN LIKELY END UP WITH A BRICKED PHONE - NOT EVEN IF GOD HIMSELF TELLS YOU TO DO SO, OR IF THE US PRESIDENT THREATENS YOU WITH THERMO-NUCLEAR WAR
[STEP5]- Once the phone is booted, you are now returned completely to stock. You will need to re-root again, and I'd recommend S-OFF
Click to expand...
Click to collapse
P.S. Remember to read disclaimer on the thread.
kmaq said:
did you try rebooting it without sdcard?
Click to expand...
Click to collapse
I have tried booting without sdcard with no luck.
Walter1115 said:
If you manage to get it running , try to flash a shipped ROM - it should unroot you and fix any software problems . Try taking it back to your carrier as that sounds more like a hardware problem.
Click to expand...
Click to collapse
I would love to try that, only I can't boot the phone at all, not even into recovery.
bortak said:
you are stuck on HTC screen are you not? Then this is the exact same situation is it not?
P.S. Remember to read disclaimer on the thread.
Click to expand...
Click to collapse
I've changed the HTC screen to a Google one, but yes, formally the HTC screen.
I will try and get to the bootloader/fastbootagain, only I have not been able to get to that today. I'm going to download an RUU, and try and flash it, although I'm not sure how if I can't get into recovery? Any help there?
stevoh84 said:
I would love to try that, only I can't boot the phone at all, not even into recovery.
I've changed the HTC screen to a Google one, but yes, formally the HTC screen.
I will try and get to the bootloader/fastbootagain, only I have not been able to get to that today. I'm going to download an RUU, and try and flash it, although I'm not sure how if I can't get into recovery? Any help there?
Click to expand...
Click to collapse
[STEP2]- Battery pull. Hold the BACK button and the POWER button to boot into FASTBOOT mode.
Click to expand...
Click to collapse
you don't need recovery
bortak said:
you don't need recovery
Click to expand...
Click to collapse
Made a noob error there and didn't have the udb plugged in. Got fastboot up, and downloading an RUU, will let you know how I get on, thanks for the help.
Would you advise, running my previous nandroid, once I get up and running again?
stevoh84 said:
Made a noob error there and didn't have the udb plugged in. Got fastboot up, and downloading an RUU, will let you know how I get on, thanks for the help.
Would you advise, running my previous nandroid, once I get up and running again?
Click to expand...
Click to collapse
up to you, doesn't make a difference
Thanks for the help, unfortunately when I got the RUU downloaded and the bootloader downgrader I now can't get the phone into fastboot! Rather gutted, as I could get it there the other day, now I may have to accept defeat!
What happens when you try to get to fastboot mode? How do you do it? Try to boot into hboot, then press power button and you should be in fastboot mode.
stevoh84 said:
Thanks for the help, unfortunately when I got the RUU downloaded and the bootloader downgrader I now can't get the phone into fastboot! Rather gutted, as I could get it there the other day, now I may have to accept defeat!
Click to expand...
Click to collapse
NEVER accept defeat with Android. Try my guide for help.
MatDrOiD said:
What happens when you try to get to fastboot mode? How do you do it? Try to boot into hboot, then press power button and you should be in fastboot mode.
Click to expand...
Click to collapse
I can't get into any sort of boot mode, I've tried leaving it for days and trying the button sequences, I've tried having it plugged in for a day, and then trying, with no luck!
bortak said:
NEVER accept defeat with Android. Try my guide for help.
Click to expand...
Click to collapse
I will have a look, I will try anything really! just need some more ideas....
bortak said:
NEVER accept defeat with Android. Try my guide for help.
Click to expand...
Click to collapse
I may have to accept defeat, but I don't think I will be blaming Android, more than likely a drop of the phone in the past that has taken it's toll or something.
Sadly nothing in the contents of your quite excellent guide jumped out at me as relating to my problem.
But, thanks for helping and your advice.
stevoh84 said:
I may have to accept defeat, but I don't think I will be blaming Android, more than likely a drop of the phone in the past that has taken it's toll or something.
Sadly nothing in the contents of your quite excellent guide jumped out at me as relating to my problem.
But, thanks for helping and your advice.
Click to expand...
Click to collapse
Ahh well that's a shame, get HTC to fix it for you
bortak said:
Ahh well that's a shame, get HTC to fix it for you
Click to expand...
Click to collapse
I have been onto them. The response from HTC was amazing, after detailing in an email my phone is dead, won't respond and won't turn on.
I was told, 'while the phone is on, remove the battery and sim and perform a soft reset, if this fails, perform a factory reset, through settings'
I replied asking them how much it will be for them to fix it, they haven't replied! Maybe they don't do weekend!
So if I send it off to them, are they going to frown upon me for fiddling with the phone and rooting etc?
Hello,
just some hours ago my Galaxy Nexus (SC-04D) rebooted while lying on the table next to me. After several sings of vibration I noticed that the phone doesn't boot completely.
When switching on the phone I get the turn-on-vibration, then the google letters are displayed. Most times the word "google" flickers from left to right over the screen (only the line where the word is supposed to be). Sometimes it boots further and I get the colored "X" displayed. This symbol starts flickering, too and if it went so far it reboots.
Here are two pictures I took from the phone failing to boot:
picpaste.com/img_0001_01-Rmm7kDYb.jpg
picpaste.com/img_0001-eoLqVoiM.jpg
The phone is running stock Android from Docomo. The phone is about 14 months old and has never been unlocked, rooted, modded, taken a bath, ... 'til now.
I tried starting with and without SIM-card, with and without charger attached and let it lie around for several minutes without battery between my tries.
Is there any chance to get my data from the phone or even get it fixed? Please give me a hint what I can do.
Well the Red exclamation mark means that there is a problem with the phone reading the build path. Since you have never rooted the phone, this would mean that the files got corrupt on the phone. With a non-rooted phone a Factory Reset is about the only solution, but is probably only a temporary fix. This is most likely caused by too many apps on the phone and it just freaked out on something eventually.
I think these options might work for you, however I cannot confirm since I have rooted my phone from day one and never looked back:
Power button + up volume= recovery
Thanks GPFboy for your fast response,
GPFboyJS said:
Well the Red exclamation mark means that there is a problem with the phone reading the build path. Since you have never rooted the phone, this would mean that the files got corrupt on the phone. With a non-rooted phone a Factory Reset is about the only solution, but is probably only a temporary fix.
Click to expand...
Click to collapse
As far as I understand a factory reset results in a complete loss of data on the phone, right? So without root/unlock there's no chance to get my data from the phone? That would be really bad.
GPFboyJS said:
This is most likely caused by too many apps on the phone and it just freaked out on something eventually.
Click to expand...
Click to collapse
What is "too many"? I think there are about 35 apps installed atm. By the moment the problem arose wifi and 3g-data,BT,GPS were disabled and just a minute before I took a look how late it was. So nothing special.
GPFboyJS said:
I think these options might work for you, however I cannot confirm since I have rooted my phone from day one and never looked back:
Power button + up volume= recovery
Click to expand...
Click to collapse
The phone reaches fastboot mode, but when selecting recovery mode I get the google logo and after that the open android with the red exclamation mark. That doesn't look good, does it?
BrainSD said:
The phone reaches fastboot mode, but when selecting recovery mode I get the google logo and after that the open android with the red exclamation mark. That doesn't look good, does it?
Click to expand...
Click to collapse
thats stock recovery.
is your bootloader already unlocked or no?
Zepius said:
is your bootloader already unlocked or no?
Click to expand...
Click to collapse
It's still locked.
you might try and go into recovery,
then press (i think) power and vol up and try and see if you can wipe just cache.
Zepius said:
you might try and go into recovery,
then press (i think) power and vol up and try and see if you can wipe just cache.
Click to expand...
Click to collapse
ok, I tried that several time now, but it didn't work. The only thing when I select recovery and press the power button is that I get the google logo and then the dead android + red exclamation sign, but this screen is scrambled and shows flickering pixels as shown in one of my pictures in the first post. So recovery mode seems not to work for me?
Is there a software or hardware problem with my device?
BrainSD said:
ok, I tried that several time now, but it didn't work. The only thing when I select recovery and press the power button is that I get the google logo and then the dead android + red exclamation sign, but this screen is scrambled and shows flickering pixels as shown in one of my pictures in the first post. So recovery mode seems not to work for me?
Is there a software or hardware problem with my device?
Click to expand...
Click to collapse
You can try to unlock your boorloader and flash a custom recovery like cwm or twrp. Maybe that helps. You can always go back and re lock it.
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
You can try to unlock your boorloader and flash a custom recovery like cwm or twrp. Maybe that helps. You can always go back and re lock it.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
He wants to keep his data... which, at this point, seems rather impossible.
If fastboot doesn't solve it, i would try omapflash, OP. That "flickering" doesn't look good.
beekay201 said:
He wants to keep his data... which, at this point, seems rather impossible.
If fastboot doesn't solve it, i would try omapflash, OP. That "flickering" doesn't look good.
Click to expand...
Click to collapse
Well if I was him I would be more worried about my expensive phone instead of data. Maybe a lesson for later to have a backup
Sent from my Galaxy Nexus using XDA Premium HD app
beekay201 said:
He wants to keep his data... which, at this point, seems rather impossible.
If fastboot doesn't solve it, i would try omapflash, OP. That "flickering" doesn't look good.
Click to expand...
Click to collapse
Yes exactly this is the point. Since I don't have a current data backup the first thing to try is getting my data from the phone. I already tried temporary loading the clockwork recovery through fastboot - with the galaxy nexus toolkit and by hand(sdk) - but it failed ("Bootloader locked").
What I'm wondering about is the fact that the phone seems to behave normally in odin and fastbood mode but going nuts the moment it's expected to boot. Besides the flickering google logo and the "matrix-modded" dead android it even ended up in a totally green screen one time.
At the moment I don't dare trying to unlock/flash the phone because of being afraid getting stuck and ending up with the phone being in some kind of undefined / totally broken state. Initially I was in hope of being able to rescue my data but now i will try my luck with docomo support first.
As far as I understood omapflash is primary used for recovering bricked phones not even starting to odin/fastboot mode. But thanks to your hint I found http://forum.xda-developers.com/showthread.php?t=2016628 "Unlock bootloader on GT-I9250 without wipe and without root" This might bring some chance for data access.
I will try to get through 1 to 4 of the guide first and see how far I get.
If this won't work I might try to unlock, recover and try to "undelete" what's possible. (http://forum.xda-developers.com/showthread.php?t=1994705)
Does this order make sense?
Btw, having a dead phone is bad, of course, even when I got it new for 2300Yen but loosing some pictures i really liked and having no phone atm currently hurts more. Especially when knowing that I was thinking of copying all photos to my computer only one day before when I pulled only some minor important ones from the phone I needed for work and planned to do a full backup and unlock this weekend when I get back my 'Milestone' currently lent to someone else.
Once again something I learned. Backup! Even you phone.
BrainSD said:
As far as I understood omapflash is primary used for recovering bricked phones not even starting to odin/fastboot mode. But thanks to your hint I found http://forum.xda-developers.com/showthread.php?t=2016628 "Unlock bootloader on GT-I9250 without wipe and without root" This might bring some chance for data access.
Click to expand...
Click to collapse
!!!
It will work actually, I read/also replied to that thread! I had forgotten about it, sorry. I must say that if you had already read the stickies that matter, you'd already know about it.
It will unlock your bootloader, bypassing fastboot. Still, it's not for the faint hearted. I refered to omapflash because its a low level tool, it doesn't require the bootloader to be unlocked, and is able to restore the bootloader to working state, and I got there because you mentioned you see graphical glitches/flickering which may indicate bootloader partition failure and/or consequent corruption.
I think that's your best shot at trying to get your data back. After unlock, boot to fastboot and 'fastboot boot custom_recovery.img', and grab your stuff (if you can) from /data/.
beekay201 said:
!!!
It will work actually, I read/also replied to that thread! I had forgotten about it, sorry. I must say that if you had already read the stickies that matter, you'd already know about it.....
Click to expand...
Click to collapse
Your hint was very helpful for me getting the right direction since I'm just starting to dig into all this stuff.
Unlocking went quite well. Writing back to the phone worked without a problem and after that it's shown as unlocked in fastboot mode.
It even started loading clockwork recovery with fastboot. But the initial cw recovery screen (their logo and the cw recovery footer) was already shown on a scattered screen (google logo + unlocked lock was fine). After that the usb port connected and disconnected several times, then the screen went blank.
May this be because of corrupted fs or defective hw?
From my understanding with omapflash one have raw access to the phones internal memory similar to with dd on Unix/Linux. So currently I'm trying to dump ("upload") the emmc from the phone - actually in smaller chunks since omapflash needs to allocate all the memory in advance for the upload and to prevent interruptions. This will take a while...
After that I want to try to 'cat' the parts together and mount the filesystem - might be possible to do this from linux since it seems to be ext4 filesystems
BrainSD said:
Your hint was very helpful for me getting the right direction since I'm just starting to dig into all this stuff.
Unlocking went quite well. Writing back to the phone worked without a problem and after that it's shown as unlocked in fastboot mode.
It even started loading clockwork recovery with fastboot. But the initial cw recovery screen (their logo and the cw recovery footer) was already shown on a scattered screen (google logo + unlocked lock was fine). After that the usb port connected and disconnected several times, then the screen went blank.
May this be because of corrupted fs or defective hw?
From my understanding with omapflash one have raw access to the phones internal memory similar to with dd on Unix/Linux. So currently I'm trying to dump ("upload") the emmc from the phone - actually in smaller chunks since omapflash needs to allocate all the memory in advance for the upload and to prevent interruptions. This will take a while...
After that I want to try to 'cat' the parts together and mount the filesystem - might be possible to do this from linux since it seems to be ext4 filesystems
Click to expand...
Click to collapse
Great, so far so good.
Yeah, they're ext4 images, but sparse images i believe - link