• 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.
you certainly would have saved yourself alot of headache if youd read the forum first and followed advices to leave s-off. rerooting would have been easy if you werent now stuck with an s-on hboot.

as for your file prollem,you will download mini-adb_inc.zip and unzip or extact it. windows 7 you may be able to right click,then click extract. with other OS you may need a utility such as 7-zip.

this should leave you with a regular,non-zipped folder called mini-adb_inc. just take this folder and drag and drop,or copy and paste,or use whatever means your comfortable moving files and place it on your C drive,not inside any folders.

then when you open your command window,and enter cd c:\mini-adb_inc your prompt should change to: "mini-adb_inc>" indicating that youve successfully changed to that directory.

if you get an erroro message instead,you have either:
1)placed the non-zipped folder somewhere other than the root of C
2)not unzipped the folder
3)inadvertantly changed or not correctly typed the name of the non-zipped folder. just make sure the <file name> matches what your folder is called when typing in cd c:\<file name>

once youve successfully unzipped and placed the folder in the right spot,and changed to it in the command window,the "md5 sums" commands should work,as those files are contained within the folder.

in order for the other commands to work,youll need to have installed drivers at some point in doing this,or for prior projects. make sure "usb debugging" is checked on. since you got unrevoked 3.22 to work,you should have working drivers,and everything should go smoothly from this point.

just make sure to read the notes on flashing PB31IMG files,as thats the biggest issue folks seem tohave with the downgrade.

hope that helps :)
 
Morning everyone, I followed the instructions in the OP on this post and have gotten my Inc1 rooted and s-off.

Excellent, and thank you!!!

One question I have though (and I wonder if there's not something I missed, even though it all seems to be working), is what to do with the constant reminders/nags about the system update that's now available?

I'm guessing Verizon noticed I wasn't 2.3.4 anymore..... :cool:


And diggin enough through the thread, I found my answer. :)

scotty85 said:
Glad you found it useful :)

As for your question,if you're now rooted and running clockwork recovery,the update will not actually work. Your best bet to avoid constantly seeing it is to flash a custom rom.
Click to expand...
 
Hey when i try to do this root i plug my phone in to do the unrevoked 3.22 and it will do its thing for a while, and then it will say "Communications with phone unexpectedly interrupted. Try Again." and then it will reboot my phone to a screen that says ClockworkMod Recovery v5.0.2.0 and it has some options i have tried redoing the the unrevoked but it always does this. Also i am pretty sure i installed the drivers correctly. can someone help me I am a noob in this kind of stuff
 
stsoccerfreak said:
Hey when i try to do this root i plug my phone in to do the unrevoked 3.22 and it will do its thing for a while, and then it will say "Communications with phone unexpectedly interrupted. Try Again." and then it will reboot my phone to a screen that says ClockworkMod Recovery v5.0.2.0 and it has some options i have tried redoing the the unrevoked but it always does this. Also i am pretty sure i installed the drivers correctly. can someone help me I am a noob in this kind of stuff
Click to expand...


if youre getting a screen that says clockwork mod recovery v5.0.2.0 then youre almost there! have you checked to see if the superuser app is in your app drawer? the process may have completed,despite the error message.

if the su app is indeed missing,no worry,just grab the superuser .zip file in the other sticky(regain root with s-off) and flash that in clockwork mod recovery. you will need to place it on the root of your sd card,then use the menu options in clockwork to flash it(wipe cache and dalvik cache for good measure). you will navigate clockwork with the optic trackpad thingy. push it to select(not the power button ;))

once youve successfully flashed superuser and hes working and grantiing permissions,you can continue on to get s-off :)
 
I've tried this a few times on my DINC and I can't get it rooted. Unrevoked works fine, it loads the clockwork recovery image and the device reboots, I see the screen during this process and unrevoked says root worked. However, when I reboot, no go.

One thing to note, after unrevoked says it is good, clockwork does throw an error that I found is because it didn't mount the SD card... it doesn't seem to affect it, though. I did do a backup and that worked.

My main thought at this point is my version. I just purchased this phone and it came with

However, it wants to do an OTA update - "Android Software Update (4.08.605.2)" - 8.6MB, and I'm wondering if that should be applied before this root process will work properly.

The Android version is 2.3.4 - build 4.06.605.3

Any thoughts on how I can resolve this?

Thanks so much for posting this information and helping us all out - it is greatly appreciated.
 
dandidit said:
I've tried this a few times on my DINC and I can't get it rooted. Unrevoked works fine, it loads the clockwork recovery image and the device reboots, I see the screen during this process and unrevoked says root worked. However, when I reboot, no go.

One thing to note, after unrevoked says it is good, clockwork does throw an error that I found is because it didn't mount the SD card... it doesn't seem to affect it, though. I did do a backup and that worked.

