Related
As title says. I installed android pay. I went through the setup which changed an nfc setting from sim card to processor. Then I restarted my phone. About 6 apps are missing. If I go to settings/ application manager/All. I can see them there but they are greyed out with an SD symbol above them.
Annoyingly this includes "suoersu". Android pay doesn't work with root so I was hoping to turn root off temporarily. I can't uninstall supersu, install it from the playstore or from apk. I can't even install other versions like superuser etc.
Any idea as to what's going on greatly appreciated.
It's a galaxy S5 with xtrestolite rom.
lgg2flash said:
As title says. I installed android pay. I went through the setup which changed an nfc setting from sim card to processor. Then I restarted my phone. About 6 apps are missing. If I go to settings/ application manager/All. I can see them there but they are greyed out with an SD symbol above them.
Annoyingly this includes "suoersu". Android pay doesn't work with root so I was hoping to turn root off temporarily. I can't uninstall supersu, install it from the playstore or from apk. I can't even install other versions like superuser etc.
Any idea as to what's going on greatly appreciated.
It's a galaxy S5 with xtrestolite rom.
Click to expand...
Click to collapse
Why don't you simply clean install the rom again? For using android pay you can try using Magisk and SuperSU systemless mode.
Thanks for the reply. I will give magisk a go.
This phone is my work phone and also has lots of photos and video pf my kids. I think it's all backed up but I always lose something when I reflash. Currently apps that were granted root in the past still have it so not a big issue yet. Xposed is missing tho so I won't be able to update modules. If that bugs me enough I may have to reflash rom. It has been smooth for 2 years at least. Probably due for a refresh. Maybe even a new phone.
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!
I've been rooting my Android phones since about 2012, but today I got a point of sale card reader for my business and I'm not having any luck hiding root from the app (square reader app). The app wont work at all so I tried a number of options in magisk manager (magisk hide the app, hide magisk manager, enable core mode only) rebooting between each try and clearing the square reader app data and setting it up fresh each time, but still no luck
I tried to uninstall magisk but the app still didn't work. So I eventually flashed back to stock and got rid of magisk all together, now the app works but I don't have root...
I tried installing magisk again after I got the app to work and hiding root from the app before I opened it up again, but it still somehow knew the device was rooted
Can anyone suggest anything I haven't tried? Or is there an alternative to rooting the OnePlus 6 (other than magisk) and hiding root? I had a bit of a look around but didn't find anything.
Thanks
I had to go back to 18.0, heard 18.2 works as well.
qbanlinxx said:
I had to go back to 18.0, heard 18.2 works as well.
Click to expand...
Click to collapse
Thanks for your reply. I tried with 18.0, damn, it still doesn't work, it still picks up that the phone is rooted
I tried the 18.2 canary build as well (18.2-e72c6685) no luck either
This app must be looking somewhere out of the ordinary for evidence of root in the phone
I have a bank application and facing the same problem. Hope someone can help us to make applications run by hiding the root
I think recent applications are looking for if knox security is tripped !! so in this case Magisk will not help
Ooohhh had to subscribe to this as I face the exact same issue!! Been trying to get my Square reader to work for a while with root and could never figure out how they are detecting root. Using Pixel XL here
Google changed something in Safety Net in play services, it passes, yet for me, google pay fails. That COULD be the issue, though I read 18.2 fixes that. Another option I helped a friend with is if it's detecting magisk itself via the files, culprit here was pokemon go.
Try opening your Magisk settings, the tick "hide magisk manager" clear the repo cache, and rename or delete the MagiskManager folder on the root of your storage. Reboot, clear data from the square app, and try again. Keep in mind, you have to unhide magisk to update it.
Skreelink said:
Google changed something in Safety Net in play services, it passes, yet for me, google pay fails. That COULD be the issue, though I read 18.2 fixes that. Another option I helped a friend with is if it's detecting magisk itself via the files, culprit here was pokemon go.
Try opening your Magisk settings, the tick "hide magisk manager" clear the repo cache, and rename or delete the MagiskManager folder on the root of your storage. Reboot, clear data from the square app, and try again. Keep in mind, you have to unhide magisk to update it.
Click to expand...
Click to collapse
In my case, I dont think its detecting the files. The reason i say that is because I play Pokemon Go just fine with no issues. So whatever Square is doing, its something different then what PoGo is doing.
Idledev said:
In my case, I dont think its detecting the files. The reason i say that is because I play Pokemon Go just fine with no issues. So whatever Square is doing, its something different then what PoGo is doing.
Click to expand...
Click to collapse
I agree, I have no problem hiding magisk and root from other apps, the square reader app must be somehow different. I've even gone through my storage and deleted any files or folders that might suggest the phone is rooted, but still no luck...
I also went into battery optimization settings to stop magisk from being put to sleep (which might stop magisk hide from working..?), that didn't work either.
I've found a temporary workaround to my problem anyway, I realized that I can share my internet (wifi hotspot) with my ipod touch, this way square reader works as the ipod touch isn't jailbroken or modified. It just means I have to carry around my ipod touch with me, which is a better trade off for me than having a stock, non root phone
Managed to get it working today! Upgraded my Pixel XL to the Android Q beta. By doing this, I had to run Magisk canary build. Installed square, enabled Magisk hide, rebooted and it worked fine! Not sure if the Android Q beta has anything to do with it,but give the canary builds of Magisk a try
Idledev said:
Managed to get it working today! Upgraded my Pixel XL to the Android Q beta. By doing this, I had to run Magisk canary build. Installed square, enabled Magisk hide, rebooted and it worked fine! Not sure if the Android Q beta has anything to do with it,but give the canary builds of Magisk a try
Click to expand...
Click to collapse
That's awesome! What canary build did you use?
I tried the latest build a few weeks ago and it didn't work for me
Build 18120
Idledev said:
Build 18120
Click to expand...
Click to collapse
No luck for me...
I updated to the latest canary build, cleared all data from square reader app, selected magisk hide, rebooted the device. After it booted up I tried to run it and it still detected root. I have a feeling that the OnePlus OS does something that doesn't totally allow me to hide root from the square reader app. It's annoying because for other apps root can be hidden
Maybe there's something in the Android Q build that lets you hide root better
Something that seems reliable right now on 18.1, Pixel Experience and OOS :
Combine Magisk Hide with Magisk "Core Mode". This seems to do the trick for now, Google Pay is triggered with normal mode, but works in Core Mode. Same for Snapchat and banking apps like N26.
But within this, you can't use any module.
kage00 said:
I also went into battery optimization settings to stop magisk from being put to sleep (which might stop magisk hide from working..?), that didn't work either.
Click to expand...
Click to collapse
This is always a good idea, on OOS at least, Magisk being optimized sometimes prevents the granting of root rights to apps, it never reacts to kernel applications requesting root on startup for example.
There's an issue with Googlypay services apparently. You need to downgrade it (remove factory updates) so it's down to version 14.something and then it should work.
You need to disable admin rights and background data to try to prevent autoupdates as well. This thread may be useful?
https://forum.xda-developers.com/ap...e-pay-magisk-discussion-t3906703/post79155616
DaveW1972 said:
There's an issue with Googlypay services apparently. You need to downgrade it (remove factory updates) so it's down to version 14.something and then it should work.
You need to disable admin rights and background data to try to prevent autoupdates as well. This thread may be useful?
https://forum.xda-developers.com/ap...e-pay-magisk-discussion-t3906703/post79155616
Click to expand...
Click to collapse
Hmm, I'm running the magisk xXx ROM and google pay is completely debloated/removed. when I get a spare half hour I might try removing the xXx module and flashing back to stock and following the advice in that thread. I'll let you know how it goes
kage00 said:
Hmm, I'm running the magisk xXx ROM and google pay is completely debloated/removed. when I get a spare half hour I might try removing the xXx module and flashing back to stock and following the advice in that thread. I'll let you know how it goes
Click to expand...
Click to collapse
Ummm yeah.. then the problem doesn't lie within Google pay it lies within the modifications that you are using.
I have to say I have never had any issues with Google pay or Android pay or any banking app using magisk. I don't even have to hide anyting. Of course I'm also not using any modified ROMs or kernels either
Hi guys,
I have this issue for a couple years now and I just cannot find a solution!
Google Pay, and 4 banking app from two different countries work fine with my 1+6 (stock ROM OOS 9.0.9 with magisk 19.4 - 7.3.4) but Square does not.
Did anyone find a solution?
Magisk config:
Magisk hide
Two modules OOS phone record and youtube
No core mode
All banking app and Square hidden
This evening, I tried flashing a Magisk module that replaces the stock keyboard sounds. In OOS 9, this worked. For some reason, it doesn't in OOS 10. I have the latest stable build of Magisk and after successfully flashing that same module (I didn't get any errors during the install), it no longer does anything. I can see the files are in /system/media/audio/ui. However, Gboard doesn't recognize those files; Neither does other keyboard apps like SimpleKeyboard.
It's not a huge deal for me right now, but I'm curious to know if this is an issue with other OOS 10 users (specifically, OP 6 users).
"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