[GUIDE] AT&T Samsung Galaxy S4 SGH-I337 Lollipop 5.0.1 OK2 Root Xposed Etc. - AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin

[GUIDE] AT&T Samsung Galaxy S4 SGH-I337 Lollipop 5.0.1 OK2 Root Xposed Etc. - AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin

This is a guide for rooting your
AT&T Samsung Galaxy S4
SGH-I337,
upgrading to the latest firmware baseband,
installing the Xposed Framework,
removing bloatware, and
resetting the flash counter.
Purpose:
The purpose of this guide is to wipe and refresh your AT&T Samsung Galaxy S4 SGH-I337. Use this guide if, for example, your trusty old S4 has been getting a little too sluggish these days, or if you just inherited someone's old S4 and want to wipe their data and start fresh. After backing up what you want to keep, you'll wipe your phone, gain root access, and upgrade to the latest firmware baseband (without losing root) for the best stock firmware stability and security. At that point, your phone will be compatible with Xposed if you want to install it, and you could take a few minutes to debloat your App Drawer before reinstalling your favorite apps and configuring your phone's settings to your liking.
Disclaimer:
Following the instructions in this guide will result in your phone being wiped. While flashing different ROMs, Kernels, etc., you run the distinct risk of throwing a permanent KNOX Warranty Flag, not to mention the distinct risk of bricking your phone. Odin can get you out of a softbrick; but if, for example, you use this guide on the wrong phone, you could end up with a several hundred dollar hardbricked paperweight. Know the risks and take adequate precautions. Please read and understand this guide in its entirety before attempting to follow any of the instructions. This guide is meant to be followed in order from start to finish; however, you may be able to skip certain steps.
Prep Work
You will need an AT&T SGH-I337, a PC, and a USB cable to connect your phone and PC. There's also a few things to check on your phone and a few things to set up on your PC before we get underway.
Step 1: Make sure that your Samsung Galaxy S4 is in fact an AT&T SGH-I337.
To verify your phone's Model Number: Go to your Settings
{
"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"
}
> open the More tab > select About Device > and check under Model Number for SAMSUNG-SGH-I337.
Step 2: Check which version of Android you're running. Depending on your Android Version, you may need to downgrade your firmware before you can root.
To check your phone's Android Version: Go to your Settings
> open the More tab > select About Device > and check under Android Version.
If Android Version < 4.4.2: Your firmware is already rootable.
If Android Version = 4.4.2: Still on the About Device page, check your Baseband Version.
If the last 3 characters are NB1: Your firmware is already rootable.
If the last 3 characters are NC1 or NI1: Your firmware must be downgraded in order to root.If Android Version > 4.4.2: Your firmware must be downgraded in order to root.
Step 3: Install the latest Samsung USB Drivers on your PC. Download Odin v3.09 and Run as Administrator.
Step 4: Make sure that your phone's battery is fully charged. Enable USB Debugging under the Developer Options menu.
To enable the Developer Options menu: Go to your Settings
> open the More tab > select About Device > and repeatedly tap Build Number until the message Developer mode has been turned on appears.
Step 5: Connect your phone to your PC via USB cable. Your phone should be in Media Device (MTP) mode. Allow Windows to "install" the phone.
To verify that your phone is in Media Device (MTP) mode: Pull down your phone's Notification Shade and look just above Touch for Other USB Options for Connected as a Media Device. If your phone is connected as anything other than a Media Device, tap Touch for Other USB Options and select Media Device (MTP).
Backing Up Your Phone
Following the instructions in this guide will result in your phone being wiped. While wiping your phone will provide a fresh, clean firmware installation, it's also critical to note that anything you don't back up now will be irretrievably lost. Do not rely on Titanium Backup, as it may have problems trying to restore your backup on a different Android Version.
Step 1: Manually back up all of your phone's important data to your PC. That includes your pictures, videos, music, and other files, as well as any important app data stored on your phone. Nothing on your SD card should be wiped, but just to be safe, back up any important files on your phone's SD card to your PC anyway.
To manually back up your data: Open an explorer window on your PC and use it to navigate to your phone's internal storage and SD card root directory. Simply copy the files you want to back up, and then paste them into a New Folder on your PC.
Step 2: Use an app like SMS Backup & Restore to back up your text messages.
Step 3: Sync your Contacts and Calendar.
Step 4: Back up anything else you care about!
Downgrading Firmware
If your firmware must be downgraded in order to root, you will need a rootable version of the Android 4.4.2 KitKat Baseband NB1 firmware. Flash it to your phone using Odin.
Step 1: Download the Rootable NB1 ROM to your PC and extract the .tar.md5 file from the compressed RAR file. Rename the .tar.md5 file extension to a .tar file extension.
Step 2: Power off your phone and boot into Download Mode.
To boot into Download Mode: Power off your phone > press and hold the power and volume down buttons at the same time > when the warning screen appears, release both buttons > and then press the volume up button.
Step 3: If 0:[COM*] is displayed on Odin, then your phone is connected to your PC via USB cable and Odin is able to communicate with your phone. Make sure that Auto Reboot and F. Reset Time are the only boxes checked. Click the AP button and select I337UCUFNB1_TWRootable_Full_Odin.tar. Click Start to flash the Rootable NB1 ROM to your phone.
Step 4: Your phone will reboot when the process is complete. Follow the prompts on your phone to complete the initial setup process. Your phone is now running a rootable version of Android.
Note: If a Security Notice appears at any point during the rooting and upgrading process asking you to restart the phone, do not restart the phone. Manually disable KNOX instead.
To manually disable KNOX: Go to your Settings
> open the More tab > open the Application Manager > open the All tab > scroll down to the following applications and Force Stop, Clear Data, and Clear Cache for each application: KLMS Agent, KNOX Notification Manager, KNOX Store, and Samsung KNOX. Now go back through the list and disable them all one more time for good measure.
Rooting and Upgrading Firmware
Use towelroot to root your phone. Install SuperSU. Upgrade to a rooted, deodexed version of the Android 5.0.1 Lollipop Baseband OK2 firmware using FlashFire and Odin.
Step 1: Set your phone's Screen Timeout to 10 Minutes and enable installation from Unknown Sources.
To change your Screen Timeout settings: Go to your Settings
> open the My Device tab > select Display > and set Screen Timeout to 10 Minutes.
To enable installation from Unknown Sources: Go to your Settings
> open the More tab > select Security > tick Unknown Sources and untick Verify Apps.
Step 2: Download the towelroot APK file to your phone's SD card, and run it to install the towelroot app. Open the towelroot app and tap Make It Ra1n to root your phone.
Step 3: Install the SuperSU app from the Play Store. Open the SuperSU app and opt to Disable KNOX. Note: If SuperSU hangs, manually disable KNOX, reinstall the SuperSU app, and try again.
To manually disable KNOX: Go to your Settings
> open the More tab > open the Application Manager > open the All tab > scroll down to the following applications and Force Stop, Clear Data, and Clear Cache for each application: KLMS Agent, KNOX Notification Manager, KNOX Store, and Samsung KNOX. Now go back through the list and disable them all one more time for good measure.
Step 4: The phone is now rooted, and the firmware can be upgraded to Android 5.0.1 Lollipop without losing root by using the following method. Download the Rooted, Deodexed OK2 ROM to your phone's SD card. Download the OK2 Bootloader to your PC, and rename its .tar.md5 file extension to a .tar file extension. Install the FlashFire app from the Play Store. Note: FlashFire requires you to first "become a tester" using your Play Store gmail account in order to access the download link.
Step 5: Open the FlashFire app and tap the + button to bring up the Actions menu. Select Flash Zip or OTA and select I337_OK2_Stock_Rooted_Deodexed_ROM.zip. Tap the check mark button to accept the default settings. Set Reboot setting to Download. Tap the lightning bolt button to flash the Rooted, Deodexed OK2 ROM to your phone. Your phone will reboot into Download Mode when the flash is complete. Note: If your phone hangs on the black Samsung Galaxy S4 boot screen instead of booting into Download Mode, go back to Downgrading Firmware Step 1.
Step 6: If 0:[COM*] is displayed on Odin, then your phone is connected to your PC via USB cable and Odin is able to communicate with your phone. Make sure that Auto Reboot and F. Reset Time are the only boxes checked. Click the AP button and select I337_OK2_Bootloader.tar. Click Start to flash the OK2 Bootloader to your phone.
Step 7: Your phone will reboot when the process is complete. This first boot will pause on the white AT&T splash screen for a solid 15-20 minutes. Don't interrupt it! Eventually your phone will finish booting up into the initial setup process. Follow the prompts on your phone to complete the initial setup process. Your phone is now running Android 5.0.1 Lollipop, and it's still rooted.
Installing Xposed
Xposed consists of an Installer app for managing Xposed Modules, as well as a Framework that can be flashed using FlashFire.
Step 1: Set your phone's Screen Timeout to 10 Minutes and enable installation from Unknown Sources.
To change your Screen Timeout settings: Go to your Settings
> open the My Device tab > select Display > and set Screen Timeout to 10 Minutes.
To enable installation from Unknown Sources: Go to your Settings
> open the More tab > select Security > and tick Unknown Sources.
Step 2: Sign into the Play Store and update the SuperSU app. Open the app, update the SU Binary when asked, and reboot as instructed. Sign into the Play Store again, and reinstall FlashFire.
Step 3: Download the Xposed Installer APK file to your phone's SD card, and run it to install the Xposed Installer app.
Where's the download link? It's at the bottom of the first forum post in the linked thread, under Attached Files. Download the latest version of the XposedInstaller_*.apk file, where * stands for the version number (version 3.0_alpha4 at the time of writing).
Step 4: Download the Xposed Framework to your phone's SD card. Open the FlashFire app and tap the + button to bring up the Actions menu. Select Flash Zip or OTA and select xposed-v*-sdk21-arm-arter97-snapdragon_requestConcurrentGC.zip. Note: If that file fails to flash properly, try flashing xposed-v*-sdk21-arm-arter97-snapdragon.zip instead. Tap the check mark button to accept the default settings. Tap the lightning bolt button to flash the Xposed Framework to your phone. When the flash is complete, your phone will reboot and then spend 10 minutes "optimizing" all ~235 of your apps and files before it finishes booting.
Where's the download link? There are 2, and they're both at the bottom of the first forum post in the linked thread, under Attached Files. Download the latest version of the xposed-v*-sdk21-arm-arter97-snapdragon_requestConcurrentGC.zip file and the xposed-v*-sdk21-arm-arter97-snapdragon.zip file, where * stands for the version number (version 75 at the time of writing).
Note: Choosing the correct version of the Xposed Framework for any given phone depends on the phone's Android Version and the Instruction Set of the phone's CPU. SDK21 ARMv7 from developer @arter97 is the version required by your SGH-I337, which has a Snapdragon 600 CPU and should now be running a rooted, deodexed version of Android 5.0.1 Lollipop. Alternatively, developer @dkcldark has released a beta version based on @arter97's work that implements a more recent (at the time of writing) version of Xposed, available here.
Step 5: If it worked, you should now have the Xposed Framework installed on your phone. Open the Xposed Installer app and tap Download to browse available Xposed Modules. Download, install, and activate your favorites; and then from the main menu of the Xposed Installer app, tap Framework and select Reboot. After your phone reboots, open the Xposed Installer app and tap Modules to configure the Xposed Modules you just installed.
Removing Bloatware
If you want to remove any of the pre-installed bloatware, it's always best to do it before you run off downloading your own apps.
Step 1: Make a list of all the apps in your App Drawer that you would prefer to uninstall. Note: Deleting system-critical apps can cause everything from annoying error messages to diminished functionality to bootloops and softbricks. If you aren't sure whether an app is safe to remove, research it. If you still aren't sure, just hide the app instead of uninstalling it; better safe than sorry!
Step 2: Using a root-required system app uninstaller app like System App Remover, uninstall the list of apps you made, taking care not to remove any that System App Remover doesn't mark as Could Remove unless you're certain that it's safe to do so. When the uninstallation process is complete, reboot your phone.
Apps known to be safe to remove:
AT&T
AT&T FamilyMap, AT&T Live, AT&T Locker, AT&T Mail, AT&T Mobile Locate, AT&T Navigator, AT&T Smart Wi-Fi, Device Help, (AT&T) Messages (not to be confused with the stock SMS app Messaging!), (AT&T) Mobile TV
Google
Chrome (gave the error: com.android.chrome has stopped when uninstalled, but no further issues), Google (the app with the square blue icon and a white g, used for search; don't uninstall the wrong thing by mistake! Uninstalling this app gave the error: com.google.android.googlequicksearchbox has stopped when uninstalled, referring to the Google Search widget that breaks without the Google app installed), Google+, Hangouts, (Google) Photos, Play Books, Play Games, Play Movies & TV, Play Music, Play Newsstand, Voice Search (part of the Google app, uninstalling the Google app also removes the Voice Search app)
Samsung
Flipboard, Group Play, (Samsung) Help, Kids Mode, KNOX (the app with a little shortcut arrow on the bottom left corner of the icon: com.sec.knox.setupwizardstub; don't uninstall the wrong thing by mistake!), Optical Reader, S Memo, S Translator, S Voice, Samsung Apps, Samsung Hub, Samsung Link
Third-party
Caller Name ID, Keeper, Lookout, TripAdvisor, Uber, YP (Yellow Pages)
Step 3: Now make a list of any remaining widgets that you would prefer to uninstall. Open the System App Remover app and uninstall the list of widgets you made, taking care not to remove any that System App Remover doesn't mark as Could Remove unless you're certain that it's safe to do so. When the uninstallation process is complete, reboot your phone.
Widgets known to be safe to remove:
Dual Clock (Digital), Samsung GALAXY Apps Widget, Google Search, Travel, Yahoo! Finance, Yahoo! News
Note: It is strongly advised not to remove any other files with System App Remover unless they're causing you a specific problem and you're completely certain that they would be safe to remove. Always reboot your phone after uninstalling any other files.
Other files known to be safe to remove:
S Note Provider (component for S Memo; safe to remove if S Memo is already uninstalled), Samsung Books, Samsung Games, Samsung Link Platform (component for Samsung Link; safe to remove if Samsung Link is already uninstalled), Samsung Link Platform Connectivity (component for Samsung Link; safe to remove if Samsung Link is already uninstalled), SamsungHub Updater (component for SamsungHub; safe to remove if SamsungHub is already uninstalled)
Resetting the Flash Counter
If, after all of your tinkering, your bootscreen now shows an unlocked padlock with the word "Custom," it means you've managed to set off a Modified System Flag. This step restores the standard black Samsung Galaxy S4 bootscreen.
Step 1: Download the Triangle Away APK file to your phone's SD card, and run it to install the Triangle Away app. Open the Triangle Away app and confirm that the Model Number displayed by Triangle Away matches your SAMSUNG-SGH-I337. Under Current Status, your Flash Counter, Binary Status, and System Status are all displayed.
Where's the download link? It's at the bottom of the first forum post in the linked thread, under Attached Files. Download the latest version of the TriangleAway-v*.apk file, where * stands for the version number (version 3.26 at the time of writing).
Step 2: Unplug your phone and tap Reset Flash Counter to reset your Flash Counter to 0 and remove your Modified System Flag. Your phone will power off. Wait at least 10 seconds before powering it on again.
Note: Triangle Away cannot remove a KNOX Warranty Flag. Your System Status as reported in Download Mode may remain Custom even after using Triangle Away. If you go to your Settings
> open the More tab > select About Device > and select Status, your Device Status as reported here, too, may remain Custom even after using Triangle Away.
:good: Credits:
The knowledge contained in this guide and the resources to which it links are thanks to the skill and contributions of the following talented and generous people. Please give them a Thanks on their threads, rate and share their apps, and donate to them if you can.
odindownload.com
@sac02 for [How-To] I installed a custom Lollipop ROM on my AT&T Galaxy S4 and it was easy!
@guut13 for [INDEX] All things AT&T [MK2 NB1 NC1 NI1 NJ4 NJ5 OC3 OC4 OK2] and ROM List, [GUIDE]Odin to Stock, Updating, Rooting, and Installing Safestrap > Part 2
@muniz_ri for Rootable NB1 ROM, [How-To] Update to I337_OK2 - 5.0.1 and KeepRoot, Rooted, Deodexed OK2 ROM, OK2 Bootloader
@geohot for towelroot
@Chainfire for SuperSU, FlashFire, Triangle Away
@Portgas D. Ace for [DISCUSSION] Xposed for Lollipop > Unofficial Q&A
@rovo89 for Xposed Installer
@arter97 for Xposed Framework
@dkcldark for Xposed Framework (beta)

In the chainfire threat it is stated that the triangle away app (ver 2.36) to reset the flash counter works on SGH-i337 with "unlocked bootloaders". This OP is talking about locked bootloader. I was wondering the OP actually tested the triangle away on SGH-i377 with locked bootloader.

The only problem I'm having now, after installing " xposed-v75-sdk21-arm-arter97-snapdragon_requestConcurrentGC.zip" is that it seems to have disabled most of my system interface - can't swipe up, can't use the softkeys, lock screen doesn't work, etc.
I'm using the Able95 S6 Port on my 1337, fwiw.
Any ideas?

sway8966 said:
In the chainfire threat it is stated that the triangle away app (ver 2.36) to reset the flash counter works on SGH-i337 with "unlocked bootloaders". This OP is talking about locked bootloader. I was wondering the OP actually tested the triangle away on SGH-i377 with locked bootloader.
Click to expand...
Click to collapse
Yeah, I tested it twice actually with no issues. :good:

bulletfodder said:
The only problem I'm having now, after installing " xposed-v75-sdk21-arm-arter97-snapdragon_requestConcurrentGC.zip" is that it seems to have disabled most of my system interface - can't swipe up, can't use the softkeys, lock screen doesn't work, etc.
I'm using the Able95 S6 Port on my 1337, fwiw.
Any ideas?
Click to expand...
Click to collapse
I know @arter97's Xposed Framework for our phones is only intended for deodexed ROMs. Is Able95 deodexed? Just a thought. The only ROM on which I've tested Xposed is the stock firmware (5.0.1 baseband OK2) referenced in the guide, the version that's been rooted and deodexed by @muniz_ri.
I don't have any experience with the ROM you're using. But the first thing you ought to try is flashing @rovo89's Xposed Framework uninstaller. @arter97's own uninstaller apparently won't work for Xposed Framework v75+.)
But if that doesn't work, and your phone's touch screen and soft keys have stopped working...then you're probably going to have to put your phone into Download Mode and use Odin to downgrade back to NB1 just to restore your phone's functionality. You can go from there back to a custom ROM if you like, or try the OK2 ROM with Xposed.

d800d00d said:
I know @arter97's Xposed Framework for our phones is only intended for deodexed ROMs. Is Able95 deodexed? Just a thought. The only ROM on which I've tested Xposed is the stock firmware (5.0.1 baseband OK2) referenced in the guide, the version that's been rooted and deodexed by @muniz_ri.
I don't have any experience with the ROM you're using. But the first thing you ought to try is flashing @rovo89's Xposed Framework uninstaller. @arter97's own uninstaller apparently won't work for Xposed Framework v75+.)
But if that doesn't work, and your phone's touch screen and soft keys have stopped working...then you're probably going to have to put your phone into Download Mode and use Odin to downgrade back to NB1 just to restore your phone's functionality. You can go from there back to a custom ROM if you like, or try the OK2 ROM with Xposed.
Click to expand...
Click to collapse
Thanks for the info - I had actually found the uninstaller about 5 minutes before I clicked back on this thread.
Then it promptly bootlooped at the samsung logo.
So, Odin back to NB1, and go from there, I guess. This guide was extremely helpful though, I really appreciate it!

bulletfodder said:
Thanks for the info - I had actually found the uninstaller about 5 minutes before I clicked back on this thread.
Then it promptly bootlooped at the samsung logo.
So, Odin back to NB1, and go from there, I guess. This guide was extremely helpful though, I really appreciate it!
Click to expand...
Click to collapse
Sorry to hear that dude. Which uninstaller did you use?
Yeah just start at the beginning of the guide and let me know how it goes. :good:

d800d00d said:
Sorry to hear that dude. Which uninstaller did you use?
Yeah just start at the beginning of the guide and let me know how it goes. :good:
Click to expand...
Click to collapse
I used the one that you linked, but I had uninstalled the framework installer via menu before that. Just checked, and that rom was deodexed.
Currently flashing the OK2 now. I'll try it out and let you know :good:

bulletfodder said:
I used the one that you linked, but I had uninstalled the framework installer via menu before that. Just checked, and that rom was deodexed.
Currently flashing the OK2 now. I'll try it out and let you know :good:
Click to expand...
Click to collapse
Ah, yeah that was just a thought. Even if it was deodexed, not all custom ROMs are gonna be compatible with Xposed.

Well, I tried several other roms, but none of them were to my satisfaction.
The good news is, your guide worked flawlessly
I tried the v71-snapdragon framework, and the v75-snapdragon framework, and neither worked. I had to use the v75-concurrent framework.
3rd time's the charm!

bulletfodder said:
Well, I tried several other roms, but none of them were to my satisfaction.
The good news is, your guide worked flawlessly
I tried the v71-snapdragon framework, and the v75-snapdragon framework, and neither worked. I had to use the v75-concurrent framework.
3rd time's the charm!
Click to expand...
Click to collapse
Far out, dude. Thanks for your post. The v75-concurrent was the one that worked for me too. :good:

I was about to ask about rooting my wife's S4, but I came across this amazing thread. Thank you.
I tried to use towelroot last night, but it did not recognize the device.
Did anyone else get that error?

after using flashfire, I got stuck on Samsung Logo with Custom written on it.. any help ?

nabril15 said:
I was about to ask about rooting my wife's S4, but I came across this amazing thread. Thank you.
I tried to use towelroot last night, but it did not recognize the device.
Did anyone else get that error?
Click to expand...
Click to collapse
Read Prep Work > Step 2.
What is your Baseband Version?
krulex said:
after using flashfire, I got stuck on Samsung Logo with Custom written on it.. any help ?
Click to expand...
Click to collapse
d800d00d said:
Step 5: Open the FlashFire app and tap the + button to bring up the Actions menu. Select Flash Zip or OTA and select I337_OK2_Stock_Rooted_Deodexed_ROM.zip. Tap the check mark button to accept the default settings. Set Reboot setting to Download. Tap the lightning bolt button to flash the Rooted, Deodexed OK2 ROM to your phone. Your phone will reboot into Download Mode when the flash is complete. Note: If your phone hangs on the black Samsung Galaxy S4 boot screen instead of booting into Download Mode, go back to Downgrading Firmware Step 1.
Click to expand...
Click to collapse

d800--you're right, and I apologize. Her phone is on OK2 (5.0.1), and I see that I need to downgrade first before starting.

nabril15 said:
d800--you're right, and I apologize. Her phone is on OK2 (5.0.1), and I see that I need to downgrade first before starting.
Click to expand...
Click to collapse
No worries. Just make sure you read the whole guide and understand it before you start flashing crap :laugh:

nabril15 said:
d800--you're right, and I apologize. Her phone is on OK2 (5.0.1), and I see that I need to downgrade first before starting.
Click to expand...
Click to collapse
Honestly, it's not a bad process. I've been using this phone for about 2 years now, and after many false starts, basically have it where I want it.
The biggest time savers for me were
a) making sure I have the ODIN file for NB1 (that takes about 30 minutes to install)
b) having the required .apk's downloaded and stored on my SD card, so I don't have to go to the Play store and try and stop all the apps from installing.
c) having a good backup in case I bootloop or softbrick. I also copied the applicable folders to my desktop so I could make sure I had my needed files.

