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.
Related
One Click Root & Recovery for the Epic 4G! v2.5.5 Now has ClockworkMod Redirector!
Here's a new one click root. 2.4.0 now flashes clockworkmod recovery for you. It's also a little less likely to fail, and is tested to work on Froyo.
It will also work correctly if you are on a pre-rooted kernel. It will install superuser, busybox, and clockworkmod.
http://firon.net/xda/one.click.root.exploitv2.5.5.zip
Here's 2.5.0 of the one click root, now with the clockwork redirector integrated.
I cleaned up noobnl's script a little bit and ensured that adbd would run as root when booted into recovery. Also made sure we symlinked every single applet that recovery's busybox provides.
Now the one click also avoids pushing playlogo unless it detects that you have the old joeykrim root installed, to avoid any potential issues with future froyo releases.
Linux and Mac users users chmod +x run.sh and run it
THANKS FIRON
Here's 2.2.7, that simplifies the root process thanks to the discoveries here: http://forum.xda-developers.com/showthread.php?t=800483
I also increased the timeout after running the root (fails less), moved more things to /system/xbin to reduce the risk of breaking things, and removes all the old files leftover from joeykrim's root (including his modified playlogo that runs at boot every time).
It also means your system will no longer be mounted as read-only every time you reboot and there's no more problems with jk-su overwriting your existing su binary.
1. you need samsung galaxy s drivers
32-bit drivers: http://firon.net/xda/Samsung_Mobile_Driver_V1.3.800_For_SPH-d700_Epic_4G.zip
64-bit drivers: http://firon.net/xda/usb_drivers_GalaxyS_x64.zip
2. push MENU, select Applications > Development, then enable USB debugging.
3. extract and run run.bat
4. enjoy!
v2.2.4 added busybox and the remount script and fixes sprint animation not showing
2.2.5 superuser.apk & su added!
v2.2.6 installs busybox to xbin
uninstaller http://firon.net/xda/one.click.stock.flasher.&.root.uninstaller-di18.zip
Any word on whether the OTA update (Hotspot/4G/AmazonMP3) breaks or makes this method not work?
lordcyrus said:
Any word on whether the OTA update (Hotspot/4G/AmazonMP3) breaks or makes this method not work?
Click to expand...
Click to collapse
no it doesn't break it
Gonna test this right now!
Sweet!!! Thanks!!! Going to do this after i get my epic after work.
Longest day ever!!!
OP. There is a really big step missing here. Guess what it is?
Hint: You need to have set the path in the command prompt for adb in order to work.
Fixter said:
Gonna test this right now!
Click to expand...
Click to collapse
You first Boriqua.
Fixter said:
OP. There is a really big step missing here. Guess what it is?
Hint: You need to have set the path in the command prompt for adb in order to work.
Click to expand...
Click to collapse
updated the post and dl link!
NOOB question, how do you know if your 32-bit, or 64-bit? Running Windows 7 basic on a net book.
Will this nand unlock?
vazquezcmp said:
NOOB question, how do you know if your 32-bit, or 64-bit? Running Windows 7 basic on a net book.
Click to expand...
Click to collapse
Odds are its 32 but heres how to check:
Click Start
Right Click Computer
Click Properties
Then look where it says System Type
32. Thanks man. I'm next.
Hmm.. Still not working.
Bring on the custom ROM's
Alright, well you needed to copy the folder to the Tools folder of the SDK.
I'm typically not brain dead but I'm lost
Working on Windows XP....
A) Installed the 32 bit drivers (strange that when I plug the phone into the USB cord the computer doesn't ever seem to acknowledge that I did so as it did with my BB?)
B) Tried to run the RUN and RUN 2 but I keep getting messages that no device is detected.
Obviously I'm missing something somewhere???????
jfenton57 said:
I'm typically not brain dead but I'm lost
Working on Windows XP....
A) Installed the 32 bit drivers (strange that when I plug the phone into the USB cord the computer doesn't ever seem to acknowledge that I did so as it did with my BB?)
B) Tried to run the RUN and RUN 2 but I keep getting messages that no device is detected.
Obviously I'm missing something somewhere???????
Click to expand...
Click to collapse
I'm not even seeing RUN2.
My phone went completely black. Not responding to anything.
I can see the device with adb devices and ran run.bat and then run2.bat and it rebooted the phone but I don't think I have root. How can I test it? I downloaded wireless tether and it doesn't broadcast.
GrandMstrBud said:
I can see the device with adb devices and ran run.bat and then run2.bat and it rebooted the phone but I don't think I have root. How can I test it? I downloaded wireless tether and it doesn't broadcast.
Click to expand...
Click to collapse
Download Titanium Backup.
Epic 4G All in One Root and Recovery 2.04 for Windows, Intel Mac, and Linux
***SORRY, AIO v2.04 IS CURRENTLY BROKEN FOR EB13, FIX IS COMING ASAP, USE ONE CLICK ROOT FOR NOW***
***WARNING NOT TO BE USED WITH ANY SUPPOSED LAGFIX, IT WILL SCREW UP YOUR SYSTEM AND YOU WILL NEED ODIN TO RESTORE***
OK, what started as scripts for my Mac turned out to be a big scripting project for Windows, Mac, and Linux.
This gives root and clockworkmod for all of the major operating systems.
This is like an Epic 4G swiss army knife, providing all of the basic tools in one convenient download.
These scripts give you a menu that allows you to choose between the following:
1) Simple One Click Root and ClockworkMod 2.04 - based on one click root 2.5.4 by noobnl and firon, compatible with Eclair and Froyo, ClockworkMod redirector for Froyo included
2) Andromeda Kernel 1.4.1 by noobnl - custom kernel with root, busybox and superuser, for 2.1 Eclair
3) SDX Stock App Remover 1.5 apk - back up and remove Stock Apps for rooted users
4) Wireless Tether 2.0.5-pre13 - Open source wireless tether for rooted users
5) Simple Root Uninstaller 2.04 - removes one clicks / z4root, Eclair and Froyo compatible
6) Reinstate Stock DI18 kernel for 2.1 Eclair
7) Reinstate Stock Samsung Recovery for Eclair or Froyo, uninstalls ClockworkMod and redirector
You could call this a noobnl festival for all operating systems...
PLEASE READ ALL MY NOTES BEFORE INSTALLING, I'VE FOUND LOTS OF PEOPLE HAVEN'T READ OR FOLLOW THE INSTRUCTIONS... FOR WINDOWS USERS, DRIVERS NEED TO BE INSTALLED CORRECTLY FOR THIS TO WORK.
http://dl.dropbox.com/u/500010/epic.aio.v2.04.zip
New! Now compatible with Android 2.2 Froyo, with ClockworkMod redirector included in script. Won't allow Eclair kernels or recovery to be installed on Froyo. ClockworkMod install now in Simple Root script. Wireless Tether added. Stock Samsung Recovery for Eclair and Froyo added.
NOTES: - Sorry so many in this page, but they really need to be listed Please at least read through until the end of the instructions before running this.
This is an all-in-one installer for the Epic 4G. When running this, the menu presented allows you to choose what you want to do, and does not install everything in one run. It is intended to only perform one menu item at a time.
If you just want to remove bloatware and run rooted apps, and don't intend to flash ROMs or rooted kernels, then just the Simple One Click Root will suffice by itself. This script now has a menu option to install SDX Stock App Remover, which is great at backing up and removing the Sprint bloatware. That will make it easy to bring back to stock and just remove root if it's necessary. Know what you're removing with the Stock App Remover, as removing the wrong system apps will get you into trouble!
Installing the Andromeda Kernel from this script does not require ClockworkMod Recovery. It can be uninstalled by flashing the stock kernel. The Andromeda kernel is already rooted, and does not require the one click root.
Clockwork Mod Recovery is used to flash other kernels, ROMs, and Mods. Instructions for booting into ClockworkMod are listed below. This is now installed with the Simple One Click Root, and a backup should be performed right away after installing it from the menu in ClockworkMod.
The past couple of generations of one click roots are safe with rooted kernels and ROMs, and are installed in /system/xbin, which is the last location in the path. Rooted kernels will just take precedence when installed.
Both the Simple One Click Root and the Root Uninstaller will remove the older joeykrim roots that use the hacked playlogo.
Because Superuser.apk is installed, superuser will ask permission before any program is granted root access. This is to ensure that no rogue program takes root privilege without your knowledge.
Booting into Clockwork Mod: Power down phone. Press and hold the camera button, then the volume down button, and then the power button, continuing pressure on all 3 keys until the Clockwork Mod menu appears, which will be seconds after the Samsung logo appears on the screen. The menu for Clockwork Mod Recovery has green text, instead of the blue text used by the stock Samsung recovery. Navigate up and down using the volume up and down keys, the power button goes back, and the camera button acts as enter key.
INSTRUCTIONS:
Before running, do the following on the phone from the home screen :
Press Menu > Settings > Applications > Development, and make sure USB Debugging is checked on your phone.
WINDOWS:
Samsung drivers are required:
32-bit drivers: http://firon.net/xda/Samsung_Mobile_Driver_V1.3.800_For_SPH-d700_Epic_4G.zip
64-bit drivers: http://firon.net/xda/usb_drivers_GalaxyS_x64.zip
Note: Driver installation under Windows 7 has been a pain for some, and has been the number one reason why people haven't been able to run the script successfully.
Also: DO NOT RUN run.bat as Administrator (by right clicking on the file and running as admin), the script will fail! Thanks to shepscrook for pointing this out.
Extract the zip file, and go inside the folder that was created with the same name.
Open run.bat (or just run) type in a number option, and press enter. Really easy (Hopefully ).
INTEL MAC & LINUX:
Note: Mac and Linux users may be prompted to enter administrative password, as adb server requires sudo permissions to start.
No drivers required.
Extract the zip file.
Open Terminal. Use the cd command to get to the directory. If you extracted inside the Downloads folder, it would be easy in Terminal as so:
Code:
cd ~/Downloads/epic.aio.v2.04
Now give permissions and run it:
Code:
chmod +x run.sh
./run.sh
THANKS TO FIRON FOR CODE MAKING THE SAME SCRIPT BOTH INTEL MAC AND LINUX COMPATIBLE.
After choosing the menu selection, just follow the instructions. I did try to make this very easy for you
THANKS TO NOOBNL FOR PERMISSION TO USE HIS STUFF, AND FIRON FOR HELP WITH SCRIPTING.
Other Credits:
joeykrim - original exploit
skeeterslint - busybox
koush - Clockwork Mod
These are just modifications of work already done by the aforementioned. I just had the vision to unify all of it into one master tool that can be used across all computers.
LINKS TO ORIGINAL RELEASES:
Handy if you're having trouble with this release, or just want to learn more about the originals:
One Click Root 2.5.4 by noobnl
ClockworkMod Recovery 2.5.1.0 by noobnl
Andromeda Kernel 1.4.1 by noobnl and Kernel Sources
SDX Stock App Remover 1.5 apk
VERSION HISTORY:
1.01 Added chmod to adb.lin and adb.osx to ensure that scripts work right first time, especially in linux.
1.10 Major rewrite for Mac and Linux unifying into one master script, with very generous script contribution by Firon. Scripts are now more organized and efficient. Remount now in /system/xbin. Uninstaller has rclean file that lists all files to be removed from phone, and now runs from phone to reduce visible rm failed errors. adb server now restarts after exploit, which greatly reduces chances of phone losing connection. Command line input options. Has busybox by skeeterslint. Added menu option to reboot phone.
1.11 Changed adb alias to include sudo, to prevent permission errors. Will prompt for password on first run if necessary.
1.12 Checks to make sure phone connection is seen before and after exploit, and after reboot. Thanks to Firon for the timer code. Checks to make sure Clockwork mod install reboot takes place, therefore knowing if it was properly installed. Added both methods for installing clockwork mod, and menu option to install SDX Stock App Remover 1.5 apk.
1.13 Smarter script, detecting if kernel is rooted, should eliminate problems with Clockwork Mod installs. Added Andromeda Kernel 1.4.0.
2.00 Rewritten based on One Click Root 2.4.0 by noobnl and Firon. Made compatible with 2.2 Froyo. Stock Samsung Recovery added. Added Wifi Tether. Will detect if Froyo is installed on phone and abort if trying to flash Eclair kernels or recovery.
2.01 ClockworkMod redirector by noobnl included, only installs if Froyo is detected.
2.02 Incorporated improvements from One Click Root & ClockworkMod 2.5.0 by noobnl and Firon. Includes Firon edits to ClockworkMod redirector files. Reinstating Stock Samsumg recovery will install appropriate bin for Eclair or Froyo automatically.
2.03 Fixes a couple of script errors, minor edits.
2.04 Updated to latest adb binaries, which affected linux users. Wifi tether updated to pre15. Playlogo replace fixed in batch script. Clockworkmod redirector files fixed to fit inside dk28 /system folder. More script fixes.
Bonus: Command line tools built into script:
e --runs the exploit, to get su from adb shell, if kernel isn't rooted
k --shuts down adb with adb kill-server
r --reboots the phone by starting adb server then calling adb reboot
s --restarts adb server, by first killing it, then starting it again
This can be evoked from the command line as so, saving some typing:
Windows:
Code:
run e
run k
run r
run s
Mac / Linux:
Code:
./run.sh e
./run.sh k
./run.sh r
./run.sh s
Enjoy!
Sorry no link here, it's in the sdx epic 4g developers forum, the file is about 13mb hosted on my dropbox account. I couldn't find a way to split it into just 2 files, all my archive programs only handle diskette and cd sizes.
I've been working on this for a while now, and figured I'd share it on xda now, especially since the post by mkasick here on the simpler root method inspired me to name the root and removal methods "simple".
I'm new at xda, I'm just a scripter, but any developer can take a look at the script and see it's legit.
If a moderator could unlock me to put the link directly in the post, I'd be much obliged... I do realize the need to prevent spammers.
OK, signing off, hope you all enjoy it!
DRockstar
OK, this has been updated for those interested. I know some of you have checked this out at the SDX forums. I'm still waiting for permissions to post outside links so that you can download it directly from here. Sorry for the inconvenience.
Used your root and worked flawlessly. Awesome job!!
phantomevo77 said:
Used your root and worked flawlessly. Awesome job!!
Click to expand...
Click to collapse
Thanks for letting me know that it's been useful! I spent a lot of time perfecting it.
Download link is finally up...
Thanks to the moderator for letting me know what I needed to do.
Have people used this? See, this is why there's not a huge dev pool on here...this would've came in handy if I saw this post a couple days ago :/ you should put this on the wiki for other people
Sent from my SPH-D700 using XDA App
My last post sounded mean...I meant it as people just don't appreciate some of the hard work on here
Sent from my SPH-D700 using XDA App
Very nice, works easy for me on Mac OS X.
Quick question, is it ok/safe to flash the Andromeda Kernel 1.4.0 by noobnl over the stock kernel just to compare it's battery life/performance over the stock kernel?
I'm NOT interested in flashing custom ROMS yet (and when i do i'll be sure to follow your caveats regarding removing one-clicks and such).
LordLugard said:
Very nice, works easy for me on Mac OS X.
Quick question, is it ok/safe to flash the Andromeda Kernel 1.4.0 by noobnl over the stock kernel just to compare it's battery life/performance over the stock kernel?
I'm NOT interested in flashing custom ROMS yet (and when i do i'll be sure to follow your caveats regarding removing one-clicks and such).
Click to expand...
Click to collapse
Yes, you'll be fine if you want to test out the Andromeda kernel in this release. The Root Uninstaller will remove it without problems. That is one reason I included it in this release, so you can at least try one good rooted kernel safely.
For Mac and Linux users, it is imperative to create a backup in clockwork mod before testing out any other kernels and ROMs. Windows has Odin3 for flashing a full stock system to the phone as a backup, while no alternative exists for Mac or Linux. There is a stock ROM posted by noobnl in the Epic 4G wiki, which I think is the best alternative we have right now.
Sent from my SPH-D700 using Tapatalk
I ran it all in one and it worked it seemed, however, it did not install clockwork. Worked great tho once I ran the file again and picked clockwork only.
Dulanic said:
I ran it all in one and it worked it seemed, however, it did not install clockwork. Worked great tho once I ran the file again and picked clockwork only.
Click to expand...
Click to collapse
This expects you to perform only one action at a time, and it should automatically reboot the phone.
The exception is installing the SDX Stock App Remover, which simply installs the apk to the phone. That can be removed easily like any other app.
Sent from my SPH-D700 using Tapatalk
Oh I see, I didnt quite read it right
A_Flying_Fox said:
Have people used this? See, this is why there's not a huge dev pool on here...this would've came in handy if I saw this post a couple days ago :/ you should put this on the wiki for other people
Click to expand...
Click to collapse
Yeah, I was just new to this particular forum and didn't realize what I needed to do... it is now in the wiki, so others can see it... I expect this to be very popular once people realize just what it is and how useful it can be.
Based on One Click 2.3.0?? I thought we were only at 2.2.9?
spitefulrain said:
Based on One Click 2.3.0?? I thought we were only at 2.2.9?
Click to expand...
Click to collapse
Well, firon and I worked together on script making the bash script Mac and linux compatible, and other things. Firon has been a valuable help in contributing code, he's gifted with scripting. He uploaded his changes to a 2.3.0 version in the SDX forums, but I guess that was never reflected in the official posts, or he just uploaded the changes without changing the version...
You can see here:
http://forum.sdx-developers.com/epi...ck-root-for-the-epic-4g!/msg102968/#msg102968
Edit: if you click the download link for the 2.2.9 one click root, you'll actually download 2.3.0 the original posts needs to be updated to reflect the update.
Sent from my SPH-D700 using Tapatalk
I am getting a message that says phone is offline. Its sees it but its offline. How do I make the phone online?
leebo73 said:
I am getting a message that says phone is offline. Its sees it but its offline. How do I make the phone online?
Click to expand...
Click to collapse
What OS version are you using? If Windows, have you loaded the drivers? If you're getting a message that the phone is offline, then your phone connection is not being recognized.
You do have debugging checked in the phone's application preferences?
If you're running Windows 7, drivers are a notorious pain, and they need to be installed correctly for any scripts like this to work.
Rockstar, this is a very underrated app, swiss army tool for the Epics for sure. Worked flawlessly on my sister's phone installing root, CWM, and SDK app remover. Appreciate your work ... if I get time, I might develop a simple frontend for this. You, Firon, noobnl, and mkaslick are awesome
Very nice package, downloading now. This should make it much easier to restore things back to how I like them after all the re-flashing to stock I do.
I download the OTA and the phone resets. When I get the Android updating screen, it dies on 20%... then reboots and tells me the update failed. anyone know why it's failing to update? I did freeze some apps from titanium backup.
ImYoungxD said:
I download the OTA and the phone resets. When I get the Android updating screen, it dies on 20%... then reboots and tells me the update failed. anyone know why it's failing to update? I did freeze some apps from titanium backup.
Click to expand...
Click to collapse
That is probably why. I'd recommend doing a factory reset in recovery.
ImYoungxD said:
I download the OTA and the phone resets. When I get the Android updating screen, it dies on 20%... then reboots and tells me the update failed. anyone know why it's failing to update? I did freeze some apps from titanium backup.
Click to expand...
Click to collapse
If you're running titanium then that means you're rooted, right? If you're rooted you should NOT (ie. Never) take a factory ota update. It has the potential to brick your phone.
What ota was it?
Sent from a SYNERGIZED GalaxySIII
Thats your device telling you to stay way the hell away from OTA's and revert to the dev section for your flashing needs!
I usually update my rooted transformer infinity OTAs with no problems.
Never knew rooted S3 can't update OTAs. meh.
I don't feel like flashing the phone because backing up the IMEI looks like such a pain ... Looks like I will have to look over it again.
ImYoungxD said:
I usually update my rooted transformer infinity OTAs with no problems.
Never knew rooted S3 can't update OTAs. meh.
I don't feel like unlocking the phone because backing up the IMEI looks like such a pain ... Looks like I will have to look over it again.
Click to expand...
Click to collapse
all you do is open terminal emulator, grant super user access, and type "NV Backup". I almost busted out in sweat the task was so strenuous.
droidstyle said:
all you do is open terminal emulator, grant super user access, and type "NV Backup". I almost busted out in sweat the task was so strenuous.
Click to expand...
Click to collapse
I have to start from scratch. I don't have ABD or whatever that thing was called. I'm going to try it out again some other day.
ImYoungxD said:
I have to start from scratch. I don't have ABD or whatever that thing was called. I'm going to try it out again some other day.
Click to expand...
Click to collapse
terminal is a app you download from the playstore... all you need is root access to use it.
droidstyle said:
terminal is a app you download from the playstore... all you need is root access to use it.
Click to expand...
Click to collapse
It's that simple...? never knew i can download it from the play store...
What is this whole site for? http://www.addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android/
read this thread
http://forum.xda-developers.com/showthread.php?t=1852255
I got that link in step 1.
"1. If your phone does not have Terminal Emulator installed, you will need to use ADB. Download and install the Android SDK platform-tools for your platform. This is a bit non-trivial as it requires the installation of the Android SDK, however, you can find a guide for installing adb here. After installing, open a command prompt and navigate to the "platform-tools" folder within the SDK, where adb is stored. If you need additional help on this, simply ask in this thread."
That site with the guide to install adb has terrible instructions so I gave up.
ImYoungxD said:
I got that link in step 1.
"1. If your phone does not have Terminal Emulator installed, you will need to use ADB. Download and install the Android SDK platform-tools for your platform. This is a bit non-trivial as it requires the installation of the Android SDK, however, you can find a guide for installing adb here. After installing, open a command prompt and navigate to the "platform-tools" folder within the SDK, where adb is stored. If you need additional help on this, simply ask in this thread."
That site with the guide to install adb has terrible instructions so I gave up.
Click to expand...
Click to collapse
Dude you are making this way too difficult lol...install terminal emulator from the playstore and run the nv backup command...then never worry about losing imei again.
For Terminal Emulator: The actual "beef" of the command is the "reboot nvbackup" line. Therefore, if you have Terminal Emulator installed, you can just run the command straight off your phone. Enter these two commands from the app:
Code:
su
reboot nvbackup
I had the same problem. Ended up using odin to push the latest stock software which included the update. Now to see if I still get the no sim error. Realizing after all this time I really didn't need to root.
ImYoungxD said:
I did freeze some apps from titanium backup.
Click to expand...
Click to collapse
This is without a doubt the reason the update failed (unless there are multiple reasons). If you unfreeze the apps, it should install as expected.
apacseven said:
This is without a doubt the reason the update failed (unless there are multiple reasons). If you unfreeze the apps, it should install as expected.
Click to expand...
Click to collapse
I had zero apps frozen and was unable to install the update. Pushing it via Odin was the only thing that worked for me.
mdt73 said:
I had zero apps frozen and was unable to install the update. Pushing it via Odin was the only thing that worked for me.
Click to expand...
Click to collapse
Yes it isnt the only thing that can cause an update to fail. But since he already stated that he had frozen some apps, then it is known that the check will fail and the update wont proceed.
If you don't know why it failed. download to OTA. And when it prompts you to install, say you'll do it later. Now extract the update file from your /cache/ directory. (That's where it was on Motorola's, I think its /cache/fota/ on our S3 ). Copy/move that file to the root of your SD card. Reboot into stock recovery and flash it. Watch the update when it fails it will call out specifically what went wrong. When you let the system automatically do it you don't get that luxury. If you initiate the update on your own through stock recovery though, you are granted that key piece of Intel as to what it didn't like.
Freezing anything in titanium will fail an OTA automatically. It checks system files to make sure certain ones are there, especially bloatware. Also having custom recovery will fail you.
As was said if your rooted you should never both with OTA anymore. If you're coming from a motorola like I did it is hard to grasp that at first. We needed official OTA to update the kernel. So you almost had to do it. Now though. We have an unlocked bootloader here. You can flash any kernel you feel. So OTA are meaningless for us on the S3. The devs steal all the good code and bits and put it in their ROMs and leave out the garbage. No reason to need official OTA anymore then unless you truly want to
Sent from a GlaDos Baked Potato
droidstyle said:
Dude you are making this way too difficult lol...install terminal emulator from the playstore and run the nv backup command...then never worry about losing imei again.
For Terminal Emulator: The actual "beef" of the command is the "reboot nvbackup" line. Therefore, if you have Terminal Emulator installed, you can just run the command straight off your phone. Enter these two commands from the app:
Code:
su
reboot nvbackup
Click to expand...
Click to collapse
Seriously..... That was easy lol. What's the point of step 1
Since I never read the next lines that says " If your phone is rooted and has Terminal Emulator installed, you don't need to do any of this. Simply open up the Terminal Emulator and go to step 2.", I never completed backing up the IMEI probably because I didn't know the Terminal Emulator was an playstore app.... Now I got a backup, I'm unlocked, running a custom rom. Thanks a lot man. You helped a lot.
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thanks
FNM
ImYoungxD said:
Seriously..... That was easy lol. What's the point of step 1
Since I never read the next lines that says " If your phone is rooted and has Terminal Emulator installed, you don't need to do any of this. Simply open up the Terminal Emulator and go to step 2.", I never completed backing up the IMEI probably because I didn't know the Terminal Emulator was an playstore app.... Now I got a backup, I'm unlocked, running a custom rom. Thanks a lot man. You helped a lot.
Click to expand...
Click to collapse
No prblem sir, glad to help!
HOWTO:
Use a card reader to format the micro SD card to exFAT (FAT32 or other formats does not work) in Windows. I haven't tried Linux or MacOS X, so they may not work.
Download the attached file (Root_for_ATTSG4_FM3.rar) and extract it into the root of your EXTERNAL microSD card using the card reader in Windows. (You can do the extraction using WinRAR or 7-zip).
Put the SD card back to the phone and download the Android Terminal Emulator app.
Open the Terminal Emulator app and run below 3 commands:
Code:
cd /mnt/extSdCard
./pwn
./script.sh
Then, open SuperSU and check everything looks good.
Then open a root app and it should be working properly.
Reboot your device once to confirm root is still working after reboot.
Come back to the post and press the THANKS button
Notes:
I uploaded a screenshot from the Terminal screen where the instructions are entered. Yours should be the same except you don't need to enter the "ls -l" command. It's just to show what files I have on the SD card. Ignore LOST.DIR directory.
Remove any SuperSU apps from your phone before following the above steps. script.sh installs it automatically.
You can use adb shell instead of a terminal app which is more convenient but requires Android SDK. Follow these steps only if you are about to use adb:
Download and install all Samsung Galaxy S 4 drivers from here.
Activate Developer options -> USB Debugging mode. To have the phone show the Developer options, go to Settings -> More -> About device. Tap on "Build number" 6 times.
You have to use an external SD card. No other alternative have been found yet. Using the device storage, i.e. /mnt/sdcard, or /data/local/tmp, DOES NOT work.
Warning (suggested by rushi.1986): "We have root for MF3 but we neither have a working recovery, nor an ODIN back to stock package. Be very careful what you do with your root. At this point, there is no way to recover even from a soft brick. (unless you know exactly what caused the soft brick and can correct it using adb)"
For those who do not know how to format an SD card on Windows (thanks to jee'sgalaxy):
Insert the micro SD into the computer (may have to use a reader or a micro SD adapter).
Go to "My Computer".
Right click on your SD card that showed up.
Click Format.
Choose exFAT as the format.
Click "OK".
Stopping AT&T Auto Software Update
Since AT&T just rolled out the new update (4.3), I add this short guide on how to stop it before it becomes late! Note that these steps require root, so you should follow the rooting steps first.
Download and install "App Quarantine ROOT/FREEZE" from Play Store.
Open the app and go to settings by tapping on the wrench icon at the top right of the screen.
Uncheck the "Hide system services" option.
Go back to the app and select "AT&T Software update".
Tap on the lock icon on the top right of the screen.
It may ask you to enable the USB debugging.
Feel safe from AT&T's new attack
How to get MK2 without losing root
I have tested this approach and it worked for myself. You should consider the risk of losing the root access and follow these steps on your on risk:
Root your MF3 phone using the approach described earlier in this post.
Stop AT&T from pushing the update as described above.
Install Super SU Pro. Note that this is not a free app and it is an add-on for Super SU.
Run Super SU. Go to Settings and check the "Survival Mode". If you don't have this option, probably you don't have the Pro version.
Disable your guard against the AT&T update by enabling "AT&T Software update".
Let the device update itself and hope for the best.
Don't forget to press the THANKS button.
Credits:
***Exploit adapted for AT&T by Jortex***
***Original Guide by Open1Your1Eyes0 for Verizon Galaxy S 4***
***Original Exploit by DooMLoRD***
MF3
Can't wait to try it...
Sent from my SAMSUNG-SGH-I337 using xda premium
I get permission denied. In terminal emulator I type
CD /mnt/extSdCard
./pwn
Then it says permission denied
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Billsfan99 said:
I get permission denied. In terminal emulator I type
CD /mnt/extSdCard
./pwn
Then it says permission denied
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Same here
Nick James said:
Same here
Click to expand...
Click to collapse
Sorry guys. I missed one step. You should format the external SD card to exFAT. Windows supports it.
Question
Does this mean that we can flash Google Edition rom on the MF3 AT&T S4?
Or do we have to wait until more exploits are discovered?
I was rocking GE rom until I went back to the stock Samsung ROM to SIM unlock my phone.
I got screwed by the OTA MF3 and have been following this forum everyday for a new root method.
ddslee said:
Does this mean that we can flash Google Edition rom on the MF3 AT&T S4?
Or do we have to wait until more exploits are discovered?
I was rocking GE rom until I went back to the stock Samsung ROM to SIM unlock my phone.
I got screwed by the OTA MF3 and have been following this forum everyday for a new root method.
Click to expand...
Click to collapse
This only allows you to root your device. No method to use custom ROM has been found yet.
So my phone WAS rooted, stock ROM.
I installed the OTA update on accident.
Ran the new exploit
Installed SuperSU
It asked me if I wanted to update the binary, I told it "Continue" and it comes back with "failed"
I suspect this is because of my previous root?
Nick James said:
So my phone WAS rooted, stock ROM.
I installed the OTA update on accident.
Ran the new exploit
Installed SuperSU
It asked me if I wanted to update the binary, I told it "Continue" and it comes back with "failed"
I suspect this is because of my previous root?
Click to expand...
Click to collapse
No need to install anything yourself. Uninstall everything and run SuperSU. Let it update itself. If that doesn't work, a reboot may help.
Also try to make sure that you have root.
jortex said:
No need to install anything yourself. Uninstall everything and run SuperSU. Let it update itself. If that doesn't work, a reboot may help.
Also try to make sure that you have root.
Click to expand...
Click to collapse
I never had SuperSU installed though.
You're talking about this, https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en
Right?
Nick James said:
I never had SuperSU installed though.
You're talking about this, https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en
Right?
Click to expand...
Click to collapse
Yes. It is being installed by the script.sh. You just need to update it. That's it.
jortex said:
Yes. It is being installed by the script.sh. You just need to update it. That's it.
Click to expand...
Click to collapse
I'm not following you. What do you mean I just need to update it? The script never installed it. I had t download it from the market and once I did that it asked me, upon opening it for the first time, "The SU binary needs to be updated. Continue?" and when I hit Continue it then says "If you have a custome recovery like TWRP or CWM, that can be used to (try to) install the SU binary. this is recommended for HTC devices. How would you like to install the SU binary? Normal or TWRP/CWM
I've tried both options with no luck.
When I run the exploit, it also says my device isnt supported but stays it obtained root?
Nick James said:
When I run the exploit, it also says my device isnt supported but stays it obtained root?
Click to expand...
Click to collapse
Mine said the same thing. I just kept going and typed the ./script.sh and thats it.
Nick James said:
When I run the exploit, it also says my device isnt supported but stays it obtained root?
Click to expand...
Click to collapse
That's fine. It tries several exploits. The first one does not apply to your device (SG4), but the last one does.
UPDATE: You already "obtained root". Look at the prompt which is changed from $ to #. As wahbob suggested, continue running script.sh. This file installs SuperSU for you. Then you can run it without explicitly getting it from Play Store.
jortex said:
This only allows you to root your device. No method to use custom ROM have been found yet.
Click to expand...
Click to collapse
Ahhh Thanks for the root though!
Thanks! Just tried it and I have Root again
thanks for this
Sorry for the noob question but when I run the cd/mnt/extsdcard command I get a "not found". Does anybody know what I'm doing wrong?
If I take the 4.3 update is the process to root it the same as it was on 4.2 or will we have to wait for a new way to root? I used this process previously and it worked for each update:
https://github.com/linux-shield/shield-root
Though now that there is a mapping utility I am not sure I will need to root it anymore... Depends on how good the mapping utility is.
This is not going to work unfortunately. I need to update the rooting procedure but am not really aware of how this is done on 4.3 (if anyone has pointers by the way) and the update arrived sooner than I thought. Will try to get that done quickly, please be patient in the meantime!
Great, thanks for the update. I will be sure to not even try then
Evo_Shift said:
Great, thanks for the update. I will be sure to not even try then
Click to expand...
Click to collapse
After upgrading, you should be able to fastboot flash CWM for SHIELD, and root that way.
agrabren said:
After upgrading, you should be able to fastboot flash CWM for SHIELD, and root that way.
Click to expand...
Click to collapse
Can you explain more what you mean. I know how to flash CWM but what do you mean "root that way"?
First, grab the Shield CWM image available here: http://forum.xda-developers.com/showthread.php?t=2390389 (LINK DEAD: MIRROR: http://cl.ly/2o3n3f0C0G2S)
Copy it to your Minimal ADB & Fastboot folder.
Then, boot to it via Fastboot. In other words, open a cmd window in the Minimal ADB & Fastboot folder and type:
adb reboot bootloader
fastboot boot recovery.img
Your device should reboot into CWM.
Then, grab the latest SU from here: http://download.chainfire.eu/351/
Copy the SU zip to an SD card. Choose "install ZIP from external SD" in CWM. Choose the SU zip. Let it finish, reboot and you're done!
Way too much damn work if you ask me, but made signficiantly easier thanks to the community. This was cobbled together from the various posts on the subject in xda developers. Thanks guys!
thank you shinratdr, that works perfectly.
Not sure what I did wrong here (have not seen this before myself) I installed the update, and everything seemed to work find. When I finally needed to use root it would not work, so i downloaded the root zip flashed that nothing changed.
From a terminal emulator on my shield when I enter su. I get no errors, and root does not work.
From the supercd /system/binuser app I get that su is not installed and it can't be installed.
From adb shell after entering su the prompt changes to # but noting that needs root works.
su is installed in /system/xbin and has the following permissions -rwsr-sr-x.
I am not sure what to do next.
Update
For now I am just restoring my back up of update59.
shinratdr said:
Then, boot to it via Fastboot. In other words, open a cmd window in the Minimal ADB & Fastboot folder and type:
!
Click to expand...
Click to collapse
Maybe stupid question but just download this here?
http://forum.xda-developers.com/showthread.php?p=42407269
Never really rooted something before and not really looking forward to it due to loss of warranty but I really want to use the PS3 controller
Allright, it was a pain in the *ss but my rooting method should now support 4.3:
https://github.com/linux-shield/shield-root
I have tested it on one device only so far, so unless you are a brave soul ready to take some (moderate) risk, please wait until other users report success here.
Google really tightened the security with 4.3 by introducing SELinux. It definitely makes your device safer and a side-effect of this is that root needs to be rethought. The update script provided by SuperSU told me what to do, but unfortunately my small Linux image lacked a few tools necessary for this, so I had to build static ARM binaries of these.
Of course by rooting your device you are undoing some of that well-thought security and making it more vulnerable to attacks, but you already know that. With the addition of the device mapper in OTA 63, you might want to reconsider if that was your only reason for rooting.
Enjoy and please report on your success or failure!
Gnurou said:
Allright, it was a pain in the *ss but my rooting method should now support 4.3:
https://github.com/linux-shield/shield-root
I have tested it on one device only so far, so unless you are a brave soul ready to take some (moderate) risk, please wait until other users report success here.
Google really tightened the security with 4.3 by introducing SELinux. It definitely makes your device safer and a side-effect of this is that root needs to be rethought. The update script provided by SuperSU told me what to do, but unfortunately my small Linux image lacked a few tools necessary for this, so I had to build static ARM binaries of these.
Of course by rooting your device you are undoing some of that well-thought security and making it more vulnerable to attacks, but you already know that. With the addition of the device mapper in OTA 63, you might want to reconsider if that was your only reason for rooting.
Enjoy and please report on your success or failure!
Click to expand...
Click to collapse
Worked great. Thanks
agrabren said:
After upgrading, you should be able to fastboot flash CWM for SHIELD, and root that way.
Click to expand...
Click to collapse
I can confirm that while you need to flash the stock recovery image you provided to update, after updating, I had no problem reflashing your CWM image in fastboot and then flashing SuperSU 1.65
Just posting as a follow up to my earlier post here
I had to download the superuser.zip from this Superuser page on the play store.
shinratdr said:
First, grab the Shield CWM image available here: http://forum.xda-developers.com/showthread.php?t=2390389
Click to expand...
Click to collapse
Hi guys!
Anybody know where i can grab this image above? Links seems to be dead.
Thanks!
punraz said:
Hi guys!
Anybody know where i can grab this image above? Links seems to be dead.
Thanks!
Click to expand...
Click to collapse
I hope you were able to find it. If not, I located the copy I left on my computer. Enjoy, this strategy seems to work fine with the latest update for a "quick" re-root.
http://cl.ly/2o3n3f0C0G2S
Thank you mate, all done now! Works like a charme. Greetings.