Develop Bugs

[Q] GT-N5120 Removal of Superuser and SU from Unrooted Tablet

Hello,
I am new to rooting of Android and I needed some advice on how to remove superuser from the system app and su from xbin.
I have a GT-N5120 on ver. 4.1.2, and I rooted it using Flamaroot. It was working fine and when ver. 4.2.2 was available I forgot to unroot my tablet and went ahead with the software update. After the update, my tablet became unrooted and I am stuck with the superuser and su file.
Tried to use flamaroot again to root the tablet but it doesn't display the same options during the first rooting, thus unable to root it. Uninstalled superuser app but file is still inside the system folder. Tried deleting the files but message shows files cannot be deleted.
How can I recover to stock version Currently tablet is showing ver. 4.2.2, Kernel version : 3.0.31-1210063, [email protected] #1.
Desperately needed help because S-pen could not detect some of the alphabets in the keyboard and wanted to send back to Samsung for repair.
Thanks in advance.

Unrooting
First, Framaroot doesn't work on 4.2.2, Samsung patched those exploits.
1) Root by CF-Auto-Root. It will install SuperSU, which is better than Superuser, IMO.
2) Reset the flash counter by Triangle Away. Otherwise Samsung will not allow you to claim the warranty.
3) Boot to the system (I assume you are on stock kernel and recovery). Fully unroot using the option in the SuperSU.
4) Go to the recovery (first Power off, and then press Vol Up + Power, release the buttons when the boot screen appear). Do a full wipe (factory & cache). Power off.
5) Go to download mode and check whether the counter reset to "0", and also system status as "official".
6) Now flash the latest firmware. Device is ready to claim warranty.
After these, check whether the S-Pen issue solved or not.

Thank you AkiOrpheus.
I will run through the links to try to understand the process on the steps you have given.
Will probably need more help to understand some of the details later and will post those questions as needed.
Thanks again.

Hi Aki,
I followed the instructions and went through the CF-Auto-Root (steps very clearly explained by Chainfire) and now my GT-N5120 is rooted and also apparently, the S-pen problem is also resolved.
Looks like I do not have to sent in to Samsung for warranty claim for now. I also did not do the Triangle Away and left my Note 8 rooted. :laugh::angel::good:
Thank you again Aki and Chainfire. You guys are great!!!!!

Good news
Good to hear problem solved. Yes, it's better to use Triangle Away only when going to pay a visit to Samsung service. Can you kindly add "[SOLVED]" before the thread title?
BTW, when come to Android Chainfire is far great

[Solved] GT-N5120 Removal of Superuser and SU from Unrooted Tablet
Problem solved.

"thread title" not the "post title"
Oh no! What I meant was like this, add "[SOLVED]" in front of the thread title not the post title. That way it's easy when someone with the similar problem searched for a solution.

SGH-T889 Rooting & Wifi Tether For Newbies on JB 4.3

After many tries of failure from ROM flashing, reprogramming and trying to understand the alien language to me, I finally figured out how to get wifi tether working for your galaxy note 2. There are links in this thread and make sure that you follow the instruction I have for you here as well.
*** Disclosure ***
I am not an expert or a someone who can give you an advice. Directions hereafter are what worked for me and I am only sharing how I got it worked. However, it is not a definite way to get wifi tether working for T-Mobile Samsung Galaxy Note 2 (SGH-T889). Please do this for US model only.
This direction is for people who have never done rooting and programming phones, and upgraded to JB 4.3 via OTA with KNOX enabled bootloader. By the end of this direction, your GN2 will be rooted on T-Mobile stock ROM with wifi tether enabled. Please be aware that this direction will void your phone's warranty by tripping KNOX counter. So do this at your own will. Also, back up your most recent ROM and personal files just in case.
So, enough disclosure.....and here it is.
(For this part of instruction, I would like to give a big thanks to mrRobinson for providing pre-rooted stock T-Mobile ROM.)
1. Download ODIN (version does not matter, but 3.07 or 3.09 should work fine)
2. Find Tmobile ROM and download JellyBean Release 4.3 (December 2013) from this link http://forum.xda-developers.com/showthread.php?t=1975560
3. Unzip downloaded ROM in your PC and run ODIN (Leave Auto Reboot and F. Reset Time checked in ODIN)
4. Find and click PDA or AP in ODIN and load downloaded ROM (root66_TMO_T889UVUCMK7_2.tar.md5)
5. Turn T889 off, then put the phone to download mode by pressing and holding Volume Down, Home and Power. Then plug USB cable to the phone
6. Click START to flash your phone
Once the phone reboots, your phone will be rooted. Easy so far, right?
Now the next step...
(For this part of instruction, I would like to give a big thanks to mattlowry.)
1. Visit this thread http://forum.xda-developers.com/showthread.php?t=2564430 and download 2 files: Version 2.1 of SWARM ROM (Look for Download(v2.1)) and WifiTethering.zip (Look for a mediafire link on Version 2.1)
2. Copy these files on your phone's SD Card
3. Turn T889 off, then enter into recovery mode by pressing and holding Volume Up, Home and Power. If the recovery mode says Android System Recovery 3e on top and does not have "advanced" menu, reboot your phone and go to Play Store. Download ROM Manager by ClockworkMod. Run Rom Manager and choose Recovery Setup. Under the Recovery Setup, install or update recovery "ClockworkMod Recovery". After this install/update, turn your phone off and enter into recovery mode.
4. In the recovery mode, select "wipe data/factory reset", then select "wipe cache partition", then select "advanced", then select "wipe dalvik cache." Once you are done this far, select "Go Back", then select "install zip." Under install zip menu, select "Choose zip from /storage/sdcard1". (There will be about 15 to 20 second delay until the next menu.) Find the SWARM ROM zip file and flash the phone's ROM.
5. After flashing the phone with SWARM ROM, go back to install zip menu and find WifiTethering.zip, then flash your phone.
A bit painful, but you've done great!...but we are not done yet.
Now, do not panic if your Wifi does not work after this step. There is a fix.
(For this part of instruction, I would like to give a big thanks to dr.ketan.)
1. Visit this link http://forum.xda-developers.com/showthread.php?p=48468121&highlight=mattlowry#post48468121
2. Download "Wifi_patch_t889.tar.rar" and extract the file in your PC.
3. Run ODIN and click on PDA or AP, then load the file "Wifi_patch_t889.tar.md5".
4. Press START and wait until your phone reboot.
Now your Wifi patch is done, but your wifi won't work until you do the following.
(For this part of instruction, I would like to give a big thanks to DerTeufel1980 for Devil Kernel.)
1. Visit this link http://forum.xda-developers.com/showthread.php?t=2239453
2. Very bottom of this thread there are files for download. Download "Devil2-2.3.2-t0lte-DUAL-20140102.zip" and save it in your phone's SD card. Make sure the file name as others will get you stuck in booting. If you download wrong kernel, you have to restart the whole process from the very top of this instruction.
3. Turn your phone off and enter into recovery mode again. Select "install zip", find the "Devil2-2.3.2-t0lte-DUAL-20140102.zip" file, then flash your phone.
4. One the flash is done, reboot your phone.
By now, your phone is rooted with Devil Kernel. All functions should work fine.
Now the wifi tether...
1. Go to Play Store and search wifi tether.
2. From the list of apps, find Wifi Tether: Network Sharing by Topapploft.
3. Do not install this app and look for a link under Description for 10.1.0 version.
4. Download the app from this link and install this app (phone will ask for installation permission for unknown source app.)
5. After the installation, run the app and go to the settings.
Change Device-Profile: Choose Generic ICS/JB (wlan0)
Change Setup-Method: Choose Netd-Ndc (master)
Send Netd Max Client Cmd: checked
Send No Tether-Interface Cmd: checked
WiFi-driver reload 2: checked
MSS clamping: checked by default
Routing fix: checked by default
You are done!
On a side note, do not use wifi tether trevemod. It has same functions as the above app, but for some reason it forcefully reboots your phone and tethering do not work.
Also, do not use Wifi Tether Router as this app will cause blackout of your phone screen on some cases. I purchased this app and regret it.
One more thing, I have not tried skipping SWARM ROM flashing. So if anyone tried, please comment it for other people.
Thanks for reading this long instruction and hope your phone works as mine.

