Develop Bugs

Returning Evo to Stock 1.47.651.1? HELP!

Hey guys,
I was wondering if someone could shed some light on my problem. I have a rooted EVO (rooted using the SimpleRoot program) running the Cyanogen Froyo RC.
I want to return the phone back to factory default since the official Froyo comes out this week anyways, and I don't want to have problems upgrading to the official version.
I attempted to run the RUU_Supersonic_1.47.651.1_Radio_2.05.00.06.10_release_CL195459 from shippedroms.com, but at first I was getting:
ERROR [170]: USB CONNECTION ERROR
Thinking it was probably a driver issue, I uninstalled HTC Sync, HTC Driver Installer, and PDANet (just for good measure), rebooted, and reinstalled (making sure virusscan was disabled).
I then connected my phone and reran the RUU. To my surprise, I got past the recognition and it got past the original error. As it attempts to flash the stock image, however, the first thing it does is reboot to the bootloader. The first thing I get is "waiting for bootloader..." and then after a timeout, I get:
ERROR [171]: USB CONNECTION ERROR
I just want to get this thing back to stock. Can anyone help me, please!?

EDIT: Maybe check this post out...I think this is actually what I did, but I already had nand unlocked.
http://forum.xda-developers.com/showthread.php?t=737447

with phone off: hold down power and vol-up, plug the phone in to the computer, now run your stock RUU. i believe that's what i had to do.
personally i would'nt do this, as you'll most likely lose your root, maybe for good. wait a 1/2 day for a rooted update to come out.

OneStepAhead said:
with phone off: hold down power and vol-up, plug the phone in to the computer, now run your stock RUU. i believe that's what i had to do.
personally i would'nt do this, as you'll most likely lose your root, maybe for good. wait a 1/2 day for a rooted update to come out.
Click to expand...
Click to collapse
I do agree everybody is so ready to unroot there EVO instead of just waiting till the devs say its ok or a good working 2. 2 Rooted Rom is here. Then you guys going to flooding the forums askinghow to get root back or how they lost root. I say if your phone is working great and you have uncap fps and a2sd work then just wait it out.
Sent from my PC36100 using Tapatalk

[Q] Unrevoked3 failing on HTC desire

hi there
I got my SLCD desire a few weeks ago and did the HTC upgrade to android 2.2.
Later I discovered that, with this upgrade, the rooting process is quite difficult.
Yesterday I found this thread to downgrade Android 2.2 to 2.1 (which I did and which seems to have worked perfectly).
Now I try to install the ClockworkMod with Unrevoked 3.1 to get root access.
I use win7 x64. Unrevoked3 gets stuck at "pushing recovery image".
It's been like that for half an hour without any change...
I installed the modified hboot driver and there are no devices without working drivers in the "device manager".
Is this a windows specific problem and it will work if I use linux?
Or did I do something wrong?
thanks for helping
sorry I'm a new member I cannot post the link to the "Downgrade froyo to stock 2.1", it tells me new members cannot post outside links...

Tyderion said:
hi there
I got my SLCD desire a few weeks ago and did the HTC upgrade to android 2.2.
Later I discovered that, with this upgrade, the rooting process is quite difficult.
Yesterday I found this thread to downgrade Android 2.2 to 2.1 (which I did and which seems to have worked perfectly).
Now I try to install the ClockworkMod with Unrevoked 3.1 to get root access.
I use win7 x64. Unrevoked3 gets stuck at "pushing recovery image".
It's been like that for half an hour without any change...
I installed the modified hboot driver and there are no devices without working drivers in the "device manager".
Is this a windows specific problem and it will work if I use linux?
Or did I do something wrong?
thanks for helping
Click to expand...
Click to collapse
How many times have you tried to run Unrevoked?

dunno, about 10 times
most times it failed after 5-40 sec with "failed to push recovery image. terminating...".
And now is the third time that it is pushing and pushing... last two times I quit after an hour or so...

Tyderion said:
dunno, about 10 times
most times it failed after 5-40 sec with "failed to push recovery image. terminating...".
And now is the third time that it is pushing and pushing... last two times I quit after an hour or so...
Click to expand...
Click to collapse
yeah well it should only take about 15 seconds in all so its obviously not working, as for why I am not sure it sounds as though you have set it up correctly. Does your phone boot into HBOOT correctly when you plug it in using Unrevoked?

