Mi 10T Pro root only - best method? (possibly preserve OTA) - Xiaomi Mi 10T / 10T Pro Questions & Answers

Hello!
Device: Mi 10T Pro
Current ROM: miui_APOLLOEEAGlobal_V12.1.2.0.RJDEUXM_cff0da241e_11.0 (Stable)
Android version: 11 RKQ1.200826.002
Bootloader: Currently 15hrs left to unlock
If one wants to root, stick with the stock ROM and possibly get OTA updates (looking forward to MIUI 12.5), what is the best method/option for rooting?
A) Patch boot.img with Magisk and flash it to device using fastboot
B) Install TWRP for Mi 10T/10T Pro by Whyle (TWRP_apollo_3.5.0_10-beta_1_whyle) by flashing it to BOOT and install Magisk using TWRP
C) Install TWRP for Mi 10T/10T Pro by Whyle (TWRP_apollo_3.5.0_10-beta_1_whyle) by flashing it to RECOVERY and install Magisk using TWRP
Thank you.

-=ApA=- said:
Hello!
Device: Mi 10T Pro
Current ROM: miui_APOLLOEEAGlobal_V12.1.2.0.RJDEUXM_cff0da241e_11.0 (Stable)
Android version: 11 RKQ1.200826.002
Bootloader: Currently 15hrs left to unlock
If one wants to root, stick with the stock ROM and possibly get OTA updates (looking forward to MIUI 12.5), what is the best method/option for rooting?
A) Patch boot.img with Magisk and flash it to device using fastboot
B) Install TWRP for Mi 10T/10T Pro by Whyle (TWRP_apollo_3.5.0_10-beta_1_whyle) by flashing it to BOOT and install Magisk using TWRP
C) Install TWRP for Mi 10T/10T Pro by Whyle (TWRP_apollo_3.5.0_10-beta_1_whyle) by flashing it to RECOVERY and install Magisk using TWRP
Thank you.
Click to expand...
Click to collapse
A) is the only choice, and you'll have to UNROOT before ota by flashing stock boot partition. C wouldn't work as we do not yet have complete working twrp.
And never flash recovery to boot partition, you'll brick your device, so B) is out of the question. And fastboot boot recovery.img is not the same as fastboot flash option, so take good care...

I just rooted my Mi 10T Pro and yes, A is the way to go. That way, you preserve your stock recovery while still letting yourself root the phone. Everything works, only after an OTA upgrade to Android 11 came, my phone got stuck in a bootloop, recoverable only by wiping doing a factory reset.

Aldenar said:
I just rooted my Mi 10T Pro and yes, A is the way to go. That way, you preserve your stock recovery while still letting yourself root the phone. Everything works, only after an OTA upgrade to Android 11 came, my phone got stuck in a bootloop, recoverable only by wiping doing a factory reset.
Click to expand...
Click to collapse
You didn't have to factory reset - just have to return to stock before ota - that's required because boot partition is changed by rooting and ota fails... So basically fastest method is flashing stock boot image before ota, making new one with magisk after ota and returning with full root

calinorg said:
A) is the only choice, and you'll have to UNROOT before ota by flashing stock boot partition. C wouldn't work as we do not yet have complete working twrp.
And never flash recovery to boot partition, you'll brick your device, so B) is out of the question. And fastboot boot recovery.img is not the same as fastboot flash option, so take good care...
Click to expand...
Click to collapse
Yes, i understand. Thank you calinorg and Aldenar.
Just so you know, after rooting (even after just unlocking bootloader), your SafetyNet (CTS profile) will fail. Yes, even if you rename your Magisk app, use MagiskHide and MagiskHide Props Config module. Personally it doesn't impact me much, cause even my banking apps are working without issues and my bank does not support NFC payments anyway. Only few apps, including infamous McDonalds app complain and do not run. I guess fast food is alot more sensitive industry than banking then . IMHO there is no point in detecting root in apps anyway. If all of your data is in your servers (with tamper checks), manipulating it on device level (like memory manipulation with games) would be pointless. More and more apps and games nowadays are using the same method. I guess McDonalds and all others alike should just fix their apps instead of blocking out rooted users.
More info on SafetyNet CTS profile failure and possible workaround here. Universal SafetyNet Fix Magisk module.
Since i don't have TWRP installed, im not eager to test SafetyNet fix yet, cause several users are reporting bootloops and problems with banking app security mechanisms. I'm guessing that (problematic) Magisk modules can be uninstalled by other means than just TWRP but still, i will wait for the more stable solution.