Love the idea.
In the first bit, skip mrRobinson's rom. Start with Odin installing a custom recovery such as TWRP. Then odin the wifi patch if you are not on the Knox bootloader and don't plan on using Devil Kernel or Agni. Then pull a nandroid backup.
Complete wipe.
Install the 4.3 rom of your choice. I like Jedi Master X, wifi tether is already configured of you stick with mobile devices (tablets etc). Follow instructions on install.
If you are on another rom, go ahead and follow your instructions.
Thanks for helping the community.
Hastily spouted for your befuddlement

Coug76 said:
Love the idea.
In the first bit, skip mrRobinson's rom. Start with Odin installing a custom recovery such as TWRP. Then odin the wifi patch if you are not on the Knox bootloader and don't plan on using Devil Kernel or Agni. Then pull a nandroid backup.
Complete wipe.
Install the 4.3 rom of your choice. I like Jedi Master X, wifi tether is already configured of you stick with mobile devices (tablets etc). Follow instructions on install.
If you are on another rom, go ahead and follow your instructions.
Thanks for helping the community.
Hastily spouted for your befuddlement
Click to expand...
Click to collapse
Thank you for your input and comment.

You shouldn't need both the WiFi patch and devil kernel for WiFi to work. Its 1 or the other. But nice thread!
Sent from my SGH-T889 using Tapatalk 4

mattlowry said:
You shouldn't need both the WiFi patch and devil kernel for WiFi to work. Its 1 or the other. But nice thread!
Sent from my SGH-T889 using Tapatalk 4
Click to expand...
Click to collapse
Thank you for your input.
I've tried WiFi patch first, but it did not work. So, I had to use devil kernel for both WiFi and tethering to work. I put both instruction just to make sure they work.

I can confirm that just using the patch does not give you wifi back on stock, rooted MK7. However, I much prefer the stock kernel to Devil Kernel in terms of smoothness.
Any idea on how to undo the WifiTethering.zip changes without having to redo the entire phone?

drdoombot said:
I can confirm that just using the patch does not give you wifi back on stock, rooted MK7. However, I much prefer the stock kernel to Devil Kernel in terms of smoothness.
Any idea on how to undo the WifiTethering.zip changes without having to redo the entire phone?
Click to expand...
Click to collapse
Flash your ROM over your present install. Should paint over the tethering changes.
Hastily spouted for your befuddlement

Thanks!!
First I want to thank you for this thread!! Since upgrading to Android 4.3 I have not been successful in getting wifi tethering to work. Prior to 4.3, trev-mod was working perfectly fine but after the update nothing seem to work except bluetooth tethering with Fox-Fi along with PDANet+ and many apps didn't work with that method.
Also I'd just like to add that I hardly ever tether at all... it's just nice to know when you are in a bind you have some sort of solution.
I'm currently on the 4.1.2 bootloader because I didn't want to have to deal with knox. Even though my warranty has already expired, for some reason I still do not want to upgrade to the new one. The wifi patch was giving me all sorts of freezes and random reboots so I decided to go back to the original bootloader, after reading EdKey's Conch Replubic thread. His ROM was very stable for me, however I recently acquired the Gear 2 and unfortunately not all was working correctly since it is heavily debloated. I'm currently using SWARM 2.1 with AGNI Kernel. Was using Devil before but battery drain appears to be very high with this ROM so I'm giving Agni a go for a couple of days. Since I am on the old bootloader, the only way to get wifi to work properly is either using Devil or Agni kernel unless there is another one out there that I'm unaware of at this time.
Anyway... I digress. My experience so far is this, when I initially start the tethering process, none of my devices see an access point until I stop tethering and start it again for a second time. Then I'm able to see the AndroidTether access point. I can connect and tether even without any sort of vpn or browser ID spoofer. I'd still recommend using a VPN anyway, just in case the operator starts packet sniffing. Who knows, maybe Trev Mod was working, I don't recall trying to re-enable tethering for a second time when I didn't see any access points so I just kind of gave up and stumbled across this thread
However, when I stop the tethering, I'm not able to reconnect to my normal home wifi until I toggle on/off the Mobile HotSpot option in the Rom. My wifi icon is enabled, but for some reason does not connect to my router until I toggle it on and then off again. This is still a better work around than having to reboot the phone each time to get my wifi to reconnect. It might have something to do with my current bootloader, but I'm not sure. I guess it will be back to the drawing board after KitKat comes out. Hopefully this will remain working for awhile...
So I just wanted to share my experience and thank you again for this thread.

Just so you know you can install jedi master rom x2. And follow my guide. It's a lot easier than doing all of this. Here's the link. http://zuck.com/xda/JediMasterX-FAQ.html#teather
Sent from my SM-G900T using XDA Premium 4 mobile app

