Develop Bugs

Droid Incredible dead black screen

Hi I am new to the forum. I have an issue. I just bought the droid incredible on Tuesday. Today it started being weird. I believe it has the slcd screen. I was rooted, and used ninja morph to remove some bloat. It was great until I rebooted and I had lost the bloat and the HTC Sense and Gmail stuff didn’t work. So I thought I could just re-flash and get everything back no problem right; wrong. I tried several ROMs and nothing would flash. I then copied all the \system\app stuff from the clockwork mod update file. So I had everything back where it needs to be and nothing showed up in the app drawer. Titanium backup and rom manager have been no help. I then installed and loaded a 140MB PB1IMG.zip that was supposed to be an official leak. So I put it on my SD card, hboot, and great its working. Bad, It turned off not reboot. It turned off, black screen, nothing. If I remove the battery and charger then put the battery in and the charger I get the orange light. If I hold vol up and power I get the QUALCOMM 3 vibrating thing. IF I hold vol down and power nothing. If I just push the power it vibrates makes a clicking sound must have a drive inside and vibrates one more time followed by more clicking. Still black and nothing after that. I am leaving it on the charger tonight. If there is a shred of hope please share.

I did basically the same thing with my SLCD Incredible, with the same results.

Hmm....
Well, the only thing i can think of is maybe the slcd incredibles have different hardware, as some roms do not run, like cm6. My guess is you flashed a PB31IMG for a amoled inc, and as such, caused your problem. Of course, it could also be a number of other things, like a bad zip of some kind, but in the end, if you cannot access recovery / hboot, something went very wrong. Hopefully you didnt mod it too much, and i would try getting it replaced. That sounds like a brick to me... however, try removing the battery and letting it sit for a bit, and if that works, immediately flash a ruu in hboot, as that resets the phone completely, aside from s-off which vzw techs dont look at. Good luck.

mikerulez121 said:
Hmm....
Well, the only thing i can think of is maybe the slcd incredibles have different hardware, as some roms do not run, like cm6. My guess is you flashed a PB31IMG for a amoled inc, and as such, caused your problem. Of course, it could also be a number of other things, like a bad zip of some kind, but in the end, if you cannot access recovery / hboot, something went very wrong. Hopefully you didnt mod it too much, and i would try getting it replaced. That sounds like a brick to me... however, try removing the battery and letting it sit for a bit, and if that works, immediately flash a ruu in hboot, as that resets the phone completely, aside from s-off which vzw techs dont look at. Good luck.
Click to expand...
Click to collapse
Pretty much.
It seems we have a functional phone underneath a non-functional display. adb devices shows the phone in recovery when we turn it on. If only I could figure out how to flash a new kernel to it without being able to see what's going on...

So a question then... when in HBOOT, will RUU recognize the phone?

arache0n said:
So a question then... when in HBOOT, will RUU recognize the phone?
Click to expand...
Click to collapse
Possibly.. But even if, you need to make sure its an RUU for the slcd incredible, otherwise youll be back to square one. I find it odd that a different screen can cause these kinds of issues... Especially nothing in hboot. But theoretically, if the screen is just dead, you can use a microsd adapter to put a new pb31img on the sd, then boot into hboot, wait like 45 seconds to be safe, then hit the up arrow to start the update. then after like 5 min that hit up again. This should be enough for the phone to flash an RUU. but you need to get the timing right. I think its just best to replace it... As for the slcd issue, i think anyone with an SLCD Inc really should just stay put right now, as its becoming apparent that the 2 phones are different in some way, and things like this can happen... Hopefully Koush or one of the higher up devs can look into it..

I am more than willing to try and fix this thing. Where can I get a good RUU file to put on it?

tjamscad said:
I am more than willing to try and fix this thing. Where can I get a good RUU file to put on it?
Click to expand...
Click to collapse
Well thats the thing... I simply don't know if a slcd run was released. I hopefully a dev will look into this... for all we know its as simple as pushing a file in recovery. You can try that with a regular ruu and see if that helps
Sent from my Incredible using XDA App

Could try shipped roms. Even though its ran by different people I think its still legit.
But like mike said there may not be a ruu for slcd.