bulletfodder said:
Honestly, it's not a bad process. I've been using this phone for about 2 years now, and after many false starts, basically have it where I want it.
The biggest time savers for me were
a) making sure I have the ODIN file for NB1 (that takes about 30 minutes to install)
b) having the required .apk's downloaded and stored on my SD card, so I don't have to go to the Play store and try and stop all the apps from installing.
c) having a good backup in case I bootloop or softbrick. I also copied the applicable folders to my desktop so I could make sure I had my needed files.
Click to expand...
Click to collapse
bulletman---what folders? what apk's?

I have mine currently rooted on 4.4.4. I assume that I can just jump to the flashfire step without downgrading, correct?

Redhawk2000 said:
I have mine currently rooted on 4.4.4. I assume that I can just jump to the flashfire step without downgrading, correct?
Click to expand...
Click to collapse
Yep, but you still need to do the Prep Work and Backing Up Your Phone steps.
Then you can skip to Rooting and Upgrading Firmware > Step 3.

Related

[TIP/GUIDE] Root + Custom Kernel + Custom Recovery = Device Status Normal + OTA

I'm fully rooted on a self-modified (initramfs/init.d/bootani/build.prop/csc etc²) stock JB 4.1.2 MF2 Rom, with AbyssN2 Kernel 2.5.1 and TWRP Recovery 2.6.0.0. My device status is normal and software update works as intended.
I had these all along since MB2 didn't realise it's working until I was just playing around and stumbled upon accidentally to share this good news :good: 1st of all, the effort is not by me Credits are in red. Please donate to these wonderful peeps! :angel:
Note: This will NOT reset your flash count or whatever you see at download mode to official as long as you have custom kernel/recovery. If you need those cleared before sending to service center, flash stock rom from sammobile.com via pc odin, temporary root, reset the counter using Triangle Away, unroot and finally factory reset. We don't cover these here, there's already lots of guides so please do a quick search if you ever need them...
Please read the guides especially on the links provided:
If you have "Triangle Away" by Chainfire (you need to allow SysScope service to run).
a) make sure you unchecked "Auto reset at boot" (else SysScope will not run properly).
b) make sure you checked "Allow tracker to run" (for Triangle Away 2.37 and below, please upgrade or just uninstall until needed).
c) make sure you unchecked "System modified workaround" (for Triangle Away 2.37 and below, please upgrade or just uninstall until needed).
Confirm that SysScope service is not disabled/frozen. You can check from "Settings, Application Manager, All" or from apps like Titanium Backup. Need not clear its data.
Install and activate the "Xposed Framework" app by rovo89, guide and apk on 1st thread http://forum.xda-developers.com/showthread.php?t=1574401
Install and enabled the "Samsung SysScope Blaster" module by _TB_TB_, apk on the 1st thread http://www.villainrom.co.uk/forum/threads/samsung-sysscope-blaster.5584/. The site has been down for awhile, refer attached for the apk.
Reboot and observe your device status at settings, it should state "Normal". It will change to "Modified" if you use Triangle Away reset feature, or wipe/kill SysScope. It'll then changed back to "Normal" again at reboot..
{
"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"
}
** Updates 1st March 2013 **
If you happen to update SuperSU (v1.20) binary using its new CWM/TWRP option, most probably your status will go back to modified. To fix this, uninstall SuperSU via its settings>cleanup>reinstall, reboot, reinstall SuperSU from Google Play Store then open SuperSU. This time, avoid the new CWM/TWRP option and just update the binary normally. And finally reboot, the status will change back to normal.
Note: I noticed the latest SuperSU acts weird after reinstalled. Root required apps will hang awaiting for user prompt. So I temporarily set the default access to grant till further updates.
** Updates 2nd March 2013 **
I noticed the status will also change to modified when the SysScope runs at boot and detects your system fs(FileSystem) is mounted as rw(ReadWrite). Strangely others such as rootfs are not affected. So look out for start up scripts in the init.d folder, if you have, that remount /system as rw(ReadWrite) but didn't set it back to ro(ReadOnly) when the script ends. Some custom kernels does such remount on post init, but they would usually revert it back when done.
busybox mount -oremount,rw system /system
#...scripts having early lines like above should end like below.
busybox mount -oremount,ro system /system
** Updates 11th July 2013 **
Good new, this method seems to be still working on the latest MF2. Personally tested an OTA update on latest TWRP recovery, it works! Need to reroot of course. For AllShare Cast, there has been mix results. Previously tested on someone else's, now I just got the dongle and created this thread [SCRIPT] custom2stock1click-v0.1 (AllShare Cast temporary workaround)

