Database Users

The difference between "Official" and "Custom" device status was S-Health.

The difference between "Official" and "Custom" device status was S-Health.
I was freaking out over being unable to get my S5 to show as "Official" in its device status (wanted to update, but was told I couldn't) .Out of paranoia, I copied over all my Downloads to my SD card and removed it, deleted any root apps and even cleaned it up using SuperSU. And I rebooted a lot. After I finished, I still saw
Device Status: Custom
Then, I remembered the S-Health bug. Since i like S-Health, I had switched it over recently from being a System app to being a User one (because S-Health on a rooted device was, well, broken). So I re-rooted with SuperSU, then re-opened Android Tuner Free and moved S-Health back from being a User app to being a System one again.
Device Status: Official
I didn't even have to unroot, remove the SU app, or reboot it; I just checked back in Settings and it was "fixed."

Really and it have you official from what I know custom comes out because the phone is rooted anybody correct if im wrong
Sent from my SM-G900P

verse187 said:
Really and it have you official from what I know custom comes out because the phone is rooted anybody correct if im wrong
Sent from my SM-G900P
Click to expand...
Click to collapse
Well, it looks like I spoke too soon. During my OTA update attempts, I had root and it showed as "Official" for a while. Then when I removed SuperSU fully (including the su binaries, making it unrooted), my next attempt to install the update proved futile.
Somehow, when I removed the su binaries with SuperSU, it re-registered my device as Custom. I don't know how, because SuperSU had been specifically told to not attempt to retain itself during OTA updates...

primetechv2 said:
Well, it looks like I spoke too soon. During my OTA update attempts, I had root and it showed as "Official" for a while. Then when I removed SuperSU fully (including the su binaries, making it unrooted), my next attempt to install the update proved futile.
Somehow, when I removed the su binaries with SuperSU, it re-registered my device as Custom. I don't know how, because SuperSU had been specifically told to not attempt to retain itself during OTA updates...
Click to expand...
Click to collapse
You did not reinstall stock recovery. You cannot get OTAs if you have a custom recovery still.

KennyG123 said:
You did not reinstall stock recovery. You cannot get OTAs if you have a custom recovery still.
Click to expand...
Click to collapse
I never actually installed a custom recovery, though. I did eventually reinstall the fully stock firmware with Kies and then performed the upgrade, something I'm going to guess wouldn't be possible otherwise... But to be specific, I never had anything installed except got XPosed mods and a moved S Health to get it functioning again.
But I'm really sad that, for whatever reason, my device status kept flickering between Official and Custom, especially when it chose Custom after I disabled root.

I just flashed the stock nd5 firmware through odin in mine and it still show's as ''custom''. Any ideas on how to get it to show ''official''?

BlackJou said:
I just flashed the stock nd5 firmware through odin in mine and it still show's as ''custom''. Any ideas on how to get it to show ''official''?
Click to expand...
Click to collapse
I ran into the same issue when trying to update OTA for WiFi calling. I wound up (before I had a chance to reset), changing the runtime back to Dalvik from ART, wound up working.

frcollier said:
I ran into the same issue when trying to update OTA for WiFi calling. I wound up (before I had a chance to reset), changing the runtime back to Dalvik from ART, wound up working.
Click to expand...
Click to collapse
It is on Dalvik though :/

well, I did it again.
rooted: Official status
Installed XPosed: Official
Removed S-Health: Official
Reinstalled old S-Health as a user app: Official
Shifted S-Health to System app: Official
Removed XPosed: Custom
Anybody know what permissions SHealth and HealthService (.apk, .odex) should be reinstated with, and in which folder they go, I'd be really happy. Especially if someone got back to me before I downloaded this 1.5GB system file to figure out if it says.

[GUIDE] AT&T Samsung Galaxy S4 SGH-I337 Lollipop 5.0.1 OK2 Root Xposed Etc.

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.

[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

How to Root G935FXXU1DPLT Latest 7.0 Build

Hello
Any one know how to root latest nougat release?????
G935FXXU1DPLT

sriszone said:
Hello
Any one know how to root latest nougat release?????
G935FXXU1DPLT
Click to expand...
Click to collapse
Root same way as you rooted marshmallow. Flash twrp, flash supersu 2.79. everything is the same. it will take a while to boot though be patient.

Flash TWRP in Odin
Flash SR3-SuperSU-v2.79-SR3-20170114223742.zip in TWRP

no its not working......After install recovery stuck in Samsung Flashing logo....

TWRP is making the devices get stuck on Samsung logo....

I think what is happening is that when you install only the twrp the encryption of the device conflicts and leaves in bootoolp. When you install twrp and root , root already comes with a tool that takes out the encryption. But if you just want twrp, as was my case, you should, first of all, on your own twrp, wipe data and then flash no-verity-opt-encrypt.

Having root and no encryption sucks. Think I'll wait

Found Some Official Announcement From @Chainfire
Source :- Link
ChainFire Info
I'm not entirely sure what is going on here yet. I've had the stock firmware randomly stop booting even without modifying the boot image (rooting). Others have also reported that just flashing TWRP may trigger a bootloop (which is weird). I have some ideas what the cause may be, but it will be some time before I can properly investigate them.
The only way I seem to reliably get both TWRP and SuperSU working right now is:
- Flash TWRP (3.0.2-5) to recovery
- Immediately boot into TWRP
- If you were encrypted, format /data (ext4) and reboot into TWRP again
- Flash SuperSU v2.79-SR3 in TWRP
- Reboot into Android
The first boot will take a while if you performed that format, but for me it ultimately completes. Note that your device will be running unencrypted at this point!
Of course, if you format /data, you will lose all your data (including contents of internal storage!). Before I flashed the new version, I used FlashFire v0.54-PRE to create a backup of /data and internal storage to the removable sdcard, and restore that backup after flashing DPLT, rooting, and reinstalling FlashFire. This worked fine for me, and all my settings - including fingerprints and system settings - transferred fine. I came from the first Nougat beta, but I've seen others reporting success doing the same thing coming from Marshmallow. As always, your mileage may vary.
Unfortunately, due to this boot-loop issue with DPLT and encrypted data, it is also impossible to use FlashFire to upgrade the firmware itself to DPLT while keeping root if you started with an encrypted device.
I am not sure if the same difficulties exist with other official builds than DPLT, nor if the same problems occur with any of the custom ROMs based on DPLT. The S7 is my daily driver so I don't like to experiment with it too much
Below attach the required Files, I gonna try tomorrow. If anyone tried now please report update.
DOWNLOAD HERE

I did root few minutes ago on my 7.0 but now im not unable to launch s health because knox is disabled.

sriszone said:
Found Some Official Announcement From @Chainfire
Source :- Link
ChainFire Info
I'm not entirely sure what is going on here yet. I've had the stock firmware randomly stop booting even without modifying the boot image (rooting). Others have also reported that just flashing TWRP may trigger a bootloop (which is weird). I have some ideas what the cause may be, but it will be some time before I can properly investigate them.
The only way I seem to reliably get both TWRP and SuperSU working right now is:
- Flash TWRP (3.0.2-5) to recovery
- Immediately boot into TWRP
- If you were encrypted, format /data (ext4) and reboot into TWRP again
- Flash SuperSU v2.79-SR3 in TWRP
- Reboot into Android
The first boot will take a while if you performed that format, but for me it ultimately completes. Note that your device will be running unencrypted at this point!
Of course, if you format /data, you will lose all your data (including contents of internal storage!). Before I flashed the new version, I used FlashFire v0.54-PRE to create a backup of /data and internal storage to the removable sdcard, and restore that backup after flashing DPLT, rooting, and reinstalling FlashFire. This worked fine for me, and all my settings - including fingerprints and system settings - transferred fine. I came from the first Nougat beta, but I've seen others reporting success doing the same thing coming from Marshmallow. As always, your mileage may vary.
Unfortunately, due to this boot-loop issue with DPLT and encrypted data, it is also impossible to use FlashFire to upgrade the firmware itself to DPLT while keeping root if you started with an encrypted device.
I am not sure if the same difficulties exist with other official builds than DPLT, nor if the same problems occur with any of the custom ROMs based on DPLT. The S7 is my daily driver so I don't like to experiment with it too much
Below attach the required Files, I gonna try tomorrow. If anyone tried now please report update.
DOWNLOAD HERE
Click to expand...
Click to collapse
You can root but you have to disable encryption. Not a fan of that personally so I'll wait for another solution. If I lose my phone at least I'll have secure power up enabled. There is no bypassing that. There are too many FRP exploits on Youtube so having no encryption and simply a password isn't enough in my opinion.
---------- Post added at 10:29 PM ---------- Previous post was at 10:29 PM ----------
Mystero said:
I did root few minutes ago on my 7.0 but now im not unable to launch s health because knox is disabled.
Click to expand...
Click to collapse
Since you are rooted, uninstall S Health and install a lower version number which doesn't require Knox.

Galactus said:
Since you are rooted, uninstall S Health and install a lower version number which doesn't require Knox.
Click to expand...
Click to collapse
Hi, i cannot manage to unistall S Health, tried already two apps, after reboot app is still there and if i try to install older version i get corrupted file error.

guys please explain what is encryption and unencription here.... how can i disable ? can we flash this no-verity-opt-encrypt-5.0.zip

sriszone said:
Hello
Any one know how to root latest nougat release?????
G935FXXU1DPLT
Click to expand...
Click to collapse
I got fully working root and TWRP on Nougat G935FXXU1DPLT.

I have installed nougat btu with Odin.
Installed twrp and rooted my device.
So far I have faced couple of issues
s health app is not working
Security log agent keeps popping up (drives me mad)
And my device freezes and reboots after i open lucky patcher
How to fix these issues

cross_312 said:
I have installed nougat btu with Odin.
Installed twrp and rooted my device.
So far I have faced couple of issues
s health app is not working
Security log agent keeps popping up (drives me mad)
And my device freezes and reboots after i open lucky patcher
How to fix these issues
Click to expand...
Click to collapse
Security log will stop after you launch SU application and let SU to disable knox, it takes me always two attempts, disable, keep trying then i restart smartphone and after restart i try to disable knox again and it works, no more pop ups.
About S Health I'm looking for solution, so far should be enough to install older version set it up and update for new one, problem is that i cannot uninstall old version to get new one working.

cross_312 said:
I have installed nougat btu with Odin.
Installed twrp and rooted my device.
So far I have faced couple of issues
s health app is not working
Security log agent keeps popping up (drives me mad)
And my device freezes and reboots after i open lucky patcher
How to fix these issues
Click to expand...
Click to collapse
S Health is now locked down if you have tripped knox. The only solution is to use an older version.
Mystero said:
Security log will stop after you launch SU application and let SU to disable knox, it takes me always two attempts, disable, keep trying then i restart smartphone and after restart i try to disable knox again and it works, no more pop ups.
About S Health I'm looking for solution, so far should be enough to install older version set it up and update for new one, problem is that i cannot uninstall old version to get new one working.
Click to expand...
Click to collapse
SuperSU couldn't disable Knox for me after many tries. In the end I just used Titanium to freeze Knox.

CuBz90 said:
S Health is now locked down if you have tripped knox. The only solution is to use an older version.
SuperSU couldn't disable Knox for me after many tries. In the end I just used Titanium to freeze Knox.
Click to expand...
Click to collapse
What did work for me was try to disable when SU was trying i did restart device and right after restart i did tried that again and it worked. Maybe lucky...
About S Healht how can i use older version if i cannot install one because new one exist, do you know how to remove s health? i Tried two apps for removing system apps without success.

Mystero said:
What did work for me was try to disable when SU was trying i did restart device and right after restart i did tried that again and it worked. Maybe lucky...
About S Healht how can i use older version if i cannot install one because new one exist, do you know how to remove s health? i Tried two apps for removing system apps without success.
Click to expand...
Click to collapse
Try titanium. Backup the app first and then uninstall.

CuBz90 said:
Try titanium. Backup the app first and then uninstall.
Click to expand...
Click to collapse
Sir thank you, i do not know how it is possible that another apps did not worked but titanium did removed new S Health. Afterwards i did install last version of S Health i found before version 5, After launching S Health and connecting account i did update on new S health and everything works.
You really saved me. Thank you

Mystero said:
Sir thank you, i do not know how it is possible that another apps did not worked but titanium did removed new S Health. Afterwards i did install last version of S Health i found before version 5, After launching S Health and connecting account i did update on new S health and everything works.
You really saved me. Thank you
Click to expand...
Click to collapse
i have tried to remove the s health app with titanium but everytime i try to install vesrion 4.8 phone says that i can not install this app beacuse there is a package with the same name
what verison did you install before s health 5 and how did you install it.
and can anyone tell me how do i make lucky patcher to work properly

After using UPSM Manager and UPSM+ almost all apps disabled/disappeared

Hi there
I wanted to add Messenger to UPSM screen (Ultra power saving mode), so I've tried UPSM Manager and UPSM+. None of them worked on my Galaxy S5 however, after few tries almost all of my apps disappeared. There are a few left. System: Contacts, Text messages, Phone, Settings plus Google and Lockwatch. That's all. The rest disappeared.
On application manager in settings I can see all of them, most of them have status "disabled".
I've downloaded those two apps from here:
UPSM Manager - https://forum.xda-developers.com/showthread.php?t=2751785
UPSM+ - http://downloadapk.net/down_UPSM-ROOT.html
I've read that there is a very high probability that they won't work and that Google does not refund price in such case hence downloading .apk - could it be some kind of trojan from the 2nd link?
I've connected with adb console and
PHP:
pm list packages -d
shows 300+ packages as disabled.
PHP:
pm list packages -d | while read line ; do pm enable ${line#*:} ; done
fails with
PHP:
Error: java.lang.SecurityException: Permission Denial: attempt to change component state from ...
I can't run su as it freezes adb shell - su is also disabled so I can't enable it nor reinstall (Failure [INSTALL_FAILED_INTERNAL_ERROR])
Any hint how to restore my phone? Right now it has less features than Nokia 3210...

So maybe I'll ask a different question. Is there a way in my current state to regain root access (via adb shell) and enable disabled apps?

Marooned_MB said:
So maybe I'll ask a different question. Is there a way in my current state to regain root access (via adb shell) and enable disabled apps?
Click to expand...
Click to collapse
Hi,
In order to get helped it is always useful to provide at the beginning some basic info like phone model, firmware ver , root, recovery (custom or stock) etc.
Easiest way when you messed up your phone would be just restore your nandroid backup but I assume that you didn't make one, did you?
If not, easiest way IMO to regain root is just flashing CF-autoroot or if you have a custom recovery supersu zip file.

I wrote in Galaxy S5 forum so
Anyway: Samsung Galaxy S5 (SM-G900F), Android 5.0, G900FXXU1BOJ1, stock os, rooted
Haven't heard of nandroid before. I had titanium backup, but that's just apps I assume and they are still present on the phone, just disabled.
I haven't heard of CF-autoroot neither, but after picking matching details I got to desktop.firmware.mobi/device:370/firmware:12219 (I can't post urls with <10 posts). I'll have to read what to do with it without breaking a phone even more.

Marooned_MB said:
I wrote in Galaxy S5 forum so
Anyway: Samsung Galaxy S5 (SM-G900F), Android 5.0, G900FXXU1BOJ1, stock os, rooted
Haven't heard of nandroid before. I had titanium backup, but that's just apps I assume and they are still present on the phone, just disabled.
I haven't heard of CF-autoroot neither, but after picking matching details I got to desktop.firmware.mobi/device:370/firmware:12219 (I can't post urls with <10 posts). I'll have to read what to do with it without breaking a phone even more.
Click to expand...
Click to collapse
Here is the link to CF-autoroot for S5 variants:
https://forum.xda-developers.com/showthread.php?t=2696537
For applying you need to be familiar with using odin pc software. Be aware that this will trigger KNOX flag if yours is still 0x0.
By the way, how did you root your device initially?

KNOX was set when I initially enable root. To be honest, I can't recall which software I used, but it just worked without any problems. I was more than a year ago. Maybe it was CF but I just don't remember the name?
Anyway, I've generated image via CF-autoroot but it fails:
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and now phone says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again" :-/

Many40 said:
Here is the link to CF-autoroot for S5 variants:
https://forum.xda-developers.com/showthread.php?t=2696537
Click to expand...
Click to collapse
That one succeed. There is a high probability I've used that one upon first root.
Anyway, it succeed but adb shell and then su still freezes. Nothing changed. Still no root I guess.

Marooned_MB said:
That one succeed. There is a high probability I've used that one upon first root.
Anyway, it succeed but adb shell and then su still freezes. Nothing changed. Still no root I guess.
Click to expand...
Click to collapse
Hmm, so you still can't enable any disabled apps? I am afraid that you may need to try factory reset and if this doesn't help then re-flash complete firmware with full wipe. Before I would make backup of all useful staff what is still working and available in your phone.
Edit: did you read whole app thread? There are a few solutions/workarounds which helped some users with their issues but not sure if it is applicable to your problem,

Many40 said:
Hmm, so you still can't enable any disabled apps?
Click to expand...
Click to collapse
Yes, exactly the same access denied error as mentioned in the 1st post. Like nothing changed at all.
Many40 said:
Before I would make backup of all useful staff what is still working and available in your phone.
Click to expand...
Click to collapse
I've downloaded all files (available without root) from sd card and internal memory.
Many40 said:
did you read whole app thread? There are a few solutions/workarounds which helped some users with their issues but not sure if it is applicable to your problem,
Click to expand...
Click to collapse
Nope, I will then. At least I'll try (157 pages!)
Thanks for your help

Many40 said:
I am afraid that you may need to try factory reset
Click to expand...
Click to collapse
There is a button "delete everything" but it does not work. Nothing happens when I click it. So the next step is to reflash firmware? That seems like a bit over my knowledge at the moment :/
Also, I assume there is no way to backup sms/mms - not able to install any backup soft and no root for adb:
PHP:
adb pull /data/data/com.android.providers.telephony/databases/mmssms.db
adb: error: failed to copy '/data/data/com.android.providers.telephony/databases/mmssms.db' to '.\mmssms.db': remote Permission denied
I'll try from recovery menu.

Ok, so it worked from recovery menu. Data are wiped, phone install some german bloatware and it's like when I first bought it. As I suspected, despite Google backup enabled, it does not work. No apps are being installed. I have to recreate every single app with it's data. That's a small disaster, ech..
Samsung backup restored some sms/mms but from February this year (heh).
Looks like all those automatic backup from Samsung and Google does not work at all and I should probably do some cyclic manual data dump. So why all those backup settings if it does nothing at all?
Anyway, thanks for your help.

Marooned_MB said:
Ok, so it worked from recovery menu. Data are wiped, phone install some german bloatware and it's like when I first bought it. As I suspected, despite Google backup enabled, it does not work. No apps are being installed. I have to recreate every single app with it's data. That's a small disaster, ech..
Samsung backup restored some sms/mms but from February this year (heh).
Looks like all those automatic backup from Samsung and Google does not work at all and I should probably do some cyclic manual data dump. So why all those backup settings if it does nothing at all?
Anyway, thanks for your help.
Click to expand...
Click to collapse
Sorry for that. What do you mean by saying "no apps installed" You wrote before that your apps (user and most of the system) have been disabled, not uninstalled by the UPSM.
Are all your disabled system apps still at the same state after factory reset?
You wrote german bloatware? It looks like you have German branded Lollipop 5.0 firmware installed. I would definitely move to Polish latest unbranded (XEO) Marsmallow 6.0.1 to clean up your phone or if you wish to have rooted and debloated stock-based firmware then this rom is a very good alternative:
https://forum.xda-developers.com/galaxy-s5/development/rom-ane4-kitkat-4-4-2-multi-csc-t2813628

Many40 said:
What do you mean by saying "no apps installed" You wrote before that your apps (user and most of the system) have been disabled, not uninstalled by the UPSM.
Are all your disabled system apps still at the same state after factory reset?
Click to expand...
Click to collapse
By saying "no apps installed" I meant that after factory reset (wipe from recovery menu) and signing into my google account, backup restore did not install anything. But I've done yet another reset, this time from options and this time I've set up google account on welcome wizard and.. it worked, google backup restored all 107 apps BUT with no settings (they claim that settings should be also restored), so I have all my apps, but with no settings, so like after fresh install. I'm recreating everything from scratch, one by one.
Many40 said:
You wrote german bloatware? It looks like you have German branded Lollipop 5.0 firmware installed. I would definitely move to Polish latest unbranded (XEO) Marsmallow 6.0.1 to clean up your phone or if you wish to have rooted and debloated stock-based firmware then this rom is a very good alternative:
https://forum.xda-developers.com/galaxy-s5/development/rom-ane4-kitkat-4-4-2-multi-csc-t2813628
Click to expand...
Click to collapse
Yup, phone was bought as (I'm not sure how to translate "powystawowy") refurbished, from shop exhibition(?), a bit cracked on corners, but 2x cheaper. Anyway, it was just a matter of uninstalling 5 German apps (with root of course).
I did not put any other firmware as the one from Samsung has some unique features like mentioned ultra power saving which I enjoy on long travels. I've read that custom roms does not support this or NFC and few others.