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...
Related
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.
Mods delete.
Unfortunately this won't happen. Had alot of trouble compiling the rom and deciding to sell it. Not much going on for my particular model anyway (G530T) and no guarantee the rom would work for other devices anyway.
On to the next one. Sorry guys and good luck
whats the catch? we need one to start custom roms and stuff.. and would it work for an SM-S920l Grand Prime?
I just want a custom recovery for the SM-S920L. I did manage to get adb shell working on the stock recovery but haven't figured out how to get an insecure adb binary to be picked up and used so no root.
xSpartacusx said:
whats the catch? we need one to start custom roms and stuff.. and would it work for an SM-S920l Grand Prime?
Click to expand...
Click to collapse
Not sure what you mean by "catch". In theory, the software should be the same for all Galaxy Grand Prime models? This is the only thing I would be modifying. I understand the kernel/baseband is different between devices (whether through reason of network, region or chipset variences) but the base software should be almost exactly the same across devices and therefore no kernels or basebands would be altered. I would obviously need willing participants to test on their personal devices throughout the development process and be able to provide logs and feedback on bug reports, but as this is supposed to only modify the software and applications I can't really forsee many issues.
That being said, I only own the 530T variant of the Grand Prime and cannot guarantee that EVERY model will accept the rom upon initial release. My team and I will valiantly make every effort to support as many Primes as possible so long as appropriate feedback from the community is gathered.
As I mentioned in the OP, I can just as well provide a tutorial of sorts to guide users along the path to modifying their device on their own. If a full blown rom isn't of much interest since all of the modifications can be done at will, we won't bother. We only look to simplify the process and hope to gain a reputation for doing so
bfoos said:
I just want a custom recovery for the SM-S920L. I did manage to get adb shell working on the stock recovery but haven't figured out how to get an insecure adb binary to be picked up and used so no root.
Click to expand...
Click to collapse
Unfortunate as flashing a custom rom (be it modified stock or otherwise) would require both root and a custom recovery. One of our members has experience building and porting recoveries, but only to devices they have had on hand
My device is rooted, I'm speaking of getting adb root working on the stock recovery which only supports adb sideload. I did manage to get adb shell working, but like I said, if I try and replace the stock adbd binary with an insecure version, the recovery won't pick it up.
by catch, i mean will it cost us anything to get it? etc. etc. and can i contribute to the developement of my grand prime? of like a stock rom or whatever..?
yes please!!!!
xSpartacusx said:
by catch, i mean will it cost us anything to get it? etc. etc. and can i contribute to the developement of my grand prime? of like a stock rom or whatever..?
Click to expand...
Click to collapse
This development is entirely on our own time with our own resources. We will never openly ask for money to make something happen. This is a passion, not a business prospect. We do this because we want to. If you'd like to support to the cause by means of monetary or physical device donations so that we may continue to expand our list of supported devices, we won't say no. It's of your own will to do so
i dont have money to send nor a device to give.. would giving you my kernel help in any way to make a stock rom for SM-S920l? or a stock recovery?
xSpartacusx said:
i dont have money to send nor a device to give.. would giving you my kernel help in any way to make a stock rom for SM-S920l? or a stock recovery?
Click to expand...
Click to collapse
It wouldn't hurt. It would also be useful to have something like a TWRP/CWM backup of ONLY the stock system, kernel, data partitions and stock recovery of as many variants as possible so we can ensure support for specific models where needed, provided you have the means to do so (root and custom recovery obviously). This would require a factory reset of your device or an Odin restore. We don't want or need any personal information you have on your phone. It's absolutely imperative that we get a fresh untouched image of the device. Its kind of a backdoor way of getting the information we need pertaining to each device, but obviously it does require some sort of recovery to get even that far. I can attempt to build from my current personal setup and that would allow feedback from others on the stability of flashing and report any and all issues.
Sound complicated? You have no idea lol
bfoos said:
My device is rooted, I'm speaking of getting adb root working on the stock recovery which only supports adb sideload. I did manage to get adb shell working, but like I said, if I try and replace the stock adbd binary with an insecure version, the recovery won't pick it up.
Click to expand...
Click to collapse
I personally don't have much experience in recovery modifications or obtaining such permissions from them but we do have a team member who may. How far his knowledge extends into the subject is beyond me. I just build the roms and do most of the PR stuff on the forums
dragonhart6505 said:
It wouldn't hurt. It would also be useful to have something like a TWRP/CWM backup of ONLY the stock system, kernel, data partitions and stock recovery of as many variants as possible so we can ensure support for specific models where needed, provided you have the means to do so (root and custom recovery obviously). This would require a factory reset of your device or an Odin restore. We don't want or need any personal information you have on your phone. It's absolutely imperative that we get a fresh untouched image of the device. Its kind of a backdoor way of getting the information we need pertaining to each device, but obviously it does require some sort of recovery to get even that far. I can attempt to build from my current personal setup and that would allow feedback from others on the stability of flashing and report any and all issues.
Sound complicated? You have no idea lol
Click to expand...
Click to collapse
ok um TWRP doesnt support the grand prime,, only the grand prime VE, which is completely different, and the CWM doesnt support the grand prime at all, either variants. i tried downloading odin.. and it wouldnt work (likeit wouldnt install)
but heres my kernel: https://www.dropbox.com/s/pv96mgsp9uqgo27/kernel-from-24-11-2015-4-18.img?dl=0
and STock recovery..: https://www.dropbox.com/s/hmdgsot6x6aybcl/stock recovery.img?dl=0
and if im wrong about the suppot for this device on either of those, please tell me and show me how to get a custom recovery from them...
xSpartacusx said:
ok um TWRP doesnt support the grand prime,, only the grand prime VE, which is completely different, and the CWM doesnt support the grand prime at all, either variants. i tried downloading odin.. and it wouldnt work (likeit wouldnt install)
but heres my kernel: https://www.dropbox.com/s/pv96mgsp9uqgo27/kernel-from-24-11-2015-4-18.img?dl=0
and STock recovery..: https://www.dropbox.com/s/hmdgsot6x6aybcl/stock recovery.img?dl=0
and if im wrong about the suppot for this device on either of those, please tell me and show me how to get a custom recovery from them...
Click to expand...
Click to collapse
Doesn't support the Grand Prime at all? I've flashed both CWM and TWRP with no issues. I have currently TWRP installed on my device (530T) but I'm not entirely sure it will support your device. It's not my development so no guarantees
Here's the thread I used:
http://forum.xda-developers.com/grand-prime/development/custom-recovery-twrp-2-8-7-0for-lollipop-t3190351
It says only for 530H, I know. But have you tried? I used RASHR from the Play Store to get it on mine. RASHR will also allow you to backup your current recovery in case the flash doesn't take. I recommend doing that first
dragonhart6505 said:
Doesn't support the Grand Prime at all? I've flashed both CWM and TWRP with no issues. I have currently TWRP installed on my device (530T) but I'm not entirely sure it will support your device. It's not my development so no guarantees
Here's the thread I used:
http://forum.xda-developers.com/grand-prime/development/custom-recovery-twrp-2-8-7-0for-lollipop-t3190351
It says only for 530H, I know. But have you tried? I used RASHR from the Play Store to get it on mine. RASHR will also allow you to backup your current recovery in case the flash doesn't take. I recommend doing that first
Click to expand...
Click to collapse
i used rashr to get those two files but i got rom manager by CWM and TWRP manager and both didnt have the normal grand prime in them
xSpartacusx said:
i used rashr to get those two files but i got rom manager by CWM and TWRP manager and both didnt have the normal grand prime in them
Click to expand...
Click to collapse
It won't because its not "officially" supported. But neither is my 530T and I got off just fine. Try to flash the file in RASHR from the thread I linked. If it doesn't take, you've got your backup so no harm no foul
ok so i extracted the tar file using 7zip, and moved the img file into my SD card storage. i used flashify and i opened it up and cicked flash and it said successfully flashed.. and i rebooted and the phone works completely fine.. now what?
---------- Post added at 06:01 AM ---------- Previous post was at 05:59 AM ----------
wait wait wait no, it doesnt.. i did it again and hitreboot, and it says Custom Binary Blocked by reactivation lock.?
---------- Post added at 06:04 AM ---------- Previous post was at 06:01 AM ----------
help?
xSpartacusx said:
ok so i extracted the tar file using 7zip, and moved the img file into my SD card storage. i used flashify and i opened it up and cicked flash and it said successfully flashed.. and i rebooted and the phone works completely fine.. now what?
Click to expand...
Click to collapse
Have you booted into the custom recovery or did you simply reboot the phone back to the system? I ask because Flashify also told me it was successful but in reality did nothing. That's why I suggested RASHR. Flashify is hit or miss in my experience
idfk what i did.. i hit chhoose file, selected the img it says successful and i hit the reboot option it gave me, and then that came up... i never rooted a phone before i never de any flashing **** before..
---------- Post added at 06:07 AM ---------- Previous post was at 06:06 AM ----------
it says custom binary blocked by reactivation lock with a big yellow triangle on the screen
xSpartacusx said:
ok so i extracted the tar file using 7zip, and moved the img file into my SD card storage. i used flashify and i opened it up and cicked flash and it said successfully flashed.. and i rebooted and the phone works completely fine.. now what?
---------- Post added at 06:01 AM ---------- Previous post was at 05:59 AM ----------
wait wait wait no, it doesnt.. i did it again and hitreboot, and it says Custom Binary Blocked by reactivation lock.?
---------- Post added at 06:04 AM ---------- Previous post was at 06:01 AM ----------
help?
Click to expand...
Click to collapse
Try booting into download mode (vol - home and power) then select no (vol -) and should boot you into the OS?
This is a custom Rom I made for the Samsung Galaxy Tab A 7.0 LTE (SM-T285), which suits my tastes.
If you have suggestions, send me a PM.
UPDATE 09/07/2016
================
A newer version that runs "root" (sepolicy constrained) scripts can be found here:
http://forum.xda-developers.com/android/development/rom-samsung-galaxy-tab-7-0-lte-2016-sm-t3455788
Use the above version instead if you want to experiment with features like apps 2 sdcard.
Modifications:
* Based on LMY47V.T285XXU0APCN
* Stock Boot and Recovery (Not much choice since the bootloader is locked)
* Removed Touchwiz launcher and redundant samsung apps (Hancom office, Kidzone), replaced with Trebuchet
* Enabled r/w to the external SD Card
Installation Instructions:
Odin or Heimdall Required.
--FLASH AT YOUR OWN RISK--
1. Make sure to backup of your data and have a copy of your stock Rom in case something goes wrong.
2. Make sure your device is OEM unlocked. (Enable Developer settings and Enable the OEM unlock settings)
3. Extract ZIP file below and flash the tar.md5 file using ODIN, for details on this kindly look for instructions in the xda site.
4. For Heimdall you can use 7zip to extract the system.img from the tar.md5 and just flash the system.img itself.
Link:
Download from Mega
jaritico said:
thanks, but what does after download zip? recovery mode or download mode? and how got it? this root t285?
Click to expand...
Click to collapse
Thanks, but what does after download zip? recovery mode or download mode? and how got it? this root t285?
Click to expand...
Click to collapse
You have to go to download mode and then use Odin to flash. Unfortunately this does not root the T285.
jedld said:
This is a custom Rom I made for the Samsung Galaxy Tab A 7.0 LTE (SM-T285), which suits my tastes.
If you have suggestions, send me a PM.
Modifications:
* Based on LMY47V.T285XXU0APCN
* Stock Boot and Recovery (Not much choice since the bootloader is locked)
* Removed Touchwiz launcher and redundant samsung apps (Hancom office, Kidzone), replaced with Trebuchet
* Enabled r/w to the external SD Card
Installation Instructions:
Odin or Heimdall Required.
--FLASH AT YOUR OWN RISK--
1. Make sure to backup of your data and have a copy of your stock Rom in case something goes wrong.
2. Make sure your device is OEM unlocked. (Enable Developer settings and Enable the OEM unlock settings)
3. Extract ZIP file below and flash the tar.md5 file using ODIN, for details on this kindly look for instructions in the xda site.
4. For Heimdall you can use 7zip to extract the system.img from the tar.md5 and just flash the system.img itself.
Link:
Download from Mega
Click to expand...
Click to collapse
Says I need the encryption key and if I do not have it to contact the developer ......
TopTongueBarry said:
Says I need the encryption key and if I do not have it to contact the developer ......
Click to expand...
Click to collapse
Sorry, updated links, try again and see if it works.
jedld said:
Sorry, updated links, try again and see if it works.
Click to expand...
Click to collapse
Yes, downloading now. Thanks.
Hi,
Anyone tried Pokemon Go update 0.37 with this ROM? The update fails to start for me. It prompts device/os version is incompatible.
I reverted back to version 0.35 and it works fine.
venomrat said:
Hi,
Anyone tried Pokemon Go update 0.37 with this ROM? The update fails to start for me. It prompts device/os version is incompatible.
I reverted back to version 0.35 and it works fine.
Click to expand...
Click to collapse
Yeah the newest version checks for xposed and a bunch of other things. Actually a lot of people were pissed that they did this. You'd probably need to revert back to stock if you want to play. Only systemless root and xposed with magisk works for Pokemon go now.
jedld said:
Yeah the newest version checks for xposed and a bunch of other things. Actually a lot of people were pissed that they did this. You'd probably need to revert back to stock if you want to play. Only systemless root and xposed with magisk works for Pokemon go now.
Click to expand...
Click to collapse
Also if you want more details on what is going on search google for "pokemon go safetynet". Basically most custom roms and not just this device should fail the test.
jedld said:
This is a custom Rom I made for the Samsung Galaxy Tab A 7.0 LTE (SM-T285), which suits my tastes.
If you have suggestions, send me a PM.
UPDATE 09/07/2016
================
A newer version that runs "root" (sepolicy constrained) scripts can be found here:
http://forum.xda-developers.com/android/development/rom-samsung-galaxy-tab-7-0-lte-2016-sm-t3455788
Use the above version instead if you want to experiment with features like apps 2 sdcard.
Modifications:
* Based on LMY47V.T285XXU0APCN
* Stock Boot and Recovery (Not much choice since the bootloader is locked)
* Removed Touchwiz launcher and redundant samsung apps (Hancom office, Kidzone), replaced with Trebuchet
* Enabled r/w to the external SD Card
Installation Instructions:
Odin or Heimdall Required.
--FLASH AT YOUR OWN RISK--
1. Make sure to backup of your data and have a copy of your stock Rom in case something goes wrong.
2. Make sure your device is OEM unlocked. (Enable Developer settings and Enable the OEM unlock settings)
3. Extract ZIP file below and flash the tar.md5 file using ODIN, for details on this kindly look for instructions in the xda site.
4. For Heimdall you can use 7zip to extract the system.img from the tar.md5 and just flash the system.img itself.
Link:
Download from Mega
Click to expand...
Click to collapse
Hello and thank you for your work with this device. Currently I am looking for a bypass for the factory reset protection on my sm t280. I have flashed the stock md5 file 3+ times attempting to do a complete data wipe and reset, and this doesnt remove the lock. Any ideas?
BadReligion420 said:
Hello and thank you for your work with this device. Currently I am looking for a bypass for the factory reset protection on my sm t280. I have flashed the stock md5 file 3+ times attempting to do a complete data wipe and reset, and this doesnt remove the lock. Any ideas?
Click to expand...
Click to collapse
To FRP unlock you have to go to developer settings and switch oem unlock to false. The stock rom should have it unless you are using a carrier locked version that I a! not aware of.
jedld said:
To FRP unlock you have to go to developer settings and switch oem unlock to false. The stock rom should have it unless you are using a carrier locked version that I a! not aware of.
Click to expand...
Click to collapse
please excuse my ignorance, but am i able to do this with out being able to login? the person i purchased it from doesnt have the original owners gmail and pw.
---------- Post added at 05:59 PM ---------- Previous post was at 05:57 PM ----------
BadReligion420 said:
please excuse my ignorance, but am i able to do this with out being able to login? the person i purchased it from doesnt have the original owners gmail and pw.
Click to expand...
Click to collapse
I just downloaded a stock recovery for a sm t285, and was going to attempt to flash to the 280. havent yet, do you feel that would be a safe thing to attempt? not looking to brick.
BadReligion420 said:
please excuse my ignorance, but am i able to do this with out being able to login? the person i purchased it from doesnt have the original owners gmail and pw.
---------- Post added at 05:59 PM ---------- Previous post was at 05:57 PM ----------
I just downloaded a stock recovery for a sm t285, and was going to attempt to flash to the 280. havent yet, do you feel that would be a safe thing to attempt? not looking to brick.
Click to expand...
Click to collapse
FRP is specifically designed to prevent flashing if you can't login to the device. You won't be able to flash unless the person has turned off oem unlock beforehand. I am not aware of any method to bypass this on this device.
Also the T280 and T285 have slightly different hardware so using a different recovery image is not recommended. Also since both devices have a locked bootloader, I highly doubt you can even change the recoveries from stock as I would imagine samsung using different keys for both. At the worst case it still always possible to reflash them back to stock if you do want to try
AARGH! If I had only waited and not sold my so difficult to get SM-T285M (to TTB)....sheesh never thought there would be this much progress
bang head live and keep learning
mac231us said:
AARGH! If I had only waited and not sold my so difficult to get SM-T285M (to TTB)....sheesh never thought there would be this much progress
bang head live and keep learning
Click to expand...
Click to collapse
And thank you so much for selling it. I don't speak enough Spanish to make the ordeal of getting one of the T285M's from so america worthwhile. I was planning on sticking with my T239M for awhile, then I saw your T285M on ebay.
I've dirty flashed jedld's T285 debloated rom, then dirty flashed his T285 tinker rom on top of that. Both onto my T285M. Working flawlessly. Wished he'd kept the mail app, but without touchwiz I guess that wasn't possible.
Something else they blocked in the kernel or with SElinux on the T285M is screen mirroring. Can only cast directly from apps.
Still I am happy overall. Now looking for a castrated version of daemonsu!
TTB
TopTongueBarry said:
And thank you so much for selling it. I don't speak enough Spanish to make the ordeal of getting one of the T285M's from so america worthwhile. I was planning on sticking with my T239M for awhile, then I saw your T285M on ebay.
I've dirty flashed jedld's T285 debloated rom, then dirty flashed his T285 tinker rom on top of that. Both onto my T285M. Working flawlessly. Wished he'd kept the mail app, but without touchwiz I guess that wasn't possible.
Something else they blocked in the kernel or with SElinux on the T285M is screen mirroring. Can only cast directly from apps.
Still I am happy overall. Now looking for a castrated version of daemonsu!
TTB
Click to expand...
Click to collapse
no need for a castrated version. Full ROOT is available soon now.
http://forum.xda-developers.com/showpost.php?p=68777842&postcount=27
Double Aargh...salt on my wounds ttb
Now my contact in S. America will not even reply to me
Contemplating on getting the Samsung J max 7.0 dual sim...yes no U.S lte but has an 8mp camera and a flash...similar to the T285 otherwise...can't say how many times I needed the flash for photos or even if for looking at labels peering into dim areas behind a monitor or tv..maybe end up in same pickle of no root...will see (number is SM-T285YD so it is based off the T285 it seems-maybe a Latin American version soon?)
Also trying to get the T705M from another source but taking forever...low hopes think it will come through
TopTongueBarry said:
And thank you so much for selling it. I don't speak enough Spanish to make the ordeal of getting one of the T285M's from so america worthwhile. I was planning on sticking with my T239M for awhile, then I saw your T285M on ebay.
I've dirty flashed jedld's T285 debloated rom, then dirty flashed his T285 tinker rom on top of that. Both onto my T285M. Working flawlessly. Wished he'd kept the mail app, but without touchwiz I guess that wasn't possible.
Something else they blocked in the kernel or with SElinux on the T285M is screen mirroring. Can only cast directly from apps.
Still I am happy overall. Now looking for a castrated version of daemonsu!
TTB
Click to expand...
Click to collapse
got another one - white color ...as a gift...God Bless - great device battery life is just incredible - nothing fancy but does its job...keeping this one (had it since early November) gave up on the 705m
Is this ROM compatible with Google Safetynet? I can't seem to log into Pokemon GO since I installed Tinker edition, so I'm thinking to switch to this one instead.
Haven't tried it but it should work.
Is the root part contained in boot.img or in system.img? In other words, when using Heimdall I should flash both system.img and boot.img, isn't it?
I'm getting bootloops with CM13, Omni and I don't know how I got Tinker working, I kind of remember flashing boot.img, then wiping, then flashing system.img, then wiping again.
EDIT: got this one working too by flashing boot.img (Heimdall complains it cannot receive confirmation msg) reboot into download again, then flashing system.img (this time heimdall does reboot the phone). however, pokemon go still wont connect due to google's safetynet compliance.
I'll try flashing recovery in case it is TWRP the one clashing with Safetynet.
PD: I didn't backup stock at the beggining of the process so I'm pretty much screwed with Pokemon until I can afford a new phone. But if someone has a stock ROM for T285MUBU0API2, please ping me.
EDIT2 Got pokemon working. I reinstalled TWRP (this ROM's recovery is the stock one, of course), then flashed unSU. It removed SuperSU binary and Google SafeNet got working again. I can't believe that, after so much hours I've put into finding the best custom ROM for this crappy phone, 95% of the time was spent in trying to get Pokemon GO running. I'm close to 40, FML.
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!
My phone had been rooted via Magisk, some system update box kept coming up, but I kept tapping cancel as I didn't think it would work anyway. Yesterday, I'm not sure if it was forced or it tapped something in my pocket, but now it has installed the update, and *boom* I'm on Android 10. Build number V11.0.5.0.QFQEUXM. Root lost, everything else seems to work though. I have a notification from Magisk Manager that says update available! press to download and install.
Should I do that to regain root? Is that the safest way to do that? I have backups, but I'd rather not have to go through that faff. Thanks so much for your help! And this super useful forum! Thanks will be given also :fingers-crossed:
FR Ray said:
My phone had been rooted via Magisk, some system update box kept coming up, but I kept tapping cancel as I didn't think it would work anyway. Yesterday, I'm not sure if it was forced or it tapped something in my pocket, but now it has installed the update, and *boom* I'm on Android 10. Build number V11.0.5.0.QFQEUXM. Root lost, everything else seems to work though. I have a notification from Magisk Manager that says update available! press to download and install.
Should I do that to regain root? Is that the safest way to do that? I have backups, but I'd rather not have to go through that faff. Thanks so much for your help! And this super useful forum! Thanks will be given also :fingers-crossed:
Click to expand...
Click to collapse
The easiest way to re-root your phone is to follow the steps on this post here. However, there are no .img files for the last versions.
I need the fastboot for 11.0.19 Global
lbsilva said:
The easiest way to re-root your phone is to follow the steps on this post here. However, there are no .img files for the last versions.
I need the fastboot for 11.0.19 Global
Click to expand...
Click to collapse
The guide you mentioned in your post also contains a link in which you can extract your own boot image and use that image to patch via Magisk to obtain root.
Here is the link: DUMP stock boot.img
pkdon123 said:
The guide you mentioned in your post also contains a link in which you can extract your own boot image and use that image to patch via Magisk to obtain root.
Here is the link: DUMP stock boot.img
Click to expand...
Click to collapse
Hi thanks for the link! It looks like I will use the TWRP and Magisk method, as there is less to go wrong. But the links on that post are from 2019, so I'm guessing they are not compatible with A10. I've found this post: https://forum.xda-developers.com/showpost.php?p=82372895&postcount=139 to try to find some updated links, but the mirrors cannot be found
FR Ray said:
Hi thanks for the link! It looks like I will use the TWRP and Magisk method, as there is less to go wrong. But the links on that post are from 2019, so I'm guessing they are not compatible with A10. I've found this post: https://forum.xda-developers.com/showpost.php?p=82372895&postcount=139 to try to find some updated links, but the mirrors cannot be found
Click to expand...
Click to collapse
I used the steps from the same post for obtaining root on my stock Android 10 V11.0.14.0.QFQMIXM i.e. global version. Now I don't know whether it will work on V11.0.19 Global or not, but it should. I cannot test it now because I'm using EvolutionX Custom ROM now.