Thoughts on GrapheneOS & Best phone for it - Android Q&A, Help & Troubleshooting

The title says it all... does anyone use GrapheneOS? Thoughts? Likes/dislikes?
Are there any phones that are better for it than others? I was looking at the Pixel 3a.

Hi sniper8752,
I know you question is now a few months old (i hope i'm not to late for my answer).
I guess cause there are nearly no xda GrapheneOS threads a question such yours running under the "radar".
I'm on, well let's say, GrapheneOS in examination marks because i don't use the OS on my pixel 4 xl as the dev intented it.
I don't know whether you were on the GrapheneOS website in the past. According to the website you should install GrapheneOS once over fastboot and lock the bootloader again to get the AVB fully working again.
That give you the most security cause you can only boot GrapheneOS and install GrapheneOS Updates over the build-in updater app.
But from my knowledge you can't install EdXposed or Magisk then cause you change partitions and AVB blocks the booting process then.
So i'm using GrapheneOS as normal Custom Rom and unlocked Bootloader to be able to use Root with Magisk.
That why i say i'm having a GrapheneOS in examiniation marks
From user view it's a clean Android 10 ROM without (!) Gapps etc. This won't change cause it a Rom for people which care about privacy and security.
What i really like too are the facts that it explicity apply the full security patches on the supported devices (which are only the pixels) and that it uses a securized kernel and some other under the hood security improvements.
I'm using the rom (stable channel) since a few days now and it's runs totally smooth and i didn't find any bugs
so far.
Atm i'm thinking to offer unofficial builds from the rom with according Magisk pre-patched boot images here on xda. But i'm not completly sure about that.
Edit:
And i forgot still one thing: The support from GrapheneOS for a device ends if google stops the support for it. Again the reason is security: Some parts of your device gets updates through the device oem. GrapheneOS can't cover this so the dev doesn't support the device anymore.
All in all GrapheneOS has another philosophy then most of the custom roms here on xda. It doesn't want to extend the lifetime of devices. It want to gives the user a more privacy and securize-friendly rom during the lifetime of device.

Hey mate - did you manage to get for example Google Photos running if you add MicroG? (in terms of Backup).
I am still not able to ditch that (at least until my full backups from the Pixel seize to exist Jan 2021 I believe...).
Mind you that the Google Photos works just fine on CalyxOS with backup functions operating.
GCam works on both (Graphene with a Services spoofer apk). Still secure.
CalyxOS using the MicroG.
Graphene OS does not allow me to use Google Photos's backup function. I've read that if I backup using Titanium root and then deploy in Graphene (with root) it should work. Using your method + Magisk maybe I can make this work ...
Battery life on Graphene has been epic for me ...
GPS was very slow and sort of inaccurate on both ...
For all else I am perfectly fine with both.

Related

Trying to understand Rooting and Security (Android specific)

Hi All,
So I am trying to better understand the Android operating system, specifically in the security section as it seems to be more 'hands off' compared to Windows.
Let me start by saying I am no security engineer in any capacity, but its a field that interests me greatly, and I understand Windows security much more than Linux/Android
I know what root is in Linux, its essentially the system account of Windows, it can do anything, and gaining root on Android is essentially gaining system in Windows, and understandably is a dangerous account to have control of.
I also understand that Android uses a verified boot process, similar to Windows with Secure boot and Bitlocker (When configured correctly)
But for Android this is as far as I go with Security, admittedly its extremely limited is my knowledge of the Android security system, I have heard of SafetyNet APIs and this can control things like Google Pay and some other applications like My EE for example, and seems to be to basically be a verification method to make sure the system is not tampered with.
But I am trying to understand what other security issues can arise with root, on my One plus when the boot loader is unlocked it prompts a warning on boot which is to be expected, it cannot verify the software you install (TWRP, Kernel, System) is safe and untampered with, but what else can happen, specifically from being attacked, maybe during system usage and what steps can be taken to help improve security?
I ask this because I feel more secure on OOS with locked BL, of course, but I also like to add things in like Magisk, V4A and Energized and I am currently deciding which I wish to settle on, Locked OOS or Unlocked OOS with addons.
Can anyone provide any light and tips on the subject? ELI5 or Advanced explanation is welcome
Many Thanks!
Hi!
I am in a similar situation as XDroidie. No security engineer, but I have technical background and I am also very interested in it.
I would like to learn how I can monitor my android system integrity and regular check if it is being tampered.
After some research I have the impression googles safetynet does a good job.(koz.io/inside-safetynet-3).
But I would prefer to live without Google Mobile Services on LineageOS or similar things.
Are there open source mimiks of safetynet, I can use as a personal security checker?
If for some reason I would get forced to use Safetynet, are there methods to check what safetynet does ? Did anybody before?
Thanks for your suggestions in advance!
Gerald

[ROM] OOS[microG] for Oneplus 5T [8.1.0]

I am no longer working on this, or updating any information here! This was created back in the day of Oreo.
I've personally moved on and I'm presently using /e/ which you can see the info here and get the ROM for OP5T.
/e/OS documentation - OnePlus 5T
Info about OnePlus 5T - dumpling
As of this post edit on 10/20/22 I'm using 'e-1.4-r-20220922220394-dev-dumpling' and /e/ uses microg. It runs quite nice, so check it out!
NEW VERSION RELEASE: OOS[microG]-5.1.7-3185.041719 - (Read the second post for changes!)
OOS[microG] - Better performance, basic and simple, customize it your way!
No more proprietary Google Framework & Play Services!
No more OnePlus Data Analytics!
OOS[microG] comes with native support built in for microG and Signature Spoofing!​
OOS[microG] is based on 1 year of experience on several devices, also hundreds of hours went into the preparation and making of OOS[microG]!
OOS[microG] is OxygenOS stripped down and more basic, allowing you to start installing it your way! There's not even a browser in OOS[microG], install what you want!
The point of OOS[microG] is to be as Google Free as possible, to offer better Performance, Security, Privacy, and Freedom without the Google Framework & Play Services!
OOS[microG] is not as complete a Google ROM as OxygenOS, but it still uses and requires a few Google applications because of how OnePlus created the ROM.
OOS[microG] uses F-Droid to access "Free Open Source Software", you can also install Aurora Store or Yalp Store which downloads directly off of the Play Store servers for any other applications you want.
Please be aware that OOS[microG] plays no part in the development of any application installed!
If you have any problems please be specfic, with as much detailed information as possible, so that issues can be investigated properly!
Please read this entire post before making any replies, as it may answer your question(s).
Features
Full ROM Deodex
Android & OnePlus setup wizards disabled
AOSP WebView & Google WebView
App permissions - "Spoof Signature" listing
boot.img patched - sepolicy for Oreo Deodex
EasterEgg removed
framework-res.apk patched - microG, signature check, signature spoofing
Gapps & OnePlus applications debloated
Google backup removed and disabled
Google Calendar & Google Contacts Sync support enabled
OnePlus Account removed
OnePlus bug reports/log removed and disabled
OnePlus Data Analytics applications removed and disabled
OnePlus Forum removed
OnePlus Photos Online removed
OnePlus Weather removed - not supported in microG
OnePlus "Notifications" "User experience program" and "System stability improvement program" removed and disabled
open.oneplus.net added to the "hosts" file to help block online Data Analytics
OxygenOS OTA update removed and disabled
RZ v3.7.0 Kernel - suspicious OnePlus services patched
services.jar patched - signature spoofing
System permissions added for microG support
8 new wallpaper added
Additional Applications
AOSP Keyboard - UI changes and Mic removed
AOSP WebView
DejaVuNlpBackend
FakeStore
F-Droid
F-Droid Privileged Extension
microG - NanoDroid version
MozillaNlpBackend
NominatimNlpBackend
Not Working
Because OOS[microG] is OxygenOS stripped of the Google Framework & Play Services, some applications and features will not work at present, these issues are being investigated, maybe in time they will be supported! Hopefully the lack of these few features will not discourage those from the many other benefits of OOS[microG]!
Gallery applications - "Share button & "Set as"
OnePlus Weather - (removed)
Because of the modifications needed for the framework-res.apk, the Gallery "Share button" & "Set as" will not work. Without these changes to the framework-res.apk the alternative would be the need for Xposed in the ROM, maybe in time this situation might change.
FAQ
Q: What is OOS[microG]?
A: OOS[microG] is a stripped down version of OxygenOS 5.1.7 that uses microG instead of the Google Framework & Services!
Q: What is this Performance, Security, Privacy, and Freedom being mentioned?
A: The Google Framework & Services do not offer the same Security, Privacy, and Freedom, mainly because of the "Proprietary Nature". The Google Framework & Services are also heavier on system resources, whereas microG is much lighter, so they lack the Performance that microG offers!
Q: OOS[microG] is for Oreo?
A: Yes - At the moment this is Oreo 8.1.0
Q: Can I Root OOS[microG]?
A: Yes - OOS[microG] can be Rooted like any typical ROM, it was tested on Magisk 18.0!
Q: Is OOS[microG] completely free software?
A: No - it still has OnePlus' proprietary software to support their hardware, and a few of their own proprietary applications, also a few Google applications are still installed because of how OnePlus created the ROM.
Q: Will OOS[microG] pass SafetyNet with microG?
A: Yes - Please see the "SafetyNet" section below!
Q: What is microG?
A: microG is basically a replacement for the Google Framework and Play Services, to allow you to still access all of Google's services, and use applications that rely on them, please see https://microg.org/
Q: Does everything work with microG?
A: It is not 100% perfect, so you might run into an issue with either an application or functionality that relies heavily on the Google Framework & Services.
Q: Is battery life better with OOS[microG]?
A: Yes - microG is lighter on resources which improves battery life, whereas the Google Framework & Services are heavier on resources causing more battery drainage.
Q: Why do you use the NanoDroid's version of microG and not the Official microG?
A: The Official microG sometimes doesn't get development as fast, and thanks to the great work of the NanoDroid project, NanoDroid-microG is getting faster development. Please be aware this is still the Official microG with fixes/changes added in by the NanoDroid project!
Q: Isn't it better to just use Custom ROMS?
A: It depends - If Custom ROMS are not using microG, then you don't have the same Performance, Security, Privacy, and Freedom, they are still reliant on the Google Framework & Services which are proprietary and not free, so less Performance, less Security, less Privacy, less Freedom, also heavier on resources, with microG it's the complete opposite! Custom ROMS also need good development to support a manufacturer's hardware, like the camera on the OnePlus 5T as an example. The hardware from manufacturers is typically supported by proprietary software, and depending on the Custom ROM development, trying to support this hardware can be easy or difficult. Using a ROM developed by the manufacturer offers the best hardware support, but of course manufacturers all use Google. For those looking for alternatives away from Google, and the best hardware support, this is where OOS[microG] steps in!
Q: Can't I just run a ROM without any Google or microG and still have it all work the same?
A: No - If you want an Android phone with a lot of features and functionality, otherwise it's going to be very limited. At the present moment you need either the Google Framework & Services or microG. The job of microG is to replace the Google Framework & Services so that you have all the same features/functionality, localization services, push notifications, Google Cloud Messaging, Maps API, etc., not to mention all the applications that are reliant on the Google Framework & Services, that won't work if you don't have either the Google Framework & Services installed or microG!
Q: I thought Android was Open Source and Free?
A: Yes and No - The core of the Android source code is known as Android Open Source Project (AOSP). However, proprietary software developed by Google known as the Google Mobile Services (GMS), is not a part of the Android Open Source Project (AOSP).
Q: Why does Free Open Source Software matter?
A: There are of course Pros & Cons between Proprietary and Free Open Source, but if Freedom, Security, or Privacy, along with Performance on the subject of microG, if any of these matter to you, then you need to investigate this for yourself. This subject matter is to indepth to fully explain here. These are a few links to point you in the right direction;
https://www.fsf.org/
https://en.wikipedia.org/wiki/Open-source_software
https://en.wikipedia.org/wiki/Free_and_open-source_software
Q: What is F-Droid Privileged Extension?
A: It allows F-Droid to install and uninstall applications without needing the unsafe "Unknown Sources" to be enabled. F-Droid can then install updates in the background without user intervention needing to click "Install".
Q: How can I get paid applications?
A: For some applications you might be able to download them through your account on either Aurora Store or Yalp Store, for others you might need to have the Play Store installed. If you need to use the Play Store, please visit the NanoDroid project on XDA for help with replacing FakeStore with the Play Store. It is recommened that you use the NanoDroid version of the Play Store which has been patched to work with microG for paid applications.
Q: Why do I see the Play Store listed for update when I add in the NanoDroid F-Droid Repo?
A: The FakeStore spoofs the Play Store as a replacement this is why you see it, you can ignore the update in F-Droid so it doesn't appear!
Q: What is this version of WebView installed and how do I update it?
A: This is the AOSP WebView, you can also install the Google WebView if you want to use it too. Whichever version you use be sure to enable it in the "Developer options" > "WebView implementation". Updates for AOSP WebView will appear on this post for you to download and install when they become available.
Installation instructions
Before installing OOS[microG]-5.1.7-3185.041719 you should check that it has the correct signatures.
Code:
MD5: 3d58a7ec85ba5d4e267c666f497a1643
SHA1: 30f8285caccd27acfc96e8a429ee31e9972b36f4
SHA256: a2ba548b75ddff1d31abd9a84e6f8f0528f81e3a553d725237bd0954463ec507
OOS[microG] is made from OxygenOS 5.1.7 Oreo!
Before installing OOS[microG] you need to wipe all of your partitions including the Storage, backup any data you have, then flash OxygenOS 5.1.7!
Next wipe all of your partitions including the Storage again, then flash OOS[microG]!
Install Steps:
Boot into Fastboot > fastboot -w
Boot into TWRP > Wipe > Format Data
TWRP > Advanced Wipe > Check all except USB
TWRP > Advanced > ADB Sideload > adb sideload OnePlus5TOxygen_43_OTA_040_all_1811051816_115c75d257934eea.zip
Boot into OxygenOS and allow it to run!
Boot into Fastboot > fastboot -w
fastboot flash recovery twrp-3.2.3-x_blu_spark_v9.85_treble-op5_op5t.img
Boot into TWRP > Wipe > Format Data
TWRP > Advanced Wipe > Check all except USB
TWRP > Advanced > ADB Sideload > adb sideload OOS[microG]
Please do not post any problems you encounter if you don't follow the steps above, these problems might be related to doing a dirty flash, you've been warned!
Download
Be sure to download the latest version "OOS[microG]-5.1.7-3185.041719"!
Thanks to their generosity OOS[microG] is hosted for download at Android File Host!
https://androidfilehost.com/?w=files&flid=289145
OxygenOS 5.1.7 from OnePlus' Official Server.
http://oxygenos.oneplus.net.s3.amaz...3_OTA_040_all_1811051816_115c75d257934eea.zip
Post Installation
The Android Setup Wizard has been disabled, even though it's disabled it still runs in the background helping to complete the installation. When the phone first starts, if you notice an overhead notification from the "Android Setup", tap "NOT NOW" then "Never", there is nothing further you can do with the Wizard!
OOS[microG] comes with the DejaVuNlpBackend, MozillaNlpBackend, and NominatimNlpBackend for the Location Services for microG. The NominatimNlpBackend uses MapQuest's Nominatim service. For the NominatimNlpBackend you'll need to sign up for a free account at MapQuest to get an API key. There are also other plugins available through F-Droid to use besides the ones installed in OOS[microG], if you wish to use!
https://developer.mapquest.com/
Phone > Settings > "Location ( Mode - High Accuracy)"
microG - "Google device registration" - ON (Enabled)
UnifiedNlp Settings - check mark all - DejaVU, Mozilla, Nominatim
"Address lookup" - Nominatim - pick MapQuest!
F-Droid > Settings - enable "Expert mode" - "Privileged Extension" will now be enabled at the bottom of the Settings.
F-Droid > Settings - Repositories - Add the NanoDroid Repo - https://nanolx.org/fdroid/repo so that you can update microG and the applications it uses!
Highly recommened for better performance/speed! - "Developer options" > Drawing - "Window animation scale" (Animation off) - "Transition animation scale" (Animation scale .5x) - "Animator duration scale" (Animation scale .5x)
Changing the "Drawing" settings in the "Developer options" might appear jumpy to some people, that is because the windows and applications will respond faster. If you don't like it, play with the settings to find what's comfortable to you. These settings that have been recommended are for people that want the ultimate speed.
Once you have completed all of the "Post Installation" steps, you should now see all the sections check marked under "Self-Check" in microG. Under the "UnifiedNlp status" section you should have 6 sections now checked, sometimes you have to give it a few seconds for all 6 to appear checked, either go out of "Self-Check" and return, or scroll up and down a few times. At any time, if you disable the Phone Location, or change the Mode, then you will see the "UnifiedNlp status" section with sections unchecked, and it will take a moment for them to all appear checked again, once you have all your Phone Settings for Location correct! "Google device registration" is also required for the Location Services!
SafetyNet
SafetyNet was tested and working with Magisk 18.0 & 18.1.
OOS[microG] doesn't come installed with Google's proprietary binary DroidGuard.
You'll need to download NanoDroid-microG from the NanoDroid Project on XDA for DroidGuard. It is located in the "/system/app/DroidGuard" folder.
You will then need to boot into TWRP and mount "System", from your computer run; adb push DroidGuard /system/app
Use the file manager in TWRP to verify that you now see /system/app/DroidGuard/DroidGuard.apk
In microG make sure that "Google SafetyNet" is ON and upper right, "3 dots > Advanced" - make sure "Use Official Server" is marked!
Open Magisk, in the menu tap "Magisk Hide" and check "microG DroidGuard Helper" & "microG Services Framework Proxy" to hide them! Now tap, "Tap to start SafetyNet check", it should pass! SafetyNet passed in OOS[microG] testing, see the screen shot below!
Updating microG
OOS[microG] uses the NanoDroid-microG version, to keep it updated, place the NanoDroid F-Droid repository in F-Droid.
F-Droid > Settings > Repositories > Upper Right + > https://nanolx.org/fdroid/repo/
FakeStore spoofs the PlayStore, so you will first notice an update for the PlayStore, which can be ignored in F-Droid. Do not install this update with only the FakeStore installed!
Parallel Apps
If you use Parallel Apps it will create a second version of microG in the App Drawer. The second version of microG is not needed and should be removed. To remove it, press and hold on the icon, when the menu appears tap on "App info", then it will take you to microG's "App info" page, tap "Disable" to disable it. You should no longer see the second version in the App Drawer.
Hit the THANKS button it keeps me happy and motivated!
Watch this section for Announcements, Updates, ChangeLogs, ToDo, etc...
April 18 2019 - NEW VERSION RELEASE: OOS[microG]-5.1.7-3185.041719
ChangeLog:
microG Dirty-227 that was updated in the last release of OOS[microG] was crashing the Gallery application, so the previous version of micoG Dirty-167 was put back into this OOS[microG] release!
To update to a new version, read the Install Steps under the Installation instructions in the OP!
April 17 2019 - New Announcement
The latest update to Dirty-122 microG that was added in the latest release of OOS[microG]-5.1.7-3185.040519 has been found to crash the Gallery application.
A new release will come out shortly reverting microG back to the last version of Dirty-167 which is working fine!
April 06 2019 - NEW VERSION RELEASE: OOS[microG]-5.1.7-3185.040519
ChangeLog:
A few OnePlus & Google apps that were originally debloated have been added back in to help improve system performance.
NanoDroid microG updated to the latest version Dirty-227
AOSP WebView updated to version 72.0.3626.121
To update to a new version, read the Install Steps under the Installation instructions in the OP!
March 08 2019 - NEW VERSION RELEASE: OOS[microG]-5.1.7-3185.030819
ChangeLog:
Parallel apps is now working!
To update to a new version, read the Install Steps under the Installation instructions in the OP!
March 05 2019 - New Announcement
I've come to realize through more testing that the reason the Gallery Share button & Set As will not work, is because of modifications to the framework-res.apk, which are needed! Without these changes then Xposed would be needed in the ROM. Hopefully many will agree, that a lack of a few features such as these in the Gallery is a better choice, instead of needing Xposed. I'll keep looking into this situation, maybe in time I will be able to figure out a work around.
Parallel apps is now working, and I will release another update in a few days!
Have a look at the screen shots I've attached for Parallel apps!
March 03 2019 - NEW VERSION RELEASE: OOS[microG]-5.1.7-3185.030319
ChangeLog:
Additional apps removed for better performance, privacy, security - (mainly suspicious apps)
App permissions - New listing added for "Spoof Signature"
AOSP Keyboard added - UI changes and Mic removed
AOSP Webview updated - 71.0.3578.99
Calendar & Contact Sync added - Tested with Gmail
EasterEgg removed
Gallery - Share button & "Set as" not working
Google Webview added back in - (Now 2 Webview choices to use between AOSP & Google)
microG updated to the latest version
microG and GsfProxy both now have matching signatures for better support
microG Signature Spoof native support updated
Parallel Apps removed, not working in microG
Simple Keyboard removed
System permissions updated
Now you have the choice of using either AOSP or Google WebView! Before using Google WebView be sure to update it to the latest version!
To switch between WebView versions: Developer Options > WebView implementation
SafetyNet also tested and working in Magisk 18.1 - (Screenshot added in OP)
To update to a new version, read the Install Steps under the Installation instructions in the OP!
ENJOY!
Thanks! I'll test it right now
im try it Now.. thanks..
how to fix cst profile & basicIntegrity in magisk 18.1?
Yeah, that's the kind of ROM I was looking for ! I'm just gonna wait for the android pie version
Thanks for your job !
draentor said:
Yeah, that's the kind of ROM I was looking for ! I'm just gonna wait for the android pie version
Thanks for your job !
Click to expand...
Click to collapse
made for the most stable OOS firmware, in PIE OOS stable 9.0.3 is not the latest, because the PIE ROM base is too early
Is it only 5.1.17 we can install on... That's quite far back for Oreo..
Also do you mean 5.1.7 or 5.1.17 because you mentioned both
siliwangi said:
how to fixed cst profile & basicIntegrity in magisk 18.1?
Click to expand...
Click to collapse
The post has been edited over, see the new "SafetyNet" section!
Please don't make one post after another; known as "Double Posting", try to keep posts contained to one at at time, thanks...
dali786546 said:
Is it only 5.1.17 we can install on... That's quite far back for Oreo..
Also do you mean 5.1.7 or 5.1.17 because you mentioned both
Click to expand...
Click to collapse
That was a typo, thanks for pointing that out, fixed now, and it's 5.1.7
DoR3M3 said:
Even LineageOS microG doesn't come with DroidGuard installed, which is suppose to be needed for SafetyNet, they don't even talk about SafetyNet either on their website.
OOS[microG] doesn't come with DroidGuard becasue it's a Google Properitary Blob, and the point is to try and stay away from Google as much as possible, but it doesn't mean someone can't use it and work with SafetyNet on their, it's just not supported in OO[microG].
SafetyNet is difficult at times to pass, given Google is always making changes, you'll have to Google or check on XDA for SafetyNet.
That was a typo, thanks for pointing that out, fixed now, and it's 5.1.7
Click to expand...
Click to collapse
Is it only from main Oxygen OS branch, not the beta?
And any idea on ETA to pie?
Look at me asking a bunch of questions to a ROM that I tried to do manually. (I have disabled all Google tracking downloaded Firefox with extensions, disabled Google history... This solutions seems a hundred times better)
dali786546 said:
Is it only from main Oxygen OS branch, not the beta?
And any idea on ETA to pie?
Look at me asking a bunch of questions to a ROM that I tried to do manually. (I have disabled all Google tracking downloaded Firefox with extensions, disabled Google history... This solutions seems a hundred times better)
Click to expand...
Click to collapse
I've been so busy working on OOS[microG], that when I started the Pie firmware was not released and I haven't been paying attention to it, but now that I see it's been released when I get a chance I'll start working on a Pie version to release, don't have an ETA at the moment.
It's great to see replies and excitement, did you read my "microG - Deodex - Signature Spoofing - Debloat Gapps!" guide when you did all this manually?
https://forum.xda-developers.com/oneplus-5t/how-to/guide-microg-deodex-signature-spoofing-t3862961
DoR3M3 said:
I've been so busy working on OOS[microG], that when I started the Pie firmware was not released and I haven't been paying attention to it, but now that I see it's been released when I get a chance I'll start working on a Pie version to release, don't have an ETA at the moment.
It's great to see replies and excitement, did you read my "microG - Deodex - Signature Spoofing - Debloat Gapps!" guide when you did all this manually?
https://forum.xda-developers.com/oneplus-5t/how-to/guide-microg-deodex-signature-spoofing-t3862961
Click to expand...
Click to collapse
No i didnt use your guide to do that.
Feedback on the ROM
Love the concept and idea
It is however quite jumpy and lavgy (when scrolling or switching apps)
It didnt come with a browser and initially F-droid wouldnt install anything... Parse error. I rebooted disabled the extension then it worked. Re enabled it
Parallel apps isnt working and some apps that require Oneplus Framework crash.... OnePlus Weather
Apps that require GSF dont work. I tried loggijg into snapchat (it cpuld also be safetynet issue with snapchat tho)
Magisk returns safetynet error.... SNot failed safetynet... Just error i think to load it
dali786546 said:
No i didnt use your guide to do that.
Feedback on the ROM
Love the concept and idea
It is however quite jumpy and lavgy (when scrolling or switching apps)
It didnt come with a browser and initially F-droid wouldnt install anything... Parse error. I rebooted disabled the extension then it worked. Re enabled it
Parallel apps isnt working and some apps that require Oneplus Framework crash.... OnePlus Weather
Apps that require GSF dont work. I tried loggijg into snapchat (it cpuld also be safetynet issue with snapchat tho)
Magisk returns safetynet error.... SNot failed safetynet... Just error i think to load it
Click to expand...
Click to collapse
Have you ever used a microG ROM before? They all work the same, of course there are different versions of microG someone can use, but overall some apps are just difficult with GSF or SafetyNet.
If you're seeking help please be "Detailed" and "Specific", also the exact steps you've taken when you saw an issue.
Did you follow the post, wipe all partitions, install OOS 5.1.7?
Has Pie been installed on your phone, or a lot of 3rd party ROMS?
OOS[microG] is a Full ROM Deodex it will only lag when you first start it. If you changed the Animation in the Developer options as I mentioned, sometimes it might seem like it's jumpy because it moves faster, the windows will move snappier. So if this is the jumpy you are talking about, if you don't like the speed it gives, you can always change back to the default settings.
I explained in the OP that it doesn't come with a browser.
F-Droid works fine, did you dirty flash, or enable "Install unknown apps" on your phone?
OnePlus Weather does not work with microG. Are there other apps giving you a OnePlus Framework message/error?
When you look at the microG GitHub Repo, and the issue reports, based off of that, and how many apps are on the Play Store, the working percentage of microG seems very high. How many apps have you tried that are not working?
Nothing is 100% with microG like any piece of software, I have no control over this, for any apps that require GSF and OnePlus Weather please seek help and submit a report on the NanoDroid if you care to run microG on ROMS!
Parallel Apps appears to not work with microG, so it will be disabled in the next release. There are 3rd party apps that help with this...
P.S. See the OP it's been edited over, there's a new SafetyNet section that's been added!
I read all the things in op and great work doing this , also gone thru faq. I m sure the developers have spent hours an days which is great...but need to be clear what we are achieving with so much effort
But still not clear what is the single pressing point to do this , battery life ? Performance ? Do we know how much % it will improve when compared to same use with Google framework rom ? I m sure the developer did some baseline around this . Performance ratings ?
Other than battery life why would one not want to use Google framework , the way it sounded it to me is , Google is buggy and has lot of issues ,, but in my day to day use I don't experience anything like that
Just trying to figure out motivation for myself to try out this ROM
Manan79 said:
I read all the things in op and great work doing this , also gone thru faq. I m sure the developers have spent hours an days which is great...but need to be clear what we are achieving with so much effort
But still not clear what is the single pressing point to do this , battery life ? Performance ? Do we know how much % it will improve when compared to same use with Google framework rom ? I m sure the developer did some baseline around this . Performance ratings ?
Other than battery life why would one not want to use Google framework , the way it sounded it to me is , Google is buggy and has lot of issues ,, but in my day to day use I don't experience anything like that
Just trying to figure out motivation for myself to try out this ROM
Click to expand...
Click to collapse
I thought the objective was made clear?
OOS[microG] - Basic and simple, customize it your way! Faster, lighter, more private, more secure, better performing!
OOS[microG] was made with simple goals in mind, Freedom and Performance!
It doesn't sound like you have used microG in the past?
DoR3M3 said:
I thought the objective was made clear?
OOS[microG] - Basic and simple, customize it your way! Faster, lighter, more private, more secure, better performing!
OOS[microG] was made with simple goals in mind, Freedom and Performance!
It doesn't sound like you have used microG in the past?
Click to expand...
Click to collapse
No I have not used in past and many users are new I guess
But how can u say better performing have u done any benchmarking ? Private I don't care
Secure how ? ...aren't we secured now? Google scans apps and all ..not sure what secure means coz it is a big context
Lighter means what ? Less in size ? Or less battery draining ? Any benchmarking ?
Google is pretty basic and simple too from end-user perspective...I can customize most things
Freedom = what ? We already have freedom , don't we ?
Manan79 said:
No I have not used in past and many users are new I guess
But how can u say better performing have u done any benchmarking ? Private I don't care
Secure how ? ...aren't we secured now? Google scans apps and all ..not sure what secure means coz it is a big context
Lighter means what ? Less in size ? Or less battery draining ? Any benchmarking ?
Google is pretty basic and simple too from end-user perspective...I can customize most things
Freedom = what ? We already have freedom , don't we ?
Click to expand...
Click to collapse
I was only asking, because by understanding and knowing microG, the Google Framework & Services, you'd then understand these things you are asking.
OOS[microG] isn't reinventing anything, or creating anything new, it has only incorporated into OxygenOS what has exsisted for several years in Android & microG.
It's already mentioned in the OP that the Google Framework & Services are heavier on the system resources, that's a fact, because of it, you don't get the same level of performance or battery life as microG.
The Google Framework & Services are Proprietary, and because of this, there are of course many discussions on the differences of Proprietary vs OpenSource as it relates to Freedom, Privacy and Security, that is why these things are mentioned in this ROM. Google also has a past track record that relates to many of these areas, that bring concern to many users...
Since we are discussing a ROM, this is not just about end-user perspective that you only see when using it, but what is underneath the hood at the System Level. At the System Level Google is not so basic and simple, it lacks the Freedom you are asking about in that it is Proprietary, only Google knows what is in that code, and that also begs the question over it's Security, when you can't audit the code and know what it's doing.
DoR3M3 said:
I was only asking, because by understanding and knowing microG, the Google Framework & Services, you'd then understand these things you are asking.
OOS[microG] isn't reinventing anything, or creating anything new, it has only incorporated into OxygenOS what has exsisted for several years in Android & microG.
It's already mentioned in the OP that the Google Framework & Services are heavier on the system resources, that's a fact, because of it, you don't get the same level of performance or battery life as microG.
The Google Framework & Services are Proprietary, and because of this, there are of course many discussions on the differences of Proprietary vs OpenSource as it relates to Freedom, Privacy and Security, that is why these things are mentioned in this ROM. Google also has a past track record that relates to many of these areas, that bring concern to many users...
Since we are discussing a ROM, this is not just about end-user perspective that you only see when using it, but what is underneath the hood at the System Level. At the System Level Google is not so basic and simple, it lacks the Freedom you are asking about in that it is Proprietary, only Google knows what is in that code, and that also begs the question over it's Security, when you can't audit the code and know what it's doing.
Click to expand...
Click to collapse
Ok I mostly care Abt perf and battery...so will try it out ..thanks
Manan79 said:
Ok I mostly care Abt perf and battery...so will try it out ..thanks
Click to expand...
Click to collapse
If you care to wait a few days, I am releasing a updated version, there were some changes made...
Thanks Bro
This work deserve more attention.
Even if it's not on Pie, I don't care, it's just too good. Pie is overrated and barely at Nougat kneel.
Thank you.
EDIT : Continuation from a DM ;
It is absolutely perfect in almost every areas,smooth and debloated of ****, sadly I can't make it work with a game called "Girls frontline" , it basically says "can't install the app" via playstore.
Of course, I got some paid apps like themes, hyperion launcher and another game that works.
So i'm turning to you, as I don't really know why it is happening.
As for your update, I can't wait to get it, it could probably fly the small issue i'm facing.
Also, I did your guide several times since the first time you created it, for fun, and I learnt lots.

Do Project Treble ROMs work with the Galaxy Tab S7+ 512GB Wi-Fi variant?

So, I've been wanting the Galaxy Tab S7+ for months. But I haven't had the money for it until now (yeah, you guesses it, stimulus payment). But I'm still on the fence about buying it. I know bootloader unlock, TWRP and Magisk root is available for this tab. But I don't want to be limited to just running stock-based ROM's. My plan is to flash a Project Treble-based firmware like Phh Treble, Resurrection Remix.
The questions I'd like to ask are:
1. This tab appears to be Treble compatible, it is listed on the Treble device compatibility page as working. But I would like to hear from an actual owner of this device that has successfully booted and ran a Treble/GSI ROM
2. The partition layout is ARM64 A/B and system-as-root?
3. Besides unlocking bootloader and flashing TWRP, are there any other special considerations I would need to know about?
Without this info, I won't buy, and Google doesn't always produce solid answers. I would like to become an active developer for this device as well, but I need compelling reasons to buy it, besides just great hardware, the latest Android 10/11, that kind of thing....the superficial stuff.
I could just buy now and test when I get it, Amazon has a 30 day return policy. But I don't think they will accept a tablet return if the warranty has been voided by the user. So this really isnt an option.
AnonVendetta said:
So, I've been wanting the Galaxy Tab S7+ for months. But I haven't had the money for it until now (yeah, you guesses it, stimulus payment). But I'm still on the fence about buying it. I know bootloader unlock, TWRP and Magisk root is available for this tab. But I don't want to be limited to just running stock-based ROM's. My plan is to flash a Project Treble-based firmware like Phh Treble, Resurrection Remix.
The questions I'd like to ask are:
1. This tab appears to be Treble compatible, it is listed on the Treble device compatibility page as working. But I would like to hear from an actual owner of this device that has successfully booted and ran a Treble/GSI ROM
2. The partition layout is ARM64 A/B and system-as-root?
3. Besides unlocking bootloader and flashing TWRP, are there any other special considerations I would need to know about?
Without this info, I won't buy, and Google doesn't always produce solid answers. I would like to become an active developer for this device as well, but I need compelling reasons to buy it, besides just great hardware, the latest Android 10/11, that kind of thing....the superficial stuff.
I could just buy now and test when I get it, Amazon has a 30 day return policy. But I don't think they will accept a tablet return if the warranty has been voided by the user. So this really isnt an option.
Click to expand...
Click to collapse
1. At present, AOSP v304 GSI can be booted, but no Magisk yet. This is if you have Android 11 stock FW. The situation with GSI might be different (probably better) with Android 10 stock FW, but I can no longer test this, as the latest BUC1 build blocked the downgrade path. You can still downgrade to Android 10 (up to ATK3) if you're on build BUBB or below.
2. This device uses a Super partition (also called dynamic partitions) for system, vendor, etc.. Because of this, flashing GSI is no longer trivial. You can try using this tool to flash a GSI from TWRP.
3. Currently TWRP cannot access /data if it's encrypted. You need to flash Multi-Disabler to disable encryption (which requires formatting /data) if you want TWRP to access it. Also, while Magisk works on stock FW, be careful when debloating as some Samsung components are not happy with certain components removed and would cause trouble.
LSS4181 said:
1. At present, AOSP v304 GSI can be booted, but no Magisk yet. This is if you have Android 11 stock FW. The situation with GSI might be different (probably better) with Android 10 stock FW, but I can no longer test this, as the latest BUC1 build blocked the downgrade path. You can still downgrade to Android 10 (up to ATK3) if you're on build BUBB or below.
2. This device uses a Super partition (also called dynamic partitions) for system, vendor, etc.. Because of this, flashing GSI is no longer trivial. You can try using this tool to flash a GSI from TWRP.
3. Currently TWRP cannot access /data if it's encrypted. You need to flash Multi-Disabler to disable encryption (which requires formatting /data) if you want TWRP to access it. Also, while Magisk works on stock FW, be careful when debloating as some Samsung components are not happy with certain components removed and would cause trouble.
Click to expand...
Click to collapse
Thanks for the info, I honestly didn't think I would ever get an answer.
You say the AOSP GSI can be booted. But do you speak from experience? Or just from what others have said?
The part about BUC1 blocking the downgrade path is useful, I'll keep that in mind before installing any OTAs or flashing firmware with Odin. Yes, I do imagine that Magisk is more compatible with AOSP based ROMs vs stock, that has always been my experience on other devices.
I already did some reading, I'm aware of the super partition thing. I know I'll have to unpack and repack the super.img, replacing the system.img with a Treble one.
I'm also aware of the file based encryption that TWRP can't read, I don't encrypt my devices, and plan to disable it.
I know all about debloating troubles, I've done it on numerous devices, important stuff can definitely break if you're not careful.
I'm wondering if you can answer a few more questions:
1. Are you rooted?
2. Can the system partition be remounted as read/write from within Android on stock firmware? I have heard cases where the dynamic partitions can prevent this, but supposedly it's not usually an issue on custom ROMs, just stock. I ask because I will be debloating, but if remounting system isnt possible, then I'll need to rely on Magisk for systemless debloating. Or just remain unrooted and debloat with ADB package disable commands (this doesn't really delete anything, and works without root).
3. If you are running Magisk,can you upload a screenshot of the main screen? I just want to see the A/B and SAR values.
4. Can you install the free version of Treble Check from Play Store, and post screenshots of the main info screen?
5. Is it possible to moves apps to SD without enabling adoptable storage (on stock, I know custom AOSP firmwares will require AS, or a root app like Apps2SD and a 2nd partition on SD.
I'm hoping to hear from at least another confirming user before I make a buying decision, spending $1k+ on a high end tablet is a big deal.
And if I do buy, I am serious about becoming a developer.
LSS4181 said:
1. At present, AOSP v304 GSI can be booted, but no Magisk yet. This is if you have Android 11 stock FW. The situation with GSI might be different (probably better) with Android 10 stock FW, but I can no longer test this, as the latest BUC1 build blocked the downgrade path. You can still downgrade to Android 10 (up to ATK3) if you're on build BUBB or below.
2. This device uses a Super partition (also called dynamic partitions) for system, vendor, etc.. Because of this, flashing GSI is no longer trivial. You can try using this tool to flash a GSI from TWRP.
3. Currently TWRP cannot access /data if it's encrypted. You need to flash Multi-Disabler to disable encryption (which requires formatting /data) if you want TWRP to access it. Also, while Magisk works on stock FW, be careful when debloating as some Samsung components are not happy with certain components removed and would cause trouble.
Click to expand...
Click to collapse
Thanks for the info, I honestly didn't think I would ever get an answer.
You say the AOSP GSI can be booted. But do you speak from experience? Or just from what others have said?
The part about BUC1 blocking the downgrade path is useful, I'll keep that in mind before installing any OTAs or flashing firmware with Odin. Yes, I do imagine that Magisk is more compatible with AOSP based ROMs vs stock, that has always been my experience on other devices.
I already did some reading, I'm aware of the super partition thing. I know I'll have to unpack and repack the super.img, replacing the system.img with a Treble one.
I'm also aware of the file based encryption that TWRP can't read, I don't encrypt my devices, and plan to disable it.
I know all about debloating troubles, I've done it on numerous devices, important stuff can definitely break if you're not careful.
I'm wondering if you can answer a few more questions:
1. Are you rooted?
2. Can the system partition be remounted as read/write from within Android on stock firmware? I have heard cases where the dynamic partitions can prevent this, but supposedly it's not usually an issue on custom ROMs, just stock. I ask because I will be debloating, but if remounting system isnt possible, then I'll need to rely on Magisk for systemless debloating. Or just remain unrooted and debloat with ADB package disable commands (this doesn't really delete anything, and works without root).
3. If you are running Magisk,can you upload a screenshot of the main screen? I just want to see the A/B and SAR values.
4. Can you install the free version of Treble Check from Play Store, and post screenshots of the main info screen?
I'm hoping to hear from at least another confirming user before I make a buying decision, spending $1k+ on a high end tablet is a big deal.
And I am serious about developing for this device if I do buy. Mainly for AOSP firmwares or porting LineageOS, but maybe for stock too.
It looks like I can't delete the previous double posts, and editing causes it to be posted again. I hate the new XDA layout, the old was so much better.
AnonVendetta said:
Thanks for the info, I honestly didn't think I would ever get an answer.
You say the AOSP GSI can be booted. But do you speak from experience? Or just from what others have said?
The part about BUC1 blocking the downgrade path is useful, I'll keep that in mind before installing any OTAs or flashing firmware with Odin. Yes, I do imagine that Magisk is more compatible with AOSP based ROMs vs stock, that has always been my experience on other devices.
I already did some reading, I'm aware of the super partition thing. I know I'll have to unpack and repack the super.img, replacing the system.img with a Treble one.
I'm also aware of the file based encryption that TWRP can't read, I don't encrypt my devices, and plan to disable it.
I know all about debloating troubles, I've done it on numerous devices, important stuff can definitely break if you're not careful.
I'm wondering if you can answer a few more questions:
1. Are you rooted?
2. Can the system partition be remounted as read/write from within Android on stock firmware? I have heard cases where the dynamic partitions can prevent this, but supposedly it's not usually an issue on custom ROMs, just stock. I ask because I will be debloating, but if remounting system isnt possible, then I'll need to rely on Magisk for systemless debloating. Or just remain unrooted and debloat with ADB package disable commands (this doesn't really delete anything, and works without root).
3. If you are running Magisk,can you upload a screenshot of the main screen? I just want to see the A/B and SAR values.
4. Can you install the free version of Treble Check from Play Store, and post screenshots of the main info screen?
I'm hoping to hear from at least another confirming user before I make a buying decision, spending $1k+ on a high end tablet is a big deal.
And I am serious about developing for this device if I do buy. Mainly for AOSP firmwares or porting LineageOS, but maybe for stock too.
Click to expand...
Click to collapse
I actually booted it myself and kept a backup of it so I can test it a bit further if needed. With TWRP and appropriate backups it's not difficult to switch back and forth.
Since Magisk can't work with Android 11 vendor at the moment, and that recent GSI builds are not certified for some reasons (which blocks Google login), my current use of GSI is still a bit limited, so I'm mostly still doing stuffs on stock.
As for other questions:
1. I'm rooted on stock ROM with Magisk (it works there). Magisk does not work on GSI with Android 11 vendor at the moment.
2. I haven't tried mounting system r/w from within Android, but TWRP certainly could mount it r/w, as Multi-Disabler needs to modify stuffs there. For GSI, you need to use vndklite variants in order to be able to mount system r/w.
Honestly, this is my first Samsung Android device and is also my first device with a super partition, so I still have a lot to learn...
EDIT: I'm using a Galaxy Tab S7+ 5G variant. I think for Wi-Fi variant most things should be similar... but I'm not really sure.
LSS4181 said:
I actually booted it myself and kept a backup of it so I can test it a bit further if needed. With TWRP and appropriate backups it's not difficult to switch back and forth.
Since Magisk can't work with Android 11 vendor at the moment, and that recent GSI builds are not certified for some reasons (which blocks Google login), my current use of GSI is still a bit limited, so I'm mostly still doing stuffs on stock.
As for other questions:
1. I'm rooted on stock ROM with Magisk (it works there). Magisk does not work on GSI with Android 11 vendor at the moment.
2. I haven't tried mounting system r/w from within Android, but TWRP certainly could mount it r/w, as Multi-Disabler needs to modify stuffs there. For GSI, you need to use vndklite variants in order to be able to mount system r/w.
Honestly, this is my first Samsung Android device and is also my first device with a super partition, so I still have a lot to learn...
EDIT: I'm using a Galaxy Tab S7+ 5G variant. I think for Wi-Fi variant most things should be similar... but I'm not really sure.
Click to expand...
Click to collapse
I am using the WIFI variant (SM-T870) on the latest stock release (T870XXU2BUC6) with root and Magisk 22.1 running just fine. Root was accomplished by flashing a Magisk modified boot image with Odin found here https://forum.xda-developers.com/t/...-updated-3-29-21.4159291/page-2#post-84843377 on this thread. I used Titanium Backup to debloat and have had no issues at all. The performance is great and the stability sound. I would suspect that a similar arrangement could accomplished on the other versions of the tablet but cannot speak from experience. Personally I have never had much luck flashing Project Treble GSIs on any of my devices. They tend to be very unstable and iffy at best and I always wind up returning to stock or another custom ROM choice.

Phillips Sonicare for Kids Root Check bypass wtf

Backstory: So got my daughter a bluetooth enabled toothbrush named in title, and loaded up the app for it:
Philips Sonicare For Kids - Apps on Google Play
Transform brush time into fun time!
play.google.com
Running on a OnePlus 6, Android 10 stock firmware other than bootloader unlocked, Magisk installed. Start it up, whines it is rooted and refuses to run. Sputter some colorful language, add app to Magisk Hide, restart, poof, works great.
Now daughter likes it, and don't want to give her my phone twice a day... so open the drawer and pull out an older phone, LG G6. Old firmware, prob full of security issues, figure I'll install LineageOS on it. OK, great, get through all that, shiny running system... repeat app install... and ugh... "t3h r00t3d phone!".
This time, Magisk Hide isn't "fixing" the problem, and I am curious what the difference is... same app version on both phones. Safetynet check passes on both phones. The only real differences I can cite are (1) Android 11 OS base and (2) Roar Gapps MiniMe build (vs full Gapp suite on stock OnePlus rom). At this point, there aren't other apps on the device (e.g. SuperSU or similar usual suspect).
Any suggestions on what is different that an app could check and call out a rooted phone?
Answering my own post, in case anyone searches this and finds it helpful...
Turns out this app appears to blacklist Lineage OS.
Reflashed clean, OS only... fail. (No root or safetynet at this point)
Added somewhat normal Gapps, now with working safetynet... fail.
Didn't need to install Magisk at this point.
Lets test the theory... grab another OS image at random, flash it (still no Gapps, Magisk, SN)... success!
Install Magisk, still success!

Question How to root Pixel 6 and successfully hide root with latest version(s) of Magisk?

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.

Categories

Resources