• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [How To] Root 2.3.4/downgrade and Get S-off

Status
Not open for further replies.
"-plug in your phone,and assuming you installed the drivers correctly,unrevoked 3.22 will start. let it do its thing. it will reboot a couple of times. when its finished,it may leave you on a blank screen. if this is the case,pull the battery and reboot.-"

It rebooted once, sat on my home screen, nothing, and unrevoked said "Flashing Recovery Image. Do not touch your phone!". I took a chance an quit unrevoked, and unplugged my dinc. My dinc still works fine, still no root :( but working fine. Reboots and enters hboot just as per usual.

I am also running a virgin install of Window$ XP inside a VirtualBox VM as I run ubuntu Lucid Lynx 10.04.3.

I'm not new to rooting, just new to htc and this whole hboot thing. I came from an LG ally, Velocity 1.2.1.
 
I installed the drivers successfully -- exactly every step shown on the given page
However, when I power on to normal mode (charge only and USB debugging on), my computer (win7 64b) doesn't recognize the phone, it keeps showing unrecognized usb device.

when I ran the unrEVOked3, no device could be found.

any help?

scotty85 said:
-install the drivers as described on unrevokeds page above.
-place your phone in charge mode,and make sure usb debugging is checked ON in settings/applications/development.
-extract the contents of the unrevoked 3.22 .zip. open the folder, right click on "reflash" and run as administrator if possible.
-click on "file" in the corner of the relfash window
-click custom recovery
-navigate to,and select your "recovery-clockwork-5.0.2.0-inc" image and select it. at the bottom of your reflash app window, it should now say "recovery:custom" and "waiting for device"[/CODE]
Click to expand...
 
FinalStorm said:
"-plug in your phone,and assuming you installed the drivers correctly,unrevoked 3.22 will start. let it do its thing. it will reboot a couple of times. when its finished,it may leave you on a blank screen. if this is the case,pull the battery and reboot.-"

It rebooted once, sat on my home screen, nothing, and unrevoked said "Flashing Recovery Image. Do not touch your phone!". I took a chance an quit unrevoked, and unplugged my dinc. My dinc still works fine, still no root :( but working fine. Reboots and enters hboot just as per usual.

I am also running a virgin install of Window$ XP inside a VirtualBox VM as I run ubuntu Lucid Lynx 10.04.3.

I'm not new to rooting, just new to htc and this whole hboot thing. I came from an LG ally, Velocity 1.2.1.
Click to expand...

sorry,no idea... i dont know if theres something about unrevoked that would affect it when running inside the VM. hopefully some others may have some insight.

simeonyu said:
I installed the drivers successfully -- exactly every step shown on the given page
However, when I power on to normal mode (charge only and USB debugging on), my computer (win7 64b) doesn't recognize the phone, it keeps showing unrecognized usb device.

when I ran the unrEVOked3, no device could be found.

any help?
Click to expand...

try rebooting your PC. it also sometimes helps to move the cable around to different ports,and try different cables.

try updating the drivers manually with the phone in fastboot,if you havent done that allready.

forget about it for 3 days and come back. <- thats a joke,dont take that seriously. i was trying a few days ago to install drivers for my nook color and did nothing but stay up way past my bedtime and become very fustrated. id type "adb devices" then just hear crickets chirping. :mad: yesterday i happened to have the nook plugged in,so for S&Gs opend a cmd window and typed "adb devices" and was finally rewarded with a serial number :eek: i have no idea why it wasnt working,or why it all of a sudden started. :confused:
 
scotty85 said:
sorry,no idea... i dont know if theres something about unrevoked that would affect it when running inside the VM. hopefully some others may have some insight.
Click to expand...

Thanks for trying scotty. Hopefully someone will have some ideas. I'm going to try again right now. It Probably won't work, but its worth a shot. If not, I'll grab one of my old machines and throw xp on it, and see if it works on some real hardware.

EDIT: Using Window$ on real H/W did the trick. Using an old lappy of mine it took 10 min after the Window$ install :) . VMs are a bit tricky i guess. Not S-Off yet, that will be a task for another day.
 
Cool,glad real hardware worked for ya :)

Just make a backup of your current setup,and you'll be able to go right back to it after the downgraade if you want.

Post up if you have any questions when you get around to the downgrade. Its well worth the effort to become s-off IMO :)
 
I have an Incredible 2.3.4 with this taken from HBOOT
Incrediblec XC Ship S-On
HBOOT-0.92.0000
Microp-0417
Touch Panel-ATMEL224_16ab
Radio-2.15.10.07.07

Ok, so here is my problem, I want to be rooted and I want S-off, but I cannot get anything done. The phone wouldn't recognize the SD Card, I got that taken care of. The phone does the 5 Vibrates when turning it on unless I have the USB plugged in and I do a battery pull. (This really screws up updates/RUU fixes where updates are necessary). And along those lines I tried an RUU back to 2.1 which didn't work because of the restart issue, but then I was able to run the update after booting into HBOOT USB but the RUU failed ultimately.