hotspot working on t-mobile galaxy note 2 running 4.3 Jellybean
jinimini1026 said:
After many tries of failure from ROM flashing, reprogramming and trying to understand the alien language to me, I finally figured out how to get wifi tether working for your galaxy note 2. There are links in this thread and make sure that you follow the instruction I have for you here as well.
*** Disclosure ***
I am not an expert or a someone who can give you an advice. Directions hereafter are what worked for me and I am only sharing how I got it worked. However, it is not a definite way to get wifi tether working for T-Mobile Samsung Galaxy Note 2 (SGH-T889). Please do this for US model only.
This direction is for people who have never done rooting and programming phones, and upgraded to JB 4.3 via OTA with KNOX enabled bootloader. By the end of this direction, your GN2 will be rooted on T-Mobile stock ROM with wifi tether enabled. Please be aware that this direction will void your phone's warranty by tripping KNOX counter. So do this at your own will. Also, back up your most recent ROM and personal files just in case.
So, enough disclosure.....and here it is.
thering-menu/
(For this part of instruction, I would like to give a big thanks to mrRobinson for providing pre-rooted stock T-Mobile ROM.)
1. Download ODIN (version does not matter, but 3.07 or 3.09 should work fine)
2. Find Tmobile ROM and download JellyBean Release 4.3 (December 2013) from this link http://forum.xda-developers.com/showthread.php?t=1975560
3. Unzip downloaded ROM in your PC and run ODIN (Leave Auto Reboot and F. Reset Time checked in ODIN)
4. Find and click PDA or AP in ODIN and load downloaded ROM (root66_TMO_T889UVUCMK7_2.tar.md5)
5. Turn T889 off, then put the phone to download mode by pressing and holding Volume Down, Home and Power. Then plug USB cable to the phone
6. Click START to flash your phone
Once the phone reboots, your phone will be rooted. Easy so far, right?
Now the next step...
(For this part of instruction, I would like to give a big thanks to mattlowry.)
1. Visit this thread http://forum.xda-developers.com/showthread.php?t=2564430 and download 2 files: Version 2.1 of SWARM ROM (Look for Download(v2.1)) and WifiTethering.zip (Look for a mediafire link on Version 2.1)
2. Copy these files on your phone's SD Card
3. Turn T889 off, then enter into recovery mode by pressing and holding Volume Up, Home and Power. If the recovery mode says Android System Recovery 3e on top and does not have "advanced" menu, reboot your phone and go to Play Store. Download ROM Manager by ClockworkMod. Run Rom Manager and choose Recovery Setup. Under the Recovery Setup, install or update recovery "ClockworkMod Recovery". After this install/update, turn your phone off and enter into recovery mode.
4. In the recovery mode, select "wipe data/factory reset", then select "wipe cache partition", then select "advanced", then select "wipe dalvik cache." Once you are done this far, select "Go Back", then select "install zip." Under install zip menu, select "Choose zip from /storage/sdcard1". (There will be about 15 to 20 second delay until the next menu.) Find the SWARM ROM zip file and flash the phone's ROM.
5. After flashing the phone with SWARM ROM, go back to install zip menu and find WifiTethering.zip, then flash your phone.
A bit painful, but you've done great!...but we are not done yet.
Now, do not panic if your Wifi does not work after this step. There is a fix.
(For this part of instruction, I would like to give a big thanks to dr.ketan.)
1. Visit this link http://forum.xda-developers.com/showthread.php?p=48468121&highlight=mattlowry#post48468121
2. Download "Wifi_patch_t889.tar.rar" and extract the file in your PC.
3. Run ODIN and click on PDA or AP, then load the file "Wifi_patch_t889.tar.md5".
4. Press START and wait until your phone reboot.
Now your Wifi patch is done, but your wifi won't work until you do the following.
(For this part of instruction, I would like to give a big thanks to DerTeufel1980 for Devil Kernel.)
1. Visit this link http://forum.xda-developers.com/showthread.php?t=2239453
2. Very bottom of this thread there are files for download. Download "Devil2-2.3.2-t0lte-DUAL-20140102.zip" and save it in your phone's SD card. Make sure the file name as others will get you stuck in booting. If you download wrong kernel, you have to restart the whole process from the very top of this instruction.
3. Turn your phone off and enter into recovery mode again. Select "install zip", find the "Devil2-2.3.2-t0lte-DUAL-20140102.zip" file, then flash your phone.
4. One the flash is done, reboot your phone.
By now, your phone is rooted with Devil Kernel. All functions should work fine.
Now the wifi tether...
1. Go to Play Store and search wifi tether.
2. From the list of apps, find Wifi Tether: Network Sharing by Topapploft.
3. Do not install this app and look for a link under Description for 10.1.0 version.
4. Download the app from this link and install this app (phone will ask for installation permission for unknown source app.)
5. After the installation, run the app and go to the settings.
Change Device-Profile: Choose Generic ICS/JB (wlan0)
Change Setup-Method: Choose Netd-Ndc (master)
Send Netd Max Client Cmd: checked
Send No Tether-Interface Cmd: checked
WiFi-driver reload 2: checked
MSS clamping: checked by default
Routing fix: checked by default
You are done!
On a side note, do not use wifi tether trevemod. It has same functions as the above app, but for some reason it forcefully reboots your phone and tethering do not work.
Also, do not use Wifi Tether Router as this app will cause blackout of your phone screen on some cases. I purchased this app and regret it.
One more thing, I have not tried skipping SWARM ROM flashing. So if anyone tried, please comment it for other people.
Thanks for reading this long instruction and hope your phone works as mine.
Click to expand...
Click to collapse
Want to get hotspot working on t-mobile SGH T-889??Follw the link below or just download (hotspot control) from google play/market and enable ACESS POINT.And you can turn hotspot from your phone's setting the normal way,without root and without downloading any other tethering apps.
http://www.androidpolice.com/2013/0...harnesses-the-latent-power-of-your-devices-te

Help samsung galaxy note ii t889 root access
Greetings to the entire community, I'm new here and I wanted to ask for some help on this problem that I have and maybe others have too.
I have a note II t889 which I've rooted, SuperSU appears installed on the phone, when I open any application that requires root it asks me permission, I click accept and it tells me I have been granted permissions, but when I try to use the application tells me that the root has failed, or that need root access to use the application.
Note: I have already tried this several rooting using odin and corresponding files (CF-Root-Auto for note II t889, root66_TMO_T889UVUCMK7_2.tar.md5, and others, and the result is the same, according to the rooteado odin has been done successfully)
Another thing I have android 4.3 version and I already delete knox using root browser (it asked me root access to use it and it worked to remove the data relating to knox)
Thanks

Found solution
Ok anybody outthere doing this it took me a couple of hours but I couldn't find Wi-Fi tether by Topapploft, no longer in the play store, thankfully I found something that worked, first go to play store and get network share & wifi tether by joliejoy, then it's going to ask you to download newest one, wifi tether plus, file name: AndroidWifiTether_10.1.10.apk, follow the instruction above, EXCEPT the device should be GALAXY S4!! It worked for me

My note 2 is unrooted but wifi tether works fine.

★ |[How-To]| | ROOT NK3 | KEEP KNOX 0x0 | The EffortLess Way | Rooting | 26NOV14 ★

