[ROOT APP] Updated: 13/09/12 - Samsung Quick Root v1.8.3 - One Click Root & UnRoot! - Galaxy S II Themes and Apps

[ROOT APP] Updated: 13/09/12 - Samsung Quick Root v1.8.3 - One Click Root & UnRoot!
Samsung Quick Root - For SAMSUNG Devices (Formerly known as S2 Root)
Here is my One Click Root and UnRoot solution for ALL SAMSUNG Devices.
It has a very nice interface and offers options to reboot your device Normally, Into Download Mode or Into Recovery Mode after Rooting.
Note: Make sure you Enable USB Debugging and Flash an Insecure Kernel before using Samsung Quick Root.
Click to expand...
Click to collapse
Enjoy!
Whats New in v1.8.3:
1. Improved: Error checking is much better with improved detection of null string entries.
2. Improved: Changed the code in the Wait For Device Dialog and improved error detection.
3. Fixed: A few bugs in the Function that writes output to the Log Window.
4. Improved: Made a few minor changes to the ADB Communication Framework.
5. Fixed: Kernel Info no longer relies on Busybox to gather the version information.
Whats New in v1.7.10:
1. Improved: Fixed a few bugs and added some new functions to the ADB Communication Framework.
2. Added: Wait For Device Dialog on application startup.
3. Changed: Added formatting to the Device Info display to make the information easier to read.
4. Fixed: A bug in the Device Info function that caused missing information or failure to display correctly in certain scenarios.
5. Optimized: Made a few changes to the code that handles removal of the 'su' and 'busybox' binaries so it runs a bit quicker.
6. Other minor bugfixes and UI improvements have also been made.
Whats New in v1.6.12:
1. Changed: Rebuilt using my ADB Communication Framework which eliminates lockups, is more reliable, stable and much quicker.
2. Added: Automatic detection of the '/system' Mount Point to potentially support other devices in the future.
3. Removed: Kernel Info button as this function was implemented elsewhere.
4. Added: Device Info button containing a more detailed view of Device, ROM and BusyBox information.
5. Optimized: Removal of su binary during 'UnRoot' is more efficient and will search and remove from: '/sbin', '/system/bin' and '/system/xbin'.
6. Optimized: Code for removing BusyBox and its symlinks during 'UnRoot' is now alot more efficient and will search and remove from: '/sbin', '/system/bin' and '/system/xbin'.
7. Changed: Replaced Superuser with SuperSU
8. Updated SuperSU and its binary to v0.93 and BusyBox binary to v1.20.2.
9. Other minor bugfixes and improvements have also been made.
Whats New in v1.5.1:
1. Changed: Tidied up User Interface and added additional reboot options which can be executed independantly of rooting.
2. Fixed: A bug in the UnRoot code that did not perform the UnRoot process after clicking Yes on the Temp Root Message Dialog.
3. Optimized: Code for removing BusyBox symlinks after removing BusyBox is now alot more efficient.
4. Added: S2 Root will now remove BusyBox and its symlinks from the '/sbin' aswell as '/system/xbin' folder if present allowing for clean up from other root methods.
5. Updated Superuser APK to v3.0.5
Whats New in v1.4.3:
1. Added: Device Manufacturer, Model and ROM Build information displayed in log when S2 Root starts.
2. Changed: Log font is now bigger and clearer.
3. Changed: Restrictions have been relaxed regarding device detection. S2 Root will now work with ALL SAMSUNG Android devices.
4. Added: A prompt on UnRooting. If TEMP ROOT is detected you now have the option to continue anyway allowing for people who Rooted with CF-ROOT as its based on an Insecure Kernel.
Whats New in v1.4.2:
1. Fixed: A bug for some locales which caused S2 Root to report No Temp Root Access even though an Insecure Kernel had been flashed.
Whats New in v1.4.1:
1. Fixed: A couple of bugs when UnRooting which caused Rooting the device again to fail.
2. Optimized: When UnRooting, BusyBox Symlinks are also removed leaving the xbin folder clean of all BusyBox traces.
3. Updated: Package now includes the latest Superuser v3.0, su binary v3.0 and BusyBox 1.19.2.
Whats New in v1.4:
1. Fixed: A couple of bugs in the Device detection routine.
2. Added: 'Tools' options to: Clear Dalvik Cache, Clear Battery Stats, Get Kernel Info from the device and Reboot the device.
3. Updated the guide in this first forum post.
Whats New in v1.3.2:
1. Fixed: A bug where Rooting would not work first time. This has now been fully tested and works first time every time!
Whats New in v1.3.1:
1. Fixed: A bug where Rooting would not work first time. Before you had to click 'Root Device' a second time for Superuser apk to install.
2. Fixed: A few bugs in the source code have been rectified.
3. Updated: 'su' Binary and 'Superuser' APK to latest versions.
Whats New in v1.2:
1. Fixed: S2 Root should now detect ALL Galaxy S II (GT-I9100) country variant devices correctly.
Whats New in v1.1:
1. Added: 'Jump To Download Mode' Button for those that cant use the 3 Button Combo or dont have a Jig to put the device into Download Mode.
2. Added: 'Don't Reboot Device When Finished' option for those that want to carry on tinkering after Rooting / UnRooting.
I am new to this! So how do I Root my device?
Note: Make sure you download and install Samsung Kies before performing any of the steps below to ensure everything goes smoothly!
Click to expand...
Click to collapse
Step 1
Download Odin3 v3.04 from HERE
Step 2
Download Insecure/Original Kernels from HERE or Latest ICS Insecure/Original Kernels from HERE
Step 3
Goto Settings > Developer options and Enable USB Debugging on your device.
Step 4
Reboot your device into Download Mode. (With Device OFF, Hold Vol Down + Home + Power) If done correctly your device should have a big Yellow Triangle in the middle of the screen with the words 'Downloading... Do not turn off target' underneath. (Or Select 'Download Mode' then press 'Execute' in Samsung Quick Root).
Step 5
Connect your device to your PC and start Odin. If you installed Samsung Kies correctly, you should see the box in the top left corner of Odin underneath where it says ID:COM should be Yellow and displaying the name of a Com Port your device is connected to.
Step 6
Check Odin's settings, Only the Auto Reboot and F. Reset Time checkboxes should be selected.
Step 7
Now press the PDA button and select the Insecure Kernel you downloaded earlier. (Note: This should be in *.tar, *.md5 or *.smd format.)
Step 8
Now press the Start button and wait for your device to reboot.
Step 9
If you have done everything correctly, you will notice a Yellow Triangle with an exclamation mark on the boot screen when the device is starting up. This indicates you are running an Insecure Kernel with Temp Root priviledges.
Step 10
When the device has finished booting, start Samsung Quick Root then press the Root Device button. Wait for the device to reboot depending on which Reboot option you selected then you are done Rooting.
Step 11
This is an OPTIONAL step but you can perform Steps 4 to 8 in this guide to flash the Original Kernel back to your device to remove the Yellow Triangle on the boot screen whilst still retaining Root Permissions.

