Develop Bugs

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.

Magisk v14 and OTA updates

Hey, guys, I wanted to ask if someone tried OTA updates working with the new method of rooting released with magisk 14- a rooting method in which we do not need root or custom recovery beforehand, we just need to provide stock boot image dump to the magisk manager. This method will do us good because if OTA's still work after root we can be rooted on the stock roms without having to download full OTA's when a new update arrives. If someone can confirm working OTA's on the OOS open beta with this root method, it would be really helpful. Thank you!

As long as you take a backup of system and keep TWRP installed so you have a backup to revert to it should be fine. The risk of issues is just too high unless you don't give a **** about your personal data.

Puddi_Puddin said:
As long as you take a backup of system and keep TWRP installed so you have a backup to revert to it should be fine. The risk of issues is just too high unless you don't give a **** about your personal data.
Click to expand...
Click to collapse
Bro, I know how to work with TWRP. Your comment does not answer the question.

blaze95rs said:
Bro, I know how to work with TWRP. Your comment does not answer the question.
Click to expand...
Click to collapse
Well think of it about this. Magisk is just one big hack on the system partition. An OTA changes files on the system partition aswell. What if the OTA changes files that Magisk needs?
1. Your phone will go into a bootloop.
2. You might end up bricking it.
3. You just have to reflash Magisk.
4. Your phone becomes buggy as hell.
Thats why we also recommend to install the full zips when flashing roms and kernels that modify system because of possible conflicts.

Puddi_Puddin said:
Well think of it about this. Magisk is just one big hack on the system partition. An OTA changes files on the system partition aswell. What if the OTA changes files that Magisk needs?
1. Your phone will go into a bootloop.
2. You might end up bricking it.
3. You just have to reflash Magisk.
4. Your phone becomes buggy as hell.
Thats why we also recommend to install the full zips when flashing roms and kernels that modify system because of possible conflicts.
Click to expand...
Click to collapse
Obviously I would uninstall magisk and then install ota and reinstall magisk. Magisk is systemless so I think there shouldn't be any problem.

blaze95rs said:
Obviously I would uninstall magisk and then install ota and reinstall magisk. Magisk is systemless so I think there shouldn't be any problem.
Click to expand...
Click to collapse
See it for yourself! Its something most people do not recommend.

Puddi_Puddin said:
See it for yourself! Its something most people do not recommend.
Click to expand...
Click to collapse
You have missed the whole point of the post. This is a NEW method. Many people have not tried this method of root. So please, if you have any valuable information then only share. Do not litter. There should be logic to your answer and not general acceptance. Saying that many people do this or do that is not a very solid answer.

blaze95rs said:
You have missed the whole point of the post. This is a NEW method. Many people have not tried this method of root. So please, if you have any valuable information then only share. Do not litter. There should be logic to your answer and not general acceptance. Saying that many people do this or do that is not a very solid answer.
Click to expand...
Click to collapse
That doesn't matter. I get that it can be installed without a custom recovery. But that doesn't mean it won't conflict with possible ota's. Again, see it for yourself. Most people including me do rather play it the safe way.

I have recently updated to the lateset Oxygen OS Beta i had Magisk installed, i use Sparks Latest twrp version, with this you can install OTA updates. I dit not unlinstalled Magisk first, you do need the full rom file, but for me when i wanted to install the OTA, it found i had rooted and autmatacly downloaded the full rom. After you installed the update you can install the latest version of Magisk.

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.

Samsung A50 US variant (A505UZ) question

Hi. I just got the unlocked US variant of the A50 (A505UZ), but don't see any posts related to it. Is it possible to root this version? If so, which version of TWRP or set of directions do I follow to do so? Lastly, can I still receive OTAs if I do root it? Thanks in advance for any and all help

I think rooting is the same for all variants incl US because there isn't a separate soc for the N.A. like some galaxy models. Try rooting with magisk, you don't have to install TWRP so you can keep the system partition intact and don't trip safetynet so you can use google pay, bank apps. And ota updates will still work. Some people don't know any better and always suggest installing TWRP as a first step.

barrack1 said:
I think rooting is the same for all variants incl US because there isn't a separate soc for the N.A. like some galaxy models. Try rooting with magisk, you don't have to install TWRP so you can keep the system partition intact and don't trip safetynet so you can use google pay, bank apps. And ota updates will still work. Some people don't know any better and always suggest installing TWRP as a first step.
Click to expand...
Click to collapse
Thanks for the help! With the Magisk method, does this allow custom ROMs also? Sorry if thats a dumb question; but honestly, I've never heard anyone not use TWRP or similar to root, even with Magisk.

bloodbath said:
Thanks for the help! With the Magisk method, does this allow custom ROMs also? Sorry if thats a dumb question; but honestly, I've never heard anyone not use TWRP or similar to root, even with Magisk.
Click to expand...
Click to collapse
Magisk is a tool to allow the phone to be modified without changing the system partition. It can be installed on the stock rom or custom roms. TWRP is used to install Magisk, but TWRP itself doesn't need to be installed. I strongly suggest you read up alot or stick to stock rom.

Mi 10T Pro root only - best method? (possibly preserve OTA)

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!