★ |[How-To]| | ROOT NK3 | KEEP KNOX 0x0 | The EffortLess Way | Rooting | 26NOV14 ★
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
If you do not care about KNOX and want a custom recovery or custom ROM installed in addition to root- Go to my other thread here! A custom ROM or custom recovery WILL trip your KNOX to 0x1 (this is irreversible and KNOX will cease to function on your phone forever and ever and ever) :crying:
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
************************************************** ************************************************** ************************************************** ************************************************** **************************************************
Welcome to ROOT with KNOX 0x0 the EffortLess Way!!​This is a quick and easy way to root the N900T T-Mobile Note 3 with the full stock N900TUVUENK3 update installed!​
This guide will assist you in rooting full stock N900TUVUENK3 without tripping KNOX (preserving 0x0)
************************************************** ************************************************** ************************************************** ************************************************** **************************************************​NOTE: You will need to be updated to the full stock N900TUVUENK3 firmware before proceeding!
If you need to update to N900TUVUENK3 and are on a stock firmware that has not been rooted yet:
Use the built-in Over The Air (OTA) software updater in your phone settings to check for an update then follow the instructions to update.
After booting up, check for an update again and confirm there are none and that you are on firmware N900TUVUENK3 before proceeding to the "EffortLess Rooting Guide" below.
If you are updating from any prior rooted stock firmware (basically, you've used this guide before but need to update) you will need to follow these steps:
Download EffortLess ROM Prep.zip and Full Stock NK3.zip
Unzip both files
Turn off your phone and then hold the Volume Down, Home Button, and Power Button at the same time, when the phone vibrates, let go of Power Button. Press Volume Up to continue past the "Warning!!" screen.
Open the EffortLess ROM Prep folder and double click on EffortLess Odin.exe
Connect your phone to the computer via USB cable (one of the boxes under ID:COM in Odin will fill with a com number and turn baby blue meaning it can communicate with your phone.. if it does not, unplug your phone and run EffortLess Odin USB Driver.exe from the EffortLess ROM Prep unzipped folder. Now plug your phone in again and it should load the driver and the box should turn baby blue and display a com number)
Click the PDA button and navigate to the unzipped Full Stock NK3 folder, click on N900TUVUENK3_N900TTMBENK3_N900TUVUENK3_HOME.tar.md5 and click Open
Wait for the file to load properly in Odin, it will take a minute and you'll see a check-mark to the left of the PDA button and the system path of the NK3 file to the right.
Now click start and wait, don't touch anything until after your phone restarts.
Now go to menu, settings, General tab, and click About device and verify the Baseband version AND Build Number are N900TUVUENK3
************************************************** ************************************************** ************************************************** ************************************************** **************************************************​EffortLess Rooting Guide
This method will revert the kernel back to the Samsung stock NE6 kernel (that is vulnerable to the towelroot method). Then you will use towelroot to root. Finally, you will flash back the NK3 kernel and enjoy root on your stock NF3 phone!
This process should take approximately 5 minutes and will not erase any files on your phone.
First download and install towelroot on your phone]:
Navigate to towelroot on your phone (once at the site, click the main center logo) and install the downloaded app (do not open the app and click make it ra1n yet).
Then download EffortLessRootPrep.zip on your Windows computer and unzip it.
Flashing NE6 Kernel
Turn off your phone and then hold the Volume Down, Home Button, and Power Button at the same time, when the phone vibrates, let go of Power Button. Press Volume Up to continue past the "Warning!!" screen.
Open the EffortLess Root Prep folder and double click on EffortLess Odin.exe
Connect your phone to the computer via USB cable (one of the boxes under ID:COM in Odin will fill with a com number and turn baby blue meaning it can communicate with your phone.. if it does not, unplug your phone and run EffortLess Odin USB Driver.exe from the EffortLess Root Prep unzipped folder. Now plug your phone in again and it should load the driver and the box should turn baby blue and display a com number)
Click the PDA button and navigate to the unzipped EffortLess Root Prep folder, click on N900TUVUDNE6_KERNEL.tar.md5 and click Open
Wait for the file to load properly in Odin, it will take a minute and you'll see a check-mark to the left of the PDA button and the system path of the root file to the right.
Now click start and wait, don't touch anything until after your phone restarts.
Running towelroot
Once your phone boots up, open the towelroot app and click "make it ra1n".
Wait ten seconds and then reboot your phone. (I know it says reboot is not required, do it anyway)
Open SuperSU (if it's not in your app drawer, download it from the play store) and if it asks to update the binary, choose the normal method. (if it says installation failed, just try again or try again after you flash back to NK3, it's normal and it'll be updated)
When it mentions disabling KNOX, click ok (this will not trip KNOX, it will simply disable it for the time being.. If you want to use KNOX while rooted, don't disable it in SuperSU). NOTE: if it hangs disabling KNOX don't worry. Turn off your phone and proceed to the next step. After flashing the NK3 Kernel back, open SuperSU and disable KNOX and it should work within a few seconds.
Flashing NK3 Kernel back
Turn off your phone and then hold the Volume Down, Home Button, and Power Button at the same time, when the phone vibrates, let go of Power Button. Press Volume Up to continue past the "Warning!!" screen.
Open the EffortLess Root Prep folder and double click on EffortLess Odin.exe
Connect your phone to the computer via USB cable (one of the boxes under ID:COM in Odin will fill with a com number and turn baby blue meaning it can communicate with your phone.. if it does not, unplug your phone and run EffortLess Odin USB Driver.exe from the EffortLess Root Prep unzipped folder. Now plug your phone in again and it should load the driver and the box should turn baby blue and display a com number)
Click the PDA button and navigate to the unzipped EffortLess Root Prep folder, click on N900TUVUENK3_KERNEL.tar.md5 and click Open
Wait for the file to load properly in Odin, it will take a minute and you'll see a check-mark to the left of the PDA button and the system path of the root file to the right.
Now click start and wait, don't touch anything until after your phone restarts.
You can uninstall the towelroot app after you're are finished.
If this helped, please click the "Thanks" button! :good:
| Let me know you like it :highfive: Donate to show your support |
Thanks to:
@geohot for making towelroot
and special thanks @toastito for getting me the stock Odin flashable kernels!

This worked for me! Followed your steps and I now have root with Knox counter 0x0. Thank you for the guide! The only issue I had was while updating the Super SU binaries I received an "installation failed" message after updating and disabling knox, but after flashing back to the NF4 kernel I had root and Super SU works fine. You might want to add something to the guide so people know this is normal. :good:

_bhaves_ said:
This worked for me! Followed your steps and I now have root with Knox counter 0x0. Thank you for the guide! The only issue I had was while updating the Super SU binaries I received an "installation failed" message after updating and disabling knox, but after flashing back to the NF4 kernel I had root and Super SU works fine. You might want to add something to the guide so people know this is normal. :good:
Click to expand...
Click to collapse
Thanks for the feedback _bhaves_! I'll be adjusting the guide as I get more feedback. I was only able to test this twice as my phone is already KNOX 0x1 and I had limited time with the KNOX 0x0 phone. I concentrated on ensuring KNOX would stay 0x0 during my testing. I had different results than you regarding installing the binaries. Now I feel that running SuperSU and updating it and disabling KNOX should be done after flashing back to NF4 kernel. I feel the reboot clears stuff up and enables SuperSU to function more fluidly. I'll change it to that and await further feedback.

Thanks for the guide! I was on NF1 and used your guides to successfully go to NF4 with no issues and still have not tripped KNOX...thank you good sir.

effortless said:
************************************************** ************************************************** ************************************************** ************************************************** **************************************************
Welcome to ROOT with KNOX 0x0 the EffortLess Way!!​This is a quick and easy way to root the N900T T-Mobile Note 3 with the full stock NF4 update installed!
This guide will assist you in rooting NF4 without tripping KNOX (preserving 0x0)​
Only proceed with this guide if you want root and do not want a custom recovery or custom ROM installed!
NOTE: You will need to be updated to the full stock NF4 ROM before proceeding!
If you need to update to NF4, use the EffortLess Guide and stop after the "For full N900TUVUDNF4 stock:" section, steps 1-8. (DO NOT proceed to root or flash a custom recovery in that thread) then come back here.
This method will revert the kernel back to the Samsung stock NE6 kernel (that is vulnerable to the towelroot method). Then you will use towelroot to root. Finally, you will flash back the NF4 kernel and enjoy root on your stock NF4 phone!
This process should take approximately 5 minutes and will not erase any files on your phone.
************************************************** ************************************************** ************************************************** ************************************************** **************************************************
First download towelroot (once at the site, click the main center logo) on your phone and install the app (do not click make it ra1n yet).
Then download EffortLessRootPrep.zip on your Windows computer and unzip it.
Rooting NF4 (Flashing NE6 Kernel)
Turn off your phone and then hold the Volume Down, Home Button, and Power Button at the same time, when the phone vibrates, let go of Power Button. Press Volume Up to continue past the "Warning!!" screen.
Open the EffortLess Root Prep folder and double click on EffortLess Odin.exe
Connect your phone to the computer via USB cable (one of the boxes under ID:COM in Odin will fill with a com number and turn baby blue meaning it can communicate with your phone.. if it does not, unplug your phone and run EffortLess Odin USB Driver.exe from the EffortLess Root Prep unzipped folder. Now plug your phone in again and it should load the driver and the box should turn baby blue and display a com number)
Click the PDA button and navigate to the unzipped EffortLess Root Prep folder, click on N900TUVUDNE6_KERNEL.tar.md5 and click Open
Wait for the file to load properly in Odin, it will take a minute and you'll see a check-mark to the left of the PDA button and the system path of the root file to the right.
Now click start and wait, don't touch anything until after your phone restarts.
Rooting NF4 (Running towelroot)
Once your phone boots up, open the towelroot app and click "make it ra1n".
Wait ten seconds and then reboot your phone. (I know it says reboot is not required, do it anyway)
Open SuperSU (if it's not in your app drawer, download it from the play store) and if it asks to update the binary, choose the normal method. (if it says installation failed, just try again or try again after you flash back to NF4, it's normal and it'll be updated)
When it mentions disabling KNOX, click ok (this will not trip KNOX, it will simply disable it for the time being.. If you want to use KNOX while rooted, don't disable it in SuperSU). NOTE: if it hangs disabling KNOX don't worry. Turn off your phone and proceed to the next step. After flashing the NF4 Kernel back, open SuperSU and disable KNOX and it should work within a few seconds.
Rooting NF4 (Flashing NF4 Kernel back)
Turn off your phone and then hold the Volume Down, Home Button, and Power Button at the same time, when the phone vibrates, let go of Power Button. Press Volume Up to continue past the "Warning!!" screen.
Open the EffortLess Root Prep folder and double click on EffortLess Odin.exe
Connect your phone to the computer via USB cable (one of the boxes under ID:COM in Odin will fill with a com number and turn baby blue meaning it can communicate with your phone.. if it does not, unplug your phone and run EffortLess Odin USB Driver.exe from the EffortLess Root Prep unzipped folder. Now plug your phone in again and it should load the driver and the box should turn baby blue and display a com number)
Click the PDA button and navigate to the unzipped EffortLess Root Prep folder, click on N900TUVUDNF4_KERNEL.tar.md5 and click Open
Wait for the file to load properly in Odin, it will take a minute and you'll see a check-mark to the left of the PDA button and the system path of the root file to the right.
Now click start and wait, don't touch anything until after your phone restarts.
You can uninstall the towelroot app after you're are finished.
If this helped, please click the "Thanks" button! :good:
| Let me know you like it :highfive: Donate to show your support |
Thanks to:
@geohot for making towelroot
and special thanks @toastito for getting me the stock Odin flashable kernels at short notice while I was away from my workstation!
Click to expand...
Click to collapse
I really wish this had came out when started rooting my Note. I had to send my phone out to Samsung and had to pay to have it fixed

N900TUVUDNE6_KERNEL.tar.md5 is not present in the folder. Only a CF root file is there and a recovery file.
Towelroot states the device isn't supported.
Knox Warranty Void 0x1

conchchowder said:
N900TUVUDNE6_KERNEL.tar.md5 is not present in the folder. Only a CF root file is there and a recovery file.
Towelroot states the device isn't supported.
Click to expand...
Click to collapse
You're mixing my how-to threads and files. You didn't download the EffortLessRootPrep file... you downloaded the EffortLess ROM Prep.zip which is used to install a custom recovery and custom rom (both of which will trip your KNOX if flashed).
Also, the whole purpose of this thread is to downgrade to the NE6 kernel which supports towelroot (before running it). I specifically mention not to run it (until after you downgrade to the NE6 kernel), because it's not compatible with NF4.

[emoji15]
Sent from my SM-N900T using Tapatalk

worked perfectly for me !!!

I would like to thank OP and other developers for all their efforts, it worked like a charm.
But I do have a quick question: I stayed on 4.3 until now due to SD card access being broken and fix requiring root access, that trip Knox.
Of course this solution solved Knox worry and therefore I went ahead updating, however I don't seem to have any SD card issues yet, even before I applied the fix. I just would like to know why?
1. Is it because Google or Samsung fix it in later release?
2. Is it because all the apps I use were already updated?
3. is it because ROMs were somehow fixed either by rooting, or by the people posting the ROM.
Or maybe it's not fixed? When I use ES explorer, I see the folders, but many appear empty, like titanium backup for example.
Now this would be the most stupid thing, if all those folders showing empty weren't, since I always delete empty folders as a rule.
So are SD Card access restrictions fixed in NF4 or not and if not which fix is working well, since I came across some posts that claim broken BT, after applying the fix.
TIA

pete4k said:
I would like to thank OP and other developers for all their efforts, it worked like a charm.
But I do have a quick question: I stayed on 4.3 until now due to SD card access being broken and fix requiring root access, that trip Knox.
Of course this solution solved Knox worry and therefore I went ahead updating, however I don't seem to have any SD card issues yet, even before I applied the fix. I just would like to know why?
1. Is it because Google or Samsung fix it in later release?
2. Is it because all the apps I use were already updated?
3. is it because ROMs were somehow fixed either by rooting, or by the people posting the ROM.
Or maybe it's not fixed? When I use ES explorer, I see the folders, but many appear empty, like titanium backup for example.
Now this would be the most stupid thing, if all those folders showing empty weren't, since I always delete empty folders as a rule.
So are SD Card access restrictions fixed in NF4 or not and if not which fix is working well, since I came across some posts that claim broken BT, after applying the fix.
TIA
Click to expand...
Click to collapse
This is a copy and paste of a previous statement I've made about this topic:
A lot of people are very confused on the SD card changes. YOU DO NOT LOSE SD CARD access! The change was that if an app created a folder on your SD card to store stuff, another app cannot access and make changes to it (Which is how it should have been from the beginning). There are many reasons as to why this is the better way (many security related as well as programming related scenarios).
This means that each app can create and write changes to SD card folders it creates and no other folder. The app has to be the creator of the folder it's making changes to.. that makes sense right?! You can still put all the music and pictures and documents you want on the SD card and they will still work like in the past. A few apps had to be updated because they were doing things the old way, but that's been done and you shouldn't have any issues that people had when the change first was done.
4.4 adds a host of new features, bug fixes, network efficiency enhancements and security patches (some are very serious and if you're still on 4.3, your phone is at risk daily). I highly suggest everyone upgrade. If you have any particular issue, private message me and I will help you address it!
To address your current questions though, the change wasn't something that was broken by Google. It shouldn't have been called an SD Card Fix either (like I said, it didn't break), but there were changes in the way Android Apps interacted with the SD card. You can still do this SD Card Fix manually or just use an app in the play store to make the changes for you. There are still certain situations where the "SD Card Fix" is useful, but if it's working for you, then leave it the way it is. Most problems initially were due to needing updates for apps at the time.

effortless said:
This is a copy and paste of a previous statement I've made about this topic:
A lot of people are very confused on the SD card changes. YOU DO NOT LOSE SD CARD access! The change was that if an app created a folder on your SD card to store stuff, another app cannot access and make changes to it (Which is how it should have been from the beginning). There are many reasons as to why this is the better way (many security related as well as programming related scenarios).
This means that each app can create and write changes to SD card folders it creates and no other folder. The app has to be the creator of the folder it's making changes to.. that makes sense right?! You can still put all the music and pictures and documents you want on the SD card and they will still work like in the past. A few apps had to be updated because they were doing things the old way, but that's been done and you shouldn't have any issues that people had when the change first was done.
4.4 adds a host of new features, bug fixes, network efficiency enhancements and security patches (some are very serious and if you're still on 4.3, your phone is at risk daily). I highly suggest everyone upgrade. If you have any particular issue, private message me and I will help you address it!
To address your current questions though, the change wasn't something that was broken by Google. It shouldn't have been called an SD Card Fix either (like I said, it didn't break), but there were changes in the way Android Apps interacted with the SD card. You can still do this SD Card Fix manually or just use an app in the play store to make the changes for you. There are still certain situations where the "SD Card Fix" is useful, but if it's working for you, then leave it the way it is. Most problems initially were due to needing updates for apps at the time.
Click to expand...
Click to collapse
Thank you for response and again great job on the root.
The reason I used word "broken" was because originally it broke many programs. I would hate not to be able to access DCIM directory created by camera, to view or delete pics with my favorite third party view program, just to give an example, of why limiting access to SD card could create major issues, but it seems to be working fine so far, so I leave it alone for now.
Another quick question: phone status says official, so do I need to worry about future updates breaking the root, or is OTA updates not possible despite official status.

pete4k said:
Thank you for response and again great job on the root.
The reason I used word "broken" was because originally it broke many programs. I would hate not to be able to access DCIM directory created by camera, to view or delete pics with my favorite third party view program, just to give an example, of why limiting access to SD card could create major issues, but it seems to be working fine so far, so I leave it alone for now.
Another quick question: phone status says official, so do I need to worry about future updates breaking the root, or is OTA updates not possible despite official status.
Click to expand...
Click to collapse
Don't accept the OTA updates (you can be notified even when rooted). They will most likely result in a softbrick.
Wait for someone to test it or you might have to unroot and take the update and then perform a similar method to get root back. It depends on what they do to prevent things like this in the future (if anything).

thanks for your quick reply, on my previous root phone status was custom, so no OTA there. I guess I just freeze the update app to be on safe side, kids play my phone sometimes and could update by accident, I remember from the time before root how pesky those update reminders can be and how easy it is to press accept instead of cancel.

Quick question: I am already at NE6, rooted with TowelRoot and KNOX is NOT tripped. Which steps I need to follow to upgrade to NF4?
Or is the steps shown here is not applicable in my case?

lanwarrior said:
Quick question: I am already at NE6, rooted with TowelRoot and KNOX is NOT tripped. Which steps I need to follow to upgrade to NF4?
Or is the steps shown here is not applicable in my case?
Click to expand...
Click to collapse
This guide will work for you. However, you should start from fresh stock NF4 unrooted. Odin stock NF4 and proceed.
It's a lot harder to update a rooted NE6 to all the NF4 files then it is to root NF4 using the NE6 kernel.

effortless said:
This guide will work for you. However, you should start from fresh stock NF4 unrooted. Odin stock NF4 and proceed.
It's a lot harder to update a rooted NE6 to all the NF4 files then it is to root NF4 using the NE6 kernel.
Click to expand...
Click to collapse
I just did an upgrade from NE6 to NF4 following the thread here: http://forum.xda-developers.com/not...udnf4-extracted-stock-firmware-t2834398/page3
But my phone is now hosed - cannot use keyboard ("Unfortunately, Samsung Keyboard has stopped" error) and APN is gone from SIM card. So I am trying to salvage this.
If I Odin NF4 (add the NF4 file to "AP" in Odin), wouldn't this trip KNOX?

lanwarrior said:
I just did an upgrade from NE6 to NF4 following the thread here: http://forum.xda-developers.com/not...udnf4-extracted-stock-firmware-t2834398/page3
But my phone is now hosed - cannot use keyboard ("Unfortunately, Samsung Keyboard has stopped" error) and APN is gone from SIM card. So I am trying to salvage this.
If I Odin NF4 (add the NF4 file to "AP" in Odin), wouldn't this trip KNOX?
Click to expand...
Click to collapse
No.. Knox is only tripped with custom kernel or custom recovery. Flashing stock NF4 in Odin will not trip Knox. Just flash NF4 in Odin and reset your phone through the settings and it will be working fine again.
Don't continue to flash the recovery or root your phone through my other guide as it will trip Knox (If that is something you are avoiding).

effortless said:
Don't continue to flash the recovery or root your phone through this guide as it will trip Knox (If that is something you are avoiding).
Click to expand...
Click to collapse
Oh, I thought this guide refer to rooting NF4? I was reading through the steps and it talks about "downgrading" to NE6 kernel if one already have NF4.
If needed to, I can flash stock NE6, do a system update to NF4, then follow this guide.
Err.. I just realized that my phone still have SU and root still working, even after hard reset. That means system update won't work. I guess flashing stock will wipe out root?

lanwarrior said:
Oh, I thought this guide refer to rooting NF4? I was reading through the steps and it talks about "downgrading" to NE6 kernel if one already have NF4.
If needed to, I can flash stock NE6, do a system update to NF4, then follow this guide.
Err.. I just realized that my phone still have SU and root still working, even after hard reset. That means system update won't work. I guess flashing stock will wipe out root?
Click to expand...
Click to collapse
Sorry for the confusion. I edited it to say my other guide (my other guide is for custom recovery and custom rom).. through this guide is fine. Don't root through Odin, root using the NE6 kernel and towelroot like it says and you'll be ok with Knox.

SPH-L520 NJ1 update question

I have obtained a Sprint s4 mini. From what I can find, the current kernel is SE secure enforcing.
The exact build number is KOT49H.L520_4.4.2_0016
Build date is Oct 7 2014
I am not new here, I know that all known root methods are now bust. What other options are there?
Searching seems to be pretty difficult for this device. All searches for bootloader and recovery come up for the i9190 / i9195
If I use Kies or Odin to flash a previous recovery image, will that brick the device? Also in the settings, it says Secure Boot Status - Type: Samsung
Guess that is referring to the Knox enforcing
The particular image I had in mind to flash with Odin is SPR-L520VPUAMK2-20131115204826
Will it work? Or am I screwed?

Well no one was able to answer my question, so I had to figure it out on my own. Hopefully the following information will be of help to someone else without spending 36+ hours digging through the internet for answers.
You CAN fix your phone it you are on the NJ1 kernel. This is NOT a guide to fixing a bricked phone, although it may fix that too.
If you are on the NJ1 kernel, there are no root methods currently available. You MUST be on NE3 or lower. I also attempted to flash the custom recovery through Odin, but after a reboot it was as if I did nothing. No Knox flag, no warranty trip, no custom recovery.
Here is what I did to get custom recovery and root:
READ THIS BEFORE ATTEMPTING STEP 1.
This is only for the Sprint variant of the S4 Mini. Model number SPH-L520
Your Warranty could be voided. Proceed if you like. (More info on steps 5 and 6)
I had a horrible time getting the downloads from Sammobile. You WILL have to create an account and login to download files. I could not find any working links for the firmware below except for this site. Register a user name and password, DO NOT UNCHECK THE BOX that says receive emails from Sammobile OR YOU WILL NOT GET YOUR REGISTRATION EMAIL. On the Register page it is at the bottom. After you register, check your email and click on the link to complete the registration.
Close all your windows that are open to sammobile.
You are going to want to download Internet Download Manager in order to download files from Sammobile. After many many attempts to download the firmware from Sammobile, all tries failed. YOU ARE GOING TO NEED IDM to get a reliable download.
Download IDM ---> https://www.internetdownloadmanager.com/download.html
Install it and follow these directions to enable resume downloads in IDM ---> http://forum.xda-developers.com/showthread.php?t=2765456
If you do not do the steps above, you most likely will have failed download after failed download.
Even after setting this up, the firmware download failed on me twice. I deleted it from the download list in IDM and started it again.
IDM integrates well with Internet Explorer. Kinda buggy with Chrome. I would suggest using IE for the rest of this Tutorial.
Ok, now that you have that squared away, move on to step 1
_________________________________________________________________________________________________________________________
1) Flash your phone back to NE3. You can get that here ---> http://www.sammobile.com/firmwares/download/31482/L520VPUBNE3_L520SPTBNE3_SPR/ (click Regular Download, then on new page right-click Confirm Download and click SAVE AS. After that the IDM window should pop up. Just Start Download)
Also go ahead and download download the NJ1 in case things get rough. List of all firmwares here ---> http://www.sammobile.com/firmwares/database/SPH-L520/
2) Download and install the Samsung drivers ---> http://www.mediafire.com/download/a4hd8y0c1iakysk/Samsung-Usb-Driver-v1.5.49.0.exe
Download Odin 3.09 ---> http://androidhost.org/PVAIv
Unzip Odin to a folder or desktop. Do not run it from in the zip folder.
3) Run Odin 3.09.
Reboot your S4 Mini SPH-L520 into download mode. Turn phone off > Hold Volume Down, Home Button, and Power Button all at the same time. Wait for the phone to buzz and the pop up on the screen. Release the buttons and press Volume Up to confirm.
Now plug in your phone to your computer. It might take a few seconds for the drivers to install. Wait until Odin shows blue color in the first bar on the left side. Should say 0:[COM3] (the COM number will be different depending on your computer and the USB port you plugged it into)
VERY VERY IMPORTANT! Make sure that the AUTO-REBOOT and F. RESET TIME boxes ARE checked. Make sure that the RE-PARTITION box is NOT checked.
4) Unzip the NE3 download from earlier. Click on the AP button in Odin and navigate to where you unzipped NE3. It should be a .MD5 type of file
Give Odin a few mins to check the file. It may appear that Odin has hung up, just be patient.
After Odin has run the check, it should say ok in the little window on the bottom left. Now click START and wait.
DO NOT bump the phone, the laptop, the usb cord, and MAKE SURE THE BATTERY DOES NOT FALL OUT!!!
After Odin is done flashing, it will reboot the phone. After the initial reboot, the phone will reboot itself once more. Be patient
Now wait for the phone to completely boot up.
5) After you have got back to ME3, you can follow this guide to root it ---> http://androidxda.com/root-samsung-galaxy-s4-mini-sprint-sph-l520
You already have most of the files you need. Just follow the instructions and download what you do not have already.
By the way, in Odin the AP button and the PDA button are the same
(This method should not trip the Knox counter, but I am unsure. Mine was already tripped before all of this)
OPTIONAL (this will trip the Knox counter and lose warranty status)
6) Now you can use this guide to install the custom recovery ---> http://techbeasts.com/2014/05/04/in...-root-sprint-samsung-galaxy-s4-mini-sph-l520/
Again, you already have most of the files you need. DL what you don't have.
_________________________________________________________________________________________________________________________
I am planning on instaling CM11 ---> http://forum.xda-developers.com/showthread.php?t=2669991
This ROM apparently needs a specific recovery in order to work properly. I installed that one instead.
MAKE A BACKUP IN THE RECOVERY OF THE STOCK ROM BEFORE FLASHING ANY CUSTOM ROMS, or else be sorry later.
This is about as simplified as I could get it. Hope this helps out those of you that were as confused as I was.
I will not be providing support. Simply do not have the time. There is more than enough info here to help you figure out what to do.

fire3element said:
I have obtained a Sprint s4 mini. From what I can find, the current kernel is SE secure enforcing.
The exact build number is KOT49H.L520_4.4.2_0016
Build date is Oct 7 2014
I am not new here, I know that all known root methods are now bust. What other options are there?
Searching seems to be pretty difficult for this device. All searches for bootloader and recovery come up for the i9190 / i9195
If I use Kies or Odin to flash a previous recovery image, will that brick the device? Also in the settings, it says Secure Boot Status - Type: Samsung
Guess that is referring to the Knox enforcing
The particular image I had in mind to flash with Odin is SPR-L520VPUAMK2-20131115204826
Will it work? Or am I screwed?
Click to expand...
Click to collapse
Can you help me to backup your first partition on your phone and send to me. You can use EFS Professional on xda.

Hmm....I installed the NJ1 update through Odin. And then flashed the CF auto root (or maybe it was the recovery.tar) with no issues. I did this when NJ1 was first released.

NCTP2 said:
Hmm....I installed the NJ1 update through Odin. And then flashed the CF auto root (or maybe it was the recovery.tar) with no issues. I did this when NJ1 was first released.
Click to expand...
Click to collapse
Can you backup your phone by EFS Pro and send to me. Thanks.

NCTP2 said:
Hmm....I installed the NJ1 update through Odin. And then flashed the CF auto root (or maybe it was the recovery.tar) with no issues. I did this when NJ1 was first released.
Click to expand...
Click to collapse
I was unsure about it considering all the changes with SE Secure and Knox. Always pays to be safer than sorry. I could not find any reports of this anywhere after hours of reading and searching. Thanks for confirming though. :good:
quanqw said:
Can you backup your phone by EFS Pro and send to me. Thanks.
Click to expand...
Click to collapse
I am sorry, I have been really busy. What exactly are you trying to do? Asking someone to backup sensitive data from their phone and share it to a stranger can be alarming.
At least tell us what is going on or why you need the backup.

worked
fire3element said:
I was unsure about it considering all the changes with SE Secure and Knox. Always pays to be safer than sorry. I could not find any reports of this anywhere after hours of reading and searching. Thanks for confirming though. :good:
I am sorry, I have been really busy. What exactly are you trying to do? Asking someone to backup sensitive data from their phone and share it to a stranger can be alarming.
At least tell us what is going on or why you need the backup.
Click to expand...
Click to collapse
thanks alot
the baseband nearly killed me but i thanked my God for you. it worked for me
my question is, is there any way to get it work for domestic sim outside USA?

About those root files

Hello. I'm just making this post to clear up some things and rumors about the posts going around about root firmware etc for newer ATT Galaxy phones like the s6, s6 edge, s6 edge + and the Note 5...
First of all these files have been around for some time now and only very few people in the unlocking/imei repair scene had them (including me) and just a few days ago someone decided to leak them and well they are now being offered for sale etc etc...Anyways these are what is called "engineering" kernel boot images with insecure adbd enabled meaning that it gives you root shell access.
Now the software that we use for our "unlocking" purposes only require this access to perform the operations that we want. However with all the new security Samsung has implemented, these kernels are by no means full root options. For example trying to use apps that require root (Titanium, Root checker) won't work and updating the SU binary under supersu app will send the phone on a bootloop because of SELINUX etc etc and as you know the only way to get around that is by flashing a custom kernel but ATT models having a locked bootloader this is not an option.
TL,DR : These files will only grant you "half assed" root that most people won't be able to take advantage of because it is all run over adb shell..maybe kernel wizards like @arter97 would like to take a look at them and see if he can find something useful
Any questions feel free to ask

Sunderwear said:
Hello. I'm just making this post to clear up some things and rumors about the posts going around about root firmware etc for newer ATT Galaxy phones like the s6, s6 edge, s6 edge + and the Note 5...
First of all these files have been around for some time now and only very few people in the unlocking/imei repair scene had them (including me) and just a few days ago someone decided to leak them and well they are now being offered for sale etc etc...Anyways these are what is called "engineering" kernel boot images with insecure adbd enabled meaning that it gives you root shell access.
Now the software that we use for our "unlocking" purposes only require this access to perform the operations that we want. However with all the new security Samsung has implemented, these kernels are by no means full root options. For example trying to use apps that require root (Titanium, Root checker) won't work and updating the SU binary under supersu app will send the phone on a bootloop because of SELINUX etc etc and as you know the only way to get around that is by flashing a custom kernel but ATT models having a locked bootloader this is not an option.
TL,DR : These files will only grant you "half assed" root that most people won't be able to take advantage of because it is all run over adb shell.
Any questions feel free to ask
Click to expand...
Click to collapse
Very informative, pretty much everything I needed to know. If you can't use root apps then I'm sure a lot of users will disregard the files, myself included as I only would like to use said apps. Thanks for the info?

all root files https://www.dropbox.com/s/gkxk32f778odlxu/AT&T_Root_Files.rar?dl=0

ohap said:
all root files https://www.dropbox.com/s/gkxk32f778odlxu/AT&T_Root_Files.rar?dl=0
Click to expand...
Click to collapse
how can we use that boot img with is associated with the N920AUCE2APB2 firmware, which no one has.
edit: turns out that the N920AUCE2APB2 firmware is based on the MashMallow (6.0.1) link below for proof . so i guess it wouldn't work on 5.1.1
img link
http://www.phone-probe.com/wp-conte...63_10205787832278168_2060735319_n-169x300.jpg

Would it be possible to use the ENG kernel to manually install the superuser binary and push the superuser apk to system? Or would that cause the same bootloops also?

We need a working recovery odin file first.

jellybear456 said:
Very informative, pretty much everything I needed to know. If you can't use root apps then I'm sure a lot of users will disregard the files, myself included as I only would like to use said apps. Thanks for the info?
Click to expand...
Click to collapse
As not much has been said in the thread, yes after Odin flashing the ENG kernel for our device and flashing a root script we can use rooted apps. @metalcated posted a script that does push SuperSU into system/. This was originally posted in the atat GS6 forum. It's a potentially complicated process and if your phone shuts off, battery dies or you hard reboot you will be stuck in a bootloop, hotbooting works fine for Xposed. Will this method be practical for everyone probably not, but considering we were told the device was unrootable........
Read thru his thread, then read it again, seriously do this. And if you still want to try, backup everything you can just in case you need to reflash via Odin to recover from a bootloop. Here were my steps.
1.Updated to newest firmware @Sunderwear posted PB2 (BL/AP/CP/CSC) this will wipe your device. In the pics provided I did try a couple firmware combinations after flashing PB2. I wouldn't suggest this but to each their own.
2.Metalcateds thread is here:
http://forum.xda-developers.com/att-galaxy-s6/general/root-5-1-1-qa-oj7-root-snag-t3334546
3. The only file I downloaded and used was this one:
https://www.androidfilehost.com/?fid=24438995911977129
(G920a5.1.1.root.metalcated-v4.zip)
4.Save it and extract it on your PC
5. Verify Samsung drivers and adb are installed
6.***ENABLE USB DEBUGGING*** this is an important step.
7. Plug device into PC open file and run root script. It'll prompt you to press enter a couple of times and reboot the phone. Just follow the on-screen instructions.
8. After it reboots you have root access.
Root apps that work for me: Titanium backup/root explorer/build.prop editor/no frills.
I was able to delete all Knox apps and debloat the heck of the stock ROM. At no point did my device freeze, reboot on its own.
None of this is my work, I just figured out how to get it going on our device. If you want to try it out and your successful thank @metalcated and everyone listed in the thread as they did all the work..
A couple people reported their Knox warranty tripped to 1. So i felt I needed to check if this tripped my own Knox counter. So I'm bootlooped for now but my Knox is 0 !!!! @TechNyne66 and @jrtran I'm posting the instructions on how to do this if you decide to try this method I originally pm'd to you both.
{
"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"
}
Sent from my Nexus 6P using XDA-Developers mobile app

Michael3214 said:
As not much has been said in the thread, yes after Odin flashing the ENG kernel for our device and flashing a root script we can use rooted apps. @metalcated posted a script that does push SuperSU into system/. This was originally posted in the atat GS6 forum. It's a potentially complicated process and if your phone shuts off, battery dies or you hard reboot you will be stuck in a bootloop, hotbooting works fine for Xposed. Will this method be practical for everyone probably not, but considering we were told the device was unrootable........
Read thru his thread, then read it again, seriously do this. And if you still want to try, backup everything you can just in case you need to reflash via Odin to recover from a bootloop. Here were my steps.
1.Updated to newest firmware @Sunderwear posted PB2 (BL/AP/CP/CSC) this will wipe your device. In the pics provided I did try a couple firmware combinations after flashing PB2. I wouldn't suggest this but to each their own.
2.Metalcateds thread is here:
http://forum.xda-developers.com/att-galaxy-s6/general/root-5-1-1-qa-oj7-root-snag-t3334546
3. The only file I downloaded and used was this one:
https://www.androidfilehost.com/?fid=24438995911977129
(G920a5.1.1.root.metalcated-v4.zip)
4.Save it and extract it on your PC
5. Verify Samsung drivers and adb are installed
6.***ENABLE USB DEBUGGING*** this is an important step.
7. Plug device into PC open file and run root script. It'll prompt you to press enter a couple of times and reboot the phone. Just follow the on-screen instructions.
8. After it reboots you have root access.
Root apps that work for me: Titanium backup/root explorer/build.prop editor/no frills.
I was able to delete all Knox apps and debloat the heck of the stock ROM. At no point did my device freeze, reboot on its own.
None of this is my work, I just figured out how to get it going on our device. If you want to try it out and your successful thank @metalcated and everyone listed in the thread as they did all the work..
A couple people reported their Knox warranty tripped to 1. So i felt I needed to check if this tripped my own Knox counter. So I'm bootlooped for now but my Knox is 0 !!!! @TechNyne66 and @jrtran I'm posting the instructions on how to do this if you decide to try this method I originally pm'd to you both. View attachment 3705507
View attachment 3705513View attachment 3705514View attachment 3705515
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
Wow that's great information and great news. Thanks! I'm going to give this all a few reads and possibly give it a shot. I'll be sure to inform anyone if I try it and have success. A long process, but I don't mind if I can successfully gain root access and use root apps that may make my battery life a bit better. Thanks again!

@Michael3214 I tried and it works good on G920A, G925A, G928A and N920A. If you have stock firmware for N920A (PB2), please post it. Thanks

If it goes in boot loop. Do u think it's really worth the effort. Personally I think it needs little more work. Least it's going in right direction. Maybe they get boot loop fixed. Even if it trips Knox it . That be fine with me.
Rocking Samsung Galaxy Universal Park Themes.

I'm sure somebody much smarter than me has tried already, but could we push a script to set SELinux to permissive upon boot?
http://forum.xda-developers.com/ver...ipt-permissive-selinux-stock-kernels-t2854364

XRange said:
If it goes in boot loop. Do u think it's really worth the effort. Personally I think it needs little more work. Least it's going in right direction. Maybe they get boot loop fixed. Even if it trips Knox it . That be fine with me.
Rocking Samsung Galaxy Universal Park Themes.
Click to expand...
Click to collapse
Without access to a pc its a bad spot to be caught in. I ran the "root-Boot.cmd" to recover from the bootloop. The phone hangs on the splash screen for 45 seconds then finishes booting back into android.
Sent from my SAMSUNG-SM-N920A using XDA-Developers mobile app
---------- Post added 4th April 2016 at 12:05 AM ---------- Previous post was 3rd April 2016 at 11:57 PM ----------
jrtran said:
@Michael3214 I tried and it works good on G920A, G925A, G928A and N920A. If you have stock firmware for N920A (PB2), please post it. Thanks
Click to expand...
Click to collapse
Here's the link to the firmware.
http://forum.xda-developers.com/showthread.php?t=3331843
Sent from my SAMSUNG-SM-N920A using XDA-Developers mobile app

I have OGG firmware restore and can try different methods if needed. I've tried a few with no success. But am able to recover from bad flashes. Willing to test anything that doesn't flash recovery or kernel.

XRange said:
If it goes in boot loop. Do u think it's really worth the effort. Personally I think it needs little more work. Least it's going in right direction. Maybe they get boot loop fixed. Even if it trips Knox it . That be fine with me.
Rocking Samsung Galaxy Universal Park Themes.
Click to expand...
Click to collapse
Excuse my ignorance if this strikes anyone as a noob question... If my device bootloops I obviously cannot go into download mode... My question is twofold: 1: Is my only recourse to flash firmware via Odin?.. And if so... 2: Will my computer/Odin recognize my phone while it is in bootloop?

2Tone23 said:
Excuse my ignorance if this strikes anyone as a noob question... If my device bootloops I obviously cannot go into download mode... My question is twofold: 1: Is my only recourse to flash firmware via Odin?.. And if so... 2: Will my computer/Odin recognize my phone while it is in bootloop?
Click to expand...
Click to collapse
Hold volume up and down + power + home tell your phone resets, then volume down + power + home to boot download mode.

TechNyne66 said:
Hold volume up and down + power + home tell your phone resets, then volume down + power + home to boot download mode.
Click to expand...
Click to collapse
And this works if you're caught in a bootloop, correct? Also, the I have the files for AOJ1 not APB2. there shouldn't be an issue restoring through odin from APB2 to the older AOJ1 because it's still lollipop, right?

can we use this just to debloat and be good?

blane3298 said:
can we use this just to debloat and be good?
Click to expand...
Click to collapse
Yes about all root is good for anyways.
---------- Post added at 06:08 PM ---------- Previous post was at 06:07 PM ----------
jellybear456 said:
And this works if you're caught in a bootloop, correct? Also, the I have the files for AOJ1 not APB2. there shouldn't be an issue restoring through odin from APB2 to the older AOJ1 because it's still lollipop, right?
Click to expand...
Click to collapse
Doesn't matter just don't downgrade firmware or flash anything but AP in odin.

have you tried this yet?

TechNyne66 said:
Hold volume up and down + power + home tell your phone resets, then volume down + power + home to boot download mode.
Click to expand...
Click to collapse
Thanks for your response... I just want to be clear, while in bootloop I can put my phone into download mode by the usual means?