Related
Hi XDA Community!
"This is my first time to post a thread. Please consider me as a junior and don't be ignorant
This is all about rooting all almost devices without using a PC.
I called it...."
DROID Universal Root
or DROID U-ROOT
ROOT can access all features deep down into system, just like you are a Administrator in Windows Computer!
ROOT can give you more benefits like, optimize performance, save more battery life, completely remove unwanted user and system apps, and more!
That's why i created this small package
(ChainsDD has also his package but it's old : http://androidsu.com/superuser/)
REQUIREMENTS:
+ Android 2.3 Gingerbread to 4.2 Jelly Bean (Not yet sure for KitKat)
+ Android Devices with ARM Architecture, not yet available for x86, MIPS, etc.
+ An Android Device with a workable Recovery Mode Console.
(Custom and NON-OEM Recoveries are Recommended! More info...)
* With a SD Card at least 20MB remaining space, a system partition at least
12MB and a "/data" or internal memory with at least 10MB space remaining.
* Unlocked Bootloader (Bootloaders issued mostly in HTC, Motorola, etc. if Available)
NOTE : For users who are using DROID_U-ROOT_******--SIGNED.zip,
If installation fails, try these two packages.
DROID_U-ROOT_******_GB--SIGNED.zip contains Superuser files by @ChainsDD
while, DROID_U-ROOT_******_ICS+--SIGNED.zip contains SuperSU files by @Chainfire
(ICS+ Means its for Android 4.0 to 4.2)
COMING SOON:
* v 1.0.21 *
BIGGEST UPDATE EVER!
-- Fixed TYPO code in updater-script for GB Edition.
-- updater-script would be obsolete, we will now using the
binary source from @ClockWorkMod (coding)
to ensure rooting process!
-- More permissions fixes using scripts to ensure it's integrity!
-- Other architectures (x86, MIPS, etc.) would be available!
Version Changelog:
* v 1.0.1 *
-- Properly Signed all packages using APK-Multi-Tool (Hope it's more compatible!)
-- Dummy file contained in init.d directory in order to sign the whole package! (It will call "su" binary at boot)
* v 1.0.0 *
-- Initial Release
ALL OF INFORMATION MAY YOU WANT TO KNOW IS ALREADY
COMPILED IN A README FILE!!!
"All of files contained in DROID UNIVERSAL ROOT package are never modified any
file belongs/owned from the RESPECTIVE OWNERS. All of Copyright complaints and
infringements was unintentional."
More info in README!!!
Thank you.
README!!!
Code:
+===============================+
DROID UNIVERSAL ROOT
by JCCULTIMA
The Universal ROOT Package
for ANDROID!
+===============================+
TEXT-BASED README Version 1.2
[HIDE]
DISCLAIMER and COPYRIGHT POLICY
All of files contained in DROID UNIVERSAL ROOT package are never modified any
file belongs/owned from the RESPECTIVE OWNERS. All of Copyright complaints and
infringements was unintentional. Instead, please report it at XDA Forums
(@jccultima) to address all of these.
SU Apps and Binaries are owned and distributed by/from ChainsDD, Chainfire, etc.
and licensed under the APACHE Version 2.0
You may not use these FILES except in compliance with the License.
You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0
APK's are repacked and published from Official Google Play Store.
Table of Contents
1. Information about ROOT
2. Advantages and Disadvantages of ROOT
3. What are the requirements to make it work?
4. How to install DROID UNIVERSAL ROOT?
5. Compatibility Notice
1. Information about ROOT
-------------------------------------------------------------------------------------
More info at: http://en.wikipedia.org/wiki/Android_Rooting
Android rooting is the process of allowing users of smartphones, tablets, and other
devices running the Android mobile operating system to attain privileged control
(known as "root access") within Android's sub-system.
Rooting is often performed with the goal of overcoming limitations that carriers and
hardware manufacturers put on some devices, resulting in the ability to alter or
replace system applications and settings, run specialized apps that require
administrator-level permissions, or perform other operations that are otherwise
inaccessible to a normal Android user. On Android, rooting can also facilitate the
complete removal and replacement of the device's operating system, usually with a
more recent release of its current operating system.
As Android derives from the Linux kernel, rooting an Android device gives similar
access administrative permissions as on Linux or any other Unix-like operating
system such as FreeBSD or OS X.
Root access is sometimes compared to jailbreaking devices running the
Apple iOS operating system. However, these are different concepts.
Jailbreaking describes the bypass of several types of Apple prohibitions
for the end user: modifying the operating system (enforced by a "locked bootloader"),
installing non-officially approved apps via sideloading,
and granting the user elevated administration-level privileges.
Only a minority of Android devices lock their bootloaders?nd many vendors such
as HTC, Sony, Asus and Google explicitly provide the ability to unlock devices,
and even replace the operating system entirely.
Similarly, the ability to sideload apps is typically permissible on Android devices
without root permissions. Thus, it is primarily the third aspect of iOS jailbreaking
relating to giving users superuser administrative privileges that most directly
correlates to Android rooting.
2. Advantages and Disadvantages of ROOT
-------------------------------------------------------------------------------------
An Android Device with a ROOT Access can give more functionality, such as by
Optimizing Performance both Software (Kernel, ROM) and Hardware (CPU, RAM, SoC)
Longing Battery Life, Uninstalling unwanted system apps, Forcibly transfer the app
to the SD Card (Even it's not supported) etc. All of these functions can separately
install using apps with a special SU (Root binary) system call.
Many users says that ROOT Access was a great function for a Android device.
But ROOT can cause vulnerabilities on your device and it's potentially dangerous
just because it can access deep down into a Android Sub-System such as modifying
system files, depending of which particular files or binaries would modify it by
users.
3. What are the requirements to make it work?
-------------------------------------------------------------------------------------
In order to make it workable smoothly, you/users must comply these requirements;
* Android 2.3 Gingerbread to 4.2 Jelly Bean (Not yet sure for KitKat)
* An Android Device with a workable Recovery Mode Console.
Custom and NON-OEM Recoveries are Recommended!
(More info: http://www.androidcentral.com/what-recovery-android-z)
* With a SD Card at least 20MB remaining space, a system partition at least
12MB and a "/data" or internal memory with at least 10MB space remaining.
This package will install a Superuser/SuperSU app in system/app/ directory, then
the su binary will install in a system/xbin/ directory. While the other functions
will be informed how at XDA forum.
4. How to install DROID UNIVERSAL ROOT?
-------------------------------------------------------------------------------------
BEFORE INSTALLATION...
Reboot your device to recovery mode, booting IT can be in different ways.
Case #1: Turning off the device and wait in a seconds to shut, and pressing
BOTH Power, Volume Up and Home Hard Buttons. This case are applicable
in many Samsung or other devices which it has a center button (HOME).
Case #2: Turning off the device and wait in a seconds to shut, and pressing
BOTH Power, and Volume Up Buttons. This case are mostly applicable
to the devices without a center button. (Soft Touch)
In some recoveries, some of them doesn't have a "select zip from sdcard" option.
So make sure you must rename the package to update.zip
INSTALLATION...
After that, Use the volume button to move, and home/menu/power button to select.
Some devices can select by tapping. Choose "select zip from sdcard" or
"select update.zip from sdcard". It will run if you rename this package
to update.zip!
AFTER INSTALLATION...
Reboot your device, wait for a moment to boot, and open your launcher menu.
When the Superuser/SuperSU app appeared, it means that you are ROOTED.
5. Compatibility Notice
-------------------------------------------------------------------------------------
NOT ALL ANDROID DEVICES are 100% workable in this package.
Many devices may not be easy to install cause of security features
such as OEM Recoveries build and provided by own manufacturers,
and locked bootloaders which it has a ability to restrict sideloading files
except their Official OTA Updates. It should be unlocked right away before
this procedure.
For users experienced Error 0 by installing this package, simply replace the
update-binary file from any of your stable update-binary.
Open the package using WinRAR then...
* META-INF/
* com/
* google/
* android/
! update-binary <<< Should be like this
* updater-script
* CERT.RSA
* CERT.SF
* MANIFEST.MF
To avoid device crashes, please make a backup through ADB (Android 4.0+ only) or
Custom Recovery (e.g. CWM). The developer is not responsible for Device Crashes,
Bootloops and other relative damages on your device.
README Version Changelog
1.0 Initial Release
1.2 Finishing and Adding more information
Don't Forget to Report us at XDA (Link Coming Soon...)
[/HIDE]
Idk what this is. OP says Stable and beta. I downloaded your signed beta rc 1.0 and it is nothing but supersu apk, su binaries, and busy box. The updater script seemed weird as supersu does all of the work in the updater-binary. Anyway, I have no idea what this is supposed to be. You might want to ask @Chainfire before repackaging his stuff though. It doesn't appear in your OP that you give him credit.
Sent from my AOSP on HammerHead using Tapatalk
LG Stylo 2 Plus K550 Stock Rom Unrooted/Tweak-less
I AM NOT RESPONSIBLE FOR ANY BRICKED DEVICES, BOOTLOOPS, NUCLEAR ANNIHILATION, OR SPONTANEOUS
COMBUSTION! YOU ARE CHOOSING TO FLASH!!!
What you need -
1) TWRP
2)A brain
What is this ROM?
This is the Stock ROM for the K550 Variant of the Stylo 2 Plus. This ROM is completely Stock for the exception of having Adoptable Storage available Out of the box, and Kernel Fixes To be used on K550 ONLY (I mean, you can try on the MS550 but I'm not sure if It will SimLock to Tmobile
How is this different from [K55010r Stock Rooted Odex for T-Mobile LG Stylo 2 Plus by pvsgh]?
1) This is a purely stock ROM extracted directly from KDZ, no mods at all
2) Kernel and Security fixes that ROM by pvsgh doesnt have, fixing ADB (which doesn't work on his ROM, which was the main reason I had to make my own since ADB is crucially needed for speedy builds in my line of work)
Also, @pvsgh, DM me if you want the boot.img to use for your ROM so you can fix these issues
Will you make this for Andrioid N, when it comes out as well? Will there be a De-odexed version? What about for the MS550?
Yes, I am planning on also having a completely stock ROM built from KDZ as soon as Android N comes out. I will only make a De-odexed version if there is demand for one. In order to make one for the MS550, I need testers first as I only have K550.
Did you give up on LineageOS?
No, I'm just waiting for Android N
How Do I install this ROM?
First of All, Download the ROM and Place it in a Directory where you can find it. Then Boot into Recovery, and Go to Install, and select the Downloaded Zip File in your Selected Directory. When prompted to, Flash. IMPORTANT! - IT IS RECOMMENDED TO FORMAT DATA (USING THE BUTTON THAT LITERALLY SAYS "Format Data" IN TWRP) IF ATTEMPTING A COMPLETELY CLEAN BUILD OR YOU MAY BE LOCKED OUT OF YOUR DEVICE AND CONTENT LOCK WILL NOT WORK ANYMORE
FEATURES
- Literally Stock
- No Mods
- No Root, No Busybox, and No Xposed Out of the Box (User Install-able)
-Custom Stock Kernel with ADB and Security fixesTo be Included
-Nothing
DOWNLOADS
Download Here
Changelog
Version - 1
Code:
[LIST]
[*]Initial Release
[/LIST]
Known Bugs
None, all Stock
If you like you can Donate (On my Profile) or Hit that thanks Button!
didn't realize adb issue is still present in my rom's kernel, i might have forget to include the fixed boot.img. thanks for the headsup.
No problem. You can just extract the boot.img from this rom and put it into yours.
Link is dead
I'm trying to understand the Android Boot Process and the new additional security measures/restrictions put in place by the device manufacturers.
So far I've read through these posts on XDA, Lineage OS Blog and some others. I've understood some and still confused about others.
[INFO] ANDROID DEVICE PARTITIONS and FILESYSTEMS
[INFO] BOOT PROCESS: ANDROID vs. LINUX
Qualcomm’s Chain of Trust
Android Boot and Recovery Images
Dissecting the Android OTA Update System
I've flashed custom ROM and TWRP on my old phone but it didn't have the new security measures in place and I didn't bother about encryption then (The entire files on the device is accessible from the recovery).
I have some doubts about the encryption and other stuff.
1) When we are running with the stock recoveries, user files are inaccessible(because those stock recoveries don't provide that function).
How can I keep my files safe while using TWRP or similar recoveries?
ie How does FDE work with the custom recoveries?
2) I've read about some users complain that FDE got triggered after firmware upgrade. In such cases what key does it use?
3) I've read on Google's website that it allows users to boot with custom keys. Is that enough for 'Certified Status' on Google Play.
4) What all modifications trigger SafetyNet?
I understand that modifying /system triggers it, so using custom kernels would trigger it Right?
Kindly help me out. I'm sorry for any mistakes.
Bump
Bump
Bumped
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Rich (BB code):
*** Disclaimer
I am not responsible for any damage you made to your device.
You have been warned
See 2nd post for Rooting Android PC
-What is Root?
A must read about root is at Wikipedia.
Here Root is not the bottom part of plant which is in soil. Rooting is the process of gaining administrator permissions to tweak partitions that are read-only before.
-What are the prerequisites for Rooting?
Good understanding of what you are doing. A method to revert back all changes done if something goes wrong.
In most cases you need an unlocked bootloader to do so. I will tell you in which cases we don't need an unlocked bootloader.
-What I can do with Root privileges?
Main advantage of rooting your device is blocking ads in system wide. Other advantage include Use apps that only work with root and modify /system, /data partitions.
-Why not to Root?
In the process of rooting, if you misunderstand something and done something wrong, then it may lead soft/hard brick of your device. Your warranty may void according to your region policy.
-Should I really need to Root my device?
In recent years, many things are changed. Before, we need custom roms/root for many customizations to device like changing font, increasing battery life, boosting performance etc.,. But now devices are capable of performing these things without root.
For example you can do below things without root:-
-Blocking ads system wide, use FireWall with VPN
Eg:- TrackerControl, Karma Firewall, OrbotMore info is at this guide or this-Removing bloatware with ADB
-Install Linux distro with PRoot.
-Is there anyway to experience Root without actually rooting device?
It is possible if you use apps like twoyi, VMOS, F1VM, x8sandbox etc., or use Android in PC(see 2nd post).
-How to Unlock Bootloader?
This is needed to flash custom partitions with fastboot or dd. Method to unlock differs from OEM to OEM. Google, OnePlus, Moto, Xiaomi, Realme has some unique methods. Your device will factory reset automatically after you unlock bootloader, so make sure to backup your data before going. More info about unlocking bootloader can be found at here and here
-How can I Root my android?
It depends on Android version of device you are going to root.
If it is Lollipop(5.x) or lower, then one-click root is far best and easy way to root your device without need of unlocked bootloader.
If your device not have above mentioned one, then you have to search Google like How to Root your_device_name and go through the steps mentioned in your device specific sites.
If searching didn't find anything, then you have to use PC(and some complicated steps in certain devices) to root. First you need to unlock bootloader of your device if it is locked. Then follow one of below method.
There are different methods for this.
Below methods require bootloader to be unlocked
-Patching boot.img/recovery.img with Magisk
Example of this, see here-Using a custom recovery and flashing root zip in it
Example of this, see here-Using a custom/GSI rom which is pre-rooted
Phh's AOSP GSI is an example of pre-rooted GSI-Using a custom kernel which is pre-rooted
Example of this, see hereWe only need this if Magisk can't patch boot.img(lower than Android 4.2(17) or unsupported format of boot.img) or Magisk doesn't work in the device for some reason-Using CF-Auto Root for Samsung
Example of this, see here
Below methods does not need to have an unlocked bootloader
-Using an exploit like MTK-SU, DirtyCow, qu1ckr00t
Example usage of MTK-SU, see hereExample usage of DirtyCow, see here, here-Using one-click root methods
Example of this, see here
Examples of one-click root apps
=> Framaroot
=> Kingo ROOT (Recommended and will work in nearly all devices)
=> KingRoot (Will work in nearly all devices)
=> Towel Root
=> UniversalAndRoot
=> z4root
-What is a Custom Recovery and how I can root my device using it?
First we need to know about stock recovery.
-What is a stock recovery?
The recovery that comes default with your device is stock recovery. Different OEMs have different stock recoveries. But the main theme and background process is same for all these.
-Can I able to flash root solution in stock recovery?
No, stock recovery needs zip to be signed with OEM keys. Only OEM has that key. If you flash root zip in stock recovery, it will simply fails by showing Signature verification error. Some stock recoveries accept testkey signed flashable zips. But we need to create a edify based installer, since stock recovery may not have busybox in PATH.
-What does a custom recovery will do?
The main thing that a custom recovery do is, it allows flashing of unsigned zips or zips that are signed with publicly available keys(google testkeys), so that we can do whatever we want.
-How can I get custom recovery?
You need to port or compile it from your device and custom recovery sources. Alternatively, you can also use pre-compiled custom recovery for your device from different sites like XDA, 4pda, hovatek etc.,
-How to flash custom recovery?
If your device manufacturer has flash tool then use it. Example Samsung's Odin, Xiaomi's MiFlash Tool. If your device does not have specific flash tool then you can use fastboot method to flash. If it also doesn't work then you have to use SoC(Mediatek, Qualcomm Snapdragon, Spreadtrum/Unisoc, RockChip) specific flash tools like SP Flash Tool, Research Download Tool.
If you are rooted and had unlocked bootloader, then you can flash recovery like dd if=custom_recovery.img of=<block_device_path_of_recovery>.
-What are different custom recoveries?
CWM, TWRP are popular recoveries. These are exist for many number of devices. Others are mainly derivatives of these like PhilZ, PBRP etc.,
-How can I root with custom recovery?
Simply choose one of the root solution that is compatible with your device from below and flash it in custom recovery.
Various custom recovery flashable root solutions
=> Magisk (Recommended for 5.x and higher)
=> SuperSU (Recommended for 2.3 - 4.4.x)
=> Phh Superuser (Recommended for 5.x and higher)
=> Koush Superuser (For 2.2 - 4.4.x)
=> ChainsDD Superuser (For 1.5 - 2.2.x (3.2-RC3 will work in 2.0 - 4.1))
* Root solutions that are recommended for specific android version may also support other android versions, but it will work better in recommended versions.
References:-
XDA Developers Eg:- this
Wikipedia
Various others like this
Root your Android PC
Rich (BB code):
______________________
< Root Your Android PC >
----------------------
\
\ \\ //
\ \\..-:::::-//
\ .://///////////:.
\ ´:// ///////// //:`
´//// ///////// ////`
://///////////////////:
.-. ----------------------- .-.
:///: /////////////////////// :///:
:///: /////////////////////// :///:
:///: /////////////////////// :///:
:///: /////////////////////// :///:
:///: /////////////////////// :///:
:///: /////////////////////// :///:
:///: /////////////////////// :///:
\_/ /////////////////////// \_/
:///////////////////:
:////: :////:
:////: :////:
:////: :////:
\||/ \||/
Android in PC is possible in following ways
-Using Android Emulator(AVD)
-Using Android-x86 or its derivatives like Lineage, Bliss, PhoenixOS, PrimeOS.
-App Players like MEmu, LDPlayer, BlueStacks, Nox.
-What is the difference between those ways?
Android Emulator is official by Google with its term AVD. It is in ARM or x86 architecture. You can choose whatever architecture you want. So, if you want to use apps then you don't need to worry with compatibility.
Android-x86 is unofficial project with x86 architecture. That means we can install it like any other OS without need of Virtualization/Emulation. But downside of this is that, we need to be take care of selecting apps. Native x86 apps will work but not all arm apps will work. App Players are also x86 versions.
-Is there a simple way to get root access?
The simplest way to root access is to use adb shell in AVD or Debug Mode (ALT + F1 to enter and ALT + F7 to exit) in Android x86. All the commands run in this way will run as root user. We can do whatever you want with commands.
Downside of this is, we cannot give SuperUser access to apps. To overcome this, we need to push su binary to PATH and install corresponding root management application. App Player may has different procedure like enabling in settings(MEmu*, LDPlayer*, Nox*) or executing hidden su like in BlueStacks* /system/xbin/bstk/su(from adb shell only!).
A new tool is made to install Magisk in Android-x86 emulators. You can get it at here
-How to push superuser files to Android?
If you are rooting Android-x86, make sure that /system is read-write when installing it.
If we want to root Android 7.x.x or below versions then we can flash SuperSU from root prompt as said above using update-binary. Before going to execute this, make sure busybox in installed and set in first of PATH. Example usage is
Code:
sh update-binary 2 1 /path/to/SuperSU-v2.82-SR5-20171001.zip
-How to root using Magisk?
See github repo by @shakalaca at here, another tool here by @newbit, one more one at here and guide at here and here.
* Tested versions of App Players with above said functionality are:-
-MEmu 7.3.2
-LDPlayer 4.0.45
-BlueStacks 4.260.0.1032
-Nox 7.0.0.8
Rooted. What next?
If you are rooted with Magisk, then check different modules in Magisk Manager that fit your needs.
Using Terminal
If you know basic things like moving, deleting, updating with commands then you only need a Terminal to do anything with root access.
Using Root File Managers
Must have app for rooted users is an file manager with root capabilities. Eg:- Ghost Commander, MiXplorer, X-plore, 3c Toolbox.
Blocking Ads
To get rid of ads system wide, there are some apps to do so like AdAway. What these actually do is just replace /system/etc/hosts with added domains to block.
Backing up apps with their data
Backing up apps data will include backing up from /data. Eg:- Migrate, OAndBackupX, Titanium Backup.
Removing bloatware
Removing bloatware requires finding exact bloatware, its remnants and deleting them. Apps like Titanium Backup, SD Maid will do these.
Boost up your battery
There are many unnecessary apps and their services taking up juice of your battery all the time. To get rid of this and without compromising the features of that apps, we can use apps like Greenify, Servicely, Naptime etc.
Gaining Performance
By removing unnecessary apps and stoping unnecessary services running in background we can also improve overall performance. Along with this, we can also tweak kernel parameters to improve performance. There are many kernel managers in Play Store. Checkout them. In XDA, most popular members are developers of custom kernels.
Audio Mods
One of the best thing after rooting is modifying audio parameters. There are plenty of apps for doing this job, but Viper4Android FX is best one to try.
Installing Xposed for customization
Installing Xposed opens door for great customizations. Apps that use Xposed include GravityBox, XprivacyLua, AppSettings.
Other Cool Things
We can automate things with Tasker. Enable Camera2API if disabled by default for using GCam.
Some more apps to try
Termux with root repository
CacheAway
AFWall+
Permission Ruler
Storage Isolation
Reserved
Firmware & ROMFirmware is the skeleton of ROM, kinda tells ROM what to do, when to do, how to do. So, they refer to the firmware of the phone as ROM, because in theory you, as a normal user, can't alter the area where the firmware is (it's in the Read Only Memory). On older phone, this was true, it wasn't easy to alter a phone software without special equipment. In nowadays, the firmware is not stored in real ROM, it's stored in the internal flash memory of the phone, which is not Read Only, so you can flash another firmware. The 2 terms are interchangeable. In general, people refer to modified firmware's as ROMs.
Again the ROM on the phone contains the phone's firmware. By replacing the firmware, the ROM of the phone is useless and if you flash a new firmware, the new firmware has complete control over it, which is why the two terms are seen as synonymous.
DRM & WIDEVINE SECURITY:DRM = Digital Rights Management, googles security for paid streaming service, divided into L1,L2,L3 SECURITY LEVEL. If your device has widevine security level L1, you can stream netflix, amazon tv etc in full HD, if L3, you can only in 480p or 540p.
Widevine CDM (content decryption module)
Widevine Media Optimizer (typically when Widevine is both the protection and content player)
if you want to check widevine security of your phone, download DRM INFO APP.
WHERE WIDEVINE SECURITY IS STORED:
PERSIST.IMG contains widevine security information. Once widevine L1 security is lost, there is little possibility of getting it back. You might get it back if you have taken your persist.img backup, that's why, in my MIUI Unlocking Bootloader, Flashing Recovery & Rooting Process thread, I put utter importance taking the persist.img partition backup. Persist also contains your sensor information, like bluetooth, wifi etc.
How do you loose it: By rolling back your android version. Never do it. If you do it, you may break your sensors, in that case, you may fix them by flashing the persist.img of your device, hope you took the backup of it, if you don't , you may flash the persist.img of same device model of other person's device but you will loose your WIDEVINE SECURITY LEVEL L1 forever. My suggestion, never roll back.
TERMINOLOGIES:gApps = Google Apps
SuperSU = another rooting app like Magisk. With simpler interface & no root hiding opportunity.
DTO = Device Tree Overlays (DTOs)
OEM = Original Equipment Manufacturer. (such as, MIUI is a OEM skin/ROM)
OEM Skin = like MIUI luncher, notification toggle like this. Custom OEM skin: customizing them using others skin.
Slot Services = it refers to partition related services in recovery mood.
Treble ROM = Treble supported rom supports ota(over the air) (in simple terms : System Updates)
non-Treble ROM = While non treble roms doesnt support ota.
BB = most probably BASEBAND
GMS, API, AOSP & PRE-LOADED APPS:GOOGLE MOBILE SERVICES (GMS) is a collection of proprietary applications and APPLICATION PROGRAMMING INTERFACES (APIs) services from Google. GMS is used by manufacturers of Android devices, such as smartphones, tablets, and smart TVs. GMS are the Android Applications developed by Google for manufacturers of Android that often come pre−installed on Android devices. GMS is not a part of the ANDROID OPEN SOURCE PROJECT(AOSP), which means an Android manufacturer needs to obtain a license from Google in order to legally pre−install GMS on an Android device. This license is provided by Google without any license fees. GMS consists of two parts; a popular bundle package and an other bundle package. In order to gain a license for GMS, the popular bundle package needs to be pre−installed by Android device manufactures, which are usually called PRE-LOADED APPS.
What is force encryption?Encryption is the process of encoding all user data on an Android device using symmetric encryption keys. Encryption ensures that even if an unauthorized party tries to access the data, they won't be able to read it. Android has two methods for device encryption: file-based encryption and full-disk encryption.
What is Dmverify?Android verified boot: As dm-verity is a kernel feature, in order for the integrity protection it provides to be effective, the kernel which the device boots needs to be trusted. On Android, this means verifying the boot partition, which also includes the root file system RAM disk and the verity public key.
What is DM-Verity?Android 4.4 and higher supports Verified Boot through the optional DEVICE-MAPPER-VERITY (dm-verity) kernel feature, which provides transparent integrity checking of block devices. dm-verity helps prevent persistent rootkits that can hold onto root privileges and compromise devices.
What is DM-verity and force encryption disabler?Many Android ROMs have become more and more secure. Many devices have been equipped with new system security mechanism to protect any advanced modification to the system itself. One of the known mechanism is Device Mapper Verity, also known as dm-verity. This security mechanism is basically developed to help prevent persistent rootkits that can hold onto root privileges and compromise devices. Most of the recent Android devices need to do a verified boot through the optional dm-verity kernel. This is sure can prevent malware to hide from detection programs and otherwise mask themselves. Unfortunately, for advanced Android users, it can be troublesome to a certain extent because it prevents the device to boot properly once custom recovery like TWRP is flashed. Previously, in order to flash TWRP on a device protected with dm-verity feature, you’ll need to first cook your own ROM modifying original ROM to disable dm-verity in its kernel. This could be so arduous for novice users. Luckily, there is a patch-like package allows you to disable dm-verity and forced encryption feature. Download the package from the link below and flash it from TWRP. (Force disabler may not be different for every phone, maybe same) Article Link
What does Vbmeta do?
The vbmeta image is cryptographically signed and contains verification data (e.g. cryptographic digests) for verifying boot. The vbmeta image can also contain references to other partitions where verification data is stored as well as a public key indicating who should sign the verification data. Also Check this link you are interested.
Dirty flashing v/s clean flashing | What's the difference, also what is OTA Update: (CLEAN FLASH AFTER ERROR)Almost every android geek has heard about "flashing" a custom ROM on their device. And digging a bit deeper reveals that flashing also has two types. "clean" flashing and "dirty flashing" But what's the difference and which one should you choose? To find out, read ahead.
The difference
A clean flash is what you do when, you install a ROM after wiping all your device partitions (System, data, ART/Davlik, and cache)
A dirty flash is done when you flash a ROM over an existing one, without erasing the system partition. (at times, only the ART partition is erased). A dirty flash keeps system data from the previous ROM. If the ROMs are not compatible with each other, you'll run into problems. A flash of rom over existing rom without wipe is known as dirty flash, generally followed for nightly or daily builds. You also need a set of gapps with backup script to survive dirty flash.
Dirty Flash = Flashing over current ROM
Clean Flash = Wiping EVERYTHING to make way for a new ROM.
Dirty flash - wipe cache and dalvik, flash ROM and gapps
Clean flash - wipe cache, dalvik, data and system, flash ROM and gapps
What should you choose?
It isn't quite difficult to choose. It depends on the similarity between the ROM you have and the ROM you want to install. If you're installing a completely different one than the one you have (like Touchwiz to Cyanogenmod or Lineage to AOSP) you better go for a clean flash.If you're updating your ROM (from the source provided by the developer of the original ROM), a dirty flash would work, although you should check what the developers says about changing and updating.
Risks
Although flashing comes with it's own risks, going dirty is a lot more unsafe than doing a clean flash. A clean flash removes everything giving the ROM enough room to be installed, minimizing chances of bricking. Whereas, a dirty flash is a lot more likely to brick your device, and if it gets hard bricked.. you don't have any option other than going to the nearest authorized service center and getting your phone fixed. Basically, if you do a clean flash where you can go dirty, nothing will go wrong. But if you go dirty where you're supposed to do a clean flash, you'll end up with a non functional device.
OTA UPDATE:
OTA = OVER THE AIR UPDATE. For example, you are updating from eu rom 12.5 to 12.6. It may not require clean flash, you just dirty flash the rom because it's basically a version update of the same ROM. Your phones auto update or MIUI update is an OTA update. An over-the-air (OTA) update is the wireless delivery of new software, firmware, or other data to mobile devices. Wireless carriers and original equipment manufacturers (OEMs) typically use over-the-air updates to deploy firmware and configure phones for use on their networks over Wi-Fi or mobile broadband. The initialization of a newly purchased phone, for example, requires an over-the-air update. With the rise of smartphones, tablets and internet of things (IoT) devices, carriers and manufacturers have turned to different over-the-air update architecture methods for deploying new operating systems (OSes) to these devices.
Clean Flash : if your device has problem, is not booting, rom is not opening, passward is asking but after entering password, it's not working, all this problem has this clean flash solution. Go to wipe, do a "Fomat Data". advance wipe of system & others is not necessary. Then , flash your new rom. (may use backup rom of your previous working/stable rom).
Disk Quota:A disk quota is a limit set by a system administrator that restricts certain aspects of file system usage on modern operating systems. The function of using disk quotas is to allocate limited disk space in a reasonable way. "This quota feature also improves system stability by preventing any single app from using more than 90% of disk space or 50% of inodes."
fstab:In Android 9 and lower, devices can specify fstab entries for early mounted partitions using device tree overlays (DTOs). In Android 10 and higher, devices must specify fstab entries for early mounted partitions using an fstab file in the first stage ramdisk. logical indicates that this is a dynamic partition.
STILL THIRSTY? WANT TO KNOW MORE ? READ THIS THREAD IN XDA
My Other Threads according to "how should you read them" serial:
1. MIUI 12.5 Chinese ROM Google PlayStore Stopped Working
2. MIUI Unlocking Bootloader, Flashing Recovery & Rooting Process
3. Android Terminology You Must Know Before Toying with Your Android (This Thread)
4. ROM Naming & CUSTOM ROM, AOSP ROM, TREBLE ROM, GSI ROM, PORTED ROM
@shafi1885 Thanks very much for your great terminology guide that is really appreciated. However, I've removed the link to Telegram from your OP.
As an excemption from the last bullet of rule no. 5 of the XDA Forum Rules, we grant only developers the privilege to provide links to their social media in their own development threads. These conditions obviously don't apply to you or your thread.
Stay safe and stay healthy!
Regards
Oswald Boelcke
Senior Moderator