This really needs to be in Q&A not Development. All these questions do nothing but junk up this thread.

I just fixed this for my buddys INC.
** Please note: Make SURE you have the correct drivers installed. I used the modified Android ones.
1.) Download the Android SDK, and then fire up a command shell in the Tools directory
2.) Boot the Incredible into Recovery:
* Pull battery, then put back in
* Hold Power and Vol Down for 5 seconds
* Wait 20 seconds
* Hit Vol Down once
* Hit Power
* Wait 20 seconds
3.) Check to make sure that ADB can see it by typing adb devices into the command shell you opened earlier
4.) Type adb reboot oem-78 into the command shell. I let the phone sit for a few minutes.
5.) Run the RUU from Shipped-Roms, located here: shipped-roms.com/download.php?category=android&model=Incredible&fil e=RUU_Incredible_C_Froyo_VERIZON_WWE_3.21.605.1_Ra dio_2.15.00.07.28_2k4k_NV_1.50_PRL58006_release_14 3351_signed.exe
Once the RUU finished running, my phone rebooted and my screen is alive!
Also posted this in Q&A

sorry, I thought this was a devolpment kinda thing. can you move it to Q&A?
FIXED http://forum.xda-developers.com/showthread.php?p=8960978&posted=1#post8960978

complete instructions
Thanks to arache0n and Jobehonda who helped me when I thought I had bricked my phone most of this is there work.

Potential fix for SLCD Bricked Incredibles

So after what seemed to be the art of bricking my Incredible over the weekend (dead, black screen), I think we have found a fix for it.
This is what we did to bring the phone back to life:
** Please note: Make SURE you have the correct drivers installed. I used the modified Android ones.
1.) Download the Android SDK, and then fire up a command shell in the Tools directory
2.) Boot the Incredible into Recovery:
* Pull battery, then put back in
* Hold Power and Vol Down for 5 seconds
* Wait 20 seconds
* Hit Vol Down once
* Hit Power
* Wait 20 seconds
3.) Check to make sure that ADB can see it by typing adb devices into the command shell you opened earlier
4.) Type adb reboot oem-78 into the command shell. I let the phone sit for a few minutes.
5.) Run the RUU from Shipped-Roms, located here: shipped-roms.com/download.php?category=android&model=Incredible&file=RUU_Incredible_C_Froyo_VERIZON_WWE_3.21.605.1_Radio_2.15.00.07.28_2k4k_NV_1.50_PRL58006_release_143351_signed.exe
Once the RUU finished running, my phone rebooted and my screen is alive!

Downloadding now I hope this works. I already called verizon and the replacement Phone should be here Wed.

let me know if this works for you, i worked with aracheon all last night and then was able to finally break it down and get it working this afternoon, if you need help let me know

Credit to be given where credit is due - I wouldn't have figured this out without Jobehonda's help.

I would not say "bricked" inc, just screen was dead because there were no drivers installed for SLCD. My phone was "OK", when i called my own number, it rings, vibrates etc, just i was not able to see anything.
What i did was just got the stock 2.2 PB31IMG.zip from somewhere around here, and using "timing" in my mind, i just repeated flashing process as usually. The only difference was that i did not see what i was doing. For the first time it failed, but i got lucky after second time, and my phone (scree that is) is back to life.
Now, i just have to root it again using caution this time....

Windows XP doesn't like RUU_Incredible_C_Froyo_VERIZON_WWE_3.21.605.1_Radio_2.15.00.07.28_2k4k_NV_1.50_PRL58006_release_143351_signed.exe file name must rename to anything(.exe) shorter I used RUU.exe

