Related
Newest update has blocked access to rooted phones. Even after hiding/ removing root access privileges (I've tried both hiding and un-rooting) I cannot log in, so I'm left only to assume that the version of the OS itself is blocked.
Simple question: Does anyone know of a way around this? I see hundreds of posts about magisk, but I cannot do that while using slimkat ( magisk requires android 5.0+)
I've really gotten into this game over the last coiuple months, but I refuse to revert to some vanilla stock version of android to play. If anyone could provide any info I'd greatly appreciate it.
I'd do what I always do when I need/want to run something of that nature: I install a "sacrificial ROM" alongside my Slim using MultiRom and boot into it when needed.
So...an app demands a non-rooted ROM? No problem: Here's a plain vanilla AOS sandbox for you to play in.
I'm playing to PoGo with any issues with SlimRom 6, I just deleted a file called su.bin from /system/bin and /system/xbin.
This erases root of the rom, and make it playable. Use SafetyNetHelper on Google Play Store to check if you pass the test (PoGo uses this test).
You can delete them (you have to delete both) on the file manager of TWRP.
The way i got mine to work(i can also use the Fake GPS hack with my POgo as well! ) is 1st i downloaded an already rooted(with SuperSU) rom for my phone off of xda and i installed the fake gps app through ucky patcher to make it a system app. i then downloaded a stock rom for my phone from here at xda, and i flashed it using Odin, this replaced everything to make it stock again but kept my system files(the fake gps app) so then all i had to do was redownload PoGo and login as normal and voila! their security check diverted and still able to fake gps it lol
"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
I made everything needed (i guess) on my old Oneplus One by following multiples guides:
1. formatted phone data, cache, system, dalvik
2. installed lineageOS 16 (android 9) and TWRP
3. rooted by flashing magisk, updated magisk and magisk manager, then i've hidden magisk itself and changed its name to GamePuzzle
4. installed FakeGPS Joystick (The App Ninjas), then unlocked full features, reinstalled with new name (Tetris), deleted the original one, in the end i've setted up my cloned app as mock position in developer settings. Also enabled "prevent app from screenshot" or something like that in GPS Joystick settings.
5. Followed a guide how to delete ADS from GPS Joystick (worked using lucky patcher).
6. Finally, followed Smali's guide, before zip creation i selected patches 1 and 4, then installed .zip module from recovery.
What i got? GPS Joystick works for real, but i have an error screen every 1-5 minutes (it's just random) which says my device is not supported. I was pretty sure it was for root's fault: then i tried uninstalling Magisk and Magisk manager too, and now i haven't that error message after 3 hours.
What can i have done wrong?
Solved, problem was all the .apk files and folders which contained words like "root" or "fakegps" in their name. I just deleted them and now works fine.
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.
As the title suggest, I'm trying to bypass a root check for an app, more specifically MyMazda App. I have tried several different methods ( repacking Magisk, Root Cloak, LSposed/Xpirvacy, Unviersal SafteyFix Patch ). None seem to work, my bank, credit and stock exchange apps work completely fine along with every other app except this one. I'm running on a complete stock ROM.
I am running:
Oneplus 8 Pro
Android 11
OxygenOS 11.0.10.10.IN11AA
Magisk v24.1
This raised a few questions:
1. Is it even possible to bypass this apps root check?
2. If it is and when I do bypass it, will all the features work (ie. Remote Start/Stop, Remote Lock/Unlock, etc.)?
3. If there is no way, will downgrading Magisk to when MagiskHide was in the app?
4. And if I do need to downgrade, is there aspecific procedure for the Op8 Pro or is just like any other phone?
Sidenote: I am very new to this, I only just rooted my phone 2 days ago, without any issues thankfully, so I may have missed something important to one of the modules for it to work. Thank you in advanced!
Checking whether Android is rooted or not basically requires only 1 line of program code.
xXx yYy said:
Checking whether Android is rooted or not basically requires only 1 line of program code.
Click to expand...
Click to collapse
Interesting, then how come this app is causing so much issues compared to my banking apps and such?