-=ApA=- said:
Yes, i understand. Thank you calinorg and Aldenar.
Just so you know, after rooting (even after just unlocking bootloader), your SafetyNet (CTS profile) will fail. Yes, even if you rename your Magisk app, use MagiskHide and MagiskHide Props Config module. Personally it doesn't impact me much, cause even my banking apps are working without issues and my bank does not support NFC payments anyway. Only few apps, including infamous McDonalds app complain and do not run. I guess fast food is alot more sensitive industry than banking then . IMHO there is no point in detecting root in apps anyway. If all of your data is in your servers (with tamper checks), manipulating it on device level (like memory manipulation with games) would be pointless. More and more apps and games nowadays are using the same method. I guess McDonalds and all others alike should just fix their apps instead of blocking out rooted users.
More info on SafetyNet CTS profile failure and possible workaround here. Universal SafetyNet Fix Magisk module.
Since i don't have TWRP installed, im not eager to test SafetyNet fix yet, cause several users are reporting bootloops and problems with banking app security mechanisms. I'm guessing that (problematic) Magisk modules can be uninstalled by other means than just TWRP but still, i will wait for the more stable solution.
Click to expand...
Click to collapse
I am using that exact Magisk module and it works like a charm - The SafetyNet check got downgraded back to Basic that and together with Magisk Hide, works like a charm!

Aldenar said:
I am using that exact Magisk module and it works like a charm - The SafetyNet check got downgraded back to Basic that and together with Magisk Hide, works like a charm!
Click to expand...
Click to collapse
Nice, thanks! I'll give it a try. What version of the module are you using? Latest release is v1.1.1 on GitHub.

-=ApA=- said:
Nice, thanks! I'll give it a try. What version of the module are you using? Latest release is v1.1.1 on GitHub.
Click to expand...
Click to collapse
Latest, so 1.1.1. As proof, see screenshots

Aldenar said:
Latest, so 1.1.1. As proof, see screenshots
Click to expand...
Click to collapse
Awesome, thanks!
EDIT: Also working for me just fine.

Any luck on 12.1.5.x or even 12.5 beta?

Illuvitar said:
Any luck on 12.1.5.x or even 12.5 beta?
Click to expand...
Click to collapse
12.5.1.0 was fine, now trying with 12.5.5.0

