MIUI 9 systemless magisk, xposed possible? - Xiaomi Mi MIX Questions & Answers

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

Related

[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"

The exact framework for note 4 marshmallows

Hello, i had read many things at the forum but i still very confused. .please in a simple answer, which one is the correct and the download link. .please i can damage my cel.
Hgt45 said:
Hello, i had read many things at the forum but i still very confused. .please in a simple answer, which one is the correct and the download link. .please i can damage my cel.
Click to expand...
Click to collapse
Hello,
first i am not sure that u are in the right forum section.
About your demand, you haven't mention the CPU arch of your phone and have you reboot in custom recovery to flash the downloaded zip ?
Rom said:
Hello,
first i am not sure that u are in the right forum section.
About your demand, you haven't mention the CPU arch of your phone and have you reboot in custom recovery to flash the downloaded zip ?
Click to expand...
Click to collapse
Hello Lyon, hope everything happy... well, i don't know if its the right fórum,, here the info:
SYSTEM: SDK versión 6.0.1 ID:MMB29M OS name: Linux OS versión:3.10.40-9120850 Dalvik VM versión: 2.1.0
DEVICE: Model: SM-N910P Product: trltespr Board:APQ8084 Brand: Samsung Fingerprint: Samsung/trltespr/trltespr:6.0.1/MMB29M/N910PVPS4DQD1:user/reléase-keys
CPU: Name: ? Current freq.: 1958.4MHz Max freq.: 2649.6MHz Min freq.: 300MHz Cores: 4
Architecture: 7 BogoMIPS:38.40 Hardware: Qualcomm APQ8084 Revisión: 1
Serial #:0000000000000000
Memory
Total:2845492kbB Free:97792kB Inactive:896648kB
I haven't reboot in custom recovery to flash the downloaded zip XposedInstaller_by_dvdandroid.apk because of the warning its shows ( i send the pictures ).. i don't want to damage my note 4.. its the righ one ?
If you or anyone can help me to easy way to do it..
1- is,, XposedInstaller_by_dvdandroid.apk ? safe to run in custon recovery ? i Yes, how to, if No, which one to download it.
Regards.
H.
Hgt45 said:
Hello Lyon, hope everything happy... well, i don't know if its the right fórum,, here the info:
SYSTEM: SDK versión 6.0.1 ID:MMB29M OS name: Linux OS versión:3.10.40-9120850 Dalvik VM versión: 2.1.0
DEVICE: Model: SM-N910P Product: trltespr Board:APQ8084 Brand: Samsung Fingerprint: Samsung/trltespr/trltespr:6.0.1/MMB29M/N910PVPS4DQD1:user/reléase-keys
CPU: Name: ? Current freq.: 1958.4MHz Max freq.: 2649.6MHz Min freq.: 300MHz Cores: 4
Architecture: 7 BogoMIPS:38.40 Hardware: Qualcomm APQ8084 Revisión: 1
Serial #:0000000000000000
Memory
Total:2845492kbB Free:97792kB Inactive:896648kB
I haven't reboot in custom recovery to flash the downloaded zip XposedInstaller_by_dvdandroid.apk because of the warning its shows ( i send the pictures ).. i don't want to damage my note 4.. its the righ one ?
If you or anyone can help me to easy way to do it..
1- is,, XposedInstaller_by_dvdandroid.apk ? safe to run in custon recovery ? i Yes, how to, if No, which one to download it.
Regards.
H.
Click to expand...
Click to collapse
I don't see your CPU arch in your details, you are in the wrong forum section and on Android 5.0+ you must flash your zip in custom recovery.
Rom said:
I don't see your CPU arch in your details, you are in the wrong forum section and on Android 5.0+ you must flash your zip in custom recovery.
Click to expand...
Click to collapse
Thank you ROM,,for answer me, sorry I'm not an experienced tech... . and I'm afraid to flash zip in custom recovery mode if is not the right one,, in other words, I haven't did before, I just install framework in my S4 with no problems before. ..
I find out CPU arch: ARMv7-A Qualcomm APQ8084 ,,etc,, see attachment.
Please could you please tell me and help me ?....
If someone move these Thread to the right place. .
Sorry if I'm bothering
Regards
H.
Hgt45 said:
Thank you ROM,,for answer me, sorry I'm not an experienced tech... . and I'm afraid to flash zip in custom recovery mode if is not the right one,, in other words, I haven't did before, I just install framework in my S4 with no problems before. ..
I find out CPU arch: ARMv7-A Qualcomm APQ8084 ,,etc,, see attachment.
Please could you please tell me and help me ?....
If someone move these Thread to the right place. .
Sorry if I'm bothering
Regards
H.
Click to expand...
Click to collapse
Hello,
Apparently your CPU is an arm32 bits processor, so dl the last zip from this page:
http://dl-xda.xposed.info/framework/sdk23/arm/
And flash it via custom recovery.
After flash the zip, reboot in classic mode and check again by opening XPosed Installer app.
Rom said:
Hello,
Apparently your CPU is an arm32 bits processor, so dl the last zip from this page:
http://dl-xda.xposed.info/framework/sdk23/arm/
And flash it via custom recovery.
After flash the zip, reboot in classic mode and check again by opening XPosed Installer app.
Click to expand...
Click to collapse
Hello Rom, wishing your are very happy...
look the picture and see what is happening..
Overall Status: Congratulations! This device has root access!
Feedback
Stage 1 - Superuser App: Installed
Installed: SuperSU by Chainfire - version 2.82
Stage 2 - Superuser Binary Files: Installed
Standard System-less Location
Command: ls -l /su/bin/su
Result: -rwxr-xr-x root root 75352 2017-09-22 16:39 su
Version: 2.82:SUPERSU
Analysis: Root access IS correctly configured for this file! Executing this file can grant root access! Root user ownership is present and setuid attribute is not present.
Standard System Location
Command: ls -l /system/bin/su
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Standard System Location
Command: ls -l /system/xbin/su
Result: /system/xbin/su: No such file or directory
Analysis: File /system/xbin/su does not exist.
Alternative Location
Command: ls -l /sbin/su
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Command: ls -l /system/sbin/su
Result: /system/sbin/su: No such file or directory
Analysis: File /system/sbin/su does not exist.
Alternative Location
Command: ls -l /system/xbin/sudo
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Alternative Location
Command: ls -l /magisk/.core/bin/su
Result: /magisk/.core/bin/su: No such file or directory
Analysis: File /magisk/.core/bin/su does not exist.
Alternative System Environment Location
Command: ls -l /vendor/bin/su
Result: /vendor/bin/su: No such file or directory
Analysis: File /vendor/bin/su does not exist.
Alternative System Environment Location
Command: ls -l /su/xbin/su
Result: /su/xbin/su: No such file or directory
Analysis: File /su/xbin/su does not exist.
Stage 3 - Root User Account: Success
Root user id: uid=0(root)
Root group id: gid=0(root) groups=0(root)
Root SELinux context: context=u:r:init:s0
Optional - ADB Shell User
Status: Non-Root Shell User
Setting stored in /default.prop and configured as: ro.secure=1
Additional - Google SafetyNet Status
SafetyNet Status: False
Google evaluates hardware and software against Android specifications
Additional - System Environment PATH
System Environment PATH: /su/bin /sbin /vendor/bin /system/sbin /system/bin /su/xbin /system/xbin
Results provided for your SM-N910P - Android 6.0.1 device by Root Checker Pro version 6.1.5 from joeykrim in Google Play - http://goo.gl/NcnHn
thanks..
h.
Hgt45 said:
Hello Rom, wishing your are very happy...
look the picture and see what is happening..
Overall Status: Congratulations! This device has root access!
Feedback
Stage 1 - Superuser App: Installed
Installed: SuperSU by Chainfire - version 2.82
Stage 2 - Superuser Binary Files: Installed
Standard System-less Location
Command: ls -l /su/bin/su
Result: -rwxr-xr-x root root 75352 2017-09-22 16:39 su
Version: 2.82:SUPERSU
Analysis: Root access IS correctly configured for this file! Executing this file can grant root access! Root user ownership is present and setuid attribute is not present.
Standard System Location
Command: ls -l /system/bin/su
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Standard System Location
Command: ls -l /system/xbin/su
Result: /system/xbin/su: No such file or directory
Analysis: File /system/xbin/su does not exist.
Alternative Location
Command: ls -l /sbin/su
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Command: ls -l /system/sbin/su
Result: /system/sbin/su: No such file or directory
Analysis: File /system/sbin/su does not exist.
Alternative Location
Command: ls -l /system/xbin/sudo
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Alternative Location
Command: ls -l /magisk/.core/bin/su
Result: /magisk/.core/bin/su: No such file or directory
Analysis: File /magisk/.core/bin/su does not exist.
Alternative System Environment Location
Command: ls -l /vendor/bin/su
Result: /vendor/bin/su: No such file or directory
Analysis: File /vendor/bin/su does not exist.
Alternative System Environment Location
Command: ls -l /su/xbin/su
Result: /su/xbin/su: No such file or directory
Analysis: File /su/xbin/su does not exist.
Stage 3 - Root User Account: Success
Root user id: uid=0(root)
Root group id: gid=0(root) groups=0(root)
Root SELinux context: context=u:r:init:s0
Optional - ADB Shell User
Status: Non-Root Shell User
Setting stored in /default.prop and configured as: ro.secure=1
Additional - Google SafetyNet Status
SafetyNet Status: False
Google evaluates hardware and software against Android specifications
Additional - System Environment PATH
System Environment PATH: /su/bin /sbin /vendor/bin /system/sbin /system/bin /su/xbin /system/xbin
Results provided for your SM-N910P - Android 6.0.1 device by Root Checker Pro version 6.1.5 from joeykrim in Google Play - http://goo.gl/NcnHn
thanks..
h.
Click to expand...
Click to collapse
Hello,, any sugestion. ?
Have a great day.
H.
: (
Sent from my SM-N910P using Xposed Modules
Hgt45 said:
: (
Sent from my SM-N910P using Xposed Modules
Click to expand...
Click to collapse
Read fully, gather resources, install prerequisites on PC and study before proceeding AND only with confidence, considering all risks. Steps are generally in order but start with verifying reactivation lock is not enabled at Settings/Security while phone is booted.
I'd also recommend that you begin with fingerprints removed and no encryption. Make backups frequently in TWRP recovery beginning with suggested stock backup on ext sdcard as explained along the way.
Note: remember, before making any backups that fingerprints should be removed. Fingerprints do not restore from custom backups and don't work as expected even restored in a backup. Problematic!
Steps may contain redundant reminders and links because I've reiterated important things more than once.
Begin here when prerequisites, explained, are installed and gathered. The SuperSU zip and Wanam unofficial Xposed can be downloaded to phone's internal memory or retained for safe keeping on your micro sdcard. Just remember where downloaded to find when flashing in recovery. Always verify md5 of zips before extracting or flashing (as applies) where available. Sanity check to be safe.
USB driver will be installed on PC as executable; Odin will be extracted to Odin folder; your user files are good location to place this folder with extracted files; the exe file is an Odin application launcher executable with dependencies. The TWRP img.tar file will be downloaded to PC to install with Odin as explained along the way.
You can use the 3.1.1 Xposed Installer apk but your Xposed framework is going to be an unofficial one from Wanam for touchwiz lollipop and marshmallow.
Wanam also has an Xposed module suggested for touchwiz marshmallow: XTouchWiz (found with download search in Xposed Installer application when successful in installing all that I've given guidance for) . You might try that one first for SM-N910P; (other likened Xposed modification modules may not be as compatible as this Wanam module-- not too be confused with Wanam unofficial framework zip for recovery flashing to install Xposed framework). Note the differences.
https://forum.xda-developers.com/showpost.php?p=62377731&postcount=1
The file you'll eventually find is Wanam unofficial Xposed framework for SDK 23 arm.
https://www.androidfilehost.com/?fid=529152257862685344
I don't believe you're rooted. It also appears you're trying to flash custom zips with stock recovery? Are you familiar with TWRP recovery by Team Win? You'll need that to backup your ROM and flash custom zips like SuperSU zip and unofficial Xposed framework by Wanam. (Bootloader is already unlocked on SM-N910P; please make sure that is your model number because that's what I'm recommending files for).
https://dl.twrp.me/trltespr/twrp-3.0.2-0-trltespr.img.tar
The file above is latest custom recovery for SM-N910P or any Qualcomm Note 4. Recently, the TWRP recovery became unified by processor but common mistakes users of Qualcomm Note 4 make is not knowing which to flash and what's required for Odin install and how to properly flash in Odin. What's Odin? It's a utility made for flashing custom tar files and stock tar updates for rooted users. There are many updates and untrusted sources (beware of adware or malware!) but basically it's installed on a PC as an executable file. But you'll also need the official USB driver to help the PC discover your phone when placed in download mode to flashed with Odin. What will you flash? The tar.img file above.
To get started download USB driver and Odin. Install USB on PC with its exe file.
http://org.downloadcenter.samsung.c...G_USB_Driver_for_Mobile_Phones_v1.5.45.00.exe
Latest Odin trusted download is below. Unzip or extract contents in a folder named Odin
https://forum.xda-developers.com/showpost.php?p=51767811&postcount=1
If you have Samsung Smart Switch or Samsung KIES installed on PC, you need to ensure all process and apps sessions are closed before using Odin. Also note that launching Odin exe on Windows 8 and below requires to launch with administrative permission (right click the executable file and select launch with administrative permission). Windows 10 does not require administrative mode at launch.
Are you familiar with launching download mode? Power Off, pull battery after charging to at least 80% (general rules for flashing in Odin download mode- never use a "boot to download mode" shortcut from system booted state; actually, that necessity applies to flashing full stock tar but remember that; make it a practice is my suggestion to avoid catheter csc errors with full stock tar flashes with Odin-- that's how rooted users update). Reinstall battery and press hold volume down, home and power button until it vibrates or launches. Read the prompt on phone* this is important because flashes are always a risk. Launch Odin on PC and goto options tab and uncheck auto restart and return to to log tab. While watching "COM" field with USB cable connected (must be data USB type cable- original Samsung Note 4 is recommended), follow prompt* I believe it's volume up to continue. Read your phone's state and see that COM field populated with your device (likely a port or device number unique to your PC where phone USB cable is connected or your phone* it only populates when you accept/commit download mode with phone and PC connected via USB with data support). Do not proceed until verifying your phone display shows Odin fast mode and that reactivation lock is disabled or inactive. If that is a go, load the img.tar in AP slot. You still see the file name fill that slot when you navigate to it on your PC and select it. The install button will be at bottom of Odin screen, I believe. Begin when all is verified.
If all above is a go, just remember that you're looking for a green field that fills and says SUCCESS! Happens quickly and stops (if you setup as directed). Wait until you see Odin log file state that "1 passed, 0 failed". Give it a minute to declare "disconnected" or just wait one minute before proceeding. Since auto reboot was unchecked, you'll have to remove USB and pull battery manually (wait at least 30 seconds after pulling battery before reinstalling). And close Odin after each flash session; you're actually done with the PC for this directive. IMPORTANT: If you fail to go directly to recovery mode after reinstalling the battery, stock recovery will restore itself and you'll have to do the Odin flash of TWRP again. To do this, press and hold volume up, home and power simultaneously until it vibrates; TWRP recovery should launch. You're now ready to backup your stock un-rooted ROM. I recommend backing up to ext SD Card (micro sdcard).
To familiar yourself with TWRP install and use, there's a support thread for that. There's also an official TWRP recovery application in Google Play. Search it there. Note the thread hasn't reflected latest update or developer notes since the official TWRP recovery app launched in Google Play but many unique questions are answered there. Ignore any suggestions to use an older TWRP version or any specific update or Android version. Suggestions like this change over time and may not be relevant at present.
https://forum.xda-developers.com/no...ility-twrp-2-8-1-0-teamwin-t2915591?nocache=1
After backup, I'd recommend installing SuperSU zip with TWRP recovery.
https://forum.xda-developers.com/showpost.php?p=68475511&postcount=1
Make a rooted TWRP backup before applying Xposed and label accordingly, saving to ext sdcard. You can edit the generalized title of backup as you prefer. Rather than the extended fine stamp, shorten to include your description.
Then you can install the Xposed Installer apk (install by sideload method not recovery- you may have already done this) and Wanam unofficial Xposed zip. Follow this thread; I've already linked the zip above but usually you're looking for the highlighted download link and browse to marshmallow SDK 23 arm.
https://forum.xda-developers.com/showpost.php?p=62377731&postcount=1
All threads referenced are your support threads for files referenced. Understand before flashing that there risks you assume yourself. Never a guarantee that you'll be successful or the inevitable happens from followed instructions offered by me or anyone else I've linked you to.
Again, make sure you haven't set reactivation lock in phone's Settings/Security tab before beginning and verify the phone display and Odin states before flashing. Not following could result in phone activating a factory reset protection mode. Not sharing to warning while flashing TWRP recovery may only refuse to flash due to reactivation lock enabled and may state such when using recent Odin releases. But that message may be only abbreviated and cause question of its intent.
Only flash when familiar and confident with instructions. Better to ask than risk misunderstood direction. There may recent demo videos to follow but avoid using suggested older files, noting date of your video; they're not necessarily scripture to live by. Best to use recent files and direction because unlike a certain BOOK, updates and time changes with Samsung, touchwiz and Note 4 development.
There's also some custom ROMs to consider if you follow the road map of XDA links for Sprint Note 4 at top of thread: Note 4 development, rather than Note 4 original development where TWRP support thread. Updates for TWRP can be found in the official TWRP recovery app but I've linked you latest recommended release for flashing in Odin.
Questions? Ask away or read the support threads to familiarize yourself. Many questions are answered there.
Sent from my SM-N920P using Tapatalk
---------- Post added at 10:28 PM ---------- Previous post was at 09:59 PM ----------
Final result on my SM-N910P Note 4. See screenshots.
I'm using a couple of non Xposed modules to compliment modification outside of Xposed. Since compatible modules and applications are sometimes limited, I'll include those for clarification. Both linked below by Google Play link. Strictly optional. Both contain back to kill foreground app shortcuts but may be premium only features- I'm not sure on both or whether one or the other would be ideal. I sort of discovered these apps by recommendation and haven't tried eliminating one or the other.
https://play.google.com/store/apps/details?id=flar2.homebutton
https://play.google.com/store/apps/details?id=com.goodmooddroid.gesturecontrol
Sent from my SM-N920P using Tapatalk
samep said:
Read fully, gather resources, install prerequisites on PC and study before proceeding AND only with confidence, considering all risks. Steps are generally in order but start with verifying reactivation lock is not enabled at Settings/Security while phone is booted.
I'd also recommend that you begin with fingerprints removed and no encryption. Make backups frequently in TWRP recovery beginning with suggested stock backup on ext sdcard as explained along the way.
Note: remember, before making any backups that fingerprints should be removed. Fingerprints do not restore from custom backups and don't work as expected even restored in a backup. Problematic!
Steps may contain redundant reminders and links because I've reiterated important things more than once.
Begin here when prerequisites, explained, are installed and gathered. The SuperSU zip and Wanam unofficial Xposed can be downloaded to phone's internal memory or retained for safe keeping on your micro sdcard. Just remember where downloaded to find when flashing in recovery. Always verify md5 of zips before extracting or flashing (as applies) where available. Sanity check to be safe.
USB driver will be installed on PC as executable; Odin will be extracted to Odin folder; your user files are good location to place this folder with extracted files; the exe file is an Odin application launcher executable with dependencies. The TWRP img.tar file will be downloaded to PC to install with Odin as explained along the way.
You can use the 3.1.1 Xposed Installer apk but your Xposed framework is going to be an unofficial one from Wanam for touchwiz lollipop and marshmallow.
Wanam also has an Xposed module suggested for touchwiz marshmallow: XTouchWiz (found with download search in Xposed Installer application when successful in installing all that I've given guidance for) . You might try that one first for SM-N910P; (other likened Xposed modification modules may not be as compatible as this Wanam module-- not too be confused with Wanam unofficial framework zip for recovery flashing to install Xposed framework). Note the differences.
https://forum.xda-developers.com/showpost.php?p=62377731&postcount=1
The file you'll eventually find is Wanam unofficial Xposed framework for SDK 23 arm.
https://www.androidfilehost.com/?fid=529152257862685344
I don't believe you're rooted. It also appears you're trying to flash custom zips with stock recovery? Are you familiar with TWRP recovery by Team Win? You'll need that to backup your ROM and flash custom zips like SuperSU zip and unofficial Xposed framework by Wanam. (Bootloader is already unlocked on SM-N910P; please make sure that is your model number because that's what I'm recommending files for).
https://dl.twrp.me/trltespr/twrp-3.0.2-0-trltespr.img.tar
The file above is latest custom recovery for SM-N910P or any Qualcomm Note 4. Recently, the TWRP recovery became unified by processor but common mistakes users of Qualcomm Note 4 make is not knowing which to flash and what's required for Odin install and how to properly flash in Odin. What's Odin? It's a utility made for flashing custom tar files and stock tar updates for rooted users. There are many updates and untrusted sources (beware of adware or malware!) but basically it's installed on a PC as an executable file. But you'll also need the official USB driver to help the PC discover your phone when placed in download mode to flashed with Odin. What will you flash? The tar.img file above.
To get started download USB driver and Odin. Install USB on PC with its exe file.
http://org.downloadcenter.samsung.c...G_USB_Driver_for_Mobile_Phones_v1.5.45.00.exe
Latest Odin trusted download is below. Unzip or extract contents in a folder named Odin
https://forum.xda-developers.com/showpost.php?p=51767811&postcount=1
If you have Samsung Smart Switch or Samsung KIES installed on PC, you need to ensure all process and apps sessions are closed before using Odin. Also note that launching Odin exe on Windows 8 and below requires to launch with administrative permission (right click the executable file and select launch with administrative permission). Windows 10 does not require administrative mode at launch.
Are you familiar with launching download mode? Power Off, pull battery after charging to at least 80% (general rules for flashing in Odin download mode- never use a "boot to download mode" shortcut from system booted state; actually, that necessity applies to flashing full stock tar but remember that; make it a practice is my suggestion to avoid catheter csc errors with full stock tar flashes with Odin-- that's how rooted users update). Reinstall battery and press hold volume down, home and power button until it vibrates or launches. Read the prompt on phone* this is important because flashes are always a risk. Launch Odin on PC and goto options tab and uncheck auto restart and return to to log tab. While watching "COM" field with USB cable connected (must be data USB type cable- original Samsung Note 4 is recommended), follow prompt* I believe it's volume up to continue. Read your phone's state and see that COM field populated with your device (likely a port or device number unique to your PC where phone USB cable is connected or your phone* it only populates when you accept/commit download mode with phone and PC connected via USB with data support). Do not proceed until verifying your phone display shows Odin fast mode and that reactivation lock is disabled or inactive. If that is a go, load the img.tar in AP slot. You still see the file name fill that slot when you navigate to it on your PC and select it. The install button will be at bottom of Odin screen, I believe. Begin when all is verified.
If all above is a go, just remember that you're looking for a green field that fills and says SUCCESS! Happens quickly and stops (if you setup as directed). Wait until you see Odin log file state that "1 passed, 0 failed". Give it a minute to declare "disconnected" or just wait one minute before proceeding. Since auto reboot was unchecked, you'll have to remove USB and pull battery manually (wait at least 30 seconds after pulling battery before reinstalling). And close Odin after each flash session; you're actually done with the PC for this directive. IMPORTANT: If you fail to go directly to recovery mode after reinstalling the battery, stock recovery will restore itself and you'll have to do the Odin flash of TWRP again. To do this, press and hold volume up, home and power simultaneously until it vibrates; TWRP recovery should launch. You're now ready to backup your stock un-rooted ROM. I recommend backing up to ext SD Card (micro sdcard).
To familiar yourself with TWRP install and use, there's a support thread for that. There's also an official TWRP recovery application in Google Play. Search it there. Note the thread hasn't reflected latest update or developer notes since the official TWRP recovery app launched in Google Play but many unique questions are answered there. Ignore any suggestions to use an older TWRP version or any specific update or Android version. Suggestions like this change over time and may not be relevant at present.
https://forum.xda-developers.com/no...ility-twrp-2-8-1-0-teamwin-t2915591?nocache=1
After backup, I'd recommend installing SuperSU zip with TWRP recovery.
https://forum.xda-developers.com/showpost.php?p=68475511&postcount=1
Make a rooted TWRP backup before applying Xposed and label accordingly, saving to ext sdcard. You can edit the generalized title of backup as you prefer. Rather than the extended fine stamp, shorten to include your description.
Then you can install the Xposed Installer apk (install by sideload method not recovery- you may have already done this) and Wanam unofficial Xposed zip. Follow this thread; I've already linked the zip above but usually you're looking for the highlighted download link and browse to marshmallow SDK 23 arm.
https://forum.xda-developers.com/showpost.php?p=62377731&postcount=1
All threads referenced are your support threads for files referenced. Understand before flashing that there risks you assume yourself. Never a guarantee that you'll be successful or the inevitable happens from followed instructions offered by me or anyone else I've linked you to.
Again, make sure you haven't set reactivation lock in phone's Settings/Security tab before beginning and verify the phone display and Odin states before flashing. Not following could result in phone activating a factory reset protection mode. Not sharing to warning while flashing TWRP recovery may only refuse to flash due to reactivation lock enabled and may state such when using recent Odin releases. But that message may be only abbreviated and cause question of its intent.
Only flash when familiar and confident with instructions. Better to ask than risk misunderstood direction. There may recent demo videos to follow but avoid using suggested older files, noting date of your video; they're not necessarily scripture to live by. Best to use recent files and direction because unlike a certain BOOK, updates and time changes with Samsung, touchwiz and Note 4 development.
There's also some custom ROMs to consider if you follow the road map of XDA links for Sprint Note 4 at top of thread: Note 4 development, rather than Note 4 original development where TWRP support thread. Updates for TWRP can be found in the official TWRP recovery app but I've linked you latest recommended release for flashing in Odin.
Questions? Ask away or read the support threads to familiarize yourself. Many questions are answered there.
Sent from my SM-N920P using Tapatalk
---------- Post added at 10:28 PM ---------- Previous post was at 09:59 PM ----------
Final result on my SM-N910P Note 4. See screenshots.
I'm using a couple of non Xposed modules to compliment modification outside of Xposed. Since compatible modules and applications are sometimes limited, I'll include those for clarification. Both linked below by Google Play link. Strictly optional. Both contain back to kill foreground app shortcuts but may be premium only features- I'm not sure on both or whether one or the other would be ideal. I sort of discovered these apps by recommendation and haven't tried eliminating one or the other.
https://play.google.com/store/apps/details?id=flar2.homebutton
https://play.google.com/store/apps/details?id=com.goodmooddroid.gesturecontrol
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
Hello Samep, I'm impressed and thankful on how you describe everything, I know its takes lon time and dedication to write,, THANKS A LOT, I know these will be the most comprehensive for many many users... I will try to do what you explained. ..
Also thanks to Rom and others for your suggestions and help.
Have a great weekend.. all the best wishes for all.
Regards
Herm.
slm note 4
note 4 I am using n910c 6.0.1. I have installed the device rooted twrp but I do not know which xposed i will install. I write armv7l in the kernel.
I do not know how many sdk I have to help you rejoice

[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?

Magisk Module Systemless Debloater

Magisk Module Systemless Debloater
Download:
GitHub - zgfg/SystemlessDebloater: Select and systemlessly debloat preinstalled system apps. Supporting up to System As Root (SAR), Dynamic partitions and Android 13. Module must be installed through Magisk app, not TWRP
Select and systemlessly debloat preinstalled system apps. Supporting up to System As Root (SAR), Dynamic partitions and Android 13. Module must be installed through Magisk app, not TWRP - GitHub - ...
github.com
GitHub - Magisk-Modules-Alt-Repo/SystemlessDebloater: Select and systemlessly debloat preinstalled system apps. Supporting up to System As Root (SAR), Dynamic partitions and Android 13. Module must be installed through Magisk app, not TWRP
Select and systemlessly debloat preinstalled system apps. Supporting up to System As Root (SAR), Dynamic partitions and Android 13. Module must be installed through Magisk app, not TWRP - GitHub - ...
github.com
Wiki pages by @ipdev:
ConfigScript
Guide for the Systemless Debloater Module. Contribute to mModule/guide_sDebloater development by creating an account on GitHub.
github.com
with his examples of apps that can be debloated (Android, Google, Oppo, Samsung, Xiaomi, LineageOS):
CommunityList
Guide for the Systemless Debloater Module. Contribute to mModule/guide_sDebloater development by creating an account on GitHub.
github.com
*** Yet another System(less) debloater, how and why?
- Systemless means that all changes made are active only when Magisk is loaded and module is enabled.
For OTA or anything, just disable the module (or boot without Magisk) and your system partitions are no more affected
- For Android up to 9 and/or 10 (depending on devices), system partitions were read-write, hence hard-debloating by use of eg TWRP, Titanium, etc (to delete the pre-installed system apps) was possible
This is no more possible for the phones released with Android 10 and higher.
System (System As Root, Dynamical partitions) becomes read-only on the file-system level and stock apps could be debloated (the same holds for any changes on the system partitions) only by the systemless approach - by use of Magisk to dynamically overlay the required changes at boot time
Hence, this module also uses the Magisk REPLACE mechanism and dynamical mounting through the module's service.sh script
- The module debloates only (stock) apps pre-installed to the system partitions, traditionally named as /system, /system-ext, /product, /vendor and /apex; plus additionally on A12 and A13 devices, variably named system partitions like /india, /my_bigball, etc
Hence sorry, to debloat user apps installed to /data, please use the other methods (first of all, just simply uninstall them or at least uninstall their updates)
- Originally I started development with Xiaomi Mi 9T (MIUI 10-12.5, Android 10-12) and later continued with Xiaomi 11 Lite 5G NE (MIUI 12-13, Android 11-12). However, the module relies on the common Magisk overlay mechanism and the list of apps to be 'debloated' is configurable hence there are many users who successfully use this module on the various other devices (like Pixel, Samsung, One Plus, etc.), with the stock or custom ROMs, and with up to Android 13
- Original, default list coming when the module is installed will be empty - user must define then himself which apps should be debloated, depending on his device, ROM and preferences
To (re)configure the list of apps for debloating, simply edit the (textual) /Download/SystemlessDebloater.cfg config file on Internal memory.
Module automatically installs the config file with instructions inside but with the empty list
(Re)configure your list of system apps you want to debloat, reinstall the module (always through the Magisk Manager, not TWRP) and reboot - to take your changes in effect
You only need to provide the proper names (not package names) for the preinstalled system apps, the module will find their exact System paths
- However, the user bears the risks and responsibility himself (device may no more boot when certain system apps are removed/debloated) but the Troubleshooting section below provides instructions how to recover, even from the bootloop cases
Nevertheless, whenever you want to 'debloat' some service or app you are not familiar with, please google first to find what that app is really about and is it generally safe to be debloated (on your but also on the other phones and even by other methods, it doesn't matter)
Don't be afraid of the module and debloating, but be cautious what are you going to debloat
*** Installation
- Download the latest module from GitHub - scroll down, open Assets and find the latest v1.5.3 zip:
https://github.com/zgfg/SystemlessDebloater/releases/tag/153
- In Magisk app (manage), open Modules tab and take Install from storage, navigate to the downloaded SystemlessDebloater.zip (as is, do not unzip)
Read what Magisk prints while installing and find the module's log in /Download/SystemlessDebloater.log file on Internal memory
To finish the installation (it applies to all Magisk modules), reboot the phone
- First time the module will not debloat anything - it will just create the input/config file /Download/SystemlessDebloater.cfg on Internal memory
Open that config file, read the instructions in the file and fill your own list of app names for debloating - look at the commented examples you will find in that config file
- Save the config file, reinstall the module and reboot.
Inspect the log and consult the Troubleshooting section below if needed
- To find what system apps you have on your phone and what are their exact names, scroll down through the SystemlessDebloater.log to the "System apps, not debloated" section
Find e.g. a line:
/system/app/Email (com.android.email)
Then copy/add just the Email name (supposed that you want to debloat the built-in Email app) into the SystemlessDebloater.cfg config file
Repeat for the other apps you want to debloat. Then reinstall the module (only on the reinstallation, module processes the config file) and reboot
Fine tune your list of apps for debloating but every time reinstall the module and reboot
- Last but not the least: Once debloated, apps can no more be found (until you reconfigure, disable or uninstall the debloater) under the Settings / Apps
Hence, if you want to delete their cache or data, do Clear cache/data before debloating the apps
Moreover, before trying to debloat any app, look first if you could simply Uninstall that app (ie, if it was a user and not the system app) from Settings / Apps
If Uninstall is not available for that app, try to Uninstall updates: updates are also installed to Data while SystemlessDebloater 'debloats' only from the System - hence the app's update on Data may still remain there
*** Troubleshooting
- What if I eg have configured the app EMail to debloat, but the app is still present?
Check if you have missed to perform Uninstall / Uninstall updates from Settings, Apps - perform, reboot and test again
Check if you have miss-spelled the application name - correct in the config file SystemlessDebloater.cfg, save, reinstall the module and reboot
App names are cases sensitive - eg, the correct name might be Email, not EMail
- To help yourself, use eg Package Manager app (from Playstore) where you can search for all the apps/services, find their exact names and installation paths (to see are them System or User apps)
- What if I change my mind and I want to un-debloat and use Email, but to debloat now eg, Chrome browser?
No problem, reconfigure the list in SystemlessDebloater.cfg, save, reinstall the module and reboot
- What if after a week or so, I realize that some functionalities on the phone were affected?
Sorry, you had decided to debloat the 'wrong' apps/services
Google about which app(s) are safe to debloat or not, reconfigure your list in the config file, reinstall the module and reboot
Or disable the module and reboot, to figure out was the problem really due to debloating
- Oops, what if I have a bootloop (phone does no more boot since the 'wrong' apps were debloated)?
If you have TWRP with the read/write access to Data, navigate to /data/adb/modules/SystemlessDebloater and by using Advanced / File explorer from TWRP, create a dummy file named disable (without extension) in that folder
Reboot and Magisk will boot but with the debloater disabled - hence, all the previously debloated apps will be un-debloated now (to see if debloating was really responsible for the bootloop)
Instead of dummy file named disable, put the remove dummy file to trigger Magisk to uninstall that module on the next reboot (all that applies to any module possibly causing your bootloops)
If the proper TWRP is not available for your device and ROM, boot to the Android Safe Mode - google for a key-combo to boot in, for my Xiaomi it takes (re)booting with Vol+ and Vol+ pressed simultaneously
Don't do anything in Android Safe mode but reboot then to 'normal' mode - Magisk will boot now with all the modules disabled (this method does not work for Magisk v20.4 or earlier)
You will have to re-enable MagiskHide/DenyList (don't worry, your list of apps to hide the Magisk from was not lost), re-enable the other modules, correct SystemlessDebloater.cfg, reinstall debloater and reboot
There is also a third method (adb wait-for-device shell magisk --remove-modules), but search yourself and read about from the Wiki Documentation on the Magisk GitHub page
*** Enough for the theory, install now and practice debloating
IMPORTANT
Since the version v1.5.1, SystemlessDebloater module supports a new SystemlessDebloater.cfg config file - thanks to @ipdev
Update will create the new config file and transfer your DebloatList
Please delete then your old SystemlessDebloaterList.sh input file and read and use the new config file instead
---
For more info about the SystemlessDebloater.cfg config file, please see: Wiki pages from @ipdev:
ConfigScript
Guide for the Systemless Debloater Module. Contribute to mModule/guide_sDebloater development by creating an account on GitHub.
github.com
and his examples what apps can be debloated (Android, Google, Oppo, Samsung, Xiaomi, LineageOS):
CommunityList
Guide for the Systemless Debloater Module. Contribute to mModule/guide_sDebloater development by creating an account on GitHub.
github.com
On my Xiaomi Mi 9T, eea Stable QFJEUXM 12.0.2 I safely debloat the following apps:
Code:
DebloatList="
AnalyticsCore
AntHalService
BasicDreams
BookmarkProvider
CatchLog
Chrome
CneApp
EasterEgg
facebook-appmanager
facebook-installer
facebook-services
FileExplorer_old
GlobalFashiongallery
GlobalMinusScreen
Gmail2
GoogleFeedback
GooglePartnerSetup
HybridAccessory
HybridPlatform
IdMipay
InMipay
Joyose
MiBrowserGlobal
MiBrowserGlobalVendor
MiCreditInStub
MiDrop
MiLinkService2
MiPicks
MiPlayClient
MiRcs
MiRecycle
MiService
MiuiBrowserGlobal
MiuiBugReport
MiuiDaemon
MSA-Global
Netflix_activation
Notes
PartnerBookmarksProvider
PaymentService
PhotoTable
Stk
TouchAssistant
Traceur
Turbo
uceShimService
Velvet
VsimCore
wps_lite
YellowPage
Zman"
E.g., I debloat YouTube and install Vanced YT root.
Similarly, I debloat GMail, Wellbeing, Netflix, Facebook, Turbo, etc - inspect and exclude from the list those apps you want to keep
Also, DebloatList I used for Mi 9T but Xiaomi.eu weekly 20.9.17 (MIUI 12, Android 10):
Code:
DebloatList="
AndroidAutoStub
AntHalService
BookmarkProvider
Browser
BTProductionLineTool
Calculator
CatchLog
CneApp
EasterEgg
Email
GoogleFeedback
GooglePartnerSetup
Health
Joyose
Lens
MiMover
MiPlayClient
MiRecycle
MiService
MiuiBugReport
MiuiDaemon
Notes
PaymentService
Stk
TouchAssistant
Traceur
uceShimService
Velvet
VsimCore
WebViewGoogle
wps_lite"
and for Xiaomi.eu Stable 12.0.6:
Code:
DebloatList="
AndroidAutoStub
AntHalService
BookmarkProvider
Browser
BTProductionLineTool
Calculator
CatchLog
CneApp
EasterEgg
Email
GoogleFeedback
GooglePartnerSetup
Health
Joyose
Lens
MiMover
MiPlayClient
MiRecycle
MiService
MiuiBugReport
MiuiDaemon
Notes
PaymentService
Stk
TouchAssistant
Traceur
uceShimService
Velvet
VsimCore
WebViewGoogle
wps-lite"
You may exclude e.g., Calculator,Email, Health or Lens, if you want to use them.
You can expect most of these apps also on the other MIUI firmwares. Installation folders on System may vary, but module will find their paths
EDIT:
SystemDebloaterList.sh and DebloatList were used in the module versions v1.5.0 and earlier, since v1.5.1 the module uses SystemDebloater.cfg
Thanks a lot to @ipdev for discussing and sharing ideas, encouraging and for successful testing on Xiaomi Poco F2 (debloater found most of the same MIUI apps as above) and OnePlus 5T
Also, thanks for your successful test on Pixel 3aXL with Android 11:
ipdev said:
Works on Pixel 3aXL. (Stock Android 11. Magisk canary.)
Attached the SystemlessDebloater.log from 3aXL.
And the SystemlessDebloaterList.sh I use for testing. (remove the .txt)
Click to expand...
Click to collapse
Reserved
Over the weekend when I have time to fix any potential bricking or boot loops, I'm going to try this on my A/B device (One Plus 7Pro, GM1917, OOS 10.3.5) ... unless before then anyone indicates that this is not even likely to work on my phone.
If I end up doing this, I'll report my results.
.​
HippoMan said:
Over the weekend when I have time to fix any potential bricking or boot loops, I'm going to try this on my A/B device (One Plus 7Pro, GM1917, OOS 10.3.5) ... unless before then anyone indicates that this is not even likely to work on my phone.
If I end up doing this, I'll report my results.
.​
Click to expand...
Click to collapse
It does not matter if it system-as-root or a slot device.
By time modules are run, system paths are set.
The active slot partition is running, and (if needed) switch root has happened.
Root directory is set to / and system directory is set to /system
curious about OxygenOS, do not run it very much so I am not sure what should/could be removed.
Cheers.
PS.
Works on Pixel 3aXL. (Stock Android 11. Magisk canary.)
Attached the SystemlessDebloater.log from 3aXL.
And the SystemlessDebloaterList.sh I use for testing. (remove the .txt)
Quick edit.
Since the back-side move for xda is still going, there are some errors while in transition.
Since attachment is not working at the moment. GoogleDrive - Link
ipdev said:
It does not matter if it system-as-root or a slot device.
By time modules are run, system paths are set.
The active slot partition is running, and (if needed) switch root has happened.
Root directory is set to / and system directory is set to /system
curious about OxygenOS, do not run it very much so I am not sure what should/could be removed.
Cheers.
PS.
Works on Pixel 3aXL. (Stock Android 11. Magisk canary.)
Attached the SystemlessDebloater.log from 3aXL.
And the SystemlessDebloaterList.sh I use for testing. (remove the .txt)
Click to expand...
Click to collapse
OxygenOS isn't as bad, bloat-wise, as some other OS's, such as what comes with Samsung. But there are still things that I don't want, such as the OnePlus camera and a few other items.
I'll report back here after I try this.
.​
ipdev said:
It does not matter if it system-as-root or a slot device.
By time modules are run, system paths are set.
The active slot partition is running, and (if needed) switch root has happened.
Root directory is set to / and system directory is set to /system
curious about OxygenOS, do not run it very much so I am not sure what should/could be removed.
Cheers.
PS.
Works on Pixel 3aXL. (Stock Android 11. Magisk canary.)
Attached the SystemlessDebloater.log from 3aXL.
And the SystemlessDebloaterList.sh I use for testing. (remove the .txt)
Click to expand...
Click to collapse
Thank you for testing on A11.
Log cannot be downloaded, 404?
zgfg said:
Thank you for testing on A11.
Log cannot be downloaded, 404?
Click to expand...
Click to collapse
Looks like some more hiccups on xda back-side again.
Will be nice once the transition is complete, xda will be fast and stable again. :fingers-crossed:
Updated my prior post with a gDrive Link.
If you look at the log, you will notice chrome is not debloated.
The stub is debloated, Chrome (Think it is in product/app) is a gzip version of the Chrome apk.
Chrome is automatically installed into /data/app/HashStringOrSomething/com.android.chrome-HashStringOrSomething/Chome.apk
I have not taken time to look into that change.
Cheers.
ipdev said:
Looks like some more hiccups on xda back-side again.
Will be nice once the transition is complete, xda will be fast and stable again. :fingers-crossed:
Updated my prior post with a gDrive Link.
If you look at the log, you will notice chrome is not debloated.
The stub is debloated, Chrome (Think it is in product/app) is a gzip version of the Chrome apk.
Chrome is automatically installed into /data/app/HashStringOrSomething/com.android.chrome-HashStringOrSomething/Chome.apk
I have not taken time to look into that change.
Cheers.
Click to expand...
Click to collapse
Interesting - what happens when you debloat Chrome-Stub from Product and leave Chrome on Data, does it still run?
Btw, I do use Chrome (because of the integrated translator, making me easy to sometimes read worldwide forums if needed) and I didn't want to debloat originally. However, my preinstalled version on Product was not the latest, and Google Play was offering me to update, but updating Chrome was always failing.
I downloaded the apk from ApkMirror but installation had also failed
Then I debloated (at that time, prior to this debloater I used to manually create my system folder given to Magisk to overlay, and with dummy apk instead of with .replace file) and only then I was able to install Chrome apk (ofc to Data) and since then, to regularly update it through Playstore
One more thing. I've found some people claiming that Chrome breaks to run if Playstore shows Device is not certified.
But back in the spring when Google started to play with enforcing CTS Profile Hardware attest, and prior than @Displax invented ro.product.model spoofing (to force Basic attest and to pass CTS/SafetyNet, to get Device certified), my CTS was failing and Device was not Certified but I had no problems using Chrome on daily basis
---
Also, you have PrebuiltGmail and Music2, I had Gmail2 and FileExplorer_old (I had to use Package Manager to find that Gmail was installed as Gmail2/Gmail2.apk and similarly the Android FileExplore as FileExplorer_old.apk)
Btw all Mi* and Miui* stuff apply only for debloating Xiaomi
In your input list you have lite and wps (both are not found in the log), mine was wps_lite (WPS preinstalled to Vendor) - please check
zgfg said:
Interesting - what happens when you debloat Chrome-Stub from Product and leave Chrome on Data, does it still run?
Btw, I do use Chrome (because of the integrated translator, making me easy to sometimes read worldwide forums if needed) and I didn't want to debloat originally. However, my preinstalled version on Product was not the latest, and Google Play was offering me to update, but updating Chrome was always failing.
I downloaded the apk from ApkMirror but installation had also failed
Then I debloated (at that time, prior to this debloater I used to manually create my system folder given to Magisk to overlay, and with dummy apk instead of with .replace file) and only then I was able to install Chrome apk (ofc to Data) and since then, to regularly update it through Playstore
One more thing. I've found some people claiming that Chrome breaks to run if Playstore shows Device is not certified.
But back in the spring when Google started to play with enforcing CTS Profile Hardware attest, and prior than @Displax invented ro.product.model spoofing (to force Basic attest and to pass CTS/SafetyNet, to get Device certified), my CTS was failing and Device was not Certified but I had no problems using Chrome on daily basis.
Click to expand...
Click to collapse
PlayStore issues are weird at best.
Hit or miss, depends on the device and/or setup.
Certificataion does not seem to play a big part over all.
If it does then Google's has more issues than fixing SafetyNet to worry about.
Sometimes it is just a Google being Google.
I will look into Chrome tomorrow.
I normally use Chrome Dev PlayStore - Link.
More so now, Brave Browser PlayStore - Link.
zgfg said:
Also, you have PrebuiltGmail and Music2, I had Gmail2 and FileExplorer_old (I had to use Package Manager to find that Gmail was installed as Gmail2/Gmail2.apk and similarly the Android FileExplore as FileExplorer_old.apk)
Btw all Mi* and Miui* stuff apply only for debloating Xiaomi
In your input list you have lite and wps (both are not found in the log), mine was wps_lite (WPS preinstalled to Vendor) - please check
Click to expand...
Click to collapse
No harm checking for apps that do not exist on the device.
It may cause extra lines in the log file and one or two seconds of install time.
My bad.
Must have split wps_lite when I was adjusting the list. Then when sorting, it just put lite and wps in the correct order.
---
I re-flashed and/or reverted a few phones tonight and added them to the gDrive Link.
The files listed as _pfile.list (preinstalle files) are a list of files located in app and/or priv-app of system, product and vendor.
I use a shell scripts for this kind of stuff, [ because I am lazy ] primarily with adb shell.
I adjusted the one I use to make the pfile list.
list_pfiles.sh - Still needs to be run as root.
list_pfiles.sh needs to be located in a writable directory. (sdcard/Download | data/local/tmp | ...)
It still uses a static NAME= variable that you will want to change.
I added a few things to make it run from a root file manager like fx or mix.
With the addition (work from a file manager app/or called from a diferent directory), if you rename the script file, you will also have to adjust the SCRIPT= variable to match.
Cheers.
Edit:
2021.Aug.21
I updated the list_pfiles script.
To Use:
Copy this script to the device.
Recommended to use the /sdcard/Download/ directory.
Run from adb shell (or a terminal app) using the sh command.
sh list_pfiles.sh
Run from a file manager that is able to execute a script file.
Note: May or may not work depending on file manager..
ipdev said:
PlayStore issues are weird at best.
Hit or miss, depends on the device and/or setup.
Certificataion does not seem to play a big part over all.
If it does then Google's has more issues than fixing SafetyNet to worry about.
Sometimes it is just a Google being Google.
I will look into Chrome tomorrow.
I normally use Chrome Dev PlayStore - Link.
More so now, Brave Browser PlayStore - Link.
No harm checking for apps that do not exist on the device.
It may cause extra lines in the log file and one or two seconds of install time.
My bad.
Must have split wps_lite when I was adjusting the list. Then when sorting, it just put lite and wps in the correct order.
---
I re-flashed and/or reverted a few phones tonight and added them to the gDrive Link.
The files listed as _pfile.list (preinstalle files) are a list of files located in app and/or priv-app of system, product and vendor.
I use a shell scripts for this kind of stuff, [ because I am lazy ] primarily with adb shell.
I adjusted the one I use to make the pfile list.
list_pfiles.sh - Still needs to be run as root.
list_pfiles.sh needs to be located in a writable directory. (sdcard/Download | data/local/tmp | ...)
It still uses a static NAME= variable that you will want to change.
I added a few things to make it run from a root file manager like fx or mix.
With the addition (work from a file manager app/or called from a diferent directory), if you rename the script file, you will also have to adjust the SCRIPT= variable to match.
Cheers.
Click to expand...
Click to collapse
Pixel comes with only G stuff but interestingly, without Wellbeing
Velvet.apk, what is the package name (you should still be able to find the name on /data/data)?
When you have Velvet (Poco F1, F2 and One+ 5T), do they also have Google.apk = com.google.android.googlequicksearchbox?
Btw, if you use MiXPlorer and choose Tools, App Remnants, you can see /data/data folders for debloated apps (and you can remove them)
HippoMan said:
Over the weekend when I have time to fix any potential bricking or boot loops, I'm going to try this on my A/B device (One Plus 7Pro, GM1917, OOS 10.3.5) ... unless before then anyone indicates that this is not even likely to work on my phone.
If I end up doing this, I'll report my results.
Click to expand...
Click to collapse
I did it just now, and it worked wth no problems on my device! For my initial test, I used SystemlessDebloater to remove GooglePartnerSetup, and it was indeed removed. No bootloops, no problems.
Good work on this module!
zgfg said:
...
Btw, if you use MiXPlorer and choose Tools, App Remnants, you can see /data/data folders for debloated apps (and you can remove them)
Click to expand...
Click to collapse
Well, in my case, GooglePartnerSetup doesn't appear anywhere among MiXPlorer's "App Remnants", even though other /data/data items are indeed being displayed there. But this is not causing any kind of issue on my device, so I am not concerned.
.​
zgfg said:
Pixel comes with only G stuff but interestingly, without Wellbeing
Click to expand...
Click to collapse
Don't worry, Google would not forget to bundle it.
Digital wellbeing is named WellbeingPrebuilt.
package: name='com.google.android.apps.wellbeing'
I just did not add it to the debloat list.
zgfg said:
Velvet.apk, what is the package name (you should still be able to find the name on /data/data)?
When you have Velvet (Poco F1, F2 and One+ 5T), do they also have Google.apk = com.google.android.googlequicksearchbox?
Click to expand...
Click to collapse
Velvet is Google.
package: name='com.google.android.googlequicksearchbox'
As far as I know, Velvet is the bundled and/or GApps name used.
Cheers.
HippoMan said:
I did it just now, and it worked wth no problems on my device! For my initial test, I used SystemlessDebloater to remove GooglePartnerSetup, and it was indeed removed. No bootloops, no problems..​
Click to expand...
Click to collapse
Just a short question - you have A11 on your OnePlus 7Pro?
zgfg said:
Just a short question - you have A11 on your OnePlus 7Pro?
Click to expand...
Click to collapse
One Plus 7Pro, GM1917, OOS 10.3.5 ... as I mentioned above OOS 10.x is A10.
.​
zgfg said:
Interesting - what happens when you debloat Chrome-Stub from Product and leave Chrome on Data, does it still run?
Btw, I do use Chrome (because of the integrated translator, making me easy to sometimes read worldwide forums if needed) and I didn't want to debloat originally. However, my preinstalled version on Product was not the latest, and Google Play was offering me to update, but updating Chrome was always failing.
I downloaded the apk from ApkMirror but installation had also failed
Then I debloated (at that time, prior to this debloater I used to manually create my system folder given to Magisk to overlay, and with dummy apk instead of with .replace file) and only then I was able to install Chrome apk (ofc to Data) and since then, to regularly update it through Playstore
Click to expand...
Click to collapse
Still have to test some more.
So far only on my Pixel aOS 11.
This is a little tricky to explain my testing/findings.
- Long post, truncated it for now. -
Not logged into Google. (PlayStore)
With Chrome stub active, Chrome is treated as a system app.
Even though the full version is in data it can not be uninstalled only disabled.
PlayStore shows an available update for Chrome.
If stub is removed (debloated), Chrome is treated as a user app.
You have the option to uninstall.
PlayStore does NOT show an update for Chrome.
Did not matter if I cleared cache and/or data on PlayStore or re-scan with with PlayProtect.
This is odd, since Google should still want to update even if it is just a user app.
I'll have to dig though the user agreement again.
Might be automatic update only when Google apps are included (system app) when not logged in.
--
As soon as I logged in, Google immediately updated some back-end.
Chrome is now available for an update and it updated fine.
This is also where some oddities came in.
--
<TRUNCATE>
--
Still have to double check everything.
Seems to be an issue distinguishing between system and user apps.
Should have time this weekend to redo and verify every step I used for testing.
As of now, I would suggest the same as you did it.
Debloat Chrome (stub)
Uninstall Chrome (should be considered a user app after the debloate.)
Install from another source (if need be then update from PlayStore.) or just install from PlayStore.
Cheers.
Btw, released v1.3.5 through the OP post #1 - just to log to the logfile the Android version, is it SAR and is it A/B - would be nice if you can test does it log correctly when you have time and A/B device.
Unfortunately, still unable to resolve a miss-communication with the bot to successfully submit to Repo
Can somebody dhare his debloat app list? Or the best, .sh file? İt would be great

[Guide][SM-T500/T505] Galaxy Tab A7 10.4 - Link to root, App2sd, SafetyNet Pass including cts profile

1. Root using magisk - Please refer to this excellent guide by @DJBhardwaj Click here for thread
2. App2sd pro by Vicky Bonick This is the playstore link
a. After activating root install busybox using any of the busybox apps on the play store. I used Busybox for android by jrummy (I know busybox is an older version in this app)
b. Format your SD card using MiniTool Partition Wizard (its a free app, just google and download) you can also use the internal tool on add2sd but they are unreliable and sometimes need a soft reboot to mount.
b1. For this to work we will first delete all partitions using MiniTool Partition Wizard or use the internal partition tool in the app2sd app.
b2. Then we will create our first partition, this is a fat32 partition (this will be a primary partition)
b2a. The fat32 partition should be larger than the ext2 partition as this is where most files are stored. An 80:20 ratio will work.
b3. Next we will create our second partition, this is a ext2 partition (this will also be a primary partition)
b4. Click apply and wait for this to complete
c. Insert the SD card into the tablet and restart
d. Once it has restarted open App2sd.
d1. On the main page click settings
d2. Click on Set su.d/post-fs-data here enter the value /data/adb/ (this will give it the directory for magisk)
d3. Check ignore systemless root
d4. Check Use pre installed busybox bianary
e. Now go pack to the app home and click on link apps to SD card
e1. Click on the three lines to open the menu
e2. Delete mount script
e3. Recreate mount script
e4. Select option ext4 (yes i know the sd card is formatted in ext2, ext2 option in app2sd has compatibility issues so for mount use ext4 option but the sd card format remains in ext2)
e5. Select I have su.d support/magisk is installed
e6. Create the script
f. Everything should now work, unfortunately the partition does not auto mount so every time you restart, you need to open app2sd and select remount 2nd partition (this is found in the three line menu in the link apps to sd card option. (if any one figures out how to get the auto mount working let me know and I will update the guide)
g. Now just link the apps and you are set
Edit 1 - Three very important notes
1. Do not click the fix SD card button. It will destroy everything on the SD card this only applies for when MiniTool Partition Wizard is used.
2. Always Link external data folder to 2nd partition, the first partition is having trouble relinking the data, which you need to do after every reboot. Short-cut to do this is by going into Link apps to SD card, Clicking on the three lines on the top left for the menu, Click on relink library file, then click on relink dalvik-cache files, rebind external folders
3. To preserve folders we need to link everything in the app2sd linking except for the APK.
How to pass the safety net check in magisk including cts profile
1. Open Magisk - open settings by clicking on the gear in the top right corner
2. Click on the toggle to enable MagiskHide
3. Click on systemless hosts
4. Download the latest zip of Universal Safetynet-fix from Github here
5. Click on the module icon (puzzle icon) in magisk
6. Click on install from storage and install the Safetynet-fix file you just downloaded
7. Install from the module list
7a. liboemcrypto disabler
7b. MagiskHide Props config (needed if safety checks are not passing after all previous steps : only use if you know what you are doing)
8. Now reboot your device all safetynet checks will pass, netflix and banking apps should work
Special Note how to retain L1 for netflix on rooted tab - After flashing the rooted OS, do not delete the system app of netflix, update it via an APK download with whatever the latest APK is; not from the play store. I repeat do not delete the system app of netflix that is pre installed.
Special Note 2 To make flow and other samsung apps work that give you the rooted error add them to the magisk hide option in the magisk app, this is in the second option (the shield). This will make flow etc work. You must also add the samsung core services apk to the magisk hide option. Samsung pay and pass will still not work.
Reserved
Did it like that and lost Widevine L1!! Didn't delete the Netflix app but updated it with a apk! Is there anything I can do?
Edit:
I do not need "liboemcrypto disabler" for SafetyNet pass! And with this module deactivated DRM Info as well as Netflix shows Widevine L1 but I'm not sure if it is FullHD when playing Video, is there any option to show the actual playback resolution?
Best Regards
glockmane88 said:
Did it like that and lost Widevine L1!! Didn't delete the Netflix app but updated it with a apk! Is there anything I can do?
Edit:
I do not need "liboemcrypto disabler" for SafetyNet pass! And with this module deactivated DRM Info as well as Netflix shows Widevine L1 but I'm not sure if it is FullHD when playing Video, is there any option to show the actual playback resolution?
Best Regards
Click to expand...
Click to collapse
Yes there is an option in the netflix settings that show if FullHD is available.
To Root the Tab A7 T-500 is the simplke thing to do : you need only Magisk, after you did flash the original AP - (and unlock Bootloader first) you will stuck twice : 1) push on/off button to pass first message - (you will never get rid of the messages - but it doesnt matter) than you will get to chosse Country & Language - this is the point were it will restart and you will stuck!! just go to accessibility and jump "back & forth" a few times - now you passed without restart! IMPORTANT - if your Tab will stop during Odin already : YOUJ MUST EXTRACT THE PIT FILE from CSC or one of those 3 files you got - then enter PIT on Odin, then it will repartition automatically (you will see, it does it byself) there you go!!!! the rest ist just updating Magisk App...... You did it! Have funView attachment 5379399View attachment 5379401
xthakila said:
1. Root using magisk - Please refer to this excellent guide by @DJBhardwaj Click here for thread
2. App2sd pro by Vicky Bonick This is the playstore link
a. After activating root install busybox using any of the busybox apps on the play store. I used Busybox for android by jrummy (I know busybox is an older version in this app)
b. Format your SD card using MiniTool Partition Wizard (its a free app, just google and download) you can also use the internal tool on add2sd but they are unreliable and sometimes need a soft reboot to mount.
b1. For this to work we will first delete all partitions using MiniTool Partition Wizard or use the internal partition tool in the app2sd app.
b2. Then we will create our first partition, this is a fat32 partition (this will be a primary partition)
b2a. The fat32 partition should be larger than the ext2 partition as this is where most files are stored. An 80:20 ratio will work.
b3. Next we will create our second partition, this is a ext2 partition (this will also be a primary partition)
b4. Click apply and wait for this to complete
c. Insert the SD card into the tablet and restart
d. Once it has restarted open App2sd.
d1. On the main page click settings
d2. Click on Set su.d/post-fs-data here enter the value /data/adb/ (this will give it the directory for magisk)
d3. Check ignore systemless root
d4. Check Use pre installed busybox bianary
e. Now go pack to the app home and click on link apps to SD card
e1. Click on the three lines to open the menu
e2. Delete mount script
e3. Recreate mount script
e4. Select option ext4 (yes i know the sd card is formatted in ext2, ext2 option in app2sd has compatibility issues so for mount use ext4 option but the sd card format remains in ext2)
e5. Select I have su.d support/magisk is installed
e6. Create the script
f. Everything should now work, unfortunately the partition does not auto mount so every time you restart, you need to open app2sd and select remount 2nd partition (this is found in the three line menu in the link apps to sd card option. (if any one figures out how to get the auto mount working let me know and I will update the guide)
g. Now just link the apps and you are set
Edit 1 - Three very important notes
1. Do not click the fix SD card button. It will destroy everything on the SD card this only applies for when MiniTool Partition Wizard is used.
2. Always Link external data folder to 2nd partition, the first partition is having trouble relinking the data, which you need to do after every reboot. Short-cut to do this is by going into Link apps to SD card, Clicking on the three lines on the top left for the menu, Click on relink library file, then click on relink dalvik-cache files, rebind external folders
3. To preserve folders we need to link everything in the app2sd linking except for the APK.
How to pass the safety net check in magisk including cts profile
1. Open Magisk - open settings by clicking on the gear in the top right corner
2. Click on the toggle to enable MagiskHide
3. Click on systemless hosts
4. Download the latest zip of Universal Safetynet-fix from Github here
5. Click on the module icon (puzzle icon) in magisk
6. Click on install from storage and install the Safetynet-fix file you just downloaded
7. Install from the module list
7a. liboemcrypto disabler
7b. MagiskHide Props config (needed if safety checks are not passing after all previous steps : only use if you know what you are doing)
8. Now reboot your device all safetynet checks will pass, netflix and banking apps should work
Special Note how to retain L1 for netflix on rooted tab - After flashing the rooted OS, do not delete the system app of netflix, update it via an APK download with whatever the latest APK is; not from the play store. I repeat do not delete the system app of netflix that is pre installed.
Special Note 2 To make flow and other samsung apps work that give you the rooted error add them to the magisk hide option in the magisk app, this is in the second option (the shield). This will make flow etc work. You must also add the samsung core services apk to the magisk hide option. Samsung pay and pass will still not work.
Click to expand...
Click to collapse
Far too much action, just to get Root! Just read what I was posting and save your precious time!
nobasband said:
Far too much action, just to get Root! Just read what I was posting and save your precious time!
Click to expand...
Click to collapse
If you read the post its not to get root! its so that you can use the memory card as an extended memory.
xthakila said:
If you read the post its not to get root! its so that you can use the memory card as an extended memory.
Click to expand...
Click to collapse
So what about a Magisk Module? There is a bunch of links on I.e. Google, to find
xthakila said:
If you read the post its not to get root! its so that you can use the memory card as an extended memory.
Click to expand...
Click to collapse
It is all about 2use external SD as an internal ? That’s simple, too
nobasband said:
It is all about 2use external SD as an internal ? That’s simple, too
Click to expand...
Click to collapse
I've owned several different Samsung tablets and it seems this discussion comes up over and over again. The answer is always the same. Nobody has solved it because the people who have the ability to do so, all consider it a bad idea. The external SD card is MUCH to slow to use to run apps. And if you move data storage, particular any 4k video files, to the external, then you shouldn't ever need more than 32gb of internal. The ONLY exception to this I've heard comes from people trying to run massive games that want to save the games on internal. And, IMO, buying tablets in this price range, to play these games, just doesn't cut it.
lewmur said:
I've owned several different Samsung tablets and it seems this discussion comes up over and over again. The answer is always the same. Nobody has solved it because the people who have the ability to do so, all consider it a bad idea. The external SD card is MUCH to slow to use to run apps. And if you move data storage, particular any 4k video files, to the external, then you shouldn't ever need more than 32gb of internal. The ONLY exception to this I've heard comes from people trying to run massive games that want to save the games on internal. And, IMO, buying tablets in this price range, to play these games, just doesn't cut it.
Click to expand...
Click to collapse
I was wondering too, why someone would want to use the slower SD for memory reasons....but it seems, that they all already know how to root the TabA7 T-500!
@xthakila 2nd partition mount on boot no problem for me, what i did differently is that i used integrated app2sd partition tool and made 1st partiton in exfat and 2nd partition in f2fs and in the Set su.d/post-fs-data option i put
Code:
/data/adb/post-fs-data.d
And didn't allow app2sd to change the system directly but tell it no if ask me if i want app2sd to write on system directly
Also changing mountspace mode in magisk to global might help too

Categories

Resources