Looks Interesting and straight to the point.

Cool thing. Exactly what I was waiting for.
How does it work and what does it change?
Edit: ah, I see... Guess it uses the same mechanism like superoneclick root? Initially read over the point that you have to flash an insecure Kernel.
Sent from my GT-I9100 using XDA App

Tested in "my" forum; runs OK.
thank you

free-sidux said:
Cool thing. Exactly what I was waiting for.
How does it work and what does it change?
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Its for devices that have had an insecure kernel flashed.
Select the reboot type on the right and simply click Root Device or UnRoot device.
The Rooting process simply installs BusyBox, su and Superuser APK.
UnRooting process will remove the above.
Sent from my GT-I9100 using Tapatalk

It runs similar to Super one click root but I used my own coding routines and made my app so its more specific to just the one device.
Sent from my GT-I9100 using Tapatalk

Ok, this is cool. I've always loved Chainfire's so timely and always-working root but your is worth a try too for me. The un-root feature is cool !
Thanks!

I'm guessing this method will increase the ROM counter. Thanks for your work.
Sent from my GT-I9100 using XDA App

drspikes said:
I'm guessing this method will increase the ROM counter. Thanks for your work.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Actually for some reason, I noticed when this app puts the phone in download mode, theres no ROM Counter. It doesnt even have any text top left of the screen, just Downloading... in the centre.
Sent from my GT-I9100 using Tapatalk

Interesting. All I want currently is root access but maintain Kies upgrade and warrantee. Is this my safest bet. Dev?
Sent from my GT-I9100 using XDA App

Actually just reread instructions. Flashing an insecure kernel is going to increase custom rom counter I think?
Sent from my GT-I9100 using XDA App

drspikes said:
Actually just reread instructions. Flashing an insecure kernel is going to increase custom rom counter I think?
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
It may do, but you can get a download mode jig. That will reset it for you whenever you like!

nothing i fiigure it out, google was my friend

I Root with "CF-Root-SGS2_XW_XEU_KE2-v3.6-CWM3.tar" I can now onRoot with this?

dbtomas said:
I Root with "CF-Root-SGS2_XW_XEU_KE2-v3.6-CWM3.tar" I can now onRoot with this?
Click to expand...
Click to collapse
I dont see why not, try UnRoot and let me know if you are sucessfull or not.
Sent from my GT-I9100 using Tapatalk

buzmay said:
how do flash an insecure kernel? dont you need to be root for that?
Click to expand...
Click to collapse
Samsungs are different from HTC. You need to download Odin which is samsungs own flashing app, then you need an insecure kernel both of which can be found in the Dev area of the forums.
Sent from my GT-I9100 using Tapatalk

lyriquidperfection said:
I dont see why not, try UnRoot and let me know if you are sucessfull or not.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
Why, is included in the zip: ABT and TOOLS

damn! is it really that simple?!?...now why did i spend so much with on the other rooting method!! is there any difference between the two? [i meant the chainfire root]

capaxdoli said:
damn! is it really that simple?!?...now why did i spend so much with on the other rooting method!! is there any difference between the two? [i meant the chainfire root]
Click to expand...
Click to collapse
Yes mine is simple! Flash insecure kernel then run S2 Root and Press Root Device. My Root method only roots the device and installs busybox. Chainfires also installs Clockworkmod Recovery.
Sent from my GT-I9100 using Tapatalk

I still don't know what an insecure kernel is! Anyway, I am rooted with CF's XWKE8, and I've that Yellow Tri..at boot up. Do I need to root with yours? It doesn't include CWM, right?

Related

[HOWTO]Root JV9 / JVO ( no custom kernel )

