So I just got a new Evo! Sweet!
It came with software version 1.13.651.1.
I want to be able to flash ROMs and run Titanium Backup Pro.
What's the best/latest root method? Should I upgrade software first, or leave it?
(There are so many threads/sites, I'm confused as to what method is best/easiest.)
Thanks!
Do you mean 2.13? It depends on hboot, if you have 1.12 you can use lazy panda to soff. Anything 1.15 and higher and you need to dev unlock, there is no soff. You can try regawmod to unlock but people are having issues. It's easier to just sign up to HTC dev and unlock that way.
Under "about phone" it says 1.13.651.1 ... no, not 2.13.
Not sure how to check the hboot version....
1.13 is the first version that the phone shipped with. You might be lucky enough to have hboot 1.12. If so then you can run regaw's method and use lazypanda.
Just checking, you may be able to soff the phone. More then likely you have 1.12 hold power and wait for phone to turn off, let go then press and hold power + volume down, it will force bootloader
Make sure to check all your info and use this thread
http://forum.xda-developers.com/showthread.php?t=1690919
Then this
http://forum.xda-developers.com/showthread.php?t=1737123
I would assume that you have hboot 1.13. If that's the case do not accept any ota's or you will lose the ability to get s-off. Check the development thread and you'll find an auto-rooter thread. Then read up on lazy panda s-off. You should probably spend a couple days reading and re-reading in case you have any issues you'll know how to resolve them.
Sent from my EVO using xda premium
Is it 1.13? Been awhile lol
Yeah, I had to check. Lol
Yeah, my bad with all the odd numbers it just felt right.
Sent from my EVO using xda premium
I checked, and I do have hboot 1.12.
I guess that's a good thing!
So just do the lazy panda method?
You need to root then s-off. Use the threads in posted in order, all instructions are there.
metalfan78 said:
Make sure to check all your info and use this thread
http://forum.xda-developers.com/showthread.php?t=1690919
Then this
http://forum.xda-developers.com/showthread.php?t=1737123
Click to expand...
Click to collapse
I'm on a Mac; no Windows. So I can't do the RegawMOD...
Should I do this:
http://androidforums.com/evo-4g-lte-all-things-root/572162-how-get-full-root-mac.html
?
That should work, just make sure that you use the latest twrp and if you plan on flashing a different Rom skip flashing superuser, its an unnecessary extra step
om4 said:
That should work, just make sure that you use the latest twrp and if you plan on flashing a different Rom skip flashing superuser, its an unnecessary extra step
Click to expand...
Click to collapse
I got as far as running the runmemac.sh script; but now it's stuck on "waiting for device ... daemon started successfully..."
There IS a USB icon on the Evo, and it's in "charge only" mode ... and the boot screen showed "UNLOCKED" ...
Hmmm ...
So you flashed the unlock code? Sorry, I wasn't thinking about soff, you will need to flash supersu or superuser for root to be able to run lazy panda. Usually most users have hboot 1.15 or higher and can't use lazy panda so it slipped my mind
om4 said:
So you flashed the unlock code? Sorry, I wasn't thinking about soff, you will need to flash supersu or superuser for root to be able to run lazy panda. Usually most users have hboot 1.15 or higher and can't use lazy panda so it slipped my mind
Click to expand...
Click to collapse
Yes, the unlocking part worked fine; now I'm trying to get root, but adb won't see the phone (anymore).
(following this guide: http://androidforums.com/evo-4g-lte-all-things-root/572162-how-get-full-root-mac.html)
To get root flash the superuser zip in recovery, did you flash twrp
USB debugging needs to be re-enabled after unlock but for rooting stock, you need to flash recovery in fastboot. The recovery that comes with the zip you downloaded is a bit out of date you can download the latest from team win website and put it in the adb folder, after flashing twrp, you can flash the superuser zip that came with the zip you downloaded
om4 said:
USB debugging needs to be re-enabled after unlock but for rooting stock, you need to flash recovery in fastboot. The recovery that comes with the zip you downloaded is a bit out of date you can download the latest from team win website and put it in the adb folder, after flashing twrp, you can flash the superuser zip that came with the zip you downloaded
Click to expand...
Click to collapse
AHA! Re-enable debug! That was it! Thanks!
So are you saying to NOT run that shell script? I think it installs busybox and su...
Code:
#!/bin/bash
varadb=adb-mac
echo "---------------------------------------------------------------"
echo " One-Click Root ToolKit For Evo 4G LTE! "
echo " Script by Max Lee from HTCEvoHacks.com "
echo " Credits go to XDA users sparkym3 and Dan Rosenburg for exploit. "
echo "---------------------------------------------------------------"
echo " [*] This script will: "
echo " (1) root your Evo 4G LTE on ICS "
echo " (2) install Busybox "
echo " (3) install SU files "
echo " [*] Before u begin: "
echo " (4) Make sure to read full instructions at OneXRoot.com! "
echo "---------------------------------------------------------------"
echo "--- STARTING ----"
echo "--- WAITING FOR DEVICE"
./$varadb wait-for-device
echo "Start Rooting..."
./$varadb shell mv /data/local/tmp /data/local/tmp.bak
./$varadb shell ln -s /data /data/local/tmp
./$varadb reboot
echo "reboot #1 - DO NOT DISCONNECT YOUR DEVICE!"
./$varadb wait-for-device
./$varadb shell "echo \"ro.kernel.qemu=1\" > /data/local.prop"
./$varadb reboot
echo "reboot #2 - DO NOT DISCONNECT YOUR DEVICE!"
./$varadb wait-for-device
./$varadb remount
./$varadb push su /system/bin/su
./$varadb shell "chown root.shell /system/bin/su"
./$varadb shell "chmod 06755 /system/bin/su"
./$varadb shell "rm /system/xbin/su"
./$varadb shell "ln -s /system/bin/su /system/xbin/su"
./$varadb push Superuser.apk /system/app/.
./$varadb shell rm /data/local.prop
./$varadb shell rm /data/local/tmp
./$varadb shell mv /data/local/tmp.bak /data/local/tmp
./$varadb push busybox /data/local/tmp/.
./$varadb shell "chmod 755 /data/local/tmp/busybox"
./$varadb shell "/data/local/tmp/busybox mount -o remount,rw /system"
./$varadb shell "dd if=/data/local/tmp/busybox of=/system/xbin/busybox"
./$varadb shell "chown root.shell /system/xbin/busybox"
./$varadb shell "chmod 04755 /system/xbin/busybox"
./$varadb shell "/system/xbin/busybox --install -s /system/xbin"
./$varadb shell "rm -r /data/local/tmp/busybox"
echo "rebooting"
./$varadb reboot
echo "All Done rooting Evo 4G LTE, check out HTCEvoHacks.com for more cool stuff like ROMs, hacks, tips, and more!"
@pause
Oh, I didn't read through the entire tutorial you linked lol, that should do it actually
Related
All credit goes to the orig guy who made the d2 exploit
If you feel the need to donate money then he deserves it [email protected]
I made an easier to follow tutorial over here with pics. Sorry but I am tired of going back and forth so just go there if you are having problems. If you can follow simple adb commands just follow the directions below
Download and Install Samsung Drivers
64bit:
http://www.wikifilez.com/root files/epic4g/usb_drivers_GalaxyS_x64.zip
32bit:
http://www.wikifilez.com/root files/epic4g/SAMSUNG_USB_Driver_for_Mobile_Phones_x86.exe
1 Click Root Method
http://forum.androidcentral.com/fascinate-roms-hacks/33899-how-root.html
Manual Method
cd C:\android-sdk\tools
adb push C:\fascinate\su /sdcard/su
adb push C:\fascinate\rage.bin /data/local/tmp/rage.bin
adb push C:\fascinate\busybox /sdcard/busybox
adb shell
cd /data/local/tmp
chmod 0755 rage.bin
./rage.bin
wait....
when it brings you back to your original shell in windows then follow these commands
adb shell (you should see # this time instead of $ this is exactly what we want)
mount -t rfs -o remount,rw /dev/block/stl9 /system
cd /system/xbin
cat /sdcard/su > su
cat /sdcard/busybox > busybox
chmod 4755 su
chmod 4755 busybox
exit
adb install C:\fascinate\Superuser.apk
This is permanent.
I just updated the files here with the latest su / superuser.apk / busybox
Also check out my tutorial to fix the memory/lag issues for this phone
http://forum.xda-developers.com/showthread.php?p=8086738#post8086738
Dirrk said:
All credit goes to the orig guy who made the d2 exploit
I feel naked without my droid lol this phone is so light
adb push su /sdcard/su
adb push rage.bin /data/local/tmp/rage.bin
adb push busybox /sdcard/busybox
adb shell
cd /data/local/tmp
chmod 0755 rage.bin
./rage.bin
wait....
when it brings you back to your original shell or windows cmd promt
adb shell
mount -t rfs -o remount,rw /dev/block/stl9 /system
cd /system/xbin
cat /sdcard/su > .
cat /scard/busybox > .
chmod 4755 su
chmod 4755 busybox
exit
adb install Superuser.apk
Please let me know if I posted something wrong.
Click to expand...
Click to collapse
does it stick after reboot?
Its supposed to be a temporary root so i doubt it will.
This works on any android phone up to 2.2. I have confirmed this works on my epic, so th same sould work here.
Sent from my SPH-D700 using XDA App
see below.
confirmed root.
Had to use Superuser.apk 2.3.6.1 and the su binary in the package, but the rest worked.. except for that cat command? Why would you cat binary files instead of copying them? (not complaining, just curious). I just adb pushed them to /system/xbin, and adb shell chmod'd them.
You also have a typo near the end "scard" instead of "sdcard".
You can also use mv or cp. I just happen to use cat because I used it the other day rooting my friends stock 2.2 droid. Which required me to use cat.
And yes this is permanent
Cool, i tried using rm -rf to get rid of a directory I created accidentally, and was getting some syntax errors, so I wasn't sure how compatibile the command line on android was to linux.
Glad it's pretty close. Being very familiar with linux makes this pretty easy to understand. Day 1 with an android device was pretty darn fun. I think I'm glad I went this direction.
I just followed this and used the same files I had from my Droid 2 (just updated the Superuser.apk from this sites thread for it) and works perfectly. Rebooted phone did "adb shell" and "su" and still have root, so it is permanent
side note: steps say "/system/xbin" and assume you meant "/system/bin" like Droid 2 was. That's where I put them and it worked.
cliffr39 said:
I just followed this and used the same files I had from my Droid 2 (just updated the Superuser.apk from this sites thread for it) and works perfectly. Rebooted phone did "adb shell" and "su" and still have root, so it is permanent
side note: steps say "/system/xbin" and assume you meant "/system/bin" like Droid 2 was. That's where I put them and it worked.
Click to expand...
Click to collapse
It works either way, both are executable system folders. Glad you it worked for you, hopefully we can get some roms cooking soon and play catch up to the other galaxy s phones
doesnt work for me, i get an error device not found
ive type adb devices - device not found. usb debugging on, usb conneced on port 5037
xirnibor said:
doesnt work for me, i get an error device not found
ive type adb devices - device not found. usb debugging on, usb conneced on port 5037
Click to expand...
Click to collapse
Your USB mode might be set wrong. Flip it to whatever it's not at, and try again.
i forgot this laptop didnt have the updated usb drivers from android sdk, downloading then will try again. i have tried so far with the sdcard mounted and unmounted, while in usb debugging mode. will post after updates
How long do you actually have to wait after the execting the rage.bin file?
itznfb said:
How long do you actually have to wait after the execting the rage.bin file?
Click to expand...
Click to collapse
I dunno, ~20-30 seconds? Assuming sound is enabled you should hear the same USB device connected/disconnected sounds.
If you want to be 100% sure just wait like 90 seconds. I'm pretty sure it killed my shell though, so if it does that, you're good to go.
ok, adb recognizes the device *see below, however when i type adb push su /sdcard/su i get cannot stat 'su': no such file or directory. ?
C:\downloads\android\android\tools>adb devices
List of devices attached
I500a2d0087a device
namebrandon said:
I dunno, ~20-30 seconds? Assuming sound is enabled you should hear the same USB device connected/disconnected sounds.
If you want to be 100% sure just wait like 90 seconds. I'm pretty sure it killed my shell though, so if it does that, you're good to go.
Click to expand...
Click to collapse
ok... running the rage.bin locked up my device twice but on the third try it worked. another fascinate rooted
xirnibor said:
ok, adb recognizes the device *see below, however when i type adb push su /sdcard/su i get cannot stat 'su': no such file or directory. ?
C:\downloads\android\android\tools>adb devices
List of devices attached
I500a2d0087a device
Click to expand...
Click to collapse
su is a file (for our purposes right here, anyway). Unless you explicity specify its path, it needs to be in the same directory you're running the adb command from.
If you installed the Android SDK per guidelines, adb should be in your PATH environment variable, and you should be able to execute it from any directory. If you didn't do that, then for the sake of simplicity, copy all the files referenced in the original steps to your working directory. From your post above, it appears that is c:\downloads\android\android\tools\
I got stuck at cat /sdcard/su > . Is that supposed to be > .? It won't let me enter that...There's not something else that's supposed to be there?
EDIT: I get the same error faspalma
I'm stuck at that point too. cat /sdcard/su > . returns "cannot create .: is a directory"
I just rooted my x2, and installed eclipse. I cant get adb to push, I get permisson denied. I cant do adb remount cuz I get operation not permitted. I had it working once, but now It wont let me do it. Im trying to theme and I need adb push to work. I also tried putting an app on the sdcard and using root explorer to change the apk, all i did was make 1 png edit and the apk wasnt working. Im not sure whats going on and any help would be nice.
TheMuffStuff said:
I just rooted my x2, and installed eclipse. I cant get adb to push, I get permisson denied. I cant do adb remount cuz I get operation not permitted. I had it working once, but now It wont let me do it. Im trying to theme and I need adb push to work. I also tried putting an app on the sdcard and using root explorer to change the apk, all i did was make 1 png edit and the apk wasnt working. Im not sure whats going on and any help would be nice.
Click to expand...
Click to collapse
My Thoughts Are,
PC Mode
Updated Drivers
Correct Path Pointing To ADB Folder Inside Android SDK
Some Computers Need The USB Cable To Be Plugged In The Back Not The Front Due To Front Ports Aren't Supported
Make Sure You're Using The Right Commands ie. adb push <Local> <Remote> -Copy File/Dir To Device
Im gunna try some more today, also when I just make 1 png edit in an apk, and use my sdcard, then root explorer to swap the apks, the new apk gets an error, even tho I only made 1 edit. Its being weird.
Edit: Ive tried PC Mode, updated all drivers. My paths are fine, as im on the same computer that ive done all my theming on for my fascinate/charge. I am using USB's in the back, same one ive always used. Im using the right commands. My phone is rooted using the 1 click script. Im not really sure what else it could be. Im just getting permission errors, I have a feeling its a root problem. I dont know.
Edit:: The only thing I can think of is trying to sbf back to stock, update to pre-rooted gingerbread, and try that?
Honestly it sounds like you are not rooted. I had troubles running the script as well after it came out. I had already rooted earlier in the day using the actual researchers blog instructions.
http://vulnfactory.org/blog/2011/08/25/rooting-the-droid-3/
Those steps are all you need then you can push the su and Superuser.apk files. I wrote a vb script file to install the drives and push the files but I need to do more testing before I put that out for people to try. Using the one click is nice but with everything flying by so fast its easy to miss an error. If you have the one click extracted open a command prompt and navigate to that folder. Then run the commands as follows:
adb shell
mv /data/local/12m /data/local/12m.bak
ln -s /data /data/local/12m
(POWER OFF DEVICE IT WILL REBOOT ON ITS OWN)
adb shell
rm /data/local/12m
mv /data/local/12m.bak /data/local/12m
mv /data/local.prop /data/local.prop.bak
echo "ro.sys.atvc_allow_netmon_usb=0" > /data/local.prop
echo "ro.sys.atvc_allow_netmon_ih=0" >> /data/local.prop
echo "ro.sys.atvc_allow_res_core=0" >> /data/local.prop
echo "ro.sys.atvc_allow_res_panic=0" >> /data/local.prop
echo "ro.sys.atvc_allow_all_adb=1" >> /data/local.prop
echo "ro.sys.atvc_allow_all_core=0" >> /data/local.prop
echo "ro.sys.atvc_allow_efem=0" >> /data/local.prop
echo "ro.sys.atvc_allow_bp_log=0" >> /data/local.prop
echo "ro.sys.atvc_allow_ap_mot_log=0" >> /data/local.prop
echo "ro.sys.atvc_allow_gki_log=0" >> /data/local.prop
(POWER CYCLE)
adb shell
(# WILL BE LISTED)
exit
adb remount
adb push busybox /system/xbin/busybox
adb push su /system/xbin/su
adb push Superuser.apk /system/app/Superuser.apk
adb shell chmod 4755 /system/xbin/su
adb shell chmod 755 /system/xbin/busybox
Anything that is in () is not to be typed but informative. The steps above have worked for me on 2 X2's so far and a friends DROID3.
** 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!
[UnROOT][ICS] UnRoot Razr ICS 4.0.3 and 4.0.4 [NEW]
[UPDATED] Jun 16 2012
[REQUIREMENTS]
Check if your USB computer connection is "Mass Storage".
It shouldn't be. Change it to "media device".
Check if your configuration of android is set to "debug mode".
[COMMANDS]
1. Enter in command line Prompt DOS Mode
2. Remember connect your razr in USB port on computer or notebook
3. Activate "debug mode" and "media device"
4. Enter this commands with prompt
5. After commands reboot your device
@UnRoot For Droid Razr ICS
@echo off
adb start-server
adb remount
adb shell chmod 0777 /system/xbin/su
adb shell chmod 0777 /system/bin/su
adb shell chmod 0777 /system/app/Superuser.apk
adb shell chmod 0777 /system/xbin/busybox
adb shell rm -r /system/app/Superuser.apk
adb shell rm -r /system/xbin/su
adb shell rm -r /system/bin/su
adb shell rm -r /system/xbin/busybox
adb reboot
exit
[ROOT] If you need Root again
[SCRIPT] Fully tested and only run in prompt and wait process
http://www.mediafire.com/download.php?p1dks81hu3dtiw7
http://www.4shared.com/rar/iqgref86/ROOT.html
[POST ORIGINAL]
http://forum.xda-developers.com/show....php?t=1707431
I'm here to help people around the world
is not what you do that makes you extraordinary
but it is the way that we give that says who we are
it can not be measured with thanks or views
Jesus is the Lord
About this Root method - Thank You XDA for this page
http://www.xda-developers.com/androi...razr/#comments
About this Root method - Thank You Droid Life for this page
http://www.droid-life.com/2012/06/14...icial-release/
I'm here to help people around the world
is not what you do that makes you extraordinary
but it is the way that we give that says who we are
it can not be measured with thanks or views
Jesus is the Lord
About this Root method - Thank You XDA for this page
http://www.xda-developers.com/android/root-achieved-for-ics-on-gsm-and-cdma-moto-razr/#comments
About this Root method - Thank You Droid Life for this page
http://www.droid-life.com/2012/06/14/razr-ice-cream-sandwich-builds-rooted-before-official-release/
Im Lost
Hey i need help in the beginning were you do the commands prompt and so on. Pleace help thanks.
Thanks hacker812c! To confirm...this root and unroot works with the 4.0.4 OTA just released by VZW right?
This root method worked just fine with 4.0.4. I do have one problem with Safestrap... when I reboot, I don't see the safesystem menu pop up just before the boot animation begins. Why is this? How can I get this fixed. I used to do a manual backup of the entire system. Help!!!
Sent from my DROID RAZR using xda app-developers app
Need help
The instructions are not very clear, i have followed every step but i dont see the prompts that i am suppose to use can you please clearify
hacker812c said:
[UnROOT][ICS] UnRoot Razr ICS 4.0.3 and 4.0.4 [NEW]
[UPDATED] Jun 16 2012
[REQUIREMENTS]
Check if your USB computer connection is "Mass Storage".
It shouldn't be. Change it to "media device".
Check if your configuration of android is set to "debug mode".
[COMMANDS]
1. Enter in command line Prompt DOS Mode
2. Remember connect your razr in USB port on computer or notebook
3. Activate "debug mode" and "media device"
4. Enter this commands with prompt
5. After commands reboot your device
@UnRoot For Droid Razr ICS
@echo off
adb start-server
adb remount
adb shell chmod 0777 /system/xbin/su
adb shell chmod 0777 /system/bin/su
adb shell chmod 0777 /system/app/Superuser.apk
adb shell chmod 0777 /system/xbin/busybox
adb shell rm -r /system/app/Superuser.apk
adb shell rm -r /system/xbin/su
adb shell rm -r /system/bin/su
adb shell rm -r /system/xbin/busybox
adb reboot
exit
[ROOT] If you need Root again
[SCRIPT] Fully tested and only run in prompt and wait process
http://www.mediafire.com/download.php?p1dks81hu3dtiw7
http://www.4shared.com/rar/iqgref86/ROOT.html
[POST ORIGINAL]
http://forum.xda-developers.com/show....php?t=1707431
I'm here to help people around the world
is not what you do that makes you extraordinary
but it is the way that we give that says who we are
it can not be measured with thanks or views
Jesus is the Lord
About this Root method - Thank You XDA for this page
http://www.xda-developers.com/androi...razr/#comments
About this Root method - Thank You Droid Life for this page
http://www.droid-life.com/2012/06/14...icial-release/
Click to expand...
Click to collapse
This thread is a non sense. Ive no idea why this is still alive.
Follow this if you wanna get unrooted.
http://forum.xda-developers.com/showthread.php?t=1710871
Sent from my XT910 using xda premium
I've tried KingRoot but it tells me the device isn't supported. Are there any ways to install a custom recovery like TWRP or CWM?
Extract the boot.img file from "UPDATE.APP", upload it here, and I'll root it manually for you.
mann1 said:
Extract the boot.img file from "UPDATE.APP", upload it here, and I'll root it manually for you.
Click to expand...
Click to collapse
I saw your post on another thread here so I got the tools to extract it, but my knowledge is limited at ro.secure=0 and bash. If you wouldn't mind sharing I'd love to know how it's done.
I've attached the file.
Well, first you need to download the following files:
1-Your rooted_boot img from here
2-Compressed folder mann1.zip from here
===
Now lets start,
1- Unzip the rooted img then flash it, (be careful it's not tested)
2- 2- Unzip the file "mann1.zip" to get folder "mann1" then copy it directly into your device internal storage NOT the SD card. Put the the whole folder not the files inside
3-If the rooted boot worked fine, restart your device in the normal mode (NOT the recovery nor bootloader), and type the following commands one by one:
Code:
adb devices
adb root
adb shell
Now you supposed to see your root like that
[email protected]:/ #
complete the commands in the adb shell:
mount -o remount,rw /system
mount -o remount,rw /etc
mkdir /system/bin/.ext
mkdir /etc/init.d
cat /sdcard/mann1/busybox > /system/bin/busybox
cat /sdcard/mann1/su > /system/xbin/su
cat /sdcard/mann1/Superuser.apk > /system/app/Superuser.apk
cat /sdcard/mann1/su > /system/xbin/daemonsu
cat /sdcard/mann1/su > /system/xbin/sugote
cat /system/bin/sh > /system/xbin/sugote-mksh
cat /sdcard/mann1/supolicy > /system/xbin/supolicy
cat /sdcard/mann1/otasurvival.sh > /system/xbin/otasurvival.sh
cat /sdcard/mann1/libsupol.so > /system/lib/libsupol.so
cat /sdcard/mann1/su > /system/bin/.ext/.su
cat /sdcard/mann1/su > /etc/.installed_su_daemon
cat /sdcard/mann1/install-recovery.sh > /etc/install-recovery.sh
cat /sdcard/mann1/99SuperSUDaemon > /etc/init.d/99SuperSUDaemon
chown 0.0 /system/bin/busybox
chmod 0755 /system/bin/busybox
chown 0.0 /system/app/Superuser.apk
chmod 0755 /system/app/Superuser.apk
chown 0.0 /system/xbin/su
chmod 0755 /system/xbin/su
chown 0.0 /system/xbin/sugote
chmod 0755 /system/xbin/sugote
chown 0.0 /system/xbin/sugote-mksh
chmod 0755 /system/xbin/sugote-mksh
chown 0.0 /system/xbin/daemonsu
chmod 0755 /system/xbin/daemonsu
chown 0.0 /system/xbin/supolicy
chmod 0755 /system/xbin/supolicy
chown 0.0 /system/xbin/otasurvival.sh
chmod 0755 /system/xbin/otasurvival.sh
chown 0.0 /system/lib/libsupol.so
chmod 0755 /system/lib/libsupol.so
chown 0.0 /system/bin/.ext/.su
chmod 0755 /system/bin/.ext/.su
chown 0.0 /etc/.installed_su_daemon
chmod 0755 /etc/.installed_su_daemon
chown 0.0 /etc/install-recovery.sh
chmod 0755 /etc/install-recovery.sh
chown 0.0 /etc/init.d/99SuperSUDaemon
chmod 0755 /etc/init.d/99SuperSUDaemon
daemonsu -d
reboot
I assumed you already know the adb and fastboot commands to flash the boot
If everything run smoothly,after restarting your device you will find SuperSU installed, and the device is rooted w/o custom recovery.
mann1 said:
Code:
adb devices
adb root
adb shell
Now you supposed to see your root like that
[email protected]:/ #
Click to expand...
Click to collapse
I just booted the image and tried to start adb as root which it does however adb shell drops me into a regular shell, I also tried to flash it but still, no dice.
Code:
[email protected]:~/Music/root$ adb root
restarting adbd as root
[email protected]:~/Music/root$ adb shell
[email protected]:/ $ exit
I have a feeling there may be a software block inside system.img to prevent adb starting a shell as root, any idea?
adamhighdefinition said:
I just booted the image and tried to start adb as root which it does however adb shell drops me into a regular shell, I also tried to flash it but still, no dice.
I have a feeling there may be a software block inside system.img to prevent adb starting a shell as root, any idea?
Click to expand...
Click to collapse
The method works fine under Windows, but I've never tried it out under Linux.
Try this new root_boot2.img HERE (be careful it's not tested)
Pls flash it, don't just boot it:
fastboot flash boot root_boot2.img
If you get error with "adb root", skip it and keep going till the "reboot"
Good luck
mann1 said:
The method works fine under Windows, but I've never tried it out under Linux.
Try this new root_boot2.img HERE (be careful it's not tested)
Pls flash it, don't just boot it:
fastboot flash boot root_boot2.img
If you get error with "adb root", skip it and keep going till the "reboot"
Good luck
Click to expand...
Click to collapse
Just tested it, it caused a bootloop though, I cleared the cache and it still looped. I'll flash the first one and test it on windows then I'll report back.
The first one does allow me to see the Logcat output for all of the system services in Android Studio though, so it is giving elevated permissions.
Yeah, same on windows. Drops me into a normal shell.
Well, try this one
mann1 said:
Well, try this one
Click to expand...
Click to collapse
Dude thank you! I was repacking custom systems all night last night trying to install it directly into the rom.
In your mann1 folder the su binary is out of date btw
adamhighdefinition said:
Dude thank you! I was repacking custom systems all night last night trying to install it directly into the rom.
In your mann1 folder the su binary is out of date btw
Click to expand...
Click to collapse
Yvw, then this last one worked fine with you.
Su binary is extracted from the most recent version of SuperSu.apk, but in all cases we just use it to get rooted then you can update the whole package via Google play.
mann1 said:
Yvw, then this last one worked fine with you.
Click to expand...
Click to collapse
Yeah, last one worked for the Mediapad T1 8.0 Pro T1-921L.
mann1 said:
Su binary is extracted from the most recent version of SuperSu.apk, but in all cases we just use it to get rooted then you can update the whole package via Google play..
Click to expand...
Click to collapse
Must just be supersu being weird then, thanks again.
This tutorial explains how to root the kernel of any device under Linux. Here
Good luck