fuzio1963 said:
I would not say "bricked" inc, just screen was dead because there were no drivers installed for SLCD. My phone was "OK", when i called my own number, it rings, vibrates etc, just i was not able to see anything.
What i did was just got the stock 2.2 PB31IMG.zip from somewhere around here, and using "timing" in my mind, i just repeated flashing process as usually. The only difference was that i did not see what i was doing. For the first time it failed, but i got lucky after second time, and my phone (scree that is) is back to life.
Now, i just have to root it again using caution this time....
Click to expand...
Click to collapse
Well, right. But the phone is effectively useless with the screen problem. The big guns are calling it an "SLCD Brick," sooo...
tjamscad said:
Windows XP doesn't like RUU_Incredible_C_Froyo_VERIZON_WWE_3.21.605.1_Radio_2.15.00.07.28_2k4k_NV_1.50_PRL58006_release_143351_signed.exe file name must rename to anything(.exe) shorter I used RUU.exe
Click to expand...
Click to collapse
Depends on where you put it. You should be able to get away with dropping that on the root of your C drive and still keep the long filename.

Fixed It works it really works, Thank you Jobehonda and arache0n

tjamscad said:
Fixed It works it really works, Thank you Jobehonda and arache0n
Click to expand...
Click to collapse
Glad to hear it.

Awesome! Glad it worked for more than just one person!

arache0n said:
Well, right. But the phone is effectively useless with the screen problem. The big guns are calling it an "SLCD Brick," sooo...
QUOTE]
What's your point here?? You said "bricking my Incredible ", soooo......?
FYI, i just rooted my Dinc with unrev....3, got black screen with two white lines, (again). Flashed recovery fix, and all is goooood, this time.
G-night all.
Click to expand...
Click to collapse

the problem aracheon had is we accidently flashed the wrong image file to upgrade back to stock recovery when trying to load the correct flash file it was not working...not sure why. Either way, both seem to fix the problem.

Jobehonda,
I'm stuck with my Black screen SLCD Dinc as well, doing the same mentioned above, and when I tried following your instructions it hasn't worked out for me so far. I can't get past the "adb devices" thing. It tells me "devices not attached" or someting to that effect after running the command. I may be doing something incorrectly... Could you be of assistance? I also posted a comment to your "Droid Incredible is a Pile" post on your site. Looking forward to you helping me bring my Droid back to life...
Thanks!

Nevermind... I fixed my "SLCD Brick"!! I will post details later of how I did it...

tjamscad said:
Downloadding now I hope this works. I already called verizon and the replacement Phone should be here Wed.
Click to expand...
Click to collapse
Well, for what it's worth your replacement phone might be an AMOLED.
A week or two ago I got a replacement for the 3G issue and recieved another AMOLED.

OK, this is, what fixed mine:
-pull battery, then put back in
-hold power + vol down for 5 seconds, nothing happened...
-then hold power down for 5 seconds, got 1 vibration...
-then hold vol up + power for 5 seconds, and to my surprise, screen turned on and only had 1 option: Hboot
-then left the screen up and took my SDcard out (the battery cover was off already) and I went to the following thread (how-to-update-your-droid-incredible-to-leaked-android-2-2); and downloaded the "PB31IMG.zip" file from step 1 and copied it over to my SDcard. Please "google" the thread title above... I'm not allowed to post full links because I'm a new user.
-then I put the SDcard back in, pull the battery, then put back in
-hold power + vol down for 5 seconds
-Boots into hboot and select Bootloader
-PB31IMG.zip will start to install.
**Note** Your phone might reboot to either hboot or recovery after trying to install PB31IMG.ZIP, just get back to hboot and install again, when you get back to hboot you should notice its version .92 and S-OFF is still on, just install PB31IMG.ZIP again and all should be good. I believe at one point after it updates hboot it has to reboot to finish the install, so this might be what you are seeing.
-Finally it will reboot and you should see HTC Screen, Droid voice/Red eye will load, and you will have a fresh new 2.2 Dinc un-rooted. You then can try re-rooting at your own risk!!
I basically used part of jobehonda's instructions, and part of the thread's instructions, combined with my own messing around with my phone to fix my "bricked SLCD" Dinc... I hope this can help others as well as it helped me! ; )
Just one more option to try... What the heck, your droid is already screwed, it can't get worse. Just try this!
BTW, a buddy of mine with a rooted Droid X, also helped me with getting this far for the last 3 days!! He helped me with searching all the droid forums out there and random sites to get answers... Thanks CLIFF!

<---- Jackass

edit
fixed.

