How To Find App That Is Incompatiable With Windows 10
You should upgrade or use an alternative browser.
- #1
Introduction
This Guide is for Pixel 5 owners that want to Root their phone, and enjoy the benefits of rooting it without installing a Custom ROM. However, for those that just can't live without a Custom ROM, take a look at 'Custom ROMs for Pixel 5'.
NEW
- Magisk Modules for Magisk Alpha/Canary
- GitHub - Fox2Code/FoxMagiskModuleManager: A new module manager for Magisk when the official app drop support for it
- Fox Magisk Module Manager Releases
- Magisk Alpha (vvb2060)
Update(s)
- Factory/OTA Images - 06/12
- Magisk Stable - Magisk-23.0 05/12
- Magisk Beta - Magisk-23.0 05/12
- Magisk Canary - Magisk-23015 24/11
- TWRP - Waiting for T.R.W.P. for Android 12
- SafetyNet - SafetyNetFix v2.2.0
- SDK Platform-tools - r31.0.3 08/18
- Custom Kernels
- ElementalX - Check ElementalX Kernel Manager
- CleanSlate vR1.8.5 06/13 S (B5) 2.9.0 24/11
- Custom ROMs
- ProtonAOSP[12] 11/01
Disclaimer
- I assume no responsibility for the malfunctioning/bricking of your phone.
- The order of listed items i.e., Custom Kernels, Custom ROMS, etc. Does not indicate my preference for them. It is your responsibility to do the research before selecting an item .
Prerequisites
- A Pixel 5 phone with an unlocked bootloader.
- The latest Android 12 Factory or OTA Image: "redfin" for Pixel 5
Factory Image
OTA Image
- A Computer with the latest SDK Platform-Tools: r31.0.3 installed.
- Important: Update Platform Tools, regularly, for optimal performance.
Other Guides
- [Guide] Pixel 4 XL Android 12
Credits/Thanks/Recognitions
- @creezalird- Flash Android 12 factory image.
- Those I may have, inadvertently, forgotten.
Index
(NOTE: Numbers 1-11 are not steps, they are individual sets of instructions).
- Open a Command Prompt/Boot Fastboot Mode/Boot Recovery
- Test fastboot
- Unlock Bootloader/Return Phone to Stock/Lock Bootloader
- Install/Update Factory Image keep data or wipe data
- ADB Sideload
- Extract/Flash boot.img
- Root/Reroot with Magisk and Pass SafetyNet.
- Set Magisk App Update Channel/Update Magisk
- Custom ROMs
- Apps/Mods/Scripts/Tethering/Themes
- T.W.R.P. Backup/Restore
Attachments
- #2
Sent from my Mi 9T Pro using Tapatalk
- #3
I just did this to my P5, however the guide was not clear on how to get Safetynet working.
After Magisk was installed and I confirmed that the device was rooted, I went to this other thread and followed the instructions for Safetynet at the very end of the first post. The downside seems to be that the device is identified as a Pixel 3A, but it got the Safetynet test to pass. I assume that this will be fixed someday.
- #4
Hey, thanks for this super-detailed guide!I just did this to my P5, however the guide was not clear on how to get Safetynet working.
After Magisk was installed and I confirmed that the device was rooted, I went to this other thread and followed the instructions for Safetynet at the very end of the first post. The downside seems to be that the device is identified as a Pixel 3A, but it got the Safetynet test to pass. I assume that this will be fixed someday.
I don't think so. Even this method is kinda kludged. Pixel 3a is the latest version not subject to the hardware check that prevented Safetynet check.
- #5
- #6
No OTA Update will not disable. RootI'm assuming OTA updates will disable this root? So don't take any?
- #7
Yes, you will lose root if you take te OTA. The only way to keep root with OTA is do #7. D..I'm assuming OTA updates will disable this root? So don't take any?
- #8
No OTA Update will not disable. Root
Incorrect, Jackie. See Homeboy76's reply. I actually did a reset to factory defaults before posting this and it removed root. An OTA would do the same.
---------- Post added at 08:39 PM ---------- Previous post was at 08:11 PM ----------
Thanks for confirming my thoughts. And thanks for this guide, it is damn brilliant.Yes, you will lose root if you take te OTA. The only way to keep root with OTA is do #7. D..
- #9
If you do a factory reset your boot image will not be overwritten so technically root is still there.
But the magisk app will be deleted because of the factory reset, the patched boot image should still be in place.
OTA overwrites those files so then it will be fully unrooted.
- #10
I don't take OTAs . I flash factory images on Mondays. But I thought you can't even take OTAs without restoring the boot image first. Either through fastboot or Magisk itself?? Or I think you can flash the full OTA from Google's website. I'm pretty sure that will replace the boot image with stock.I'm not an expert but as far as i know that's not correct.If you do a factory reset your boot image will not be overwritten so technically root is still there.
But the magisk app will be deleted because of the factory reset, the patched boot image should still be in place.
OTA overwrites those files so then it will be fully unrooted.
- #11
- #12
Did you toggle the unlock in developer settings? If you can't and it's greyed out, your out of luck. Are you on the bootloader screen when your fastbooting? You have updated platform tools?My 3XL died, so I ordered a 5 unlocked from Amazon. In trying to unlock the bootloader with 'fastboot flashing unlock', I receive FAILED (remote: 'flashing unlock is not allowed'). How can I tell if I have an unlocked phone or is there something else I am missing?
- #13
My bad, I enabled OEM Debugging, but not the Enable OEM Unlock. Bootloader is unlocked!My 3XL died, so I ordered a 5 unlocked from Amazon. In trying to unlock the bootloader with 'fastboot flashing unlock', I receive FAILED (remote: 'flashing unlock is not allowed'). How can I tell if I have an unlocked phone or is there something else I am missing?
- #14
Sweet! Glad you got it.My bad, I enabled OEM Debugging, but not the Enable OEM Unlock. Bootloader is unlocked!
- #15
The guide goes over this in Step 7D how it is possible on devices with A/B partitions but not those without them.I don't take OTAs . I flash factory images on Mondays. But I thought you can't even take OTAs without restoring the boot image first. Either through fastboot or Magisk itself?? Or I think you can flash the full OTA from Google's website. I'm pretty sure that will replace the boot image with stock.
---------- Post added at 11:44 AM ---------- Previous post was at 10:54 AM ----------
So you're saying that after I lost root on factory reset, all I needed to do was reinstall Magisk?I'm not an expert but as far as i know that's not correct.If you do a factory reset your boot image will not be overwritten so technically root is still there.
But the magisk app will be deleted because of the factory reset, the patched boot image should still be in place.
OTA overwrites those files so then it will be fully unrooted.
- #16
The guide goes over this in Step 7D how it is possible on devices with A/B partitions but not those without them.---------- Post added at 11:44 AM ---------- Previous post was at 10:54 AM ----------
Unless I'm reading it incorrectly, that is no longer an option. Taking the OTA and installing Magisk to the inactive slot has been removed.
- #17
I'm reading that some devices can be done that way while others cannot. This guide is linked in #7D: https://topjohnwu.github.io/Magisk/ota.htmlThe guide goes over this in Step 7D how it is possible on devices with A/B partitions but not those without them.---------- Post added at 11:44 AM ---------- Previous post was at 10:54 AM ----------
Unless I'm reading it incorrectly, that is no longer an option. Taking the OTA and installing Magisk to the inactive slot has been removed.
I personally won't be doing it, I'll just re-root from scratch, but it does seem like an option.
- #19
<Edit> You're right!I'm not an expert but as far as i know that's not correct.If you do a factory reset your boot image will not be overwritten so technically root is still there.
But the magisk app will be deleted because of the factory reset, the patched boot image should still be in place.
OTA overwrites those files so then it will be fully unrooted.
- #20
Are you sure the boot.img is not overwritten?
Why?
If the boot.img was not overwritten Magisk and Magisk Manager would still be on your phone.
The reason the boot.img is still there is it is stored on your computer i.e. C:/Platform-tools folderA Factory reset wipes the phone's data & it's Internal Storage.
magisk manager is an app, the root itself is something that is changed in the boot image.
by a factory reset the system and boot image/partitions are not touched, only the data partition and internal storage if you choose so.
that clears everything exept the boot image, that's why if people would realy want to go back to stock they have to flash a stock/factory image.
because if you do that or OTA the boot image will be overwritten by the stock one.
Similar threads
How To Find App That Is Incompatiable With Windows 10
Source: https://forum.xda-developers.com/t/guide-root-pixel-5-android-12.4187609/
Posted by: huttonandless00.blogspot.com
0 Response to "How To Find App That Is Incompatiable With Windows 10"
Post a Comment