How To Guide [Guide] MIUI Battery Optimization Whitelist - MIUI 12 - Redmi 9 Power / 9T

Namaste friends! Today we will learn how to remove Xiaomi's apps from Android's native battery optimization function also known as 'Doze' and how to optimize the whole MIUI further more for acute battery and performance optimization too.​
Note: Please continue on your own risk. I will never be held responsible for anything you cause to your device. As I've never experienced any minor / major issues after the process explained here in this post. So, proceed on your own risk.
This process is extensively tried and tested multiple times with multiple MIUI release versions on a same single device running a global version of MIUI 12.5 and so. The device underwent in this process is Redmi 9 Power (India). Let's not waste time for modding our device to our own need.
Requirements: A Xiaomi device having root and unlocked bootloader with a custom recovery (TWRP/else) installed on it. A good root file manager, in my case it is MixPlorer.
Let's begin​
Clean flash your ROM (Recovery or Fastboot, make sure the bootloader is unlocked after the flash) .
Reboot to recovery and flash Magisk Pathed Boot.img of the ROM you just flashed.
Format and reboot to system.
After boot, proceed with installing Magisk apk followed by MixPlorer.
Launch MixPlorer > goto /root folder > grant root (Magisk PopUp) .
Go to /system/xbin and delete all files in there. (these files do something at device boot-up and patch something before the lock screen appears) .
Again in /system/etc/sysconfig delete the xmls that include 'Xiaomi app names' with "allow-in-power-save" tag. You can also rename the xml file extention to anything other than xml that will also work like they are deleted or not there. ( XMLs like - miui core, miui-whitelist, power save config etc. Please open the xmls and verify before modifying the same )
Now head to /system/etc/permission, delete XMLs with "Facebook" names. You can also review some more XMLs in there as I found and patched some more XMLs including "allow-in-power-save" followed by mi apps.
If supported, go to /product/etc/sysconfig and rename google.xml to google.bak for gms to be optimised on next reboot.
Now debloat: Delete apps and their corresponding files in the same folder where apps are. Do not delete the folder only delete the apk and its dll or odex / vdex files. ( Never delete Find device, Mi account, Security etc.)
Now when done, reboot to recovery > format data > reboot to system.
to be continued...

Related

[ROM] [2016.12.07] XT1096 5.x stock based rom