I am glad you figured it out, basically for the device to be recognized in adb you need to make sure your definately in recovery, if you follow the steps and count, one one thousand, two one thousand, etc etc you should be able to get it into recovery and recognized by adb.
the other thing is you need to make sure you have the HTC drivers installed prior, otherwise it wont recognize.

Then I shall edit it.

[Q] evo wont boot and RUU fails with error

I tried one of the rooting processes today and it didn't work. Now when I turn my Evo on it goes no further than the white HTC screen that you get when you turn it on. When I try to run the RUU it gets a connection error and won't go through. Can someone please help?

Robes1 said:
I tried one of the rooting processes today and it didn't work. Now when I turn my Evo on it goes no further than the white HTC screen that you get when you turn it on. When I try to run the RUU it gets a connection error and won't go through. Can someone please help?
Click to expand...
Click to collapse
If you pull the battery can you get to the bootloader screen? (hold volume down and power button when turning on)

You should be able to do what Greenfieldan suggests. It is possible to work through this issue, so don't fear but it make take a few tries.

Greenfieldan said:
If you pull the battery can you get to the bootloader screen? (hold volume down and power button when turning on)
Click to expand...
Click to collapse
once I get to this screen how do I get the RUU to connect to the phone? I've tried it several times from this screen and nothing is working.