I've tried to gain root access through unrevoked 3.22, it simply says failed to push recovery, terminated. I've tried rooting using zergRush, it tells me that it has found a path and that its sending zergs, then it just stops without telling me what happened and kicks me back out of adb shell. This is a recurring problem, I will be in adb shell and then randomly and for no reason it was kick me out to the root of my computer.

I'm working on a Windows 7 64 bit machine, I have been using an ADB mini download, but have also tried working through the installed ADB with equal results.

If anyone has any idea of what I could be doing wrong or different please let me know. I really need some kind of help because I am at a major loss.
 
jfritzs2 said:
I have an Incredible 2.3.4 with this taken from HBOOT
Incrediblec XC Ship S-On
HBOOT-0.92.0000
Microp-0417
Touch Panel-ATMEL224_16ab
Radio-2.15.10.07.07

Ok, so here is my problem, I want to be rooted and I want S-off, but I cannot get anything done. The phone wouldn't recognize the SD Card, I got that taken care of. The phone does the 5 Vibrates when turning it on unless I have the USB plugged in and I do a battery pull. (This really screws up updates/RUU fixes where updates are necessary). And along those lines I tried an RUU back to 2.1 which didn't work because of the restart issue, but then I was able to run the update after booting into HBOOT USB but the RUU failed ultimately.

I've tried to gain root access through unrevoked 3.22, it simply says failed to push recovery, terminated. I've tried rooting using zergRush, it tells me that it has found a path and that its sending zergs, then it just stops without telling me what happened and kicks me back out of adb shell. This is a recurring problem, I will be in adb shell and then randomly and for no reason it was kick me out to the root of my computer.

I'm working on a Windows 7 64 bit machine, I have been using an ADB mini download, but have also tried working through the installed ADB with equal results.

If anyone has any idea of what I could be doing wrong or different please let me know. I really need some kind of help because I am at a major loss.
Click to expand...

You need to fix the 5 vibrates first:
http://androidforums.com/incredible-all-things-root/409991-5-vibs-death-fix.html
 
I've got the same problem as another user where for some reason the image file never gets unzipped when I run the bootloader. Here are the instructions I'm fuzzy on:
place the PB31IMG of 2.2 on the root of your sd card. rename PB31IMG.
Click to expand...
I'm not sure what this means. That's the same thing, no? The card is definitely FAT32 and the file is in the root of the card. I checked the MD5 checksum and it's the same. Downloaded the file twice with same results. Any other ideas?

*Edit* One strange thing is that Astro doesn't seem to find the .zip file in the SDCard. Anyone seen that before?
 
LowlySpartan said:
I've got the same problem as another user where for some reason the image file never gets unzipped when I run the bootloader. Here are the instructions I'm fuzzy on:
I'm not sure what this means. That's the same thing, no? The card is definitely FAT32 and the file is in the root of the card. I checked the MD5 checksum and it's the same. Downloaded the file twice with same results. Any other ideas?

*Edit* One strange thing is that Astro doesn't seem to find the .zip file in the SDCard. Anyone seen that before?
Click to expand...

That's bad. You sure the card is even being recognized at all? Can you see all the other SD contents? If so, you might be one of the few that would benefit by actually naming the file PB31IMG.zip in order to gain recognition.
 
@jfritzs2,
Your situation sounds rough, I see the quandry. Only idea I have are to try a different battery perhaps or maybe even try reflashing the newest (albeit not quite perfect) PB31IMG for Gingerbread. Maybe you just got a bad OTA update? Then retry the process again with a fresh 2.3.4 reload. Grasping at straws.
 
LowlySpartan said:
I've got the same problem as another user where for some reason the image file never gets unzipped when I run the bootloader. Here are the instructions I'm fuzzy on:
I'm not sure what this means. That's the same thing, no? The card is definitely FAT32 and the file is in the root of the card. I checked the MD5 checksum and it's the same. Downloaded the file twice with same results. Any other ideas?

*Edit* One strange thing is that Astro doesn't seem to find the .zip file in the SDCard. Anyone seen that before?
Click to expand...

as for "rename PB31IMG",just rename it to that if youre using windows. i wasnt 100% sure if the download was allready correctly named,or was actually names something like "PB31IMG_download_2.2". it should more accurately say "verify the name of the 2.2 downgrade is PB31IMG"

as far as not seeing,again,2 reasons:
1)card not fat32
2)file not correctly named

youll just have to figure out wich one. on a couple occasions a bad sd has caused prollems. you might try a reformat even if your sure your card is FAT32(cant be just FAT)

as far as astro not seeing,this is the question to answer:
iowabowtech said:
Can you see all the other SD contents?
Click to expand...

