Severe panic!!
I rooted my Desire which was running 2.2 Froyo on the O2 UK network using unrevoked and it worked fine without any issues. Custom recovery by ClockworkMod.
The next day I then decided i needed to turn S-off so found a guide and tried installing unrevoked forever from a zip on the root of the SD and i got 'installation aborted error 42'. Tried again the next day but before i got started i decided to give myself re-assurance that i wouldnt lose anything on the device so i entered recovery and chose restore.
Big mistake! My handset then rebooted and got to the O2 splash screen. It wont move from there. Pulled battery out and tried again. Same. I assume i havent bricked the device and it is just stuck in a boot loop?
Since then i have removed all my user data from the SD card and 'cleared storage'. Tried installing an miui rom and again 'installation aborted'.
Can anyone clarify why this is happening and point me in the right direction?
I am a noob and would appreciate any help on this.
TannyBhoy said:
Severe panic!!
I rooted my Desire which was running 2.2 Froyo on the O2 UK network using unrevoked and it worked fine without any issues. Custom recovery by ClockworkMod.
The next day I then decided i needed to turn S-off so found a guide and tried installing unrevoked forever from a zip on the root of the SD and i got 'installation aborted error 42'. Tried again the next day but before i got started i decided to give myself re-assurance that i wouldnt lose anything on the device so i entered recovery and chose restore.
Big mistake! My handset then rebooted and got to the O2 splash screen. It wont move from there. Pulled battery out and tried again. Same. I assume i havent bricked the device and it is just stuck in a boot loop?
Since then i have removed all my user data from the SD card and 'cleared storage'. Tried installing an miui rom and again 'installation aborted'.
Can anyone clarify why this is happening and point me in the right direction?
I am a noob and would appreciate any help on this.
Click to expand...
Click to collapse
Try to bring you phone to stock.
Download RUU .
Turn your phone on in fastboot (hold back button and press power - when your phone is off).
You have to have HTC Sync installed.
Run the exe file.
After that repeat the rooting and s-off-ing procedure.
Can the RUU be flashed in clockwork mod recovery or does it have to go through HTC Sync?
If it cannot be flashed in Clockwork Mod, I presume he has to
Connect phone via USB to PC,
boot into Fastboot as you mentioned
run HTC Sync
and then run the Ruu.exe file (does HTC Sync recognise this filetype and then do it's thing?)
And that's it? (Just that it seems too simple!)
OriginalThinking said:
Can the RUU be flashed in clockwork mod recovery or does it have to go through HTC Sync?
If it cannot be flashed in Clockwork Mod, I presume he has to
Connect phone via USB to PC,
boot into Fastboot as you mentioned
run HTC Sync
and then run the Ruu.exe file (does HTC Sync recognise this filetype and then do it's thing?)
And that's it? (Just that it seems too simple!)
Click to expand...
Click to collapse
You might need a goldcard. Try without one for now.
Right I'll let him know to give that a go. If it doesn't work I might pick your brains around the goldcard option.
Massive thanks so far for your advice!
Dude thanks for that. Im going to give that a bash and let you know how i get on!
Much appreciated!
Haven't tried this but it's worth giving it a shot. http://www.addictivetips.com/mobile...gold-card-for-htc-desire-without-hex-editing/
Or this: http://www.nazriawang.com/2010/04/how-to-create-goldcard-with-ubuntu.html
TannyBhoy said:
The next day I then decided i needed to turn S-off so found a guide and tried installing unrevoked forever from a zip on the root of the SD and i got 'installation aborted error 42'. Tried again the next day but before i got started i decided to give myself re-assurance that i wouldnt lose anything on the device so i entered recovery and chose restore.
Click to expand...
Click to collapse
Hello. I think you wanted to say you chose back-up, otherwise you couldn't have chosen the restore option since you don't have any restore points.
So if you hit back-up and your phone stuck in the boot loop it is normal. This is a problem because of the root and the fact that making a nandroid back-up will mess something in the NAND. But restoring the back-up you just made should resolve all the problems. I had the same issue and by only restoring the back-up I've just made got me working back, and still had the ROOT.
I don't think you need to run a RUU just for this.
UsManyDead said:
Hello. I think you wanted to say you chose back-up, otherwise you couldn't have chosen the restore option since you don't have any restore points.
Click to expand...
Click to collapse
I should have made clearer sorry. After i rooted successfully i entered recovery and hit backup option and it told me it had created a backup successfully. I had been using the phone as normal for another day before deciding to s-off and at that point i thought to 'test' my backup to make sure it had done it so i chose restore thinking anything i have downloaded on the phone since the back up will disappear and was expecting the restore to bring my phone back to the settings i had the previous day but the restore failed and thats when it got stuck in the boot loop.
Mine did the same thing except, instead of trying to s-off it just decided at one point that it felt like it, literally, I wasnt even using it at the time it was just charging. I did downloaded the stock ruu, it was linked earlier. Put it in fastboot, run the ruu and boom, however i did it on my goldcard, so make one if it doesnt work without it. Good luck.
paul.c said:
Try to bring you phone to stock.
Turn your phone on in fastboot (hold back button and press power - when your phone is off).
You have to have HTC Sync installed.
Run the exe file.
After that repeat the rooting and s-off-ing procedure.
Click to expand...
Click to collapse
BACK IN BUSINESS!! Dude you are the man! The RUU didnt install as it was a different boot version so from the site you suggested i used the Froyo version and its now working! Many thanks.
P.s. What's the easiest way to s-off? Also whats the correct way to create a complete back up restore point and then actually restore to that point without getting to this stage again?
paul.c said:
Try to bring you phone to stock.
Turn your phone on in fastboot (hold back button and press power - when your phone is off).
You have to have HTC Sync installed.
Run the exe file.
After that repeat the rooting and s-off-ing procedure.
Click to expand...
Click to collapse
BACK IN BUSINESS!! Dude you are the man! The RUU didnt install as it was a different boot version so from the site you suggested i used the Froyo version and its now working! Many thanks.
P.s. What's the easiest way to s-off? Also whats the correct way to create a complete back up restore point and then actually restore to that point without getting to this stage again?
TannyBhoy said:
BACK IN BUSINESS!! Dude you are the man! The RUU didnt install as it was a different boot version so from the site you suggested i used the Froyo version and its now working! Many thanks.
P.s. What's the easiest way to s-off? Also whats the correct way to create a complete back up restore point and then actually restore to that point without getting to this stage again?
Click to expand...
Click to collapse
Easiest way to s-off is alpharev:
http://alpharev.nl
***NEW ISSUE***
Since i have my phone back to it's original state and have lost root access. The idea is to root again via Unrevoked, which requires me to update the Android 1.0 driver (in device manager under other devices) to the Android Bootloader Interface. However, DM now does not say 'other devices - Android 1.0' and instead it says 'Android Devices - MY HTC'. So i decided to completely uninstall HTC Sync and all it's drivers and then rebooted PC, reinstalled SYNC and then uninstalled again but this time leaving the drivers in. Rebooted again and repeated the process but it still recognises the device as 'MY HTC' instead of 'Android 1.0'.
Could it be that this is fine, it's just the new way since i am using the updated version of HTC sync now? Or is this going to cause an issue? I am now playing it a lot safer to avoid anymore issues and quite happy to try something you may suggest...
TannyBhoy said:
***NEW ISSUE***
Since i have my phone back to it's original state and have lost root access. The idea is to root again via Unrevoked, which requires me to update the Android 1.0 driver (in device manager under other devices) to the Android Bootloader Interface. However, DM now does not say 'other devices - Android 1.0' and instead it says 'Android Devices - MY HTC'. So i decided to completely uninstall HTC Sync and all it's drivers and then rebooted PC, reinstalled SYNC and then uninstalled again but this time leaving the drivers in. Rebooted again and repeated the process but it still recognises the device as 'MY HTC' instead of 'Android 1.0'.
Could it be that this is fine, it's just the new way since i am using the updated version of HTC sync now? Or is this going to cause an issue? I am now playing it a lot safer to avoid anymore issues and quite happy to try something you may suggest...
Click to expand...
Click to collapse
Same here. But everything is working fine.
So put phone in usb debug mode and "only charge" mode, start abd, connect phone via usb to pc and type
Code:
adb devices
. If your desire's serial number is shown, everything is fine.
MatDrOiD said:
Same here. But everything is working fine.
So put phone in usb debug mode and "only charge" mode, start abd, connect phone via usb to pc and type
Code:
adb devices
. If your desire's serial number is shown, everything is fine.
Click to expand...
Click to collapse
Hey man thanks for the advice. If yours is working fine, ive no reason not to try it!
As i am a noob, can you clarify "start abd" ??
Also, type code "adb devices", where to type?
TannyBhoy said:
Hey man thanks for the advice. If yours is working fine, ive no reason not to try it!
As i am a noob, can you clarify "start abd" ??
Also, type code "adb devices", where to type?
Click to expand...
Click to collapse
To start adb issue: "adb start-server" command without the quotes
To stop it: "adb kill-server"
Here is the complete list: http://developer.android.com/guide/developing/tools/adb.html
TannyBhoy said:
***NEW ISSUE***
Since i have my phone back to it's original state and have lost root access. The idea is to root again via Unrevoked, which requires me to update the Android 1.0 driver (in device manager under other devices) to the Android Bootloader Interface. However, DM now does not say 'other devices - Android 1.0' and instead it says 'Android Devices - MY HTC'. So i decided to completely uninstall HTC Sync and all it's drivers and then rebooted PC, reinstalled SYNC and then uninstalled again but this time leaving the drivers in. Rebooted again and repeated the process but it still recognises the device as 'MY HTC' instead of 'Android 1.0'.
Could it be that this is fine, it's just the new way since i am using the updated version of HTC sync now? Or is this going to cause an issue? I am now playing it a lot safer to avoid anymore issues and quite happy to try something you may suggest...
Click to expand...
Click to collapse
Thanks for the suggestions surrounding ADB but i guess im too much of a noob for that part, it seems massively complicated, im sure it doesnt to you guys. Isnt there an easier way? Or considering my above quote, can i just assume that its all working fine and go ahead with the root or should it really need to have 'Android 1.0' in device manager?
Im pretty certain this all happened becuase the first time i rooted i had followed instructions and uninstalled HTC Sync (not the drivers) which had been on my system since i got the phone lat year. Since i had to reinstall to flash the RUU im certain its an updated version of HTC Sync thats causing this issue. But is it really an issue?
TannyBhoy said:
Hey man thanks for the advice. If yours is working fine, ive no reason not to try it!
As i am a noob, can you clarify "start abd" ??
Also, type code "adb devices", where to type?
Click to expand...
Click to collapse
Here you have a nice guide about adb:
http://androidforums.com/desire-all...fastboot-windows-updated-1st-june-2011-a.html
This should answer all your questions.
Related
Let me just start off by saying poop.
I've been reading up on these forums quite a lot, equipping myself with enough knowledge to get going on using this phone to its potential.
After the anticipation of getting my DHD, I went about rooting it. I used this guide: http://forum.xda-developers.com/showthread.php?t=841076.
Everything went fine without much trouble. I completed all the steps in rooting it and gaing SU access. Also installed the Clockwork Recovery mod without a hiccup. I went on to install the Android Revolution ROM and going through the guide I used a tool called: 'Easy Wipe Upgrade.'
After installing this zip, the phone reboot and it just refuses to budge. Stuck on the HTC splash screen.
I've held down the bottom volume button with power and it gets me into HBOOT. I've tried a variety of option such as factory resets and nothing seems to be working.
My luck and phones. Just have a very expensive brick now sitting on my desk. Ah
I'd appreciate any help I can get please. Thanks.
I managed to resolve it!
Just FYI. Mounted the USB (Which was hidden fairly deeply) I guess you don't look when you panic? I then dropped on the ROM and installed it and boot up took a while but voila, it worked!
Well done, I would go mental if I bricked my phone. That's why I am still just reading up rather than trying things.
Sent from my Desire HD using XDA App
in the exact same situation as you where Could you go into abit more detail how you resolved this? currently have no phone cheers
whats wrong with your phone mate
Just so you know, as long as you have access to the bootloader (can be stock bootloader with S-ON, doesn't matter), 99% of the time you can 'unbrick' your phone by installing a stock RUU (PD98IMG.zip method) which returns your phone to complete stock.
If you install the wrong RUU while ENG HBOOT S-OFF then you can potentially fudge up your phone for good (unless you have Radio S-OFF, then you are fine - just install the correct RUU).
So don't worry, because there is nearly always a way to go back to how your phone was before you started hacking it.
prank1 said:
Just so you know, as long as you have access to the bootloader (can be stock bootloader with S-ON, doesn't matter), 99% of the time you can 'unbrick' your phone by installing a stock RUU (PD98IMG.zip method) which returns your phone to complete stock.
If you install the wrong RUU while ENG HBOOT S-OFF then you can potentially fudge up your phone for good (unless you have Radio S-OFF, then you are fine - just install the correct RUU).
So don't worry, because there is nearly always a way to go back to how your phone was before you started hacking it.
Click to expand...
Click to collapse
Here is a link to the pd98img.zip method if anyone wants it for reference.
thanks for the replies got it fixed as explained above cheers
DarkShadowAy said:
I managed to resolve it!
Just FYI. Mounted the USB (Which was hidden fairly deeply) I guess you don't look when you panic? I then dropped on the ROM and installed it and boot up took a while but voila, it worked!
Click to expand...
Click to collapse
My DHD is not starting up after i have applied s-off tool and the orange led light is on without pluggin in , by mounting USB can cure my problem ??
PLEASE HELP !!
dr.m0x said:
Here is a link to the pd98img.zip method if anyone wants it for reference.
Click to expand...
Click to collapse
hey guys, hope u could help me out.. i tried this RD1945's method.. got an ruu file, renamed the ruu file, then i put it on my micro sd card using a reader, then i plug it back in my phone, run hboot, the hboot parsed the zip file which i renamed according to the steps.. after it parsed it brought me back to the fastboot, recovery, restore factory defaults menu, etc... which i then chose fastboot then reboot... it reboots but im still stuck at the htc white splash screen for some time now.. what am i doin wrong? does it take long to start? sorry im a noob can someone explain to me how its done properly?
agonize said:
hey guys, hope u could help me out.. i tried this RD1945's method.. got an ruu file, renamed the ruu file, then i put it on my micro sd card using a reader, then i plug it back in my phone, run hboot, the hboot parsed the zip file which i renamed according to the steps.. after it parsed it brought me back to the fastboot, recovery, restore factory defaults menu, etc... which i then chose fastboot then reboot... it reboots but im still stuck at the htc white splash screen for some time now.. what am i doin wrong? does it take long to start? sorry im a noob can someone explain to me how its done properly?
Click to expand...
Click to collapse
You are not supposed to rename the RUU file, rather you run the RUU file and then afterwards locate the ROM.zip file located in your temp folder. This ROM.zip file is meant to be renamed PD98IMG.zip, NOT the RUU file.
ok that was stupid of me.. ok will try to give it a go..
sorry if this sounds stupid to you again.. but, i just wana be sure.. its my first smartphone..
anyway, i run the ruu file on my pc, yeah? so then when i run it, it asks me to connect my dhd using the usb cable.. so i did... but it couldnt detect my phone.. thus, it couldnt continue it's setup.. ;-( thank you for helping out..
Make sure you install HTC Sync, it should also install all the DHD USB drivers needed.
hey, do you have any step by step guide on doing this? im afraid il do something wrong again and just risk messing up the phone even more..
i have htc sync and the htc drivers on my laptop but when i connect the usb plug to my phone and try to run the ruu.. it still gives me the prompt of no connection from the pc and android phone.. :-| what am i doing wrong? sorry...
thanks in advance for the any help!
i managed to get to the update part.. but now it prompts a 131 error message.. :-( help?
http://forum.xda-developers.com/showthread.php?t=841890
Did u have a Look here...this shows the method and its very self explanatory
OK i just got the evo 4g tried rooting it and failed during the bootloader check on the autorooter so i had to pull the battery and tried to run the ruu as stated in the autorooter tutorial and now i am getting error code 170 in the ruu i ran in compatibility i ran it also as an administrator and i have tried it in the recovery mode and still no connection tried adb devices and the serial number pops up but the ruu will not run because of the ec 170
You running windows? Try grabbing the htc sync drivers from their website. Error Code 170 is something like it cannot detect phone through usb or something.
i have tried this and still getting nothing i hold down the power and volume up rocker to go to hboot and try it from there and still get the error code...
is there a command to boot the phone so i can run the ruu ?
did you try going into fastboot from the bootloader screen to run the ruu?
adb to reboot into bootloader: adb reboot bootloader
otherwise you want to hold volume down and hit the power button while the phone is off
when i run the fastboot all it says is fast boot usb and then i run the ruu and it still gives me the error code 170
h_townesp785 said:
when i run the fastboot all it says is fast boot usb and then i run the ruu and it still gives me the error code 170
Click to expand...
Click to collapse
If you have the unrevoked drivers installed you have to uninstall then first. If not you made need to use a diff computer.
Your phone must show fastboot usb highlighted in red as well
Sent from my PC36100 using XDA App
can i run it through the golden card way by placing the ruu in my sd card root and running the update through bootloader ? or will this just damage the phone
h_townesp785 said:
can i run it through the golden card way by placing the ruu in my sd card root and running the update through bootloader ? or will this just damage the phone
Click to expand...
Click to collapse
You'll need to use the pc36img out of it to flash through the bootloader, those can be found in the autoroot thread as well
Sent from my PC36100 using XDA App
h_townesp785 said:
i have tried this and still getting nothing i hold down the power and volume up rocker to go to hboot and try it from there and still get the error code...
Click to expand...
Click to collapse
You're supposed to use volume down, volume up puts the phone in diagnostic mode and will start causing all kinds of trouble for you
Sent from my PC36100 using XDA App
so using the down will make the ruu work
h_townesp785 said:
so using the down will make the ruu work
Click to expand...
Click to collapse
Should, you will need it to show fastboot usb highlighted in red. Let it sit for a minute or so without the battery first though.
Sent from my PC36100 using XDA App
amazing just took three hours and a full computer overhaul lol but got it had to wipe computer took a nose dive with that and then got it back up and had to install the sdk all over again and finally got the drivers running after four tries and got the phone up and running with the ruu and power and volume DOWN lol thank you so much
much appreciated ive learned my lesson
h_townesp785 said:
amazing just took three hours and a full computer overhaul lol but got it had to wipe computer took a nose dive with that and then got it back up and had to install the sdk all over again and finally got the drivers running after four tries and got the phone up and running with the ruu and power and volume DOWN lol thank you so much
much appreciated ive learned my lesson
Click to expand...
Click to collapse
Glad you were able to finally get it to work, were you able to root properly afterward? Everything needed for adb is included so the sdk is not necessary for the script, some have said installing it can interfere with it but I made it on a computer that has the sdk installed without any problems.
Now that I was finally able to root my phone using the autoroot method and a few kind folks answering my rookie questions, I seem to have become even more confused!!
What exactly did the autoroot put on my phone? Obviously it is a "sense-like" ROM??
When it created the Nand backup, what exactly did it back up-- how it was AFTER it booted and completed the root process for the first time? ie, before I re-installed a few apps and threw a few widgets up
Also, I've downloaded ROM manager. I've read all over the place that it makes flashing ROMs very easy. I guess that is why I'm asking what the autoroot method did? When I click on "Download ROM" in ROM manager, it says I must have ClockworkMod Recovery installed before I continue and to install it through the ROM manager.
Seems like I read something about Clockwork not being good (no 4g???)
If all this is the case, then is ROM manager completely useless.
I feel like I'm missing something here. So when you stop laughing at me for being a clueless rookie, could somebody kindly help here!?!?
clowork rom mananger
clockwork works just fine for me when you in rom manager let it flash the latest version of clockwork for u and ull be just fine, the latest version backsup 4g. i been using it for months and flashed various roms and mods and never had one problem with it or using one of my nandroid backups. Just let rom manager refalsh the latest version. I wouldnt tell u nothing that isnt factual or i havent done
if this helps make sure you hit the thanks buttton
Hey everyone, I have tried almost everything and my camera is broken. The lens opens up but the picture is all purple and not clear. I need to unroot my phone so I can take it back to the sprint store but I do not know which is the best method to use. I saw the RUU and I tried it but it wont connect to my phone usb. The program will open and close on its own.. This is my phone software
2.2
Baseband version
2.15.00.11.19
stock kernel
Build Number
3.70.651.1
Thanks for any help!
Install HTC sync on your computer to get the correct drivers for you USB and then try rerunning the RUU.
http://www.shipped-roms.com/shipped/Supersonic/
Download the 3.70 version, boot the phone into fastboot, connect to pc, the run the RUU exe.
Go to youtube and search it. There are a bunch of good videos out there that walk you through exactly what you need to do
Sent from my Evo while i should be working
http://forum.xda-developers.com/search.php?searchid=61344039
thanks everyone, Im still trying to figure it out. Im looking thru the forum here and i am trying to download the "unrevoked-forever-son.zip" but i cant find where to download it. Do you guys know where I can download it? the link people post when i go to it, its a blank page
teh roxxorz said:
http://www.shipped-roms.com/shipped/Supersonic/
Download the 3.70 version, boot the phone into fastboot, connect to pc, the run the RUU exe.
Click to expand...
Click to collapse
+1 on this method, teh roxxorz and I have helped a few people with this in the past few days. However, I would add a few things to this list. If you still get the connection error completely close the ruu and reboot the bootloader from the fastboot menu a few times and then try the ruu again. If this does not work then completely close out of everything and reboot your computer and reboot your phone back into the fastboot and try again. It can take a few tries to get this to work, but I promise you it will. I have used this method 4 times on 3 different phones. Plus, it is the safest route out of any of the methods IMHO.
EVOandroid1 said:
thanks everyone, Im still trying to figure it out. Im looking thru the forum here and i am trying to download the "unrevoked-forever-son.zip" but i cant find where to download it. Do you guys know where I can download it? the link people post when i go to it, its a blank page
Click to expand...
Click to collapse
http://downloads.unrevoked.com/forever/current/unrevoked-forever-son.zip
Thank you everyone for the input! I am trying to run the RUU and its giving me the Error[170] USB connection error. I have the drivers updated. What do you think I can do? I also have S-off
I dont know what im doing wrong. In the youtube videos I been watching off of HTCEVOHACKS.com my ADB in control panel is called HTC BOOTLOADER.. in the videos under ADB its my "MY HTC" does it matter? I tried to install other drivers and it is always called htc bootloader. Does anyone know what the problem may be for me to be getting that error 170?
I'm not sure, but you have done the following:
-If on windows, installed the HBOOT drivers
-Installed and the un-installed HTC sync
-The phone is booted into the bootloader, select fastboot, THEN connect to pc and the run the RUU exe
?
I have never installed htc sync. I have a 64bit windows 7 pc
http://www.htc.com/us/support/evo-sprint/downloads/
You can download sync there. Install it, and then immediately un-install it, then try the process again.
thanks man, i will try that now. its taking forever to download
Yea, it can take a couple of minutes, depending on your connection, but hopefully this solves it.
It worked!! THANK YOU SO MUCH!!!!!!!! I also formatted my SD card. so does this mean I can take my phone back to sprint without them knowing i had it rooted? I only had 384MB free internal. Is that supposed to be like that? I also did a factory reset of my phone. My camera is still messed up tho. The picture is all purple and blue still
No problem man! And the memory is fine. And for the camera, just say it happened with the latest OTA
Edit: Also in the bootloader, you should be S-ON.
oh no!!!! i am still S-OFF in the bootloader!!!! nooooooooo!!!!! what does that mean?
http://unrevoked.com/rootwiki/doku.php/public/forever
Go down to the Q&A and then download and flash the S-ON tool.
so does that mean I have to reroot my phone? I dont understand. Do i have to hook up my phone to my pc and redo all that root stuff using unrevoked or do i just download these files and put them in the sd card and open them up thru rom manager and install them from the sd card?
Let me preface this by saying yes I know there are dozens if not more threads on boot loop problems. I have recovered from boot loops before. This is very different.
I rooted my incredible with unrevokedForever and had cyanogen 6 on it. Everything was fine until yesterday I woke up to it in a boot loop, but not the cyanogen boot animation, the white HTC Incredible screen. I can only get to HBOOT, once I try to enter recovery, use an update.zip, or anything after the HBOOT page it goes into its loop. Should I pursue the RUU and find a windows computer or will that not help me?
I think I may have to bite the bullet and buy a new phone. As obviously they will not replace an S-OFF phone. Any help is appreciated.
jenic said:
Let me preface this by saying yes I know there are dozens if not more threads on boot loop problems. I have recovered from boot loops before. This is very different.
I rooted my incredible with unrevokedForever and had cyanogen 6 on it. Everything was fine until yesterday I woke up to it in a boot loop, but not the cyanogen boot animation, the white HTC Incredible screen. I can only get to HBOOT, once I try to enter recovery, use an update.zip, or anything after the HBOOT page it goes into its loop. Should I pursue the RUU and find a windows computer or will that not help me?
I think I may have to bite the bullet and buy a new phone. As obviously they will not replace an S-OFF phone. Any help is appreciated.
Click to expand...
Click to collapse
As long as you can still get into HBOOT and Recovery, you should be okay. Your best bet is to get the RUU and go back to stock/s-on, then re-root/s-off (if you want). I had to do this once, and it's pretty straight forward. Just do a search for Bezerker7's Ultimate Get Back to Stock Thread. It has all the info you'll need on how to do it.
RMarkwald said:
As long as you can still get into HBOOT and Recovery, you should be okay. Your best bet is to get the RUU and go back to stock/s-on, then re-root/s-off (if you want). I had to do this once, and it's pretty straight forward. Just do a search for Bezerker7's Ultimate Get Back to Stock Thread. It has all the info you'll need on how to do it.
Click to expand...
Click to collapse
The problem is I can only get into HBOOT, not recovery. It would be a fairly simple matter if I had access to recovery features. Would RUU work without access to recovery?
jenic said:
The problem is I can only get into HBOOT, not recovery. It would be a fairly simple matter if I had access to recovery features. Would RUU work without access to recovery?
Click to expand...
Click to collapse
Looks like you'd need recovery to flash back to s-on first. First you could try flashing a recovery image using fastboot, go here for that information. You'd also need to find a 2.5.x.x recovery image, go here for the 2.5.1.2 image. Don't worry about renaming it, you won't have to do that here like the page says to.
Then, you could go here for instructions on using the RUU to flash back to stock.
RMarkwald said:
Looks like you'd need recovery to flash back to s-on first. First you could try flashing a recovery image using fastboot, go here for that information. You'd also need to find a 2.5.x.x recovery image, go here for the 2.5.1.2 image. Don't worry about renaming it, you won't have to do that here like the page says to.
Then, you could go here for instructions on using the RUU to flash back to stock.
Click to expand...
Click to collapse
Your concise post is most appreciated. I will do as you instruct and post results back here when finished.
RMarkwald said:
Looks like you'd need recovery to flash back to s-on first. First you could try flashing a recovery image using fastboot, go here for that information. You'd also need to find a 2.5.x.x recovery image, go here for the 2.5.1.2 image. Don't worry about renaming it, you won't have to do that here like the page says to.
Then, you could go here for instructions on using the RUU to flash back to stock.
Click to expand...
Click to collapse
Hit an unfortunate snag right away. fastboot (nor adb) is detecting the device. Screen is showing XC SHIP S-OFF as it should, it is in FASTBOOT USB mode and my computer detects the USB itself just fine.
dmesg output:
[346853.772041] usb 2-6: new high speed USB device using ehci_hcd and address 17
[346853.922917] usb 2-6: configuration #1 chosen from 1 choice
Click to expand...
Click to collapse
Thank you though that was a great suggestion! (Was very hopeful for a second there
I've never used the fastboot command before, but I seem to recall that sometimes my PC's don't report connection from ADB, but I haven't checked recently... Hmmm...
Just checked and it does report a device using ADB. Did you try typing the fastboot command to flash the recovery image file: fastboot flash recovery /path/to/<recovery.img file> anyways to see what happens? I am assuming if it isn't detecting the connection, it may fail...
EDIT: Did you pull the battery out, put it back in and try to get into recovery again? If you, try doing a user/factory reset + dalvik cache before trying to install a ROM from your SD card.
This may or may not help, but I had a similar issue of not having the phone recognized by fastboot while playing with a friends EVO Shift. I was able to use the program described in this thread to uninstall all HTC drivers. Then, when the phone was recognized and new drivers installed automatically, fastboot worked as expected.
http://forum.xda-developers.com/showthread.php?t=532719
RMarkwald said:
I've never used the fastboot command before, but I seem to recall that sometimes my PC's don't report connection from ADB, but I haven't checked recently... Hmmm...
Just checked and it does report a device using ADB. Did you try typing the fastboot command to flash the recovery image file: fastboot flash recovery /path/to/<recovery.img file> anyways to see what happens? I am assuming if it isn't detecting the connection, it may fail...
Click to expand...
Click to collapse
My ADB daemon would always recognize it in the past, when the phone was working. Yes I tried the command anyway, even though fastboot devices did not return anything. It hung there waiting for the device to be connected.
RMarkwald said:
EDIT: Did you pull the battery out, put it back in and try to get into recovery again? If you, try doing a user/factory reset + dalvik cache before trying to install a ROM from your SD card.
Click to expand...
Click to collapse
Yes, I pulled battery out multiple times, and when installing the rom I factory reset, cleared dalvik and normal cache through Clockwork. Cyanogen was working fine for weeks, this is a freak concurrence that happened without warning. I woke up to find it this way, or rather, it woke me up with its constant rebooting. lol.
cf9182 said:
This may or may not help, but I had a similar issue of not having the phone recognized by fastboot while playing with a friends EVO Shift. I was able to use the program described in this thread to uninstall all HTC drivers. Then, when the phone was recognized and new drivers installed automatically, fastboot worked as expected.
http://forum.xda-developers.com/showthread.php?t=532719
Click to expand...
Click to collapse
I appreciate the help however I am using Linux, and that seems to be a windows issue. I have not had issue detecting the device until this problem arouse. The sentiment is of course appreciated though, please do not feel that I am ungrateful! You have both been very supportive. I think I have just about resigned to dump money on a new phone. This time I will leave it stock for awhile and see if this occurs a third time.
jenic said:
My ADB daemon would always recognize it in the past, when the phone was working. Yes I tried the command anyway, even though fastboot devices did not return anything. It hung there waiting for the device to be connected.
Yes, I pulled battery out multiple times, and when installing the rom I factory reset, cleared dalvik and normal cache through Clockwork. Cyanogen was working fine for weeks, this is a freak concurrence that happened without warning. I woke up to find it this way, or rather, it woke me up with its constant rebooting. lol.
I appreciate the help however I am using Linux, and that seems to be a windows issue. I have not had issue detecting the device until this problem arouse. The sentiment is of course appreciated though, please do not feel that I am ungrateful! You have both been very supportive. I think I have just about resigned to dump money on a new phone. This time I will leave it stock for awhile and see if this occurs a third time.
Click to expand...
Click to collapse
This happened to me and many other people. It has nothing to do with the fact that you rooted as my replacement from verizon did the same thing even before I rooted. Finally on my 2nd replacement (my 3rd DINC), it has stopped happening.
You're going to have to take it to the store. The guy who looked at my phone looked right at the HBOOT (where it says s-OFF) and then said "we're going to have to send you another one."
So you may get lucky. Your other option (if you're nervous about the store seeing the s-OFF) is just to call Verizon and ask them to send you a replacement. My experience has been that the folks in the Verizon store have no idea what the f they're doing, and you'll probably be just fine taking it in.
jaba14 said:
This happened to me and many other people. It has nothing to do with the fact that you rooted as my replacement from verizon did the same thing even before I rooted. Finally on my 2nd replacement (my 3rd DINC), it has stopped happening.
You're going to have to take it to the store. The guy who looked at my phone looked right at the HBOOT (where it says s-OFF) and then said "we're going to have to send you another one."
So you may get lucky. Your other option (if you're nervous about the store seeing the s-OFF) is just to call Verizon and ask them to send you a replacement. My experience has been that the folks in the Verizon store have no idea what the f they're doing, and you'll probably be just fine taking it in.
Click to expand...
Click to collapse
That was definitely a laugh. Thank you I will see if I can get it replaced! I've been kinda just ignoring the fact that I do not have a phone all this time... Thankfully I had setup the phone to forward calls to google voice. It has been a lifesaver.
My phone is stuck at the white Evo splash screen. This happenned after I performed the autoroot procedure located at: http://forum.xda-developers.com/showthread.php?t=838448
I have tried all kinds of ways to bring it back with no success. I downloaded shipped roms 3.30 and 3.70 (3.70) is what my phone originally was. The RUU_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed.exe will not run on my windows 7 machine I assume it's corrupted and I have downloaded it from two different sources. The RUU_SuperSonic_S_Sprint_WWE_3.30.651.3_Radio_2.15.00.09.01_NV_1.77_003_release_157088_signed.exe runs but it always tells me that my battery is below 30% even though I plug the phone in to the charger and after a few minutes the LED turns green. Then I tried downloading the 3.70 rom as a zip file, named it pc36100.zip, put it in the root of my sd card, then I went into recovery mode and I told it to start the update. It looks like it works but I get a message at the end that says "partition update fail!" and then it asks me to reboot and I'm right back at the endless white evo splash screen. I even tried to load several times using the evo-recovery where I was able to pick which image I wanted to phone to update but it fails with a symlink error of some sort.
I'm stuck. Any help would be appreciated here.
Thanks
Try PC36IMG from here http://forum.xda-developers.com/showpost.php?p=8097472&postcount=1
deeztech said:
My phone is stuck at the white Evo splash screen. This happenned after I performed the autoroot procedure located at: http://forum.xda-developers.com/showthread.php?t=838448
I have tried all kinds of ways to bring it back with no success. I downloaded shipped roms 3.30 and 3.70 (3.70) is what my phone originally was. The RUU_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed.exe will not run on my windows 7 machine I assume it's corrupted and I have downloaded it from two different sources. The RUU_SuperSonic_S_Sprint_WWE_3.30.651.3_Radio_2.15.00.09.01_NV_1.77_003_release_157088_signed.exe runs but it always tells me that my battery is below 30% even though I plug the phone in to the charger and after a few minutes the LED turns green. Then I tried downloading the 3.70 rom as a zip file, named it pc36100.zip, put it in the root of my sd card, then I went into recovery mode and I told it to start the update. It looks like it works but I get a message at the end that says "partition update fail!" and then it asks me to reboot and I'm right back at the endless white evo splash screen. I even tried to load several times using the evo-recovery where I was able to pick which image I wanted to phone to update but it fails with a symlink error of some sort.
I'm stuck. Any help would be appreciated here.
Thanks
Click to expand...
Click to collapse
I would also try running the RUU and PC36IMG a couple more times, maybe download them from a different source. Do you have HTC sync installed on your computer? I believe it's needed to use the RUU. So if you pull your battery out, reinsert it, then plug your Evo into a wall charger, the light goes steady green after a few minutes? Strange, I'd try a different RUU. Did you download from here? http://forum.xda-developers.com/showthread.php?t=884060&highlight=hboot-0.97+ruu . I haven't experienced problems like this before (fortunately) but I've also read about people needing to format their SD card before it would work, using the PC36IMG. Not sure why, but possibly something corrupted on the SD card? Did the auto root give you any sort of errors or anything? Or did it just appear to work, and then this happened?
Also, you could try running the RUU from fastboot mode. Boot to the bootloader, select 'fastboot', and then try the RUU
HTC Sync is indeed needed for the RUU in .exe form.
Boot into hboot by holding down the volume down button while turning on your phone. I believe you choose hboot USB and then run the RUU exe.
k2buckley said:
I would also try running the RUU and PC36IMG a couple more times, maybe download them from a different source. Do you have HTC sync installed on your computer? I believe it's needed to use the RUU. So if you pull your battery out, reinsert it, then plug your Evo into a wall charger, the light goes steady green after a few minutes? Strange, I'd try a different RUU. Did you download from here? http://forum.xda-developers.com/showthread.php?t=884060&highlight=hboot-0.97+ruu . I haven't experienced problems like this before (fortunately) but I've also read about people needing to format their SD card before it would work, using the PC36IMG. Not sure why, but possibly something corrupted on the SD card? Did the auto root give you any sort of errors or anything? Or did it just appear to work, and then this happened?
Also, you could try running the RUU from fastboot mode. Boot to the bootloader, select 'fastboot', and then try the RUU
Click to expand...
Click to collapse
The fastboot method worked! Awesome. So, in the hboot menu, it says S-OFF, which I assume means it's rooted. If that's the case, then I can push any rom I want on top of it now, correct?
deeztech said:
it says S-OFF, which I assume means it's rooted. If that's the case, then I can push any rom I want on top of it now, correct?
Click to expand...
Click to collapse
Correct. You can copy any ROM (suggesting nandroid backup first) to SD card and flash it
deeztech said:
The fastboot method worked! Awesome. So, in the hboot menu, it says S-OFF, which I assume means it's rooted. If that's the case, then I can push any rom I want on top of it now, correct?
Click to expand...
Click to collapse
Sweet, I'm glad it worked for you. So it says you're S off, even after running the RUU? I've never used the Autoroot method, but it must flash unrevoked forever, somewhere in the process. Well, if it says you're S off, I believe the only thing you're missing before you can flash anything is a custom recovery, which you most likely do not have, after running RUU. I believe that since you're s off, you can just flash a custom recovery from the bootloader, and then flash a rom. You could also use ROM manager to flash a recovery, you'd just need to download and install the Super User app, I believe. I think that should work for you? I've never tried to just flash a recovery from a stock ROM, right after an RUU, but if you're s off, i dont see why you can't do that. Download the PC36IMG I attatch here, make sure its named PC36IMG, put it on the main directory of your sd card, boot to the bootloader. Let it scan and ask you to update. Select volume up for yes. After that's done, you should have custom Amon Ra V2.3 recovery. From there, you 'should' be able to flash ROMs. good luck.
Edit: wouldn't let me upload the PC36IMG for some reason. Instead, click this link to download. http://db.tt/7jGH2CA
erik077 said:
Try PC36IMG from here http://forum.xda-developers.com/showpost.php?p=8097472&postcount=1
Click to expand...
Click to collapse
Uhh no. That PC36IMG.zip is waaay outdated. You know they are all different, right? Just because it's a PC36IMG.zip does NOT mean it's the same file as the next one.
I used that one in two situations...
1. when my friend phone was bricked
2. when did unroot
both times that file worked for me
erik077 said:
I used that one in two situations...
1. when my friend phone was bricked
2. when did unroot
both times that file worked for me
Click to expand...
Click to collapse
I did as you suggested and installed the custom recovery. Worked beautifully! I was able to install the MIUI rom and it's a beautiful thing. Thanks a lot for all your help.
Np, that's why we here
Sent from my PC36100 using XDA App
help!!!!
im stuck on step 8 my phone is showing the red triangle with the ! the DOS promt says...
waiting for the phone...
found the phone connected as 'recovery'
setting up a temporary recovery...
**daemon still not runningerror: cannot connect to daemon
*daemon not running. starting it now on port 5037 *
*daemon started successfully *
**daemon still not runningerror: cannot connect to daemon
what do i do?