12.5.5.0 needs Universal SafetyNet Fix module update (i'm using 2.1.1), otherwise SafetyNet check will fail! With 12.5.1.0 it's still working fine with Universal Safetynet Fix 1.1.1 tho.
You will also need to install Riru to use Universal SafetyNet fix 2.1.1

Update:
12.5.12.0 still working. Had to rename magisk.db tho and reinstall Magisk 23.0.
Make sure not to update Magisk beyond version 23!

Related

How can I change my Android Emojis to Emoji One without Root or bypass Safetynet ?

Hello Guys,
I have a Oneplus 3 with Oxygen OS 4.0.1 with locked Bootloader atm because when I try to use Android Pay with Root and Freedom OS it doesn't work
I figured out that this Safetynet fails when I unlock my Bootloader but
I would like to get the EmojiOne Emojis back in Whatsapp and Android Keyboard is this Possible ?
Is there a Way to bypass Safetynet that I can use Root and V4A again ?
(I already tried Magisk)
Greetings
Magisk has an emoji one module, root, etc while passing safety net
Sent from my du_oneplus3 using Tapatalk
slothdabski said:
Magisk has an emoji one module, root, etc while passing safety net
Sent from my du_oneplus3 using Tapatalk
Click to expand...
Click to collapse
Okay and how can I hide my unlocked Bootloader ?
Just try it, working like a charm. Really, worth.
mucha.k1994 said:
Just try it, working like a charm. Really, worth.
Click to expand...
Click to collapse
It doesn't work on Oneplus 3 because it's nearly Stock and the Safety Thing checks for unlocked Bootloader......
I managed it by installing a custom Whatsapp Mod and maybe a custom Keyboard soon.....
Luro02 said:
It doesn't work on Oneplus 3 because it's nearly Stock and the Safety Thing checks for unlocked Bootloader......
I managed it by installing a custom Whatsapp Mod and maybe a custom Keyboard soon.....
Click to expand...
Click to collapse
In fact, Magisk patch the bootloader dm-verity (which is used by SafetyNet to check if your device is unlocked), so juste flash a completly stock system, check SafetyNet, and Install latest Magisk with the modules you want, reboot and you're good to go !
Arno500 said:
In fact, Magisk patch the bootloader dm-verity (which is used by SafetyNet to check if your device is unlocked), so juste flash a completly stock system, check SafetyNet, and Install latest Magisk with the modules you want, reboot and you're good to go !
Click to expand...
Click to collapse
Dude did you tried it on the Oneplus 3 ???
IT'S NOT WORKING WITH UNLOCKED BOOTLOADER !!!!!!!!!
Luro02 said:
Dude did you tried it on the Oneplus 3 ???
IT'S NOT WORKING WITH UNLOCKED BOOTLOADER !!!!!!!!!
Click to expand...
Click to collapse
Working perfectly with the normal way of unlocking, installing TWRP and flashing Magisk
What can you do with root before it breaks ? (Xposed,Substratum,Adblocker or V4A working ?)
What were your Steps to get it working ?
Do you still have the DM-Veriy Warning on Boot ?
Luro02 said:
What can you do with root before it breaks ? (Xposed,Substratum,Adblocker or V4A working ?)
What were your Steps to get it working ?
Do you still have the DM-Veriy Warning on Boot ?
Click to expand...
Click to collapse
I'm running Open Beta 13 with an unlocked bootloader and Magisk with Substratum. I would recommend unlocking your bootloader, flashing stock, then rooting with just Magisk, not SuperSU. I followed these steps and I have it working, SafetyNet passed.
Luro02 said:
Dude did you tried it on the Oneplus 3 ???
IT'S NOT WORKING WITH UNLOCKED BOOTLOADER !!!!!!!!!
Click to expand...
Click to collapse
Its working perfectly on op3 with magisk. So relax.
You must check magisk hide in magisk settings ofc.
Running latest freedomOS CE and all good. Magisk, safetynet, V4A, abblock, substratum. All working.
So stop saying it doesnt work with unlocked bootloader, thats just bull****.
Update to latest version of Freedom OS.
I think you should try updating your ROM to latest version of Freedom OS. Has everything you need.
Thanks Guys
It works

Help With Root

I'm a little lost on Root for the Pixel XL. I am currently running unlocked with Screw'd ROM - 3.1.2-****ery-20170712-1454. This is a BETA, but has been running really smooth for the last 2 days.
Security Patch Level - July 5, 2017
Vendor - NJH47D
Last time I tried to apply root while running PureNexus the phone continued to boot loop and I had to eventually flashall.bat and start over.
1. What version of SuperSU should I be flashing? The latest and newest or is there other versions that work better?
2. What are the correct steps? Is wipe cache/dalvik necessary before? Do I need to install anything on the phone beforehand?
Boot to TWRP, Flash SuperSU, Reboot? Easy as that?
I see this version being talked about a lot - SR3-SuperSU-v2.79-SR320170114223742.zip, but it isn't the latest available that I can see. The SuperSU thread states to install the latest version and using google brings me to many versions of SuperSU.
Lastly, after rooting will apps like SnapChat work? If not how to you bypass this?
So I just found some information after searching more. Some of it is dated. I currently have twrp-pixel-installer-marlin-3.1.0-0RC2.zip version for TWRP installed.
Is RC1 needed for root, and with what SuperSU version. Or which combination of RC2 and SuperSU work together?
jws86 said:
So I just found some information after searching more. Some of it is dated. I currently have twrp-pixel-installer-marlin-3.1.0-0RC2.zip version for TWRP installed.
Is RC1 needed for root, and with what SuperSU version. Or which combination of RC2 and SuperSU work together?
Click to expand...
Click to collapse
When I was rooted I initially was using RC1, I think my supersu was V2.8? And no Snapchat, Pokemon go, and Android pay, etc, will not work. So a little work around for Snapchat, you need to log in first then flash supersu, or just go with magisk and enable magisk hide to make life easier.
sakumaxp said:
When I was rooted I initially was using RC1, I think my supersu was V2.8? And no Snapchat, Pokemon go, and Android pay, etc, will not work. So a little work around for Snapchat, you need to log in first then flash supersu, or just go with magisk and enable magisk hide to make life easier.
Click to expand...
Click to collapse
Is there a guide to Root with Magisk somewhere floating around?
jws86 said:
Is there a guide to Root with Magisk somewhere floating around?
Click to expand...
Click to collapse
I believe it's the same as when you flash supersu, don't quote me on that
sakumaxp said:
I believe it's the same as when you flash supersu, don't quote me on that
Click to expand...
Click to collapse
Yeah I found the guide. It seems I need to flash stock image first before. So Magisk gives you the ability to root first, then download apps such as snapchat and still login if you use magisk hide?
jws86 said:
Yeah I found the guide. It seems I need to flash stock image first before. So Magisk gives you the ability to root first, then download apps such as snapchat and still login if you use magisk hide?
Click to expand...
Click to collapse
Correct, downloading isn't a problem, but it'll just prevent you from logging in since supersu, trips safetynet
sakumaxp said:
Correct, downloading isn't a problem, but it'll just prevent you from logging in since supersu, trips safetynet
Click to expand...
Click to collapse
I read through this thread: https://forum.xda-developers.com/pixel-xl/how-to/guide-stock-7-1-2-root-safetynet-ok-t3617347
Seems pretty straightforward, however currently I have a ROM installed I'm really liking. To do this I would have to flash back to stock image, then go through the root process. My question would be after rooting, if I went to flash Screw'd again, doesn't it wipe everything and I would lose root again, then just have to flash it after the ROM?
jws86 said:
I read through this thread: https://forum.xda-developers.com/pixel-xl/how-to/guide-stock-7-1-2-root-safetynet-ok-t3617347
Seems pretty straightforward, however currently I have a ROM installed I'm really liking. To do this I would have to flash back to stock image, then go through the root process. My question would be after rooting, if I went to flash Screw'd again, doesn't it wipe everything and I would lose root again, then just have to flash it after the ROM?
Click to expand...
Click to collapse
Myself I've never been on screwd before, I would assume so, but in my experience the pixel XL is more complicated than my previous phones
If you just want root you shouldn't need to flash the stock image again. You would need to do that if you wanted to flash a custom kernel but not for root. You need to download the modified version of Magisk for the Pixel XL. The official version doesn't work on the Pixels. I'm not currently rooted as I went back to stock but I was using Magisk. At that time the latest version wasn't stable but it might be fixed now. You need to boot into fastboot TWRP, flash the Magisk zip, flash the TWRP zip and then boot up. After you are booted up you install the Magisk Manager app. The tricky thing is installing the right version of Magisk Manager that works properly with the unofficial build of Magisk that you are using. You can get more information in the Resurrection Remix rom thread which for some reason is the official place where the modified version of Magisk is hosted if you can't find good info about which combination of unofficial Magisk and Magisk Manager you should be using. Also when I used Magisk you needed to enable core only mode for it to pass Safety Net but that may no longer be the case. You should be able to find the most up to date info either in the thread you cited or the RR rom thread. Just remember that official builds of Magisk do not work on the Pixel. You need to stick with one of the unofficial builds.
jhs39 said:
If you just want root you shouldn't need to flash the stock image again. You would need to do that if you wanted to flash a custom kernel but not for root. You need to download the modified version of Magisk for the Pixel XL. The official version doesn't work on the Pixels. I'm not currently rooted as I went back to stock but I was using Magisk. At that time the latest version wasn't stable but it might be fixed now. You need to boot into fastboot TWRP, flash the Magisk zip, flash the TWRP zip and then boot up. After you are booted up you install the Magisk Manager app. The tricky thing is installing the right version of Magisk Manager that works properly with the unofficial build of Magisk that you are using. You can get more information in the Resurrection Remix rom thread which for some reason is the official place where the modified version of Magisk is hosted if you can't find good info about which combination of unofficial Magisk and Magisk Manager you should be using. Also when I used Magisk you needed to enable core only mode for it to pass Safety Net but that may no longer be the case. You should be able to find the most up to date info either in the thread you cited or the RR rom thread. Just remember that official builds of Magisk do not work on the Pixel. You need to stick with one of the unofficial builds.
Click to expand...
Click to collapse
I think I got which versions of magisk and magisk manager I need to use from the other thread I had posted earlier. This helps to clear some things up for me though. I have both the .apk and the zip on my phone now. Getting a bit of a charge and I guess I'll go ahead and try it.
It worked, I'm officially rooted .Thanks for the help!
jws86 said:
It worked, I'm officially rooted .Thanks for the help!
Click to expand...
Click to collapse
Cool.

New 2XL - Starting out info..

Hi Guys,
Forgive the noobie Question; I am searching, but I’m after verification and advice;
I’m very new - I’ve just purchased myself a Pixel 2XL 128Gb today.
I’m coming from a Note 4, that had Magisk and systemless Xposed. (And TWRP)
From what I’ve researched so far, I can install root via Magisk, following this procedure;
https://www.xda-developers.com/how-to-unlock-bootloader-and-root-the-google-pixel-2-and-pixel-2-xl/
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
https://forum.xda-developers.com/pixel-2-xl/development/2017-11-6-root-pixel-2-xl-t3701176
And possibly get Xposed via here;
https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268 (anyone know which version?)
My questions are, for those who have a Pixel 2 XL, and are Rooted/Xposed..
1) Are these the best guides to follow?
2) Should I back anything up (EFS/IMEI etc) before I do any modding? If so, how? (when it’s unrooted / locked)
3) Is there any point having TWRP?
(I used to use this for backup / restore / flashing, but I can flash stuff via ADB, is there any advantage to having it?
I would like to update OS as updates come along, but if TWRP is going to cause issues, then I can go without..)
4) is it safe to use Xposed? I have a few modules I want to continue using, but read it can cause issues. What’s the safest way to set this up.
5) Is there anything else I should know / consider before I set this up / unlock / root / xpose etc?
6) Should I stay on stock, or change Kernel? Which Kernels are considered the best for the 2XL?
(I may have more questions..)
Thanks in Advance!
Brik
BrikHaus said:
Hi Guys,
Forgive the noobie Question; I am searching, but I’m after verification and advice;
I’m very new - I’ve just purchased myself a Pixel 2XL 128Gb today.
I’m coming from a Note 4, that had Magisk and systemless Xposed. (And TWRP)
From what I’ve researched so far, I can install root via Magisk, following this procedure;
https://www.xda-developers.com/how-to-unlock-bootloader-and-root-the-google-pixel-2-and-pixel-2-xl/
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
https://forum.xda-developers.com/pixel-2-xl/development/2017-11-6-root-pixel-2-xl-t3701176
And possibly get Xposed via here;
https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268 (anyone know which version?)
My questions are, for those who have a Pixel 2 XL, and are Rooted/Xposed..
1) Are these the best guides to follow?
2) Should I back anything up (EFS/IMEI etc) before I do any modding? If so, how? (when it’s unrooted / locked)
3) Is there any point having TWRP?
(I used to use this for backup / restore / flashing, but I can flash stuff via ADB, is there any advantage to having it?
I would like to update OS as updates come along, but if TWRP is going to cause issues, then I can go without..)
4) is it safe to use Xposed? I have a few modules I want to continue using, but read it can cause issues. What’s the safest way to set this up.
5) Is there anything else I should know / consider before I set this up / unlock / root / xpose etc?
6) Should I stay on stock, or change Kernel? Which Kernels are considered the best for the 2XL?
(I may have more questions..)
Thanks in Advance!
Brik
Click to expand...
Click to collapse
Dang! That's a lot of questions! Lets see....
1. Look at this guide...https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
2. Backup EFS after twrp is installed.
3. I like twrp to backup/restore and flash kernels and magisk. Monthly updates won't harm twrp, you just install it again.
4. Many use exposed without issue. Follow the guide you already have.
5. Make sure you unlock _critical when you unlock the bootloader.
6. I like custom kernels. Flash kernel is the most popular, and is updated regularly.
7. Next question ?
Badger50 said:
Dang! That's a lot of questions! Lets see....
1. Look at this guide...https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
2. Backup EFS after twrp is installed.
3. I like twrp to backup/restore and flash kernels and magisk. Monthly updates won't harm twrp, you just install it again.
4. Many use exposed without issue. Follow the guide you already have.
5. Make sure you unlock _critical when you unlock the bootloader.
6. I like custom kernels. Flash kernel is the most popular, and is updated regularly.
7. Next question ?
Click to expand...
Click to collapse
Thank you very much Badger50! I'm very keen to play with this, but obviously don't want to brick it!
What's the best 'Order of operation'?
Unlock > Flash TWRP > Backup > Flash Magisk > Flash Kernel > Flash Xposed?
BrikHaus said:
Thank you very much Badger50! I'm very keen to play with this, but obviously don't want to brick it!
What's the best 'Order of operation'?
Unlock > Flash TWRP > Backup > Flash Magisk > Flash Kernel > Flash Xposed?
Click to expand...
Click to collapse
Run BOTH bootloader unlocking commands, this will wipe your phone!!
Reboot, then do a minimal setup, leaving your lock screen set to either swipe or none.
Fastboot twrp, once in twrp, flash the twrp installer zip, then the kernel zip(optional) then the magisk zip. Reboot and you should be rooted.
Then go ahead with your xposed installation
Badger50 said:
Run BOTH bootloader unlocking commands, this will wipe your phone!!
Reboot, then do a minimal setup, leaving your lock screen set to either swipe or none.
Fastboot twrp, once in twrp, flash the twrp installer zip, then the kernel zip(optional) then the magisk zip. Reboot and you should be rooted.
Then go ahead with your xposed installation
Click to expand...
Click to collapse
Awesome! Thank you!
Badger50 said:
Run BOTH bootloader unlocking commands, this will wipe your phone!!
Reboot, then do a minimal setup, leaving your lock screen set to either swipe or none.
Fastboot twrp, once in twrp, flash the twrp installer zip, then the kernel zip(optional) then the magisk zip. Reboot and you should be rooted.
Then go ahead with your xposed installation
Click to expand...
Click to collapse
Systemless Xposed still trips safetynet right?
darkfire404 said:
Systemless Xposed still trips safetynet right?
Click to expand...
Click to collapse
That is correct.
sublimaze said:
That is correct.
Click to expand...
Click to collapse
Is there any way to avoid xposed tripping safetynet? Or do I have to go with a custom kernel like Flash?
BrikHaus said:
Is there any way to avoid xposed tripping safetynet? Or do I have to go with a custom kernel like Flash?
Click to expand...
Click to collapse
You use xposed you will trip safety net.
p70shooter said:
You use xposed you will trip safety net.
Click to expand...
Click to collapse
Bugger.
Ah.. The kernel only hides bootloader unlock, not xposed.
Can safetynet be "untripped" if a new method of hiding xposed is developed?
Apart from 'Banking' etc, is there any benefit to keeping safetynet?
(i tend use xposed mods more than nfc payment apps)
BrikHaus said:
Bugger.
Ah.. The kernel only hides bootloader unlock, not xposed.
Can safetynet be "untripped" if a new method of hiding xposed is developed?
Apart from 'Banking' etc, is there any benefit to keeping safetynet?
(i tend use xposed mods more than nfc payment apps)
Click to expand...
Click to collapse
The Devs are always working on things for xposed and magisk, so maybe someday a true fix can be found. However, as of now, it's either...don't use exposed and use your banking apps, or, use xposed, and pull out your credit card :good:
NVM
BrikHaus said:
Bugger.
Ah.. The kernel only hides bootloader unlock, not xposed.
Can safetynet be "untripped" if a new method of hiding xposed is developed?
Apart from 'Banking' etc, is there any benefit to keeping safetynet?
(i tend use xposed mods more than nfc payment apps)
Click to expand...
Click to collapse
If you depend on Google Pay or an app that requires SafetyNet validation, then you can't use Xposed. The purpose of SafetyNet is to check the integrity of the system, and installing Xposed framework changes that. There is no way around it.
However, some Xposed mods are available as Magisk modules, which remain hidden from SafetyNet. Open Magisk, tap the hamburger menu at top left and check the "Downloads" list. If the mod you want is not listed, then you must install Xposed and give up SafetyNet. Unfortunately, that is just the way it is.
I understand why people prefer using their bank's phone app instead of using a web browser.
But I don't use my bank's app because if I lose my phone, I don't want the person that finds it to know I which bank I use. That is just one step closer to someone gaining access to my account.
Huge Thanks for your reply @Badger50!
Managed to sucessfully install TWRP, Magisk, Flash Kernel and xposed, all without issue.
Cheers Mate, very appreciate your answers & tips.
Not fussed to lose SafetyNet. Still use cards when shopping, and much prefer xposed functionality.
Hey Guys,
I got a System message that says my XL tried to install a critical update and failed.
I assume this is because I'm running the FLASH kernel.
My question is do I need to flash this, or will the patches be incorporated into a FLASH release at some point?
Do other people bother with these? or just swipe away?
Cheers!
B
BrikHaus said:
Hey Guys,
I got a System message that says my XL tried to install a critical update and failed.
I assume this is because I'm running the FLASH kernel.
My question is do I need to flash this, or will the patches be incorporated into a FLASH release at some point?
Do other people bother with these? or just swipe away?
Cheers!
B
Click to expand...
Click to collapse
Having been rooted since root was available on my P2XL, I've never had one of those notifications. Then again, I have automatic updates turned off in developer options. Are you on the May release?
Badger50 said:
Having been rooted since root was available on my P2XL, I've never had one of those notifications. Then again, I have automatic updates turned off in developer options. Are you on the May release?
Click to expand...
Click to collapse
I believe so.
Kernel version
4.4.127-FlashKernel-Taimen-v2.30 (clang version 7.0.0)
[email protected] #1
Sun Apr 8 04:05:46 MST 2018
BrikHaus said:
I believe so.
Kernel version
4.4.127-FlashKernel-Taimen-v2.30 (clang version 7.0.0)
[email protected] #1
Sun Apr 8 04:05:46 MST 2018
Click to expand...
Click to collapse
The kernel won't make any difference with those notifications. Just shut them off. By May release I meant the OS build number.
Badger50 said:
The kernel won't make any difference with those notifications. Just shut them off. By May release I meant the OS build number.
Click to expand...
Click to collapse
Apologies !
it's
OPM2.171019.029
BrikHaus said:
Apologies !
it's
OPM2.171019.029
Click to expand...
Click to collapse
No worries. Are you ok April or May security patch?

