• 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.
I re-read this from Post #1:

special notes on hboot flashing PB31IMG files a common issue folks are having is the PB31IMG is not being found by hboot.
*there are only 2 reasons a PB31IMG is not found on the root of the sd card:
a)not named correctly. the phone muse see exactly "PB31IMG.zip". due to the way windows automatically adds and hides file extensions,it is usually correct to name the file "PB31IMG" with windows. common errors are for the file to be named "PB31IMG.zip.zip" after manually tying in the ".zip". on rarer occasions,it may not be adding/hiding the file extension,resulting in the file actually beening seen by the phone as "PB31IMG" check your file with a file manager on your phone and see how its seeing it.

b)sd card not formatted FAT32. if it is plain FAT or anything else,PB31IMG is invisible. on rare occasion,i have seen claims that a bad sd card,or card that needs reformatted(even tho it may be FAT32) will have the same affect.
*this has been addressed several times in the thread,skim thru it for more information.
Click to expand...

1. I just re-checked and the file is named correctly on the SD Card: PB31IMG
And the file is there; just checked. It is a .zip file.

2. My SD card is formatted FAT32. I have checked this 3 times.


Any other ideas? Do I need to re-format my SD card?
 
ousuxndallas said:
I re-read this from Post #1:



1. I just re-checked and the file is named correctly on the SD Card: PB31IMG
And the file is there; just checked. It is a .zip file.

2. My SD card is formatted FAT32. I have checked this 3 times.


Any other ideas? Do I need to re-format my SD card?
Click to expand...

Yeah, I'd format it again. Do NOT use the quick format option.
 
Okay, just figured it out. I placed the .zip file in the wrong place. I have 3 directories that pop up when I connect my phone - an "M:" drive, a "J:" drive and a "K:" drive. I was placing the .zip in the internal drive, not the SD Card.
 
