[Q] Touch Sensors not working - Droid Incredible Q&A, Help & Troubleshooting

So out of no where my touch sensors on my screen are not working. I do have nand backup of my current rom and yes that probably would fix whats going on. heres my issue though, i used unrevoked to root my phone a while back, but when i used the clockwork recovery, i got the black screen with white bars, so ive been using RA recovery to flash roms etc. last night i decided to turn my usb debugging off because my friends computer was being retarded when i connected my phone to it. also the only time i flashed the clockwork recovery was when i was using rom manager to check for rom updates. Unfortunately i was on the clockwork recovery before my sensors went out. i could easily use unrevoked again to flash RA recovery and restore my back up, BUT MY USB DEBUGGING IS OFF Now all i can do is turn my screen on and stare at my lock screen. Any ideas on anything i can do to make my phone function again? if anybody would know, i know it would be the people of this forum. thank you

Wrong forum, this belongs in Q&A. The easy answer is: find a stock RUU, get the PB31IMG.zip from it, and flash that in bootloader, then you can get back to turning USB debugging back on--assuming that you don't just have bad hardware.

Thank you!

DirtySimpleClean said:
Thank you!
Click to expand...
Click to collapse
Make sure to backup EVERYTHING first, RUUs are like steamrollers, they return everything to HTC/Verizon standards, and you very well could lose data.

how do i pull the PB31IMG.zip from the ruu?

Related

[Q] Bricked if I cannot reach recovery?

