I'm completely new to rooting (and android) and was just about ready to take my ally back for a droid, but if this is rooted and I can clean up the phone and get rid of the bloat and overclock the cpu a bit I think I'll love the phone.
So like I said I'm completely new so I'm not sure what to really do. I'm downloading umbuntu so I can load it from my flash drive, but I'm not sure what to do from there.
I'm completely new to rooting (and android) and was just about ready to take my ally back for a droid, but if this is rooted and I can clean up the phone and get rid of the bloat and overclock the cpu a bit I think I'll love the phone.
So like I said I'm completely new so I'm not sure what to really do. I'm downloading umbuntu so I can load it from my flash drive, but I'm not sure what to do from there.
They're finishing up an image that you can flash and from there they'll overclock i think they'll be done by the end of this week for the root that your asking for... So if you got time wait a week or so.
im also new..to rooting and linux.... will we still be using the andriod applications or will we be using linux or will linux be like the root and driod the surface program?
all this line of code confuses the crap out of me.... will it still need to be in line of code or once you get through the basic rooting return to a similair interface as andriod?
sorry last question do i gotta download the 700 mb ubuntu?
Quick question, as I am about to try this. Just follow what im saying and tell me if im on the right track and if not, point me in the right direction, please
1) Where the hell do I do all this
"backup mtds
# cat /dev/mtd/mtd0 > /sdcard/mtd0.img
do 0 through 7"
^ that. Where do I do that? I suppose that is a file you want me to back up, but Im not quite sure how to find it.
2) And then am I correct in assuming I will be making all of these mumbo jumbo commands in asroot2 (that I have currently extracted to my desktop)?
3) You probably want me to put asroot2 from my desktop to the phone?? And then use the terminal on my phone and type all that in? Or do I use asroot2 on my PC?
4) Im on Windows 7. Do I need to worry about this linux stuff?
Wait wait wait back up. I changed my mind. I think you want me to run this commands FROM my computer? Where do I do that? On my PCs "run" thingy? Bah! I need a little start.
im also new..to rooting and linux.... will we still be using the andriod applications or will we be using linux or will linux be like the root and driod the surface program?
all this line of code confuses the crap out of me.... will it still need to be in line of code or once you get through the basic rooting return to a similair interface as andriod?
sorry last question do i gotta download the 700 mb ubuntu?
Ubuntu is used to root your phone, it wont replace android or anything, your phones original operating system doesn't get replaced or anything.
And it doesn't matter what Ubuntu you get, all you need is the terminal
Quick question, as I am about to try this. Just follow what im saying and tell me if im on the right track and if not, point me in the right direction, please
1) Where the hell do I do all this
"backup mtds
# cat /dev/mtd/mtd0 > /sdcard/mtd0.img
do 0 through 7"
^ that. Where do I do that? I suppose that is a file you want me to back up, but Im not quite sure how to find it.
2) And then am I correct in assuming I will be making all of these mumbo jumbo commands in asroot2 (that I have currently extracted to my desktop)?
3) You probably want me to put asroot2 from my desktop to the phone?? And then use the terminal on my phone and type all that in? Or do I use asroot2 on my PC?
4) Im on Windows 7. Do I need to worry about this linux stuff?
Wait wait wait back up. I changed my mind. I think you want me to run this commands FROM my computer? Where do I do that? On my PCs "run" thingy? Bah! I need a little start.
First make sure you enabled USB Debugging on your phone
1) Open terminal/cmd (cmd = Command Prompt and its a little different than terminal because they're in different operating systems), if your adb shell is on the desktop than do:
cd ~/Desktop
./adb kill-server
./adb start-server
./adb shell
and after that you back up mtds
2) The hard part to the process is to make sure you type correct locations so it doesn't matter where it is as long as you can put the correct locations in terminal/cmd.
3) You are pushing superuser.apk to your phone asroot2 is just used to do the exploit.
4) Windows 7 should work but linux makes it a lot easier since these are all linux files and android is linux based. Ubuntu homepage | Ubuntu <<< LINUX
Backup is done in cmd (assuming you have Windows)> Start>Run> type "cmd"
Last edited by Vmanisme; June 29th, 2010 at 12:28 PM.
Would love to try this, but just not real comfortable doing it and i'm afraid of bricking my phone. Wish there was some simple installation method that wouldn't require me to use Ubuntu since i'm not overly familiar with linux. Plus, how do I make sure I can unroot and get the phone back to stock if need be? I never try anything unless I know I can back out of it easily.
Would love to try this, but just not real comfortable doing it and i'm afraid of bricking my phone. Wish there was some simple installation method that wouldn't require me to use Ubuntu since i'm not overly familiar with linux. Plus, how do I make sure I can unroot and get the phone back to stock if need be? I never try anything unless I know I can back out of it easily.
This wont brick your phone because you are not replacing the OS or flashing any ROM's. All you are doing is "installing a file" to the system so brick wont happen. And you can back up your mtds before rooting so if anything you can restore your phone any day.
Well that's nice to know, but that still leaves me with no knowledge of linux so how to backup and/or restore my phone is still a mystery to me (although I see the commands for backing up listed in the directions).
Plus, I was looking at the directions in the root thread and there are 'Updated steps' and 'Corrected steps' and I don't know which one to follow. Like I said, i'm a big dummy on this stuff.
Well that's nice to know, but that still leaves me with no knowledge of linux so how to backup and/or restore my phone is still a mystery to me (although I see the commands for backing up listed in the directions).
Plus, I was looking at the directions in the root thread and there are 'Updated steps' and 'Corrected steps' and I don't know which one to follow. Like I said, i'm a big dummy on this stuff.
Follow the last ones, i believe in the Corrected steps, and backing up is done like this:
cd ~/Desktop
./adb kill-server
./adb start-server
./adb shell
and after that you back up mtds:
# cat /dev/mtd/mtd0 > /sdcard/mtd0.img
# cat /dev/mtd/mtd1 > /sdcard/mtd1.img
# cat /dev/mtd/mtd2 > /sdcard/mtd2.img
# cat /dev/mtd/mtd3 > /sdcard/mtd3.img
# cat /dev/mtd/mtd4 > /sdcard/mtd4.img
# cat /dev/mtd/mtd5 > /sdcard/mtd5.img
# cat /dev/mtd/mtd6 > /sdcard/mtd6.img
# cat /dev/mtd/mtd7 > /sdcard/mtd7.img
--Note that for "mtd#" you'll need to replace it with the name of the mtd
The Following User Says Thank You to Vmanisme For This Useful Post:
Replace it with the name of the mtd......rrrriiiight. Like I would know what name to use. I think it's best I just stick with the stock installation for now.
Replace it with the name of the mtd......rrrriiiight. Like I would know what name to use. I think it's best I just stick with the stock installation for now.
Or just do the root and dont worry about brick, the worst that can happen with this method is it wont work.
I'm about to throw something through a wall here lol. OK I'm back in linux now. I figured out I was not in the right directory before, but now everytimei try and do ./adb push asroot2 /data/local/ i get error: insufficient permissions for device. Now I'm stuck here.
I have tried the Windows instructions and never have been able to get the # prompt as opposed to the $ prompt. I have tired it with the SD Card ion, out, mounted and unmounted and no luck. Any help would be appreciated.
I have tried the Windows instructions and never have been able to get the # prompt as opposed to the $ prompt. I have tired it with the SD Card ion, out, mounted and unmounted and no luck. Any help would be appreciated.
When I only received the $ prompt, I have typed 'exit' until I got back to the normal dos prompt. You usually have to type 'exit' twice. Then I type 'adb shell' and it went right to the # prompt.
Thanks for the response icon. when I get the $ and type exit it gives me another $ and then I type exit again and get back to a DOS prompt. When I go back into the adb shell I get the same $. At no time have I been able to get the # and have the mount command succeed. It is really driving me nuts as I can't figure out why it isn't working when I am following the instructions to the letter.
I just wanted to thank everyone for the help. Finally rooted Now I just gotta figure all this root stuff out lol. Anyone know if setcpu works for the ally?
Will, I suspect that it depends on what you mean by "works". I tried OverclockWidget, since it's free; didn't want to pay for setcpu yet. You can change the clock speed just fine within the normal limits, but you can't overclock it (i.e., 600 MHz is the limit). It looks like you might need kernel support to do any better, so my guess is the same would happen with setcpu... i.e., it will run, and you will be able to underclock, but you can't overclock until someone gets around to building a new kernel for the device.
can someone please post a different link to the asroot2 program, cause im beginning to think that the file gets corrupted during the download from its host site for me.
__________________
"No bastard ever won a war by dying for his country. He won it by making the other poor dumb bastard die for his country." General George Patton
So just to summarize; if you are having a problem with asroot2 not giving you a root shell (i.e., a # prompt), then:
(a) Take comfort in the fact that, at least, you are having problems at the right place. This is the actual hard step of the process, where we're exploiting a flaw in the phone software to essentially trick the phone into doing something it wasn't supposed to do.
Related to this, though, realize that no one really *knows* for sure how to make asroot2 work correctly. A lot of us have gotten it to work, but if we were to have to do it again, we might be just as bad off as you.
(b) Try all sorts of things with the SD card. That seems to make a difference for a lot of people. Try toggling the option to share the SD card with the operating system (by clicking the "Ongoing" item in the notification bar). Try removing and reinserting the SD card. Try exiting and rerunning the adb shell command. And every time you change *anything*, run asroot2 again to see if it works. This really is just a matter of fiddling until something happens.
(c) It is extremely unlikely that trying a different operating system will have any effect on whether asroot2 functions. I know a lot of people are talking about getting Linux to do this, but it's almost surely not worth your time to go install Linux somewhere if you've already got this far. Unless of course you just wanted the better operating system anyway.
As I've reported before, I seemed to get asroot2 working consistently by ensuring that the phone was connected by USB with USB debugging enabled, and the SD card shared with the computer. That might have just been a coincidence, though. Like I said, no one really knows for sure.
The Following 2 Users Say Thank You to cdsmith For This Useful Post:
ive tried everything various times but cannot get to the root( #) prompt
anyone else had a problem and solved it using a method named above? im stuck... could i have pushed some thing incorrectly? i did mess up but started back over... will a reboot fix it? and should i start over?
If you are getting "permission denied" when trying to run the command "adb push <file> <file>" try copying the files to the sd card manually through windows.
(please note: my card was drive F: yours probably will be a different letter)
**************************************
very important here - also copy the "asroot2" program to the SD card. I don't have it pictured because I didn't need to use this method
****************************************
If you copied these files manually, and if you did this while you were connected into your phone (through "adb shell"), type exit until you get back to the windows command prompt (c:\android\sdk\tools). After that, use windows to eject drive F: (or what ever drive letter you had - from the task bar icon near the time in the bottom right hand corner of your screen) then unplug the phone from the computer. Wait about 5-10 second and plug the phone back in. wait another couple of seconds for windows to recognize the phone and then go back to the command prompt window and type in:
adb devices
if you see your phone again (which you should) skip the "adb push" and the "adb shell chmod ..." commands in my windows guide and type in:
adb shell
***************************************
very important here.....
If windows can see your SD card, the phone will NOT be able to access it. If, after you plug the phone back into your computer, windows wants to look at the contents then just leave the phone connected to the computer and use windows' eject icon and "eject the drive". Windows must not be able to see the SD card for you to continue.
*************************************
Once again you should see the "$" prompt. At this point, type in these two commands
cat /sdcard/asroot2 > /data/local/asroot2
chmod 777 /data/local/asroot2
From here, you should be able to start with step 9 in my windows guide and go from there. Let me know if you're still having issues.
Last edited by Crux.V; July 3rd, 2010 at 09:30 AM.
$ ls -l
ls -l -rwxrwxrwx shell shell 74512 2010-07-02 08:31 asroot2
drwxrwx--x shell shell 2010-06-07 00:59 tmp
$
the line that I bolded is the one you want to see. if you don't see that line, the asroot2 program is not on your phone and you need to reread/retry the steps above.
if you see that exact line, type in:
cd /system/bin
then:
ls -l
*WARNING* there are a lot of file in this directory, you will probably have to search pretty hard for the "sh" program.
these lines will probably not be exactly like what you see on your phone but the line I bolded needs to be somewhere in that long list of programs. If you don't see "sh" anywhere... you have a real problem with your phone.
Evidentally once you ever get permission denied errors on the sdcard they can't be removed. I just formated the sdcard, rebooted both pc an phone and they are still showing up. Maybe the card is a cheap piece of crap, so im gonna go get a new card tonight as see whats up with that.
bamared, Can you please post exactly what command you're typing, and exactly what error you're getting from it? I'm looking around for that information, but I don't see it off-hand.
bamared, Can you please post exactly what command you're typing, and exactly what error you're getting from it? I'm looking around for that information, but I don't see it off-hand.
Im connecting the phone to the pc and running the adb device command to make sure the phone is connected. Next i will run the allyroot.bat file and it will slam back permission denied errors when the bat file tries to write the su and superuser.apk file to the sdcard. asroot2 will write correctly as it should, but those other 2 files wont. I also get the same errors if i just do the commands one at time via adb as well.
I will say though that i did get the allyroot.bat file work correctly the very 1st time i ran it. But when i got to the last command or 2 where you supposed to get the # sign, it would never work and say enjoy the shell but always be the $ sign. I tried all the steps to rerun that last step or 2 again an it would always be the same, it would say it worked but never give me the root sign. So i just closed out of the whole thing, and now all i get is permission denied errors when i am running the bat file or doing it the manual way
As for which commands, i have typed them word for word, an also just cut an pasted them into Cpromt as well always getting the same results. Going by crux.v's walkthrough of course. I have a dual booting PC with windows 7 an XP as well, and i get those errors either which way i go.
Also if a mod would like to delete my posts from the original root thread, please do in the interest of cleaning up the thread.
Last edited by bamaredwingsfan; July 2nd, 2010 at 07:36 PM.
$ ls -l
ls -l -rwxrwxrwx shell shell 74512 2010-07-02 08:31 asroot2
drwxrwx--x shell shell 2010-06-07 00:59 tmp
$
the line that I bolded is the one you want to see. if you don't see that line, the asroot2 program is not on your phone and you need to reread/retry the steps above.
if you see that exact line, type in:
cd /system/bin
then:
ls -l
*WARNING* there are a lot of file in this directory, you will probably have to search pretty hard for the "sh" program.
these lines will probably not be exactly like what you see on your phone but the line I bolded needs to be somewhere in that long list of programs. If you don't see "sh" anywhere... you have a real problem with your phone.
I think i may see my error. When i do the above commands, here is what mine says
-rwxrwxrwx shell shell 0 2010-07-02 19:52 asroot2 -rw-rw-rw- shell shell 46809 2010-06-30 21:09 asroot2.txt
im thinking it shouldn't be a text file there. How do i delete it an start over?
Last edited by bamaredwingsfan; July 2nd, 2010 at 08:09 PM.
Holy cow, i did it. Im going to be honest, i don't know how i did it, but i did it. I did alot of removing and inserting the sdcard at various stages of the install so may times, i lost count. But that had alot to do with it. I will cut an past my install log, and maybe somebody can make heads or tails out of it and see something i did an it help them out.
Quote:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Jason Hayes>cd c:\android\sdk\tools
C:\android\sdk\tools>adb devices
List of devices attached
A00000215934EF device
C:\android\sdk\tools>dir
Volume in drive C has no label.
Volume Serial Number is 18EF-9BE4
Directory of C:\android\sdk\tools
07/02/2010 12:01 AM <DIR> .
07/02/2010 12:01 AM <DIR> ..
07/01/2010 11:58 PM 578,611 adb.exe
07/01/2010 11:58 PM 96,256 AdbWinApi.dll
07/01/2010 11:58 PM 60,928 AdbWinUsbApi.dll
07/01/2010 11:58 PM 517 allyroot.bat
07/01/2010 11:58 PM 3,394 android.bat
07/01/2010 11:58 PM 1,565 apkbuilder.bat
07/01/2010 11:58 PM 2,129 ddms.bat
07/01/2010 11:58 PM 302,823 dmtracedump.exe
07/01/2010 11:58 PM 1,491 draw9patch.bat
07/01/2010 11:58 PM 8,596,234 emulator.exe
07/01/2010 11:58 PM 17,976 emulator_NOTICE.txt
07/01/2010 11:58 PM 921,075 etc1tool.exe
07/01/2010 11:58 PM 336,613 fastboot.exe
07/01/2010 11:58 PM 1,528 hierarchyviewer.bat
07/01/2010 11:58 PM 216,987 hprof-conv.exe
07/01/2010 11:59 PM <DIR> Jet
07/01/2010 11:59 PM 1,680 layoutopt.bat
07/02/2010 12:01 AM <DIR> lib
07/02/2010 12:01 AM 212,741 mksdcard.exe
07/02/2010 12:01 AM 205,851 NOTICE.txt
07/02/2010 12:01 AM 33 source.properties
07/02/2010 12:01 AM 1,627,623 sqlite3.exe
07/02/2010 12:01 AM <DIR> su
07/02/2010 12:01 AM 1,982 traceview.bat
07/02/2010 12:01 AM 628,727 zipalign.exe
22 File(s) 13,816,764 bytes
5 Dir(s) 68,573,335,552 bytes free
C:\android\sdk\tools>adb shell
$ cat /sdcard/asroot2 > /data/local/asroot2
cat /sdcard/asroot2 > /data/local/asroot2
cannot create /data/local/asroot2: text busy
$ chmod 777 /data/local/asroot2
chmod 777 /data/local/asroot2
$ chmod 777 /data/local/asroot2
chmod 777 /data/local/asroot2
$ /data/local/asroot2 /system/bin/sh
/data/local/asroot2 /system/bin/sh
[+] Using newer pipe_inode_info layout
Opening: /proc/15537/fd/3
SUCCESS: Enjoy the shell.
$ data/local/asroot2 /system/bin/sh
data/local/asroot2 /system/bin/sh
[+] Using newer pipe_inode_info layout
Opening: /proc/15544/fd/3
SUCCESS: Enjoy the shell.
$ exit
exit
$ adb shell
adb shell
adb: permission denied
$ data/local/asroot2 /system/bin/sh
data/local/asroot2 /system/bin/sh
[+] Using newer pipe_inode_info layout
Opening: /proc/15556/fd/3
SUCCESS: Enjoy the shell.
$ adb push asroot2 /data/local/
adb push asroot2 /data/local/
adb: permission denied
$ adb shell chmod 0755 /data/local/asroot2
adb shell chmod 0755 /data/local/asroot2
adb: permission denied
$ data/local/asroot2 /system/bin/sh
data/local/asroot2 /system/bin/sh
[+] Using newer pipe_inode_info layout
Opening: /proc/15571/fd/3
SUCCESS: Enjoy the shell.
$ chmod 0755 /data/local/asroot2
chmod 0755 /data/local/asroot2
$ cat /sdcard/asroot2 > /data/local/asroot2
cat /sdcard/asroot2 > /data/local/asroot2
cannot create /data/local/asroot2: text busy
$ cat /sdcard/asroot2 > /data/local/asroot2
cat /sdcard/asroot2 > /data/local/asroot2
cannot create /data/local/asroot2: text busy
$ data/local/asroot2 /system/bin/sh
data/local/asroot2 /system/bin/sh
[+] Using newer pipe_inode_info layout
Opening: /proc/15699/fd/3
SUCCESS: Enjoy the shell.
$ data/local/asroot2 /system/bin/sh
data/local/asroot2 /system/bin/sh
[+] Using newer pipe_inode_info layout
Opening: /proc/15722/fd/3
SUCCESS: Enjoy the shell.
$ data/local/asroot2 /system/bin/sh
data/local/asroot2 /system/bin/sh
[+] Using newer pipe_inode_info layout
Opening: /proc/15727/fd/3
SUCCESS: Enjoy the shell.
$ data/local/asroot2 /system/bin/sh
data/local/asroot2 /system/bin/sh
[+] Using newer pipe_inode_info layout
Opening: /proc/15732/fd/3
SUCCESS: Enjoy the shell.
$ data/local/asroot2 /system/bin/sh
data/local/asroot2 /system/bin/sh
[+] Using newer pipe_inode_info layout
Opening: /proc/15748/fd/3
SUCCESS: Enjoy the shell.
$ data/local/asroot2 /system/bin/sh
data/local/asroot2 /system/bin/sh
[+] Using newer pipe_inode_info layout
Opening: /proc/15753/fd/3
SUCCESS: Enjoy the shell.
$ data/local/asroot2 /system/bin/sh
data/local/asroot2 /system/bin/sh
[+] Using newer pipe_inode_info layout
Opening: /proc/15756/fd/3
SUCCESS: Enjoy the shell.
$ data/local/asroot2 /system/bin/sh
data/local/asroot2 /system/bin/sh
[+] Using newer pipe_inode_info layout
Opening: /proc/15759/fd/3
SUCCESS: Enjoy the shell.
$ data/local/asroot2 /system/bin/sh
data/local/asroot2 /system/bin/sh
[+] Using newer pipe_inode_info layout
Opening: /proc/15767/fd/3
SUCCESS: Enjoy the shell.
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
# cat /sdcard/Superuser.apk > /system/app/Superuser.apk
cat /sdcard/Superuser.apk > /system/app/Superuser.apk
/sdcard/Superuser.apk: No such file or directory
# cat /sdcard/Superuser.apk > /system/app/Superuser.apk
cat /sdcard/Superuser.apk > /system/app/Superuser.apk
/sdcard/Superuser.apk: No such file or directory
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
# cat /sdcard/Superuser.apk > /system/app/Superuser.apk
cat /sdcard/Superuser.apk > /system/app/Superuser.apk
/sdcard/Superuser.apk: No such file or directory
# cat /sdcard/su > /system/bin/su
cat /sdcard/su > /system/bin/su
/sdcard/su: No such file or directory
# chmod 06755 /system/bin/su
chmod 06755 /system/bin/su
# chmod 777 /data/local/asroot2.txt
chmod 777 /data/local/asroot2.txt
# rm /data/local/asroot2.txt
rm /data/local/asroot2.txt
# cat /sdcard/Superuser.apk > /system/app/Superuser.apk
cat /sdcard/Superuser.apk > /system/app/Superuser.apk
/sdcard/Superuser.apk: No such file or directory
# cat /sdcard/Superuser.apk > /system/app/Superuser.apk
cat /sdcard/Superuser.apk > /system/app/Superuser.apk
# cat /sdcard/su > /system/bin/su
cat /sdcard/su > /system/bin/su
# chmod 06755 /system/bin/su
chmod 06755 /system/bin/su
# reboot
reboot
C:\android\sdk\tools>
The LG Ally was one of the first Android handsets from the Korean manufacturer to see a US release. The QWERTY slider came to Verizon in the spring of 2010 as a mid-range smartphone geared towards those looking for a solid media and messaging... Read More
Ask question's here (Dont flood the root topic, please)
Now I just gotta figure all this root stuff out lol. Anyone know if setcpu works for the ally?