How to install magisk in Oneplus 5T?

I have a OnePlus 5T locked and unrooted phone having OxygenOS 5.1.7 installed. I am new to rooting and related kinds of stuff. Can someone help me to give some instructions to install Magisk in my device? I know the below steps, but at the same time, I am having some questions in my mind.
1. Unlock bootloader - I saw some commands here to unlock bootloader - https://forum.xda-developers.com/showpost.php?p=74504347&postcount=4 - looks like these are outdated, last updated on Dec 2017. Are those work today also?
2. Install TWRP recovery - I heard that, OxygenOS 5.1.7 is having Project Treble supported. Can I use the same TWRP recovery mentioned in the above link?
3. Root using Magisk or SuperSU. What is the difference? What is systemless root? Anyway, I need to install Magisk Manager finally - Please suggest a way.
4. And the last one, How do I unroot my device if something goes wrong? Or is that possible?
5. I don't want to install any custom ROMs, I am fine with OOS.
https://www.youtube.com/watch?v=bTpxvmwBruQ&t=193s
Most of your questions have been answered on xda, youtube, and reddit before. Please try searching before posting.
sarathsnair said:
I have a OnePlus 5T locked and unrooted phone having OxygenOS 5.1.7 installed. I am new to rooting and related kinds of stuff. Can someone help me to give some instructions to install Magisk in my device? I know the below steps, but at the same time, I am having some questions in my mind.
1. Unlock bootloader - I saw some commands here to unlock bootloader - https://forum.xda-developers.com/showpost.php?p=74504347&postcount=4 - looks like these are outdated, last updated on Dec 2017. Are those work today also?
2. Install TWRP recovery - I heard that, OxygenOS 5.1.7 is having Project Treble supported. Can I use the same TWRP recovery mentioned in the above link?
3. Root using Magisk or SuperSU. What is the difference? What is systemless root? Anyway, I need to install Magisk Manager finally - Please suggest a way.
4. And the last one, How do I unroot my device if something goes wrong? Or is that possible?
5. I don't want to install any custom ROMs, I am fine with OOS.
Click to expand...
Click to collapse
1. Yes the unlock commands remain the same till date.
2. Use the latest bluspark twrp which has the treble support, link mentioned is fine and if you need the direct link, its here
3. Use the latest Magisk as SU is a dead project now.
4. Whenever you want to unroot just dirty remove/uninstall all the mods, dirty flash the latest stock rom > Factory reset in recovery and lock the bootloader. I did a post here for the 6T and it should work the same way on 5T.
5. You can stay rooted on OOS no need of custom roms any more :good:
Let me know if you want to know anything else, Thanks.
PS: Thread moved to Q&A Section
Funk Wizard said:
4. Whenever you want to unroot just dirty remove/uninstall all the mods, dirty flash the latest stock rom > Factory reset in recovery and lock the bootloader. I did a post here for the 6T and it should work the same way on 5T.
Click to expand...
Click to collapse
What happens to the installed twrp recovery if I unroot?
sarathsnair said:
What happens to the installed twrp recovery if I unroot?
Click to expand...
Click to collapse
Its replaced by stock recovery :good:
I got some more question too.
1.will I get official update from oneplus after my magisk root??
2.can I root my 5t with beta room ?
3.can I switch from beta to official and from official to beta once I rooted my device.
4.can I use confidential app like banking app.???
alisrovi said:
I got some more question too.
1.will I get official update from oneplus after my magisk root??
2.can I root my 5t with beta room ?
3.can I switch from beta to official and from official to beta once I rooted my device.
4.can I use confidential app like banking app.???
Click to expand...
Click to collapse
1. Yes, but your phone will download the whole firmware at each update instead of the ota.
2. Yes
3. Yep you can.
4. Yes of course, but some apps will detect root. So you will have to use Magisk Hide (inside the Magisk Manager) to hide root from these apps.
Note : I didn't use OOS anymore but it seems to me that OOS overwrites root everytime you update, so keep in mind that you will have to reflash it everytime
alisrovi said:
I got some more question too.
1.will I get official update from oneplus after my magisk root??
2.can I root my 5t with beta room ?
3.can I switch from beta to official and from official to beta once I rooted my device.
4.can I use confidential app like banking app.???
Click to expand...
Click to collapse
1- Yes, but you will recieve full sized zip (1.5+)GB automatically in rooted OOS. Incremental small sized ota won't work in case of root, and don't bother with it.
The downside of updating full whole zip is that you will loose root & twrp recovery after the update. So keep in mind, you will re-install both of them later.
2- I haven't tried beta, but i am sure yes
3- any switch between those requires clean flash in TWRP (wiping dalvik cache, cache, data, vendor and system). So, make sure to have backup in safe place.
4- yes, as long as you passed the safety net in Magisk. Magisk has a feature to hide root on certain apps of your choice, so you can use banking apps later
All my magisk installed whether in oos stable or custom roms, passed the safety net out of the box. So I haven't faced issues there.

