I had the same message until i realized the phone had changed to disc drive instead of charge only. Had to change it. But now when i type su after the $ I get permission denied
Do I start adb over?
-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.
So I have successfully completed all the steps before this one. Installing the drivers, making sure my phone is on debugging, charge only, etc and that unrevoked is using the correct recovery image.
I plug in my phone and unrevoked says it's doing it's thing... it installs, reboots my phone, and then says Rooting.. but after a while, I get "Error: failed to get root. Is your firmware too new?"
I have tried changing my phone to mount as disk drive, as some other forums have suggested. I have tried deleting some applications on my phone that might have caused the problem (task killer, Zysploit), I have basically tried every suggestion on other forums, but I keep getting the same error message.
Can anyone help?? Much appreciated!
I would confirm that you are using Unrevoked 3.22, you are describing the message that you get when using Unrevoked 3.32...maybe.
I had the same message until i realized the phone had changed to disc drive instead of charge only. Had to change it. But now when i type su after the $ I get permission denied
Do I start adb over?
Have you successfully run unrevoked 3.22 and gotten superuser working and granting permissions to things?
If so,then wake your phone up before typing adb shell. When you type Su superuse will pop up on the screen and ask for permissions. You'll have to allow permissions before the $ will change to a #.
Of the phone is aslleep,you may never be aware of the popup requesting permissions. Not allowing permissions results in the permission denied error
__________________
The Delivery Guy
If someone has helped you,please click the THANKS button on that post.
Please post questions so others can benefit from the answers. donate to my device fund
Last edited by scotty85; December 4th, 2011 at 05:25 AM.
The Following 2 Users Say Thank You to scotty85 For This Useful Post:
scotty85, thank you for all of your help with rooting the dinc for my wife. I had to rerun adb and it worked fine. a long week but well worth it. kudos to you and everyone behind this thread.
The Following User Says Thank You to dhs2011 For This Useful Post:
I followed the steps and successfully gained root. However, after I rebooted I get a message that the System UIDs are inconsistent. I've tried doing a factory reset and still get the message. Also, when I reboot the phone is stuck in boot loop. When I boot into Hboot it says:
Searching SD Card
PB31DIAG.zip
No image
PB31DIAG.nbh
No Image
PB31IMG.zip
Main version is older
Update Fail
Eventually I get the phone to boot up. I usually have to let it sit for awhile turn off.
I followed the steps and successfully gained root. However, after I rebooted I get a message that the System UIDs are inconsistent. I've tried doing a factory reset and still get the message. Also, when I reboot the phone is stuck in boot loop. When I boot into Hboot it says:
Searching SD Card
PB31DIAG.zip
No image
PB31DIAG.nbh
No Image
PB31IMG.zip
Main version is older
Update Fail
Eventually I get the phone to boot up. I usually have to let it sit for awhile turn off.
Take the PB31IMG.zip file off the root of your sd card.
You need to alter the misc.img file before you can load it.
The Following User Says Thank You to sdrawkcab25 For This Useful Post:
I took PB31IMG off the sd card. It's still stuck in bootloop. When I go into Hboot it shows several errors very quickly then the menu. Trying reboot, recovery, or factory data reset just puts me back in bootloop again.
I took PB31IMG off the sd card. It's still stuck in bootloop. When I go into Hboot it shows several errors very quickly then the menu. Trying reboot, recovery, or factory data reset just puts me back in bootloop again.
The errors are normal, they always show up, unless you have a usable PB31IMG.zip file on your sd card. The one you had is for 2.2
You need to get a hold of the PB31IMG.zip file for gingerbread(2.3.4) and place that on the root of your sd card.
The Following 2 Users Say Thank You to sdrawkcab25 For This Useful Post:
If you can't find the pb31img for the current firmwAre, the .exe file is linked a few posts back. You can run it by placing your phone in fastboot,then start the .exe
The Following User Says Thank You to scotty85 For This Useful Post:
Thanks, it seems to boot up okay now. I put the gingerbread zip in the card. What do I do about the System UIDs? I've cleared my data, done a factory reset, and reformatted my SD card, but I still get this message when I start the phone.
I was finally able to do a factory reset through CWM and the System UIDs message is gone. Never had this much trouble rooting a phone, thank god it's just a phone to play around with and not my primary. Now on to downgrading to Froyo and turning S-off. Thanks again for all your help guys!
The Following User Says Thank You to Stretch44 For This Useful Post:
I have to say this has got to be one of the most amazing posts I've seen in forums like this - though I may be a bit of a n00b. All of the complexity removed in one big post. I rooted my Droid post 2.3.4 and S-off with Unrevoked all in one shot.
Now my question: Just after doing this I got a System Update push from the powers that be. Need I fear this will undue all my work? Am I supposed to use the superadmin feature to disable this sort of thing now?
Thanks!!
The Following User Says Thank You to brockmanah For This Useful Post:
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.
The Following User Says Thank You to scotty85 For This Useful Post:
ok i have a.d.h.d. like crazy my inc died and my company got me a replacement. i havent rooted a droid inc in over a year.. droid 2 droid x droid 3 plenty of times.. can some pleas poinr me to a detailed step by step to root a droid inc running gb
ok i have a.d.h.d. like crazy my inc died and my company got me a replacement. i havent rooted a droid inc in over a year.. droid 2 droid x droid 3 plenty of times.. can some pleas poinr me to a detailed step by step to root a droid inc running gb
Past! First post
The Following User Says Thank You to scotty85 For This Useful Post:
So, everything I've found about running ADB on Mac has been over a year old in the threads and assumes you have the full SDK downloaded. I've been assuming that's not needed for these instructions given the mini-adb package replaced that process. Is my assumption correct, or am I making an ASS out of U and ME?
What I did learn is that you need to put './' in front of your commands in the Mac Terminal when running the command from the directory they are in. For instance, "adb devices" would be ./adb devices. Alternatively, you can drag the file from your Finder window and drop it into the Terminal command line so that you don't have to type out the entire path if not on a root directory (handy little trick!). I'm still having an issue with the "adb" command not being found in the directory, so not sure what's up with that...still trying to figure that part out though.
Thought I'd share this info for the few Mac users that have popped up on here. Here's a link I found that was helpful:
Thanks so much for this thread!! I bought my Incredible on the 1st day they were sold and have finally rooted it! I got tired of the "low space" issues and was getting bored with the stock Sense. Now I've loaded Cyanogenmod 7.1 and LOVE IT! It's like having a new phone....That runs faster too!!
so I followed the instructions to the letter, and I'm stuck at this step below. It finds the update, but gives me a Main Version is older! error. what do I do from here?
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.
you did not successfully rewrite the misc image. check the md5s of all your downloads,then start at step 3,if you use the unrevoked 3.22 method and still have root access. if not,youll have to start over.
make sure the outputs to each command match the ones in my code box on the first post.
after your done,copy the whole thing and paste it here by:
right click in the command window,click mark. highlight everything in white. hit enter.
then,in your reply to thread box here,click the "#" up top and paste everything between the [code] tags.
then if it doesnt work,we should be able to see where you went wrong with the comands
The Following 2 Users Say Thank You to scotty85 For This Useful Post:
you did not successfully rewrite the misc image. check the md5s of all your downloads,then start at step 3,if you use the unrevoked 3.22 method and still have root access. if not,youll have to start over.
make sure the outputs to each command match the ones in my code box on the first post.
after your done,copy the whole thing and paste it here by:
right click in the command window,click mark. highlight everything in white. hit enter.
then,in your reply to thread box here,click the "#" up top and paste everything between the [code] tags.
then if it doesnt work,we should be able to see where you went wrong with the comands
hey I went through step 3 again, step by step, and it worked this time. I'm rooted and S-OFF. Thanks so much for your help!
For those using a Mac, you will need to download the Android SDK starter package as well as the platform-tools addition (platform-tools is not part of the starter package, but is easily obtained by running the android command in the terminal once you've downloaded SDK and downloading it from the menu). The platform contents will automatically be saved in your SDK folder. You can get the SDK here: Android SDK | Android Developers
Also, you still need to download the mini-adb-inc package that Scotty has on the OP because you still need the flash_image and mtd0.img files to push to your phone. After that, the steps are the same, but with a few minor tweaks that I'll detail below.
So, I'll begin at step 2: "2)root with unrevoked 3.22" worked flawlessly, just make sure to use the unrevoked 3.22 link for Mac that Jess found and Scotty added to the bottom of the OP. This will simply get you root with s-on.
GREEN instructions are what I tweaked...if it's bold, it's code
3)prepare to downgrade
-extract the mini-adb_inc .zip. place the mtd0 and flash_image in your Android SDK platform-tools folder. (no real need to put anything at root directory if you don't want, I'll explain why in a moment)
-place the 2.2 downgrade on the root of your sd card...this part of step 3 is the same.
4)downgrade with adb. This is where things get more interesting.
At this point, I've assumed the Mac users know how to get to your terminal...if not, go to Applications->Utilities->Terminal. Go ahead and check your md5's...the command in Terminal is simply md5, not md5sums. OK, moving along...
-make sure phone is plugged in and usb debugging checked on,in charge only mode
-at the promt in your Terminal window:
cd <after the space, drag the platform-tools folder from the Finder window and drop it into the command line...this will automatically load your path and why you don't necessarily need to place everything in your root directory> Here's what mine looked like:
gkinsellas-imac:~ gkinsella$ cd /Users/gkinsella/AndroidSDK/platform-tools
gkinsellas-imaclatform-tools gkinsella$
./adb devices must use ./ in front of the command to execute the adb commands from the platform-tools folder
md5 mtd0.imgmd5 flash_image
for both of these, type the md5 command followed by a space, and then drag and drop each file to automatically include the path for the file. These will return the same numbers Scotty has on the OP
./adb shell your prompt should change to a #. if it changes to a $,then type su note your phone may pop up a message asking you to allow permissions the first time you do this (the first time I did this, I received a "Permission denied" message...I typed su again and got the # prompt). if it does check "always" and touch "allow" on the superuser request on the phone screen.
cd /data/local chmod 0755 /data/local/flash_image
cd /data/local ./flash_image misc /sdcard/mtd0.img
NOTE: no changes to these commands because you're now in the phone!
you can now downgrade back to 2.2,so you can run "unrevoked forever" to regain s-off
exit to get back to $ prompt exit to get back to the "platform tools" prompt
./adb reboot bootloader this will boot your phone to "fastboot" select "bootloader" with the power button.
And that's it! Follow everything after the bootloader instruction as Scotty outlined. I'll put a copy of my session on the next post. I hope this helps...Scotty, I'm not sure how you want to add this to your OP as it's not much different code-wise obviously, but definitely a few different steps than what you had.
Last edited by gkinsella2; December 10th, 2011 at 09:38 PM.
The Following 7 Users Say Thank You to gkinsella2 For This Useful Post:
thats awsome! lots of mac users will be extremely greatful
as far as integrating it,there are a few ways we could do it... if you want to make up your own complete post,using most of my guide or parts,or none,we can link from the first post to wherever it is,or if rooter28 doesnt mind we can grab his post(#3) and put the mac guide there. only prollem with doing that is that only the guides and mods can edit it,so if you need to make changes youll have to get one of us to do it. wich is not a big deal to me,just pm me or sdraw or any of us if you need to make a change.
i could also just take what you posted above,and either link to it,or add it to post #3.
id like to have all of it in the first few posts,but if you want to keep it your post so you can change it,its no biggie to link it.
however you want to do it,sir. your contributions are greatly appreciated.
The Following 2 Users Say Thank You to scotty85 For This Useful Post:
gkinsellas-imac:~ gkinsella$ cd /Users/gkinsella/AndroidSDK/platform-tools
gkinsellas-imac:platform-tools gkinsella$ ./adb devices
List of devices attached
HTXXXXXXX device
gkinsellas-imac:platform-tools gkinsella$ md5 /Users/gkinsella/mini-adb_inc/mtd0.img NOTE: I ran the md5 before I moved these to my platform-tools folder. That's why it shows a different path.
MD5 (/Users/gkinsella/mini-adb_inc/mtd0.img) = 34307be744275f1db1dd16af04c37839
gkinsellas-imac:platform-tools gkinsella$ md5 /Users/gkinsella/mini-adb_inc/flash_image same reason as above for different path
MD5 (/Users/gkinsella/mini-adb_inc/flash_image) = 0098a7dd6600b55fac34fc6645be5d7a
gkinsellas-imac:platform-tools gkinsella$ ./adb push flash_image /data/local/
1747 KB/s (76044 bytes in 0.042s)
gkinsellas-imac:platform-tools gkinsella$ ./adb push mtd0.img /sdcard/
2106 KB/s (655360 bytes in 0.303s)
gkinsellas-imac:platform-tools gkinsella$ ./adb shell
$ su
Permission denied as mentioned above, not sure why I was denied
$ su however, I knocked twice and got in! :D
# cd /data/local
# chmod 0755 /data/local/flash_image
# cd /data/local
# ./flash_image misc /sdcard/mtd0.img
# exit
$ exit
gkinsellas-imac:platform-tools gkinsella$ ./adb reboot bootloader
gkinsellas-imac:platform-tools gkinsella$
Last edited by gkinsella2; December 10th, 2011 at 09:36 PM.
The Following User Says Thank You to gkinsella2 For This Useful Post:
thats awsome! lots of mac users will be extremely greatful
as far as integrating it,there are a few ways we could do it... if you want to make up your own complete post,using most of my guide or parts,or none,we can link from the first post to wherever it is,or if rooter28 doesnt mind we can grab his post(#3) and put the mac guide there. only prollem with doing that is that only the guides and mods can edit it,so if you need to make changes youll have to get one of us to do it. wich is not a big deal to me,just pm me or sdraw or any of us if you need to make a change.
i could also just take what you posted above,and either link to it,or add it to post #3.
id like to have all of it in the first few posts,but if you want to keep it your post so you can change it,its no biggie to link it.
however you want to do it,sir. your contributions are greatly appreciated.
I don't think I'll need to edit it...if I do, I can add by "replies" and you guys can update it if need be. I agree with you though, keep it in the first few posts. It'll be more centralized that way and easier for others to find/follow. Glad I could help out!
The Following User Says Thank You to gkinsella2 For This Useful Post:
Hello all:
Thanks to Scotty for posting these instructions and for continuing to answer everyone's questions. After downloading all the files and verifying their MD5 sums, I ran into a problem installing the Unrevoked USB drivers. According to their instructions below, one needs to go into the HBOOT menu to install the drivers.
Turn off your phone, then boot it into the HBOOT menu by holding power and volume down.
Connect the phone to your Windows machine with a USB cable and wait for the phone to say HBOOT USB PLUG on screen.
However, my phone already has the OTA 2.3.4 without having previously rooted, or, done S-off. So pressing Power and Vol. down does not give the HBOOT menu. As a result, I don't have the Bootloader Interface driver loaded as described. All I have is the Android Composite ADB Interface driver. Is there a way to circumvent this and load the Unrevoked drivers as they have described ?
Any advice/insight would be greatly appreciated.
Thanks
that should be an easy fix. just go to settings/power uncheck "fastboot".
having this checked prevents you from getting to hboot via power/vol down. freaked me out bigtime first time it happened to me on my thunderbolt
Thanks much, Scotty. That worked perfectly and now I've got root. I can't believe how easy that was. So far I haven't downgraded and am doing the Titanium and Nandroid backups.
After the Titanium backups, I tried to remove some of the extra apps (CityID, VZW NAvigator, etc) using Titanium. However, even though Titanium reports the apps as having been removed, they are still present in the App drawer and still work. I'm not sure what I'm doing wrong here. I have the free Titanium app.
Thanks much, Scotty. That worked perfectly and now I've got root. I can't believe how easy that was. So far I haven't downgraded and am doing the Titanium and Nandroid backups.
After the Titanium backups, I tried to remove some of the extra apps (CityID, VZW NAvigator, etc) using Titanium. However, even though Titanium reports the apps as having been removed, they are still present in the App drawer and still work. I'm not sure what I'm doing wrong here. I have the free Titanium app.
Cheers,
you need s-off to remove the apps with titanium unless you use the "recovery exploit". Or buy the paid version and you can freeze them.
The Following 2 Users Say Thank You to sdrawkcab25 For This Useful Post:
Yup,this is the post to use for 2.3.4. The chances of bricking really are slim to none,if you follow the directions.
Just read thru the directions a couple of times and ask any questions you can't find the answers to prior to getting yourself in a bind. Download all the files,check their ms5s,and organize yourself so you can find them all. Don't skip the part about checking ms5s because you don't understand it,or know how to do it,as using corrupt files is the only way you *could* potentially brick it.
Once you've downloaded and checked everything,just carefully procede. Make sure the outputs match and you don't miss any steps,and you'll be fine.
The Following User Says Thank You to scotty85 For This Useful Post:
So, I'll begin at step 2: "2)root with unrevoked 3.22" worked flawlessly, just make sure to use the unrevoked 3.22 link for Mac that Jess found and Scotty added to the bottom of the OP. This will simply get you root with s-on.
I think you're saying I should follow step 2 on the original page, which directs me to public:windows_hboot_driver_install [RootWiki] . But that page contains instructions for a Windows machine. I have only a Mac, running 10.6.8. Do I need a Windows machine in order to continue at this point? I can reach the HBOOT USB PLUG screen on the Incredible, but running ./adb devices from platform-tools does not show any connected devices at this stage.
Thanks for your patience.
[Edit:] I do have the unrevoked Recovery Reflash Tool for Mac, as described in the original post.
Last edited by hazelnut; December 13th, 2011 at 09:19 PM.
Reason: clarification
I think you're saying I should follow step 2 on the original page, which directs me to public:windows_hboot_driver_install [RootWiki] . But that page contains instructions for a Windows machine. I have only a Mac, running 10.6.8. Do I need a Windows machine in order to continue at this point? I can reach the HBOOT USB PLUG screen on the Incredible, but running ./adb devices from platform-tools does not show any connected devices at this stage.
Thanks for your patience.
[Edit:] I do have the unrevoked Recovery Reflash Tool for Mac, as described in the original post.
i believe that on a mac,your phone is naturally,magically compatible,you dont need to install drivers you can skip over the part about installing drivers.
start on step 2,and use unrevoked to root your phone. make sure to change the recovery if youre on an slcd,as described in step 2. i dont believe this part will be much different on a mac. youll still need to place the recovery image somewhere you can find it,then point the unrevoked to it.
then,as was said,directions for the downgrade adb commands are in post 629
The Following User Says Thank You to scotty85 For This Useful Post:
i believe that on a mac,your phone is naturally,magically compatible,you dont need to install drivers you can skip over the part about installing drivers.
start on step 2,and use unrevoked to root your phone. make sure to change the recovery if youre on an slcd,as described in step 2. i dont believe this part will be much different on a mac. youll still need to place the recovery image somewhere you can find it,then point the unrevoked to it.
then,as was said,directions for the downgrade adb commands are in post 629
Sorry if I sounded rude. I was simply pointing to the correct post for the Mac adb instructions.
Thanks. Yes, I've been following the instructions in post 629; that's what my original quote was to.
Step 2 of that post is now done. For the benefit of any other Mac users as slow-witted as I am, I'll describe what I did in that step.
After confirming the checksum of recovery-clockwork-5.0.2.0-inc.img, I installed the Mac version of Reflash from http://downloads.unrevoked.com/recovery/3.32/Reflash.dmg . I copied Reflash from the .dmg to a regular directory and ran it from there.
With Reflash running but phone not plugged in, select File -> Custom Recovery , and choose "recovery-clockwork-5.0.2.0-inc" from the place it was saved to. Reflash screen-bottom now says "Recovery image: custom". Only then did I plug in the phone. Reflash found the phone and after asking for my confirmation, began installation and a series of reboots.
After all was finished, I got an error "Error verifying extendedcommand", but on reboot (from a blue, not green, menu on the phone), I was able to go to Settings -> Applications -> Manage Apps , choose "all" pane, -> Superuser Permissions version 2.1; from there I cleared the data, and root checkers confirm that I am rooted.
In Step 3 of the instructions, it says, 'place the 2.2 downgrade on the root of your sd card,and verify it is named "PB31IMG".' The 2.2 downgrade is not "Android 8" from the Android SDK Manager, but the directory called "PB31IMG" that was downloaded from PB31IMG.zip , correct? That directory contains a file "android-info.txt" containing
Pushing flash_image is successful, but I am getting a permissions error when I try to push mtd0.img .
[Edit:] From within the adb shell, I can see that /sdcard/ has permissions of 000. Trying to write to it or change the permissions brings me "Unable to chmod /sdcard/: Read-only file system". Any idea how I can change the permissions?
Thanks for your patience.
Last edited by hazelnut; December 13th, 2011 at 11:16 PM.
Reason: more information
Whoo Hoo, S-OFF! Finally got it to work. Somewhere in all the posts I was reading, I got the wrong image I tried to flash, and I think I missed the (completely didn't see) the Charge only, and had it in disk mode.
Tried again tonight when I was fresh and all went the first time (after replacing the bad PB31IMG.zip that was way too small.
Went right through and now I am looking for a OS to load.
Thanks for the instructions at the beginning of the thread! Great Job.
Pushing flash_image is successful, but I am getting a permissions error when I try to push mtd0.img .
[Edit:] From within the adb shell, I can see that /sdcard/ has permissions of 000. Trying to write to it or change the permissions brings me "Unable to chmod /sdcard/: Read-only file system". Any idea how I can change the permissions?
Thanks for your patience.
Hazelnut, did you change your shell prompt from '$' to '#'?
1Likes
latform-tools gkinsella$
And yes, serial # is now edited, thanks!