Thank you. Worked for me getting my status back to normal.
Sent from my GT-N7100 using Tapatalk 2

OK, nice guide. But does it have any value as far as updates are concerned?
I'm on rooted stock 4.1.1. It was reported "changed" and I couldn't OTA update to 4.1.2.
If I now have "normal" will it update to 4.1.2 through OTA? (I tried and it stared downloading, but will it WORK?)
Will I loose my root?
Is it good idea to update OTA like this ?
Thanx,
D.

Wow, a simple guide that actually works.
Thanks dude.

dalanik said:
OK, nice guide. But does it have any value as far as updates are concerned?
I'm on rooted stock 4.1.1. It was reported "changed" and I couldn't OTA update to 4.1.2.
If I now have "normal" will it update to 4.1.2 through OTA? (I tried and it stared downloading, but will it WORK?)
Will I loose my root?
Is it good idea to update OTA like this ?
Thanx,
D.
Click to expand...
Click to collapse
yes, you will looose the root. i have rooted stock rom with 0 counter and "official". after update with kies i loose my root.

dalanik said:
OK, nice guide. But does it have any value as far as updates are concerned?
I'm on rooted stock 4.1.1. It was reported "changed" and I couldn't OTA update to 4.1.2.
If I now have "normal" will it update to 4.1.2 through OTA? (I tried and it stared downloading, but will it WORK?)
Will I loose my root?
Is it good idea to update OTA like this ?
Thanx,
D.
Click to expand...
Click to collapse
As mentioned by tuksedra previously, yes you would lose root. But rooting back is not a problem. It's a click away using Exynos Abuse app or you can even use SuperSU's survival mode to keep root. Else old school odin method should come in handy.
Personally I hate downloading 1gb of full rom just to upgrade. I have a 200mb fiber connection but hotfile is just too slow. Please let us know if it works for you.
This method should also be working for those who is still having status modified issues even on stock kernel/recovery but rooted. Not sure about kies though (what kies uh?), if anyone can confirm I'll update the OP...

