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

Root Android Debug Bridge - help

Try to refrain from quadruple posting. You can hit the edit button and add more stuff.

If that's the case, open up superuser permissions, remove anything you see in there, and give it another try through adb.

This time, when you request su permissions, something should pop up on your phone asking to allow it. Make sure you accept, and select remember.
 
:) thanks again - i guess i didnt notice the box that came up on the phone.
okay so i entered all of that and now i have something in my superuser app. my droid reset all by itself after i hit reboot and hit enter. i hope that was it so im on to the next step!!


nope- on the next step after i type in su i get access denied! :(
is there a way to check if i have rooted the phone? or , well what should i do at this point?

man its late i think i am seeing things.
okay im going to try that step again because maybe that box on my phone popped up again after i type in su
 
nope - well thanks for the help ill try more tomorrow. on the next step i wound up with the big triangle with caution sign so im still doing something wrong
 
saltysteve said:
hey - yeah it is still in zip and i downloaded it to my desktop. i run xp
Click to expand...

That is what I thought was happening - glad you got it figured out.

saltysteve said:
nope - well thanks for the help ill try more tomorrow. on the next step i wound up with the big triangle with caution sign so im still doing something wrong
Click to expand...

OK, Fab is working with you on this, I am off to work, but I'll log in back later to try to help trace down where you were and how you got there and post back.
 
well i am back for some more reading but i wanted to take some time out to thank you guys who are helping me. I really couldnt have even gotten this far with out your help, so thank you very much!!!!:)
 
okay so the things i forgot to post was that after i did the "HOW TO GET ROOT" step i noticed a file in my superuser app folder. i touched it and it disappeared. so none the folder is empty.

also is there a way to test to see if i did the "HOW TO GET ROOT" step correctly before moving on?

i went through the Obtaining Root guide again and that was done 100%
 
i went through the Obtaining Root guide again and that was done 100%

everything worked and i have the superuser with a file in it -
file is : 2000:2000 0:0 /system/bin/sh

once i touch this file (2000:2000 0:0 /system/bin/sh) in superuser it goes away

where i am stuck is here- busybox
i enter in Command Prompt-
adb push busybox /data/local/busybox and push enter
and get "error: device not found"

im not sure why- the busybox file is unzipped in the tools folder with adb.exe
 
and your command prompt is actually in the folder that adb is in? Meaning that your command prompt looks something like this:

Code: 
c:\{path to android sdk}\android SDK\tools\>
when you're typing those instructions?
 
You could just skip the busybox part and move on to flashing a custom recovery. You will get busybox when you flash a new ROM.
 
johnlgalt said:
and your command prompt is actually in the folder that adb is in? Meaning that your command prompt looks something like this:

Code: 
c:\{path to android sdk}\android SDK\tools\>
when you're typing those instructions?
Click to expand...

He needs to make sure he has debugging enabled on the phone. Or, what CRP said, although I like to install it myself.
 
johnlgalt said:
and your command prompt is actually in the folder that adb is in? Meaning that your command prompt looks something like this:

Code: 
c:\{path to android sdk}\android SDK\tools\>
when you're typing those instructions?
Click to expand...


um, i am not sure about that- they look like this:
C:\Documents and Settings\steven\Desktop\android-sdk-windows\tools

crp-"You could just skip the busybox part and move on to flashing a custom recovery. You will get busybox when you flash a new ROM. "

so skip this step??

well that didnt work either
i tried to go to custom recovery and the 2nd copy and paste was "permission denied"

now what?

and yes i have had debugging enabled

everything after How to get root i can not do. i get "permission denied" in the comand prompt. So why am i getting "permission denied"?
 
Under your settings > applications > development
make sure USB debugging is checked.

Does
adb devices
Show anything? If not, type
adb kill-server
adb start-server
And see if it recognizes it.
Or just download droidmod from the market and install your choice of ROMs.

Clear anything in your superuser app. Reconnect your phone, enter adb shell, type su, press allow on your phone. Now what's it say?
 
esocid said:
Under your settings > applications > development
make sure USB debugging is checked.

Does
adb devices
Show anything? If not, type
adb kill-server
adb start-server
And see if it recognizes it.
Or just download droidmod from the market and install your choice of ROMs.

Clear anything in your superuser app. Reconnect your phone, enter adb shell, type su, press allow on your phone. Now what's it say?
Click to expand...


YES, debugged is checked
adb devices? where can i see if they r showing anything?

i typed
adb kill-server
adb start-server
and it appeared to recognize
enter adb shell, type su, press allow on your phone. Now what's it say?
it says #


custom recovery :

here is whats going on


