Can someone outline how I unroot (for insurance) I want to get it back to stock in case I have to take it in. Do I just have to flash the stock RUU?
Now that we have full NAND root, how do I unroot from that?
run the stock Ruu like just like the hero
Yep just run the stock 1.32.651.6 RUU I did your Link searching for ya just plug in your phone and run it.
http://shipped-roms.com/shipped/Sup...Radio_1.39.00.05.31_release_171253_signed.exe
lostinroot:) said:
Yep just run the stock 1.32.651.6 RUU I did your Link searching for ya just plug in your phone and run it.
http://shipped-roms.com/shipped/Sup...Radio_1.39.00.05.31_release_171253_signed.exe
Click to expand...
Click to collapse
Thank you very much!
seems like a simple process..but Im new to android phones.
Do you run this .exe on the phone? or connected to USB to PC. Not that I will be wanting to un-root anytime soon but it might be good to know down the line.. thanks..
elstupidos said:
seems like a simple process..but Im new to android phones.
Do you run this .exe on the phone? or connected to USB to PC. Not that I will be wanting to un-root anytime soon but it might be good to know down the line.. thanks..
Click to expand...
Click to collapse
.exe will always run from windows computer. android is linux based, no .exe file will run on the android phone.
for the RUU .exe follow the directions on your windows computer, it will guide you through the process, will need USB cable.
joeykrim said:
.exe will always run from windows computer. android is linux based, no .exe file will run on the android phone.
for the RUU .exe follow the directions on your windows computer, it will guide you through the process, will need USB cable.
Click to expand...
Click to collapse
Is it possible to flash it from the phone, and not need a windows computer?
Re: Un-Root
Not with a exe. I'm not sure how the architecture is built for the phobe, but u don't see why flashing a ruu from SD wouldn't work if one were built that way.
-------------------------------------
Sent via the XDA Tapatalk App
All a Ruu is a wrapper. The Ruu just checkes a few things then executes scripts. its kinda just like an automatics ADB.
If you run the EXE is extracts a bunch of files including a ROM.zip. You could probably copy that to your phone and install it from there using the recovery firmware.
I'm trying to restore using this method. The phone is definitely recognize by the software, (it shows the current .1 image version) it jumps to the black HTC screen then sits at "waiting for bootloader" then times out with a ERROR 171 "cannot connect to your android phone" message. Any suggestions? If I run adb devices command the phone is recognized. Any suggestions?
Edit: It seems on the 4th try it worked. At least the updating percentage is moving up.
Why can't a basic rooted rom with recovery be created using this method. That would really be a "1 click" root.
mrono said:
Is it possible to flash it from the phone, and not need a windows computer?
Click to expand...
Click to collapse
i've seen it posted on here, if you take the rom.zip which comes inside the ruu .exe and put it on the root of the sdcard, rename it PC36IMG.zip and boot into the bootloader, vold down + pwr, it will flash the phone w/o needing a computer.
i haven't personally tested it, so use at your own risk.
Updated first post
"Now that we have full NAND root, how do I unroot from that?"
mrono said:
Updated first post
"Now that we have full NAND root, how do I unroot from that?"
Click to expand...
Click to collapse
Run the ruu, you will be completely stock after that.
danknee said:
Run the ruu, you will be completely stock after that.
Click to expand...
Click to collapse
Thank you
When un-rooting, do you need to have the HTC drivers installed on your Windows machine? What mode (charge, disk mount, etc) does the EVO have to be in when you connect it via USB? Does HTC sync have to be installed or the Android SDK?
mrmack said:
When un-rooting, do you need to have the HTC drivers installed on your Windows machine? What mode (charge, disk mount, etc) does the EVO have to be in when you connect it via USB? Does HTC sync have to be installed or the Android SDK?
Click to expand...
Click to collapse
Phone should be fully charged. Really you just need enough juice to ensure it doesn't crap out during the flash process (could brick your phone).
I don't believe you need the HTC drivers, but every time I've run a ruu they were already installed on my machine, so I don't know.
Disk mount mode won't matter because the ruu will restart the phone before it has its way with it.
sync and sdk don't matter, the ruu is a self contained utility that issues adb commands to your phone.
Alternatively the ruu can be "run" by putting the proper file on the root of your sd card and powering your phone on with your volume down button pushed in.
To make the change back
I have done it 2x's and this worked both times. I tried to install the original Sprint Rom with the file provided here. Each time it stopped at the black HTC screen. All that needs to be done is to re-try the install of the original sprint Rom when it is at the black HTC screen. When the installation program says it can't complete and closes (wait for that to happen) just double click on the install program again (while you are at the black HTC screen (don't unplug from your computer)). When you try the install the second time at the black HTC screen, a green progres bar shows up on said screen and will show you the install progress. Hope this helps
Thanks guys! I was trying to mount the disk, then install HTC sync, etc. Leaving it on the black screen seemed to make the difference for whatever reason...
danknee said:
Phone should be fully charged. Really you just need enough juice to ensure it doesn't crap out during the flash process (could brick your phone).
I don't believe you need the HTC drivers, but every time I've run a ruu they were already installed on my machine, so I don't know.
Disk mount mode won't matter because the ruu will restart the phone before it has its way with it.
sync and sdk don't matter, the ruu is a self contained utility that issues adb commands to your phone.
Alternatively the ruu can be "run" by putting the proper file on the root of your sd card and powering your phone on with your volume down button pushed in.
Click to expand...
Click to collapse
Hey there! Having trouble unrooting from latest xda root method. I run the RUU and keep getting error 170- usb connection error. Is the driver not installed. Stupid me, when it prompted to install the driver before, I hit 'never for this device'. Any reversal for this??? Thx in advance!
Related
Is there any guide or instructions how to root and flash the Desire with a new custom ROM?
Im so confused right now, rooted my Hero and flashed it dozen times but now its different with Desire. Plz someone help?
Take this guide
http://forum.xda-developers.com/showthread.php?t=672770
Do i have to make a goldcard if i have a unlocked and unbranded Desire in sweden? 0.80 bootloader...
I think you have to.
I've done it with a goldcard, have also a unclocked device.
Unbranded devices generally don't need gold cards.
cedeel said:
Unbranded devices generally don't need gold cards.
Click to expand...
Click to collapse
Yep totally correct! If the handset was unbranded when new then no goldcard is needed. I didn't need one on mine.
socktug said:
Yep totally correct! If the handset was unbranded when new then no goldcard is needed. I didn't need one on mine.
Click to expand...
Click to collapse
thx for the info, didn't know that
cedeel said:
Unbranded devices generally don't need gold cards.
Click to expand...
Click to collapse
Thank you
So practicly what i have to do is this:
if you have a bootloader version 0.80.xxxx or below AND a current ROM of 1.21.xxx.x or below -
Part 1
Part 2
*- Copy the 'rooted update' you downloaded above to the root of your SD card, before replacing it into your device
*- Turn off your HTC desire, then turn it back on with the 'back' button held down. You'll see 'FASTBOOT' written on the screen in a red box.
*- Connect the phone to your computer, then run the 'test ruu' that you downloaded above (it may take a short while to start). Let the update complete and turn your device off as soon as it reaches the configuration wizard. If you need USB drivers, you can find them as part of the HTC Sync install.
*- Your device should now be off. Unplug the device from your computer. Turn it on again while holding down the 'volume down' button this time. The screen will look similar to before, but will say 'HBOOT' instead of 'FASTBOOT'. Use the volume buttons and the power button to select the 'RECOVERY' option. You should then see a screen with a red triangle - at this point, plug it into your Linux or OSX computer.
*- Now you need to unzip the 'push files' zip that you downloaded above. When you have done so, you'll see a file called 'recovery-linux.sh' or 'recovery-mac.sh'. Run the one appropriate to your operating system and the screen of your device should change to display the green recovery image menu.
*- In the recovery image (moving around using the optical trackball), select 'Wipe -> Wipe data /factory reset' then 'Flash zip from sdcard' and choose the rooted update. Confirm with the trackball and the update process will begin. It'll take a little while, so go make a nice cup of tea.
---------------------------------------------------
I hope i havent forgot anything? Im pretty nervous right now :/
I don't want to confuse issues, but that one looks a bit out of date. it will work fine, but there is a newer slightly easier method now.
Are you confident in following basic instructions on using linux? I wasn't but it is so easy that anyone can do it!
Take a look here and see which one you prefer.
http://android.modaco.com/content/htc-desire-desire-modaco-com/308542/r4-htc-desire-easy-rooting-guide-with-tiny-core-linux/
All you need to do with this one is download the appropriate file, burn it to disc and type 4 commands in linux.
Or just use r5. The scripts are good and shouldn't cause any trouble. If you are on linux/mac you might need to change permissions on some files though.
socktug said:
I don't want to confuse issues, but that one looks a bit out of date. it will work fine, but there is a newer slightly easier method now.
Are you confident in following basic instructions on using linux? I wasn't but it is so easy that anyone can do it!
Take a look here and see which one you prefer.
http://android.modaco.com/content/htc-desire-desire-modaco-com/308542/r4-htc-desire-easy-rooting-guide-with-tiny-core-linux/
All you need to do with this one is download the appropriate file, burn it to disc and type 4 commands in linux.
Click to expand...
Click to collapse
Without a doubt that seems easy, i just wonder if i can do it the same way with Ubuntu 9.10 ? Its because i have a livecd with Ubuntu but no empty cd to burn on
infexis said:
Without a doubt that seems easy, i just wonder if i can do it the same way with Ubuntu 9.10 ? Its because i have a livecd with Ubuntu but no empty cd to burn on
Click to expand...
Click to collapse
Try this one then! http://android.modaco.com/content/htc-desire-desire-modaco-com/307365/24-may-r5-htc-desire-rooting-guide-now-with-hboot-0-80-and-os-to-1-21-support/
socktug said:
Try this one then! http://android.modaco.com/content/htc-desire-desire-modaco-com/307365/24-may-r5-htc-desire-rooting-guide-now-with-hboot-0-80-and-os-to-1-21-support/
Click to expand...
Click to collapse
That is the guide i read first, but now it seems there is a better solution with linux.
I'm not sure what newer method you mean?
At the end of the day, any of the methods posted here will work for you. The first one I pointed to with tiny core linux was for me the easiest.
Just give one of them a try and post back if you encounter any problems, if the worst happens and you make a mistake and cause the usb to be bricked, it can now be easilly fixed.
As far as I am aware there are no other issued you can run into if you follow the guides.
Yeay, i just found a cd-rw at home
I will now erase the disc, burn the .iso file on it and start rooting
Wish me luck!
Lol. Good luck. Once you start flashing custom roms, you will never be happy and want to keep trying more!
socktug said:
Lol. Good luck. Once you start flashing custom roms, you will never be happy and want to keep trying more!
Click to expand...
Click to collapse
I know Ive had a Hero for about a year now
you dont need to use linux anymore there is a windows method
all you need is to download the pushfiles and extract them in the desire root files click on recovery windows.bat when you get to the triangle on the desire it will take you to the recovery options
also ur device has to be connected with usb and dont remove the usb when you updating the rom
tori007 said:
you dont need to use linux anymore there is a windows method
all you need is to download the pushfiles and extract them in the desire root files click on recovery windows.bat when you get to the triangle on the desire it will take you to the recovery options
also ur device has to be connected with usb and dont remove the usb when you updating the rom
Click to expand...
Click to collapse
That is the method to go to recovery after rooting. You still need to root first. Also, the windows method may be easier, but a lot of people are commenting on driver problems. The linux method is by far the least problematic.
Just my opinon of course!
i did not have any issue while rooting go to the hero section and use those drivers they worked fine for me
I'm using the GingerVillain rom, but I was wondering is there a way I can make my device S-OFF whilst using this ROM?
Also I was wondering why my Orange 3G/H signal is so rubbish, it nearly always ends up being on G internet? Anyone else have this problem?
I'm trying to install CWM 3.0.0.5 from recovery, it comes up in the new colours after installing, but on the next reboot it's back to the old one? Do I need to root again with unrevoked using the 3.0.0.5 zip file?
Also is there any was I can run alpharev without having to burn to a CD? I've tried running a virtual box but no luck?
Thanks for reading hope somebody can help.
Jamie94 said:
1. I'm trying to install CWM 3.0.0.5 from recovery, it comes up in the new colours after installing, but on the next reboot it's back to the old one? Do I need to root again with unrevoked using the 3.0.0.5 zip file?
2. Also is there any was I can run alpharev without having to burn to a CD? I've tried running a virtual box but no luck?
Click to expand...
Click to collapse
1. This is because the rom manager doesnt support CWM 3.0.0.5 yet but only: 2.5.x.x
2. The CD option is 100% working and it is quick and almost safe imo.
Jamie94 said:
Also is there any was I can run alpharev without having to burn to a CD? I've tried running a virtual box but no luck?
Click to expand...
Click to collapse
You can burn it on pendrive as bootable usb drive, or use VM like Parallels Desktop (i used it, and worked fine)
I used virtual box, but I had to load specific drivers, and follow alternate instructions. A total PITA, but it works.
I only used UnRevoked because I forgot which other program I used for my previous phone. Afterwards, I now have an app called zysploit running all the time ((((
Moscow Desire said:
I used virtual box, but I had to load specific drivers, and follow alternate instructions. A total PITA, but it works.
I only used UnRevoked because I forgot which other program I used for my previous phone. Afterwards, I now have an app called zysploit running all the time ((((
Click to expand...
Click to collapse
Mind helping me out a bit?
I download a package called "universal usb installer 1.8" Do a search for it. Now, listen up.
As far as I can remember, after extracting, I had to tell Device Manager to install the driver specifically, Not browse for them. Because windows will always look for a signed driver. I had to ignore the normal message that it wasn't signed.
If I'm not mistaken, you need to load the Android Bootloader interface (with phone plugged in, USB debugging enabled)
This "should" allow unrevoked to interface with the phone.
Hello xda, in accordance with the signup video I have scoured the earth looking for an answer. However I'm not sure how much necro posting is frowned upon here so I thought it would be safer to just start a new thread.
I have an HTC Desire HD from Telus(for use on the Rogers network). I am in the process of rooting it but have encountered a problem. I can gain temporary root on the terminal emulator(Because the $ turns to #) however when attempting to run clockwork flash clockworkmod recovery I get the error "An error occurred while attempting to run privileged commands!"
I get the same error when attempting the "Fix Permissions" so I'm currently at a loss of what to do.
I have the ninja superuser icon in the apps menu however when I open it the screen is blank. I am unsure if this is how it is supposed to be or not. I have seen several references to a permission box that pops up during some of the steps but I haven't seen that at all.
I've tried four separate methods, the last of which coming from this thread http://forum.xda-developers.com/showthread.php?t=954997
I am currently at step B.d which involves running the S-OFF tool and Easy Radio OFF tool. But still clockwork will not flash a backup, and when I restart the phone I can not get super user to work on the terminal (ie by typing su) and must use the rage method to regain temporary root.
Also, I don't know if this is related or not, but when I restart the phone and attempt to boot in recovery mode, the volume buttons don't allow me to select other options, and instead the phone just forces me to reboot normally.
Some more facts:
model HTC Desire HD A9191
Build # 1.32.405.6
Android 2.2
Anymore info I'm probably forgetting just ask away!
So my question is: Can anyone identify what the issue is?
Thanks much for taking the time to read my question.
Does visionary not work for you?
I've seen that alot of success has been gained by doing temp root and perm root through it?
It does sound like the rage method might not be working for you from what I can tell..
I do want to check all the steps you followed before where fine?
Sent from outer space on my DHD running beatmod gingersense v1.3
Visionary was how I rooted mine. Worth a try if you havent tried it: http://android.modaco.com/content/software/320350/19-nov-r14-visionary-one-click-root/
Thanks for the visionary suggestion, but Visionary still isn't working :/
Has visionary been tested with the Telus Desire? I heard there was a difference. What happens when I attempt to temproot is it moves to a blank screen then goes back to the menu.
When I used visionary on 1.32 it did not always work first try ... generally always worked after 2 runs. then used it to perm root
It works. You do not have Telus software in your phone anymore.
Sent from my Desire HD using Tapatalk
Try my method (I made it because the methods I found for my Telus desire HD were flaky at best and only got temproots from it.)
Since you already flashed to 1.32 start at step 2
If you want to go gingerbread, dl the 2.36.405 ruu and use that and your pc to put 2.3.3 on it (dont worry, it works fine, i was using it since it came out and built a rom based off that, kingdom, and pyramid roms for my own sense 3 rom) and use the gingerbreak method.
http://driphter.com/index.php?topic=3867.0
Still haven't managed to get root. JSLEnterprises my antivirus won't let me download your file :/
I'm at a loss for what to do.
lemonpartyz said:
Still haven't managed to get root. JSLEnterprises my antivirus won't let me download your file :/
I'm at a loss for what to do.
Click to expand...
Click to collapse
Disable your Antivirus (Avast say's its malicious), Norton or F-Prot says its clean.
and Internet Explorer 9 says its not trustworthy (because there's .bat files in the zip), Firefox says its fine.
There is no malicious code in the zip, you can edit each individual batch file in the Resource folder to see the code. Its very simple and basic.
I disabled my antivirus, but when I run Install Visionary nothing happens. The CMD window opens and says it has been succesfuly installed but nothing has been installed, and nothing appeared in the app menu.
Edit: I went into the resource folder and then followed the steps from there and everything worked, except I still don't have the # symbol in terminal (even when entering "su") and ROM manager still gives me the same error.
lemonpartyz said:
I disabled my antivirus, but when I run Install Visionary nothing happens. The CMD window opens and says it has been succesfuly installed but nothing has been installed, and nothing appeared in the app menu.
Click to expand...
Click to collapse
go into the resource folder, edit the visionary install batch in notepad, delete the "cls" line, save and exit
rerun it with the phone attached. See if it truly installed successfully.
lemonpartyz said:
I disabled my antivirus, but when I run Install Visionary nothing happens. The CMD window opens and says it has been succesfuly installed but nothing has been installed, and nothing appeared in the app menu.
Edit: I went into the resource folder and then followed the steps from there and everything worked, except I still don't have the # symbol in terminal (even when entering "su") and ROM manager still gives me the same error.
Click to expand...
Click to collapse
you dont need to use the termial in my method.
Once visionary is installed, and you run it, and everything is done exactly whats described in my 9 easy steps thread (along with outcomes along the way), then you should be perm rooted, with s-off and eng-off with supercid.
I managed to install visionary with your method, however when running Eng-S I encountered the error "Bootloader corrupt, DO NOT REBOOT! Seek help from XDA!"
Help?
Edit: Followed the advice here http://forum.xda-developers.com/showthread.php?p=14936635 and s-off worked properly this time. Hopefully my DHD won't brick on reboot. Could super user be the problem? it never asks me for permissions or anything, all I have is an icon and a blank screen when i open the app.
Edit2: Rom manager took three attempts to install correctly. Still the same result "An error occurred while attempting to run privileged commands!"
FML
lemonpartyz said:
I managed to install visionary with your method, however when running Eng-S I encountered the error "Bootloader corrupt, DO NOT REBOOT! Seek help from XDA!"
Help?
Edit: Followed the advice here http://forum.xda-developers.com/showthread.php?p=14936635 and s-off worked properly this time. Hopefully my DHD won't brick on reboot. Could super user be the problem? it never asks me for permissions or anything, all I have is an icon and a blank screen when i open the app.
Edit2: Rom manager took three attempts to install correctly. Still the same result "An error occurred while attempting to run privileged commands!"
FML
Click to expand...
Click to collapse
looks like the superuser application isnt running properly.
I would use the 1.32 ruu (not the pd98img.zip off the sd) and then from a fresh install (without resoring any data other than google account to visit the market)
run through the visionary, s-off tool, eng-off tool, and then reboot again, then install rom manager from the market, run it, it should ask you for permission and may hang for a second, and then say you have about 5 seconds to allow root permissions.
Then install rom's away. if you're not into making seperate rom specific app folders on your sd card, google JSL Er3BuS. its a sense 3 rom without the extra scripts.
How do I install the 1.32 RUU if I can't install it from the SD card?
Thanks!
lemonpartyz said:
How do I install the 1.32 RUU if I can't install it from the SD card?
Thanks!
Click to expand...
Click to collapse
It is very easy mate,
1. Download the RUU of your choice from http://shipped-roms.com/index.php?category=android&model=Ace
2. Put your phone in charge mode only with USB debug on.
3. Make sure you have HTC Sync installed on your PC, and close HTC Sync application from your system bar in windows (make sure that HTC Sync is not running as all you need is the driver)
4. Right click on the RUU file and select "Run as Administrator"
5. Connect your DHD by the USB cable to your PC.
6. Click some boxed and "next"s.
7. Waiting!
8. Profit!
I tried following the steps here http://forum.xda-developers.com/showthread.php?t=841890
But got the error "ERROR [120]: Low MAIN BATTERY POWER. When the battery is above 30%.
This is getting ridiculous lol
I'm sorry I'm such a bother.
naailalzuhir said:
It is very easy mate,
1. Download the RUU of your choice from http://shipped-roms.com/index.php?category=android&model=Ace
2. Put your phone in charge mode only with USB debug on.
3. Make sure you have HTC Sync installed on your PC, and close HTC Sync application from your system bar in windows (make sure that HTC Sync is not running as all you need is the driver)
4. Right click on the RUU file and select "Run as Administrator"
5. Connect your DHD by the USB cable to your PC.
6. Click some boxed and "next"s.
7. Waiting!
8. Profit!
Click to expand...
Click to collapse
Tried this, now the update process has taken 45 minutes.
Well, it took 5 hours to finish, but finish it finally did. Rom manager installed no problem, flashed no problem and I am in the process of installing cryogen. Thanks everyone for their help and kind words.
Fingers crossed cryogen works.
I'm going away for the weekend, but when I come back I'll update this thread with the full details of what went down so hopefully someone will be helped by my many many hours spent raging.
-Lemonpartyz
lemonpartyz said:
Well, it took 5 hours to finish, but finish it finally did. Rom manager installed no problem, flashed no problem and I am in the process of installing cryogen. Thanks everyone for their help.
Click to expand...
Click to collapse
Glad its sorted for you , and hoping it status that way...enjoy your custom roms setting your phone free
Look forward to your post letting us know how its going.
Sent from outer space on my DHD running beatmod gingersense v1.3
Alright, so, I guess I'm not the only person having issues with the current versions of ICS, which is kinda comforting. If you can't update your SU binary in an ICS rom because your SU app tell you you're not S-Off, that means the bootloader partition was somehow damaged and forgot you're S-Off, so here's a detailed guide of what I did to get my phone up and running again.
This is also a great guide to help fix any stability problems your phone is having in general.
If you just need to unroot to send the phone back to Verizon or to sell it to someone, stop after step 17 and reading everything after it, but before step 18.
***WARNING***
If you do not follow these directions perfectly, you have a chance of damaging your phone. Part of this process involves flashing hboot manually through ADB, which is dangerous. PLEASE PAY SPECIFIC ATTENTION TO THAT SECTION OF THIS GUIDE. If you don't, your phone is going to be a very depressing paperweight.
IF AT ANY TIME YOUR PHONE TRIES TO ACCEPT AN OTA YOU NEED TO DENY IT! Because of how the Revolutionary Team's S-Off Tool works, we need to be in Froyo to flash hboot manually. An OTA will only get in the way!
Make sure your phone has a decent amount of battery (More than 50%) and keep it plugged in whenever you boot to hboot to be safe. If your phone powers off or dies when flashing a PG32IMG.zip, BAD BAD BAD things will happen!
I am also not responsible for anything that happens to your phone. If you're rooted and S-Off, you already know the dangers, so be smart!
Before I get started though, I have some people to credit, as their tools are used in this guide.
Thanks to:
notluK for his Unroot Guide on Android Central. Pretty much all of this guide is a direct kang/plagiarization from him, with minor changes due to file hosting fiascos.
CLSShortFuse for his SuperOneClick tool
The Revolutionary Team for their S-Off Tool
The unrEVOked Team for hosting the HTC Fastboot drivers
I think that's it... now, for your bacon.
NOTE: I do not have the original md5 sums for these files, so don't ask. Just download over a reliable connection (NOT ON YOUR PHONE!).
Pre-Requisites:
HTC Fastboot Drivers
Android SDK
Froyo (2.2.1) PG32IMG.zip
Gingerbread (2.3.3) PG32IMG.zip
Super SU ZIP from here
And a significant amount of time and patience
Okay... here goes. Please make sure to keep all of the above files on your PC to be safe. They are always good to have in case your phone goes screwy.
1. Download and install the Android SDK, install the HTC drivers and then reboot your PC. (If your SDK is fully functional and you already have the Fastboot drivers installed, just skip this step.)
2. Put the Froyo RUU zip on the root of your SD card and rename it to PG32IMG.zip (if Windows is hiding your file extensions, don't add the .zip to the end).
3. Boot your phone into the Bootloader (Vol Down + Power while off)
4. Press Vol Up to accept the update
5. Reboot phone when done (It may power off to a black screen instead of actually rebooting. Don't panic, just turn the phone on like you normally would ) When it's done booting, delete the PG32IMG.zip from the SD.
6. Check your OS version under Menu>Settings>About Phone>Software Information. Verify your OS version as 2.2.1.
7. Enable USB Debugging under Menu>Settings>Applications>Development
8. Plug in your phone and run the SuperOneClick root tool. When it asks if you want Busybox installed, say Yes. This is important, as you will need Busybox to verify the md5 of the hboot image you are about to flash to your phone manually.
9. Reboot your phone
10. Find the Froyo PG32IMG.zip on your computer and find the hboot_0.97.0000_336906.nb0 file inside. Extract it and put it in the platform-tools folder of your SDK.
11. Make sure your phone is still plugged in and then open your Command Prompt/Terminal and cd to your SDK's platform-tools folder, and follow the adb commands below, with your phone still plugged in, of course!
EXAMPLE: This is where mine is, yours may be different, so check!
Code:
cd C:\android\platform-tools\
Once that's done, continue:
Code:
adb devices (make sure ADB sees your phone if not, this is an appropriate time to ask for help :))
adb root
adb remount
adb push hboot_0.97.0000_336906.nb0 /data/local/
STOP HERE! If you're a dummy and didn't install Busybox with your SuperOneClick, download a Busybox Installer app from the Market and install it to /system/xbin/.
12. Now, do:
Code:
adb shell
su
/system/xbin/busybox md5sum /data/local/hboot_0.97.0000_336906.nb0
If your answer is not affe3dc9abe9d3a8c8bb3ba0ee5176ac, stop now and reboot your phone, then start over again at step 11.
***WARNING***
If you skip this step, you're a big, dumb idiot. This next step involves flashing something to what is probably the most important partition on your phone. If you mess this up, no one can help you, and your phone is permanent brick.
13. If the md5sums match, continue:
Code:
adb shell dd if=/data/local/hboot_0.97.0000_336906.nb0 of=/dev/block/mmcblk0p18
14. Verify the partition's md5sum to be extra-safe. If it's not exactly the same as the original md5 above, DO NOT REBOOT YOUR PHONE! Just start at step 11 again.
Code:
adb shell /system/xbin/busybox md5sum /dev/block/mmcblk0p18
15. Go into your Settings and disable Fast Boot (I don't remember where this is on the 2.2.1 firmware, so look around until you find it). Now, put the 2.3.3 PG32IMG.zip on the root of your SD and boot into hboot like you did before (Vol Down + Power while off).
16. Press Vol Up to accept the update.
17. Reboot into GB when done.
***WARNING***
If you accept the 2.3.4 OTA before going S-Off, you will have no way of reverting and back and re-rooting, SO DON'T DO IT!
The above may not be true, but I'm pretty sure it is, so PLEASE, for your own good, DON'T ACCEPT THE OTA!
If you needed to unroot to send the phone back to Verizon/wherever you got it from, or to sell it, this is the place to stop. If you're selling the phone to someone and they know what rooting is, they'll thank you for not updating to 2.3.4.
18. Run Revolutionary like you did before and accept the installation of ClockworkMod recovery (It'll be an old version, but that's okay).
19. Put the SuperUser zip from earlier on your SD and flash it like normal. (Backup first if you want to have a backup of factory stock unrooted)
20. Profit!
At this point, your phone is now at root 2.3.3 stock and S-Off again! Update your ClockworkMod recovery (or use 4ext, which I like a lot), make a backup (PLEASE, MAKE A BACKUP!) and then flash the rom of your choice, probably an ICS one.
Feel free to update your radio and stuff too. Things should be working much better than before.
And, to be safe, never OC past 1.3ghz. You shouldn't ever need to anyway, and it can break things, which means you'll have to do this all over again. Overclocking too high and my phone overheating is how I got into this situation in the first place, so I'm not just blowing hot air here. (Haha, get it? )
If anybody has any questions (please, don't bombard me with them ), feel free to post here and I'll do my best to respond in a helpful and timely manner.
If this helped you, click the "Thanks" button, or I'ma find you!
Happy flashing!
^^ should be stickied
thx for the legwork gathering and re-uploading all the files to new sharing sites.
ballisticn8 said:
^^ should be stickied
thx for the legwork gathering and re-uploading all the files to new sharing sites.
Click to expand...
Click to collapse
I'm glad this is useful! I have all the RUU files saved on my pc too, so if the links do go bad at some point, I still have them and can re-upload.
RegnierD said:
I'm glad this is useful! I have all the RUU files saved on my pc too, so if the links do go bad at some point, I still have them and can re-upload.
Click to expand...
Click to collapse
Links are definitely bad. Any chance you still have the files?
I found the Froyo RUU, but I still need the latest Gingerbread RUU.
This helps a lot thanks
Reg, could update the links for the Froyo and GB RUU's? Thanks!
I'll post new links sometime today, guys.
RegnierD said:
I'll post new links sometime today, guys.
Click to expand...
Click to collapse
Thanks you!!
the RUU files can be found here:
http://goo-inside.me/vivow/ruu
Does anyone have the 2.3.3 stock kernel? I tried another and now wifi won't enable
nevermind!... lol
my phone isn't charging (read that many users have had problems with the charging port on this phone), i just unrooted and s-off'ed. i'm on froyo now. should i download 2.3.3? where can i get it and would that be enough to get a new phone under warranty? or do i need to have the latest OTA 2.3.4? thanks in advance and i apologize for all the questions
ballisticn8 said:
^^ should be stickied
thx for the legwork gathering and re-uploading all the files to new sharing sites.
Click to expand...
Click to collapse
Now stickied
If I helped, give thanks, if you please.
........Death before dishonor........
hokieputter said:
the RUU files can be found here:
http://goo-inside.me/vivow/ruu
Click to expand...
Click to collapse
which one should i download if i just want the stock 2.3.3 so that i can return my phone for warranty? thanks.
The links are bad. I need the two PG32IMG files... My phone is not fairing well =/
S-On
Where in the guide should I stop if i want to go from s-off back to s-on so i can get a replacement phone?
smayer85 said:
Where in the guide should I stop if i want to go from s-off back to s-on so i can get a replacement phone?
Click to expand...
Click to collapse
RegnierD said:
17. Reboot into GB when done.
***WARNING***
If you accept the 2.3.4 OTA before going S-Off, you will have no way of reverting and back and re-rooting, SO DON'T DO IT!
The above may not be true, but I'm pretty sure it is, so PLEASE, for your own good, DON'T ACCEPT THE OTA!
If you needed to unroot to send the phone back to Verizon/wherever you got it from, or to sell it, this is the place to stop. If you're selling the phone to someone and they know what rooting is, they'll thank you for not updating to 2.3.4.
Click to expand...
Click to collapse
Reading helps.
I cannot get android SDK to install, it says "Java SE Development Kit (JDK) not found. Error: Failed to find Java version for 'C:\Windows\system32\java.exe': [2] The system cannot find the file specified." I have went and tried to install the java it says to but that won't work either. Should I uninstall any java I have installed and try then? My phone bootloops everytime i restart causing me to factory reset it so I need to get a replacement. Thank you.
Edit: Got the java to install after deleting and also have android SDK installing all the stuff now.
New issue, sorry for so many questions im kind of a noob, but when i try to adb root it says something about not able to in production. Does it affect me that my sdk folder in on a seperate HDD from c:\? I'm gonna try to redo it now and hopefully have this working this afternoon. Also, cmd will not let me cd to my SDK folder.
Mount error
When I enter the remount command an error is returned stating: adb remount failed: unknown error: 0
Anyone have any ideas how to resolve this?
Thanks
I'm so confused, the RUU just closes after the initial installsheild window. Bar fills then the window disappears after a few seconds disappears from task manager.
windows 10 current updates
Labeled said:
I'm so confused, the RUU just closes after the initial installsheild window. Bar fills then the window disappears after a few seconds disappears from task manager.
windows 10 current updates
Click to expand...
Click to collapse
Uninstall HTC sync manager but leave the drivers if you have it installed. And see if you can flash the same RUU via the zip and SD card method. Much easier! RUU.exe files are sh!t
Mr Hofs said:
Uninstall HTC sync manager but leave the drivers if you have it installed. And see if you can flash the same RUU via the zip and SD card method. Much easier! RUU.exe files are sh!t
Click to expand...
Click to collapse
The zip doesn't work from the SD card, even after having successfully and completely updated. 2 out of the 3 PCs I had tried the RUU.exe on, the same thing happened as with the OP - the RUU ran the extraction and then just closed.
This method works, but only if you can get the RUU.exe to work - which it did for me fine after following this method on the 1 out of the 3 PCs that the RUU worked on: https://forum.xda-developers.com/showpost.php?p=75167460&postcount=4049
roirraW "edor" ehT said:
The zip doesn't work from the SD card, even after having successfully and completely updated. 2 out of the 3 PCs I had tried the RUU.exe on, the same thing happened as with the OP - the RUU ran the extraction and then just closed.
This method works, but only if you can get the RUU.exe to work - which it did for me fine after following this method on the 1 out of the 3 PCs that the RUU worked on: [URL="[/URL].
Click to expand...
Click to collapse
I don't even know what RUU he is talking about :laugh: hence the global answer
Mr Hofs said:
I don't even know what RUU he is talking about :laugh: hence the global answer
Click to expand...
Click to collapse
Of course I'm assuming, but it's a safe assumption. Likely the recent Oreo RUU.exe that is either unofficial or at minimum, early. Even if it were another RUU, this method is general too - so good knowledge to have.
Edit: fixed my link in my previous post.
Sorry, the exe for us unlocked oreo RUU, I figured it out it didn't have a visual c++ 2008 x86(not 64) for whatever reason it just force closes rather than informing you to download the dependencies.
I'm not able to use it though because of the signature error, somehow my version is now 2.51.617.21, I can only find that version for the Verizon variant which is what I think is screwing it up?
I had the same problem; installing VC redist 2008 sp1 enabled the RUU to run
Chatter in other threads suggests that this is a beta RUU and won't install onto S-ON devices since the RUU requires flashing its extracted firmware manually first, which requires S-OFF due to lack of htc signatures required for S-ON devices.
Fortunately, the "erasing user data" before halting due to signature error didn't seem to actually erase anything.
Decrypting and flashing the 2PS6IMG.zip via download mode fails also.
For anyone who didn't get the RUU before it was pulled, and even though it's not likely to be official if you still want it, here's everything you need to update in one place as long as you're either U.S. Unlocked with S-OFF or have changed your MID and CID.
Every file is numbered to make it clear the order of steps to take.
https://androidfilehost.com/?w=files&flid=240833