Related
Desire C people!
This stuff is good. Probably you heard about it already, now I tried it and seems to work very well, especially the memory management. Quite a sophisticated tool as far as me noob understand ugh,ugh! :cyclops:
So basically a collection of kernel and memory management tweaks, but has a lot of other like SD card tweaks and maintenance scripts which you can also schedule with SManager. And the download page has some other useful stuff like 3G turbocharger and battery calibrator.
In all it seems like a must have for DC users.
http://forum.xda-developers.com/showthread.php?t=991276
Once you used it a bit it's pretty straight forward and explains everything in details when running the script, and you have the option to "unsupercharge", but have a nandroid backup at hand.
I used two guides, but the first is for Galaxy and the second is less detailed:
http://forum.xda-developers.com/showthread.php?t=1603953
http://forum.xda-developers.com/showthread.php?t=1908505
And for Desire C, check the post below
Many thanks for nikhil16242 for recommending me this, many scripts are in his Customiser already, he would have integrated the whole V6 Supercharger, but Aroma doesn't like it. That would be awesome though!
All credits to zeppelinrox for these truly awesome scripts:good:
One wonders why android doesn't have some of them by default.
V6 Supercharger Install Guide for Desire C
~ v6 supercharger install guide for desire c ~
aka how I have done it, so it's not an absolute one.
zeppelinrox's original thread is here.
Originally Posted by zeppelinrox
What's it do?
It makes your phone FAST... super snappy with better multitasking!
It rearranges and fixes the OOM Groupings and Priorites and lowmemorykiller values.
So basically, it's a COMPLETE MEMORY MANAGEMENT FIX!
It's the ONLY one of it's kind
NO LAUNCHER REDRAWS, faster than ever, multitasking is better... why?
Because it works with the lowmemorykiller and letting it work the way it's meant to work.
Also, because of the rearrangement, it works the same on all roms!
The problem with using minfree tweakers like AMM or AKMO is that it doesn't work the same on all roms.
Secondary apps may be in slot 3 on some roms but in slot 5 in others!
That's why you hear people comment "I tried AKMO but it didn't do anything..."
Most likely it didn't do anything because the apps weren't sitting where they were expected to be.
So fasten your seat belts and enjoy the ride!
Click to expand...
Click to collapse
NOTE: Delete all conflicting scripts from init.d folder, otherwise it will be laggy and annoying!
Conflicting scripts I have found so far:
- all the thunderbolt except miuiCMremount (V6 does most of these like sd card tweaks and zipalign anyway)
- mpengine and laserdroid (also from /system and /xbit)
If you don't know which scripts are from where, unzip nikhil16242's Customiser and check the folders.
Also do not install everything on one breath. Do it gradually (v6 - nullifier - engine flush and so on), test with a demanding game like Temple Run, so you can opt out any possible problems.
What you need:
All V6 scripts are here.
ScriptManager [download]
- If you have stock ROM:
Download Supercharger Starter Kit from the V6 scripts, on the page it's explained how to use it, couldn't be more simple:
Using SuperCharger Starter Kit (Prepares your ROM with the fixed su binary, zipalign binary, sqlite3 binary and busybox v1.19.4... and does NOT include the V6 SuperCharger scipt):
- Extract the zip to the root of the sdcard and it will all be in /sdcard/SuperCharger_Starter_Kit
- With Script Manager, just run StartMeUp.sh to install everything at once.
- Or, in terminal do: su, enter, sh /sdcard/Super*/Start*
Click to expand...
Click to collapse
All the rest is the same as the following:
- If you are on custom ROM:
then busybox is already installed, so you don't need the starter kit.
I. SUPERCHARGER INITIAL SETUP
The script guides you through the process, so watch it closely. In the setup it automatically determines some optimal settings, but you can change them any time.
Step 1. Put the latest V6_SuperCharger_for_Android-UpdateX_XXX (X is the actual version number) on your SD card
Step 2. In SManager:
--- 1. make sure you have granted SuperUser access, and set browse in root (long press recent apps button > Menu > Advanced > Configuration > Browse as root), but if you used before it's already set
--- 2. open the script on your SD card, set the properties to: Favorites (star icon), Root (green android skull icon) and tap Run to execute the script installer.
Step 3. A bunch of text start to come up, watch it closely, it guides you through the installer. Home Locked in Memory? n (No) and press enter and another enter to continue to drivers console.
First it goes to Pit Stop to set Driver Options, where you will be asked for Scroll Speed but also various tweaks which can improve the performance. Go through each and decide if you want them or not (I enabled most of them in he script)
When asks Use Build.Prop? : n (No) to use local.prop - I chose this, it sounds safer.
Step 4. You need to patch services.jar. It can be done automatically or manually (however the script recommends manual, and when I did it automatically for the first time, it did not backup services.jar and could not unsupercharge, only by restoring it from the rom .zip) Don't worry, doing it manually couldn't be easier:
In the Driver's Console choose:
25. Jelly ISCream Parlor {Install services.jar}Choose manual mode, which will take you to the [RC9] ULTIMATIC RC6! [EXE]-=Ultimate Jar Power Tools=-With Maximum MultiTasking Mods! thread in your default browser, from which the essential instructions are the following:
--- 1. Connect your Android to your PC with Android Debugging ENABLED and Mass Storage DISABLED so your device has access to your sdcard. I just put it in Charge Only mode...
--- 2. Download the latest Ultimatic_Jar_Patcher_Tools_XXX_Windows.exe.zip to your PC - Windows exe is NOT zipped. Just remove the .zip extension!
--- 3. Start the exe and follow the instructions in the script. It will ask you which mode you want to use your Launcher in: Hard To Kill Launcher, Die-Hard Launcher or BulletProof Launcher. Choose Hard to Kill (HK), it is the best for our device.
You can add Maximum Multitasking mod as well, according to tests it works fine, but I did not install it in the beginning, then didn't bother
If follow the instructions in the script till the end, your services.jar should be patched, and the script will confirm this.
--- 4. On your phone in V6 script, you are still in the menu 25., right? Press x (exit), which takes you again to the Driver's Console. Choose: 32. SuperClean & ReStart! (ie. Wipe Dalvik Cache & Reboot)
Step 5. Press enter to return to Drivers Console. Pressing enter will automatically run Quick V6 Cust-OOMizer and will calculate optimum SuperMinFree values
Apply SuperMinFree Calculator Settings? : y (Yes) to apply calculated MinFree (low memory killer - lmk) values so you don’t need to choose, but you can change it after completing the initial setup and then running the script again in menu point:
10. Quick V6 Cust-OOMizer.Or if you type n (No), you can choose manually right away, doesn't make a difference. If it was set automatically, go to step 5. and come back later if you want to change it:
For a low memory device like ours, 512 HP recommended, these are the options in menu points:
5. UnLedded (Multitasking) {8,14,40,50,60, 75}
6. Ledded (Balanced) {8,14,55,70,85,100}
7. Super UL (Aggressive) {8,14,75,90,95,125} - it does 130-140MB
However the best setting recommended me by educated colleague nikhil16242 and I tried is:
10 15 25 45 80 100 (slot1 - slot2 and so on)
with this I always have 120-130MB free RAM and no lag, Temple Run is butter smooth Basically it kills processes below that level (but still prioritises them - really smart script), which means less multitasking, but two-three apps that I needed in multitask were working perfectly, I didn't notice any difference, but snappier phone.
Try whichever suits you best.
Step 6. Press Enter - this action will backup Re-SuperCharger files to SD Card, in case you want to restore your Supercharger settings.
Step 7. SuperClean & ReStart : y (Yes), this will wipe your dalvik-cache so bootup time will take longer this time.
Step 8. After restart, open SManager and:
--- 1. Go to /system/etc/init.d (you can bookmark it for later access)
--- 2. Tap on S99SuperCharger and set the following properties:
------ a. Favorites (star icon)
------ b. Root (green android skull icon)
------ c. Start on Boot (gear icon)
--- 3. Tap on Save, close Script Manager and Restart your phone
NOTE:
If you don’t follow step 8., you will get an error the next time you run the script and it will show you owner’s handbook on your default web browser.
II. OOMIFIER & LAUNCHER
If you patched services.jar and choose SuperMinFree values manually then you have this already. If not, then:
OOM Grouping Fixes will determine which are the more priority apps and keeps them alive better. The Launcher mode determines how easy it will be for the mem killer to kill the launcher in case of low memory. Works flippin good, I'm tellin ya
Step 9. After restart, open SManager and Run V6_SuperCharger_for_AndroidX_XXX script again (make sure you run it in root [skull icon] but not boot [gear icon])
--- 1. SuperCharger will run Test Drive, just wait for it to finish and then continue to the Drivers Console.
During the install it should set the optimal mode automatically, which was BulletProof for me, probably because I chose the aggressive memory kill (sounds convincing lol) mode. Anyway, this means the Launcher will never get killed, about which some say it's not recommended.
--- 2. So on the Drivers Console you can choose between these launcher modes in the menu points, in reverse order of toughness:[/INDENT]
11. OOM Grouping Fixes + Hard To Kill Launcher
12. OOM Grouping Fixes + Die-Hard Launcher
13. OOM Grouping Fixes + BulletProof LauncherEventually I changed it to Hard To Kill, but it's up to you.
--- 3. Hard To Kill? : y (Yes) to apply
Press Enter to go back to Drivers Console
III. NITROLAG NULLIFIER
It's an experimental feature, don't know what it does exactly, but I switched it on Everything is flawless for me since, so I say go for it.
Step 10. In the Drivers Console, select:
21. Nitro Lag Nullifier {Experimental}Enter (N)ullify, (U)n-Nullify, E(X)it: N (Nullify) to apply Nitro Lag Nullifier
After applying Nitro Lag Nullifier, press enter to go back to Drivers Console.
IV. 2 in 1 ENGINE FLUSH
It flushes the RAM cache so the phone doesn't get sluggish after days of usage.
The 2 Modes are: -=Fast Engine Flush=- for instant flush and -=Engine Flush-O-Matic=- for automation.
Step 11. In the Drivers Console, select:
17. Engine Flush-O-Matic {ReCoupe RAM Booster}Continue and drop all file system caches? : y (Yes) to clear system cache on RAM
It will ask you (gives you 20 s to decide lol) if you want to automate it, so you don't need to schedule it in SManager. If yes, you set an interval between 1-24, which counts as hours, so it determines how frequently flushes the RAM cache. Some people set it for every hour, so why not, I did that too. Hmmm that was good
After Engine Flush, press enter to go back to Drivers Console.
V. SUPERCLEAN AND RESTART
Wipes dalvik and reboots the phone, you need that before you start to using it.
Step 12. In the Drivers Console, select:
30. SuperClean & ReStart {Wipe Dalvik & Reboot}Do you want to SuperClean & ReStart now? : y (Yes)
VI. VERIFY SUPERCHARGER STATUS
Step 13. After restart, open SManager and run V6 SuperCharger again. You should see Supercharger Level: 100%, then you are good to go.
As the script rolls it indicates your settings so you know what is set and what's not. You can check out the other menu points, and number:
27. Owner's Guide {Open !SuperCharger.html}This opens the... Owners Guide! ...in the default browser, you can wise yourself up about the different options.
VII. KICKASS KERNELISER
Downolad the script and launch it the same way as V6. Look at the text, wisen up and choose KickAss (k).
It will place S98KickAssKerneliser script in init.d, skull it and gear it, and reboot the phone.
TIPS & TROUBLESHOOTING
If you are only 75% supercharged, that probably means MinFree (the mem killer) settings doesn't stick (so you see you have the usual low amount of free RAM). Check the S99Supercharger script in SManager if it has the root and boot privileges (In /system/etc/init.d or Long pressing recent apps button > Menu > Scripts), set them again if they were not and reboot the phone. If it's not set again, open Owner's Guide to figure out what's next, but if you followed the steps properly, you should be fine.
Check the note in the beginning of the post for deleting conflicting scripts!
All the scripts and backups are in two places:
1. on SD card /V6_SuperCharger folder
2. /data/V6_SuperCharger
and the logs and manuals under them.
When you run a script in SuperCharger, it places a separate one in the folders, so you can make widgets with SManager for fast access:
- Long press home screen, select SManager from widgets, locate the SuperCharger folder and select the script you want to have at hand.
- For example for quick change between MinFree modes, the scripts will be in V6SuperCharger/PowerShift_Scripts (you need to run them in SuperCharger first in order to be created separately, or if you installed the additional V6 scripts (or something like that) in nikhil16242's Customiser before, they will be in init.d already).
You'll know you have chosen a suitable MinFree mode if if you play Temple Run with no lags at all shaboooooom!!!!
See, wasn't too hard and you are SuperCharged now.
Enjoy it like a Boss!
Kudos to CarlDeanCatabay and Androidmarketuser for the guides that helped me and are in the OP.
And most of all to zeppelinrox for V6 SuperCharger :good:
Started reading looks great but by ekk I'm finding it hard to get my old head round some of it. Usually when I'm like this I have to read read read till it starts making sense .So will prolly take me a bit of time.
Re: [Script][TWEAKS] V6 Supercharger
This script is really awesome once you get everything done properly,just takes a while to read the entire OP though .
Ram management is another very essential thing to be done on a low ram device like ours.Stock ram management seems to be poor imo so I use this and the results are truely amazing .
Sent from my HTC Desire C using xda app-developers app
thanks
neoyoli said:
Desire C people!
This stuff is good. Probably you heard about it already, now I tried it and seems to work very well, especially the memory management. Quite a sophisticated tool as far as me noob understand ugh,ugh! :cyclops:
So basically a collection of kernel and memory management tweaks, but has a lot of other like SD card tweaks and maintenance scripts which you can also schedule with SManager. And on the download page has some other useful stuff like 3G turbocharger and battery calibrator.
In all it seems like a must have for DC users.
http://forum.xda-developers.com/showthread.php?t=991276
Once you used it a bit it's pretty straight forward and explains everything in details when running the script, and you have the option to "unsupercharge", but have a nandroid backup at hand.
I used this detailed guide, but it's for Galaxy so use your brain
http://forum.xda-developers.com/showthread.php?t=1603953
Here's is an other one, just in case, but less detailed:
http://forum.xda-developers.com/showthread.php?t=1908505
Many thanks for nikhil16242 for recommending me this, many scripts are in his Customiser already, he would have integrated the whole V6 Supercharger, but Aroma doesn't like it. That would be awesome though!
All credits to zeppelinrox for these truly awesome scripts:good:
One wonders why android doesn't have some of them by default.
Click to expand...
Click to collapse
works great
guide updated
Hey guys, well actually i have an issue while i'm trying to run the v6 supercharger. It succesfully passes the drive test but it gets stuck at the next step. it throws me a lot of lines like 'find system/lost+found/ Too many open files' and i can't get rid of it, please help
this guide is quite old now, supercharger has been updated since numerous times. if you have a nandroid backup restore it, if not then ask zeppelinrox in his original thread. also supercharger does automatic backup before you apply the settings, which can be restored from the menu if something goes wrong, try it.
At first, I am not liable for any harm or damage that may happen to your device!
If you have su and didn't trigger knox, I CANNOT guarantee that running this script won't cause 0x1!
Requirements:
1) P905/viennalte/Qualcomm based model ONLY (won't work on Exynos devices. MIGHT work on other Qualcomm LTE deices from Note Pro and Tab Pro series - feel free to repost but give credits!) running 4.4.2 stock;
2) root access with SuperSU (using cf-root - credits to chainfire);
3) busybox installed (I do recommend this paid installer: https://play.google.com/store/apps/details?id=stericson.busybox.donate , MOST PROBABLY free version will be more than enough, too, but I haven't tested it as I have license...)
4) Android Terminal Emulator installed ( free at: https://play.google.com/store/apps/details?id=jackpal.androidterm )
Installation:
1) download file init.d_qcom.sh using below link and put it in the root of internal memory (so it will be placed in: /sdcard/init.d_qcom.sh)
2) run Android Terminal Emulator
3) at command line, type:
Code:
su -c /sdcard/init.d_qcom.sh
(give it an access if requested)
4) voila.
Additional info for advanced users:
1) scripts in /system/etc/init.d shall be root:root 755 (and NOT 777 as stated in A LOT of sources, thou has to be a heavy idiot to give write access for system files to "world"...)
2) init.d is handled from one of the /system/etc qualcomm additional scripts as it refused to work using regular install-recovery.sh method...
3) scripts are triggered paralelly but I am using different method (find/nohup/su combination...), as this damn rom refused to simply execute "run-parts" applet...
4) init.d permission helper script included (just put your scripts in init.d and they'll receive proper permissions on reboot)
Download:
http://www12.zippyshare.com/v/32009778/file.html
Nice to see some developement for this tab!
Anyway to port it to exynos? :fingers-crossed:
prohackerbro said:
Nice to see some developement for this tab!
Anyway to port it to exynos? :fingers-crossed:
Click to expand...
Click to collapse
+1
sent from my amazing NotePro 12.2 via Tapatalk
Criminal23 said:
+1
sent from my amazing NotePro 12.2 via Tapatalk
Click to expand...
Click to collapse
I might try, however I do not own the device and the file structure is completely different.. Can you first enter via Android Terminal:
Code:
su
ls -l / >/sdcard/content.txt
ls -l /system/etc >>/sdcard/content.txt
And post the /sdcard/content.txt file which will be created (or its contents only)?
Also, i would be glad if you copy every *.rc file from root of filesystem to a dir , compress it to one file and post it too
esgie said:
I might try, however I do not own the device and the file structure is completely different.. Can you first enter via Android Terminal:
Code:
su
ls -l / >/sdcard/content.txt
ls -l /system/etc >>/sdcard/content.txt
And post the /sdcard/content.txt file which will be created (or its contents only)?
Also, i would be glad if you copy every *.rc file from root of filesystem to a dir , compress it to one file and post it too
Click to expand...
Click to collapse
Here you are
Criminal23
Criminal23 said:
Here you are
Criminal23
Click to expand...
Click to collapse
Criminal23 said:
Here you are
Criminal23
Click to expand...
Click to collapse
After looking into sent (and posted) files, I have to say that the init process in our devices are ABSOLUTELY different.
Qualcomm version triggers about 7-8 scripts lying in /system, which are provided by Qualcomm, which are pointed in configuring all the hardware provided with their chipset - in addition to init.???.rc files from the kernel. The clue was to add init.d execution command at the very end of one of those scripts (and that is done automatically with script attached in the first post).
Exynos version does not launch (almost - see below) ANY external script during the boot. Whole process seems to be performed by rc files lying in root of the filesystem, which are embedded in kernel's ramdisk and any edits won't preserve the reboot, so it cannot be done without repacking the kernel and that is something far more troublesome to perform without device in hand, without the firmware on disk and without a plenty of time.
BUT
it still runs /system/etc/install-recovery.sh which is an Android standard and which genuine purpose was to reflash recovery back to stock if a custom one was detected. Now, it is sometimes utlized to run somehing at boot, especially: it is used by SuperSu (in addition with other methods) to run its daemon. The problem is that kitkat introduced enforcing SELinux, that Samsung SELinux policy adds special security context for this file, that install-recovery.sh won't be launched if the file has no proper security label - and that while installing SuperSu, the context is set in a different way and in final, install-recovery.sh isn't launched, until we restore /system context, and restoring context to the system ends with... non working su, so we have to flash it again, breaking install-recovery.sh context... Did you get it? - it's a loop as fixing one thing breaks the second, and fix to the second breaks the first That is why on my qualcomm device i have chosen another script file to run the init.d - and as you don't have any other script except install-recovery.sh, I don't know where it might be put...
BUT also I cannot guarantee that the behavior above is not qualcomm-exclusive and it is possible that on exynos device everything will work without problem!
That's why you may want to try standard method for all the devices (term init - uses install-recovery.sh method described above):
http://forum.xda-developers.com/showthread.php?t=1933849
and if it won't work then you have to wait for - at least - repacked kernel with init.d support embedded into init.rc files or run your script by an external app, ie SManager. Just be aware that even if term init work, it may stop working every time you flash SuperSu, so remember to run the script again then.
Sorry for not being too helpful.
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"
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
Hi all,
I was backing up with the unofficial TWRP and found out that I started getting error 255 after having set and removed (because otherwise TWRP could not decrypt) the PIN. Yoink in this thread pointed out that:
"You need to look at /tmp/recovery.log while in recovery (adb pull it). Look in it for the last file that it tried to read before it gave the error. Your options are either delete that file or pull it then delete it. However, the file is corrupt in some way and the backup will never finish. Restoring an older nandroid fixes this because it deletes the existing files and writes your nandroid back over them."
I tried doing what he suggested but found multiple files with gibberish names at the location.
I understand that the TWRP that I used is an unofficial version, and only want to point out that the error only occurred after a PIN was set, in case someone experienced same issue.
I had the same error when I tried to do a backup on my P20 with the unofficial TWRP. I pulled the recovery.log and it noted a folder '/data/system_ce/10' that it couldn't read. So I jumped into the File Explorer withing TWRP and surprised to find that folder's contents all encrypted whereas nothing else was encrypted (I've removed all lockscreen PIN/fingerprint etc).
After some digging around, that folder is created when you use the App Twin feature as it creates encrypted account information when you duplicate say WhatsApp or Facebook. Removing the duplicated apps removes the '/10' folder which I can then do a full nandroid backup.
I could resolve my nandroid /data backup error on my EMUI 8.0 Mediapad M5 device with those following steps:
1 - Use a correct TWRP implementation
TWRP need to access the uncyphered partition /data.
There no possibility to backup it, if TWRP does not implement deciphering user data partition.
2 - Remove all users except user 0 (the administrator)
You can verify that there is no unwanted users, looking at directory /data/user : the only subdirectory should be "0".
To remove the others users :
Remove the PrivateSpace if you have one (Settings > Security & Privacy > PrivateSpace, and tap on the garbage can).
Remove all the secondary users (Settings > Users & accounts > users, and tap on each users to delete them). Keep just the main administrator user.
On EMUI, remove all twins applications (Settings > Apps & Notifications > App Twin, and disable all twin apps).
On OxygenOS, remove all parallel apps (Settings > Apps > Parallel Apps, and disable all parallel apps).
On MIUI, remove all dual apps (Settings > Dual Apps, and disable all dual apps)
On others devices ... you must find all parameters that create those unwanted users.
If you are not able to get the correct settings to suppress those users, in last resort you can try this command : "pm remove-user user-no. (For example "pm remove-user 999").
3 - Do not forget to protect your backups by a password
This would be stupid to cipher your /data partition and keep backups of this partition unprotected.
These steps fixed the nandroid backup problem for /data partition on my Huawei Mediapad M5 device.
I post on this forum because I hope that this will be helpful for others devices owners.
larpoux said:
I could resolve my nandroid /data backup error on my EMUI 8.0 Mediapad M5 device with those following steps:
1 - Use a correct TWRP implementation
TWRP need to access the uncyphered partition /data.
There no possibility to backup it, if TWRP does not implement deciphering user data partition.
2 - Remove all users except user 0 (the administrator)
You can verify that there is no unwanted users, looking at directory /data/user : the only subdirectory should be "0".
To remove the others users :
Remove the PrivateSpace if you have one (Settings > Security & Privacy > PrivateSpace, and tap on the garbage can).
Remove all the secondary users (Settings > Users & accounts > users, and tap on each users to delete them). Keep just the main administrator user.
On EMUI, remove all twins applications (Settings > Apps & Notifications > App Twin, and disable all twin apps).
On OxygenOS, remove all parallel apps (Settings > Apps > Parallel Apps, and disable all parallel apps).
On MIUI, remove all dual apps (Settings > Dual Apps, and disable all dual apps)
On others devices ... you must find all parameters that create those unwanted users.
If you are not able to get the correct settings to suppress those users, in last resort you can try this command : "pm remove-user user-no. (For example "pm remove-user 999").
3 - Do not forget to protect your backups by a password
This would be stupid to cipher your /data partition and keep backups of this partition unprotected.
These steps fixed the nandroid backup problem for /data partition on my Huawei Mediapad M5 device.
I post on this forum because I hope that this will be helpful for others devices owners.
Click to expand...
Click to collapse
also don't forget if you had use appLock on Miui... it also restrict the backingup... so disable those apps that are locked...