ROOT U Firmware
Hello everyone it's XMayhem here!
We have two root methods with other combined guides along with tweaks & mods after root
These root methods are specifically for Sprint U firmware
Why? Less bloat and a lot more stable in rooting
The first method I personally use, you don't need Lspeed or Kernel auditor. The quickvic's rootbat it'self has all the performance you need with no lag. Or you can use the supersu 2.82 root.bat by jrkruse
Your choice of root!
First off I'm not responsible for any damage done to your phone or if the world explodes.
Or flashing twrp when it's not stated to flash in the OP. That's why we have flashfire people.
U Firmware Files they can be found on both sites
https://www.sammobile.com/firmwares/
http://updato.com/
For root you need to be on a clean installation of U Firmware
Once you have firmware extract files
1. Place phone in download mode. Power + Vol Down + Home
2. Connect Phone to computer
3. Open Official Odin
4. Odin should recognize your phone. If not, you need to download and install the Samsung Driver Files here http://developer.samsung.com/galaxy/others/android-usb-driver-for-windows
5. Place the BL, AP, CP,CSC_OYM from the rar in the corresponding slots.
6. Press Start & Firmware should flash
Next Download these files
Eng boot https://androidfilehost.com/?fid=457095661767141717
Quickvic's rootbat https://drive.google.com/file/d/0Bygh6W_e2Fo5Vkk1bURVaHdKbzg/view
or
Jrkruse root https://androidfilehost.com/?fid=889764386195909311
PrinceComsy modified Odin for root only https://www.androidfilehost.com/?fid=24591023225177749
Official odin for flashing stock U firmware https://samsungodin.com/
Playstore apps you'll need
Bk package disabler paid
https://play.google.com/store/apps/details?id=com.kunkunsoft.packagedisabler&hl=en
or Adhell it's free
https://play.google.com/store/apps/details?id=com.getadhell.androidapp&hl=en
Flashfire https://play.google.com/store/apps/details?id=eu.chainfire.flash&hl=en
Got everything downloaded? Good let's move on
G930U RC1 Nougat Root
1. First, you should already have flashed the U firmware
2. Completely finish activation and finish initial setup (I recommend signing into google first then samsung account after root)
3. Update PRL and Profile.
4. Then enable USB debugging under developer settings and turn off verify apps via ADB.
5.Turn off auto update system in developer options
6. Go into other security settings from lock screen and security settings, click security policy updates and turn auto updates off
7. Disable the following packages via bk or adhell
Chameleon
Sprint OMADM
Sprint OMADM Phone Interface
MDMApp
SecurityLogAgent
Security Policy Updates
Security Storage
8. This step is for people who use Snapchat like me make sure you have downloaded it and already logged in before moving on to the next step. You won't be able to sign in after root I know there are games that might not work either ex. Pokemon Go
9. Flash the engboot image via Modified Odin by PrinceComsy Flash it in AP Slot
10. For Sprint MMS/DATA fix go to:
Settings>Connections>Mobile Networks>Access Point Names
Delete Wholesales OTA apn by selecting, clicking top right menu, and delete.
Now the Global Roaming APN.. select it.
Change the whole APN to:
Name: APN2 LTE Internet
APN: n.ispsn
MMSC: http://mms.sprintpcs.com
Multimedia message proxy: 68.28.31.7
Multimedia message port: 80
MCC: 310
MNC: 000 // Do Not CHANGE!
APN type: default,supl,mms,dun,fota
APN Protocol: IPv4/IPv6
APN roaming protocol: IPv4/IPv6
Bearer: LTE
Top right menu>SAVE! Make sure APN2 LTE Internet is enabled and by the dot being blue. LTE should display icon and reset device to verify it stuck.
Before flashing either root. For those having samsung expired session please check out this link.
It works on both root methods
https://forum.xda-developers.com/galaxy-s6/general/fix-samsung-account-login-password-loop-t3575443
Samsung pass apk will install, if the samsung account apk doesn't install just use the apkmirror one here https://www.apkmirror.com/?post_type...amsung+account
11. Run Quickvics root.bat file ( Same with Jkruse root)
Here's how
1. Extract rootbat
2. Open the folder & double click root windows batch file
3. Wait for your phone to be recognized, it'll install root on it's own
4. Wait for your phone to reboot, and for your phone to recognized by computer
5. Once it's recognized go back into quickvics folder and click on fingerprint fix folder
6. Double click fingerprint fix windows batch
7. After it installs go into recovery mode by powering off phone holding Home+Power+Volume Up button
8. Wait till the android icon falls and it'll bring you to the recovery page
9. Wipe cache & reboot phone
10. I ask that you let your phone settle after the reboot, don't touch it for at least a good 15 mins!!
Sign in to your samsung account and Enjoy your rooted phone!:victory:
Extras & Mods
Hotspot
1. Download and install Termux
2. Type "su", press enter and allow root access.
3. Type "settings put global tether_dun_required 0" and press enter.
4. Type "settings put global tether_dun_apn "APNDUN, n.ispsn... http://mms.sprintpcs.com,68.28.31.7,...dun,mms,supl"
5. Turn off mobile data.
6. Turn on hotspot and it should work just fine
Adblocker Adaway
https://forum.xda-developers.com/showthread.php?t=2190753
Xposed for Nougat ( Use at your own risk I personally don't use it)
https://forum.xda-developers.com/sprint-galaxy-s7/how-to/xposed-nougat-t3653750
Changing Emoji
https://forum.xda-developers.com/general/general/emojis-android-ios10-nougat-emojione-t3508636
Sound Mod
https://forum.xda-developers.com/showthread.php?t=2634729
Substratum for Samsung
https://forum.xda-developers.com/apps/substratum/7-0-substratum-sex-tw-beta-t3620796
Block Youtube ads
https://forum.xda-developers.com/android/apps-games/app-iytbp-injected-youtube-background-t3560900
Screenshots
{
"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"
}
Big Thanks to these awesome people here on XDA!! Give them all the thanks you can
@JUSMEJOSE https://forum.xda-developers.com/member.php?u=1113488
@princecomsy https://forum.xda-developers.com/member.php?u=5028474
@jrkruse https://forum.xda-developers.com/member.php?u=1949695
@Araltd https://forum.xda-developers.com/member.php?u=2326775
@paul2112 https://forum.xda-developers.com/member.php?u=8099997
@YMNDLZ https://forum.xda-developers.com/member.php?u=7683955
@Chainfire https://forum.xda-developers.com/member.php?u=631273
Useful Tips
Tips
1. Doze: Forcedoze https://play.google.com/store/apps/details?id=com.suyashsrijan.forcedoze&hl=en
or Greenify https://play.google.com/store/apps/details?id=com.oasisfeng.greenify&hl=en
2. Animation: Change the animation speeds to .5 via developer options
3. Voicemail: Google Voice
4. Back up apps & delete them with a reboot using Titanium Backup
5. I prefer using google apps over Samsung apps plus they can be themed using Substratum
DELETED.
Deleted
DELETED.
Confirm that this is working? screens?
Using boostmobile
Bricked during U firmware flashing
Bricked my Sprint Samsung S7 after flashing u Firmware with Odin v3. 12, Now the screen won't turn on, no indication light while charging, tried soft reset combination keys, hard reset combination keys, nothing works. Any leads?
I'm a noob.
robinsingh2490 said:
Bricked my Sprint Samsung S7 after flashing u Firmware with Odin v3. 12, Now the screen won't turn on, no indication light while charging, tried soft reset combination keys, hard reset combination keys, nothing works. Any leads?
I'm a noob.
Click to expand...
Click to collapse
Plug phone hold volume down and power till download comes on ,there's really no way it can brick if using real firmware files and correct Odin by Prince cosmey,if it's not working it's ur phone it's self
Some more details
miko12312 said:
Plug phone hold volume down and power till download comes on ,there's really no way it can brick if using real firmware files and correct Odin by Prince cosmey,if it's not working it's ur phone it's self
Click to expand...
Click to collapse
Sorry, but I should have included some more details, that I downloaded the U firmware, tried flashing S7 sprint, didn't happen twice, then I put in SM-G930 SPT pit file In the pit tab and Then selected All options under options tab except for "Nand erase All and Flash lock" and after these steps I flashed the phone through Odin, it showed Pass but then the phone died, and now no combination of keys work.
robinsingh2490 said:
Sorry, but I should have included some more details, that I downloaded the U firmware, tried flashing S7 sprint, didn't happen twice, then I put in SM-G930 SPT pit file In the pit tab and Then selected All options under options tab except for "Nand erase All and Flash lock" and after these steps I flashed the phone through Odin, it showed Pass but then the phone died, and now no combination of keys work.
Click to expand...
Click to collapse
Well you did something that wasn't part of the guide here. Charge your phone to 80% and follow the steps to a fresh installation of the U firmware above.
robinsingh2490 said:
Sorry, but I should have included some more details, that I downloaded the U firmware, tried flashing S7 sprint, didn't happen twice, then I put in SM-G930 SPT pit file In the pit tab and Then selected All options under options tab except for "Nand erase All and Flash lock" and after these steps I flashed the phone through Odin, it showed Pass but then the phone died, and now no combination of keys work.
Click to expand...
Click to collapse
To my knowledge the only thing that should be checked under the Options menu is Auto Reboot and F. Reset Time. Nothing else should be checked but those two. You should not need to use the PIT file at all. Leave that alone. In your post you state the g930 SPT...did you mean g930 SPR because I am not familiar with an SPT version of our firmware.
Try downloading unmodded(stock) version of ODIN 3.12.7. With that version ODIN I can flash anything to my phone with no issue at all whether it be eng boot or stock firmware and I have done all kinds of crazy combinations of these firmwares on the s7.
Simply load AP into AP, BL into BL, CP into CP, and make sure you load CSC_OYM on the first time loading the U firmware. Also, personally I always delete cache 3 times in recovery followed by 2 factory resets before I go into the download mode. And like the OP stated, clear cache after any flash as well.
Hope that helps...just remember that as long as there is stock firmware, and ODIN...you "should" always be able to return to a stock phone. Nothing is impossible, but you get the drift. :good:
I am so thankful the U firmware's LTE icon is soooo much larger than the P firmware. I can easily tell when I am on the LTE+ network ever since the switch, and guys don't forget to go the easy route when uninstalling the Samsung apps that come with the U firmware. Very simple...Settings>Device Maintenance>Storage>Apps>Select All. Make sure that no other apps have been installed when you do this or else you will simply need to select each app individually. But the stock uninstaller is amazingly fast....it surprises me till this day.
To the OP, I'm not sure if the Beats Audio requires the same as V4A, but in my experience Adapt Sound, Sound Alive, and SplitSoundService should be disabled by your Package disabler prior to flashing the EngBoot AP. It removes any potential popping which I can personally attest to on V4A 2505. I just do a search for 'sound' in Adhell.
Excellent post by the way. I have enjoyed the layout and think it is very easy to read. Not overwhealming at all like some other guides I have attempted to follow. I am trying out your sound mod as we speak... thanks! :good:
Have you had any problems with the external sd card ,copying or moving from internal to external sd and files become corrupt after finishing , I had this problem on mm ,but after n I didn't until latest update
Not I! Everything works great as long as you follow the OPs instruction. I am in the process of modifying this method just a tad by attempting to update the modem with the new Verizon QH1 firmware....we shall see! Ill be running some tests to see if there is a difference at all...I doubt it though.
Battery life???
Anyone using this root method long enough to draw some decent comparisons of root vs nonroot battery life? The insane battery drain is the sole reason i haven't rooted my phone running MM (been lazy to upgrade, but used my mom's phone running stock, bloated nougat and holy crap that phone was fast XD)
Works with latest update
Does wifi calling work on the u firmware or is that only a Sprint firmware feature? Just got aS7 trying to decide on rooting the Sprint firmware or switching it to the U firmware
sent from my Wicked S4/S6 hybrid
bodyshop said:
Does wifi calling work on the u firmware or is that only a Sprint firmware feature? Just got aS7 trying to decide on rooting the Sprint firmware or switching it to the U firmware
sent from my Wicked S4/S6 hybrid
Click to expand...
Click to collapse
I think it's a sprint firmware feature, you'll need the apk for it.
Bricked during U firmware flashing
I tried all steps, the phone isn't coming on only, plus it is not being detected by my laptop also.
leeboski44 said:
To my knowledge the only thing that should be checked under the Options menu is Auto Reboot and F. Reset Time. Nothing else should be checked but those two. You should not need to use the PIT file at all. Leave that alone. In your post you state the g930 SPT...did you mean g930 SPR because I am not familiar with an SPT version of our firmware.
Try downloading unmodded(stock) version of ODIN 3.12.7. With that version ODIN I can flash anything to my phone with no issue at all whether it be eng boot or stock firmware and I have done all kinds of crazy combinations of these firmwares on the s7.
Simply load AP into AP, BL into BL, CP into CP, and make sure you load CSC_OYM on the first time loading the U firmware. Also, personally I always delete cache 3 times in recovery followed by 2 factory resets before I go into the download mode. And like the OP stated, clear cache after any flash as well.
Hope that helps...just remember that as long as there is stock firmware, and ODIN...you "should" always be able to return to a stock phone. Nothing is impossible, but you get the drift. :good:
I am so thankful the U firmware's LTE icon is soooo much larger than the P firmware. I can easily tell when I am on the LTE+ network ever since the switch, and guys don't forget to go the easy route when uninstalling the Samsung apps that come with the U firmware. Very simple...Settings>Device Maintenance>Storage>Apps>Select All. Make sure that no other apps have been installed when you do this or else you will simply need to select each app individually. But the stock uninstaller is amazingly fast....it surprises me till this day.
To the OP, I'm not sure if the Beats Audio requires the same as V4A, but in my experience Adapt Sound, Sound Alive, and SplitSoundService should be disabled by your Package disabler prior to flashing the EngBoot AP. It removes any potential popping which I can personally attest to on V4A 2505. I just do a search for 'sound' in Adhell.
Excellent post by the way. I have enjoyed the layout and think it is very easy to read. Not overwhealming at all like some other guides I have attempted to follow. I am trying out your sound mod as we speak... thanks! :good:
Click to expand...
Click to collapse
can you get back into download mode by pressing POWER+HOME+VOL DOWN then VOL UP?
If so you can reload the factory firmware through ODIN and flash back to stock.
Hesitant on rooting... Mainly for battery life and lag. I remember the previous bootloader caused lag and you'd have to adjust cpu properties to kinda counter act the lag. That the case with this root method?
Sent from my SM-G930P using Tapatalk
Related
Here is a way to gain root if you all ready have the latest NH5 or NK2 firmware on your phone.. This way you dont have to revert back to an older complete firmware. This method also does not wipe out any of setting or mods that you may have done before you decided to root, like ringtones, clock settings, alarm settings, notifications etc.... If you update to the latest firmware and you use wanam or xposed, You will have to re install the framework from xposed to get all you settings restored. Once you install the Xposed framework you will have to restart the phone, all the modules should be restored to the way it was before you did the update.....This method should not trip Knox.
Before you try this method, you should disable Lookout apk and go into settings-general-security and uncheck verify apps, also put a check on unknown sources, then under security policy updates, uncheck the update box, also make sure to uncheck send security reports. This should prevent any hang ups while trying to install super user apk and disabling knox hang.
After you get root and back on NH5 or NK2 you can go back and put those checks back only if you plan on using the Knox security stuff, but it is not necessary if you dont. It does not affect anything you do with your phone anyway. This is up to you to decide. HAPPY ROOTING.. LOL
Thanks goes to @iworkout for pointing it out, as i did not run into the hang under superuser install for i just automatically do this when i root a phone without thinking.
.
.
1. Download these files to your computer and unzip them.. (ATTENTION,,, These boot.tar are not the bootloader.tar that everyone thinks it is. These are just boot.img (Kernels) needed to root and return back to latest stock with root.)
A- NE6 Boot.Tar----- NE6 BOOT.ZIP<<<< This is the kernel to root with.
.
B- NH5 Boot.tar------ NH5 BOOT.ZIP <<<< Earlier firmware before NK2, you only need to use this if you want to stay on NH5 otherwise skip this one..
.
C- NK2 Boot.tar------ NK2 BOOT.ZIP <<<<< This is the latest TMO Firmware as of 11/10/2014.
Download these files to your phone:
.
C- Download Towel Root from here ( TowelRoot ), and SuperSu ( from the Play Store) to your Phone..
2. Once you have the files unziped, Open up PC ODIN 3.09 which you can get here PC ODIN 3.09 .
.
3. Once you have opened up PC odin, click on AP and load the NE6 boot.tar.md5 file into the slot.
.
4. Put your phone into Download mode, By powering off the phone and holding the volume down and home button at the same time and press the power button, once you see the phone start to boot let go of the power button and you phone should go to download mode, Make sure you press the volume up button to enter download mode.
.
5. Connect the phone to the computer, Make sure the PC ODIN sees your phone, (If not make sure you have the latest drivers loaded.) Once PC odin sees your phone and you have the file loaded in the AP slot, you can go ahead and start the flash, this should only take about 30 seconds to complete and the phone should reboot. Once your phone reboots you should have NE6 Kernel loaded onto you phone. You shouldnt have any fc's ( as i did this and did not have any FC's).
.
6. Once your phone reboots click on Towel root and click on " Make it Rain". Your phone should now have root, You can close towel root,
.
7. Open up SuperSu and install the Binarys into your phone, Make sure you click Normal install and not CWM/TWRP. You then will be prompted to Disable knoxs, You click yes, (I clicked disable and have had no side effects.) You will have to reboot to make sure Super user takes effect. You can check to see if you have root by downloading root checker of your choice from the playstore.
7a, If you some reason you get an error saying the super user failed to install, Dont worry, just reboot your phone and and re run super su apk and you will see that it actually did install super user, you can verify by using root checker to verify. You do not need to restore your phone back to stock and start over.
.
8.Once you verified that you have root, You can now go back to step 3 and load the NH5 or NK2 Boot.tar.mds into the AP slot of Odin, and follow steps 4- 5. That is it. You now should be back on the latest NH5 or NK2 kernel and have root. You can check by usng root checker and to see if all your info, you can download Samsung Phone Info from the playstore, and this will show you all the files and knoxs should be 0x0.
.
Here is the full T-Mobile Stock NK2 Rom, Just in case you have to Odin back to stock if you mess up after you root and or want to take the Official update, But be warned that Official updates from any carrier may block Root.
.
Download------ Stock Full NK2 Rom 11/10/2014.
Here is the full T-Mobile Stock NH5 Rom, Just in case you have to Odin back to stock if you mess up after you root and or want to take the Official update, But be warned that Official updates from any carrier may block Root.
.
Download------ Stock Full NH5 Rom.
If you are having issues with odin failing, I would try a different cable, one that is not usb 3.0. I have read on the forums that some people have been having issues with odin failing due to the new usb 3.0 cable that samsung has issued with the Galaxy S5. Most people are using computers that are not able to support 3.0 usb, and this may be an issue for some with odin. This is just an idea so it may or may not work for you. If it still fails i would try a different usb, maybe one on that is on the back of a desktop instead of one in front, and maybe a different computer all together..
.
.
I only use a windows (Currently using Window 7) / linux pc to do most of my work on android. So i know this method and odin works. It seems that some users are having issues with mac and odin, so be carefull. Personally if you plan on working on android you should purchase a cheap windows pc or laptop. Plus you can dual boot a win pc to do linux as well. Linux is what i use to do alot of my cooking of roms with. So if you are using an apple product to do your flashing, than unfortunatly I can not help you with that.. Sorry.
.
Now remember that I am not responsible if you void your warranty or if you break your phone. This method worked for me and i found it easier and quicker this way. If something did not work then you did something wrong or did not read the instruction correctly.
.
If this method helped you in any way please hit the thanks button .. If the Mods would like to make this a sticky, please do. Thanks
Can anyone confirm that this works
{
"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"
}
Thanks for posting this method - I just got a new S5 that came with NH5 and was about to try it, but the files you linked to don't match the files in your description.
"NE6 BOOT.ZIP" links to a file called "NE6Kernel.zip"
In Step 3, you say it should unzip to "NE6 BOOT.IMG" but instead the file is "boot.tar.md5"
The same goes for your NH5 link & the file inside.
Should I just ignore the mismatched file names and follow the same instructions?
iworkout said:
Thanks for posting this method - I just got a new S5 that came with NH5 and was about to try it, but the files you linked to don't match the files in your description.
"NE6 BOOT.ZIP" links to a file called "NE6Kernel.zip"
In Step 3, you say it should unzip to "NE6 BOOT.IMG" but instead the file is "boot.tar.md5"
The same goes for your NH5 link & the file inside.
Should I just ignore the mismatched file names and follow the same instructions?
Click to expand...
Click to collapse
Yes just ignore the file names and follow the steps. Cause inside the zip they are correct file name--- Boot.tar.md5 is actually a kernel that you are installing to get root. And pc odin does not reconize any other name but boot.tar.md5. I tried to rename the files and odin rejected it. So when you unzip the Boot.Zip, you know whats inside of that folder. Also renamed the files in op to make it less confusing..
.
If This helps you please hit the thanks button..
galaxyuser88 said:
Yes just ignore the file names and follow the steps. Cause inside the zip they are correct file name--- Boot.tar.md5 is actually a kernel that you are installing to get root. And pc odin does not reconize any other name but boot.tar.md5. I tried to rename the files and odin rejected it. So when you unzip the Boot.Zip, you know whats inside of that folder. Also renamed the files in op to make it less confusing..
.
If This helps you please hit the thanks button..
Click to expand...
Click to collapse
Done. It worked exactly as you described. Only hiccup was when SuperSU first attempted to disable KNOX, I got a message in my notification panel, "Security notice: unauthorized actions have been detected - reboot to undo changes."
My phone came with Lookout security installed, so I don't know if that had anything to do with it. I went to task manager and stopped Lookout and SuperSU (which just seemed to be hanging) and ran SuperSU a couple more times. It said KNOX disabled on the 2nd run.
Rebooted & installed root checker, verified root, installed NH5 in Odin and then verified root again. Thanks!
iworkout said:
Done. It worked exactly as you described. Only hiccup was when SuperSU first attempted to disable KNOX, I got a message in my notification panel, "Security notice: unauthorized actions have been detected - reboot to undo changes."
My phone came with Lookout security installed, so I don't know if that had anything to do with it. I went to task manager and stopped Lookout and SuperSU (which just seemed to be hanging) and ran SuperSU a couple more times. It said KNOX disabled on the 2nd run.
Rebooted & installed root checker, verified root, installed NH5 in Odin and then verified root again. Thanks!
Click to expand...
Click to collapse
Yeah i didnt have that issue, as soon as i got the phone i disabled that lookout crap. Also already had the security check also disabled, as when you install apks from outside the playstore, you are told to disable the security checks.
I will have to add that to the op when i get home and at my laptop.
It works
It works as described. Only hiccup was disabling KNOX, SuperSU hung for a minute so I restarted and opened SuperSU again. It asked if I wanted to disable KNOX. I said yes and it disabled it successfully almost immediately..
Works!
nguyener said:
It works as described. Only hiccup was disabling KNOX, SuperSU hung for a minute so I restarted and opened SuperSU again. It asked if I wanted to disable KNOX. I said yes and it disabled it successfully almost immediately..
Click to expand...
Click to collapse
This was my only hangup, as well. Beyond that, everything went smoothly, and I have root access with no Knox trip.
nguyener said:
It works as described. Only hiccup was disabling KNOX, SuperSU hung for a minute so I restarted and opened SuperSU again. It asked if I wanted to disable KNOX. I said yes and it disabled it successfully almost immediately..
Click to expand...
Click to collapse
AndreTheShadow said:
This was my only hangup, as well. Beyond that, everything went smoothly, and I have root access with no Knox trip.
Click to expand...
Click to collapse
Yeah that is something with superuser and not the method. Maybe when they upgrade the supersu apk, it may correct that. But good to see that this helped out to acheive root for ya.
Thx worked like a charm. SuperSu did hang when i tried to disable knox. I just rebooted and used SuperSu again and it disabled with no problems. Now if someone could just point me to the volume boost hack I will be good. I cant find it for the life of me.
So by clicking "Disable Knox" will that prevent me from using ALL the apps like PayPal with FINGERPRINT login & Google Wallet to tap & pay? Isn't Knox also needed for private mode?
On the flip side, what if I click "NO" & keep Knox enabled? Can I still root? Will Knox counter be tripped?
Will this affect my ability to upgrade to Android L via normal stock method?
Does this affect anything like that negatively? I'm having trouble searching the internet for hours about these fine details. Thanks for this awesome bit of info!
Hypoxic1 said:
So by clicking "Disable Knox" will that prevent me from using ALL the apps like PayPal with FINGERPRINT login & Google Wallet to tap & pay? Isn't Knox also needed for private mode?
On the flip side, what if I click "NO" & keep Knox enabled? Can I still root? Will Knox counter be tripped?
Will this affect my ability to upgrade to Android L via normal stock method?
Does this affect anything like that negatively? I'm having trouble searching the internet for hours about these fine details. Thanks for this awesome bit of info!
Click to expand...
Click to collapse
Iam not sure what will not work if disable knox. I dont use anything that might need knox, so i can not help you there. I have had no negative affect from disabling knox.
You can always try it and see what happens. The worst thing you will have to do is odin back to stock and try again. This is how i found disabling knox did not affect my phone or the apks i use in anyway. Yes you can choose not to disable knox and you will still have root.
As far as upgrading, you can do it 2 ways.
1. Odin back to stock and take the upgrade. But be warned that if you take a stock update, you may lose the ability to root, if the update closes the holes.
2. You can wait for one of the great devs to take the update and clean it and post it in xda. This is the safer bet.
Thank you for the quick & informative response! I really do appreciate your time.
Hmm, I took the plunge & CAREFULLY read, re-read, re-read again to be sure of the instructions. It keeps giving me a fail now. When I click START in ODIN, it's like it doesn't wait for the phone to do it & gives me the fail. When looking at the phone, I can see the line/bar thing drawing from left to right & before it is finished "drawing" that line, ODIN gives me the fail. Great...
OK, got it to work by downloading the FULL 1.5GB files from another thread. But I still used YOUR instructions. Whew! What a task.
LOL, wow I messed up. Now I'm back on NH5 & it unrooted. OK, so now I've redone it again & back on a ROOTED NE6. I'm afraid to try the NH5 since it failed before & bricked my phone. Not sure how to proceed.
Hypoxic1 said:
OK, got it to work by downloading the FULL 1.5GB files from another thread. But I still used YOUR instructions. Whew! What a task.
LOL, wow I messed up. Now I'm back on NH5 & it unrooted. OK, so now I've redone it again & back on a ROOTED NE6. I'm afraid to try the NH5 since it failed before & bricked my phone. Not sure how to proceed.
Click to expand...
Click to collapse
Ok why did you go back to ne6? If you all ready were on nh5, than my methods works perfectly, except for a hiccup in su. Seems like you did something wrong. I would load the full factory stock nh5 rom thru odin and try my method again. This only works on a full nh5 stock rom. If you were on some other firmware(older) then trying to upgrade to nh5 with my file will not work. It is only the kernel and not the whole rom. Hence the title.
If pc odins fails before you start, then it sound like the drivers are not loaded correctly, or one of the files you downloaded is corupt. Check to make sure the md5 matches and or redownload the files again, and try to use chrome to download. Afh seems to have issues with other explorers. Dont ask cause i do not have a clue as to why. Also if you continue to have issue, i would try a different usb port, different cable and or a different pc.
I know this method works. For i have done it about 20 times, i like to flash stuff on my phone to see what works.
I did start with a new phone with NH5, but your method didn't take as stated in my prior post. I was extremely careful to follow the directions properly, as well. I just got this S5 brand new from T-Mobile the other day & already had latest NH5 on it.
So to UNBRICK my phone, I had to use the method by ashraf sharif (http://forum.xda-developers.com/tmo...tutorial-towelroot-onlatest-firmware-t2908019). But I'm afraid to proceed to updating to NH5 using his method, hence why I'm on NE6 at the moment.
Hypoxic1 said:
I did start with a new phone with NH5, but your method didn't take as stated in my prior post. I was extremely careful to follow the directions properly, as well. I just got this S5 brand new from T-Mobile the other day & already had latest NH5 on it.
So to UNBRICK my phone, I had to use the method by ashraf sharif (http://forum.xda-developers.com/tmo...tutorial-towelroot-onlatest-firmware-t2908019). But I'm afraid to proceed to updating to NH5 using his method, hence why I'm on NE6 at the moment.
Click to expand...
Click to collapse
If you are afraid to use my method, then purchase mobile odin pro and use that to upgrade to nh5. Read the thread were you got the full ne6 and follow his directions. I honestly can not understand what the issue is that you are having. Cause like i said before, I have done a full odin back to nh5 and used my method with no issues. My phone also came with NH5 from tmo. Sorry.
No, no. Don't be sorry. You're awesome for posting all this & helping me out. I have no idea why it did not work also since I've made no mods up to this point. I carefully read everything & did days of research prior to jumping into this on this phone. This sure isn't as easy as a Nexus device! I basically have OCD when I do this sort of stuff, so I carefully read every word many, many times.
Thanks for the "go ahead" tip on the mobile odin pro. I will do that since you recommend it. I'm just unsure how he states the bootloader needs to be flashed separately. I'm a bit scared of PC odin at this point, lol.
Hypoxic1 said:
No, no. Don't be sorry. You're awesome for posting all this & helping me out. I have no idea why it did not work also since I've made no mods up to this point. I carefully read everything & did days of research prior to jumping into this on this phone. This sure isn't as easy as a Nexus device! I basically have OCD when I do this sort of stuff, so I carefully read every word many, many times.
Thanks for the "go ahead" tip on the mobile odin pro. I will do that since you recommend it. I'm just unsure how he states the bootloader needs to be flashed separately. I'm a bit scared of PC odin at this point, lol.
Click to expand...
Click to collapse
That is why i figured out my method, too many steps with the other thread. I orignally did it his way many times on my phone and it does work, just alot of steps and it takes alot longer to flash and root and then flash again.. The problem with mobile odin pro is it doesnt flash all the files that a stock rom has in it, this is why you need to flash some files with pc odin and then the rest with mobile odin pro..
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
Below, not only will you find step by step instructions on how to root your device but also a FAQ section in post #2 that will guide you through the problems most of us encountered in the beginning. It is highly recommended that you read through all of it. Basic knowledge of ADB is required and if you don't have it then you should definitely read the FAQ section for ADB set up. Make sure you have all the files downloaded.
Update 10/25/2016: Attached at the end of this thread is a modified debloat script for knox removal and a few other apps. This will make your root experience a heck of a lot smoother than before. Just flash the zip using FlashFire without changing any settings. You may notice a reboot or two. There are few bloatware apps that will still be there (amazon shopping, amazon videos, amazon photos, etc) that you'll have to remove manually. Happy flashing and don't forget to hit that Thanks button down below!
Disclaimer:
This root method is NOT for beginners. It is NOT easy. If you don't get it then DON'T do it. Especially if you're worried about voiding the warranty and blah blah blah. Simply put, don't do it if you don't have the slightest idea of what you're doing. I'm tired of complaints. This guide is not for the faint of heart. Do this at your own risk!
Package Disabler Pro is required to get this rooting method working. Yes, it costs money ($.99) but it's the way I acheived this work around at the moment.
Be prepared to lose data (LTE) connection but don't be scared as it's an easy fix.
Make sure you don't have Secure startup set up before you start the process. Having this set up causes issues.
Must have ADB set up and installed system-wide.
This root method should be used with PE1 firmware for both the GS7 and the GS7 Edge. Although this root method might work with the latest firmware, users have been reporting issues dealing with APN's on the newest update. Look at post 2 FAQ's returning to stock for flashing PE1 firmware through Odin.
Do not update to PJ2 if you want to keep service with your root. Phone calls and text messages won't come through after rooting on PJ2.
Files you will need:
Odin by Princecomsy: http://d-h.st/gsDA
G935A: http://d-h.st/kDWz (S7 Edge)
G930A: http://d-h.st/o3hm (S7)
SuperSU: https://download.chainfire.eu/970/SuperSU/SuperSU-v2.76-S7QC.zip
Click on the BLUE "download" links. Extract everything into a folder easy to locate.
Here we go:
After downloading and getting set up Package Disabler Pro, you'll need to disable the following three packages:
samsung dm phone interface
samsung dm service
securityLogAgent.
Use the search box to easily find these packages.
Power off your device and boot into download/bootloader mode by pressing and holding the volume down, home, and the power button. Press volume up to get into bootloader.
Open PrinceComsy odin and flash the engineer boot.img by clicking AP and navigating to the file for your model. Click start and your device should reboot by itself.
Enable developer options by going to Settings>About Device and tapping Build Number till it shows Developer mode has been turned on. You will now have Developer options under the settings menu.
Enable USB debugging in the Developer options settings.
Extract the SuperSU zip and run the root.bat file. Your phone will reboot if the script is successfully ran.
Next, we'll get LTE data back:
Method A: BuildProp Editor (easiest method)
Open Build.Prop with BuildProp Editor and change the following settings:
ro.cdma.default_numeric=310000 to 310120
ro.cdma.default_alpha=Chameleon to Sprint
ro.build.characteristics=Chameleon to Sprint
Make sure you grant root permissions when it asks. You may have to try this twice. Reboot and LTE should stick.
Method B: Manual activation (also if you're not able to make any calls)
Enable the three packages disabled in step 1. Go into the phone dialer and type in ##72786# and your phone should reboot and begin the activation process. After the 5th retry, it will manually activate itself. It should say "writing to device". Don't click done yet. Press the home button and disable the three packages once again. Reboot.
Alternatively, after renabling the three packages and dialing ##72786#, you can go into Settings>Activate this device and manually try to activate it yourself. It still must say "writing to device". Don't click done. Disable the packages once again. Reboot. Voice and LTE should stick.
Download S7_or_S7Edge_Fixes_V15.zip to your internal or external storage and install install FlashFire from the playstore.
Open FlashFire and let it acquire root access. Click the + button at the bottom right corner then click on Flash ZIP or OTA. Navigate and select the S7_or_S7Edge_Fixes_V15.zip. file. Leave the options alone and click the check in the top right. Scroll down to the bottom and click flash. Your phone will reboot and flash the zip. This can take a while.
Go to Settings>Lock screen and security>Other security settings>Security policy updates and turn off "Automatic updates" and "Wi-Fi only". Reboot. This seems to be the culprit of the 7 day soft brick.
Open back up Package Disabler Pro and search for "software update". Disable both packages (com.sec.android.soagent and com.wssyncmldm)
Enjoy your rooted device with minimal to almost no lag.
???
Profit.
As always, be sure to donate to the people who actually helped achieved root: @Princecosmy, @br3w3r, and @Chainfire
For the bounty donate to [email protected] PayPal
Shout out to @psouza4, @izzibew26, @mhill1986, @LeftyGR, @Soooperstar, and to all of you who are contributing in making this root method easier everyday. Thanks for the feedback.
Originally, it started getting interesting at post #185:
http://forum.xda-developers.com/att-galaxy-s7/how-to/bounty-att-s7-root-exploit-t3341274/page4
I'm also keeping track of the Sprint Galaxy S7 Edge (SM-G935P) version:
http://forum.xda-developers.com/sprint-s7-edge/how-to/root-t3410424
FAQ's:
My WiFi credentials keep on getting erased after a reboot. What gives?
A: This seems to be an issue across all the QC S7 variants. Here's what I did to fix it. Download BuildProp Editor and change: ro.securestorage.support=true to ro.securestorage.support=false
Credit goes out to: @guaneet for this fix
Can I install Xposed?
A: Yep. Here's how to do it:
fnztakedown said:
Alright. Here is a DB link of the two files I had installed to get xposed working. To flash this you will need flashfire.
Process is simple. Download both files and install the apk.
Open flashfire> select flash new file> find the xposed zip, flash. Give it a solid 5-7 minutes during boot up.
Ensure you do not have any major packages disabled and ensure you have BACKED UP YOUR ROM VIA FLASHFIRE. Please be aware, this was successful for me on the 935T and I do have random reboots at time. I cannot confirm this is the cause yet. I would also suggest finding the uninstall zip in the event you have issues you can flashfire back.
{
"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"
}
https://www.dropbox.com/sh/0yabdfx6ao69dpd/AAAnu-9Jv8W9stjjuG1Nq5jba?dl=0
Click to expand...
Click to collapse
Credit goes out to: @fnztakedown for these instructions
I'm having issues with ADB. Any help?
A: Easiest way to install ADB and its subsequent drivers would be to get it from here:
http://forum.xda-developers.com/showthread.php?t=2588979
It's SO easy to install and it takes most if not all of the hassle out of it.
Credit to @Snoop05 for this easy ADB installer.
How do I enable USB debugging?
A: Go to Settings>About device and tap Build number until it shows Developer options has been enabled.
I'm stuck on the LTE splash screen. What do I do?
A: Press and hold the Volume Down + Power button down until your phone restarts. If you keep on getting stuck at the LTE splash screen you may have to factory reset your device. As soon as your phone restart quickly press the volume up + home + power button and let it boot into recovery. Wipe data/factory reset and cache partition.
I'd like to unroot and return to factory stock. How would I go about this?
A: Head on over to @psouza4's post HERE and follow his steps in the return to stock section. The steps are easy and he's posted mostly all the firmware.
[*]Does this method trip Knox?
A: No, it doesn't. And flashing back to stock will allow Knox to work again, as long as you didn't flash files from other sources (there are some that will trip Knox, so be careful).
[*]Does Samsung Pay work?
A: No, sorry. They can detect the rooted boot environment through a driver, so you can't even hide root from the app using RootCloak.
[*]Does Android Pay work?
A: It does, but you have to make a change that disables root and then reboot your phone. You can toggle this back/forth without flashing, but you either get root or Android Pay at any one time.
[*]What happens if I brick my phone?
A: As long as there are stock images to flash back to, it's almost impossible to do this no matter how badly the process goes. Check that we have stock images; if we do, then we can always flash them over the device using the unroot method in this guide. That practically guarantees a return-to-stock experience for a phone as long as it doesn't have any serious physical damage preventing it from powering on.
[*]I installed the ADB system-wide on my Windows computer/laptop, but I see "'adb' is not recognized as an internal or external command, operable program or batch file".
A: Your user profile path can't contain a space. That means if your Windows user is 'Somebody Nice' and thus your Windows user path is 'C:\Users\Somebody Nice', the install will fail. You can create another user on your computer (if prompted for a Microsoft login, choose to make only a local account) and enter a short, single-word name for your user. Sign into and use that user profile instead. Also, the path where you extract the SuperSU package can't contain a space, so try extracting them to somewhere simple like perhaps C:\S7Root.
More answers to FAQ's to come.
colormedroid said:
Just got home to test this out. Currently on PC5 since I've been waiting for this day to come. Will post back once I have results.
Just flashed the engineering boot.img. Make sure you boot into BOOTLOADER mode when using odin to flash this because the instructions don't show this. Also, make sure to back up all your stuff because most likely this will involve a factory reset.
Update #3: So, seems like our variant seems to have issues with the activation process. Here's what I did to fix it. It's a temporary fix until it gets figured out completely but it's a fix none the less.
1. Flash engineer boot.img through odin.
2. Factory reset/wipe
3. Go through the setup process without actually activating (once it gets to the activation screen press and hold the back button).
4. I signed into my google account through wifi and I downloaded Package Disable Pro+ Samsung (https://play.google.com/store/apps/details?id=com.ospolice.packagedisablerpremium). Yes it costs money but it's the way I achieved this work around at the moment.
5. I went into settings>Acitvate this device.
Don't click "done" after it gets activated.
6. Press the home button to get to the main screen and open up Package Disabler Pro+ Samsung
7. After Package Disabler Pro is set up... I searched for Samsung DM Service and I disabled it.
Voila! No more rebooting. Like I said, this is hopefully temporary until it gets figured out.
Now on to installing SU. I will post back with pictures of Root Checker.
Update #4: Installed SU through the root.bat file in the instructions. Took a screenshot of root checker. Here it is in all it's glory.
http://imgur.com/FHvak9Z
Almost forgot to mention that it seems that the engineer boot.img does lag the system a little bit so again, try it at your own risk. I for one will be trying this out like I have with all my older devices. Next step is Adaway =D.
Click to expand...
Click to collapse
I can't believe it! Have you tried to install adaway and xposed yet? You said the system lags a bit, is it laggy enough that it would become frustrating after using for a few minutes? I'm still on my Galaxy S5 and just deciding whether I should head to the Sprint store today or not.
slickdealers said:
I can't believe it! Have you tried to install adaway and xposed yet? You said the system lags a bit, is it laggy enough that it would become frustrating after using for a few minutes? I'm still on my Galaxy S5 and just deciding whether I should head to the Sprint store today or not.
Click to expand...
Click to collapse
Adaway installed successfully. Haven't installed xposed but someone said that you could do it through flashfire. That might have to wait for tomorrow as today is the 4th. M'urica!
*whoops, forgot to quote you my bad.
Sent from my SM-G935P using Tapatalk
It works
I tried it and it works also have adaway installed through f Droid
Can i install this update?
Sent from my SM-G930P using Tapatalk
You should NEVER install an over the air update if you want to keep root. Always get your updates from xda.
Sent from my SM-G930P using XDA-Developers mobile app
sml2004 said:
View attachment 3803555
Sent from my SM-G930P using XDA-Developers mobile app
Click to expand...
Click to collapse
Good job getting it working!
Sent from my SM-G935P using Tapatalk
colormedroid said:
Good job getting it working!
Sent from my SM-G935P using Tapatalk
Click to expand...
Click to collapse
Now I guess we need Hotspot mod. And a damn sd card fix. Lol
Sent from my SM-G930P using XDA-Developers mobile app
Has anyone tried this on PF2? I honestly had to update and have been taking updates, because this is one ****ty sluggish phone. It seems to get worse the longer I have the S7. This is much like what happened with the S6, so root would be appreciated to alleviate it.
mafaesto said:
Has anyone tried this on PF2? I honestly had to update and have been taking updates, because this is one ****ty sluggish phone. It seems to get worse the longer I have the S7. This is much like what happened with the S6, so root would be appreciated to alleviate it.
Click to expand...
Click to collapse
Pf2 works
Sent from my SM-G930P using XDA-Developers mobile app
---------- Post added 5th July 2016 at 12:22 AM ---------- Previous post was 4th July 2016 at 11:50 PM ----------
Could someone drop their stock feature.xml file here?
Sent from my SM-G930P using XDA-Developers mobile app
I lost service. But I have root. I am Sprint. I thought that if I left SimCard in unlike with my S6, I would have service, but no. It has none. How do I fix it
I have SM-G930P that is still on APB5 can I do the process with APB5 or is there some other step that I have to do?
Thanks in advance!!
BTW, OP thanks for putting this thread together!
CharmedWhovian said:
I lost service. But I have root. I am Sprint. I thought that if I left SimCard in unlike with my S6, I would have service, but no. It has none. How do I fix it
Click to expand...
Click to collapse
Read post #2 please.
Sent from my SM-G935P using Tapatalk
treepog said:
I have SM-G930P that is still on APB5 can I do the process with APB5 or is there some other step that I have to do?
Thanks in advance!!
BTW, OP thanks for putting this thread together!
Click to expand...
Click to collapse
No problem. ?
This should work on APB5. Just make sure to read post #2 for activation problems.
Let me know if y'all need any help!
Sent from my SM-G935P using Tapatalk
Gear VR
I saw on AT&T bounty thread that gear vr may break. Can anyone confirm that this happens?
I have been waiting for root, using my S5 for things that I need root for. I do not want to lose the VR 3d video player and games I play just for root.
N3Cr0 Cr0W said:
I saw on AT&T bounty thread that gear vr may break. Can anyone confirm that this happens?
I have been waiting for root, using my S5 for things that I need root for. I do not want to lose the VR 3d video player and games I play just for root.
Click to expand...
Click to collapse
Actually, I was very happy that the Gear VR was still in action. So much so, that I did not notice that my Mobile Network State was Disconnected.
CharmedWhovian said:
Actually, I was very happy that the Gear VR was still in action. So much so, that I did not notice that my Mobile Network State was Disconnected.
Click to expand...
Click to collapse
haha, made me lol.
Sent from my SM-G935P using Tapatalk
Crap, now I went from having no service, to Avtivate Bootloop to Logo Bootloop. I rather have no service. I can't leave out of the house without music. wth do I do
Updated. I am now back to stock. but for a weird reason, Mobile Network state is still disconnected.
Newest Nougat rom is availabe at here: https://forum.xda-developers.com/galaxy-j7/development/rom-axvy-rom-sm-j7108-stable-sexy-af-t3687461
I posted previously for j7108 https://forum.xda-developers.com/galaxy-j7/development/j7108-android-6-0-1-marshmallow-rom-t3542561
This Rom contain Google Play too.
Bloatware is heavily removed, after flash this Rom you will able to uninstall them!
- using newest update from Samsung
- Camera seem to focus faster and able to capture clearer picture
- phone app has new transition
Lot of preloaded apps/bloatwares are removed properly, it will be very long if I list them all.
Tips for keyboard:
Set Keyboard Swipe to Cursor Control, when you typing you can move the cursor up down left right easily
Keyboard size is helpful especially for those screen with problem
Download language pack to enable spell checking.
Edited build.prop for optimisation, check that old thread. Lot are the same except I remove the nobootanimation already.
My warranty is voided last time because I didn't know about frp lock while flashing wrong rom of other country.
To close Frp Lock, enable Developer Options(google it for step), enable OEM Unlock before flashing
Yet I did not add root to this rom for now, comment if you need it.
I do not know if this rom will void your warranty. Feel free comment to tell us. (Mine after flash in Odin mode said official firmware thought)
In summary I think this rom is better, if you have any request, leave a comment below
Will Void waranty!!!
Cannot use pin version, for those who don't have SD card or phone insufficient space:
Download 720.9mb, extract 1 time and ready to flash using odin. Use AP: https://mega.nz/#!ucl01DaA!APSN35pyT0qH4RnP4GNoc9J8C6wVRlpC5TKBfCBvXJE Set lock screen pin not working
No error version. No need format or wipe your phone and all Knox Carmode stub etc removed in compare to top one:
press backspace to hide keyboard. Files below all extract one time and ready to flash.
1. Flash this first: https://mega.nz/#!qUsXmbwD!Q-rr7wJW7AKYi0xsTIZZvhhDG2zHCCbDAWiAA_mS4JY
2. Flash TWRP using odin https://mega.nz/#!ycc3nLBR!_do-RBTeOfIWvDK5enea8tJXDn5w1hyWuL7j7ZCuh5I select AP
3. Put zip to Phone folder or SD card, install using twrp HOME+POWER+ volume up: https://mega.nz/#!aNFECCRS!84XOLiu_-nyMoSSDTS0ym6dA3xek7Cc2GEHlbib30sE
Personal or application data will remain, this is just like update the Rom.
I have tested this rom before post it but still back up your phone. First boot time will be quite long, please wait for it.
Fyi, when preparing update it take lot of time processing, don't interrupt it and it will come to the last step optimise app.
First boot is always slow then it will be fine. Comment if you don't understand or face problem.
{
"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"
}
Credits:
Tickle My Android - @Ticklefish
SuperR's Kitchen - @SuperR.
XDA for resources
And myself @doulc
reserved, check below for more screenshot. Subscribe this thread to get nougat update
Quite amazing all functions are working fine, so far no crash and used for few day already
Cannot use pin version: Screen Lock type can't be set.
Pin won't show after lock, don't set pin because it will tell you wrong pin even it's correct when you want to reset it
To remove password you have to go to https://findmymobile.samsung.com/?p=home
I will reupload soon but busy now
Or flash back stock then change pin, not a big issue
Link updated, added twrp j7108 download link
Hopefully it help more people out there, I hope you love this Rom
Further update and improved. I have perform lot of testing. It's stable. Lot of tweaks added.
It has symbol above every key, long press to use symbol. I really love Samsung Keyboard so much, especially the cursor.
To get red underline, for typo, download language pack first. Assistant Menu is come with the phone, google to enable it.
And quick tip to make your phone faster, enable developer mode then disable animation scale. Screenshot more is very nice, I want to thanks Samsung to provide such features allow me to enjoy their product so much. I hope they add edge panel soon, most useful feature.
Here is the new download link, you can find above too, you need twrp for j7108, check above.
THIS WILL VOID WARRANTY!!
https://mega.nz/#!aNFECCRS!84XOLiu_-nyMoSSDTS0ym6dA3xek7Cc2GEHlbib30sE
Custom recovery will trigger 0X05 !!!
Do you Have Custom Rom for J7180?
Burubugyot said:
Do you Have Custom Rom for J7180?
Click to expand...
Click to collapse
What do you mean by custom Rom?
If you mean not stock firmware release by Samsung then this is a custom rom.
For ultimate fast speed and hacks for j7108 Rom pm me.
It's release for private only
I installed this ROM but I seem to still have all the bloatware. You say after this flash I'll be able to uninstall bloatware, but it is as before, if I select uninstall it only gives me option to uninstall updates and return to factory version of apps.
Hmm, should I have wiped system and cache before flashing?
Clearly I have your new ROM installed because I now have the edge app which I did not before. Or, what did I miss.?
Before flashing I was at version J7108ZHU1BQB1 which is same as what you suggest we upgrade to first. Then I used Odin to flash j7first.tar and then J7108twrp-3.0.3.0.tar, then I used TWRP recovery to install ExcellentTweakedTrimmed.zip
billeuze said:
I installed this ROM but I seem to still have all the bloatware. You say after this flash I'll be able to uninstall bloatware, but it is as before, if I select uninstall it only gives me option to uninstall updates and return to factory version of apps.
Hmm, should I have wiped system and cache before flashing?
Clearly I have your new ROM installed because I now have the edge app which I did not before. Or, what did I miss.?
Before flashing I was at version J7108ZHU1BQB1 which is same as what you suggest we upgrade to first. Then I used Odin to flash j7first.tar and then J7108twrp-3.0.3.0.tar, then I used TWRP recovery to install ExcellentTweakedTrimmed.zip
Click to expand...
Click to collapse
Yes it should and it will, can you help me check which bloatware is not removed? Look:
can be completely uninstall
That's odd, both .img and twrp version will uninstall my apps.
You say it revert to old version? Flash it again perhaps since it match stock version of that app.
Really, I have tried both of then several time for bug testing, that's why I believe it will 100% work. NO wipe required ya, this is just like updat, DON'T reset as I have tested.
I am gladly to watch it over video to see at what's the problem, if you don't mind pm me your skype username.
doulc said:
Yes it should and it will, can you help me check which bloatware is not removed? Look:
View attachment 4156572 can be completely uninstall
That's odd, both .img and twrp version will uninstall my apps.
You say it revert to old version? Flash it again perhaps since it match stock version of that app.
Really, I have tried both of then several time for bug testing, that's why I believe it will 100% work. NO wipe required ya, this is just like updat, DON'T reset as I have tested.
I am gladly to watch it over video to see at what's the problem, if you don't mind pm me your skype username.
Click to expand...
Click to collapse
Ha, OK, yes it does work. When I hit "uninstall" it gives me the same dialogue box as always before:
"Do you want to replace this app with the factory version? [Cancel], [OK]"
So I thought nothing had changed and I didn't even try to go further, But now I see that that if I select [OK], it actually does uninstall - it does not revert to the factory version like the dialogue box says it will..
I installed the TWRP version by the way
billeuze said:
Ha, OK, yes it does work. When I hit "uninstall" it gives me the same dialogue box as always before:
"Do you want to replace this app with the factory version? [Cancel], [OK]"
So I thought nothing had changed and I didn't even try to go further, But now I see that that if I select [OK], it actually does uninstall - it does not revert to the factory version like the dialogue box says it will..
I installed the TWRP version by the way
Click to expand...
Click to collapse
Glad to know that, thanks for providing feedback. Deeply appreciated
Which version of j7 supported?
Do u have a twrp flashable zip or is it just for Odin flashing...
Vivek Kantesaria said:
Which version of j7 supported?
Click to expand...
Click to collapse
For j7108 only
fullofhell said:
Do u have a twrp flashable zip or is it just for Odin flashing...
Click to expand...
Click to collapse
Note This is for j7108, look at the "no error version" that is twrp
Also twrp will void warranty mean Knox and Samsung Pay will not usable.
To everyone if your warranty is voided ald then it's ok to try
doulc said:
Note This is for j7108, look at the "no error version" that is twrp
Also twrp will void warranty mean Knox and Samsung Pay will not usable.
To everyone if your warranty is voided ald then it's ok to try
Click to expand...
Click to collapse
Ok thank you, yeah warranty was void long ago..lol
No I already have twrp and use custom ROMs on this phone all the time, I just need a flashable zip of your ROM..want to see if it works with the j700t.
fullofhell said:
No I already have twrp and use custom ROMs on this phone all the time, I just need a flashable zip of your ROM..want to see if it works with the j700t.
Click to expand...
Click to collapse
It won't work, the kernel is not compatible
This is for j7108, still if you want to try I won't stop you.
Place the custom rom in your phone at all time so when anything happen just flash that custom rom you are using now back.
Go to my thread use this link
"3. Put zip to Phone folder or SD card, install using twrp HOME+POWER+LOCK :
https://mega.nz/#!aNFECCRS!84XOLiu_-nyMoSSDTS0ym6dA3xek7Cc2GEHlbib30sE
"
That one is flashable, extract with 7z one time put it to your phone or sd card
doulc said:
It won't work, the kernel is not compatible
This is for j7108, still if you want to try I won't stop you.
Place the custom rom in your phone at all time so when anything happen just flash that custom rom you are using now back.
Go to my thread use this link
"3. Put zip to Phone folder or SD card, install using twrp HOME+POWER+LOCK :
https://mega.nz/#!aNFECCRS!84XOLiu_-nyMoSSDTS0ym6dA3xek7Cc2GEHlbib30sE
"
That one is flashable, extract with 7z one time put it to your phone or sd card
Click to expand...
Click to collapse
Thank you I have a different kernel I can flash post ROM flash.thank you I'll let u know if I have success.i appreciate your time and help
Introducing:
SamFAIL!
[Size=DEPRECATED]DEPRECATED![/size]
This ENTIRE THREAD is old, busted, and has been deprecated for some time. Please stop reading it, and go to the link below this line of text:
https://forum.xda-developers.com/galaxy-s8/development/root-partcyborgrom-aqi6-deodexed-t3702988
It has some very clear advantages over this version:
- Supports All existing bootloader revisions
- Latest version(s) of Nougat
- Huge community of support
- Telegram channel
- Preinstalled audio mods, visual mods, looks really good
- Actually still works
- very debloated without compromising many touchwiz features. It's over 50% faster on my device
- Deodexed, xposed FULLY supported.
- Rooting method improved, essentially foolproof
I don't want to have this thread closed, but I will
A New Alternative Root Method For The US Samsung Galaxy S8! (G950U Snapdragons)
Rooting your s8 just got easier.
DISCLAIMER 1: Although this method does not trip the "Knox Flag" you are still taking a risk by rooting your device. We are not responsible for your blazing fast smartphone with root! Let's hope this one doesn't catch on fire!
DISCLAIMER 1.5: THIS IS NOT FOR EXYNOS!
First and foremost, SHOUTOUTS!
- @partcyborg for finding the root method!
- @me2151 for testing on Note 8 and facilitating root on the Note 8!
- @elliwigy for... Shenanigans! And thread template
- @Chainfire For opening the door to make this root useful. He will be missed! (no he is not dead, just retired.)
- @samsung for the amazing phone and leaving rediculous loopholes open for us to root!
Disclaimer 2: The method to root should be pretty straight forward as the hard work has already been done for you. With that being said, you will need to know how to download files from the internet, extract a zip file and to use ODIN. That is basically it! Oh yea, PLEASE BE SURE TO READ ALL THE INSTRUCTIONS THOROUGHLY BEFORE ASKING FOR HELP!
Once again...
READ THE ENTIRE SET OF INSTRUCTIOMNS BEFORE BEGINNING!
There are important things to note about this process that WILL likely trip you up if you expecting them. Some things are not intuitive and may sound unimportant to follow but trust me they are. Every single step added her is absolutely necessary.
Prerequisites:
- A working computer with a working USB drive that is capable of successfully flashing firmware to your device.
- Comsey ODIN and Normal ODIN (Found in Post #2 As well)(In case you give up and want to go back to stock)
- SamFAIL S8 Custom Hybrid Combo/Stock firmware package (also in Post #2)
- A functioning Snapdragon Galaxy S8 G950U/U1 or ANY other US Snapdragon based Galaxy S8 that can run the standard 950U firmware. Must be able to boot to download mode, and NO EXYNOS OR
- The CSC file for your phone(also in Post #2)(NOTE: You MUST use the CSC matching your device or your network will not function correctly. If your CSC is not in the downloads section you must download your devices firmware and extract the CSC from it and use that one. I will continue to add CSCs as I have time to download them but please be patient as they can take a while to download. Bonus points if you can send me individual .tar.md5 CSC archives so I don't have to download 4GB of ROM.
Part 1 Instructions:
0) BACKUP YOUR CRAP This procedure wipes your entire phone, so anything that you don't want gone for good back up somewhere NOT ON THE PHONE for the duration of this process. TECHNICALLY it should be safe to leave on a SD card, but checking one accidental checkbox in Odin will make you lose it. Take the SDCard out or copy the stuff to your computer.
1) Unzip the SamFAIL S8 ZIP archive. Inside there will be two tarballs (.tar files). If you have flashed a rom before these should hopefully look familiar. NOTE: There is no CP archive because the hybrid BL_ archive contains all drivers needed to operate your device.
2) Boot up Comsy Odin. Reboot your phone into download mode. Connect your phone to your pc and make sure that you get the Blue box that signifies proper connectivity and that the Odin log has said "Added!"
3) In the AP slot, place the AP tarball. There will not be a long pause like stock ROMs as there is no md5 signature to check.
4) In the BL slot, place the hybrid combo/stock firmware package. Again, you can place these in any slot and Odin will handle it just fine.
5) Click on the OPTIONS tab, and select the following checkboxes: Auto Reboot, Re Partition, F. Reset Time, NAND ERASE ALL.
After finishing the above steps, your Odin should look exactly 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"
}
6) Read step #5 again and confirm that you have everything selected EXACTLY as shown in the picture and written in the words. Check it again and when you are sure everything is correct press START.
7) Wait for ODIN to complete the flashing of the system partition. Naturally, ODIN and your phone will see this image is not signed and return FAIL. Your device will say "Secure Check Fail: system" or something close to it. THIS IS EXPECTED, DO NOT PANIC OR GIVE UP. Your flash may have failed, but it did not fail hard enough
At this point you may be wondering "What is going on and how does failing to flash get me root?"
The answer is because of a very simople to fix (pre-launch) issue with secure boot verification. I will explain in more detail when we are done and you have root but the short story is, yes they fail the flash when it does not match a known image, but they do so at the end, AFTER all of the data has been written to the disk!
it indicates that everything is ruined and you should bring them your phone right away. Fortunately we are smarer than that. Despite not saying so, while this screen is showing the device is in fact in download mode ready to receive new firmware.
This screen will likely say something like "System Failure" and there will be instructions displayed to take your device to the nearest repair store. Laugh at Samsung's silly attempt at subterfuge.
Now, lets put that data to good use with part II:
8) Reboot the phone into download mode again (hold down power, vol down, bixby) until the device resets back to a blue-green ("Download Mode Color") screen. If you have not seen or experienced a bad flash before, this screen may be new to you. You should see something that says "OPERATING SYSTEM UPDATE FAILED" and find that your phone will boot only to this state and nothing else. DO NOT PANIC! THIS IS EXPECTED and exactly what we want. Odin/Secure Boot are refusing to boot because you flashed unrecognized code, and wants you to flash code it recognizes. Lets give them what they want.
9) If you closed Odin or hit Reset after the first clash, open it again. Plug your phone back in if necessary and ensure that Odin sees you device just like last time.
10) IMPORTANT! IMPORTANT! It is IMPORTANT that you be sure to remember to do the following: Click the RESET button onthe bottom middle of the page. Alternatively, you can Uncheck "NAND Erase All" "Re-Partition", but its extra work to remember which ones.
WARNING: IF you fail to do this, Odin will happily erase your device and have to start from scratch. Worse though is the failure mode. If you don't notice is not obvious that it is caused by this, which will likely cause you and others unecessary grief.
11) Click on the BL row again and Load the same Hybrid Firmware Combination as last time. Be sure the checkbox next to it is selcted.
12) IMPORTANT: If you did not click "Reset", be sure that the AP_ROOTEED_YSTEM tar is NOT loaded. You can uncheck the check box next to it and it will not be sent as part of the coming flash. If you do not do this, you will fail again and it will be for real this time.
13) Click on the CSC row and load the CSC file you downloaded that matches your device and service plan. Be sure that the checkbox next to it is checked.
14) Double check that your screen and options now look like this or has the same options.
- NAND ERASE is UNCHECKED
- F RESET is CHECKED
- REBOOT is CHECKED
This part is basic ODIN flashing here guys... Not rocket science!
15) Press START and watch the LOG tab to see what is happening. If it says the words "Erasing..." you have failed to follow directions and ust start completely over with step again.
16) This is where the Matic happens... Odin will flash all of the fimrware files in the tarball, and will fihnd that all of them are 100% valid signed images by Samsung. Since Odin has a very poor memory, he completely forgets that you had just flashed a bad system image, and marks your secure boot flag as "Safe" and lets you proceed to boot!
17) Have a good laugh (at least i found if funny)
18) The phone will reboot to recovery and dump you there for one of two reasons:
a) You will see the progress bar advance over a feconds to 32% or so and then stop, printing an error about faling to find resize data. This is normal and happens with every flash of CSC OYN that I have ever seen. You are safe to advance to the nxt step.
b) The recovery will immediately exit with an error that says "Failed to mount /system (Invalid Argument)". This is unfortunately bad news as it means that the failed flash attempt was not successful in writing enough data to see the file system. Do not dispair yet though! This happens sometimes with this method. Start off by starting over from scratch. If that does not work, reach out to me and I will walk you through a few procedures that will eventually fix it.
19) If you made it past step 18, all you need to do now is execute a data wipe/factory reset. This is necessary and your device will not boot withiout it, as there is no userdata image file flashed through odin.
Now, wait for the device to boot up (it will take 3-5min like most new isntalls) and then you can try out your new root!
20) Once phone boots up, Setup your device as normal and proceed to the SuperSU app. It will ask you to update the SU Binary. Select Normal method and let it do its thing. A popup should show up to disable KNOX. Follow its instructions then SU should say it was Successful in updating and it needs to reboot(You may have to do it multiple times. I belive its 2 or 3 times then its good) ENJOY SamFAIL ROOT!
NECESARY CLEANUP
The reason that this works at all is that modern filesystems like ext4 (what android uses) are very robust in the face of errors on the disks. Particularly in the days of old when everything was on spinning platters, that may moving parts was a lot more prone to failure, so filesystems were designed to keep your data safe in the face of losing parts of the disk. Fortunately for us this allos us to successfully mount and load android off of an incompleted filesystem. To make sure that the device is table, and that future SamFAIL attmpts do not degrade into "Invalid Argument" errors, we need to do a filesystem repair.
Download fsck.ext4 and push it to your device to fix any errors that cropped up from the SamFail dirty flash.
Connect via adb (or shell on your device) and run the following
FROM YOUR COMPUTER WITH PHONE PLUGGED IN AND AD ENABLED:
Code:
adb push <localpath to fsck.ext4 /tmp/
Then on the Device:
Code:
su
chmod 755 /tmp/fsck.ext4
mount -o ro,remount /system
/tmp/fsck.ext4i -f $(find /dev -name system)
It is possible that oyu will see a LOT of errors reported. Do not worry though all of the stock os will have made it through ok. Press "a" to say auto-yes to all the questions and your filesystem will be healthy from here on out.
EPILOGUE
It is HIGHLY recommended that you follow this step with the flashing of either a custom rom or a full stock /system ROM using FlashFire. The image I provided that is pre-rooted essentially has no more work done to it than that, and I have no plans to do that work anytime soon. Unforutnately my experiments with using SamFAIL to flash more custom /system partitiuons made them a lot more unstable and frequently would not boot at all. Consider this a stepping stone that requires a little less work than SamPWND used to be before more automation work was done.
The AQH3 Image in post #2 has the "warning this device has been modded" message and i took a brief stab at it but wasnt able to get it locked down. If someone wants to do so i will havppily upgrade the rom to a better vesrion. Otherwise there are some really cool bnew roms out for the s8/s8+ now that I recommend checking out.
The more exciting prospect is that this can be used by ANY Samsung device with a permissive Selinux version without dm-verity. That covers a wide range of devices which we will be investifating.
DISCLAIMER 3:
* SamFAIL DOES NOT TRIP KNOX
* SamFAIL DOES NOT FIX THE 80% BATTERY CHARGE ISSUE
* Boot.img is SECURE which means you MUST use SYSTEM ROOT. (Similar to SamPWND)
* This means that MAGISK DOES NOT WORK
* Which also means SAFETY NET FAILS. So any apps you enjoy that require passing Safety Net will most likely not work while you are rooted with SamFAIL
* Again, similar to SamPWND, this root method uses a factory binary boot.img which is necessary to boot the modified system. THIS MEANS BATTERY ONLY CHARGES TO 80% (Thanks Samsung.)
* SamFAIL DOES NOT UNLOCK YOUR BOOTLOADER AND DOES NOT SIM UNLOCK YOUR PHONE.
* This *should* in theory, work for other Snapdragon Models of the Note 8. If you have another model and are successful please post so we can add "support" for other models.
Back to Stock?
- Download the full STOCK firmware of your choice.
- Flash it in ODIN/Comsey ODIN as you would any other time!
- It will take a few reboots for the "custom" splash screen to go away.
Donations:
As always, the devs have been hard at work recently to bring you root. Donations are definitely NOT REQUIRED but if you feel generous and want to spot the devs a few bucks for their hard work you can donate to this Paypal Address:
Donations
NOTE: this message is geared more towards the Note 8 users, for whom this root method is their first and only.
DOWNLOADS will be in POST #2
UPDATES will be in POST #3(RESERVED FOR FUTURE UPDATES)
As always, ENJOY ROOT and thank SamFAIL for making it all possible!
P.S. See why we called it SamFAIL now? Massive fail on Samsungs part.
SamFAIL Downloads
Rooted AQH3 Android 7.0 System for Galaxy S8 Snapdragon (Flashing in Odin)
AP_SamFAIL_G950U1_AQH3_ROOTED_SYSTEM.tar:
Hybrid Stock/Combination Full Firmware (minus userdata and system) For Rooted Devices.
AQI6 Stock, AQI1 Combo (for Flashing in Odin):
BL_SamFAIL_G950U1_HYBRID_AQI6_STOCK_AQI1_COMBOtar.tar
VZW CSC OYN for US VZW Customers on AQH3 (for Flashing in Odin):
CSC_OYM_SamFAIL_G950U1_AQH3_VZW.tar.md5
Staticly Compiled fsck.ext4 binary for fixing filesystem issues:
fsck.ext4
*YANK*
(reserved for future use)
Yay!
Nice!
Are there any custom ROMs for the Snapdragon variants (specifically the Canadian variant W8)?
Ad.Shk2 said:
Are there any custom ROMs for the Snapdragon variants (specifically the Canadian variant W8)?
Click to expand...
Click to collapse
i have 1 or 2 but not gonna upload em until theres more stuff done.. its basically got minor visual mods and deodex n theusual stuff
That sounds promising... I've been patiently waiting for custom ROMs for the Canadian variant... Good luck to you bro!
Sent from my SM-G950W using Tapatalk
Ad.Shk2 said:
That sounds promising... I've been patiently waiting for custom ROMs for the Canadian variant... Good luck to you bro!
Click to expand...
Click to collapse
but yea,just not enough done yet in order to release.. i hope note 8 root will kick offmore mods n such for us
I'll be going for Aosp based ROMs too, since it's for the Snapdragon
Sent from my SM-G950W using Tapatalk
Ad.Shk2 said:
Are there any custom ROMs for the Snapdragon variants (specifically the Canadian variant W8)?
Click to expand...
Click to collapse
There is one that supports at least everything thats part of CSC OYN:
https://forum.xda-developers.com/tm.../samsung-tmo-galaxy-s8-sampwnd-turbo-t3662719
Its listed under the tmoblle section because the developer has tmobile, but as our devices are multi-csc so is his rom
partcyborg said:
There is one that supports at least everything thats part of CSC OYN:
https://forum.xda-developers.com/tm.../samsung-tmo-galaxy-s8-sampwnd-turbo-t3662719
Its listed under the tmoblle section because the developer has tmobile, but as our devices are multi-csc so is his rom
Click to expand...
Click to collapse
The OP states: "this custom rom is only for tmo. i removed all other carriers config files..."
Also, what's CSC OYN?
Sorry about my illiteracy in this regard, I'm a Nexus/pixel guy which are a breeze to root and customize.
Sent from my SM-G950W using Tapatalk
Ad.Shk2 said:
The OP states: "this custom rom is only for tmo. i removed all other carriers config files..."
Also, what's CSC OYN?
Sorry about my illiteracy in this regard, I'm a Nexus/pixel guy which are a breeze to root and customize.
Click to expand...
Click to collapse
Aww that's a bummer, last I talked to him he was fine with other carrier use.
partcyborg said:
Aww that's a bummer, last I talked to him he was fine with other carrier use.
Click to expand...
Click to collapse
all he has to do is flash a csc after the rom lol if all he did was remove the other carrier stuff
Will this work for the S8 Plus?
NexusS4gFreak said:
Will this work for the S8 Plus?
Click to expand...
Click to collapse
yes if and when a modified system.img is created lol i dont plan on making it as i am already maintaining SamPWND root
NexusS4gFreak said:
Will this work for the S8 Plus?
Click to expand...
Click to collapse
elliwigy said:
yes if and when a modified system.img is created lol i dont plan on making it as i am already maintaining SamPWND root
Click to expand...
Click to collapse
I'm going to do my best to make one shortly but given I do not have an s8+ to test on I'm not so sure how effective I will be
Does this work? Anyone tried. I really want to root my Canadian model sm-g950w
Ad.Shk2 said:
I'll be going for Aosp based ROMs too, since it's for the Snapdragon
Click to expand...
Click to collapse
I think the usual comment about camera quality degrading still stands when using AOSP ROMs? Have yet to root the Samsung S8 but I'd like to do it soon, along with flashing a debloated ROM for my sister.
partcyborg said:
Aww that's a bummer, last I talked to him he was fine with other carrier use.
Click to expand...
Click to collapse
His rom has all the carrier info in it. He just doesn't update the op except the link to new rom.