Database Users

[Q] no wifi rooted at&t S4 4.4.2 NB1

greetings!
I've been searching for hours and bashing my brains trying to get wifi working. It originally broke after an OTA update
tried all the tips and still nothing works permanently. The things I have tried are too numerous to remember or list.
It's not a hardware issue as wifi can work for periods of time but it always breaks - I assume because of an update that downloads and breaks it.
i see talk of reflashing "modules" with safestrap but safestrap has never worked properly and now does not work at all ("unfortunately safestrap has stopped") Can modules be flashed from Odin?
TIA !

Sorry to hear about your troubles man. Been there, done that...
IMHO, if you don't have hardware issues, this what you should do:
ODIN to stock http://forum.xda-developers.com/show....php?t=2616221 (post 1, the Returning to Stock / ODIN section)
After that root
Root with towel root (https://towelroot.com/)
Install SuperSU (PlayStore) and let it disable Knox.
Install BusyBox (PlayStore) and let it cook
Install SELinux Mode Changer (PlayStore). Run and set it to Permissive.
Install Safestrap (http://forum.xda-developers.com/show...php?p=45693712)
Now it's time to flash you favorite rom (Safestrap has the list). Copy the following to your SD card:
Your favority ROM
SuperSU.zip file. (http://download.chainfire.eu/451/Sup...erSU-v2.01.zip)
Your modem zip file (http://forum.xda-developers.com/show...96&postcount=1).
I337 Build.prop/APN (http://forum.xda-developers.com/show...81&postcount=9)

Same boat as well I believe, need help please.
I have a Samsung Galaxy S4 AT&T I337 ucufnbn1 MDF. And I've tried to get into the UMTS menu with every possible number and trick I can find on Google, here, YouTube. And nothing works. I just want to be able to sim unlock it and also be able to put cwm recovery on it so I can put ROMs on it. I do have it rooted with Towel and have busy box installed as well as SU. Cyanogen's website picks it up by its other name jfelte or whatever and has a lot of ROMs. If someone could please help me finish getting the rest of the way, that would be greatly appreciated.

Few screens to help out
Here are a few screen shots that I hope help someone out. Please let me know what I can do if anything.

ONLY DRAGONMIKE said:
I have a Samsung Galaxy S4 AT&T I337 ucufnbn1 MDF. And I've tried to get into the UMTS menu with every possible number and trick I can find on Google, here, YouTube. And nothing works. I just want to be able to sim unlock it and also be able to put cwm recovery on it so I can put ROMs on it. I do have it rooted with Towel and have busy box installed as well as SU. Cyanogen's website picks it up by its other name jfelte or whatever and has a lot of ROMs. If someone could please help me finish getting the rest of the way, that would be greatly appreciated.
Click to expand...
Click to collapse
You won't be able to put cwm on it or cm. See index, all things at&t......in the general forum
Sent from my Nexus 5 using XDA Free mobile app

Ummmm a tiny bit more help please lol
I looked at the stuff in that link and like eating ice cream to fast , I got a brain freeze or headache........ Lol. I'm getting that I need to downgrade to mk this and flash that. Could someone be kind enough to give me a quick but correct step by step run through. Again it'd be very appreciated.

ONLY DRAGONMIKE said:
I looked at the stuff in that link and like eating ice cream to fast , I got a brain freeze or headache........ Lol. I'm getting that I need to downgrade to mk this and flash that. Could someone be kind enough to give me a quick but correct step by step run through. Again it'd be very appreciated.
Click to expand...
Click to collapse
Just click on the spoiler for nb1 need users. The step by step is there. It's in the first post
Sent from my Nexus 5 using XDA Free mobile app

So this one
So are you talking about this one and if so, why would I do that when that's what I'm already on. I'm on nb1 4.4.2 rooted with towel. So I'm lost in what your trying to explain.

ONLY DRAGONMIKE said:
So are you talking about this one and if so, why would I do that when that's what I'm already on. I'm on nb1 4.4.2 rooted with towel. So I'm lost in what your trying to explain.
Click to expand...
Click to collapse
You're on nb1 and rooted. The next step is to install safestrap 3.72
Sent from my Nexus 5 using XDA Free mobile app

So Safestrap 3 it is
So I need to install Safestrap. I heard with my s4 being MDF , it would damage it. I could be wrong and if so cool. Just let me know no probs.

ONLY DRAGONMIKE said:
So I need to install Safestrap. I heard with my s4 being MDF , it would damage it. I could be wrong and if so cool. Just let me know no probs.
Click to expand...
Click to collapse
What's mdf?
Sent from my Nexus 5 using XDA Free mobile app

MDF Reply
Security software Version
MDF v1.0 Release 2

MDF Reply
Here is a screenshot of where I'm talking about. Oh and Safe strap 3.72 is installed perfectly thank you so very much for that. Your awesome. And a lot of people are saying when you reboot and it shows the "Safestrap is disabled" screen you can't get back into it. I did just fine.

ONLY DRAGONMIKE said:
Here is a screenshot of where I'm talking about.
Click to expand...
Click to collapse
You're on nb1 firmware, safestrap is ok
Sent from my Nexus 5 using XDA Free mobile app

NB1 discussion
Ok , well I honestly appreciate your help with this. With this setup can I install any ROMs at all? Am I limited to certain ones or can I install any compatible ones for my model? I know sometimes when your on a certain stock ROM your stuck with only like certain types. Like Paranoid or whatever it is, and a few others.

ONLY DRAGONMIKE said:
Ok , well I honestly appreciate your help with this. With this setup can I install any ROMs at all? Am I limited to certain ones or can I install any compatible ones for my model? I know sometimes when your on a certain stock ROM your stuck with only like certain types. Like Paranoid or whatever it is, and a few others.
Click to expand...
Click to collapse
You can not install any roms. The i337 on any firmware higher than mdl can only flash touch wiz based roms. See the index, all things at&t.... for roms that are compatible.
Sent from my Nexus 5 using XDA Free mobile app

This mini-guide should work!
The problem is, in order to get WiFi working, you need to install the NB1 modules, but to do that, you need to install Safestrap. However, you can not install Safestrap because the app keeps closing on you. There is a simple fix to this, which I will explain later. For now, just read this WHOLE post BEFORE you do anything, and keep in mind that I am NOT held liable if you mess up your phone. Use this at your own risk.
1.) Root your phone
If you're already rooted with something like SuperSU or Superuser, skip this. If not, read ahead. Download and install the Towelroot APK file attached to this post, open it, and click 'make it ra1n'. If your phone didn't reboot, now you have root (they need to trademark that). Now, down below, I also included the APK for SuperSU. Download and install it. Now open it. When you open it, let it install the 'Normal' way, not via the 'TWRP/CWM' way. Also, when it asks you to disable KNOX, say yes, wait a couple of minutes (it will still be loading) and reboot your phone. Open up SuperSU again, click 'Yes' to disable KNOX again, and now you have a good base to start from.
2.) Install Safestrap AFTER fixing the error
The error your are getting is easily fixed. Go to the Play Store and install 'SELinux Mode Changer'. Open it, grant it root access, and change the mode to 'Permissive'. Now, open up Safestrap again (you mentioned you already installed it), and it shouldn't force close. Click 'Install', and if the 'Reboot to Recovery' option below is not grayed out after that then it worked.
3.) Download and install the NB1 modules
On your phone, download the included NB1 modules ZIP file I attached for you, and once that is done you need to reboot. After the Galaxy S4 logo, you'll see a screen that says 'SAFESTRAP: DISABLED' and there will be a little robot. TIP: To enter Safestrap, press the menu button (physical, hardware key) under 'Recovery' at that screen. To continue to Android, press the back key (again, physical) under the 'System' tab. For now, press the menu button under 'Recovery'. Now, click 'Install' which should be in red, click 'Add zips', and navigate to your Downloads folder. Now click on the NB1 modules ZIP you just downloaded. Swipe to install, and reboot. This time, hit the back key under 'System'.
All done!
Now, Android should (and will) boot up, and you'll have working WiFi! If, for some odd reason, you don't have WiFi- do NOT panic! Just search around for the MF3 modules and flash those! All is good, all is good. A lot of this guide was taken from my post about my personal method of SIM unlocking the AT&T Galaxy S4 without the dialer codes or an AT&T SIM. It was just modified a little to work for you.
Remember, hit thanks! :good:

How to Downgrade Firmware on AT&T’s S5 Active SM-G870A and get Root Access after Augu

How to Downgrade Firmware on AT&T’s S5 Active SM-G870A and get Root Access after Augu
It took me over a week to search through threads and learn how to root my S5 Active SM-G870A after I installed the new August 2014 update and then later discovered the SD card issue (i.e. needing root access to allow apps to write to it).
Anyway, these forums helped but I had to piece lots together in order to do it right and make sure that I was not going to destroy a $600 phone.
Below is a compilation of what I found. I do not take any credit for the original contents. I have simply organized what I have found in many other threads so that others searching to resolve the same issue can do so in less time than me. Also, I put this together so that I do not feel like my time was wasted hunting all of this down!
How to Downgrade Firmware on AT&T’s S5 Active SM-G870A and get Root Access after August 2014 Update
Step 1: Downgrade your Phone’s Firmware to an Earlier Version
Original Thread Link: http://forum.xda-developers.com/showthread.php?t=2799754
Before Starting:
1. Download and Install the latest Samsung USB Drivers.
2. Download and install the latest version of Odin (you may need to extract it using a zip program).
3. Download and extract the firmware file: http://www.sammobile.com/firmwares/3/?download=31669 (May 9th, 2014) OR HERE.
4. Make sure USB debugging is checked under “Settings/Developer Options” (If you don't know how to do that, go to "About Device" in Settings, and click on "Build Number” 5 times to unlock “Developer Options").
5. Back up your phone using any backup program that does not require root, just in case.
Flash Instructions:
6. Open Odin v3.09.
7. Reboot phone in Download Mode (press and hold Home + Power + Volume Down buttons).
8. Connect phone to your PC and wait until you get a blue sign in Odin.
9. Add the un-zipped firmware file to AP / PDA (Make sure re-partition is NOT ticked).
10. Click the start button, sit back and wait a few minutes.
You should see a bar at the bottom of your phone indicating progress and also in Odin. Once the phone restarts Odin will check to see if the firmware flash was a success. If it is, the “System” box will now display “Success.” Congratulations, you have downgraded your phone’s firmware, now you can root it using towelroot (www.towelroot.com).
Step 2: Install Towelroot
Before Starting:
1. Disable antivirus software on your phone. Towelroot is an exploit: it is how you get root. So your antivirus (if it’s worth a damn) will flag it.
2. Make sure that your phone can install application from unknown sources: Settings>Security>Unknown Sources>Check.
Towelroot Instructions:
3. Using your phone’s browser navigate to www.towelroot.com.
4. Click on the lambda in order to download the tr.apk file.
5. Locate the file on your phone and click on it. Chose the Android Package installer.
6. Follow the additional instructions.
Step 3: Do I have REALLY have Root Access?
1. Go to the Play Story and search “root checker.”
2. Download and install the app with the same name.
3. Run it. If it is a success, then download and install SuperSU.
I recommend getting Titanium Backup and paying for the pro-version ($5.99). Doing so will allow you to disable the AT&T notifications (“Freeze” AT&T Update) that will bug you once you downgrade your firmware, and there are lots of other things you can do with it now that your phone it rooted.
This “complete” intro guide should help anyone (especially newbies) root their S5 Active SM-G870A in a safe way if they have upgrade their phone in August 2014 or after.

UPDATE-Post Flash/Root
After working with the downgrade for a few days everything works fine except I lost the ability to use the default e-mail app. I noticed an "email" failure upon the first boot after the flash, but I ignored it because I was so focused on rooting.
This is not a big deal to me since I was not in love with the stock e-mail app to begin with. I have since found acceptable alternatives (that are actually better IMO). But if this is a big deal to you just be aware. It may be the firmware downgrade or it may have just happened to me. However, some people in the other thread mentioned losing GPS, but mine works fine (as does everything else).

I'm not a noob but thanks for putting this together

GS5 Firmware Download
Whenever I go to the SamMobile website, and go to the page for my phone (Samsung Galaxy S5 AT&T). When I download the file, I'm not able to extract the file because there is nothing in it. What am I doing wrong/does anyone have a direct download link. I tried googling around, but I couldn't find anything that worked.

Dont use the Odin Link, it is SPAM! just search xda
http://forum.xda-developers.com/galaxy-s-advance/help/version-odin3-v3-10-t2859776

Nice to have it all in one place!
UPDATE: Failed to work on SM-g900a. Guess I'll just keep waiting for someone to n crack lollipop code.
ranthon007 said:
It took me over a week to search through threads and learn how to root my S5 Active SM-G870A after I installed the new August 2014 update and then later discovered the SD card issue (i.e. needing root access to allow apps to write to it).
Anyway, these forums helped but I had to piece lots together in order to do it right and make sure that I was not going to destroy a $600 phone.
Below is a compilation of what I found. I do not take any credit for the original contents. I have simply organized what I have found in many other threads so that others searching to resolve the same issue can do so in less time than me. Also, I put this together so that I do not feel like my time was wasted hunting all of this down!
How to Downgrade Firmware on AT&T’s S5 Active SM-G870A and get Root Access after August 2014 Update
Step 1: Downgrade your Phone’s Firmware to an Earlier Version
Original Thread Link: http://forum.xda-developers.com/showthread.php?t=2799754
Before Starting:
1. Download and Install the latest Samsung USB Drivers.
2. Download and install the latest version of Odin (you may need to extract it using a zip program).
3. Download and extract the firmware file: http://www.sammobile.com/firmwares/3/?download=31669 (May 9th, 2014) OR HERE.
4. Make sure USB debugging is checked under “Settings/Developer Options” (If you don't know how to do that, go to "About Device" in Settings, and click on "Build Number” 5 times to unlock “Developer Options").
5. Back up your phone using any backup program that does not require root, just in case.
Flash Instructions:
6. Open Odin v3.09.
7. Reboot phone in Download Mode (press and hold Home + Power + Volume Down buttons).
8. Connect phone to your PC and wait until you get a blue sign in Odin.
9. Add the un-zipped firmware file to AP / PDA (Make sure re-partition is NOT ticked).
10. Click the start button, sit back and wait a few minutes.
You should see a bar at the bottom of your phone indicating progress and also in Odin. Once the phone restarts Odin will check to see if the firmware flash was a success. If it is, the “System” box will now display “Success.” Congratulations, you have downgraded your phone’s firmware, now you can root it using towelroot (www.towelroot.com).
Step 2: Install Towelroot
Before Starting:
1. Disable antivirus software on your phone. Towelroot is an exploit: it is how you get root. So your antivirus (if it’s worth a damn) will flag it.
2. Make sure that your phone can install application from unknown sources: Settings>Security>Unknown Sources>Check.
Towelroot Instructions:
3. Using your phone’s browser navigate to www.towelroot.com.
4. Click on the lambda in order to download the tr.apk file.
5. Locate the file on your phone and click on it. Chose the Android Package installer.
6. Follow the additional instructions.
Step 3: Do I have REALLY have Root Access?
1. Go to the Play Story and search “root checker.”
2. Download and install the app with the same name.
3. Run it. If it is a success, then download and install SuperSU.
I recommend getting Titanium Backup and paying for the pro-version ($5.99). Doing so will allow you to disable the AT&T notifications (“Freeze” AT&T Update) that will bug you once you downgrade your firmware, and there are lots of other things you can do with it now that your phone it rooted.
This “complete” intro guide should help anyone (especially newbies) root their S5 Active SM-G870A in a safe way if they have upgrade their phone in August 2014 or after.
Click to expand...
Click to collapse
Like you, I have been scouring the Web trying to downgrade my sm-g900a back to Kitkat since Lollipop and At&t's locked bootloader prohibits rooting or any kind of customization. Whatsoever. So I really appreciate you taking the time to compile these steps! I am wondering however, is there a way to use Odin on a device other than a PC or Mac? For example an LG tablet? Sorry if that's a noob question. I know how and have successfully rooted previous Samsung galaxies using my PC Odin. I'm just away from home and only have a tablet with me. And this Lollipop cap has got to go ! Really appreciate your response.

FAIL! (AUTH)
the message I get is FAIL! (AUTH) in Odin 3.09.
now I am stuck at the Android system recovery screen <3E>
I'm looking for a way back from this.

squirt r6 said:
the message I get is FAIL! (AUTH) in Odin 3.09.
now I am stuck at the Android system recovery screen <3E>
I'm looking for a way back from this.
Click to expand...
Click to collapse
I found solution. Just follow the guide in decription and everything is ok. https://www.youtube.com/watch?v=8481Qm0l010

nhutung said:
I found solution. Just follow the guide in decription and everything is ok.
Click to expand...
Click to collapse
I had the same exact problem you did. I followed the link. Thanks for that! I got a PASS from Odin! But I am still stuck on the recovery boot screen. Doing a Data wipe and Cache wipe then restart doesn't work. Still stuck on that page. Any suggestions? Every forum I find just says to perform the data wipe and cache wipe then restart and I should be golden, except I'm not.

Updated method!
Allows downgrade from MM 6.0 down to OF3, which we now have the ability to root using this guide.

sure this guide is for the G870A?
IJoxer said:
Updated method!
Allows downgrade from MM 6.0 down to OF3, which we now have the ability to root using this guide.
Click to expand...
Click to collapse
lJOXER, this guide seems to be for the standard S5 and not the ACTIVE? am i correct? is there any way to root a 5.0 OC3 ACTIVE?
---------- Post added at 03:35 PM ---------- Previous post was at 03:34 PM ----------
electric101 said:
lJOXER, this guide seems to be for the standard S5 and not the ACTIVE? am i correct? is there any way to root a 5.0 OC3 ACTIVE?
Click to expand...
Click to collapse
Sorry "OF3"

bigpapi19 said:
I'm not a noob but thanks for putting this together
Click to expand...
Click to collapse
you ever try this on the active?

electric101 said:
you ever try this on the active?
Click to expand...
Click to collapse
Hey @electric101, sorry, I upgraded to an S7 and have been using another account. This guide actually applied to both, which is also the case for most custom roms. I actually owned the Active myself, often flashed and rooted with 900a methods. Hope that helps, good luck!

thats interesting.... the guy who posted the actual guide (AptLogic) told me that it didnt work with the 870A .... did you try it on an unrooted 870A running 5.0 or newer? when i try it fails on the first step of flashing experimental firmware using odin 3.11
if you were able to maybe i'm just not doing something right....

thank u..
those who r havin trouble...change cords & keep tryin! took me 3 trys.... and a few mins to get passed the att logo screen.. dont get discouraged
i did and walked away came back later at it was all gravy... w android 5.0... still cant root it... so if anyone has any idea...

5.1.1 [DOK2] Setup [Debloated & Systemless Root] [Viper4Android][Bettery Battery]

5.1.1 [DOK2] Setup [Debloated & Systemless Root] [Viper4Android][Bettery Battery]
I have seen a few people having issues with the DOK2 update and were looking for a step by step process of how to upgrade to the new firmware and optimize it to get goo performance. this thread will guide you through that process as well as link to the appropriate threads to download and get the needed files/add ons.
*****This process will wipe your phones internal storage and give you a clean install of the new firmware.
Step 1: Download the DOK2 firmware to your PC
There are a few places you can get this from:
Sammobile: N910T Firmware
Or XDA thread: Stock TW Firmware/Bootloader/Modem N910TUVU2DOK2 UNMODIFIED Mirror
(You will need the entire firmware not just the modem and baseband)
Step 2: Download ODIN to you computer
From ODIN DOWNLOAD: ODIN 3.10.7
Step 3: Odin Flash new firmware.
The download from Sammobile or Mega should be a .zip file. you will need to unzip that file to find the .tar file which is what you will use for ODIN flashing the firmware.
If you need help using Odin to flash the firmware check out this post on Android Central: Help Thread
After you have completed the Odin Flash the phone should reboot and come to the setup screen with your new firmware.
Step 4: Odin Flash TWRP
Download TWRP to your computer: TWRP Downloads
Specifically you want this file: twrp-2.8.7.0-trltetmo.img.tar
Use Odin to flash TWRP recovery onto your device.
If you get lost you can check this tutorial: ODIN Help
Step 5: Reboot your device and setup
Once you have rebooted go ahead and set up your device. we will worry abou debloating and getting root after your device is setup.
Step 6: make a backup in TWRP
Once your device is setup make a TWRP backup of your setting
Step 7: Getting Root
*****Update: New SuperSu 2.64 beta. Works even better with Samsung phones. *******
You will need the latest SuperSU beta from the below thread.
SuperSU Beta Systemless Root
Newest version is 2.64
You will then boot into TWRP and flash that zip in recovery. This will give you "Systemless Root"
Systemless root allows you to use the stock kernel with SE LINUX enforcing, but still be able to use root apps. However this is not complete root. Some root apps that need to modify the system will not work. this is just a BETA root and is not final yet. check back to that thread for updates as they come out.
Once you have flashed the SuperSU zip reboot your device and verify your root apps are working.
Step 8: DeBloating TW.
There are 2 options for debloating TW.
Option #1: V3.90 Debloater V3.90 DeBloater
This option works on both rooted and unrooted devices. It really is a program that uases ADB to allow you to FREEZE system apps. This will not allow you to completely delete the application with Systemless Root.
The OP has a TON of detail and walks through this process of how to uses his program.
Option #2: [Script]Touchwiz De-Bloating Script and Gapps ~ 222 Apps
http://forum.xda-developers.com/not...pt-touchwiz-bloating-script-222-apps-t3258537
This Option removes 222 applications. It is a simple download and flash in recovery process.
****HOWEVER This will remove some functionality of the device READ the list of application before you flash to make sure there are not any that you use. The OP also has instructions on how to modify the script if you want some application to not be removed.
Step 9 Viper4Android on Systemless root.
Download the Viper4 Andriod/Beat installer
Viper4Android w/ Beat Audio
Flash the installer zip in TWRP and reboot your device
Download BusyBox Installer
BusyBox by Stephen (Stericson)
Install BusyBox
Reboot
install Viper$Android Drivers
Reboot
Download both the Viper4Android SU policy fixes
1.) ViPER4Android-supolicy.zip
2.) XM_V4A_Fix_by_androidexpert35.zip
Reboot into TWRP and flahs both of these. you can flash them at the same time just to them in the order above. [1 then 2]
Reboot the device and enjoy V4a.
******Also the Beat portion of the zip is a bit wonky sometimes. I have not yet been able to get it to opperate effectively, so you may want to disable it or freeze it with Titanium backup.
Disclaimer: NONE of these zips are mine. I am posting download links from my mega, because I pulled these files from 3 different threads and only one was from an OP. the main Viper4Android /beats install zip comes from here : [SUPER MOD][4.3+/6.0][ v6.2 ] XTREMEMusic™ THE SOUND THAT YOU'VE NEVER HEARD!
*************************************************************************************************************************************************************************
With this setup I have easily gotten more than a days worth of usage. I average about 5.5 hours of SOT and 24 hrs between charges. Normally I plug in around 20 hours with about 40% battery left.
*****These are all items developed by other XDA USERS. Please provide the thanks on their respective threads as well.

Thanks for taking the time for this write up. I don't have much experience with the new systemless root. I was wondering since the steps you mentioned above doesn't require any pre-rooted steps if there is any way of getting root without triggering Knox. I know in the past you can do this with Android 4.x, however since I'm currently on the latest boatloader there is no going back. I understand many don't care about Knox, but since my replacement and having Knox intact, I'd thought it might be worth my while since systemless root seems to be the future for new Android releases. Also I've been running stock for the last few months and the experience has been pretty good, though I miss some of the conveniences of having root.

James62370 said:
Thanks for taking the time for this write up. I don't have much experience with the new systemless root. I was wondering since the steps you mentioned above doesn't require any pre-rooted steps if there is anyway off getting root without triggering Knox. I know in the past you can do this with Android 4.x, however since I'm currently on the latest boatloader there is no going back. I understand many don't care about Knox, but since my replacement and having Knox intact, I'd thought it might be worth my while since systemless root seems to be the future for new Android releases. Also I've been running stock for the last few months and the experience has been pretty good, though I miss some of the conveniences of having root.
Click to expand...
Click to collapse
This method is for root only. It requires installing TWRP which is a custom recovery. That means you will have to unlock the bootloader to be able to use this method. Once you unlock the bootloader (by Odin flashing TWRP) you have already tripped Knox. Knox is no big deal from what I have heard though. I have not heard of anyone getting denied a new phone because it was tripped.
The two main reasons to use this method are:
1.) It keeps the system intact, which allows you to use apps that check for root. (eg. Android Pay, Some Bank Apps etc)
2.) It allows you to use the stock kernel from 5.1.1. Currently the only way to get root on 5.1.1 and up is to install a custom kernel. Which is fine, and there are two really great option available with Emotion and Beast Mode, but I find the stock kernel gets me the best battery life and is the most stable.
ALSO this will be the way root is done going forward. 6.0.1 has a bunch of system file locks that prevent much of the system tinkering from happening. Chainfire (dev who built SuperSU) has a nice right up about the system partition on XDA right now explaining why some of the system tweaks we were used to will not be possible in the future. so at the very least this is good practice for getting ready for the Marshmallow update.