This has been tested on I9000BUJV9 and it's working
You'll need the following :
- Heimdall
https://github.com/downloads/Benjamin-Dobell/Heimdall/heimdall-suite-1.1.1-win32.zip
for it to work you need Microsoft Visual C++ 2010 , link in the program README
- fuguroot kernel for Heimdal
http://fugumod.org/zImage-root
- zImage from your desired firmware (extract the zImage file from the PDA.tar or the onefile firmware .tar using 7zip)
You'll need to do the following :
1. backup your files just in case , or if you're not on a clean firmware and wish to do so
2. turn your phone off and remove the battery for a few seconds
3. put the battery in and start the phone in download mode
4. connect the phone to the PC and start zadig.exe from Heimdall folder
- select options -> list all devices
- select samsung usb composite device
- select install driver and wait (select install driver anyway if warning appears)
5. exit zadig.exe and start heimdall-frontend.exe
6. browse from the kernel category and select the fuguroot kernel for Heimdall
-> the zImage-root you've downloaded previously
7. click start and wait for it to be done
DO NOT REMOVE THE USB CABLE AFTER IT'S DONE
8. right after the flashing is done you'll see the fugu bootlogo ( red fish ) and then the phone turns itself off and starts charging
AS SOON AS YOU SEE THE CHARGING BATTERY , REMOVE THE PHONE'S BATTERY AND CABLE
9. after a few seconds put the battery back in and start the phone in download mode again
10. connect the phone back to the pc and now browse from the KERNEL category to your stock zImage you've extracted from the stock firmware
11. select start again and as it completes you MAY REMOVE THE CABLE
The phone starts , and voila , superuser is there and also the phone is rooted
You may also perform a hard/factory reset as the root and superuser will still be present.
thanks to Heimdall readme file
thanks to nikademus for creating fuguroot kernel
thanks to me ^^
root I9000BUJV9 JV9
root I9000XXJVO JVO
I stopped using fuguroot since discovering it was deleting files without being upfront about it. If the author fixed that it would be great.
Sent from my GT-I9000 using XDA Premium App
can i use gingerbreak for JVO ?
gingerbreak doesn't quite work , but for JVO theres this method , theres CF-ROOT
{Angel} said:
I stopped using fuguroot since discovering it was deleting files without being upfront about it. If the author fixed that it would be great.
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
Which files does it delete and why? Is it just drexe and npsmobex? These can be restored fairly easily. If removing these is integral to gaining root, then yes, it should be noted.
Apart from fscking Kies up (which is no great loss), what else does this cause issues with?
Personally, I think fuguroot is a great tool which works faultlessly for me over JVB-JVO, but I agree file deletion should be stated somewhere in the release notes.
fauxdeluxe said:
Which files does it delete and why? Is it just drexe and npsmobex? These can be restored fairly easily. If removing these is integral to gaining root, then yes, it should be noted.
Apart from fscking Kies up (which is no great loss), what else does this cause issues with?
Personally, I think fuguroot is a great tool which works faultlessly for me over JVB-JVO, but I agree file deletion should be stated somewhere in the release notes.
Click to expand...
Click to collapse
Yes those files. Deleting them is not required for rooting which is the sole intended purpose of this kernel as per the authors description. I dont want something deleting stuff it shouldnt for no aparent reason and no disclosure. I am also uncomfortable the author has not rectified this. What else it might be doing? Catch my drift? ...otherwise this would be a very useful tool.
Sent from my GT-I9000 using XDA Premium App
myshu said:
[HOWTO]Root JV9 / JVO ( no custom kernel )
Click to expand...
Click to collapse
Not to be a douche but since when was fuguroot not a custom kernel?
Yeah this is a custom kernel, as it involves flashing a Z-Image, which is kind of misleading...
jaju123 said:
Yeah this is a custom kernel, as it involves flashing a Z-Image, which is kind of misleading...
Click to expand...
Click to collapse
I was also thinking this. To defend the OP though, I think the point is that you can flash back to stock kernel afterwards
no custom kernel as in , you don't have to stay onto a custom kernel to keep the root , once you flash back to stock kernel you can factory reset and its 100% stock but with root access
myshu said:
no custom kernel as in , you don't have to stay onto a custom kernel to keep the root , once you flash back to stock kernel you can factory reset and its 100% stock but with root access
Click to expand...
Click to collapse
Thats the case with pretty much every other custom kernel...
Sent from my GT-I9000 using XDA Premium App
On every ginger rom,flash the speedmod k13 for froyo without autoreboot,install root in the recovery options and flash any kernel you want after has always worked so far.
From the fuguroot thread. Good news?
Originally Posted by {Angel}
This should really be addressed, why is FuguRoot deleting these files in the first place?
That is a relic of fugumod, I will address that as soon as time permits.
Click to expand...
Click to collapse

[PATCH] Install Superuser, Busybox and Rooted Kernel (For Use After Obtaining S-OFF)

The first thing anyone is going to want to do once AlphaRev's S-OFF process is complete will be to get your device properly rooted within Android. I have created a simple update zip which will take care of the following for you:
Re-install the stock kernel, using a rooted ramdisk (credit jcase).
Install the Superuser app and su binary in /system/xbin.
Install and setup Busybox in /system/xbin.
Simply install this patch via CWM and reboot. From there you can proceed to run any root apps you need (such as Titanium).
rmk40 said:
The first thing anyone is going to want to do once AlphaRev's S-OFF process is complete will be to get your device properly rooted within Android. I have created a simple update zip which will take care of the following for you:
Re-install the stock kernel, using a rooted ramdisk (credit jcase).
Install the Superuser app and su binary in /system/xbin.
Install and setup Busybox in /system/xbin.
Simply install this patch via CWM and reboot. From there you can proceed to run any root apps you need (such as Titanium).
Click to expand...
Click to collapse
This the same file on Rootwiki? Or is it the same minus the kernel?
http://rootzwiki.com/showthread.php?587-ROOT-Gaining-root-after-s-off
rmk40 said:
The first thing anyone is going to want to do once AlphaRev's S-OFF process is complete will be to get your device properly rooted within Android. I have created a simple update zip which will take care of the following for you:
Re-install the stock kernel, using a rooted ramdisk (credit jcase).
Install the Superuser app and su binary in /system/xbin.
Install and setup Busybox in /system/xbin.
Simply install this patch via CWM and reboot. From there you can proceed to run any root apps you need (such as Titanium).
Click to expand...
Click to collapse
THANK YOU SO MUCH YOUR THE BEST lol
That's the method I used. Worked a treat when I found it at rootzwiki last night. Many thanks!
Sent from my ADR6350 using XDA App
Is busy box already on cm7?
Sent from my Incredible 2 using XDA Premium App
Superuser keeps force closing when I use ROM Manager or Wireless Tether.
knipp21 said:
Is busy box already on cm7?
Sent from my Incredible 2 using XDA Premium App
Click to expand...
Click to collapse
I think so. I was told not to install this patch after cm7.
MotorcycleMike said:
Superuser keeps force closing when I use ROM Manager or Wireless Tether.
Click to expand...
Click to collapse
Try going into the application menu and clear the data for superuser. Fixed my fc problems on my phone.
Sent from my ADR6350 using XDA Premium App
The attached zip goes on the root of the sd card correct? then boot into CWM and install zip?
dobosininja said:
Try going into the application menu and clear the data for superuser. Fixed my fc problems on my phone.
Sent from my ADR6350 using XDA Premium App
Click to expand...
Click to collapse
Fixed mine as well. Thanks!
bluedegeon said:
The attached zip goes on the root of the sd card correct? then boot into CWM and install zip?
Click to expand...
Click to collapse
that is correct
ltredbeard said:
that is correct
Click to expand...
Click to collapse
Thanks!
Sorry maybe this is a stupid question.. How can we use CWM to flash this .zip if CWM won't work without a root first???
demersk89 said:
Sorry maybe this is a stupid question.. How can we use CWM to flash this .zip if CWM won't work without a root first???
Click to expand...
Click to collapse
AlphaRevX patches CWM for your recovery during the S-OFF process. And even if it fails you can follow a guide posted on this forum on how to fastboot it.
I flashed this .zip through CWM and Titanium backup won't work. It's telling me that it is unable to find root. I clicked the "Problems?" button and still nothing happened. I remember with the Eris it would run the busybox after you pushed that button. I might just try to install busybox manually as described on Titanium's wiki.
Any other thoughts before I do that?
I flashed this file on my stock but rooted/soff incredible 2, and i seem to have lost root privileges. Luckyily I made a backup before I flashed this so now I'm back to my original problem, of not being able to fix permissions via rom manger because it doesn't see root.
Hey, I have S-Off and patched CWM, but when I hold down the volume button and try to power on, it goes straight to the HTC screen. What am I doing wrong? Does fastboot need to be turned off?
Sithben24 said:
Hey, I have S-Off and patched CWM, but when I hold down the volume button and try to power on, it goes straight to the HTC screen. What am I doing wrong?
Click to expand...
Click to collapse
Turn off fast boot in settings>applications. Turn off. Keep down held while powering on.
Sent from my ADR6350 using Tapatalk
Sithben24 said:
Hey, I have S-Off and patched CWM, but when I hold down the volume button and try to power on, it goes straight to the HTC screen. What am I doing wrong?
Click to expand...
Click to collapse
Menu/settings/power/uncheck fastboot
Perfect. Thanks guys!

