Related
New 100% reliable "temp root" for Titanium Backup (won't stop working until reboot!)
Hi all,
I grew frustrated by the annoyance of losing root access randomly, when modified files on /system suddenly become inaccessible because of the S-ON lock.
But here's some good news: I came up with a way to get a 100% reliable "temp root" for Titanium Backup.
Advantages:
You will not lose root access until next reboot!
100% reliable, does not modify /system at all.
Drawbacks:
Minimalistic approach with no BusyBox.
Will only work with select root apps.
Tested with Titanium Backup only (for now).
Requirements:
Original "out of the box" Sensation or EVO 3D (untested).
Android SDK tools ("adb" command) on a computer.
USB connection between computer and phone.
Installed Superuser app from the Market.
Initial (one-time) setup:
unzip better-temp-root.zip
adb push fre3vo /data/local/tmp/
adb shell "cd /data/local/tmp ; chmod 755 fre3vo ; ./fre3vo"
adb shell "mkdir /data/bin ; mv /data/local/tmp/fre3vo /data/bin/"
adb push su /data/bin/
adb push root.sh /data/bin/
adb shell "chmod 4555 /data/bin/su ; chmod 755 /data/bin/root.sh"
adb shell "/data/bin/root.sh"
After every reboot:
adb shell "/data/bin/fre3vo"
adb shell "/data/bin/root.sh"
The advantage of this method is that /system is not modified, therefore the rooting will be totally stable and will persist until the next reboot
Q&A:
Will it work with other root apps?
This is a minimalistic approach which installs no busybox and does not touch /system, in order to be perfectly reliable. The drawback of this is that it will work only with root apps that are able to find "su" at /data/bin/su, and that don't need a busybox in $PATH. Fortunately, Titanium Backup fulfills both of these criteria. If you know other apps that do, please post about them.
Status:
Titanium Backup (free & pro): works
Root Explorer: works
MyBackup pro: works?
SetCPU: FC
Wireless tether: needs system modification
Greetings go to #teamwin for the exploit, of course.
Have fun !
Great. Good job!
Now where is that test recovery?
If it works well, maybe you should try and pass the files onto agrabren for him to implement into Fre3vo^2 (apk that makes root better like your fix is aiming to).
That way things will move a LOT faster
Using this, I can get Titanium Backup to work, but not AdFree. Might just wait for Fre3vo^2.
Adfree is build to edit files on /system partition which is not possible with temp root
Set-Cpu is working?
possible to make a script that runs
Code:
adb shell "/data/bin/fre3vo"
adb shell "/data/bin/root.sh"
at each boot automatically?
Does barnacle or any WiFi tether apps work with this? Still at work.....
Sorry for the noob question but where do unzip it to, the computer or the phone?
Sent from my PG86100 using XDA App
madindehead said:
Using this, I can get Titanium Backup to work, but not AdFree. Might just wait for Fre3vo^2.
Click to expand...
Click to collapse
Thanks for your feedback. I hadn't tested AdFree, but I'm not surprised here. This solution is a willful compromise: we refrain from modifying /system, and thus we gain 100% reliability - but at the same time we lose compatibility with some root apps, because they often rely on BusyBox being in /system (or at least in $PATH).
I have contacted @agrabren on Twitter with a link to this thread. I haven't looked into it, but if #teamwin can come up with a way to execute adb commands locally on the phone, it could all be done automatically at boot. Hopefully they'll add a configuration choice such as:
Method 1: Full compatibility with root apps, system BusyBox, "ephemeral" root
Method 2: Compatibility with *some* root apps, no system BusyBox, 100% reliable root
Let's see how it goes... but I know which method I'd personally use
Tiffany84 said:
Sorry for the noob question but where do unzip it to, the computer or the phone?
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
Unzip to the computer, you'll get 3 files. Go on from there
What about this:
Any difference to files/method from first post?
http://www.facebook.com/pages/S-Off-for-Sensation-and-Evo-3d-NOW/117107248377328?sk=wall&filter=1
joel.bourquard said:
Unzip to the computer, you'll get 3 files. Go on from there
Click to expand...
Click to collapse
Ok. So this is where I struggle with adb. So how does it know where the files are at? Do u have to tell it the location of the files or do u put it in the same directory with adb? Again, I apologize when it comes to being clueless with adb.
Sent from my PG86100 using XDA App
DomSim said:
possible to make a script that runs
Code:
adb shell "/data/bin/fre3vo"
adb shell "/data/bin/root.sh"
at each boot automatically?
Click to expand...
Click to collapse
That's the goal - but such a script would not work right now, because: (1) the 1st command terminates the current shell and (2) the 2nd command must be called through ADB.
As far as I see, the 1st command could be invoked automatically from an Android app at boot, but the 2nd one needs to be called through adb, which requires a separate computer right now.
I haven't looked into that - but I think @agrabren / #teamwin are aiming at this (ie: somehow doing the equivalent of running commands through "adb" from the device itself) with Fre3vo^2.
Thanks very much..
Sent from my HTC Sensation Z710e using XDA App
Tiffany84 said:
Ok. So this is where I struggle with adb. So how does it know where the files are at? Do u have to tell it the location of the files or do u put it in the same directory with adb? Again, I apologize when it comes to being clueless with adb.
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
Same directory
Tiffany84 said:
Ok. So this is where I struggle with adb. So how does it know where the files are at? Do u have to tell it the location of the files or do u put it in the same directory with adb? Again, I apologize when it comes to being clueless with adb.
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
I run Linux personally, but I think if you just unzip the files into some empty folder, then stay in that same folder and run ADB by its absolute path, it should work fine. Something like:
"C:\Program Files\Android SDK\BIN\ADB.EXE" push xx yy
Maybe a Windows user could give you more precise advice here...
Why would you need barnacle when you have wireless tether built in?
Sent from my HTC Sensation 4G using XDA App
With this,only run fre3vo bat file and all will install
automatically:
Ganii said:
What about this:
Any difference to files/method from first post?
http://www.facebook.com/pages/S-Off-for-Sensation-and-Evo-3d-NOW/117107248377328?sk=wall&filter=1
Click to expand...
Click to collapse
Anyone tried SetCPU ? Which profile did you select, and does it work?
Pinepig said:
Same directory
Click to expand...
Click to collapse
Thanks.
Sent from my PG86100 using XDA App
for some reason, i cannot gain permission through adb, i have tried everything. all i get is the $ sign. yes usb debugging is enabled, im running stock rom just updated with ota. i AM rooted, i have my drivers installed, idk why i cant get # via adb, someone help? any advice?
sk8dayfuknight said:
for some reason, i cannot gain permission through adb, i have tried everything. all i get is the $ sign. yes usb debugging is enabled, im running stock rom just updated with ota. i AM rooted, i have my drivers installed, idk why i cant get # via adb, someone help? any advice?
Click to expand...
Click to collapse
Follow the steps in this link: http://forum.xda-developers.com/showthread.php?t=1152148
He did an awesome job with this.
If you did follow this then you probably need to boot into recovery and change permissions settings.
when i type in su in adb i get # but when i type in adb shell i still get $, it says adb: Not found
sk8dayfuknight said:
for some reason, i cannot gain permission through adb, i have tried everything. all i get is the $ sign. yes usb debugging is enabled, im running stock rom just updated with ota. i AM rooted, i have my drivers installed, idk why i cant get # via adb, someone help? any advice?
Click to expand...
Click to collapse
i have the same issue after OTA update. root only with terminal emulator on the device. try'd to fix permission in recovery, no changes. adb shell gives me no #, only $, allways permission denied by trying su.
Edit:
it looks like that only adb can't switch the user. su_2.3.6.3_efgh is sccessfully installed via CWM 4.0.1.4 without any errors. all root apps (e.g. Titanium Backup Pro, Root Explorer, Superuser, Terminal Emulator) are working perfect. root check from market told me that adb binary is set to default shell user access as a standard non-root user. any idears?
holly1963 said:
i have the same issue after OTA update. root only with terminal emulator on the device. try'd to fix permission in recovery, no changes. adb shell gives me no #, only $, allways permission denied by trying su.
Edit:
it looks like that only adb can't switch the user. su_2.3.6.3_efgh is sccessfully installed via CWM 4.0.1.4 without any errors. all root apps (e.g. Titanium Backup Pro, Root Explorer, Superuser, Terminal Emulator) are working perfect. root check from market told me that adb binary is set to default shell user access as a standard non-root user. any idears?
Click to expand...
Click to collapse
i found i only have trouble with stock rom, i flashed leedroid rom last night and was able to get "#" with "adb shell" on the first try...
sk8dayfuknight said:
i found i only have trouble with stock rom, i flashed leedroid rom last night and was able to get "#" with "adb shell" on the first try...
Click to expand...
Click to collapse
for now i don't want to flash a custom rom, i'am using the VF stock ROM. So I still have the same issue
holly1963 said:
for now i don't want to flash a custom rom, i'am using the VF stock ROM. So I still have the same issue
Click to expand...
Click to collapse
You need to have Busybox installed.
Sent from my HTC Sensation 4G using Tapatalk
Rhiannon224 said:
You need to have Busybox installed.
Sent from my HTC Sensation 4G using Tapatalk
Click to expand...
Click to collapse
thanks for your help, busybox is successfully installed but i still can't change the user with adb
inside the trouble guide thread from the development they advice to flash a custom rom, but this is not my target.
seems the only way to get "#" from adb shell is with a custom rom. for me at least. i tried everything, changing the permissions of su, fixing permissions in recovery, and installing busybox,
When you type su are you going back to your phone and allowing super user for the unknown device? - I know that is a basic answer.
zylith said:
When you type su are you going back to your phone and allowing super user for the unknown device? - I know that is a basic answer.
Click to expand...
Click to collapse
i have thought about that method, but in the superuser.apk nothing comes up when trying to get a shell to my phone thorugh adb...
sk8dayfuknight said:
i have thought about that method, but in the superuser.apk nothing comes up when trying to get a shell to my phone thorugh adb...
Click to expand...
Click to collapse
When you're in CMD and type adb shell or su, if its the first time you should see a request to allow or deny su permission on the phone, right? Does that happen when you attempt?
Sent from my HTC Sensation Z710e
BlackElvis79 said:
When you're in CMD and type adb shell or su, if its the first time you should see a request to allow or deny su permission on the phone, right? Does that happen when you attempt?
Click to expand...
Click to collapse
there is no request on the phone, nothing happens (screen was on)
Open super user- and see if you already hit deny- You can also change it from there. Also when you type "adb devices" does your phone show up with serial number?
sk8dayfuknight said:
for some reason, i cannot gain permission through adb, i have tried everything. all i get is the $ sign. yes usb debugging is enabled, im running stock rom just updated with ota. i AM rooted, i have my drivers installed, idk why i cant get # via adb, someone help? any advice?
Click to expand...
Click to collapse
Try rooting again. Reinstall superuser.,also download busybox installer from the market and instal
Sent from my HTC Sensation Z710e using XDA App
It is not working with the stock ROM no point redoing every thing it wont work no matter how many times you try.
I doubt we will get much help it is not a problem with a custom ROM so there wont be that many peeps who will be looking into it.
Best bet it to stick a custom stock based ROM with a stock kernel.
thanks shady for the toggles and letting me use your theme. After installing boot will take approx 3-5 mins. Update superuser from the market.
Deodexed, Rooted, Overclocked, Webtop via HDMI mod, Toggles, Zipaligned.
....Flash at your own risk....
WIPE DATA/FACTORY RESET
http://depositfiles.com/files/wk7i3b1n1 <----Stock Rooted 2.3.5
http://www.mediafire.com/?rt4v29ompo3am6s <----Alt Link 2.3.5
http://www.multiupload.com/IZVCVPRNGJ <----Alt Link 2.3.5
Good luck and let me know about any issues not already covered.
ps. voice search and maps would not deodex so get them from the market.
http://forum.xda-developers.com/showthread.php?t=1385283
^--This works for us. I cant tell you how many times this has saved me from using rsd just b/c of a bootloop.
There seems to be some confusion with overclocking, If you don't understand it please read through this thread.
http://forum.xda-developers.com/showthread.php?t=1341514
___________________________________________________________________
Stock Rooted Deodxed 2.3.6
http://depositfiles.com/files/dmi40o4qx <----2.3.6
^---This is a cwm backup. You will need to wipe data/factory reset then restore the backup. Extract zip to root of sd card
________________________________
***********MD5**************
StockRootedDeodex 2.3.5 36E1DE744C0144C70AFF4BFD624BA369 *StockRootedOcWebDeodex.zip
StockRootedDeodex 2.3.6 BA6AF46EF4A2E0904422E6F73E8893AE *236_Rooted_Deodex_Do_No_Flash.rar
[Theme's]
1.) adb push framework-res.apk /mnt/sdcard
2.) adb push SystemUI.apk /mnt/sdcard
3.) adb push Settings.apk /mnt/sdcard
4.) adb push BlurPhone.apk /mnt/sdcard
5.) adb push BlurDialer.apk /mnt/sdcard
6.) adb push GoogleQuickSearchBox.apk /mnt/sdcard
7.) su
8.) mount -o rw,remount /dev/null /system
9.) cp /sdcard/framework-res.apk /system/framework
10.) cp /sdcard/SystemUI.apk /system/app (case sensitive)
11.) cp /sdcard/Settings.apk /system/app (case sensitive)
12.)cp /sdcard/BlurPhone.apk /system/app (case sensitive)
13.)cp /sdcard/BlurDialer.apk /system/app (case sensitive)
14.)cp /sdcard/GoogleQuickSearchBox.apk /system/app (case sensitive)
15.) reboot
16.) click thanks!
http://db.tt/qd0dVE0p <--Ics/Artic
Flashable Zip http://www.multiupload.com/9ANWSIAPA9
http://db.tt/21dhrctR <--ICS
Flashable Zip http://www.multiupload.com/SN3DKIIVNI
(Ports from shadys various themes)
***Wanna be sure your not going to boot loop? Make a backup and install the cwm on boot linked above. Commands are the same in recovery omitting 5&6 instead go to mounts and mount /system***
**The first 2 pictures are from Ics/artic, The last 4 pics are from ICS***
You peronally use the unofficial atrix 2 bootstrap for flashing correct?
Awesome man. I'm gonna hide in a corner and see what happens for now, but definitely exciting news.
Jimmy273 said:
You peronally use the unofficial atrix 2 bootstrap for flashing correct?
Click to expand...
Click to collapse
Yes
Everything downloaded well and is up and running!!! BTW boot took no longer than a usual boot on mine
Could you give some clarification on some of the notification drop down toggles and what they are? What is the little sun like icon and the circle arrow icon?
Will leave feedback as more proper use comes
I would guess the sun icon is brightness control and the circle arrow is sync
Sent from my MB865 using xda premium
Flashing it right now!
Jimmy273 said:
You peronally use the unofficial atrix 2 bootstrap for flashing correct?
Click to expand...
Click to collapse
Yes sir I do.
We need some step by step on how to install this ROM.
already flashed, so far so good.
Here is what i dou need to root first)
1: go here and download Bootstrap Recovery
http://forum.xda-developers.com/showthread.php?t=1346977
2: Download the rom and put it on sd card
3: install the app and boot into recovery.
4: do a backup first
5: factory reset
6: flash the rom
7: reboot!
last thing !!!!! Flash at your own risk!!!!!!!!!!
OH almost forgot. HAPPY NEW YEAR!!!!!
Just flashed so far so good
Sent from my MB865 using xda premium
What is this overclocked to and what other changes does it have. Maybe someone thats done it can do a video demonstration on youtube.
Running great so far..awesome job..thought I was gonna have to wait months for something..on point..just came reluctantly over from a g2x due to T-Mobiles lack of sympathy for the broke...any way to get instructions on how to overclock via terminal emulator?
Sent from my MB865 using xda premium
Are we able to restore Nandroid backups successfully? I read in the other thread that .img files were not present in the Nandroid backup. Has that been resolved?
devsk said:
Are we able to restore Nandroid backups successfully? I read in the other thread that .img files were not present in the Nandroid backup. Has that been resolved?
Click to expand...
Click to collapse
Yup! You can use it like you would any other cwm.
pretty much all cwm features are working, nandroid backup, restore, flash rom, wipe......
Thanks for the ROM!
So, let's see if I understand how this works: the only thing we can't do yet without unlocking the bootloader is to install a different kernel. Everything else can be changed, right?
devsk said:
Are we able to restore Nandroid backups successfully? I read in the other thread that .img files were not present in the Nandroid backup. Has that been resolved?
Click to expand...
Click to collapse
Yup! Everything restored perfectly for me...
Sent from my MB865 using xda premium
Its telling me that its at 300-1000Mhz. I don't believe its OC'd? Otherwise, LOVING it. Thanks a ton.
Sent from my MB865 using XDA App
---------- Post added at 09:40 AM ---------- Previous post was at 09:36 AM ----------
Zoide_ said:
Thanks for the ROM!
So, let's see if I understand how this works: the only thing we can't do yet without unlocking the bootloader is to install a different kernel. Everything else can be changed, right?
Click to expand...
Click to collapse
Can't flash new radios either.
Calundle said:
Its telling me that its at 300-1000Mhz. I don't believe its OC'd? Otherwise, LOVING it. Thanks a ton.
Click to expand...
Click to collapse
I think right now its not, but the scripting is there so if you want the OC you have to do it manually via terminal emulator or ADB shell.
I've had no problems as well. Cant wait to see the OC and a theme on it BTW loving the notification toggles!!! If airplane mode was included it would be set!!!
Here is a dump of my /system/app and /system/framework that is deodexed/zipaligned. Its just the directories; its not flashable in CWM. I'll try and put together a stock zip later, but I don't have time at work. If someone else wants to do it, feel free to PM me a link and I'll host it.
For now, developers will know how to use this. In addition, if you feel brave, you can use the following steps:
Prework:
Download the zip. Extract it. Copy the deodex_app and deodex_framework directories to your external SD card.
1) Boot your phone into recovery
2) Mount /system and /sdcard from the mount menu
3) adb shell rm /system/app/*.odex
4) adb shell rm /system/framework/*.odex
5) adb shell cp /sdcard/deodex_app/* /system/app/
6) adb shell cp /sdcard/deodex_framework/* /system/framework/
7) adb shell chmod 644 /system/app/*
8) adb shell chmod 644 /system/framework/*
9) Wipe Dalvik cache from the advanced menu
10) Make sure /system, /data, and /sdcard are unmounted in the mounts menu
11) Reboot. It took about 5 minutes for my phone to boot and then it said "Upgrading Android" or something like that and went through 175 apps or so.
Download here.
ROM developers, feel free to use this to base your ROMs on. Please give credit for the base source of your ROM as always.
Edit: Clarified its also zipaligned.
Awesome!! I wish I was brave enough to try this..
So rom does this mean you'll be whippin up a kernel?? : ))))))
Sent from my SAMSUNG-SGH-I727 using xda premium
pingfl00d said:
So rom does this mean you'll be whippin up a kernel?? : ))))))
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
I need the source which is not available yet. I suspect it will be shortly after this is OTA'ed. But yes, once it is, I will be updating my stock-ish
Procedure works perfectly.
At "Android is upgrading... " message now
Edit: Home button dead.
rjohnstone said:
Procedure works perfectly.
At "Android is upgrading... " message now
Edit: Home button dead.
Click to expand...
Click to collapse
My home button works fine. This seems to be a common problem if you restore with TiBu. Did you do that?
romracer said:
My home button works fine. This seems to be a common problem if you restore with TiBu. Did you do that?
Click to expand...
Click to collapse
Only user apps, no system data.
And the button worked prior to replacing files, so I'm curious what was deleted/changed that caused the button to stop working?
rjohnstone said:
Only user apps, no system data.
And the button worked prior to replacing files, so I'm curious what was deleted/changed that caused the button to stop working?
Click to expand...
Click to collapse
My guess would be something that "Android is updating..." did. I'm still not entirely sure what that is doing.
romracer said:
My guess would be something that "Android is updating..." did. I'm still not entirely sure what that is doing.
Click to expand...
Click to collapse
Most likely... no biggie.
Factory reset should take care of it.
Worst case, I have a nandroid backup.
Edit: factory reset didn't fix it... time for a restore.
I will try and add this too a zip. Thank you
EDIT:
I added this to my ROM. I am still working on ironing out all of the issues, but this helped!
http://forum.xda-developers.com/showthread.php?t=1566820
And if you want to mirror that would be amazing.
that actually worked perfectly! although you should probably add in there that people can use emmc instead of sdcard if they dont have an external card (i dont).
Thanks for this.
Sent from my SAMSUNG-SGH-I727 using xda premium
thanks
I waiting for .Zip flasheable
if you don't mind me asking, how did you come across deodexing this rom? I know others were having troubles doing so. Also how did you zipalign it? I zipaligned my leak by using rom toolbox pro, did you use the kitchen?!?!
Thanks romracer, always run into issues with the kitchen. I'm going to try your classpath includes in a sh script and see if it works where the kitchen hadn't.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2 Beta-4
mjwhirly said:
if you don't mind me asking, how did you come across deodexing this rom? I know others were having troubles doing so. Also how did you zipalign it? I zipaligned my leak by using rom toolbox pro, did you use the kitchen?!?!
Click to expand...
Click to collapse
I do most of it by hand. I'm a Linux/Windows System Administrator by day, so I'm comfortable with the command line I do use Cygwin for just about everything though rather than the Command Prompt.
promiseofcake said:
Thanks romracer, always run into issues with the kitchen. I'm going to try your classpath includes in a sh script and see if it works where the kitchen hadn't.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2 Beta-4
Click to expand...
Click to collapse
The one liner I pasted in the other thread should work for both app and framework. It has more includes in the class path than are necessary for framework, but I don't think it'll break it.
It assumes the following:
You are in a directory with app, framework, deodex_app, deodex_framework and tmp subdirectories. app and framework contain the originals from the phone. The one liner should be run from this top level directory. I'd recommend doing framework first. You'll also need to Google java.awt.jar and put it in the framework directory too. Don't upload this to your phone though, its just needed for deodex'ing.
finally abit stable with these deodexed files
flash ics leak through odin
boot into android and get past the attready2go
flash cwm through odin
copy your deodexed files to sd and boot into cwm
follow your adb commands to copy and replace
reboot
only problems were superuser being a pain to flash in cwm. someone else mentioned toggle signature verification which is just before choosing your zip to install in cwm. looks good now.
mjwhirly said:
if you don't mind me asking, how did you come across deodexing this rom? I know others were having troubles doing so. Also how did you zipalign it? I zipaligned my leak by using rom toolbox pro, did you use the kitchen?!?!
Click to expand...
Click to collapse
i think the problem most people are having isnt related to the deodexing (anymore) but trying to flash it in CWM. it seems that flashable zips are messing up everything, as i used the same files i tried flashing in a zip this way and it works now. the zip version was unusable.
quikt said:
finally abit stable with these deodexed files
flash ics leak through odin
boot into android and get past the attready2go
flash cwm through odin
copy your deodexed files to sd and boot into cwm
follow your adb commands to copy and replace
reboot
only problems were superuser being a pain to flash in cwm. someone else mentioned toggle signature verification which is just before choosing your zip to install in cwm. looks good now.
Click to expand...
Click to collapse
That's basically exactly what I did (and my phone seems stable). Thanks for typing out the parts I left out
I've always had to flash the Superuser zip twice for some reason. I just flash it twice right on top of each other (without rebooting, exiting CWM, etc). Never have any problems in the actual OS doing it that way.
Grab the official Superuser zip from goo-inside.me/superuser
THIS WILL NOT WORK WITH JELLY BEAN.
---
Here's a easy-to-use tool based on the method in this thread.
If you like this tool, please click the Thanks button!
Even better, see my signature.
DISCLAIMER: As with any rooting tool, there is some chance that something will go wrong. Use of this tool is at your own risk, and I will not be responsible if you brick your phone in the process. Although there have been zero reports of this tool breaking anyone's phone, don't run it if you aren't comfortable with the possibility of having something go wrong and having to re-Odin back to stock or worse.
Instructions:
Install the USB drivers if you don't have them already: Verizon_Wireless_I535_GSIII_Samsung_USB_Driver_v1_4_6_0.exe
Download the package and extract it somewhere (you'll need 7-Zip or some other modern compression tool) Make sure you extract all the files to a folder somewhere! Running it straight from your compression program probably won't work.
On your phone, enable installation of third-party apps (Settings --> Security --> Unknown sources, near the bottom in the "Device administration" section)
On your phone, enable USB debugging (Settings --> Developer options --> USB debugging)
On your PC, make sure you don't have any other Android devices connected, any Android emulators running, or any Android tools like PdaNet running.
Plug your phone into a USB port on your computer. For best results, use a port directly on the machine, and not a USB hub.
Double-click RootDebugfs.bat and follow the directions on the screen. Your phone will reboot 3 or 4 times during the process; just leave it plugged in. To be safe, don't switch to any other applications while the root process is running.
DOWNLOAD GS3DebugFSRoot R2 FOR US GALAXY S III VARIANTS ONLY!!!
(Released July 24, 2012)
If anything goes wrong, post here and I'll see what I can do.
Credits:
* miloj, for the debugfs root method for the Asus TF300T
* sparkym3, for his script for rooting the Asus Transformer Prime - this is a modified version of that script
* ChainsDD, for Superuser
Version History:
The most recent version is always at the top.
r2 2012-07-24
+ Changed font color to white for readability
+ Cleaned up output
+ Fixed typo in title (GSII instead of GSIII)
+ Fixed Unknown Sources/USB Debugging directions
+ Included latest version of adb from platform-tools 13, might make things more reliable
* Includes ChainsDD Superuser 3.1.3 and su binary 3.1.1
* Known to work with LF2 and LG1.
r1 2012-07-23
* Initial beta
* Includes ChainsDD Superuser 3.1.3 and su binary 3.1.1
* Works with LF2. Probably works with LG1.
Possible future features:
* APK version of the tool! I'm still not sure if this is possible - currently researching.
Sadly, I don't think this is going to happen.
* Unroot tool.
* Choice of Superuser or SuperSU.
FAQs:
Q: What versions of the stock ROM does this work with?
A: It's known to work with anything from LF2 up to LHE. It seems likely that DebugFSRoot will be able to work with any ICS ROMs. We'll have to wait and see if it works on JB or not.
Q: I'm getting an error like "adb is not recognized as an internal or external command", or "cannot stat 'su': No such file or directory". What do I do?
A: Don't run the tool straight from your compression program. Make sure to extract all the files somewhere first.
Q: Will this wipe my data?
A: Nope.
Q: How can I unroot? Will flashing a stock ROM unroot?
A: Flashing a stock ROM will unroot and also remove any modifications you made to /system.
Q: Everything seems to have worked fine, and the Superuser app shows the binary as present and working. However, none of my root apps work. What do I do?
A: This seems to happen to a very small number of people, and the cause is unknown. If this happens to you, try installing Chainfire SuperSU.
Q: Is this any better than flashing the root66 ROM?
A: The end result should be pretty much the same, but this tool is much smaller to download than the root66 ROM.
A: If you are on a phone with the stock LG1 ROM update, root66 will downgrade you to LF2, while this tool will leave your ROM alone.
Q: Is this any better than using the VRALEC boot chain method?
A: The boot chain is a little more complicated. It requires flashing two bootloaders, flashing recovery, and using Triangle Away to reset the Custom Binary Download counter. If you intend to install a custom recovery/custom ROMs anyway, it's fine and probably quicker. However, if all you want is root to run Titanium Backup or other root apps, GS3DebugFSRoot is easier.
Q: Will this increment the flash counter?
A: Not on its own. If you flash anything else after rooting, however, you might, so read up on what you're doing.
Q: Will this cause the "custom unlock" boot screen to appear?
A: In general, no. However, the spyware Samsung/Verizon included (SysScope/libcordon) is paranoid, and a lot of tweaks you can do after rooting will trigger it. If you don't want to risk getting the custom unlock screen, don't freeze any apps using Titanium Backup and generally limit your tweaking to things you could do without root.
Q: Can Samsung/Verizon block this method in the future?
Yes. It's very possible that a future OTA will patch the exploit that this tool uses. If you want to root, it's always best to do it now!
I just tried this and it appears to work. Installed Titanium Backup and SuperUser permissions were given. Thanks!
P.S.
Some of the instructions in the console app are incorrect for the location of enabling Debug Mode and Installing Unknown App Sources.
DFieldFL said:
I just tried this and it appears to work. Installed Titanium Backup and SuperUser permissions were given. Thanks!
P.S.
Some of the instructions in the console app are incorrect for the location of enabling Debug Mode and Installing Unknown App Sources.
Click to expand...
Click to collapse
Ah, I forgot to update that part in the Transformer Prime script I based this on. I'll fix it tomorrow.
Did you get the custom unlock boot screen?
Noxious Ninja said:
Ah, I forgot to update that part in the Transformer Prime script I based this on. I'll fix it tomorrow.
Did you get the custom unlock boot screen?
Click to expand...
Click to collapse
Also title says Galaxy S II not III.
Noxious Ninja said:
Ah, I forgot to update that part in the Transformer Prime script I based this on. I'll fix it tomorrow.
Did you get the custom unlock boot screen?
Click to expand...
Click to collapse
The boot screen looks the same to me.
Worked for me, thanks
Cant recognize the phone using this tool. Yet device is recognized by adb in a standalone cmd prompt..
saying "adb is not an executable file"
phantomevo77 said:
Cant recognize the phone using this tool. Yet device is recognized by adb in a standalone cmd prompt..
saying "adb is not an executable file"
Click to expand...
Click to collapse
Same thing happening to me.
EDIT: Just switched usb ports and unplugged and replugged my phone in and it worked!
If my gs3 came updated with the newest version, will this still work?
Next release will be out tonight after I test it.
DFieldFL said:
Some of the instructions in the console app are incorrect for the location of enabling Debug Mode and Installing Unknown App Sources.
Click to expand...
Click to collapse
Fixed in the next version. Also, I added those steps to the main post.
open1your1eyes0 said:
Also title says Galaxy S II not III.
Click to expand...
Click to collapse
Typo on my part. Will be fixed in the next release.
phantomevo77 said:
Cant recognize the phone using this tool. Yet device is recognized by adb in a standalone cmd prompt..
saying "adb is not an executable file"
Click to expand...
Click to collapse
I'm not sure about this one. However, I had packaged a slightly older version of adb, which could cause a difference. The next release will have the latest adb.
eakrish said:
If my gs3 came updated with the newest version, will this still work?
Click to expand...
Click to collapse
I think so, but I don't know if it's been tested. Worst case should be that it would fail when trying to copy su into /system/xbin/, and you might have to manually clean up a few things:
Code:
adb shell
[COLOR="Red"]$[/COLOR] rm /data/local/tmp
[COLOR="Red"]$[/COLOR] mv /data/local/tmp.bak /data/local/tmp
[COLOR="Red"]$[/COLOR] rm /data/local/su
[COLOR="Red"]$[/COLOR] rm /data/local/debugfs
[COLOR="Red"]$[/COLOR] rm /data/local/debugfsinput
[COLOR="Red"]$[/COLOR] exit
Really worst case is that your /system is screwed up and you have to re-flash a stock ROM with Odin, but that is highly, highly unlikely with this method.
Thanks for this awesome tool!!! Will there be a reversal to what this script does, aka, non-root to reverse changes if necessary or will that require odin flash?
It's probably possible to unroot via script. I think it might even be possible to move this into an APK and do away with adb altogether. I'll play around with it.
Is there an unroot method that's just as easy? I'd prefer not to reflash the phone to get rid of root. I guess I'm one of the oddballs here as I can care less about custom roms, I only root to be able to backup and remove bloatware.
edit: sorry I typed and posted this as others were doing the same... I couldn't delete or edit the post for a few minutes because of my newby status.
edthesped said:
Is there an unroot method that's just as easy? I'd prefer not to reflash the phone to get rid of root. I guess I'm one of the oddballs here as I can care less about custom roms, I only root to be able to backup and remove bloatware.
Click to expand...
Click to collapse
You should be able to do it via adb shell.
Code:
adb remount rw
adb shell
$ su
# rm /system/xbin/su
# exit
And then uninstall the Superuser app.
I'll try and add it to the script.
Thank You ! so much ... The tool works perfectly on my stock VZ ... Finally can get rid of all the crap that VZ puts in.
Noxious Ninja said:
It's probably possible to unroot via script. I think it might even be possible to move this into an APK and do away with adb altogether. I'll play around with it.
Click to expand...
Click to collapse
That would be awesome. It would be cool if you could make it unroot as well. Keep up the good work!
Tap'd via SGSIII(!)
CooL Very Very CooL
Thanks Noxious Ninja
eakrish said:
If my gs3 came updated with the newest version, will this still work?
Click to expand...
Click to collapse
Mine came with the update and I was able to root successfully with this tool. Very nice.