I have seen cases where there is status is modified even device never been rooted, as far as warranty is concern there should not be have issue for status 'modified' once flash counter is 'No'
I have seen many cases of SDS and all i remember have status 'custom' on download mode, though i never read any post where warranty claim rejected for 'custom' status
Here one trick working on Rooted/non rooted device too (without any third party SW)
setting - Appl manager - All - SysScope - clear data
do same with Enterprise SysScope if available
And status will turn to 'Normal'
Another weired phenomenon of OTA is even after doing lots workout and turn status to 'Normal' there is no guarantee you will get OTA updates.(though i have seen cases where OTA successfull even device is rooted)
sometime it needs unroot
sometimes needs unroot + Factory reset
and myself observed 1 time even after unroot + factory reset i didn't get OTA, though update file was downloaded but installation was failed, then i have tried to flash old ROM with Odin and then tried OTA and it was worked, so something there in system can block OTA.

dr.ketan said:
I have seen cases where there is status is modified even device never been rooted, as far as warranty is concern there should not be have issue for status 'modified' once flash counter is 'No'
I have seen many cases of SDS and all i remember have status 'custom' on download mode, though i never read any post where warranty claim rejected for 'custom' status
Here one trick working on Rooted/non rooted device too (without any third party SW)
setting - Appl manager - All - SysScope - clear data
do same with Enterprise SysScope if available
And status will turn to 'Normal'
Another weired phenomenon of OTA is even after doing lots workout and turn status to 'Normal' there is no guarantee you will get OTA updates.(though i have seen cases where OTA successfull even device is rooted)
sometime it needs unroot
sometimes needs unroot + Factory reset
and myself observed 1 time even after unroot + factory reset i didn't get OTA, though update file was downloaded but installation was failed, then i have tried to flash old ROM with Odin and then tried OTA and it was worked, so something there in system can block OTA.
Click to expand...
Click to collapse
Hi dr.ketan!
I rooted my Note II yesterday using your Method 1 and used TA to reset counters and this is what i did and noticed:
Note: Did almost workaround, yours, other posts and mine. Geee... read more than 100 pages, rebooted nth times!
1. After rebooting and setup/updates, checked my device status and it is still normal.
2. Recheck again via reboot and download mode, Binary DL: No, Binary: Official & Status is official also.
3. Reboot and check Device, status again normal.
4. Install Avast, do 2 & 3.
5. Configure Avast Firewall, SuperSU prompted and granted.
6. Do 2,.
7. Do 3, but status is modified now.
8. Reflash stock ROM DMB2 Philippines via PC ODIN and back again to stock unrooted phone.
Again, refer to NOTE above.
Any additional workaround Sir or anyone?
For me, Device Status Modified is an eye sore.
Also, I want to say THANK YOU VERY MUCH for all the guides and posts Sir!!

dr.ketan said:
Another weired phenomenon of OTA is even after doing lots workout and turn status to 'Normal' there is no guarantee you will get OTA updates.
Click to expand...
Click to collapse
What about if
1) I have some frozen apps (suppose this is no big deal)?
2) I have integrated some updated apps into ROM?
3) I have added some user apps to system?
Will this be lost/changed after OTA?
D.

