Related
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).
i used unrevoked3 to root my phone and i never did anything to the phone. no custom roms or anything. Im on Android 2.2 and i used this technique to unroot youtube.com/watch?v=irOD_Kho-Ks and now my phone wont come on. Please help or am i screwed? im a noob to this stuff
You're not entirely screwed. I'm going to say you have an SLCD incredible, and the one in the video is an AMOLED device on 2.1. The RUU you flashed was for 2.1 and the older hboot and radio. Made for the AMOLED. The SLCD is different and so you can't see the screen now. You will need to flash a new RUU.
Here is an SLCD compatible RUU: http://dougpiston.com/files/RUU/bui...and-2.15.00.07.28-hboot-0.92.0000_PB31IMG.zip
Rename PB31IMG.zip on root of SD card.
You will have to flash it blind though. So make sure it's charged. Then boot into hboot (Vol + PWR DWN) and wait a few minutes for it to recognize the zip. Then you should be able to press VOL+UP. And this will take a while. Say 5-10 minutes.
Then you should be able to press VOL+UP again, and it will reboot into stock 2.2.
EDIT: And you will need to use a Micro SDHC card reader to put the file on the card. Because you can't see the phone to mount it through USB.
black screen
ok so i question i rooted my phone and installed ultimate droid on it. ran ok but i decided i wanted to go back to stock. i installed a different radio and now my phone turns on but i can't see anything. the screen is black my pc (running windows 7) only reads as a mass storage device for my phone but will not open up as well.Is there any help for me? i can't even boot in hboot
scoobntaz1996 said:
ok so i question i rooted my phone and installed ultimate droid on it. ran ok but i decided i wanted to go back to stock. i installed a different radio and now my phone turns on but i can't see anything. the screen is black my pc (running windows 7) only reads as a mass storage device for my phone but will not open up as well.Is there any help for me? i can't even boot in hboot
Click to expand...
Click to collapse
Try what Brett suggested above....
Sent from my ADR6300 using XDA App
So..... Did anyone get it to work?
its really hard. no luck yet. i dot know how long to wait for everything. i formatted my sd card then put the .zip on there. hopefully it worls
paulwoods1114 said:
its really hard. no luck yet. i dot know how long to wait for everything. i formatted my sd card then put the .zip on there. hopefully it worls
Click to expand...
Click to collapse
THANKS!!!! BRett you saved me about 200 hundred dollars.
brett thank you so much
I was having this issue led would light up phone would vibrate when powering on just no picture thus i did this blind and worked like a gem thank you so much as i am selling this phone and thought i had bricked it before i could ever see any money back from it so thank you much man i owe ya one
hey guys i am having an issue with my gf new evo i bought from craigslist and i am hoping its something software based so i can fix it....so here is the details....
My gf recently lost her evo and no insurance so i went on to craigslist to buy one so when i get the phone it looks nice...legit you know....so anyways i get home and get to craking....so when i started first thing i did was opened the recovery and to my suprise the evo S-off and i was like wahhhttt....anyways so i proceded to rooting it with UnrEVOked and did everthing great so i decided to flash the old rom she had on her old phone cause she liked it so i did and short story long got her phone back to normal...until recently the phonw will randomly reboot when were using it with phone calls or NAV or just music or to many things at once and full battery and will reboot try to turn on then ....IT VIBRATES 4...5 times and shuts off and the LED blinks green every second.....the only way i could turn it on is taking the batter off for a few minutes then reinserting batter and BOOM back on like nothing happend....so i need so help please....did a full wipe of everything and reinstalled rom and nothing....OHHH and it came with stock batter and two non stock!!... PLEASE HELP SHES NAGGING TO MUCH LOL
I don't know for sure but I've read that changing your kernel might fix it
Sent from my PC36100 using XDA App
KaL-EL3038 said:
hey guys i am having an issue with my gf new evo i bought from craigslist and i am hoping its something software based so i can fix it....so here is the details....
My gf recently lost her evo and no insurance so i went on to craigslist to buy one so when i get the phone it looks nice...legit you know....so anyways i get home and get to craking....so when i started first thing i did was opened the recovery and to my suprise the evo S-off and i was like wahhhttt....anyways so i proceded to rooting it with UnrEVOked and did everthing great so i decided to flash the old rom she had on her old phone cause she liked it so i did and short story long got her phone back to normal...until recently the phonw will randomly reboot when were using it with phone calls or NAV or just music or to many things at once and full battery and will reboot try to turn on then ....IT VIBRATES 4...5 times and shuts off and the LED blinks green every second.....the only way i could turn it on is taking the batter off for a few minutes then reinserting batter and BOOM back on like nothing happend....so i need so help please....did a full wipe of everything and reinstalled rom and nothing....OHHH and it came with stock batter and two non stock!!... PLEASE HELP SHES NAGGING TO MUCH LOL
Click to expand...
Click to collapse
Hmm. Any time I ever see anyone reporting what you're describing, I've never seen a solution. What I would try though, is to unroot it, by turning S back to On, and then running an RUU. See if it will run stable while on a stock ROM. If so, try rooting again. If it is still doing the same thing after running RUU, with S on, I would take it Sprint. The phone is still under warranty, and if it turns out to be hardware related, you should be able to have Sprint do something for you.
RUU: http://forum.xda-developers.com/showthread.php?t=884060&highlight=hboot-0.97+ruu
I also attatched the Unrevoked S on tool. Flash the Unrevoked S on tool in recovery. Confirm that S is on. (what bootloader are you on? If its the Eng .76 bootloader, you don't need the S on tool, in which case you'd just run the RUU). Once S is on, run the RUU, to flash you back to stock. You want to run the RUU that matches your bootloader version, software version, and radio versions the closest. That will take you back to stock, and then you can see how the phone performs.
And it kind of sounds like the phone may have had some issues before. It was obviously rooted, since it was already S off when you purchased it. Who knows what type of issues it had prior to you obtaining it..
Thanks so much!!!
k2buckley said:
Hmm. Any time I ever see anyone reporting what you're describing, I've never seen a solution. What I would try though, is to unroot it, by turning S back to On, and then running an RUU. See if it will run stable while on a stock ROM. If so, try rooting again. If it is still doing the same thing after running RUU, with S on, I would take it Sprint. The phone is still under warranty, and if it turns out to be hardware related, you should be able to have Sprint do something for you.
RUU: http://forum.xda-developers.com/showthread.php?t=884060&highlight=hboot-0.97+ruu
I also attatched the Unrevoked S on tool. Flash the Unrevoked S on tool in recovery. Confirm that S is on. (what bootloader are you on? If its the Eng .76 bootloader, you don't need the S on tool, in which case you'd just run the RUU). Once S is on, run the RUU, to flash you back to stock. You want to run the RUU that matches your bootloader version, software version, and radio versions the closest. That will take you back to stock, and then you can see how the phone performs.
And it kind of sounds like the phone may have had some issues before. It was obviously rooted, since it was already S off when you purchased it. Who knows what type of issues it had prior to you obtaining it..
Click to expand...
Click to collapse
Mohawka said:
I don't know for sure but I've read that changing your kernel might fix it
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
ok well thanks so much for your guys help...i take it there has been many reports before regarding this i was thinking it was the BATTERYS and my second gues was the kernel lol hahah so ill try the kernel first if you think that will help k2buckley and then ill will go all out i am not sure which booatloader i have cause i am using wifi tether to write this but as soon as i found out ill report back and again thanks so much
KaL-EL3038 said:
ok well thanks so much for your guys help...i take it there has been many reports before regarding this i was thinking it was the BATTERYS and my second gues was the kernel lol hahah so ill try the kernel first if you think that will help k2buckley and then ill will go all out i am not sure which booatloader i have cause i am using wifi tether to write this but as soon as i found out ill report back and again thanks so much
Click to expand...
Click to collapse
I don't suspect that changing the kernel will have any affect on your situation. Sometimes a kernel can cause the phone to reboot, but your phone isn't just rebooting. I believe that the 5 vibrates, followed by a black screen and a blinking led, means that the phone is pushing itself into diagnositc mode, for whatever reason. I am not sure what causes this. The only way to get out is to pull the battery out, and i believe you need to eithe be sure you're usb cable is unplugged (or is it be sure that it's plugged in..... I don't recall) Then reboot. Sorry I don't remember the exact specifics, as I've never had to do it, but I've seen it mentioned around here. If you search xHausx's posts, I know he has given instructions on how to attempt recovering from that situation a few times, but I don't usually see it successful, and people end up attempting to run an RUU, if you can keep the phone on long enough. If you do resort to running the RUU, I'd try running it from fastboot mode, which you select from the bootloader.
thanks again
k2buckley said:
I don't suspect that changing the kernel will have any affect on your situation. Sometimes a kernel can cause the phone to reboot, but your phone isn't just rebooting. I believe that the 5 vibrates, followed by a black screen and a blinking led, means that the phone is pushing itself into diagnositc mode, for whatever reason. I am not sure what causes this. The only way to get out is to pull the battery out, and i believe you need to eithe be sure you're usb cable is unplugged (or is it be sure that it's plugged in..... I don't recall) Then reboot. Sorry I don't remember the exact specifics, as I've never had to do it, but I've seen it mentioned around here. If you search xHausx's posts, I know he has given instructions on how to attempt recovering from that situation a few times, but I don't usually see it successful, and people end up attempting to run an RUU, if you can keep the phone on long enough. If you do resort to running the RUU, I'd try running it from fastboot mode, which you select from the bootloader.
Click to expand...
Click to collapse
thanks alot man i gladly appreciate it i see there is other threads going on about this some all which are somewhat the same and some that are exactly the same i am experiencing....so i will take the RUU as my last step if that does not work what else can i do....insurance claim right??? oh and i am having dificulty on choosing the right pcimg or ruu ive never had to do this before so i dont know which one to chosse out of all the ones in the thread you posted?
KaL-EL3038 said:
thanks alot man i gladly appreciate it i see there is other threads going on about this some all which are somewhat the same and some that are exactly the same i am experiencing....so i will take the RUU as my last step if that does not work what else can i do....insurance claim right??? oh and i am having dificulty on choosing the right pcimg or ruu ive never had to do this before so i dont know which one to chosse out of all the ones in the thread you posted?
Click to expand...
Click to collapse
You said you can still get to the OS for a limited amount of time right? See if you can get to menu>settings>about phone>software information. Get all the info there, (PRI, Baseband/radio, Software version (3.70? 3.30?, etc) Just record everything on that page down. Then boot to your bootloader. What's the hboot version? (2.02, 2.10, .97, .93, .76, etc etc.) Report back with that info. Most likely though, you'll need to run the most recent one (first on the page in that thread I sent you, which is 3.70 software)
k2buckley said:
You said you can still get to the OS for a limited amount of time right? See if you can get to menu>settings>about phone>software information. Get all the info there, (PRI, Baseband/radio, Software version (3.70? 3.30?, etc) Just record everything on that page down. Then boot to your bootloader. What's the hboot version? (2.02, 2.10, .97, .93, .76, etc etc.) Report back with that info. Most likely though, you'll need to run the most recent one (first on the page in that thread I sent you, which is 3.70 software)
Click to expand...
Click to collapse
yeah u see i am able to keep the phone one for a while....like example yesterday i was using it to tether to my PS3 no problem but when i open like a new app or sometimes even a phone call it reboots at first i thought it was like the batteries were over heating but now that ive seen this happen to other people i see that not the case...so back to the point here is the info
Baseband-2.15.00.11.19
kernel-2.6.32.17 -gee557fd/[email protected]#15
build- Myns TwoPointTwo rls5
Software Version-3.70.651.1
Webkit-3.1
PRI version-1.90_003
PRL version-60677
Hardware version-0003
HBOOT-0.93.0000
Radio-2.15.00.11.19
and there you go that all i need to get right?
KaL-EL3038 said:
yeah u see i am able to keep the phone one for a while....like example yesterday i was using it to tether to my PS3 no problem but when i open like a new app or sometimes even a phone call it reboots at first i thought it was like the batteries were over heating but now that ive seen this happen to other people i see that not the case...so back to the point here is the info
Baseband-2.15.00.11.19
kernel-2.6.32.17 -gee557fd/[email protected]-2#15
build- Myns TwoPointTwo rls5
Software Version-3.70.651.1
Webkit-3.1
PRI version-1.90_003
PRL version-60677
Hardware version-0003
HBOOT-0.93.0000
Radio-2.15.00.11.19
and there you go that all i need to get right?
Click to expand...
Click to collapse
Yup. That's all. Your software and radios are the latest, but your hboot isn't. I would try the newest 3.70 RUU first. If that gives you any trouble, try the 3.30 RUU, or even 3.29. Its just because your hboot is older that I'm not a hundred percent sure.
Sent from my PC36100 using XDA App
k2buckley said:
Yup. That's all. Your software and radios are the latest, but your hboot isn't. I would try the newest 3.70 RUU first. If that gives you any trouble, try the 3.30 RUU, or even 3.29. Its just because your hboot is older that I'm not a hundred percent sure.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
so do i just download the RUU and not the pcimg??? or both??
KaL-EL3038 said:
so do i just download the RUU and not the pcimg??? or both??
Click to expand...
Click to collapse
Either one you want. They are two separate methods of running the RUU. If you download the actual RUU, it's a .exe that runs from your computer, while the phone is plugged in Via USB. You need HTC Sync installed to run the RUU.
PC36IMG, is a file that you put on your sd card, and then boot to your bootloader. If the PC36IMG is on the main directory of your sd card, and it's named exactly PC36IMG, then when you boot to the bootloader, it will prompt you to update after a few seconds. Just wait for it to ask, then select volume up to say yes. That will then run the 'ruu' from your phone. Either method will acheive the exact same results. Personally, I think it's easier to use the PC36IMG, but they are both easy to do.
k2buckley said:
Either one you want. They are two separate methods of running the RUU. If you download the actual RUU, it's a .exe that runs from your computer, while the phone is plugged in Via USB. You need HTC Sync installed to run the RUU.
PC36IMG, is a file that you put on your sd card, and then boot to your bootloader. If the PC36IMG is on the main directory of your sd card, and it's named exactly PC36IMG, then when you boot to the bootloader, it was prompt you to update after a few seconds. Just wait for it to ask, then select volume up to say yes. That will then run the 'ruu' from your phone. Either method will acheive the exact same results. Personally, I think it's easier to use the PC36IMG, but they are both easy to do.
Click to expand...
Click to collapse
yeah i think i will personally use the pc36img cause i dont want to mess with HTC sync i heard its a pain in the butt!! lol and thanks man i will report back to see what happends ok!
KaL-EL3038 said:
yeah i think i will personally use the pc36img cause i dont want to mess with HTC sync i heard its a pain in the butt!! lol and thanks man i will report back to see what happends ok!
Click to expand...
Click to collapse
cool, sounds good. And just don't forget to turn it back to S on, by flashing the unrevoked s on tool, before you run the RUU(or PC36IMG). Good luck with it!
k2buckley said:
cool, sounds good. And just don't forget to turn it back to S on, by flashing the unrevoked s on tool, before you run the RUU(or PC36IMG). Good luck with it!
Click to expand...
Click to collapse
ohhhh snap thanks man luckly i came back and read this also am i suppose to unzip the pcimg on to the root of my sdcard?
KaL-EL3038 said:
ohhhh snap thanks man luckly i came back and read this also am i suppose to unzip the pcimg on to the root of my sdcard?
Click to expand...
Click to collapse
No, just leave it as is, unzipped. Boot into the bootloader, let it scan, then apply the update and reboot, you'll be all set.
KaL-EL3038 said:
ohhhh snap thanks man luckly i came back and read this also am i suppose to unzip the pcimg on to the root of my sdcard?
Click to expand...
Click to collapse
And just to be more clear, you only need to run the Unrevoked S on tool if you have any point used Unrevoked-Forever. If you are on the .76 Eng Bootloader, you don't need to run it, in which case you'd just skip right to running the RUU.
Edit: And as teh roxx said, leave the PC36IMG zipped, and on the main directory of your sd card. Named exactly PC36IMG.
k2buckley said:
And just to be more clear, you only need to run the Unrevoked S on tool if you have any point used Unrevoked-Forever. If you are on the .76 Eng Bootloader, you don't need to run it, in which case you'd just skip right to running the RUU.
Edit: And as teh roxx said, leave the PC36IMG zipped, and on the main directory of your sd card. Named exactly PC36IMG.
Click to expand...
Click to collapse
thanks so much guys i will report back to see if this help ok and i have bootloader .96 so i think i have to run S-On tool..
Aye aye cappy, someone should be around.
Darn itttt
teh roxxorz said:
Aye aye cappy, someone should be around.
Click to expand...
Click to collapse
HUUHHHH ????? lol
KaL-EL3038 said:
thanks so much guys i will report back to see if this help ok and i have bootloader .96 so i think i have to run S-On tool..
Click to expand...
Click to collapse
On another note....Here are my results guys...
well ok first thing i did was format my sd card so i wouldnt run into any problems with that....then i continued to placing the zip file of S-ON tool on to the root of the sdcard Flashed it with clockwork and after it did its handy work i rebooted on to Bootloader and confirmed S-On.....so then i place the PC136img on the root of my sd card and it scanned it and i fallowed what told of me to do....so as soon it was done it asked me to reboot!!so as i clicked up to say yes it rebooted...now here is there the fun begins...when i first rebooted it went into a boot loop of turning on to HTC EVO screen then turning off And HTC EVO screen over and over again so it was turning on and off by itself....so i decided to reflash PC136 IMG all over again cause i thought something went wrong....so it completed everything again i rebooted and this time it did an HTC EVO Screen on and off thing again .....but this time i decided to take out the battery leave it out for a little and put it back on.....and as i was putting it back on i turned it on and this screen with a phone laying down with arrows going in a circle kind of like a recycle came on and stayed on so i took of the battery...and reflashed PC136 IMG again....so then i rebooted again and The darn HTC EVO screen on and off again.....so this time i took out battery again and waited for like five minutes...put it back on and the PHONE LAYING DOWN WITH ARROWS AGAIN CAME ON and i let it sit for a while and phone came on....so i was like YEAHHHHH worked welll after fully charging phone and trying to Repeat the same process i would do to get the PHONE OFF WITH ORANGE LIGHTS FLASHING....well that did not happen.....butttttttt HERE is the new thing it does the same process i would do to make that happen i do it again .....and to my suprise phone still turns off but this time its not PHONE ORANGE LIGHTS.....ITS HTC EVO SCREEN BOOT LOOP.....so now what guys.....
KaL-EL3038 said:
HUUHHHH ????? lol
On another note....Here are my results guys...
well ok first thing i did was format my sd card so i wouldnt run into any problems with that....then i continued to placing the zip file of S-ON tool on to the root of the sdcard Flashed it with clockwork and after it did its handy work i rebooted on to Bootloader and confirmed S-On.....so then i place the PC136img on the root of my sd card and it scanned it and i fallowed what told of me to do....so as soon it was done it asked me to reboot!!so as i clicked up to say yes it rebooted...now here is there the fun begins...when i first rebooted it went into a boot loop of turning on to HTC EVO screen then turning off And HTC EVO screen over and over again so it was turning on and off by itself....so i decided to reflash PC136 IMG all over again cause i thought something went wrong....so it completed everything again i rebooted and this time it did an HTC EVO Screen on and off thing again .....but this time i decided to take out the battery leave it out for a little and put it back on.....and as i was putting it back on i turned it on and this screen with a phone laying down with arrows going in a circle kind of like a recycle came on and stayed on so i took of the battery...and reflashed PC136 IMG again....so then i rebooted again and The darn HTC EVO screen on and off again.....so this time i took out battery again and waited for like five minutes...put it back on and the PHONE LAYING DOWN WITH ARROWS AGAIN CAME ON and i let it sit for a while and phone came on....so i was like YEAHHHHH worked welll after fully charging phone and trying to Repeat the same process i would do to get the PHONE OFF WITH ORANGE LIGHTS FLASHING....well that did not happen.....butttttttt HERE is the new thing it does the same process i would do to make that happen i do it again .....and to my suprise phone still turns off but this time its not PHONE ORANGE LIGHTS.....ITS HTC EVO SCREEN BOOT LOOP.....so now what guys.....
Click to expand...
Click to collapse
When the phone coming on with the arrows comes on, you need to let that finish. That's a part of the process of running the ruu/PC36IMG. When it comes to that screen, let it sit there for a bit (could be a few minutes), and don't pull the battery unless you're positive that it's stuck there.
Also, which RUU are you trying? I forget which one you went with. Perhaps try a different one as well. You may be having trouble due to the wrong RUU. Did you try downloading a different one yet?
Also, remember that there was something wrong with you're phone to begin with. It is entirely possible that there is some sort of hardware problem with it, since it was giving you the black screen with the blinking led before. The important thing here is that you got S on. That way you can at least take it in to Sprint, and not have to worry. Just be sure that if you take it in, to take your SD card out before taking it in, so they don't see any root related stuff on the card.
I've seen threads like this but not quite the same. I'm trying to help fix my bosses Evo. I have the MT4G, so it's similar; still HTC but I guess the rooting methods or different. I'm trying to help him unroot now to sell it, but he's bricked it pretty badly. The phone will only boot into the bootloader. I put the PC36IMG file on the sd card, and it seems to start to flash that then freezes after counting up to [9] WIMAX.
If any of this is familiar to you guys, I would appreciate very much some assistance. I can't get anywhere but the bootloader, and it starts doing its own thing right away, so I guess my options are to somehow adjust the SD card using my PC. Thoughts? Thanks guys!
80centjack said:
I've seen threads like this but not quite the same. I'm trying to help fix my bosses Evo. I have the MT4G, so it's similar; still HTC but I guess the rooting methods or different. I'm trying to help him unroot now to sell it, but he's bricked it pretty badly. The phone will only boot into the bootloader. I put the PC36IMG file on the sd card, and it seems to start to flash that then freezes after counting up to [9] WIMAX.
If any of this is familiar to you guys, I would appreciate very much some assistance. I can't get anywhere but the bootloader, and it starts doing its own thing right away, so I guess my options are to somehow adjust the SD card using my PC. Thoughts? Thanks guys!
Click to expand...
Click to collapse
What version is the bootloader showing?
It shows HBOOT-0.76.2000 with radio 2.15.00.09.01. Hopefully that's helpful. Thanks again!
80centjack said:
It shows HBOOT-0.76.2000 with radio 2.15.00.09.01. Hopefully that's helpful. Thanks again!
Click to expand...
Click to collapse
No big deal then, definitely not bricked...
Remove the SD Card from the phone, put the battery back in, boot back up to boot loader, plug the phone into the PC, (You might have to install HTC Sync for this) Then press the power button on the "FASTBOOT" option. Then run this exe: http://u.115.com/file/t541677279 <--- same link as the RUU EXE here: http://forum.xda-developers.com/showthread.php?t=874091&highlight=stock+ruu
It's the RUU for the 3.70 update for the phone. it will return it to stock, reload the entire phone to that update, which is 2.10 hboot, and 3.70 software.
That's great news. I'll try right when I get home from work and report back in a few hours. Thank you very much!
unknownforce beat me to it yeah do what he says and have you which pc36img file did you try the amon ra right?
Hmmm... it won't seem to respond to me pressing the power button to choose options. I know the power button isn't physically broken, since the phone still powers on using it. But I've got the files you linked to downloaded and on the sd card and HTC sync installed, when I boot up it begins loading then wants me to make a selection, but I can't make any adjustments.
Okay, I've gotten past that (I had the wrong file.) Now I have the correct file, but I'm back to where it pulls up a list of things like Bootloader, Radiom Boot, Recovery, System, etc... and ends with Wimax. Then it just stalls. Because it won't boot up HTC Sync doesn't recognize it. Any suggestions?
EDIT: Forgot to mention that this phone is not finding the PC36DIAG file. I don't know if that means anything... but several hours of trying and I'm feeling like giving up.
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!