• 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.
From the easier way thread: " put the file that you want to flash into the mini adb-folder". What file is that? The ROM? I think I'm getting somewhere... at least it seems I'm connected to the laptop now.

Thanks
 
Using the "easier way" method, I think I'm getting closer. Things fail at the command prompt when I enter "adb reboot bootloader'. I get "error: device not found".

Anyway... getting cross-eyed now. Will come back to it tomorrow.
 
smg65 said:
I'll check out that thread, Scotty. I haven't tried those things. But I'm must be missing a fundamental point. If I can't get into the phone at all... can't establish a data connection... and the menu items do not work at HBoot, how can I install anything or run anything? Is this something that can be done if I remove the SD card and install on it?

I'm sorry for being so dense! I'm going to go back and read the thread you mentioned above.
Click to expand...

have you tried installing PB31IMG in hboot? like when you downgraded? even if the sd card is not being recognized in a booted rom,it should still be recognized in hboot. the solution may be as simple as putting the froyo PB31IMG(the one that you used to downgrade when following the guide) back onto the sd card and letting is update.

your bootloader has 2 modes. "hboot" wich is the mode that its in when you turn off the phone and then hold vol down+power. in this mode you have the menu options you mention,plus the ability to flash software/firmware files.

if you use the power putton and vol rocked to select "fastboot" youll be in the bootloaders other mode. in this mode you can communicate with your PC to do different things,provided you have the proper drivers and the fastboot utility. since you used the guide to downgrade and s-off,ill assume you have both. typing in "fastboot devices" with your phone plugged in andin fastboot mode will verify. the fastboot utility you have as well,in your mini-adb_inc folder.

the menu options in "hboot" taking you to the hat are not of any concern. that actually what they are supposed to to. they typically will boot you to the stock recovery to perform the various options. since you have replaced the stock recovery with clockwork,chosing thes menu options sends you to the clockwork hat screen.

so to recap,id try:
1)put froyo PB31IMG back on your sd card. boot to hboot,if it finds the file,let it update.
2) if for some reason that fails,download this .exe file. once its downloaded,put your phone into the "fastboot" mode. right click on the .exe file,and run as administrator if your version of windows has that option. then just follow the onscreen directions. if you have a way to charge the battery fully prior to doing this,do so.
3) if neither of those works,we can try the ruu method that youre currently working on,ill try and answer those questions in the next post.
 
smg65 said:
I'll go back and try that. But how do I "place the phone in fastboot,put it in RUU mode" when the HBoot menus don't work, and after a minute or so, the clockwork menu comes up which doesn't appear to be operable?

I can see I'll be busy tonight trying this... that is unless you write and tell me to forget it! I hope I've learned my lesson! Although this is really the first device that I've truly boogered up! Thanks for your assistance. :-)
Click to expand...
fastboot is described above(power on into hboot. select "fastboot" from the hboot menu). ruu mode is,as per the directions,accesed by entering the command fastboot oem rebootRUU ;)

smg65 said:
Wow! What a pest I am! I'm beginning to hate myself! lol

Don't know if this would tell you anything, but I've removed my SD card and read it in my card reader on my laptop. Everything is there and intact, including my backups.

OK... over and out! Thanks!
Click to expand...
youre not being a pest. youre new to this,and its quite understandable youre a lil freaked out by the fact that your phone doesnt work :)

pretty sure theres nothing wrong with your sd card,but if you want to,you can back it up,then reformat it,making sure to select FAT32. at this point,tho,i do not believe this is neccessary.

smg65 said:
From the easier way thread: " put the file that you want to flash into the mini adb-folder". What file is that? The ROM? I think I'm getting somewhere... at least it seems I'm connected to the laptop now.

Thanks
Click to expand...
the file you want to flash can be literally anything. an hboot,splash screen,radio,a whole rom. in your case it will be a rom- the PB31IMG for froyo that you used to downgrade.

smg65 said:
Using the "easier way" method, I think I'm getting closer. Things fail at the command prompt when I enter "adb reboot bootloader'. I get "error: device not found".

Anyway... getting cross-eyed now. Will come back to it tomorrow.
Click to expand...

unless you got your phone to boot into the OS,the reboot bootloader command isnt working because its an ADB command,not a fastboot command.

adb(android debug bridge) is used to communicate with your phone when its functioning normally in the operating system.

you will need to use fastboot commands,since fastboot is the mode you can currently get to.

in order to use the easier way method,youll need to modify it a little:

-power on into hboot
-select fastboot with power button/vol rocker
-follow all of step 1
-in step 2,go from the "md5 sums" command to the "fastboot devices" command. skip over "adb devices" and "adb reboot bootloader" since they are adb commands and will not work in fastboot ;)