Sounds like there weren't any ideas in Q&A for this one, and I haven't seen much in terms of not being able to access recovery, so here goes...
I was happily using CM7, and while reading through a Diablo III news page (hopefully it comes out soon ), my phone rebooted into a boot loop. Weird, but I figured at worst I would wipe data and reinstall a ROM. Unfortunately, I can't get into recovery any longer.
If I boot the phone normally, I see the white HTC splash screen for a few seconds, then it reboots. I can use HBOOT fine, but as soon as I try to reboot normally / boot into recovery / boot into Restore Factory Defaults, my phone will reset. Let me clarify...
Pull and replace battery
Boot into HBOOT (volume down + power)
Select Recovery
Phone reboots and reaches CWM Recovery 3 for about 1/2 second, not long enough for me to click anything
Phone reboots into boot loop
I've used HBOOT to flash to CWM Recovery 3.0.0.8, downgraded to the stock radio, run the 2.2 RUU. I'm still running up against the same boot loop problem.
I wouldn't be surprised if it was a hardware problem, but I'm anxious to hear if anyone has ideas to try first. Additionally, is there any way to restore to S-ON through HBOOT in case I need to bring this into a Verizon store? I have fastboot.exe that can recognize the device over USB while the device is in HBOOT, maybe this will help?
Thanks!
Current state: Ran 2.2 RUU, S-OFF, HBOOT-0.92.0000, AMOLED, 2.15.00.07.28 radio
Thanks again.
Had this exact issue while running cm7. First couple of from when it was crackflashers. I couldn't find anything to help or fix it. I got a new dinc because I can't afford to be without for long.
Good luck dude.
Sent from my ADR6300 using Tapatalk
Thanks for the note. Maybe my fate will be the same. Did you get any sympathy from Verizon?
Doesn't sound like there are even any suggestions using fastboot, lol. [crickets chirping]
Can you flash cwm 2.5.x and try? Not sure if it will help but worth a shot?
sent from a phone
Yeah take out battery, then pull out sd card put it into a adapter and insert it to ur pc. Then find the file that was shipped specifically for ur device it looks something like this PC130mg.zip or some crap like that anyways put that on the root of your sd card. load ur card back to your phone now into hboot(volume down plus power) mode. Your phone will auto detect that file and start to ask if u want to install update say yes boom it will flash back to stock.....however my only concern would be if u need to turn s-ON before u do this.
I did this for a evo 4g and it worked but I turned s-ON first as it was in the instructions I was following. I think maybe the update file checks to see if ur S-off or on. But don't quote me on that.
Sent from my PG06100 using Tapatalk
popasmurfn23 said:
Yeah take out battery, then pull out sd card put it into a adapter and insert it to ur pc. Then find the file that was shipped specifically for ur device it looks something like this PC130mg.zip or some crap like that anyways put that on the root of your sd card. load ur card back to your phone now into bootloader (volume down plus power) mode. Your phone will auto detect that file and start to ask if u want to install update say yes boom it will flash back to stock.....however my only concern would be if u need to turn s-ON before u do this.
I did this for a evo 4g and it worked but I turned s-ON first as it was in the instructions I was following. I think maybe the update file checks to see if ur S-off or on. But don't quote me on that.
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
Yeah, I agree with popasmurf. Put the PB31IMG.zip on your sdcard. Then let hboot discover and update it. It'll be back to stock and youll have to reroot but better than a paperweight.
You can find the image here -----> http://dougpiston.com/?page_id=108
I'm assuming you have a dinc.
sent by carrier pigeon
hope that helps
@phazeone let's say he just does that. Now his phone reboots and is on stock and looses his root, now he can root it again and then turn the S-on by the single file flash from recovery mode, and then use the update file again to flash the phone back to normal stock without root ( if he was taking it back) so whenever u want to manipulate the S security u must be rooted correct?
Sent from my PG06100 using Tapatalk
popasmurfn23 said:
@phazeone let's say he just does that. Now his phone reboots and is on stock and looses his root, now he can root it again and then turn the S-on by the single file flash from recovery mode, and then use the update file again to flash the phone back to normal stock without root ( if he was taking it back) so whenever u want to manipulate the S security u must be rooted correct?
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
You are correct.
popasmurfn23 said:
Yeah take out battery, then pull out sd card put it into a adapter and insert it to ur pc. Then find the file that was shipped specifically for ur device it looks something like this PC130mg.zip or some crap like that anyways put that on the root of your sd card. load ur card back to your phone now into hboot(volume down plus power) mode. Your phone will auto detect that file and start to ask if u want to install update say yes boom it will flash back to stock.....however my only concern would be if u need to turn s-ON before u do this.
I did this for a evo 4g and it worked but I turned s-ON first as it was in the instructions I was following. I think maybe the update file checks to see if ur S-off or on. But don't quote me on that.
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
phaze one said:
Yeah, I agree with popasmurf. Put the PB31IMG.zip on your sdcard. Then let hboot discover and update it. It'll be back to stock and youll have to reroot but better than a paperweight.
You can find the image here -----> http://dougpiston.com/?page_id=108
I'm assuming you have a dinc.
sent by carrier pigeon
Click to expand...
Click to collapse
Thanks for the replies.
I tried this method to flash back to the stock 2.2 image before I started this thread. That's what I meant by "I've used HBOOT to ... run the 2.2 RUU." The stock image seemed to install properly in HBOOT. I have evidence that it successfully went back to stock, since I get the original ! triangle graphic instead of CWM when I try to enter recovery from HBOOT. However, I only see the graphic pop up for a brief second before it reboots again. Trying to boot into recovery or the ROM itself still result in a reboot.
I cannot achieve S-ON without having access to recovery, at least there's no way that I've found to do it through HBOOT.
Any other thoughts? I think it's a hardware problem. It appears the phone is back to stock (except it's still S-OFF), but everything outside of HBOOT causes a boot loop. I stopped in at Verizon this afternoon and they'll be sending a new phone to arrive by Tuesday. At this point, it'd be nice to try all avenues of repair for the future benefit of others that run into this problem.
Probably bad memory chips on the phone. Since it happened all of a sudden during normal use it usually indicates hardware failure.
That is pretty much what I determined. Bad hardware. Sorry for your trouble but is nice to know I'm not the only person to ever have this. Also nice to know I didn't miss something that could've brought it back to life.
I filed an insurance claim. Figured since I have had it for years and never used it I'd take advantage.
Sent from my ADR6300 using Tapatalk
You can boot your phone like regular right? Just let it launch up or do you get loops?
Nevermind i see what ur saying. when i was flashing incorrect kernals i would get the same behavior from my phone. So i suggest you take phazeones link and try that file.Because u might have the incorrect file. There might be more than meets the eye make sure u got the right file.
When i searched for my zip file for my evo there was like 4 of them. They had to match what was said in the upper left corner of my hboot screen. So let me knoe if it worked
I wonder if he could just wipe that SD card, place a new Rom etc on it and reinstall. Bricking displays no response you've got a better shot at recovering course your SD card/battery could be bad
Since you're trying to flash the 3.x.x.x version of CWM, that may be your issue. Here's a zip for 2.5.0.5, one of the most stable earlier Recoveries. Flash through hboot as per usual.
If that doesn't work, (I'm assuming that you can boot the phone normally at this point) try re-rooting with the Unrevoked tool.
Then use Rom Manager to flash a newer Recovery (be sure to check Erase Previous Recovery under Settings). If that still doesn't work, I'll see about packaging an RUU in a PB31IMG.zip with a valid version of CWM as the recovery.img within that zip. I'm not sure about the practicality of this final option, but if it comes down to it, I'll attempt to package that up for you.
This sounds incredibly frustrating. Thus my interest in the matter.
There's gotta be a way to fix this... even if it's just long enough to get S-On and keep your warranty valid.
Sent via my Incredible CM7 Gingerbread sorcery.
Crans said:
I wonder if he could just wipe that SD card, place a new Rom etc on it and reinstall. Bricking displays no response you've got a better shot at recovering course your SD card/battery could be bad
Click to expand...
Click to collapse
This would work if he could access CWM Recovery, but he can't, thus the issue.
I wonder if he could mount something from within hboot and replace the binary code for the recovery image with a bunch of zeroes and then try flashing another through hboot again.
Sent via my Incredible CM7 Gingerbread sorcery.
I was JUST about to post the same topic when I came across this. I have done the stock image restore, restored BACK to hboot 0.92, back to the most current INC radio, and have tried flashing CW3.0 and Amon_RA. Everything flashes fine but the boot loop continues and if I try to enter recovery, it lasts maybe one full second before rebooting again. The only thing that I can think of that would create this situation for me was that earlier I was trying to update the PRL via *228 on MIUI but the dialpad never popped up so I hung up.
popasmurfn23 said:
So i suggest you take phazeones link and try that file.Because u might have the incorrect file. There might be more than meets the eye make sure u got the right file.
When i searched for my zip file for my evo there was like 4 of them. They had to match what was said in the upper left corner of my hboot screen. So let me knoe if it worked
Click to expand...
Click to collapse
I'll take another crack at it, but I don't think I had gotten the wrong image. No worries though, it's easy enough to try again using the link on page 1 directly. Can't hurt, right ;-)
RegnierD said:
Since you're trying to flash the 3.x.x.x version of CWM, that may be your issue. Here's a zip for 2.5.0.5, one of the most stable earlier Recoveries. Flash through hboot as per usual.
Click to expand...
Click to collapse
Sure. Once again, worth a shot.
RegnierD said:
This sounds incredibly frustrating. Thus my interest in the matter.
There's gotta be a way to fix this... even if it's just long enough to get S-On and keep your warranty valid.
Click to expand...
Click to collapse
Thanks for the sympathy . Like I mentioned, I visited the Verizon store and a new one is on its way... doesn't that mean that it doesn't matter (other than for science sake) whether this gets S-On or even fixed?
[waiting for flash of build-3.26.605.1-release-152016-baseband-2.15.00.07.28-hboot-0.92.0000_PB31IMG.zip]
It just seems unlikely that this is a problem with flashing the wrong recovery, or the wrong stock image, since booting into recovery and booting normally both exhibit the same behavior. If I could boot normally into recovery but not boot into a stock image, I would suspect that I had flashed the wrong image. Since both have the same problem, I think it might be something else.
[finished flashing build-3.26.605.1-release-152016-baseband-2.15.00.07.28-hboot-0.92.0000_PB31IMG.zip]
Same behavior. White htc Incredible splash screen -> darkness for a second (presumably while the ROM tries to boot) -> reboot.
Alternatively, HBOOT -> Recovery -> White htc Incredible screen -> Triangle / ! error screen for a half second -> reboot.
[finished flashing CWM 2.5.0.5]
Same behavior:
HBOOT -> Recovery -> White htc Incredible screen -> CWM recovery 2.5.0.5 for a half second (this confirms that it flashed properly) -> reboot.

