Related
Hello,
I'm trying to use an app from the playstore called "vipps".
It's from a bank in norway called DNB, and it let's you transfer money near instantly from one to another.
This app refuses to run on my phone because it's rooted and have a custom rom etc.
I'm running Xtrestolite Deodexed with the included alliance firmware.
I have read somewhere about Rootcloak Plus with Cydia (no idea what this really is, but i understood cydia is like app store for iOS jailbreaked phones?)
I'm wondering if this exsists on 5.0.2 lollipop (and how to get it / install it if it does), or if there is any other known way of bypassing this applications refusal to run on my device.
I'm on a SM-G920F (international version) if that helps.
Any tips / questions / help regarding this is most welcome and much appreciated!
- Renolz
Try searching for a Xposed Module that does this
I remember there was one for kitkat but i dont know whether or not its currently available for lollipop
itsbighead said:
Try searching for a Xposed Module that does this
I remember there was one for kitkat but i dont know whether or not its currently available for lollipop
Click to expand...
Click to collapse
I tried to get xposed, but it's not yet compatible with the S6 as far as i know.
Something about SDK version 21 and arm 64 (no idea what this is, but that was the error when trying to install it)
renolz said:
I tried to get xposed, but it's not yet compatible with the S6 as far as i know.
Something about SDK version 21 and arm 64 (no idea what this is, but that was the error when trying to install it)
Click to expand...
Click to collapse
Cydia is for ios based devices and if s6 had xposed that module called root cloak will work for what you need it for. but since theres no xposed. You cant run it.
I second that!
I have the exact same problem! Please let me know if you find a way to bypass the app restrictions!
Same here:
Cyanogen OS 12.0, android 5.0.2, OnePlus One
Tried RootCloak plus app, add no.dnb.vipps app but still does not open.
I have the same issue with a Huawei running 4.4.4 Vipps by DNB does not work.. Xposed says that there is a known issue with the room installed. I deactivated the Resource hoocks, but it did not solve the issue.. BALLS!!
Mr.P
parrafin23 said:
I have the same issue with a Huawei running 4.4.4 Vipps by DNB does not work.. Xposed says that there is a known issue with the room installed. I deactivated the Resource hoocks, but it did not solve the issue.. BALLS!!
Mr.P
Click to expand...
Click to collapse
Hi,
I was able to fix the Vipps issue by using Rootcloak version 1.4 (not the newest one), and adding no.dnb.vipps to the list.
Works like a charm on SGS6
Hope this helps!
OPO CyanogenOS 12.1.1 Android 5.1.1 rootcloak vipps
I have a oneplus one With CyanogenOS 12.1.1-YOG7DAS2K1 and android version 5.1.1. The phone is rooted and I have twrp installed.
I used twrp to install Xposed framework 85 trough the link provided in this post: http://forum.xda-developers.com/showthread.php?t=3034811
Within the xposed installer app I downloaded the module RootCloak version 2.1.0
In rootCloak I added no.dnb.vipps (add/remove apps -> three dots -> add custom app -> write "no.dnb.vipps")
Now I can run vipps without any problems.
Vipps on OPO running cm14.1
Sorry to bring up an old thread.
I've been using this Norwegian bank app on cm12/cm13 with rootcloak for a while now without any trouble. Lately the app just crashed on login when using rootcloak so i decided to flash cm14.1 nightly and see if systemless root and magisk would do the trick instead. I flashed cm14.1, fully unrooted the phone, flashed magisk and phhs systemless root. I downloaded SafetyNet playground, and my phone passes all SafetyNet checks. I also downloaded pokémon GO to verify, and that works flawlessly. Vipps however, does not work... The app does not crash anymore, but i get the message "vipps doesn't support rooted devices".
It seems to me like the app detects that i'm running cyanogenmod. When my oneplus one was new, the app wouldn't work even though i had a locked bootloader and no root. I actually had to unlock bootloader, root, flash xposed and install rootcloak to get it working.
Is there any workaround for this problem? It seems to me that rootcloak did something more than just hide the root from the app. Is this correct? I can upload the .apk file for Vipps if that would be of any help. The app force closes before login with the message "Vipps doesn't support rooted devices", so i dont think region will be a problem.
I too am curious of this.
Is there a way to "fool" an app from checking if there is a custom ROM or original ROM?
I assume the app only checks ROM info, and perhaps that can be easily edited?
Magish Hide, checkmark:
com.android.phone
no.dnb.vipps
not sure if these are needed as well
com.slash.batterychargelimit
com.grarak.kerneladiutor
com.dp.logcatapp
Hi All,
Need help of this forum in solving a problem. The problem is in two parts.
1. I need to gain root access on my 7.1.1 on Merlin.
So can i use adb to gain root access ? Learnt something like this from giving elevated access to Greenify for doze. Can someone point to the right direction so that i can learn it to do myself and not depend on third party apps.
2. I have given administrator usages to Airwatch Agent which monitors whether i have root or not. If i gain root access then i lose the service and wont be able to view configured mails. So basically i need to root and not let all the apps know i have root. Somehow hide it.
Please guide. Thanks in advance.
deepray said:
Hi All,
Need help of this forum in solving a problem. The problem is in two parts.
1. I need to gain root access on my 7.1.1 on Merlin.
So can i use adb to gain root access ? Learnt something like this from giving elevated access to Greenify for doze. Can someone point to the right direction so that i can learn it to do myself and not depend on third party apps.
2. I have given administrator usages to Airwatch Agent which monitors whether i have root or not. If i gain root access then i lose the service and wont be able to view configured mails. So basically i need to root and not let all the apps know i have root. Somehow hide it.
Please guide. Thanks in advance.
Click to expand...
Click to collapse
Well, basically you are not going to get around AirWatch knowing you are rooted, even with Magisk if their Air Watch server is relatively current... I have tried and tried this (we sell and administer Airwatch for ourselves and lots of customers). Airwatch has been specifically designed to detect King*Root, SuperSU, and Magisk (and it's iPhone equivalents), and it uses far more advanced detection schemes than just SafetyNet, so far it hasn't been bypassed that we have seen on Android 6 and higher devices... (Android 5.1 and older have a different mechanism for bypassing root detection from Airwatch that apparently isn't possible with Marshmallow and higher). Also be aware that Airwatch will flag any device on a custom ROM of any kind too (rooted or not) as an incompatible device.
I don't think there is sufficient need for a detection bypass to be implemented into Magisk for Airwatch, and I am not sure the developers would even consider it, since it would be more about getting around a corporate security policy you agreed too more than just getting around some stupid restrictions from the Play Store or an app developer, but hey, it's worth a shot to ask I guess.
Getting around most apps knowing you have root is pretty simple with Magisk, but Airwatch and some of it's competitors MDM applications are much tougher to deal with.
To be honest you are better to just let Greenify go or to get a separate cheapo device just for your corporate email and keep root on your personal device.
Thats insightful.
Thanks a lot for the comments. I however have not seen Airwatch revoking my device enrollment even when i am running a custom ROM. It just checks whether i have root or not.
And can you guide how to use Magisk to root my Nougat on merlin.
deepray said:
Thanks a lot for the comments. I however have not seen Airwatch revoking my device enrollment even when i am running a custom ROM. It just checks whether i have root or not.
And can you guide how to use Magisk to root my Nougat on merlin.
Click to expand...
Click to collapse
Download Magisk and flash it... If your running a custom ROM with SuperSU or some other root built in, might want to ask in your ROM thread to see the right process.
Odd a custom ROM doesn't do anything weird... We have tried several ROM's on our Nexus device and every one will not allow device enrollment.
Confused
acejavelin said:
Download Magisk and flash it... If your running a custom ROM with SuperSU or some other root built in, might want to ask in your ROM thread to see the right process.
Odd a custom ROM doesn't do anything weird... We have tried several ROM's on our Nexus device and every one will not allow device enrollment.
Click to expand...
Click to collapse
I flashed magisk. It rooted my device. Could use greenify with root and lucky patcher with root too. Which means i have got root access. Now comes Airwatch Agent. It asked for root access And i denied it. So now my device is not unenrolled and i am able to use configured mails successfully. Happy. But confused.
deepray said:
I flashed magisk. It rooted my device. Could use greenify with root and lucky patcher with root too. Which means i have got root access. Now comes Airwatch Agent. It asked for root access And i denied it. So now my device is not unenrolled and i am able to use configured mails successfully. Happy. But confused.
Click to expand...
Click to collapse
So latest Magisk is not seen by AirWatch... Nice. I'll have to play with it again.
But there's a new problem now.
acejavelin said:
So latest Magisk is not seen by AirWatch... Nice. I'll have to play with it again.
Click to expand...
Click to collapse
I lost the root. Dont know why. I actually tried installing supersu from playstore which asked something like- do you want to copy binaries to somwhere and i said yes. To that effect my device was unenrolled by Airwatch Agent. Then i removed supersu and i was able to enrol my device again. But the next morning i am noy rooted anymore. Lucky patcher says root is not stable. Don't know what to do.
deepray said:
I lost the root. Dont know why. I actually tried installing supersu from playstore which asked something like- do you want to copy binaries to somwhere and i said yes. To that effect my device was unenrolled by Airwatch Agent. Then i removed supersu and i was able to enrol my device again. But the next morning i am noy rooted anymore. Lucky patcher says root is not stable. Don't know what to do.
Click to expand...
Click to collapse
You can't mix SuperSU and Magisk... after you flash Magisk you need to install Magisk Manager, but it isn't in the Play Store.
And BTW, don't mention Lucky Patcher here... that is purely a pirating app and users of it are thieves.
I will not assist you with anything to do with that software.
acejavelin said:
You can't mix SuperSU and Magisk... after you flash Magisk you need to install Magisk Manager, but it isn't in the Play Store.
And BTW, don't mention Lucky Patcher here... that is purely a pirating app and users of it are thieves.
I will not assist you with anything to do with that software.
Click to expand...
Click to collapse
I am sorry if i offended the community. I installed it as a means to achieve background play of YouTube as till Marshmallow, this was beautifully done by xposed mods. But as for Nougat as xposed is still in development, i needed that app.
I was not aware of other uses of that app. Nor do i have any further intention. Actually i tried using OG Youtube and the other app which was needed but that provided for popup only. Hope you understand.
deepray said:
I am sorry if i offended the community. I installed it as a means to achieve background play of YouTube as till Marshmallow, this was beautifully done by xposed mods. But as for Nougat as xposed is still in development, i needed that app.
I was not aware of other uses of that app. Nor do i have any further intention. Actually i tried using OG Youtube and the other app which was needed but that provided for popup only. Hope you understand.
Click to expand...
Click to collapse
Not really... Background playback on YouTube is a paid service, no matter how you bypass that it's stealing.
Trust me, I don't like it either but I'm not going to steal the service
acejavelin said:
Not really... Background playback on YouTube is a paid service, no matter how you bypass that it's stealing.
Trust me, I don't like it either but I'm not going to steal the service
Click to expand...
Click to collapse
Got the message. I found it difficult to draw the line though.
Magisk modules is similar to system less root by Chain fire which allowed users to get root access without modifying the system partition. Both apps are allowing uninterrupted installation for OTA updates even when the device is rooted.
Magisk download app can bypass the Safety Net on Android, enabling apps to work even on rooted Android phones. Magisk works system less.which you can install the OTA updates on your rooted phone without loosing the root access on your android phone. The better part of this app is that it works on Android 6.0.1 Marshmallow, 7.1.2 Nougat, up to Android O.
Advantages
You can use Snapchat without any issues.
You can use Financial/Banking applications
You can also play Pokemon Go on your rooted Android device.
You can install OTA updates on your device.
You can also install System-less Xposed framework on your lollipop and marshmallow devices.
You can use Android Pay.
You can also bypass SafetyNet
magiskandroid.com
hummm ... thanks for letting us know but that`s really old news ... https://forum.xda-developers.com/apps/magisk
thread closed
"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
Hi everyone.
to see if anyone can help me get full root please.
I have tried to root my "poco x3 pro" many times but to no avail.
According to magisk and root checker they say that if there is root but when using the apps, they request root access and according to magisk it grants it but then it says that the option is temporarily unavailable.
this happens to me with "es file Explorer", "root Essentials" "sixaxis controller" etc ,.
I already tried it with the global official miui, miui.eu and xperience rom, I installed it with twrp and with orangefox. Thank you very much and greetings.
Edit:
Well, it's appear that the apps I used, are incompatible and obsolete on android 11.
Magisk can grants root very well.
Thanks everyone
What magisk versions are you using
Try some other versions
LR7875 said:
What magisk versions are you using
Try some other versions
Click to expand...
Click to collapse
Hi. Thanks for answer
I try v21,22and23
Re-flash Stock ROM to get rid off of all modifications you applied so far.
jwoegerbauer said:
Re-flash Stock ROM to get rid off of all modifications you applied so far.
Click to expand...
Click to collapse
I already flash the stock rom and it remains the same
Not surprising me: don't think phone's Stock ROM ( Android 10 MIUI 12 ) is pre-rooted.
BTW:
To root phone's Android TWRP isn't needed, you achieve this by means of Magisk. How-to in detail is described here
How to Root Poco X3 & Unlock Bootloader: Step-by-Step Guide
One of the largest smartphone producers, Xiaomi has recently released its new device from Poco, the Poco X3. It has one NFC variant and a standard variant of Poco X3. Moreover, Xiaomi devices are best for customization, and to achieve this, one needs to root their device. Rooting a phone gives...
techburner.in
brakaman said:
I already flash the stock rom and it remains the same
Click to expand...
Click to collapse
Try fastboot method as shown here:
https://forum.xda-developers.com/t/4288121/post-85137969
pl1992aw said:
Try fastboot method as shown here:
https://forum.xda-developers.com/t/4288121/post-85137969
Click to expand...
Click to collapse
I did try it too. Thanks
did you install the manager after rooting?
brakaman said:
I did try it too. Thanks
Click to expand...
Click to collapse
Do you have other apps that can use root access?
For example: root explorer, MiXplorer, termux, terminal emulator... any apps that can use root.
Try them and see if those apps can get root access.
A) If those example apps can get root permission and works properly, then the problems are within those apps that does not work properly with root.
es file Explorer : original ones cannot be found on Play store, suspect lack of maintenance for new Android version
root Essentials : last update : October 27, 2017, some comment on Play store states issues for Android 10
sixaxis controller : can't find on Play store, last update found was 2017
B) If those example apps cannot get root permission, then prepare to do a clean flash, which will completely wipe data. Do backup of the data on your own.
jwoegerbauer said:
Not surprising me: don't think phone's Stock ROM ( Android 10 MIUI 12 ) is pre-rooted.
BTW:
To root phone's Android TWRP isn't needed, you achieve this by means of Magisk. How-to in detail is described here
How to Root Poco X3 & Unlock Bootloader: Step-by-Step Guide
One of the largest smartphone producers, Xiaomi has recently released its new device from Poco, the Poco X3. It has one NFC variant and a standard variant of Poco X3. Moreover, Xiaomi devices are best for customization, and to achieve this, one needs to root their device. Rooting a phone gives...
techburner.in
Click to expand...
Click to collapse
This phone it come with a11 miui 12
I did try that too
Thanks
Lu5ck said:
did you install the manager after rooting?
Click to expand...
Click to collapse
I did install it after and before
pl1992aw said:
Do you have other apps that can use root access?
For example: root explorer, MiXplorer, termux, terminal emulator... any apps that can use root.
Try them and see if those apps can get root access.
A) If those example apps can get root permission and works properly, then the problems are within those apps that does not work properly with root.
es file Explorer : original ones cannot be found on Play store, suspect lack of maintenance for new Android version
root Essentials : last update : October 27, 2017, some comment on Play store states issues for Android 10
sixaxis controller : can't find on Play store, last update found was 2017
B) If those example apps cannot get root permission, then prepare to do a clean flash, which will completely wipe data. Do backup of the data on your own.
Click to expand...
Click to collapse
pl1992aw said:
Do you have other apps that can use root access?
For example: root explorer, MiXplorer, termux, terminal emulator... any apps that can use root.
Try them and see if those apps can get root access.
A) If those example apps can get root permission and works properly, then the problems are within those apps that does not work properly with root.
es file Explorer : original ones cannot be found on Play store, suspect lack of maintenance for new Android version
root Essentials : last update : October 27, 2017, some comment on Play store states issues for Android 10
sixaxis controller : can't find on Play store, last update found was 2017
B) If those example apps cannot get root permission, then prepare to do a clean flash, which will completely wipe data. Do backup of the data on your own.
Click to expand...
Click to collapse
pl1992aw said:
Do you have other apps that can use root access?
For example: root explorer, MiXplorer, termux, terminal emulator... any apps that can use root.
Try them and see if those apps can get root access.
A) If those example apps can get root permission and works properly, then the problems are within those apps that does not work properly with root.
es file Explorer : original ones cannot be found on Play store, suspect lack of maintenance for new Android version
root Essentials : last update : October 27, 2017, some comment on Play store states issues for Android 10
sixaxis controller : can't find on Play store, last update found was 2017
B) If those example apps cannot get root permission, then prepare to do a clean flash, which will completely wipe data. Do backup of the data on your own.
Click to expand...
Click to collapse
Hi.
Appear you're right
The example apps can get root.
So my apps are incompatible.
I almost get crazy
Well thank you so much.
Now I need to fix the apps or find another's.