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
Related
I downloaded the executable, ran it and I get the following error:
USB Connection Error (Something like that)
The phone reboots and just says htc. The executable is waiting for boot loader and times out after a minute or so.
I unplug the usb after the executable errors out and it instantly goes to a boot loader screen with ruu. I cannot run anything and have no choice but to battery pull.
According to the RUU thread, one person mentioned having to complete part 2 of rooting so i did that. I still cannot return this thing to stock!!!
I need to send it back to sprint, but I gotta get it back to stock first.
How the crap do I get this back to stock!
I'd reply in the RUU thread, but it looks like the last guy who posted never got a response...hopefully this thread will get me an answer.
adb reboot into recovery using "adb reboot recovery" then enable USB and run the RUU
dreamliner330 said:
I downloaded the executable, ran it and I get the following error:
USB Connection Error (Something like that)
The phone reboots and just says htc. The executable is waiting for boot loader and times out after a minute or so.
I unplug the usb after the executable errors out and it instantly goes to a boot loader screen with ruu. I cannot run anything and have no choice but to battery pull.
According to the RUU thread, one person mentioned having to complete part 2 of rooting so i did that. I still cannot return this thing to stock!!!
I need to send it back to sprint, but I gotta get it back to stock first.
How the crap do I get this back to stock!
I'd reply in the RUU thread, but it looks like the last guy who posted never got a response...hopefully this thread will get me an answer.
Click to expand...
Click to collapse
I ran in to the same issue just now. I couldn't fix it, but here is how to do essentially the same thing.
Follow this guide to extract the RUU
Rename the rom.zip file you extract to PC36IMG.zip and put it on the root of your SD card
Reboot into the bootloader, it will load the file and ask if you wanna install it, you should do so
It'll finish and ask if it should reboot, choose yes and boot into a stock phone.
Its a driver issue, at least it was for me, the google drivers don't work for the htc ruu application. You need the htc drivers install for the phone to be recognized by the rom updater. Hope that helps.
i had that issue too, for me it was the drivers. i then used my work computer and it allowed me to use the RUU
I always had to run a ruu from fastboot in order for it to work
YMMV, but I had to run the oldest RUU first when I was at 1.47 level, and then re-run 1.47 RUU for it to work. Otherwise, bootloader would never get pickup up.
I always had to restart the RUU after I got the error first. Run it again after it times out, when your phone is sitting at the HTC screen and it will work.
Just install the latest HTC Sync and you're set. That will fix your issue. Install HTC Sync and run the RUU afterwards.
Geniusdog254 said:
I ran in to the same issue just now. I couldn't fix it, but here is how to do essentially the same thing.
Follow guide to extract the RUU
Rename the rom.zip file you extract to PC36IMG.zip and put it on the root of your SD card
Reboot into the bootloader, it will load the file and ask if you wanna install it, you should do so
It'll finish and ask if it should reboot, choose yes and boot into a stock phone.
Click to expand...
Click to collapse
Perfect! Exactly what I was looking for. I was able to load that ROM. I think it's still rooted though, I can get to the menu by pressing volume down/power.
Any ideas?
ideas on what?
Your being vague.
I like turtles.
Sent from my PC36100 using XDA App
dreamliner330 said:
Perfect! Exactly what I was looking for. I was able to load that ROM. I think it's still rooted though, I can get to the menu by pressing volume down/power.
Any ideas?
Click to expand...
Click to collapse
Any ideas if my phone is still rooted, or what I need to do to get it back 100% to the way I got it from Sprint.
You can always got into that recovery when holding down vol and pwr. If you go to recovery you should only see a triangle and an exclamation. That means you are not rooted.
Sent from my PC36100 using XDA App
dreamliner330 said:
Any ideas if my phone is still rooted, or what I need to do to get it back 100% to the way I got it from Sprint.
Click to expand...
Click to collapse
At this time there isn't a way to get your Evo 100% back to stock. Why do you quote yourself?
^I quoted myself because mattrb thought I was being vague, and I didn't want anyone to be confused, so I emphasized my previous post which was clear enough, I thought....and I was right!
Thanks guys for all the help. In the end, I used the copied the RUU ROM to the SDCARD, named it PC36IMG and restarted the phone holding volume down...the rest was automatic.
hey dreamliner did u use the 1.47 ruu or the 1.32? I am in need of the same thing but I cant get the 1.47 to run...
would this work renaming the zip and copying it to the mSD card?
http://www.sdx-downloads.com/sdx/evo/stock/OTA_Supersonic_1.47.651.1-1.32.651.6_release.zip
I cant get the RUU to extract using process manager, and only once have I gotten the 1.47 RUU to boot the device into bootloader and tried again with the phone on the HTC black screen, unplugged, re plugged and thenran it again and it was giving me the 170 usb error again.
Geniusdog254 said:
I ran in to the same issue just now. I couldn't fix it, but here is how to do essentially the same thing.
Follow guide to extract the RUU
Rename the rom.zip file you extract to PC36IMG.zip and put it on the root of your SD card
Reboot into the bootloader, it will load the file and ask if you wanna install it, you should do so
It'll finish and ask if it should reboot, choose yes and boot into a stock phone.
Click to expand...
Click to collapse
Is there a thank you button or rep on this forum, because you just saved me from the same problem. I give you a BIG HEARTY THANKS!!!!
bcnice20 said:
I always had to run a ruu from fastboot in order for it to work
Click to expand...
Click to collapse
This is the easy solution, worked for me. No need to make things more complicated by extracting the rom.zip.
As bcnice said just run the RUU and when your phone is showing the HTC logo and you get the USB error just rerun the RUU.
I tried to update my EVO radio this mornig. Now everytime I turn on my phone, it gets stuck in the boot animation. When I reboot to recovery, I get hboot, but when I choose recovery, it gets stuck on white HTC screen. I tried fastboot but after three re-installs of SDK, it still give me a this application fails to start because AdbWinApi.dll was not found. PLEASE SOMEONE HELP!!!!!
captainphoenixx said:
I tried to update my EVO radio this mornig. Now everytime I turn on my phone, it gets stuck in the boot animation. When I reboot to recovery, I get hboot, but when I choose recovery, it gets stuck on white HTC screen. I tried fastboot but after three re-installs of SDK, it still give me a this application fails to start because AdbWinApi.dll was not found. PLEASE SOMEONE HELP!!!!!
Click to expand...
Click to collapse
Have you tried using an RUU?
How do I load it to my device?
captainphoenixx said:
How do I load it to my device?
Click to expand...
Click to collapse
You don't load it to your device. Plug phone in with usb to computer. Launch RUU.exe and see if RUU finds the phone. If it does, then follow onscreen instructions.. Make sure phone is powered on when you launch RUU otherwise it will not recognize... Phone can be on white screen and still possibly be recognized depending on exactly what the problem is... If it is recognized follow onscreen instructions and at the end your phone will work again.
leenypost said:
You don't load it to your device. Plug phone in with usb to computer. Launch RUU.exe and see if RUU finds the phone. If it does, then follow onscreen instructions.. Make sure phone is powered on when you launch RUU otherwise it will not recognize... Phone can be on white screen and still possibly be recognized depending on exactly what the problem is... If it is recognized follow onscreen instructions and at the end your phone will work again.
Click to expand...
Click to collapse
If this method doesn't work you need to figure out how to get adb to work again.
Can you get to bootloader? When powered down hold volume down and power button at the same time...if so you can use the 3.30 pc36img posted somewhere in here or I have a copy with Amon recovery....if your rooted.
I Have Amon recovery, but after the update, it still gets stuck, and yes i can get to bootloader, just cant recover or flash
captainphoenixx said:
I Have Amon recovery, but after the update, it still gets stuck, and yes i can get to bootloader, just cant recover or flash
Click to expand...
Click to collapse
If you can get to bootloader an RUU should work for you. Give it a shot.
Here's a link to the thread. RUU link is in first post. Download it and follow the instructions I gave you earlier.
http://forum.xda-developers.com/showthread.php?t=874091
This is the newest RUU though that you flashed the radio from.. Once you get it working you will have to wait on a Root method that works to re-root the phone. Shouldn't be long. You can try an earlier RUU if you want but you'll have to find that in the Rom Sticky Post.
All you gottado is.put the pc36img on the root of your card and the bootloader will read it for you. Just let it run....
Sent from my PC36100 using XDA App
lawnguy said:
All you gottado is.put the pc36img on the root of your card and the bootloader will read it for you. Just let it run....
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Yep, that should work too. I forgot about that as I frequently just RUU'd and then re-rooted, LOL... Good call.
Get a pc36img.zip, place it on the SD card (not in a folder) and start up bootloader. The rest will be taken care of automatically.
If I was at home id send you one with Amon Ra its saved me a bunch if you don't get it tonight I can send it to you tomorrow ... I will keep checking this thread
Sent from my PC36100 using XDA App
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?
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.
Hey all and sorry for this thread as i know you ahve probably seen them before but for the past week i have been trying to root my Wildfire S which was given to me after i sold my other phone.
Now i have read many posts and tried many things but so far i have gotten no where and i have no idea what im doing wrong, i have been to the HTC website and signed up i have then downloaded the right exe file (o2de/en if i remember right) started to run that then when the phone reboots the applicatin dies and the white screen i get when i unplug the cable is "ruu..." and thats it no other text.
I have also tried installing zip files onto the sd card and running them but these have failed too specially when it comes to the root.zip al i get is a red triangle with an explanation mark (up +power > install from sd = nothing)
Can someone help me out, i basically want to try soem roms out i have teh one thats on i have been using go launcher with ICS on it but it does not work fully to my likening plus if its possible i want to change the start up screen adn also get rid of some of the bloat wear.
Thanks in advance if someone is willing to take the time to look and help out. Im near the end of my teather and re-installing go launcher and evrything else (wiped the phone clean before attempting to root)
Btw ive tried guides on this site and on many others using htc website, pg76img (3.75 and 3.50mb versions) and now like i said im stuck.
Phone is wildfire s
software 2.13.206.1
htc files ive tried:
O2DE/UK 2.13.206.1 PG7610000 Download < one i need and keeps failing
HTC EU 2.13.401.3 PG7610000 Download
This one helped me when i was in your condition...hope this qill help you too
androidforums.com/wildfire-s-all-things-root/480954-guide-how-root-wildfire-s-s-finally.html
Sent from my Wildfire S using XDA
abhi8569 said:
This one helped me when i was in your condition...hope this qill help you too
Sent from my Wildfire S using XDA
Click to expand...
Click to collapse
Yeh tried that tutorial before and always got stuck on this part: C:\Users\[YourLoginNameHere]\AppData\Local\Temp\{82B23FCD-D5D0-45CA-A3A2-5350D3926551}
Anyway finally got round it by using CCleaner and finding the right app an now installing the SDK. Dunno why i didnt think of clearing out the temp folder before doh! Will report back if i have another issue. =)
Nope stuck, this was the issue i was having before. I thought i just fixed it but nope not getting any further.
I am upto fastboot oem get_identifier_token, the issue i had was i would plug in the usb cable get 3 short fast beeps from the computer (not recognized) which i have since fixed so it makes the correct beep. But soon as i do the following:
cmd
cd \
cd android
fastboot oem get_identivier_token
I get "waiting for device".
I will have another shot tomorrow been a good hour now iphone was alot easier to do lol
Guess im staying unrooted then im stuck =(
waiting for device means it's not connecting in fastboot mode.
you need to boot the phone by holding vol- and power, then after it's finished reading the sd card, press power again to select fastboot mode (the writing at the top should say "fatboot usb" in re writing.
is your phone bl-unlocked or s-off? because i think you need one of those first before you can try flashing custom recovery?
::EDIT::
if you're having problems with HTCdev site etc....I think there was a tool floating around somewhere that could unlock bootloader without HTCdev site....
::EDIT2::
http://forum.xda-developers.com/showthread.php?t=1576844
try this tool for BL-unlock without htcdev.