[Q] Unrooted phone having problems?

Ok I need some help, I unrooted my phone because I had to take into sprint to get a new screen. The problem is this. After unrooting the Evo it constantly reboots itself and on top of that it will not recognize the SD card. Any ideas on how to fix this.
First, being that the phone is no longer rooted, take it to Sprint and have them troubleshoot it. If you don't want to do that, you can try booting into recovery to see if the card will mount there.
dougjamal said:
First, being that the phone is no longer rooted, take it to Sprint and have them troubleshoot it. If you don't want to do that, you can try booting into recovery to see if the card will mount there.
Click to expand...
Click to collapse
If the phone is *properly* unrooted (s-on zip, RUU) there shouldn't be a recovery to boot into.
OP, did you unroot the way I mentioned?
(from... Evo/MIUI/Tapatalk)
plainjane said:
If the phone is *properly* unrooted (s-on zip, RUU) there shouldn't be a recovery to boot into.
OP, did you unroot the way I mentioned?
(from... Evo/MIUI/Tapatalk)
Click to expand...
Click to collapse
I was under the impression that there is a stock recovery.
dougjamal said:
I was under the impression that there is a stock recovery.
Click to expand...
Click to collapse
From what I understand, the stock recovery is no recovery. On a brand new not rooted phone, if you try to go into recovery, you get the black screen with red triangle.
At least that's what I've always heard. The Evo I had before this one was freaking out - it had never been rooted. I went into the bootloader to clear storage and out of curiosity chose recovery afterwards. I got the no recovery screen.
Running the RUU should give you the same result.
(from... Evo/MIUI/Tapatalk)
plainjane said:
From what I understand, the stock recovery is no recovery. On a brand new not rooted phone, if you try to go into recovery, you get the black screen with red triangle.
At least that's what I've always heard. The Evo I had before this one was freaking out - it had never been rooted. I went into the bootloader to clear storage and out of curiosity chose recovery afterwards. I got the no recovery screen.
Running the RUU should give you the same result.
(from... Evo/MIUI/Tapatalk)
Click to expand...
Click to collapse
Oh Okay. Thanks for clearing that up for me. Take care, my friend...
Thanks for the info, I did unroot it the way you mentioned in the thread. And it is unrooted the s zip is on and when I try to get into recovery I do get the red triangle warning. So I guess my best bet is to take it to Sprint. Is there a way to root the phone thru bootloader or do I have to have the phone turned on to root it. As far as the SD card issue any ideas.
killwrath said:
Thanks for the info, I did unroot it the way you mentioned in the thread. And it is unrooted the s zip is on and when I try to get into recovery I do get the red triangle warning. So I guess my best bet is to take it to Sprint. Is there a way to root the phone thru bootloader or do I have to have the phone turned on to root it. As far as the SD card issue any ideas.
Click to expand...
Click to collapse
so you didnt run an RUU? Did you just flash a PC36IMG.zip from the bootloader? The problem with that method is that you dont know what all was in the zip, or if it included everything. Theres a lot of PC36IMG.zip's out there that all serve different purposes. Go download the official RUU on your computer, plug your phone in and boot into fastboot (or just bootloader, not sure), wait for the process to finish, and your phone will be back to stock 100% no matter what. This is what sprint will do to restore a phone, so its official.
Ok one more quick question, how do I get my computer to recognize my phone after I plug it in. I found the official RUU and when I plugged my phone in and booted to bootloader the computer did not find it. As a result running the RUU did nothing. I went thru all the warning screens and then when it was searching for the phone and then gave me a warning that no phone was connected. So if I could get the phone connected to the computer then I am sure I can run the RUU and see if that helps. Any ideas?
killwrath said:
Ok one more quick question, how do I get my computer to recognize my phone after I plug it in. I found the official RUU and when I plugged my phone in and booted to bootloader the computer did not find it. As a result running the RUU did nothing. I went thru all the warning screens and then when it was searching for the phone and then gave me a warning that no phone was connected. So if I could get the phone connected to the computer then I am sure I can run the RUU and see if that helps. Any ideas?
Click to expand...
Click to collapse
check my guide have a link to the ruu you need just place it PC36IMG.ZIP on SD card and run get into boot loader mode and there you go.
Ok the phone wins. It is going back to sprint to see what they can do. All of your suggestions have been great, thanks for them. I just cant get the computer to recognize the phone when its plugged in. And the phone cant detect the SD card even in bootloader. And it will only charge when its is turned off. DAMN YOU TECHNOLOGY!!! hahahaha
Again thanks a ton for all your help. Warms the heart to know there are lots of fellow phone hackers willing to help out.
First thing is Thank You Everyone for all your help and suggestions.
Here is the update. The phone won and I had to take it to Sprint. And much to my suprise and honestly relief, they could not get the software reinstalled, it was stuck in a boot cycle is what they said. Ok if you say so. So they are going to send me a new phone. WOO HOO!!!!!
Thanks again for everything. Guess I get to try out Auto Root this time.
Yeah Rooting.

