Related
Alright, so I've used the SuperOneClick application to root my phone, which tells me was done successfully, however, I don't seem to be able to access files in the system folder through adb.
Is there some way I can positively confirm whether my phone is or isn't actually rooted? Like I said I was using adb to push a file into the system folder, and was given a permission denied message. At this time the only thing I'm attempting to do to the phone is this:
/showthread.php?t=820749&page=3
It seems pretty basic and it's my first android phone, so I'm starting off small here..
Using the leaked 2.2 FW, other than the being rooted (attempted), the phone is stock 2.2..
cryo.burned said:
Alright, so I've used the SuperOneClick application to root my phone, which tells me was done successfully, however, I don't seem to be able to access files in the system folder through adb.
Is there some way I can positively confirm whether my phone is or isn't actually rooted? Like I said I was using adb to push a file into the system folder, and was given a permission denied message. At this time the only thing I'm attempting to do to the phone is this:
/showthread.php?t=820749&page=3
It seems pretty basic and it's my first android phone, so I'm starting off small here..
Using the leaked 2.2 FW, other than the being rooted (attempted), the phone is stock 2.2..
Click to expand...
Click to collapse
Do you have the "superuser" app on your phone?
cryo.burned said:
Alright, so I've used the SuperOneClick application to root my phone, which tells me was done successfully, however, I don't seem to be able to access files in the system folder through adb.
Is there some way I can positively confirm whether my phone is or isn't actually rooted? Like I said I was using adb to push a file into the system folder, and was given a permission denied message. At this time the only thing I'm attempting to do to the phone is this:
/showthread.php?t=820749&page=3
It seems pretty basic and it's my first android phone, so I'm starting off small here..
Using the leaked 2.2 FW, other than the being rooted (attempted), the phone is stock 2.2..
Click to expand...
Click to collapse
If you type:
adb shell
su (after hitting enter, you should get a popup on your phone asking for superuser permission, click allow)
If you see this:
C:\Users\*yournamehere*>adb shell
$ su
su
#
Then you have root permissions.
TheRomero09 said:
Do you have the "superuser" app on your phone?
Click to expand...
Click to collapse
Yes, I have it on my phone
miztaken1312 said:
If you type:
adb shell
su (after hitting enter, you should get a popup on your phone asking for superuser permission, click allow)
If you see this:
C:\Users\*yournamehere*>adb shell
$ su
su
#
Then you have root permissions.
Click to expand...
Click to collapse
I have the app on my phone, but when I try this, I do not get a prompt for super user permissions, and the CL shell returns permission denied
EDIT: I was going to look at the superuser app to see what was in it to give you more info, but it the "app" that I assume is actually my computer had denied permissions. After changing it back to allow, the shell returns
Code:
su
#
Psneuter exploit is working on IS, but because /system is locked on s-on phones, we can't copy su and superuser.apk into /system, apps required root access can't work.
The following procedure uses psenuter exploit to gain adb shell root, and then copy su (without privilege control ) and busybox into /sbin (which is on rootfs and in the global PATH list) to gain root access for apps.
The procedure:
1. Unzip the attached .zip into a directory (like c:\adb)
2. Open a command prompt and cd to the directory where you extracted the .zip (like cd \adb)
3. run pushroot.bat (simply type pushroot)
4. adb shell /data/local/tmp/getroot
5. adb shell
6. you are now in # prompt. Type /data/local/tmp/pushroot
You have to redo steps 4,5,6 once you reboot your phone.
The procedure will have all apps gaining root access.
!!USE ON YOUR OWN RISK!!
Known working programs: Root explorer, Titanium backup, gscript lite, trasproxy 2.04, ...
Some apps check existence of su in /system/xbin , and reject to proceed if the su binary is not exist (like transproxy 3.08). For this kind of apps, this procedure won't help.
Nice but old news mate...
Sent from my HTC Incredible S using XDA Premium App
Good job...thanks
Thanks for writing this up, might quell the thirst for S-OFF a little longer
/system/ is writeable btw, if you remount it, but after reboot everything u done will be changed to the way it were before.
so a temp root in xbin is possible also, only it will be gone afterwards (atleast i never tried this, but should work also...)
Yes. /system could be remount in rw with root. However, the files you wrote will be gone after you remount ro, and then you won't be able to copy the same filename into the same location again before next reboot ( I don't know why, actually!!). This is why I put su in sbin instead of /system/xbin.
thanks to your files 非常感谢你的工作。
Does anyone know whether steps 4, 5 and 6 can be run from the device itself?
Can I put these commands into some sort of script and run it everytime I need temp root or would I need to do this from a computer every time?
faf said:
Does anyone know whether steps 4, 5 and 6 can be run from the device itself?
Can I put these commands into some sort of script and run it everytime I need temp root or would I need to do this from a computer every time?
Click to expand...
Click to collapse
I believe you can do it from a terminal emulator but haven't got the chance to try it myself though.
Sent from my HTC Incredible S using Tapatalk
pushroot error
c:/adb>adb shell ln /data/local/tem/busybox /data/local/tmp/cp
Link failed File exists
and
c:/adb>adb shell /data/local/tmp/getroot
mmap<> failed. operation not permitted
Why??THX....
itandy said:
I believe you can do it from a terminal emulator but haven't got the chance to try it myself though.
Sent from my HTC Incredible S using Tapatalk
Click to expand...
Click to collapse
Definitely, this is the way to go.
Unfortunately, the root exploit I know could run on device itself, including
rageagainstthecage (ratc) and local root exploit (hotplug) both failed on IS.
The solution will be nearly perfect if we can get temp root on IS without a computer link.
Any input will be welcome.
sky1212 said:
pushroot error
c:/adb>adb shell ln /data/local/tem/busybox /data/local/tmp/cp
Link failed File exists
and
c:/adb>adb shell /data/local/tmp/getroot
mmap<> failed. operation not permitted
Why??THX....
Click to expand...
Click to collapse
Please then type adb shell.
If you see # but not $, do
cd /data/local/tmp
rm ./cp
ln busybox cp
./pushroot
Then you finished the install.
If you see $, please do all over again.
You can also add ShootMe (screen capture app) and SetCPU to the list of working apps. SetCPU will only allow you underclock for now due to the kernel, but it is a nice touch if you are worried about battery life. Adfree doesn't appear to work
l0st.prophet said:
You can also add ShootMe (screen capture app) and SetCPU to the list of working apps. SetCPU will only allow you underclock for now due to the kernel, but it is a nice touch if you are worried about battery life. Adfree doesn't appear to work
Click to expand...
Click to collapse
Adfree is working for me. Are you getting some type of error message?
MetaMorph, screenshot and MyBackup Root are also working.
I had to mount system, then push su to /system/xbin. Then install BusyBox Installer from Market.
No erro, still got the ads. I've tried rebooting & rerooting, still no luck
l0st.prophet said:
No erro, still got the ads. I've tried rebooting & rerooting, still no luck
Click to expand...
Click to collapse
What site/app are you going to so I can see if I get the ads.
the anti-ads actually tries to modify the current host file... which is not allowed in your state as far as i know
what you can do is replace it by pushin it to the right spot
but after reboot gone,but sure u know
Adfee is working for me, you can also add Droidwall.
@eddycyf, did you test adfree with apps? Since it aint working for prophet...
Sent from my HTC Incredible S using XDA Premium App
Mhm AdFree isnt working for me. The App states that everything is okay, and that my hosts file is up to date, but I see ads everywhere.
But I am kinda happy now, because i can use Titanium Backup
Originally posted by Stetsonaw at androidforums...
Please be aware that I did not write these instructions. I only posted them. Stetsonaw wrote these instructions. While comfortable in ADB and have rooted my phone many times in testing as well as rolled back the versions etc... I have no more insight into how or why it is not working for you. If you followed the directions exactly on a version 4 phone, this should work no problem.
Haxcid
Links to the necessary files are listed at the bottom.
Remember, I am not at fault if you brick your phone, now, proceed.
Connect your phone in charge only mode to install the LG Bootstrapper and drivers, or grab the LG Universal Drivers.
Change your USB Mode to Internet Connection
Go into Settings/Applications/Development and ensure USB Debugging is turned on
If all goes according to plan, you should see the ADB Ladybug icon in your notification bar
I updated the Rootzwiki page with the same info found below.
Busybox actually comes installed by LG on the Revo, how awesome is that??
Download the rageagainstthecage binary
Download the SU binary
Move these files to the same directory your adb.exe is in.
Code:
The > and # characters below illustrate the prompt
you should have, if you have the $ when you go into adb shell,
exit out and type 'adb usb' then go back into adb shell and
you should see the #
Open Command prompt (either use the Windows Key+R and type cmd or start/run, then type cmd)
32-bit users: >cd c:\program files\android\android-sdk\platform-tools
64-bit users: >cd c:\program files (x86)\android\android-sdk\platform-tools
Or >cd (whatever directory adb is in)
>adb devices (verifies you are connected)
>adb push rageagainstthecage-arm5.bin /data/local/temp/rage
(if the above command fails due to read-only, type 'adb usb' then 'adb root' to validate root status, then 'adb devices' again to verify connection)
>adb push su /data/local/temp/su
>adb shell chmod 777 /data/local/temp/rage
>adb shell ./data/local/temp/rage
>adb shell (If this gives you a $ prompt instead of a # prompt, type 'su', if that fails, 'exit', 'adb usb' like above.)
#mount -o remount,rw -t ext3 /dev/mmcblk0p12 /system
#busybox cp /data/local/temp/su /system/bin/su
#chmod 6755 /system/bin/su
Verify the file is in place w/correct permissions
#cd /system/bin
#ls -l *su
After the ls command you should see the following returned by the system:
-rwsr-sr-x root root 26248 2011-05-29 01:09 su
At this point, you may way to remove the files you put in /data/local/temp (optional):
#rm /data/local/temp/su
#rm /data/local/temp/rage
continue with commands
#reboot
Download and install SuperUser from the Market
Thanks Zennmaster, _mrbirdman_ for finding the linux routes and birdman for helping me out, and droidx8971 for helping me find all the information possible!
http://wikifilez.com/Root Files/revolution/rageagainstthecage-arm5.bin
http://wikifilez.com/Root Files/revolution/su
https://market.android.com/details?id=com.noshufou.android.su&feature=search_result
http://www.lg.com/us/support/mc-support/drivers/LGAndroidDriver_Ver_1.0_All.exe
Just a note for some. The rageagainstthecage bin file may be detected as a virus/trojan. It is not. You may want to disable your antivirus before downloading the .bin file.
I run avira on my desktop and it caught the file as a virus everytime I downloaded it and then deleted it. Avast on my laptop however did not.
Root is simple if you follow the instructions. You need to make sure that adb recognizes your device. Takes 5 minutes to complete, took me longer to install adb again and update it.
Any reason to not use the one click method? Seems to be working
bwhxeon said:
Any reason to not use the one click method? Seems to be working
Click to expand...
Click to collapse
No idea. I have not used the one click. Create a thread for it. I posted what I know which is adb.
Successfully Rooted
with RootzWiki instructions for Windows, needed the remount and busybox lines to overcome the permission denied when pushing su.
Hey guys, either using S1C or ADB Commands, have we found out if it's possible to unroot this as long as you Nand Backup the stock rom then unroot from there yet? Just because I got this phone as a filler/4g unl. lock and got buyback on it from best buy so I could buy a dual/quad later on when they come out .
MXFrodo195 said:
Hey guys, either using S1C or ADB Commands, have we found out if it's possible to unroot this as long as you Nand Backup the stock rom then unroot from there yet? Just because I got this phone as a filler/4g unl. lock and got buyback on it from best buy so I could buy a dual/quad later on when they come out .
Click to expand...
Click to collapse
Doing a factory reset I believe will unroot you. There is no nand back up at this time. We are waiting for a recovery mod.
Haxcid said:
Doing a factory reset I believe will unroot you. There is no nand back up at this time. We are waiting for a recovery mod.
Click to expand...
Click to collapse
Oh ya I know, I just always keep a stock one, on the Inc if you factory reset from an AOSP rom, you'd bootloop, so you had to make sure you were on a Sense 1.0 or stock rom(from my experience), so I was just making sure it was no big deal to go back.
Any idea when we will have cw on this?
Haxcid said:
Doing a factory reset I believe will unroot you. There is no nand back up at this time. We are waiting for a recovery mod.
Click to expand...
Click to collapse
I tried the factory reset. I am still rooted.
navycow said:
I tried the factory reset. I am still rooted.
Click to expand...
Click to collapse
That's what i figured. Can anyone verify if you remove SU and Rage through adb will it unroot?
Sent from my VS910 4G using XDA Premium App
MXFrodo195 said:
That's what i figured. Can anyone verify if you remove SU and Rage through adb will it unroot?
Sent from my VS910 4G using XDA Premium App
Click to expand...
Click to collapse
If you have to return your device, simply remove the superuser app, after you unfreeze anything you may have frozen then factory reset. They honestly will never know it was rooted. The only way now that you can really tell is the super user app from market.
Just so everyone knows. SuperOneClick can root and unroot this phone ok.
navycow said:
Just so everyone knows. SuperOneClick can root and unroot this phone ok.
Click to expand...
Click to collapse
Thank you for confirming this. My revolution just came in the mail today!
Thanks for posting this here for me Haxcid!
Sent from 1885
navycow said:
Just so everyone knows. SuperOneClick can root and unroot this phone ok.
Click to expand...
Click to collapse
Cool thanks for checking. Any benefits for ADB over S1C? Can't wait to finally root and freeze half these apps. I think we need a few more twitters to praise koush for a recovery on this beast.
Sent from my VS910 4G using XDA Premium App
Is there recovery for this now? Did I miss something?
stetsonaw said:
Is there recovery for this now? Did I miss something?
Click to expand...
Click to collapse
No No, I was saying we need to praise Koush's good work so he will make one faster .
And Stetsonaw, any idea if I root through ADB, can I unroot with S1C, since it uses the same idea.
S1C for whatever reason will not run(tried three computers, a XP, Vista, and Win7 lol), it keeps freezing at the same spot, everytime.
Should be able to, since S1C does what the ADB method does... or you could just delete the 'su' file out of /system/bin and /system/xbin (if it's there) to unroot.
EDIT: I couldn't get S1C to open on my desktop, and my laptop, which would open the program, would bluescreen when i connected the phone, so i had no choice but to do it the ADB way.
stetsonaw said:
Should be able to, since S1C does what the ADB method does... or you could just delete the 'su' file out of /system/bin and /system/xbin (if it's there) to unroot.
EDIT: I couldn't get S1C to open on my desktop, and my laptop, which would open the program, would bluescreen when i connected the phone, so i had no choice but to do it the ADB way.
Click to expand...
Click to collapse
Hmmm, ya now my computer for whatever reason won't open up ADB through command. This is getting irritating lol. Should be nice and simple, but it just won't go through. If I downloaded the SDK Manager like 4 months ago, it shouldn't matter, correct?
make sure you change directory to wherever your adb.exe is located... as in:
Code:
cd C:\Program Files\Android\android-sdk-windows\platform-tools
Ok so here it is almost day 2 trying to install CWM on zv8 after using "mt's easiest way to keep root thru zv8'. (Oh and by the way MT your the MAN). Now getting to zv8 was easy, But getting the recovery installed is another issue all together. First started with the AIO bat. file which installs cwm (kudos to MT and djrbliss). And it reads
"system cannot find the path specified'.
SO ok well apparently the computer isnt reading the phone found out the driver has issue shows the error message(on both my laptops).
ok lets try the terminal emulator with
brad6360 said:
1) Download the cwmrecovery.img to your SD. ( I downloaded MT's zip file and then extracted all with root explorer, but you only need the cwmrecovery.img file.)
2) Use root explorer to copy or move it to the /data/local/tmp directory (make sure permissions are set to r/w/exe).
3) Launch terminal emulator and type these commands:
su
mount -orw,remount /dev/block/system /system
mount -orw,remount /dev/block/data /data
dd if=/data/local/tmp/cwmrecovery.img of=/dev/block/mmcblk0p14 bs=4096
rm /data/local/tmp/* 2>/dev/null
4) exit terminal emulator and then reboot.
You can then try the vol down+power button combo upon boot to enter CWM.
Good luck.
Click to expand...
Click to collapse
didn't work and I the local.prop file in the data folder.
Someone PLEASE HELP!!!
(not a noob or expert but I can read and follow directions lol)
Are you sure you still have root level access?
Does adb detect your phone at all?
Still have root access I used root explorer to add the local.prop.
Adb recognizes my phone it shows a serial number under adb devices
Is there a way I can flash cwm in adb?
Sent from my VS910 4G using XDA
Use the newest aio from Mt. It worked for me. The simplest way is to flash the v7.tot then 'JUST' root, create the local.prop file, then ota to v8. Then continue on with Mt's aio to install cwm. Don't worry about having complete root access (cuz I didn't, but had cwm). Flashed broken out and haven't looked back.
--My REVO is Broken, tweaked, SC'd, and TB'd. Just awesome!
Thats where I'm stuck. I'm on zv8, using mt's easiest AIO to update from zv7. The AIO for cwm isn't installing nor through the terminal emulator. Any other suggestions?
Sent from my VS910 4G using XDA
What happens when you go into recovery? Is it the stock recovery? Stock v8 didn't have the option to boot into recovery. Just a thought. When I did it I got a lot of errors, but it took.
--My REVO is Broken, tweaked, SC'd, and TB'd. Just awesome!
mrand1 said:
Thats where I'm stuck. I'm on zv8, using mt's easiest AIO to update from zv7. The AIO for cwm isn't installing nor through the terminal emulator. Any other suggestions?
Sent from my VS910 4G using XDA
Click to expand...
Click to collapse
I have the same problem, Even when i Flash zv7 tot and try old AIO it says
Cannot find specified path
and i am not a noob and have broken out an old revo with mt's help but this new one with pre loaded zv8...No luck yet
had to manually push
I'm glad that I'm not the only one having this issue
Can you use Root Explorer to check and make sure adb is pushing the image file to your phone? Look in this directory: /data/local/tmp/cwmrecovery.img
You could always do this manually using adb. Here's how.
1. Open the ZV8CWMRecovery folder on your PC.
2. Double click the 'Files' folder to go into that directory.
3. Highlight/select and copy the address of your current folder location on your PC. It will look something like this:
Code:
C:\Documents and Settings\username\My Documents\Downloads\ZV8CWMRecovery\Files
4. Click Start>Run>type 'cmd' and hit enter/return to open your command prompt.
5. Type 'cd', hit your spacebar, then paste your address which you copied in step 3 into your command prompt, hit enter/return.
6. You should now be positioned in the folder containing the adb and CWMRecovery files.
7. Type the following to copy the CWMRecovery image to your phone:
Code:
adb devices
adb remount
adb push cwmrecovery.img /data/local/tmp/cwmrecovery.img
adb shell dd if=/data/local/tmp/cwmrecovery.img of=/dev/block/mmcblk0p14 bs=4096
adb shell "rm /data/local/tmp/* 2>/dev/null"
adb shell rm /system/etc/install-recovery.sh
adb shell rm /system/recovery-from-boot.p
adb shell rm /data/local.prop
adb reboot
Phone should reboot. Try and boot into CWMRecovery after it reboots.
idk if I'm not doing something right or wrong. I have usb debugging and internet connection, and I'm getting "remount failed: operation not permitted".
I had the same issue but following these instructions helped me, what finally helped me was typing a wrong command wich gave me a help menu with all the commands, the important one being "adb reboot [Recovery:Bootlaoder]"
adb reboot recovery did the trick, then wiped flashed broken out and sooo happy to be done with it.
after pushing CWM in command prompt of course
I'm also getting "remount failed: operation not permitted" when trying adb remount in the command prompt just as mrand1 apparently did.
I (perhaps noobishly) skipped that step and did adb push cwmrecovery.img /data/local/tmp/cwmrecovery.img but after trying the next step got cannot open for write: Permission denied.
I'm trying to get back to Broken Out 1.1 - when it first came out I successfully downgraded to zv7 by flashing the .tot and then doing the OTA update, but now when I try to do that I can't seem to get the OTA to start downloading. I flashed zv8 tot in order to test the latest root method (which works) I just can't get CWM on there now - I don't seem to have any recovery at all actually. Any help would be appreciated.
slimzim said:
I'm also getting "remount failed: operation not permitted" when trying adb remount in the command prompt just as mrand1 apparently did.
I (perhaps noobishly) skipped that step and did adb push cwmrecovery.img /data/local/tmp/cwmrecovery.img but after trying the next step got cannot open for write: Permission denied.
I'm trying to get back to Broken Out 1.1 - when it first came out I successfully downgraded to zv7 by flashing the .tot and then doing the OTA update, but now when I try to do that I can't seem to get the OTA to start downloading. I flashed zv8 tot in order to test the latest root method (which works) I just can't get CWM on there now - I don't seem to have any recovery at all actually. Any help would be appreciated.
Click to expand...
Click to collapse
I did the same thing, flashed to zv8 tot, was able to root but was unable to flash cwm recovery. I tried manually doing it and running MT's AIO. It's telling me permission denied on all of the steps except the push cwmrecovery.img. It appears I do not have any recovery either. Trying to get to Broken Out! Any help is appreciated, thanks guys!
asauber said:
I tried ... running MT's AIO. It's telling me permission denied on all of the steps except the push cwmrecovery.img.
Click to expand...
Click to collapse
For what it's worth I also tried that with the same results.
I finally got this to work much more easily thanks to a quick talk with mtmichaelson. Here's the method:
1) Get to ZV8 (I got there via LGNPST)
2) Root using the tool found here: http://forum.xda-developers.com/showthread.php?t=1621625
3) Open a Terminal Emulator
4) Type: su
5) Hit enter
6) Type: echo 'ro.kernel.qemu=1' > /data/local.prop
7) Press enter
8) Reboot
9) Use the ZV8CWMRecovery.bat found here: http://forum.xda-developers.com/showthread.php?t=1583023
Good luck!
slimzim said:
I finally got this to work much more easily thanks to a quick talk with mtmichaelson. Here's the method:
1) Get to ZV8 (I got there via LGNPST)
2) Root using the tool found here: http://forum.xda-developers.com/showthread.php?t=1621625
3) Open a Terminal Emulator
4) Type: su
5) Hit enter
6) Type: echo 'ro.kernel.qemu=1' > /data/local.prop
7) Press enter
8) Reboot
9) Use the ZV8CWMRecovery.bat found here: http://forum.xda-developers.com/showthread.php?t=1583023
Good luck!
Click to expand...
Click to collapse
Man, that was too easy!
Thanks for posting this slimzim. This worked straight away for me, I'm installing Broken Out as I type! I'm actually a little glad this happened because now I'm a little more familiar with terminal emulator and what local.prop does. Never had to use it in the past. This is exactly the second phone I've ever rooted and am usually able to just use AIOs.
And of course, thanks to mtmichaelson for chatting with you about it and doing all the hard work in the first place!
slimzim said:
I finally got this to work much more easily thanks to a quick talk with mtmichaelson. Here's the method:
1) Get to ZV8 (I got there via LGNPST)
2) Root using the tool found here: http://forum.xda-developers.com/showthread.php?t=1621625
3) Open a Terminal Emulator
4) Type: su
5) Hit enter
6) Type: echo 'ro.kernel.qemu=1' > /data/local.prop
7) Press enter
8) Reboot
9) Use the ZV8CWMRecovery.bat found here: http://forum.xda-developers.com/showthread.php?t=1583023
Good luck!
Click to expand...
Click to collapse
So far not working...repeating process now...
da_morales said:
So far not working...repeating process now...
Click to expand...
Click to collapse
If you've done all steps exactly it should work. I went through a ton of other "fixes" that didn't work, I believe the key here is when you use the terminal emulator directly on the phone to create local.prop. I was trying to create local.prop in every way but that, and until I did it directly on the phone did I have success.
Good luck!
local.prop missing
I used the Easy ZV8 All in One Rooting Tool, and have no sound at all like a couple of other users. One of the suggestions was to rename the local.prop file in the /data folder to local.prop.bak.
I assume this is the /data folder in the internal folder? When I did the steps for the all in one rooting tool (coming from rooted zv7), there is no local.prop file in my /data folder to rename, yet I still have no audio for ringtones, phone calls, etc. except for the boot up sound on the splash page.
Any ideas why my local.prop file isn't even there? I even tried copying the one from the mtmichelson zip file into there, still no avail. Thanks!
I have the same issue. I used the echo command in term emulator and the local.prop file was there. rebooted and the file is gone. I have root but cannot install cw recovery. I have tried AIO, adb, and terminal emulator but nothing makes it stick. Any help would be greatly appreciated
Rob
Update:
Holy crap, I just thought of something like, way stupid simple.
Just update Su before updating to 4.1. Then simply use OTA Rootkeeper like normal.
Again, I sincerely apologize for not realizing this sooner, and wasting a lot of time.
I guess I'll keep this guide here for people who forgot to update su before updating. Sorry guys.
---------------------------------------------------------------------------------------------------------------------
You might want to read this all the way through, THEN do the steps. Good Luck.
Remember to have Unknown Sources enabled.
First off, you're going to need to start off with ICS, rooted. Thats a pretty straight forward process, and can be accomplished totally with the AHD Utility (Here). Go ahead and install OTA Root keeper, we're going to need that.
After Root Keeper is installed, locate it with your favorite file manager, I prefer Root Explorer, but anything that can mount with r/w is great. It's going to be in /data/app. Copy the APK to /system/app and install it. Do this exact same thing with your file manager's APK. This way, they wont be uninstalled when we update to 4.1.
Run OTA Rootkeeper. Backup Su, and temp unroot. From here, you can upgrade to 4.1 without losing your essentials by using stock recovery to flash the 4.1 zip.
So that's finished, you're now in Jelly Bean and you decide not to read the rest of this because you think "oh i know where this is going, I flashed roms back on the atrix 4G all the time, im a PRO at this phone stuff" and you've restored root with Rootkeeper, and you're like "wat the heck, i dont have root, lying tutorial". Have no fear, we're not done yet.
In JB, open Rootkeeper and restore root from backup.
Now go update the Superuser app from Google Play (Anyone else ever call it Market still?)
Ok, almost done. If you were to go in to Superuser and update the binary, it would not work (I don't have an explanation for why, it just says Root failed. Probably since we're not actually rooted (but we have su so wtf mate)) So what we're going to need to do is go download the binary here from androidsu.com.
Extract the su binary from the zip and put it on your SD card. On your phone, using that trusty File explorer from earlier, mount the fs as r/w and put su in /system/bin. Make sure permissions are all checked EXCEPT Group Write and Others write. (I don't know if it makes a difference, but I don't want to mislead you.)
Alternatively, you can use ADB. Mount the file system as r/w on the phone. Put su on the root of your hard drive, and use " adb push c:/su /system/bin "
Then it's done. Test root from adb with " adb shell su " and from the phone by using any root app, or typing "su" in terminal emulator. Or just root checker.
Thanks for making this so easy! Updated to JB without losing anything. However, I hit a snag. Everything was okay until I tried to update su.bin via ES File Explorer. I couldn't write to system/bin, and couldn't get the app to gain root access again. Now I'm stuck with no root... Can I adb the file in, or somehow write to system/bin? Or will I have to do this all over again? I just really don't want to lose any settings.
doublea70 said:
Thanks for making this so easy! Updated to JB without losing anything. However, I hit a snag. Everything was okay until I tried to update su.bin via ES File Explorer. I couldn't write to system/bin, and couldn't get the app to gain root access again. Now I'm stuck with no root... Can I adb the file in, or somehow write to system/bin? Or will I have to do this all over again? I just really don't want to lose any settings.
Click to expand...
Click to collapse
Yes. The un-updated version of Su should be enough to give ADB root, so you can use ADB to remount the filesystem with r/w, then push the new su.
For future readers who don't know:
First, navigate to ADB in the terminal of your choice (Command Prompt on Windows, Terminal on Linux/OS X. I'll be using Windows.)
Do this by typing
Code:
cd /your directory ADB is in/
In my case, it now says "C:/Users/MyName/Desktop/ADB" because I keep ADB on my desktop like a silly person.
Now, remount your filesystem in ADB with read/write access. The command is
Code:
adb shell su mount /system rw
Now, we can push that new SU binary with ease, with
Code:
adb push c:/The_Directory_you_keep_su_in/ /system/bin
In my case, It was just "adb push c:/su /system/bin" because I keep files I want to push on the root of my hard drive, like a silly person.
Now, switch system back to read only with
Code:
adb shell su mount /system ro
All done, use Superuser app to Check for updates. It should say you're up to date, and if you update anyway, it'll do it without failing.
Is there another method to this? I have this problem idk why it says I have root saved but it won't let me restore? I don't have computer access and my root keeper says I have root?
Sent from my MB886 using Tapatalk 2
Gaining root access... fail!
ripin150 said:
Update:
Holy crap, I just thought of something like, way stupid simple.
Just update Su before updating to 4.1. Then simply use OTA Rootkeeper like normal.
Again, I sincerely apologize for not realizing this sooner, and wasting a lot of time.
I guess I'll keep this guide here for people who forgot to update su before updating. Sorry guys.
---------------------------------------------------------------------------------------------------------------------
You might want to read this all the way through, THEN do the steps. Good Luck.
Remember to have Unknown Sources enabled.
First off, you're going to need to start off with ICS, rooted. Thats a pretty straight forward process, and can be accomplished totally with the AHD Utility (Here). Go ahead and install OTA Root keeper, we're going to need that.
After Root Keeper is installed, locate it with your favorite file manager, I prefer Root Explorer, but anything that can mount with r/w is great. It's going to be in /data/app. Copy the APK to /system/app and install it. Do this exact same thing with your file manager's APK. This way, they wont be uninstalled when we update to 4.1.
Run OTA Rootkeeper. Backup Su, and temp unroot. From here, you can upgrade to 4.1 without losing your essentials by using stock recovery to flash the 4.1 zip.
So that's finished, you're now in Jelly Bean and you decide not to read the rest of this because you think "oh i know where this is going, I flashed roms back on the atrix 4G all the time, im a PRO at this phone stuff" and you've restored root with Rootkeeper, and you're like "wat the heck, i dont have root, lying tutorial". Have no fear, we're not done yet.
In JB, open Rootkeeper and restore root from backup.
Now go update the Superuser app from Google Play (Anyone else ever call it Market still?)
Ok, almost done. If you were to go in to Superuser and update the binary, it would not work (I don't have an explanation for why, it just says Root failed. Probably since we're not actually rooted (but we have su so wtf mate)) So what we're going to need to do is go download the binary here from androidsu.com.
Extract the su binary from the zip and put it on your SD card. On your phone, using that trusty File explorer from earlier, mount the fs as r/w and put su in /system/bin. Make sure permissions are all checked EXCEPT Group Write and Others write. (I don't know if it makes a difference, but I don't want to mislead you.)
Alternatively, you can use ADB. Mount the file system as r/w on the phone. Put su on the root of your hard drive, and use " adb push c:/su /system/bin "
Then it's done. Test root from adb with " adb shell su " and from the phone by using any root app, or typing "su" in terminal emulator. Or just root checker.
Click to expand...
Click to collapse
After following all the steps. When i install root checker, it is telling me i don't have root.
Below is what i got back from superuser:
Su Binary Updater
Downloading Manifest... Okay!
Parsing manifest.. Okay!
Latest version = 3.1.1
Checking installed version = 3.1.1
Upacking sutools... okay!
Checking current install path.. /system/bin/su
Downloding new binary.. okay!
Gaining root access... fail!
Any idea to help?