Related
Here comes the latest rooting method that works with 2.0.2.A.0.24 firmware.
Credits to Scotty2 for his psneuter exploit!
1. Download and unpack rootme.tar.bz2
2. Execute ./rootme (linux) or rootme.bat (windows)
3. Done.
---
You may also want to try SuperOneClickv1.5.5-ShortFuse.zip (modified by batman_112 to use the latest exploit).
Cheers,
z
Stop for me at Point 4)
I got back
./ratc: Permission denied
Click to expand...
Click to collapse
after
./ratc
i get ... permission denided
Wow, actually it seems that copying files with adb push via script messes thing up I corrected the instructions, so now it will work for you, but need to copy the files manually.
zdzihu said:
Wow, actually it seems that copying files with adb push via script messes thing up I corrected the instructions, so now it will work for you, but need to copy the files manually.
Click to expand...
Click to collapse
Your link is broken
Try now, I got rid of installation scripts
EDIT: Now it works flawlessly. I still have no clue why copying files with .bat file messes everything up, but manual copying does the job.
why the superone reach the root sometimes so slow?
your method uses the same exploit, and works at first try
check the files plz: Invalid or Deleted File
can't download the ratc-pack --> Invalid or Deleted File
please reup - THX
EDIT: Link is OK now --> THX
Link is OK. Downloading at the moment.
Tried it manually (as described)...
But same problem... :-(
UserX10 said:
Tried it manually (as described)...
But same problem... :-(
Click to expand...
Click to collapse
I just reflashed my phone and it worked for me at 1st attempt.
Could you please got rid of the old files and retry from the beggining?
Cheers!
meta96 said:
after
./ratc
i get ... permission denided
Click to expand...
Click to collapse
Same thing for me
:-( Same Problem
I flashed my X10 with nordic FW and tried it again Step by Step... but "permission denied"... even if i remove and make the tmp directory as described...
Ok, last thing to try... After you copy the files, go with:
Code:
adb shell
chmod 777 /data/local/tmp/*
I added some screenshots to show how the process works for me.
is this a full root? i mean, is root+shell root?
zdzihu said:
Hi guys, I've noticed some people still can't get their phones rooted with SuperOneClick method. So do I, never managed to get it working Here is a simple method of rooting, using the same exploit (rageagainstthecage - credits to author). This is quick and 100% guaranteed to work but I'd rather recommend it to advanced users.
1. Install Android Terminal Emulator from the market http://bit.ly/9B46Nl
2. Download and unpack http://www.mediafire.com/?s0428zxc7n50i28
3. Plug in the phone (usb debugging mode), copy the following files with adb and change permissions:
Code:
adb push ratc /data/local/tmp/ratc
adb push busybox /data/local/tmp/busybox
adb push su /data/local/tmp/su
adb push rootme /data/local/tmp/rootme
adb push superuser.apk /data/local/tmp/superuser.apk
adb shell
chmod /data/local/tmp/*
4. Start Terminal Emulator on your phone and issue those commands:
Code:
cd /data/local/tmp
./ratc
5. Exit out of Terminal Emulator using BACK button.
6. Start any other application and exit out of it using BACK button.
7. Start Terminal Emulator again - note that you're running it as root (#)
8. Issue those commands:
Code:
cd /data/local/tmp
./rootme
Your phone will reboot - and it's done. I suggest installing Busybox from the Market. Hope it helps.
Cheers!
EDIT: Fixed.
Click to expand...
Click to collapse
Finally I was able to root my phone
just one correction, you got to use chmod 777 /data/local/tmp/*
it was not allowing to root otherwise
i kept breaking my head using the "simple" SuperOneCLick but could not show my rage against the machine
thank you for explaining this process for Root.
zdzihu said:
Ok, last thing to try... After you copy the files, go with:
Code:
adb shell
cd /data/local/tmp
chmod 777 *
I added some screenshots to show how the process works for me.
Click to expand...
Click to collapse
chmod 777 *
did it. thanx. btw like your oldstyle-skills
Just saw this thread and wanted to root my phone also...I downloaded the files provided in the first post and extracted onto my PC. When I tried running the adb application, I only get a command window only for a split second and then it disappears. Am I doing something wrong?
Everything works fine until the final step where I write ./rootme in the emulator.
Before the phone reboots, it says something right after, something about superuser.apk.
Once the phone is back on the emulator goes back to $. As well as not being able to download Busybox.
Appreciate your efforts
EDIT: No worries, I managed to get root using SuperOneClick (finally!). It was rather sketchy, would've preferred your way tbh.
I used up this guide to try and root my x10mini
http://forum.xda-developers.com/showthread.php?t=739874
now after some reading I passed afew problems I had while trying to push the files in to my sdcard.
now I got stock when I got to
"
cd sqlite_stmt_journals
chmod 755 exploid
chmod 755 busybox
Immediately after the next command, you will need to disable and enable the wi-fi using the power widget on the phone:
./exploid
then run:
rootshell
"
when I reached the point where I write ./exploid
it tells me "permission denied.
to note, I were able to push all the files above.
Im pretty stock. and need help! any ideas how to resolve this?
I got stuck on my stock SE recently and had hell rooting with the newest firmware. After HOURS...I discovered it was an old Busybox file which was the problem. I put in the latest busybox (on my SD or in the rooting program, maybe both) and bam! Rooted!
Try this apk as a last resort. Good luck!
if the one above still can't root your mini, try search the latest superoneclick
hi
Worked root 2.3.5 65.1.21.XT910.PSHAsiaRetail.en.03 and 65.1.21.XT910.MERetail.en.03
[Instruction]
Install USB Drivers
Extract Motofail_windows.zip Package
Enable debugging on device. Settings -> Application -> Development -> Tick USB Debugging
Connect device to PC
Test if device is recognised in command prompt using ADB Devices (Optional)
Run the Run.bat
Enjoy
Download
http://vulnfactory.org/public/motofail_windows.zip
Original link
http://vulnfactory.org/blog/2012/02/...ty-experiment/
Dan Rosenberg
It's works, on my RAZR XT910 Asia, SEAOP.
I am using GNU/Linux and this how I re-ROOT my RAZR back.
Note: Only for advanced and know what todo users. Actually this is for anyone who knows how to use adb or fastboot, either in GNU/Linux, OSX or Windows.
1) I already installed the adb and fastboot in $PATH.
2) Extract the motofail exploit
3) cd /to/motofail
4) $ adb push motofail /data/local/.
5) $ adb shell 'chmod 755 /data/local/motofail'
6) $ adb shell '/data/local/motofail exploit'
7) $ adb reboot
8) $ adb remount
9) $ adb push su /system/xbin/.
9a) $ adb shell 'chmod 4755 /system/xbin/su'
10) $ adb shell '/data/local/motofail clean; reboot'
11) Install Superuser from Market.
If you already rooted your RAZR, but had been removed by OTA, you can skip step 9) to re-ROOT your RAZR. .
Note and suggestion: DO NOT push Superuser.apk to /system/app . It is wise to INSTALL from Market or do $ adb install -r Superuser.apk. Better to remove /system/app/Superuser.apk before reinstall the Superuser.apk from Market or adb : $ adb shell 'rm /system/app/Superuser.apk'
You can remove the motofail later;
$ adb shell 'rm /data/local/motofail'
You can read run.bat to see the commands involved.
Thank you...
almstag said:
hi
Worked root 2.3.5 65.1.21.XT910.PSHAsiaRetail.en.03 and 65.1.21.XT910.MERetail.en.03
[Instruction]
Install USB Drivers
Extract Doomlords Package
Enable debugging on device. Settings -> Application -> Development -> Tick USB Debugging
Connect device to PC
Test if device is recognised in command prompt using ADB Devices (Optional)
Run the Runme.bat
Enjoy
Download
http://vulnfactory.org/public/motofail_windows.zip
Click to expand...
Click to collapse
So do I extract Doomlords' package [from other threads] or do I extract the ATTACHED package? Namely, Motofail_windows.zip.
Edit: Turns out that the "Doomlord's Package" in the instructions was for the attached pacakge. I've successfully rooted my XT910 that's on 65.1.21.XT910.PSHAsiaRetail.en.03
I'm sorry
Thank you
Worked on 65.1.21.xt910.optus.en.au
Thankyou!
I want the Fastboot file for the Asian model of Razr XT910. Can any1 link me?
manish.sanil said:
I want the Fastboot file for the Asian model of Razr XT910. Can any1 link me?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1362956
Just look for your device's ROM at this thread.
hugothebas said:
http://forum.xda-developers.com/showthread.php?t=1362956
Just look for your device's ROM at this thread.
Click to expand...
Click to collapse
Is it just me or is it just that 65.1.21.XT910.PSHAsiaRetail.en.03 isn't on that thread?
Sim Kai Long said:
Is it just me or is it just that 65.1.21.XT910.PSHAsiaRetail.en.03 isn't on that thread?
Click to expand...
Click to collapse
No, there's no fastboot file for 65.1.21.XT910.PSHAsiaRetail.en.03. But you can go there by OTA Update via Moto Recovery
Do I just need to extract the motofail and run .bat file on my razr which is on new ota?
Sent from my XT910 using xda premium
Sedariya11 said:
Do I just need to extract the motofail and run .bat file on my razr which is on new ota?
Sent from my XT910 using xda premium
Click to expand...
Click to collapse
Extract motofail_windows.zip to a folder anywhere on your computer, on your desktop perhaps?
Make sure the phone is enabled for USB Debugging [Read the instructions for this]
Run "Run.bat" through your PC and the other processes will be automated.
Thank u so much bro.. I have been trying to root it after update but coludnt but ur process is tooo easy..thanks again. U r awesome..
Sent from my XT910 using xda premium
elias.parasini said:
No, there's no fastboot file for 65.1.21.XT910.PSHAsiaRetail.en.03. But you can go there by OTA Update via Moto Recovery
Click to expand...
Click to collapse
Hey thanks for your prompt reply..
I am getting this error when i do OTA
had to get the asia rom through the method above but i can't update any OTA!
i have downloaded the asia ota and put it on my sd.
i boot into recovery and update from zip/sd card.
all goes well until half way and i get an error.
something along the lines of "assert failed: apply_patch_check("MTD:boot:8388608:c3d17a6e41533c 813209ed51dfef327df8e1f76")
E:error in /tmp/sideload/package.zip
(status7 )
Installation Aborted
So i must have damaged some system files right?? Now how do i get the Fastboot files or is there any alternative as to how to go about it?
Worked for me like a charm, thx bro (651.167.19.XT910.Retail.en.EU).
Edit:
Titanium Backup said that 4755 isn't optimal for su and changed it to 6755
failed to root on my 65.1.21.XT910.PSHAsiaRetail.en.03
by manually executing the commands, i get stuck at step 9, with the error
"failed to copy 'su' to '/system/xbin/su': Read-only file system"
ptewee said:
failed to root on my 65.1.21.XT910.PSHAsiaRetail.en.03
by manually executing the commands, i get stuck at step 9, with the error
"failed to copy 'su' to '/system/xbin/su': Read-only file system"
Click to expand...
Click to collapse
Oh I see that you're using manual. Give the auto one a try?
i tried the auto first, everything completed successfully but i still end up unrooted...
then i tried manually step by step and there was the error at step 9...
It seem the /system didn't remounted to rw(read/write) mode. Did the exploit success?
Do the motofail clean step, reboot and start again from step 1 again.
Good luck.
Sent from my XT910 using XDA App
'motofail exploit' completed without error
will try flashing it again today, thanks
Hi,
I would like to know if voodoo rootkeeper is able to restore the root after the JB update ?
Greamlive said:
Hi,
I would like to know if voodoo rootkeeper is able to restore the root after the JB update ?
Click to expand...
Click to collapse
Worked for me
Does anyone know if the built in "OTA Root keeper" in SuperSU works too?
Sent from my Galaxy Nexus using Tapatalk 2
Unfortunately rootkeeper did not work for me. TPSparkyRoot and Debugfs were unsuccessful. Does anyone know of a root method for JB? The method used for TF300 perhaps?
Greamlive said:
Hi,
I would like to know if voodoo rootkeeper is able to restore the root after the JB update ?
Click to expand...
Click to collapse
Worked fine for me. FYI if you are using EZOverclock.apk freeze or remove it.
Scumbag Inc. said:
Unfortunately rootkeeper did not work for me. TPSparkyRoot and Debugfs were unsuccessful. Does anyone know of a root method for JB? The method used for TF300 perhaps?
Click to expand...
Click to collapse
Currently (to the best of my knowledge), the only way they could have root on the TF300 with JB was to restore root using both SuperSU and OTA Rootkeeper. There haven't been any new exploits as far as I know.
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app.
Rootkeeper did not work for me. The only apps I was using that required root were Titanium Backup and Samba Fileshare, plus obviously Super User and Busy Box. Anyway I can't use them now, with no root after updating to 4.1.1 despite Rootkeeper.
Something to take note of. Prior to the update I deleted my su backup and did it over again. Don't know if that made a difference or not but that was the only thing I did prior to the JB update.
Rooted, stock, locked bootloader.
My Transformer Prime just finished the update successfully!
Took several minutes to do whatever it does.
Lost root when updated, but Voodoo OTA RootKeeper restored root.
Nice to have JB on my Prime and Nexus 7.
Darkseider said:
Something to take note of. Prior to the update I deleted my su backup and did it over again. Don't know if that made a difference or not but that was the only thing I did prior to the JB update.
Click to expand...
Click to collapse
I checked and I have no /system/su_backup file, despite OTA RootKeeper telling me it was there before I installed the JB OTA. I wonder if my doing a cold boot before installing the OTA somehow erased the su_backup? I wish I had copied it somewhere else.
So I Do Have Su Backup File in sys but it doesnt work any thoughts? root keeper says it works but doesnt acually work
Updateing now.
I just erased and recreated my su backup with Voodo's OTA Rootkeeper.
back in a minute.
-------------
EDIT:
no dice.
installs .
restores the su binary at /system/bin/su
but it does not work.
-------------
Update got root access though adb using the backup su binary at /system/usr/we-need-root/su-backup
i just used the full path at the commad line...
copied the binary to /system/bin/su
more later.
-------------
Update:
got root working using
Root MANY ANDROID! [Upd: 20.09.2012]
I use linux so i just followed the steps in the batch file ( following the GOTO jumps for normal install) .
Problems:
this is the script i followed. it is in the zip at the link.
These are the command i used from the file. on linux i just replaced the stuff\adb.exe part with adb at the command line.
The files would not push to /data/local/tmp directly so i pushed the files to /sdcard/tmp then used adb shell and su'ed to cp (mv gave errors) them to /data/local/tmp
Code:
:START
echo Pushing busybox....
stuff\adb.exe push stuff/busybox /data/local/tmp/.
echo Pushing su binary ....
stuff\adb.exe push stuff/su /data/local/tmp/.
echo Pushing Superuser app
stuff\adb.exe push stuff/Superuser.apk /data/local/tmp/.
echo Making busybox runable ...
stuff\adb.exe shell chmod 755 /data/local/tmp/busybox
When i launched the backup app from adb it did not appear to ever stop. so i closed it after about 5 minutes and rebooted then continued.
Code:
stuff\adb.exe restore stuff/fakebackup.ab
echo Please look at your device and click RESTORE!
echo If all is successful i will tell you, if not this shell will run forever.
echo Running ...
stuff\adb.exe shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done" > NUL
echo Successful, going to reboot your device!
stuff\adb.exe reboot
echo Waiting for device to show up again....
ping -n 10 127.0.0.1 > NUL
stuff\adb.exe wait-for-device
The busybox binary did not work so i just used regular commands at adb shell prompt. Some of the commands required me to su first.
Code:
echo Going to copy files to it's place
stuff\adb.exe shell "/data/local/tmp/busybox mount -o remount,rw /system && /data/local/tmp/busybox mv /data/local/tmp/su /system/xbin/su && /data/local/tmp/busybox mv /data/local/tmp/Superuser.apk /system/app/Superuser.apk && /data/local/tmp/busybox cp /data/local/tmp/busybox /system/xbin/busybox && chown 0.0 /system/xbin/su && chmod 06755 /system/xbin/su && chmod 655 /system/app/Superuser.apk && chmod 755 /system/xbin/busybox && rm /data/local.prop && reboot"
:FINISH
echo You can close all open command-prompts now!
echo After reboot all is done! Have fun!
echo Bin4ry
pause
I may have left out some steps but if you follow the script and use su at the adb shell prompt you can get most of the steps to work. If there is enough demand i may put together a shell/bat script.
Greamlive said:
Hi,
I would like to know if voodoo rootkeeper is able to restore the root after the JB update ?
Click to expand...
Click to collapse
I had no issues. restored root perfectly
I lost root. Before i updated I deleted my backed up root in root keeper then protected again. Then updated to jb with file. Lost root but voodoo says I have a protected copy. But pressing restore does not bring it back. Hope there's a way to bring it back.
Edit: I did not temp unroot b4 update. Maybe my problem?
Sent from my DROID RAZR using xda app-developers app
Shinare said:
I lost root. Before i updated I deleted my backed up root in root keeper then protected again. Then updated to jb with file. Lost root but voodoo says I have a protected copy. But pressing restore does not bring it back. Hope there's a way to bring it back.
Click to expand...
Click to collapse
If i remember correctly from one of the previous updates, updating using a file is what caused voodoo to not be able to restore the root.
I had to wait until they found a new exploit to get it back.
x-web said:
I may have left out some steps but if you follow the script and use su at the adb shell prompt you can get most of the steps to work. If there is enough demand i may put together a shell/bat script.
Click to expand...
Click to collapse
I appreciate you pointing this out but here's the problem I'm running into. "mount: permission denied"
I can't su because I don't have root.
Here's what I do.
1. After knowing Superuser could very possibly be failed to restore root, I downloaded SuperSu in Google Play and installed it. Updated new binary of SuperSU.
2. Deleted the old backup in OTA Rootkeeper and protect the new root.
3. Went through OTA.
4. restored root from OTA Rootkeeper. Voila.
Something strange is going on here, i restored root with OTA root keeper, everything worked well and when i check status it states that my device is rooted and root permission granted.
Titanium Backup works perfectly as well, but other apps like Gesture Control are unable to get root access and when i run a root checker app it says that I dont have proper root access. Is there a way to fix this? Or is my root lost? I still have some hope as it works fine with TB
Stuff i'm still able to do:
-Temp unroot/reroot with OTA root keeper
-delete SU backup and make a new one
-Use Titanium Backup
-Use any root explorer i've tested so far, i can also access /data folder!
-Use Terminal emulator
-Also the file system/bin/SU is present.
What i cant do:
-app: gesture control
-update my SU binary with superuser app
-update my busybox using BusyBox free from play store
there must be a way!
Damn pissing on my sunny day. I want to see JB but am afraid of what problems it will cause. Thanks to all that posted saying OTA worked I hope it works for me too.
iamhcg said:
Here's what I do.
1. After knowing Superuser could very possibly be failed to restore root, I downloaded SuperSu in Google Play and installed it. Updated new binary of SuperSU.
2. Deleted the old backup in OTA Rootkeeper and protect the new root.
3. Went through OTA.
4. restored root from OTA Rootkeeper. Voila.
Click to expand...
Click to collapse
I did the same and can confirm that I successfully restored root.
before i made the update i did a backup of the root with voodoo ota rootkeeper.
now after the update rootkeeper the box "root permission granted" is unchecked and i dont know how to change it.
i tried to delete the "su backup" but it didnt work.it is written that the su backup is deleted but when i restart the rootkeeper it is still there.
i found a thread which could help me :http://forum.xda-developers.com/showthread.php?t=1911261
(For those with 'partial' root after JB update - regain root).
with adb the command su works.
but the problem is when i start adb shell there is no device listed anymore.i still can browse through the directory of my asus prime but i cannot push files because then there is no device error.
when i quit adb and restart adb to run "adb devices" the device is listed but after i start adb shell there isnt any device listed anymore.
cheers
lumpilumpe
Don't delete the SU backup - that is all you have with root at the moment.
It isn't clear which steps you can do.
Push files to device (in any state, /data/local/tmp for example?)
SU within ADB shell?
remount /system within ADB?
Seems like you can make it, if you work out the right things to do...
thx for the fast reply. yeah su within adb.
step 1:adb shell
step 2:su
step 3: yeaaaaahh... i found my mistake!!!
thx again for your answer , i solved it now.
for everyone who has the same problem.follow the steps from these link :http://forum.xda-developers.com/showthread.php?t=1911261
i made a mistake before .
last question:what can i do next time to prepare myself a better way?
cheers
lumpilumpe
Q
UOTE=tshoulihane;34224306]Don't delete the SU backup - that is all you have with root at the moment.
It isn't clear which steps you can do.
Push files to device (in any state, /data/local/tmp for example?)
SU within ADB shell?
remount /system within ADB?
Seems like you can make it, if you work out the right things to do...[/QUOTE]
lumpilumpe said:
before i made the update i did a backup of the root with voodoo ota rootkeeper.
now after the update rootkeeper the box "root permission granted" is unchecked and i dont know how to change it.
i tried to delete the "su backup" but it didnt work.it is written that the su backup is deleted but when i restart the rootkeeper it is still there.
i found a thread which could help me :http://forum.xda-developers.com/showthread.php?t=1911261
(For those with 'partial' root after JB update - regain root).
with adb the command su works.
but the problem is when i start adb shell there is no device listed anymore.i still can browse through the directory of my asus prime but i cannot push files because then there is no device error.
when i quit adb and restart adb to run "adb devices" the device is listed but after i start adb shell there isnt any device listed anymore.
cheers
lumpilumpe
Click to expand...
Click to collapse
I like SuperSU instead of SuperUser.
Check to see if you still are rooted by installing another app that requires root. (SuperSU will do).
What I did was simply have SuperSU forget OTA Rootkeeper, then close OTA Rootkeeper completely meaning ending it completely and then opening it again and having SuperSU ask if I want to grant it SU permissions again.
I don't remember if SuperUser lets you forget an app so it asks you again or not.