[Q] Evo Rooting failed? Please help now on restarting loop

Hey guys,
I tried to root my my evo 4g with the instructions from the sticky and when I started the autoroot file as it said, it would get to found root then establishing something and the cmd would close out and my phone would stay in the bootloader mode. Instructions said to go to recovery if it didn't continue and I did go into recovery and all it gave me was a black screen with the red triangle and nothing was happening so I pulled out the battery to restart the phone. Now my phone boots up normally and it just freezes up after maybe 30 seconds of use everytime and just reboots and it repeats over and over again nonstop. It won't be recognized by my computers and it just says unidentified with the CDMA drivers not working and the phone does not recognize the SD card when its running and booted up. Please help if you guys know what I could do to make it stop restarting. Thanks in advance!
Try re-rooting via unrevoked. Click on unrevoked in my signature and follow the directions, but first, boot into the bootloader screen (after shutting off the device, simultaneously press the DOWN volume button and the power button until the device starts). Look at the top of the screen and see if it displays "S-OFF". If it does, great, you're rooted, bit if it displays "S-ON" then follow the rooting method of unrevoked or retry the method you used. If it does indeed display "S-OFF", I suggest you flash a custom recovery like amon_RA.
posting & replying via the XDA Premium app.
Well I can't do that since it won't recognize the phone through USB or recognize the SD card
Update: I just flashed my evo with the stock 3.70.651.1 rom using a card reader putting the PC36IM something file on the SD card and used bootloader to flash and It's still not recognizing the SD card and it's still freezing up 1 minute after it has booted up and restarts and repeats the loop.
I sorta have a similar problem. I have a rooted evo running CM7 .
trying to use HDMI cable with a 1080p vizio LCD TV. Nothing happens. Does CM7 support the HDMI video out.
Sent from my PC36100 using XDA Premium App
SprintTouchPro2 said:
Hey guys,
I tried to root my my evo 4g with the instructions from the sticky and when I started the autoroot file as it said, it would get to found root then establishing something and the cmd would close out and my phone would stay in the bootloader mode. Instructions said to go to recovery if it didn't continue and I did go into recovery and all it gave me was a black screen with the red triangle and nothing was happening so I pulled out the battery to restart the phone. Now my phone boots up normally and it just freezes up after maybe 30 seconds of use everytime and just reboots and it repeats over and over again nonstop. It won't be recognized by my computers and it just says unidentified with the CDMA drivers not working and the phone does not recognize the SD card when its running and booted up. Please help if you guys know what I could do to make it stop restarting. Thanks in advance!
Click to expand...
Click to collapse
can you send me the autorootlog.txt file? that should show what happened to it. And def don't try rooting it with anything else while the phone is in an inconsistent state, that is just asking to corrupt it.
Use unrevoked 3 my guide has all you need links and so on
I like unrevoked 3 easy to root and unroot . All the other programs that work for rooting can make unrooting a pain in the butt. Do what you want you want .
You don't have a recovery installed that's why you get black screen and triangles . Use amon 2.3
reaper24 said:
Use unrevoked 3 my guide has all you need links and so on
I like unrevoked 3 easy to root and unroot . All the other programs that work for rooting can make unrooting a pain in the butt. Do what you want you want .
Click to expand...
Click to collapse
how is unrooting different?
xHausx said:
how is unrooting different?
Click to expand...
Click to collapse
I'm not going to war with you on that man just saying turn s off flash a stock Ruu the latest and your good to go. Trying to find a auto or one click unrooting program to unroot can be a pain to do if your h boot is to new or old .
I'm sure your way is good I just prefer unrevoked 3 is all. Not dogging your root way. Just familiar with unrevoked 3 use it to root everyone's phone I know.
reaper24 said:
I'm not going to war with you on that man just saying turn s off flash a stock Ruu the latest and your good to go. Trying to find a auto or one click unrooting program to unroot can be a pain to do if your h boot is to new or old .
I'm sure your way is good I just prefer unrevoked 3 is all. Not dogging your root way. Just familiar with unrevoked 3 use it to root everyone's phone I know.
Click to expand...
Click to collapse
Well you're saying there's a difference in how you have to unroot when it's not true. Or at least that I know of, if there is I'm curious as to how.
Autoroot will try to downgrade the hboot to the unlocked engineering leak, if successful it's finished and all you have to do to unroot is run the RUU. If it's unable to downgrade the hboot it will bring up the stock recovery and use unrevoked forever to unlock the nand; when this is used you have to flash the s-on tool (that is left on the sdcard as URFSOn.zip) and then flash the RUU to unroot.
Unrevoked 3 breaks in through the hboot and unlocks the nand through the radio, so you will also have to use the s-on tool and flash the RUU.
You're also telling him to keep trying to root when his phone is obviously in a weird state, that's bad advice unless you want him to end up bricked like a ton of people did when the latest firmware came out.
xHausx said:
Well you're saying there's a difference in how you have to unroot when it's not true. Or at least that I know of, if there is I'm curious as to how.
Autoroot will try to downgrade the hboot to the unlocked engineering leak, if successful it's finished and all you have to do to unroot is run the RUU. If it's unable to downgrade the hboot it will bring up the stock recovery and use unrevoked forever to unlock the nand; when this is used you have to flash the s-on tool (that is left on the sdcard as URFSOn.zip) and then flash the RUU to unroot.
Unrevoked 3 breaks in through the hboot and unlocks the nand through the radio, so you will also have to use the s-on tool and flash the RUU.
You're also telling him to keep trying to root when his phone is obviously in a weird state, that's bad advice unless you want him to end up bricked like a ton of people did when the latest firmware came out.
Click to expand...
Click to collapse
no I'm not telling him to brick his phone. He doesn't have a recovery on his phone that is what he needs . Just saying if he does end up rerooting at some point he can try unrevoked 3 just a suggestion. My advice isn't bad not new to rooting or flashing. Pretty good at trouble shooting .
Well how do I get a recovery? I thought I have one since I have the option to go there? Gives me a red triangle with a phone under it. Once i mash the volume up and down and power button at the same time and hold it in for a bit a menu pops up to update from SD card or to clear storage and some other options. But anyway I reflashed the stock rom from bootloader and it's still doing the freeze after 30 seconds of use and restarts over and over again. So how do I actually get recovery and what do I do after that to make this stupid restarting of my phone to stop.
SprintTouchPro2 said:
Well how do I get a recovery? I thought I have one since I have the option to go there? Gives me a red triangle with a phone under it. Once i mash the volume up and down and power button at the same time and hold it in for a bit a menu pops up to update from SD card or to clear storage and some other options. But anyway I reflashed the stock rom from bootloader and it's still doing the freeze after 30 seconds of use and restarts over and over again. So how do I actually get recovery and what do I do after that to make this stupid restarting of my phone to stop.
Click to expand...
Click to collapse
I'll need to take a look at your autorootlog.txt file in order to find out what's up with your phone. It should be in the autoroot folder and you can post it by using the 'manage attachments' button, if it doesn't want to let you for some reason you can also email it to me.
edit: odds are you're phone is still locked but it won't hurt to try flashing the recovery, all you have to do to flash it is run the FlashZip script that came with AutoRoot and select the one that says Amon RA - hausmod. That's if it's unlocked of course, if it says s-on or that the security is still on then your phone will reject it.
There you go, there is my autorootlog
I'm not too worried about this as I took the phone to sprint and they ordered me a new phone since they didn't know what was wrong with it and I'll get it today or tomorrow but I just want to figure out what went wrong so that I know what to do if I am to root my new phone..cause this autoroot I used on this website messed up and I followed every step perfectly.

