-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root Ask question's here (Dont flood the root topic, please)
bamaredwingsfan
Android Enthusiast
I kept taking the card in an out during those attempts
. I had a slight problem at the end as well getting the last 3 steps to work, but again i was jiggling the card to do it
Also when i removed that bad asroot2.txt file that might have helpd the last 3 steps as well so who knows
thegabrielj
Lurker
heres where im at
This will happen if you're still sharing the card with your computer. Like I said in my post, after you copy the files over to the sdcard, you have to eject the drive/phone from the windows box. The phone will not see the card if windows can see it. hence your "not found error".
just to be sure you're not sharing the card between the system and the phone, unplug the USB cable from the PC (after ejecting it), leave it out for a couple seconds and plug it back in. If windows tries to show you the contents of the card after plugging it back in, just eject it from windows and leave the phone connected then try to run the commands.
biggest thing to remember is that only one operating system will be able to mess with the sdcard at a time. Think of it like an external hard drive.
just to be sure you're not sharing the card between the system and the phone, unplug the USB cable from the PC (after ejecting it), leave it out for a couple seconds and plug it back in. If windows tries to show you the contents of the card after plugging it back in, just eject it from windows and leave the phone connected then try to run the commands.
biggest thing to remember is that only one operating system will be able to mess with the sdcard at a time. Think of it like an external hard drive.
heres where im at
Gabriel.... you need a space between cat and /sdcard/asroot2. That's the problem you're seeing above. Without the space, the system thinks "cat" is a directory name, rather than a command. So type:
cat /sdcard/asroot2 > /data/local/asroot2
with those spaces. Maybe it's best to copy and paste it.
cat /sdcard/asroot2 > /data/local/asroot2
with those spaces. Maybe it's best to copy and paste it.
I cannot get adb to see the phone:
Host systems:
A. Ubuntu Server 8.04, 64-bit Intel mode desktop
B. Mint Linux 7 (based on Ubuntu 9.04), 32-bit mode notebook
adb:
From SDK I downloded March 27, so thinking it should be Android 2.1? I installed it then on the Server machine, and tried it there, then today copied just the adb runtime file to the Mint notebook to try from there - did I need any of the rest of the files from the SDK installation on the Mint PC?
I do have the phone in debug mode (tried toggling it and using adb in both modes of debug/no debug on both Linux boxes). /var/log/messages shows a sd "SCSI" device being mounted when enabling debug and connecting cable (original LG and other minu-USB cables) - should debug mode cause/allow that?
"adb devices" gets no response - is there some other way to verify?
Could I just copy the files on the Linux machines directly to the card mounted on them? That is, I know I can do that, but will the Ally then let me use the files with the Terminal program I installed on it for the copying from the card to the system directories? A number of commands I try from that terminal session on the Ally get "no permissions" responses.
Don't tell me I have to do this with Windoze - that would be so ... embarassing! ;-}
TIA,
rokky
Host systems:
A. Ubuntu Server 8.04, 64-bit Intel mode desktop
B. Mint Linux 7 (based on Ubuntu 9.04), 32-bit mode notebook
adb:
From SDK I downloded March 27, so thinking it should be Android 2.1? I installed it then on the Server machine, and tried it there, then today copied just the adb runtime file to the Mint notebook to try from there - did I need any of the rest of the files from the SDK installation on the Mint PC?
I do have the phone in debug mode (tried toggling it and using adb in both modes of debug/no debug on both Linux boxes). /var/log/messages shows a sd "SCSI" device being mounted when enabling debug and connecting cable (original LG and other minu-USB cables) - should debug mode cause/allow that?
"adb devices" gets no response - is there some other way to verify?
Could I just copy the files on the Linux machines directly to the card mounted on them? That is, I know I can do that, but will the Ally then let me use the files with the Terminal program I installed on it for the copying from the card to the system directories? A number of commands I try from that terminal session on the Ally get "no permissions" responses.
Don't tell me I have to do this with Windoze - that would be so ... embarassing! ;-}
TIA,
rokky
Rokky, it is possible that you could do the entire process by copying asroot2, su, and Superuser.apk to the sd card, and then copying asroot2 from there to /data/local, and then running the asroot2 command from a terminal emulator on the phone. asroot2 is VERY finicky, and I don't know if anyone has tried running it from a terminal emulator. Don't be surprised if it never works, but it's worth a shot.
Once you have a root shell, then you're definitely fine. Just type the rest of the commands into the terminal emulator.
Once you have a root shell, then you're definitely fine. Just type the rest of the commands into the terminal emulator.
thegabrielj
Lurker
that was a big part of it
i replaced the spaces with underscores fro emphasis
cat_/sdcard/asroot2_>_/data/local/asroot2
WARNING the underscore is so u can see the spaces do not put them in the line of code
i am now rooted!!!
i did however run the steps in 13 twice... would that mess anything up? is it possible to double it up inside?
Well, I tried, but still do not have permission to do anything of that sort - cannot execute asroot2 from the card, cannot copy it anywhere. The mount command shows me that the sdcard is mounted with nosuid and noexec, so no chance of running anything from it.
That, and adb not connecting, seem to indicate that my Ally, at least, is really "locked down". Guess I might resort to trying adb from ... Windoze. Or just send the cotton-picker back to VZW, and get my life back to less challenging ways to waste time like re-compiling a linux kernel...
Thanks for the response.
R
Your Ally is probably the same as everyone else's. What you want to do is:
a) copy su, asroot2, and Superuser.apk to the sd card.
b) In your phone's terminal emulator, type:
$ cat /sdcard/asroot2 > /data/local/asroot2
$ cd /data/local
$ chmod +x asroot2
$ ./asroot2 /system/bin/sh
These steps should work up until the last one. The last one is shaky for everyone, but won't work any worse just because you copied asroot2 in a different way. Once you have a root prompt, follow the instructions from earlier procedures.
a) copy su, asroot2, and Superuser.apk to the sd card.
b) In your phone's terminal emulator, type:
$ cat /sdcard/asroot2 > /data/local/asroot2
$ cd /data/local
$ chmod +x asroot2
$ ./asroot2 /system/bin/sh
These steps should work up until the last one. The last one is shaky for everyone, but won't work any worse just because you copied asroot2 in a different way. Once you have a root prompt, follow the instructions from earlier procedures.
vn909kaliboi
Lurker
rookie question
I'm downloading pdanet and having trouble installing it. I'm getting the error message
"Android phone not detected (error=104 and 103). Please wait for driver installation to complete and make sure the Android ADB driver is loaded without error in Device Manager. If you run into a driver error please find help at. http://junefabrics.com/android/driver.php."
I checked device manager and the android adb driver isn't there, can someone please help? thanks
also I'm running vista
I'm downloading pdanet and having trouble installing it. I'm getting the error message
"Android phone not detected (error=104 and 103). Please wait for driver installation to complete and make sure the Android ADB driver is loaded without error in Device Manager. If you run into a driver error please find help at. http://junefabrics.com/android/driver.php."
I checked device manager and the android adb driver isn't there, can someone please help? thanks
also I'm running vista
bamaredwingsfan
Android Enthusiast
Do you have USB debugging enabled? In the phone setting for apps/developement
vn909kaliboi
Lurker
Yea I enabled the debugging. The computer only recognized my phone as an external drive, like a flash drive. Ill try on another computer later.
bamaredwingsfan
Android Enthusiast
Try mounting the SD card, then starting up adb and then trying the adb devices command.
bdufflebag
Lurker
I have completed all the first 5 steps for Linux, but I'm still not getting the # in the shell. Someone help? I do everything I am told. I make it up to where i'm in the Android shell and after entering in that command (
etc..) I still don't get the #. I've done it 20 times. I have done
then
. Please can someone help.
Code:
/data/local/asroot2
Code:
./adb kill-server
Code:
sudo ./adb start-servervn909kaliboi
Lurker
couldn't get it to work on my computer but it worked on my brothers computer. Well my phone is successfully rooted, thanks
bdufflebag, all I can say is, apparently just keep typing the asroot2 command many, many times, and it might eventually work? if you get bored with typing it over and over, try changing something random with the SD card or USB configuration. There's no clear picture emerging of when it does and doesn't work.
I wish my Ally was the same as everyone else's. I cannot copy a file from a card to any dir on the Ally, even the only one with "other" permissions set to 7, sqlite_stmt_journals. I even formatted a card on the Ally first, and then, when that failed to help, formatted it under Linux as ext3 file system so I could set the permissions to full 777 (which is not possible on a FAT32 fs). I cannot cp any file into any dir on the Ally via the termulator. About the only response I get to about any command is "permission denied" The "id"command shows me running as app_61 - is that "normal"?
I also did get adb for Windows and run it from Win XP, and it also cannot connect/see devices. I used a direct connection between the Ally and the USB port built into the notebook PC since intermediate hubs can cause issues sometimes, and I used the cable shipped with the unit.
Thanks anyway,
R
PowerBomb
Android Enthusiast
The $ to # is where I had the most trouble too. I did it with the SD card out, got a failed message, put the SD card back in, typed in the command again, and finally it changed to #. Just keep trying. Took me probably ten times.
Guess I got it to work. Phone rebooted and I got the Superuser icon in my Apps. I installed Terminal Emulator to make verify, and when I entered "SU", the notification popped up telling me to Allow or Deny.
So.... what kind of cool stuff can I do now that it's rooted?
Guess I got it to work. Phone rebooted and I got the Superuser icon in my Apps. I installed Terminal Emulator to make verify, and when I entered "SU", the notification popped up telling me to Allow or Deny.
So.... what kind of cool stuff can I do now that it's rooted?
xxFakeLifexx
Lurker
I was working on rooting mine earlier and ran into a handfull of problems. I got pretty far when i realized I had some of the installed programs in the wrong locations wich might be a problem for others aswell. Was wondering if its possible to create our own file ,files via ES File explorer . Without being connected to our comps. sounds like alot of code but sure fire if we already know what it is.
Thanx.
Thanx.
bamaredwingsfan
Android Enthusiast
When you say loaded a program, did you go though the rooting process? Or did you just download a program in the marketplace that says you must be rooted to use?
I downloaded from marketplace. It was ShootMe, after reading through some post on this website, someone mentioned "Rooted", they made it seem like this was a really bad thing to do (due to voiding the warranty). I'm lost, if this is true, how can these programs be available it they void the warranty on our phones?
bamaredwingsfan
Android Enthusiast
Just uninstall the program, as you have not rooted yet, and have nothing to worry about