I have never used a Pixel phone, but I am strongly considering a Pixel 6 now. I want to root the phone using Magisk **and** I want to successfully hide root. Furthermore, I want to be able to install some modules in an Xposed-like framework such as LSPosed, and I want the existence of that XPosed-like framework also to be hidden. Ever since Android 11, it's been complicated and confusing to figure out how to accomplish all of this in a reliable manner, given the latest changing versions of Magisk and given the various root-hiding mechanisms that are now offered, and which are also now still in development.
There is a huge amount of information about this general topic in the following threads ...
https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/page-2689#post-87696219
https://forum.xda-developers.com/t/discussion-magisk-the-age-of-zygisk.4393877/
https://forum.xda-developers.com/t/...r-unofficial-third-party-magisk-fork.4460555/
https://forum.xda-developers.com/t/lsposed-xposed-framework-8-1-13-0-simple-magisk-module.4228973/
... however, there are collectively more than 50,000 messages in this group of threads, and for me, this fits into the category of "Too Much Information", especialy given that much of this info is contradictory, with different people reporting success and others reporting failure, and different people reporting slightly different versions of the same procedures.
The reason I'm posting here is that I'm wondering of anyone has successfully accomplished what I'm trying to do with a Pixel 6 under Android 11 or Android 12, and if so, whether that person (or people) might be willing to share a straightforward, step-by-step, cookbook-like set of instructions about how to accomplish all of this from beginning to end.
By "beginning to end", I mean to start with a brand new locked Pixel 6 and to install all of the software and features that I described above, with the end result being a reliably rooted Pixel 6 (with root reliably hidden) running some sort of XPosed-like framework under Android 11 or Android 12, and which can be consistently rebooted with no boot loops.
If that is considered off-topic here, I'm glad to take this into private chat.
Thank you very much in advance for any help that you might be able to offer.
What he said, but instead of android 11 or 12, give me one for 13 please.
Oh! I somehow overlooked the following thread when I first came here:
https://forum.xda-developers.com/t/...nlock-bootloader-pass-safetynet-more.4388733/
It covers a lot of the information I'm looking for.
I will soon dig into that thread in more detail, and if it indeed ends up explaining everything that I want to learn, then I will abandon this current thread.
But for the moment, I'll keep this thread alive.
I can confirm my rooted Pixel 6 running 13 passes SafetyNet check and is certified in the Play app following those instructions. However, Google is not using SafetyNet to check for an unlocked bootloader in their apps anymore. GPay complains about device security and there are some apps that I can't download. Netflix, Hulu. Other than GApp and having to sideload Netflix, I don't have any issues.
Here's a thread about the new security check.
https://forum.xda-developers.com/t/discussion-play-integrity-api.4479337/
anyone having issues with some apps detecting root even after magiskhide should try the shamiko module. helped me
few stupid questions regarding rooting my pixel 6 .....
1) its new unlocked phone, should i have the new SIM in phone when rooting, does it matter ?
ok to put it when its done ?
same question for being signed into Google account when rooting, does it even matter, either way ?
2) is there a way to get the pixel phone transfer to show back up, or a way to access it ?
Its very easy for me to transfer all backed up data from my current Pixel 3 that way...
3) can I still run my banking & crypto apps once rooted ? I have read conflicting reports on this... elsewhere that is.
Thank y'all for the awesome information ya provide on here, and Thank You in advance if you have any input for me rooting...
Its amazing how far along we've come along since my bag phone
kengel1969 said:
few stupid questions regarding rooting my pixel 6 .....
1) its new unlocked phone, should i have the new SIM in phone when rooting, does it matter ?
ok to put it when its done ?
same question for being signed into Google account when rooting, does it even matter, either way ?
2) is there a way to get the pixel phone transfer to show back up, or a way to access it ?
Its very easy for me to transfer all backed up data from my current Pixel 3 that way...
3) can I still run my banking & crypto apps once rooted ? I have read conflicting reports on this... elsewhere that is.
Thank y'all for the awesome information ya provide on here, and Thank You in advance if you have any input for me rooting...
Its amazing how far along we've come along since my bag phone
Click to expand...
Click to collapse
1. No, yes, no
2. Yes, kind of
3. Yes with safetynet module and magisk deny list, and sometimes magisk props.
Read @Volatyle's and @Homeboy76's guides. Great info in both.
It would be better if you explained what your end result is. Hiding root can be very difficult; depending on the app requirements, simply having an unlocked bootloader can be enough, because an unlocked device will always fail hardware backed attestation.
If you're simply trying to get apps like Google Pay to work, you should need to do nothing more than install Displax's modded USNF module, and enforce DenyList on the Play Store and Play Protect service.
If on the other hand you're trying to use apps that specifically detect the presence of Magisk, then you may need to hide the Magisk app. As far as hiding the presence of root itself, I am unsure as to whether any app without root privileges can detect whether an SU binary is installed. Someone like @pndwal would know better than I would.
Related
Is there currently a way to have both the Amazon App store and the Google Play store working together? On the newest update?
Does rooting have any adverse affects from Amazon? Like will anything stop working?
I plan on buying a used tablet, how can I check to make sure the tablet is deactivated so that I can use my own Amazon stuff on it and it doesn't get marked as stolen?
I may think of other questions I need help with in the meantime, but thanks for any help.
everwhere
Hobox10 said:
Is there currently a way to have both the Amazon App store and the Google Play store working together? On the newest update?
Does rooting have any adverse affects from Amazon? Like will anything stop working?
I plan on buying a used tablet, how can I check to make sure the tablet is deactivated so that I can use my own Amazon stuff on it and it doesn't get marked as stolen?
I may think of other questions I need help with in the meantime, but thanks for any help.
Click to expand...
Click to collapse
Check out the general section, you will find the anwser you seek. if you have any other questions there is also a search abilility..there are only about a half a dozen threads titled with the same or basically the same as yours...thanks for visiting and I hope you find all the information you need. Previous owner must unregister. the tablet from their account before u received it.and I would attempt to register it and setup your account before cash exchanges hands or contact amazon with id to verify that it has not been blackliisted already, it can either be unregistered by owner from tab then reset . Or done through ther online account..
A lot of the threads I have read seem to have people contradicting or trying to figure out what actually works or not, or is simply outdated.
Yeah, I'm with OP. I have a new Fire HDX and am trying to figure out the 'best' way to root it, and after reading through everything I'm more confused than before.
I haven't taken my Fire out of the box yet. There seems to be discussion that if I haven't downloaded an OTA yet, I can root in a way others can't because the new updates block it?
Is there a known "best" ROM someone can point us to?
Why do I keep seeing everyone say 'don't ever turn on wifi!'? I assume that is just to not get the OTA update at the beginning. But once rooted, obv we can use wifi right?
Is every root method dependant on creating a separate partition for the new ROM, and whenever we use the Kindle we have to choose to use the stock amazon rom or the new ROM we've flashed?
Thanks!
well
lordtigger said:
Yeah, I'm with OP. I have a new Fire HDX and am trying to figure out the 'best' way to root it, and after reading through everything I'm more confused than before.
I haven't taken my Fire out of the box yet. There seems to be discussion that if I haven't downloaded an OTA yet, I can root in a way others can't because the new updates block it?
Is there a known "best" ROM someone can point us to?
Why do I keep seeing everyone say 'don't ever turn on wifi!'? I assume that is just to not get the OTA update at the beginning. But once rooted, obv we can use wifi right?
Is every root method dependant on creating a separate partition for the new ROM, and whenever we use the Kindle we have to choose to use the stock amazon rom or the new ROM we've flashed?
Thanks!
Click to expand...
Click to collapse
Well "root"has nothing to do with seperate partitions n such. root is all permission control over system.
The only way to flash anything currently is being on older os rooting,then installing safestrap which will set up alternate system and data boot path allowing you to flash a ROM separately from your factory os ,as to not disturb it. Because currently we do not have stable working fastboot for this device. As for BEST rom. In any situation is totally in one own experience and opinions. Currently there isn't any selection if u look in development section the only two that function only work on old firmware ...you can roll back to that firmware ..but also bootloader is locked tight thus the need for a "safe" type of recovery as of moment only works on older firmware also. Just.within the last couple of days have reveiled a couple of rooting options for lastest firmware so ...this tab per Amazon gives no warning nor asks permission to upgrade of firmware which unrooted a ton of people last few months...soooo no root no development....now we have root again we will get going again..Have fun and most of all be PATIENT and do not ask for ETA remember all the developers here are doing that on there FreeTime and free of pay most the time. AS FAR as rooting and adding gapps to newest firmware I heard that it has been achieved with HDXPOSED found in development and permission module . Then sideload gapps... As far as adverse effects... Like I said you will have to be patient if you want somebody else to find out bugs for you.. still to new .....due to new root releases..like last three days.
I'm perfectly fine with the stock rom honestly, as long as I can get Google Play store working alongside the Amazon app store. Now, assuming I can root when I receive the tablet, I will install safestrap. Is there any bugs or anything with safestrap but just using the stock rom? I saw some people mention getting permission errors and such but I think that was just for custom roms in another slot. I only want safestrap to make a backup.
Basically, is there any actual danger to modifying the stock rom at all, even something simply like play store? Or should it all be done on a custom rom slot? I would assume having the backup would mean if something got messed up I can just restore it.
Secondly, there is a SEPARATE play store mod you can do where they don't both work together right? I believe I saw something about it where you just have to install a custom launcher, and with the custom launcher the google play apps work but under the amazon launcher, amazon stuff works? If that's correct, does that work without root? Because I can live with that temporarily until root is secured.
Thanks.
nope
Hobox10 said:
I'm perfectly fine with the stock rom honestly, as long as I can get Google Play store working alongside the Amazon app store. Now, assuming I can root when I receive the tablet, I will install safestrap. Is there any bugs or anything with safestrap but just using the stock rom? I saw some people mention getting permission errors and such but I think that was just for custom roms in another slot. I only want safestrap to make a backup.
Basically, is there any actual danger to modifying the stock rom at all, even something simply like play store? Or should it all be done on a custom rom slot? I would assume having the backup would mean if something got messed up I can just restore it.
Secondly, there is a SEPARATE play store mod you can do where they don't both work together right? I believe I saw something about it where you just have to install a custom launcher, and with the custom launcher the google play apps work but under the amazon launcher, amazon stuff works? If that's correct, does that work without root? Because I can live with that temporarily until root is secured.
Thanks.
Click to expand...
Click to collapse
As far as I know gapps aside from gmail will not work without root and HDXposed..(fixes permissions)and as far as doing any mods to stock slot it is not advised because of very difficult if even possible recovery due to no fastboot capabilities. Check for bugs for any mods in associated threads. As far as flashing anything ,again I am not sure safestrap is functioning on latest firmware .. And there hasn't been enough time for any development because of the recent rooting capabilities.
Alright, so it sounds like this is what I should do then:
Get tablet
Root it (If I can't, then I stop here)
Install safestrap
Backup
Install the backup on romslot 1??
Make the modifications I want to romslot 1
Is that right?
Also let's assume I can't root it, I can still sideload most apps I want like Gmail, Youtube, etc? (Those aren't on the amazon app store correct?)
yeap
Hobox10 said:
Alright, so it sounds like this is what I should do then:
Get tablet
Root it (If I can't, then I stop here)
Install safestrap
Backup
Install the backup on romslot 1??
Make the modifications I want to romslot 1
Is that right?
Also let's assume I can't root it, I can still sideload most apps I want like Gmail, Youtube, etc? (Those aren't on the amazon app store correct?)
Click to expand...
Click to collapse
Yeah I would say you just about got the idea .... If it is a brand-new unit you have a possibility that it will be on the old firmware still ... That is why they need to bypass activation skip set up . And check firmware before you hook it to any active Wi-Fi service .. And even if it does or is already updated there is now root available for the latest firmware ... It's just a question whether or not we can get anything else to work along with the latest firmware ... I would be advised if you attempt to run the OTA blocker which comes in the HDX utility you may have Wi-Fi glitches and reboots .... But like I said those bugs need to be checked for and follow through and repaired in their associated threads ... Not a new thread that only plugs up our forums but puts the helpful threads on the next page where cannot find them ... Remember there are multiple pages each forum section and some of the helpful threads have been buried on the next page due to people starting new threads with the same questions or problem... That have been resolved already... Remember reading is more informative than typing . And remember if anybody here is giving you their personal time to answer your questions and respond to your post it is courtesy here to hit the thanks button in the left lower corner of the post.End rant. thx
<~~~~~~~~~~ ; )
Ok, So i got the new updates from Google Wallet to the new Google Wallet and Android Pay.
When I attempted to setup Android Pay, I received the error that my device couldn't be "verified as being compatible."
A little browsing turned up some information that Android Pay doesn't like rooted devices, and even gave a couple of solutions.
1. Disable Superuser access if your Superuser app has the capability.
2. If option one isn't possible, then go back to stock, activate, and re-root.
This fix will NOT work for everyone, but since it is a simple setting change, it can't hurt to try this before looking into more 'drastic' measures. This will most likely only work on rooted stock ROMS.
I know that I use Chainfire's SuperSU app, and it has the ability to be disabled so the operator does not has superuser access until it is re-enabled. Simply go to your SuperSU app, go into the "Settings," and uncheck the "Enable Superuser." Different versions and other apps may be a little different, but principle should remain the same if it is an option.
After disabling SuperSU, open Android Pay and complete your initial setup. Once completed, return to the SuperSU app and re-enable Superuser access. The Android Pay app has continued working since then for me.
Based on information given by 'rbeavers,'
https://koz.io/inside-safetynet/
Guess I'm screwed
Click to expand...
Click to collapse
it appears rooted stock ROMs will probably work if you disable superuser (no guarantee though). Custom and ported ROMs most likely will never work unless the devs figure out a workaround. I would also imagine a otherwise stock ROM running a custom kernel wouldn't work either based on rbeavers' link.
Another note, I've integrated updated system apps and certain other apps into the system partition, so that probably won't matter if anyone is curious about that. (Could be different for other people though.)
Original Posting:
Just got the new Android Pay. I received an error that my device couldn't be verified as being compatible. Found some where else that it doesn't like rooted devices . Fix with SuperSU is easy. Go to SuperSU, touch Settings, and uncheck Enable superuser. Setup Android Pay, then re enable it, and so far, it's working for me.
Click to expand...
Click to collapse
Tried it didn't work for me "turned off " SU. My bank isn't on the "list". So that might be it?
Maybe? I didn't think Android Pay used the bank account, only Wallet does. Pay requires you to link your debit or credit card. Both apps automatically pulled my information, so I didn't have to dig into that very much.
Another thing my ROM is otherwise stock.
I've also read that Android Pay just doesn't like some ROMs, so users on custom or ported ROMs and a few devices in general are probably going to be left out in the cold... unfortunately.
Hopefully someone with more knowledge of the Android system can help us out here soon.
https://koz.io/inside-safetynet/
Guess I'm screwed?
Interesting read. Thanks for sharing
So, rooted stock ROMs will probably work if you disable superuser (no guarantee though). Custom and ported ROMs most likely will never work unless the devs figure out a workaround. I would also imagine a otherwise stock ROM running a custom kernel wouldn't work either based on your link.
Another note, I've integrated updated system apps and certain other apps into the system partition, so that shouldn't matter if anyone is curious about that.
Hey team,
Long time forum creeper and general tech hacker / fiddler. I don't generally post on forums but I'm hoping to nab some suggestions. Done a fair lot of looking already, but either turning up stones / outdated info / things that just aren't applicable to me.
Been looking to get Snapchat (and other stubborn apps similar) logged in on my device, honestly I don't even really use it and it's turned into more of a challenge getting it to run at this point because instead of thinking if I should I'm fixated more with the idea of proving that I could.
The phone is rooted, yes I know I could un-root it, stock rom, blah blah, but where is the fun in that?
Anywho the setup is as follows.
Galaxy S10+ SM-975F (Exynos)
Lineage OS 17.1 (Custom rom found here)
I have TWRP in as a recovery, phone is rooted with Magisk and it runs MicroG.
I have signature spoofing working with EdXposed (FakeGapps) and funnily enough I pass SafetyNet (lol I know, wassup google)
(HiddenCore for Xposed helps with this for those who seem to be struggling with newer devices)(Google is your friend "sometimes")
Now, I've done the obvious and sorted out Magisk hide, I've also tried RootCloak for Xposed with no success, again done the obvious install / reinstall / clear app data storage etc etc.
Does anyone have any ideas about what further detection methods they are employing? You'd think hiding root and passing SafetyNet would do it, but noooooo.
NB: In before It's some silly app I've left installed it doesn't like.
Your suggestions would be greatly appreciated!
deusxanthus said:
Hey team,
Long time forum creeper and general tech hacker / fiddler. I don't generally post on forums but I'm hoping to nab some suggestions. Done a fair lot of looking already, but either turning up stones / outdated info / things that just aren't applicable to me.
Been looking to get Snapchat (and other stubborn apps similar) logged in on my device, honestly I don't even really use it and it's turned into more of a challenge getting it to run at this point because instead of thinking if I should I'm fixated more with the idea of proving that I could.
The phone is rooted, yes I know I could un-root it, stock rom, blah blah, but where is the fun in that?
Anywho the setup is as follows.
Galaxy S10+ SM-975F (Exynos)
Lineage OS 17.1 (Custom rom found here)
I have TWRP in as a recovery, phone is rooted with Magisk and it runs MicroG.
I have signature spoofing working with EdXposed (FakeGapps) and funnily enough I pass SafetyNet (lol I know, wassup google)
(HiddenCore for Xposed helps with this for those who seem to be struggling with newer devices)(Google is your friend "sometimes")
Now, I've done the obvious and sorted out Magisk hide, I've also tried RootCloak for Xposed with no success, again done the obvious install / reinstall / clear app data storage etc etc.
Does anyone have any ideas about what further detection methods they are employing? You'd think hiding root and passing SafetyNet would do it, but noooooo.
NB: In before It's some silly app I've left installed it doesn't like.
Your suggestions would be greatly appreciated!
Click to expand...
Click to collapse
Sorry for double post, I've spent time podding and poking with some code and packaged something that seems to be working!
I'll keep testing it and come back
deusxanthus said:
Hey team,
Long time forum creeper and general tech hacker / fiddler. I don't generally post on forums but I'm hoping to nab some suggestions. Done a fair lot of looking already, but either turning up stones / outdated info / things that just aren't applicable to me.
Been looking to get Snapchat (and other stubborn apps similar) logged in on my device, honestly I don't even really use it and it's turned into more of a challenge getting it to run at this point because instead of thinking if I should I'm fixated more with the idea of proving that I could.
The phone is rooted, yes I know I could un-root it, stock rom, blah blah, but where is the fun in that?
Anywho the setup is as follows.
Galaxy S10+ SM-975F (Exynos)
Lineage OS 17.1 (Custom rom found here)
I have TWRP in as a recovery, phone is rooted with Magisk and it runs MicroG.
I have signature spoofing working with EdXposed (FakeGapps) and funnily enough I pass SafetyNet (lol I know, wassup google)
(HiddenCore for Xposed helps with this for those who seem to be struggling with newer devices)(Google is your friend "sometimes")
Now, I've done the obvious and sorted out Magisk hide, I've also tried RootCloak for Xposed with no success, again done the obvious install / reinstall / clear app data storage etc etc.
Does anyone have any ideas about what further detection methods they are employing? You'd think hiding root and passing SafetyNet would do it, but noooooo.
NB: In before It's some silly app I've left installed it doesn't like.
Your suggestions would be greatly appreciated!
Click to expand...
Click to collapse
Are you able to help me unlock a permanently locked Snapchat?
Hello I would appreciate some help fixing an issue.
Please excuse my lack of knowlage, I will try to give adequate info. If more info is needed let me know.
I have a Oneplus Nord N10 5G "unlocked" (I believe that means global) Build# BE86AA Model# BE2026 Android ver. 11
The phone has been rooted since October 13-20
I cannot recall the tutorial I followed to root. I do have TWRP and Magisk on the phone. With Magisk 23.0 I passed SafetyNet (I used the built in SafetyNet Checker Via Magisk)
A few days go (Feb/18/22) I updated Magisk(24.1)/App(24.1) Via the Magisk app. I no longer pass SafetyNet (I used Root and SafetyNet Checker from "BetterOpts")
Magisk 24.1 no longer has Magiskhide
Now I cannot play Niantic's game called Ingress.
A message pops up saying "Ingress is not supported on this device configuration"
I had no issue when I had Magisk 23.0 (using magiskhide)
I googled that message and found that Niantic searches for root/rooting apps.
I have messed around with "Magiskhide props config v6.1.2" changing device fingerprint, force basic attestation.
Nothing seemed to help so i Reset all options/settings
I have read many horror stories of people hard bricking or causing more damage by trying to revert/unrooting back to stock.
I think i did a dumb and did not backup anything from Pre-root.
I saw a few posts on reddit/gaming.stackexchange people saying outdated SupperSU caused them to get the message.
I do not have SupperSU.
Another person they deleted a folder called "MAGISKMANAGER" and that solved the message.(this post was back in 2019)
I'm not sure if they unrooted and thats why they deleted the folder.
I couldn't find a folder with that name.
A lot of posts I found all say "Use Magiskhide"
But Magiskhide has been removed from Magisk24.0+
I did a search (using files app) and found Magisk.apk(s)
Magisk_patched
and Magisk-23.0.zip
I'm not sure if should delete these. Not sure if deleting (or moving files to computer) would cause problems on the phone at next reboot.
I am no rooting expert so again please excuse my ignorance. again if more info is needed please let me know and i will answer to my best ability.
Do you recommend a Hide Root App/Mod?
Should I install Xposed Framework via Magisk?
Thank you for your time and advice
Edit:
I am very stupid. I found kdrag0n safetynet-fix from Github.
Downloaded the latest release (2.2.1)
Installed Via Magisk app
Rebooted
Ingress works
I'm thinking of leaving this post up. It might help someone?
If you still need to upgrade to Magisk 24.1 then study at least the start of this thread. Maybe not for now but in the future.
Magisk 23 and lower will not be supported any longer.
Wonderful new week for you !
[Discussion] Magisk - The Age of Zygisk.
This is a discussion and help thread for the newer versions of Magisk. The main goal of this thread is to help users migrate to Magisk v24+ SafetyNet Basic integrity Pass CTS profile match Pass Play Protect certification Device is certified...
forum.xda-developers.com
xabu said:
If you still need to upgrade to Magisk 24.1 then study at least the start of this thread. Maybe not for now but in the future.
Magisk 23 and lower will not be supported any longer.
Wonderful new week for you !
[Discussion] Magisk - The Age of Zygisk.
This is a discussion and help thread for the newer versions of Magisk. The main goal of this thread is to help users migrate to Magisk v24+ SafetyNet Basic integrity Pass CTS profile match Pass Play Protect certification Device is certified...
forum.xda-developers.com
Click to expand...
Click to collapse
I saw that thread right after i made my post.I thought about deleting the post. I'm sure there will be other people who will update without reading beyond "New update" and hopefully this will find them and steer them toward getting their device up and running.
For anyone curious.
Go into magisk settings, use the option to change magisks package name.
Then enable Zygote mode.
Reboot your phone.
Go back into your now renamed magisk app (mine is usually named system because who the hell looks at an app named system and think "this is the malicious code, I know it!")
Open your magisk app, go back into the settings and look for the option that says deny, click it and look for the app you're gonna hide from magisk.
If you're looking to use something like Pokemon go, click it twice so that way Zygote rejects both checks.
Now go be a pokemon master
Hello,
I recently installed GrapheneOS on my Pixel 6 and I want to use XPrivacyLua on it. But when I install and activate LSPosed (1.8.3) and reboot then it says there's no LSPosed installed. But in Magisk it is loaded together with Shamiko. Shamiko works fine, but I wasn't able to use LSPosed yet. Does anybody know how LSPosed can be used successfully on GrapheneOS?
Thank you,
Oebbler
Oebbler1 said:
Hello,
I recently installed GrapheneOS on my Pixel 6 and I want to use XPrivacyLua on it. But when I install and activate LSPosed (1.8.3) and reboot then it says there's no LSPosed installed. But in Magisk it is loaded together with Shamiko. Shamiko works fine, but I wasn't able to use LSPosed yet. Does anybody know how LSPosed can be used successfully on GrapheneOS?
Thank you,
Oebbler
Click to expand...
Click to collapse
you lose more for the little gain you get by using xprivacylua. also graphene os isn't meant to be used with root since you defeat the main goal of the os itself: security. it hardens several aspects of android to make it more secure, and that's why things like lsposed won't work.
hellcat50 said:
...graphene os isn't meant to be used with root since you defeat the main goal of the os itself: security.
Click to expand...
Click to collapse
That's a redundant and absurd thing to say. First of all, grapheneos objection to root is realistically tied to support burden and public impression rather than anything practical. Second, root doesn't threaten security if used responsibly. Third, root is HELPFUL for security when used competently.
Now for the other thing... lsposed... avoid like the plague.
Thank you for your answers!
The thing is that I cannot avoid LSPosed for XPrivacyLua on Android 12. I really want to use it in order to avoid tracking by getting IDs and other data from my device. So my question still remains on how to make LSPosed runnable.
I tried to install it with Riru. Riru was telling me that LSPosed is loaded, but the LSPosed app told me it cannot find LSPosed. It seems the same as with LSPosed on Zygisk. Is there any way to get LSPosed (or maybe EdXposed) working?
Oebbler1 said:
Thank you for your answers!
The thing is that I cannot avoid LSPosed for XPrivacyLua on Android 12. I really want to use it in order to avoid tracking by getting IDs and other data from my device. So my question still remains on how to make LSPosed runnable.
I tried to install it with Riru. Riru was telling me that LSPosed is loaded, but the LSPosed app told me it cannot find LSPosed. It seems the same as with LSPosed on Zygisk. Is there any way to get LSPosed (or maybe EdXposed) working?
Click to expand...
Click to collapse
Please read this about ID's: https://grapheneos.org/faq#hardware-identifiers
Thank you! This sounds good, but leaves something out which I also want to do:
I want to allow access to particular contacts for some apps only. And maybe in the future it should be possible to hook some other methods (with XPrivacyLua Pro) that apps use for things I don't want them to do. So I think I cannot avoid LSPosed, EdXposed or something like that. How can this be achieved?
Oebbler1 said:
Thank you! This sounds good, but leaves something out which I also want to do:
I want to allow access to particular contacts for some apps only. And maybe in the future it should be possible to hook some other methods (with XPrivacyLua Pro) that apps use for things I don't want them to do. So I think I cannot avoid LSPosed, EdXposed or something like that. How can this be achieved?
Click to expand...
Click to collapse
Contacts permission does not need any additional hacks to be denied.
hellcat50 said:
you lose more for the little gain you get by using xprivacylua. also graphene os isn't meant to be used with root since you defeat the main goal of the os itself: security. it hardens several aspects of android to make it more secure, and that's why things like lsposed won't work.
Click to expand...
Click to collapse
Unless you're running GrapheneOS via yellow state boot loader (and you checking the finger print each boot), I can't take claims of "root is insecure" quite seriously.
I don't want to deny contacts permission at all, but I want to allow only certain contacts to be seen by some apps. So I want e. g. Telegram or Signal to only see the contacts I am using in these apps. These aren't the same so Telegram's and Signal's access to the contacts list need to be hooked in order to provide individual faked/manipulated lists to these apps.
And maybe in the future some apps do a call to e. g. some app-internal ID which is used for tracking, so I want to hook that later on.
To me it doesn't matter if there are other hacks available to do these things. I'd just like to do that with XPrivacyLua Pro. So how can I get this working on GrapheneOS?
ezdiy said:
Unless you're running GrapheneOS via yellow state boot loader (and you checking the finger print each boot), I can't take claims of "root is insecure" quite seriously.
Click to expand...
Click to collapse
Yeah right rooting makes your device more secure haha. https://madaidans-insecurities.github.io/android.html#rooting
Oebbler1 said:
I don't want to deny contacts permission at all, but I want to allow only certain contacts to be seen by some apps. So I want e. g. Telegram or Signal to only see the contacts I am using in these apps. These aren't the same so Telegram's and Signal's access to the contacts list need to be hooked in order to provide individual faked/manipulated lists to these apps.
And maybe in the future some apps do a call to e. g. some app-internal ID which is used for tracking, so I want to hook that later on.
To me it doesn't matter if there are other hacks available to do these things. I'd just like to do that with XPrivacyLua Pro. So how can I get this working on GrapheneOS?
Click to expand...
Click to collapse
I don't think lsposed will ever work on graphene os. for that you will have to switch the os
hellcat50 said:
Yeah right rooting makes your device more secure haha. https://madaidans-insecurities.github.io/android.html#rooting
Click to expand...
Click to collapse
Applications don't just have access to root if you make it available to yourself. Again, its about the USER being competent and not just granting root permission willy nilly like a total retard. Nice try, but NOPE.
A project to keep an eye on...
GitHub - chriswoope/resign-android-image: Resign Android OS (esp. GrapheneOS) images with your signing keys and add ADB root and other modifications
Resign Android OS (esp. GrapheneOS) images with your signing keys and add ADB root and other modifications - GitHub - chriswoope/resign-android-image: Resign Android OS (esp. GrapheneOS) images wit...
github.com