Noob Gets Greedy, Consequences Follow

Hey guys, New here. I attempted to download the new Sense 3.0 ROM (I forgot the proper title for it) directly to my Supersonic and I flashed the ROM properly and backed up beforehand. When I went to reboot the phone to start up the ROM The HTC EVO screen appears and then afterwards the screen went black and the phone vibrated about 6 times with the status light flashing green occasionally. I couldn't do anything with the phone except put into recovery mode. I attempted to recover the previous ROM (CM7 Stable Build) but it doesnt pick up my SD Card either! Sometimes I cant even access the Recovery menu only the bootloader!
Help would be greatly appreciated!
Thanks, Supersonic600
If u can get to bootloader, try to ruu back to stock
Sent from the bowels of my mind....
Dredge said:
If u can get to bootloader, try to ruu back to stock
Sent from the bowels of my mind....
Click to expand...
Click to collapse
2.2 stock, or a rooted 2.3. Don't RUU to 2.3 or you'll lose root.
I downloaded the RUU and it would load PC36IMG and then stop doing so after it said "Parsing PC36IMG" and go back to the main bootloader screen. Now after tampering with it a little more, I can't access Recovery mode. Any other possible downloads I could do?
SilverZero said:
2.2 stock, or a rooted 2.3. Don't RUU to 2.3 or you'll lose root.
Click to expand...
Click to collapse
I agree, if you used the new RUU with 2.3, HTC has locked down recovery mode and removed root. The six vibrations and a blinking green light are, in my experience, indicitive of a temperature issue, or something internal preventing your phone from turning on properly. It does this to keep from damaging itself when it turns on. The only way to turn the phone on after that is to pull the battery.

[Q] OMG! Accidentally Formatted system data!

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!

Categories

Resources