My main thought at this point is my version. I just purchased this phone and it came with

However, it wants to do an OTA update - "Android Software Update (4.08.605.2)" - 8.6MB, and I'm wondering if that should be applied before this root process will work properly.

The Android version is 2.3.4 - build 4.06.605.3

Any thoughts on how I can resolve this?

Thanks so much for posting this information and helping us all out - it is greatly appreciated.
Click to expand...

Before I tried rooting mine I thought it would be a good idea to be up to date on updates so I did a factory reset (I knew there was an OTA from Oct. that never installed because of low space) Once I did the reset, the update installed right away to 4.08.605.2 I then rooted the phone. Dont know if that made a difference or not. Plus I wasn't planning on downgrading.
 
clipperqb said:
Before I tried rooting mine I thought it would be a good idea to be up to date on updates so I did a factory reset (I knew there was an OTA from Oct. that never installed because of low space) Once I did the reset, the update installed right away to 4.08.605.2 I then rooted the phone. Dont know if that made a difference or not. Plus I wasn't planning on downgrading.
Click to expand...

That is very helpful - I'm thinking I need to do that update and will do so shortly and report back. Thanks!
 
ruh roh - decided to install the update and do a factory reset before trying to root again. Now, when it boots I get a message saying "system UID inconsistent" Anyone got any tips on how to resolve this?

O shoot - It just asked me to apply the same android update (4.08.605.2) so it must not have done so last time. I tried again and it just says rebooting now... and sits there. Any way to know what it is or isn't doing? I'll just wait and see what happens.

And, what might this indicate? Why would this happen?
 
one more data point: I can still load into clockwork 5.0.2.0 per the instructions, but after loading it says (and always has):

waiting for SD card to mount (20s)
card mounted
verifying SD card marker
SD card marker not found
checking internal sd card marker
error verifying extendedcommand
error processing ROM manager script. Please verify you have ROM manager v4.4.0.0 or higher installed
/tmp/recover.log was copied to /sdcard/clockworkmod/recovery.log. please open Rom manager to report the issue

Any ideas on this issue or how it may be related...?

Thanks again.
 
dandidit, not sure if I'm too late, but if you're still running 4.06, you don't actually need to follow the instructions on this post! Simply avoid running the update, go to unREVoked's site, and follow the directions from there.
 
no, you are not too late... I'm still on .06

Also, is it important that this phone is not currently activated? That shouldn't matter, should it?
 
As far as I know, no. I've read where people simply use the DINC as a mp3 with wifi, similar to an iPod Touch, and are still obtaining root.
 
oh my... where to start :eek:

dandidit said:
I've tried this a few times on my DINC and I can't get it rooted. Unrevoked works fine, it loads the clockwork recovery image and the device reboots, I see the screen during this process and unrevoked says root worked. However, when I reboot, no go.

what do you mean,"a no go"? do you mean that you dont have the superuser app in your app drawer? or it just isnt granting permissions?

if the superuser app is missing,simply follow the directions in post #730. you have a custom recovery,youre in good shape. you dont need to run unrevoked more times,or accept updates.

if you mean that SU isnt granting permissions,you do need to try and run some root only apps. titanium backup,root explorer,rom manager,are all apps that will request SU permissions. once youve tried a couple and they fail,go to setting/applications/manage apps/superuser and clear its data. it should work after that.


My main thought at this point is my version. I just purchased this phone and it came with

However, it wants to do an OTA update - "Android Software Update (4.08.605.2)" - 8.6MB, and I'm wondering if that should be applied before this root process will work properly.
The Android version is 2.3.4 - build 4.06.605.3

this method works after doing this update,but the update is in no way shape or form required.
Click to expand...

dandidit said:
ruh roh - decided to install the update and do a factory reset before trying to root again. Now, when it boots I get a message saying "system UID inconsistent" Anyone got any tips on how to resolve this?
as youve figured out,you just needed to do a factory reset in recovery
O shoot - It just asked me to apply the same android update (4.08.605.2) so it must not have done so last time. I tried again and it just says rebooting now... and sits there. Any way to know what it is or isn't doing? I'll just wait and see what happens.

you are now running clockwork recovery,wich is effectively blocking your OTA. you need a stock recovery to accept an OTA update.
Click to expand...

dandidit said:
one more data point: I can still load into clockwork 5.0.2.0 per the instructions, but after loading it says (and always has):

waiting for SD card to mount (20s)
card mounted
verifying SD card marker
SD card marker not found
checking internal sd card marker
error verifying extendedcommand
error processing ROM manager script. Please verify you have ROM manager v4.4.0.0 or higher installed
/tmp/recover.log was copied to /sdcard/clockworkmod/recovery.log. please open Rom manager to report the issue

Any ideas on this issue or how it may be related...?

i wouldnt really worry about this right now. its not affecting anything.
Click to expand...