Updated 2016.12.07 - Post updated with current files, see end of post for links to helpful posts.
Updated 2016.04.14 - Post updated with current files.
Updated 2016.01.23 - This post has been rewritten for people who have unlocked their Verizon XT1096 through the Motorola unlock page. It is presumed that you have fastboot installed and working and that you have at least a 5.x version of Android on your phone. (Android version in Settings -> About phone) If not and you're still on 4.4.4, the information hidden at the bottom of this post will help you upgrade.
This ROM is based on the Stock ROM and has SuperSU v2.65, Xposed v80, Xposed Installer, BusyBox v1.24.1-Stericson, sqlite3, zip, aapt, and DNS support for Busybox apps pre-installed. System is mounted R/W via su.d script, addon.d scripts are supported, the Verizon part of the boot animation is removed, tethering is enabled. The following obsolete files are deleted from the stock image:
Avatar
AvatarPermissionsApp
Bug2GoStub
com.customermobile.preload.vzw
CQATest
DemoMode
fswriter
GuideMe
LMIRescue
LMIRescueSecurity
LocalWipePolicyManager
MediaShortcuts
MotoCare
MotoCareInt
VerizonSSOEngine
VMobileSecurity
VzwAVS
vznavigator
In addition to TWRP mentioned next, you'll need a few files on hand to complete the process:
XT1096-23.32-25-5-5-Firmware.zip - TWRP zip to update firmware.
xt1096-5.1-23.32-25-5-5-Mod.zip- The factory based modified ROM
A GApps package, this is possibly the most confusing part for new ROM flashers and will be discussed below.
xt1096-5.1-debloat.zip - Optional, removes some Verizon bloat, see list below
xt1096-5.1-debloat-keepconnect.zip - Same as above but retains Moto Connect and some files need for the Moto Gallery app.
If you want root, flash SuperSU from this thread: SuperSU Release (As of the time of this posting the direct link to the download is here: SuperSU-v2.78-201609011115.zip
If you want Xposed, flash xposed from this thread: Xposed thread you want the version for SDK22 for ARM. (As of the time of this posting, the direct link to the download is here: xposed-v87-sdk22-arm.zip
Here is the list of apps deleted by the debloat zip, the keepconnect version does not remove Motorola Connect:
ECID_VZW_Victara (Verizon Caller ID $)
GoogleHindiIME
GooglePinyinIME
iWnnIME
KoreanIME
com.gotv.nflgamecenter.us.lite
VZMessages
BodyGuardApp (Alerts)
Verizon Cloud
Verizon CloudSetup
Entitlement
MotorolaConnect
MyVerizon
VVM3 (Visual Voice Mail $)
GApps are Google Applications, the stock ROM originally had many of the GApps but they are outdated. Note: Due to changes in the Open GApps package, the minimum level that will work correctly with this ROM is the Micro package, the nano and pico packages probably won't work. Like other custom ROM's, if you want to use any Google services and/or the Play Store, you must install a GApps package. One source is here: Open GApps with an XDA discussion group here: XDA Open GApps When selecting your GApps package, choose ARM for the platform and 5.1 for the version of Android. Then any of the variants will work to give you access to the Google services. The XT1096 has plenty of room and resources for the larger packages. The "Full" variant is probably most like what the phone came with as stock. Be advised that the "Stock" and "Super" variants, by default, will replace the excellent Motorola camera app with the Google camera app. You can avoid this by creating a gapps-config.txt file kept in the same place as the installer zip. In addition, all but the "Nano" and "Pico" variants will put Google Photos in place of the stock Gallery app with it's Highlight Reel tool. Creating a gapps-config.txt file is described on the pages linked above. To avoid losing the Moto Camera and Gallery apps, you might have a gapps-config.txt file like this:
Code:
+Gallery
CameraGoogle
Collect all the needed zip files and place them all in your download folder on the phone or on a USB-OTG drive.
Install TWRP. The TWRP app from the Play Store doesn't always work reliably, install TWRP using fastboot. The latest official version is 2.8.7.1 and you can download it from here: https://dl.twrp.me/victara/. (Note: Some people have reported problems with official versions of TWRP getting stuck at the splash screen. See post 1013 for alternate versions of TWRP that may work for you.) Put the .img file in the same place that you run fastboot from, put the phone in bootloader/fastboot mode and run the following command (replacing the file name at the end with the file you want to flash):
Code:
fastboot flash recovery twrp-2.8.7.1-victara.img
The process only takes a couple seconds, ignore any errors about size mismatch. Use the volume down key to highlight recovery, then press the volume up key to select. The phone should reboot into TWRP. Make a backup, preferably to a USB-OTG drive before you do anything else. If something goes wrong with the next steps, you'll be able to restore the backup and be back to where you started.
In TWRP select WIPE, then Advanced Wipe. Select, Data, System, Cache and then slide the slider to begin the process. This will wipe the phone except for your pictures and other things on the "SDCARD" or internal storage. (The phone will enter setup when booting the first time after flashing the ROM. You might be able to get away with not doing the wipe, most people will have problems if the wipe isn't done due to the Google apps being updated from the stock installed versions.)
Return to the Home menu in TWRP, select install, then add zip. Select xt1096-23.32-25-5-2_gpt.zip. Tap add zip again and select xt1096-23.32-25-5-2_Firmware.zip. Tap add zip again and select xt1096-5.1-23.32-25-5-2_1.zip. These 3 must be first. Tap add zip again and select the GApps zip file that you selected. If you are debloating, tap add zip again and select that zip file. If you want the CM AudioFX, tap add zip again and select that zip (you can actually do this step in the future by itself if you want.) At this point you have at least 4 zips and possibly 6 selected; slide the slider to begin the flashing process. This will take a while, don't interrupt it. If the screen turns off, use the power button to turn it back on. When done, use the Reboot System button to restart the phone. The phone will reboot, it will show the logo and then the boot animation. It will take 4-5 minutes during which time the boot animation will appear to be stuck, don't panic, this is normal and will only happen the first time after a clean install. The phone should start an optimizing apps process and when that completes, you will see the first set up screen.
Enjoy your rooted stock ROM!
See post 2 for zips to add Viper4Android, restore Exchange2, or remove Xposed and links to other useful things.
See post 886 for flashable zips to change the boot logo and boot animation to a Marshmallow style.
See post 1009 for more info about the current files listed here.
See post 1057 for more info about the April 2016 security update.
See post 1108 for more info about the August/November security update and instructions to flash your phone to stock.
The info below is about mofo and previous versions of this rom. Most people won't need to look at it!
Updated 2015.09.16 - Jump to post 781 for the TWRP Stagefright patch update!
Updated 2015.09.12 - Jump to post 783 for the MOFO Stagefright patch update!
Below is the original information for using Mofo to flash 5.0 images, upgrade to 5.1 and other Mofo info. If you have used Sunshine to unlock your bootloader, you can still flash any of the old images using fastboot. Now, this thread will have images for flashing with both mofo and TWRP..
I've created a base XT1096 v5.1 stock based image that is setup like a custom ROM. This image has tether enabled in build.prop, Busybox and SQLite3 are installed. The ROM has been rooted with SuperSU. Support for DNS in Busybox is included. Certain apps that are potentially spyware or are outdated have been removed. Even more stock apps can be removed via TWRP with the xt1096-5.1-debloat.zip file available in post 2. As time permits I'll create some more TWRP zip files to add Viper4Android, the stagefright patches when released, etc.
Important: This ROM, like other custom ROMs, does not included GApps (like PlayStore, etc.) Most everyone will want to download a GApps package and include it in the list of zips to install in TWRP. There are several GApps packages out there, TK GApps are very flexible and can be configured to install just the bare minimum or the full set of Google Apps: TK GApps 5.1 If using Xposed, you will need to reinstall the Xposed Installer app from here: XposedInstaller_3.0_alpha4.apk; you will then need to open the Xposed Installer and enable your installed modules before they will function.
The TWRP flashable image is available here: xt1096-5.1-stock-20150820.zip
If you do a clean flash (wipe data), it takes 4-5 minutes for the phone to start the first time.
See some useful links and additional TWRP zips in the next post!
Here is a nice guide for upgrading from the Mofo to the unlocked bootloader with Sunshine, installing TWRP and using the TWRP compatible zips by @betarepeating:
Starting with 5.1 Mofo Rooted image provided in this thread:
First install/run sunshine. This process was painless and easy and I'm not going to waste my time typing instructions here.
Nuke the "Warning Message" boot logo
Instructions | Download
Just opened that folder and typed:
Code:
fastboot flash logo logo.bin
Installing TWRP
Instructions | Download
then do
Code:
adb reboot bootloader
fastboot flash recovery twrp.img
fastboot reboot
Now when you boot to recovery you will see TWRP!
Installing Apps
===============
Boot into recovery (TWRP)
Made backups of /system and /boot (didnt backup /data because I don't have an OTG cable or room on my internal storage - but you should!)
Copied backups to my PC
Copied the following to the TWRP folder on my phone (could put them anywhere doesnt matter):
xt1096-5.1-stock-20150820.zip
xt1096-5.1-debloat.zip
xt1096-5.1-CM-Stuff.zip
tk_gapps-modular-mini-5.1.1-20150816-signed.zip
xposed-v71-sdk22-arm-by-romracer-20150816.zip
Links to download are in the second post of this thread
Went into Wipe > Advanced Wipe and checked system and dvalik-cache and wiped them.
Installed all the zips from above in the listed order (all that matters is the xt1096-5.1-stock-20150820.zip goes first)
Rebooted
Phone sat and optimized for a long time
While waiting I downloaded:
XposedInstaller
AdAway
CF.Lumen
Dropped the APKs onto my phone once it was booted and ran them from file explorer.
Done.
=================================================
Here is the original info and links for Mofo 5.0 images:
The mofo image file with Xposed v65 baked in is listed below. It is based on the image posted by btdownloads7. It includes root, tether, BusyBox and SQLite3 while adding Xposed v65.
You need to flash an image with root from here: http://forum.xda-developers.com/showpost.php?p=60537982&postcount=1 to be able to follow the instructions below.
You also need to install the alpha Xposed apk from here: http://forum.xda-developers.com/attachment.php?attachmentid=3383776&d=1435601440 Download the apk to your phone, find it with your phone file manager and click on it to install. Do not try to install the framework from within the Xposed installer.
While in your root file manager, navigate to /data/dalvik-cache and delete both the "arm" and "profiles" folders. (This is needed one time due to a glitch in the alpha Xposed for Lollipop.) You must do this!
Connect your phone to your pc and issue the "adb reboot-bootloader" command to get into fastboot mode (or use the proper key combination on the phone to enter fastboot mode.)
Flash the image file with mofo as normal.
After mofo completes its work, enter "fastboot erase cache" from your pc to flush the system cache.
Once done, reboot the phone. The boot animation will end and seem to freeze for a minute or two, then it will start the upgrading/optimizing apps process. Once your phone is booted up, open the Xposed installer from the app drawer, install a module (like Gravity Box for LP) and enjoy!
Note: If you get system memory full errors after the reboot, you didn't delete the folders in /data/dalvik-cache as noted above; with luck you will be able to delete them in between error messages and reboot. Otherwise, you'll need to flash an image without Xposed and start over.
XT1096_5.0-tether-root-bb-sqlite3-XposedV65.img.7z - XT1096 image for use with mofo. Includes HDR fix, tether, root, busybox, sqlite3 and Xposed v65
http://forum.xda-developers.com/attachment.php?attachmentid=3383776&d=1435601440 - Link to Xposed Installer Alpha 4 needed for Xposed v65
XT1096_5.0-tether-root-bb-sqlite3-XposedV65-DeBloat.img.7z - Image with bloat removed, see this post for details: Post 169
XT1096_5.0-tether-root-bb-sqlite3-XposedV65-DeBloat-AdAway.img.7z - Image for AdAway users with symlink for hosts file, see this posrt for details: Post 188
Here is the info for 5.1 Mofo Images, updating, patching, etc.:
Thanks to @JulesJam and @Slack3r we have Android 5.1 for the XT1096 with mofo! Below are links to the 5.1 mofo image and patch files.
These images have tether enabled, root, Sqlite3, BusyBox, Xposed, CF.lumen and support for AirAudio, AdAway, iOS Emoji fonts and Viper4Android with the latest TK Gapps installed. Here are the main files:
5.1bins.7z - Kernel, modem and other 5.1 update files
xt1096-5.1-v3.1g-pkg.7z - Base image
You should save the base 5.1 image file. When there are updates in the future, patch files will be used to work with this base image.
@JulesJam has written an excellent guide for new users (and those who might need a refresher) here: Mofo Noob Guide
These images are for Android 5.1. If you are still running 5.0, here are instructions for upgrading to 5.1:
The following presumes that you already are running a rooted mofo version of Android 5.0. You shouldn't loose your data by making this upgrade, however, it is always wise to backup anything on your device that isn't also stored somewhere else. As usual, I can't be responsible if your phone malfunctions in some way. I have installed these files following the instructions below without any difficulty.
First, download the 5.1 base file and the 5.1 base image with patches.
Do not remove your SIM card, leave it installed.
Using your root file explorer (like ES Explorer with root enabled), delete everything in /data/dalvik-cache - YOU MUST DO THIS! Then reboot into bootloader mode.
Extract the files from the 5.1bins.7z archive and then run these commands:
Code:
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash recovery recovery.img
Then, immediately use mofo to flash the 5.1 image. Reboot your phone and enjoy Android 5.1!
The base image can be patched to enable/disable features. The patch files are listed below and instructions on how to apply them are here:
First, you need to have the Xdelta3 program:
xdelta3 for Windows x86
xdelta3 for Windows 64-bit
xdelta3 for Linux
For Linux, extract the files from the archive, enter the folder with the extracted files and run the following command to install xdelta3 to your system:
Code:
./configure && make && make install
For windows extract the xdelta3-3.0.9-x86.exe file from the zip and rename it to xdelta3.exe.
Put the patch file(s), the xdelta3 program and the base image mofo file into the folder where your mofo program file is.
Open a command window in this folder.
Enter the "dir" command (Without quotes. You should see your files listed including xdelta3, mofo, etc.)
For both Windows and Linux users enter the following cmd while in your mofo directory:
Code:
xdelta3 -d -s base_image_file patch_file
In other words, to patch the base image to add Xposed, your command would look like this:
Code:
xdelta3 -d -s xt1096-5.1-mofo-base-v2.img base-to-base_xp.patch
The patched image will be created and you can then flash that like normal.
Make sure the newly created image is the exact same size as the original image. If a patch for another image is applied to the wrong image, there will be an error message displayed. Even if there is an error, a patch file may be created but it will usually not be the same size as the original.
The patch files for the base image are included in the image archive
In the archive are patches to do the following:
3.1{x}--3.1{x}-de - Removes some apps from v3.1f image
3.1{x}--3.1{x}-cf-de - Removes some apps from v3.1f image, keeps CF.lumen
3.1{x]--3.1{x}-v4a - Adds Viper4Android to the image
3.1{x]--3.1{x}-v4a -cf-cmt-de - Adds Viper4Android to the image with some apps removed
The apps removed in the Debloat patch(es) are listed here:
Code:
3c_main (Moto Apps Manager)
3c_checkin (Moto Apps Connector)
3c_notification (Moto Apps Notifications)
3c_ota (Moto Apps Data Manager)
BodyGuardApp (Moto Alerts)
Books (Google Books)
CF.lumen
Chrome (Google Chrome)
Cloud (Verizon cloud storage)
Drive (Google Drive)
Ears (Google Sound Search)
ECID_VZW_Victara (Verizon CallerID pay service)
EditorsDocs (Google Docs)
EditorsSheets (Google Sheets)
EditorsSlides (Google Slides)
FaceLock (Face Unlock)
Google Earth (Google Earth)
Google HindiIME (Hindi keyboard)
Google PinyinIME (Pinyin keyboard)
Google PlayGames (Playgames (not playstore))
Hangouts (Google Hangouts)
Inbox (Google Inbox)
iWnnIME (iWnn keyboard)
Keep (Google Keep)
KoreanIME (Korean keyboard)
Maps (Google Maps)
Messenger (Not Messaging)
MotorolaConnect (Connect to watches or your PC)
Music2 (Google Play Music)
MyVerizon (My Verizon Mobile)
News & Weather (News & Weather widget)
Newsstand (Google Magazines)
Nflgamecenter (NFL App)
PlusOne (Google+)
Quickoffice (Google Quickoffice)
Talkback (Google Talkback)
Translate (Google Translate)
Trebuchet (CM Launcher)
Videos (Google Play Movies & TV)
VVM3 (Verizon Visual Voicemail)
VZMessages (Verizon Messages)
VzwEntitlementService (Not needed with tether in build.prop)
Wallet (Google Wallet)
YouTube (Google YouTube)
Tips:
The image includes AdAway support. If you want to use AdAway, go into the AdAway settings and set the location of the hosts file to /data/data/hosts
To change the bootup animation, place your desired bootanimation.zip file (not the installer zip) into /data/local/moodle and set the permissions to rwx rwx rwx (chmod 777) and owner:group u0_a40:u0_a40
To use iOS Emojis, follow these instructions:
Code:
If iOS Emojis are desired,
Copy /system/fonts/NotoColorEmoji.ttf.iOS to
/data/data/NotoColorEmoji.ttf
To restore the stock font,
Copy /system/fonts/NotoColorEmoji.ttf.stock to
/data/data/NotoColorEmoji.ttf
Or, just delete the file and the system will copy the
stock one into place at the next boot.
Changelog:
Code:
xt1096-5.1-v3.1f - 2015.08.06
- Major improvement to updated /system app cleanup
of apps in /data. Now takes 2 seconds instead of 90
Cleanup happens seamlessly, no reboot required
- Add CF.lumen v3.00, will add to debloat list if any requests
- Add CM's AudioFX, remove moto Audio Effects
- Add CM's Trebuchet Launcher, not in debloated image
On first boot of image with Trebuchet, you will be prompted to retain
the Google Now Launcher, select Always to keep the current launcher.
Launcher can be changed in Settings->Home
- Add patch to include Viper4Android v2.3.4.0 in image
Patch disables Selinux enforcing to allow V4A to work
Patch removes AudioFX
- Update Xposed Framework to v69
Minor changes don't require clearing dalvik-cache
- Updated Chrome to v44.0.2403.133
- Updated Docs to v1.4.292.15.35
- Updated Drive to v2.3.283.23.35
- Updated Moto App to v3.0.45
- Updated VZ Message+ to v5.6.5
- Patches now included with image & version update patch archive:
3.1e--3.1f.patch - Version update patch
3.1f--3.1f-v4a.patch - Patch to add Viper4Android
3.1f--3.1f-de.patch - Patch to debloat image
Requests for additional patch variations will be considered
xt1096-5.1-v3.1e - 2015.08.01
- Fixed incorrect permissions on Inbox causing fc
- Update Xposed Framework to v68
- Update Google Play Services to v7.8.95
- Update Chrome to v44.0.2403.128
- Update Connect to v2.06.16-pc-249
- Update My Verizon Mobile to v10.0.751
- Update Google Play Music to v6.0.195S.2109908
- Update Google+ to v6.0.0.99065591
- Update Maps to v9.12.1
- Update NFL Mobile to v12.0.28
- Update Photos to v1.2.1.99143001
- Update Translate to v4.0.0.RC08.99220384
- Updated debloat list
xt1096-5.1-v3.1d - 2015.07.29
- Fix problem with Connect force closing.
- Add Google Camera in addition to stock Moto Camera
xt1096-5.1-v3.1c - 2015.07.28
- Made change in updated play store app cleanup to account for
unexpected data in /data/system/packages.xml possibly causing
system failure to set correct processor parameters. Possible
infinite loop corrected.
- Added Google Inbox, rolled in updated versions of Google Photos,
Verizon Cloud, Message+, MyVerizon.
- Add Google Inbox to debloat list.
xt1096-5.1-v3.1b - 2015.07.25
- Fixed problem where apps updated by play store could be incorrectly
reverted to /system version which was actually older.
- Rolled into /system latest versions of: Google Keep, Maps, YouTube, Wallet.
- Restore stock Email app that was accidentally removed.
xt1096-5.1-v3.1a - 2015.07.21
- Fixed some directory permissions.
- Restored stock mms app to image.
- Rolled updated versions of apps into system:
NFL Game Center
Google Docs
Google Slides
Verizon Message+
- Added functionality for system to automatically remove
obsolete copies of apps in /data/app when new image has
newer or equal version of those apps (same as custom Roms.)
Release 5 - 2015.07.20
- Base file name: xt1096-5.1-v3.1.img
- Exchange is enabled in Gmail, old stock email was removed.
- Add PA-Gapps Stock package 20150717 - updates all Google
apps to versions available as of the date noted. Thanks
to TKruzze & osm0sis @ xda for their work.
- Updated Motorola and Verizon apps are integrated into image.
- Removed deprecated Spotlight player
- Installed AdAway and Xposed Installer into /system
- Corrected permissions on auto created /data/data/hosts file
- Install Air Audio in base image. (Future MMU will give option
to disable/enable this as well as other apps.)
- Updated Xposed to v67 (nothing major changed from v65)
- Made iOS Emoji support permanent by creating a symlink.
The Emojis will not be available until the second time
booting with this image.
If iOS Emojis are desired,
Copy /system/fonts/NotoColorEmoji.ttf.iOS to
/data/data/NotoColorEmoji.ttf
To restore the stock font,
Copy /system/fonts/NotoColorEmoji.ttf.stock to
/data/data/NotoColorEmoji.ttf
Or, just delete the file and the system will copy the
stock one into place at the next boot.
Release 4 - 2015.07.15
- Base file name: xt1096-5.1-v3.0.img
- Fix security context and ownership on BusyBox symlinks
- Add symlink for /system/etc/resolv.conf to /data/data/resolv.conf
Does not require user action, allows BusyBox DNS resolution by
creation of /data/data/resolv.conf file. Make one like the
following if you want to use Google's nameservers for DNS resolution
in adb shell programs like nslookup, traceroute, etc. Remember.
the adb shell nslookup, etc. only work after you su to root.
nameserver 8.8.8.8
nameserver 8.8.4.4
nameserver 4.4.4.4
- Add Better Battery Stats XDA version as a system app
- Add /system/etc/mofobuild.prop with name of image installed
- Alpha version of Mofo Utility
Release 3 - 2015.07.10
- Base file name: xt1096_5.1_mofo-base-v2.img
- Fix broken BusyBox installation
Release 2 - 2015.07.09
- Base file name: xt1096_5.1_mofo-base.img
- Correct security context on /system/etc/install-recovery.sh to value
in original ROM instead of value as (not) set by SuperSU installer
causing script to not run at boot.
- Make AdAway support the default. Added functionality to create
/data/data/hosts file on boot, if it doesn't exist, for users who
don't wish to use AdAway ensuring there will be no problems in
resolving localhost for apps/processes that might use that.
- Shorten and simplify names of base and patch files.
- Upgrade SuperSU from v2.46 to v2.49
Initial Release - 2015.07.05
- Base file name: XT1096_5.1-tether-root-bb-sqlite3.img
XDA:DevDB Information
Mofo XT1096 5.x Images, ROM for the Moto X 2014
Contributors
mikeoswego
ROM OS Version: 5.1.x Lollipop
Based On: Stock
Version Information
Status: No Longer Updated
Created 2015-05-04
Last Updated 2017-06-28
Updated 2016.01.21 - xt1096-5.1 & 23.32-25-5x TWRP based zips
The zips attached below are available for use with TWRP on the xt1096-5.1 & 23.32-25-5x images:
xt1096-5.1-Viper4Android.zip - Adds Viper4Android (disables selinux security and removes Audio Effects app)
xt1096-5.1-Mail-Exch2.zip - Restores stock email & exchange2, included in xt1096-5.1-23.32-25-5_3. Flash after flashing GApps
xt1096-5.1-Rem-Xposed.zip - Removes Xposed from ROM, use only after ROM has been started and setup is complete
See post 886 for a flashable alternate boot logo and boot animation.
Useful Links:
CF.lumen xda thread - Or search the Playstore fo CF.lumen
BetterBatteryStats xda thread - Get the BetterBatteryStats installer here
TWRP for Motorola Moto X 2014 - TWRP info page for MotoX 2014
TWRP for victara - TWRP download page
Open GApps for Android 5.1 - Google Apps installer
AdAway xda thread - Get AdAway from here
Was first!
Are the steps the same to flash the updated image with the boot animation or can I just flash and wipe cache. I literally just booted the previous Xposed image after installing GravityBox and a few other modules and this is the first thing I see lol.
Thanks so much for the image though, it took a while to boot and start apps but it hasn't given me any issues otherwise yet.
fakieskr8333 said:
Are the steps the same to flash the updated image with the boot animation or can I just flash and wipe cache. I literally just booted the previous Xposed image after installing GravityBox and a few other modules and this is the first thing I see lol.
Click to expand...
Click to collapse
If you are already running the previous image with Xposed, you can just flash the new one in the normal way with mofo, no special steps needed.
Nvm
That's some animation! Sometimes I reboot just to watch it.
I don't seem to have the new animation....everything else is working fine though..
Empty \data folder
I didn't seem to have anything in my \data folder so I proceeded with flashing the image. Now, it appears I have the memory issue. Also, the apk for the xposed intaller seems to be for Alpha 2 - does that matter?
Thanks for everything!
Updated without any issues at all. Now time to get crazy with modules! Thanks again!
dudicle said:
I didn't seem to have anything in my \data folder so I proceeded with flashing the image. Now, it appears I have the memory issue. Also, the apk for the xposed intaller seems to be for Alpha 2 - does that matter?
Thanks for everything!
Click to expand...
Click to collapse
Hmmm. Found 'em! Wonder if I needed root to see those files in the first place. Since this was my first flash away from unrooted stock, I didn't have root yet. Anyhow, deleted them and reflashing the image. So far so good...
I can't seem to be able to install the Xposed Framework after I flashed this image. Is there something I'm missing??
dudicle said:
Hmmm. Found 'em! Wonder if I needed root to see those files in the first place. Since this was my first flash away from unrooted stock, I didn't have root yet. Anyhow, deleted them and reflashing the image. So far so good...
Click to expand...
Click to collapse
Right you have to have root to be able to delete the dalvik-cache files. I'll edit the first post.
Aroch925 said:
I can't seem to be able to install the Xposed Framework after I flashed this image. Is there something I'm missing??
Click to expand...
Click to collapse
The framework is already installed in the image. You can't install the framework from the Xposed installer for two reasons. First, this root doesn't open up /system for writing (which Xposed normally needs for installation), and two, this alpha version of Xposed for Lollipop doesn't install the framework on its own anyway, it has to be flashed from recovery (but we don't have a recovery yet so it has to be baked in.) Hope that makes it more clear!
mikeoswego said:
The framework is already installed in the image. You can't install the framework from the Xposed installer for two reasons. First, this root doesn't open up /system for writing (which Xposed normally needs for installation), and two, this alpha version of Xposed for Lollipop doesn't install the framework on its own anyway, it has to be flashed from recovery (but we don't have a recovery yet so it has to be baked in.) Hope that makes it more clear!
Click to expand...
Click to collapse
So does that mean I can't actually use Xposed yet?
Aroch925 said:
So does that mean I can't actually use Xposed yet?
Click to expand...
Click to collapse
It means you just go to the download section and choose the modules you want to install. The installer can't install the framework but it does install the modules you want to use. :good:
tjohnstone3 said:
I don't seem to have the new animation....everything else is working fine though..
Click to expand...
Click to collapse
The new animation is quite different so you would know if you had it. I had the previous version of this image with Xposed linked in the OP for a few minutes after first posting it. The file you dl'd should have been named XT1096_5.0-tether-root-bb-sqlite3-Xposed.img.rar. If not, dl it again from the link in the OP.
dudicle said:
Also, the apk for the xposed intaller seems to be for Alpha 2 - does that matter?
Click to expand...
Click to collapse
The Xposed framework is alpha 4 but the installer is only alpha 2 because no changes have been needed in that part.
What is the fix for low memory. I flashed this img with mofo but I cant seem to resolve the low memory issue? Thanks
---------- Post added at 12:46 AM ---------- Previous post was at 12:39 AM ----------
Jah Ruggz said:
What is the fix for low memory. I flashed this img with mofo but I cant seem to resolve the low memory issue? Thanks
Click to expand...
Click to collapse
Disregard..I did not realize I had a recovery that I could wipe cache from. I will try that and see if it works.
Thanks for the image- love it, well documented tutorial helped heaps. Do you plan on updating this thread with new updates or by chance taking feature requests?
Cheers - Harrison

[Rom] [Ufirm_Flat_QE2_Hybrid_Nougat_Rom_FlashFire_Install][Status Official For All]

Latest Ufirm QE2 Nougat Firmware For The S7 Flat Only
This well give you a Customizable NonRooted Rom that uses stock boot.img not the eng boot image so there is no lag and it will pass safetynet checks and samsung pay will work
Give this guy @umaro some thanks he worked on this until it became reality even when I gave up​
Files To Download
Odin.zip
ADB_Root_G930U_QE2Files.zip
UFIRM_G930_Odin_Firmware.zip
FlashFire_Flashable_G930UFirmware.zip
UFirm_Multi_Carrier_Hybrid_NoNaMe_PS_BS_Free_G930U_QE2_V2.zip
These first 2 step must be done first unless you are on my previous version of this rom or my carrier specific rom that do not have root or if your unsure just do this first
This Will Wipe Your Phone
1. Unzip UFIRM_G930_Odin_Firmware.zip and flash all files in odin
2. Go through setup ignore invalid sim message and skip adding accounts
3. Goto Step 3 Below
If you are on one of my previous version of this rom or my carrier specific rom
1. Unzip UFIRM_G930_Odin_Firmware.zip
2. Use odin to flash BL and CP
3. Unzip ADB_Root_G930U_QE2Files.zip
4. Flash EngBoot image with odin
5. Root Phone. Im not going to have half a page about rooting there is an entire rooting thread here. The Eng Boot.img can be found in the UFIRM_QD2_Modified_Nougat_Firmware Folder
6. Unzip FlashFire_Flashable_G930UFirmware.zip
7. Copy AP_FlashFire_Only_G930U_QE2_Firmware.tar.md5 to your phone
8. Copy UFirm_Multi_Carrier_Hybrid_NoNaMe_PS_BS_Free_G930U_QE2_V2.zip to your phone
9. Open FlashFire and click Add Zip and choose UFirm_Multi_Carrier_Hybrid_NoNaMe_PS_BS_Free_G930U_QE2_V2.zip make sure to check mount system
10. Now in FlashFire click Add Firmware and choose AP_FlashFire_Only_G930U_QE2_Firmware.tar.md5 select all the partitions
11. Make sure Inject SuperSu is not selected
12. Click Add Wipe and choose Wipe Dalvik Cache and Cache and choose Format Cache Also select wipe SuperSU image. Make sure wipe is at end of flash sequence. The sequence should be AP file first then Zip second and Wipe cache last
13. Now Choose Flash
14. Phone will take Up to 20 minutes to boot
15. Reflashing Zip Will Require Flashing The AP File In FlashFire At The Same Time
16. Do not use Package Disabler Pro if you Choose NoNaMe mods in Aroma
MODS- (NoNaMeRomControl)
3minitbattery
Speed meter
Status bar mods
Center clock
Wifi/signal bar mods
Color change icon mod
Custom backgrounds
Notification drop-down
Incallui background
Gif in notification drop-down
Change/remove carrier names
And much more...
THANKS AND CREDITS
@jds3118 for testing and providing files and bootlooping his phone countless times for me
Gharrington for his awesome 3minitbattery mod...
NoNaMe rom development team for their incredible mods and rom control app...
@malbert16442 for his black themes
Xda for all the great guides to accomplish this...
Kernel source
RomControl Source
In the OP I had the ADB_Root_G930U_QE2Files.zip linked to the ADB_Root_G935U_QE2Files.zip zip so please make sure you have the ADB_Root_G930U_QE2Files.zip when downloading. Its fixed in the OP now so just double check
I recommend everyone put the Flashfire AP zip and Rom Zip on your internal storage as the AP file is so large that it may not be read properly do too limitations of some SD Cards. When you select AP file in Firmware there should be 4 partitions that are selected. If not then you have a bad download or need to have AP file on internal storage
Thanks for all your hard work . I just installed this so far so good but I am missing Wi-Fi calling. Is that normal or am I just not looking in the correct place? Thanks
ledezma2003 said:
Thanks for all your hard work . I just installed this so far so good but I am missing Wi-Fi calling. Is that normal or am I just not looking in the correct place? Thanks
Click to expand...
Click to collapse
You may have to flash the TMO version of this rom
jrkruse said:
You may have to flash the TMO version of this rom
Click to expand...
Click to collapse
Ok will try that when I get a chance. Thanks again.
Thx for an awesome rom.
Sorry if this question is asked before but couldn't find a solution (checked Verizon thread as well).
I am running Playstore version ROM and everything is working fine except Video Recording.
Photo is fine but when I record a video with included Camera NX, it only plays sound and the screen is either still or black.
I have been taking a needed break. I will update all my s7 roms including this one in the next few days
Nice
That rom can flash for g930p? tks your work!!
@jrkruse
Thanks for all your contributions to this device. I just bought this device and I've been diving through the forums trying to gather as much info on this locked down device.
Could you provide me with just the boot images that don't check the system image and from what model/rom are they from?
Oh and could you provide the partitions locations? The latest roms have an updated Knox that blocks SU from doing it's thing and I have to perform everything via adb (eng boot).
Blank screen
Hello,
I am on your custom rom and the phone was working fine for a day. After I restarted the phone I am not able to see the lockscreen. Its just blank. I do hear the sound of taking a screenshot when I press the buttons and I also can see the " shut down, restart, emg mode" buttons when I hold the power button but no lockscreen. I tried running the recovery boot img but nothing changed.
There is some kind of issue at the locksceen after a restart.
I'm Stuck
jrkruse said:
Latest Ufirm QE2 Nougat Firmware For The S7 Flat Only
This well give you a Customizable NonRooted Rom that uses stock boot.img not the eng boot image so there is no lag and it will pass safetynet checks and samsung pay will work
Give this guy @umaro some thanks he worked on this until it became reality even when I gave up​
Files To Download
Odin.zip
ADB_Root_G930U_QE2Files.zip
UFIRM_G930_Odin_Firmware.zip
FlashFire_Flashable_G930UFirmware.zip
UFirm_Multi_Carrier_Hybrid_NoNaMe_PS_BS_Free_G930U_QE2_V2.zip
These first 2 step must be done first unless you are on my previous version of this rom or my carrier specific rom that do not have root or if your unsure just do this first
This Will Wipe Your Phone
1. Unzip UFIRM_G930_Odin_Firmware.zip and flash all files in odin
2. Go through setup ignore invalid sim message and skip adding accounts
3. Goto Step 3 Below
If you are on one of my previous version of this rom or my carrier specific rom
1. Unzip UFIRM_G930_Odin_Firmware.zip
2. Use odin to flash BL and CP
3. Unzip ADB_Root_G930U_QE2Files.zip
4. Flash EngBoot image with odin
5. Root Phone. Im not going to have half a page about rooting there is an entire rooting thread here. The Eng Boot.img can be found in the UFIRM_QD2_Modified_Nougat_Firmware Folder
6. Unzip FlashFire_Flashable_G930UFirmware.zip
7. Copy AP_FlashFire_Only_G930U_QE2_Firmware.tar.md5 to your phone
8. Copy UFirm_Multi_Carrier_Hybrid_NoNaMe_PS_BS_Free_G930U_QE2_V2.zip to your phone
9. Open FlashFire and click Add Zip and choose UFirm_Multi_Carrier_Hybrid_NoNaMe_PS_BS_Free_G930U_QE2_V2.zip make sure to check mount system
10. Now in FlashFire click Add Firmware and choose AP_FlashFire_Only_G930U_QE2_Firmware.tar.md5 select all the partitions
11. Make sure Inject SuperSu is not selected
12. Click Add Wipe and choose Wipe Dalvik Cache and Cache and choose Format Cache Also select wipe SuperSU image. Make sure wipe is at end of flash sequence. The sequence should be AP file first then Zip second and Wipe cache last
13. Now Choose Flash
14. Phone will take Up to 20 minutes to boot
15. Reflashing Zip Will Require Flashing The AP File In FlashFire At The Same Time
16. Do not use Package Disabler Pro if you Choose NoNaMe mods in Aroma
MODS- (NoNaMeRomControl)
3minitbattery
Speed meter
Status bar mods
Center clock
Wifi/signal bar mods
Color change icon mod
Custom backgrounds
Notification drop-down
Incallui background
Gif in notification drop-down
Change/remove carrier names
And much more...
THANKS AND CREDITS
@jds3118 for testing and providing files and bootlooping his phone countless times for me
Gharrington for his awesome 3minitbattery mod...
NoNaMe rom development team for their incredible mods and rom control app...
@malbert16442 for his black themes
Xda for all the great guides to accomplish this...
Kernel source
RomControl Source
Click to expand...
Click to collapse
I followed the directions up to Step 7.
For the life of me I can not get the AP file to copy to my SD card. Yes I have enough space on it and I can get the ROM copied.
I tried copying the AP file with a file explorer, on my PC, external card reader. Every time I try, it gets to about 95-99% and says "copy failed".
I know it says flashfire only, but is that my only option?
Reegs said:
I followed the directions up to Step 7.
For the life of me I can not get the AP file to copy to my SD card. Yes I have enough space on it and I can get the ROM copied.
I tried copying the AP file with a file explorer, on my PC, external card reader. Every time I try, it gets to about 95-99% and says "copy failed".
I know it says flashfire only, but is that my only option?
Click to expand...
Click to collapse
In my case I created a folder named Download in Internal Storage and copied Zip and AP files there. I didn't have trouble coping files there.
From my experience & guess, you may still have old files & settings even though you flashed U-firm files Step 1-2.
Try to access recovery mode and do factory reset and see if this helps. Make sure you backup all important files to External SD because it will factory reset.
So I rooted my phone using Araltd's guide in this forum. I've got a couple of questions about this rom...
1. If I were to flash this rom to my device, would it remove my root access?
2. What's device performance like? After rooting, my device is very slow and buggy. Will this fix that?
3. Will my device still be full of T-Mobile's bloatware?
Thanks!
wolfpls254 said:
So I rooted my phone using Araltd's guide in this forum. I've got a couple of questions about this rom...
1. If I were to flash this rom to my device, would it remove my root access?
2. What's device performance like? After rooting, my device is very slow and buggy. Will this fix that?
3. Will my device still be full of T-Mobile's bloatware?
Thanks!
Click to expand...
Click to collapse
1. Yes, it will remove Root Access but you can still use ADB to do root stuff like push / pull files.
2. Since it will use stock boot instead of ENG boot, it will fix the lag issue.
3. This is U (universal) firmware so it won't have Tmobile bloat but it will have Samsung bloat/apps. During the install you can also choose de-bloat level too. From my experience BS-Free (2nd one), is both lightweight and stable. If you go with Playstore level (most lightweight, replace Samsung Apps with Google ones), you will have trouble with camera.
kyungone said:
1. Yes, it will remove Root Access but you can still use ADB to do root stuff like push / pull files.
2. Since it will use stock boot instead of ENG boot, it will fix the lag issue.
3. This is U (universal) firmware so it won't have Tmobile bloat but it will have Samsung bloat/apps. During the install you can also choose de-bloat level too. From my experience BS-Free (2nd one), is both lightweight and stable. If you go with Playstore level (most lightweight, replace Samsung Apps with Google ones), you will have trouble with camera.
Click to expand...
Click to collapse
Do you know how this rom compares to the QF6 one which seems to be a bit more popular?
wolfpls254 said:
Do you know how this rom compares to the QF6 one which seems to be a bit more popular?
Click to expand...
Click to collapse
The QF6 ROM you mentioned is T-mobile firmware so it will have Tmobile apps. Most of them can be removed from ROM install or disabled after.
Other than that there's no performance difference.
If you want Tmobile like environment with Tmobile update schedule, go with T-mobile one. If you want less carrier apps, go with U-Firmware one.
I will no longer be updating my s7 threads until the time Oreo is released with root method. For now I have worked with @stang5litre to bring my non-root method to his amazing rom. He currently has a nougat release found here http://stang5litre-roms.proboards.com/
I keep getting samsung pay connection error. any fixes? i tried factory reset and reset settings, but the app still doesnt work. do i have to reflash the rom?
amdeng said:
I keep getting samsung pay connection error. any fixes? i tried factory reset and reset settings, but the app still doesnt work. do i have to reflash the rom?
Click to expand...
Click to collapse
If you at any point tried to root it or flashed the modified boot image then you are no longer passing the safteynet checks, my suggestion is to do a clean install and see if it works then try it again making sure you don't root after you are done installing this rom.

[Guide] Deodex SM-T285 (Android 5.1.1, API Level 22)

Hi everybody,
I did not want to flash a custom ROM on my new SM-T285 (Android 5.1.1, API Level 22) so that I could use Xposed.
Instead I deodexed my own stock ROM --without going into boot loop-- using knowledge and tools from XDA members. Below are the steps I took, with the links to where you can find the original member posting and/or their instructions. Please make sure to "thank" the person who posted the information and/or tool
Assuming you are rooted with TWRP installed, these steps will hopefully work for you as well.
STEP 1: Flash Jedid's SM-T285 Kernal (https://forum.xda-developers.com/ga...rnel-galaxy-tab-7-0-2016-lte-sm-t285-t3474967)
STEP 2: Unpack the system folder from your TWRP nandroid (https://forum.xda-developers.com/showpost.php?p=53913623&postcount=22)
STEP 3: Understand you will need to get the latest oat2dex.jar file (https://forum.xda-developers.com/showpost.php?p=61284936&postcount=395)
STEP 4: Understand what deodexing tool works well for Samsung (https://forum.xda-developers.com/showpost.php?p=68432791&postcount=757)
STEP 5: Download svadev's deodexing tool (https://forum.xda-developers.com/galaxy-s5/general/tool-deodex-tool-android-l-t2972025)
STEP 6: Download latest oat2dex.jar file (https://github.com/testwhat/SmaliEx/releases)
Note: I downloaded all the SmaliEx files and dumped them into the folder with "SVADeodexerForArt.exe" in it (it replaced the oat2dex.jar file too)
STEP 7: When finished using SVADeodexer, create a flashable zip (https://forum.xda-developers.com/showpost.php?p=65481181&postcount=722)
Note: do not include in your zip, the "Dex" and "Odex" files created by SVADeodexer, just the app, priv-app, and framework folders.
STEP 8: Save the zip file you created to your phone internal memory, and flash via TWRP.
After flashing the new system folder (containing the deodexed folders: app, priv-app, and framework) using TWRP; I cleared the delvik cache and restarted my "tablet." It took a long time to load to the "Android is starting..." screen, and I was eventually able to log in. After logging in, I confirmed the the new system folders installed, and yes, my device is truly deodexed --not a single odex file.
Please note, I am not a developer, and please make sure you create a complete backup before doing anything.
---------------UPDATE (Aug 16, 2017)---------------
My phone/tablet is still working great since I've deodexed it. I have since flashed a custom version of @rovo89 's Xposed framework, which was customized by @wanam. I hope to find time in the near future to compile the outstanding posts where I gained the knowledge on how to do these things, and obtained the resources to do them, and give the authors and developers proper credit. In the meantime, if you own an SM-T285 and are eager to install Xposed, I would suggest starting with wanam's custom Xposed module (https://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960), which worked for me. The key I found is to use a certain version, which did not cause my phone to boot loop. I'll need to go through my files to confirm which version this was. Additionally, I also recommend debloating using Galaxy Cleaner Lollipop DeBloater from @blaz1nr (https://forum.xda-developers.com/galaxy-s6/general/script-galaxy-cleaner-lollipop-debloater-t3156007). It worked like a charm for me at that point when I used it, having achieved the steps I mentioned above. I did use the script as is, and it really got rid of a lot of stuff I did not know was safe to get rid of.
bro trying your method on my Galaxy Note 3 Neo SM-N750 hl3gxx , running 5.1.1 , but no success , i have used svadev tool , it showed success but when pushing back to system its giving bootloops
used your link for Template zip , that causing bootloop too , so instead of zip , i did copy of app/priv-app/framework to my internal storage , went in TWRP , delete those three folders first from system and pasted the deodex one from internal storage

Solved - Boot S10 into rooted ROM without requiring 3 buttons pressed

I have purchased my Samsung S10 Exynos and successfully rooted it using the only possible ways that have seems to be available so far. I have gained root, but I was wondering if anyone has solved the issue of having to turn the device on with all 3 keys held down at the same time. I understand that this is because the rooted version of the phone has be installed on the recovery of the phone, but I hope that there becomes a way to turn on the phone with root and use only the power button. I check from time to time, but it seems that this has not been solved yet. If anyone can find a solution for me so that I do not have to keep searching then I will reward them $100. An idea that I had is if there was a way to modify the power button to boot into recovery by itself? I believe this would be impossible but if anyone could think of a way to do that then that would solve the problem. I am okay with never being able to unroot the device if this would be the case.
How often do you cold boot?
reboot:
- Magisk boot menu
- adb reboot recovery
DHGE said:
How often do you cold boot?
reboot:
- Magisk boot menu
- adb reboot recovery
Click to expand...
Click to collapse
Hello, thank you for the suggestion. I thought about that idea already and I forgot to mention it in my post. I am looking for a way to do it via a cold boot. I know about the reboot into recovery method already, and I know of a way to map the power button to reboot into recovery if held down, but I am looking for a way to cold boot into recovery with just the power button.
I like your idea, but if there was a way to do it as a cold boot then that is ideally what I'm looking for. Your method would work if there was a way to just keep the phone shut down and wait until I hold the power button to turn it on and then it boot into recovery. If you can think of a way to do that then let me know.
The reason I am seeking this is because I root the S10 out to have a proprietary app on it and the app requires root to function properly. I need the power button to boot with root on the S10 so that it will always do so and my employees / customers will not access the non-rooted side of the phone by accident. The 3 button combination is too difficult, so I would need to resort so either a S8 or S9 if the S10 won't allow power button only to boot with root access. The app that I make uses a great amount of battery life so I need the ability to shut down the phone and cold boot it back into recovery. Thanks.
Hi, I assume you have rooted using the magisk-patched-recovery method (patched AP file) and if memory serves and from what I am re-reading this method does require the 3-button-combo to boot to rooted system.
When I first got my s10 and rooted this was the only method at the time, but then came custom kernels with built-in magisk.
With this method from power menu if I...
- reboot, phone will reboot to rooted system.
- power off, the power on button will boot to rooted system.
In fact I'm not sure how/if I can boot to non-rooted system with this method.
I currently on custom rom AmbasadiiRom 2.2 with AmbasadiiCruel Kernel G97xF-v3.10.
There are a few custom kernels that have built-in magisk. You will have to check rom compatibility but believe they work on samsung stock based firmware/roms, AmbasadiRomi is based on stock firmware.
- Cruel Kernel
- ThundeRStormS kernel
If you like I can provide a step-by-step, but you will lose all data as it will require flashing stock unpatched firmware, unpatched twrp in odin then custom rom (optional - depending on if the custom kernel does work on stock firmware) & custom kernel.
pjc21 said:
Hi, I assume you have rooted using the magisk-patched-recovery method (patched AP file) and if memory serves and from what I am re-reading this method does require the 3-button-combo to boot to rooted system.
When I first got my s10 and rooted this was the only method at the time, but then came custom kernels with built-in magisk.
With this method from power menu if I...
- reboot, phone will reboot to rooted system.
- power off, the power on button will boot to rooted system.
In fact I'm not sure how/if I can boot to non-rooted system with this method.
I currently on custom rom AmbasadiiRom 2.2 with AmbasadiiCruel Kernel G97xF-v3.10.
There are a few custom kernels that have built-in magisk. You will have to check rom compatibility but believe they work on samsung stock based firmware/roms, AmbasadiRomi is based on stock firmware.
- Cruel Kernel
- ThundeRStormS kernel
If you like I can provide a step-by-step, but you will lose all data as it will require flashing stock unpatched firmware, unpatched twrp in odin then custom rom (optional - depending on if the custom kernel does work on stock firmware) & custom kernel.
Click to expand...
Click to collapse
Awesome. Your solution sounds perfect for what I was looking for. Yes, I got my S10 back over a year ago and rooted it with patched AP file and magisk. I was only able to find that method even up until yesterday. I would like a step by step if you are able to quickly put one together. If it works then I am glad to grant you the reward for your help. I am willing to do this in the easiest way possible, even if it requires wiping data. I never used the phone so wiping is no problem at all. I am looking to do this to several devices so the easiest and fastest way would be the best. I will look into your comments and see if I can figure out doing this over this weekend. Will keep everyone updated.
pjc21 said:
Hi, I assume you have rooted using the magisk-patched-recovery method (patched AP file) and if memory serves and from what I am re-reading this method does require the 3-button-combo to boot to rooted system.
When I first got my s10 and rooted this was the only method at the time, but then came custom kernels with built-in magisk.
With this method from power menu if I...
- reboot, phone will reboot to rooted system.
- power off, the power on button will boot to rooted system.
In fact I'm not sure how/if I can boot to non-rooted system with this method.
I currently on custom rom AmbasadiiRom 2.2 with AmbasadiiCruel Kernel G97xF-v3.10.
There are a few custom kernels that have built-in magisk. You will have to check rom compatibility but believe they work on samsung stock based firmware/roms, AmbasadiRomi is based on stock firmware.
- Cruel Kernel
- ThundeRStormS kernel
If you like I can provide a step-by-step, but you will lose all data as it will require flashing stock unpatched firmware, unpatched twrp in odin then custom rom (optional - depending on if the custom kernel does work on stock firmware) & custom kernel.
Click to expand...
Click to collapse
I just read some info on the links you provided and i think i can figure it out. if i have any trouble then ill let you know. Dont worry about a step by step for now unless I have any trouble. Thanks!
Here is a bit of a step-by-step for Samsung s10 Exynos Model:SM-G973F
Info below is based on using December Security patch: 2020-12-01 firmware G973FXXS9DTK9 (Android 10) and Ambasadii Rom
NOTICE: The easiest and fastest way would probably be flashing kernel with stock firmware/rom. I have only done custom (but stock based) roms with kernel so am assuming the steps (5a.) for stock firmware/rom, you may want to post in chosen kernel thread to confirm if those steps are correct.
- both kernels I mentioned say they are compatibly with stock roms & AmbasadiiCruel Kernel is based on Cruel Kernel so I assume that would also work on stock rom.
This assumes you have already unlocked your bootloader, if not check this Recovery thread under Instructions: Odin (windows) - steps 1-6 for how to unlock bootloader.
1. Download all files needed to pc.
- Current latest firmware G973FXXS9DTK9, I use frija tool as downloading from samfirmware.com is very slow.
Enter Model, CSC, check the auto box & click check update and download.
Once complete unzip with 7Zip or preferred zip tool.
- In Recovery thread download latest twrp for device, is this case for S10 G973F latest twrp is - twrp-3.5.0_9-1-beyond1lte.img.tar
Under Instructions: Odin (windows) download
- Odin v3.14.1
- avb disabled vbmeta.tar
- click link to multidisabler-samsung-2.* and download latest version from there, currently multidisabler-samsung-3.1.zip
If sticking with stock and custom kernel
- easiest one looks like it would be Cruel kernel or AmbasadiiCruel kernel.
- check kernel thread of choice for compatibility with stock firmware and specific install instructions.
For custom rom in this example for Ambasadii rom
- Download files from Ambasadii rom site
- ROM.G97xF.XXS9DTK9-v2.2.by.ambasadii.zip
- mods_DTJA-v1.3.4.zip
- magisk_safetynet_fix.zip
- AmbasadiiCruel-G97xF-v3.10.zip (rom does include previous kernel 3.9 but this one is updated to latest magisk 21.2)
Bootlogo patcher - this will get rid of the warning about bootloader being unlocked when booting phone. (optional)
TWRP_Bootlogo_patcher.zip
Copy the below files to phones external SDCard
- multidisabler-samsung-3.1.zip
- TWRP_Bootlogo_patcher.zip (optional)
- chosen kernel zip - if sticking with stock
Custom Rom files
- ROM.G97xF.XXS9DTK9-v2.2.by.ambasadii.zip
- mods_DTJA-v1.3.4.zip
- magisk_safetynet_fix.zip
- AmbasadiiCruel-G97xF-v3.10.zip
2. Flashing stock firmware - Odin
- Open Odin on pc
- Turn off the phone
- Use vol down + bixby, then connect usb cable to phone from pc to start the phone in download mode, press vol up to confirm and go to download mode.
- In Odin under log you should see added, I also like to turn off auto reboot under the options tab and do manual reboot once complete but that's up to you.
- Add BL, AP, CP & CSC from the unzipped firmware downloaded in step 1. The AP & CSC can take a little time as they are larger files.
- Once all files added click start and wait until complete, you should see SUCCESS in the top left area once done.
- If you turned off auto-reboot then unplug usb and do manual reboot by pressing vol down + power for 7 seconds, else phone should reboot automatically then unplug.
3. Once phone boots up
- complete setup and connect to Wi-Fi or data
- skip adding Google & Samsung accounts.
- enable developer settings & check OEM unlock is on.
- turn off the phone.
4. Flashing TWRP Recovery - Odin
- In the Recovery thread under Instructions: Odin (windows) continue on from step 8 including formatting data and flashing multidisabler zip which you copied to SDCard.
- in twrp go back to wipe and select advanced and wipe data, cache & dalvik-cache
5a. If sticking with stock & custom kernel - Read NOTICE at top of post
Assumed Steps
- Still in twrp recovery go back to main menu
- select install and flash kernel zip, then TWRP_Bootlogo_patcher.zip
- Not sure if magisk_safetynet_fix is needed or works on stock, would need to confirm in Ambasadii thread.
- go back to main menu and select reboot & system
- give the phone a few minutes to start, and then complete setup including adding your accounts.
- once setup is complete open magisk and it will run additional setup, and then phone will reboot
- done
OR
5b. If flashing Custom Rom & Kernel - steps below for Ambasadii Rom
- Still in twrp recovery go back to main menu
- select install and flash ROM.G97xF.XXS9DTK9-v2.2.by.ambasadii.zip, choose options in aroma - once the install is complete exit back to twrp recovery
- select and flash mods_DTJA-v1.3.4.zip, then magisk_safetynet_fix.zip, then AmbasadiiCruel-G97xF-v3.10.zip, then TWRP_Bootlogo_patcher.zip
- once you have flashed all files go back to main menu and select reboot & system
- give the phone about 8 minutes to start, and then complete setup including adding your accounts.
- once setup is complete open magisk and it will run additional setup, and then phone will reboot
- done
6. If you went with Ambasadii Rom
- you will then notice status bar icons are pushed to the right behind the camera
- open rom control, grant superuser rights
- select status bar/options and play around with notch adjustments and positions
- can be a little confusing to start but play around and you'll get the hang of it.
Hope this info helps, let me know if you need any clarification/detail to any of the steps
Also no need for reward, happy to help
pjc21 said:
Here is a bit of a step-by-step for Samsung s10 Exynos Model:SM-G973F
Info below is based on using December Security patch: 2020-12-01 firmware G973FXXS9DTK9 (Android 10) and Ambasadii Rom
NOTICE: The easiest and fastest way would probably be flashing kernel with stock firmware/rom. I have only done custom (but stock based) roms with kernel so am assuming the steps (5a.) for stock firmware/rom, you may want to post in chosen kernel thread to confirm if those steps are correct.
- both kernels I mentioned say they are compatibly with stock roms & AmbasadiiCruel Kernel is based on Cruel Kernel so I assume that would also work on stock rom.
This assumes you have already unlocked your bootloader, if not check this Recovery thread under Instructions: Odin (windows) - steps 1-6 for how to unlock bootloader.
1. Download all files needed to pc.
- Current latest firmware G973FXXS9DTK9, I use frija tool as downloading from samfirmware.com is very slow.
Enter Model, CSC, check the auto box & click check update and download.
Once complete unzip with 7Zip or preferred zip tool.
- In Recovery thread download latest twrp for device, is this case for S10 G973F latest twrp is - twrp-3.5.0_9-1-beyond1lte.img.tar
Under Instructions: Odin (windows) download
- Odin v3.14.1
- avb disabled vbmeta.tar
- click link to multidisabler-samsung-2.* and download latest version from there, currently multidisabler-samsung-3.1.zip
If sticking with stock and custom kernel
- easiest one looks like it would be Cruel kernel or AmbasadiiCruel kernel.
- check kernel thread of choice for compatibility with stock firmware and specific install instructions.
For custom rom in this example for Ambasadii rom
- Download files from Ambasadii rom site
- ROM.G97xF.XXS9DTK9-v2.2.by.ambasadii.zip
- mods_DTJA-v1.3.4.zip
- magisk_safetynet_fix.zip
- AmbasadiiCruel-G97xF-v3.10.zip (rom does include previous kernel 3.9 but this one is updated to latest magisk 21.2)
Bootlogo patcher - this will get rid of the warning about bootloader being unlocked when booting phone. (optional)
TWRP_Bootlogo_patcher.zip
Copy the below files to phones external SDCard
- multidisabler-samsung-3.1.zip
- TWRP_Bootlogo_patcher.zip (optional)
- chosen kernel zip - if sticking with stock
Custom Rom files
- ROM.G97xF.XXS9DTK9-v2.2.by.ambasadii.zip
- mods_DTJA-v1.3.4.zip
- magisk_safetynet_fix.zip
- AmbasadiiCruel-G97xF-v3.10.zip
2. Flashing stock firmware - Odin
- Open Odin on pc
- Turn off the phone
- Use vol down + bixby, then connect usb cable to phone from pc to start the phone in download mode, press vol up to confirm and go to download mode.
- In Odin under log you should see added, I also like to turn off auto reboot under the options tab and do manual reboot once complete but that's up to you.
- Add BL, AP, CP & CSC from the unzipped firmware downloaded in step 1. The AP & CSC can take a little time as they are larger files.
- Once all files added click start and wait until complete, you should see SUCCESS in the top left area once done.
- If you turned off auto-reboot then unplug usb and do manual reboot by pressing vol down + power for 7 seconds, else phone should reboot automatically then unplug.
3. Once phone boots up
- complete setup and connect to Wi-Fi or data
- skip adding Google & Samsung accounts.
- enable developer settings & check OEM unlock is on.
- turn off the phone.
4. Flashing TWRP Recovery - Odin
- In the Recovery thread under Instructions: Odin (windows) continue on from step 8 including formatting data and flashing multidisabler zip which you copied to SDCard.
- in twrp go back to wipe and select advanced and wipe data, cache & dalvik-cache
5a. If sticking with stock & custom kernel - Read NOTICE at top of post
Assumed Steps
- Still in twrp recovery go back to main menu
- select install and flash kernel zip, then TWRP_Bootlogo_patcher.zip
- Not sure if magisk_safetynet_fix is needed or works on stock, would need to confirm in Ambasadii thread.
- go back to main menu and select reboot & system
- give the phone a few minutes to start, and then complete setup including adding your accounts.
- once setup is complete open magisk and it will run additional setup, and then phone will reboot
- done
OR
5b. If flashing Custom Rom & Kernel - steps below for Ambasadii Rom
- Still in twrp recovery go back to main menu
- select install and flash ROM.G97xF.XXS9DTK9-v2.2.by.ambasadii.zip, choose options in aroma - once the install is complete exit back to twrp recovery
- select and flash mods_DTJA-v1.3.4.zip, then magisk_safetynet_fix.zip, then AmbasadiiCruel-G97xF-v3.10.zip, then TWRP_Bootlogo_patcher.zip
- once you have flashed all files go back to main menu and select reboot & system
- give the phone about 8 minutes to start, and then complete setup including adding your accounts.
- once setup is complete open magisk and it will run additional setup, and then phone will reboot
- done
6. If you went with Ambasadii Rom
- you will then notice status bar icons are pushed to the right behind the camera
- open rom control, grant superuser rights
- select status bar/options and play around with notch adjustments and positions
- can be a little confusing to start but play around and you'll get the hang of it.
Hope this info helps, let me know if you need any clarification/detail to any of the steps
Also no need for reward, happy to help
Click to expand...
Click to collapse
Hey There, Been busy lately and I haven't gotten around to trying any of these methods until today. Today I attempted the stockrom+CruelKernel. I am having a strange problem. I am acquiring root but as a read-only. I can not make any changes to system files, I can only view them. Can you tell me if you are able to modify or add to the system directory? Let me know. I know your phone is running custom rom + custom kernel, so I just might have to do that if that is the only fix. I have tried several things and read all of the threads but can not find anyone else that is experiencing this issue / I can not find a fix. I'm about to try the custom rom (stock based) + custom kernel to see if that works. If you can tell me if you have access to read/write system files then let me know so I know if this is even possible. Thanks.
I have found out that I can modify system files through twrp recovery, but when I boot into the main operating system then I have root but as read-only.
Hey, sorry for late reply - ever since xda updated it's not sending me emails when I get a notification.
As for the system directory being read-only, I believe this is normal even with root. Root just gives access to the /root dir that you would not normally have without it.
- my system dir permissions by default are 755/rwxr-xr-x
After a bit of searching looks like there are a few ways to change permissions
- twrp, can mount system as r,w - but as you said this reverts on reboot
- adb shell, and chmod permissions, same why you do with linux
- in android using either root explorer or x-plore, haven't tried root explorer as it is a paid app but did test with x-plore and working fine.
check this vid on changing the root access to superuser+mount writable which allows for changes in read-only folders and how to set permissions for files/folders.
I not sure if changing permissions on the system folder itself is safe or would cause any issues, I just created a folder within system and set permissions to 644 reclusive, created some files and rebooted - created folders/files and modified permissions remained fine after reboot.
If you need write permissions in system to install apps as system/app you may find this magisk module useful, it's called App Systemizer which allows you to use apps as system apps systemlessly. Just search in magisk modules.
Hope this helps.
pjc21 said:
Hey, sorry for late reply - ever since xda updated it's not sending me emails when I get a notification.
As for the system directory being read-only, I believe this is normal even with root. Root just gives access to the /root dir that you would not normally have without it.
- my system dir permissions by default are 755/rwxr-xr-x
After a bit of searching looks like there are a few ways to change permissions
- twrp, can mount system as r,w - but as you said this reverts on reboot
- adb shell, and chmod permissions, same why you do with linux
- in android using either root explorer or x-plore, haven't tried root explorer as it is a paid app but did test with x-plore and working fine.
check this vid on changing the root access to superuser+mount writable which allows for changes in read-only folders and how to set permissions for files/folders.
I not sure if changing permissions on the system folder itself is safe or would cause any issues, I just created a folder within system and set permissions to 644 reclusive, created some files and rebooted - created folders/files and modified permissions remained fine after reboot.
If you need write permissions in system to install apps as system/app you may find this magisk module useful, it's called App Systemizer which allows you to use apps as system apps systemlessly. Just search in magisk modules.
Hope this helps.
Click to expand...
Click to collapse
Cool, I'll give your suggestions a try. I'm a fan of ES File Explorer. They have a root explorer built in their app and previously I had a S8 Exynos and a S9 Exynos and that app worked for those phones but with this S10 the switch is grayed out and no other app is working for me either. On my older S8 Exynos and S9 Exynos I rooted with stock-rom + stock-kernel and just needed TWRP+Magisk and I always was able to modify or add/delete system files with ES file explorer. I guess Samsung is getting more and more strict on allowing this by making us hop through more hoops in order to do so. So far I only have ready only system files on the S10 Exynos which is new to me because the S8 and S9 always allowed modifying system files in the past but I will try your methods you suggested. Worst case I'll attempt the custom-rom + custom-kernel and see if that works. Right now I have stock-rom+custom-kernel. I was able to make changes in the system files in TWRP but hopefully your method will allow me to edit system files without having to switch to TWRP every time I want to change something. I will keep you updated.
On a side note I just rooted a Samsung S20 Exynos and turns out that the system files are read only everywhere whether in TWRP or not, so Samsung keeps making things more difficult on us all. I currently have no way of modifying system files on the S20 no matter what I try but that phone is still much newer so I will give the magicians more time before I look into the forums more for that phone. Right now if I can get the S10 Exynos then I'll be happy.
I'll let you know how things progress. If I get what I need done with this S10 then I am happy to give you a donation for your help in this matter. I would not have gotten this far without your help. Previously the S8 and S9 days were so much easier and people had youtube videos galore that described how to root. The process was easy and everything was unlocked as read write back in the S8 and S9 days.
Yeah I use to use ES on android 6-8 then moved of to solid explorer, very similar ui to ES and also has root explorer but unfortunately it does not work to change permissions on s10 android 10 (bloody samsung/google). So far the only free one I have found is x-plore to be able to do this now. Looks like google is locking down android even more now with android 11

[INDEX] REDMI S2/Y2 Ultimate Collection & Guides

Welcome to REDMI S2/Y2 Ultimate Collection!
(ysl)
Template for the index by Retrial
​OFFICIAL STOCK MIUI ROM
You can check my Guides for installation.
Recovery ROM V12.0.2.0.PEFMIXM
Fastboot ROM V12.0.2.0.PEFMIXM
FIRMWARES
Redmi S2/Y2 Firmwares
Redmi S2/Y2 Vendors
CUSTOM ROMS
You can check my Guides for installation.
Based on Stock MIUI ROM
Xiaomi.eu V11.0.1.0.PEFCNXM
Most of this Custom ROMS listed are UNOFFICIAL and with a great probability that will never get updated.
Android 12/12L​
Lineage OS 19.1 (unofficial)
PixelPlusUI
LineageOS 19.1 (unofficial)
Project Elixir
AOSP 12
ArrowOS (Unofficial)
CorvusOS vS3.0 (Unofficial)
Android 11
Pixel Experience
LineageOS
crDroid Android
EvolutionX
Palladium OS
Descendant XI
Pixel Extended
Pixel Blaster
StagOS
DerpFest
RevengeOS
Superior OS
Pixel Plus UI
Styx OS
CipherOS
DotOS
KangOS
Octavi-OS
Project LegionOS
Android 10
Pixel Experience
LineageOS
HavocOS
FreakyOS
PixysOS
AncientOS
RevengeOS
ShapeShiftOS
MSM-Xtended
CUSTOM KERNELS
Linux Kernel 4.9 Source
StormBreaker EAS Kernel
Fox Kernel Project
Qwerty Kernel (Discontinued)
Revvz Kernel
CUSTOM RECOVERY
You can check my Guides for installation.
TWRP Recovery
PitchBlack Recovery
OrangeFox Recovery
Sky Hawk Recovery Project
GAPPS
Note: be sure you have selected Platform: ARM64 and the proper Android version of the ROM you are going to flash. If the ROM you want to flash include GApps, no need to download and flash any GApps at all.
Most of the GApps have also a config. file which can be used to to configure your installation the way you like. You can skip any Package that you don't want to be part of your installation. For more infos about that, read the instructions of the GApps you chose or search in Google.
NikGApps[Create your own NikGApps build -> Video Guide]
Open GApps
MindTheGapps
FlameGApps
BiTGApps
MAGISK ROOT SOLUTION
You can check my Guides for installation.
Magisk (APK)
Magisk.zip (Flashable Zip)
Uninstall.zip (Flashable Zip)
Magisk Canary (APK)
Disable Force Encryption (DFE) & Encryption
You can check my Guides to find for what is used for.
Disable Force Encryption (No Magisk Included)
Disable Force Encryption (With Magisk Included)
Encrypt Data
GOOGLE CAMERA PORTS & UNIVERSAL STOCK CAMERA UNINSTALLER & ANXCAMERA
Only works if you're installed a 64-bit Android
san1ty
Parrot043
BSG (Private Version) [XML Configs] [Video Review]
BSG (Public Version) [[/B]Video Stabilization Settings]
ANXCamera(Magisk Module - No Addon needed)
Universal Stock Camera Uninstaller(Flash it in Recovery)
Note: If you updated GcamGo from the Play Store, you will need to flash this file and manually uninstall GcamGo from the app info.
GOOGLE PLAY SYSTEM UPDATE 🛡
You can manually update Google Play System by downloading and installing Main components.
USEFUL APPS
Check the Privacy & Security section in my Guides
If for some reason you can't find/install an app on Google Play Store due country restrictions or anything, you can sideload the app from APKMirror.
Adaway: Open Source ad blocker for Android using the hosts file.[/B]
Aegis Authenticator: Aegis Authenticator is a free, secure and open source app for Android to manage your 2-step verification tokens for your online services.[/B]
BetterBatteryStats: With BetterBatteryStats you can analyse the behavior of your phone and find applications causing the phone to drain battery while it is supposed to be asleep.
Brave Browser: Open Source Privacy Browser with built-in adblock.[/B]
Bromite: Bromite is a open source Chromium fork with ad blocking and enhanced privacy.[/B]
Cryptomator: Cryptomator encrypts your data quickly and easily. Afterwards you upload them protected to your favorite cloud service.
Device Info HW: A hardware and software information app for Android devices.
FairEmail: Fully featured, open source, privacy oriented email app.[/B]
Franco Kernel Manager: Complete toolbox for all devices with a rich feature set aimed for ease of use to supercharge your kernel.[/B]
KeepassDX: KeePassDX is a free open source password manager for Android, which helps you to manage your passwords in a secure way.[/B]
MiXplorer: Fully-featured File Manager.[/B]
NetGuard: NetGuard provides simple and advanced ways to block access to the internet - no root required. Applications and addresses can individually be allowed or denied access to your Wi-Fi and/or mobile connection.
NewPipe: Open Source Youtube alternative platform without ads.[/B]
Nova Launcher 7: Nova Launcher replaces your home screen, providing you with powerful features that you will soon realize you can't live without.
Shade Launcher: Make your phone feel like home. Free, open source, no ads.[/B]
Signal: Signal is a free and open source software application, allowing users to send end-to-end encrypted group, text, picture, and audio & video messages, and have encrypted phone conversations between Signal users.
Simple Mobile Tools: A group of simple, open source Android apps without ads and unnecessary permissions, with customizable widgets.[/B]
SysLog: Open Source tool for quickly taking and sharing system logs.[/B]
Today Weather: Today Weather is a beautiful & simple-to-use weather app that provides the world's most accurate local weather forecasts.[/B]
Youtube Vanced: Vanced is a well known modded version of YouTube with many features such as adblocking, background playback and many many more.[/B]
XIAOMI TOOLS
Mi Unlock
Xiaomi Mi Flash Tool
Xiaomi ADB/Fastboot Tools
MINIMAL ADB AND FASTBOOT
Minimal ADB and Fastboot
AMD RYZEN FASTBOOT FIX
Check the AMD Ryzen Fastboot Fix Guide for the proper steps.
AMD Ryzen Fastboot Fix (Batch File .bat)
(Scroll Down to check the Guides)
​
REDMI Y2/S2 Ultimate Guides!
(ysl)
!DISCLAIMER!
Most people I know (including myself) who used my Guides and steps, did that with success many times. If you don't follow exactly the steps or you do a mistake during the process, I do not take any responsibility for any unexpected results or damage that may happen. However I am here to help if something goes wrong, just ask in the thread.​
AMD RYZEN FASTBOOT FIX
Some AMD Ryzen Systems may have problems to recognize your device in fastboot. Try the following ways:
1. Install AMD Ryzen Chipset Drivers.
2. Enable USB Debugging at device (Settings > Additional settings > Developer options > USB Debugging) and give authorization after connecting it to PC.
3. Use USB Hub.
4. Use USB Type-A 2.0.
5. Download this .bat file (unzip it) or manually create a .bat file with these lines below, and run it as an administrator, then reboot:
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\18D1D00D0100" /v "osvc" /t REG_BINARY /d "0000" /f​reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\18D1D00D0100" /v "SkipContainerIdQuery" /t REG_BINARY /d "01000000" /f​reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\18D1D00D0100" /v "SkipBOSDescriptorQuery" /t REG_BINARY /d "01000000" /f​Check the steps an another user did to make it work here.
If this doesn't help, unfortunately you have to use Intel System.
UNLOCK BOOTLOADER
Note: Some AMD Ryzen Systems may have problems to recognize your device in fastboot. [Read the AMD Fastboot Fix Guide above]
Please keep in mind by Unlocking Bootloader the device will reset and all your data will be lost. Make a backup of your data first to PC or to USB.
1. Create a Mi account on Xiaomi’s website.
2. Add a phone number to your Mi account.
3. Insert a SIM into your phone (If you haven't added already).
4. Enable developer options in Settings > About Phone by repeatedly tapping (7 times) on MIUI Version.
5. Link the device to your Mi account in Settings > Additional settings > Developer options > Mi Unlock status. Also enable USB Debugging.
6. Download the Mi Unlock app (Windows is required to run the app).
7. Run the Mi Unlock app and follow the instructions provided by the app.
8. Reboot your device into Fastboot mode. For that simply turn off your device, press the Power Button + Volume Down (–) button at the same time. Then connect the device to the Windows PC/laptop via a micro USB cable.
9. After device and Mi account are successfully verified, the Bootloader should be Unlocked and your device will restart by itself.
INSTALL CUSTOM RECOVERY
Fastboot Method (No Custom Recovery currently installed)
Note: Some AMD Ryzen Systems may have problems to recognize your device in fastboot. [Read the AMD Fastboot Fix Guide above]
1. Make sure your Bootloader is Unlocked.
2. Enable developer options in Settings > About Phone by repeatedly tapping (7 times) on MIUI Version.
3. Enable USB Debugging in Settings > Additional settings > Developer options > USB Debugging.
4. Download a custom recovery of your choice. [You can find a recovery of your choice in my Collection]
5. Download the portable Minimal ADB and Fastboot and run adb.exe
6. Reboot to Fastboot mode by pressing Power Button + Volume Down (–) and keep holding both buttons until the word “FASTBOOT” appears on the screen, then release.
7. Once the device is in Fastboot mode, connect your device to PC and verify you can find it by typying in adb: fastboot devices.
8. Flash Recovery by typing in adb: fastboot flash recovery <recovery_filename>.img (The file may not be named identically to what stands in this command, so adjust accordingly).
9. Reboot to Recovery by typing in adb: reboot recovery or manually hold Power Button + Volume Up (+) until you boot to Recovery.
10. Done! You now have a new Custom Recovery installed.
Recovery Method (Custom Recovery already installed)
1. Download a custom recovery of your choice. [You can find a recovery of your choice in my Collection]
2. Reboot to Recovery by holding Power Button + Volume Up (+).
3. Press Install Image.
4. Locate the recovery.img you recently downloaded.
5. Select it and choose the option Recovery and Flash.
6. Go back and Reboot to Recovery.
7. Done! Your new recovery should be installed.
MAGISK ROOT SOLUTION
The easiest way to root your device is via Magisk, it should work in all ROMs, Stock and Customs.
Install Magisk:
1. Install latest TWRP Recovery. [Read the Install Custom Recovery Guide above]​2. Download the Magisk [You can find it in my Collection]​3. Reboot to TWRP Recovery by pressing Power Button + Volume Up (+) and flash it.​4. Reboot and check whether the Magisk app is installed. If it isn’t installed automatically, manually install the APK. [You can find it in my Collection]​Note: From Official TWRP Recovery 3.5.1 and onwards (and other recoveries based on that), Magisk.apk can be flashed as apk without the need of rename it to .zip. So you can simply flash the Magisk.apk in TWRP.​Manually Creation of Flashable Zip:​Download the latest Magisk APK and rename the Magisk.apk → Magisk.zip.​
Uninstall Magisk:
Flash the Uninstall.zip in TWRP Recovery and reboot. [You can find it my Collection]
If Magisk App isn’t uninstalled automatically, manually uninstall the app.
Manually creation of Flashable Uninstall Zip:
Download the latest Magisk APK and rename the Magisk.apk → uninstall.zip
Uninstall Magisk directly through the Magisk app. Simply press the Uninstall button.
DISABLE FORCE ENCRYPTION (DFE) & Encryption
[You can find it in my Collection]
Disable Force Encryption
Disable Force Encryption (a.k.a DFE) is flashed during installation of a custom ROM to avoid the system encrypting /data partition when the devices boot for the first time.​Some ROMs are not encrypted by default and so is not necessary to flash DFE. However if your ROM comes with encryption by default you can always flash DFE after clean installation of ROM and always after every update or flash or you can use any custom recovery like OrangeFox, Pitchblack, Skyhawk Recovery Project which can automatic flash DFE after every flash.​I don't recommended to use DFE if you don't switch ROMs frequently and you are casual user. Beside the fact that if you lose your device your data are not protected, many people get in confusion while doing OTA or manually updates, which if the ROM is encrypted by default and flashed DFE and in next update you forget to flash DFE you will lock out from your data and you wil get into bootloop (use custom recoveries mentioned above to avoid that).​​
Encryption
Warning - This works only on clean flash:
1. Flash ROM.zip in recovery
2. Mount vendor partition in recovery (for some reason does not mounting with newer TWRP).
3. Flash encrypt.zip.
4. Reboot to system.
Note:
The encrypt zip needs to be flashed after every update.
So flash ROM.zip and follow with encrypt zip.
Encrypted ROMs are recommended if you are stable and casual user of a ROM. Encryption have the benefit to protect your data, in case you lose your device for example. ​Always use the latest TWRP Recovery so you can be able to decrypt the data by filling the same lock screen password you have set in ROM.​Some ROMs are not encrypted by default but devs provide an Encryption.zip (script) which can encrypt the ROM. Same as DFE you need to flash it after clean installation of ROM and always after every update to stay encrypted and not get into bootloop. Unfortunatly there is not any custom recovery automatic doing that like with DFE, so you must be careful, avoid doing OTA updates and flash it every time you manually update a ROM.​
BATTERY TIPS
Advanced Guide
Simple Battery & Charging Tips
Improve your SOT
Battery Calibration
Steps:
1. Discharge your phone fully until it turns itself off.
2. Turn it on again and let it turn itself off.
3. Plug your phone into a charger and, without turning it on, let it charge until the on-screen or LED indicator says 100 percent.
4. Turn your phone on. It's likely that the battery indicator won't say 100 percent, so plug the charger back in (leave your phone on) and continue charging until it says 100 percent on-screen as well.
5. Unplug your phone and restart it. If it doesn't say 100 percent, plug the charger back in until it says 100 percent on screen.
6. Repeat this cycle until it says 100 percent (or as close as you think it's going to get) when you start it up without it being plugged in.
Overheating
Following reasons will lead to device heating issue:
During the initial setup after purchase or when restoring data.
Downloading large files.
Using apps that require more power or using apps for extended periods such as:
Playing high-quality games for long time.
Recording videos for extended periods.
Streaming videos while using the maximum brightness setting.
Using the Screen Mirroring / Smart View feature (connecting mobile to a TV).
While multitasking or when running many apps in the background i.e:
Using Multi window.
Updating or installing apps while recording videos.
Downloading large files during a video call.
Recording videos while using a navigation app.
Large amount of data for syncing with the cloud, email, or other accounts.
Exposing device under sunlight when temperature is high around you.
Extensive usage of mobile hotspot and tethering feature.
Using device in areas with weak signals or no reception or in roaming network.
Charging the battery with a damaged / unapproved USB cable.
Device's multipurpose jack is damaged or exposed to foreign materials, such as liquid, dust, metal powder, and pencil lead.
Solution:
Turn off Wi-fi, GPS , bluetooth and other connectivity options when not in use by dragging the notification panel.
Decrease screen brightness.
Close background running applications.
Too many applications installed in device may result in device heating since their corresponding process will keep on running in background. It is advised to uninstall un-necessary apps if not using them.
Avoid using apps like GPS, data dependent apps or graphic intensive games for longer duration since they require more energy to function, causing device to heat.
It is advised not to use device while charging as it may cause the device to over heat.
General:
DO:
Use manual brightness or dim the screen.
Turn off notifications for apps you don't use. Better still, delete/disable the apps entirely if you don't need them.
Enable battery or power saving mode when you want to extend your battery life.
Use the power adapter that came with your phone. Other chargers can charge slowly/faster but they can also damage your phone or battery.
Turn off bluetooth, location tracking, and Wi-Fi (unless you are actively using it)
Turn off print services from bluetooth connection preferences.
Avoid extremes of heat and cold. If your phone gets very hot or cold it can strain the battery and shorten it's lifespan.
DON'T:
Have Bluetooth or Wi-Fi turned on constantly.
Leave apps running in the background. Instead restrict background usage off apps that you don't need running.
Push email means your device is always listening for new email which drains alot of battery.
Drain your phone battery all the way to 0% or charging it all the way to 100%. Keep it between 20% - 90% for longer battery lifespan.
The more advanced the graphics and animations are (games, videos, photos, animations), the harder the processor and graphics chip in your smartphone have to work. More activity means more battery use.
PRIVACY & SECURITY
Some useful links:
All about Privacy & Security at PrivacyTools.
Electronic Frontier Foundation
Check if your email address is in a data breach at Firefox Monitor & at Have I been Pwned
Test your browser to see how well you are protected from tracking and fingerprinting at Cover Your Tracks by EFF.
Ad Block Tester is a free service on the Internet to evaluate content blocking solutions. It is not designed to be a benchmark, but it reveals the level of blocking against a set of hosts that are very popular.
Check on AM I FLoCed? by EFF if your your Chrome browser has been turned into a guinea pig for Federated Learning of Cohorts or FLoC, Google’s latest targeted advertising experiment.
How to block ads on Android.
General:
Always prefer Open Source or well popular Programs, Apps, ROMs, Kernels & Stuff.
Open Source doesn't mean it's 100% safe but it's unlikely to have something suspicious, since you and other users can check the code in GitHub or in any other code hosting platform the "stuff" is hosted.
Prefer ROMs & Kernels with SELinux Enforcing. You can find informations here.
Always download and install Apps, Programs, ROMs & Stuff from official sources and do not use redirection links from different sites. Google is your friend to find the official source of the stuff you want.
Always check the permissions an app requires, before download and install it to your device. If an app ask for permissions which has nothing to do with the app functionality then it's should be reconsider or ask the developer why these permissions needed.
If you want to avoid Google and Play Store (De-Google), you can choose a ROM without GApps preinstalled like LineageOS and use F-Droid client which is an installable catalogue of FOSS (Free and Open Source Software) applications for the Android platform. The client makes it easy to browse, install, and keep track of updates on your device. Note that not all apps from Play Store will be available in F-Droid. Only Open Source projects. You can find alternatives though.
Alternative you can use LineageOS for microG or any ROM which support signature spoofing and can support microG.
For Windows use the default Windows Defender & Malwarebytes to scan your files whenever you want (Prefered before open or install them). Also use the addon/extension uBlock Origin in your Browser. These should be enough for normal users.
For Android Do not use any antivirus - antimalware since it's useless, just check what apps and from where you installing.
Always verify the source of addons/extensions in your browser. Avoid installing random and unpopular addons/extensions. Keep it minimal and clean, so browser can be fast and safe, no need bunch of extensions.
If you are using VPN, always check the terms and rules of the provider. Avoid random VPN Services.
Recommended VPN Services.
Using a VPN will not keep your browsing habits anonymous, nor will it add additional security to non-secure (HTTP) traffic.
Recommended is to encrypt your data/files always before uploading them to cloud with tools like Cryptomator.
Always use unique and strong passwords for each of your accounts.
Use awarded open source Password Managers like KeePass or KeePassXC for Desktop and KeePassDX for Android to manage your passwords and have them with you safe, encrypted and secure. Must be noted you can use the same database file between these programs.
Always enable 2 Step Authentication wherever is available for your accounts.
You can use apps like Aegis Authenticator.
Do not open or click on links attached in unknown emails you may get. Always check the adress of the email and verify it's legit from the official source.
Create and use "burned" email for accounts/sites you have concerns but you definitely want to try them. Do not use your personal or business email.
CLEAN INSTALL CUSTOM ROM
You can also do the same steps below to install Stock MIUI Recovery ROM.
1. Backup all your data to PC or to external SDCard. [All your data into Internal Storage will be lost on step 7 while Formating Data or Wiping Internal Storage]
2. Unlock Bootloader. [Read the Unlock Bootloader Guide above]
3. Download: [You can find everything in my Collection]
Custom Recovery of your choice.
Custom ROM of your choice
GApps (be sure you have selected Platform: ARMx64 and the proper Android version of the ROM you are going to flash) if the ROM you are going to flash does not include. [Optional]
Magisk Root Solution [Optional]
Disable Force Encryption [Optional]
4. Move all these files in one folder to your Internal Storage or to External SDCard if you have.
5. Install Custom Recovery. [Read the Install Custom Recovery Guide above]
6. Reboot to Recovery Power Button + Volume Up (+)
7. Installation:
Steps without external SDCard:
Select Wipe > Advanced Wipe
Select Dalvik / ART Cache, System, Data, Vendor, Cache and then Swipe to Wipe.
Flash ROM > GApps [Optional] > Magisk [Optional] > DFE [Optional - Not Recommended]
Go back and select Wipe > Format Data > type yes [All your data into Internal Storage will be lost]
Reboot Enjoy!
Steps with external SDCard:
go to Advanced > File Manager > External_SD and delete all folders in ur ext sd card (For example you should delete: Android, .android_secure, LOST.DIR, DCIM, etc) except your personal files/folders and the folder with your custom ROM/Gapps/Magisk/DFE you want to flash.
Each app on your phone with the WRITE_EXTERNAL_STORAGE permission may create files or folders in ur sdcard. Most of these folders have once been created by one of these apps and many of them may be deleted with a few exceptions (e.g. Android, .data, .android_secure, these contain important system or app data like a game's downloaded content):
.android_secure: apps installed and then moved to sdcard
Android: app data/cache
data: app data
.estrongs: ES file manager
LOST.DIR: sort of trash folder (collects recovered files after phone crashes)
DCIM: phone gallery's photos and previews
OTA-update: Over The Air update service
ppy_cross: an unknown third-party app's data.
So I recommend to delete them so you can put your phone/sdcard in a clean state and is guaranteed to be able to re-create these folders.
Select Advanced Wipe
Select Dalvik / ART Cache, System, Data, Internal Storage, Vendor, Cache and then Swipe to Wipe. [All your data into Internal Storage will be lost]
Flash ROM > GApps [Optional] > Magisk [Optional] > DFE [Optional - Not Recommended]
Go back and select Wipe > Format Data > type yes [All your data into Internal Storage will be lost]
Reboot Enjoy!
DIRTY INSTALL YOUR CUSTOM ROM
Note: Before you start flashing, keep in mind the ROM you dirty flashing MUST be the same with the one you have already installed.
1. Make a full nandroid backup, just in case something goes wrong. You can use TWRP to do that. (TWRP > Backup > Select everything) [Optional]
2. Remove all Magisk modules. [Optional]
3. Reboot to TWRP and Wipe Dalvik / ART Cache, System, Vendor, Cache.
4. Flash the ROM > GApps [Optional] > Magisk [Optional] > DFE [Optional - Not Recommended]
5. Reboot and Enjoy!
I've skipped some explanations, because if you are going to dirty flash, you already know for example how to boot to TWRP.
CLEAN INSTALL OFFICIAL STOCK MIUI ROM & RELOCK BOOTLOADER
Note: Some AMD Ryzen Systems may have problems to recognize your device in fastboot. [Read the AMD Fastboot Fix Guide above]
1. Download the official Fastboot ROM and unzip it to your PC. [You can find it in my Collection]
2. Download Xiaomi Mi Flash Tool and run XiaomiMiFlash.exe
3. Turn off you device and then boot in Fastboot mode by pressing Power Button + Volume Down (–) and keep holding both buttons until the word “FASTBOOT” appears on the screen, then release.
4. Connect your device to PC via USB Cable.
5. On the Xiaomi Mi Flash Tool, Click on Select and browse to the folder where you have Unzip the downloaded ROM file then press OK.
6. Click on Refresh button and you will see that your device connected to port com.
7. Select what method you prefer:
Clean All: The process will flash full Fastboot ROM and will wipe everything (include user data) but Bootloader will remain unlocked.
Save User Data: The process will flash Fastboot ROM without wiping user data.
Clean All and Lock: The process will flash full Fastboot ROM and will wipe everything (include user data) but Bootloader will be relocked
8. Now click on the Flash button to begin the flashing progress.
9. Once your ROM is successfully flashed, you’ll see green bar inside XiaomiMiFlashtool.
FIX FOR STUCK ON OREO FIRMWARE (SOFTBRICKED)
FIX (Read Carefully)
New Update: 12/11/2021
Changelog:
Adding the Android 12 roms
Updating links
Minor text fixes
New Update: 23/07/2021
Changelog:
Initial Release
Links to Custom ROM is broken ???

Categories

Resources