Robes1 said:
once I get to this screen how do I get the RUU to connect to the phone? I've tried it several times from this screen and nothing is working.
Click to expand...
Click to collapse
Thread stalking is fun, I see which thread you are reading, but you may have to reset you phone.
Do you either:
Have a recovery installed (if you aren't sure, then you may not)
have a PCIMG36 on the root of your sdcard, (if you aren't sure then you may not)

Robes1 said:
once I get to this screen how do I get the RUU to connect to the phone? I've tried it several times from this screen and nothing is working.
Click to expand...
Click to collapse
Go in to fastboot and you should see something toward the top that says "FASTBOOT USB", once there run the RUU

SnoopDawg said:
Thread stalking is fun, I see which thread you are reading, but you may have to reset you phone.
Do you either:
Have a recovery installed (if you aren't sure, then you may not)
have a PCIMG36 on the root of your sdcard, (if you aren't sure then you may not)
Click to expand...
Click to collapse
I have a pc36img file on the root of my sd card. It says that it can't open it when i select flash zip from sd card.

Just download the actual ruu from http://forum.xda-developers.com/showthread.php?t=884060. It will be one of the .exe files same version of you had on the phone will prolly work best. Then do what xhausx said and run the ruu file once there. Thanks xhausx btw cause i was confused too.

aclearersky said:
Just download the actual ruu from http://forum.xda-developers.com/showthread.php?t=884060. It will be one of the .exe files same version of you had on the phone will prolly work best. Then do what xhausx said and run the ruu file once there. Thanks xhausx btw cause i was confused too.
Click to expand...
Click to collapse
or download an unrooted version of your software in pc36img.zip format and boot into the bootloader and it will restore your phone to stock if you cant run any ruu

Need Help
I know this is an old thread, but I'm working on an old phone. Hopefully some of you guys are still following this.
My father has an EVO 3D that showed up one day stuck on the white HTC screen. The only remedy was to pull the battery. I thought it would be no big deal to just go into the boot menu and either try and run recovery, or at worst do a factory reset. Both of these options failed. I even made a few attempts at trying from the SD card with a ROM or two. So I downloaded the RUU direct from HTC thinking that would finally take care of the problem. But after connecting up in FASTBOOT mode and running the RUU, it eventually fails when the update gets to the point that it's supposed to restart the phone in bootloader mode. Because at that point the phone just restarts to the white HTC logo again, and the software times out telling me that it can't connect to the device. Any help here other than passing me a trash can Thanks in advance!

[Q] I tried rooting and....I guess I screwed up?

Here's my 4 hour journey...
I tried rooting my Evo using AutoRoot v2.4 (http://forum.xda-developers.com/showthread.php?t=838448 I would post there but I don't have permissions, plus my problem seems more general at this point anyway). I followed all of the instructions (I'm running Android 2.2 with 3.70.651.1). At first, it was telling me that it was unable to root. After trying a couple things (such as killing all running processes), I used an RUU of 3.70.651.1 (http://www.multiupload.com/W679R1W391). I ran AutoRoot again, and this time it told me Root was successful and took me to the bootloader screen. As it did this, the AutoRoot DOS window just disappeared. I rebooted and tried a few more times, same result.
Here's where I'm not quite sure what I did. I think the next thing was I went into Recovery from bootloader, didn't really know what I was doing, and did a battery pull. Then I tried to factory reset by going bootloader -> clear storage. When I went to try and run AutoRoot again, my computer wasn't recognizing my Evo (I guess restoring the Evo caused it to lose the drivers?). When I plugged it in, it briefly searched for several "Qualcomm CDMA Technologies MSM" drivers (weird, never saw it look for those before when I plugged in my Evo?), asked me if I had a disk that came with the hardware, and when I said no it told me it couldn't find the drivers.
So basically my computer doesn't seem to recognize my Evo anymore even though it seems to be at its factory original stock settings. To top it off, it now seems to be stuck in a continuous reboot cycle every couple minutes or so (the worst that's ever happened to me before was semi-random restarts, maybe a couple times per week). I tried doing a factory reset by doing bootloader -> recovery -> menu -> factory reset but that didn't do anything. And I don't think it's charging anymore, considering that the battery is slowly getting lower and lower even though the orange light goes on when it's plugged in (though maybe it's just losing more battery than its gaining through all this restarting). At this point all I want is to get out of this continuous reboot cycle that I've spent the last couple hours trying to look for solutions for, with no luck. Much less re-customize my phone to how it was pre-restore and much less actually get through rooting it... Any help?

First re-run your RUU.
http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install ; download the modified hboot drivers
http://unrevoked.com/recovery/ ; download unrevoked
Make sure to have installed, then uninstall htc sync on your computer, and that usb debugging is enabled on your phone. Then run unrevoked and you should be good to go.

"First re-run your RUU."
But my PC isn't recognizing my Evo, I guess because something is wrong with the drivers? I tried running the RUU and it said Error [170]: USB Connection Error.

Caperi said:
"First re-run your RUU."
But my PC isn't recognizing my Evo, I guess because something is wrong with the drivers? I tried running the RUU and it said Error [170]: USB Connection Error.
Click to expand...
Click to collapse
http://dl.dropbox.com/u/19699565/3.70 RUU Zip.zip
A 3.70 ruu in PC36IMG form. Re-name to PC36IMG, then place on your sdcard, then boot into the bootloader, and apply the update and reboot.

teh roxxorz said:
[link]
A 3.70 ruu in PC36IMG form. Re-name to PC36IMG, then place on your sdcard, then boot into the bootloader, and apply the update and reboot.
Click to expand...
Click to collapse
How should I access my sdcard, since my PC isn't recognizing my phone?
I could probably do it via another phone, but I won't have access to that until tomorrow; is that the only way?
Edit: Oh boy. Just tried typing your link in on my phone, and apparently the phone doesn't recognize its sdcard... Might be why my PC isn't seeing my phone?

Well, you can take the battery out, remove the sdcard, the mount it to your computer via micro usb adapater.

teh roxxorz said:
Well, you can take the battery out, remove the sdcard, the mount it to your computer via micro usb adapater.
Click to expand...
Click to collapse
Don't have one of those, but even if I did (or got the files on there via another phone), wouldn't the fact that it won't recognize the sdcard be a problem when trying to get it to apply the update?
The battery is starting to get really low (about 10%), I think it's not recognizing the charger

Caperi said:
Don't have one of those, but even if I did (or got the files on there via another phone), wouldn't the fact that it won't recognize the sdcard be a problem when trying to get it to apply the update?
The battery is starting to get really low (about 10%), I think it's not recognizing the charger
Click to expand...
Click to collapse
Then what you could do is copy the files on the sdcard to the pc, then re-format it from there, then place the files on it, and stick it on the charger asap.

This link to recover sd card and usb:
http://forum.xda-developers.com/showthread.php?t=695243
Then let charge, use external wall charger if needed. If you have to buy one, its like 5 or 10 bucks and its better then having to buy a whole new phone.
Then, download the PC36IMG.zip (RUU in zip form), place on root of sd card, boot into bootloader, let it scan, when it asks if you want to run the update, say yes. Bada bing bada boom, your up and running. Then go download Unrevoked, its easier if your not completely sure what your doing, plus it has a nice and pretty UI that you cant possibly screw up and 5 minutes later your completely rooted, simple as that.

RileyGrant said:
This link to recover sd card and usb:
http://forum.xda-developers.com/showthread.php?t=695243
Then let charge, use external wall charger if needed. If you have to buy one, its like 5 or 10 bucks and its better then having to buy a whole new phone.
Then, download the PC36IMG.zip (RUU in zip form), place on root of sd card, boot into bootloader, let it scan, when it asks if you want to run the update, say yes. Bada bing bada boom, your up and running. Then go download Unrevoked, its easier if your not completely sure what your doing, plus it has a nice and pretty UI that you cant possibly screw up and 5 minutes later your completely rooted, simple as that.
Click to expand...
Click to collapse
Pardon me if I'm misunderstanding, but what I'm seeing from your post is that to fix the sd card issue I need to fix the usb issue, to fix the usb issue i need to get root, and to get root i need to fix the sd card issue? Haha, yeah I lost you somewhere along the way...
@teh roxxorz - You're saying that the sd card issue should be fixed if I reformat the SD card on my PC? If so, that's what I'm going to try tomorrow when I have that other phone I can use.

That should fix your issue.

So I reformatted the sdcard on my PC, got the PC36IMG.zip on there, ran it via bootloader, and it worked. But, I'm still stuck in the continuous reboot cycle, can't connect my phone to the PC, and in the brief moments it stays on, it won't recognize the sdcard...
On the bright side, it successfully charged overnight, so that's not going to be a problem.
I'm hesitant to try rooting (if that's even possible at this point) to fix the problem while it's in this state in case I have to take it back to Sprint, unless there's a reason that should fix the problem? It seems pretty hopeless right now...

If you're phone is still acting crazy & it won't stay on, I wouldn't try unrevoked. Just get rid of any evidence of rooting from your SD card, and take it back to Sprint - assuming you're s-on. If you have insurance, they'll give you a new one for free. Otherwise, I'm not sure what it will cost or if it will, or if you'll have to go through HTC.

plainjane said:
If you're phone is still acting crazy & it won't stay on, I wouldn't try unrevoked. Just get rid of any evidence of rooting from your SD card, and take it back to Sprint - assuming you're s-on. If you have insurance, they'll give you a new one for free. Otherwise, I'm not sure what it will cost or if it will, or if you'll have to go through HTC.
Click to expand...
Click to collapse
+1.
If its acting wacky before root, rooting it wont fix it. I would take it back to Sprint, for sure.
Sent from my PC36100 using XDA App

It sounds like you put your phone in diagnostic mode, when turning it on Volume Down takes it to the bootloader while Volume Up does Diag Mode. Check to see whether or not your phone shows S-OFF in the bootloader, if so you'll want to run the FlashZip script and select the Sprint Lovers file.
However, if your computer is still having trouble recognizing your phone let it sit for two minutes without the battery. If that still does not fix it use Volume Up and power one more time to try and take it out of that. I would also recommend against running Unrevoked if your phone is in Diag mode, it is very easy to permanently mess something up with it in that state.
edit: If you need to charge it more just turn the phone off and it should charge fine.

Problem I'm seeing is that u used auto root. I've seen nothing but thread after thread of problems with it. I've always used unrevoked3 and I've rooted many different phones including...2 heros, 2 evos, an Eris, a Droid, a Droid 2, and a Droid incredible. Never once did it fail or give me any issues. Simply follow the instructions and even watch the video on their site. If I where u I'd just ruu ur phone and start all over.

xHausx said:
It sounds like you put your phone in diagnostic mode, when turning it on Volume Down takes it to the bootloader while Volume Up does Diag Mode. Check to see whether or not your phone shows S-OFF in the bootloader, if so you'll want to run the FlashZip script and select the Sprint Lovers file.
However, if your computer is still having trouble recognizing your phone let it sit for two minutes without the battery. If that still does not fix it use Volume Up and power one more time to try and take it out of that. I would also recommend against running Unrevoked if your phone is in Diag mode, it is very easy to permanently mess something up with it in that state.
edit: If you need to charge it more just turn the phone off and it should charge fine.
Click to expand...
Click to collapse
My phone has always been S-ON throughout this.
I did try leaving it off and without battery for extended periods of time - no dice.
How could I tell if it's in diagnostic mode and what does diagnotistic mode do?
plainjane said:
If you're phone is still acting crazy & it won't stay on, I wouldn't try unrevoked. Just get rid of any evidence of rooting from your SD card, and take it back to Sprint - assuming you're s-on. If you have insurance, they'll give you a new one for free. Otherwise, I'm not sure what it will cost or if it will, or if you'll have to go through HTC.
Click to expand...
Click to collapse
k2buckley said:
+1.
If its acting wacky before root, rooting it wont fix it. I would take it back to Sprint, for sure.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
So I took it to Sprint, they spent a couple hours on it, placed an order for a new one, and gave me this one back saying it was dead and unfixable (I think all they did was a hard reset). When they gave it to me, it was on, and remained on without restarting for like 30 mins (I thought they had fixed it without realizing it). Just now, I turned it off and on again, and the reboot cycle started again... Any reason why it may have been working that one time? I'll probably just wait for the replacement, but just curious as to why it may have worked.
@Papa_Smurf - Yeah I tried to RUU it but that didn't fix any of the problems

I think it may have just been playing possum. Is it still doing it?

Yeah now it's in the reboot cycle again. Maybe if I was to let it run through the cycle long enough it might eventually stop until I manually powered down and on again (I'm guessing that's what had happened when I got it back from Sprint).

HELP!!! Rooted using Unrevoked 3, now phone randomly locks up!

So I just rooted using the latest unrevoked, but now my phone locks up after about 30 seconds or so, then vibrates 5 times. More troubling: It cannot see an SD card, will not mount or format.
Hoping someone can help me get back to stock.
I did not take the gingerbread OTA, FWIW.

OK, well ,the obvious first question is gonna be are you s-on or s-off.
Turn your phone on while holding the power button down to see what it says at the top when Hboot starts up.

HipKat said:
OK, well ,the obvious first question is gonna be are you s-on or s-off.
Turn your phone on while holding the power button down to see what it says at the top when Hboot starts up.
Click to expand...
Click to collapse
It says S-ON

dsf3g said:
It says S-ON
Click to expand...
Click to collapse
Boot into the bootloader, then select clear storage, then try to boot up normally.

OK, so I managed to flash PC36IMG.zip. So now I'm back to stock and the EVO runs fine without rebooting. Wheeew! I was already scanning eBay for a replacement, LOL! Only issue I have now is that my Evo does not recognize the SD Card (won't let me mount, format, nothing.) I'm seeing some threads on this sort of thing, but if anyone has a quick fix I'd love o hear it. I've got a 16 GB card full of music that's just sittin' there.

Oh, now this is bad: the battery does not seem to charge after restoring... at least the charging symbol is not coming on!
UPDATE: OK, the red light is coming on now when I plug in, but battery status shows "discharging." I don't know at this point whether it's charging or not.

OK, just verified. Phone isn't charging. Down to 50%. Shutting off so I'll have enough juice to fix ti when I figure our what needs to be done. I don't have a separate battery charger, so I'm SOL if I can't get this thing working again.
Any help would be much appreciated!

http://forum.xda-developers.com/showthread.php?t=695243
sd card fix. Also, turn the phone off as you have, but leave it plugged in charged over night and see what happens for now.
Make sure you have the hboot drivers downloaded, then install, then uninstall htc sync, enable usb debugging from applications > development, then run unrevoked again.

teh roxxorz said:
http://forum.xda-developers.com/showthread.php?t=695243
sd card fix. Also, turn the phone off as you have, but leave it plugged in charged over night and see what happens for now.
Make sure you have the hboot drivers downloaded, then install, then uninstall htc sync, enable usb debugging from applications > development, then run unrevoked again.
Click to expand...
Click to collapse
Thanks, I'll give it a try this weekend. Right now I've got a spare battery charger on order with Amazon. Should be in this Friday. Don't want to mess with anything until I can start with a fully charged battery.

You're S-On. There's nothing you can, or could have messed with, unless you don't have the new update on your phone, which was going to be my next question

HipKat said:
You're S-On. There's nothing you can, or could have messed with, unless you don't have the new update on your phone, which was going to be my next question
Click to expand...
Click to collapse
I don't have the new update on my phone. It's still showing Android 2.2 and I never approved the OTA.
One suggestion that seems to work for some people is to flash a new radio. I wonder if someone could help me with this:
1) What do I need to know choose the appropriate radio to flash?
2) Do I need to be rooted to do so, because it seems I'm not.
I'm browsing eBay for cheapie Oprimus S phones... please help me not have to buy a used $100 Optimus S because I murdered by Evo :-(

Yes, you need to be rooted to flash the radios fro ma zip file.
you don't to flash form PC36IMG.zip file, and there is the choice to do it either way.
I'm curious, you said in your OP that you rooted, and the phone went into maintenance mode (The vibrates 5 times thing is maintenance Mode).
Are you sure the root took? I would do this, reinstall HTC-Sync, then install just the program, not the drivers, and try Unrevoked again, make sure it goes through the root process and the flash of clockwork recovery.
If it boots up, then you're good.
From there, I would flash Amon Ra, as it's a better recovery, and then try a ROM.
Radios is the least important thing you can flash, and I'd save that for last, and make sure you know in detail what you're doing, when it comes to radio flashing.

HipKat said:
Yes, you need to be rooted to flash the radios fro ma zip file.
you don't to flash form PC36IMG.zip file, and there is the choice to do it either way.
I'm curious, you said in your OP that you rooted, and the phone went into maintenance mode (The vibrates 5 times thing is maintenance Mode).
Are you sure the root took? I would do this, reinstall HTC-Sync, then install just the program, not the drivers, and try Unrevoked again, make sure it goes through the root process and the flash of clockwork recovery.
If it boots up, then you're good.
From there, I would flash Amon Ra, as it's a better recovery, and then try a ROM.
Radios is the least important thing you can flash, and I'd save that for last, and make sure you know in detail what you're doing, when it comes to radio flashing.
Click to expand...
Click to collapse
I can't be sure I rooted. I'm just going by what Unrevoked reported. Superuser was installed, but the phone would die before I had much time to verify that I was actually rooted.
I've never installed HTC Sync, BTW. According to the unrevoked instructions you shouldn't have it installed on your PC because it causes problems.

OK, so I got home and the phone says battery is 100% charged. So that's good. It appears to charge when turned off, at least.
Sadly, it does not recognize USB at all. The computer beeps when I plug the phone in, but the phone shows no popups or anything.
I tried running "unrevoked" again, but unrevoked just kept waiting for me to plug in the phone. I did not install HTC Sync.
The phone does not recognize micro sd cards from within Android, but I can flash signed ROMs. I did that today, flashing what I think is a newer ROM than I had before, but alas it did me no good. The phone still does not see the micro SD card or realize that I'm plugged in and charging.
The ROM I sintalled this time was the third link on this page:
http://forum.xda-developers.com/showthread.php?t=884060
It corresponds to the software version I was running before running UNREVOKED the first time.
I'm getting pretty worried here. I don't see how I'm supposed to fix this phone if I cannot communicate via USB.

Installing HTC Sync will install the drivers on your computer, which you need for unrevoked to work, but then, you need to uninstall the program (not the drivers).

Ugh, now I've discovered another problem. With this latest stock ROM I've lost bluetooth!
I'm losing hope here. My last best hope seems to be to accept the Gingerbread OTA, and if that doesn't solve the problem throw myself on the mercy of our local Sprint repair store. Anyone know what their policy is on this?
Will they repair something like this for a fee if it's not under warranty? I imagine even completely brcked Evos can be repaired with a new motherboard, right?
Should I try telling them that the OTA screwed it up? Will they be able to tell what I've done to the phone?
At this point I just want to get back to stock. No longer interested in rooting. I need a cell phone just for daily living.