hope that helps :)
 
Hey Everyone,

I'm working on getting my wife's phone downgraded to fix some other issues.

I'm sorry if the following has been posted before....
scotty85 said:
exit to get out of your adb shell,and back to the "mini-adb_inc" prompt

adb reboot bootloader this will boot your phone to "fastboot" select "bootloader" with the power button.

hopefully what you will see now,is a blue status bar as your phone finds the PB31IMG,unpacks it,checks it,then asks if youd like to update. select yes to update with the volume up rocker. if youve never installed a full ruu in hboot,it will take a few minutes,so dont panic. place the phone gently down somewhere where it wont fall and spit out the battery. let it do its thing. push power to reboot when prompted.
Click to expand...

when I type adb reboot bootloader (the last quoted command above) I get an access denied error. I tried it as su (without exiting the adb shell) but then the phone didn't install the zip file. Any ideas on what I'm not doing correctly. I think I followed all of the steps correctly.

Any help would be greatly appreciated.

Loren
 
lorenjz said:
Hey Everyone,

I'm working on getting my wife's phone downgraded to fix some other issues.




when I type adb reboot bootloader (the last quoted command above) I get an access denied error. I tried it as su (without exiting the adb shell) but then the phone didn't install the zip file. Any ideas on what I'm not doing correctly. I think I followed all of the steps correctly.

Any help would be greatly appreciated.

Loren
Click to expand...

you need to be completely out of the shell,and the normal prompt.

you can accomplish the same thing by just powering off the phone and then powering on(vol down+power) into hboot. if hboot does not find the PB31IMG,there is something else wrong(reread the OP there are some tips for flashing PB31IMG files)
 
Got my phone back! THANK YOU, SCOTTY!!!!!! I really appreciate all the time and effort you put into helping me. Not that I needed it, but talk about restoring one's faith in mankind!! :-)

This fix from your 9:17 post (you sure went out of your way to help!) is what got me going. I will store all these posts away in a vault... just in case there's a "next time"!

1)put froyo PB31IMG back on your sd card. boot to hboot,if it finds the file,let it update.
2) if for some reason that fails,download this .exe file. once its downloaded,put your phone into the "fastboot" mode. right click on the .exe file,and run as administrator if your version of windows has that option. then just follow the onscreen directions. if you have a way to charge the battery fully prior to doing this,do so.
3) if neither of those works,we can try the ruu method that youre currently working on,ill try and answer those questions in the next post.

Again.. thank you so much!
 
Now... possibly heading for "new frontiers". Gotta make a decision about going from rooted 2.2 to the latest Gingerbread. I'll continue with my research, but also start a new thread.

Thanks again! :-)
 
Thank you all for such great info. Tearing my hair out trying to get this working on my Incredible. After running through the procedures in step 2, I went into Root Explorer to remove some bloatware. I renamed some apk's to *.bak then went back in to Root Explorer and noticed they reverted back to original names.

I felt like this was a little suspect so I used a Terminal Emulator to check root and it got me to #, but then gave me permissions errors when trying to mkdir in /system. I then downloaded a Root Checker and it says I have Root permission. Didn't trusted so tried running through the steps again after upgrading to ClockwordMod Recovery 5.0.2.0

What I'm getting is Unrevoked says "Done", but the process ends in the ClockworkMod 5.0.2.0 with the following error:

Code: 
ClockworkMod Recovery v5.0.2.0
Waiting for SD Card to mount (20s)
SD 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/recovery.log was copied to /sdcard/clockworkmod/recovery.log. Please open ROM Manager to report the issue.

Anybody have any ideas? Any help would be very much appreciated. Thanks!
 
jpfulton248 said:
Thank you all for such great info. Tearing my hair out trying to get this working on my Incredible. After running through the procedures in step 2, I went into Root Explorer to remove some bloatware. I renamed some apk's to *.bak then went back in to Root Explorer and noticed they reverted back to original names.

I felt like this was a little suspect so I used a Terminal Emulator to check root and it got me to #, but then gave me permissions errors when trying to mkdir in /system. I then downloaded a Root Checker and it says I have Root permission. Didn't trusted so tried running through the steps again after upgrading to ClockwordMod Recovery 5.0.2.0

What I'm getting is Unrevoked says "Done", but the process ends in the ClockworkMod 5.0.2.0 with the following error:

Code: 
ClockworkMod Recovery v5.0.2.0
Waiting for SD Card to mount (20s)
SD 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/recovery.log was copied to /sdcard/clockworkmod/recovery.log. Please open ROM Manager to report the issue.