if the answer is yes,then no ive never see that :eek: make sure you havent accidentally placed PB31IMG inside a folder

if the answer is no,then i suspect you may be trying to view your sd while it is mounted to the PC for storage ;) astro wont see the sd at all in this situation. put your phone back in charge mode and see if the contents show up aagin :)

edit: as an afterthot,also make sure youre not accidentally putting the PB31IMG onto the emmc,as it will pop up an "open to view files" box also when you plug it in.
 
-insert evil laugh here- I am now in full control!!!!!! -further evil laughs-

Another successful root-downgrade-soff here. Now happily running CyanogenMod7.

I did have one problem, but easily fixed. After I flashed the RUU my dinc just bootlooped at the droid eye. So I just went back into hboot and flashed it again. a is well.

Thanks scotty for putting this guide together. Works like a charm.
 
I figured out the problem. For some reason the incredible that I have looks like it has two SD Cards. Didn't think that was possible on this thing. I was putting it on the wrong one. I checked the size of the SD Card within the options of the phone and could then tell which was which. I'm all good now. Thanks guys.
 
Yeah phone storage and sd card both come up when in disk drive mode. I make a phony folder called AA_SDCARD on mine so it's obvious which storage I'm dealing with. Since the contents are in alphabetical order its always front and center or...I'm looking at the phone storage instead.

Glad you got it.
 
Hello everyone, I followed the first part of this guide in the OP on my brothers S-LCD Inc and we were able to root and downgrade to Froyo from his leaked .2 GB. The only thing is for some reason, we didn't get S-OFF. The bootloader still shows S-ON. Because we were able to root and install the latest CWM 5.0.2.0 and he ended up installing MIUI which he wanted on his Incredible all along. Is there still a way to get S-OFF on the phone? Thanks.
 
google123 said:
Hello everyone, I followed the first part of this guide in the OP on my brothers S-LCD Inc and we were able to root and downgrade to Froyo from his leaked .2 GB. The only thing is for some reason, we didn't get S-OFF. The bootloader still shows S-ON. Because we were able to root and install the latest CWM 5.0.2.0 and he ended up installing MIUI which he wanted on his Incredible all along. Is there still a way to get S-OFF on the phone? Thanks.
Click to expand...

this has actually been addressed several times if you skim thru the thread ;)

all you need to do is flash the s-off tool in recovery:
public:forever [RootWiki]

glad it worked for you :)
 
Im stuck, this is mind boggling! I can find the same problem in the forums,just cant find a straight answer. Im using the above method to get back to 2.2 from 2.3.4, and s off is what im trying to get. I have an error saying status 42,just like above! unsupported radio verson/update failed/Check /sdcard/soff.log/ error in/data/local/unrevoked-foreverzip (Status 42) Installation aborted .tmp/recovery/log was copied to /sdcd a hand, it would really be appreciated. Thanks for all your hard work putting this together!

Ok, I tried it again, and I think its right, but still has s on and still 2.3.4? I did notice that I have SuperUser in my apps now? Downloading ROM manager, and trying to figure this out. I cannot access the live chat for some reason? This is tough!

Ok, Im attempting the downgrade now! Im apparently rooted? My phone is sLCD as well, will keep you up to date.
 
Just wanted to let you guys know that you can add another sLCD to the list of successful roots. Just around the time the update hit I was thinking of rooting my phone then I got the update and couldn't and had a million more reasons to root it. Thank you guys for putting this guide together I am by no means bad with phones or computers but this was my first root and it worked flawlessly up until using Unrevoked 3.32 to root on 2.2. Once I switched computers however the root went perfectly and now I have the latest CWM and Cyanogen on my phone with S-Off. Again thank you guys for all the trials and testing and coming up with this idea and guide it was very easy to follow.
 
-place the 2.2 downgrade on the root of your sd card,and verify it is named "PB31IMG". Does this mean put the entire folder on your sd card or just the image file? Sorry for all the questions! Thanks so much to Scott and everyone else lending a hand to Us. Its greatly appreciated!
 
jlsmelser said:
-place the 2.2 downgrade on the root of your sd card,and verify it is named "PB31IMG". Does this mean put the entire folder on your sd card or just the image file? Sorry for all the questions! Thanks so much to Scott and everyone else lending a hand to Us. Its greatly appreciated!
Click to expand...

Just the PB31IMG file to the root directory of your SD card. If that doesn't work, try renaming it to PB31IMG.zip.
 
Update: I am now rooted and running 2.2 with s off on sLCD Incredible. Thanks to Scotty and Iowa for their great work, I have read this thread front to back several times, I found renaming the PB31IMG file PB31IMG.zip made all the difference in attaining root and s off, Thanks to FinalStorm! To those who get discouraged, just keep reading and rereading the posts. I only used the unRevoked method, again many Thanks to all of you here. My phone is free! Now for the fun part!
 
Status
Not open for further replies.
Back
Top Bottom