Really difficult to say anything regarding OTA
Thogh even you get OTA
- frozen application should remain as it is if OTA doesn't have same application
- user application pushed to system should remain as it is
Sent from my GT-N7100 using xda premium
---------- Post added at 01:53 PM ---------- Previous post was at 01:51 PM ----------
wyndcryst25 said:
Hi dr.ketan!
I rooted my Note II yesterday using your Method 1 and used TA to reset counters and this is what i did and noticed:
Note: Did almost workaround, yours, other posts and mine. Geee... read more than 100 pages, rebooted nth times!
1. After rebooting and setup/updates, checked my device status and it is still normal.
2. Recheck again via reboot and download mode, Binary DL: No, Binary: Official & Status is official also.
3. Reboot and check Device, status again normal.
4. Install Avast, do 2 & 3.
5. Configure Avast Firewall, SuperSU prompted and granted.
6. Do 2,.
7. Do 3, but status is modified now.
8. Reflash stock ROM DMB2 Philippines via PC ODIN and back again to stock unrooted phone.
Again, refer to NOTE above.
Any additional workaround Sir or anyone?
For me, Device Status Modified is an eye sore.
Also, I want to say THANK YOU VERY MUCH for all the guides and posts Sir!!
Click to expand...
Click to collapse
If you mean you are having unrooted stock rom with device modified
Then try
Setting - application manager - all - sysscope - clear data
Same with enterprise sysscope
It may turn to normal
Otherwise factory reset also works
Sent from my GT-N7100 using xda premium

dr.ketan said:
If you mean you are having unrooted stock rom with device modified
Then try
Setting - application manager - all - sysscope - clear data
Same with enterprise sysscope
It may turn to normal
Otherwise factory reset also works
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Yes after factory reset or clearing all syscope, it turns normal.
I have done that also Sir, but after installing avast, rebooted - normal status, configure firewall, status is back to modified. Done it many times and tried to workaround.
Anyway, I'm back to stock right now and will do a rooting rematch later after office. Any more advice Sir on rooting procedure?
I know, you will direct me to your posts but perhaps there is other way to do it basing from your experience...

Rooting rematch started...
Question Doc, after wipe data/factory reset, do i need to re-install Triangle Away to allow tracker to run?
Just finished factory reset, configure setup and updated SuperSU, Currently my Device Status is Normal.

I think there is no meaning to keep on tracking, whenever you need just clear data for sysscope that's it.
Sent from my GT-N7100 using xda premium

dr.ketan said:
I think there is no meaning to keep on tracking, whenever you need just clear data for sysscope that's it.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Thanks Sir!
After enabling USB Debugging, device status turns modified. followed your advice then rebooted and now status is back to normal! :good:
I'll update once setup and all installation are completed. :fingers-crossed:
Again, thank you very much!

If one need continue normal status then try method described in op
Otherwise reset manually whenever you need (like for ota)
Sent from my GT-N7100 using xda premium

dr.ketan said:
If one need continue normal status then try method described in op
Otherwise reset manually whenever you need (like for ota)
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Yeah, I will Sir!
I'll take one step at a time.
Thanks!

Mine has gone back to modified. Tried a few things, but no luck as to get ir back to normal.
Installed both apps and clearing the data before didn't help as well. Did the uninstall and clean app from within xposed installer. Rebooted and reinstalled and status still modified.
Any suggestions ?
Sent from my GT-N7100 using Tapatalk 2

Did you installed, updated or performed anything recently? Mine is custom kernel/recovery (just flashed latest TWRP 2.4.2.0) and wifey's rooted(older 4.1.1) but stock kernel/recovery, till now both status is still normal.
What I noticed is that it will change to modified, if you clear SysScope data or kill'em, use TA to reset counter or prevent SysScope tracker to run normally at boot...

Worked fine after twrp install. There was a supersu update that I installed and after that it went to modified.
Sent from my GT-N7100 using Tapatalk 2

I had supersu updated too, didn't really checked the status... I remember only choosing to update su binary normally instead of the new option via cwm/twrp. I just rebooted and the status is still normal now. You might wanna try clearing both ent/SysScope then reboot...

Towel root

Does towel root method work on AN12 update. I have read the root methods for under AN12 but since this update has been out for a while now i thought maybe they got towel root to work.
Thank you in advance.
Sent from my GT-N5110 using XDA Premium HD app

Short answer is yes, however, you will need to ODIN your kernel first then gain root with towel root. Read this thread http://forum.xda-developers.com/showthread.php?t=2784860