Anybody have any ideas? Any help would be very much appreciated. Thanks!
Click to expand...

That error is normal after running unrevoked... when using root explorer are you changing the option that makes the directory read/write capable?
 
sdrawkcab25 said:
That error is normal after running unrevoked... when using root explorer are you changing the option that makes the directory read/write capable?
Click to expand...

No kidding... weird. Yeah changed to R/W and all seemed fine. And in hopes of keeping my post concise I didn't mention that I was able to remove two apps via rename to *.bak... so they're not in the drawer, however going back in to /system/app shows the names reverted back to just *.apk. And despite renaming other apk's they will not leave app drawer. AND, as mentioned, cannot mkdir in /system or /system/app ... not that it's an entire necessity but I planned on moving the apk's to a different directory rather than renaming them.

I guess I'm going to trying moving on to step 3 and see if I get anywhere. I'm just feeling like there's something that isn't 100% right with my root job. Any input?
 
jpfulton248 said:
I guess I'm going to trying moving on to step 3 and see if I get anywhere. I'm just feeling like there's something that isn't 100% right with my root job. Any input?
Click to expand...

if superuser granted permissions to root explorer,it should be fine for moving on to step 3.

if you plan to flash a custom rom after getting s-off,then i wouldnt worry too much about it. if you plan to come back to the backup that you make prior to downgrading,then you could go ahead and update superuser,it may just be the old version unrevoked installs has some issues with GB.

as ive said many times in this thread,the important function of unrevoked is to get you a custom recovery. superuser access is easily flashed in recovery of its out of date or missing :)

download and flash in recovery: superuser 3.0.7

a wipe of cache/dalvik cache is prolly not neccessary,but not a bad idea :)
 
scotty85 said:
if superuser granted permissions to root explorer,it should be fine for moving on to step 3.

if you plan to flash a custom rom after getting s-off,then i wouldnt worry too much about it. if you plan to come back to the backup that you make prior to downgrading,then you could go ahead and update superuser,it may just be the old version unrevoked installs has some issues with GB.

as ive said many times in this thread,the important function of unrevoked is to get you a custom recovery. superuser access is easily flashed in recovery of its out of date or missing :)

download and flash in recovery: superuser 3.0.7

a wipe of cache/dalvik cache is prolly not neccessary,but not a bad idea :)
Click to expand...

Many many thanks. With your help I now have s-off and root. Root explorer is acting "normally" and all else is what I expect. Thanks for your dedication.
 
Scotty,

I can tell by this forum that you are pretty much the man when it comes to this stuff. :) I have an Incredible 2 that I rooted following strict step-by-step instructions. I was reading comments from the original Incredible forum and started getting nostalgic so I pulled my phone out and charged her up. :D I wanted to root this phone, but it has 2.2 on it right now since it has been off for a while now. What process do I need to follow to get her rooted from this state? Thanks so much for your help. I would either A. like to test drive cyanogenmod, or B. perform a switch back to my Incredible again. Either way, I want to root her and see what old girl can do. I replaced her, because I dropped her in a pool. She obviously was able to be fixed, but that pushed me in the direction to get two Inc 2's for free through wirefly. I still love the small size of the original incredible and might even be willing to swap back and forth during times when my larger phone won't work.
 
twister8008 said:
Scotty,

I can tell by this forum that you are pretty much the man when it comes to this stuff. :) I have an Incredible 2 that I rooted following strict step-by-step instructions. I was reading comments from the original Incredible forum and started getting nostalgic so I pulled my phone out and charged her up. :D I wanted to root this phone, but it has 2.2 on it right now since it has been off for a while now. What process do I need to follow to get her rooted from this state? Thanks so much for your help. I would either A. like to test drive cyanogenmod, or B. perform a switch back to my Incredible again. Either way, I want to root her and see what old girl can do. I replaced her, because I dropped her in a pool. She obviously was able to be fixed, but that pushed me in the direction to get two Inc 2's for free through wirefly. I still love the small size of the original incredible and might even be willing to swap back and forth during times when my larger phone won't work.
Click to expand...
If it is still on 2.2, all you need to do is run unrevoked.
unrevoked
 
What question or issue do you have with it?
Send me a link to an Inc 2 forum thread and I'd be happy to help with it :)
 
I got a couple of simple questions:

It works with Droid Incredible 1 with 2.3.4 right?

Does it work for both Amoled and Slcd droids?

After rooting, can I edit the build.prop file?
 
Status
Not open for further replies.
Back
Top Bottom