You have to use a custom image to root slcd screen using unrevoked. Let me see if i can find the link
http://forum.xda-developers.com/showpost.php?p=7563237&postcount=1

hahaha i'm stupid! *facepalm*
nowhere is written that the sd card has to be in disk mode (opposed to charge only for the downgrade)
now it is working I think that was the only problem .... :S
thanks anyways for the quick answers

hmm ... how long should it take to flash it?
It now correctly goes to hboot, connects and then reboots and then states:
Flashing recovery image. Do not touch your phone!
But it's already been doing that for some minutes....
Is it normal that it starts flashing while the HTC-Boot-Logo is still visible?
(late) EDIT: worked with Linux LiveCD, something on windows made it impossible to finish the rooting process

help get past: waiting for device on unrevoked root

I am going crazy trying to root my friend’s Evo, I did mine so long ago using toast 1+ 2 method; which is a breeze compared to the unrevoked 3.21. I have tried everything to get the re-flash tool to move past : waiting for device:
I have tried:
1. downloaded HTC sync, but did not run it.
2. Running HTC sync, reboot, and then uninstall
3. Turning of anti-virus on computer
4. Switching USB cords
Nothing has worked…… Please help!
The hboot is 0.97, which should be rootable.
Thanks in advance

[Q] Stuck in recovery boot loop HTC Desire GSM ~ ASSISTANCE APPRECIATED!!

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.

[Q] Unsuccessful Root of Desire HD. Please Help, Newbie Here.

Hello everyone, first of all I am a total newbie not just to rooting but also today was my first time ever using linux so please bear with me. Having said that, I have done my best to learn and understand the linux commands in the effin manual and followed all instructions as best as I could though I couldn't understand them well enough which is why I am here.
I am using Ubuntu 11.04 64 bit live cd but managed to install the i32-libs as stated in the effin manual. This is the only version of Ubuntu I could get from my friends as I have very slow internet connection and cannot download the new version or just the 32 bit one.
Anyway, on to the problem at hand.
I first ran the aahk, going through all the steps in the effin manual. My phone was originally on 2.3.5 and Sense 3 so I had to downgrade and the aahk downloaded the necessary rom(?) or RUU (?) to do this.
Once that was done, aahk carried on until the step where my phone rebooted.
This was where things started going wrong for me.
When the phone rebooted into 2.3.3 and started the wizard to set up my phone, I went through all that.
If I recall, at this point the aahk screen was up to “Once the downgrade is successful, press a key to return to the menu.... Otherwise, cut and paste the output to the screen into a text file for evaluation... then press a key. Press any key to continue...”
However, the step before that, “The phone will now reboot into HBOOT. If everything is okay, the phone will prompt you to continue by pressing VOLUME UP. It will reboot, flashing twice.”
PUSH POWER WHEN THIS STEP COMPLETES
I don't recall this happening for me or maybe it did but I did not notice. I did not press VOLUME UP nor see the flashing twice but surely it happened? Otherwise I would have been able to reboot into the phone environment correct? My head is spinning now...
Okay, this is where I may have gotten ahead of myself when reading the effin manual. You have to understand, I was just brimming with joy “thinking” I had successfully rooted my first ever and one and only smartphone.
I started looking for BusyBox or Superuser but couldn't find anything.
Not knowing what else to do, I rebooted the phone MANUALLY (hold power button and reset).
Then everything started going wrong.
Please don't get mad. I did not realise the aahk had to reboot several times. I thought once and that was it. I just found that out now.
However, between that time and when I found this out I believe I caused all sorts of damage.
When the phone rebooted, it got stuck on the white screen with HTC logo and aahk was no longer working.
The wrong things I did were to to go into HBOOT and RECOVERY and WIPE EVERYTHING (DATA, CACHE, DAVLIK, EVERYTHING) *SORRY!*
And so here I am, hoping someone can help me.
After searching around the forums some similarities I had with other users in the past was that the phone is still showing S-ON and because of what I had done, aahk did not get to work properly so my phone has no ROM and no RECOVERY.
And I also JUST realised I made things worse by deleting USB debugging when I WIPED everything!.
Please help.... (_ _”)

I can help you out. Can you still go in Hboot?
Sent from my Desire HD using XDA

