Related
Ah safetynet, the thorn in the side of every technical android user who wants to use Android Pay.
It's even worse on a xiaomi device, because once you've been granted a bootloader unlock after waiting for days, you don't want to re-lock it for fear of locking yourself out of the device and having to wait another 30 days before you can get a new unlock permission!
There is a lot of old information around about hiding root, custom kernels, installing things in particular orders and I'm pretty sure I've tried them all - including compiling kernels from scratch with a few different versions of the unlocked bootloader hiding patch.... never getting past the dreaded CTS Mismatch
But all of a sudden I happened on a little known secret found by @kyasu that the build fingerprint is also checked : https://forum.xda-developers.com/showpost.php?p=70831797&postcount=3665
Also, conveniently, Magisk (since v9) patches the ro.boot.verifiedbootstate and related props that SafetyNet checks.
This now gives us two options to enable safetynet regardless of bootloader state.
You will need either a kernel with bootloader state hidden OR magisk, as well as a method of changing the build fingerprint.
This also assumes you've got TWRP installed and are comfortable using it.
Tested on Mi5 Lineage OS 14.1-20170206-NIGHTLY-gemini and various xiamoi.eu 7.2.X and 7.3.X versions:
NOTE: Magisk Hide on MIUI currently does not work (21st July 2017)
This has been widely reported and there are a number of open issues:
https://github.com/topjohnwu/Magisk/issues?utf8=✓&q=is:issue is:open miui
A fix may have been found, not ready to test however:
https://github.com/topjohnwu/Magisk/issues/298#issuecomment-316687923
Magisk:
Remove any previous root, usually this can be done by simply dirty flashing your current rom in twrp.
From TWRP install Magisk v13.3: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Restart and Magisk Manager app should be installed.
Hit the test safetynet button in Magisk Manager, if it passes stop here! Latest lineage roms don't need my magisk fingerprint module anymore, they just work.
Otherwise, download this magisk module on your phone: https://gitlab.com/alelec/magisk-ge...2bbf9dc8/magisk-gemini-safetynet-props-v3.zip
In Magisk Manager, go to modules and install the magisk-gemini-safetynet-props zip just downloaded. It should prompt to restart to enable module, do so.
After restart, fire up Magisk Manager and "tap to start SafetyNet check", fingers crossed it comes up Green!
Note: After each rom update you will need to reinstall Magisk in twrp, but the safetynet enabling module above should stick just fine and not need reinstall.
Custom Kernel:
I don't test this as often, as I prefer the Magisk method, however this is an option for people who don't want any kind of root on their phones.
I also don't maintain any patched kernel for miui based roms as the one's I've tried are just too buggy.
Remove any previous root, usually this can be done by simply dirty flashing your current rom in twrp.
Install gemini-safetynetpass-stable-fingerprint-20170217.zip
this package is based on gemini-safetynetpass-20170213.zip by @kyasu but only changes the build prop fingerprint, the old custom kernel has been removed:
Install a patched kernel, you can either use my autobuild of a patched latest LineageOS kernel for Mi5 (includes fingerprint fix):
https://gitlab.com/alelec/android_kernel_xiaomi_msm8996/tags (LineageOS-gemini-safetynet-kernel_XXXXXX.zip links)
or recent DragonXia kernels appear to be patched
https://forum.xda-developers.com/mi-5/development/kernel-brand-kernel-cm13-alpha-1-0-t3480663 (LineageOS)
https://forum.xda-developers.com/mi-5/development/kernel-dragonxia-kernel-v1-0-t3546619 (MIUI)
Note: Both the kernel and fingerprint zip above will need to be re-installed after each rom update.
On a related note, if you want to use Android Pay on MIUI based roms, make sure the HCE wallet configuration and permissions are set correctly.
See the following for more details: http://en.miui.com/thread-405166-1-1.html
Once you unlock it once, you can unlock it again without waiting. I just unlocked and relocked my Mi5 about 3 times in a couple days.
Sent from my MI 5 using Tapatalk
Oh really? Wow, nothing I've read anywhere in the last few weeks has said that before, certainly simplifies things!
Do non stock kernels boot on a locked bootloader though? They didn't on my previous Sony.
coronafire said:
Oh really? Wow, nothing I've read anywhere in the last few weeks has said that before, certainly simplifies things!
Do non stock kernels boot on a locked bootloader though? They didn't on my previous Sony.
Click to expand...
Click to collapse
It does make it easy. I initially unlocked my bootloader to flash the global stable, then used mi flash to flash the ROM and relock my bootloader. I wasn't happy with the stable ROM, so I went back into the mi unlock tool, unlocked again, and flashed the dev ROM and relocked Then I see 8.2 is coming soon, so I went back to mi unlock and unlocked yet again so I can flash the new 8.2 when it comes out.
I'm not sure on kernels, haven't messed with them on Xiaomi devices.
Sent from my MI 5 using Tapatalk
Did anyone try this patch on MIUI?
Edit: Just tried on MIUI v7.2.9 Global Dev. CTS profile and Basic Integrity check both fails.... What a bummer...
the_poolee said:
Did anyone try this patch on MIUI?
Edit: Just tried on MIUI v7.2.9 Global Dev. CTS profile and Basic Integrity check both fails.... What a bummer...
Click to expand...
Click to collapse
Drats. If basic integrity is failing that's something else triggering the issue. Before I changed the fingerprint I only had cts failing, basic was usually fine. Sometimes a replacement kernel would cause it to fail basic, but I never narrowed down exactly what the cause was.
Works on LOS. Anyway my bank doesn't support android pay yet.
Ulver said:
It does make it easy. I initially unlocked my bootloader to flash the global stable, then used mi flash to flash the ROM and relock my bootloader. I wasn't happy with the stable ROM, so I went back into the mi unlock tool, unlocked again, and flashed the dev ROM and relocked Then I see 8.2 is coming soon, so I went back to mi unlock and unlocked yet again so I can flash the new 8.2 when it comes out.
Click to expand...
Click to collapse
Looked into it some more to confirm - I'm quite sure you can't re-lock the bootloader if using anything that's not an official xiaomi rom, ie if using lineage, or even the xiaomi.eu rom, you can't lock bootloader without having a bootloop.
And yeah, I've confimed this method doesn't work on xiaomi.eu rom 7.1.20 or 7.2.16 on mi5. It gets both failed basic integritry and failed cts profile match.
I've also tried on Global Stable 8.1.4.0 with unlocked bootloader and had no luck at all, same error.
This was a clean install, factory wipe, install magisk v11.1. Initially the check couldn't work at all, I had to get google play services updated for anything to work. Then the check operates, but fails on both counts.
I passed safety net on 8.1.2.0 global stable, but failed to add a card in Android Pay. I'm hoping 8.2 works.
Sent from my MI 5 using Tapatalk
Ulver said:
I passed safety net on 8.1.2.0 global stable, but failed to add a card in Android Pay. I'm hoping 8.2 works.
Sent from my MI 5 using Tapatalk
Click to expand...
Click to collapse
As described by @Ulver if you're on official builds, you should be able to re-lock the bootloader and avoid this issue (although without root I guess).
Aside from that, you definitely shouldn't need the zip I made for the build prop change, as you'll already have a stable build fingerprint
It turns out there's lots of versions of official rom that don't pass safetynet even when cleanly flashed with locked bootloader - xiaomi themselves keep breaking it!
A little search finds lots of references, such as this entire thread, and this post in particular: http://en.miui.com/forum.php?mod=redirect&goto=findpost&ptid=273319&pid=7515203
This certainly complicates things....
Turns out you can't always re-unlock....
To test more thoroughly I decided to flashtool wipe and lock my mi5 to stable release that's reported to pass safetynet; global_images_V8.0.2.0.MAAMIDG
My plan is to verify that it passed when locked (it did), then unlock and just install magisk to see if that worked to hide.
Well, MiUnlock has told me I can't unlock, I logged back into unlock web site and it now says my unlock request is rejected (on same account as I originally unlocked on). So now I have a locked device on global stable and have to wait for re-application to unlock.
FWIW I then allowed MIUI to OTA update itself to 8.1.2.0(MAAMIDI) and then safetynet helper originally told me no, fail on both basic and cts.
Ran it a couple more times though and now it's passing. go figure... safetynet is somewhat unreliable.
tl;dr don't re-lock your phone assuming you'll be able to immediately re-unlock it, it clearly works some of the time, not always though.
Good news, I've got SafetyNet pass on xiaomi.eu (MIUI) rom with unlocked bootloader
In the end it's basically the same as the original LOS method except that as we've all seen earlier Magisk v11.1 isn't working for MIUI.
This win was achieved with Magisk v9 and phh-superuser-magisk-r266-2 with the current Magisk Manager (4.2.6)
As per the screenshot I'm running xiaomi.eu MUIU 8.3 7.2.24 in Mi5
My procedure was:
* dirty flash rom to clean up prior attempts (Install) xiaomi.eu_multi_MI5_7.2.24_v8-7.0.zip
* Install gemini-safetynetpass-stable-fingerprint-20170217.zip
* Install Magisk-v9.zip
* Install phh-superuser-magisk-r266-2.zip
* Reboot.
Simple as that, Magisk Manager shows SafetyNet passing (after asking for root privs on first launch)
I've added a new card in Android Pay, haven't tested at a terminal yet though.
If anyone's interested I previously got SafetyNet passing on MIUI with a custom kernel instead of Magisk, this gave SafetyNet green without any kind of root.
The problem with custom kernel's at this stage is the capacitive buttons (back and app switch) have reduced sensitivity / only work well when the phone is charging. AFAIK this is only really a problem on phones with LGD lcd's (what I have), the other ones might work fine.
If anyone wants to try my kernel instead let me know and I'll share it, I found it to be a bit flaky though.
@up:
For me not working.. SafetyNet test always have CTS false.. I tried clean install and for now it's not works.
rafix96 said:
@up:
For me not working.. SafetyNet test always have CTS false.. I tried clean install and for now it's not works.
Click to expand...
Click to collapse
Which version of which rom did you try?
coronafire said:
Which version of which rom did you try?
Click to expand...
Click to collapse
I would definitely would like to confirm this on the latest miui official global dev
First i try this on 7.2.24 xiaomi.eu later i updated MIUI to 7.2.3 and unfortunately it does not working too...
rafix96 said:
First i try this on 7.2.24 xiaomi.eu later i updated MIUI to 7.2.3 and unfortunately it does not working too...
Click to expand...
Click to collapse
That's annoying, 7.2.24 is what works for me. It's been my daily driver since, and I've used android pay at a terminal no worries.
Do you definitely have Magisk v9 and phh-superuser-magisk-r266-2.zip ?
Magisk v11 cannot be installed else a dirty flash will be needed.
Oh, I just remembered I've also installed the 'phh's SuperUser' app from Play Store. This is probably needed
After that I opened Magisk Manager, which asked for root permissions the first time (which has to be granted).
@coronafire
Yes i tried everything but i have another one idea, when i come back to home i did MiFlash and then install eu 7.2.24 maybe will work.
Wysłane z mojego MI 5 przy użyciu Tapatalka
basically, if you don't need root, just flash
the latest zip in the following link (by kyasu)
https://www.androidfilehost.com/?w=files&flid=149919
will pass safetynet without locked bootloader. As they latest kernel is 2 weeks old, please consider there may be some drawback in flashing an old kernel to latest LOS build. By the way, would kyasu please update the file or let us know is there is any easy way to patch on our own?
hklam0 said:
basically, if you don't need root, just flash
the latest zip in the following link (by kyasu)
https://www.androidfilehost.com/?w=files&flid=149919
will pass safetynet without locked bootloader. As they latest kernel is 2 weeks old, please consider there may be some drawback in flashing an old kernel to latest LOS build. By the way, would kyasu please update the file or let us know is there is any easy way to patch on our own?
Click to expand...
Click to collapse
Just to note, this is only for LineageOS, not MIUI.
Personally I find it easier to not need to replace the kernel and just install magisk, if root isn't wanted it can be disabled in the magisk app.
But yes it's true you can replace the kernel with a patched one, avoiding installing any kind of root.
I've experimented with this quite a bit myself, however to update it requires at a minimum applying a patch/commit to a fork of the kernel source you're starting with and compiling it.
I've got a fork of the MIUI kernel from @Shaky156 with the appropriate patch:
https://github.com/andrewleech/Mi5-...mmit/66cbe734eb15d2508a5c80157a8af38d59373535
and example build script:
https://github.com/andrewleech/Mi5-MIUI8-Nougat-Kernel/blob/master/build.sh
Or there's the original patch by @Sultanxda which usually works as well, I did test this on a LineageOS kernel but this is pretty out of date too by now, and I started from a different forked kernel anyway.
https://github.com/andrewleech/andr...mmit/f8314c10146971979ad26c881be9bd17603c1e7d
I flashed TWRP and a custom ROM, but decided to go back to Stock whilst waiting for Magisk since Google Pay is not working (and I miss it).
Flashed a stock official ROM via ODIN, everything checked out fine.
However, even though I am now fully stock, Google Pay is still claiming my device does not meet requirements. On further investigation, Safety Net is failing due to 'CTS Profile Mismatch'.
I would have thought going back to full stock should have resolved this.
Anyone know how I can fix this?
Thanks.
+1
This is caused from rooting/installing a custom rom on your device previously. This has triggered the KNOX fuse in the device which cannot be undone. This is causing the CTS mismatch because it has ruined the integrity of the device and Google’s protection measures will see it. However, you can hide the CTS mismatch using Magisk Manager. I believe you can install this without a custom recovery from downloading the Magisk Manager and selecting the patched boot format in settings to .img.tar then go to the main menu and installing. This will then let you install Magisk in ODIN.
The issue turned out to be I flashed back to stock via ODIN before relocking the bootloader. I had to wait another 7 days for OEM Unlock to reappear, so I could actually relock the bootloader. After that, CTS Profile mismatch was False and Safety net passed once again, and Google Pay started working.
Great to hear its fixed
salada2k said:
The issue turned out to be I flashed back to stock via ODIN before relocking the bootloader. I had to wait another 7 days for OEM Unlock to reappear, so I could actually relock the bootloader. After that, CTS Profile mismatch was False and Safety net passed once again, and Google Pay started working.
Click to expand...
Click to collapse
How's about your knox? Looks like you dont care?
boydzethuong said:
How's about your knox? Looks like you dont care?
Click to expand...
Click to collapse
Correct, don't care. p.s. It's not working.
salada2k said:
The issue turned out to be I flashed back to stock via ODIN before relocking the bootloader. I had to wait another 7 days for OEM Unlock to reappear, so I could actually relock the bootloader. After that, CTS Profile mismatch was False and Safety net passed once again, and Google Pay started working.
Click to expand...
Click to collapse
Can you please explain more the process you did to restore your phone, we have exactly the same issue and need some help.
salada2k said:
The issue turned out to be I flashed back to stock via ODIN before relocking the bootloader. I had to wait another 7 days for OEM Unlock to reappear, so I could actually relock the bootloader. After that, CTS Profile mismatch was False and Safety net passed once again, and Google Pay started working.
Click to expand...
Click to collapse
This post makes absolutely no sense, quit bullshitting.
Is anyone able to pass safety net test on their mi pad 4? If so can you let me know your set up.
I've tried many different methods of installing gapps but even on stock I can't pass it. Right now I'm on stock Chinese ROM 9.6.23.0 with gapps flashed through twrp from opengaps. Every time I try to submit a safety net request it fails, and on magisk manager checking safety net status results in an error, "the response is invalid".
I've tried Google installer apk, using a mi5 backup and twrp flashing and I'm still getting the same response. If anyone has gotten their device to pass safety net please let me know the ROM you're currently running and the method you used for flashing gapps.
unlock BL and use the xiaomu.eu beta ROM, apparently it passes safetynet (as long as you don't go ahead and root as well lol)
https://xiaomi.eu/community/threads/when-will-xiaomi-eu-be-available.45622/page-2
wintermute000 said:
unlock BL and use the xiaomu.eu beta ROM, apparently it passes safetynet (as long as you don't go ahead and root as well lol)
https://xiaomi.eu/community/threads/when-will-xiaomi-eu-be-available.45622/page-2
Click to expand...
Click to collapse
I have rooted mi pad 4 with xiaomi.eu MIUI 10 developer rom and safety net passing without any problems.
Hey guys:
I did unlock bootloader unload/root according to this guide.
First Wifi worked.
Then I did try to figure out OTA issues, could not uninstall Magisk, so temporary flashed stock image back.
From here on out - no matter, if stock, or Magisk_patched image: No chance to turn WiFi on.
In the WiFi-Menu, if I touch "turn on", it will show for one second: Turning Wi-Fi on", and then just return to the WiFi off-setting...
I did do factory reset from recovery - no success, flashed again (stock and patched) - no success.
I can't figure it out! Anybody an idea?
Are you sure that you are using correct boot.img version? It must be the same version as your system - build number and EU/GB variant must match.
Yes. I did, unless I had an older Version on a different slot and somehow did change slots and started messing around there. Could be an explanation.
Got tired of messing with it. Did download the whole stock rom, flashed it and will stay "unrooted" for now. Not worth the hassle to me.
BUT: What a mess that these manufacturers make it so hard to have working and rooted phone.
My guess would be that you flashed incorrect stock boot image.
Also how come that you couldn't uninstall Magisk?
Rooting is pretty straightforward, even if Mi A3 has a slight complication with missing "fastboot boot" command support, but otherwise it's nothing special. Take the correct boot.img, patch it, flash it and you're done.
First take your phone into fastboot mode. write fastboot set_active a .unzip stock rom and you will see flash_all.bat click it and you will succesfully have brand new rom with no issue. Note:If anything bad happens or goes wrong im not responsible. Its all your decision to do it
_mysiak_ said:
My guess would be that you flashed incorrect stock boot image.
Also how come that you couldn't uninstall Magisk?
Rooting is pretty straightforward, even if Mi A3 has a slight complication with missing "fastboot boot" command support, but otherwise it's nothing special. Take the correct boot.img, patch it, flash it and you're done.
Click to expand...
Click to collapse
Magisk said: no backup. tht's why I did install the original boot.img back, and this is where the WiFi-issue started.
I wanted to go this route, but did not manage it after several hours, so gave up and went stock:
https://forum.xda-developers.com/mi-a3/how-to/guide-create-manual-backup-stock-boot-t3988345
WorstCases said:
Magisk said: no backup. tht's why I did install the original boot.img back, and this is where the WiFi-issue started.
I wanted to go this route, but did not manage it after several hours, so gave up and went stock:
https://forum.xda-developers.com/mi-a3/how-to/guide-create-manual-backup-stock-boot-t3988345
Click to expand...
Click to collapse
Yeah, you need to create first backup manually. The guide works perfectly, I tested all methods (otherwise I wouldn't mention them ). What issues did you have?
The system is probably installed in b partition, you need to set partition a as active and reinstall rom via mi flashtool
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!