ShrekOpher said:
Step 8: DeBloating TW.
There are 2 options for debloating TW.
Option #1: V3.90 Debloater [http://forum.xda-developers.com/android/software/debloater-remove-carrier-bloat-t2998294]
This option works on both rooted and unrooted devices. It really is a program that uases ADB to allow you to FREEZE system apps. This will not allow you to completely delete the application with Systemless Root.
The OP has a TON of detail and walks through this process of how to uses his program.
Option #2: [Script]Touchwiz De-Bloating Script and Gapps ~ 222 Apps [http://forum.xda-developers.com/not...t-touchwiz-bloating-script-222-apps-t3258537]
This Option removes 222 applications. It is a simple download and flash in recoevery process.
****HOWEVER This will remove some functionality of the device READ the list of application before you flash to make sure there are not any that you use. The OP also has instructions on how to modify the script if you want some application to not be removed.
Click to expand...
Click to collapse
Witch option is the easier? :silly:

Avide said:
Witch option is the easier? :silly:
Click to expand...
Click to collapse
Option #2 is WAY easier as long as you don't want to modify the script. You just download it to you phone boot into recovery and flash it. Then reboot. Takes 5 min.

ShrekOpher said:
This method is for root only. It requires installing TWRP which is a custom recovery. That means you will have to unlock the bootloader to be able to use this method. Once you unlock the bootloader (by Odin flashing TWRP) you have already tripped Knox. Knox is no big deal from what I have heard though. I have not heard of anyone getting denied a new phone because it was tripped.
Click to expand...
Click to collapse
Appreciate your reply. I was under the impression that the boatloader is already unlocked which is why we can flash a recovery without jumping through too many hoops. I know that a custom recovery trips Knox, but if there's a way to install the latest supersu through a utility such as flashfire or mobile odin, Knox won't be tripped.
I'm not really worried about warranty, just curious to see if it's possible to retain the integrity. Unfortunately both those options I mention requires the device to already be rooted which defeats what I'm trying to accomplish.
Hopefully someone will be able to figure something out in the near future.