Towelroot v3 refuses to install on Galaxy S5 from Verizon.
I'm having problems getting Towelroot v3 installed on my Verizon Wireless, Samsung Galaxy S5 16mb phone.
We were running fine while being rooted under V4.4.4 and Rom *NHA*.
We removed SuperSU, and uninstalled. it.
We installed the update, with no problems.
We rebooted, into Download mode, and flashed Kernel *NCG* .
We copied Towelrootv3 over and attempted to install it... (This is where the problem begins...)
We attempt to install TowelrootV3.apk. We get the popup that gives us the warning, along with the checkbox, we select the checkbox, which allows us to go ahead with the installation... the install begins but then suddenly says, "App not installed". (??????)
I have ensured that we are booted up under the NCG Kernel, and that we have selected:
Settings ->Security->Unknown Sources [ck'd]
Settings->Security->Verify Apps [Ck'd']
Developer Options->USB Debugging [not Ckk'd]
Developer Options->Allow Mock Locations [Chk'd]
No matter how many times that we try to install it, with different settings etc.... it fails with "App not installed!"
What could possibly be the reason that it refuses to install when we are using the *NCG* kernel?
I removed the NCG kernel and put the NK2 Kernel back in, and rebooted for the time being. It's working well, I just cannot get TowelrootV3 installed so that I can install SuperSU.
I've rooted another S5, using the very same procedure, and had absolutely no problems.
What am I doing wrong on this phone? It's driving me crazy, and I don' t have too far to go...:silly:
Thanks in Advance!
Please Help.
Stone.

stonecoldxlh said:
I'm having problems getting Towelroot v3 installed on my Verizon Wireless, Samsung Galaxy S5 16mb phone.
We were running fine while being rooted under V4.4.4 and Rom *NHA*.
We removed SuperSU, and uninstalled. it.
We installed the update, with no problems.
We rebooted, into Download mode, and flashed Kernel *NCG* .
We copied Towelrootv3 over and attempted to install it... (This is where the problem begins...)
We attempt to install TowelrootV3.apk. We get the popup that gives us the warning, along with the checkbox, we select the checkbox, which allows us to go ahead with the installation... the install begins but then suddenly says, "App not installed". (??????)
I have ensured that we are booted up under the NCG Kernel, and that we have selected:
Settings ->Security->Unknown Sources [ck'd]
Settings->Security->Verify Apps [Ck'd']
Developer Options->USB Debugging [not Ckk'd]
Developer Options->Allow Mock Locations [Chk'd]
No matter how many times that we try to install it, with different settings etc.... it fails with "App not installed!"
What could possibly be the reason that it refuses to install when we are using the *NCG* kernel?
I removed the NCG kernel and put the NK2 Kernel back in, and rebooted for the time being. It's working well, I just cannot get TowelrootV3 installed so that I can install SuperSU.
I've rooted another S5, using the very same procedure, and had absolutely no problems.
What am I doing wrong on this phone? It's driving me crazy, and I don' t have too far to go...:silly:
Thanks in Advance!
Please Help.
Stone.
Click to expand...
Click to collapse
Check enable USB debugging and see if it works.

Problem fixed... working now, successfully Rooted
Well,
I found that if you do not copy the towelroot.apk to your internal memory, it will not allow you to install towelroot.
Instead of Downloading towelroot.apk from the website from the phone itself, I downloaded it onto my PC. Then connected my phone to my pc, and placed it into "Access Picture" mode so that you can upload and download pictures into the phone's internal memory. I used that mode to copy towelroot from my pc to the phone.
I used Odin3 to load up NGC Kernel.
Then I disconnected from my pc, rebooted the phone, and was able to install towelroot with no further warnings.
Once that was done, I was able to use Odin3 again to load back up the NK2 original Kernel. I then rebooted again,
and then I could "Make it Rain". After a nice summer rainstorm, I was able to install SuperSU from Google Playstore and install it.
I sure hope that when 5.0 comes to our Verizon Android S5 phones, it's equally as easy to get root access as it has been for 4.4.4. I would surely be hindered without it as my phone relies upon a lot of apps that require root access. Unless Verizon changes their ways, this will be the last Samsung Galaxy I will ever purchase, so that I can move over to a Nexus device.
Thanks to everyone who has stepped up and helped us keep our phones productive and rooted.
Cheers,
-Stone
:good:

[Q] May have bricked my Tab

So my wife and I got a 7" Tab 3 from some hour long seminar thing. She setup her account and then I did mine. On mine I get a popup about every 20 seconds about my Knox account not being activate. I've never heard of Knox so I did some googling. In the security administrators menu it won't let me uncheck the Knox box. There is no Knox app. When I go into all apps there are 2 apps with Knox in the name and I can't open, kill, stop, or anything else to either. So from what I could tell I was stuck with the popup. I decided to try and root it and see if I could delete it that way. I have probably rooted about 15 phones, tabs, iCraps, etc. in the past with no problems. During the Odin root it failed. Now it's stuck at a screen saying "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again". I'm downloading Kies now. Any suggestions? Thanks

How did you root it? This is tab 4 forum not 3.... Can you still get into Odin mode?
Sent from my XT907 using XDA Free mobile app

twstdtstcles said:
So my wife and I got a 7" Tab 3 from some hour long seminar thing. She setup her account and then I did mine. On mine I get a popup about every 20 seconds about my Knox account not being activate. I've never heard of Knox so I did some googling. In the security administrators menu it won't let me uncheck the Knox box. There is no Knox app. When I go into all apps there are 2 apps with Knox in the name and I can't open, kill, stop, or anything else to either. So from what I could tell I was stuck with the popup. I decided to try and root it and see if I could delete it that way. I have probably rooted about 15 phones, tabs, iCraps, etc. in the past with no problems. During the Odin root it failed. Now it's stuck at a screen saying "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again". I'm downloading Kies now. Any suggestions? Thanks
Click to expand...
Click to collapse
search odin reboot, odin reboot tar, odin reboot dummy, odin force reboot
it's one of those, when you find the thread you'll know it.
flash that dummy file to force odin to reboot and hopefully clear/dump cache,
make sure you have the appropriate custom recovery odin image for your tab,
if odin reboot works, force reboot your tab again to odin, start a fresh session of
odin on your pc [not reset, a new session] flash your custom recovery,
i strongly advise AGAINST twrp for this operation, after you get your tab
re-established then switch to twrp if that's your preference.
if recovery flash goes well, force reboot to recovery and connect via adb.
download chainfire's latest supersu update zip and a custom rom for your
tab, if needed. Push file to tab via adb push, then flash supersu if your
stock rom is still intact, otherwise flash custom rom.
stock rom intact - open app drawer and launch supersu, it should ask you
if you want to disable the knox nag. if successful, reboot to recovery
and make a backup, then perform a factory reset, reboot and re-launch
supersu and go from there.
by the way... WRONG FORUM !!!
just kidding ... :silly:
seriously though...
m

First, thanks for the reply. I got it fixed this morning.
Sorry, it's a Tab 4. I guess I was in a hurry and tried flashing the firmware for the 10". I let it sit overnight so the battery would die. I downloaded the correct stock firmware which took hours. In the morning I let it charge for a few hours then plugged it into the computer. I got the same screen but Odin recognized it. I flashed the stock firmware without any problems. Its working fine now with no traces of Knox.
I guess the next step will be rooting it...

Tab 4 ...no google play store, etc. after unrooting??
Anyways I had the great idea of rooting my newly purchased TAB 4. I too used Odin 3. I loved the fact that I was successful at gaining root without data or app loss,. though slowly I began to see pop-ups pertaining to apps on my sd card. After awhile, I was seeing more pop ups on my screen for apps that began to stop working. Most importantly Google Play store. I panicked and decided to unroot without backing up. After that, I tried to factory restart. Being that I was no longer rooted, I figured it was safe to restart from scratch. What was I thinking? It all started over again, only this time with the out of the box look. Honestly I have only done the whole root process a couple of times and from what I understood it seemed to be fairly easy according to the process explained to me. All was well until I couldn't gain access to my apps. or for that matter download new ones. Is my Tablet dead or is there a possible answer? Does anyone have any suggestions on what I could do?
Thanks
twitch23

I think you're leaving a step out here... Did you use some app like apps 2 SD? Why did you root? What root software did you use?
Sent from my XT907 using XDA Free mobile app

hi,
after unroot , factory reset, cache and dalvik wipe don't account for the
garbage left in /data/data and settings left in place.
apps 2 sd is janky on stock roms, that's been my experience anyway.
you should only be using an odin root method for devices that do not
have a custom recovery available. Use chainfire's supersu update zip.
m

[ROOT] (Updated) Official Stock Nougat 7.0 (100% Working) - All Exynos Models

ROOT for Official Stock Nougat 7.0 (100% Working) - All Exynos Models (Tested it on SM-G930F/D SM-G935F/D)
By rooting you may lose some and gain some. Be careful in what you are doing.
Read each and every step mentioned in this post carefully and then start working on Root.
If you've any fear about the root. Please stop it here and close the window :angel:
Desclaimer:
[*]This is working on Exynos (SM-G930F) S7 Flat and (SM-G935F) S7 Edge models! (Should also work on all the Exynos Models)
[*]This will erase your phone so be sure to backup anything you need
[*]Your warranty is VOID Knox flags 0x1 or 0x500
[*]I'm not responsible for damage to your mobile or loss of warranty!
Things that may not work:
No official OTA updates (Of-course)
All Knox Based Apps (Samsung Pass, Secure Folder, Samsung Pay, S Health)
But you can get the above working - We have some ways to make them work even after root. Please Check that after the root process below
Here are the instructions to root your Nougat:
Instructions are similar to Marshmallow. Main thing to note here is - Use the latest supersu build.
Prerequisite:
Samsung Drivers
ODIN
SR2-SuperSU-v2.79 and above versions.
twrp-3.0.2-4
Instructions:
Enable OEM unlock & Debugging Mode in the Developer Options
Reboot your device into Download mode. To do this, hold the [Volume Down] + [Home] buttons for a while.
Once you reach the Download mode warning screen, press [Volume Up] to continue.
Open Odin and place that TWRP tar file in the [AP] slot and disable Auto-Reboot and click on "Start" by connecting your phone.
When its done flashing, Hold [Volume Down] + [Home] + [Power] to get out of Download mode and immediately swap to [Volume Up] when the screen blanks.
If you don't see TWRP boot splash, try again.
At this point, you will reach the screen asking you if you want to allow system modifications.
By swiping right, you will trigger dm-verity, and if you don't follow the next step you will be unable to boot!
If you are going to root your device and follow the rest of these steps, then it is safe to swipe right and enable modifications.
If you want to use Systemless DevBase, then do not swipe. Keep it as read only.
Go to Wipe and click on format data. Type "yes" and it will format.
Now go back to home and click on "Reboot" then click on "Recovery" Option.
Now Transfer the above downloaded filed into your Phone or Memory Card or OTG Pendrive.
Now again click on Install and flash the Super SU. Only the latest Super SU is working fine with no issues. Do not use the old versions.
You can now click on reboot > system
It will take about 5 Min and boot. Done. You've got the Nougat rooted.
After the fresh boot, you will setup everything. Once you are in, you can observe a notification.
This is a security notification - unauthorised actions have been detected. Restart your device to undo any unauthorised changes
Disable the notification permissions in settings and restart your device by using power button.
Do not restart it by using the option mentioned in that window!
Now go into supersu app. A popup will open to disable the Knox. click on OK. It will take some time to disable it. If its taking more than 5 min and failed to disable, then restart the mobile again and do the same step. it will work now.
Note: You can ignore the last step, If you want to use KNOX - do not disable it.
How to Disable the notification permissions:
Slightly move the notification to the right. You can see a 'settings icon'. Click on that and you'll be taken to notification permissions.
If you see "Allo notifications", disable it.
or
Go to Settings > Applications > Click on 3 dot menu on the right corner and select "Show system Apps". Find "SecurityLogAgent" and open it.
If you dont see that option to disable the notifications:
Go to settings > device maintainance > Device Security > Click on scan device once and close the settings.
Open the supersu app and you may see the popup to disable KNOX. click on OK. (If you've already done this, just restart your mobile)
Restart the device. Done.
If you the see the notification again, install titanium Backup app and Disable/Freeze - SecurityLogAgent & SharedDeviceKeyguard.
Restart your mobile.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I've Mentioned that some of the things may not work. But, You can make it work if you follow some of the other threads posted for our S7.
Here is the list of all the different threads about Root:
1. If you dont need anything except root : Follow the above root process and you are done.
OTA Updates & Knox based Samsung Apps (S Pay, S Health, Secure Folder & S Pass) do not work.
2. If you want to tweak your device with Mods & Apps:
This includes Custom Kernel Installation, Some Mods/Apps -
Custom Kernels for Nougat:
Super Kernel
Super Stock Kernel
TGP Kernel
Mods & Apps:
UniMod script
The Sound Mod Thread by ZuBi182
Zero Camera Mod v8.1 - Bitrates | JPG+ quality | Latest Camera - G930/G935 - New App
Viper4Android
Viper4Arise
ADDONS-v11.0.by.ambasadii - This will contain all the above mods and ROM control options.
Google Assistant
3. If you want root with most of the things working: Use this method only after flashing the Official firmware through odin.
Use knox and Samsung pay with root
How to use snapchat with root (no Xposed needed)
Nougat w/ working Samsung Pay STEP BY STEP Guide
Samsung Pass and OTA updates May/do not work here.
4. If you want root with OTA updates and some other things:
Follow this thread - SYSTEMLESS DevBase
Note: It seems Samsung Pass is not working in anyway after root. If you want to use it, please stay without root.
Custom Stock Nougat ROMs - Following are some of the custom stock ROMs:
Flashable CSC Selection
SuperMan ROM
Helios ROM
Android Nougat 7.0 by ambasadii
Stable D8N ROM
THE GALAXY PROJECT
SuperStock ROM
Norma ROM
Aurora ROM
Thanks to:
@Chainfire
@jcadduono
@_alexndr
@zubi182
@NQNH
And All the Devs working on S7.
Special Note:
Please do not use the old versions of supersu on Nougat. You'll have some problems with the root. You may get the root but some of the things may not work well.
Camera doesnt work, flash light doesnt work, wifi problem, delay in response, keyboard doesn't work properly, App closure etc etc.
So, use SR2-SuperSU-v2.79-SR2-20170103215521 and above versions for better results.
Phsuperuser and magisk will also work but, you may have to use custom kernels.
Did you brick your device ?
Then flash the official firmware using ODIN. Download the official stock firmware from sammobile.com or by using this tool
Hit Thanks if it helps :fingers-crossed:
have a good day:good:

This worked for me Thank You ..
but, I could not find the place to disable this notification ..
"You may get a security notification that "unauthorized actions have been detected. Restart your device to undo any unauthorized changes."
Open the notification and scan the device once. Then Disable the notification permissions for that in settings and restart your device."
The option to disable the notifications doesn't work?
Help me with this one?

cocteau2x said:
This worked for me Thank You ..
but, I could not find the place to disable this notification ..
"You may get a security notification that "unauthorized actions have been detected. Restart your device to undo any unauthorized changes."
Open the notification and scan the device once. Then Disable the notification permissions for that in settings and restart your device."
The option to disable the notifications doesn't work?
Help me with this one?
Click to expand...
Click to collapse
Slightly move the notification to the right. You can see a 'settings icon'. Click on that and you'll be taken to notification permissions.
If you see "Allo notifications", disable it.
or
Go to Settings > Applications > Click on 3 dot menu and select "Show system Apps". Find "SecurityLogAgent" and open it.
Some of the members are unable to see this option. Members who have upgraded directly from Marshmallow to Nougat are having this issue. You cannot change the notification permissions for system Apps. And for those who have upgraded from Beta, they have the option to disable. not sure why.
If you dont see that option to disable the notifications:
Go to settings > device maintainance > Device Security > Click on scan device once and close the settings.
Open the supersu app and you may see the popup to disable KNOX. click on OK. (If you've already done this, just restart your mobile)
Restart the device. Done.
If you the see the notification again, install titanium Backup app and Disable/Freeze - SecurityLogAgent or SharedDeviceKeyguard.
Restart your mobile.
We have some MODs available to remove knox and bloatware for Marshmallow and Beta Nougat. I did not test any mods on this official Nougat.
May be after sometime this procedure will get easy.
Hope that helps :good:

Killer333 said:
ROOT for Official Stock Nougat 7.0 (100% Working) - Exynos SM-G930F/D SM-G935F/D
Desclaimer:
This is working on Exynos (SM-G930F) S7 Flat and (SM-G935F) S7 Edge models! (Didnt test on other Models! )
This will erase your phone so be sure to backup anything you need
Your warranty is VOID Knox flags 0x1
I'm not responsible for damage to your mobile or loss of warranty!
Things that may not work: You Can Ignore these.
No official OTA updates (Of-course)
Samsung Pass - Its not working from the beginning!
S Health App (Sorry Gear S users)
'Motion Effect' option in 'Set as wallpaper' option (No one knows about this ).
I got the official Nougat 7.0 Update recently and I've tried rooting.
Here are the instructions to root your Nougat:
Instructions are similar to Marshmallow. Main thing to note here is - Use the latest supersu build.
Prerequisite:
Samsung Drivers
ODIN
SR2-SuperSU-v2.79-SR2-20170103215521
twrp-3.0.2-4
no-verity-opt-encrypt - Latest One - 5.1.
Instructions:
Enable OEM unlock & Debugging Mode in the Developer Options
Reboot your device into Download mode. To do this, select reboot from the power menu and hold the [Volume Down] + [Home] buttons while your device reboots.
Once you reach the Download mode warning screen, press [Volume Up] to continue.
Open Odin and place that TWRP tar file in the [AP] slot and disable Auto-Reboot and click on "Start" by connecting your phone.
When its done flashing, Hold [Volume Down] + [Home] + [Power] to get out of Download mode and immediately swap to [Volume Up] when the screen blanks.
If you don't see then TWRP boot splash try again from step 6.
At this point, you will reach the screen asking you if you want to allow system modifications.
By swiping right, you will trigger dm-verity, and if you don't follow the next step you will be unable to boot!
If you are going to root your device and follow the rest of these steps, then it is safe to swipe right and enable modifications.
Go to Wipe and click on format data. Type "yes" and it will format.
Now go back to home and click on "Reboot" then click on "Recovery" Option.
Now Transfer the above downloaded filed into your phone or memory card or OTG Pendrive.
Now, in TWRP , Click on "Install". Go to the file location and select "no-verity-opt-encrypt-XXX" and swipe to the right.
Now again click on Install and flash the Super SU. Only the latest Super SU is working fine with no issues. Do not use the old versions.
You can now click on reboot > system
It will take about 5 Min and boot. Done. You've got the Nougat rooted.
You may get a security notification that "unathorised actions have been detected. Restart your device to undo any unauthorised changes."
Open the notification and scan the device once. Then Disable the notification permissions for that in settings and restart your device by using power button.
Do not restart it by using the option mentioned in that window!
By using power button, restart your mobile and go into supersu app. A popup will open to disable the Knox. click on OK. It will take some time to disable it. If its taking more than 5 min and unable to disable then restart the mobile again and do the same step. it will work now.
How to Disable the notification permissions:
Slightly move the notification to the right. You can see a 'settings icon'. Click on that and you'll be taken to notification permissions.
If you see "Allo notifications", disable it.
or
Go to Settings > Applications > Click on 3 dot menu on the right corner and select "Show system Apps". Find "SecurityLogAgent" and open it.
Some of the members are unable to see this option. Members who have upgraded directly from Marshmallow to Nougat are having this issue. You cannot change the notification permissions for system Apps. And for those who have upgraded from Beta, they have the option to disable. not sure why.
If you dont see that option to disable the notifications:
Go to settings > device maintainance > Device Security > Click on scan device once and close the settings.
Open the supersu app and you may see the popup to disable KNOX. click on OK. (If you've already done this, just restart your mobile)
Restart the device. Done.
If you the see the notification again, install titanium Backup app and Disable/Freeze - SecurityLogAgent or SharedDeviceKeyguard.
Restart your mobile.
You can also Flash Sound Mods by ZuBi182. Its working. You can get the files here
and also Viper4Android. You can check this thread
Thanks to:
@Chainfire
@jcadduono
@zubi182
@NQNH
Special Note:
Please do not use the old versions of supersu on Nougat. You'll have some problems with the root. You may get the root but some of the things may not work well.
Camera doesnt work, flash light doesnt work, wifi problem, delay in response, keyboard doesn't work properly, App closure etc etc.
Use SR2-SuperSU-v2.79-SR2-20170103215521 and above versions for better results :good:
I haven't tried ph super user and magisk! So, cant comment anything on that.
Hit Thanks if it helps.
have a good day:good:
Click to expand...
Click to collapse
Read on TWRP thread that the latest super su does not require flashing of no verify zip file as it does the job? Is that true?

But now I can't log in on Snapchat

facutopa said:
But now I can't log in on Snapchat
Click to expand...
Click to collapse
I think it's your first time to root your phone.
Snapchat will not work on Rooted devices. Its blocking the user to login on rooted devices.
But, we have many threads in XDA on how to use snapchat despite the root. You should takeout some time to search on google
Here is a thread by @TheGejr - Snapchat on rooted devices without Xposed (Nougat)
Another Thread : Snapchat and Root
Or you can use the following steps:
unroot your phone and Restart : Open Supersu > go into settings > go to 'Clenaup' Category > click on "Full unroot". It will remove the root.
Login to your snapchat.
Root the phone by super su again.
You can use the snapchat again.
Hope that helps

choosymoron said:
Read on TWRP thread that the latest super su does not require flashing of no verify zip file as it does the job? Is that true?
Click to expand...
Click to collapse
Not sure. Can you link that thread ?

Killer333 said:
Not sure. Can you link that thread ?
Click to expand...
Click to collapse
Sure here you go..
http://forum.xda-developers.com/galaxy-s7/development/recovery-official-twrp-herolte-t3333770/page80

choosymoron said:
Sure here you go..
http://forum.xda-developers.com/galaxy-s7/development/recovery-official-twrp-herolte-t3333770/page80
Click to expand...
Click to collapse
Yeah Right. Its not needed (as per the comments in that thread).
I have observed the same in MM as well.
In most of the rooting method threads, everyone recommended to flash the no-verify zip. So, I did the same.
Will see if it works that way with the new supersu.
May be you can try that when you get the nougat update

I rooted my s7 v7.0 but i screen mirroring not working on this root i tried to connect when its connect it gives error failed.

Tnbh9 said:
I rooted my s7 v7.0 but i screen mirroring not working on this root i tried to connect when its connect it gives error failed.
Click to expand...
Click to collapse
Sorry wrong person reply..
---------- Post added at 02:13 PM ---------- Previous post was at 02:11 PM ----------
Haha yeah I'll keep you posted on that.

Tnbh9 said:
I rooted my s7 v7.0 but i screen mirroring not working on this root i tried to connect when its connect it gives error failed.
Click to expand...
Click to collapse
Was it working before root ?
I dont have any smart TV. So didnt check.
Try unrooting the device and check again.

Omg but way can't run s-health on ruted devices; bad samsung, bad! If any1 finds a way to enable it, please shere...or I can sell my gearfit
Sent from my SM-G930F using Tapatalk

Proday said:
Omg but way can't run s-health on ruted devices; bad samsung, bad! If any1 finds a way to enable it, please shere...or I can sell my gearfit
Sent from my SM-G930F using Tapatalk
Click to expand...
Click to collapse
How much you looking to sell it for
Sent from my SM-G930F using Tapatalk

Id like more to see working s-health than to sell it mate
Sent from my SM-G930F using Tapatalk

Proday said:
Id like more to see working s-health than to sell it mate
Click to expand...
Click to collapse
In the new official Nougat, S Health app is checking the KNOX flags due to updated security policy. If your knox tripped, then it wont work.
I've tried removing the knox, Removed S Health app and installed it as user app. Nothing worked.
This is working in custom ROMs. Anyway you want to root the official stock, so using custom roms is almost the same. Try them instead of this

[MENTION=817964]@Killer333 yeah, I know mate; becouse of that I'm waiting for new superman rom
Sent from my SM-G930F using Tapatalk

Proday said:
Id like more to see working s-health than to sell it mate
Sent from my SM-G930F using Tapatalk
Click to expand...
Click to collapse
Killer333 said:
In the new official Nougat, S Health app is checking the KNOX flags due to updated security policy. If your knox tripped, then it wont work.
I've tried removing the knox, Removed S Health app and installed it as user app. Nothing worked.
This is working in custom ROMs. Anyway you want to root the official stock, so using custom roms is almost the same. Try them instead of this
Click to expand...
Click to collapse
I didn't try it myself but maybe it will work:
Just delete S Health completely from system/app and get an older version (e.g. 4.8) from apkmirror. Install that apk as a regular user app and let it update. Some people claim that this method worked for them.

Root dont work
Hi i have s7 with nougat official and I root the phone is ok I have root all good but the root apps don't work properly they ask for permission every 10 sec or crash or they tell my i don't have root the root futures of apps don't work properly
(Lucky Packer crash . Game killer after premison don't work or they tell my my phone isn't root .app2sd error on root)

just install the TWRP another kernel for example, TGP Kernel then lucky works

S6 SM-G920P BoostMobile G920PVPU3BOL1 5.1.1 STOCK Root XposedFW Viper4A 2020

Stock out of box Samsung Galaxy S6 From Boost Mobile.
Disclaimer >>>Might Work With the Sprint S6, since Boost is just the prepay of Sprint, the same phone I think...
First to say this is a rare find (2015 Release) but if you can get your hands on this awesome handset it has, 8Cores, 32Gb of Memory, 16mp.Cam, and as far as i know the Last Samsung Galaxy With the iR Blaster. So I take No-Responsibility to any Malfunctions or Broken Devices. Personally Had Little to Zero Problems Achieving this I would say This is the Best, Most stable Rooted Device i'v ever owned.
Im Posting here expecting that everyone knows what ROOT, TWRP, CWM, SuperSU is, Developer Mode/How to activate, how to reboot to recovery/Download Mode, Flash via Odin, and use TWRP.
I'll try to put this whole thing in chronological order. so out of box... or anyone who can restore their device back to this build BOL1It Works Flawlessly, Very-Fast/ResponsiveSystem Wide Equalizer>V4A-starts on boot, Xposed FW, Xprivacy, Lightning Wall, and The Google PlayStore still works.
Take Phone out of box [UNACTIVATED/NOSIM/AIRPLANE] LoL... Turn on at home alone... DO NOT CONNECT TO WiFi/DATA it will force update BOL1. Dont sign in google Acc. or Samsung Acc. SET UP http://wakasoftware.com/app-freezer-setup/ Once Completed With Freezer App Set up Reboot and Freeze The following Apk.'s
Search (Update) in Freezer app. You should find [com.sec.android.fotaclient, com.wssyncmldm, com.sec.fwservice, com.sprint.ce.updater, and [NOT100%ON com.policydm] Disable them. Next search sprint in Freezer; Disable every apk. listed under sprint search [com.sprint.zone, com.sprint.psdg.sw, com.samsung.sprint.chameleon, com.sprint.w.installer, com.sprint.ce.updater, com.sprint.w.prefact, com.sprint.dsa, com.samsung.sprint.setupwizard, and com.sprint.voicemail]
You can probably leave voicemail enabled boost has theirs installed anyways. Not sure if sprint-Vmail works or not. Go ahead and freeze any bloat ware or apps you don't want. Disable at own risk. If something messes anything up, reboot to recovery, factory reset, then start over lol
THIS WILL TRIP KNOX
Alright now go developer options and turn on OEM unlocking (allow the Bootloader to be unlocked) Now im going to thank (spammy l) XDA Member for this post https://forum.xda-developers.com/sp...ainfire-autoroot-stock-custom-kernel-t3294308
Follow That Root Method-Just USE THE LATEST SuperSU & TWRP instead. Im on [SU 2.82-SR3] & [twrp-3.3.1-0-zerofltespr] Once obtained Root, an have installed TWRP&BUSYBOX; Create a Custom Recovery backup-TWRP BEFORE you go on to install XposedFW.
You can connect to WiFi/Data, set up google, samsung accounts, and activate wireless services/put SiM Card Back/Disable-airplane-mode now that you have the sprint apps disabled. WARNING if you root this without sprint apps disabled sprint will detect root on the phone and try to force update and continuously restart the phone only 10seconds or so after bootup. I did not know this when i first activated my services. Even after i turned off wifi and pulled the sim card out it was still rebooting only 10seconds after bootup. Giving me only moments to navigate to freezer app and search ''sprint'' and freeze freeze freezze.... so thats why we freeze them first. Also by disabling the sprint Apk. s it Removed the Boost Mobile Boot Animation not sure which one but just FYI just see stock samsung boot.img cool still.
Next have to Thank (wanam Contributor/Developer) For Their Forum( https://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960 ) on how to install XposedFW For [5.1/6.0]Lollipop/Marshmallow. Follow That to get Xposed Installed properly. Once flashed it dose take a few minuets to startup, it will boot cycle a couple times, be patient.
Last but my personal favorite piece of software to place in to the system, ViPER4Android-FX 2.5.0.5
My last shout-out goes to (kevintm78 Senior Member) for his method on installing V4A The Proper Way. Here (https://forum.xda-developers.com/note-4/themes-apps/how-to-viper4android-install-proper-t3691597) after all that you should make a new custom recovery point to save your work. Thanks to all just wanted to put all that into one place for this specific build of phone.
A Few Apk. s to Mention
--Galaxy Universal Remote Version 4.1.3 out there on the web<<aptoid
--XBooster-Free Version 5.1.2 PlayStore
--Physical Button Music Control Version 4.0 beta6 Xposed Module
--lightningWall Version 3.9.2 Xposed Module
--APM+ (Advanced Power Menu) Version 17.12 Xposed Module
--XPrivacy Version 3.6.19 Xposed Module
--Flappy Bird Version 1.3 lol...

Database Users

welcome