"Can't load Android system" and "Factory data reset" tried and does not work
Hi all,
I bought a Pixel 3a, unlocked the bootloader, upgraded it to Android 10, and then tried to root it with Magisk. I must somehow have missed a step because now the phone only boots to:
Android Recovery
google/sargo/sargo
9/PQ3B.190801.002/5674421
user/release-keys
Use volume up/down and power.
Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device.
Try again
Factory data reset
If I "Try again" I end up in the same place after a long time with the Google logo and a reboot. If I "Factory data reset" I also end up in the same place.
My desktop has adb and fastboot, and was able to access the phone until the failed attempt at rooting. Now it does not detect the phone despite the system "bleeping" as if it has found a new device:
>adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
>adb devices
List of devices attached
Is there a way out of this mess?
FD
You're still on P by what recovery says. 0801 image. PQ3B is P. You want QP1A. Please try downloading the recent Q image and follow the official instructions from Google in the link and try again.
https://developers.google.com/android/images
Uzephi said:
You're still on P by what recovery says. 0801 image. PQ3B is P. You want QP1A. Please try downloading the recent Q image and follow the official instructions from Google in the link and try again.
https://developers.google.com/android/images
Click to expand...
Click to collapse
Thank you very much! Using the flash-all script I have managed to get my phone back. I have flashed the original Android 9 the phone came with.
Now, one further question, are there some good (as in unlikely to brick my phone again) instructions on how to root my Pixel 3a? I believe that Android 9 is preferred when using Magisk to Android 10, and I do not mind staying with Android 9, but I would like some instructions on how to root it without bricking it again.
Again, thanks for your prompt reply.
Yours,
FD
Frederick Davies said:
Thank you very much! Using the flash-all script I have managed to get my phone back. I have flashed the original Android 9 the phone came with.
Now, one further question, are there some good (as in unlikely to brick my phone again) instructions on how to root my Pixel 3a? I believe that Android 9 is preferred when using Magisk to Android 10, and I do not mind staying with Android 9, but I would like some instructions on how to root it without bricking it again.
Again, thanks for your prompt reply.
Yours,
FD
Click to expand...
Click to collapse
I followed this guide. it's for a pixel 3 but it's exactly the same for a 3a. There is no TWRP for 10 so doing it this way is the only way for now.
https://android.gadgethacks.com/how-to/root-your-pixel-3-android-10-0200295/
Just use magisk to patch Android 10 boot IMG and Flash it and your rooted on Android 10
Frederick Davies said:
Now, one further question, are there some good (as in unlikely to brick my phone again) instructions on how to root my Pixel 3a? I believe that Android 9 is preferred when using Magisk to Android 10, and I do not mind staying with Android 9, but I would like some instructions on how to root it without bricking it again.
Again, thanks for your prompt reply.
Yours,
FD
Click to expand...
Click to collapse
I have created a (IMHO) very thorough quide on how to root your Pixel 3a. It walks you through rooting with both Android Pie and Android 10 with very clear and precise steps. If you have any questions about it, feel free to post in that thread or reach out to me via a direct message.
There is no limitation on using Magisk or rooting under Android 10. The only thing you cannot do with Android 10 is use TWRP, but that isn't a deal breaker. TWRP is good for making backups of your OS, but as you have found you can still recover from just about any situation using the Google factory images, so while a backup might be beneficial at times, it isn't a necessity. Personally I would definitely recommend using Android 10 because Pie isn't being updated by Google anymore, so you are going to be behind on security updates, etc if you stick with Pie.
Watch this video and you shouldn't have any problems
sic0048 said:
I have created a (IMHO) very thorough quide on how to root your Pixel 3a. It walks you through rooting with both Android Pie and Android 10 with very clear and precise steps. If you have any questions about it, feel free to post in that thread or reach out to me via a direct message.
Click to expand...
Click to collapse
Very detailed indeed, but I still have a question: in your instructions you seem to boot into TWRP to install Magisk, but you do NOT install TWRP itself, just boot it for the installation of Magisk. Is that correct? Why?
sic0048 said:
There is no limitation on using Magisk or rooting under Android 10. The only thing you cannot do with Android 10 is use TWRP, but that isn't a deal breaker. TWRP is good for making backups of your OS, but as you have found you can still recover from just about any situation using the Google factory images, so while a backup might be beneficial at times, it isn't a necessity. Personally I would definitely recommend using Android 10 because Pie isn't being updated by Google anymore, so you are going to be behind on security updates, etc if you stick with Pie.
Click to expand...
Click to collapse
I am going through all this rigmarole to be able to install XPrivacyLua through the Xposed Framework, but the instructions for Xposed (https://www.xda-developers.com/xposed-framework-hub/) seem to indicate you need TWRP as a requisite, hence I think am stuck with Android P (9.0).
On the other hand, I get conflicting information as to whether Xposed for Magisk does (https://www.xda-developers.com/xposed-framework-hub/) or does not (https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268) pass SafetyNet. Most confusing...
FD
Frederick Davies said:
Very detailed indeed, but I still have a question: in your instructions you seem to boot into TWRP to install Magisk, but you do NOT install TWRP itself, just boot it for the installation of Magisk. Is that correct? Why?
FD
Click to expand...
Click to collapse
There is no need to install or boot into TWRP (btw. there is even no working TWRP for Android 10 yet) to install Magisk. It's sufficents to install Magisk Manager on your phone and patch the boot.img extracted from the factory image. Just follow the instructions which have been quoted here in the thread already.
AndDiSa said:
There is no need to install or boot into TWRP (btw. there is even no working TWRP for Android 10 yet) to install Magisk. It's sufficents to install Magisk Manager on your phone and patch the boot.img extracted from the factory image. Just follow the instructions which have been quoted here in the thread already.
Click to expand...
Click to collapse
Dear AndDisa,
As I said, I am rooting my Pixel 3a because I want to install XPrivacyLua, which requires the Xposed Framework; and to install Xposed with Magisk, it lists TWRP as a pre-requisite (see "Method 2: Magisk" in https://www.xda-developers.com/xposed-framework-hub/). Since it seems there is some kind of reluctance to use/install TWRP in this thread, I am asking why that is so. I understand it is possible to install Magisk without TWRP, I am just asking "why?"
Again, thank you all for your help.
FD
TWRP doesn't work on Android 10 at this point so you can't flash it.
Frederick Davies said:
Dear AndDisa,
As I said, I am rooting my Pixel 3a because I want to install XPrivacyLua, which requires the Xposed Framework; and to install Xposed with Magisk, it lists TWRP as a pre-requisite (see "Method 2: Magisk" in https://www.xda-developers.com/xposed-framework-hub/). Since it seems there is some kind of reluctance to use/install TWRP in this thread, I am asking why that is so. I understand it is possible to install Magisk without TWRP, I am just asking "why?"
Again, thank you all for your help.
FD
Click to expand...
Click to collapse
If you read closely in the guide sic linked, he does state the TWRP method is only for P because you can't use TWRP on 10. It is the way partitions are handled in 10 where you really can't read your internal storage and it would have to require a code rework. Until that's done, no TWRP.
Edit: quote from twrp developer about it. https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
https://github.com/ElderDrivers/EdXposed/pull/354
https://github.com/ElderDrivers/EdXposedManager/releases
You can flash xposed without TWRP. Just install edxposed by downloading and installing through magisk and install the edxposed manager. You don't need TWRP
Frederick Davies said:
Very detailed indeed, but I still have a question: in your instructions you seem to boot into TWRP to install Magisk, but you do NOT install TWRP itself, just boot it for the installation of Magisk. Is that correct? Why?
FD
Click to expand...
Click to collapse
As other have noted, TWRP does not work with Android 10. However, I also wanted to answer your question because it is valid.....
With Android Pie (9), you cannot permanently install TWRP unless you first flash a custom kernel that supports LZMA compression. Using the stock kernel, you can load TWRP using ADB and use it just like normal, but when you reboot the phone TWRP will not be loaded anymore. My instructions are about rooting the phone and not about installing TWRP permanently on the phone and therefore I provided the simplest method to accomplish that goal.
Most custom kernels have been updated with LZMA support, but you should really read the TWRP thread for more information on how to permanently install TWRP on Android Pie
Dear All,
Thank you for all your help and explanations concerning my questions.
I have now rooted my Pixel 3a running Android 9 following the instructions supplied (no TWRP installation), and It seems that Magisk is installed and happy (at least it thinks it is and FX has root access), but I am afraid that EdXposed and XPrivacyLua are not working as expected.
After Magisk, I installed the "Riru - Core" and "Riru - EdXposed (YAHFA)" modules. I then installed the "EdXposed Framework (YAHFA)" (giving the EdXposed Installer superuser privileges; EdExposed reports it is installed and active), and the XprivacyLua module inside it. But now Magisk complains that the SafetyNet checks are failing (this coincides with installing XPrivacyLua, but it is the only module I have in EdXposed), and XPrivacyLua is not actually blocking anything at all (that is, even when I supposedly block access to some functions, the apps just go ahead and use them).
Why do I get the impression Google does not want people to root their phones?
Yours,
FD
Frederick Davies said:
Dear All,
Thank you for all your help and explanations concerning my questions.
I have now rooted my Pixel 3a running Android 9 following the instructions supplied (no TWRP installation), and It seems that Magisk is installed and happy (at least it thinks it is and FX has root access), but I am afraid that EdXposed and XPrivacyLua are not working as expected.
After Magisk, I installed the "Riru - Core" and "Riru - EdXposed (YAHFA)" modules. I then installed the "EdXposed Framework (YAHFA)" (giving the EdXposed Installer superuser privileges; EdExposed reports it is installed and active), and the XprivacyLua module inside it. But now Magisk complains that the SafetyNet checks are failing (this coincides with installing XPrivacyLua, but it is the only module I have in EdXposed), and XPrivacyLua is not actually blocking anything at all (that is, even when I supposedly block access to some functions, the apps just go ahead and use them).
Why do I get the impression Google does not want people to root their phones?
Yours,
FD
Click to expand...
Click to collapse
It is most certainly the things you have installed that are breaking the SafetyNet check. I don't know anything about XprivacyLua, but I would assume there is a support thread here on XDA for it. I would read that support thread and see if there is a solution to the Safetynet issue.
Dear All,
OK, I have now rooted my Pixel 3a: I am running Android 9, and I flashed Magisk (Magisk Manager version 7.4.0; Magisk version 20.1) without installing TWRP as per the instructions. Then I installed the Riru - Core (version 10) and Riru - Ed Exposed (version 0.2.8_beta) modules, which allowed me to install EdXposedInstaller (version 2.2.5). I am currently running Xposed Framework (version 90.0-0.2.8) with XPrivacyLua (version 1.25).
The result is that XPrivacyLua is working with a few caveats: the SafetyNet Check fails both the ctsProfile and basicIntegrity checks (this is triggered by XPrivacyLua, not (Ed)Xposed), and when I limit access of WhatsApp to the Contacts list, there are constant errors whenever WhatsApp tries to read it (though it seems to work as expected). Also, the Contacts list keeps disappearing from the Contacts app itself, despite WhatsApp actually seeing those contacts in there (go figure).
Other apps that require root (like FX) are working as expected.
In the end, I have decided that since I am not interested in using my mobile for Google Pay, I will have to live with it as it is now, but I have a couple of points for others that may want to follow in my footsteps (this is not necessarily related to the method of rooting; those who helped me here are certainly not at fault for the following):
1. XPrivacyLua is in no way as capable and easy to use as XPrivacy was (XPrivacy is the main reason why I am rooting my phone). If I could install Android 4 on my Pixel 3a, I would do so and go back to XPrivacy (my venerable Nexus 5's second battery is shot, so I had to get new hardware). There is nothing in Android 9 that I actually need that was not there in Android 4.
2. We really need a Nexus Toot Toolkit for Pixel phones. The multitude of versions and steps required in rooting them successfully is too much for those like me who will root their phone for one or two apps and then leave it as it is. I know that these forums are really for tinkerers who want to extract the maximum from their hardware, and hence my point of view is not representative here, but I just want a mobile that will not spy on me, the rest is irrelevant to me.
I guess I will have to open a thread in the XPrivacyLua forums to see if I can sort out my problems, but I would like to thank you all for your help in getting me here and answering my questions (no matter how pointless they may have seemed).
Yours,
FD
Frederick Davies said:
Dear All,
OK, I have now rooted my Pixel 3a: I am running Android 9, and I flashed Magisk (Magisk Manager version 7.4.0; Magisk version 20.1) without installing TWRP as per the instructions. Then I installed the Riru - Core (version 10) and Riru - Ed Exposed (version 0.2.8_beta) modules, which allowed me to install EdXposedInstaller (version 2.2.5). I am currently running Xposed Framework (version 90.0-0.2.8) with XPrivacyLua (version 1.25).
The result is that XPrivacyLua is working with a few caveats: the SafetyNet Check fails both the ctsProfile and basicIntegrity checks (this is triggered by XPrivacyLua, not (Ed)Xposed), and when I limit access of WhatsApp to the Contacts list, there are constant errors whenever WhatsApp tries to read it (though it seems to work as expected). Also, the Contacts list keeps disappearing from the Contacts app itself, despite WhatsApp actually seeing those contacts in there (go figure).
Other apps that require root (like FX) are working as expected.
In the end, I have decided that since I am not interested in using my mobile for Google Pay, I will have to live with it as it is now, but I have a couple of points for others that may want to follow in my footsteps (this is not necessarily related to the method of rooting; those who helped me here are certainly not at fault for the following):
1. XPrivacyLua is in no way as capable and easy to use as XPrivacy was (XPrivacy is the main reason why I am rooting my phone). If I could install Android 4 on my Pixel 3a, I would do so and go back to XPrivacy (my venerable Nexus 5's second battery is shot, so I had to get new hardware). There is nothing in Android 9 that I actually need that was not there in Android 4.
2. We really need a Nexus Toot Toolkit for Pixel phones. The multitude of versions and steps required in rooting them successfully is too much for those like me who will root their phone for one or two apps and then leave it as it is. I know that these forums are really for tinkerers who want to extract the maximum from their hardware, and hence my point of view is not representative here, but I just want a mobile that will not spy on me, the rest is irrelevant to me.
I guess I will have to open a thread in the XPrivacyLua forums to see if I can sort out my problems, but I would like to thank you all for your help in getting me here and answering my questions (no matter how pointless they may have seemed).
Yours,
FD
Click to expand...
Click to collapse
Cool story bro
Related
OK, I’ve ordered and am awaiting arrival of my unlocked Pixel 2 from Google. I am on Verizon GFUDP and I plan on unlocking, rooting with Magisk and installing the tethering module. Then I plan on enjoying the phone and pretty much don’t plan on fussing around much with it.
I plan on unlocking before I do anything, including installing my Verizon sim. But do I have to allow the phone to do any upgrading prior to the rooting process? Also, can I (should I)hold off installing my sim until everything is rooted and up and running?
I was also thinking of using the Skipsoft toolset, but not sure if it is necessary. What are your thoughts on that?
Also, regarding lockscreen security on the phone, is fingerprint or password required? Can you use one or the other? I never use a passcode in general so wondering how it works.
Any "must have" apps to take advantage of Pixel 2?
Any help or advice is much appreciated!
Thanks in advance!
I purchased two Pixel 2 phones, and did the same thing you're planning on doing. I also have Verizon.
1) Unlocking the bootloader will wipe the device; Do this first. If you set up the phone prior to OEM unlocking, you will lose everything you set up.
2) Installing the SIM at anytime won't affect anything. When you install the Verizon SIM, some verizon apps will download. You can delete them if you want.
3) I did not use skipsoft. If you have a basic knowledge of ADB/Fastboot you will be fine without it.
4) The finger print reader is crazy fast. Also, setting up the phone it asks for a pin. Try it with the security of both to start. If you dislike it you can disable it in the future.
5) Apps I like/use: Tasker, Magisk, Titanium Backup, Custom Navigation Bar, Hide "using battery" notification, AdAway, Nova Launcher, Swipepad (where I put the "reboot" shortcuts), Reboot (Material Design) [ I made shortcuts to enter recovery, bootloader, etc], 1weather, Digilux (screen brightness control from the fingerprint reader), and Naptime (Have seen some battery length increase, though slows down notifications)
6) Not really apps, though @Tulsadiver made mods via Aroma from here: Various Mods for 8.1 December Update (Added Screen shots to show black notifications, battery icon removal, and clock w/day & ampm)
7) I like the Snoke kernel found here: [KERNEL]Snoke Kernel by @DespairFactor
There is a guide here: [GUIDE] Unlock/Flash/Root for the Pixel 2 (walleye) by @nathanchance
I laid out steps in this post here: [GUIDE] Unlock/Flash/Root for the Pixel 2 (walleye) - Post 127
Here are links because sometimes they can be tiresome to find:
SDK Platform Tools
(Follow the steps in the linked Post 127 to make cmd and SDK tools easier)
Factory Images for Nexus and Pixel Devices
Full OTA Images for Nexus and Pixel Devices
amajamar said:
Do I have to allow the phone to do any upgrading prior to the rooting process?
Click to expand...
Click to collapse
You should.
amajamar said:
Also, can I (should I)hold off installing my sim until everything is rooted and up and running?
Click to expand...
Click to collapse
Doesn't make a difference.
amajamar said:
I was also thinking of using the Skipsoft toolset, but not sure if it is necessary. What are your thoughts on that?
Click to expand...
Click to collapse
I'd do it manually via the command line with fastboot and adb - knowing how to use these tools is very important in case something ever goes wrong.
amajamar said:
Also, regarding lockscreen security on the phone, is fingerprint or password required? Can you use one or the other? I never use a passcode in general so wondering how it works.
Click to expand...
Click to collapse
You can use both.
Diesel_Jeremiah said:
I purchased two Pixel 2 phones, and did the same thing you're planning on doing. I also have Verizon.
1) Unlocking the bootloader will wipe the device; Do this first. If you set up the phone prior to OEM unlocking, you will lose everything you set up.
2) Installing the SIM at anytime won't affect anything. When you install the Verizon SIM, some verizon apps will download. You can delete them if you want.
3) I did not use skipsoft. If you have a basic knowledge of ADB/Fastboot you will be fine without it.
4) The finger print reader is crazy fast. Also, setting up the phone it asks for a pin. Try it with the security of both to start. If you dislike it you can disable it in the future.
5) Apps I like/use: Tasker, Magisk, Titanium Backup, Custom Navigation Bar, Hide "using battery" notification, AdAway, Nova Launcher, Swipepad (where I put the "reboot" shortcuts), Reboot (Material Design) [ I made shortcuts to enter recovery, bootloader, etc], 1weather, Digilux (screen brightness control from the fingerprint reader), and Naptime (Have seen some battery length increase, though slows down notifications)
6) Not really apps, though @Tulsadiver made mods via Aroma from here: Various Mods for 8.1 December Update (Added Screen shots to show black notifications, battery icon removal, and clock w/day & ampm)
7) I like the Snoke kernel found here: [KERNEL]Snoke Kernel by @DespairFactor
There is a guide here: [GUIDE] Unlock/Flash/Root for the Pixel 2 (walleye) by @nathanchance
I laid out steps in this post here: [GUIDE] Unlock/Flash/Root for the Pixel 2 (walleye) - Post 127
Here are links because sometimes they can be tiresome to find:
SDK Platform Tools
(Follow the steps in the linked Post 127 to make cmd and SDK tools easier)
Factory Images for Nexus and Pixel Devices
Full OTA Images for Nexus and Pixel Devices
Click to expand...
Click to collapse
Nice! Thanks! No need for TWRP? I was going to install it.
Was there a "thing" regarding which version of Magisk to install? I thought I read something somewhere about issues with the newest version.
amajamar said:
Nice! Thanks! No need for TWRP? I was going to install it.
Was there a "thing" regarding which version of Magisk to install? I thought I read something somewhere about issues with the newest version.
Click to expand...
Click to collapse
I have TWRP installed as well. I didn't comment on it since you didn't ask about it.
NOTE: You have to boot TWRP img, then install TWRP ZIP. Search threads, you'll find the info.
NOTE 2: You cannot install TWRP, Magisk and Kernel at the same time. Best way is to install everything is: TWRP ZIP, reboot. Flash Kernel, reboot. Flash Magisk, reboot.
As for Magisk, I'm on v5.5.3 and V15.2 without issues.
I've been upgrading through Magisk direct install without issues.
NOTE: You will get a pop up that your system has an issue and contact the manufacturer after Magisk. Do not panic, it'd because Magisk is modifying the DTBO img. It does not harm anything.
I also installed Viper4Android from Magisk.
Version 2.5.0.4 = works normal and processes correctly.
Diesel_Jeremiah said:
I have TWRP installed as well. I didn't comment on it since you didn't ask about it.
NOTE: You have to boot TWRP img, then install TWRP ZIP. Search threads, you'll find the info.
NOTE 2: You cannot install TWRP, Magisk and Kernel at the same time. Best way is to install everything is: TWRP ZIP, reboot. Flash Kernel, reboot. Flash Magisk, reboot.
As for Magisk, I'm on v5.5.3 and V15.2 without issues.
I've been upgrading through Magisk direct install without issues.
NOTE: You will get a pop up that your system has an issue and contact the manufacturer after Magisk. Do not panic, it'd because Magisk is modifying the DTBO img. It does not harm anything.
I also installed Viper4Android from Magisk.
Version 2.5.0.4 = works normal and processes correctly.
Click to expand...
Click to collapse
Awesome! What features does the Snoke kernel give? Any issues with it? Do you need to flash the factory kernel to take an OTA?
I never used Viper4Android before. What does it do?
Thanks.
amajamar said:
Awesome! What features does the Snoke kernel give? Any issues with it? Do you need to flash the factory kernel to take an OTA?
I never used Viper4Android before. What does it do?
Thanks.
Click to expand...
Click to collapse
Custom Kernel: Android Basics 101: Understanding Kernels – XDA Developer TV
I feel a bit snappier response and better battery life. There is Snoke, Flash, and ElementalX to name a few.
If you've loaded TWRP at all or mounted system rw; OTAs will not work. You'll have to use the factory images.
I've had no issues with the Snoke kernel. Just ensure you use the proper one for 8.0 or 8.1.
Viper4Android: Get the Sound you Deserve with ViPER4Android -- Android App Review
Viper4Android and Pizel 2 front facing speakers work very well together.
Diesel_Jeremiah said:
Custom Kernel: Android Basics 101: Understanding Kernels – XDA Developer TV
I feel a bit snappier response and better battery life. There is Snoke, Flash, and ElementalX to name a few.
If you've loaded TWRP at all or mounted system rw; OTAs will not work. You'll have to use the factory images.
I've had no issues with the Snoke kernel. Just ensure you use the proper one for 8.0 or 8.1.
Viper4Android: Get the Sound you Deserve with ViPER4Android -- Android App Review
Viper4Android and Pizel 2 front facing speakers work very well together.
Click to expand...
Click to collapse
Excellent information! Thanks!
Hi,
I am trying to root my Google Pixel on 8.1. I was on Magisk for a long time but I gave up on it because a few root apps I was trying to use aren't compatible.
I read some guides but they are ridiculously out of date. They say to use an experimental version of TWRP because it fails unlock codes and such; a lot of really out of date stuff. Some don't mention the ElementalX step, and then other guides say a custom kernel is required for rooting. But I had root with Magisk and never had to install a custom kernel. Other guides are still telling me to use the signature zips which supposedly hasn't been needed in forever. Trying to piece this all together is causing me to rip my hair out.
Anyway this is what I did, and it kept failing (I kept getting a "patching sepolicy" error in TWRP).
1) I booted the TWRP.img
2) I installed the twrp.zip
3) I booted into recovery
4) I installed Elemental X 13.3 zip
5) I installed SuperSU zip
6) I installed SuperSUHide zip
This isn't working. Every time I try to open SuperSU it says I don't have root. I also get an error every time I boot about their being an internal problem with my hardware and to contact the manufacturer. I believe Elemental X 13.3 is the cause. I wiped my phone and reinstalled stock and I am no longer getting that error.
Can anybody let me know what the deal is? Do I still have to install a custom kernel to install SuperSU? If so, what are the steps? Obviously whatever I am doing is wrong. Thanks so much in advance.
SuperSU is not working in the Pixel with 8.1
Sh0X31 said:
SuperSU is not working in the Pixel with 8.1
Click to expand...
Click to collapse
Oh. I had no idea.
Do any root methods that aren't Magisk work?
daddylonglegs said:
Oh. I had no idea.
Do any root methods that aren't Magisk work?
Click to expand...
Click to collapse
Looks like Magisk is becoming more and more popular nowadays, so I don't think any other method with 8.1 works.
What's the problem with magisk? It's super easy and you can also install systemless modules, which is a big advantage
TENN3R said:
Looks like Magisk is becoming more and more popular nowadays, so I don't think any other method with 8.1 works.
What's the problem with magisk? It's super easy and you can also install systemless modules, which is a big advantage
Click to expand...
Click to collapse
1) Magisk doesn't work with StickMount. I need a way for my USB-C flash drive to mount as something all file explorer programs can see. There seems to be no way to do this with Magisk
2) Magisk does not work with WifiTetherRouter. I need to use it to tether without being capped at 512kbps. It only works with "real root" like SuperSU.
3) I don't benefit at all from systemless modules because I use GravityBox, which makes the whole systemless thing pointless for me
daddylonglegs said:
1) Magisk doesn't work with StickMount. I need a way for my USB-C flash drive to mount as something all file explorer programs can see. There seems to be no way to do this with Magisk
2) Magisk does not work with WifiTetherRouter. I need to use it to tether without being capped at 512kbps. It only works with "real root" like SuperSU.
3) I don't benefit at all from systemless modules because I use GravityBox, which makes the whole systemless thing pointless for me
Click to expand...
Click to collapse
1) OTG
2) There are tether modules on magisk and other tether apps that will work with magisk
3) How does gravity box make systemless pointless? To my knowledge gravity box just builds custom rom features on top of stock, systemless modules should work regardless and provide things GB cannot
Lastly SuperSU isn't to be trusted anymore as it is no longer owned and maintained by chainfire. And could you explain the "real root" thing because magisk is a very real tangible root.
TENN3R said:
Looks like Magisk is becoming more and more popular nowadays, so I don't think any other method with 8.1 works.
What's the problem with magisk? It's super easy and you can also install systemless modules, which is a big advantage
Click to expand...
Click to collapse
KittyRgnarok said:
1) OTG
2) There are tether modules on magisk and other tether apps that will work with magisk
3) How does gravity box make systemless pointless? To my knowledge gravity box just builds custom rom features on top of stock, systemless modules should work regardless and provide things GB cannot
Lastly SuperSU isn't to be trusted anymore as it is no longer owned and maintained by chainfire. And could you explain the "real root" thing because magisk is a very real tangible root.
Click to expand...
Click to collapse
1) Doesn't that depend on the phone? Does my phone support OTG? And if so, why does my USB flash drive not show up in a bunch of apps?
2) None of them work with WiFi tethering except for WifiTetherRouter. PDANet works but it requires a PDANet program to be installed on the receiving computer, which means I am out of luck on stuff like the Nintendo Switch
3) Because from what I understand the entire point of Systemless root is to pass SafetyNet, and SafetyNet fails if you have GravityBox installed.
As for the "real root" thing, the developer of Auto Call Recorder here on XDA told me the newest version is not compatible with Magisk, only "real root" (his words). The developer of WifiTetherRouter told me the same thing.
daddylonglegs said:
1) Doesn't that depend on the phone? Does my phone support OTG? And if so, why does my USB flash drive not show up in a bunch of apps?
2) None of them work with WiFi tethering except for WifiTetherRouter. PDANet works but it requires a PDANet program to be installed on the receiving computer, which means I am out of luck on stuff like the Nintendo Switch
3) Because from what I understand the entire point of Systemless root is to pass SafetyNet, and SafetyNet fails if you have GravityBox installed.
As for the "real root" thing, the developer of Auto Call Recorder here on XDA told me the newest version is not compatible with Magisk, only "real root" (his words). The developer of WifiTetherRouter told me the same thing.
Click to expand...
Click to collapse
Pretty sure otg should work but I could be wrong. Try mounting otg via twrp. And ohh my bad I see what you mean about the tethering thing I misunderstood. As far as the magisk thing meh safetynet isn't that important and u can have a second slot that is properly intact and idk about the real root business but if that's what the devs said then fair enough
TENN3R said:
Looks like Magisk is becoming more and more popular nowadays, so I don't think any other method with 8.1 works.
What's the problem with magisk? It's super easy and you can also install systemless modules, which is a big advantage
Click to expand...
Click to collapse
KittyRgnarok said:
Pretty sure otg should work but I could be wrong. Try mounting otg via twrp. And ohh my bad I see what you mean about the tethering thing I misunderstood. As far as the magisk thing meh safetynet isn't that important and u can have a second slot that is properly intact and idk about the real root business but if that's what the devs said then fair enough
Click to expand...
Click to collapse
Thanks so much for the reply!
For some reason when I flash TWRP on this phone my phone will only boot into recovery until I flash back the stock boot.img (or the patched Magisk one). I am using the newest TWRP. Anyone else with this problem?
Anyway I mounted OTG in TWRP using the bootable image for TWRP. Would it make a difference? Does it have to be done in the installed version of TWRP where TWRP is my actual recovery?
After enabling OTG in TWRP I still can't find my SD/USB store in storage/emulated which is where I need it to be if I want all my apps to see it. Is there any way to do that?
daddylonglegs said:
Thanks so much for the reply!
For some reason when I flash TWRP on this phone my phone will only boot into recovery until I flash back the stock boot.img (or the patched Magisk one). I am using the newest TWRP. Anyone else with this problem?
Anyway I mounted OTG in TWRP using the bootable image for TWRP. Would it make a difference? Does it have to be done in the installed version of TWRP where TWRP is my actual recovery?
After enabling OTG in TWRP I still can't find my SD/USB store in storage/emulated which is where I need it to be if I want all my apps to see it. Is there any way to do that?
Click to expand...
Click to collapse
I don't flash twrp zip, just boot it, I know twrp on pixel oreo has still some troubles.
You can try to put your pin and AFTER (when you are on the main scrren with all the actions) plug the otg. On nougat this worked for me, now I just put the 2 or 3 files in internal storage so I don't use otg anymore from recovery so I don't know if this method works or not.
daddylonglegs said:
Hi,
I am trying to root my Google Pixel on 8.1. I was on Magisk for a long time but I gave up on it because a few root apps I was trying to use aren't compatible.
I read some guides but they are ridiculously out of date. They say to use an experimental version of TWRP because it fails unlock codes and such; a lot of really out of date stuff. Some don't mention the ElementalX step, and then other guides say a custom kernel is required for rooting. But I had root with Magisk and never had to install a custom kernel. Other guides are still telling me to use the signature zips which supposedly hasn't been needed in forever. Trying to piece this all together is causing me to rip my hair out.
Anyway this is what I did, and it kept failing (I kept getting a "patching sepolicy" error in TWRP).
1) I booted the TWRP.img
2) I installed the twrp.zip
3) I booted into recovery
4) I installed Elemental X 13.3 zip
5) I installed SuperSU zip
6) I installed SuperSUHide zip
This isn't working. Every time I try to open SuperSU it says I don't have root. I also get an error every time I boot about their being an internal problem with my hardware and to contact the manufacturer. I believe Elemental X 13.3 is the cause. I wiped my phone and reinstalled stock and I am no longer getting that error.
Can anybody let me know what the deal is? Do I still have to install a custom kernel to install SuperSU? If so, what are the steps? Obviously whatever I am doing is wrong. Thanks so much in advance.
Click to expand...
Click to collapse
Install ElementalX before TWRP if you wish to install TWRP.
SuperSU is no longer maintained and will not work any longer on modern versions of Android until further notice.
About the "internal problem" this can be completely ignored and does not harm the functionality of the device whatsoever.
Magisk 16.3 is the best version of Magisk and mounting USB-OTG shouldn't be problematic whatsoever. Mounting the drive in TWRP has no effect on it mounting in the system and vice-versa.
To mount the OTG in TWRP, plug it in, go to "mount" and select storage location, here you can choose between the internal sdcard and the USB-OTG storage device.
Regarding the mounting of the USB-OTG device in Android the drive must be formatted using a filesystem/partition scheme that Android is capable of mounting. I think FAT32 is the most compatible option.
Applications won't just magically see the external storage unless they're made to support such devices. Google kinda messed up some external storage functionality in Nougat and Oreo, it's kind of quirky. :silly:
I was about to put this in the main discussion thread of FlashFire, but it was closed so i decided to post it here.
So this is what happened, i rooted my Xiaomi Redmi Go with Magisk, the latest one, and when i opened FlashFire, it basically said that i have root, but access couldn't be acquired. It added "Found root: 19.4:MAGISKSU".
It was said in the Supported roots that Magisk is included so can't i use this app? I also tried to change my SELinux to permissive mode by going to the terminal and putting "setenforce 0", and the app still won't let me.
Any solutions to this? I was about to do perform a live backup through this app because the current TWRP version for this device is defective for my phone, the Backup option doesn't work and I've been looking for ways to backup my phone without custom recovery, but still with root of course.
Any help would be appreciated, thankyou!
Flashfire is discontinued so it is no longer compatible with the latest versions of Magisk
You might try going back to a older Magisk. It's definitely going to be before 19.3 but it may need to be older than that. There are two ways of doing this.
Set a custom channel in Magisk manager (install the older manager first).
Download the older release. If you're not familiar with github, expand the assets link under the release you want. The zip files will be listed there.
Make sure to remove the newer Magisk first.
spider1163 said:
Flashfire is discontinued so it is no longer compatible with the latest versions of Magisk
Click to expand...
Click to collapse
So is there solution that i can bypass that error ?
Android 10 comes earlier than expected, but there's no twrp to flash Magisk to gain root access. I tried to use SAR method to patch boot image, and it actually worked:
Requirements:
- A PC with ADB environment setup. * If you are using macOS, try to use a Virtual machine instead.
- XperiFirm to download Android 10 firmware.
- Magisk Manager App.
- unsin.exe program to extract sin file. Download here.
Instructions:
1. download the latest Android 10 firmware from XperiFirm, the current one is 52.1.A.0.532
2. open the downloaded folder and find boot_X-FLASH-ALL-B6B5.sin file. it may vary on XZ2C, but it surely will start with `boot_X-FLASH-ALL` .
3. drag the boot_X-FLASH-ALL-B6B5.sin file over unsin.exe to extract boot image, then you will get boot_X-FLASH-ALL-B6B5.img in the same directory.
4. Copy boot_X-FLASH-ALL-B6B5.img into your phone.
5. Install Magisk manager app, and make sure your phone is connected to the internet
6. Press Install → Install → Select and Patch a File, and select boot_X-FLASH-ALL-B6B5.img
7. Copy the patched image from your device to your PC, then flash it with fastboot command:
Code:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
fastboot reboot
after reboot the devices, your XZ2 is should be rooted, but it probably not pass SafetyNet Check, you can use MagiskHide Props Config Module to fix it.
I can't find the way to leave the boot image and patched boot image down below as the attachments, but even if I did, I still suggest to do it manually, just in case I am an idiot and it might broke your phone.
stupid question, but do I have to unlock my bootloader first?
Ressax said:
stupid question, but do I have to unlock my bootloader first?
Click to expand...
Click to collapse
In official way, google it and you will passed to the sony site.
Okay, but am I losing my warranty?
Ressax said:
Okay, but am I losing my warranty?
Click to expand...
Click to collapse
Read the info on the sony site
can you share the unsin.exe?
found it
https://forum.xda-developers.com/crossdevice-dev/sony/tool-unsin-sin-v3-unpacker-t3128106
Ressax said:
Okay, but am I losing my warranty?
Click to expand...
Click to collapse
Yes.
And your DRM keys, video enhancement, Netflix with 480p and no HDR, some bank apps and a lot of other things.
Hingbong said:
can you share the unsin.exe?
found it
https://forum.xda-developers.com/crossdevice-dev/sony/tool-unsin-sin-v3-unpacker-t3128106
Click to expand...
Click to collapse
Thank you bro, I was edit this post in a rush, forget to add the unsin unpacker
Luhccas-X10 said:
Yes.
And your DRM keys, video enhancement, Netflix with 480p and no HDR, some bank apps and a lot of other things.
Click to expand...
Click to collapse
is it still true after Pie update?
hary232 said:
is it still true after Pie update?
Click to expand...
Click to collapse
This is independent of any android version.
Unlocking the bootloader means erasing all important cert keys, image enhancements (both on screen and on camera) and revoking the security verification of some applications.
Thanks for posting this! Figured I'm chime in with my experience:
1. I'd recommend wiping userdata when upgrading to Android 10 - I don't know if this is strictly necessary, but I do know that I haven't experienced the unresponsive fingerprint sensor issue others have mentioned, or any other issues.
2. If you want to use Xposed modules like GravityBox, don't install EdXposed! The versions in the Magisk stable repository are not compatible with Android 10 and will bootloop, and even the beta version 0.4.6.0 from https://github.com/ElderDrivers/EdXposed/releases doesn't work with any module I tried.
3. Fortunately, https://taichi.cool/ works perfectly with GravityBox! Install it along with its Magisk module, and then install GravityBox Q beta 6 from https://forum.xda-developers.com/xposed/modules/app-gravitybox-v10-0-0-beta-1-android-10-t3974497.
works on my xz2c
@everyone who is interested in getting EdXposed working with Android 10
You need to add the following Magisk modules:
1. Riru - Core 19.6 from here
2. EdXposed-SandHook-0.4.6.1 from here (not the YAHFA version!)
Further you need to install the most current Xposed Manager app from here (the default Xposed Installer app won't work, so deinstall it!).
After a soft reboot, it should work :good:
Most probably it'll break Safety Net (have a look inside Magisk Manager). As a workaround, you have to open Xposed Manager and black-list the following:
- Google PlayStore
- Google Play Services
- Google-Services-Framework
Reboot system
Done!
> Apply your modules (maybe not every module will work. I have successfully tested AFWall+ and XprivacyLUA)
@serajr
Thanks a lot for your kind help to get this working :highfive:
Klaus N. said:
@everyone who is interested in getting EdXposed working with Android 10
You need to add the following Magisk modules:
1. Riru - Core 19.6 from here
2. EdXposed-SandHook-0.4.6.1 from here (not the YAHFA version!)
Further you need to install the most current Xposed Manager app from here (the default Xposed Installer app won't work, so deinstall it!).
After a soft reboot, it should work :good:
Most probably it'll break Safety Net (have a look inside Magisk Manager). As a workaround, you have to open Xposed Manager and black-list the following:
- Google PlayStore
- Google Play Services
- Google-Services-Framework
Reboot system
Done!
> Apply your modules (maybe not every module will work. I have successfully tested AFWall+ and XprivacyLUA)
@serajr
Thanks a lot for your kind help to get this working :highfive:
Click to expand...
Click to collapse
Hello, thanks for this little tutorial !
However, on another thread, ppl aren't singing the same tune ! Look at this answer that I get. @Ænimal explained me that YAHFA version should be better, especially if I want to use XPrivacyLUA.
I guess I should follow your instruction, but I downgraded my XZ2C to Android 9 from 10. I don't know if it will work as you.
I tried with this version of EdXposed : magisk-EdXposed-SandHook-v0.4.6.0_beta.4471.-release.zip and after installed Riru succesfully, I installed SandHook v0.4.6.0 and I get a bootloop issue on my phone.
So I guess I have to try SandHook v0.4.6.1 and if it doesn't work I should try YAHFA v0.4.6.1.
stilflip said:
Hello, thanks for this little tutorial !
However, on another thread, ppl aren't singing the same tune ! Look at this answer that I get. @Ænimal explained me that YAHFA version should be better, especially if I want to use XPrivacyLUA.
I guess I should follow your instruction, but I downgraded my XZ2C to Android 9 from 10. I don't know if it will work as you.
I tried with this version of EdXposed : magisk-EdXposed-SandHook-v0.4.6.0_beta.4471.-release.zip and after installed Riru succesfully, I installed SandHook v0.4.6.0 and I get a bootloop issue on my phone.
So I guess I have to try SandHook v0.4.6.1 and if it doesn't work I should try YAHFA v0.4.6.1.
Click to expand...
Click to collapse
I've always used to install YAHFA builds till android 9, with no issues. So, while you're on android 9, YAHFA is the answer!
SandHook builds, on android 10, FOR NOW, seem to cause less error than YAHFA (at least in the logs - verbose/modules), that's why I'm using it.
But, as soon as EdXposed's dev releases an android 10 YAHFA fixed version, I flash it!
Klaus N. said:
@everyone who is interested in getting EdXposed working with Android 10
You need to add the following Magisk modules:
1. Riru - Core 19.6 from here
2. EdXposed-SandHook-0.4.6.1 from here (not the YAHFA version!)
Further you need to install the most current Xposed Manager app from here (the default Xposed Installer app won't work, so deinstall it!).
After a soft reboot, it should work :good:
Most probably it'll break Safety Net (have a look inside Magisk Manager). As a workaround, you have to open Xposed Manager and black-list the following:
- Google PlayStore
- Google Play Services
- Google-Services-Framework
Reboot system
Done!
> Apply your modules (maybe not every module will work. I have successfully tested AFWall+ and XprivacyLUA)
@serajr
Thanks a lot for your kind help to get this working :highfive:
Click to expand...
Click to collapse
Hell yeah ! This method worked for me !
I have a XZ2C (H8324) on Android 9 (build 52.0.1.8.131), and I follow step by step your tutorial, and everything worked like a charm !
I installed XPrivacyLua, it seems working. I'll post here if I have any issue to report !
Thanks !
Backup TA
Thank you for your post
Sorry for going offtopic, but can someone give info on how to safely backup TA? I spent two days but couldn't find any info on how to do it on (at the moment, latest) stock Android 10 (52.1.A.0.532) on H8324 (XZ2c).
The way I understand for this root procedure to work, I need to unlock bootloader, and that means losing DRM keys. Is there any info on how to restore bootloader and DRM keys after I finish rooting my device?
I tried to:
1) Downgrade to stock Android 8.
2) Use backupTA_v2 or FlashTool to backup TA.
But that doesn't work.
maricn said:
Thank you for your post
Sorry for going offtopic, but can someone give info on how to safely backup TA? I spent two days but couldn't find any info on how to do it on (at the moment, latest) stock Android 10 (52.1.A.0.532) on H8324 (XZ2c).
The way I understand for this root procedure to work, I need to unlock bootloader, and that means losing DRM keys. Is there any info on how to restore bootloader and DRM keys after I finish rooting my device?
I tried to:
1) Downgrade to stock Android 8.
2) Use backupTA_v2 or FlashTool to backup TA.
But that doesn't work.
Click to expand...
Click to collapse
Hello there,
If you unlock your bootloader on Android 8, DRM keys will be lost on Android 8 so you'll lost camera definitely.
However, on Android 10 and 9, you won't lost DRM keys. Take care, you'll loose camera preview on Android 9 with this version of build and lower : 52.0.A.3.84.
So better to upgrade at least to Android 9, and the lower firmware where camera isn't bugged at all when you unlock bootloader is Android 9 (52.0.A.8.131).
Conclusion : for rooting your device, you need to unlock your bootloader. If you're running on Android 10 (build 52.1.A.0.532) then, everything will be ok, I did it myself and everything worked fine.
If you need more help on how to downgrade your firmware, just let me. Personally, I didn't like Android 10 so I came back to Android 9 (52.0.A.8.131)
So, if unlocking bootloader on android 10 we won't lose the DRM keys or any other functionality?
DUMIY said:
So, if unlocking bootloader on android 10 we won't lose the DRM keys or any other functionality?
Click to expand...
Click to collapse
You will lost he drm keys always when unlock the bootloader on an xperia device.
My daughter got a new phone, after struggling with bootloops and magisk issues. Finally got everything working correctly.
But,
I got root to go fine, only thing is she has had location issues. Google maps, other GPS or location services did not work.
So I uninstalled xprivacylua and seems like services came back, looks like I wasn't hiding anything on it anyways. Or I don't remember what it was.
So instead of reinstalling xprivacylua I decided to look for different answers .
Maybe some other solutions.
Here is a list of apps and modules that are installed. I think some of them overlapped and are kind of messed up. To many that my head is spinning.
Magisk
23.0 (23000)
Magiskhide Props Config.
Riru
Riru LS exposed (Tried switching back and forth to edxposed)
Systemless Hosts
Universal Safetynet fix 1.1.2. (Tried different versions)
LS Esposed one module,
Hiddencore module (enabled Google services Framework and google play services)
Also cleared Data and Cache on google play store.
Rebooted every time
Always safety net failure.
I know its a lot to take in , and do appreciate any feedback or help on this issue.
Is it an 8T? Are you running stock OOS with magisk?
In that case all you need to pass safteynet should be Magisk 23 with magisk hide activated. No need to bother with Magisk hide propconfig, or edexposed or anything.
If you are running a custom rom it is a different matter
I have magisk 23 and magisk hide is active on all google play services, but it still fails.
Its 8t with stock rom.
I think this is why its a little confusing since on my stock 7 pro I have google play services and only android.gms, and android gms unstable hidden and it works fine.
There is not a custom recovery on either of these phones.
Magisk and magisk hide works fine for me, so don't know what to say.
Perhaps try to uninstall Riru and exposed to make sure that they aren't triggering safety net?
You have to get termux. Get su superuser permissions then type props a menu will load press 2 then select yes to change device name then y again to reboot then it should pass safety net
Screens of magisk hide props config
scottlam1 said:
You have to get termux. Get su superuser permissions then type props a menu will load press 2 then select yes to change device name then y again to reboot then it should pass safety net
Click to expand...
Click to collapse
Nope.. Terminal Emulator is actually recommended. With Termux, you are required to use root access for props to work.
with Terminal Emulator, you can just type:
props
and then it'll load. no "su" necessary. That's termux. I've had some issues that these people are talking about with my OnePlus 8T (KB2005, unlocked completely).. I'll try Termux just to rule this out, but this is highly doubtful as to whether or not safetynet passes based on this--it's attempting to modify the same values. Anyway, when I unlocked that bootloader on a stock rom, CTS Profile started showing as false. So I did get the stock on there correctly and it initially passed with a LOCKED bootloader. There's an alpha TWRP that you can actually flash if you want. There's a couple others where you can only boot it.. there's a lot of "only's" here.. and I couldn't get it going with any of the apps mentioned, including ditching EdXposed and deciding to try LSPosed, but that + XPrivacyLau didnt seem to help me. Maybe I'm doing something wrong. From what I can tell I've done everything right and I've got quite a bit of experience attempting/doing this. Sometimes Device SImulation and forced BASIC ATTESTATION can be a lifesaver.
On my OnePlus 6T, I don't have this problem.. then again it's on Android 10. I can't even get a proper root explorer for Android 11. I seriously can't stand what they did to Android 11.. it's so ridiculous how many apps are now incompatible. Root Explorer Pro was possibly the best Root File Manager I've ever used and I've used it since day 1.
Anyway, I'm gonna give all of this a shot in different order.. and this time I'll see if Magisk can do the trick (last time it was on some different firmware and i just now was able to get it going by flashing via Fastboot in Linux). It's the manual way (payload dumper) as opposed to MSMDownloadTool -- which could be used via a VM.. and maybe even better than using Windows tools where you literally have no idea what you're actually doing. I'm just saying. Android is a linux distro, technically.. and we're trying to use just basic root apps for Android 11, and they don't seem to work.. it's insane. They did something with the partitions and it's apparently having issues even mounting R/W even with Magisk giving it root permissions. Btw, Magisk Canary is now outdated, as far as I can tell? Or it's just nowhere to be found when it comes to versions. Either way, I have tried multiple. So I'll try again in a different order.
Sorry for the long post. I've just had it. I've been working on this for a WEEK non stop.. 5-6 days and this is the first sign of progress (reverting via fastboot via Linux, which is the same thing as the MSMDownloadTool ultimately... without the hassle of finding it)
Let me know if there's anything else.. cause I've tried just about everything out there. Remember, for me, so far... unlocked bootloader = CTS Profile failure.. but locked bootloader + stock rom? Passed. I don't know. Before it wasn't passing with a stock rom that came with it so that drove me nuts and made no sense, hence me saying "progress" ... heh. Anyway.. Please let me know if you guys do find anything that works for it. I'm at my wits end. There's basically almost zero support for the 8T but plenty for the 8 and 8 Pro. So that also gets on my nerves. Sorry, once again, for this really long post. Some of it is just venting and I'll update if I get somewhere with it.
.. and now this morning after installing magisk, by just booting twrp (not flashing, but booting) and then using LSPosed/XPrivacyLua (I installed MagiskProps too but I barely did anything aside from pick a fingerprint) --- and it passed? WHAT?
I'm gonna look into this, but I'm not complaining. Let's see if I can find good Android 11 apps for actually browsing the system and being able to r/w any elusive partitions -- wasn't working well with Android 11 before. Not sure if that's around with a simple design anymore. Root Explorer Pro was king of that. Then Android 11 stepped in. I still have to install Lucky Patcher, if it will even work as a module for LSPosed. (Yes, I'm one of those idiots) -- I fully expect it to fail with that but I might be pleasantly surprised. Who knows. So, we'll just call this mixed results. For now -- Passing somehow. I don't understand aside from LSPosed and XPrivLua.. maybe magiskprops. Not sure which one did what first to cause this to go the right direction.
All I can say is all I have is magisk props not the other 2 modules you speak of
Well this is super weird. I didnt see my daughter for 2 days and she said everything is working fine.
I did tons of reboots and other installs/uninstalls and nothing worked.
But now I do safety net check and it works fine.
I dont get it.
If I do have issues again I will post here and follow instructions.
Thank you for your time and help
eracet said:
Well this is super weird. I didnt see my daughter for 2 days and she said everything is working fine.
I did tons of reboots and other installs/uninstalls and nothing worked.
But now I do safety net check and it works fine.
I dont get it.
If I do have issues again I will post here and follow instructions.
Thank you for your time and help
Click to expand...
Click to collapse
Ok asked her what she did. Mentioned updated YouTube vanced. And not sure of anything else.