Database Develop

[ROM][PEREGRINE][6.0][STOCK]Identity Crisis 6 LTE NoGoogle (updated to 1.2c)

Introduction
This ROM is based on lost101's, kingkaminari's and VitaTaf's work you can find here. The main aim of my modifications is putting debloating to the extreme and getting rid of intrusive Google spying services that violate user's privacy. Before you flash this ROM read all the information below and make sure you still want to do it as some stuff you find essential might be missing and irreplaceble. Please also mind you will have to setup your device manually with ADB to unlock all of its functions.
Disclaimer
Even if everything works 100% fine for me I take no responsibility for anything that happens to anyone else's device after flashing my ROM. If you want to try it, do it on your own risk. Always backup your data.
Description
This is Identity Crisis 6 LTE v1.0a by lost101, kingkaminari and VitaTaf with the following modifications:
Version 1.2c
Changes
Version 1.0
1. build.prop
#USB debugging lock bypass
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb
It is advised to remove these lines from build.prop after you're done with setup as they compromise your device's security
2. Removed from system/app:
- BasicDreams
- BookmarkProvider
- Calculator
- CalendarGoogle
- com.motorola.android.setting.diag_mdlog
- DeskClockGoogle
- Exchange3Google
- FaceLock
- FMRadioService
- GoogleContactsSyncAdapter
- HoloSpiralWallpaper
- HTMLViewer
- LatinImeGoogle
- LiveWallpapers
- LiveWallpaperPicker
- NoiseField
- PartnerBookmarksProvider
- PhaseBeam
- Piktures
- PrintSpooler
- UserDictionaryProvider
3. Removed from system/etc/permissions:
- com.google.android.maps.xml
- com.google.android.media.effects.xml
- com.google.widevine.software.drm.xml
- com.motorola.camera.xml
- com.motorola.context.xml
- com.motorola.gallery.xml
- com.motorola.software.fmradioservice.xml
- com.motorola.software.storageoptimizer.xml
4. Removed from system/framework:
- com.google.android.maps.jar
- com.google.android.media.effects.jar
- com.google.widevine.software.drm.jar
- com.motorola.android.dropboxhelper.jar
- com.motorola.gallery.jar
5. Removed from system/priv-app:
- AppDirectedSmsProxy
- atfwd
- AudioEffects
- BackupRestoreConfirmation
- CalendarProvider
- CallLogBackup
- CellBroadcastReceiver
- ConfigUpdater
- Contacts
- ContactsProvider
- CQATest
- EmaraPhoneExtensions
- GmsCore
- GoogleBackupTransport
- GoogleFeedback
- GoogleLoginService
- GoogleOneTimeInitializer
- GooglePartnerSetup
- GoogleServicesFramework
- MotCamera
- MotoOneTimeInitializer
- Phonesky
- PreloadContacts
- SetupWizard
- SetupWizardExt
- StorageOptimizer
- WallpapaerCropper
- WapPushSI
6. Removed from system/usr/srec:
- en-US folder and its files
7. Removed from system/vendor:
- pittpatt folder and its files
8. Added to system/apps:
- AnySoftKeyboard
- MiXplorer
Flashing
1. Boot into TWRP
(2. Backup)
3. Format data (Wipe>Format data>yes)
4. Transfer ROM to SD card/Local storage
5. Wipe>Factory reset
6. Install
7. Reboot
Setup (version 1.0 only)
When the installation completes you'll find there's no Setup Wizard, and some important UI components (Home button, Notifications, Quick Settings) are blocked. There's also no access to Developer's Options. Don't worry - they're normally being unlocked after you're done with Setup Wizard but since it's not there you need to do it manually:
1. Open ADB terminal on your computer
2. Connect your device
3. Execute the following commands:
Code:
adb shell
su
settings put global device_provisioned 1
settings put secure user_setup_complete 1
reboot
After reboot your device is ready to use.
Known issues
- Please refer to IDCrisis 6 LTE original thread
Life after Google
You can try using Micro GmsCore to access Play Store content, and here are some alternatives:
1. Interesting and useful apps in F-Droid store:
- Adaway (system-wide ad blocker)
- AFWall+ (very nice firewall. I use it in whitelist mode because it blocks internet access to all apps by default)
- Etar (calendar. Won't work without Google calendar service and account)
- K-9 mail (bit ugly but awesome mail client)
- Open camera (stock camera replacement)
- Wifi automatic (turns wifi off when you lock the screen which saves battery and improves security. Bugged a little and randomly disables wifi from time to time)
- SMSsecure (messaging app with encryption)
- 920 Editor (text editor)
- Document Viewer (self explanatory)
- Network Log (self explanatory)
2. Other interesting and useful apps around the web (mostly on XDA):
- ApkTrack (app updates tracker),
- Calc+ (calculator),
- CoolTool (CPU and RAM usage and other info display),
- DejaOffice (office app that looks a bit outdated, but it's the only calendar app to work without Google services I found so far),
- Disconnect.me (private web searches; the app FC right after starting it, probably due to lack of Google search services available)
- DriveDroid (turns the phone into Linux live USB),
- ES File Explorer (file explorer),
- Firefox (web browser),
- Gravity Screen (Turning screen off and on without using physical power button),
- Greenify (apps hibernator),
- KWGT (custom widget maker),
- LiveBoot (Chainfire's app that replaces boot animation with system log display),
- maps.me (open source google maps alternative),
- MiXPlorer (file explorer),
- MoboClean (permissions manager),
- Naked Browser (web browser),
- NetGuard (no-root firewall),
- NeutriNote (notes),
- Nova Launcher (launcher)
- Open Camera (same as F-Droid app),
- Parasol (community based permission manager),
- PryFi (WiFi security),
- QuickPic (gallery),
- Recently ("close all apps" button in recents window),
- Recordr (sound recording app),
- Servicely (services management. Think twice before installing and using it - developer's G+ site, developer's APKMirror downloads
- SD Maid (cleaning tool),
- Super Backup (apps, sms, call logs, etc. backup),
- Titanium Backup (data backup),
- True phone (dialer),
- VLC (media player),
- WifiKill (WiFi killer),
- Wifi Protector (WiFi security, anti-wifikill),
- Xposed
You can find more interesting apps and links on this XDA forum
3. Software that may help you secure your device - sufficientlysecure.org
4. More security software - Secure Mobile Apps
5. XDA Labs (alpha version of XDA app store)
6. Firefox browser add-on that lets you download apk files directly from google play store (without Google account connected to your device) in case you can't find desired app anywhere else.
7. Alternative app-stores, .apk mirrors, etc. - use at your own risk. So far I only tried Amazon's store - the pro is that it exists, the cons are that it requires tons of permissions, has very unfriendly interface, takes a lot of space, and the apps you download will only work as long as the store's app is installed.
Credits and thanks
Motorola for making such a good device
Google for supporting Android (but not for invading it with their intrusive services)
lost101, kingkaminari and VitaTaf - creators of original ROM
HootanParsa - creator of MIxplorer
Menny Even Danan and all creators of AnySoftKeyboard
Tesla Coil and all creators of Nova Launcher
Klaus Weidner, creator of Hacker's Keyboard
All people behind TWRP
All the developers who share useful information and solutions in the web
Please let me know if I missed someone, I'll be happy to update this list
Download
IC6_lte_v1.2c_nogoogle.zip
Identity Crisis 6 LTE v1.0a_NoGApps_mod_v.1.0_beta.zip
Version information
Status: stable
Created: 4.03.2016
Updated: 24.05.2016

reserved

reserved 2

Has anyone had success getting this working yet?
I'm having trouble getting this to work.
Yesterday when I tried to install it i got the following error:
"symlink: no of syymlinks failed = 1
Updater process ended with error: 7
Error installing zip file '/sdcard/Identity+Crisis+6+LTE+v1.0a_NoGApps_mod_v.1.0_beta.zip'
Tried again today and managed to get it to install after rebooting recovery a few times, but ended up getting into a bootloop for 40 minutes.
I tried wiping everything, ART cache, system, data, internal and cache, but still get the same, an endless bootloop.
Any ideas?
Edit: This is on an XT1039

cvamoose said:
Has anyone had success getting this working yet?
I'm having trouble getting this to work.
Yesterday when I tried to install it i got the following error:
"symlink: no of syymlinks failed = 1
Updater process ended with error: 7
Error installing zip file '/sdcard/Identity+Crisis+6+LTE+v1.0a_NoGApps_mod_v.1.0_beta.zip'
Tried again today and managed to get it to install after rebooting recovery a few times, but ended up getting into a bootloop for 40 minutes.
I tried wiping everything, ART cache, system, data, internal and cache, but still get the same, an endless bootloop.
Any ideas?
Edit: This is on an XT1039
Click to expand...
Click to collapse
The first issue is internal TWRP error that happens pretty randomly, just restart recovery and it should be gone. The second thing never really happened to me, and I have to ask if you've followed instalation instructions? They're quite strict. You must wipe data and do a factory reset prior to installation. Just try again, following all steps exactly.

I'd also consider waiting a bit for final stable version with error fixes of lost101's ROM I use as a base. It's still kind of WIP.

I'd sure want to try this out, just wondering how well Google Play and Youtube work with the Micro G framework? Those are basicly the only google apps I use.
I could use the browser for youtube, create a link directly to the homescreen maybe. And I probably could survive without the play store to, just download apk from a mirror and sideload, but it would be kind of a hassle.
Anyhow, I probablt wait a few weeks until the MM rom seems stable.

Are you going to update this with the latest MM build by lost101?

baxtex said:
Are you going to update this with the latest MM build by lost101?
Click to expand...
Click to collapse
V1.2 seems stable, so I'll try to build something on this one, but don't really have much free time atm

No worries, just wondering!
Edit: I could actually remove all this stuff myself, the setup should be identical right?
Edit: Here is a version were I removed the same things you did. But I can't get it to work, or rather, I can't setup the phone. As your description says, you need to set it up with adb. But my computer won't detect the phone. I've tried reinstalling drivers here and there but whatever I do, Windows/adb won't detect any device. I do get a beep however that it is connected, and it says something like MTP usb device. But I can't do anything with that. I've tried installing it as an adb device instead but that didn't work.
https://mega.nz/#!P4k1QYwS!fBCp3E4uyjBXy7x6x_uTLTnj3pWjoIbgpqvodzWfEuQ
So I restored my backup, and I can connect to my pc just fine. In the device manager my device is shown as: Android Device>Motorla ADB Interface.

baxtex said:
No worries, just wondering!
Edit: I could actually remove all this stuff myself, the setup should be identical right?
Edit: Here is a version were I removed the same things you did. But I can't get it to work, or rather, I can't setup the phone. As your description says, you need to set it up with adb. But my computer won't detect the phone. I've tried reinstalling drivers here and there but whatever I do, Windows/adb won't detect any device. I do get a beep however that it is connected, and it says something like MTP usb device. But I can't do anything with that. I've tried installing it as an adb device instead but that didn't work.
https://mega.nz/#!P4k1QYwS!fBCp3E4uyjBXy7x6x_uTLTnj3pWjoIbgpqvodzWfEuQ
So I restored my backup, and I can connect to my pc just fine. In the device manager my device is shown as: Android Device>Motorla ADB Interface.
Click to expand...
Click to collapse
I read through IC thread - Lost101 is still polishing it, so I'll wait for some final build. And I guess you've got problem with ADB connection, because you didn't add persistent ADB debug to build.prop, or added but with some dodgy notepad (in Windows use Notepad++) - the lines that need to be added are in the OP.

minimale_ldz said:
Disclaimer
Even if everything works 100% fine for me I take no responsibility for anything that happens to anyone else's device after flashing my ROM. If you want to try it, do it on your own risk. Always backup your data.
Known issues
- Please refer to IDCrisis 6 LTE original thread
Click to expand...
Click to collapse
I have found a bug.
I was setting a lockscreen password that contained = in it and it came up as bad bad characted (I thought it's just a bug because it wouldn't show that error on stock firmware) so I have tried to enter the same password once more and it worked. Then I have locked the phone and couldn't unlock it because I allways entered the wrong password.
I think that the same thing would happen to encrypted devices.
I have found an interesting app that lets you enter permission control settings without root, because these permission settings is hidden in most android versions that came before marshmallow. Not granual, but still better than nothing.
It's size is 7kb, it asks for no permissions, probably because it's just a shortcut to the settings.
To people who don't have Play Store:
Install BlueStacks on your pc.
Root it using King Root.
Install desired apps using Play Store.
Install ES File Explorer:
From panel select:
-Tools/Root Explorer
-Tools/Show hidden files
-Network/Cloud/+/your desired cloud provider and log in.
-Local/Device/data/app .
Select your installed apps and copy them to your drive.
From your Play Store missing device goto your cloud provider website, log in ,download and install your apps.
This method can be long, but you will have all of the apps that you downloaded on cloud so you won't have to do the same process over and over again.

@minimale_ldz since u bought new phone I have to ask - you still remember about Moto G members, right?
I'm not asking when you'll update this rom, but if you're even going to

toster88 said:
@minimale_ldz since u bought new phone I have to ask - you still remember about Moto G members, right?
I'm not asking when you'll update this rom, but if you're even going to
Click to expand...
Click to collapse
It's coming soon

@toster88 motivated me with his comment to spend some time on preparing updated version of this rom. It' based on @lost101's IC6 LTE 1.2c version and contains a few little changes:
- AnySoftKeyboard replaced with Hacker's Keyboard as ASK is a bit awkward when it comes to accesing numeric keys
- MiXplorer has been updated to the newest version (6.4.0)
- Nova Launcher added (sorry for some artifacts like empty folders or Google search box, but I have no idea how to get rid of them)
- persistent ADB debugging removed from build.prop as it's no longer needed. Init.d script deals with initial device provisionig now. /system/etc/init.d/setup can be removed after first boot if everything is working fine (quick settings, home button, developer's options, etc. are accessible).
That's about it, I hope you'll enjoy this build. Please let me know if there are any bugs specific to this rom (and not to MM or IC6 1.2c) as I'm not using XT1039 as a daily driver anymore.

Temporary Google Drive link is now live

alezardstar said:
@minimale_ldz - Can you share with us how did you manage to debloat all the ROM and purge every GApps out of it preserving its stability? Did you delete the apks by hand using your laptop before installing the zip or what did you exactly do? I'm keen to get this working on the very last release (1.5b) for Falcon.
Thanks in advance.
Click to expand...
Click to collapse
You can just unzip the rom and remove unwanted apps (with their folders) by hand in Windows file explorer and then zip it back. Or, if you wanna feel more like a propper dev you can do it with Superr Kitchen where you create custom debloat list. Both methods are confirmed to work. Removing GApps is a bit tricky as you need to remove all of them - if you leave anything it may give you FCs or black screen after boot. You will also have to choose some way to provision the device without GApps and i believe the smoothest method is by init.d script sice it's enabled in @lost101 rom and doesn't require users to do anything after installation. The script looksi like this:
Code:
#!/system/bin/sh
su -c "settings put global device_provisioned 1"
su -c "settings put secure user_setup_complete 1"
and goes in /system/etc/init.d folder
I hope that helps.

alezardstar said:
Thanks for your response. I definitely shall give it a spin with next Identity Crisis release. It happens to me I do not work on Windows, rather GNU/Linux. Do you think I can delete all the OP mentioned apks and on top of that any missed folder/apk appearing on this link using Fedora 25? As far as I could read, the link I'm passing on has Linux instructions, though being honest, I have no leisure time to read it thoroughly and that's why I'm saying I shall do it next Identity's release better. In the meantime, I want to be a hundred percent sure about what I will do when the moment comes in. Can you tell me what provision is? What does it stand for? Should I get a signature spoofer? All I want to do is Identity working as it works itself, with no GApps and supersu working as it's been working always. Although I'd say installing microG may cushion the blow since it is a FLOSS Google framework that will not make things break in a regular use. To sum it up, do I need to create a .txt file or something with the code and thereafter make it work with a init.d script application or something similar?
Thanks for all your help! Looking forward to hear from you and sorry for my late response. Real life keeps me away from my beloved hobbie: learning.
Click to expand...
Click to collapse
I guess it should work pretty much the same on Linux. Do mind I've removed much more than just GApps and today I'd left some more apps in the rom as I found them useful - eg. Calendar Provider or FM radio, but it's up to you. The bare minimum, required to get rid of GApps is:
Code:
/system/app:
- ConfigUpdater
- CalendarGoogle
- GoogleContactsSyncAdapter
/system/priv-app:
- BackupRestoreConfirmation
- GmsCore
- GoogleBackupTransport
- GoogleFeedback
- GoogleLoginService
- GoogleOneTimeInitializer
- GooglePartnerSetup
- GoogleServicesFramework
- MotoOneTimeInitializer
- Phonesky
- SetupWizard
- SetupWizardExt
The list you linked is more extensive and goes deeper into the system but it's quite similair to what I've done. You cane safely remove
Code:
system/usr/srec/en-US/
as it contains speech recognition files that Google Services use to listen to us.
I was careful with
Code:
system/lib/
because I didn't find any source describing what these libraries are actually for. Removing anything with "google" in its name seems safe. You can compare what IDCrisis has with the list and see if it can be removed safely - there's a lot of experimenting involved but the list looks like a good guide.
Code:
system/vendor/pittpatt/
contains face recognition system that I find useless with or without GApps and it can be safely removed.
Now, when you remove all GApps you'll have to provision your device. Long story short is that when you first boot your phone after flashing new rom it will start with Setup Wizard where you'll be asked for wifi password, google account details and where you accept all terms & conditions. By default you're locked in setup mode until it's finished - you can't use home button to escape it, you can't access settings, etc. If you remove GApps there's no Setup Wizard so your phone will stay in setup mode and you need to end it manually. Like I said before, the best way is to use init.d script. Use Notepad to create new file, copy the lines I posted last time, save it without any extension, I believe its permissions need to be set to 755 (rwxrxrx). Place the file in
Code:
system/etc/init.d
and that's it.
Alternatively you can use ADB or terminal emulator to execute these commands:
Code:
adb shell (only if you use ADB)
su
settings put global device_provisioned 1
settings put secure user_setup_complete 1
or you can use XDRsetup app I made to do the job (it needs root to work).
Good luck

alezardstar said:
@minimale_ldz - Apologies for my late answer. I've been busy. Thanks for your response. It is appreciated what you've done for Peregrine's users and hence for everyone who's willing to ditch GApps from @lost101 builds.
At the moment I'm stuck at a step. I'm on Fedora 25 and I want to remove a whole folder within the system /system/app/MagiskManager/ or whatever the directory is and I can not. Albeit I might delete the superuser and Magisk folders whose location is the very first thing we see as we open the .zip, I can't do the same with folders within the system and I wonder why. The other option is extracting the whole content of the ROM in a new directory and deleting files at my will. Thereafter, I can zip it back. The problem is that I do not know how to zip it back. Do you have any idea of somebody who mod on GNU/Linux?
On the other hand, I saw this apk you passed on to make the init.d script work. The simple steps that popped up on my mind were:
- Factory reset.
- Flash ROM + supersu.zip
How can I put your application within the system folders and ensure it'll work as expected? Another thing that I lack knowledge of is the permissions. How can I give a file or a folder permissions on GNU/Linux? There's nothing else I can think of other than wiping everything, flashing the ROM alongside the supersu.zip and booting up but as you told me, I'd be frozen at the first screen. It's strange for me to get ahead but I'm keen to learn and get ahold from you anytime.
Click to expand...
Click to collapse
My knowlege of Linux is pretty much none. I'm using Ubuntu for Superr's Kitchen and that's it. I don't know how different Fedora is from Ubuntu, but Ubuntu interface is very similair to Windows, so never had any problems with simple files operations like unpacking, deleting, etc, and there's always Google at hand with tons of tips and help. Extracting the rom.zip is a good first step, but I'd install the Kitchen - it really makes things esier.
BTW - beside Magisk and Superuser folders there are also apps in /system/app that need to go if you're deleting binaries. They will survive factory reset but won't work. AFAIK they are in lost101's only temporarily and he said he'll use Chainfire's SU in next version anyway.
For setting permissions, as mostly Windows user, I have two solutions - you can either set them in TWRP using its file manager or do it in Android (I'm using MiXplorer for that). You just need to root your rom first.
And you won't be frozen at the first screen if you remove all GApps and SetupWizard apks.

I got almost everything working, but I can't access the Phone via USB from my WIN7 Desktop. It works with adb/fastboot but not as MobileDevice, also it is shown in WIN-Eplorer as XT1072. It did work before I flashed this ROM.
Any advice would be highly appreciated
Thanks in advance
Solved
"Internal Storage not accessible from PC?
With Marshmallow, the default USB connection type is 'Charging only' mode. You can change USB mode to 'MTP' via the pull-down notification option"

[2016.10.10] suhide v0.55 [CLOSED]

THIS IS CURRENTLY NOT WORKING
A newer version is available here: https://forum.xda-developers.com/apps/supersu/suhide-lite-t3653855
suhide is an experimental (and officially unsupported) mod for SuperSU that can selectively hide root (the su binary and package name) from other applications.
Pros
- Hides root on a per-app base, no need to globally disable root
- Doesn't need Xposed
- Even supports SuperSU's ancient app compatibility mode (BINDSYSTEMXBIN)
- Passes SafetyNet attestation by default on stock ROMs (last officially tested on 2016.10.07)
Cons
- Ultimately a losing game (see the next few posts)
- No GUI (at the moment) - Unofficial GUI by loserskater
Requirements
- SuperSU v2.78 SR1 or newer (link)
- SuperSU installed in systemless mode
- Android 6.0 or newer
- TWRP (3.0.2 or newer, with access to /data - link!) or FlashFire (link)
Xposed
Xposed is not currently officially supported, but if you want to use it directly, you must be using @topjohnwu 's systemless xposed v86.2 exactly (attached at the bottom). It seems to mostly work during my non-extensive testing, but there are still some performance issues (both boot-time and run-time). Proceed with caution, expect bootloop.
Alternatively, there are some reports that the latest Magisk version + the latest systemless xposed (for Magisk) also works. I have not personally tested this.
CyanogenMod
I've personally tested with CM13 on i9300 without issue, however, several users are reporting it doesn't work for them. Proceed with caution, expect bootloop. Also, aside from just flashing SuperSU, you need to make sure /system/bin/su and /system/xbin/su are removed, or CM's internal root will still be used.
Usage
Install/Upgrade
- Make sure you have the latest SuperSU version flashed in systemless mode
- Make sure you are using the latest TWRP or FlashFire version
- Remove any and all Xposed versions
- If you have been having issues, flash suhide-rm-vX.YY.zip first, and note that your blacklist has been lost.
- Flash the attached suhide-vX.YY.zip
- If you are upgrading from suhide v0.16 or older, reflash SuperSU ZIP, and note that your blacklist has been lost.
- Optionally, flash the Xposed version linked above, and pray
At first install SafetyNet is automatically blacklisted.
If you have just flashed a ROM, it is advised to let it fully boot at least once before installing suhide.
Uninstall
- Flash the attached suhide-rm-vX.YY.zip. The version may appear older, the uninstall script doesn't change very often.
Blacklisting an app
You need the UID (10000 to 99999, usually 10xxx) of the app, which can be tricky to find, or the process name. There may be a GUI for this at some point.
(Note that all commands below need to be executed from a root shell)
If you know the package name, ls -nld /data/data/packagename will show the UID - usually the 3rd column.
Similarly, for running apps, ps -n | grep packagename will also show the UID - usually the 1st column.
Note that the process name is often the same as the package name, but this is not always the case. UID is more reliable for identifying a specific app, and it is also faster than blocking based on process names.
When you know the UID or process name:
Add to blacklist: /su/suhide/add UID or /su/suhide/add processname
Remove from blacklist: /su/suhide/rm UID or /su/suhide/rm processname
List blacklist: /su/suhide/list
All running processes for that UID or process name need to be killed/restarted for su binary hiding. For SuperSU GUI hiding, the device needs to be restarted. I recommend just (soft-)rebooting your device after making any changes.
Please keep in mind that many apps store their rooted state, so you may need to clear their data (and then reboot).
Integration into SuperSU
This mod isn't stable, and probably will never be (see the next few posts). As SuperSU does aim to be stable, I don't think they're a good match. But who knows, it all depends on how things progress on the detection side.
Detections
This mod hides the su binary pretty well, and does a basic job of hiding the SuperSU GUI. The hiding is never perfect, and suhide itself is not undetectable either. This will never be a perfectly working solution.
Debugging bootloops
- Get your device in a booting state
- Make sure you have TWRP or a similar recovery
- Install LiveBoot (link)
- If you are not a LiveBoot Pro user, enable the Freeload option
- Enable the Save logs option
- Recreate the bootloop
- In TWRP, get /cache/liveboot.log , and ZIP+attach it to a post here.
Download
Attached below.
Any rm version should work to uninstall any suhide version.
There may be multiple versions of suhide attached, please look carefully which one you are downloading!
YOU ARE EXPLICITLY NOT ALLOWED TO REDISTRIBUTE THESE FILES
(pre-v0.51: 17410 downloads)

Hiding root: a losing game - rant du jour
Most apps that detect root fall into the payment, banking/investing, corporate security, or (anit cheating) gaming category.
While a lot of apps have their custom root detection routines, with the introduction of SafetyNet the situation for power users has become worse, as developers of those apps can now use a single API to check if the device is not obviously compromised.
SafetyNet is of course developed by Google, which means they can do some tricks that others may not be able to easily do, as they have better platform access and control. In its current incarnation, ultimately the detection routines still run as an unprivileged user and do not yet use information from expected-to-be-secure components such as the bootloader or TPM. In other words, even though they have slightly more access than a 3rd party app, they still have less access than a root app does.
Following from this is that as long as there is someone who is willing to put in the time and effort - and this can become very complex and time consuming very quickly - and SafetyNet keeps their detection routines in the same class, there will in theory always be a way to beat these detections.
While reading that may initially make some of you rejoice, this is in truth a bad thing. As an Android security engineer in Google's employ has stated, they need to "make sure that Android Pay is running on a device that has a well documented set of API’s and a well understood security model".
The problem is that with a rooted device, it is ultimately not possible to guarantee said security model with the current class of SafetyNet tamper detection routines. The cat and mouse game currently being played out - SafetyNet detecting root, someone bypassing it, SafetyNet detecting it again, repeat - only serves to emphasize this point. The more we push this, the more obvious this becomes to all players involved, and the quicker SafetyNet (and similar solutions) will grow beyond their current limitations.
Ultimately, information will be provided and verified by bootloaders/TrustZone/SecureBoot/TIMA/TEE/TPM etc. (Samsung is already doing this with their KNOX/TIMA solutions). Parts of the device we cannot easily reach or patch, and thus there will come a time when these detection bypasses may no longer viable. This will happen regardless of our efforts, as you can be sure malware authors are working on this as well. What we power-users do may well influence the time-frame, however. If a bypass attains critical mass, it will be patched quickly.
More security requires more locking down. Ultimately these security features are about money - unbelievably large amounts of money. This while our precious unlocked bootloaders and root solutions are more of a developer and enthusiast thing. While we're all generally fond of shaking our fists at the likes of Google, Samsung, HTC, etc, it should be noted that there are people in all these companies actively lobbying to keep unlocked/unlockable devices available for us to play with, with the only limitation being that some financial/corporate stuff may not work if we play too hard.
It would be much easier (and safer from their perspective) for all these parties to simply plug that hole and fully lock down the platform (beyond 3rd party apps using only the normal APIs). Bypassing root checks en masse is nothing less than poking the bear.
Nevertheless, users want to hide their roots (so do malware authors...) and at least this implementation of suhide is a simple one. I still think it's a bad idea to do it. Then again, I think it's a bad idea to do anything financial related on Android smartphone that isn't completely clean, but that's just me.
Note that I have intentionally left out any debate on whether SafetyNet/AndroidPay/etc need to be this perfectly secure (most people do their banking on virus ridden Windows installations after all), who should get to decide which risk is worth taking, or even if Google and cohorts would be able to design the systems more robustly so the main app processor would not need to be trusted at all. (the latter could be done for Android Pay, but wouldn't necessarily solve anything for Random Banking App). While those are very interesting discussion points, ultimately it is Google who decides how they want this system to work, regardless of our opinions on the matter - and they want to secure it.

--- reserved ---

Changelogs
2016.10.10 - v0.55 - RELEASE NOTES
- Some code cleanup
- Support for blocking based on process name
- Should fix some crashes (requires uninstall/reinstall to activate)
2016.10.07 - v0.54 - RELEASE NOTES
- Fix for latest SafetyNet update
2016.09.19 - v0.53 - RELEASE NOTES
- Haploid container (monoploid)
2016.09.18 - v0.52 - see v0.51 release notes below
- Fix root loss on some firmwares
2016.09.18 - v0.51 - RELEASE NOTES
- Complete redesign
- Zygote proxying (haploid)
- Binder hijacking (diploid)
- su.d instead of ramdisk modification
- Xposed supported (-ish)
2016.09.04 - v0.16 - RELEASE NOTES
- Fix some SELinux access errors
- Should now work on devices that ask for a password/pattern/pin immediately at boot - for real this time!
- Binderjacking improvements for Nougat
2016.08.31 - v0.12 - RELEASE NOTES
- Fix some issues with suhide-add/rm scripts
- Fix not working at all on 32-bit devices
- Should now work on devices that ask for a password/pattern/pin immediately at boot
- Rudimentary GUI hiding
- No longer limited to arm/arm64 devices: support for x86/x86_64/mips/mips64 devices added
2016.08.29 - v0.01
- Initial release

As always thank you Chainfire! I will try and edit this post.
Edit @Chainfire this seems to work for enabling Android Pay! I didn't get the chance to actually pay yet. But it did let me add my card and did not display the message about a failed authorization of Android check! Before I couldn't even get past that first screen.
Edit 2: @Chainfire It seems to of had an adverse effect on Snapchat. I cleared cache on the app, uninstalled and reinstalled and restarted. It kept Force closing after a photo no matter what. I used suhide-rm and it seems to have fixed the app from any issues. Thanks again and hopefully we'll get you some more reports. Either way your solution works!
Tested on stock rooted 7.0 Nexus 6p.

@Chainfire
What was your reason for doing this project?
Sent from my Nexus 6P using XDA-Developers mobile app

Ofthecats said:
What was your reason for doing this project?
Click to expand...
Click to collapse
For building it, curious if the method I came up with would work well. For releasing, if others are doing it, join them or be left behind.

I'm assuming with custom ROM android pay still won't work right?

HamsterHam said:
I'm assuming with custom ROM android pay still won't work right?
Click to expand...
Click to collapse
I'd just give it a try. It's spoofing the specific app, not the entire ROM that matters. It's fairly simple to try.

Installed on LG G4 w/ V20g-EUR-XX update and rerooted with TWRP 3.0.2-0 and SuperSU-v2.76-2016063161323. seems to be working fine, for the moment. Thank you for the update.

So far so good, I was able to add card to android pay. I would try using it during lunch and report back. Again, thanks for the continuous hard work.

djide said:
So far so good, I was able to add card to android pay. I would try using it during lunch and report back. Again, thanks for the continuous hard work.
Click to expand...
Click to collapse
What was the UID or process you found to blacklist it with?
Sent from my ONEPLUS A3000 using Tapatalk

how to install it? which file should I flash ? Both?

I can't see to add an app using terminal.
I'm typing in
/data/adb/suhide-add 10284
Says file not found. Can someone help, cheers.

Joshmccullough said:
What was the UID or process you found to blacklist it with?
Click to expand...
Click to collapse
Android Pay comes blacklisted out-of-the-box

HamsterHam said:
I can't see to add an app using terminal.
I'm typing in
/data/adb/suhide-add 10284
Says file not found. Can someone help, cheers.
Click to expand...
Click to collapse
Are you in Android or TWRP ?
ls -l /data/adb/

Chainfire said:
Android Pay comes blacklisted out-of-the-box
Click to expand...
Click to collapse
Derp. That's what I get for not reading the entire sentence under 'Install' in the OP......thanks!

PedroM.CostaAndrade said:
how to install it? which file should I flash ? Both?
Click to expand...
Click to collapse
Please don't quote a large post like that just to ask a single question.
Please read the first post, so you know what to do.

OnePlus 2 here, stock 6.0.1, systemless rooted with SuperSU Pro v2.76, flahed using Flashfire.
Passes SafetyNet check, does not pass my bank's root check, propably for the reasons the OP states above.

thdervenis said:
OnePlus 2 here, stock 6.0.1, systemless rooted with SuperSU Pro v2.76, flahed using Flashfire.
Passes SafetyNet check, does not pass my bank's root check, propably for the reasons the OP states above.
Click to expand...
Click to collapse
You need to blacklist the UID for your bank. Directions are in the OP.

MIUI 9 systemless magisk, xposed possible?

Dear fellow mixers,
I try to achieve the combination of:
MIUI 9 Android 7.0 either from EpicROM or xiaomi.eu
Installing Magisk systemless root
Installing Xposed for magisk
3 Questions:
Anyone achieved this already? If yes, can you tell us which version/release of MIUI, which variant of Magisk & Exposed did you use?
If someone didn't do it, but knows which combination of MIUI, Magisk and Xposed (especially which versions and mods) should work in theory, can you say so?
To my understanding this should help to *not* trip safetynet and allow us to run Snapchat?
My research so far:
According to this post, Unofficial Xposed 88.1 for MIUI9 SDK24 should work
According to this post, 88.1 works and xmiui also has a magisk zip
Another guide that seems to be written before 88.1 was released with MIUI 9 compatibility. So I'm confused which guide to follow, which combination of systemless xposed/magisk will work?
Edit:
I'll use my experiences and document them here to later create another how-to for systemless magisk/xposed on miui9 and another guide how to properly backup second space apps.
Second space backup:
Using Titanium Backup installed and started in First Space will only backup first space apps. Installing Titanium Backup in Second space also didn't work properly for me for some apps like LINE messenger.
Actually there are two (somethimes three) places that need to be backed up:
1. App APK (the installation files itself)
/data/app/<appname>
for both spaces, because they use the same app installation, as no user data is saved here, so it's in a single location, no matter how many android user accounts or MIUI spaces you have.
2. App's user data (like LINE Messenger database etc. normally not visible to you but important):
First space: /data/user/0/<appname>
Second space: /data/user/10/<appname>
This is unique for every user account (or miui space), here individual data is being saved, like two different LINE messenger accounts, or FB accounts.
3. User's accessible app data (where your app stores things that you produce in your apps and are visible to you when connecting your phone to your PC or checking your sdcard/internal storage):
First Space: /storage/emulated/0/<folder>
Second Space: /storage/emulated/10/<folder>
the folder names can be a mess here, whatsapp names their user data folder simply Whatsapp. Here they store your chat history DB, your downloaded pictures, videos and audio. Other apps can basically name their folder however they want and sometimes it's difficult to find out what folder your app stores files in. The app "Magix Pro Screen Recorder" as a fictional example could store your screen recordings in /storage/emulated/0/Movies/recordings/
To properly backup whatsapp in second space:
copy /storage/emulated/10/whatsapp folder to your PC
in new rom/phone create second space, then copy the backup form your PC to the same location as above in your new rom/phone
install whatsapp from play store, open it and it should recognize the backup and ask you to directly restore it
To properly backup a more complex app that uses all three folder types described above I take Naver LINE Messenger as an example:
backup /data/user/10/jp.naver.line.android/ *
backup /data/app/jp.naver.line.android-1 *
in new rom/phone create second space, then copy the backups to the same locations as above
don't open line app yet
install terminal emulator and delete the previous LINE settings by using the following commands:
su
sqlite3
/data/user/10/jp.naver.line.android/databases/naver_line
delete from setting;
.quit
if you don't have the sqlite3 binary, you can try to find it online for android (arm64 binary), paste it to your /bin folder and try again, or open the file on your computer with an sqlite explorer
if available, delete the following xml:
/data/user/10/jp.naver.line.android/shared_prefs/jp.naver.line.android.settings.xml
open the Line app and it will ask you to enter your user and password
Alternative method:
backup /data/user/10/jp.naver.line.android/
backup /data/app/jp.naver.line.android-1
in new rom/phone create second space, then copy the backups to the same locations as above
don't open line app yet
use an sqlite editor on your phone or on your pc to empty the following database:
/data/user/10/jp.naver.line.android/databases/naver_line
start line
My preferred method:
on old phone, install device id changer pro in second space and open it
note down device ID
backup /data/user/10/jp.naver.line.android/
backup /data/app/jp.naver.line.android-1
in new rom/phone create second space, then copy the backups to the same locations as above
don't open line app yet
install device id changer pro in second space and open it
enter the previously noted down device ID and set it
start line
* creating proper backups of the two LINE folders is a whole procedure again, we need to use tar gz to preserve permissions when copying and pasting:
- enable developer mode and usb debugging
- connect to pc
- install minimal adb & fastboot on your PC
- start cmd, execute:
adb shell
- accept popup on device, then type into cmd:
su
- accept supersu on device
- type:
cd /data/user/10/jp.naver.line.android
tar -cvpzf /storage/emulated/0/user-10-jp.naver.line.android.tar.gz .
cd /data/user/0/jp.naver.line.android
tar -cvpzf /storage/emulated/0/user-0-jp.naver.line.android.tar.gz .
cd /data/app/jp.naver.line.android-1
tar -cvpzf /storage/emulated/0/app-jp.naver.line.android-1.tar.gz .
- copy the 3 backup tar.gz files into your first space internal storage, and type:
cd /storage/emulated/0/
tar xpvzf user-10-jp.naver.line.android.tar.gz /data/user/10/
tar xpvzf user-0-jp.naver.line.android.tar.gz /data/user/0/
tar xpvzf app-jp.naver.line.android-1.tar.gz /data/app/

Reported Psyman version seems work and sometimes... latest build officialy released by Rovo works... then u need made a backup and try to flash a magisk version, lastest will have more chance to work because include all report from git...
And a lot of xposed module need to be updated....
cheers

I wasn't unable to make xposed 88.0 or 88.1 to work with the latest N MIUI 9 Epic rom using magisk. the only version that worked for me was V87 xposed but somehow gravity box didn't seen to work well when enabling setting and applying theme, that is gravity older version not the newest the newest version require xposed 88 and newer which didn't activated on N MIUI 9 Epic newest rom, exMIUI did work though

Ok, some news...
Lastest stable from Xiaomi.eu (9.1 - 7.0 - SDK 24) works with magisk and xposed... only need good version and right apk...
Cheers

[DEBLOAT] OOS 9.5.x De-bloat (Systemless+Automated+Easily Reversible) [Aug 28]

This script was made to 9.5.8 OP7 OxygenOS, some things can be different in future, so report if something is broken. Use at your own risk and feel free to experiment as this is a systemless mod.
First, the prerequisites:
1- Unlocked bootloader with Magisk and TWRP (you can use temporary TWRP if you please). If you don't know what is that, take a look at the XDA threads about it, it's easy. Please don't ask about "how to unlock bootloader" or "how to install Magisk".
2- Debloater (Terminal Emulator) Magisk module. Download it from Magisk Manager.
3- Any Terminal Emulator app.
4- import-debloat.txt config file. Download it here
5. Backup (yeah, this module doesn't change anything in /system and can be reverted at any time, but backups are always welcome)
6. Magisk Mount script. Download it from here
Magisk mount is needed to "reinstall" system apps by deleting the dummy folders from Magisk partition if something breaks.
If you have everything handy it should be a matter of few seconds to debloat.
Let's deal with useless system apps, temeletry, some ****ty apps. According from the @Tomatot- thread:
Tomatot- said:
-You'll get more privacy: I've removed Qualcomm telemetry, OnePlus telemetry as well as some Google Telemetry (but you can't expect too much as long as you use gapps)
-You'll get better battery life: less apps running in the background, less wakelocks, less services communicating with servers to send telemetry.
-You'll get better performance: for the same reasons. Don't expect a huge difference as our phone is very smooth already.
-The feeling of having a clean device. And this has no price.
Click to expand...
Click to collapse
Debloated apps list (It's the same Tomatot-'s Light app list):
Code:
AntHalService^=/system/app/AntHalService
AutoRegistration^=/system/app/AutoRegistration
BasicDreams^=/system/app/BasicDreams
BookmarkProvider^=/system/app/BookmarkProvider
BTtestmode^=/system/app/BTtestmode
PrintService^=/system/app/BuiltInPrintService
card^=/system/app/card
EasterEgg^=/system/app/EasterEgg
EgineeringMode^=/system/app/EngineeringMode
EngSpecialTest^=/system/app/EngSpecialTest
GooglePrint^=/system/app/GooglePrintRecommendationService
GoogleTTS^=/system/app/GoogleTTS
LogKitSdService^=/system/app/LogKitSdService
NetflixActivation^=/system/app/Netflix_Activation
NetflixStub^=/system/app/Netflix_Stub
NFCTestMode^=/system/app/NFCTestMode
OEMTCMA^=/system/app/oem_tcma
OEMAutoTestServer^=/system/app/OemAutoTestServer
OEMLogKit^=/system/app/OEMLogKit
OnePlusBugReport^=/system/app/OPBugReportLite
OnePlusCommonLogTool^=/system/app/OPCommonLogTool
OPSesAuthentication^=/system/app/OPSesAuthentication
PartnerBoorkmarksProvider^=/system/app/PartnerBookmarksProvider
PhotosOnline^=/system/app/PhotosOnline
PlayAutoInstallConfig^=/system/app/PlayAutoInstallConfig
QdcmFF^=/system/app/QdcmFF
RFTuner^=/system/app/RFTuner
SensorTestTool^=/system/app/SensorTestTool
SoterService^=/system/app/SoterService
Stk^=/system/app/Stk
Talkback^=/system/app/talkback
Traceur^=/system/app/Traceur
UIMRemoteClient^=/system/app/uimremoteclient
Video^=/system/app/Videos
WallpaperBackup^=/system/app/WallpaperBackup
WAPICertManage^=/system/app/WapiCertManage
WIFIRFTestApk^=/system/app/WifiRfTestApk
GoogleFeedback^=/system/priv-app/GoogleFeedback
OnePlusCellBroadcastReceiver^=/system/priv-app/OPCellBroadcastReceiver
Tag^=/system/priv-app/Tag
USBDrivers^=/system/etc/usb_drivers.iso
Reserve^=/system/reserve
RFToolkit^=/vendor/app/Rftoolkit
AmazonShittyApps^=/vendor/etc/apps
Account^=/system/app/Account
OPBackup^=/system/app/Backup
BackupRestoreRemoteService^=/system/app/BackupRestoreRemoteService
CarrierDefaultApp^=/system/app/CarrierDefaultApp
CTSShimPrebuilt^=/system/app/CtsShimPrebuilt
GoogleDrive^=/system/app/Drive
GoogleDuo^=/system/app/Duo
GooglePay^=/system/app/GooglePay
HTMLViewer^=/system/app/HTMLViewer
GooglePlayMusic^=/system/app/Music2
NVBackupUI^=/system/app/NVBackupUI
OnePlusPush^=/system/app/OPPush
YouTube^=/system/app/YouTube
BackupRestoreConfirmation^=/system/priv-app/BackupRestoreConfirmation
CallLogBackup^=/system/priv-app/CallLogBackup
CTSShimPrivPrebuilt^=/system/priv-app/CtsShimPrivPrebuilt
GoogleRestore^=/system/priv-app/GoogleRestore
GoogleBackupTransport^=/system/priv-app/GoogleBackupTransport
GoogleOneTimeInitializer^=/system/priv-app/GoogleOneTimeInitializer
ManagedPrivisioning^=/system/priv-app/ManagedProvisioning
OnePlusWizard^=/system/priv-app/OnePlusWizard
OPAppLocker^=/system/priv-app/OPAppLocker
OnePlusDeviceManager^=/system/priv-app/OPDeviceManager
OnePlusDeviceManagerProvider^=/system/priv-app/OPDeviceManagerProvider
SharedStorageBackup^=/system/priv-app/SharedStorageBackup
Let's start this!
1. Copy the import-debloat.txt config file to the folder /data/cache in the root. (you can copy it by a root explorer or reboot into recovery and copy it by TWRP file explorer)
2. Install the Debloater (Terminal Emulator) Magisk module using the Magisk Manager.
3. Open the terminal emulator app
> Type 'su' and press enter
> Grant root permissions
> Type debloat and press enter.
4. You will see the options to debloat in various categories which are self explanatory. As we have the config file which has a predefined app list to de-bloat stored in /data/cache folder in root already. Type 'i' which says import config and press enter 2 times.
5. Reboot 2 times and you're done most probably if nothing breaks.
Ta-dah! Fully debloated OOS. To keep the debloat after update the ROM, just reflash Magisk and you're fine. You don't need to do the procedure every update.
Read from here if something breaks (from @Sreekant)
If it breaks the system or causes boot-loop which shouldn't be the case as I'm using the OP7 9.5.8 and everything is fine, but well, **** happens. Don't worry! It's pretty easy to reinstall all of them in one click by TWRP.
Did you download the Magisk Mount script which I asked to earlier? If yes, just flash it with TWRP and the magisk will be mounted and accessible in TWRP file explorer. If you didn't download the script earlier, Just adb sideload it in recovery.
After mounting the Magisk in TWRP > Click on Advanced and go to file explorer.
Then delete the app folder of the system app you've uninstalled in /Magisk/terminal_debloater/system/app (/sbin/.core/img/terminal_debloater/system/app) or /Magisk/terminal_debloater/system/priv-app (/sbin/.core/img/terminal_debloater/system/priv-app) then that should undo it.
Click to expand...
Click to collapse
----------------------
Feel free to give any feedback about the script.
Special thanks to:
@Tomatot- (the apps list and some explanations are from his thread)
@Sreekantt (the thread base and original idea from debloat for Poco F1)
@topjohnwu (Magisk developer)
The Debloater (terminal) team

Hi, welcome and thanks for your work..as I understand , that is magisk module to use for debloat ? If you used script from Tomato, is it light debloat or which one. More info about that will be nice..thanks again

marko94 said:
Hi, welcome and thanks for your work..as I understand , that is magisk module to use for debloat ? If you used script from Tomato, is it light debloat or which one. More info about that will be nice..thanks again
Click to expand...
Click to collapse
I took the Light debloat from Tomatot and converted to Debloat (Terminal Emulator) module syntax. I will let it more clear in the thread.
I can convert the other two ones (Extreme and Invisible), specially Invisible would be fine to less experienced users.

Dan_Jacques said:
I took the Light debloat from Tomatot and converted to Debloat (Terminal Emulator) module syntax. I will let it more clear in the thread.
I can convert the other two ones (Extreme and Invisible), specially Invisible would be fine to less experienced users.
Click to expand...
Click to collapse
Yes, that will be cool.. also if we want edit some of script, for example we don't want debloat one app ,is it possible ? Thanks

marko94 said:
Yes, that will be cool.. also if we want edit some of script, for example we don't want debloat one app ,is it possible ? Thanks
Click to expand...
Click to collapse
Yes, just follow the syntax do add another system app to debloat:
Appname^=/system/path/to/appfolder
If you don't want to debloat some app, just erase the entry with the app that you don't want to remove.
You can find the system apps folder browsing /system/app and /system/priv-app. After every change to import-debloat.txt you have to run debloat and import again (to create the dummy empty folders.)
Edit it in Notepad++ to avoid format issues (at PC) or Quickedit (at cell phone).

Light it's the best choice.
Invisible it's to low and Extreme could be too hard on cleaning up. But it's up to you, of course.:good:

Dev any update for OB Q oos ? Thanks

Updated to Android 10 and doesnt appear to be working. Any debloat solutions for android 10 around?

Question Ive rooted my Pixel 7. I updated some apps on my P7. Now some apps are saying they wont work on Rooted devices. How to fix without unrooting?

I used these videos on Youtube to root my Pixel 7 several months ago.
Main reason was so I take advantage of the root version of APH Phone (Call recorder). Now I have a app called Roadie installed and updated and now its saying It will not work on Rooted or Jailbroken devices.
Is there any way to be able to use this with unrooting? Maybe some sort of root checking blocker?
Unrooting is a last resort.

See Post #2 - Unlocking Bootloader / Rooting / Updating | SafetyNet | ADB/Fastboot & Windows USB Drivers:
TL;DR - for the seasoned repeat users
SafetyNet

Magisk_Module_+_Uninstaller << Here are the needed Files!!!!
-Install Magisk.apk App from /sdcard/ and start Magisk App
-go to Settings and Enable "Zygisk" Option
-Setup the Denie-List with Apps you would hide Root (Especially Banking-Apps and other the dont start in Rooted-Device)
-Setup "Hide-Magisk-App" and choose a name 4 the new Shortcut
-Now The App starts again
-goto Modules and choose "Setup from Internal_storage" and Install "MagiskHidePropsConf-v6.1.2.zip" &
"safetynet-fix-v2.4.0.zip" without Restart the Device!!!
-After that reboot the Device
-Now Setup a Terminal_Emulator/Termux/etc.. from PlayStore!!!
-open your Terminal on Android and Type the following command
su
props
choose 1
choose f
choose your Device in next 2 Steps!!
(Samsung - 26 / Galaxy Tab A 10.1 2019 - 84)
choose y
choose y to reboot Device!!
-After Reboot open Settings and go to Apps
show all and choose
1# Google-PlayStore and Clear Stored-Datas/ Clear Cache
than goto
2# Google-PlayServices and Clear Stored-Datas/ Clear Cache
-Now you can Download "YASNAC SafetyNet Checker" from Playstore and can Check the Status!!!
-Finish!!!!!!

While changing your phone model through MagiskHidePropsConfig (MHPC) is a viable method, it really is a drastic one and should be one of the last resorts -- your phone gets identified by apps as non-rooted, but also Google services, other services, and other apps will wrongly identify your phone as what you "spoof" and they can try and apply incorrect data because it doesn't see the device as a Pixel 7, but what you spoof.
Especially since there are so many other hide root methods out there that one should try first that doesn't require such drastic methods (with more minimal side-effects) and work like 95% percent of the time; regular ol' Zygisk DenyList, Universal SafetyNet Fix (best for our device is Displax Mod 2.1), Shamiko (there are blacklists and whitelists (in this option) that one can employ in addition), Magisk Delta, HideMyApp (which had been suggested previously), and a few others.
I hope you keep this in mind...

surel
simplepinoi177 said:
While changing your phone model through MagiskHidePropsConfig (MHPC) is a viable method, it really is a drastic one and should be one of the last resorts -- your phone gets identified by apps as non-rooted, but also Google services, other services, and other apps will wrongly identify your phone as what you "spoof" and they can try and apply incorrect data because it doesn't see the device as a Pixel 7, but what you spoof.
Especially since there are so many other hide root methods out there that one should try first that doesn't require such drastic methods and work like 95% percent of the time; regular ol' Zygisk DenyList, Universal SafetyNet Fix (best for our device is Displax Mod 2.1), Shamiko (there are blacklists and whitelists (in this option) that one can employ in addition), Magisk Delta, HideMyApp (which had been suggested previously), and a few others.
I hope you keep this in mind...
Click to expand...
Click to collapse
i know now other Methods ok, but i must Test them out to say more!! In the past i was Satisfied with the shown Method, works fine on Magisk & Lygisk!!!