Question Update and Magisk Root

How do I update my Magisk Rooted oneplus 9 pro without losing root access?
Shanemichealrowland said:
How do I update my Magisk Rooted oneplus 9 pro without losing root access?
Click to expand...
Click to collapse
grab the latest full ota from oxygen updater by downloading it to device storage - go to system update; local update - install the ota but do not reboot - once installed go into magisk and install to inactive slot (after ota) - reboot and profit
I found oxygen updater in Google play store. Is that what you're talking about?
sbcdave said:
I found oxygen updater in Google play store. Is that what you're talking about?
Click to expand...
Click to collapse
No,I was hoping to figure out how to manually update my 9 pro without uninstalling Magisk manager or losing root access Besides,I don't think Oxygen os updater supports the 9 pro
Shanemichealrowland said:
No,I was hoping to figure out how to manually update my 9 pro without uninstalling Magisk manager or losing root access Besides,I don't think Oxygen os updater supports the 9 pro
Click to expand...
Click to collapse
Yes it does, I've been using it since I got my op9pro on 1st April.
thirtythr33 said:
grab the latest full ota from oxygen updater by downloading it to device storage - go to system update; local update - install the ota but do not reboot - once installed go into magisk and install to inactive slot (after ota) - reboot and profit
Click to expand...
Click to collapse
Like This...
On 11.2.5.5 now, updating via this route.
Oxygen updater supports the 9Pro.
Bunecarera said:
Like This...
On 11.2.5.5 now, updating via this route.
Oxygen updater supports the 9Pro.
Click to expand...
Click to collapse
I assume you disable all magisk modules prior updating.
netgar said:
I assume you disable all magisk modules prior updating.
Click to expand...
Click to collapse
Yes.
There are no full ota's for LE2125 Global 11.2.5.5 AA yet!
galaxys said:
There are no full ota's for LE2125 Global 11.2.5.5 AA
Click to expand...
Click to collapse
This is rather annoying. Why are we left behind?
the bolt of thunder said:
This is rather annoying. Why are we left behind?
Click to expand...
Click to collapse
I think it's because the Global ota's are being stored on Google servers instead of the OnePlus servers for some reason
Shanemichealrowland said:
How do I update my Magisk Rooted oneplus 9 pro without losing root access?
Click to expand...
Click to collapse
I updated my BA using oxygen updater (download full os, settings/system/system updates/lokal update) without touching magisk at all. reboot, bootloader, reflash https://mega.nz/file/bNozXKJI#0zNfKtRw1IBqG6ojFuW3830dxXLgewmtsbbh4T4WGzs (I know its 1.1.2.4.4, but it works...) done
Flashing a non-matching boot image is a rather bad idea. Install the update, don't reboot. Then install Magisk to INACTIVE slot and reboot. Done.
dreinulldrei said:
Flashing a non-matching boot image is a rather bad idea. Install the update, don't reboot. Then install Magisk to INACTIVE slot and reboot. Done.
Click to expand...
Click to collapse
thats what i did first of all, my device didnt boot at all but kept going to stock recovery. afterwards i flashed what i wrote above, everythinx fine now.
galaxys said:
There are no full ota's for LE2125 Global 11.2.5.5 AA yet!
Click to expand...
Click to collapse
I decided to unroot and take the update. I'll just wait until the full OTA comes to us before rooting. :/
thirtythr33 said:
grab the latest full ota from oxygen updater by downloading it to device storage - go to system update; local update - install the ota but do not reboot - once installed go into magisk and install to inactive slot (after ota) - reboot and profit
Click to expand...
Click to collapse
Exactly, and thx for your info!
One question. Why is it necessary to deactivate the magisk module before the update? Maybe somebody knows. I forgot to disable some of them without any issues. Just out of interest, as it is mentioned or recommended from time to time.
Happy Sunday to all..
Flying Fox said:
Exactly, and thx for your info!
One question. Why is it necessary to deactivate the magisk module before the update? Maybe somebody knows. I forgot to disable some of them without any issues. Just out of interest, as it is mentioned or recommended from time to time.
Happy Sunday to all..
Click to expand...
Click to collapse
Some of the modules may not be compatible with upgrade, causing issues like bootlooping. That makes it a pain in the butt, to enter recovery and and delete the module.
There isn't a recovery yet (that can delete Magisk mods). Some mods might copy system files during installation to mess with them. Keeping the module means you might carry over system files from an older system version, causing trouble with new updates. Hence: turn them off before the update (except for stuff where you know it won't cause harm, like systemless hosts). And _reinstall_ those that modify system stuff, e.g. Qualcomm Wifi Bonding. This won't e.g. cause boot loops, but on my sons phone wifi was dead until I reinstalled the module.
dreinulldrei said:
There isn't a recovery yet (that can delete Magisk mods). Some mods might copy system files during installation to mess with them. Keeping the module means you might carry over system files from an older system version, causing trouble with new updates. Hence: turn them off before the update (except for stuff where you know it won't cause harm, like systemless hosts). And _reinstall_ those that modify system stuff, e.g. Qualcomm Wifi Bonding. This won't e.g. cause boot loops, but on my sons phone wifi was dead until I reinstalled the module.
Click to expand...
Click to collapse
schmeggy929 said:
Some of the modules may not be compatible with upgrade, causing issues like bootlooping. That makes it a pain in the butt, to enter recovery and and delete the module.
Click to expand...
Click to collapse
Thx for your answers!! Nice to be back to Oneplus. Great community here...
Does anyone know if oxygen updater from the play store is a trustworthy source for these OTAs?

Categories

Resources