Related
Thinking about rooting the tfp for the first time. What's the best way from .28?
Currently this is the only way to root .28 if you haven't rooted before. http://forum.xda-developers.com/showthread.php?t=1706588
Sent from my ADR6425LVW using XDA Premium.
I have had great success with that tool. I was on .21 rooted, but OTArootkeeper didnt keep root (derp) so I rooted with Debugfs, just do what it says on the tool and make sure you have the drivers and you're away.
It also adds the Superuser app
Worked for me But....
SteveG12543 said:
Currently this is the only way to root .28 if you haven't rooted before. http://forum.xda-developers.com/showthread.php?t=1706588
Sent from my ADR6425LVW using XDA Premium.
Click to expand...
Click to collapse
The root method worked like a charm on my TFP .28
I used root checker and it confirmed that I have root access.
However, most of my root apps are not working and say that they have no root access, despite allowing them using Superuser app.
Could it be with the error I got on step two (Check Attached.)
Manar Aleryani said:
The root method worked like a charm on my TFP .28
I used root checker and it confirmed that I have root access.
However, most of my root apps are not working and say that they have no root access, despite allowing them using Superuser app.
Could it be with the error I got on step two (Check Attached.)
Click to expand...
Click to collapse
im not sure about others
but im having a real hard time reading what it says, could you type out what it says in your cmd?
also did super user get installed onto your prime? if so open it and make sure you have the latest binary on there~
yeah i can barely read it lol
lil-devil said:
im not sure about others
but im having a real hard time reading what it says, could you type out what it says in your cmd?
also did super user get installed onto your prime? if so open it and make sure you have the latest binary on there~
Click to expand...
Click to collapse
Here is what it says,
Step 2 - Rooting...
debugfs: rm: File not found by ext2_lookup while trying to resolve filename
debugfs: rm: File not found by ext2_lookup while trying to resolve filename
debugfs: debugfs: Allocate inode: 1431
debugfs: debugfs: debugfs: debugfs:
Rebooting...
Yes SuperUser was installed
After a second thought, I think I forgot to check if the binary is up to date.
My TFP is not near by. I will check it when I go home.
A million thanks if it turns out to be the problem.
Manar Aleryani said:
Here is what it says,
Step 2 - Rooting...
debugfs: rm: File not found by ext2_lookup while trying to resolve filename
debugfs: rm: File not found by ext2_lookup while trying to resolve filename
debugfs: debugfs: Allocate inode: 1431
debugfs: debugfs: debugfs: debugfs:
Rebooting...
Yes SuperUser was installed
After a second thought, I think I forgot to check if the binary is up to date.
My TFP is not near by. I will check it when I go home.
A million thanks if it turns out to be the problem.
Click to expand...
Click to collapse
yeah thats usually the problem
when i first started mine i went omgwtfbbq at it too xDD
let us know if thats the problem or not!
lil-devil said:
yeah thats usually the problem
when i first started mine i went omgwtfbbq at it too xDD
let us know if thats the problem or not!
Click to expand...
Click to collapse
I tried to update the binary and this is what I get (Check Attached.)
Same problem. Still most root apps not working
Personally, I was able to get the debugfs batch file to work properly, but it took some doing.
My .28 TF Prime wouldn't reboot fast enough for the batch file to work right, so I ended up messing around with the batch file a bit to get it to work.
Even still, the second reboot was too slow and it failed to install superuser. However, I just downloaded SU from the Play Store and it worked fine.
I would recommend running the debugfs batch file again and see if that might fix the issue since your SU binary is already up to date.
Manar Aleryani said:
I tried to update the binary and this is what I get (Check Attached.)
Same problem. Still most root apps not working
Click to expand...
Click to collapse
when you start any programs that requires root like titanium backup, does it ask for root access?
try downloading super SU also~
Hello, when i try to use this tool on my TFP .28, it just sticks at
Waiting for device to be detected...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Click to expand...
Click to collapse
Just use straight commands, dont use a script/toolkit, if you dont know how to tweak or dont understand it
Sent from my i9250
Gipjoe said:
Hello, when i try to use this tool on my TFP .28, it just sticks at
Click to expand...
Click to collapse
Make sure you have ADB and the drivers installed.
---------- Post added at 09:12 AM ---------- Previous post was at 09:08 AM ----------
lil-devil said:
when you start any programs that requires root like titanium backup, does it ask for root access?
try downloading super SU also~
Click to expand...
Click to collapse
Titanum backup is actually one of the apps that work.
I'm having problems with other root apps.
And yes; they do ask for root access and I grant them.
I will try to use Super SU. But will I have to disable the original SuperUser app? And how?
lil-devil said:
when you start any programs that requires root like titanium backup, does it ask for root access?
try downloading super SU also~
Click to expand...
Click to collapse
I tried downloading Super SU. It changed nothing but ruining my original super user app. Now the app allows all root apps without prompt and I can't use the Super SU because it's Super slow
I lost root when I had to factory reset my phone after the OTA upgrade. I was getting Motorola Services Stopped Errors randomly and I couldn't identify the app(s) causing it so I just reset.
Is there a root yet for the JB? I am going to assume not since it is so new.
murky024 said:
I lost root when I had to factory reset my phone after the OTA upgrade. I was getting Motorola Services Stopped Errors randomly and I couldn't identify the app(s) causing it so I just reset.
Is there a root yet for the JB? I am going to assume not since it is so new.
Click to expand...
Click to collapse
Nope no way to root yet. Most likely you had a problem because the proper procedure wasn't followed that's on droidrzr.com (not sure if its here yet)
Full-Throttle Team
You can try to use Matt's root fixer found here Root Fixer near the bottom of page 19.
Download file above - Extract
Enable USB Debugging in Settings/Development (if it's grayed out you need to enable development tools at the top slider)
Enable "Unknown Sources" in Settings/Privacy
Connect Phone
go to Settings/Storage menu softkey "USB Computer Connection"
Select MTP
Run .bat tool
Should see 0 and all is well
badjedi said:
You can try to use Matt's root fixer found here Root Fixer near the bottom of page 19.
Download file above - Extract
Enable USB Debugging in Settings/Development (if it's grayed out you need to enable development tools at the top slider)
Enable "Unknown Sources" in Settings/Privacy
Connect Phone
go to Settings/Storage menu softkey "USB Computer Connection"
Select MTP
Run .bat tool
Should see 0 and all is well
Click to expand...
Click to collapse
I tried this it didn't work for me.
Sent from my DROID RAZR using Tapatalk 2
iguanad said:
I tried this it didn't work for me.
Sent from my DROID RAZR using Tapatalk 2
Click to expand...
Click to collapse
ditto, had the same problem. Tried to go back to ICS and that didn't work either
dbtrumpetguy said:
ditto, had the same problem. Tried to go back to ICS and that didn't work either
Click to expand...
Click to collapse
There is no way back and no way to root, yet.
I tried rooting a JB Razr Maxx for two days with a combination of methods.
They have closed all the exploits The one that looked promising, and came close requires being able to generate a debug log.
I couldn't get the JB Razr to do that.
So as of now, no root...
Re-Root Fail
Ok Re-Root method fails for me as well.
Here is what I have done and what I get:
Drivers loaded.
USB debugging Connected
Connected as a media device (MTP)
Unknown sources is selected
Connect phone and windows 7 recognizes phone as Mot Composite ADB Interface and Motorola USB Networking Driver
When I run FixRoot.bat I get the following:
"Have drivers installed, phone connected, and USB Debugging enabled in Developer Options."
/system/bin/sh: su: not found
2879 KB/s (91992 bytes in 0.031s)
2778 KB/s (1020803 bytes in 0.358s)
/system/bin/sh: su: not found
/system/bin/sh: su: not found
/system/bin/sh: su: not found
/system/bin/sh: su: not found
/system/bin/sh: su: not found
"Rebooting..."
NO ROOT
jasonfzj80 said:
Ok Re-Root method fails for me as well.
Here is what I have done and what I get:
Drivers loaded.
USB debugging Connected
Connected as a media device (MTP)
Unknown sources is selected
Connect phone and windows 7 recognizes phone as Mot Composite ADB Interface and Motorola USB Networking Driver
When I run FixRoot.bat I get the following:
"Have drivers installed, phone connected, and USB Debugging enabled in Developer Options."
/system/bin/sh: su: not found
2879 KB/s (91992 bytes in 0.031s)
2778 KB/s (1020803 bytes in 0.358s)
/system/bin/sh: su: not found
/system/bin/sh: su: not found
/system/bin/sh: su: not found
/system/bin/sh: su: not found
/system/bin/sh: su: not found
"Rebooting..."
NO ROOT
Click to expand...
Click to collapse
I opened the bat file and ran each command manually in a dos window to see which area was causing issues. I compared the files the bat file was looking or with what I could find with Astro file viewer. Some of the paths were incorrect. Once I corrected the paths and continued to execute each line manually it finally worked.
Thanks Matt!
tieman123 said:
I opened the bat file and ran each command manually in a dos window to see which area was causing issues. I compared the files the bat file was looking or with what I could find with Astro file viewer. Some of the paths were incorrect. Once I corrected the paths and continued to execute each line manually it finally worked.
Thanks Matt!
Click to expand...
Click to collapse
Can you correct the file and repost? Or at least tell us the corrected paths?
Sent from my DROID RAZR using Tapatalk 2
iguanad said:
Can you correct the file and repost? Or at least tell us the corrected paths?
Sent from my DROID RAZR using Tapatalk 2
Click to expand...
Click to collapse
Never mind I got it. Thanks Matt and tieman.
To all who are interested, if you find where the file su-backup is on your phone all you need to do is correct the file path in the batch file using text editor wherever su-backup is mentioned.
Sent from my DROID RAZR using Tapatalk 2
I am having the same issue. However, I do have a couple of backups, is there anyway to retrieve the needed files from therm?
iguanad said:
Never mind I got it. Thanks Matt and tieman.
To all who are interested, if you find where the file su-backup is on your phone all you need to do is correct the file path in the batch file using text editor wherever su-backup is mentioned.
Sent from my DROID RAZR using Tapatalk 2
Click to expand...
Click to collapse
Where did you find the files and if you can tell us, what would you change?
10X
I've updated my RestoreRoot.zip for each to use 3 different possibles:
/system/usr/we-need-root/su-backup
#Lastest Update of Voodoo OTA Rootkeeper
/system/su-backup
#Older version of Voodoo OTA Rootkeeper
su
#Generic call for su binary in either /system/bin/ or /system/xbin/
If you don't have root there.. you don't have root lol
Mine was in system bin
Sent from my DROID RAZR using Tapatalk 2
iguanad said:
Mine was in system bin
Sent from my DROID RAZR using Tapatalk 2
Click to expand...
Click to collapse
You didn't backup root and have a useless su binary without the proper permissions.
Sent from my DROID RAZR HD using Tapatalk 2
mattlgroff said:
You didn't backup root and have a useless su binary without the proper permissions.
Sent from my DROID RAZR HD using Tapatalk 2
Click to expand...
Click to collapse
Correction. It was in the system folder, not system / bin. My root was restored using your tool.
Sent from my DROID RAZR using Tapatalk 2
mattlgroff said:
I've updated my RestoreRoot.zip for each to use 3 different possibles:
/system/usr/we-need-root/su-backup
#Lastest Update of Voodoo OTA Rootkeeper
/system/su-backup
#Older version of Voodoo OTA Rootkeeper
su
#Generic call for su binary in either /system/bin/ or /system/xbin/
If you don't have root there.. you don't have root lol
Click to expand...
Click to collapse
Hey Matt, I see that I have system/su-backup and also su binary in system/xbin. Yet still, your script is not restoring root. I had root after 4.1.2 upgrade and using your restore root tool, but had to do a factory reset. Now it won't work the second time.
badjedi said:
You can try to use Matt's root fixer found here Root Fixer near the bottom of page 19.
Download file above - Extract
Enable USB Debugging in Settings/Development (if it's grayed out you need to enable development tools at the top slider)
Enable "Unknown Sources" in Settings/Privacy
Connect Phone
go to Settings/Storage menu softkey "USB Computer Connection"
Select MTP
Run .bat tool
Should see 0 and all is well
Click to expand...
Click to collapse
Hi badjedi
I use 50 posts per page so a link to a page 19 fails to get to the right page. A link to the post will work every time though.
Matt's Post Clicky
I found a link to a site with a JB root method for the Razr M. Has anyone tried it? I cant because I am on my phone.
http://forums.androidcentral.com/droid-razr-m/219078-guide-razr-m-root-method.html
sparta10 said:
Hey Matt, I see that I have system/su-backup and also su binary in system/xbin. Yet still, your script is not restoring root. I had root after 4.1.2 upgrade and using your restore root tool, but had to do a factory reset. Now it won't work the second time.
Click to expand...
Click to collapse
If neither of them work then it isn't gonna happen.
Try yourself calling them in adb shell.
Update 9/14/2013
A better solution has been released, please update using it.
http://forum.xda-developers.com/showthread.php?p=45598648
Warning: Don't attempt to use this on a device that isn't Motorola.
Lets break this sub forum open with a good one.
See: http://www.androidpolice.com/2013/09/12/exclusive-how-to-root-moto-x-ultra-mini-and-maxx/ for the story
Bounty payouts or donations can be paypaled to [email protected], or use the donate button to the left. If its for the bounty, please reply below with confirmation number or pm me.
These files are not to be mirrored elsewhere, no included in other packages. Its simple already, no need to repackage it.
Same APK should work for Maxx, Ultra and Mini. If it does not, I just need to rebuild it and need someone to test, it will work.
adb install -r <filename>
Run MotoRoot app
Press Setup
Install Supersu app
Phone will reboot, and you will be rooted as soon as device is fully booted.
Limitations:
Uninstalling the app will disable root until reinstalled
supersu is not able to update su yet, this will be fixed in an update shortly.
su is maintained in a ext4 img at /data/xbin.img and mounted over /system/xbin at BOOT_COMPLETE.
su is not available for the first few seconds of boot, im working on this.
/system is write protected, even with unlocked bootloaders you can not write to it while booted in Android.
Unroot:
Two choices, factory reset, or press the unroot menu option in the app.
Problems:
Run into a problem? try hittung unroot then re-rooting
Credits:
We use two vulns in this app, first being 9695860 to gain system user, then a symlink attack of mine to get root from system.
xIndirect (nick) for assisting me from start to finish
Whoever originally found bug 9695860
Saurik for his description of 9695860
Ryan Welton for his 9695860 tool
Dave Kover for yet another kick butt icon
and Anthony Fox/Droid-Hive for great help with getting the device to me today
Very much appreciated.
PayPal transaction ID 4GK69936510343543.
Ignore everything I said, I will send my donation thank you
jcase said:
/system is write protected, even with unlocked bootloaders you can not write to it while booted in Android.
Click to expand...
Click to collapse
firist off thank you for all your hard work
i do have a question dose this mean we can not install apps on the system/app folder?
jcase said:
su is not available for the first few seconds of boot, im working on this.
Click to expand...
Click to collapse
and dose this mean files cant be pushed with adb as a work around?
Confirmation number: 3FS7579230091290J
Thanks!!
Confirmation 17R58863KC726802C , I didn't pledge on the bounty thread.
Yes!
Worked like a charm!
Been waiting for this since day one. You are a god sir.
TheWhiteChallenger said:
firist off thank you for all your hard work
i do have a question dose this mean we can not install apps on the system/app folder?
and dose this mean files cant be pushed with adb as a work around?
Click to expand...
Click to collapse
No messing with system/app yet, just system/xbin. Will be addressing the rest of it soon, I just got my phone today. Been talking with HashCode and DBHacker about getting custom roms going, it is being looked at now.
adb works fine, su just doesnt get remounted until the BOOT_COMPLETE broadcast is sent, it means poorly written apps that does retry a root command with a delay, MIGHT fail to get root at boot. They should retry. I will be addressing this, soon.
Like I said, just got the phone about 7 hours ago.
Thanks man!
Sent from my XT1080 using XDA Premium 4 mobile app
got adfree working, but you have to do it QUICKLY. remount /system as rw, then immediately press the update button on the adfree app. the changes will remain until reboot, but I hardly ever reboot
busybox mount -o remount,rw /system;
Thanks...didn't expect to have root so soon. Confirmation 7PD1555899342392B - pledged over on the Droid Ultra bounty page
Droid Mini Confirmed! Thank you!
Sent from my XT1030 using xda app-developers app
jcase said:
No messing with system/app yet, just system/xbin. Will be addressing the rest of it soon, I just got my phone today. Been talking with HashCode and DBHacker about getting custom roms going, it is being looked at now.
adb works fine, su just doesnt get remounted until the BOOT_COMPLETE broadcast is sent, it means poorly written apps that does retry a root command with a delay, MIGHT fail to get root at boot. They should retry. I will be addressing this, soon.
Like I said, just got the phone about 7 hours ago.
Click to expand...
Click to collapse
ok kool, i dont mean to sound ungrateful thats just mainly what i use root for is fiddling with stuff of the system folder, so i was just wondering if i was permanently screwed of if was something that is atleast being working on, thanks again ill be sending my donation as soon as i remember my paypal pw, lol
Should USB Debugging be enabled?
is the "Transaction ID" the confirmation number?
Thanks! 8JG23957NE2435454
Posted from http://forum.xda-developers.com/showthread.php?t=2431005
Confirmation number: 4JK07192689429602
Thanks!
So this has to be installed by adb? What if in my haste and excitement, I "accidentally" installed it without ADB? I noticed I can't uninstall it. However, when I do Root Checker, it shows I'm rooted but I can't install SU it says "Installation Failed!"
Every time I start SuperSU the message "The SU binaries needs to be updated. Continue?" comes up, but when "Normal" button is pressed on the next screen (since we dont have custom recoveries) the update fails.
Should we not update SU?
CrazyRussianXDA said:
Every time I start SuperSU the message "The SU binaries needs to be updated. Continue?" comes up, but when "Normal" button is pressed on the next screen (since we dont have custom recoveries) the update fails.
Should we not update SU?
Click to expand...
Click to collapse
I'm getting the exact same thing, if you push cancel it just closes the app.
CrazyRussianXDA said:
Every time I start SuperSU the message "The SU binaries needs to be updated. Continue?" comes up, but when "Normal" button is pressed on the next screen (since we dont have custom recoveries) the update fails.
Should we not update SU?
Click to expand...
Click to collapse
Just don't open SuperSU once it's installed. Reboot one more time and you'll get regular prompts from SuperSU to allow permissions as apps request root.
Disclaimer: rooting your phone entails risk. You may brick it, cause it to catch fire, cause it to form the first node in the Skynet network, or otherwise render it inoperable. Please read the directions carefully to ensure that nothing unexpected happens. This rooting tool is as safe as I can make it, but there's never any guarantees.
After a very helpful suggestion from Surge1223, I managed to take an existing root exploit for the Xperia and modify it to work on 4.3 with SELinux enforcing. This installs su, SuperSU, and the necessary support files to enable the root.
This rooting process should work with a wide range of Android devices, particularly those running Linux Kernel before 3.5.5 (which most Android 4.3 ROMs use.) It 's known to work for may GS4 variants and is harmless if it fails to work (no "Warranty Void" flags get set.)
Again, using this WILL NOT set the "Knox Warranty Void" flag.
For a video showing the steps to root, see Tomsgt's awesome work here.
There's another video from owenbeals here.
A hint to people having problems using this:
If you use XDA to e-mail me a question, SET YOUR XDA ACCOUNT UP TO ACCEPT MAIL.
If you are set up to refuse mail, then your question will be ignored. Actually, you shouldn't e-mail me. PM or post here.
Step 1 - setting up the USB drivers
Before you try using this rooting program, you'll need to have the USB drivers installed for your phone.
The easiest way to do this is to install Samsung Kies. If Kies sees your phone, you're OK for the drivers.
If you don't have the drivers working, the root installer will hang at "waiting for device..."
Step 2 - Enable USB Debugging
The second thing you must do is to enable USB debugging on your phone. Go to "Settings", "More...", then "Developer Options".
If "Developer Options" doesn't appear, then you'll need to enable it - go to "Settings", "More", "About Phone". Scroll down so the "Build Number" is visible, then tap on that several times until developer mode is enabled.
In Developer Options, make sure "USB Debugging" is checkmarked.
Step 3 - Enable USB ADB Access
Make sure that your computer is allowed to use USB debugging on your phone. To do this, unplug your phone and unlock it. Then, plug in the USB cable.
If you see an "Alllow USB debugging?" window pop up, tap on the "Always allow from this computer" to check it, then tap OK.
If you don't see that popup, it's OK, you should be OK to proceed.
That's it for the phone.
Step 4 - Unzip the saferoot.zip
Then you need to unpack the attached ZIP file somewhere onto your PC.
You should have the following when done:
- a file called "install.bat"
- a file called "install.sh"
- a folder called "files"
Step 5 - Root your phone
Double click on the "install.bat" to run the root. It will root and reboot your phone. Once that's done, you're rooted!
The first thing that the install script will ask you is whether or not to install Busybox. Busybox is a program that provides a fairly extensive set of Linux shell utilities that a Unix user would expect to see. If you're not going to be using the shell (terminal emulator or adb shell) then you may not want to install Busybox. You may, however, find that some root-required utilities assume that Busybox is installed.
If SuperSU asks you to update the su binary, choose the "Normal" method.
If SuperSU asks you about disabling Knox, allow it.
This exploit will NOT set the Knox Warranty Void flag. It will set the "Custom" flag, but that's nothing to worry about.
While you're running this, you'll need to keep the phone awake and watch both the computer running the rooting script and your phone.
You shouldn't unplug the phone unless you're prompted by the rooting script. Leave it connected until it's done.
Rooting on Linux and MacOS
The saferoot script has a copy of adb for MacOS and for Linux included.
To run this root, download and unzip the zip file. Open a shell window, use "cd" to change to the directory where you unpacked the zip, and type "sh ./install.sh". The OS will be detected automatically and the root should run basically as described above.
If the embedded adb fails, you'll need to have the Android Debugging Bridge (adb) installed and configured and on your path. You can test that it's ready by opening a shell (Terminal) window and typing "adb shell". If you get a shell prompt on the phone, type "exit" and you're ready to go.
Notes
Don't try to download this onto your phone and run it from there. That won't work, at least for the i545 (i.e. running it from the Terminal Emulator app will fail.)
Having troubles getting adb connected? There are several possible causes and solutions.
There are cases where people can't get the connection working unless they toggle the USB connection type from Camera to Media and back. Perhaps that may help getting it to work. Toggling the "Enable USB Debugging" apparently helps in some cases as well.
Others report that using these Samsung USB drivers resolve connectivity issues. Of course, these drivers are for Samsung phones. Install the right stuff for your phone.
Important - please read
If you fail to read this, you will be taunted.
1. You can't install custom recovery and custom ROMs on a phone with a locked bootloader. This rooting program does not unlock your bootloader and won't allow you to flash custom on a locked device. However, NOTHING allows flashing a custom recovery on a bootloader locked phone at the moment. See Safestrap for a way to install some custom ROMs.
2. Resetting the "Custom" and open padlock indication during boot can be worked around using the Xposed Framwork and Wanam Xposed. Get those two from the Play Store. In Wanam, tick "Security Hacks", "Fake System Status".
3. If Saferoot fails with the messages
"Your kernel is patched!
This device is not supported."
That means that your device's Linux kernel has been updated to keep Saferoot from working. Unless you can downgrade to an older kernel, you can't use Saferoot.
Reported Successes
Here's a list of phones and reported builds where this has been verified to work.
AT&T Galaxy Note 2 (SGH-I317), Android 4.3
AT&T Galaxy S3 (SGH-i747), MJB
AT&T Galaxy S4 (SGH-i337) MK2,MK6
AT&T Galaxy S4 zoom
Bell Mobility i337,MK6
Canadian Galaxy S4 SGH-I337M
Digicel (Jamaica) i9500, MK1
d2vzw s3 with the 4.3 update
Galaxy NX Camera, JDQ39
Galaxy Legend SCH-I200,MK2
Galaxy Note 2 GT-N7100, MK9
Galaxy Note 2 N7105 4.3
GT-I9192, MK4 (ML2 does not work)
Google Glass, (XRT73B), XR14
i605
International Galaxy S4, I9505: MH6, MH8, MJ5, MKE, MKF
I9500: MJ8, MK1
Kindle Fire HD
LG Optimus F3 - T-Mobile
LG Escape -P870 - ATT
MK4 Build Date 13.11.2013
Razr HD 9.30.1 OTA
Razr M 98.18.94,98.30.1
Samsung Exhilarate SGH-I577, Android 4.0.4, Build LH3
Samsung GT-I9192, UBUBMK4
Samsung Galaxy Tab 2 GT-P5513
Samsung Galaxy S4 Mini LTE (GT-I9195), MJ7
Samsung i547, Android 4.1.2
Sprint Galaxy S3 (SPH-L710), MK5
Sprint Galaxy S4 Mini SPH-L520
Sprint Galaxy S4 SPH-L720,MK2 (NA2 does NOT work)
Sprint Galaxy S4 (SPH-L720T), MK5
T-Mobile Galaxy S4 SGH-M919 JFLTETMO, MK2
T-Mobile Galaxy Note 2 SGH-T889, MK7
Telcel (Mexico) SGH-i337M, MK6
Telus Note 2 SGH-I317M
Verizon Galaxy Note 2 Android 4.3
Verizon Galaxy S3 I9300 - LF2
Verizon Galaxy S3 SCH-I535
Verizon Galaxy S3 Mini, SM-G730V, MI9
Verizon Galaxy S4 (SCH-i545) ME7,MJ7,MK2
Verizon Galaxy S4 (SCH-i545L) MG6, MK4
Verizon Galaxy S4 Mini SCH-I435, MK5
Verizon Galaxy S4 Developer Edition, I1545OYUAMDK
Verizon HTC One
Verizon SCH-I200PP, MK2
xt907, xt925/6 & mb866
Edits:
12/12/13: This version of the zip file includes the adb.exe so you don't need to install ADB just for this.
I've also changed it so you shouldn't have to unzip to any special place.
12/13/13: I've swapped out Superuser for SuperSU. This version also installs busybox for you once the phone finishes rebooting.
12/14/13: Fixed install of busybox. Install SuperSU as Chainfire wants it: called Superuser.apk, installed into /system/app.
12/14/13: Move "Look at your phone and give permission" message to the top of the script.
12/15/13: Update source distribution to correspond to updates.
12/16/13: Rename to saferoot as it's not just for MJ7.
12/17/13: Update to fix "text file busy" errors
12/18/13: Correct the "text file busy" fix. Force su binary to be setuid root so root checkers will work.
12/18/13: Add more help in the "install.bat" for people having troubles getting adb working
12/18/13: Ensure the folder setup is right when starting install.bat
12/18/13: Give users time to allow su permissions
12/21/13: Disable SEAndroid before rooting
12/22/13: Install selinuxoff to set SELinux to Permissive mode at boot
12/23/13: Fix permission on selinuxoff binary, update SuperSU install and clean up rooting program
12/30/13: Remove selinuxoff program - it doesn't do anything. Updates to the install scripts.
1/6/14: Hard code kernel addresses for ATT Galaxy S4 so it takes less time to root.
1/6/14: Try to work around Knox deleting the su binary
1/10/14: Clear immutable bit on existing programs to allow them to be updated
1/12/14: Update to current SuperSU binary
1/13/14: Updates suggested by @bgmg
1/16/14: Correct typo in Linux/OSX installer
1/21/14: Really correct the typo. Add OS detection to install.sh so it can run on OSX or Linux without installing adb.
1/21/14: Update to current SuperSU
2/4/14: Detect when the phone is not rooted and don't continue the rest of the operations.
3/29/14: Install 'unroot' script and add unroot.bat/unroot.sh to allow simple removal of Saferoot changes.
4/4/14: Fix problem with unroot not running
4/30/14: Clearer error messages on root fail, allow user to choose installation of busybox
5/14/14: Fix typo in Unix install script, more text on why it failed.
5/24/14: Fix install.sh portability issue with double equals on test.
Source code, Unrooting, and the Custom Flag
The source code for the exploit tool used for this rooting method is attached.
In addition, two common questions:
1. How do I unroot?
OK, so why are you so anxious to unroot just after rooting?
If you have used the current version of Saferoot to root your phone, then there's an unroot script installed to make this easy.
If you still have Saferoot unzipped, plug in your phone and use "unroot.bat" (Windows) or "unroot.sh" (Unix) to remove the changes that Saferoot made. Then, open SuperSU and instruct it to perform a "full unroot". After that, all changes that Saferoot have made to your device have been removed.
If you don't have the unroot.sh, then you can unroot manually as below.
There's two things you need to do to undo what this installer does. First, remove busybox. This will require adb shell or the use of Terminal Emulator to get a shell prompt. Execute the commands below at a shell prompt.
The "$" and "#" characters at the start of those lines are the system prompt. You don't type those.
Spacing, case, etc. matter. The letter after "type" in the "find" command is a lowercase L.
$ su
# mount -o remount,rw /system
# rm -f /system/etc/install-recovery-2.sh*
# rm -f /system/xbin/selinuxoff*
# find /system/xbin -type l | xargs rm
# rm /system/xbin/busybox
# mount -o remount,ro /system
# exit
$ exit
The easiest way to do this is to install the "Terminal Emulator" app from the Play Store. Or use "adb shell" to get a shell prompt.
You can cut and paste the following to make it easier.
su
mount -o remount,rw /system
rm -f /system/etc/install-recovery-2.sh*
rm -f /system/xbin/selinuxoff*
find /system/xbin -type l | xargs rm
rm /system/xbin/busybox
mount -o remount,ro /system
exit
exit
Click to expand...
Click to collapse
It's very likely that the "/system/xbin/selinuxoff" and "/system/etc/install-recovery-2.sh" files won't be there.
Now, open SuperSU and use "Settings", "Full unroot". When that's done, everything that this installer has done has been reverted.
If you've installed xposed framework or wanam, you should remove those and reboot BEFORE doing the SuperSU unroot. Also, if you've installed Safestrap you'll need to boot into SS recovery, delete the custom ROM slots, then uninstall Safestrap recovery. Or, uninstall the Safestrap application. If you forget to do these before doing the SuperSU unroot, you'll need to re-root to do those.
If you need adb to access your phone, there's a copy in the "files" directory included with the installer. You'll need to open a command prompt and use cd to change to the files directory before trying to use that adb.
2. How do I get rid of the "Custom" padlock open screen at boot?
You get that because you're running custom software. Samsung has an application that runs at boot to look for modified system files; this app detects that the phone has been modified and sets that flag.
If you really need to get rid of that, you can do the unroot in #1 above, then reboot. Wait about 10 minutes or so, then reboot again. If you haven't changed any other system files, the custom flag should have been reset.
If that doesn't fix it, flash the stock no-wipe ROMs from this forum. Those will undo whatever you've changed and allow the phone to reset the custom flag.
If you want to keep root while getting rid of that "Custom" flag, then you can fake it. Install xposed framework (google for it), enable it, then reboot.
Then install Wanam Xposed, and enable that module in xposed.
In Wanam, choose "Security Hacks", "Fake system status".
That will keep the "Custom" flag from appearing. This is a cosmetic fix, but it does get rid of the "Custom" screen.
Other devices?
There is really nothing specific to the I545 or MJ7 in this root tool. There's a good chance it'll work on anything currently running 4.3.
If you have success with other devices, please reply to let us know.
Im glad I could help and good work! Im sure this will work with MK2 too.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Surge1223 said:
Im glad I could help and good work! Im sure this will work with MK2 too.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yup. I'd say that it's almost certain.
Script did not work for me. I think there is a problem with the script or the zip.
Suppose there is something actually malware-ish about vroot or kingoroot, would that be something that could be "undone" so to speak by unrooting? As in, I've already rooted via both of those other methods at different times. Should I unroot to stop whatever they "may" be doing and then try and root via your method? Or is there really no point now that I'm already rooted?
Oozura said:
Script did not work for me. I think there is a problem with the script or the zip.
Click to expand...
Click to collapse
Which of the two scripts? What error did you get?
I'll be happy to fix if you'll provide some details!
I can confirm this works on ME7 just in case anyone is wondering, Im pretty sure it can easily work on any build we have so far. Might require minor modification but for the most part, this is solid.
sharkie405 said:
Suppose there is something actually malware-ish about vroot or kingoroot, would that be something that could be "undone" so to speak by unrooting? As in, I've already rooted via both of those other methods at different times. Should I unroot to stop whatever they "may" be doing and then try and root via your method? Or is there really no point now that I'm already rooted?
Click to expand...
Click to collapse
As far as lingering malware on the phone, the only thing you could do would be to flash a full-wipe factory image then root it when done.
I don't know if it's worth the hassle or no. If it was me, I'd be wiping, but I put the effort in to make this happen since I couldn't accept the closed-source risk with vroot.
sharkie405 said:
Suppose there is something actually malware-ish about vroot or kingoroot, would that be something that could be "undone" so to speak by unrooting? As in, I've already rooted via both of those other methods at different times. Should I unroot to stop whatever they "may" be doing and then try and root via your method? Or is there really no point now that I'm already rooted?
Click to expand...
Click to collapse
Sharkie, I'm new to S4, but I've been reading for decades & decades & saw a reference to a youtube video by Sgt tom (not sure of the name, but…) you can search for titles there relating to rooting S4, & it shows how you can install kingo root to obtain the exploit, do some stuff (don't recall, it may just be deleting that)… & installing Super SU in it's place or over that.
So do a little searching on root & s4 in youtube & invest some time… sorry, not sure if that was all meant for a diff version of the firmware; but it is worth looking into to use the kingo's exploit & then immediately replace it.
Don't know about the issue w/kingo is malware, or 'just' that it harvests your meid &/or other personal info, but there is a way to use it & replace it if you are OK with that approach…
Sorry I don't have specific references, but I just got into this since 'Grey Thursday' sale @ Staples, early start on Black Friday sales… hth,
oldwolf
First off... THANK YOU SO MUCH!
I did this method by putting it on my sd card... and it went through and told me to reboot. but upon reboot i have no custom splash screen and no su. i will try again tho.
I think I'm doing it wrong? Can someone help my dumb ass. Lol or I can just to adb. Either way haha.
Sent from my SCH-I545 using xda app-developers app
Craleb said:
I think I'm doing it wrong? Can someone help my dumb ass. Lol or I can just to adb. Either way haha.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Try the adb method first then if you get a failure message try the install.sh method from terminal again. After the script is done type "su". See if that works
Sent from my SCH-I545 using XDA Premium 4 mobile app
Surge1223 said:
Try the adb method first then if you get a failure message try the install.sh method from terminal again. After the script is done type "su". See if that works
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I am having the same results as the poster before you. I tried using adb method, and the prompt said adb couldn't be found.
Anybody want to confirm this works? I just updated to MK2 right now and want to try but would like another confirmation first.
Ugh I have adb setup and everything... but my freaking phone will not go into debug mode. Even after restart. I have debugging checked in dev options. It just "connected as an installer" then MTP
Sent from my SCH-I545 using xda app-developers app
Thanks for working on this. Copy of errors running script run in terminal emulator attached.
on MK2 and got the same output as Jiggity
Sent from my SCH-I545 using XDA Premium 4 mobile app
Hi guys,
I found a method to change System Status in Odin mode to 'Official/Samsung' that is very simple and only using the busybox application "devmem". Use this command in adb shell or terminal emulator. Just type it in, hit enter, and reboot. Bam.
Code:
devmem 0xF91CF8C 32 0xFF000000
This will change your status to Official and remove the padlock with 'Custom' on it. If you want 'Custom', replace FF with EE.
Immediately upon reboot, Odin mode and the device recognize the device as official.
The explanation is that this is from a small region of memory that stores what's known as DDI data. I don't know what that means yet, but some other information like the CC Mode flag and device name/product number are stored here. I'm still doing further research on what else resides here.
Enjoy.
Seem that "DDI" can be either:
A "MAC-e header parameter" as specified HERE.
Data Description Indicator (DDI):
The DDI field identifies the logical channel, MAC-d flow and size of the MAC-d
PDUs concatenated into the 3GPP associated MAC-es PDU. The mapping between the
DDI values and the logical channel ID, MAC-d flow and PDU size is provided by
higher layers. The length of the DDI field is 6 bits. When, due to the
quantization in the transport block sizes that can be supported, the size of the
data plus header is less than the TB size originally selected by the E-TFC
selection entity minus 6 bits, the DDI value [111111] shall be appended at the
end of the MAC-e header to indicate that there are no more MAC-es PDUs
concatenated into this MAC-e PDU. In any other case it will be understood that
another MAC-es PDU would not fit and it will therefore not be necessary to
reserve room in the transport block for this additional DDI field.
Click to expand...
Click to collapse
QVGA Display Driver IC (DDI) chip that incorporates QUALCOMM's Mobile Display Digital Interface (MDDI).
I'd vote its the second, as it also contain a good chunk of SRAM memory.
Couldn't get this to work. Anyone else have any luck?
coreydkoster said:
Couldn't get this to work. Anyone else have any luck?
Click to expand...
Click to collapse
What didn't work? Do you have busybox installed?
ryanbg said:
What didn't work? Do you have busybox installed?
Click to expand...
Click to collapse
I havent got it to work either. Though im guessing its only good til a reboot before it gets rewritten?
I thought I read in passing that syscope was the app that checked to see if the system was modified or not. I think it said if you get your phone to say official and freeze/uninstall syscope you won't have the padlock show up anymore.
Sent from my SM-N900V using XDA Premium HD app
Triangle away app gets rid of the padlock.
Sent from my SM-N900V using xda premium
Wanam Xposed module also can get rid of the custom status padlock also.
I get to here but not anywhere else. Am I on the right track.. If so what next?
Sent from my SM-N900V using XDA Free mobile app
---------- Post added at 06:52 AM ---------- Previous post was at 06:50 AM ----------
Sent from my SM-N900V using XDA Free mobile app
Hi
I have "blocked by cc mode" on my S7
I have TWRP installed which has a terminal. I can't use USB for anything
I try "busybox devmem..." But it comes back saying can't find /dev/mem. I'm guessing this is what's called. Do you know where I can download "mem" from please.
I need to bring my phone back to life. I can use the SD card to copy across.
Please help
Deansmithok said:
Hi
I have "blocked by cc mode" on my S7
I have TWRP installed which has a terminal. I can't use USB for anything
I try "busybox devmem..." But it comes back saying can't find /dev/mem. I'm guessing this is what's called. Do you know where I can download "mem" from please.
I need to bring my phone back to life. I can use the SD card to copy across.
Please help
Click to expand...
Click to collapse
Busybox is an app. It creates s series of links to commands that are typically available on a Linix (unix) system. Android kernel is linix based.
devmem is a command available in an adb shell or in terminal mode.
No idea if the hack still works or not.
If it does still work I am sure it would require root.
Sent from my SM-N900V using Tapatalk
donc113 said:
Busybox is an app. It creates s series of links to commands that are typically available on a Linix (unix) system. Android kernel is linix based.
devmem is a command available in an adb shell or in terminal mode.
No idea if the hack still works or not.
If it does still work I am sure it would require root.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Hi
I have root.
I have terminal and busybox, but the devmem command fails.
I can install anything on the phone using TWRP
I'll try your hack. I really hope it works. There is almost no other info on cc mode available.
Best regards
Deansmithok said:
Hi
I have root.
I have terminal and busybox, but the devmem command fails.
I can install anything on the phone using TWRP
I'll try your hack. I really hope it works. There is almost no other info on cc mode available.
Best regards
Click to expand...
Click to collapse
This is what I get running devmem
[email protected]:/ $ devmem
BusyBox v1.24.2-Stericson (2016-04-23 13:23
:09 EDT) multi-call binary.
Usage: devmem ADDRESS [WIDTH [VALUE]]
Read/write from physical address
ADDRESS Address to act upon
WIDTH Width (8/16/...)
VALUE Data to be written
1|[email protected]:/ $
To actually use it, you need to su first to get the # root prompt like this:
1|[email protected]:/ $ su
[email protected]:/ #
Then try the command /dev/mem isn't writeable by ordinary users
Sent from my SM-N900V using Tapatalk
Hi
Thanks for the "su" headup.
The problem is that I have so little installed on the phone now.
I need the dev/mem code
I even need the "su" code. At the moment it says "su not found".
So I need to install some zips. Can you suggest some for me please... I guess busybox would be one, do you know where I can get all the code for the "dev" folder please - which Zip is that?
Regards
Dean
Deansmithok said:
Hi
Thanks for the "su" headup.
The problem is that I have so little installed on the phone now.
I need the dev/mem code
I even need the "su" code. At the moment it says "su not found".
So I need to install some zips. Can you suggest some for me please... I guess busybox would be one, do you know where I can get all the code for the "dev" folder please - which Zip is that?
Regards
Dean
Click to expand...
Click to collapse
Both busybox and supersu are available in the playstore. /dev/mem is a file directory not a file, unless you are root, it's not acessible to you.
Sent from my SM-N900V using Tapatalk
donc113 said:
Both busybox and supersu are available in the playstore. /dev/mem is a file directory not a file, unless you are root, it's not acessible to you.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Hi
I have root. Thank God.
I don't have play store, but I can find the Zips and install them through TWRP.
Then I'll su and busybox that devmem command.
I'll let you know how it goes.
Regards
Deansmithok said:
Hi
I have root. Thank God.
I don't have play store, but I can find the Zips and install them through TWRP.
Then I'll su and busybox that devmem command.
I'll let you know how it goes.
Regards
Click to expand...
Click to collapse
How do you not have play store (Google Play)? They are not zips, they are apps.
Sent from my SM-N900V using Tapatalk
donc113 said:
How do you not have play store (Google Play)? They are not zips, they are apps.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Hi
I don't have the play store because I don't have android.
The apps need android, but my phone won't even boot. I have "custom rom blocked by cc mode"
Download is blocked by it too.
All I have left is TWRP in recovery mode.
Regards
I got adb shell to work. I connected to the phone...
[email protected]:/dev # ./su
[email protected]:/dev # ./mem
sh: ./mem: can't execute: Permission denied
126|[email protected]:/dev # busybox devmem
BusyBox v1.22.1 bionic (2016-08-25 18:25 -0400) multi-call binary.
Usage: devmem ADDRESS [WIDTH [VALUE]]
Read/write from physical address
ADDRESS Address to act upon
WIDTH Width (8/16/...)
VALUE Data to be written
1|[email protected]:/dev # busybox devmem 0xF91CF8C
Bus error
135|[email protected]:/dev #
Deansmithok said:
I got adb shell to work. I connected to the phone...
[email protected]:/dev # ./su
[email protected]:/dev # ./mem
sh: ./mem: can't execute: Permission denied
126|[email protected]:/dev # busybox devmem
BusyBox v1.22.1 bionic (2016-08-25 18:25 -0400) multi-call binary.
Usage: devmem ADDRESS [WIDTH [VALUE]]
Read/write from physical address
ADDRESS Address to act upon
WIDTH Width (8/16/...)
VALUE Data to be written
1|[email protected]:/dev # busybox devmem 0xF91CF8C
Bus error
135|[email protected]:/dev #
Click to expand...
Click to collapse
You just need devmem and the address. Not busybox devmem and the address.
The only thing I can suggest is that you use ODIN to flash back to whatever the latest stock ROM you were on and go through the rooting process all over again.
The bootloader won't allow you to boot with a non stock recovery unless you unlock the bootloader.
Sent from my SM-N900V using Tapatalk