Is it possible to use xposed with this?

So Shrek you've made the total move over?
I am holding off, althoguh i dunno for how long , because i need darker theme colors. do you know of any options?

masri1987 said:
So Shrek you've made the total move over?
I am holding off, althoguh i dunno for how long , because i need darker theme colors. do you know of any options?
Click to expand...
Click to collapse
Unless there is a feature in 5.1.1 that you MUST have, I would wait. I don't find anything to be significantly better on 5.1.1 vs. 4.4.4, but the battery life is much worse.

chodaboy19 said:
Unless there is a feature in 5.1.1 that you MUST have, I would wait. I don't find anything to be significantly better on 5.1.1 vs. 4.4.4, but the battery life is much worse.
Click to expand...
Click to collapse
Well i'm on 5.0.1 right now pop rocks, so yeah i probably will wait since there isn't a particular feature... i'm using the DOK2 modem on COD6 rom right now.

Is there a list of apps you should disable via the debloater specific to the tmobile note4?

masri1987 said:
So Shrek you've made the total move over?
I am holding off, althoguh i dunno for how long , because i need darker theme colors. do you know of any options?
Click to expand...
Click to collapse
There is no dark theme option as of right now, really it's the only thing i miss.

Will Rickards said:
Is there a list of apps you should disable via the debloater specific to the tmobile note4?
Click to expand...
Click to collapse
The list of apps on the "Debloater Script" (Option #2) thread is a great reference.

I tried everything exactly as indicated by this great guide, but I am still getting very poor battery life. I give up, I don't know what else to do.
I have googled and tried all sorts of suggestions from others with the same problem to no avail. Google Play Services and 5.1.1 have made my phone a useless POS. I guess it's time for a new phone. LOL

chodaboy19 said:
I tried everything exactly as indicated by this great guide, but I am still getting very poor battery life. I give up, I don't know what else to do.
I have googled and tried all sorts of suggestions from others with the same problem to no avail. Google Play Services and 5.1.1 have made my phone a useless POS. I guess it's time for a new phone. LOL
Click to expand...
Click to collapse
Do you ever use power saving mode? If you are in the stock kernel it can help a bunch. The phone operates just fine on it, if you are going to play a game or something you just turn it back off, but while your phone is in your pocket or laying around idle it keeps those background running Google services in check.
I'm normally getting about 6 hrs of SOT and about 24 hrs between charges. Below is where I'm at so far today. With about 2.5 hrs of SOT.

ShrekOpher said:
Do you ever use power saving mode? If you are in the stock kernel it can help a bunch. The phone operates just fine on it, if you are going to play a game or something you just turn it back off, but while your phone is in your pocket or laying around idle it keeps those background running Google services in check.
I'm normally getting about 6 hrs of SOT and about 24 hrs between charges. Below is where I'm at so far today. With about 2.5 hrs of SOT.
Click to expand...
Click to collapse
I think I found the culprit after 2 days of googling and countless wasted hours. My specific problem was that Media process was running all the time which in turn was causing Google Play Services to run at all times.
The Media process includes 2 packages: Media Storage and Download Manager. Together they perform scanning and indexing of media files on the internal SD and external SD.
I came across this page:
http://geeknizer.com/fix-android-media-server-scanner-sdcard-cpu-battery-drain/
I did step #3 which states that having more than 1,000 files in a folder makes this process crap out. I reformatted my microSD card, then I copied back all the files to the microSD. Then finally I deleted most of the pictures so that no one folder had more than 400 images.
I rebooted my phone and it started to behave normally. The Media Process only ran for 5minutes and stopped. Google Play Services ran for 2min and stopped. I have been through 1 charge already and got 5hrs or so of screen time with heavy use, I was installing apps, configuring accounts, freezing apps with Titanium backup, etc.
Overall, it seems like I have a happy ending to my story, BUT I will post a followup if the phone craps out again.
EDIT:
How do you get it to show the time on battery?
Mine doesn't have that information:

Does anyone have any interest in me adding how to set up Viper4Android on Systemless root to this thread? Just curious if I should go through the trouble.

There is a new version of SuperSU 2.64:
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
Changelog:
20.12.2015 - v2.64 - BETA
- (systemless) Detect more boot image partition names
- (systemless) Blank partitions before writing to them
- (systemless) Ask to restore boot and recovery images on full unroot
- (systemless) Implement "uninstall competing superuser apps"
- (systemless) Samsung: prevent "KERNEL IS NOT SEANDROID ENFORCING" warning
- (systemless) Cleanup system install properly if present, fixes a number of possible bootloops
- ZIP: 6.0+: Detect firmwares that can reload sepolicy from /data and use system-based root on these ("allow init kernel:security { load_policy }")
- supolicy: Additional SELinux patches for M (reduced logging only)
- Update translations

ShrekOpher said:
The list of apps on the "Debloater Script" (Option #2) thread is a great reference.
Click to expand...
Click to collapse
Link to script isn't working. ..have another?
Sent from my SM-N910T3 using Tapatalk

AlexanderBlaQ said:
Link to script isn't working. ..have another?
Sent from my SM-N910T3 using Tapatalk
Click to expand...
Click to collapse
Should be working now. Thanks for the heads up.

Root Xperia Z2 Tablet (All Models/Regions) on 5.1.1 build 23.4.B.0.319 in 3 Steps

Hello everyone,
I've noticed that there hasn't been any threads about rooting the Xperia Z2 Tablet on lollipop. Most threads have discussed how to root the device on 4.4.4 and to create an update image to maintain your root whilst updating to 5.0+.
I've scoured the interwebs and found nothing so I'll make it easy for those whom don't know how to achieve root or don't want to do much work without creating images and such.
First off I'm not responsible for any inconvenience that may come with rooting your device and losing your warranty. I can and will be willing to help out in restoring or answering questions that you may have.
This method uses Kingroot... For those who have a problem with kingroot, it is only used to achieve root and this guide will also be showing you how to remove kingroot and install Supersu with ease. Using the link below download the necessary files: Kingroot V4, Supersume, XZDualRecovery 2.8.26. Place all these files on the root of your devices internal storage/SD card excluding Xdualrecovery as that needs a PC. (If you want to Xposed working I will also supply the files needed for that as well). https://www.mediafire.com/download/wrsajbgw2jr6czt
*Make sure you have unknown sources enabled under Settings>Security>Device administrators as well as Developer Options available and USB debugging enabled. (To enable Developer Options go to Settings>About Tablet>Build Number and click it 10 times).
1. Install NewKingroot.apk and run the application. It will notify you that a root method was found and to try it. It may take up to 2 minutes to achieve root. (If all you wanted was root and are content with kinguser then you're done! :good: if you want Supersu and/or a custom recovery then continue on to step 2!
2. Connect your Tablet to your PC via microUSB. On your PC open and extract the contents of TabZ-lockeddualrecovery2.8.26-RELEASE.combined.zip to your desktop. Now double click install.bat a screen will pop up providing you with options to install xdualrecovery. Choose option 2. Installation on ROM rooted with SuperUser by pressing 2 and enter. The script will run its course and tell you to grant permission on your tablet. Open up your tablet and a kinguser prompt will show asking you to grant or deny permission to ADB (Grant it!!!) afterwards your tablet will reboot on it's own to TWRP. (I advise you to either make a backup of the tablet now or after you install Supersu as insurance in case of any mishaps). Click reboot System.
3.Install Supersume, open the application and run it. It will of course ask to grant it permission (Grant it!!!) it will check the environment (making sure that there isn't any Pokemon nearby that you don't need... Sorry Pokemon Go reference) and it will begin removing kingroot and install Supersu. If you didn't have Supersu installed already great! It'll open up Supersu automatically. Supersu may ask you to update binaries (DO NOT click TWRP as it will reboot and you have to start the process over from step one!!! :crying: Just click Normal and once it says successful you're done! :victory: The next step is optional if you Want Xposed.
*Optional 4. Install XposedInstaller_3.0_alpha4.apk. Open your app drawer and open NDR Utils. It will ask for permission (Grant it!!!) now here you may choose your preferred recovery... Philz Touch Recovery,TWRP or Clockwork Mod Recovery. Click Reboot to Primary Recovery (fourth option) once it's rebooted you want to click install>SD>xposed-v85.1-sdk22-arm-by-romracer-20160620.zip and swipe to install. You should get a success when it's finished. Now simply reboot and your apps will be upgrading. Congratulations you now have root with SuperSU and xposed! :victory:
**if you wish to uninstall Xposed simply reboot to recovery and click install>SD>xposed-uninstaller-20151218-arm.zip uninstall the application once it's rebooted and you're good to go!
***if you have a problem with Supersume not working, reinstall Newkingroot.apk and run it again to get root. Then run supersume again (Grant permission!!!) and let it run its magic.
If anyone has issues, has questions or needs help PM and I will do my best to help and answer all your questions. Please don't be discouraged because I'm new here! I will be soon adding a link to a video tutorial on how all these steps can be done!

I have the Verizon 561, will this allow rom upgrade to marshmallow?

chin_bone said:
I have the Verizon 561, will this allow rom upgrade to marshmallow?
Click to expand...
Click to collapse
Hi there, I also have SGP561 as well for Verizon. Verizon didn't release Marshmallowfor the device yet unfortunately. ???? still waiting and more then willing to confirm when it does

Just ran on my 5.1.1 z2 and work first time. Great stuff thanks!

creepingcreep said:
Just ran on my 5.1.1 z2 and work first time. Great stuff thanks!
Click to expand...
Click to collapse
Glad it worked for you. Just wanted to help people out as I had invested time trying to figure out my own. I didn't like flashing files constantly so tried making easy.

Never had luck with kingoapp and today isnt any different

Thanks so much. I am away for another week but I can not wait to try this. I got a verizon z2 tablet since it seemed to be the cheapest 10 inch tablet. You have breathed new life in to it.
Sent from my SM-G930V using XDA-Developers mobile app

Am i correct that you don't provide the kingroot.apk?
Which version are you using?

How do you boot into custom recovery from device off? Everytime I try it takes me to the stock recovery
Sent from my SGP561 using XDA-Developers mobile app

ToneLa said:
Never had luck with kingoapp and today isnt any different
Click to expand...
Click to collapse
Sorry to hear what version are you using? Use the provided KingRoot in the download link provided

Daimonion1980 said:
Am i correct that you don't provide the kingroot.apk?
Which version are you using?
Click to expand...
Click to collapse
No, in the link provided all necessary apps and folders/zips are included. Including KingRoot apk

Cammy253 said:
How do you boot into custom recovery from device off? Everytime I try it takes me to the stock recovery
Click to expand...
Click to collapse
Power off device. While device is booting up at the Sony logo hold power and volume down/up (depends on customer recovery) until led flashes green and device vibrates then let go

JediDru said:
Thanks so much. I am away for another week but I can not wait to try this. I got a verizon z2 tablet since it seemed to be the cheapest 10 inch tablet. You have breathed new life in to it.
Click to expand...
Click to collapse
That's great news to hear! I picked one up and wanted to root and I did on KitKat but when I upgraded to lollipop I lost root and rooted it the long way... Needed something simpler and couldn't find anything on here. So I wanted to make sure a guide was available to all. Enjoy and let me know how it went

reymund602 said:
Power off device. While device is booting up at the Sony logo hold power and volume down/up (depends on customer recovery) until led flashes green and device vibrates then let go
Click to expand...
Click to collapse
Thank you working great
Sent from my SGP561 using XDA-Developers mobile app

If you're talking about your google drive, there is no kingoapp.apk in there
All there is:
- supersume.apk
- tabz-lockeddualrecovery
- xposed uninstaller
- xposed v85.1
- xposed installer

I downloaded the most recent kingroot, which worked on my Verizon sgp561, and then I used your superuser file to change over to su. Seems to work just fine.. I'm on 5.1.1.

I tried the most recent kingroot and it fails.
An old version gave me an error code of 0x162982

ToneLa said:
If you're talking about your google drive, there is no kingoapp.apk in there
All there is:
- supersume.apk
- tabz-lockeddualrecovery
- xposed uninstaller
- xposed v85.1
- xposed installer
Click to expand...
Click to collapse
Let me double check and if anything I'll post a link to the apk
Sorry that you're having issues though

bilestoad said:
I downloaded the most recent kingroot, which worked on my Verizon sgp561, and then I used your superuser file to change over to su. Seems to work just fine.. I'm on 5.1.1.
Click to expand...
Click to collapse
Thanks for confirming! If you didn't see the KingRoot apk in drive I'll upload the current version!

ToneLa said:
I tried the most recent kingroot and it fails.
An old version gave me an error code of 0x162982
Click to expand...
Click to collapse
What is the software version you are having problems with?

Shortcut to being rooted on N910VVRU2CQI2

Here's my Cheat Sheet ! This is the same procedure I used a while back with N910VVRU2CPD1 . I just updated the thread to work with the newer package.
1. Odin SamMobile N910VVRU2BPA1
reboot and factory reset a few times if needed to remove custom icon
2. Odin hsbadr's N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar HERE
3. Unlock with the samsung_unlock_n4-fix PROCESS use SIM card for data. Wi-Fi will not work at this point.
4. Odin twrp-3.0.2-0-trltevzw.tar Uncheck Auto Reboot, Manually boot into TWRP
5. Odin hsbadr's N910VVRU2CPD1_StockRestore.tar HERE
6. TWRP BETA-SuperSU-v2.71-20160331103524, Factory Reset, boot system
7. Use FlashFire to Flash firmware package SamMobile N910VVRU2CQI2
( ! System and Cache only ! )
Your mileage may vary.
Before I install my personal apps I remove as much Verizon, Samsung and Google spyware as possible.
-------------------------------------------------------------------------------------------------
EDIT: I was able to skip the recommended rooting and unlocking of 5.1.1 and make the jump I described.
I did not do the unlock using Kingroot until step 3 and I did not permanent root with Super Su until step 6.
No matter how you get there the phone has to be on [Firmware] [MM] [6.0.1] [RetEd/DevEd] Safe Upgrade to Marshmallow [N910VVRU2CPD1] then you can use FlashFire.
Hyperlinks are in the text to most of what's needed.
Credit AstonsAndroid I found it HERE

I keep seeing people saying there is a way to just flash TWRP and Magisk and you're done. I'd like to avoid SuperSU and the other root methods if possible. How would that work with your updated guide? Thanks

My main concern is the spyware the guys on Reddit bring up. Not to use kingroot and the like. Was there any resolution to this thread you posted Dr cool? Want to unlock my bootloader and flash the MODest ROM but I want to be able to avoid spyware too. Thanks for your work.
https://forum.xda-developers.com/no...spyware-fix-fixed-lag-wi-fi-problems-t3433839

RootMyNote4Please said:
My main concern is the spyware the guys on Reddit bring up. Not to use kingroot and the like. Was there any resolution to this thread you posted Dr cool? Want to unlock my bootloader and flash the MODest ROM but I want to be able to avoid spyware too. Thanks for your work.
https://forum.xda-developers.com/no...spyware-fix-fixed-lag-wi-fi-problems-t3433839
Click to expand...
Click to collapse
I'm not sure if it was spyware or what. but my phone performance better after cleaning out that folder.

Thanks doc. Is that a folder that gets overwritten when you flash a new room?

This says "Continue with sim card data because wifi wont work at this point."
What if we don't have any data right now? Will it still work?

lodilovesmuffins said:
This says "Continue with sim card data because wifi wont work at this point."
What if we don't have any data right now? Will it still work?
Click to expand...
Click to collapse
Kingroot needs to connected to root. I never seen it work without a connection. N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar brakes wifi but you get it back with N910VVRU2CPD1_StockRestore.tar, I dont know why. It just works

RootMyNote4Please said:
Thanks doc. Is that a folder that gets overwritten when you flash a new room?
Click to expand...
Click to collapse
My best guess now is it's some kind of provisioning issue that is cleaned up. Some of the files deleted you may actually need some day.

does this require the developer version? btw how do i backup

I seem to lose root after I flash CPD1. Still have TWRP though and says developer mode. What could be causing this?
Edit - When I flash stock restore I mean. I get rooted on BPA/CPD and then when I go to the next step I'm losing root and Kingroot says it has no solutions. I must be doing something wrong.

RootMyNote4Please said:
I seem to lose root after I flash CPD1. Still have TWRP though and says developer mode. What could be causing this?
Edit - When I flash stock restore I mean. I get rooted on BPA/CPD and then when I go to the next step I'm losing root and Kingroot says it has no solutions. I must be doing something wrong.
Click to expand...
Click to collapse
As long as you have TWRP installed still you are in good shape. At that point, you could either flash (through TWRP) SuperSu or magisk (on certain kernels magisk install errors out in twrp). The main objective is to get the custom recovery (twrp) installed on the 6.0.1 bootloader and once that's done it's just a matter of flashing your preferred rooting method or flashing a rom that has root included.
You can use an app like this to check your bootloader to make sure it's the right one.

kevintm78 said:
As long as you have TWRP installed still you are in good shape. At that point, you could either flash (through TWRP) SuperSu or magisk (on certain kernels magisk install errors out in twrp). The main objective is to get the custom recovery (twrp) installed on the 6.0.1 bootloader and once that's done it's just a matter of flashing your preferred rooting method or flashing a rom that has root included.
You can use an app like this to check your bootloader to make sure it's the right one.
Click to expand...
Click to collapse
That's weird. I flashed SuperSU but it didn't show up in the apps and when I tried to use Flashfire it said I didn't have root.

Got there. SuperSU had an error message when I tried to install it the 1st time after flashing full system. So I rebooted and installed again. Now Flashfire crashes and won't open. Switched to Flashify and it seems to work ok.
Edit - Stuck here for now. Flashify can't seem to find the CQI2 file and I still haven't been able to get Flashfire to work. Tried an older version and still crashes when it checks to see if I have the pro version or not.

In case someone else has the same problem with Flashfire, it's because the program expired April 1st, 2018. Turn the date back on your phone and it will load.

Finally completed it!!!
Ok, so the things I learned from my trials and errors.
1) DON'T flash the kernal and SU after you root with the N4 fix. I did this the 1st 15 times and could never get Flashfire to work later on. So skip all of the stuff in that post after you flash TWRP. Then flash the next firmware step.
2) Uncheck auto time and date on your phone and roll it back to before 4/1/18 to get Flashfire to work.
I'm sure there are some more things and I'll add whatever else I think can help the next guy along. Good luck! And thanks for the guide doc!
Note: Did the phone icon on your lock screen disappear as well when you were done? The camera is there on the bottom right like normal, but the phone is gone on the bottom left and it displays the charging info there now.

Thanks for this - it was helpful to make clear that in my mind that despite what other guides say, there is no need to unlock a Lollipop bootloader with a Lollipop kernel + ROM first, and that we can boot a Lollipop kernel + ROM with a Marshmallow bootchain and unlock the Marshmallow bootloader from the get-go.
I tracked down the CQI2 full Odin and I made hybrid Odins that get you "rooted on N910VVRU2CQI2" in fewer steps, following hsbadr's file naming scheme:
N910VVRU2BPA1_N910VVRU2CQI2_FullFirmware.tar.md5: MM CQI2 bootchain/firmware/modem, LL BPA1 ROM/kernel/recovery
N910VVRU2CQI2_StockRestore.tar: MM CQI2 ROM/kernel (no recovery - TWRP isn't overwritten)
These should be fine as drop-in replacements for the files mentioned in steps 2 and 5 of your guide.
Using these obviously means that you are unlocking the CQI2 aboot instead of the CPD1 aboot in step 3 while temprooted, and - importantly - step 7 is unnecessary to get to a CQI2 ROM, which is good because Flashfire is now expired :3
I doubt there's much of a real benefit to being on the newer aboot, but hey, why not.

Hey, no one answered my question from a while ago. So I'll ask again, does this require the developer version of the Note 4?

lodilovesmuffins said:
Hey, no one answered my question from a while ago. So I'll ask again, does this require the developer version of the Note 4?
Click to expand...
Click to collapse
No, this will work with both versions of the verizon note 4.

kevintm78 said:
No, this will work with both versions of the verizon note 4.
Click to expand...
Click to collapse
Ok, thank you very much. I'll try and root my phone with this tutorial now.

Please help!!!!
I followed this link because its supposed to be a way to downgrade from 6.1.0 to 5.1.1 so I can unlock boot loader. However, these instructions make no sense to me. Can someone PLEASE help me. I've been searching and searching for a way to root my note 4 (N910VVRS2CQA1) and can't seem to find a way. I've never done this before so I'm pretty clueless. When I read these instructions, I just don't understand what I'm supposed to be doing. A lot of this tech lingo means nothing to me unfortunately. I'm starting to thing I should just give up the idea of rooting this Note 4 that's getting slower and slower and just get a new one. I don't really want to though bc I love the fact that you can replace the battery. It'd be much easier to just root and upgrade.....well, easier if I actually knew how.