help needed

hey ive really new to the world of android after moving from iphone and i need help. ive managed to root my phone have clockworkrecovery installed and working, but the problem comes when i try to install the liquidsmooth rom (http://forum.xda-developers.com/showthread.php?t=1911009) i clear everything but when i go to install the first part i get a status aborted status 7, please help any advice would be useful
What version of CWM do you have?
EDIT - After looking through the development thread for the ROM (which i'm going to assume you didn't) i found several mentions of your issue. The ROM devs confirmed my suspicion that the problem lies most likely in an outdated CWM recovery. Download Clockwork Rom Manager from the market and install the latest recovery version for your device, i'm going to assume its the AT&T SG3 but this is a guess since you didn't say what device you are using. Once the recovery is installed try flashing again. I'm going to make another guess and say you probably dont have a working OS on your phone either, if this is true you have 2 choices...you can either download the recovery from here CWM 6.0.1.2: http://db.tt/QHZZqecH and copy it to an external sd card and flash it from the the existing recovery OR you will have to flash a different rom that will boot up to get you to the market.
P.S. - In the future try to provide as much information as possible to help out whoever may be trying to help you. What phone you have, what rom you are on if any, what you have attempted in effort to fix the problem. The more info you give the easier it will be for someone to help you, and improve your chances of getting it fixed quickly.
http://teamw.in/project/twrp2/104
Go to this link download the recovery.img
Follow the indications. Two methods are offered to you.
Android App Install Method (Preferred):
Download the GooManager app from either location:
Market Link
Direct Download
Install the app and open it. Tap menu then hit Install OpenRecoveryScript. Tap Yes. Verify that the filename displays your device's code name and hit Yes. The file will download and your device will install the recovery automatically.
Download - Recovery Image
Method (using dd):
openrecovery-twrp-2.3.1.0-d2att.img
Download the above file.
Using adb shell or terminal emulator:
su
dd if=/sdcard/recoveryfilename.img of=/dev/block/mmcblk0p18
Make certain that you get this command right. Typing the wrong number could result in a brick!
Sent from my SGH-I747 using xda app-developers app
dntesinfrno said:
What version of CWM do you have?
Click to expand...
Click to collapse
CWM-based Recovery v5.5.0.4
Also, I know you're new around here but this kind of stuff go in Q&A. this being said, have fun flashing ROMs and kernels and be careful with what you flash. I dont think Bricking a 600$ device is so funny.
Sent from my SGH-I747 using xda app-developers app
I would have to agree with liltitiz once you get the rom going and use TWRP, the interface is much easier to use, it includes a built in file manager as well as on screen keyboard support for naming backups as you run them.
Go to this link download the recovery.img
Follow the indications. Two methods are offered to you.
Android App Install Method (Preferred):
Download the GooManager app from either location:
Market Link
Direct Download
Install the app and open it. Tap menu then hit Install OpenRecoveryScript. Tap Yes. Verify that the filename displays your device's code name and hit Yes. The file will download and your device will install the recovery automatically.
Download - Recovery Image
Method (using dd):
openrecovery-twrp-2.3.1.0-d2att.img
Download the above file.
Using adb shell or terminal emulator:
su
dd if=/sdcard/recoveryfilename.img of=/dev/block/mmcblk0p18
Make certain that you get this command right. Typing the wrong number could result in a brick!
Sent from my SGH-I747 using xda app-developers app[/QUOTE]
that seems a little to advanced for me
Lets start at the top, can you boot your phone or are you stuck with no OS currently? I'm gonna be here for a while so check back often and we can get this sorted out tonight.
liltitiz said:
Also, I know you're new around here but this kind of stuff go in Q&A. this being said, have fun flashing ROMs and kernels and be careful with what you flash. I dont think Bricking a 600$ device is so funny.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
lol thnx i will remember tips from both of u
dntesinfrno said:
Lets start at the top, can you boot your phone or are you stuck with no OS currently? I'm gonna be here for a while so check back often and we can get this sorted out tonight.
Click to expand...
Click to collapse
so your correct i have the samsung s3 i747 with rogers
after all the resets it still boots up back to the default system
i do the factory reset
cache reset
followed by the reset found under advanced
i proceed to install from zip and the LIQUIDSMOOTH JellyBean v2.0 RC5 (D2ATT) will begin followed by the error message that i spoke of earlier
i than go back and reboot
sorry for late responses im still new and have a 5 minute wait period
kul1 said:
so your correct i have the samsung s3 i747 with rogers
after all the resets it still boots up back to the default system
i do the factory reset
cache reset
followed by the reset found under advanced
i proceed to install from zip and the LIQUIDSMOOTH JellyBean v2.0 RC5 (D2ATT) will begin followed by the error message that i spoke of earlier
i than go back and reboot
sorry for late responses im still new and have a 5 minute wait period
Click to expand...
Click to collapse
Ok, go ahead to the google play store and search for clockwork rom manager, download this and install it. Once inside the app the top button will ask you to choose your device to install the latest recovery image, of course you are looking form Samsung Galaxy S3 AT&T. Once the download is complete it will automatically install, at this point you can click the reboot into recovery button and follow the OP for installing the ROM.
ROM manager for cwm recovery. You need to pay if you want touche recovery.
Or use the first method from my other post. Using goo manager from the play store to get twrp recovery. Which I prefer over cwm touch.
Either way are easy and depends only on what recovery you want
Sent from my SGH-I747 using xda app-developers app
Yes, i'm just trying to get his ROM installed then he (or she?) can experiment
dntesinfrno said:
Yes, i'm just trying to get his ROM installed then he (or she?) can experiment
Click to expand...
Click to collapse
Yup, one at a time. No offense but two sets of instructions could be confusing to a new user. Get a working phone first, then go for the tweaks and experiment....a little at a time and carefully.
Haven't heard from him (or her) in a while, hope they are too busy checking our their sweet new ROM to let me know if they got it working :laugh:
Let's hope so. One.....drawback....I guess in android is that there is usually 7 different ways to get to the same end result and that's what confuses most new users.....too many options :what:
jethro650 said:
Let's hope so. One.....drawback....I guess in android is that there is usually 7 different ways to get to the same end result and that's what confuses most new users.....too many options :what:
Click to expand...
Click to collapse
Drawback or exactly the point depending on how you look at it i suppose. Thats the beauty and challenge of open source, which is why reading and understanding what you are getting into is emphasized so much....although seemingly hopelessly sometimes.
Please read forum rules before posting
Questions go in Q&A
Thread moved
Friendly Neighborhood Moderator
dntesinfrno said:
Haven't heard from him (or her) in a while, hope they are too busy checking our their sweet new ROM to let me know if they got it working :laugh:
Click to expand...
Click to collapse
lol sorry i had just gotten home from work and somehow knocked out..i dont have any access to play store at the moment
Most custom aosp based ROM you need to flash gapps usually found in the op of the ROM thread.

How to Root stock SPH-L710 4.3

Modified Guide for easier rooting/rom installing steps:
THIS IS FOR THE STOCK SPRINT L710 4.3 OTA SYSTEM
*has been confirmed this works on the Virgin Mobile S3 L710 and the C Spire SCH-L710 running 4.3 OTA*
(if needed, samsung drivers can be found here)
Rooting files:
1st download the all in 1 root folder I put together----> S3 Root Bundle
extract the folder to your desktop (or wherever else you'd like for easy access)
Setting up your phone for rooting:
go to your phones: settings menu>more>about device...scroll down to "Build number" and tap on it several times, you will see a countdown begin that will make you a "developer"...this is necessary to engage the usb debugger mode. once it says "you're now a developer", simply press the back key and you'll see "developer options" now below "date and time".
click on it, enable usb debugging, once done, connect your phone to your computer via usb cord. once it's connected, open the extracted folder you downloaded and copy/paste the 2 following zip files to your SDCard...DO NOT EXTRACT THESE 2 FILES!!
DE-SAMSUNGNIZER_KNOX_REMOVAL_SCRIPT_V1.0 and UPDATE-SuperSU-v1.93
Flashing Custom Recovery:
once copied over, power off your phone, I usually pull the battery...once powered off, go into to download mode by holding the volume down/home and power keys. you'll see a yellow triangle screen, press volume up to proceed and leave as is! now connect the phone back to the computer and now go back to the extracted folder and run Odin 3.07
once Odin is up, it should recognize the phone by showing it's connected to COM3 (or com whatever number it reads)
now "uncheck" the auto reset option and leave "reset time" checked
now check the box PDA and then load the PDA file from the root folder named: philz_touch_6.00.8-d2spr.tar.md5
now press start...once it's finished, disconnect the phone from the computer and pull the battery
Rooting:
restart the phone by holding: volume up/home and power buttons and you'll now be in the custom recovery menu, red in color.
using touch or the volume buttons to scroll and power button to select, go to: install zip>choose zip from /storage/sdcard1>DE-SAMSUNGNIZER_KNOX_REMOVAL_SCRIPT_V1.0>Yes-install
once that's done you're going to do the same steps by going back and this time installing UPDATE-SuperSU-v1.93>yes-install...once done, reboot your phone.
once rebooted, go to the app "supersu" and then open it, choose to update SU binary "normal" and then reboot the phone 1 last time...you are now rooted!! go install rooted apps and enjoy!!
*any supersu issues during su binary update, verify via playstore that supersu is up to date*
SuperSu play store link
Custom Roms:
-the 1st 2 listed Roms are official/stable releases based on the 4.3.1 stock rom
Always perform a nandroid backup before flashing any rom files via recovery menu: backup/restore>backup to sdcard1
Cyanogenmod CM10.2 (4.3.1): video tutorial compliments of WoodenDiamond71
-you can bypass the steps in the video of editing the cm10 zip file using notepad ++ because I made/tested the zip file based on his steps and uploaded it along with the gapps zip file needed as well...follow the backing up your phone steps and then transferring the files to your phone and on
-download the needed zip files HERE
follow the video tutorial: WoodenDiamond71's video guide
Slimbean 4.3.1:
download the bundle here
-once extracted, transfer the 2 files: Slim_AIO_gapps.4.3.build.2 and Slim-d2spr-4.3.build.2.2-OFFICIAL-1742 to your sdcard
once transferred, boot into recovery via: power down, hold the volume up, home, and power button all at the same time until you have seen the blue text on the upper left of the screen
Philz recovery has an option called "CLEAN TO INSTALL A NEW ROM" under -wipe data/factory reset
-run this option and say "yes" to installing a new rom
-once wiped, go back and choose install zip>install zip from sdcard1 and flash the 2 transferred files beginning with Slim-d2spr-4.3 1st, then gapps
once reboot has finished and you signed into your accounts to initialize your phone, go to: settings>about device>build number-tap on it until you're a developer to get "developer options" and enable "android debugging". now you're ready to begin installing rooted apps, this rom will run Supersu off the playstore which I highly recommend doing before installing rooted apps.
-download Supersu, open it, update the su binary via normal, reboot once done and begin using rooted apps
Cyanogenmod CM11 (KitKat 4.4.2)-credit goes to WoodenDiamond71 (installation video)
-download the bundled folder here latest release updated in bundle 2/3/14
-once downloaded, extract it
-plug your phone into your computer and transfer the zipped CM11 nightly rom and the zipped Gapps to your sdcard
-this Rom is constantly being updated, so keep up to date by frequently checking HERE and downloading/installing the latest release (to update, simply download the latest zip file by DATE, transfer it over to your sd card and install it via Recovery menu, your phone will be as you left it, settings and all)
video available or follow written steps below link:
CM11 Installation Video Tutorial
-once transferred, boot into recovery via: power down, hold the volume up, home, and power button all at the same time until you have seen the blue text on the upper left of the screen
Philz recovery has an option called "CLEAN TO INSTALL A NEW ROM" under -wipe data/factory reset
-run this option and say "yes" to installing a new rom
once wiped, navigate to INSTALL ZIP, CHOOSE ZIP FROM /STORAGE/SDCARD1 and locate the CM11 zip 1st and flash it
once flashed, locate the gapps zip and flash it, once you have completed all the tasks reboot your phone
once reboot has finished and you signed into your accounts to initialize your phone, go to: settings>about device>build number-tap on it until you're a developer to get "developer options" and enable "android debugging". now you're ready to begin installing rooted apps, this rom uses superuser, to install/use supersu instead:
-download supersu from play store, once downloaded open it and update the su binary via normal, do not reboot yet!! go to supersu settings: under security "enable" su during boot, now reboot and supersu will be used for rooted apps instead of superuser
This is a great guide.... very easy to understand!
http://i.imgur.com/qrByUGN.jpg
Would this remove the knox bootloader so that you could install other roms?
I have a fever. And the only prescription is MORE COWBELL!
Worked like a charm, thanks for the guide. Only thing that I couldnt get to work was updating the supersu app in the play store, would it be possible to uninstall then reinstall to get the latest version or should I just leave well enough alone?
Sent from my SPH-L710 using xda app-developers app
thanks for the feedback...yes this does uninstall the knox, you're actually doing that as 1st part of the recovery menu process. as far as installing other roms, i just tweak my stock rom myself a bit and run a few rooted apps so i don't know if you can do the other roms.
also for the supersu issue, i've always had to update the app in the store the update the su binary and reboot, so yeah you can try installing it again via recovery menu and/or uninstall it manually and reinstall it with through the playstore and then attempt the su binary update, reboot and run a few rooted apps to check it...but i've never had the not updating issue, oh but i always did search for it in the playstore manually and not going to "my apps"
Will this method work for rooting the virgin mobile galaxy s3 L710?
Sent from my LG-D800 using xda app-developers app
chaz411 said:
Will this method work for rooting the virgin mobile galaxy s3 L710?
Sent from my LG-D800 using xda app-developers app
Click to expand...
Click to collapse
NO
goku2778 said:
NO
Click to expand...
Click to collapse
Actually YES on the Virgin Mobile question. And as far as Knox bootloader, that cannot be removed, ever. What is being removed/disabled are the associated apps that go with Knox.
---------- Post added at 12:27 PM ---------- Previous post was at 12:24 PM ----------
goku2778 said:
thanks for the feedback...yes this does uninstall the knox, you're actually doing that as 1st part of the recovery menu process. as far as installing other roms, i just tweak my stock rom myself a bit and run a few rooted apps so i don't know if you can do the other roms.
also for the supersu issue, i've always had to update the app in the store the update the su binary and reboot, so yeah you can try installing it again via recovery menu and/or uninstall it manually and reinstall it with through the playstore and then attempt the su binary update, reboot and run a few rooted apps to check it...but i've never had the not updating issue, oh but i always did search for it in the playstore manually and not going to "my apps"
Click to expand...
Click to collapse
Just FYI, version 1.65 is now several versions ago, most recent is 1.86 as of this writing, Chainfire has a thread here on XDA with links to a flashable zip for the newest version.
http://forum.xda-developers.com/showthread.php?t=1538053
---------- Post added at 12:37 PM ---------- Previous post was at 12:27 PM ----------
chaz411 said:
Will this method work for rooting the virgin mobile galaxy s3 L710?
Sent from my LG-D800 using xda app-developers app
Click to expand...
Click to collapse
If you want to get better, Virgin Mobile-specific answers, go to Android Forums, there is a subforum dedicated to the rooted VM SGS3:
http://androidforums.com/virgin-mobile-galaxy-s3-all-things-root/
Mr. Struck said:
Actually YES on the Virgin Mobile question. [/URL]
Click to expand...
Click to collapse
Maybe the op is not as informed or didn't want the responsibility of trying to support a device he does not own with this guide. So maybe that's why he responded no in the first place
Sent from my SPH-L710 using xda app-developers app
jbadboy2007 said:
Maybe the op is not as informed or didn't want the responsibility of trying to support a device he does not own with this guide. So maybe that's why he responded no in the first place
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Quite possible, but in that case "I don't know" would have been much better than a capitalized "no."
meant no harm by the NO but yeah as from what I've always seen it was for the sprint only. so if it in fact works, let me know and I'll add it in the initial part of the guide, along with the link posted for the update I gotta look at
Mr. Struck said:
Actually YES on the Virgin Mobile question. And as far as Knox bootloader, that cannot be removed, ever. What is being removed/disabled are the associated apps that go with Knox.
---------- Post added at 12:27 PM ---------- Previous post was at 12:24 PM ----------
Just FYI, version 1.65 is now several versions ago, most recent is 1.86 as of this writing, Chainfire has a thread here on XDA with links to a flashable zip for the newest version.
http://forum.xda-developers.com/showthread.php?t=1538053
thanks, i checked it out and updated the zip file in the download link i posted...he still even said that the playstore updating method is the best route
Click to expand...
Click to collapse
goku2778 said:
Mr. Struck said:
Actually YES on the Virgin Mobile question. And as far as Knox bootloader, that cannot be removed, ever. What is being removed/disabled are the associated apps that go with Knox.
---------- Post added at 12:27 PM ---------- Previous post was at 12:24 PM ----------
Just FYI, version 1.65 is now several versions ago, most recent is 1.86 as of this writing, Chainfire has a thread here on XDA with links to a flashable zip for the newest version.
http://forum.xda-developers.com/showthread.php?t=1538053
thanks, i checked it out and updated the zip file in the download link i posted...he still even said that the playstore updating method is the best route
Click to expand...
Click to collapse
Both methods should work. I find it is also good practice to save each download of the SuperSU .zip as they are released, just in case. His versions from 1.80 on are designed with Knox in mind, by the way, so I usually recommend that one as a good starting point if you go the route of letting Play Store do the update for you.
---------- Post added at 01:54 PM ---------- Previous post was at 01:48 PM ----------
goku2778 said:
meant no harm by the NO but yeah as from what I've always seen it was for the sprint only. so if it in fact works, let me know and I'll add it in the initial part of the guide, along with the link posted for the update I gotta look at
Click to expand...
Click to collapse
Method you posted is the exact same as what VM and Boost do to root. Only point of clarification is that the step for disabling the Knox apps is only necessary for any user who accepted the OTA to 4.3; anyone coming from 4.1.2 would not need that step, in case one of those users sees this thread and method. Otherwise good job, I always prefer more hands-on rooting methods like this as opposed to one-click type options.
Click to expand...
Click to collapse
I just ordered an S3 refurb. I'm coming from IOS, and I've got a couple of questions.
If I do an OTA update is the latest version 4.3? Also coming from IOS there were just simple one click apps to jailbreak. It seems rooting on Android is more complicated. Is there no just simple double click rooting app?
yes the latest is 4.3 and it really isn't that hard to do, the 1 click methods haven't really worked out for anyone but these methods always work best
Mr. Struck said:
goku2778 said:
Both methods should work. I find it is also good practice to save each download of the SuperSU .zip as they are released, just in case. His versions from 1.80 on are designed with Knox in mind, by the way, so I usually recommend that one as a good starting point if you go the route of letting Play Store do the update for you.
---------- Post added at 01:54 PM ---------- Previous post was at 01:48 PM ----------
Method you posted is the exact same as what VM and Boost do to root. Only point of clarification is that the step for disabling the Knox apps is only necessary for any user who accepted the OTA to 4.3; anyone coming from 4.1.2 would not need that step, in case one of those users sees this thread and method. Otherwise good job, I always prefer more hands-on rooting methods like this as opposed to one-click type options.
Click to expand...
Click to collapse
thanks for that. well I just updated my guide a bit, but it is clearly stated for the users that this is for 4.3 OTA only so I'm gonna leave it as is but if anyone does ask that, now I know. I always preferred these methods as well, but when I finally updated to 4.3 from my rooted 4.1.2, I had to use like 3 different sites to collect the working files, mainly the custom recovery. also a lot missing steps like the debugging method, some custom recoveries I even used from guides wanted a password and couldn't find the files to install. once I found all the files that worked, took me 2 mins to do lol so I shared the ease......
Click to expand...
Click to collapse
goku2778 said:
Mr. Struck said:
thanks for that. well I just updated my guide a bit, but it is clearly stated for the users that this is for 4.3 OTA only so I'm gonna leave it as is but if anyone does ask that, now I know. I always preferred these methods as well, but when I finally updated to 4.3 from my rooted 4.1.2, I had to use like 3 different sites to collect the working files, mainly the custom recovery. also a lot missing steps like the debugging method, some custom recoveries I even used from guides wanted a password and couldn't find the files to install. once I found all the files that worked, took me 2 mins to do lol so I shared the ease......
Click to expand...
Click to collapse
Again, good job! I share your pain in trying to research all this kind of stuff and having to sort through a bunch of half-truths and misinformation. Definitely nice to have access to all necessary files from one OP, really hope this gets stickied so all can see what a simple solution you have posted!
Click to expand...
Click to collapse
about to do 1 more update, I just discovered a "kinda" 1 click method using simply the recovery menu
Mave025 said:
I just ordered an S3 refurb. I'm coming from IOS, and I've got a couple of questions.
If I do an OTA update is the latest version 4.3? Also coming from IOS there were just simple one click apps to jailbreak. It seems rooting on Android is more complicated. Is there no just simple double click rooting app?
Click to expand...
Click to collapse
i just added a way of basically doing this, but again this isn't hard, takes literally a few mins if you've rooted droids before
Awesome. Thank you guys for all of your feed back and input. I just wanted to do a double check because Sprint modle number is sph-l710 and virgin mobile modle number is exactly the same "sph-l710". I'm about to use this method I'll post back to verify so the op next time will have a different response to the question next time other just straight up "NO".
Sent from my LG-D800 using xda app-developers app

P601/600 - Root / UnRoot Guide/ Recovery / And many more

P600/601 - ROOT / UNROOT GUIDE​
Summary
Root [step by step]
Install TWRP recovery [step by step]
Install Busy Box [step by step][root required]
How to unroot
Comming soon:
Flash stock kernel via Odin
Restoring your device to stock
More comming
Disclaimer:
This guide will be a kind of all-in-one reference for our devices since I can't find any similar guide like that. If you have any sugestion post in thread or send me a PM. This will trigger Knox!!!. Your warranty is void. After root there is no way back to knox count, I saw many people asking if knox can be preserved or restored, I can afirm if you dont change your motherboard you can't reset Knox count, because it's trigged by a physical part inside, it's a kind of fuse in processor that burn after you flash something not official. After you root you can't recive OTA updates, even if you unroot and restore to stock, because knox count will be trigged.
Root [step by step]
1 - Download [Look, download the cf auto root for your device]
Samsung Drivers
Odin 3.10
Cf-autoroot-P600
Cf-autoroot-P601
2 - Install Samsung USB Drivers
3 - Unzip Odin files and Cf-auto root at the same folder
4 - Put your device in download mode [power button + vol down + home] and press volume up after warning message.
5 - Connect your device using the original cable
6 - Go to odin folder and run odin as administrator
NOW BECAREFUL IF YOU DON’T KNOW WHAT YOU DOING YOU GOING TO BRICK YOUR DEVICE.
7 - In option section must be ticked JUST: auto-reboot and F.Reset Time
8 - Click on AP button and select the Cf-auto-root for your device
9 - Then Start
10 - Your device will reboot couple times and you are rooted with SuperSU.
Install TWRP Recovery [step by step]
1 - Donwload twrp (Choose one)
TWRP-2.6.3.3 (is the most stable one, thanks to 22sl22 to give me this information)
TWRP-2.7.1.1
TWRP-2.8.1
2 - Go your settings -> General -> About Phone -> Click five times on build number
3 - You have unlocked developers options and turn on
4 - Put your device in download mode [power button + vol down + home] and press volume up after warning message.
5 - Connect your device using the original cable
6 - Go to odin folder and run odin as administrator
7 - Click on AP and select twrp-recovery that you downloaded
8 - If the md5 check is ok, then press START
9 - Good you installed the twrp recovery
Install Busy Box [step by step][root required]
1 - Download and install Busybox on Rails from market
2 - Grant root access and then click on Install
How unroot (Thx to Orion116)
1 - Open SuperSU app and go to configuration tab
2 - Go to cleaning section
3 - Select "complete remove root"
4 - Confirm
Credits:
@Chainfire
@Orion116
 @22sl22
Thanks to Samsung and odindownload websites for the files
reserved for me
another reserve for future FAQ
Can you add link for TWRP 2.6.3.
Sent from my SM-P600 using XDA Free mobile app
Orion116 said:
Can you add link for TWRP 2.6.3.
Sent from my SM-P600 using XDA Free mobile app
Click to expand...
Click to collapse
Here,
Thank you someone was looking for that version of TWRP and couldn't find it. So I figured this would be a good place for me to send him.
Sent from my SM-P600 using XDA Free mobile app
Orion116 said:
Thank you someone was looking for that version of TWRP and couldn't find it. So I figured this would be a good place for me to send him.
Sent from my SM-P600 using XDA Free mobile app
Click to expand...
Click to collapse
I'm curious, why you wanted this version of recovery? Is it more stable than 2.8 version for our devices?
Erai Dev. said:
I'm curious, why you wanted this version of recovery? Is it more stable than 2.8 version for our devices?
Click to expand...
Click to collapse
In some circumstances, yes. 2.6.3.3 is considered the most stable TWRP version because others have issues. Some people might not have issues on newer versions but a lot of people do, the most prominent issue is wiping cache, it gets stuck on most versions except for 2.6.3.3, that's why I still use that version as well :good:
If 2.8 works for you though then thats fine, it's just that 2.6.3.3 is the most stable
Erai Dev. said:
I'm curious, why you wanted this version of recovery? Is it more stable than 2.8 version for our devices?
Click to expand...
Click to collapse
This is the thread I am referring to http://forum.xda-developers.com/showthread.php?t=2977061. So I figured having a more stable recovery was required. I use TWRP 2.8.1 my old s3 d2lte. It works fine there but for our tablet some have issues with anything newer the 2.6.3. That is why I requested that version.
Sent from my SCH-R530U using XDA Free mobile app
| After you root you can't recive OTA updates, even if you unroot and restore to stock, because knox count will be trigged. |
Fair warning, but, I rooted the device last December. I did a factory reset and flashed back to unrooted stock a couple months later. I have received three OTA updates since.
Sent from my SM-N910V using XDA Free mobile app
mignone said:
| After you root you can't recive OTA updates, even if you unroot and restore to stock, because knox count will be trigged. |
Fair warning, but, I rooted the device last December. I did a factory reset and flashed back to unrooted stock a couple months later. I have received three OTA updates since.
Sent from my SM-N910V using XDA Free mobile app
Click to expand...
Click to collapse
Flash updates firmware from Sammobile.Com with Obin?
Sent from my SM-P600 using XDA Free mobile app
I m using 2.8.0 of twrp on my p601 and having no problems at all
SM-P601 cihazımdan Tapatalk kullanılarak gönderildi
Bump for people looking for help.
Sent from my SM-P600 using XDA Free mobile app
Does the cf-autoroot depend on the stock android version? Can I apply the autoroot for P600 to my Android 4.4.2 tablet?
Thanks, Thomas
murmlgrmpf said:
Does the cf-autoroot depend on the stock android version? Can I apply the autoroot for P600 to my Android 4.4.2 tablet?
Thanks, Thomas
Click to expand...
Click to collapse
Download the newest version of CF-Autoroot for are device and try. It should work on any version of KK.
Sent from my SCH-R530U using XDA Free mobile app
Thanks, but do I need to install TWRP Recovery and busybox?
All I need is to get access to write and erase on the sd card. So do I still need to install twrp and busybox?.
rirawin said:
Thanks, but do I need to install TWRP Recovery and busybox?
All I need is to get access to write and erase on the sd card. So do I still need to install twrp and busybox?.
Click to expand...
Click to collapse
Not if you don't want.
Sent from my SM-P600 using XDA Free mobile app
Orion116 said:
Not if you don't want.
Sent from my SM-P600 using XDA Free mobile app
Click to expand...
Click to collapse
Can I ask what are the benefits of installing twrp and busybox?
anyone please?
TWRP is a custom recovery that will let you flash custom ROM's
rirawin said:
anyone please?
Click to expand...
Click to collapse
Or you can flash other files with it like custom versions of apps and interfaces, like Dark Google play store or even custom keyboards that might not be able to be installed normally.
BUSYBOX is an interface that allows UNIX commands to run inside the Android environment further enhancing the Super user capabilities. I hope this helps.

Categories

Resources