dandidit said:
Update: I no longer have the UID issue. No matter how many times I did a factory reset via droid, no go. I did one via clockwork and that fixed it.
the "factory reset" option in the setting menu is connected to the stock recovery. using it now,wont do anything. as you found,you must manually do things in clockwork.

Now I'm stuck at trying to apply the 4.08 update (seems many people are) and will keep trying per Second GB Update/Patch Won't Reboot Issue - SOLVED! - Page 4 - Android Forums at AndroidCentral.com

again,you cant install the update with while running clockwork. your best bet is continue the process and achieve s-off. you can then flash a custom rom based on the 4.08 ota. you will have a much better experience this way,as the basic code is the same,with a few tweeks to make it better.
Click to expand...

gkinsella2 said:
dandidit, not sure if I'm too late, but if you're still running 4.06, you don't actually need to follow the instructions on this post! Simply avoid running the update, go to unREVoked's site, and follow the directions from there.

unless im misunderstanding what youre saying here,you do need the directions here to root/downgrade/reroot. the 4.06 update to GB 2.3.4 broke the "rage against the cage" exploit that unrevoked forever uses.
Click to expand...

so to recap,and further assist you,you need to answer:

what do you mean root is "a no go"?
1)do you mean that you dont have the superuser app in your app drawer?
or
2)superuser is there but not working
or
3)something different? :eek:
 
Quick question: If I had root, should S-on be S-off? It is currently and has always been S-on

I'm not exactly sure what superuser in my app drawer should look like - I've got superuser permissions, but it is blank when I launch it. In the past it did have some other information in it, but it was all greyed out...

I'll try installing the other apps and see what happens.
 
ok, I didn't have a superuser app, but I did install rom manager, updated it and I'm running a backup of my current rom right now. It did say I needed root to install and it requested access and it said it worked, so it seems I have root. It wasn't clear to me about the whole S-on S-off setting. Can you explain what that means in regards to having root? Is that not a 1:1 relationship with root / non-root ?

Thanks.
 
alright, I'm further along. I completed the mini-adb steps, had to SU (phone did the popup and I allowed) and I'm getting ready to do the boot, but not until it charges up more. I appreciate the help and will update shortly.
 
dandidit said:
Quick question: If I had root, should S-on be S-off? It is currently and has always been S-on
Click to expand...

unless youve performend the steps to dongrade and reroot with unrevoked,then you should be s-on.

the whole point of this guide is to downgrade gingerbread back to froyo so that unrevoked 3 can be run,and s-off achieved

in a nutshell: s-off stands for security off. its a flag in the radio that tells the bootloader wether or not it needs to perform checks for htc signatures before letting it flash.

this offers several advantages: being able to flash radios and recoveries easily in hboot,as well as being able to downgrade firmware if you want,without performing a bunch of steps and adb commands.

being s-off,as long as you dont randomly,haphazzardly flash things,is IMO much safer,as it allows more options to recovery a soft-bricked phone.

from the sounds of your other posts,you are indeed rooted :)

with the adb commands,just make sure each command gives the same output as in my codebox in the first post. then make sure youve read and understood the notes on flashing the PB31IMG file,since this is a common prollem folks have. :eek:

been a long day,and ive got some stuff to do before i crash,but ill try and watch your progress :)
 
Total rooting newbie here. I have a bone stock DInc with 2.3.4 and 4.08. If I want to root ONLY does the process wipe my phone? Do I need to copy my SD card and phone memory to a folder to replace everything afterwards?

Thinking of giving this a go tonight. Just follow the directions in the OP?
 
TzuDohNihm said:
Total rooting newbie here. I have a bone stock DInc with 2.3.4 and 4.08. If I want to root ONLY does the process wipe my phone? Do I need to copy my SD card and phone memory to a folder to replace everything afterwards?

Thinking of giving this a go tonight. Just follow the directions in the OP?
Click to expand...

the only reason you should need to back up your sd card,is if you find it to be formatted FAT,or something else,and need to reformat it FAT32. otherwise its contents are safe,but feel free to back them up for some peace of mind.

running unrevoked 3.22 should give you root access with s-on,and will not wipe your phone. technically you could stop there,but IMO its well worth the effort to continue the process and become s-off. if you make a nandroid backup prior to downgrading,you will be able to restore it after downgrading and achieving s-off.

so in the end,you CAN do this without losing any of your setup and data,as long as you make the backup. :)
 
hsxpunisher said:
still waiting for the charger to get here probably another week or so...if this doesnt work i get to go back to my old original ENV until i can scrape together enough for a new phone
Click to expand...

youre not near dayton,oh are you? :eek: id be happy to let you come over and pop a good battery in and run the RUU to get you up and going if you were close
enuff to do so. :)
 
Status
Not open for further replies.
Back
Top Bottom