reboot recoveryMicrosoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\steven>cd C:\Documents and Settings\steven\Desktop\and
roid-sdk-windows\tools
C:\Documents and Settings\steven\Desktop\android-sdk-windows\tools>adb shell
$ dd if=/sdcard/flash_image of=/data/local/flash_image
dd if=/sdcard/flash_image of=/data/local/flash_image
/sdcard/flash_image: cannot open for read: Permission denied
$ chmod 755 /data/local/flash_image
chmod 755 /data/local/flash_image
$ rm /sdcard/flash_image
rm /sdcard/flash_image
rm failed for /sdcard/flash_image, Permission denied
$ su
su
# /data/local/flash_image recovery /sdcard/recovery-0.99.2b.img
/data/local/flash_image recovery /sdcard/recovery-0.99.2b.img
error opening /sdcard/recovery-0.99.2b.img: No such file or directory
# mount -o remount,rw /dev/null /system
mount -o remount,rw /dev/null /system
# mv /system/recovery-from-boot.p /system/recovery-from-boot.p.bak
mv /system/recovery-from-boot.p /system/recovery-from-boot.p.bak
failed on '/system/recovery-from-boot.p' - No such file or directory
# reboot recovery
reboot recovery
C:\Documents and Settings\steven\Desktop\android-sdk-windows\tools>
 
saltysteve said:
C:\Documents and Settings\steven\Desktop\android-sdk-windows\tools>adb shell
$ dd if=/sdcard/flash_image of=/data/local/flash_image
dd if=/sdcard/flash_image of=/data/local/flash_image
/sdcard/flash_image: cannot open for read: Permission denied
$ chmod 755 /data/local/flash_image
chmod 755 /data/local/flash_image
$ rm /sdcard/flash_image
rm /sdcard/flash_image
rm failed for /sdcard/flash_image, Permission denied
$ su
su
# /data/local/flash_image recovery /sdcard/recovery-0.99.2b.img
/data/local/flash_image recovery /sdcard/recovery-0.99.2b.img
error opening /sdcard/recovery-0.99.2b.img: No such file or directory
# mount -o remount,rw /dev/null /system
mount -o remount,rw /dev/null /system
# mv /system/recovery-from-boot.p /system/recovery-from-boot.p.bak
mv /system/recovery-from-boot.p /system/recovery-from-boot.p.bak
failed on '/system/recovery-from-boot.p' - No such file or directory
# reboot recovery
reboot recovery
C:\Documents and Settings\steven\Desktop\android-sdk-windows\tools>
Click to expand...

All that stuff you did at the beginning where it said permission failed, I think you need to be root to do them.

Just type su, and try to run those commands again. If they fail, you can't actually do the next steps.

Make sure you have a # instead of a $ before you do stuff, otherwise you'll get those permission denied errors.
 
I think you have learned enough trying to do it this way, I would say get the dmupdater app or droidrootpro and let it do this for you. You know how to use adb now and have it installed which is usually the thing people miss out on when going the automatic way.
 
Damn,
This thread is enough to make me unroot my phone and revert back to stock :eek: Just goes to show that sometimes everything goes without a hitch and then there are other times when nothing goes as planned.
 
saltysteve said:
YES, debugged is checked
adb devices? where can i see if they r showing anything?

i typed
adb kill-server
adb start-server
and it appeared to recognize
enter adb shell, type su, press allow on your phone. Now what's it say?
it says #


custom recovery :

here is whats going on


reboot recoveryMicrosoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\steven>cd C:\Documents and Settings\steven\Desktop\and
roid-sdk-windows\tools
C:\Documents and Settings\steven\Desktop\android-sdk-windows\tools>adb shell
Missing the su command here <-- this is the most important step - if you do not do a su here you do not gain root access, and all the following commands will fail

If you do su here, then all of following commands will have a # in front of them, not a $ like yours do.
$ dd if=/sdcard/flash_image of=/data/local/flash_image
dd if=/sdcard/flash_image of=/data/local/flash_image
/sdcard/flash_image: cannot open for read: Permission denied
$ chmod 755 /data/local/flash_image
chmod 755 /data/local/flash_image
$ rm /sdcard/flash_image
rm /sdcard/flash_image
rm failed for /sdcard/flash_image, Permission denied
$ su <-- this is too late - you need su for the previous command s to work, and only if you perform the previous commands will the following commands also work
su
# /data/local/flash_image recovery /sdcard/recovery-0.99.2b.img
/data/local/flash_image recovery /sdcard/recovery-0.99.2b.img
error opening /sdcard/recovery-0.99.2b.img: No such file or directory
# mount -o remount,rw /dev/null /system
mount -o remount,rw /dev/null /system
# mv /system/recovery-from-boot.p /system/recovery-from-boot.p.bak
mv /system/recovery-from-boot.p /system/recovery-from-boot.p.bak
failed on '/system/recovery-from-boot.p' - No such file or directory
# reboot recovery
reboot recovery
C:\Documents and Settings\steven\Desktop\android-sdk-windows\tools>
Click to expand...

I am basically repeating what Fab wrote, but making it more obvious with my boldface type and the red coloring.

Everything in bold is my own addition.
 
You must log in or register to reply here.
Back
Top Bottom