Related
So I've been getting lots of different questions about how to get this and that on android 7.0 nougat so to make it easier for everyone to find ill create this thread.
1. TWRP
Is twrp available for N? If so where can I find it?
http://forum.xda-developers.com/p9/how-to/twrp-3-0-2-0-n-t3506947
2. ROOT
Oh cool now I have twrp. So how can I root?
Download phh r275 version and flash
Download and install Material phh apk: Release post
Now you should be good to go. If any issues feel free to ask here or in phh official thread.
3. BUSYBOX
User friendly zip flash this and the below steps isn't needed!
Flashable zip (1.25.1) : https://mega.nz/#!zlRm3S4B!9rAtfi0wI8oFu6xjJITgF0dRwV21UPsxvZQZzMo6VXk
This one is a bit tricky. If you run root. But
Download jrummy's busybox on Gplay.
Select installation folder to /system/xbin or if u don't want to touch system folder use /sbin if available. U can replace jrummy''s busybox with stericsson version if you like it better. But you must have installed jrummys version first if you're booted into android. Else stericsson busybox might have issues installing. Or u can use zips which contains busybox Google busybox flashable.
4. VIPER
More user friendly if using this zip the below steps should only need se Linux mode changer!
Flashable zip: https://mega.nz/#!f8wlzIrB!vVCAv-xqWB8lOrcQTgIyFL0WS7MFsE9iFb08E1YKV2Y
Is quite a mess to get working. You need se Linux mode set to permissive. Flash guitarheroes version of v4a (2.5.0.5) once flashed you need to replace the audio effects in /vendor/etc/audio_effects else you'll get I/O driver installation failed. Copy the .so files to /system/lib and /system/lib64 and set correct permission. If you have wrong busybox message. Try different versions of busybox but I use latest from stericsson and it works great. Hope u get it working.
Oh and don't forget to allow sd storage access or you'll get driver I/O error as well. And se Linux changed to permissive use se Linux mode changer for it. It works great with phh!
5. MAGISK
As it seems to be now. Magisk won't work due to loop issues on boot. And mount seems to have losetup fail 1 on mounting a .img while booted.
6. Xposed
Not yet available. Be patient rovo needs time we can wait for him
7. comes soon.
More stuff.
Sent from my FRD-L09 using Tapatalk
how does your audio_effects.conf look like? i used one for aosp from "ARISE+Sound+Systems+Deuteronomy+2.3.3.zip" and got it working but don`t know if this is the right one for our device (huawei phones).
paratox said:
how does your audio_effects.conf look like? i used one for aosp from "ARISE+Sound+Systems+Deuteronomy+2.3.3.zip" and got it working but don`t know if this is the right one for our device (huawei phones).
Click to expand...
Click to collapse
It doesn't matter if it's aosp. Since it is for v4a it will work. As long as the audio effects works it doesn't matter.
Also I just finished my hopefully new nougat viper4android zip (i made my own for M with material designed version for my s5 neo) which worked fine until now.
Now it extract all files to its locations even to /vendor partition which all zips I used previously never had. I'll also update busybox zip which previous available is 1.24.2 which I'll bump up to 1.25.1.
I'll also going to upload my stuff to android file host. But that will be later
New files can be found https://mega.nz/#F!HlpzlaZL!wGNoJinVPZL0YiBcdbLlKA
Tapatalk is messing with the link
Sent from my FRD-L09 using Tapatalk
Updated op with latest busybox by stericsson. More user friendly now
Sent from my FRD-L09 using Tapatalk
LastStandingDroid said:
Updated op with latest busybox by stericsson. More user friendly now
Click to expand...
Click to collapse
Nice job mate!
dodgedroid said:
Nice job mate!
Click to expand...
Click to collapse
Easy to do when you got a zip for it just update the busybox executable and replace old one
Sent from my FRD-L09 using Tapatalk
Installation of ARISE
paratox said:
how does your audio_effects.conf look like? i used one for aosp from "ARISE+Sound+Systems+Deuteronomy+2.3.3.zip" and got it working but don`t know if this is the right one for our device (huawei phones).
Click to expand...
Click to collapse
How did you installed ARISE in Nougat?
I've been trying all day and I'll always end with an I/O or Busybox error. I tried a lot of things, like changing /vendor/etc/audio_effect.conf to audio_effect.conf.bak or installing Busybox into system/bin, but none of them seems to work for me.
I'm on B361 btw. And sorry for answering an old post
LastStandingDroid said:
Also I just finished my hopefully new nougat viper4android zip (i made my own for M with material designed version for my s5 neo) which worked fine until now.
Now it extract all files to its locations even to /vendor partition which all zips I used previously never had...
New files can be found https://mega.nz/#F!HlpzlaZL!wGNoJinVPZL0YiBcdbLlKA
Click to expand...
Click to collapse
Do you know, is your Viper4Android installer compatible with the following rooting/Busybox configuration:
- L09 c432/b378
- TWRP 3.1.0-0
- SuperSU-v2.79-201612051815-EMUI5.0.zip
- Rummy"s BusyBox (installed to /system/xbin)
as described by @hakaz and @Atarii in the post #102 and follow-ups:
https://forum.xda-developers.com/showpost.php?p=71588837&postcount=102
Also, should SELinux really be switched to Permissive mode for V4A to work on P9 with Nougat?
Thanks
zgfg said:
Do you know, is your Viper4Android installer compatible with the following rooting/Busybox configuration:
- L09 c432/b378
- TWRP 3.1.0-0
- SuperSU-v2.79-201612051815-EMUI5.0.zip
- Rummy"s BusyBox (installed to /system/xbin)
as described by @hakaz and @Atarii in the post #102 and follow-ups:
https://forum.xda-developers.com/showpost.php?p=71588837&postcount=102
Also, should SELinux really be switched to Permissive mode for V4A to work on P9 with Nougat?
Thanks
Click to expand...
Click to collapse
Yes it should be compatible and yes u need to switch to permissive mode else it'll be asking you to install over again, or simply not start to work
Sent from my CUBOT_MANITO using Tapatalk
LastStandingDroid said:
Yes it should be compatible and yes u need to switch to permissive mode else it'll be asking you to install over again, or simply not start to work
Click to expand...
Click to collapse
Yes, thanks, I have flashed your Viper.zip through TWRP and installed vViPERFX_v2.5.0.5.apk
I have also installed SELinuxModeChanger and set SELinux mode to stay Permissive over rebooting
Viper4Android works fine - thanks
LastStandingDroid said:
5. MAGISK
As it seems to be now. Magisk won't work due to loop issues on boot. And mount seems to have losetup fail 1 on mounting a .img while booted.
Click to expand...
Click to collapse
in my p9 lite emui 5.0 magisk is successfully installed !
it worked by flashing the modded boot.img by @HassanMirza01 and by setting selinux to permissive !!
big thanks to @Paolo83 who found this method
simo255 said:
in my p9 lite emui 5.0 magisk is successfully installed !
it worked by flashing the modded boot.img by @HassanMirza01 and by setting selinux to permissive !!
big thanks to @Paolo83 who found this method
Click to expand...
Click to collapse
Having Magisk, can you now also install Xposed?
PS: Please provide links to your resources and threads.
Btw, you have P9 Lite - does the method for Magisk apply also to (regular) P9 (single SIM)?
zgfg said:
Having Magisk, can you now also install Xposed?
PS: Please provide links to your resources and threads.
Btw, you have P9 Lite - does the method for Magisk apply also to (regular) P9 (single SIM)?
Click to expand...
Click to collapse
it workes because we have a modded boot.img created by @HassanMirza01, ask him what he did so as to he will do the same for p9 boot.img(or anyone else)
install selinux and set it to permissive, after that install magisk app via playstore and click on autoinstall
no xposed isnt working because there is no xposed for Nougat.
simo255 said:
it workes because we have a modded boot.img created by @HassanMirza01, ask him what he did so as to he will do the same for p9 boot.img(or anyone else)
install selinux and set it to permissive, after that install magisk app via playstore and click on autoinstall
no xposed isnt working because there is no xposed for Nougat.
Click to expand...
Click to collapse
Can you post the link to install his kernel?
Danymat said:
Can you post the link to install his kernel?
Click to expand...
Click to collapse
it won't work because it's a boot.img of p9 lite not for p9
simo255 said:
it won't work because it's a boot.img of p9 lite not for p9
Click to expand...
Click to collapse
So for p9 we don't have any solutions to install magisk?
Danymat said:
So for p9 we don't have any solutions to install magisk?
Click to expand...
Click to collapse
try to install the pre rooted boot.img (phh one) via this link https://forum.xda-developers.com/p9/development/root-pre-rooted-boot-img-p9-nougat-b378-t3574548
and follow the steps that i wrote above
simo255 said:
in my p9 lite emui 5.0 magisk is successfully installed !
it worked by flashing the modded boot.img by @HassanMirza01 and by setting selinux to permissive !!
big thanks to @Paolo83 who found this method
Click to expand...
Click to collapse
Is this using a Magisk.img in /data folder?
As said magisk can be made working since we had supersu working by chain I still doubt it uses a loop
Sent from my CUBOT_MANITO using Tapatalk
LastStandingDroid said:
Is this using a Magisk.img in /data folder?
As said magisk can be made working since we had supersu working by chain I still doubt it uses a loop
Click to expand...
Click to collapse
no there is no magisk.img folder, but there is a magisk folder which include those files (look at the screenshot
simo255 said:
no there is no magisk.img folder, but there is a magisk folder which include those files (look at the screenshot
Click to expand...
Click to collapse
Yes this is how Magisk is being made working
Sent from my CUBOT_MANITO using Tapatalk
Hi guys,
My Pixel are systemlessly rooted with Magisk since many months now, but for some reasons I'm tired by the method of Magisk: I want to touch at the /system partition, move or delete or edit system files and apps, and with Magisk I can't do it.
Okay, Magisk was pretty useful for keeping Safetynet pass, but with Xposed this ability becomes useless for me. Only things I'm still using is Magisk Hide for using Netflix or NFC paiment app, and Sony Framework module for using PS4 Remote Play.
Before I'm using Magisk and his systemless mode I was using SuperSU, and with it I had no problem with the system partition or with différents things like flashing Viper4android (didn't works whatever the way I use, magisk module or old system mode, it says the drivers need to be reinstalled), mouting partition/making file partition in Linux Deploy, stop background app, modifying the booting apps...
So I'm here now: are they exist a method for having system mode root and still using magisk modules ? Or maybe I've using the wrong way with Magisk and I've missed something for properly having root access ?
Thanks for your help ?
billiepreks said:
So I'm here now: are they exist a method for having system mode root and still using magisk modules ? Or maybe I've using the wrong way with Magisk and I've missed something for properly having root access ?
Thanks for your help ?
Click to expand...
Click to collapse
the whole point of magisk is to systemless modifications. I'm not sure that I follow all of the modifications that you want to make to the system partition?? or rather the specific apps that you want to use... but I can tell you that your /system partition (and others) are just mirrored with magisk and are tmpfs file systems...
I think the real /system lives in /dev/magisk/mirror/system, unless I'm mistaken....
question though; if you prefer SuperSU and only use magisk for safetynet, then why not just use a custom kernel that passes safetynet + SuperSU + suhide?. ... and then use that xposed or whatever....
anyhoo, you definitely have root access. but the intention with magisk and it's modules is to modify the system without actually modifying it directly....
nine7nine said:
the whole point of magisk is to systemless modifications. I'm not sure that I follow all of the modifications that you want to make to the system partition?? or rather the specific apps that you want to use... but I can tell you that your /system partition (and others) are just mirrored with magisk and are tmpfs file systems...
I think the real /system lives in /dev/magisk/mirror/system, unless I'm mistaken....
question though; if you prefer SuperSU and only use magisk for safetynet, then why not just use a custom kernel that passes safetynet + SuperSU + suhide?. ... and then use that xposed or whatever....
anyhoo, you definitely have root access. but the intention with magisk and it's modules is to modify the system without actually modifying it directly....
Click to expand...
Click to collapse
Thanks for your help ?
If Magisk create a mirror of /system as your said, this explain many things that I didn't knew since now.
This night I've made a clean installation of my Pixel, on stock 7.1.2 NJH47F with ElementalX 1.15 for hiding the unlocked bootloader, then I've flashed SuperSU 2.82 SR5. On xda I've seen that suhide 0.55 are discontinued since one year, and suhide-lite 1.09 who works with SuperSU 2.89 are uncompatible with Xposed, so I didn't flash it. There is a way to hide SuperSU with Xposed ?
For my needs with the /system partition, I'll try to explain better myself, I give you some examples:
- Uninstalling system app in ES Explorer or TiBu, it works but after reboot those apps are still here.
- Editing files like build.prop, unable to save the edited file or to replace original file by a modified one
- installing Viper4android drivers, it says "drivers needs to be reinstalled" everytime I launch it
- Linux Deploy, an app for running GNU/Linux distrib on your device, works the first time I launch it, but after reboot he said he didn't get root permission or found busybox, it's very strange.
Many things who worked before with SuperSU 2.79.
Edit : and what about SuperSU and CCMT ?
billiepreks said:
If Magisk create a mirror of /system as your said, this explain many things that I didn't knew since now.
This night I've made a clean installation of my Pixel, on stock 7.1.2 NJH47F with ElementalX 1.15 for hiding the unlocked bootloader, then I've flashed SuperSU 2.82 SR5. On xda I've seen that suhide 0.55 are discontinued since one year, and suhide-lite 1.09 who works with SuperSU 2.89 are uncompatible with Xposed, so I didn't flash it. There is a way to hide SuperSU with Xposed ?
Click to expand...
Click to collapse
You should look in Magisk's log to get a better idea of how it changes your system. trting to modify /system is pointless since it is a tmpfs mount (temperary)...
unfortunately, i can't help much with xposed. i don't use it. after it didn't work with Nougat, i ported a couple of it's modules to my rom (at the time) and then i got the pixel and i run Oreo + my own custom kernel + magisk...
xposed isn't providing any 'suhide' tyype functionality?
billiepreks said:
For my needs with the /system partition, I'll try to explain better myself, I give you some examples:
- Uninstalling system app in ES Explorer or TiBu, it works but after reboot those apps are still here.
- Editing files like build.prop, unable to save the edited file or to replace original file by a modified one
Click to expand...
Click to collapse
again, no point in editing your /system partition, it's a tmpfs mount, of course - any modifications will disappear on reboot.... you probably need to edit the real /system partition to make any change stick.
as far as the other apps, they obviously are trying to modify your aystem partition, which is why they don't work.... i think that you could install soumd mods via magisk modules?
i would recommend.consulting relevant forum threads on specific topics/apps though. u are bound to get better solutions&.
@billiepreks
Did you find the solution?
I'm in the same situation.
Did you try using TWRP's filemanager? I think it has true system access. You just need to mount the partition.
"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
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.
I want to edit hosts file in my non-rooted Android device.
Since flashing a Custom ROM is basically installing a new OS, I was wondering,
Is a hosts file already present in a Custom ROM or is it generated later and at what point?
If it is preincluded in the ROM, is it possible to edit that hosts file and then flash the ROM, basically editing the hosts file without rooting?
parker_04 said:
I want to edit hosts file in my non-rooted Android device.
Since flashing a Custom ROM is basically installing a new OS, I was wondering,
Is a hosts file already present in a Custom ROM or is it generated later and at what point?
If it is preincluded in the ROM, is it possible to edit that hosts file and then flash the ROM, basically editing the hosts file without rooting?
Click to expand...
Click to collapse
Some custom ROMs do include custom hosts files, and you could potentially edit it before flashing the ROM. I'm not sure why you'd want to use a custom ROM without root, though - with root access, you can use a hosts manager like AdAway to update your hosts file on the fly.
V0latyle said:
Some custom ROMs do include custom hosts files, and you could potentially edit it before flashing the ROM. I'm not sure why you'd want to use a custom ROM without root, though - with root access, you can use a hosts manager like AdAway to update your hosts file on the fly.
Click to expand...
Click to collapse
(I am a newbie in rooting and flashing Custom ROM so please correct me)
Well my main objective is to edit the hosts file.
I understand it generally require root privileges but I want to use rooting as a last resort.
I am already going to flash Xiaomi Eu ROM in my Redmi Note 11. And if it is possible to edit the hosts via the ROM, wouldn't it be a better alternative than rooting? As with rooting, there also comes some consequences like tripping SafetyNet which I would gladly like to avoid.
parker_04 said:
(I am a newbie in rooting and flashing Custom ROM so please correct me)
Well my main objective is to edit the hosts file.
I understand it generally require root privileges but I want to use rooting as a last resort.
I am already going to flash Xiaomi Eu ROM in my Redmi Note 11. And if it is possible to edit the hosts via the ROM, wouldn't it be a better alternative than rooting? As with rooting, there also comes some consequences like tripping SafetyNet which I would gladly like to avoid.
Click to expand...
Click to collapse
SafetyNet is no longer relevant; it has been replaced by Play Integrity. See this thread. Even so, it is possible to pass Play Integrity BASIC and DEVICE attestation using the Universal SafetyNet Fix Magisk module.
I'm rooted with Magisk 25.2 on my Pixel 5. I use AdAway to manage my hosts file, and USNF 2.3.1 MOD 2, and I have zero issues with Play Integrity.
O
V0latyle said:
SafetyNet is no longer relevant; it has been replaced by Play Integrity. See this thread. Even so, it is possible to pass Play Integrity BASIC and DEVICE attestation using the Universal SafetyNet Fix Magisk module.
I'm rooted with Magisk 25.2 on my Pixel 5. I use AdAway to manage my hosts file, and USNF 2.3.1 MOD 2, and I have zero issues with Play Integrity.
Click to expand...
Click to collapse
I see.
But SafetyNet/Play Integrity is only one of the consequences of rooting. In Xiaomi devices, the warranty remains intact even after unlocking bootloader unless the device is rooted.
I am happy with flashing Custom ROM with edited hosts file without rooting.
I can always root my device later if this doesn't work.
Unless there is some other drawback which I am not aware of. If there is, please inform me so I don't end up in a mess.
parker_04 said:
I see.
But SafetyNet/Play Integrity is only one of the consequences of rooting. In Xiaomi devices, the warranty remains intact even after unlocking bootloader unless the device is rooted.
Click to expand...
Click to collapse
How would they know whether you rooted the device?
I can see how flashing custom firmware could void the warranty, like Samsung...So I suppose I've answered my own question as rooting would ostensibly involve either patching the boot image or installing SU to system. But, if you're editing a hosts file, you're also changing the system image, so I would assume that this would do the same thing.
parker_04 said:
I am happy with flashing Custom ROM with edited hosts file without rooting.
I can always root my device later if this doesn't work.
Unless there is some other drawback which I am not aware of. If there is, please inform me so I don't end up in a mess.
Click to expand...
Click to collapse
Well, as I pointed out above, you're making modifications to the software. If you're concerned about the warranty, don't use ANY modified software on your device, and keep your bootloader locked. You can't have your cake and eat it too.