This is for both US Cellular Samsung S6 and S6 Edge variant. Thanks also goes to @g.lewarne for his work on Unikernel as a couple of their ramdisk/kernel commits were needed to get this going. Also, thanks to @datajosh for this template And @bpdev for testing the 925R4 version...
This will trip KNOX. It will. Trip. KNOX. IF YOU HAVE NOT TRIPPED KNOX YET - THIS WILL TRIP IT. ALSO - you CANNOT downgrade after you take the OTA so be sure you want it.
I hope that's clear enough?
Instructions:
After you've booted into OF7, go to Settings > About device and tap Build number 7 times to enable Developer Mode.
Go back and select Developer options and turn on OEM unlocking
Reboot in to download mode (Power + Home + Volume Down)
Use ODIN to flash 925R4root.tar or 920R4root.tar (depending on your device)
After your phone boots you will now have root!
If you notice constant messages about security issues because of KNOX and the kernel being permissive. To get rid of these, open Titanium Backup (or your personal favorite app freezing app) and freeze SecurityLogAgent.
Downloads
925R4 - http://1drv.ms/1HeDWXO
925R4 Source
920R4 - http://1drv.ms/1NUVJ8B This is untested...I did not have a tester for this version....
920R4 Source
The 925R4 version may or may not work with the Sprint 925P variant...no working data confirmed!
ENJOY!
Man I wish we could just find a damn exploit already lol gone this long without tripping Knox. And with the fact that I've received the "Fingerprint scanner has encountered an error, use your backup password." error 4-5x already I'm worried about tripping Knox, although you'd think they'd still fix that considering just rooting shouldn't break the scanner lol.
So this requires me to stay on that kernel huh? I couldn't go back to stock kernel huh?
cpfeifer said:
Man I wish we could just find a damn exploit already lol gone this long without tripping Knox. And with the fact that I've received the "Fingerprint scanner has encountered an error, use your backup password." error 4-5x already I'm worried about tripping Knox, although you'd think they'd still fix that considering just rooting shouldn't break the scanner lol.
So this requires me to stay on that kernel huh? I couldn't go back to stock kernel huh?
Click to expand...
Click to collapse
You could go back to the stock kernel, but you would loose root. Also as stated above you would trip knox.
someone on a sprint s5 edge said the only thing they noticed didnt work was data..just posting for them since they under 10 post..so thats awesome! if we could get data goin..we can have root!!
---------- Post added at 03:29 PM ---------- Previous post was at 03:17 PM ----------
this kernel has working data on the edge...if you could port the data stuff in yours it should be fine http://forum.xda-developers.com/spr...t/5-1-1-stock-of7-kernel-root-7-4-15-t3150350
Does this method then require flashing a custom recovery then SuperSU.zip (or CF Auto Root)? Just curious because all that's in the .rar is a boot.img and some are having issues with following the method and not having root immediately.
borxnx said:
Does this method then require flashing a custom recovery then SuperSU.zip (or CF Auto Root)? Just curious because all that's in the .rar is a boot.img and some are having issues with following the method and not having root immediately.
Click to expand...
Click to collapse
It should be flashed using ODIN...I believe I updated the link in the OP to fix that issue since I derp'd...
Sent from my SM-G920P using Tapatalk
Flashed on a 920r4, but it is not rooted.
Funny enough, I get knox warnings about threats and stuff. But when I check with root checker, I don't have root.
sintro said:
Flashed on a 920r4, but it is not rooted.
Funny enough, I get knox warnings about threats and stuff. But when I check with root checker, I don't have root.
Click to expand...
Click to collapse
Perhaps you still have to install SuperSU or another super user app.
Sent from my SM-G925R4 using Tapatalk
cpfeifer said:
Perhaps you still have to install SuperSU or another super user app.
Sent from my SM-G925R4 using Tapatalk
Click to expand...
Click to collapse
I reflashed back to stock, then installed supersu. Then opened it up, obviously it said "supersu binary not installed". Next, I flashed this kernel and once booted up supersu still repeats the previous message. In addition, root checker shows that phone is not rooted.
The only thing in the .tar file, for 920r4 at least because that's all I downloaded, is a modified kernel. Nothing about SuperSU or its binaries. This method alone does not root. This merely installs a modified SELinux permissive stock kernel. More steps are necessary to obtain root. You must flash either CF Auto Root or a custom kernel + SuperSU.zip.
Bump? Nobody? OP, amirite? Because the method you describe, and thank you so much for the SELinux permissive kernel, does not complete all of the steps between stock and fully rooted.
borxnx said:
Bump? Nobody? OP, amirite? Because the method you describe, and thank you so much for the SELinux permissive kernel, does not complete all of the steps between stock and fully rooted.
Click to expand...
Click to collapse
920R4 http://1drv.ms/1HzSj73 try this...
I've redone the ramdisk and use the exact same files on my 920P...and kept the carrier parts for US Cellular...
Let me know if this works...
djvoleur said:
920R4 http://1drv.ms/1HzSj73 try this...
I've redone the ramdisk and use the exact same files on my 920P...and kept the carrier parts for US Cellular...
Let me know if this works...
Click to expand...
Click to collapse
Thank you for redoing the ramdisk.
Will try out and let you know.
Anyone experiencing issues with 925r4? I have service but see no signal bars no matter where I go.
https://youtu.be/y7EpSirtf_E
djvoleur said:
920R4 http://1drv.ms/1HzSj73 try this...
I've redone the ramdisk and use the exact same files on my 920P...and kept the carrier parts for US Cellular...
Let me know if this works...
Click to expand...
Click to collapse
This does indeed work. Thank you so much!
Edit...Added instructions I used to complete the root process.
First of all, I wanted to thank the OP of this thread for posting this guide and getting me headed in the right direction.
Credit to @djvoleur
I just wanted to share the method I used to root my USC Galaxy S6 with the Android 5.1.1 update. You will notice that the instructions are similar in the beginning. I added the extra steps that I used to complete the root process. I do not know if this method works for the Edge version.
As the OP states: This will trip knox. Personally, it doesn’t matter to me. I am too impatient and too much of a flash-a-holic to wait for a method that doesn’t trip knox.
Also, I am not a dev and I am unable to answer any questions other than how I obtained root. I am not responsible for any damage that might happen to your phone. Follow this procedure at your own risk.
Having stated these disclaimers, it really isn’t very difficult to implement. I’ve done it twice and both times worked perfectly.
Files you will need for flashing in Odin:
Odin 3.10.7 found here: http://tinyurl.com/puyq4v9
Rooted kernel 920R4root.tar found in the OP.
TWRP 2.7.8.0 (Sprint version, but I can confirm it worked for me. YMMV.) Here: http://tinyurl.com/phvrkaf
Files for flashing in TWRP:
Updated V-Kernel 920R4-071615.zip found here: http://tinyurl.com/o2h8rv4
Super SU v2.49 (beta) found here: http://tinyurl.com/or6mmqr
Now, PLEASE read these instructions before starting so that you will have a good understanding of what to do. After reading, you may begin.
Don’t forget to put the files for flashing in TWRP on your SD card (phone) before beginning this process.
After you've booted into OF7, go to Settings > About device and tap Build number 7 times to enable Developer Mode.
Go back and select Developer options and turn on OEM unlocking
Boot into download mode (Power + Home + Volume Down)
Use ODIN to flash 920R4root.tar
Use ODIN to flash TWRP and make sure that reboot is NOT checked in options.
Unplug the phone and hold the Power + Volume Down key to reboot. When the screen goes blank, quickly hold the Power + Home + Volume Up key to boot into TWRP. If it doesn’t boot to TWRP, you may have to start over.
In TWRP flash the updated V-Kernel file first, then the Super SU file, and then reboot.
After your phone boots you will now have root!
If you notice constant messages about security issues because of KNOX and the kernel being permissive. To get rid of these, open Titanium Backup (or your personal favorite app freezing app) and freeze SecurityLogAgent. (Worked for me.)
You now should be able to install Chainfire's Super SU app from the Play Store, and you can also use Root Checker to confirm you are rooted.
Good Luck!
Would this work on G920R7... J4 (rather than OF7) 5.1.1? That's what I have.
I see there is a PC1 update available also for my G920R7 which is 6.0 marshmallow.
Hard to believe I've had this device for a year with no root... Anyone can help me get this rooted? Thanks!
so after installing the intial kernel that did not work I scrolled through and saw the updated version...you should probably update the link for the untested r4 to the working version later posted...
my problem is that Im unable to load in anything but download mode due to kernel not seandroid enforcing basically not enabling me to load into recovery mode so I need the zipped version of the kernel to install via odin in download mode if possible otherwise im waiting on a 2 hour download of the stock kernal to install
i just picked up a us cellular note 5 (SM-N920R4 on OJ5)
its trying to download and update to a new firmware so i turned off wifi and that appears to stop it but i cant do any of the gazillion updates from play store like we normally do after you receive a new phone or do a factory data reset.
please advise what i need to do since im already on OJ5 and can not connect to wifi as it will auto install whatever update its trying to download.
thanks again
en11gma said:
i just picked up a us cellular note 5 (SM-N920R4 on OJ5)
its trying to download and update to a new firmware so i turned off wifi and that appears to stop it but i cant do any of the gazillion updates from play store like we normally do after you receive a new phone or do a factory data reset.
please advise what i need to do since im already on OJ5 and can not connect to wifi as it will auto install whatever update its trying to download.
thanks again
Click to expand...
Click to collapse
Use TB to remove the update apps - green phone icons in TB. That's how it always gets stopped on any samsung.
Related
This guide will enable you to easily root your phone in 6 steps. I've taken out the mystery and complications.
1) Go to HTC Dev site and manually unlock your bootloader. Select "register" and create your account.
1a) After you are registered select "all other supported models" in the pull down box
1b) Click "begin unlock bootloader". it will ask "are you sure" yes of course you are. acknowledge legal terms. then continue.
1c) Ignore the battery pull instructions as we can't pull the battery. hold down the power key and the volume down key until the bottom buttons stop flashing and your phone shuts off (don't worry if you take a screenshot. It happens all the time). then release ONLY THE POWER BUTTON. Keep holding the volume down key until the bootloader screen shows up.
1d) Follow "step 3" and the rest of the instructions as listed on the HTC site to unlock your bootloader manually.
2) Install android ADB/SDK on your pc. This video shows how to do it nicely:
2a) ****NEW UPDATED 03/05/13*** Alternatively if you DON'T want to install ADB/SDK you can just download the NON-FLASHABLE platform-tools.zip file located in my dropbox folder here.
Just extract this folder to your desktop using WINZIP or whatever archive tool you use and proceed to step 3.
3) Open a command line in your "platform-tools" folder by holding shift+right click anywhere within the folder and selecting the menu option "open a command window here". Then click here to install TWRP using fastboot. Follow the "Download - Fastboot Method:" instructions.
3a) If your phone isn't detected by windows please install the proper USB drivers for your operating system. Go here for 32bit. Go here for 64 bit.
4) Flash SuperSu and Busybox on your device:
4a) Click here and download the latest version of SuperSu. save it to your sdcard.
4b) Go to my dropbox and download Busybox 1.20.2 and save it to your sdcard.
5) Reboot into recovery (via the bootloader selection)
6) Flash the SuperSu zip and the Busybox zip listed in 4a and 4b
That's it!
"So now what?" you may be asking.
You are now free to flash ROMs that support s-on.
Two are my favorites are
(1) Stock with Goodies. (my personal favorite and the one I use today). This is a great ROM for beginners and people who prefer a slimmed down ROM (minus the bloat) and lots of free memory!
(2) Viper4G. This is a ROM for more experienced users and offers TONS of customization.
You can also run apps from Google play that required ROOT access!
If you're feeling slightly adventurous you can flash a custom kernel (which will allow you to overclock your phone). Two of the kernels I use are:
(1) ElementalX by flar2. Click here to take a trip over there. This one is especially important to flash as it seems HTC was up to shenanigans with the latest HBoot (2.09).
If you're unlucky enough to have HBoot 2.09 they have RESTRICTED access to your /system partition. What does this mean to you? It means that if any app writes to your /system partition (ROOTED or not) the phone will "panic" and reboot. Shady behavior if you ask me. The solution? Flash this kernel! it will give you write access so that everything works properly.
(2) The Arc-Reactor kernel! This one is for people that are s-off (see below for an explanation of s-off) only! It's the kernel I currently use and is the fastest kernel out there! Highly recommended if you decide to go s-off!!!
If and when you're feeling more adventurous you can go "s-off" (security off) which removes any security limitations of your phone. It makes flashing ROMs and updating firmware a lot easier. You can find out about s-off by taking a trip over to the DirtyRacun thread here. I will NOT walk you through this process. They will totally help you on their IRC channel. Just read post # 1 in that thread.
There's also a new method of s-off which literally takes 2 minutes. It's called facepalm and is located here But is NOT for the feint of heart, bad typers, nor people that cannot follow instructions! Why? One typo here and your phone is a brick. A paperweight. Useless. Well...you can recover...but that's not the purpose of this thread. If you DO brick your phone PM me. I'll help you out.
I take NO credit for any of this. It's all out there to learn I just put it all together. In one spot. Any questions feel free to PM me.
If I helped you out hit the THANKS button...or buy me a beer! Either way lol!
Tested and works with 3.16.651.3 (even if you took the OTA and have hboot 2.09 and are s-on)
Did you use SuperSU or Superuser for root access? Either way could you please update the binary to see if it succeeds or if you get an instant reboot?
lancemoreland said:
Did you use SuperSU or Superuser for root access? Either way could you please update the binary to see if it succeeds or if you get an instant reboot?
Click to expand...
Click to collapse
Everyone that is using supersu is experiencing that issue. The program itself will grant superuser access to your device. You don't need to open it. When you try and open it it will attempt to update the binary and then reboot the phone. You can ALWAYS reflash a new version of supersu when they update it.
To be clear: I'm up and running on my phone right now with superuser access. I'm fine unless I try to open the supersu program itself. Then I experience this issue you pointed out.
rawintellect said:
Everyone that is using supersu is experiencing that issue. The program itself will grant superuser access to your device. You don't need to open it. When you try and open it it will attempt to update the binary and then reboot the phone. You can ALWAYS reflash a new version of supersu when they update it.
To be clear: I'm up and running on my phone right now with superuser access. I'm fine unless I try to open the supersu program itself. Then I experience this issue you pointed out.
Click to expand...
Click to collapse
I agree. I am up and running also but the new hboot locks the system partition and any app that tries to write to it will cause a reboot. Ad-free is another example.
lancemoreland said:
I agree. I am up and running also but the new hboot locks the system partition and any app that tries to write to it will cause a reboot. Ad-free is another example.
Click to expand...
Click to collapse
Indeed this is a well documented problem but really not what this thread is about. Perhaps you can check out THIS thread where they are discussing this issue at length and hopefully they will come up with a solution for it?
http://forum.xda-developers.com/showthread.php?t=1538053
It also looks as though chainfire (the OP) is working on a fix if I read the last few posts correctly. and when he gets it I will update this post with it.
rawintellect said:
It also looks as though chainfire (the OP) is working on a fix if I read the last few posts correctly. and when he gets it I will update this post with it.
Click to expand...
Click to collapse
Yes I am participating in that thread. Chainfire is looking for a work around for his specific app, other apps that write to the system partition will no longer work. The point is that with Hboot 2.09 there are limitations and we will not enjoy full root as we have before when we were s-on.
Updated with an alternative superuser program.
SuperSU would ask to update binary and then just reboot. This fixed my problem for being able to access/deny and turn off messages. However it did not uninstall superSU will this cause a conflict having them both?
Edit: Okay I am dumb, I had to uninstall superSU first. Then I reflashed superuser to be able to have root privileges for my apps. When I just reflashed superuser hoping it would get ride of and superuser and keep root it did not.
Thanks it worked!
Help with rooting please.
So my phone was updated OTA without being rooted to 3.15.651.16 but now it is frozen. The touch screen will work temporarily upon a simulated battery pull and then freeze again only for me to simpull again and then it freeze again. I've gone into the bootloader and factory reset and wiped the cache but it's still messed up. So I think that maybe it's the software not installing correctly or something because this only started happening immediately after I download the new update.
I'm thinking about rooting my phone and even though I'm a pretty techy person this is new to me. I'm hoping that if I root my phone I can put it back to the stock software before the update and then just re-update OTA stock to the new update. I think that may fix it. Do y'all have any input it would be greatly appreciated as I have been dealing with this useless phone for over a week now.
Thanks.
MrSteez said:
So my phone was updated OTA without being rooted to 3.15.651.16 but now it is frozen. The touch screen will work temporarily upon a simulated battery pull and then freeze again only for me to simpull again and then it freeze again. I've gone into the bootloader and factory reset and wiped the cache but it's still messed up. So I think that maybe it's the software not installing correctly or something because this only started happening immediately after I download the new update.
I'm thinking about rooting my phone and even though I'm a pretty techy person this is new to me. I'm hoping that if I root my phone I can put it back to the stock software before the update and then just re-update OTA stock to the new update. I think that may fix it. Do y'all have any input it would be greatly appreciated as I have been dealing with this useless phone for over a week now.
Thanks.
Click to expand...
Click to collapse
Well my suggestion is to go ahead and unlock your phone, flash a recovery and root it using my instructions. Then if you want BONE stock flash the odexed version of Jellybean that Viperboy has in his thread located here: http://forum.xda-developers.com/showthread.php?t=2045929
Why am I suggesting you do this? Because the OTA was very bugged. HTC is VERY slow with fixes. Developers can fix errors in the base errors usually faster than HTC. And most importantly when you are feeling like a change you can flash a custom zip at any time. The ONLY downside to unlocking and rooting is that you void your warranty with HTC, but NOT with sprint! Sprint will still honor a replacement phone when you RELOCK your phone and use the RUU (which isn't available yet but will be) to bring it back to stock. Your bootloader will say *RELOCKED* which lets them know you unlocked it but again they will honor a replacement.
Updated thread with instructions on manually uninstalling supersu first before installing superuser 3.2
Thank you very much!
rawintellect said:
Well my suggestion is to go ahead and unlock your phone, flash a recovery and root it using my instructions. Then if you want BONE stock flash the odexed version of Jellybean that Viperboy has in his thread located here: http://forum.xda-developers.com/showthread.php?t=2045929
Why am I suggesting you do this? Because the OTA was very bugged. HTC is VERY slow with fixes. Developers can fix errors in the base errors usually faster than HTC. And most importantly when you are feeling like a change you can flash a custom zip at any time. The ONLY downside to unlocking and rooting is that you void your warranty with HTC, but NOT with sprint! Sprint will still honor a replacement phone when you RELOCK your phone and use the RUU (which isn't available yet but will be) to bring it back to stock. Your bootloader will say *RELOCKED* which lets them know you unlocked it but again they will honor a replacement.
Click to expand...
Click to collapse
Thanks I seriously appreciate it. I'm at work right now (I actually work at Sprint by the way which is why I'm not worried about having the phone replaced my tech will do it regardless) so I'm probably gonna look over your instructions carefully and then do this tomorrow. I'll let you know what happens I'm really hoping this will do it. It has to be some kind of serious installation bug in the new update because I never had this problem until literally minutes after updating.
And then after the completely stock RUU comes out (with no root or anything special) I can go back to completely locked and stock again? That's what I think I'd prefer but who knows I'm a Android and tech fanboy maybe I'll prefer the root.
MrSteez said:
Thanks I seriously appreciate it. I'm at work right now (I actually work at Sprint by the way which is why I'm not worried about having the phone replaced my tech will do it regardless) so I'm probably gonna look over your instructions carefully and then do this tomorrow. I'll let you know what happens I'm really hoping this will do it. It has to be some kind of serious installation bug in the new update because I never had this problem until literally minutes after updating.
And then after the completely stock RUU comes out (with no root or anything special) I can go back to completely locked and stock again? That's what I think I'd prefer but who knows I'm a Android and tech fanboy maybe I'll prefer the root.
Click to expand...
Click to collapse
yes. going back to stock is as simple as this:
(1) Boot your phone into the bootloader. make sure fastboot is selected. if you have the drivers installed correctly your phone will read "fastboot usb"
(2) if you followed my instructions on rooting you have ADB/SDK installed. so issue the command to relock your phone. type: fastboot oem lock
(3) run the RUU for 3.15.651.16. Done. Your bootloader will say *relocked* but it will be 100% stock.
Uh oh
I think i messed up. I did not see busy box installed and SuperSU is not updating.
The file listed in step 6 contains busybox. It also contains supersu. You want to flash the superuser file after flashing the file in step 6. It will overlay supersu with superuser 3.2. There is no need to update superuser 3.2 once you flashed it. It is the latest release.
Sent from my EVO using xda app-developers app
do i need to just flash the new superuser and it will fix the binary problema nd the titanium problem?
mobilecj said:
do i need to just flash the new superuser and it will fix the binary problema nd the titanium problem?
Click to expand...
Click to collapse
I replied to your email. But check my first post on the subject of superuser and how to uninstall supersu. if you need to that is. I tested this myself and it did uninstall supersu for me by just flashing superuser 3.2. Some people have reported this doesn't work for them.
okay sorry just got both i am going to try it now.. Its all knew to me it seemed like the information was explaining a dual process and i only had acquired one problem.. will post back in a few!
Greetings, fellow Mega-Maniacs!
I am currently working with dev Geohot to get us root access for the SGH-I527 with Baseband Version I527UCUBNE7. All known root methods have been tested and proven to not work with this version of android with this baseband, due to the extremely locked down nature of Samsung Knox on this device.
I, personally, have been throwing every exploit I can think of at this device, to no avail. As of the time and date of this post, we have a donor ready to help the cause (Special thanks to caguas56). That is why I'm proposing a bounty on root access for this phone (SGH-I527 AT&T US version only, although there is a high possibility that it'll work on the Sprint,T-Mo and VZW variant).
The first developer who can successfully get ROOT on KitKat with baseband I527UCUBNE7 and demonstrate this with a successful public test will be awarded the bounty. The bounty will be split equally between devs and donors willing to team up.
I'm in for $10 at the moment, and I'll piss away more if needed down the line.
Who else is in? LETS GET THIS DONE, PEEPS!
Please, only posts regarding root access on this thread. For firmware rollbacks to 4.2.2, see azpatterson3's thread located HERE
kmt5150 said:
Greetings, fellow Mega-Maniacs!
I am currently working with dev Geohot to get us root access for the SGH-I527 with Baseband Version I527UCUBNE7. All known root methods have been tested and proven to not work with this version of android with this baseband, due to the extremely locked down nature of Samsung Knox on this device.
I, personally, have been throwing every exploit I can think of at this device, to no avail. As of the time and date of this post, we have a donor ready to help the cause (Special thanks to caguas56). That is why I'm proposing a bounty on root access for this phone (SGH-I527 AT&T US version only, although there is a high possibility that it'll work on the Sprint,T-Mo and VZW variant).
The first developer who can successfully get ROOT on KitKat with baseband I527UCUBNE7 and demonstrate this with a successful public test will be awarded the bounty. The bounty will be split equally between devs and donors willing to team up.
I'm in for $10 at the moment, and I'll piss away more if needed down the line.
Who else is in? LETS GET THIS DONE, PEEPS!
Please, only posts regarding root access on this thread. For firmware rollbacks to 4.2.2, see azpatterson3's thread located HERE
Click to expand...
Click to collapse
In for at least $20.
Put me down for 2 bucks.
I know you stated you had tried it all but I have a couple questions for you.
#1. Are you able to odin and access the latest PhilZ Recovery on your Mega? I ask because I read other sections like the Note 2's, etc on AT&T and they are able to flash recovery fine and boot into recovery fine.
#2. If you have tried this method, did you try and flash the latest SuperSU v2.00 from Chainfire through PhilZ?
================
Below is a method I suggested to some in my OTA Update thread to NE4 ( KitKat ) for Rooting all my Galaxy phones on KitKat listed and not one has failed to gain root or to disable KNOX. Note this method will trip KNOX and void your warranty. Try this at your own risk....
================
1.Flash the latest Philz recovery ( Galaxy Mega (meliusltexx) ) .
1a) Be sure when flashing a custom recovery not to allow the device to reboot into the OS right after and instead go straight to the recovery first.
( Uncheck reboot device in Odin or if you forgot to uncheck the box after a successful flash of the Custom Recovery in Odin, quickly hold down vol+, Menu & Power Button or last resort pull the battery before it has time to reboot into the OS {again this is after the phone reboots from flashing the custom recovery and passes}).
The security will over write the custom recovery with the stock recovery and you will have to flash Philz or if available TWRP again. First boot into custom recovery will make it stick on after.
2. Once flashed and booted into recovery, you'll be on the main screen.
( Optional but recommended )
2a) At this point, and it is just a suggestion to you all, make a complete backup of the phone as it sits unmodded. I couldn't really tell you how many times I have read/seen of people post that they forgot to back up their phones after they had attempted to do something to their phones and had caused them to have problems..... well many would be surprised how often this happens and I have been guilty of it due to just being impatient. This way you will have a starting point fresh, stock and even unrooted to go back to. After your done proceed to step #3.
3. Tick on Philz settings.
4. Tick on Re-root System (Super SU).
5. You will then see the log scroll at the bottom and tell you to reboot and install SuperSU through the Playstore.
6. Reboot Device and once you have booted up, install SuperSU via Playstore or if you have the APK on hand, install it.
7. Once installed it will ask you that it needs to update binaries, do so. It will also detect KNOX and ask to attempt
to disable it, go ahead and it will attempt to do so. ( I have yet for it to say unsuccessful )
8. Enjoy being rooted afterwards.
=======================================
If after step #6 it fails to update binaries or for some chance the SuperSU APK failed to install properly or failed to provide Root Access, below is a link for the newer SuperSU v2.00 that is flashable in your Custom Recovery. Flash it by rebooting back into Recovery and flashing the ZIP file that's downloadable from the middle of the main page in the link below. Once flashed continue on from step #6 above.
Thank you @Chainfire
SuperSU v2.00 <------- click here
.
.
.
.
.
DarkAngel said:
I know you stated you had tried it all but I have a couple questions for you.
#1. Are you able to odin and access the latest PhilZ Recovery on your Mega? I ask because I read other sections like the Note 2's, etc on AT&T and they are able to flash recovery fine and boot into recovery fine.
#2. If you have tried this method, did you try and flash the latest SuperSU v2.00 from Chainfire through PhilZ?
================
Below is a method I suggested to some in my OTA Update thread to NE4 ( KitKat ) for Rooting all my Galaxy phones on KitKat listed and not one has failed to gain root or to disable KNOX. Note this method will trip KNOX and void your warranty. Try this at your own risk....
================
1.Flash the latest Philz recovery ( Galaxy Mega (meliusltexx) ) .
1a) Be sure when flashing a custom recovery not to allow the device to reboot into the OS right after and instead go straight to the recovery first.
( Uncheck reboot device in Odin or if you forgot to uncheck the box after a successful flash of the Custom Recovery in Odin, quickly hold down vol+, Menu & Power Button or last resort pull the battery before it has time to reboot into the OS {again this is after the phone reboots from flashing the custom recovery and passes}).
The security will over write the custom recovery with the stock recovery and you will have to flash Philz or if available TWRP again. First boot into custom recovery will make it stick on after.
2. Once flashed and booted into recovery, you'll be on the main screen.
( Optional but recommended )
2a) At this point, and it is just a suggestion to you all, make a complete backup of the phone as it sits unmodded. I couldn't really tell you how many times I have read/seen of people post that they forgot to back up their phones after they had attempted to do something to their phones and had caused them to have problems..... well many would be surprised how often this happens and I have been guilty of it due to just being impatient. This way you will have a starting point fresh, stock and even unrooted to go back to. After your done proceed to step #3.
3. Tick on Philz settings.
4. Tick on Re-root System (Super SU).
5. You will then see the log scroll at the bottom and tell you to reboot and install SuperSU through the Playstore.
6. Reboot Device and once you have booted up, install SuperSU via Playstore or if you have the APK on hand, install it.
7. Once installed it will ask you that it needs to update binaries, do so. It will also detect KNOX and ask to attempt
to disable it, go ahead and it will attempt to do so. ( I have yet for it to say unsuccessful )
8. Enjoy being rooted afterwards.
=======================================
If after step #6 it fails to update binaries or for some chance the SuperSU APK failed to install properly or failed to provide Root Access, below is a link for the newer SuperSU v2.00 that is flashable in your Custom Recovery. Flash it by rebooting back into Recovery and flashing the ZIP file that's downloadable from the middle of the main page in the link below. Once flashed continue on from step #6 above.
Thank you @Chainfire
SuperSU v2.00 <------- click here
.
.
.
.
.
Click to expand...
Click to collapse
Bootloader is locked
So no recovery flashing
Sent from my GT-I9205 using XDA Free mobile app
Grarak said:
Bootloader is locked
So no recovery flashing
Sent from my GT-I9205 using XDA Free mobile app
Click to expand...
Click to collapse
Well technically all bootloaders are locked (except for the few that aren't) but I take it AT&T is wanting/trying to join the band wagon with Verizon and locking the bootloaders indefinitely by encrypting them on all the devices they can now.
Sorry then, my method will not work straight forward. Good luck. :good:
DarkAngel said:
I know you stated you had tried it all but I have a couple questions for you.
#1. Are you able to odin and access the latest PhilZ Recovery on your Mega? I ask because I read other sections like the Note 2's, etc on AT&T and they are able to flash recovery fine and boot into recovery fine.
#2. If you have tried this method, did you try and flash the latest SuperSU v2.00 from Chainfire through PhilZ?
================
Below is a method I suggested to some in my OTA Update thread to NE4 ( KitKat ) for Rooting all my Galaxy phones on KitKat listed and not one has failed to gain root or to disable KNOX. Note this method will trip KNOX and void your warranty. Try this at your own risk....
================
1.Flash the latest Philz recovery ( Galaxy Mega (meliusltexx) ) .
1a) Be sure when flashing a custom recovery not to allow the device to reboot into the OS right after and instead go straight to the recovery first.
( Uncheck reboot device in Odin or if you forgot to uncheck the box after a successful flash of the Custom Recovery in Odin, quickly hold down vol+, Menu & Power Button or last resort pull the battery before it has time to reboot into the OS {again this is after the phone reboots from flashing the custom recovery and passes}).
The security will over write the custom recovery with the stock recovery and you will have to flash Philz or if available TWRP again. First boot into custom recovery will make it stick on after.
2. Once flashed and booted into recovery, you'll be on the main screen.
( Optional but recommended )
2a) At this point, and it is just a suggestion to you all, make a complete backup of the phone as it sits unmodded. I couldn't really tell you how many times I have read/seen of people post that they forgot to back up their phones after they had attempted to do something to their phones and had caused them to have problems..... well many would be surprised how often this happens and I have been guilty of it due to just being impatient. This way you will have a starting point fresh, stock and even unrooted to go back to. After your done proceed to step #3.
3. Tick on Philz settings.
4. Tick on Re-root System (Super SU).
5. You will then see the log scroll at the bottom and tell you to reboot and install SuperSU through the Playstore.
6. Reboot Device and once you have booted up, install SuperSU via Playstore or if you have the APK on hand, install it.
7. Once installed it will ask you that it needs to update binaries, do so. It will also detect KNOX and ask to attempt
to disable it, go ahead and it will attempt to do so. ( I have yet for it to say unsuccessful )
8. Enjoy being rooted afterwards.
=======================================
If after step #6 it fails to update binaries or for some chance the SuperSU APK failed to install properly or failed to provide Root Access, below is a link for the newer SuperSU v2.00 that is flashable in your Custom Recovery. Flash it by rebooting back into Recovery and flashing the ZIP file that's downloadable from the middle of the main page in the link below. Once flashed continue on from step #6 above.
Thank you @Chainfire
SuperSU v2.00 <------- click here
.
.
.
.
.
Click to expand...
Click to collapse
Believe me, we have tried it all. I have tried a process similar to this and when the phone got done with all the flashing and went to boot up, I got a prompt that said 'We have detected software not approved for use by AT&T. Please take your phone to an AT&T store for assistance.' It also says Secure Check Failed: Kernel. I had to send my phone to sammy to get it fixed since I tripped a few flags. Should be back by Friday the 10th.
Possible to use this method with 4.4 kernel from mega?
http://forum.xda-developers.com/showthread.php?t=2722073
I don't know much about this but my S4 active also has a locked bootloader, and I was able to achieve root on 4.4.2 using the above method. Thought it might be possible to adapt to your cause.
jstinger9489 said:
http://forum.xda-developers.com/showthread.php?t=2722073
I don't know much about this but my S4 active also has a locked bootloader, and I was able to achieve root on 4.4.2 using the above method. Thought it might be possible to adapt to your cause.
Click to expand...
Click to collapse
Will definitely try this again when my phone gets here tomorrow and post updates...
jstinger9489 said:
http://forum.xda-developers.com/showthread.php?t=2722073
I don't know much about this but my S4 active also has a locked bootloader, and I was able to achieve root on 4.4.2 using the above method. Thought it might be possible to adapt to your cause.
Click to expand...
Click to collapse
Tried and my device still won't act right, can only get into download mode. recovery is gone and when i attempt to power on, I get a msg about Secure fail: Kernel and then a yellow triangle with a ! says 'System software not authorized by AT&T has been found on your phone. Please turn off your phone and go to the nesrest AT&T store for help."
UPDATE: A buddy of mine has a JTAG service and I'm going to send it to him for repair. UGH! I'm selling this sonofabitch. I should NOT have to go thru this much bull**** just do modify something I paid 500 bucks for without a contract.
kmt5150 said:
Tried and my device still won't act right, can only get into download mode. recovery is gone and when i attempt to power on, I get a msg about Secure fail: Kernel and then a yellow triangle with a ! says 'System software not authorized by AT&T has been found on your phone. Please turn off your phone and go to the nesrest AT&T store for help."
UPDATE: A buddy of mine has a JTAG service and I'm going to send it to him for repair. UGH! I'm selling this sonofabitch. I should NOT have to go thru this much bull**** just do modify something I paid 500 bucks for without a contract.
Click to expand...
Click to collapse
Have you tried towel root
http://towelroot.com/
BarakOsama said:
Have you tried towel root
http://towelroot.com/
Click to expand...
Click to collapse
Have YOU tried towelroot?
Or have you not read any of the many theads on the subject?
Sorry, not trying to be rude, the same thing has been said so many times
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Can anyone send me boot.img of ATT KK rom?
captemo said:
Have YOU tried towelroot?
Or have you not read any of the many theads on the subject?
Sorry, not trying to be rude, the same thing has been said so many times
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Click to expand...
Click to collapse
My bad..
Alright.
To summarize for people who haven't paid attention. Phone was bricked in a last ditch effort to flash back to 4.3 because the 4.4 update made my phone run like s#it. I also have an S4 Active and the service sucks harder than it already did. The 4.4 update makes the S4 drop out constantly and the battery life blows. Samsung told me to run kies in download mode to get it back to 4.3 I did and BOOM, now phone is fu©k!ng bricked and they won't fix it, claiming it's 'rooted' because the kernel says it's version 3 when it's supposed to be at 4 for kitkat. Fu©k!ng duh, you jerks made me flash it back. I am personally never buying another samsung product again because their customer service was horsesh!t. I happen to have a sammy tv, blu ray, home theater and 2 of their former 'top end' phones, but now I'm ditching them. They can lick my scrotum for all I care anymore.
end rant, back to music.
SCH-R960
I have the US Cellular Galaxy Mega SCH-R960 also updated to 4.4.2 out of the box. I am in for some bucks if you can apply this to my version also the baseband number is R960TYUBNF1, I will send you whatever info you need from the phone. Lets get this done! Thank you!
MeatHammer311 said:
I have the US Cellular Galaxy Mega SCH-R960 also updated to 4.4.2 out of the box. I am in for some bucks if you can apply this to my version also the baseband number is R960TYUBNF1, I will send you whatever info you need from the phone. Lets get this done! Thank you!
Click to expand...
Click to collapse
Can you make a complete firmware dump and compile a .PIT file?
No root.
I do not have root so I can not do those things. If there is a way without root please point me in that direction. Thanks
MeatHammer311 said:
I do not have root so I can not do those things. If there is a way without root please point me in that direction. Thanks
Click to expand...
Click to collapse
sure you can
use heimdall
and can anyone send me the boot.img now?
I don't even think you guys want root if you're not even trying to help
Grarak said:
sure you can
use heimdall
and can anyone send me the boot.img now?
I don't even think you guys want root if you're not even trying to help
Click to expand...
Click to collapse
tell me how to get it any you will have it 1 before 5pm today est.
also here is the pit file you asked for. I used it to unbvrick my phone a few times with odin.
ita for the at&t version
Hi All!
I have been looking around these forums for a few days now and can't find anything concrete on rooting my S6 EDGE 6.01 BUILD: G925IDVU3EPGG.
I have found plenty for the previous builds, and am unsure whether they still apply to my build.
Can someone out there provide the info relevant to gaining root on this build please?
Thanks in advance, David.
hammondegs said:
Hi All!
I have been looking around these forums for a few days now and can't find anything concrete on rooting my S6 EDGE 6.01 BUILD: G925IDVU3EPGG.
I have found plenty for the previous builds, and am unsure whether they still apply to my build.
Can someone out there provide the info relevant to gaining root on this build please?
Thanks in advance, David.
Click to expand...
Click to collapse
https://autoroot.chainfire.eu
This will root your phone. Doesn't matter about the build it works for g925i 6.0.1
callumbr1 said:
This will root your phone. Doesn't matter about the build it works for g925i 6.0.1
Click to expand...
Click to collapse
Thanks for your quick response.
Knox
I have my credit card stored using a banking app.
I read this method will trip Knox, how will this affect my credit card use?
...and is there a rooting method that does not trip knox?
hammondegs said:
I have my credit card stored using a banking app.
I read this method will trip Knox, how will this affect my credit card use?
...and is there a rooting method that does not trip knox?
Click to expand...
Click to collapse
You won't be able to use any banking apps. This is the only root available for s6 edge 6.0.1..
Is there a specific reason you want to root?
callumbr1 said:
You won't be able to use any banking apps. This is the only root available for s6 edge 6.0.1..
Is there a specific reason you want to root?
Click to expand...
Click to collapse
Mostly to install Adaway and remove some apps I don't want.
I also read I will lose the fingerprint function, which I also use.
hammondegs said:
Mostly to install Adaway and remove some apps I don't want.
I also read I will lose the fingerprint function, which I also use.
Click to expand...
Click to collapse
Ahh i see.
I dint think you lose fingerprint with cf auto root. My fingerprint scanner works perfect
callumbr1 said:
Ahh i see.
I dint think you lose fingerprint with cf auto root. My fingerprint scanner works perfect
Click to expand...
Click to collapse
Okay, I am at your mercy, I read in a forum elsewhere that a user lost the fingerprint function.
However, you say that yours still works... that's good to hear.
If I decide to go ahead with root, would it be advisable to uninstall the banking app?
Or will the other functions of the Banking app still work?
Do you know of any developer working on root without tripping knox?
hammondegs said:
Okay, I am at your mercy, I read in a forum elsewhere that a user lost the fingerprint function.
However, you say that yours still works... that's good to hear.
If I decide to go ahead with root, would it be advisable to uninstall the banking app?
Or will the other functions of the Banking app still work?
Do you know of any developer working on root without tripping knox?
Click to expand...
Click to collapse
Yeah mine works perfect, ive rooted an unrooted many times and never had a problem with it.
It doesnt really matter if you uninstall the app chances are it just wont work after root.
And im not really sure now... there are developers for s6 edge still but ita mainly about custom ROMS. Im not sure if theres any devs still working on root. Have a good luck on here.
One thing to ask.. on settings > about device > software info.. what does it say for android security patch level?
Btw i would have a look at custom ROMS too. CarHD is an excellent rom. Comes with root and loads of extras
callumbr1 said:
Yeah mine works perfect, ive rooted an unrooted many times and never had a problem with it.
It doesnt really matter if you uninstall the app chances are it just wont work after root.
And im not really sure now... there are developers for s6 edge still but ita mainly about custom ROMS. Im not sure if theres any devs still working on root. Have a good luck on here.
One thing to ask.. on settings > about device > software info.. what does it say for android security patch level?
Btw i would have a look at custom ROMS too. CarHD is an excellent rom. Comes with root and loads of extras
Click to expand...
Click to collapse
Was 1 August 2016, but my phone has just been updated to 1 September 2016, Build: G925iDVS3EPIF. So I can assume the CF Auto Root will still work?
Thanks.
hammondegs said:
Was 1 August 2016, but my phone has just been updated to 1 September 2016, Build: G925iDVS3EPIF. So I can assume the CF Auto Root will still work?
Thanks.
Click to expand...
Click to collapse
I havnt heard of any times it doesn't work. You can always flash unikernel through twrp and install supersu. Theres 2 ways to do it
Have a read on here. Not sure if the september security patch affects anything.
callumbr1 said:
I havnt heard of any times it doesn't work. You can always flash unikernel through twrp and install supersu. Theres 2 ways to do it
Have a read on here. Not sure if the september security patch affects anything.
Click to expand...
Click to collapse
CF Auto Root looks a lot easier to install than the TWRP method. There are so many threads here about howto install, yet am confused which way to go.
Looks like no matter which I choose, Knox will be tripped even with a custom ROM installed.
All I really want to do is edit the hosts file to circumvent ads.
I have downloaded CarHDRom_V.24.7_4DPGW.zip and will eventually install it. I have read the procedure, but I don't understand why I would flash a stock firmware over my current stock firmware before flashing CarHDRom on to the phone, and the author's grammar is a little hard to comprehend... ergo if you have a link that spells it out in plain english for an old man, I would greatly appreciate it.
Thanks.
hammondegs said:
CF Auto Root looks a lot easier to install than the TWRP method. There are so many threads here about howto install, yet am confused which way to go.
Looks like no matter which I choose, Knox will be tripped even with a custom ROM installed.
All I really want to do is edit the hosts file to circumvent ads.
I have downloaded CarHDRom_V.24.7_4DPGW.zip and will eventually install it. I have read the procedure, but I don't understand why I would flash a stock firmware over my current stock firmware before flashing CarHDRom on to the phone, and the author's grammar is a little hard to comprehend... ergo if you have a link that spells it out in plain english for an old man, I would greatly appreciate it.
Thanks.
Click to expand...
Click to collapse
Cf autoroot is the easiest just flash through odin.
Do you need step by step instructions?
For CarHD rom all you do is flash through twrp it is very easy.
You must root first before flashing.
Do you want instructions?
callumbr1 said:
Cf autoroot is the easiest just flash through odin.
Do you need step by step instructions?
For CarHD rom all you do is flash through twrp it is very easy.
You must root first before flashing.
Do you want instructions?
Click to expand...
Click to collapse
I find the CF Auto Root option easy as I have used Odin before with an S2 & S4. I am just paranoid with this phone, as to remove the battery from the Edge isn't easy.
I figure I will go the CF Auto Root method first, then CarHD.
My problem with TWRP is I have read some people have had issues when it came to swipe to load, (or words to that affect).
So a clear cut procedure of TWRP and CarHD install, will be greatly appreciated if you have the time.
Thanks again. :good:
hammondegs said:
I find the CF Auto Root option easy as I have used Odin before with an S2 & S4. I am just paranoid with this phone, as to remove the battery from the Edge isn't easy.
I figure I will go the CF Auto Root method first, then CarHD.
My problem with TWRP is I have read some people have had issues when it came to swipe to load, (or words to that affect).
So a clear cut procedure of TWRP and CarHD install, will be greatly appreciated if you have the time.
Thanks again. :good:
Click to expand...
Click to collapse
Right so first thing, download the autoroot for your g925i
https://autoroot.chainfire.eu
Download TWRP
https://dl.twrp.me/zerolte/
Make sure CarHD 24.7 is saved to your device.
1st thing to do back up your stuff.
Open odin. V3.10.6 works best.
Boot to download mode.
Flash TWRP through odin in AP. Make sure auto reboot and f reset time are checked. Repartition unchecked. Same options for cf autoroot.
Once complete boot into twrp recovery and swipe to make modifications.
Once done you can click back up and backup your stuff, or you can make a full nandroid backup, this will backup absolutely everything including the current rom your using, data, settings. I reccomend this.
Boot back into download mode.
Now flash cf autoroot through AP in odin. Unzip the zip before placing in odin.
Once complete and you have the pass screen phone will reboot. 1st boot can take a few minutes and can bootloop a few times this is normal. Once phone back on, download root checker from playstore just to verify root is done.
https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck
If root is succesful i would 100% reccomend backing up your efs partition. This will backup your IMEI. Loss of imei is the worst thing and can rarely be revived.
Use partitions backup app to back it up.
https://play.google.com/store/apps/details?id=ma.wanam.partitions
Once efs is backed up transfer it to a safe place not on the phone, on a memory stick or pc or somewhere safe. If its on the phone you may not be able to get it should you need it. Chances are you wont ever need it but its just to be safe. I see people always on here trying to fix there phone because efs has corrupted.
If all this is fine so far power off phone. Boot back into recovery.
In TWRP click install, navigate to the saved CarHD rom and swipe ro flash.
Once the installer comes on make sure to choose full wipe. 1st time you have to start from fresh. Once prompted choose arter97 kernel for your phone model. Then the installer will do the rest.
Again once its done select reboot device. The 1st boot can take a while, like up to 20-30 minutes as it has a lot to install to the phone. If it sticks on the samsung logo just leave it a while.
After all this you will have CarHD and rooted phone.
Once again make sure you are 100% before trying anything! Everything you do is at your own risk.
Any problems or anything you want to know let me know
Awsome Thankyou very much!
callumbr1 said:
If root is succesful i would 100% reccomend backing up your efs partition. This will backup your IMEI. Loss of imei is the worst thing and can rarely be revived.
Use partitions backup app to back it up.
Click to expand...
Click to collapse
I don't like the sound of this, what causes corruption of the EFS partition?
hammondegs said:
Awsome Thankyou very much!
I don't like the sound of this, what causes corruption of the EFS partition?
Click to expand...
Click to collapse
A few things can cause it. Even updating software OTA officially can cause it. Just back it up to be safe mate. I always do but ive never had to use it.
callumbr1 said:
Right so first thing, download the autoroot for your g925i
https://autoroot.chainfire.eu
Download TWRP
https://dl.twrp.me/zerolte/
Make sure CarHD 24.7 is saved to your device.
1st thing to do back up your stuff.
Open odin. V3.10.6 works best.
Boot to download mode.
Flash TWRP through odin in AP. Make sure auto reboot and f reset time are checked. Repartition unchecked. Same options for cf autoroot.
Once complete boot into twrp recovery and swipe to make modifications.
Once done you can click back up and backup your stuff, or you can make a full nandroid backup, this will backup absolutely everything including the current rom your using, data, settings. I reccomend this.
Boot back into download mode.
Now flash cf autoroot through AP in odin. Unzip the zip before placing in odin.
Once complete and you have the pass screen phone will reboot. 1st boot can take a few minutes and can bootloop a few times this is normal. Once phone back on, download root checker from playstore just to verify root is done.
https://play.google.com/store/apps/d...krim.rootcheck
If root is succesful i would 100% reccomend backing up your efs partition. This will backup your IMEI. Loss of imei is the worst thing and can rarely be revived.
Use partitions backup app to back it up.
https://play.google.com/store/apps/d...nam.partitions
Click to expand...
Click to collapse
If I stop here, will I be using a rooted version of my stock OS?
hammondegs said:
Awsome Thankyou very much!
I don't like the sound of this, what causes corruption of the EFS partition?
If I stop here, will I be using a rooted version of my stock OS?
Click to expand...
Click to collapse
Yes you will have stock firmware rooted :good:
callumbr1 said:
Yes you will have stock firmware rooted :good:
Click to expand...
Click to collapse
Okay, I now have my thick head around this. All I need now is to overcome the paranoia of messing with a new phone
I Thankyou for your time and patience.
Cheers!:good:
This is for the Sprint SM-T587P "gtaxlqltespr" Galaxy Tab A 10.1 variant only.
As far as I can tell, the Nougat update came out for the Sprint Variant sometime around the 20th of September 2017. Update to the T587PVPU1BQI1 Nougat update if you have not already.
1. Read all instructions, there are no known issues. Be on 7.0.0 official. (QI1)
2 Enable Developer Options. Settings, About Device, Software info, tap on build number until it is enabled.
3. Enable OEM unlock and USB Debugging in the Developer Options menu.
There are a couple options here. You can do any combination of the following:
install TWRP
root via superuser (requires installing TWRP)
disable dm-verity (requires installing TWRP)
root by flashing magisk patched bootimage (does not require TWRP)
disable force-encryption (requires installing twrp)(required if you want TWRP to see /data/ files)(not required for flashing zips such as superuser through TWRP)
To install TWRP:
1. Boot into download mode
2. Launch ODIN, Uncheck "Auto Reboot" in the options tab. Flash included TWRP file in the AP section of ODIN.
To Disable Force-Encryption (if want to see /data/ in twrp)
1. Install TWRP recovery
2 Boot into TWRP recovery
3. Format Data
4. Reboot into TWRP from TWRP reboot menu, without rebooting into system.
5. Flash the included superuser.zip to disable force-encryption and dm-verity
To Root via superuser or disable dm-verity
1. Install TWRP recovery.
2. Boot into TWRP recovery
3. flash superuser.zip (this needs to be done with ADB if you have not disabled force-encryption and are unable to see /data/)
Superuser root provided as-is. Magisk is the recommended root. If you prefer the outdated, beta, un-updatable phh superuser binary which breaks safetynet that's all you. However it is the only way i have found to disable dm-verity.
Magisk v16 root:
Device is stock
If you have not installed twrp, disabled dm-verity, or disabled force encryption:
1. Boot into Download Mode
2. Use the AP section of ODIN to install "fe-dm-patched_boot.img.tar"
Disabled dm-verity, but NOT force-encryption
If you did not format DATA in TWRP and have installed superuser.zip using ADB:
1. Boot into Download Mode
2. Use the AP section of ODIN to install "fe-patched_boot.img.tar"
Disabled Both
If you disabled dm-verity AND disabled force-encryption:
1. Boot into Download Mode
2. Use the AP section of ODIN to install "Magiskv16_patched_boot.img.tar"
WIFI IS NOW WORKING AFTER ROOT/BOOT PATCH
Recovery: twrp-3.1.1-0-gtaxlqltespr.tar
phh's Superuser.zip
fe-dm-patched_boot.img.tar
fe-patched_boot.img.tar
Magiskv16_patched_boot.img.tar
Magisk Manager 5.6.1(105)
XposedInstaller_3.1.4_Magisk.apk
Stock 7.0.0 boot image
Stock 7.0.0 Recovery
phh's Superuser
Nougat Firmware
AP
BP
CP
CSC
Gonna try it now!!! Been waiting for along time.... thanks
Sent from my Sprint Samsung Galaxy Note5 using XDA Labs
THANK YOU!!!!!! this is working great so far. the only question i have is ......have you found a way to get the hotspot/wifi working yet?
any chance you have the stock firmware? sammobile doesnt have it, i may or may not have bricked my device>>>>>>> oops,
T587P need stock firmware and recovery
Hey Guys, I tryed this for the heck of it I thought i may be able to get wifi working but it said i wasnt rooted either , TWRP worked fine but now i did something and i am on tablet but no longer have recovery..but i can get into tablet and boot but have no wifi... does anyone have T587P stock firmware and recovery stock recovery? I just want to flash it back to stock firmware and recovery until someone can come up with a proper root and all where everything works as it should....any help for this , I would be grateful.. I need to get recovery back on here and my wifi working ...PLEASE... Thanks guys for everything
Ok what i did being i just didnt have recovery and wifi , i restored the tablet in samsung smart switch now everything works again as it should..i will hold out until we have a safe root for our T587P devices. Thank you
follow the link below to get back to 100% stock!!! i had to pay for this and i dont wanna see anyone else pay for it. so please let everyone know that they can find it here.
this is for sprint model SM-T587P . you must extract files , then flash with odin......
https://www.mediafire.com/file/88fljatrjrhs5nh/T587PVPU1AQB1_6.0.1_4File_USA (Sprint).7z
---------- Post added at 09:51 PM ---------- Previous post was at 09:51 PM ----------
follow the link below to get back to 100% stock!!! i had to pay for this and i dont wanna see anyone else pay for it. so please let everyone know that they can find it here.
this is for sprint model SM-T587P . you must extract files , then flash with odin......
https://www.mediafire.com/file/88fljatrjrhs5nh/T587PVPU1AQB1_6.0.1_4File_USA (Sprint).7z
Any updates on WiFi fix?
Flash the latest Supersu beta V2.82 sr4. That should give root and no issues with wifi.
Also note to the author. You should post the device this post refers to as there are several Tab A devices.
Rpartin04 said:
THANK YOU!!!!!! this is working great so far. the only question i have is ......have you found a way to get the hotspot/wifi working yet?
Click to expand...
Click to collapse
A stock kernel has to be built from source.
Rpartin04 said:
any chance you have the stock firmware? sammobile doesnt have it, i may or may not have bricked my device>>>>>>> oops,
Click to expand...
Click to collapse
It is linked to in the original post. EDIT. I posted the wrong link originally, i didnt realize it was behind a paywall. http://gsm-firmware.com/index.php?a=browse&b=category&id=8259
DavidBeckett.db said:
Hey Guys, I tryed this for the heck of it I thought i may be able to get wifi working but it said i wasnt rooted either , TWRP worked fine but now i did something and i am on tablet but no longer have recovery..but i can get into tablet and boot but have no wifi... does anyone have T587P stock firmware and recovery stock recovery? I just want to flash it back to stock firmware and recovery until someone can come up with a proper root and all where everything works as it should....any help for this , I would be grateful.. I need to get recovery back on here and my wifi working ...PLEASE... Thanks guys for everything
Click to expand...
Click to collapse
I didnt realize the firmware was behind a paywall, the correct link has been posted.
This is a proper root via the magisk patched boot. There is no reason to flash the recovery at all.
Rpartin04 said:
follow the link below to get back to 100% stock!!! i had to pay for this and i dont wanna see anyone else pay for it. so please let everyone know that they can find it here.
this is for sprint model SM-T587P . you must extract files , then flash with odin......
https://www.mediafire.com/file/88fljatrjrhs5nh/T587PVPU1AQB1_6.0.1_4File_USA (Sprint).7z
---------- Post added at 09:51 PM ---------- Previous post was at 09:51 PM ----------
follow the link below to get back to 100% stock!!! i had to pay for this and i dont wanna see anyone else pay for it. so please let everyone know that they can find it here.
this is for sprint model SM-T587P . you must extract files , then flash with odin......
https://www.mediafire.com/file/88fljatrjrhs5nh/T587PVPU1AQB1_6.0.1_4File_USA (Sprint).7z
Click to expand...
Click to collapse
Anyone who doesnt read the first post closely enough to locate locate the stock firmware being made to pay for it seems like a form of natural selection. Edit: or that would be the case were this the case, however, i posted the wrong link in the OP ( i had visited a lot to find the firmware, i misremembered which one was correct.)
ashyx said:
Flash the latest Supersu beta V2.82 sr4. That should give root and no issues with wifi.
Also note to the author. You should post the device this post refers to as there are several Tab A devices.
Click to expand...
Click to collapse
Is the device not clerarly labeled in the thread title as the sprint only sm-t587p gtaxlqltespr?
Should work or does? You're right, there are many tab a variants, and unlike the ones you develop for, this variant is a snapdragon 625. While you say su 2.82 should work, you would also think 2.72 would work. Bootloop. I included a working su to flash standalone that DOES work in my op for people who do not care about systemless magisk, which is the recommended root at any rate.
arlyn said:
It is linked to in the original post. EDIT. I posted the wrong link originally, i didnt realize it was behind a paywall. http://gsm-firmware.com/index.php?a=browse&b=category&id=8259
Click to expand...
Click to collapse
This as well is not a free deal. It would help out a ton if you just link these files to your account via Google drive, mediafire, ect....
EDIT!!!!
I didn't scroll all the way down... ignore me
arlyn said:
Is the device not clerarly labeled in the thread title as the sprint only sm-t587p gtaxlqltespr?
Should work or does? You're right, there are many tab a variants, and unlike the ones you develop for, this variant is a snapdragon 625. While you say su 2.82 should work, you would also think 2.72 would work. Bootloop. I included a working su to flash standalone that DOES work in my op for people who do not care about systemless magisk, which is the recommended root at any rate.
Click to expand...
Click to collapse
Did you edit it? If not must be going blind.
Any custom kernels made for this model?
Or anyone found source code for this model?
EDIT!!
I really wish my xda-labs would alert me when the op edits the thread. I also found that source code, I have been trying to compile the kernel as well. very new on this end of development. I give it a whirl
Rpartin04 said:
Any custom kernels made for this model?
Or anyone found source code for this model?
EDIT!!
I really wish my xda-labs would alert me when the op edits the thread. I also found that source code, I have been trying to compile the kernel as well. very new on this end of development. I give it a whirl
Click to expand...
Click to collapse
Haha, I didn't realize you had to subscribe to your own threads, I didn't know people were even replying in here for weeks. Thank you for attempting to compile, i know there are some tutorials on xda, i'm pretty sure an flashing an SELinux permissive kernel will fix the wifi issue with the magisk root. I do not know that I'll ever have the time or motivation to compile it myself, but I can help to test.
Thanks arlyn! Will definitely be trying this out.
Says root is not properly installled.... any ideas? I followed directions to a T... even flashed back to stock nougat and tried a 2nd time...
I'd like to keep this simple. I tried rooting and not a single tutorial on here has ended with root privileges for various reasons. I'm done with it. I flashed stock firmware in hopes of removing any trace of files that may have been altered during the various root tutorials I followed, but Samsung Pass says the device is still rooted.
What do I need to do to return to 100% stock?
noxarcana said:
I'd like to keep this simple. I tried rooting and not a single tutorial on here has ended with root privileges for various reasons. I'm done with it. I flashed stock firmware in hopes of removing any trace of files that may have been altered during the various root tutorials I followed, but Samsung Pass says the device is still rooted.
What do I need to do to return to 100% stock?
Click to expand...
Click to collapse
I assume you unlocked the bootloader. Try Relocking and flash the firmware again.
Weather that will work is anybodys guess.
Rooting is a pretty simple procedure I can't think of any reason it didn't work except user error.
This method works perfectly on T860.
***********************
https://forum-xda--developers-com.c...-to/root-guide-t860-root-twrp-method-t4095677
jhill110 said:
I assume you unlocked the bootloader. Try Relocking and flash the firmware again.
Weather that will work is anybodys guess.
Rooting is a pretty simple procedure I can't think of any reason it didn't work except user error.
Click to expand...
Click to collapse
Well, this isn't the first time I've rooted a device and I followed every step of every tutorial I found on here and, for some reason, it would not root. This is the first, and only, device I've had this much trouble with.
The tutorial for rooting without TWRP: I made the patched AP file and flashed it; however, I could not boot into recovery or download mode and it always stuck on the boot logo.
The tutorial for installing TWRP didn't have a link for the encryption disabler and the one I found did absolutely nothing and the folders in storage just showed as a string of numbers and letters.
Maybe, if someone could put together a full tutorial with the files being used within the tutorial, it would have worked.
noxarcana said:
Well, this isn't the first time I've rooted a device and I followed every step of every tutorial I found on here and, for some reason, it would not root. This is the first, and only, device I've had this much trouble with.
The tutorial for rooting without TWRP: I made the patched AP file and flashed it; however, I could not boot into recovery or download mode and it always stuck on the boot logo.
The tutorial for installing TWRP didn't have a link for the encryption disabler and the one I found did absolutely nothing and the folders in storage just showed as a string of numbers and letters.
Maybe, if someone could put together a full tutorial with the files being used within the tutorial, it would have worked.
Click to expand...
Click to collapse
Did you get the bootloader unlocked?
Unlocking the bootloader:
https://www.getdroidtips.com/how-to...to_Unlock_Bootloader_on_Samsung_Galaxy_Tab_S6
To get to download mode it's volume up and volume down then plug your pc into device. NOT POWER AND VOLUME DOWN. This can be a pain in the back side.
If you do it this way you'll get the option unlock / lock bootloader or go to bootloader mode.
If you follow the instructions perfectly and then follow the instructions for rooting it will work.
Move on to root.
ROOTING :
https://forum-xda--developers-com.c...-to/root-guide-t860-root-twrp-method-t4095677
AP SLOT = PATCHED FILE
BL SLOT = BL FILE
CP SLOT = CP FILE (T865) NOT T860... T860 HAS NO CP FILE
CSC SLOT =HOME CSC FILE
DON'T forget to setup WiFi before installing magisk manager. ^^^^^^^^^
Install TWRP.
TWRP :
https://forum-xda--developers-com.c...b-s6/development/recovery-twrp-3-3-1-t3975587
I hope this helps you out.
If you have anymore questions just ask.
Disable DM VERITY ENCRIPTION DISABLER
PATCHED ODIN
jhill110 said:
Did you get the bootloader unlocked?
Click to expand...
Click to collapse
Yep, bootloader unlock was easy. I'll give root another try with your steps in a couple of days when I'm off work. Sorry if I came across a bit aggressive in my previous posts; I have a tendency to do so even when I'm not frustrated.
This has been so frustrating to me because I know rooting is usually a simple process; as you said previously.
jhill110 said:
ROOTING :
https://forum-xda--developers-com.c...-to/root-guide-t860-root-twrp-method-t4095677
AP SLOT = PATCHED FILE
BL SLOT = BL FILE
CP SLOT = CP FILE (T865) NOT T860... T860 HAS NO CP FILE
CSC SLOT =HOME CSC FILE
DON'T forget to setup WiFi before installing magisk manager. ^^^^^^^^^
Click to expand...
Click to collapse
So, yea, I'm a bit late getting around to this. Sorry.
This is where things get hung up. Everything flashes just fine and I can even get into TWRP; however, when I try to boot the tablet i get the Galaxy Tab S6 screen, then the warning about the bootloader being unlocked, and back to the Galaxy Tab S6 screen but with a "unofficial software" warning....and repeat. It just boot loops and this is where I've since I started this thread.
Also, returning to stock doesn't completely remove root traces as I can't use Samsung Pass and I simply get a warning about the device seemingly being rooted even though it isn't.
If you installed TWRP, then you tripped Knox tripping Knox will permentally disable Samsung Pay as far as I'm aware. You'll never get it back, regardless of root or no root access.
Also, I'm not sure why you're installing TWRP AND trying to flash a Magisk patched OS. It's one or the other, you don't need to do both. Unless something has changed in Android 10?
If you're flashing TWRP, you just need to flash Magisk in TWRP(along with the other files!), no need to patch AP.
bartleby999 said:
If you installed TWRP, then you tripped Knox tripping Knox will permentally disable Samsung Pay as far as I'm aware. You'll never get it back, regardless of root or no root access.
Also, I'm not sure why you're installing TWRP AND trying to flash a Magisk patched OS. It's one or the other, you don't need to do both. Unless something has changed in Android 10?
If you're flashing TWRP, you just need to flash Magisk in TWRP(along with the other files!), no need to patch AP.
Click to expand...
Click to collapse
Not Samsung Pay, I couldn't care less about that, but Samsung Pass; I guess it looks for knox being tripped now too. That sucks, but I'll make do without it.
I was following the guides posted above. The root guide said to flash a Magisk patched OS and then there was a guide for installing TWRP. I never had this many issues or this much confusion with my 1st gen Tab S; maybe I just haven't kept as close of an eye on these things since I've been without a tablet for awhile before getting the Tab S6.
Anyway, for clarification, all I need to do is flash TWRP and then flash magisk from within TWRP? Or, just install the magisk apk after booting into Android?
noxarcana said:
Not Samsung Pay, I couldn't care less about that, but Samsung Pass; I guess it looks for knox being tripped now too. That sucks, but I'll make do without it.
I was following the guides posted above. The root guide said to flash a Magisk patched OS and then there was a guide for installing TWRP. I never had this many issues or this much confusion with my 1st gen Tab S; maybe I just haven't kept as close of an eye on these things since I've been without a tablet for awhile before getting the Tab S6.
Anyway, for clarification, all I need to do is flash TWRP and then flash magisk from within TWRP? Or, just install the magisk apk after booting into Android?
Click to expand...
Click to collapse
My bad for some reason I just read that as Samsung Pay. But yeah Samsung Pass also doesn't work with root, I'm not sure if that is permanent though as I've never used Samsung Pass, but did come across this thread https://forum.xda-developers.com/general/rooting-roms/samsung-pass-knox-tripped-devices-t3687977 it is possible to get some components of Knox to function again, (I have a working Secure Folder) so might be worth taking a look.
As for you question...
You should give this thread a good read... https://forum.xda-developers.com/galaxy-tab-s6/development/recovery-twrp-3-3-1-t3975587
Basic steps are... Unlock the bootloader and then boot into system and ensure it's unlocked in settings. You may need to connect to the web, I can't remember tbh
First you need to install TWRP, once that is done you need to reboot but YOU HAVE TO boot directly back into TWRP. You cannot boot into system, or TWRP will be overwritten by stock recovery and you'll need to start over again. Once TWRP is installed, boot into TWRP and format data then reboot recovery, flash Kernel then flash encryption disabler then unmount the system and flash Magisk 20.4 - Finally reboot to system.
I'd seriously and strongly suggest reading that TWRP thread to ensure things go smoothly.
bartleby999 said:
First you need to install TWRP, once that is done you need to reboot but YOU HAVE TO boot directly back into TWRP. You cannot boot into system, or TWRP will be overwritten by stock recovery and you'll need to start over again. Once TWRP is installed, boot into TWRP and format data then reboot recovery, flash Kernel then flash encryption disabler then unmount the system and flash Magisk 20.4 - Finally reboot to system.
I'd seriously and strongly suggest reading that TWRP thread to ensure things go smoothly.
Click to expand...
Click to collapse
I'll give those threads a thorough reading over tonight and tomorrow night while at work and then see if I can get this all sorted out Monday when I'm off. I remember Pass still working with root on the original Tab S so I'm hoping it hasn't changed.
Thanks for jumping in to try and help me with this. I'll update within a few days instead of months like my last update. ?
noxarcana said:
I'll give those threads a thorough reading over tonight and tomorrow night while at work and then see if I can get this all sorted out Monday when I'm off. I remember Pass still working with root on the original Tab S so I'm hoping it hasn't changed.
Thanks for jumping in to try and help me with this. I'll update within a few days instead of months like my last update. ?
Click to expand...
Click to collapse
It has definitely changed. Pass doesn't work on my Tab S6 and I'm rooted, I guess Knox is now integrated with alot of Samsung apps now. Not sure if it's possible or not to get it working again though, I've never bothered to research it as I don't need it for anything - But as I said, I got Secure Folder working again, so there's some hope for Pass I guess - That first thread I linked looked promising, but I only skimmed it, because frankly I'm not interested.
If you need anymore help, report back -I'll try my best. Also, the TWRP thread I linked is full of helpful people. :good:
bartleby999 said:
It has definitely changed. Pass doesn't work on my Tab S6 and I'm rooted, I guess Knox is now integrated with alot of Samsung apps now. Not sure if it's possible or not to get it working again though, I've never bothered to research it as I don't need it for anything - But as I said, I got Secure Folder working again, so there's some hope for Pass I guess - That first thread I linked looked promising, but I only skimmed it, because frankly I'm not interested.
If you need anymore help, report back -I'll try my best. Also, the TWRP thread I linked is full of helpful people. :good:
Click to expand...
Click to collapse
Perhaps I'm just not meant to have root with this device. Flashing that kernel causes Wifi not to work, but it does boot. Not flashing the kernel also booted, but I couldn't install Magisk Manager. Other than the bootloader still being unlocked, I'm back on stock firmware.
noxarcana said:
Perhaps I'm just not meant to have root with this device. Flashing that kernel causes Wifi not to work, but it does boot. Not flashing the kernel also booted, but I couldn't install Magisk Manager. Other than the bootloader still being unlocked, I'm back on stock firmware.
Click to expand...
Click to collapse
What firmware are you running?
I remember seeing something about one of the newer Kernels effecting WIFI on Android 10. Assume you're running that?
If that's the case, give the TWRP thread a browse - You maybe able to find an older version of the Kernel that'll work - As far as I'm aware, an older Kernel than what you currently installed will work, but a newer version than currently installed will possibly cause bootloop.
I can't help much with Android 10 specific stuff as I'm still running Android 9 because it's stable.
bartleby999 said:
What firmware are you running?
I remember seeing something about one of the newer Kernels effecting WIFI on Android 10. Assume you're running that?
If that's the case, give the TWRP thread a browse - You maybe able to find an older version of the Kernel that'll work - As far as I'm aware, an older Kernel than what you currently installed will work, but a newer version than currently installed will possibly cause bootloop.
I can't help much with Android 10 specific stuff as I'm still running Android 9 because it's stable.
Click to expand...
Click to collapse
I am definitely on the latest Android 10 update so I'll see if I can find an earlier version that will work. I'll see what I can find out on the TWRP thread.
noxarcana said:
I am definitely on the latest Android 10 update so I'll see if I can find an earlier version that will work. I'll see what I can find out on the TWRP thread.
Click to expand...
Click to collapse
If you can't find an older Kernel (I'm not sure there is one for Android 10), it may be the case that you'll need to wait for the Kernel to be updated.
bartleby999 said:
If you can't find an older Kernel (I'm not sure there is one for Android 10), it may be the case that you'll need to wait for the Kernel to be updated.
Click to expand...
Click to collapse
Yea, it looks like Samsung made some "wifi improvements" in OneUI 2.5 and that's causing some kernel issues preventing wifi from working. I think I could find a kernel fairly easily, but I think I'm just going to wait for a kernel update. If it never comes, I'll find an older kernel. Thanks for the help!