I'm pretty new at this, so i hardly have an idea of what I'm actually doing
I followed all of the steps of the adb how to, it went well until I hit a prompt saying--Cannot copy boomsh.: Permission denied---
help if possible. :(
 
Your error message is different, but perhaps this will work for you.

From post #2

2nd edit:
if you get the following error trying to run zergRush: " [-] Cannot copy boomsh : No such file or directory",dont panic.

that error comes from running zergrush twice. reboot your phone,push and run zergrush again,then when you get the error,enter the following:
rm /data/local/tmp/booms
rm /data/local/tmp/sh
then
/data/local/zergRush

it should look something like this(just pretend that miniadb_merge says mini-adb_inc ):

Code: 
c:\miniadb_merge>adb push zergRush /data/local/
735 KB/s (23052 bytes in 0.030s)

c:\miniadb_merge>adb shell
$ chmod 755 /data/local/zergRush
chmod 755 /data/local/zergRush
$ /data/local/zergRush
/data/local/zergRush

[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.

[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.

[-] Cannot copy boomsh.: Permission denied
$ rm /data/local/tmp/booms
rm /data/local/tmp/booms
rm failed for /data/local/tmp/booms, No such file or directory
$ rm /data/local/tmp/sh
rm /data/local/tmp/sh
$ /data/local/zergRush
/data/local/zergRush

[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.

[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.

[+] Found a Froyo ! 0x00015108[*] Scooting ...[*] Sending 149 zerglings ...
[+] Zerglings found a way to enter ! 0x10
[+] Overseer found a path ! 0x00015108[*] Sending 149 zerglings ...
[+] Zerglings caused crash (good news): 0x401219e4 0x006c[*] Researching Metabolic Boost ...
[+] Speedlings on the go ! 0xafd1598f 0xafd1adb3[*] Sending 149 zerglings ...

[+] Rush did it ! It's a GG, man !
[+] Killing ADB and restarting as root... enjoy!

c:\miniadb_merge>adb shell
# exit
exit
Click to expand...
 
JRHOLDSEM said:
what am i doing wrong to get "base system device" instead of "android 1" with the devise manager? I am unable to update the drivers any help please!
Click to expand...

i wouldnt think it would matter much what your devices is being called in device manager,that you should still be able to manually update the drivers.

if not,id start by uninstalling htc sync and everything else your PC that has the ability to interaact with your phone. next download the driver .exe file from alpharev/unrevoked and run it. my laptop had never had any phone software on it,and running the ,exe file was all i needed to do to get adb and fastboot to see the phone.

if you have a "virgin" laptop or PC,might not hurt to switch to it. at least for the purpose of rooting.

aside from that,sometimes rebooting phone and/or pc helps,switch usb ports and cables.

triple check that usb debugging is turned on

ive had a mess of different drivers on my PC,from htc sync,to modified drivers found here on the forum,to drivers from unrevoked/revolutionary. ive literally had so many different drivers that i have no idea which ones are working :o ive also goe PDAnet installed,as well as motorola drivers and nook color drivers. yet every htc phone i plug in is instantly recognized despite the hot driver and phone program mess(currently still have rsd lite,cdma workshop,some lg software,and who knows what all else :eek:)

what im getting at is that,there is nota black and white combination of things that work or dont,as far as programs on a PC. wish i could be of more help,but the driver situation shouldnt be this hard to make work,so if something on your PC is possibly messing it up and you have no idea where to start looking,dont beat yourself up too much over it,maybe just try and borrow a different PC or laptop.
 
You know, I think im gonna rewrite the how to root section when i get a lil bit of time. It just wasnt exactly as straightforward as the Evo how-to. It ended up being pretty easy, just think that a noob might have some trouble. And with the Incredibles being sold on craigslist and ebay etc etc there might be a resurgence of new rooters... Just a thought
 
My root Inc still going strong but speaker starting to crackle, going bad, tried the remove screen and use magnet to pick up anything on speaker or screen, didn't do anything. I could buy a new speaker on Ebay for $3 and do it myself but it voids the warranty taking the back off with the void sticker. Even though Inc almost 2 years old still have the insurance/warranty so VZ going to send me a certified inc, assuming it will already have the recent update, so was concerned about getting root again with s-off, so this thread was a good find...thanks
 
Another noob here with a quick question. I followed the root guide and have s-off and everything seems to be proper, except for one thing. I have NO phone or 3g access. What could I have done wrong here? I have heard mention about 'radios', but I am not certain that is my problem. Any suggestions/advice would be greatly appreciated. Once again, the phone was downgraded from 2.3.4 to 2.2 and now has s-off. Unfortunately there now is no service on the phone and no bars. HELP! :)
 
hard to say what could have happened... but resrt assured that no part of what you just did should have affected it. first thing i would try is to run an RUU. since youre now s-off,you can run any one you want... run the froyo one again,or go ahead and run the latest GB one.

id run the newest GB RUU,as it will contain the newest/most stable radio,and this is the firmware you want to be on if you have to call vzw.

if you dont have your phone and data back after running the GB RUU,you will need to call vzw and have them help you reprogram it(it may work to just dial *228 fro your phone)

hope that helps :)
 
sweetb2006 said:
Ok so yea, as I was afraid... Google isn't going to find anything. So, if the sums don't match for mini-adb_inc, where the heck am i supposed to find one that does? :`(


scotty85 said:
sweetb2006 said:
Just wanted to let you know... So far, so good... I'm rooted... Woot! & I did have to download newest free rom manager, as it had a fix/update for the "sd card not mounted/found" Thus I wasn't able to make a backup... I'm now going to attempt downgrading & will not be bothering you unless i run into an issue that an extensive forum search can't help me with. ;)
Click to expand...

awsome! glad you got it(sorry for the lack of responses i havent been home all day)
Click to expand...
Click to expand...

fist make sure that you are downloading from the "mirror" link on media fire( miniadb_inc.zip )

and then make sure you are comparing the md5 to the mirror md5( 7c5211686a20b558ccd660c782f82e2b )

make sure youre taking the md5 of the zipped download,not after youve extracted.

make sure you are doing ad md5 hash,and not some other hash(with some summers its easy to confuse)

unless you have an antivirus program or firewall that is screwing with your download,i cant think of any other reasons the md5 would match. i just downloaded again and double checked,and the md5 does match. you may need to turn off such programs,or possible download the file on a different PC and transfer it via flash drive to yours in a worse case.

a bad md5 wont keep the file from being seen. you proly do not have it in the correct spot,you still have it zipped up,or you are typing the cd command not quite correctly.

a copy paste of everything in your cmd window should help us figure it out. double check that your mini-adb_inc file(or whatever you renamed it to) is on the root of your PCs C drive,and that is unzipped. start the adb commands again,and if you have trouble,provide us the copy/paste as described at the top of the first post.

dont worry,im sure its a small error,and youll be downgraded and s-offed in no time :)
 
scotty85 said:
fist make sure that you are downloading from the "mirror" link on media fire( miniadb_inc.zip )

and then make sure you are comparing the md5 to the mirror md5( 7c5211686a20b558ccd660c782f82e2b )

make sure youre taking the md5 of the zipped download,not after youve extracted.

make sure you are doing ad md5 hash,and not some other hash(with some summers its easy to confuse)

unless you have an antivirus program or firewall that is screwing with your download,i cant think of any other reasons the md5 would match. i just downloaded again and double checked,and the md5 does match. you may need to turn off such programs,or possible download the file on a different PC and transfer it via flash drive to yours in a worse case.

a bad md5 wont keep the file from being seen. you proly do not have it in the correct spot,you still have it zipped up,or you are typing the cd command not quite correctly.

a copy paste of everything in your cmd window should help us figure it out. double check that your mini-adb_inc file(or whatever you renamed it to) is on the root of your PCs C drive,and that is unzipped. start the adb commands again,and if you have trouble,provide us the copy/paste as described at the top of the first post.

dont worry,im sure its a small error,and youll be downgraded and s-offed in no time :)
Click to expand...

I absolutely downloaded that correct file, if any virus or other program was stopping me from doing so, it wouldn't have downloaded in the first place. :)

I copy & pasted Exactly as I should, as you will see, if I successfully attached the image. I also, absolutely unzipped before placing on C: & believe I placed it in the correct place? Perhaps I didn't do the hash correctly. However, as you said, that should not prevent it from being seen by command prompt.
 

Attachments

  • Capture.JPG
    Capture.JPG
    139.3 KB · Views: 94
now were getting somewhere :)

i can see the unzipped folder "android" on the root of C\

so your cmd line should be:

cd c:\android

you are forgetting the \

your cmd window shows cd c:android


hopefully that gets you fixed up :)
 
wow somethin wierd is goin on here... the OP had the command as you were tying it. i have no idea who or what changed it,but i assure you it hasnt been that way :eek:

for some reason it took several edits to get it changed in the post,and in the code box :confused:

my aoplogies for the confusion it caused you... ill have to look over the post later and make sure nothing esle is out of wack

im off to work,but ill try and watch in case you have further questions :)
 
scotty85 said:
wow somethin wierd is goin on here... the OP had the command as you were tying it. i have no idea who or what changed it,but i assure you it hasnt been that way :eek:

for some reason it took several edits to get it changed in the post,and in the code box :confused:

my aoplogies for the confusion it caused you... ill have to look over the post later and make sure nothing esle is out of wack

im off to work,but ill try and watch in case you have further questions :)
Click to expand...

Had anyone other than you edited your OP?
 
scotty85 said:
Nope... That's why its so confusing :eek:
Click to expand...

Shew! :p And here I thought I was loosing my mind, as I knew I had been copy/pasting! Then I saw your first reply, tried it & Viola! At that point I'm thinking "wtf". Anyway, glad you saw that it wasn't just me. ;) Thanks a million for all your help. I will let you know how the downgrade goes & if I have any issues with it.
 
Dumb question? =(

I'm successfully at this point. Woot! But stumped by the statement below. I can now downgrade back to 2.2? I thought that's what I was doing? lol So, how do I downgrade?

you can now downgrade back to 2.2,so you can run "unrevoked forever" to regain s-off
Click to expand...
 
Status
Not open for further replies.
Back
Top Bottom