dnplee said:
Hello everyone, first of all I am a total newbie not just to rooting but also today was my first time ever using linux so please bear with me. Having said that, I have done my best to learn and understand the linux commands in the effin manual and followed all instructions as best as I could though I couldn't understand them well enough which is why I am here.
I am using Ubuntu 11.04 64 bit live cd but managed to install the i32-libs as stated in the effin manual. This is the only version of Ubuntu I could get from my friends as I have very slow internet connection and cannot download the new version or just the 32 bit one.
Anyway, on to the problem at hand.
I first ran the aahk, going through all the steps in the effin manual. My phone was originally on 2.3.5 and Sense 3 so I had to downgrade and the aahk downloaded the necessary rom(?) or RUU (?) to do this.
Once that was done, aahk carried on until the step where my phone rebooted.
This was where things started going wrong for me.
When the phone rebooted into 2.3.3 and started the wizard to set up my phone, I went through all that.
If I recall, at this point the aahk screen was up to “Once the downgrade is successful, press a key to return to the menu.... Otherwise, cut and paste the output to the screen into a text file for evaluation... then press a key. Press any key to continue...”
However, the step before that, “The phone will now reboot into HBOOT. If everything is okay, the phone will prompt you to continue by pressing VOLUME UP. It will reboot, flashing twice.”
PUSH POWER WHEN THIS STEP COMPLETES
I don't recall this happening for me or maybe it did but I did not notice. I did not press VOLUME UP nor see the flashing twice but surely it happened? Otherwise I would have been able to reboot into the phone environment correct? My head is spinning now...
Okay, this is where I may have gotten ahead of myself when reading the effin manual. You have to understand, I was just brimming with joy “thinking” I had successfully rooted my first ever and one and only smartphone.
I started looking for BusyBox or Superuser but couldn't find anything.
Not knowing what else to do, I rebooted the phone MANUALLY (hold power button and reset).
Then everything started going wrong.
Please don't get mad. I did not realise the aahk had to reboot several times. I thought once and that was it. I just found that out now.
However, between that time and when I found this out I believe I caused all sorts of damage.
When the phone rebooted, it got stuck on the white screen with HTC logo and aahk was no longer working.
The wrong things I did were to to go into HBOOT and RECOVERY and WIPE EVERYTHING (DATA, CACHE, DAVLIK, EVERYTHING) *SORRY!*
And so here I am, hoping someone can help me.
After searching around the forums some similarities I had with other users in the past was that the phone is still showing S-ON and because of what I had done, aahk did not get to work properly so my phone has no ROM and no RECOVERY.
And I also JUST realised I made things worse by deleting USB debugging when I WIPED everything!.
Please help.... (_ _”)
Click to expand...
Click to collapse
Do not panic...although you did a factory reset and disabled usb debugging, you can solve your situation. Just flash the RUU (PD98IMG-GBx.zip) file you used to downgrade the phone. It has to be in the PD98IMG folder of the Hack Kit. Make sure that it is that file and no other. Rename it PD98IMG.zip and then put it in the root of the sdcard. Then boot in hboot and update pressing volume up. Let it finish....then you will have a working phone. Then re run the hack kit to Gain S-OFF and Root....if you can´t do it just hit the IRC Channel that is stated in the OP of the Hack Kit thread.

benydc, glevitan, thank you both for the offers of help and advice.
I eventually found my way to the IRC aahk support channel and was blessed to get the help of attn1, one of the ops there.
He helped me through my problem and now everything is as is should be. Thankfully I have a working rooted phone.
Everyone there was very friendly and helpful, not just attn1. He must have spent the last two hours or so juggling with helping out three users (probably more). We even got to make some friendly banter amongst ourselves.
Though I was freaked out initially, I am glad everything works now and from the support I got there, I am somehow not going to shy away from trying to learn about rooting.
I managed to save all the text during our conversation so when I get the time, I will try and build a simple but detailed walkthrough of how attn1 got my phone working again. I will post it here so that it may help others who find themselves in a similar position one day.
Many thanks you guys. This is a great community.

same problem,s-on,no recovery
hey there...ive got similar problem with u and i try putting the PG98IMG on the root of the SD card which i get from the folder from AAHK...but when i go to HBOOT and try to install the PG98IMG, it failed and it says MAIN VERSION IS OLDER ! what should i do?

hi
i have same phone whith you
2.3.5 sens 3.0
i used AAHK but the file name downloaded is "PD98IMG-GB2"
you can rename "PD98IMG" on "PD98IMG-GB2"