Related
•••• Qualcomm Moto E4 (xt1766) SPerry Only ••••
DISCLAIMER:
By proceeding further, you are assuming sole responsibility for the integrity and functionality of your device. Although this ROM has been thoroughly tested on my own device, I take no responsibility for bricked or otherwise inoperable devices incurred as a result of this thread. Follow the instructions carefully, and things should go smoothly and without negative results.
SPECIFICATIONS:
• Moto E4 (XT1766) SPerry
• Sprint, Virgin Mobile, Boost Mobile
• Android Version: 7.1.1 Nougat
• Build No. NCQS26.69-64-10
• System Version: 26.231.8.sperry_sprint.en.US
• Radio Version: M8920_15000.280.06.58.05R
• Kernel Version: Linux 3.18.31-perf
• Security Patch Level: September 1, 2018
FEATURES:
• Stock Configuration
• Systemless Root - Magisk v17.1 Stable
• SafetyNet Pass (ctsProfile & basicIntegrity)
• Zipaligned /system/app & /framework
• Optimized RAM efficiency
• Disabled AVB & dm-verity
• Disabled Force Encryption (Opt-Encrypt)
• BusyBox v1.29.2 (Static Binaries)
• TWRP Flashable Installer
PREREQUISITES:
An unlocked bootloader and TWRP custom recovery are required to install this ROM. IMPORTANT: Use @squid2's TWRP v3.2.1-r1 or older for installation https://forum.xda-developers.com/devdb/project/dl/?id=27958 Newer builds will cause a conflict with the /vendor & /oem partitions when installing my partition updater zip. After installation, you may update TWRP to a newer or current version.
The conflict is due to the partition scheme of my updater-script, and is not due to any fault in @squid2's current TWRP builds. Here is a link to @squid2's TWRP thread for the Qualcomm Moto E4. https://forum.xda-developers.com/mo...velopment/twrp-twrp-moto-g4-qualcomm-t3655160 Please be sure and hit the thanks button on his thread if you use his work.
NOTES:
• If you have previously installed the 26.221.3 OTA to bring your build version up to NCQS26.69-64-10, you should have no need to install the partition updater zip prior to installing the ROM. However, if you are unsure of your present firmware build, or if you have not installed the latest OTA, the partition updater should be installed per the instructions below, in order for the ROM to work with the best results;
• As to force encryption, the kernel fstab has been modified to disable this OEM security feature. However, you may still manually encrypt your /userdata by fully charging your device, going to Settings>Security>Encrypt Phone, and following the on-screen prompts;
• This OTA update did not augment the baseband (radio firmware) version (M8920_15000.280.06.58.05R), which remains unchanged from NCQS26.69-64-8. While the radio firmware did receive a couple of minor patches, the changelog in this regard is insignificant, so I did not include these in either the partition updater or the ROM. If anybody wants these radio patches, leave a comment and I'll fix up a TWRP flashable installer.
INSTRUCTIONS:
• 1. Download the ROM and Partition Updater from the download link below and save them to your device's external storage (because the /usedata partition needs to be formatted to disable force encryption, saving the downloaded zips to internal storage would be futile);
• 2. Make a backup of any important files on your device;
• 3. Boot your device into TWRP recovery mode;
• 4. Select Wipe>Advanced Wipe and select System, Cache & Dalvik Cache. Swipe the action bar to commence the wipe;
• 5. Again select Wipe>Format Data, input the word "YES" when prompted, and swipe the action bar to commence the format. Reboot Recovery (often necessary to ensure proper mounting of /usedata after a format);
• 6. Select Install, navigate to the saved location of the Partition Updater zip, and swipe to commence install (this updates your /oem partition, /rpm primary bootloader, /tz trust zone partition, and /devcfg partition to Build No. NCQS26.69-64-10);
• 7. Select Install, navigate to the ROM zip, and swipe to commence install;
• 8. Reboot System.
Kernel Source Code (msm8920): https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-NCQ26.69-48
THANKS & CREDITS:
•Thanks to the long-dedicated @squid2 for his TWRP builds for this and many other Motorola devices;
•Thanks to the great @SuperR. for his amazing Windows version SuperR's Kitchen;
• Thanks to the world famous @topjohnwu for his Magisk Universal Systemless Interface;
• Thanks to @madbat99 for his dedication to Motorola devices, and for taking the time to assist so many Motorola device owners;
• Thanks to @osm0sis for his static BusyBox installer and his Magisk Modules;
• Thanks to @Davey126 for his support of Motorola devices, and his dedication to helping other members on various device threads.
DOWNLOAD LINKS:
NCQS26.69-64-10 Partition Updater: https://drive.google.com/file/d/1VmOPXbYBQQkqB475iVzKip2JI_AO0YCM/view?usp=drivesdk
NCQS26.69-64-10 Stock Android 7.1.1 ROM: https://drive.google.com/file/d/1VRuKnSgVHNkewbk5juB7_WWeLm_ptmUP/view?usp=drivesdk
I have also made a debloated build of this ROM, with all Amazon, Sprint and OEM related apps removed from /system/app, /system/priv-app, /oem/app, etc. I will try and post this version this coming week for anybody interested.
I'm new bee kinda so flashing this os just the update so if I have everything up and running good them really don't need this update seems updates have me screwed from getting data on custom rom now so any advice
Bailey36375 said:
I'm new bee kinda so flashing this os just the update so if I have everything up and running good them really don't need this update seems updates have me screwed from getting data on custom rom now so any advice
Click to expand...
Click to collapse
If you have taken the OTA update and you are on Build No. NCQS26.69-64-10, and everything is running smoothly, you have no need to install anything here.
I'm not on 10 I'm on 8 but would like that debloted version
Bailey36375 said:
I'm not on 10 I'm on 8 but would like that debloted version
Click to expand...
Click to collapse
It'll be up in a couple of days. By the way, there is no danger in taking the OTA. No reported bugs, instabilities, etc. And you can still flash the debloated ROM when I post it.
Thanks for taking time to do this and keep support going for the E4. I'm planning on trying the debloat when you post it.
S o S just flashed and now it is only booting to TWRP it says its flawed but
Only boots to TWRP help after flash
---------- Post added at 05:34 AM ---------- Previous post was at 05:18 AM ----------
Really need help I have TWRP 3.2.1 r1 I did what the instructions said but now just goes to the TWRP what's the issue I'm sure it's something I'm doing help this is my only phone
---------- Post added at 05:52 AM ---------- Previous post was at 05:34 AM ----------
Got it woohoow
MotoJunkie01 said:
I have also made a debloated build of this ROM, with all Amazon, Sprint and OEM related apps removed from /system/app, /system/priv-app, /oem/app, etc. I will try and post this version this coming week for anybody interested.
Click to expand...
Click to collapse
Yayyyyyyy!!!!!! I,ll be waiting for that one. Thanks motojunkie01.
Does Radio work in Custom Roms.
EarthMan1 said:
Does Radio work in Custom Roms.
Click to expand...
Click to collapse
The radio was not updated with the new OTA. The Baseband Version remains the same as the previous build, M8920_15000.280.06.58.05R
That means the voice calls won't work on Custom ROMs.
EarthMan1 said:
That means the voice calls won't work on Custom ROMs.
Click to expand...
Click to collapse
Voice, MMS/SMS, and 4G/LTE data works on my device with LineageOS 14.1 on the 05R radio firmware. Although I am aware that an earlier OTA (NCQS26.69-64-8) did break the cell radio for some device owners running custom ROMs.
MotoJunkie01 said:
Voice, MMS/SMS, and 4G/LTE data works on my device with LineageOS 14.1 on the 05R radio firmware. Although I am aware that an earlier OTA (NCQS26.69-64-8) did break the cell radio for some device owners running custom ROMs.
Click to expand...
Click to collapse
So, if i want to update I have to wipe my data.
EarthMan1 said:
So, if i want to update I have to wipe my data.
Click to expand...
Click to collapse
No. But if you want to install this ROM, you will need to format /userdata in order to disable force encryption. If you want your data encrypted, you are not required to format /userdata.
No, I want only to install the partition updater.
EarthMan1 said:
No, I want only to install the partition updater.
Click to expand...
Click to collapse
Then formatting data is not necessary. Keep in mind that the partition updater does not change your radio firmware. You'll still have the 05R radio version after updating your partitions. The partition updater updates your bootloader, /devcfg and /oem partitions.
So if your radio didn't work on custom ROMs before, the partition updater likely will not change that.
Why this partition updater size is big compared to the NCQS26.69-56 one.
EarthMan1 said:
Why this partition updater size is big compared to the NCQS26.69-56 one.
Click to expand...
Click to collapse
Because the /oem partition is large (656 MB)
Why isn't it included in the 56 one
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
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
SYSTEM DIALOG ERROR DISABLER V2.0
SUPPORT: TELEGRAM CHANNEL - TELEGRAM GROUP - SUPPORT ME
ABOUT THIS:Magisk module to disable system alerts on every boot forever, based on Dynamic Installer
Features:
Disabling alerts includes the most common "There is an internal problem with the device, contact the manufacturer for more information"
HOW DO I USE IT?
Code:
1. Simply install the module by Magisk app
2. The process requires the recompilation of a .JAR so be patient!
CREDITS TO:
Me @BlassGO (Developer of System Dialog Error Disabler and Dynamic Installer)
System Dialog Error Disabler 2.0
WARNING: In case of any ERROR, delete the module: /data/adb/modules/dialog-error-disabler
Reserved
Will be testing as soon as I do a full backup. Fiddling with stuff last night threw me into an unexpected bootloop and I hadn't backed up, so I just got things back in order.
Edit: installed, warning still appears
Jason Hugg said:
Will be testing as soon as I do a full backup. Fiddling with stuff last night threw me into an unexpected bootloop and I hadn't backed up, so I just got things back in order.
Edit: installed, warning still appears
Click to expand...
Click to collapse
Hi, in what version of android and can u send me ur stock services.jar? The magisk module installation log would also be helpful.
Moto G Power (2021} A11 LOS 18 gsi, stock recovery, stock kernel magisk patched boot.img, verity off, system r/w
Jason Hugg said:
Moto G Power (2021} A11 LOS 18 gsi, stock recovery, stock kernel magisk patched boot.img, verity off, system r/w
Click to expand...
Click to collapse
Okay, also send me the installation log (there is a save button at the top after installation in the magisk app)
Jason Hugg said:
Moto G Power (2021} A11 LOS 18 gsi, stock recovery, stock kernel magisk patched boot.img, verity off, system r/w
Click to expand...
Click to collapse
Thx for the services.jar, I found the problem, I will release a more generic update soon
Jason Hugg said:
Moto G Power (2021} A11 LOS 18 gsi, stock recovery, stock kernel magisk patched boot.img, verity off, system r/w
Click to expand...
Click to collapse
Done, u can try the new version
Can we get additionals info about this module?? What can be done if bootloop?? What about OEM? Samsung or other, Which Android it supports?
Is there for example a hard force uninstaller to recover?
Thx
Can you put this on your github repo?
Just for some clarification...this removes the message after boot or while on the bootscreen regarding an unlocked bootloader?
Personally I'm looking for it to remove the message while on the bootscreen as I get none after boot.
kevinco1 said:
Just for some clarification...this removes the message after boot or while on the bootscreen regarding an unlocked bootloader?
Personally I'm looking for it to remove the message while on the bootscreen as I get none after boot.
Click to expand...
Click to collapse
im looking for the same thing
Disable Force Encryption NEODo you all know what DFE is? no?
Anyway. Basically, your device has an encrypted data section "/data" by default. Let's look at the advantages of google's solution that we will lose after disabling encryption:
- Confidence in data retention. Even if your device has TWRP/OFOX or other custom Recvoery, before accessing your data, you will need to enter the password from the lockscreen, otherwise it will be impossible to read the data.
What disadvantages follow from this?
- As an enthusiast who wants to flash different ROMs, you may have noticed that every time that you flash a new ROM, you have to format the "/data" section. Which can be a pain.
Why is it necessary to do this?
- The fact that every ROM is assembled/compiled on a different database and may have different approaches (encryption keys) for data encryption. In order for this to work you need to format the data partition so that when the new ROM boots it can encrypt the system with its own unique encryption keys, so that the integrity of the data partition is maintained and it is accessible to the user.
So what does the DFE do?
- Removes the keys that are used to encrypt the data section from the fstab file
Read more about fstab here source.android.com
What are the advantages of using DFE?
- You don't need to FORMAT the data in the following cases:
*If you change the android database (From 11 to 12 and vice versa)
*If you change vendor database, miui/aosp/OOS/LOS and so on
*** !!!! You will still need to make wipe data for the ROM to work correctly
-There are also disadvantages:
*Since the data is not encrypted in any way, then access to them is free. Anyone who gets access to your device will be able to access ALL the data
*You need to carefully monitor the sequence of actions when installing or changing the ROM, so that the DFE is active, otherwise you may lose data because the data will try to be encrypted again, you will get a bootloop, and all data will be lost
What is DFE-NEO?
*Many people know DFE from this thread XDA, it has stopped working for A/B devices with dynamic partitions, there is also a problem that in some ROMs the system has the RO(Read-Only) status of the system partition. Starting with A13 Google will promote EROFS(Enhanced Read-Only File System) which will not be possible to manipulate without first converting to EXT4, in order to change the status to RW(Read-Write). Because of this, it is not possible to modify fstab directly in 100% of cases. This is where DFE-NEO comes in.
*The NEO method works by utilizing Magiskinit and Overlay.d GitHub
How does it work without Magisk?
*In fact, in no way. If my script does not detect magisk in the boot_a/Boot_b section, magisk will be installed, after which the main bianrys files will be deleted, so there will be no root access but magiskinit itself will continue to work. In this regard, the system boot time will be longer by 40-50 seconds ( from the brand logo )
And so what can this script do:
-Hides Encryption - Forces the system to think that the data is encrypted.
-Reflash recovery after OTA - only for devices with recovery in boot_a/_b
-Flash current recovery - only for devices with recovery in boot_a/_b
-Flash DFE
-Flash magisk
Spoiler: Arguments.txt
{
"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"
}
If you want to change the parameters , then you need to change the file argumetns.txt inside the archive , or put the modified arguments.txt to the archive, or to rebuild the archive with the changed argumetns.txt
Code:
# legacy or neo
DFE method=neo
# both | in-current | un-current
Flash SLOT=both
# none|system|bootloader|recovery
Reboot after installing=none
# You can add your own language, to do this, just drop
a file into the language folder by analogy with the topic
that is already there
# indo|russian|english
Language=english
Code:
# ================================================== #
Force reading arguments.txt=false
# ================================================== #
Flash DFE= true
Disable AVB= true
Disable QUOTA= true
Hide not encrypted= true
# ================================================== #
Flash Magisk= false
# ================================================== #
Reflash Recovery for OTA= false
Reflash current Recovery for Recovery= false
# ================================================== #
Wipe DATA= false
Remove PIN= false
# ================================================== #
Skip warning= false
Modes of operation of these parameters
These parameters have two modes:
• true (yes, true),
• false(no, not true)
Exceptions for specific parameters
• DFE method(DFE method)= neo(new method)
Another argument for DFE method
legacy(old method)
• Flash slot= both (patching boot_a and boot_b sections, also applies to magisk firmware, twrp)
More arguments for Flash slot
• in-current (patching of the boot_x section, where x is the current slot, also applies to magisk firmware, twrp)
• un-current (patching the boot_x partition, where x is the opposite slot)
• Reboot after installing(Reboot after installation)= none (no, that is, there will be no reboot)
More arguments for Reboot after installing
• system(restart into the system, simple reboot)
• bootloader (reboot to fastboot mode)
• recovery (reboot into recovery mode)
• Language(installer language)=english(English)
More arguments for Language
• indo(Indonesian)
• russian (Russian language)
So we have sorted out the modes of operation of all parameters. Now, what does each of them mean.
The values of these parameters
Here the functions of the parameters are described in true mode, for exceptions depending on the mode of operation of the parameter
• DFE method - DFE patching method
• Flash slot - patching the boot partition
• Reboot after installing - reboot after installation
• DISABLE DINAMIC REFRESHRATE - disable dynamic screen formatting, ONLY FOR MIUI
• Language - the language of the installer
• Force reading arguments.txt - dfe-neo will immediately address the arguments in arguments.txt without the possibility of creating a temporary arguments.txt
• Flash DFE - DFE firmware
• Hide not encrypted - The ROM will think that encryption is enabled
• Skip warning - at the end, a guide will be shown on the correct use of dfe after firmware
• Reflash recovery for ota - reinstalling recovery after ota updates, according to the Flash slot parameter mode=
• Reflash current Recovery for Recovery - flash the current recovery, according to the Flash slot parameter mode=
• Wipe DATA - deleting the contents of the /data section without formatting the internal memory (where the Android, Downloads, Music, etc. folders are located) If you sew DFE for the first time, then we still do format data
• Remove PIN - remove password
• Disable AVB - system integrity check is disabled (or whatever you call it, you can set false if you flash magisk)
• Disable QUOTA - (to be honest, I didn't understand what it was, but you can leave it true)
• Flash Magisk - Installing Magisk, according to the Flash slot parameter mode=
And you can also set up your own temporary arguments.txt during installation:
In DFE-NEO, in addition to using arguments.txt in .zip archive, you can still set up your temporary one.
Launch the dfe-neo archive and select Configure Arguments now ( volume + >> volume - )
And we are offered to configure the parameters.
Volume + indicates change
Volume - indicates select
What should I choose DFE method= neo or legacy?
• Neo method - patches the boot partition, we leave neo if the system partitions are read-only, also suitable if the system partitions are editable
• Legacy method - patches fstab.qcom in the /vendor/etc/ section, this method cannot be used if the system partitions are read-only.
Also be careful and read what the script writes at the end of the installation
If you data is encrypted, then after flashing DFE you need to format data
If DFE was installed with Magisk you can upgrade or downgrade the Magisk version later without flashing DFE again
If you uninstall Magisk via uninstall or Magisk app Then the DFE will stop its work! In this case, you will need to flash the DFE again
If DFE was WITHOUT Magisk, it WILL work, but you can also install Magisk later. And also follow the warning 1 and 2
If you install TWRP or another custom recovery, then DFE by analogy with Magisk, will stop working
If you update/Install a new ROM, then DFE will need to be flashed again, by analogy with Magisk
You can install DFE as a magisk module. BUT THIS IS NOT A MODULE, BUT JUST AN INTERFACE FOR INSTALLATION
Demo vido: https://t.me/mfpupdate/22
And also you can flash as a regular zip archive via TWRP, while you do not have to reboot TWRP.
The work consists of the same mechanism as Magisk. If your recovery is located in boot, then after updating / flashing twrp, just like magisk, dfe will be overwritten
After updating/changing ROM you need to reflash dfe again
You can flash dfe without rebooting twrp
No needed for system to be RW for DFE to work
Support erofs
Support flashing from magisk app ( like module magisk )
Later from the computer I will supplement the post. I will add screenshots, etc.
Download link - SourceForge
TG group : @PocoF3DFE
Donate only TG link https://t.me/mfpupdate/47
Great job Alexey. Very useful mod
LeeGarChat said:
Hello everyone, I am writing a script to disable encryption on A/B devices. if you help me with testing on other devices, I will be glad, at the moment it works fine for Poco f3 ( Alioth/Aliothin ). I'm sure it will work just as well on other devices.
And so what can this script:
Hide no encrypted - Forces the system to think that the data is encrypted.
Reflash recovery after OTA - only for devices with recovery into boot_a/_b
Flash current recovery - only for devices with recovery into boot_a/_b
Flash DFE
Flash magisk
The work consists of the same mechanism as Magisk. If u recovery if your recovery is located in boot, then after updating / flashing twrp, just like magisk, dfe will turn off
After update/change ROM u need reflash dfe
You can flashing dfe without reboot twrp
No needed RW system
Support erofs
Support flashing from magisk app ( like module magisk )
Later from the computer I will supplement the post. I will add screenshots, etc.
TG group : @PocoF3DFE
Click to expand...
Click to collapse
Great job bro its perfectly work on my Redmi Note 11 Spes, thanks buddy
sorry for my noob question:does it solove the read-only attribute for erofs partion，my phone is civi （code mona）
wsdyleon said:
sorry for my noob question:does it solove the read-only attribute for erofs partion，my phone is civi （code mona）
Click to expand...
Click to collapse
Yes, if I understand u. Anyway it's working on RW system and RO system. But anyway waiting 0.8.0 beta, because in > 0.7.0 patching only boot partitions, I think need patching recovery partition for device with recovery
LeeGarChat said:
Yes, if I understand u. Anyway it's working on RW system and RO system. But anyway waiting 0.8.0 beta, because in > 0.7.0 patching only boot partitions, I think need patching recovery partition for device with recovery
Click to expand...
Click to collapse
thank u for your answer，but i donnt konw how to flash it.i flash"dfe+magisk+reflash"on my phone in twrp，but bootloop for me
LeeGarChat said:
Yes, if I understand u. Anyway it's working on RW system and RO system. But anyway waiting 0.8.0 beta, because in > 0.7.0 patching only boot partitions, I think need patching recovery partition for device with recovery
Click to expand...
Click to collapse
my english still sucks,after flashing the zip ，the ro system would still ro，just dfe。am i right?
LeeGarChat said:
Download link - SourceForge
Click to expand...
Click to collapse
Great and Congrats!
Can you explain about each zip file made?
Is there a situation for each file?
What does each file do exactly?
Which file should I choose?
----------------------------------------
UPD.
Okay OP. Good work but have consequencies........
Here what I made:
installed magisk;
installed DFE-NEO-0.7.0-BETA+HNE.zip via magisk - modules;
Rebooted device.
Problem: Red message in the screen (look attached SS).
Solved with:
USB Debugging enable;Permission adb Okay;cmd command:
Code:
D:\Program Android\platform-tools>adb shell
Mydevice:/ $ pm list packages
package:com.google.android.networkstack.tethering
package:com.android.fmradio
package:com.android.temperature
[...]
package:com.android.theme.icon_pack.filled.settings
package:com.android.watermark
package:com.android.dreams.basic
[...]
Mydevice:/ $ pm uninstall --user 0 com.android.watermark
Success
127|Mydevice:/ $ exit
D:\Program Android\platform-tools>adb reboot
D:\Program Android\platform-tools>
Reboot device and Red message good bye.
My device fir reference: MTK arm64 -- armv8-a - A11 - TWRP AB - ro.virtual_ab.enabled=true
lopestom said:
Great and Congrats!
Can you explain about each zip file made?
Is there a situation for each file?
What does each file do exactly?
Which file should I choose?
----------------------------------------
UPD.
Okay OP. Good work but have consequencies........
Here what I made:
installed magisk;
installed DFE-NEO-0.7.0-BETA+HNE.zip via magisk - modules;
Rebooted device.
Problem: Red message in the screen (look attached SS).
Solved with:
USB Debugging enable;Permission adb Okay;cmd command:
Code:
D:\Program Android\platform-tools>adb shell
Mydevice:/ $ pm list packages
package:com.google.android.networkstack.tethering
package:com.android.fmradio
package:com.android.temperature
[...]
package:com.android.theme.icon_pack.filled.settings
package:com.android.watermark
package:com.android.dreams.basic
[...]
Mydevice:/ $ pm uninstall --user 0 com.android.watermark
Success
127|Mydevice:/ $ exit
D:\Program Android\platform-tools>adb reboot
D:\Program Android\platform-tools>
Reboot device and Red message good bye.
My device fir reference: MTK arm64 -- armv8-a - A11 - TWRP AB - ro.virtual_ab.enabled=true
Click to expand...
Click to collapse
Thanks for feedback. I'll try fix it. After installing DFE noe, is your device no longer encrypted?
LeeGarChat said:
Thanks for feedback. I'll try fix it. After installing DFE noe, is your device no longer encrypted?
Click to expand...
Click to collapse
I can make backup of Data now with TWRP.
But..........
I need to do more testing regarding the ROM.
I fixed a reset - FORMAT DATA with TWRP to see/test if everything would work fine after that.
Knowing that there would be a possibility it might not work, re-install your zip file and reboot to test again.
So there's a big problem: - WiFi connection doesn't work
- going to settings - Security - Encryption&credentials =====>>> Black Screen .......... stop ............ go back setting automatically
- others??
Do not worry about me. I have experience in getting the device running normally. The device is also not for my daily use.
So I will need time for more testing or you should write for users not to do a factory reset.
lopestom said:
I can make backup of Data now with TWRP.
But..........
I need to do more testing regarding the ROM.
I fixed a reset - FORMAT DATA with TWRP to see/test if everything would work fine after that.
Knowing that there would be a possibility it might not work, re-install your zip file and reboot to test again.
So there's a big problem: - WiFi connection doesn't work
- going to settings - Security - Encryption&credentials =====>>> Black Screen .......... stop ............ go back setting automatically
- others??
Do not worry about me. I have experience in getting the device running normally. The device is also not for my daily use.
So I will need time for more testing or you should write for users not to do a factory reset.
Click to expand...
Click to collapse
Send me download link on you ROM. I'll check structure
LeeGarChat said:
Send me download link on you ROM. I'll check structure
Click to expand...
Click to collapse
UMIDIGI Power 5 4GB_N_V1.0_20220315 - SPFT release
UMIDIGI_POWER5_4GB_N_V1-0_20220315.rar
Great.
lopestom said:
I can make backup of Data now with TWRP.
But..........
I need to do more testing regarding the ROM.
I fixed a reset - FORMAT DATA with TWRP to see/test if everything would work fine after that.
Knowing that there would be a possibility it might not work, re-install your zip file and reboot to test again.
So there's a big problem: - WiFi connection doesn't work
- going to settings - Security - Encryption&credentials =====>>> Black Screen .......... stop ............ go back setting automatically
- others??
Do not worry about me. I have experience in getting the device running normally. The device is also not for my daily use.
So I will need time for more testing or you should write for users not to do a factory reset.
Click to expand...
Click to collapse
Test 0.9.0 version please
LeeGarChat said:
Test 0.9.0 version please
Click to expand...
Click to collapse
Thanks man. I appreciate what you're doing.
I already tried with this and newer version DFE-NEO-0.10.1-BETA.zip having the same situation as before.
Unfortunately there is something that blocks the wifi working after installing DFE-NEO-x.xx.x-BETA.zip. Regarding this, I tested restoring the NVRAM, NVCFG and NVDATA files and the wifi started to work, however the part that DFE-NEO does is lost.
Is there something that DFE-NEO does with NvRam, NvCfg and NvData partitions?? Is it something that is a prerequisite for the ROM to work encrypted and consequently to work or not work the wifi?
I couldn't try all possibilities to investigate and test as I have been sick for a few days.
lopestom said:
Thanks man. I appreciate what you're doing.
I already tried with this and newer version DFE-NEO-0.10.1-BETA.zip having the same situation as before.
Unfortunately there is something that blocks the wifi working after installing DFE-NEO-x.xx.x-BETA.zip. Regarding this, I tested restoring the NVRAM, NVCFG and NVDATA files and the wifi started to work, however the part that DFE-NEO does is lost.
Is there something that DFE-NEO does with NvRam, NvCfg and NvData partitions?? Is it something that is a prerequisite for the ROM to work encrypted and consequently to work or not work the wifi?
I couldn't try all possibilities to investigate and test as I have been sick for a few days.
Click to expand...
Click to collapse
Some ROMs may not work correctly with DFE, due to the fact that the ROMs are designed to work with an encrypted data partition, or there are any protections. also, on some ROMs, the data split must be formatted according to the associated with certain keys -C and -O -g. DFE-NEO does not modify any partitions except boot, just like magisk. DFE-NEO works thanks to magisk-init, which allows you to run custom scripts during ROM startup. the script that is executed during system startup, makes a copy of fstab, deletes the encryption keys and mounts it in place of the original fstab, there is no full-fledged verification of the system. all work is based on magisk logic
Awesome job LeeGarChat, much appreciated by all users I have quoted your post link in other threads too so all can see the magic .
My device is Shamshung Galeksi M21 2021 (SM-M215G) But when I flashed from TWRP it showed some red error : 577 something like that, then when I flashed from Majisk it showed error code 3 : DFE-NEO only for virtual_ab devices
Treble Check shows my device is treble compliant having AB partition and TWRP displays following partitions: System, Vendor, Product, Odm, Cache, Data, EFS, Metadata, Sec EFS, Micro SD Card, USB OTG.
In my Shaomi Readmi Note 10 (mohito) TWRP displays Slot A & Slot B under Advanced Tab and ROMs get directly flashed to Inactive Slot B, also everytime I try flash new custom ROM I have to first flash MyUi Factory ROM and also System partition doesnt show in TWRP Mount section.
My question is what is the difference between Shamshung Galeksi M21 Android 11 out-of-box & Shaomi Readmi Note 10 Mohito ? why TWRP shows System partition mount in Shamshung and not in shaomi though both are A/B devices?
Pls help.
LeeGarChat said:
Some ROMs may not work correctly with DFE, due to the fact that the ROMs are designed to work with an encrypted data partition, or there are any protections. also, on some ROMs, the data split must be formatted according to the associated with certain keys -C and -O -g. DFE-NEO does not modify any partitions except boot, just like magisk. DFE-NEO works thanks to magisk-init, which allows you to run custom scripts during ROM startup. the script that is executed during system startup, makes a copy of fstab, deletes the encryption keys and mounts it in place of the original fstab, there is no full-fledged verification of the system. all work is based on magisk logic
Click to expand...
Click to collapse
Great News!
@2mkl and me solved the Wi-Fi issue......... But I not write here about.
Thanks again
lopestom said:
Great News!
@2mkl and me solved the Wi-Fi issue......... But I not write here about.
Thanks again
Click to expand...
Click to collapse
can you tell us in PM how you fixed the problems you wrote about earlier
History of updates and news
June 16
Update DFE-NEO 0.10.0 beta
- Added Feature, choose wether you want to flash DFE legacy / neo ( for legacy need RW system and not working with erofs)
july 14
Update dfe-neo beta 0.11.0
- Add magisk 25.1
- Add volume key selector
- Add remove lockscreen-pin select for key selector
july 20
Update dfe-neo beta 0.12.0
- Add new arguments:
- Wipe data
- Reboot after
july 22
DFE-NEO-0.12.4-BETA update
- Add additional settings (optional) like wipe data, reboot after
- Add disable dynamic refrash rate display ( only miui and works with dfe-neo method )
july 23
DFE-NEO-0.13.0-BETA update
- Add new arguments into arguments.txt, now u can change it without volume key
- Add new options "remove avb" " remove quota" ( default removed )
- The code has been slightly rewritten
- Update somthing patches for safety net fix based on later version 2.3.1 https://github.com/kdrag0n/safetynet-fix/releases/tag/v2.3.1
july 24
DFE-NEO-0.13.3-BETA update
- Minor fix
- Cleaning ui print
- Added calculation of script running time
july 25
I show by my example how to install a ROM in conjunction with DFE-NEO, as well as additional zips
Download DFE-NEO LINK ( Alway later version )
Thread XDA LINK
Please subscribe to the updates and news channel LINK
Thanks
july 28
DFE-NEO-0.14.0-BETA update
- Add language select ( it is currently configured only in the file arguments.txt )
Languages:
• Russian
• English
• Indo
• you can add your own language
- Fix ro.dfe.neo.state
- Add force reading arguments.txt
july 30
DFE-NEO-0.14.1-BETA update
- Reworked my_print function to work correctly in other languages. previously, it worked fine only with English
- Updated the Russian language. fixed typos
july 30
DFE-NEO-0.15.0-BETA update
- Add support A-Only devices
Languages v003:
- There was a bug with a large number of characters ****