So I installed the latest ASUS firmware update (build 9.4.2.11) and lost root. I did not have OTA Rootkeeper (like an idiot) so I'm wondering if there is any way of re-rooting/restoring root without having to flash back to an earlier version.
If anyone can figure it out, it would be greatly appreciated.
You'll just have to wait until viperboy finds a way of rooting that firmware most likely. It shouldn't be too long.
I'm an idiot too.
Sent from my Transformer Prime TF201 using Tapatalk
I cringed as soon as I clicked that install button, but there was no way to cancel or stop the update to . . . soon as one of our awesome devs finds a new way to root, if any kind soul could post here to share the joy would be much appreciated.
zeusal said:
I cringed as soon as I clicked that install button....
Click to expand...
Click to collapse
I hang my head in shame also....
Made the same stupid move here
Looks like a lot of us in the same boat. Nothing to do but wait for a new root solution. I wish there was a way I could go back to previous version, root use OTA rootkeeper, then update. Other than that, the update is working great. Wifi signal seems to be a bit better, and I'm getting locks with GPS now.
Sent from my Transformer Prime TF201 using Tapatalk
Same thing here. Tried unrooting then rerooting using the viperboy primetime method and it didnt work. So now i just keep refreshing a bunch of different pages to see if anyone finds another way lol
Mea culpa etiam.
Sent from my Thunderbolt using Tapatalk
i was reading the root keeper as it was verifying the install, i was like NOOOOOOO
and well, you know the rest.
soon enough.
props to viper.
lets hope we have root again soon,
i do notice more stable wifi, it was going NUTS before the update, and now its great, and i already sideloaded my apps when i WAS rooted, so im kinda ok for a bit.
weeee,
loveing my prime, and cant wait for bootloader to be unlocked and get some stellar roms on this beast.
~k
I actually used ota root keeper, updated, and my update rendered it basically useless... I had no choice but to sideload it I guess at least now I have a functional tab again
For those who may have subscribed to this thread, good news if you are comfortable using ADB and shell.
I just used the stripped down version of ADB included with the previous one click root.
Testing that ADB has access
C:\Users\Zeusal\Downloads\TransformerPrimeRootICS>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:/ $ exit
exit
Executing commands from [ROOT] Mempodroid root - ICS including 9.4.2.11 I would have posted the below as feedback on actual thread to help those having issues troubleshoot, but I didn't have permission
C:\Users\Zeusal\Downloads\TransformerPrimeRootICS>adb push mempodroid /data/l
ocal
568 KB/s (37273 bytes in 0.064s)
C:\Users\Zeusal\Downloads\TransformerPrimeRootICS>adb push su /data/local
642 KB/s (22364 bytes in 0.034s)
C:\Users\Zeusal\Downloads\TransformerPrimeRootICS>adb shell chmod 777 /data/l
ocal/mempodroid
C:\Users\Zeusal\Downloads\TransformerPrimeRootICS>adb shell /data/local/mempo
droid 0xd9ec 0xaf47 mount -o remount,rw '' /system
C:\Users\Zeusal\Downloads\TransformerPrimeRootICS>adb shell
[email protected]:/ $ /data/local/mempodroid 0xd9ec 0xaf47 sh
/data/local/mempodroid 0xd9ec 0xaf47 sh
[email protected]:/ # cat /data/local/su > /system/xbin/su
cat /data/local/su > /system/xbin/su
[email protected]:/ # chown 0.0 /system/xbin/su
chown 0.0 /system/xbin/su
[email protected]:/ # chmod 06755 /system/xbin/su
chmod 06755 /system/xbin/su
[email protected]:/ # exit
exit
[email protected]:/ $ exit
exit
C:\Users\Zeusal\Downloads\TransformerPrimeRootICS>adb shell rm /data/local/me
mpodroid
C:\Users\Zeusal\Downloads\TransformerPrimeRootICS>adb shell rm /data/local/su
C:\Users\Zeusal\Downloads\TransformerPrimeRootICS>adb reboot
After Reboot
Launch Super User app if you were previously rooted, or else download it from the market
Execute from Options, "Su binary__Tap to check for updates", then update anyway to install busybox etc.
Root complete and functional, thank you very much for posting se1000!
Related
EDIT: Great news! We have an on-device one-click root again!
Simply download VISIONary from (edit: used to be in the Market) Modaco. I tried it on FRG83 stock. It works. No ADB, no external computer required, no fuss. Thanks to the developers!
EDIT again: Sorry, the FRG83D build no longer works with VISIONary - BUT - the overall rageagainstthecage method still works via ADB. I also hear that SuperOneClick works but it requires a Windows machine.
----
Ok it's been established that Universal Androot / exploid / freenexus no longer works on FRG33/FRG83 etc. And it's been established that "rageagainstthecage" does still work. So far I'm not aware of a one-click method to implement the latter exploit.
So I'm starting this thread to centralize everyone's experiences. I don't personally need these instructions but other folks apparently do. I've quoted a rooting guide in post #2. If you think any refinements are necessary or you have a better way of writing it out, please feel free to add to this thread.
Thanks to efrant for pointing the way to this guide. Based on comments below, I'm quoting another revised version.
hmanxx said:
Hi OP,
You may want to edit your post #2, I have inserted the mounting commands in the thread i posted previously. this will help novice users to get thing right out of box without figuring why permission denied.
I have just tried out the additional mounting steps..things are working fine..
Tidy up step by step rooting
1) Getting rageagainstthecage-arm5.bin
http://stealth.openwall.net/xSports/RageAgainstTheCage.tgz
2) Getting Superuser.apk, busybox,su
http://forum.xda-developers.com/showthread.php?t=736271
Or
Find yourself..there are many floating around.
3) Rooting Process (Installing custom Recovery rom section is deleted to simplify illustration
Reference:http://forum.xda-developers.com/showpost.php?p=8120790&postcount=250
Code:
F:\ADB>adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage
263 KB/s (5392 bytes in 0.020s)
F:\ADB>adb shell chmod 700 /data/local/tmp/rageagainstthecage
F:\ADB>adb shell
$ cd /data/local/tmp
cd /data/local/tmp
$ ./rageagainstthecage
./rageagainstthecage
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C
[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3084, 3084}
[*] Searching for adb ...
[+] Found adb as PID 64
[*] Spawning children. Dont type anything and wait for reset!
[*]
[*] If you like what we are doing you can send us PayPal money to
[*] 7-4-3-C[at]web.de so we can compensate time, effort and HW costs.
[*] If you are a company and feel like you profit from our work,
[*] we also accept donations > 1000 USD!
[*]
[*] adb connection will be reset. restart adb server on desktop and re-login.
$
F:\ADB>adb kill-server
F:\ADB>adb start-server
* daemon not running. starting it now *
* daemon started successfully *
F:\ADB>adb shell
#mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
Follow the following steps to install Superuser.apk, busybox,su
F:\ADB>adb shell
# cd /data/local/tmp
cd /data/local/tmp
# ./busybox cp busybox /system/bin
./busybox cp busybox /system/bin
# chmod 4755 /system/bin/busybox
chmod 4755 /system/bin/busybox
# busybox cp Superuser.apk /system/app
busybox cp Superuser.apk /system/app
# busybox cp su /system/bin
busybox cp su /system/bin
# chmod 4755 /system/bin/su
chmod 4755 /system/bin/su
# exit
exit
F:\ADB>adb shell
# su
su
#mount -o remount,ro -t yaffs2 /dev/block/mtdblock3 /system
# exit
exit
Click to expand...
Click to collapse
And below are the previous contents of this post, prior to editing.
-------------
Many respondents on this thread have indicated that the instructions don't work the first time. If you get to the step where you are supposed to get a root shell (#) but you instead get a non-root shell ($), start from the top and try the exploit once or twice more. Apparently if you are persistent it will work.
I'm also told these instructions are missing adb remount before the steps where you push busybox, su and so forth.
hmanxx said:
Tidy up step by step rooting
1) Getting rageagainstthecage-arm5.bin
http://stealth.openwall.net/xSports/RageAgainstTheCage.tgz
2) Getting Superuser.apk, busybox,su
http://forum.xda-developers.com/showthread.php?t=736271
Or
Find yourself..there are many floating around.
3) Rooting Process (Installing custom Recovery rom section is deleted to simplify illustration
Reference:http://forum.xda-developers.com/showpost.php?p=8120790&postcount=250
Code:
F:\ADB>adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage
263 KB/s (5392 bytes in 0.020s)
F:\ADB>adb shell chmod 700 /data/local/tmp/rageagainstthecage
F:\ADB>adb shell
$ cd /data/local/tmp
cd /data/local/tmp
$ ./rageagainstthecage
./rageagainstthecage
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C
[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3084, 3084}
[*] Searching for adb ...
[+] Found adb as PID 64
[*] Spawning children. Dont type anything and wait for reset!
[*]
[*] If you like what we are doing you can send us PayPal money to
[*] 7-4-3-C[at]web.de so we can compensate time, effort and HW costs.
[*] If you are a company and feel like you profit from our work,
[*] we also accept donations > 1000 USD!
[*]
[*] adb connection will be reset. restart adb server on desktop and re-login.
$
F:\ADB>adb kill-server
F:\ADB>adb start-server
* daemon not running. starting it now *
* daemon started successfully *
F:\ADB>adb shell
#
Follow the following steps to install Superuser.apk, busybox,su
F:\ADB>adb shell
# cd /data/local/tmp
cd /data/local/tmp
# ./busybox cp busybox /system/bin
./busybox cp busybox /system/bin
# chmod 4755 /system/bin/busybox
chmod 4755 /system/bin/busybox
# busybox cp Superuser.apk /system/app
busybox cp Superuser.apk /system/app
# busybox cp su /system/bin
busybox cp su /system/bin
# chmod 4755 /system/bin/su
chmod 4755 /system/bin/su
# exit
exit
F:\ADB>adb shell
# su
su
# exit
exit
Click to expand...
Click to collapse
I too am interested in this info. Looking forward to any info provided....
There is detailed step-by-step info in many threads as to how to use the rageagainstthecage exploit to root your device, e.g.: http://forum.xda-developers.com/showpost.php?p=8300203&postcount=55
Why start a new thread?
efrant said:
There is detailed step-by-step info in many threads as to how to use the rageagainstthecage exploit to root your device, e.g.: http://forum.xda-developers.com/showpost.php?p=8300203&postcount=55
Why start a new thread?
Click to expand...
Click to collapse
Actually that's perfect, thanks.
I started a new thread because the step-by-step info is buried in other threads and many folks post questions asking about it because they can't find said guides. I figured if I could start a new thread with a proper title, it would be located more easily.
All the info is located in Nexus One Wiki, under "Guides" / "Rooting". Direct link to the post with complete data. So I still don't see any need for the post, that will be buried in forum depths. My signature..
But since you posted it, and it's more detailed - I'll change the link to point to it.
[edit 2] The Wiki is damn slow after the forum crash...
[edit 3] It refuses to accept the submit, complaining about "session data loss". Time to complain to admins..
Heh well if the Wiki is crashy at the moment, all the more reason to have a redundant post here.
If you look back to the linked posts, I was the one who suggested which instructions for ali3nfr3ak to follow after a successful push of rageagainstthecage, and then ali3nfr3ak reported success on FRG33, and then hmanxx seems to have stripped out the irrelevant/unnecessary lines. So it's teamwork =)
One thing I'm not sure of - I see the original "exploid"/"freenexus" instructions included a cleanup by removing /system/bin/rootshell. Should something similar be done after rageagainstthecage to clean up?
@ cmstlst This is a good idea, because when I did this I had like 3 different pages open as all the information was spread everywhere, hopefully this will make it easier for everyone to follow, good one
I used the steps posted here to restore root access to a Nexus One which had been previously rooted with 1-click. It was running stock FRF91. It was a fairly smooth process, especially since the update to FRG83 did not delete my Superuser.apk, su, or busybox files. The permissions had just been turned down, so with the RageAgainstTheCage exploit active, I was able to change the permissions as indicated and was off and running.
The only gotcha I ran into was that I had to mount the /system partition read/write before I could set permissions on the files there. After the exploit was active and I had shelled back into the phone via ADB, I issued the command
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
for the read/write mount and was then able to turn up the permissions. And, in the interests of completeness, to mount /system read-only again afterward:
mount -o remount,ro -t yaffs2 /dev/block/mtdblock4 /system
Thanks much for consolidating the procedure where it was easy to find.
anyway to re-lock the Bootloader
highvista said:
The only gotcha I ran into was that I had to mount the /system partition read/write before I could set permissions on the files there. After the exploit was active and I had shelled back into the phone via ADB, I issued the command
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
Click to expand...
Click to collapse
It's mtdblock3, not mtdblock4, though for some reason the mount worked for me even on 6. But in any case, much better and easier done using ADB command:
adb remount
Finally the Wiki is also back to work, the "Rooting FRG83" link is updated to point to this thread.
Here, the rageagainstthecage didn't work.
I followed these steps:
F:\ADB>adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage
263 KB/s (5392 bytes in 0.020s)
F:\ADB>adb shell chmod 700 /data/local/tmp/rageagainstthecage
F:\ADB>adb shell
$ cd /data/local/tmp
cd /data/local/tmp
$ ./rageagainstthecage
./rageagainstthecage[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3084, 3084}[*] Searching for adb ...
[+] Found adb as PID 64[*] Spawning children. Dont type anything and wait for reset![*][*] If you like what we are doing you can send us PayPal money to[*] 7-4-3-C[at]web.de so we can compensate time, effort and HW costs.[*] If you are a company and feel like you profit from our work,[*] we also accept donations > 1000 USD![*][*] adb connection will be reset. restart adb server on desktop and re-login.
$
F:\ADB>adb kill-server
F:\ADB>adb start-server
* daemon not running. starting it now *
* daemon started successfully *
F:\ADB>adb shell
#
Click to expand...
Click to collapse
But, I didn't get root shell (#), when I typed "adb shell" I still got ($).
I'm in FRG83, Android 2.2.1.
Any ideas?
cmstlist said:
Thanks to efrant for pointing the way to this guide.
Click to expand...
Click to collapse
Thank you for posting this. It was a big help. I lost my root after 2.2.1 and this worked great. I did have to execute the .bin file 3 times. The first time, I got $, and the second time as well. It was only on the 3rd execute that I got the # prompt. I read that others had the same problem, that it only worked after a few times.
highvista said:
I used the steps posted here to restore root access to a Nexus One which had been previously rooted with 1-click. It was running stock FRF91. It was a fairly smooth process, especially since the update to FRG83 did not delete my Superuser.apk, su, or busybox files. The permissions had just been turned down, so with the RageAgainstTheCage exploit active, I was able to change the permissions as indicated and was off and running.
The only gotcha I ran into was that I had to mount the /system partition read/write before I could set permissions on the files there. After the exploit was active and I had shelled back into the phone via ADB, I issued the command
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
for the read/write mount and was then able to turn up the permissions. And, in the interests of completeness, to mount /system read-only again afterward:
mount -o remount,ro -t yaffs2 /dev/block/mtdblock4 /system
Thanks much for consolidating the procedure where it was easy to find.
Click to expand...
Click to collapse
Thank you for this. I was in the same situation and I was not able to set the premissions. Then I saw your post. I am not a Linux/Unix guy, so it was step-by-step for me. Curiously, why is it necessary to change the premission for su, busybox, etc.?
Thanks guys.
Atento said:
Here, the rageagainstthecage didn't work.
I followed these steps:
But, I didn't get root shell (#), when I typed "adb shell" I still got ($).
I'm in FRG83, Android 2.2.1.
Any ideas?
Click to expand...
Click to collapse
I had this, too. Like the above poster said, I got # after several tries. However something went wrong midway through the other steps from efrant, and I went back and lost #, only had $.
Also looking for ideas.
Xel'Naga said:
I had this, too. Like the above poster said, I got # after several tries. However something went wrong midway through the other steps from efrant, and I went back and lost #, only had $.
Also looking for ideas.
Click to expand...
Click to collapse
I would try the process over again from the beginning. Once you get the #, follow highvista's information to mount the file system as RW, and do the chmods. After you are done, re-mount as RO.
snovvman said:
I would try the process over again from the beginning. Once you get the #, follow highvista's information to mount the file system as RW, and do the chmods. After you are done, re-mount as RO.
Click to expand...
Click to collapse
Yup, had to reboot the device and try again about four times and then it finally all stuck. Now rooted on 2.2.1.
snovvman said:
Thank you for posting this. It was a big help. I lost my root after 2.2.1 and this worked great. I did have to execute the .bin file 3 times. The first time, I got $, and the second time as well. It was only on the 3rd execute that I got the # prompt. I read that others had the same problem, that it only worked after a few times.
Thank you for this. I was in the same situation and I was not able to set the premissions. Then I saw your post. I am not a Linux/Unix guy, so it was step-by-step for me. Curiously, why is it necessary to change the premission for su, busybox, etc.?
Thanks guys.
Click to expand...
Click to collapse
Thanks for your replies! I'm rooted now.
Thanks for all!!!
Hi OP,
You may want to edit your post #2, I have inserted the mounting commands in the thread i posted previously. this will help novice users to get thing right out of box without figuring why permission denied.
I have just tried out the additional mounting steps..things are working fine..
Tidy up step by step rooting
1) Getting rageagainstthecage-arm5.bin
http://stealth.openwall.net/xSports/...nstTheCage.tgz
2) Getting Superuser.apk, busybox,su
http://forum.xda-developers.com/showthread.php?t=736271
Or
Find yourself..there are many floating around.
3) Rooting Process (Installing custom Recovery rom section is deleted to simplify illustration
Reference:http://forum.xda-developers.com/show...&postcount=250
Code:
F:\ADB>adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage
263 KB/s (5392 bytes in 0.020s)
F:\ADB>adb shell chmod 700 /data/local/tmp/rageagainstthecage
F:\ADB>adb shell
$ cd /data/local/tmp
cd /data/local/tmp
$ ./rageagainstthecage
./rageagainstthecage[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3084, 3084}[*] Searching for adb ...
[+] Found adb as PID 64[*] Spawning children. Dont type anything and wait for reset![*][*] If you like what we are doing you can send us PayPal money to[*] 7-4-3-C[at]web.de so we can compensate time, effort and HW costs.[*] If you are a company and feel like you profit from our work,[*] we also accept donations > 1000 USD![*][*] adb connection will be reset. restart adb server on desktop and re-login.
$
F:\ADB>adb kill-server
F:\ADB>adb start-server
* daemon not running. starting it now *
* daemon started successfully *
F:\ADB>adb shell
#mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
Follow the following steps to install Superuser.apk, busybox,su
F:\ADB>adb shell
# cd /data/local/tmp
cd /data/local/tmp
# ./busybox cp busybox /system/bin
./busybox cp busybox /system/bin
# chmod 4755 /system/bin/busybox
chmod 4755 /system/bin/busybox
# busybox cp Superuser.apk /system/app
busybox cp Superuser.apk /system/app
# busybox cp su /system/bin
busybox cp su /system/bin
# chmod 4755 /system/bin/su
chmod 4755 /system/bin/su
# exit
exit
F:\ADB>adb shell
# su
su
#mount -o remount,ro -t yaffs2 /dev/block/mtdblock3 /system
# exit
exit
Thanks, I'll fix it up when I'm at a desktop computer again and less occupied by the Masters thesis I'm defending in just over 2 weeks
Sent from my Nexus One using XDA App
hehe oh noes. I gave the cage file a go 3 times, failed, so I got pissed and unlocked the bootloader, then now I read about the remounting of the file system.. didn't think about that.
well.. now I can't undo the unlocking :/
** This is completely unsupported!!!!!!! **
ALL credit goes to saurik for the root method, Jason A. Donenfeld (zx2c4) for finding the exploit, alpharevx for finding the offsets and initial confirmation on the Transformer Prime and viperboy for finding it and posting it in his thread. I did not research, find, or develop this root method!
Mods, if I've done anything wrong, please feel free to remove this thread.
You will need to know how to use ADB commands, otherwise, use viperMOD PrimeTime!!!!!!!!!!!!!!!!!!!!!!!!.
Downloads:
mempodroid binary
su binary
Root:
adb push mempodroid /data/local
adb push su /data/local
adb shell
chmod 777 /data/local/mempodroid
/data/local/mempodroid 0xd9ec 0xaf47 sh
** You should now be in a remote shell session with root (indicated by #)
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
** IF you have previously rooted your Prime, run the following two commands. They may throw an error that the file a file was not found.
rm /system/bin/su
rm /system/xbin/su
cat /data/local/su > /system/xbin/su
chown 0.0 /system/xbin/su
chmod 06755 /system/xbin/su
rm /data/local/mempodroid
rm /data/local/su
exit
exit
adb reboot
After your Transformer Prime comes up, install Superuser from android market.
HOPEFULLY everyone has learned their lesson and will also install Voodoo Rootkeeper as well!!!!!!!!!!!!!!!!!!!! R
Enjoi!!!!!!!!!!!!!!!
** Feb 21 2012 Edit **
Works on 9.4.2.14
** Feb 09 2012 Edit **
Works on 9.4.2.13
** Jan 25 2012 Edit **
Changed the mount command - thanks viperboy!
Added steps to possibly resolve issues with previously rooted systems
Changed a few steps to be a little bit easier.
**Jan 24 2012 Edit **
Some people are reporting issues with this method. I suspect this is due to previously having root or other altered files. A method that has worked for some is to update to 9.4.2.11.1 and then following the above procedures. Please note, this firmware release is unofficial and at this time THERE IS NO DOWNGRADE PATH.
i keep getting permission denied after
adb shell /data/local/mempodroid 0xd9ec 0xaf47 mount -o remount,rw '' /system
i missed a chmod step, add it just now.
run:
adb shell chmod 777 /data/local/mempodroid
and then pick up right where you left off.
as i am not root nor superuser .. i don't even get access
/ $ cd data
~ $ ls
ls: can't open '.': Permission denied
after this command
adb shell /data/local/mempodroid 0xd9ec 0xaf47 sh
i got [email protected]:/ # but i cant type anything else in the dos windows after it.. can you explain further please
insane111 said:
after this command
adb shell /data/local/mempodroid 0xd9ec 0xaf47 sh
i got [email protected]:/ # but i cant type anything else in the dos windows after it.. can you explain further please
Click to expand...
Click to collapse
click on the window, you should be able to continue typing
/mnt/sdcard/Download $ adb push su /data/local
error: device not found
for some odd reason i cant type anything else after on that window..
after shell with root, i get the #, but i can't type anything afterwards. do i just repeat the process over?
edit: question was already asked, tried clicking on window, doesn't work.
insane111 said:
for some odd reason i cant type anything else after on that window..
Click to expand...
Click to collapse
updating!
10 char
toby77jo said:
/mnt/sdcard/Download $ adb push su /data/local
error: device not found
Click to expand...
Click to collapse
no offense, you may want to just wait for the one click root.
Tairen said:
after shell with root, i get the #, but i can't type anything afterwards. do i just repeat the process over?
edit: question was already asked, tried clicking on window, doesn't work.
Click to expand...
Click to collapse
updated, should be working now.
hehe that is fine .. not offended
se1000 said:
updated, should be working now.
Click to expand...
Click to collapse
thank you very much sir.. it work...
insane111 said:
thank you very much sir.. it work...
Click to expand...
Click to collapse
NICE!!!!!!!!!!!!!!!!!!!!
hmm did everything on your post, and rebooted. already had SU so i just opened up an app that requires root (titanium backup) and it says it wasn't able to attain root?
edit: confirmed with root checker that i still don't have root
Tairen said:
hmm did everything on your post, and rebooted. already had SU so i just opened up an app that requires root (titanium backup) and it says it wasn't able to attain root?
edit: confirmed with root checker that i still don't have root
Click to expand...
Click to collapse
Try re-installing superuser? When I was rooted before, sometimes superuser wouldn't prompt me for SU on occasion too.
se1000 said:
Try re-installing superuser? When I was rooted before, sometimes superuser wouldn't prompt me for SU on occasion too.
Click to expand...
Click to collapse
ahh i see the problem..
cat /data/local/su > /system/xbin/su
sh: cannot create /system/xbin/su: Read-only file system
how do i proceed?
Tairen said:
ahh i see the problem..
cat /data/local/su > /system/xbin/su
sh: cannot create /system/xbin/su: Read-only file system
how do i proceed?
Click to expand...
Click to collapse
Looks like something went wrong on the first mempodroid command. Go back and start from the begining just in case. Shouldn't hurt anything.
se1000 said:
Looks like something went wrong on the first mempodroid command. Go back and start from the begining just in case. Shouldn't hurt anything.
Click to expand...
Click to collapse
Sounds good, will try again and update!
This worked on my prime which appeared to have a partial root after upgrading with the OTA update, i was able to restore full root by running a few commands.
View: Root Transformer Prime After Jellybean 4.1.1 Update
For the experinced users its just a case of running a few commands
adb push su /data/local/tmp/
adb push Superuser.apk /data/local/tmp/
adb push busybox /data/local/tmp/
adb shell
chmod 6755 /data/local/tmp/su
chmod 755 /data/local/tmp/busybox
chmod 644 /data/local/tmp/Superuser.apk
sysrw
cp /data/local/tmp/su /system/bin
cp /data/local/tmp/busybox /system/bin
cp /data/local/tmp/su /system/xbin
cp /data/local/tmp/busybox /system/xbin
cp /data/local/tmp/Superuser.apk /system/app/
reboot
InsaneNutter said:
This worked on my prime which appeared to have a partial root after upgrading with the OTA update, i was able to restore full root by running a few commands.
View: Root Transformer Prime After Jellybean 4.1.1 Update
For the experinced users its just a case of running a few commands
adb push su /data/local/tmp/
adb push Superuser.apk /data/local/tmp/
adb push busybox /data/local/tmp/
adb shell
chmod 6755 /data/local/tmp/su
chmod 755 /data/local/tmp/busybox
chmod 644 /data/local/tmp/Superuser.apk
sysrw
cp /data/local/tmp/su /system/bin
cp /data/local/tmp/busybox /system/bin
cp /data/local/tmp/su /system/xbin
cp /data/local/tmp/busybox /system/xbin
cp /data/local/tmp/Superuser.apk /system/app/
reboot
Click to expand...
Click to collapse
Did you use OTA rootkeeper to get that partial root or did you just blindly upgrade to jelly bean from rooted ics?
Yuhfhrh said:
Did you use OTA rootkeeper to get that partial root or did you just blindly upgrade to jelly bean from rooted ics?
Click to expand...
Click to collapse
I had my root backup from OTA rootkeeper which i tried to restore, and didnt get anywhere with. I then followed the instructions there and got root perfectly.
If you were not rooted before upgrading then i dont believe it will be any good for you.
Did about the same, worked for me
Upgraded with the manual upgrade (http://forum.xda-developers.com/showthread.php?t=1909820) because OTA failed, protected root with OTA rootkeeper. After update i only had partial root but i could put the important files back to where they belong, after all i could still move/copy/rename files everywhere.
I used rootkeeper but it wouldnt offer to restore root after OTA upgrade. In ADB I can't copy so /system/bin I get "read only" message. I want but if I type SU root and hit enter superuser log shows "Shell .... Allowed" Is that a good sign?
I was able to use adb install for busybox.apk and it said success. I just can't seem to move SU ?!
Oh, after I couldnt keep root I thought (mistakenly) that the stock rom I had dowloaded from ASUS would be able to be applied. Put it on the SD card, got the triangle for upgrade in the bottom right corner. Tapped on it, it said upgrade available on SD. I tapped "OK" then it went on to say it was a downgrade and I tapped "ok". Then it said it was going to wipe and I tapped "OK" All that it did was wipe =/ All of the above about the SU log and installing busybox has come after a wipe.
hx4700 Killer said:
I used rootkeeper but it wouldnt offer to restore root after OTA upgrade. In ADB I can't copy so /system/bin I get "read only" message. I want but if I type SU root and hit enter superuser log shows "Shell .... Allowed" Is that a good sign?
I was able to use adb install for busybox.apk and it said success. I just can't seem to move SU ?!
Oh, after I couldnt keep root I thought (mistakenly) that the stock rom I had dowloaded from ASUS would be able to be applied. Put it on the SD card, got the triangle for upgrade in the bottom right corner. Tapped on it, it said upgrade available on SD. I tapped "OK" then it went on to say it was a downgrade and I tapped "ok". Then it said it was going to wipe and I tapped "OK" All that it did was wipe =/ All of the above about the SU log and installing busybox has come after a wipe.
Click to expand...
Click to collapse
I think your root is still good. You check with the RootExploer or ES Explorer that will show you how to access or modify files in /system partition.
InsaneNutter said:
This worked on my prime which appeared to have a partial root after upgrading with the OTA update, i was able to restore full root by running a few commands.
View: Root Transformer Prime After Jellybean 4.1.1 Update
For the experinced users its just a case of running a few commands
adb push su /data/local/tmp/
adb push Superuser.apk /data/local/tmp/
adb push busybox /data/local/tmp/
adb shell
chmod 6755 /data/local/tmp/su
chmod 755 /data/local/tmp/busybox
chmod 644 /data/local/tmp/Superuser.apk
sysrw
cp /data/local/tmp/su /system/bin
cp /data/local/tmp/busybox /system/bin
cp /data/local/tmp/su /system/xbin
cp /data/local/tmp/busybox /system/xbin
cp /data/local/tmp/Superuser.apk /system/app/
reboot
Click to expand...
Click to collapse
I was fine until I reached sysrw. I substituted sysrw with mount -o remount,rw '' /system as such:
adb push su /data/local/tmp/
adb push Superuser.apk /data/local/tmp/
adb push busybox /data/local/tmp/
adb shell
chmod 6755 /data/local/tmp/su
chmod 755 /data/local/tmp/busybox
chmod 644 /data/local/tmp/Superuser.apk
mount -o remount,rw '' /system
cp /data/local/tmp/su /system/bin
cp /data/local/tmp/busybox /system/bin
cp /data/local/tmp/su /system/xbin
cp /data/local/tmp/busybox /system/xbin
cp /data/local/tmp/Superuser.apk /system/app/
reboot
Also, remember if you had to wipe your data like I had to in order to fix an issue with the upgrade when you select the Developer options from the Settings menu you need to turn them on. There is an off button found on the top right hand corner of the screen. You can press it to toggle the Developer settings on.
Butch1326 said:
I was fine until I reached sysrw. I substituted sysrw with mount -o remount,rw '' /system as such:
adb push su /data/local/tmp/
adb push Superuser.apk /data/local/tmp/
adb push busybox /data/local/tmp/
adb shell
chmod 6755 /data/local/tmp/su
chmod 755 /data/local/tmp/busybox
chmod 644 /data/local/tmp/Superuser.apk
mount -o remount,rw '' /system
cp /data/local/tmp/su /system/bin
cp /data/local/tmp/busybox /system/bin
cp /data/local/tmp/su /system/xbin
cp /data/local/tmp/busybox /system/xbin
cp /data/local/tmp/Superuser.apk /system/app/
reboot
Also, remember if you had to wipe your data like I had to in order to fix an issue with the upgrade when you select the Developer options from the Settings menu you need to turn them on. There is an off button found on the top right hand corner of the screen. You can press it to toggle the Developer settings on.
Click to expand...
Click to collapse
I couldnt use sysrw either, it said not found. I copied your mount command and it didnt work. What looks like a regular double quote copies as two single quotes, which is it? If I use a double quote it doesnt throw an error and the prompt turns to > in the shell.
Doesnt seem to work for me either way =/
This is what I get on your mount command:
mount -o remount,rw '' /system
mount: Operation not permitted
Ok so doubting I actually have root in ADB When I type SU and hit enter this is what I get:
1|[email protected]:/ $
Not #
The normal prompt is like above without the 1| at the start.
Previously I can change R/W in the Root Explorer and type su with '#' in terminal.
After applying this method, I lost the su in both...
In Superuser, I still see the app list there. Any hints to fix it?
I had exactly the same problem and found the solution here : http://forum.xda-developers.com/showthread.php?t=1911261
After I root my Asus Prime and restore it to factory setting,my Asus got problem to log in.I send it to Asus service centre and the technician said that my Asus cannot be use anymore due to software missing cause by root.The motherboard need to replace new.Is it true?
Tech is either ignorant or trying to squeeze ya for money. Root removes no software and even if it did their standard repair procedures would restore it. I'd be surprised if a factory reset didn't do the trick in fact.
Sent from my Transformer Prime TF201 using XDA Premium App
Hello guys, I think this is my first thread ever and I would like to ask someone in the know to help me (and probably a lot others) to obtain root on my device which is the Sharp Aquos Zeta SH-02E.
After reading lots and lots of forums in Japanese (which I barely started learning) I found a couple of commands and files to obtain root on the device. Reading it looks simple. However my expertise on the area is no more than 0.
I replied on a dead post with that code and after waiting almost two months I decided to create this thread.
The code goes like this
adb push sh02eunlock /data/rootkit
adb push acdbwritevalue /data/rootkit
adb push su /data/rootkit
adb shell chmod 777 /data/rootkit/
adb shell chmod 777 /data/rootkit/sh02eunlock
adb shell chmod 777 /data/rootkit/acdbwritevalue
adb shell chmod 777 /data/rootkit/su
adb shell
su
cd /data/rootkit/
./acdbwritevalue 0xc0e74998 0x80200000
./acdbwritevalue 0xc0e749a8 0x01000000
./sh02eunlock 0
cat /data/rootkit/su >cat /data/rootkit/su > /system/xbin/su
mount -o rw,remount /system /system
cat /data/rootkit/su > /system/xbin/su
chown root.root /system/xbin/su
chmod 06755 /system/xbin/su
cat /data/rootkit/sh02eunlock > /system/xbin/soff
chmod 755 /system/xbin/soff
mount -o ro,remount /system /system
chmod 755 /system/xbin/soff
sync;sync;sync
The file is available at the bottom. That's all I got. I really need to delete all this spy/statistics apps from the phone and without root it's impossible.
Thanks in advance.
I don't know if bumping = ban but I will take the risk.
Wow! It's really painful to have so many functions on this phone and not be able to use them because I'm not using a specific company's sim card. Without root, I am not even able to use the FM functions.
Fot the love of cheesecake (or chocolate cake, whatever is your favorite), help me out with this. I won't bother anymore after this reply. Thanks.
Hey guy
see this forum ttp://desktop2ch.tv/smartphone/1374753134/
number 136 :good:
Got root, then su binary installed need some help backtracking a few things. If someone is up for it?
I guess the first thing first is. The first time I adb shell'd I got promted with root user: ( does this happen right off the bat for anyone else? I did a few things before this with modstrings and busybox. But, didn't try adb till after)
Code:
adb shell
[email protected]:/ #
Once I noticed I had root on shell I simply found the system mount at /dev/ubui0_0 and I mounted it rw.
Code:
[email protected]:/ # mount -o remount, /dev/ubi0_0
moved the su binary over to the sdcard. wrote it to system/xbin link named to /system/bin. gave permisions.
Code:
adb push su /sdcard/
[email protected]:/ # cat /sdcard/su > /system/xbin/su
[email protected]:/ # ln -s /system/xbin/su
[email protected]:/ # chmod 6755 /system/xbin/su
[email protected]:/ # su
[email protected]:/ # :D
Off I went. I need to update the binary, but as of right now Superuser shows root as 'allow', SuperSU deny (think it old binary).
If you guys are not getting root after adb shell on this device, I think I can backtrack the modstrings and other stuff I did.
I really don't know where this device sits on getting rooted. It seems like some windows programs did it before an update that happened at some point, but not anymore? I don't have access to windows so I don't keep up with those methods.
Thanks! Hope someone can help me out.