Related
Three new tools have been released or updated by their developers recently that may have a major impact on how we root and flash our phones. I will need to update the Guides with the new information, but first some confirmations are needed.
1) Chainfire has released a tool called Mobile Odin which will flash roms from the phone. There are two versions, Mobile Odin Pro which is available on the market for a small fee, and Mobile Odin Lite which is available free to xda members. Quoting from his thread: Flashing with Mobile ODIN does NOT increase your custom kernel flash counter or make the yellow warning triangle appear. This tool was updated today (November 28, 2011) to work with a host of new phones, including SGH-I777.
2) DooMLoRD has released DooMLoRD's Easy Rooting Toolkit (zergRush Exploit) which is reported to allow permanant rooting of our SGH-I777 phone without installing a custom kernel. This was most recently updated on November 16, 2011.
3) CLShortFuse developed SuperOneClick Root over a year ago, and recently updated it (November 10, 2011) to include the ZergRush exploit and SU 3.0.
With these tools, if they work as advertised on our phone, it will be possible to root and install custom software without incrementing the flash counter. When you have used one or more of these tools, I would appreciate it if you would post your results back here in this thread so I can gather information to update the [GUIDE] How to Flash Custom Binaries Without Ever Incrementing the Flash Counter!!
Thanks.
I have used the new version of SuperOneClick with the zergRush exploit to successfully root my SG2. However I will mention that the Unroot feature of SuperOneClick did not work. I simply used the unroot script DooMLoRD provided in his thread and I was able to unroot successfully. I am currently still unrooted as I have a business app I have to run that will not if it detects root. However, I assume either SuperOneClick or DooM's script will work once again if needed.
Will any of these tools reset flash counter and warning sign on already rooted phone?
I rooted without knowing these problems. Now I'm stuck with it.
Jig may or may not work, so didn't even try yet.
lambition said:
Will any of these tools reset flash counter and warning sign on already rooted phone?
I rooted without knowing these problems. Now I'm stuck with it.
Jig may or may not work, so didn't even try yet.
Click to expand...
Click to collapse
No. At some point we may figure it out to reset it through software, but until then only jigs reset the counter.
Sent from my páhhōniē
I recently noticed after flashing to UnNamed that the caution sign didn't appear. Has the ROM been developed to not trigger it or does it have to do with using the jig? I bought a jig a month ago from mobiletechvideo and I've only used it once. I've flashed CM7, Galnet MIUI and UnNamed since with no caution sign.
These tools will probably provide a new way to flash custom software without incrementing the flash counter. None of them will remove the warning triangle or reset the flash counter, however.
The only two ways to remove the warning triangle, and get the AT&T boot screen back, are 1) jig and 2) flash a stock kernel with Odin or Heimdall.
The only known way to reset the flash counter is with a jig.
The only thing that causes the I9100 boot screen with the warning triangle and increments the flash counter is flashing a custom kernel with Odin or Heimdall. So, you can flash with adb or Android Terminal Emulator or ClockworkMod Recovery, or appearantly with the new Mobile Odin, without incrementing the flash counter.
I'm definitely interested in hearing about peoples results using these tools. That is the main purpose of this thread. Thanks.
I used the DooMLoRD method, which is really easy, and it's been working for several weeks with no issues. I haven't needed to unroot, so haven't tried that yet.
[Edit] I haven't tried flashing a new rom, so I can't comment on the flashing without triangle. I just wanted root for a couple small issues, I'm going to wait to start flashing until some stable releases of ICS start appearing.
I've used SuperOneClick with Zerg to root, then installed Entropy's Daily Driver through Android Terminal then flashed UnNamed through CWM all without tripping any counters.
Love it!
So just confirming, when I get my S II, using your earlier guide that's a sticky, I'll be able to not increment the flash counter AT ALL (flashing Entropy's kernel through adb, then flashing the unNamed Rom via CWM, and also flashing the su package for root)?
Or should I wait a week or so for you to possibly update your guide, with an even more idiot-proof process?
Thanks again!
Thanks for sharing
avidmovies said:
So just confirming, when I get my S II, using your earlier guide that's a sticky, I'll be able to not increment the flash counter AT ALL (flashing Entropy's kernel through adb, then flashing the unNamed Rom via CWM, and also flashing the su package for root)?
Or should I wait a week or so for you to possibly update your guide, with an even more idiot-proof process?
Thanks again!
Click to expand...
Click to collapse
The guide is still good. I'd like to provide all the options though.
At this point, it is clear that rooting with either SuperOneClick or ZergRush will be part of step 2 in the guide, and may be easier than using Odin or Heimdall.
Still waiting for any information on Mobile Odin. If it's easy to use on our phones, it may be an improvement over steps 3 and 4.
Thanks!
Sent from my Nexus S 4G using Tapatalk
Used the zergrush root and then mobile odin to set my friends sgsii up with unnamed and icsrewed theme. Worked great without one issue.
Sent from my páhhōniē
gr8hairy1 said:
Used the zergrush root and then mobile odin lite to set my friends sgsii up with unnamed and icsrewed theme. Worked great without one issue.
Sent from my páhhōniē
Click to expand...
Click to collapse
Did you use lite or pro?
Could you describe using Mobile Odin, setting it up, how the flashkernel works, etc?
I downloaded the zergrush root package from the op. Then went to (edit):
http://forum.xda-developers.com/showthread.php?t=1347899
and downloaded mobile Odin lite.
First downloaded Samsung kies for the proper drivers then downloaded and opened zergrush. When you first open zergrush by opening 'run me' (i think it was called) it will tell you everything you need to have already done before plugging in your phone. It recommends changing your screen timeout to 10. I'm guessing this is for adb use, as adb can not connect to your phone if the screen is off.
I then plugged the phone in and pressed a key for it to start. All in all it took around 5 minutes. Majority of the time was processes coming up that waited 40 seconds. Guessing the phone was doing things that you couldn't see. At no time did I need to press anything on the keyboard or phone.
After that was done I opened mobile Odin lite. It gives you the choice of downloading the file you need or cancel. I already had the kernel I was going to flash, entropy512's dd, but I clicked download file just in case out would load the file for me. Well it didn't. It took my browser to:
http://forum.xda-developers.com/showthread.php?t=1347899
That's great for most users but I already had the zImage I wanted. I hit the back arrow which took me to a black screen, guessing mobile Odin. Hit back again and was at my home screen. Reopened mobile Odin, and after a few tries found out you need to hit cancel to continue on.
That gives you this screen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After that:
The only main option is kennel, and that's all I neededafter choosing it I got:
It was stored on the root of my internal sdcard, so I selected internal and then seen:
It obviously automatically put the kernel at the top by itself. Picked it and then had:
Chose flash kernel, rebooted the phone, and it was done. Downloaded unnamed, used three button hold to get into recovery, sure enough CWM was there, chose unnamed. Rebooted and viola, custom rom. Through this whole process the boot screen never changd to i9100 with the yellow exclamation point or was the flash counter tripped.
Sent from my páhhōniē
(yeah, I typed that all on my phone, talk about a sore hand)
I guess after you open Odin, you pour a Guinness , then download the file you need or cancel?
@gr8hairy1
Nice write up. Very useful. I'll probably get a chance to install this and play around with it tomorrow. Couple questions though.
gr8hairy1 said:
I downloaded the zergrush root package from the op. Then went on the android market and downloaded mobile Odin lite.
Click to expand...
Click to collapse
Did you download the lite version from the market? I only see the pro version on the market, and Chainfire's thread also indicates to download the lite version from his thread.
...
After that was done I opened mobile Odin lite. It gives you the choice of downloading the file you need or cancel. I already had the kernel I was going to flash, entropy512's dd, but I clicked download file just in case it would load the file for me. Well it didn't. It took my browser to:
http://forum.xda-developers.com/showthread.php?t=1347899
That's great for most users but I already had the zImage I wanted. I hit the back arrow which took me to a black screen, guessing mobile Odin. Hit back again and was at my home screen. Reopened mobile Odin, and after a few tries found out you need to hit cancel to continue on...
Click to expand...
Click to collapse
Do you know what Chainfire means in his Mobile Odin thread by flashkernels? Did you have to download one? From your write up, it sounds like you didn't and Entropy's kernel flashed fine.
Thanks.
iainash said:
I guess after you open Odin, you pour a Guinness , then download the file you need or cancel?
Click to expand...
Click to collapse
Yeah buddy! Need to put that step in there.
Though I'm a yengling fan
Edit: lol, just seen my guinness spelling error. Nice to know swype appreciates a good beer
Sent from my páhhōniē
creepyncrawly said:
@gr8hairy1
Nice write up. Very useful. I'll probably get a chance to install this and play around with it tomorrow. Couple questions though.
Did you download the lite version from the market? I only see the pro version on the market, and Chainfire's thread also indicates to download the lite version from his thread.
Do you know what Chainfire means in his Mobile Odin thread by flashkernels? Did you have to download one? From your write up, it sounds like you didn't and Entropy's kernel flashed fine.
Thanks.
Click to expand...
Click to collapse
You're right, I downloaded it from xda. Not sure how I got that mixed up. I'll update my post. Though I had taken a vicodin, alieve, and 2 benedryl around 1am, and it was almost 2am when I posted that. Stupid butt surgery is kicking my butt.
And correct, I did not download his flashkernel. I was tempted to flash it to check out what it did but it wasn't my phone I was working on. I stuck with flashing what I knew would get me cwm, and flashed Entropy512's kernel. Flashed with no issue.
Sent from my páhhōniē
creepyncrawly said:
2) DooMLoRD has released DooMLoRD's Easy Rooting Toolkit (zergRush Exploit) which is reported to allow permanant rooting of our SGH-I777 phone without installing a custom kernel. This was most recently updated on November 16, 2011.
Click to expand...
Click to collapse
First I wanted to say THANK YOU for all your help. I was able to follow your guide to flash my phone with out incrementing the flash counter.
But before I did that I did try DoomLoRD root fix. It worked as advertised and was exactly how the instructions were documented. I had no issues.
Again big thanks to you for all your help!
Unlocking, rooting, relocking and unrooting simplified! (and much more!)
VERSION 2.1.4 - This program will automatically bring together all the files you need to unlock and root your device in a few clicks, or flash it back to stock and re-lock it. You can also use this program to backup/restore all your important data, flash zips, set file permissions, push and pull files, install apps, generate logcats/bugreports, and much more! With the included file association options, you can perform tasks like flashing zips, installing apps, restoring android backup files, and flashing/booting img files with just a double click! The program includes a full featured interface for automating tasks in TWRP, enhanced restore features, an in-built auto-updater/notification system, ‘any build’ mode, advanced restore features,’NRT- Live Log’ for viewing the adb/fastboot cmds that are run in the background, quick tools utilities, and tools for taking screenshots/screen-recordings. All the latest official Android builds and Nexus devices are supported. The program intelligently and selectively downloads the files it needs for your device and makes sure you are using the latest files available. The program can even auto-detect your device and build. This release brings full Marshmallow root support plus all automated features by utilizing a new system that no longer requires modified boot.imgs. Check out the updated changelog for a more comprehensive breakdown of the feature set and changes in this release.
~ my goal for this project is make the entire process as smooth and simple as possible ~
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please read the FAQs before posting questions: http://www.wugfresh.com/nrt/faqs/
Looking for a walk-through? >> Excellent Instructional/How-To Videos: http://www.wugfresh.com/videos/
More information & Download Links: http://www.wugfresh.com/nrt/
Changelog: http://www.wugfresh.com/nrt/changelog/
Enjoy! ^_^
{{ WugFresh }}
Does automatically install Clockwork recovery?
danthepan124 said:
Does automatically install Clockwork recovery?
Click to expand...
Click to collapse
I believe it flashes TWRP recovery. Thats what I got from reading the change log here http://www.wugfresh.com/nrt/changelog/
Great job this looks awesome thank you for putting this together!
danthepan124 said:
Does automatically install Clockwork recovery?
Click to expand...
Click to collapse
If you check the "flash custom recovery" checkbox under root, then yes.. however it defaults to flash TWRP, unless the user selects CWM in the options menu:
It also will take care of renaming the system files to ensure its sticks, and it will install the busybox installer (free) app by Stericson.
{{ WugFresh }}
Nice. Will be nice to have this as a backup option . Definitely easier to use in terms of UI thank the Nexus 4 Root toolkit by mskip heh.
That backup option - is there a way, once unlocked and rooted, to grab my apps from the backup that were wiped, but not the entire thing? I downloaded about 8GB of apps before rooting, so I have no way to backup, I think. :[
Alright did it, rooted. Used the backup option a couple times trying to get it to work all the way, but for some reason, it only backed up about half of my apps.
The best rooting kit in the land
Sent from my Nexus 4 using xda premium
been waiting for this since the release of nexus 4, much thanks!
I've just added this toolkit to the Nexus 4 Complete Index
Sent from my GT-I9100 using xda premium
Just unlocked and rooted my N4 with this... great piece of software as always Wug, thanks Donated you some cash.
Hey guys quick two questions:
1) When I was unrooting through this toolkit, it said that there were three files that were not found in the directory, but continued to go through the process regardless, and it appears that I was successful. I can't remember the names as the command prompt ended before I had the chance to screenshot it. Am I okay?
2) If I go through the unrooting process through this toolkit, and then the OEM Lock process, does that basically put my phone back to the way it was when I received it?
Thanks!
Thanks for this, while I know my way around the manual commands okay, this will make everything a breeze for me tomorrow when my Nexus 4 arrives.
Will turn on, get the newest OTA, then unlock and root with your app.
Out of interest, can you still get OTA updates on stock with a custom recovery installed, or do you need to keep the stock recovery? I plan on sticking with stock until the custom ROMs get more stable, so I will stay on a default recovery if I can't use OTA updates. Otherwise I'll just flash a custom recovery with your app and get it done for future use.
This might be a dumb question.. But can I use this to root my Nexus 4 without unlocking the bootloader (thus wiping data)? Or has there not been a way found to do that yet?
BraydenJames said:
This might be a dumb question.. But can I use this to root my Nexus 4 without unlocking the bootloader (thus wiping data)? Or has there not been a way found to do that yet?
Click to expand...
Click to collapse
Have to unlock 1st. Just back up everything to your pc and restore it after.
Was waiting for this, thanks!
Sent from my Nexus 7
Night Galaxy said:
Hey guys quick two questions:
1) When I was unrooting through this toolkit, it said that there were three files that were not found in the directory, but continued to go through the process regardless, and it appears that I was successful. I can't remember the names as the command prompt ended before I had the chance to screenshot it. Am I okay?
2) If I go through the unrooting process through this toolkit, and then the OEM Lock process, does that basically put my phone back to the way it was when I received it?
Thanks!
Click to expand...
Click to collapse
1.) Yes, those are sig files. They are always missing. For whatever reason google doesn't include sig files in their packages and fastboot still checks for them. I guess google doesn't bother because they are redundant considering you need to be unlocked flash stock with fastboot. I can't suppress that output, so it just always will say that.. no worries.
2.) Yes, not basically.. exactly. Everything will be wiped, and you device will be exactly as it was when you received it.
{{ WugFresh }}
Audioboxer said:
Thanks for this, while I know my way around the manual commands okay, this will make everything a breeze for me tomorrow when my Nexus 4 arrives.
Will turn on, get the newest OTA, then unlock and root with your app.
Out of interest, can you still get OTA updates on stock with a custom recovery installed, or do you need to keep the stock recovery? I plan on sticking with stock until the custom ROMs get more stable, so I will stay on a default recovery if I can't use OTA updates. Otherwise I'll just flash a custom recovery with your app and get it done for future use.
Click to expand...
Click to collapse
No, you need the stock recovery. That said, in advanced utilities of the toolkit their is a button just for restoring stock recovery, so you can just do that if you want to when an OTA comes out (assuming you didn't make any other big system mods) if you had previously flashed a custom recovery. Also.. you can use temp recovery whenever you want as long as you have access to a computer with the toolkit.
{{ WugFresh }}
im having trouble unrooting my device....i get to the part where it says press ok to install please be patient, and then a command pops up but nothing happens, it just stays there...
edit: i keep getting to the Flash stock and Unroot screen, but nothing happens at that point! help!
Are these the steps to unlock and root and be able to receive OTA updates?
1. Click on "Full Driver Installation Guide"
2. Connect phone to computer
3. Click on Unlock
4. Click on Root and leave "Custom Recovery" box unchecked.
Then, after OTA updates are installed, re-click "Root" since OTA update will unroot?
This technique will not work if you have applied the OTA update from 18January2012. Go here: http://forum.xda-developers.com/showthread.php?t=2118348
This device is now unlocked to the point of development board status. After you finish this process, you will have the ability to destroy your device so make sure you flash CAREFULLY. Using only the files in this guide, there is no way to brick your device. Stay away from Odin once you've finished this process unless you're flashing back to stock.
TLDR version: Put your device into USB Debug Mode. Run CASUAL Injection 9. Flash the Suck It Verizon Bootloader with Odin3 If CASUAL calls you a Noob, flash the PIT and Bootloader Baseline package with Odin.
Introduction
The instructions have changed DRAMATICALLY since initial release. It's super simple. You are expected to be stock running I605VRALJB version of software. If you have modified your device using another procedure previous to this, undo it. This is where you start.
Prerequisites
any I605VRALJB stock bootloader and a stock ROM or a rooted stock ROM.
Downloads (in the order you need them)
The Pit File This is the stock i605VRALJB Pit file. It works to make your device partitions stock again. Flashing this will prepare your device for unlock.
The Bootloader Baseline package - Odin Package This is a stock I605VRALJB bootloader, params, kernel and recovery. Flashing this will prepare your device for unlock and relock your device in a safe manner. *This will reset your device if you screw up during the process so you can start over.
Odin3 is a tool from Samsung used to flash Odin packages.
CASUAL Suck It Verizon Injection 9 CASUAL stands for Cross-Platform ADB Scripting Universal Android Loader. In this case, it deploys the Suck It Verizon exploit. To use CASUAL you must enable "Settings>Developer Options>USB Debugging" on your device. CASUAL is used as an automation tool so that you don’t have to use ADB, watch for results, upload files, download files, make decisions and enter commands. CASUAL will make those determinations for you. This guide is much shorter because of it. Source code for CASUAL can be found at http://android-casual.googlecode.com. The exploit was designed by Ralekdev, packaged, tested and made safe by AdamOutler. --DON'T MIRROR, this is in development.
Suck It Verizon Bootloader 2- Odin Package provides a bootloader which has been modified to ignore all security checks at the highest level possible. This firmware runs every time you turn on your device. The SBoot's job is to validate Download Mode flashes. It also validates and executes the kernel. This bootloader will not validate, only download and execute. It will also allow you to flash anything you like, including firmware packages which will destroy your device. This bootloader replacement is not only a Bootloader Unlock, this is an IROM Unlock... The lowest level unlock possible. The bootloader was developed by Ralekdev, conceptualized by Rebellos, tested and packaged with a Sprint GN2 TWRP Recovery by AdamOutler.
Instructions
If these instructions dont quite make sense, check out the video below.
Part 1: Install the Baseline
Launch Odin or click the "reset" button at the bottom if it's already open.
Place the sch-i605-16gb.pit into the "PIT" section of Odin.
Place BootloaderBaseline2.tar.md5.gz into the "Bootloader" section of Odin.
Click Start
Part 2: Run the CASUAL Exploit
Put your device into development mode. Settings>Developer Options>USB Debugging
You need Java installed to double-click or run with "java -jar path_to_file.jar" Do you have java?
Click the "Root and Unlock Me Now!" button and accept( or continue) any notifications which may pop up on the phone or CASUAL.
When prompted by the phone, press the Volume Up key then continue to Part 2.
Part3: Install Suck It Verizon Insecure Bootloader+Recovery
Start Odin or click the "reset" button at the bottom if it's already open.
Place SuckItVerizon_Odin_Package2.tar.md5.gz into the "Bootloader" section of Odin
Click Start
You may now flash a custom ROM of your choice to your 100% IROM/Bootloader unlocked device. You are now Rooted and have the ability to install any CWM recovery zip with TWRP.
Video instructions
Troubleshooting Windows
Q. Why is CASUAL calling me a noob?
A. You need to Install the "Bootloader Baseline" with odin. We only support ONE bootloader, that's VRALJB.
Put your device into Odin Mode by powering on with Volume Down and Home pressed.
Put the BootloaderBaseline.tgz from above into the "Bootloader" section of Odin.
Click Start.
Q. Why am I bootlooping or the device won't boot?
A. You flashed the wrong thing at the wrong time. Flash the bootloader baseline in Odin, then repeat the instructions above.
Q.Why isn't CASUAL working correctly
A. Try redownloading the latest CASUAL package. Also make sure you're running the latest version of Java.
Q.Why is Odin is failing to open or use the package?
A. The download was damaged. Redownload it.
Q.Other unexplained problems?
A.Try using the proper drivers.
1. Go to device manger right-click and uninstall on the device.
2. Go to add/remove programs, uninstall any driver packages.
3. Unplug your device
4. Install Samsung Kies http://www.samsung.com/us/kies/
Q. How come CASUAL didn't start the first time?
A. Unplug and replug your device, or click CASUAL again and deal with both windows. This is a known issue. I cannot reproduce it in my development environment, it only happens on production compilations in JAR format and affects only Windows. If you'd like to submit a patch, you can get the source and I can add you as a contributor to http://android-casual.googlecode.com.
Q. Why won't CASUAL connect to the device?
A. If you've already installed the PROPER drivers, try disabling any firewalls. ADB uses a network connection to talk to your device. ADB is a network transparent protocol.
Q. I'm STILL having a problem.
A. Did you turn it off and then turn it back on again?
Troubleshooting Device
Q.Why does CASUAL fail to find a rooted device?
A. Check the SuperSU/Superuser Permissions app to verify that you have not inadvertently denied root access to shell.
Q. Why won't my phone start? why is it saying unauthorized software?
A. You unlocked, flashed something, then relocked. You need to flash back to stock VRALJB then repeat the unlock procedure. Use this guide http://forum.xda-developers.com/showthread.php?t=2040264
Q. I'm STILL having a problem.
A. Did you turn it off and then turn it back on again?
Pictures
Heres some pictures to show the newfound capabilities of your device.
TWRP Recovery
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CASUAL
Verizon device running AT&T firmware
Verizon device running International Firmware
Download count of 63 from testing- Note, do not flash any i9300 ROMs.
Conclusion
Congratulations, You're Unlocked. Your Galaxy Note 2 has gone from the most secure device on the market, to the least secure device publicly available. Your device will now accept any flash. Be careful and dont flash with Odin again. Stick to CWM zip packages so as to lower your risk.
Reserved for technical details
Thanks everybody involved! quick question, you say not to odin flash after using this...does that mean we can not odin back to stock after this modification?
Edit* Yes you can odin back to a stock i605 rom only!
Thank you Adam. Really appreciate all your hard work
Sent from my SCH-I605 using Tapatalk 2
Thanks! Will report back downloading now
Sent from my SCH-I605 using xda app-developers app
You Rock!
droidstyle said:
Thanks everybody involved! quick question; you say not to odin flash after using this...does that mean we can not odin back to stock after this modification?
Click to expand...
Click to collapse
Yeah I would like to know that as well.
Can't wait to do thus after school! Can't wait for the roms to start flooding the forums.
Sent from my rooted galaxy note 2... U mad?
Amazing, I am speechless!!! Thanks for all your hard work!
awesome work thanks
Thanks for all your work
FTW
Very cool. Great stuff Adam. Suck it Verizon indeed. :highfive:
Well...2 hours to download the Revision3 file on our crappy work internet (but damned if I'm going to wait until I get home). At least I'll get to watch the successes/failures roll in in the meantime.
Also...you mention to stick to flashable zip packages. If I understand correctly, flashing through recovery will still run the typical recovery checks, but ODIN will not?
Is there any reason I can't use Heimdall?
If we want to relock later, we can just flash a stock bootloader?
I already have my system setup how I like it and would like to not have to overwrite it with Revision. Will CASUAL work anyways as long as I have the dependencies?
Thanks so much Adam and Team!
:good:
awesome!
Thank you everyone involved!
I'm assuming that when running AT&T firmware/international firmware it won't recognize our VZW SIM correct? Awesome work though! Super excited about this.
I just wanna thank all of you for Guinea pigging this (so to speak). I'm gonna wait for droidstyles broke down step by step before i do this. Its probably not as bad as I'm making it out to be but I error to the side of caution.
Has anybody actually done this with no problem yet??
This guy is the f*ckin' man!!!
Thanks to everybody involved! Cant wait, I might just leave work now
Sent from my SCH-I605 using xda app-developers app
Original Thread for GS5
Thanks to developer @geohot, I was able to easily and successfully root my phone, here is the method. Should work with an 4.4.2 with a kernal build before Jun 3, 2014
1: On your phone go to towelroot.com
2: Click the image to download tr.apk
↓↓↓↓↓↓↓(LOOKS LIKE THIS)↓↓↓↓↓↓↓↓
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3. Install the apk
4. Run the apk and click make it ra1n, Device will reboot
5. After Reboot download Superuser from the play store
The reset was copied from @npjohnson so credits to him!
Note: SafeStrap doesn't work with encryption turned on (disabled by default). If you don't know if you don't have encryption on/your phone isn't a business phone (in which case you shouldn't be doing this!!!) then you most likely don't have encryption on!!
6. Use this app to change your SELinux mode to "Permissive" https://play.google.com/store/apps/details?id=com.mrbimc.selinux, this is required to use SafeStrap
7. Install SafeStrap 3.72 APK from this thread http://forum.xda-developers.com/showthread.php?t=2448925, NOT 3.71 FROM THE VERIZON THREAD!!! Then click install in the SafeStrap App
8. Flash http://download.chainfire.eu/448/SuperSU/UPDATE-SuperSU-v1.99r5.zip, this step is NOT OPTIONAL, without this file, your SU Binaries will not update!!! (This is important!)
Normal Method
6. Download http://download.chainfire.eu/448/SuperSU/UPDATE-SuperSU-v1.99r5.zip
7. Use ES File Explorer https://play.google.com/store/apps/details?id=com.estrongs.android.pop and unzip the file
8. Open the /common folder in the unzipped file, and copy the SuperUser.apk to the /system/app/ folder in the root of the phone, confirm any SuperUser Access requests at this point
9. Reboot
10. Open SuperSU and under the settings tab, update your SU Binary
11. Profit
TWEAKS
(Optional)
12. Flash http://www.androidfilehost.com/?fid=23487008491962487 in SafeStrap to enable wifi tethering
13. Use https://play.google.com/store/apps/details?id=com.bitcubate.root.busybox.complete to update to the newest version of BusyBox (The more popular BusyBox apps wouldn't work for me/ didn't have the newest version)
SAFESTRAP NOTES/HOW TO
- We CANNOT just flash a custom recovery, our bootloader is locked, and won't be unlock in the foreseeable future, we have to use SafeStrap instead
- To flash a ROM, reboot the phone, and click the menu button during boot up to get to SafeStrap, go to "Mount" ==> Check /System, leave the others checked
Then go back to the menu, go to "Wipe" ==> /System and swipe to wipe, you do not have to wipe /data, but it is strongly recommended (But this WILL wipe your data!!!)
The go back to menu, click "Install" select you ROM's .zip file AND SuperSU 1.99v4.zip to be safe
- You cannot use ROM Slots because this version of SafeStrap is made for the ATT S4, because of that we have some incompatibilities, you can only install to the "Stock" Slot
- BEWARE of flashing a Custom ROM and wiping /system, because if wipe /system, YOU ARE ERASING SAFESTRAP, if you flash a ROM that doesn't boot/is incompatible, you will have to ODIN back to stock!!!
- On a similar note, don't just flash a new ROM over your current ROM without wiping /system, as "dirty" flashing never ends well
- Most ATT SafeStrap 4.4.2/3 ROM work on the Verizon version, just a matter of testing them!!!
ROMS THAT ARE CURRENTLY COMPATIBLE WITH SAFESTRAP 3.72
Pre-Rooted 4.4.2 - Removes BloatWare stuff and implements the features from the International version that Verizon removed http://www.androidfilehost.com/?fid=23329332407590564
This rom may be illegal as creator used other peoples work without permission. Google Edition ROM - Google Edition ROM that IS compatible with SafeStrap, although not everything works... I know it says ATT, but I have tested and it works on verizonhttp://forum.xda-developers.com/showthread.php?t=2767026[/B]
BlackBox - An AOSP themed ROM that keeps many Samsung features, just google "BlackBox ROM S4 for a list of features/screenshots http://www.androidfilehost.com/?fid=23501681358541454
HyperDrive RLS 16.1 - TouchWiz S5/Note 3 with many awesome baked in features http://forum.xda-developers.com/showthread.php?t=2301724
Purified ROM - AOSP Themed with custom toggles http://forum.xda-developers.com/showthread.php?t=2759811
gDux - Highly Customized TouchWiz/AOSP, hard to explain, but really cool!!! http://forum.xda-developers.com/showthread.php?t=2759786
Blue Chrome Edition - Googlie made this.... I don't know anything about it, wanna describe it @googlie? http://www.androidfilehost.com/?fid=23329332407588272
PhoeniX ROM V8.0.1 - Strongly tweaked ROM based on TouchWiz, again just google "PhoeniX ROM S4" for description/screenies http://www.androidfilehost.com/?fid=23501681358541455
FoxHound ROM - Same case as above, just google "FoxHound ROM S4" for description/screenieshttp://www.androidfilehost.com/?fid=23487008491966537
Baja ROM - AOSP/TouchWiz Hybrid http://forum.xda-developers.com/showthread.php?t=2696872
Echoe ROM - First 4.4.2 TouchWiz ROM made for out phone, very stable/stock-ish with some added features http://forum.xda-developers.com/showthread.php?t=2702592
This is a link to @googlies downloads folder in case anybody wants it, there are some work in progress ROMs and ROM backups (.rar files,) you can check out in there, to use those just unRAR them into you SafeStrap folder on you SD Card, and then restore the backup in SafeStrap
HOW TO BOOT TO RECOVERY/DOWNLOAD MODE
Stock Recovery Mode = Hold Volume Up + Home Button + Power until it buzzes, then release the power button
Download/ODIN Mode = Hold Volume Down until it buzzes and when prompted push volume up to accept
SafeStrap Recovery = "Reboot to Recovery" buttoning the SafeStrap app does not work, instead turn the phone off and turn it back on, then push the menu button after the Samsung Screen goes away
Note - If you see a "Samsung Custom" screen with an unlocked padlock, it doesn't mean you have an unlocked bootloader!!! Don';t get your hopes up, it just means that the phone is customized software size
ODIN GUIDE
ODIN is a program used to return Samsung phones to stock, it provides many ways to restore the different partitions of the phone;
F. Reset Time - Doesn't ever hurt anything, usually recommended/necessary, but I am not completely sure what it does?
Auto Reboot - Check unless you plan on flashing multiple files before reboot (not recommended)
PIT File - Necessary when completely repartitioning the phone, in most cases will wipe the whole phone clean (excluding @googlies/@Surge1223s guide to downgrade from NC5), it is a partition table template. Comes in the form of a .PIT file.
BL (Called Bootloader in older versions of ODIN) - Restores Bootloader, don't jack with this unless you know what you are doing, you cannot flash any bootloader lower than the on you are currently on! Ex. NC5 ==> MDK won't work, there are some small exceptions like @googlies NC5 ==> MK2 Downgrade, this was only possible due to the NC2 leak that allows downgrades. These files must be signed by Samsung. Comes in the form of a .tar file
AP (Called PDA in older versions of ODIN) - Restores to /System, doesn't Wipe it, just overwrites if necessary. Comes in the form of a .tar file
CP - (Called Phone/Modem in older versions of ODIN) - Restores Modem, wipes it and overwrites with new version. Comes in the form of a .tar file
CSC - (Called Cache in older versions of ODIN) - Restores to /Cache, wipes it and overwrites with new version. Comes in the form of a .tar file
UMS - I am unsure... Anyone?
ODIN 3.09 - Stock ODIN program, used in ALL cases except downgradeshttps://www.dropbox.com/s/b1kjainbic4iloo/Odin_v3.09.zip
ODIN 3.10 - made by @googlie I believe? Used in his guide for downgrading http://www.androidfilehost.com/?fid=23329332407587822
NC5 No-Wipe and Full-Wipe Tars - No-Wipe (Use in most cases) will leave your data in tact but restore /system to stock, Full-Wipe restores everything to stockhttp://forum.xda-developers.com/showthread.php?t=2735172
MK2 No-Wipe and Full-Wipe Tars - http://forum.xda-developers.com/showthread.php?t=2578209
MDK Full-Wipe Tar (If anyone has a link to a No-Wipe, please post it) - http://forum.xda-developers.com/showthread.php?t=2289325
HOW TO RUN 4.3 ROMS IF ON NC5/NC2
This is made for NC5 phones, but will also work on NC2 and allow you to retain the NC2 Bootloader. If you don't know if you are on NC2, THEN YOU ARE NOT, very few people are on NC2, and those that are are there because they know what they are doing (hopefully).
If you want to run 4.3 ROMS in SafeStrap unRAR this file and place it in the AP slot of ODIN (credits to @googlie) http://www.androidfilehost.com/?fid=23501681358537591, then reboot to stock recovery and wipe data and cache, then reboot and use SafeRoot to Root http://forum.xda-developers.com/showthread.php?t=2565758 and install SafeStrap 3.71 from here http://forum.xda-developers.com/showthread.php?t=2441441 and finally flash your 4.3 ROM found here: http://forum.xda-developers.com/show....php?t=2630040
If you have issues, flash the different fixes (Wifi, Voice, Data, etc.) from this thread http://forum.xda-developers.com/showpost.php?p=51955929 in SafeStrap, READ WHAT THEY ARE BEFORE FLASHING
SAMSUNG KNOX
To disable/remove KNOX from stock ROMs:
Download: To Disable: Titanium Backup https://play.google.com/store/apps/details?id=com.keramidas.TitaniumBackup
To remove completely use RootAppDelete https://play.google.com/store/apps/details?id=zsj.android.uninstall, use Pro mode within the app when it asks
Open the app that you downloaded above (either one depending on your choice) Tap the search button and type ‘Knox’ and you’ll get the list of all the files named as knox.
Freeze/Remove (Pro-Mode) the following using titanium backup/RootAppDelete, to find them just search "KNOX"
Delete/Freeze
com.sec.enterprise.knox.attestation
com.sec.knox.eventsmanager
KLMS Agent
KNOX
Knox Notification Manager
KNOX Store
wzhigaylo said:
Original Thread for GS5
Thanks to developer geohot, I was able to easily and successfully root my phone, here is the method. Should work with an 4.4.2 with a kernal build before Jun 3, 2014
1: On your phone go to towelroot.com
2: Click the image to download tr.apk
↓↓↓↓↓↓↓(LOOKS LIKE THIS)↓↓↓↓↓↓↓↓
3. Install the apk
4. Run the apk and click make it ra1n
5. Device will reboot
6. After Reboot download Superuser from the play store
7. Check root w/ a free root checker in the play store
Click to expand...
Click to collapse
Already been posted in general forum...
sent by bajarom v2.2 kitkat
definatly been covered already dude in my thread and in the general thread.
wzhigaylo said:
Original Thread for GS5
Thanks to developer geohot, I was able to easily and successfully root my phone, here is the method. Should work with an 4.4.2 with a kernal build before Jun 3, 2014
1: On your phone go to towelroot.com
2: Click the image to download tr.apk
↓↓↓↓↓↓↓(LOOKS LIKE THIS)↓↓↓↓↓↓↓↓
3. Install the apk
4. Run the apk and click make it ra1n
5. Device will reboot
6. After Reboot download Superuser from the play store
7. Check root w/ a free root checker in the play store
Click to expand...
Click to collapse
I appreciate the thread. Thanks!
Worked great on mine tks for the info
scottguest11 said:
Worked great on mine tks for the info
Click to expand...
Click to collapse
Verizon security identified it as spyware - [Artemis!9b1c7c68adb3:3:1.0]
Just reporting what the phone is telling me.
rjh20136 said:
Verizon security identified it as spyware - [Artemis!9b1c7c68adb3:3:1.0]
Just reporting what the phone is telling me.
Click to expand...
Click to collapse
That will happen occasionally when the file being scanned has to do with rooting a phone. Simply because rooting a phone exploits the system which is what an antivirus is supposed to detect. You gotta depend on what other users say. If its on XDA your more than likely OK.
Sent from a Shaftamle Galaxy S4
"Thanks Button" is always appreciated!
http://mycolorscreen.com/Shaftamle/
Shaftamle said:
That will happen occasionally when the file being scanned has to do with rooting a phone. Simply because rooting a phone exploits the system which is what an antivirus is supposed to detect. You gotta depend on what other users say. If its on XDA your more than likely OK.
Sent from a Shaftamle Galaxy S4
"Thanks Button" is always appreciated!
http://mycolorscreen.com/Shaftamle/
Click to expand...
Click to collapse
+1.
Verizon is detecting this as "Malware" because it breaks their stranglehold. Tough noogies.
k1mu said:
+1.
Verizon is detecting this as "Malware" because it breaks their stranglehold. Tough noogies.
Click to expand...
Click to collapse
I'll run it thru a couple of other scanners that I have.
rjh20136 said:
I'll run it thru a couple of other scanners that I have.
Click to expand...
Click to collapse
anything it pops up will be a false flag its no virus. easily the best root hack yet and from the worlds most well known hacker/developer period u can trust geo to always deliver the best of the best no point in virus scanning he isnt like that. obviously
gigilie said:
definatly been covered already dude in my thread and in the general thread.
Click to expand...
Click to collapse
Sorry I didn't check the general section before it was to late.
Moved to general and closed to avoid clutter of same topic.
BACKGROUND: OK this question gets asked every day, by members of varying skill levels, so this is intended to be a one stop guide on how to root, no matter what firmware version you're running. Yes this will trip Knox, no that will have no effect on your phone whatsoever, and there are ways to reset the Knox counter. If worst comes to worst and you need to bring your phone in for warranty and they give you any sort of lip for the Knox counter, tell them Kies broke your phone and they da** well better fix it (worked for me with multiple Samsung devices).
That said, this will root the SM-G900T (T-Mobile Galaxy S5) no matter what version of android you're running. Make sure you read this entire post and understand everything before trying anything.
PREPARATION: Disclaimer out of the way, now for the fun stuff. First, preparation, you need to download the following files to your PC: Odin 3.11.1 (this is Odin, it flashes stuff to Samsung android phones); twrp-3.0.2-2-klte.img.tar (this is the custom recovery we're going to use). Extract the Odin zip file to your PC's Desktop. Download the file named UPDATE-SuperSU-v2.79-20161211114519.zip somewhere to your phone's internal storage or external SD, doesn't really matter which. Now in your phone's settings, go to About device, scroll down to Build number. Repeatedly tap Build number until your phone tells you Developer options have been turned on. Go back and enter developer options, enable USB debugging and hit OK. At this point you'll want to connect your phone to your PC with USB, just to make sure it actually connects (it should). If not, you can download the USB drivers from here (scroll down to Downloads section), but most likely this won't be necessary. OK prep work done, now we get to actually get started on rooting our phone. Make sure your phone has at least 50% battery, this is always a smart safety step.
STEPS:
Power off the phone. Boot into download mode (hold vol-, home, and power all at once in that order), then hit vol+ to continue
Run Odin (double click the Odin3 v3.11.1.exe file). Click the Options tab, disable the "Auto-Reboot" option and double check that "Re-Partition" option is disabled (it should be by default), this is critical to success
Connect phone via USB. Hit AP button in Odin, select the twrp-3.0.2-2-klte.img.tar
Flash (click start). When it's done, the progress bar will be full and Odin should say "PASS!"
Hold vol+, home, and power (all at once, in that order) to boot into recovery. THIS MUST BE DONE BEFORE REBOOTING NORMALLY!. TWRP might ask if you want to let it modify your system or keep it read only. I would highly recommend you let it modify your system, you might be OK keeping it read only, but I cannot guarantee that. You will be fine letting it modify your system, that I can guarantee.
Hit the install option and navigate to the SuperSU zip file that is saved to your tablet. Select it and swipe to install.
Reboot system (normal reboot). If TWRP should ask you, do not let it install supersu the way it wants to (do not swipe to install, just reboot).
When android is booted, run the superSU app and go into settings, disable the Mount namespace separation option, and reboot immediately.
Please note the first boot might take a while. If after 10 minutes or so the phone has not rebooted, you should boot back into TWRP, install the supersu zip file again, and this time wipe cache and dalvik before rebooting. Otherwise the cache and dalvik wipe is not necessary. I will eventually post pictures to demonstrate all the steps in the 2nd post, and hopefully FAQs or whatever in the third post.
If you want to hit the thanks button that would be awesome, but the real credit goes to chainfire for his amazing work with supersu and really just all things root in general; and Dees_Troy for doing an excellent job developing and maintaining TWRP custom recovery for our device. They're the real heroes, I just wrote up this guide
Pictures to Demonstrate Steps
Sorry all the pictures are sideways. If you want, you can still view them by clicking the following link, file names begin with corresponding step numbers: https://www.dropbox.com/sh/wgguior3q2c6638/AAAzas50Zd-Du7jNXI3HsZU2a?dl=0
Proof I have the SM-G900T, latest 5.1.1 firmware, unmodified:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Step 1:
Step 2:
Step 3:
Step 4:
Step 5:
Step 6:
Step 7:
Step 8:
Proof We're Now Rooted:
FAQ's
Does this method work with the new marshmallow (6.0.1) firmware?
Yes. I have done it myself, it works
So I'm rooted now what?
Once you're rooted, you can use certain apps you would be unable to use not rooted. A few I would definitely recommend checking out: AdAway (an adblocker), Viper4Android (significantly, noticeably improve your audio quality by tweaking the settings in this app), Titanium Backup (not only backup and restore app settings, but freeze/uninstall unwanted system apps, aka bloatware), and a root-enabled file explorer such as Root Browser or ES File Explorer (with the root option enabled) is recommended. If you plan to install Viper4Android, before doing so please first flash this file in TWRP and then reboot, edit the following lines in the file /system/build.prop, and reboot again once the edits are made:
Code:
lpa.decode=true to lpa.decode=false
tunnel.decode=true to tunnel.decode=false
lpa.use-stagefright=true to lpa.use-stagefright=false
Where can I find custom ROMs for this phone?
Touchwiz (Samsung's version of Android similar to the one that comes stock with the phone) based ROMs can be found in the T-Mobile Galaxy S5 Android Development Section. AOSP (Google's original version of Android) based ROMs, such as CyanogenMod, AOKP, Mokee, Bliss, AICP, Resurrection-Remix, etc. can be found in the S5 Unified Development Section. I must warn you i can give a lot more information on the aosp based ROMs since that is my personal preference in overall Android experience, as a result my knowledge of touchwiz based development is much shakier. To each their own, and we ought to cherish android's ability to give us such a powerful freedom of choice and fight for this continued ability for our control of our personal devices against current trends of locking everything down too tight to allow for true development based innovation. Remember, when getting ROMs from this section, this phone's development name is klte (as opposed to kltevzw, kltespr, klteusc, etc.)
More info to come
Thank you very much for posting this, I just got a used S5 in the mail today and your process worked like a charm. Rooted on the first pass.
thisisapoorusernamechoice said:
Reserved, FAQ's or something
Click to expand...
Click to collapse
It works is cm stable
Sent from my LG-D851 using Tapatalk
---------- Post added at 01:09 PM ---------- Previous post was at 12:32 PM ----------
thisisapoorusernamechoice said:
BACKGROUND: OK this question gets asked every day, by members of varying skill levels, so this is intended to be a one stop guide on how to root, no matter what firmware version you're running. Yes this will trip Knox, no that will have no effect on your phone whatsoever, and there are ways to reset the Knox counter. If worst comes to worst and you need to bring your phone in for warranty and they give you any sort of lip for the Knox counter, tell them Kies broke your phone and they da** well better fix it (worked for me with multiple Samsung devices).
That said, this will root the SM-G900T (T-Mobile Galaxy S5) no matter what version of android you're running. Make sure you read this entire post and understand everything before trying anything.
PREPARATION: Disclaimer out of the way, now for the fun stuff. First, preparation, you need to download the following files to your PC: Odin 3.10.7 (this is Odin, it flashes stuff to Samsung android phones); twrp-3.0.2-1-klte.img.tar (this is the custom recovery we're going to use). Extract the Odin zip file to your PC's Desktop. Download the file named BETA-SuperSU-v2.71-20160331103524.zip somewhere to your phone's internal storage or external SD, doesn't really matter which. Now in your phone's settings, go to About device, scroll down to Build number. Repeatedly tap Build number until your phone tells you Developer options have been turned on. Go back and enter developer options, enable USB debugging and hit OK, also enable Allow mock locations a couple lines below it. At this point you'll want to connect your phone to your PC with USB, just to make sure it actually connects (it should). If not, you can download the USB drivers from here (scroll down to Downloads section), but most likely this won't be necessary. OK prep work done, now we get to actually get started on rooting our phone. Make sure your phone has at least 50% battery, this is always a smart safety step.
STEPS:
Power off the phone. Boot into download mode (hold vol-, home, and power all at once in that order), then hit vol+ to continue
Run Odin (double click the Odin3 v3.10.7.exe file). Click the Options tab, disable the "Auto-Reboot" option and double check that "Re-Partition" option is disabled (it should be by default), this is critical to success
Connect phone via USB. Hit AP button in Odin, select the twrp-3.0.2-1-klte.img.tar
Flash (click start). When it's done, the progress bar will be full and Odin should say "PASS!"
Hold vol+, home, and power (all at once, in that order) to boot into recovery. THIS MUST BE DONE BEFORE REBOOTING NORMALLY!. TWRP might ask if you want to let it modify your system or keep it read only. I would highly recommend you let it modify your system, you might be OK keeping it read only, but I cannot guarantee that. You will be fine letting it modify your system, that I can guarantee.
Hit the install option and navigate to the SuperSU zip file that is saved to your tablet. Select it and swipe to install.
Reboot system (normal reboot). If TWRP should ask you, do not let it install supersu the way it wants to (do not swipe to install, just reboot).
When android is booted, run the superSU app and go into settings, disable the Mount namespace separation option, and reboot immediately.
Please note the first boot might take a while. If after 10 minutes or so the phone has not rebooted, you should boot back into TWRP, install the supersu zip file again, and this time wipe cache and dalvik before rebooting. Otherwise the cache and dalvik wipe is not necessary. I will eventually post pictures to demonstrate all the steps in the 2nd post, and hopefully FAQs or whatever in the third post.
@lox2013
Click to expand...
Click to collapse
Cm 13 is instill thanks to u should get all the credit BC nobody else find out
Sent from my LG-D851 using Tapatalk
SuperSU Install?
Thank you for putting this together with simple to follow steps!
Hypothetically if someone were to accidentally swipe to install supersu at step 7 rather than just rebooting, what problem(s) does that cause?
thisisapoorusernamechoice said:
STEPS:
Power off the phone. Boot into download mode (hold vol-, home, and power all at once in that order), then hit vol+ to continue
Run Odin (double click the Odin3 v3.10.7.exe file). Click the Options tab, disable the "Auto-Reboot" option and double check that "Re-Partition" option is disabled (it should be by default), this is critical to success
Connect phone via USB. Hit AP button in Odin, select the twrp-3.0.2-1-klte.img.tar
Flash (click start). When it's done, the progress bar will be full and Odin should say "PASS!"
Hold vol+, home, and power (all at once, in that order) to boot into recovery. THIS MUST BE DONE BEFORE REBOOTING NORMALLY!. TWRP might ask if you want to let it modify your system or keep it read only. I would highly recommend you let it modify your system, you might be OK keeping it read only, but I cannot guarantee that. You will be fine letting it modify your system, that I can guarantee.
Hit the install option and navigate to the SuperSU zip file that is saved to your tablet. Select it and swipe to install.
Reboot system (normal reboot). If TWRP should ask you, do not let it install supersu the way it wants to (do not swipe to install, just reboot).
When android is booted, run the superSU app and go into settings, disable the Mount namespace separation option, and reboot immediately.
Click to expand...
Click to collapse
I might should have not been doing this for the first time at 3a? How much trouble did I cause myself but letting TWRP install supersu by swiping?
Thank you again.
SethVIII said:
Thank you for putting this together with simple to follow steps!
Hypothetically if someone were to accidentally swipe to install supersu at step 7 rather than just rebooting, what problem(s) does that cause?
I might should have not been doing this for the first time at 3a? How much trouble did I cause myself but letting TWRP install supersu by swiping?
Thank you again.
Click to expand...
Click to collapse
I'm pretty sure it'll cause a bootloop, I would recommend against doing the swipe to install when twrp asks you to, saying supersu isn't installed (it is when you install the zip, twrp just can't detect it). The reason for this is something in the kernel called selinux (long story, Google it if you want the full blown details) but the short version is starting with android 5.1.1 older versions of supersu (ie the one twrp wants to install for you automatically) usually cause a bootloop. The supersu zip file I link to in my post is specifically designed to avoid this issue. Thanks for reminding me, I wanted to put this question in the FAQ section. It's an important issue and something anyone who wants to know a little more about android should be aware of
thisisapoorusernamechoice said:
I'm pretty sure it'll cause a bootloop, I would recommend against doing the swipe to install when twrp asks you to, saying supersu isn't installed (it is when you install the zip, twrp just can't detect it). The reason for this is something in the kernel called selinux (long story, Google it if you want the full blown details) but the short version is starting with android 5.1.1 older versions of supersu (ie the one twrp wants to install for you automatically) usually cause a bootloop. The supersu zip file I link to in my post is specifically designed to avoid this issue. Thanks for reminding me, I wanted to put this question in the FAQ section. It's an important issue and something anyone who wants to know a little more about android should be aware of
Click to expand...
Click to collapse
Thank you for your quick and helpful response. So if my phone is booting now, with supersu installed, does that mean I am good to go?
Bootloop may be what happened. After awhile, I pulled the battery, booted back into TWRP and reinstalled the supersu zip file. I did not wipe cache or dalvik but I also did not swipe to install supersu. My phone now boots and acts fine other than showing "Set Warranty Bit : kernel", but I think that is expected, correct?
SethVIII said:
Thank you for your quick and helpful response. So if my phone is booting now, with supersu installed, does that mean I am good to go?
Bootloop may be what happened. After awhile, I pulled the battery, booted back into TWRP and reinstalled the supersu zip file. I did not wipe cache or dalvik but I also did not swipe to install supersu. My phone now boots and acts fine other than showing "Set Warranty Bit : kernel", but I think that is expected, correct?
Click to expand...
Click to collapse
The Set Warranty Bit: kernel thing is normal, that's just your phone telling you it's rooted (I mean it's technically telling you the kernel has been modified, in this case only just to allow for supersu to be installed). As long as you're booting fine, that's what's important. Thanks for the feedback, and I hope I've been helpful
thisisapoorusernamechoice said:
The Set Warranty Bit: kernel thing is normal, that's just your phone telling you it's rooted (I mean it's technically telling you the kernel has been modified, in this case only just to allow for supersu to be installed). As long as you're booting fine, that's what's important. Thanks for the feedback, and I hope I've been helpful
Click to expand...
Click to collapse
Yes, very helpful, thank you.
So any confirmed root on FOL1 yet??? With custom ROM flashed
Sent from my SM-G900T using XDA-Developers mobile app
VICIOUSVIC1 said:
So any confirmed root on FOL1 yet??? With custom ROM flashed
Sent from my SM-G900T using XDA-Developers mobile app
Click to expand...
Click to collapse
Is confirm I rooted my gf phone the s5 5.1.1 it works she running cm 13 most stable rom
Sent from my SM-N920C using Tapatalk
VICIOUSVIC1 said:
So any confirmed root on FOL1 yet??? With custom ROM flashed
Sent from my SM-G900T using XDA-Developers mobile app
Click to expand...
Click to collapse
FYI, I don't know of any Custom ROMs that are not already rooted. Rooting is only needed for Stock ROMs.
Rob
Trying with FOL, downloaded via the link provided here. After installing TWRP, i have to remove the battery to get the phone to turn off. It still acts as if it were being updated, and the power button does not work. Taking out the battery, putting it back in, and pressing vol up, home, power brings up twrp.
After hitting install, the zip file fails:
<<<<<<<<<<<
Updating partition details...
...done
Full SELinux suppot is present.
MTP Enabled
Installing zip file ' /external_sd/._BETA-SuperSU-v2.
71-20160331103524.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Zip file is corrupt!
Error installing zip file '/external_sd/._BETA-
SuperSU-v2.71-20160331103524.zip'
Updating partition details...
...done
<<<<<<<<<<<
About Device shows the baseband version: G900TUVS1FOL1
I'm probably just doing something wrong. With some help, i'd like to try again.
trips KNOX
thisisapoorusernamechoice said:
BACKGROUND: Yes this will trip Knox, no that will have no effect on your phone whatsoever, and there are ways to reset the Knox counter. If worst comes to worst and you need to bring your phone in for warranty and they give you any sort of lip for the Knox counter, tell them Kies broke your phone and they da** well better fix it (worked for me with multiple Samsung devices).
Click to expand...
Click to collapse
not good to trip KNOX from what I understand. maybe there can be included in this a way to remove KNOX? I know I posted this comment in another post that linked to this. I thought I was on the right post. sorry. OH and What is Kies and how is that pronounced?
musterion1973 said:
not good to trip KNOX from what I understand. maybe there can be included in this a way to remove KNOX? I know I posted this comment in another post that linked to this. I thought I was on the right post. sorry. OH and What is Kies and how is that pronounced?
Click to expand...
Click to collapse
Knox is Samsung's indicator if your phone has ever had a non-stock kernel installed. Currently there are very few pieces of software - Samsung only - that check this flag. One may be Samsung Pay. However, it doesn't cause any other problems with any other parts of Android. And, doesn't keep you from turning your phone back it, etc.
KIES is the software that Samsung supplies to flash updates, make backups, etc.
You can find it here: http://www.samsung.com/in/support/usefulsoftware/KIES/
Rob
SethVIII said:
Yes, very helpful, thank you.
Click to expand...
Click to collapse
When i hit the install supersu when twrp asked me i was put in a bootloop like thispoorusernamechoice said. I learned my lesson though?
I am a thank you slut.lol
rlichtefeld said:
Knox is Samsung's indicator if your phone has ever had a non-stock kernel installed. Currently there are very few pieces of software - Samsung only - that check this flag. One may be Samsung Pay. However, it doesn't cause any other problems with any other parts of Android. And, doesn't keep you from turning your phone back it, etc.
KIES is the software that Samsung supplies to flash updates, make backups, etc.
You can find it here: http://www.samsung.com/in/support/usefulsoftware/KIES/
Rob
Click to expand...
Click to collapse
Thank you Rob.
---------- Post added at 04:02 AM ---------- Previous post was at 03:15 AM ----------
thisisapoorusernamechoice said:
BACKGROUND: OK this question gets asked every day, by members of varying skill levels, so this is intended to be a one stop guide on how to root, no matter what firmware version you're running. Yes this will trip Knox, no that will have no effect on your phone whatsoever, and there are ways to reset the Knox counter. If worst comes to worst and you need to bring your phone in for warranty and they give you any sort of lip for the Knox counter, tell them Kies broke your phone and they da** well better fix it (worked for me with multiple Samsung devices).
twrp-3.0.2-1-klte.img.tar (this is the custom recovery we're going to use).
Click to expand...
Click to collapse
twrp-3.0.2-1-klte.img.tar 10.6M
twrp-3.0.2-1-klte.img 10.6M
do I need both of these or just the very top one. I downloaded both ? in the event they are bother needed. but what one will we be using here Sir or Ma'am.
Yes this will trip Knox said:
did not seem to trip KNOX. so how di I remove KNOX altogether?
Click to expand...
Click to collapse
musterion1973 said:
twrp-3.0.2-1-klte.img.tar 10.6M
twrp-3.0.2-1-klte.img 10.6M
do I need both of these or just the very top one. I downloaded both ? in the event they are bother needed. but what one will we be using here Sir or Ma'am.
Click to expand...
Click to collapse
You just need the twrp-3.0.2-1-klte.img.tar 10.6M