Related
The Kernal Source has been released by Razer.
Links to the source is at the bottom of this page:
http://support.razerzone.com/mobile/razer-phone
Here are the links to the source just in case:
MR1 Releases:
Build 853
Build 851
Production Releases:
Build 822
Build 813
It has been talked about already but not in this section. This is where it belongs and nice job posting direct links to it.
https://forum.xda-developers.com/razer-phone/how-to/source-code-posted-t3719665
MedicStuder said:
Surprised no one else posted in the section with this. The Kernal Source has been released by Razer which means modding can start.
https://www.xda-developers.com/razer-phone-kernel-source-code/
http://www.androidpolice.com/2017/12/15/kernel-source-code-just-released-razer-phone/
https://www.gizchina.com/2017/12/16/razer-releases-kernel-source-files-razer-phone/
Links to the source is at the bottom of this page:
http://support.razerzone.com/mobile/razer-phone
Here are the links to the source just in case:
MR1 Releases:
Build 853
Build 851
Production Releases:
Build 822
Build 813
Click to expand...
Click to collapse
I mentioned it in the factory image thread 5 days ago
Mods, can we pin this in the dev section since it contains the links to the needed source code for development purposes. Seems appropriate to have it pinned in this thread. thanks.
I've also got the kernel source going with CAF history included (based on LA.UM.5.7.r1) at https://github.com/jcadduono/android_kernel_razer_msm8998/tree/android-7.1
Fixed a minor bug and added some build scripts to simplify the process of configuring and building.
Added qcacld-3.0 sources into the kernel build for WiFi drivers but I appear to be missing something so it doesn't build. :/
I'm sure someone here can figure that out!
For TWRP support, essentially you'll need to build the stock kernel with additional options like f2fs and exFAT if desired. The OS and TWRP will be sharing the same kernel binaries due to the A/B setup so you *will* need to build the WiFi driver, even for recovery.
If someone is daring enough, they can simply build TWRP normally (ex. for a non-A/B device), flash it to boot_b or boot_a partition (depending what's active), boot up TWRP, and make backups of the opposite A/B partitions.
This can't actually be too hard to do, Dees_Troy has already done most of the work by supporting A/B on Pixel devices already.
I suppose I'm willing to give it a try if anyone is willing to possibly lose the ability to get into the OS until Razer releases factory images.
The chance of that happening is pretty slim, as long as we're only flashing the *active* boot partition (we'll check that in OS using mount command), we should be able to simply grab a copy of the opposite boot partition and restore it to how it was.
YOU CAN simply use fastboot to swap to the other boot partition, restoring your OS to bootable even if TWRP fails to work. (we will test this first to make sure Razer has enabled this option...)
Probably safe, but there's just that risk.
As I'm unsure exactly how to compile the WiFi drivers right now, I'll do this:
Create a normal TWRP image, which you can flash to your *active* boot partition.
Create a TWRP flashable zip that will take the ramdisk from the active boot partition and flash it to the inactive boot partition's boot image, then flash the inactive boot partition's image to your active boot partition.
Result: Both partitions contain the original stock kernel image with TWRP support and a fully working OS.
Slight issue: F2FS won't be supported because the stock kernel will have module signing enabled and TWRP won't be able to load it.
I'm also fairly certain I'll never get decryption working myself for this device...it looks like the vendor partition may be required and it is already encrypted itself? (not encrypted on the Pixel 2 so this is new)
Dees_Troy will be getting his Razer Phone next week. If anyone can get TWRP working it's him. No need to worry ?
MishaalRahman said:
Dees_Troy will be getting his Razer Phone next week. If anyone can get TWRP working it's him. No need to worry ?
Click to expand...
Click to collapse
No way! :victory:
That's the best news I've heard yet
---------- Post added at 04:44 AM ---------- Previous post was at 04:30 AM ----------
jcadduono said:
I've also got the kernel source going with CAF history included (based on LA.UM.5.7.r1) at https://github.com/jcadduono/android_kernel_razer_msm8998/tree/android-7.1
Fixed a minor bug and added some build scripts to simplify the process of configuring and building.
Added qcacld-3.0 sources into the kernel build for WiFi drivers but I appear to be missing something so it doesn't build. :/
I'm sure someone here can figure that out!
For TWRP support, essentially you'll need to build the stock kernel with additional options like f2fs and exFAT if desired. The OS and TWRP will be sharing the same kernel binaries due to the A/B setup so you *will* need to build the WiFi driver, even for recovery.
If someone is daring enough, they can simply build TWRP normally (ex. for a non-A/B device), flash it to boot_b or boot_a partition (depending what's active), boot up TWRP, and make backups of the opposite A/B partitions.
This can't actually be too hard to do, Dees_Troy has already done most of the work by supporting A/B on Pixel devices already.
I suppose I'm willing to give it a try if anyone is willing to possibly lose the ability to get into the OS until Razer releases factory images.
The chance of that happening is pretty slim, as long as we're only flashing the *active* boot partition (we'll check that in OS using mount command), we should be able to simply grab a copy of the opposite boot partition and restore it to how it was.
YOU CAN simply use fastboot to swap to the other boot partition, restoring your OS to bootable even if TWRP fails to work. (we will test this first to make sure Razer has enabled this option...)
Probably safe, but there's just that risk.
As I'm unsure exactly how to compile the WiFi drivers right now, I'll do this:
Create a normal TWRP image, which you can flash to your *active* boot partition.
Create a TWRP flashable zip that will take the ramdisk from the active boot partition and flash it to the inactive boot partition's boot image, then flash the inactive boot partition's image to your active boot partition.
Result: Both partitions contain the original stock kernel image with TWRP support and a fully working OS.
Slight issue: F2FS won't be supported because the stock kernel will have module signing enabled and TWRP won't be able to load it.
I'm also fairly certain I'll never get decryption working myself for this device...it looks like the vendor partition may be required and it is already encrypted itself? (not encrypted on the Pixel 2 so this is new)
Click to expand...
Click to collapse
I'm willing to temporarily sacarfic my device for this. I will message you tomorrow morning and we can give it a shot.
We have lift off! @jcadduono you were right :highfive:
Waiting on you for further instructions on how to proceed.
Even if this leads to no where it sure feels damn good to see the twrp logo.
Everything is going well, we're getting copies of each partition and I'm working on making factory restorable images right now.
I am fairly certain I can even support encryption on this device with no issues.
The device itself actually supports hardware Qualcomm full-disk encryption like most non-Google Qualcomm devices so it's nothing new!
However, the Razer Phone supports HW encrypted SDcards like LG does, so TWRP needs support in the actual crypto code used in the project to work with encryptable sdcards. Maybe Dees_Troy will be up to that task when he gets his phone.
TWRP images will be distributed like so:
- A twrp.img file that you flash to your active boot partition
- A zip file that copies the TWRP ramdisk from your active boot partition into your inactive boot partition, then copies your inactive boot partition to your active boot partition
The zip file will effectively install TWRP and the next time you boot TWRP it will be relying on your ROM's kernel instead of the TWRP kernel.
jcadduono said:
Legend!
Mad props to you, can't wait to see more! :good: This will be a good Christmas, can I ask whether being carrier or not will matter for installation?
Click to expand...
Click to collapse
@jcadduono Legend!
Mad props to you, can't wait to see more! :good: This will be a good Christmas, can I ask whether being carrier or not will matter for installation?
P.s I'll take a pop if you want a second test
thread stuck like Chuck for now, hopefully we can get some dev going for this device.
yeahh !!!!!!! wake up dev teams !!
Any information regarding Franco kernel?
I am just curious if the vendor.img actually changed between the March and April factory images. The reason is that in order to get data and voice to work I have to make changes to the vendor partition. If it is the same then I can exclude it in the update and avoid the process of changing vendor partition.
Thanks
Code:
*** Disclaimer ***
All flashing is done at your own risk!
While nothing from this thread should break your device,
don't come back here blaming anyone if it does!
Introduction
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and
Click to expand...
Click to collapse
Images
Installation instructions
TWRP Image Install method:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed.
Download the latest version of TWRP appropriate for your device/firmware
Reboot to TWRP
Hit Install and tap the "Install Image" button in the lower right
Browse to the location of the TWRP image on your device and select it
Select recovery from the partition list and swipe to flash
Alternate Installation Method:
Fastboot Install Method:
You will need the platform-tools from the Android SDK on your computer. Find the Android command line tools section on the page linked and install the SDK tools package. From the SDK Manager, download only the platform-tools to get adb and fastboot binaries.
Windows users will need proper drivers installed on their computer. You can try the Naked ADB drivers or the Universal ADB drivers if you don't already have a working driver installed
On your device, go into Settings -> About and find the Build Number and tap on it 7 times to enable developer settings. Press back and go into Developer Options and enable USB debugging. From your computer, open a command prompt and type:
Code:
adb reboot download
You should now be in fastboot mode.
Download the correct image file and copy the file into the same folder as your adb and fastboot binaries. Rename the image to twrp.img and type:
Code:
fastboot flash recovery twrp.img
Code:
fastboot reboot
Click to expand...
Click to collapse
Device Changelog
Current version: 3.5.1_9-0:
Initial official release - no device-specific changes
Click to expand...
Click to collapse
Older Device-specific versions:
3.3.1-1:
Update prebuilt kernel to support both stock and LOS decryption
3.2.0-1:
[Fix] Re-sync build tree so recovery boots
[Update] Source-built kernel with f2fs/ntfs/exfat support
Click to expand...
Click to collapse
Click to expand...
Click to collapse
TWRP Official Change Log
Downloads
Download
Latest Official versions
Latest Unofficial versions
Sources
Device tree
Kernel source
Click to expand...
Click to collapse
Known Issues
Device-specific
N/A
TWRP Upstream
Encrypted backups are broken - DO NOT USE THIS FEATURE!!
Click to expand...
Click to collapse
Bug Reporting
If you have an issue, the first step is to post a recovery log so we can determine the cause of the issue. This is done in recovery using Advanced -> Copy Log, or adb pull /tmp/recovery.log. Once a log is uploaded we can determine how best to proceed. NOTE: Posts that are reporting bugs or issues without an accompanying recovery log will be ignored! Additionally, providing details about your device setup, including variant, firmware version, and exact steps to reproduce your issue will also be helpful in diagnosing the problem.
{
"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 your issue is determined to be a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to contact us via our website. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
Click to expand...
Click to collapse
TWRP Official Change Log
Current version: 3.5.1:
TeamWin has prepared a mini release before Android-11 support.
Android 9 Branch only:
Build fixes in 7.1 tree - CaptainThrowback
SAR Update script name for clarity - CaptainThrowback
SAR: Don't follow symbolic links for block devices - bigbiff
Android 9 and Android 10 Branches:
Wrappedkey support running only on FBE devices - CaptainThrowback
TWRP App log information reduced - epicX67
Refresh details after system wipe and adb sideload - AdrianDC
Chinese translation updates - betaxb
Support keymaster 2 - PeterCxy
add tzdata to TWRP for timezones - CaptainThrowback
ParitionManager: support delayed adopted storage mount - PeterCxy
Support to start terminal from file manager directory - AndroiableDroid
Nano support - nebrassy
Add nano support to open files from file manager - CaptainThrowback
Include new magisk apk support to be installed by TWRP - ianmacd
Add support to change directory name where TWRP stores backups - epicX67
Add bash support - not the default shell - DarthJabba9
ORS support to format data - AdrianDC
Add support to flash both slots when flashing an image - epicX67
NL translation updates - ianmacd
Cleanup
Installation cleanup - remove dupe PackageExtractFn - klabit87
Remove logd-reinit service - CaptainThrowback
Fixes
Restore system root context - bigbiff
Only include keymaster 2 if tree supports it - CaptainThrowback
Strip lines containing '--' in language_helper.py - ianmacd
Unlocalized string fix - ianmacd
Click to expand...
Click to collapse
Older versions:
3.5.0:
For this release we are breaking down new support for devices based on android trees and device compatibility. For Pie and earlier devices, they will be built out of the android-9.0 branch. For devices that
are released with Android Version 10, they will be supported under the android-10 branch. The separation became apparent when a lot of functionality was dropped in the android-10 release last year.
You will notice a new version scheme. Devices that are built in the android-9 tree will be suffixed with 3.5.0_9.
Devices built in the android-10 tree will be suffixed with 10 like 3.5.0_10. Each device tree update will have a
final suffix for any updates made for the device like 3.5.0_10-1.
Android 9 only
Fix building in android-5.1 trees - CaptainThrowback
New QTI Haptics Support - AndroidableDroid
New TSPDriver Haptics Support - LameMonster82
Selinux restore issues - AndroidableDroid
OEM build fixes - Fighter19
More file extension support in Gui file selector - Mauronofrio
FBE Fixes - CaptainThrowback
Ozip Decryption - Mauronofrio
Don't use persist for recovery logs - bigbiff
Delay touch startup if necessary - bigbiff
Spanish translation Updates - R0rt1z2
Fix cache wiping on Slot A only devices - AndroidableDroid
Exclude dumpsys directory from backups - DarthJabba9
Gerrman translation Updates - 4ndyZ
HW Rotation during runtime (does not affect touch panel) - webgeek1234
API 24 fixes - AndroidableDroid
vold_decrypt error on unmount - CaptainThrowback
Multiuser - warn when users are not decrypted - noahajac
FDE encryption fixes - CaptainThrowback
Crypto state fixes - nebrassy
Chinese translation Updates - Whyle
Theme updates to match android-10 release: CaptainThrowback
Move TWRP App install to Advanced page - Dees_Troy
Update Russian Translation - f2065
Android 10
Omni 10 minimal support: CaptainThrowback
General Bringup: Bigbiff, Mauronofrio, AndroidableDroid, CaptainThrowback, ianmacd, DarthJabba9
Encryption support: Bigbiff, Mauronofrio, CaptainThrowback
Fastbootd support: Bigbiff
Install Support: Bigbiff, CaptainThrowback
Magisk Support: Bigbiff
Backuptool Support: Chaosmaster
Apex support: Bigbiff
Dynamic Partition Support: Bigbiff
3.4.0:
System As Root (SAR)
Fix backup and restore using SAR - dianlujitao
System mount point - Chaosmaster
ORS - Chaosmaster
Zip install - Chaosmaster
system_root bind mount to /system - Chaosmaster
Autodetection of SAR - Chaosmaster
Digest
fix creation of digests for sub-partitions (was bugfix applied to many devices since last year) - Bigbiff
Encryption
ext4Crypt Wrapped Key Update - Peter Cai
Fix upgrading encryption key if export fails - Peter Cai
Fix wrapped key support for devices without metadata partition - mauronofrio
Don't skip decryption when using block map file in order to write to /data in ORS - CaptainThrowback
FDE - Decrypt master key first - AndroidableDroid
vold_decrypt - set Android version and patch level automatically - CaptainThrowback
Set wrapped decrypt support by twrp flag - Peter Cai
Don't try wrapped support unless needed - mauronofrio
restore ext4 policy on /data/cache - Bigbiff
multiuser decryption - Noah Jacobson
FDE retry - AndroidableDroid
TWRP App
unmount system after checking for app - Bigbiff
Prebuilt updates
[email protected] - cryptomilk
Compilation Fixes
TW_EXFAT_FUSE compilation fixes - Bigbiff
libuuid - cryptomilk
'system/etc/ld.config.txt' not found error - Martin Dünkelmann
Language Updates
Portugal - Vasco Machado
Dutch - Ian Macdonald
Turkish - Fatih Fırıncı
Localisation of Backup_Tar - Ian Macdonald
ld.config.txt
updates for 8.x trees - CaptainThrowback
fix search path for /sbin - CaptainThrowback
/sbin should come first in search path - Ian Macdonald
General Bugs
Fix persistent log storage - SyberHexen
Compress Persistent Logs - Bigbiff
FB2PNG compilation errors - Bigbiff
exclude per_boot from backups - Darth9
Unmount all directories that point to same block device - AndroidableDroid
Blank screen fixes - Sean hoyt
Toolbox is default on android-9+ - mauronofrio
Cleanup
Typo fix in comment - VDavid003
newlines in ext4crypt - CaptainThrowback
TW_OEM_BUILD compilation issue - Patrick Zacharias
Fix Dependency requirements - Dees_Troy
Fix Symbolic links for BB and Toolbox - Dees_Troy
Bootloader Message
cleanup - Alessandro Astone
add configurable offsets
Error Cleanup
uevent errors and decryption error - mauronofrio
using copy_file to copy files from /etc - CaptainThrowback
ueventd access to /acct - early directory creation in init - cryptomilk
Haptics
TSP Driver - LameMonster82
QTI Input - AndroidableDroid
update_engine
read all asserts - Hernán Castañón
Resetprop
Add Resetprop from Magisk - CaptainThrowback & mauronofrio
compile from source - Chaosmaster
fix for android-7 and earlier - Chaosmaster
cleanup for spaces in properties - AndroidableDroid
Properties
Add Property override - Chaosmaster
Backuptool
mount system and vendor for A/B installs for backuptool - Chaosmaster
twrpTar
fix backup freezes when pigz and openaes are used - Fabrice Bellet
Zip Installs
Info for A/B zip installing to inactive slot - Chaosmaster
Reboot to system button now allows to be rebooted to different partitions after zip install
progressbar rework - Chaosmaster
Magisk updates
update binaries from source - AndroidableDroid
A/B Updater Zip Template
rewrite A/B installer zip from scratch using a new generic template and latest magiskboot - osm0sis
installer zip support for recovery_a/recovery_b partition ramdisks on newer 2SI SAR A/B devices - osm0sis
generate installer zips for all prod A/B devices - bigbiff
improve installer zip dump/write speed and add more error catching - arter97 & osm0sis
OZIP Encryption Support
add OZIP encryption - mauronofrio
File Selector
Support for more extensions in File Selector - mauronofrio
3.3.1:
Fix selinux issues during formatting - dianlujitao
Various fixes for toybox and toolbox builds - CaptainThrowback and bigbiff
Flash both A and B partitions when installing a recovery ramdisk - Dees_Troy
Add option to uninstall TWRP app from /system - Dees_Troy
Create digest for subpartitions - bigbiff
3.3.0:
Merge AOSP 9.0 r3 (Dees_Troy)
Use ANDROID_ROOT variable instead of hard coding to /system (CaptainThrowback)
Decrypt FBE on 9.0 and metadata decrypt (Dees_Troy)
vold decrypt updates (nijel8, CaptainThrowback)
Support vibration on LED class devices (notsyncing)
Metadata decrypt support for Pixel 3 (Dees_Troy)
Support rotating the display via build flag (vladimiroltean)
Reboot to EDL mode button (mauronofrio)
Support MTP on FFS devices (bigbiff)
Update FDE decrypt to support keymaster 3 and 4 (Dees_Troy)
Detect mkfs.f2fs version to properly format on f2fs partitions (Dees_Troy)
Allow TWRP to use md5 and sha256 checksums for zip installs (bigbiff)
TWRP can use /data/cache/recovery and /persist/cache/recovery on AB devices with no cache partition (bigbiff)
Switch part of advanced menus in TWRP to use a listbox of options (Dees_Troy)
Use magiskboot to allow repacking boot images for installing TWRP (Dees_Troy with thanks to topjohnwu of course)
3.2.3:
Fix automatic installing of OTA zips on encrypted devices
Remove SuperSU from TWRP
Support both md5 and md5sum file extensions when doing MD5 checking for zip files
3.2.2:
adb backup fixes
OTA style update zips will now install automatically without prompting for decrypt
minor tweaks to handling date/time on Qualcomm devices
updates to some language translations
3.2.1:
minui fixes (cryptomilk)
Better android-8.0 compatibility in ROM trees (Dees_Troy)
Fix missing library in android-8.0 (nkk71)
Fix inconsistent SDCard naming (DevUt)
Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)
3.2.0:
Allow restoring adb backups in the TWRP GUI (bigbiff)
Fix gzip backup error in adb backups (bigbiff)
Fix a bug in TWRP's backup routines that occasionally corrupted backup files (nkk71)
Better support for installing Android 8.0 based zips due to legacy props (nkk71)
Support vold decrypt with keymaster 3.0 in 8.0 firmwares (nkk71)
Decrypt of synthetic passwords for Pixel 2 (Dees_Troy)
Support newer ext4 FBE policies for backup and restore in libtar (Dees_Troy)
v2 fstab support (Dees_Troy)
Bring TWRP forward to android 8.0 AOSP base (Dees_Troy)
Various other minor bugfixes and tweaks
3.1.1:
Backups will now include adopted storage keys (Dees_Troy)
Fixed an adb restore issue (bigbiff)
Fixed rebooting when no OS is present (Dees_Troy)
Fixed line wrapping in the GUI terminal (_that)
Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)
3.1.0:
vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
adb backup to stream a backup directly to or from your PC, see documentation here (bigbiff)
tweak MTP startup routines (mdmower)
support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
better indicate to users that internal storage is not backed up (Dees_Troy)
improve automatic determination of TW_THEME (mdmower)
minimal getcap and setcap support (_that)
try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
shut off backlight with power key (mdmower)
timeout during FDE decrypt (Dees_Troy and nkk71)
support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
boot slot support (Dees_Troy)
TWRP app install prompt during reboot (Dees_Troy)
support for AB OTA zips (Dees_Troy)
support new Android 7.x log command (Dees_Troy)
update recovery sources to AOSP 7.1 (Dees_Troy)
numerous bugfixes and improvements by too many people to mention
3.0.3:
Partial release to help support the release of the Official TWRP app
3.0.2:
Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
Add Greek translation to some builds.
3.0.1:
support new CM 13.0 pattern encryption (sultanqasim)
fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
libtar updated to latest upstream and fixes (jcadduono)
fixes for loading custom themes (_that)
TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
translation updates - added Italian, Czech and Polish and significant updates to Dutch
progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
fix input box text display (Dees_Troy)
reboot option after zip install complete (bigbiff)
other mostly invisible bug fixes and improvements
3.0.0:
Completely new theme - Much more modern and much nicer looking (by z31s1g)
True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
SuperSU prompt will no longer display if a Marshmallow ROM is installed
Update exfat, exfat fuse, dosfstools (by mdmower)
Update AOSP base to 6.0
A huge laundry list of other minor fixes and tweaks
Additional Notes
WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.
Notes for themers: In addition to the updated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
2.8.7.0:
Initial ground work for software drawn keyboard (_that)
Fix handling of wiping internal storage on datamedia devices (xuefer)
Allow DataManager to set and read values from the system properties (xuefer)
Fix crash when taking screenshots on arm64 devices (xuefer)
Fix error message after an ORS script completes (Dees_Troy)
Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
Add system read only option – more details below (Dees_Troy)
Add resize2fs and GUI option to run resize2fs (Dees_Troy)
Fix crash loop caused by empty lines in AOSP recovery command file (_that)
Prevent duplicate page overlays such as multiple lock screens (mdmower)
Additional Notes
Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Had to recreate this thread as the original version got lost when the forum got flattened.
Here is my log, could you check it please?
h**ps://www.filedropper.com/recovery_4
I had to slightly modify the link to be able to insert it.
Thanks
@Captain_Throwback
I forgot, when he created the log the usual errors appeared even if he says created successfully ..
fabulas_ said:
Here is my log, could you check it please?
h**ps://www.filedropper.com/recovery_4
I had to slightly modify the link to be able to insert it.
Thanks
@Captain_Throwback
I forgot, when he created the log the usual errors appeared even if he says created successfully ..
Click to expand...
Click to collapse
Please don't post pictures of your phone screen. The recovery log is sufficient. If you feel like you really have to give me a screenshot, please use Power+Volume Down to capture a proper screenshot.
As I told you in the other thread, to use the "Copy Log" feature, you need to switch the storage to your SD card first, since your "regular" storage isn't working properly.
Please try the TWRP linked below and let me know if you still see errors. If you do, please attach another recovery log, and also provide the output of
Code:
adb logcat > logcat.txt
https://drive.google.com/file/d/1VcYhdSIuX-8OazWcpP3JVXgpYezHo0OY/view?usp=sharing
Thanks.
P.S. Please provide recovery log even if it's working, actually.
P.P.S. Also, there's no need to mention me, as you're posting in my thread so I will be notified.
Captain_Throwback said:
Please don't post pictures of your phone screen. The recovery log is sufficient. If you feel like you really have to give me a screenshot, please use Power+Volume Down to capture a proper screenshot.
As I told you in the other thread, to use the "Copy Log" feature, you need to switch the storage to your SD card first, since your "regular" storage isn't working properly.
Please try the TWRP linked below and let me know if you still see errors. If you do, please attach another recovery log, and also provide the output of
Code:
adb logcat > logcat.txt
https://drive.google.com/file/d/1VcYhdSIuX-8OazWcpP3JVXgpYezHo0OY/view?usp=sharing
Thanks.
P.S. Please provide recovery log even if it's working, actually.
P.P.S. Also, there's no need to mention me, as you're posting in my thread so I will be notified.
Click to expand...
Click to collapse
It is not clear to me how to mount the microsd as internal memory ....
I go to Mount, in the screen that appears which folders should I select? microsd card and cache are selected by default.
the check on "Mount system partition read-only" I leave it?
and then I tap on "Mount Usb Storage"?
another question the recovery you gave me should I load it and try it only after loading the usb as internal memory?
I'm sorry for the many questions but I would like to avoid making mistakes otherwise the problem becomes even more complicated.
fabulas_ said:
It is not clear to me how to mount the microsd as internal memory ....
I go to Mount, in the screen that appears which folders should I select? microsd card and cache are selected by default.
the check on "Mount system partition read-only" I leave it?
and then I tap on "Mount Usb Storage"?
another question the recovery you gave me should I load it and try it only after loading the usb as internal memory?
I'm sorry for the many questions but I would like to avoid making mistakes otherwise the problem becomes even more complicated.
Click to expand...
Click to collapse
I didn't say to mount the SD card as internal memory - I just said to select it as default storage, as in Mount -> Select Storage -> choose "Micro SD Card" -> click OK. When you do that, TWRP will copy logs to the card instead of the broken internal storage. You don't need to touch anything else.
It doesn't matter whether you do that before or after flashing the new TWRP. Please just flash it and provide the recovery log.
Captain_Throwback said:
I didn't say to mount the SD card as internal memory - I just said to select it as default storage, as in Mount -> Select Storage -> choose "Micro SD Card" -> click OK. When you do that, TWRP will copy logs to the card instead of the broken internal storage. You don't need to touch anything else.
It doesn't matter whether you do that before or after flashing the new TWRP. Please just flash it and provide the recovery log.
Click to expand...
Click to collapse
I did exactly as you said
> Select Storage -> choose "Micro SD Card" -> click OK.
and then I went back without tapping on Mount usb storage. I tried to create the log always with the twrp I had and always the same errors it gives me ...
Then I put your TWRP, always done Mount> Select Storage -> choose "Micro SD Card" -> click OK. and then I created the log and it always gives me the same errors
Here is the log
h**p://www.filedropper.com/recovery_5
I didn't understand how to retrieve the logcat.txt file
fabulas_ said:
I did exactly as you said
> Select Storage -> choose "Micro SD Card" -> click OK.
and then I went back without tapping on Mount usb storage. I tried to create the log always with the twrp I had and always the same errors it gives me ...
Then I put your TWRP, always done Mount> Select Storage -> choose "Micro SD Card" -> click OK. and then I created the log and it always gives me the same errors
Here is the log
h**p://www.filedropper.com/recovery_5
I didn't understand how to retrieve the logcat.txt file
Click to expand...
Click to collapse
You have to use adb (from your PC) to retrieve the logcat, using the command I gave you.
But after looking at your log, it seems that you need to Format Data in TWRP. Wipe -> Format Data -> type "yes". Then reboot into Android and back to TWRP. Please let me know if that resolves your issue.
Captain_Throwback said:
You have to use adb (from your PC) to retrieve the logcat, using the command I gave you.
But after looking at your log, it seems that you need to Format Data in TWRP. Wipe -> Format Data -> type "yes". Then reboot into Android and back to TWRP. Please let me know if that resolves your issue.
Click to expand...
Click to collapse
I made a format data and I solved the errors .. now he doesn't make them + ... and this is already a very important first step .. I was sure that with you I would have solved it since you are the leader of the experts.
The weird thing I am wondering is when flashing the RUU doesn't it automatically do a format data? because the RUU I flashed it I don't know how many times and this problem was always present.
I'll put here a log made now after making the format data
http://www.filedropper.com/recovery_6
Still need the logcat file?
Now the famous screen that appeared to me every time whether to allow changes to the file system or keep read-only has also disappeared, and every time I selected "keep read-only" now it is not appearing +.
Now what do I do, I put Magisk v21 on sd and then from TWRP I install it? when I installed it yesterday, as I told you, it gave me the usual errors on the Twrp during installation even if he had installed Magisk Manager but the root was not done. checking the SafetyNet also the basic integrity was false as well as the CTS ... now I hope that installing it there are no errors, I assume not, and that the SafetyNet at least the basic integrity does not become false otherwise Magisk hide does not work for me ... and I'm interested in being able to use the banking apps .. I'm waiting for your message so I proceed based on what you tell me to do.
If you prefer we can return to the other thread.
thanks a lot
fabulas_ said:
I made a format data and I solved the errors .. now he doesn't make them + ... and this is already a very important first step .. I was sure that with you I would have solved it since you are the leader of the experts.
The weird thing I am wondering is when flashing the RUU doesn't it automatically do a format data? because the RUU I flashed it I don't know how many times and this problem was always present.
I'll put here a log made now after making the format data
http://www.filedropper.com/recovery_6
Still need the logcat file?
Now the famous screen that appeared to me every time whether to allow changes to the file system or keep read-only has also disappeared, and every time I selected "keep read-only" now it is not appearing +.
Now what do I do, I put Magisk v21 on sd and then from TWRP I install it? when I installed it yesterday, as I told you, it gave me the usual errors on the Twrp during installation even if he had installed Magisk Manager but the root was not done. checking the SafetyNet also the basic integrity was false as well as the CTS ... now I hope that installing it there are no errors, I assume not, and that the SafetyNet at least the basic integrity does not become false otherwise Magisk hide does not work for me ... and I'm interested in being able to use the banking apps .. I'm waiting for your message so I proceed based on what you tell me to do.
If you prefer we can return to the other thread.
thanks a lot
Click to expand...
Click to collapse
Yes, you can flash Magisk from TWRP, and then when you boot into Android, you have to open Magisk Manager settings and enable MagiskHide if you want to pass SafetyNet.
Captain_Throwback said:
Yes, you can flash Magisk from TWRP, and then when you boot into Android, you have to open Magisk Manager settings and enable MagiskHide if you want to pass SafetyNet.
Click to expand...
Click to collapse
Installed Magisk did not give me errors on Twrp, I checked the root with Root Checker and it is done ... the big problem is that as I expected now the Safetynet as basic integrity gives me "false" while before installing Magisk it gave me " true "checked with the" SafetyNet attest "app ... even the CTS is false, in this way I don't do anything about the root since I can't deprive myself of the various banking apps ... but how is it possible that the basic integrity before installing Magisk is okay and then after installing it does not pass the check? ....
fabulas_ said:
Installed Magisk did not give me errors on Twrp, I checked the root with Root Checker and it is done ... the big problem is that as I expected now the Safetynet as basic integrity gives me "false" while before installing Magisk it gave me " true "checked with the" SafetyNet attest "app ... even the CTS is false, in this way I don't do anything about the root since I can't deprive myself of the various banking apps ... but how is it possible that the basic integrity before installing Magisk is okay and then after installing it does not pass the check? ....
Click to expand...
Click to collapse
Did you enable MagiskHide like I said?
Captain_Throwback said:
Did you enable MagiskHide like I said?
Click to expand...
Click to collapse
sorry I had tapped on magisk hyde in the home and I thought it was that ... now I have activated it in the settings and redone the check and everything went ok ... I thank you immensely for helping me solve the problem.
so in the end I didn't have the damaged memory but a farmat data was enough ... as TWRP I can leave the one you gave me equally true?
fabulas_ said:
sorry I had tapped on magisk hyde in the home and I thought it was that ... now I have activated it in the settings and redone the check and everything went ok ... I thank you immensely for helping me solve the problem.
so in the end I didn't have the damaged memory but a farmat data was enough ... as TWRP I can leave the one you gave me equally true?
Click to expand...
Click to collapse
Yes, you can keep the one I gave you. It has some updates that won't be merged until the next official version, so enjoy!
Captain_Throwback said:
Yes, you can keep the one I gave you. It has some updates that won't be merged until the next official version, so enjoy!
Click to expand...
Click to collapse
Ok perfect .. very kind. Thanks.
Before unlocking the bootloader and then doing the root I had a space problem as the internal memory is only 16gb ... now since the phone is still fine I wanted to find a solution.
And I saw that through the Link2SD app I can move some apps to the microsd (maybe the apps I use less), to do this I read that you have to make a partition in the microsd so that you can move the apps and that it is seen as "an extension of the internal memory" ... so I should connect the microsd to the pc to create the partition ... then there is another way which is to format the microsd as internal memory but this is not recommended ... while instead do as I wrote before a partition in the microsd and use it as an "extension of the internal memory" do you think it is a good solution to solve the app space problem? because I only have the apps in the internal memory ... the media are automatically saved on microsd ... so in theory by making a partition in the microsd the partition is an extension of the internal memory and the non-partitioned part should be used by the camera to save photos and videos .. do you think it's feasible?
One last thing as an app to remove the various system apps that I don't use like some Google apps, now that I have root I can do it ... which app do you recommend to do this?
fabulas_ said:
Ok perfect .. very kind. Thanks.
Before unlocking the bootloader and then doing the root I had a space problem as the internal memory is only 16gb ... now since the phone is still fine I wanted to find a solution.
And I saw that through the Link2SD app I can move some apps to the microsd (maybe the apps I use less), to do this I read that you have to make a partition in the microsd so that you can move the apps and that it is seen as "an extension of the internal memory" ... so I should connect the microsd to the pc to create the partition ... then there is another way which is to format the microsd as internal memory but this is not recommended ... while instead do as I wrote before a partition in the microsd and use it as an "extension of the internal memory" do you think it is a good solution to solve the app space problem? because I only have the apps in the internal memory ... the media are automatically saved on microsd ... so in theory by making a partition in the microsd the partition is an extension of the internal memory and the non-partitioned part should be used by the camera to save photos and videos .. do you think it's feasible?
One last thing as an app to remove the various system apps that I don't use like some Google apps, now that I have root I can do it ... which app do you recommend to do this?
Click to expand...
Click to collapse
Titanium Backup or Oandbackupx.
My phone keep restarting after install twrp.
@andmars
I saw your post in the LOS thread and I believe several people have reported that 3.5.0 is the last version that boots for you. I just reset the device tree back to that version to see whether it's something I did that broke it (although I'm not sure how that's possible). So the below link is a test version I just built that resets things back to that point. I saw only one flag that was changed, but it's not one that should be relevant to the device booting or not. But if this works, I'll have to re-evaluate. Please try it at your earliest convenience, and if you know anyone else with the same issue, please direct them here to test as well.
twrp-3.6.0_9-0_CPTB-20211226-01-hiae.img
drive.google.com
Captain_Throwback said:
@andmars
I saw your post in the LOS thread and I believe several people have reported that 3.5.0 is the last version that boots for you. I just reset the device tree back to that version to see whether it's something I did that broke it (although I'm not sure how that's possible). So the below link is a test version I just built that resets things back to that point. I saw only one flag that was changed, but it's not one that should be relevant to the device booting or not. But if this works, I'll have to re-evaluate. Please try it at your earliest convenience, and if you know anyone else with the same issue, please direct them here to test as well.
twrp-3.6.0_9-0_CPTB-20211226-01-hiae.img
drive.google.com
Click to expand...
Click to collapse
Ahoi Captain,
I tested you version of 3.6.0 and it didn't boot. I get the red warning text, then a few seconds of blank screen after which it boots into normal os.
Greets
A
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 ****
Read Only to Read Write for android (RO2RW) Update 03.01.2023 : Stable Beta v 3.7.2.1The first truly working script, original and unique in its logic for all devices with a SUPER partition
Universal auto RO2RW | EROFS-2-RW | F2FS-2-RW by LeeGarChat
{
"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"
}
Spoiler: Screenshots
Short description:
Converts EROFS, EXT4(RO), F2FS Super partition to RW
Description:
A simple utility to convert your Super partition to RW mode (Read/Write) As well as the expansion and distribution of free space for each section, depending on how much space is available in the original Super section.
You can flash both via:
1. TWRP: by using controls in the script: (Volume control (+) to switch, Volume control (-) to select) in this case, the new super RW is flashed directly.
2. Magisk module: in this case you will need to go to the terminal and enter RO2RW, and a new RW-super.img will be prepared in the internal memory, you can choose both image output for FASTBOOT and RECOVERY.
For these two modes, the creation of the original super as a backup is supported, the file will also be output to the internal memory as bak-super.img
Spoiler: FAQ
Do I need to format the data after installation?- No, it is not necessary in normal cases, this script does not affect encryption in the data section. But in some cases, it is necessary to do the date format, it is not yet clear how this is related, for example on Asus devices.
Why do I need this script, for what and why; why do I, need it?- When your system partitions have read-only mode (RO), then you cannot integrate modifications directly into the firmware, (such as Viper4Android) as well as manually edit/delete files from system partitions. This script converts it in the case of F2FS and EROFS to EXT4, or forcibly in the case of EXT4 enables the "Read/Write" (RW) mode, and also expands partitions as much as possible.
What are systems partitions?What are system partitions?
- These are the sections that are located in the main container "super" (the script is focused only on devices with super), it includes system, product, vendor, etc., when mounting the system, the structure looks like this:
System <--- In TWRP it is mounted as /system_root
, in the system itself it is mounted as
Code:
/ <--- The main mount point for system
├── /product <--- The main mount point for product
├── /vendor <--- The main mount point for vendor
|
├── /system <--- Here are the main system files
│ │
│ ├── /system/vendor <--- Additional mount point for vendor
│ │
│ ├── /system/product <--- Additional mount point for product
And by analogy with product and system, all other partitions, or other mount points. This can be viewed in the fstab file located in vendor/etc/
Some files cannot be edited at the root, or even if they can be edited without RW, those modifications won't stick, because these are temporary files responsible for the operation of the kernel and the entire linux system, in this case android. For example, proc, or sys, if you open a clean image, or mount a system image, you will see that these folders are empty, and files appear there only after the system is started.
Is ROOT required?- If you want to prepare a new super partition inside the system, then you need it, the firmware via TWRP does not need root.
How does the script work in Magisk?- You need to install the archive via Magisk manager as a module, the script will tell you if you need to restart the device. Next, you need to launch the terminal and give it root rights with the command "su", Then enter the command "RO2RW" and the script will run, it will prepare an image of RW-super.img according to your choice and optionally backup the original super bak-super.img, these files will be located in internal memory, after which you need to them to a PC if it is a fastboot image, or flash it via TWRP as super img if the images are for recovery.
What does S=40% SE=10% and so on mean?- This is the distribution of free space in the super between the partitions 'System=S' 'Product=P' 'System_ext=SE' 'Vendor=V' 'Other sections are there they are= OT'
- For example: The whole system occupies a conditional 4.7 GB. The super partition always has a fixed size in the memory block on the device, for example, take the example with PocoF3, it has 8.5GB there
Code:
Super size 8.5-GB
{1111111111,111111111111,111111111,11111,11111111,111111111111111,000000000000000}
System System_ext Product Odm Vendor Others if any Unused memory
2.2/2.2G 0.5/0.5G 0.8/0.8G 7/7M 1.2/1.2G 1/1GB 3.8~G
- As you can see, there is unused space for the second slot in the section (In 99.99% of cases it is not needed for users with root), and we can use this space for expansion of the partitions, and for system, 40% of this free space will be distributed. For system_ext 10%, for other partitions, if there are any, conditional 10% will be divided between all of them
RO2RW worked correctly, and the system started, but I can't delete or change files, what is the reason?- Perhaps you have some Magisk module installed that prevents you from doing this, for example OverlayFS.
Also, the reason may be that your device is of the MTK family, in some models there is a restriction at the kernel level for changing system partitions, and therefore mounting in RW, you will not even be able to reinstall magisk on such devices from the system
In this case, you open the way only to modding via TWRP
Also, you need to use the latest version of a normal file manager, these are the ones I recommend:
Solid Explorer File Manager
Solid Explorer File Manager - Apps on Google Play
Organize, protect and share your files in a dual pane layout.
play.google.com
Root Explorer
Root Explorer - Apps on Google Play
The ultimate file manager for rooted devices. The original and still the best.
play.google.com
MT manager
下载 | MT管理器
MT管理器官网
mt2.cn
RO2RW worked correctly, the system started, but in any section, for example vendor, there is little free space available, 2-10mb, can it be expanded somehow?In- That's how it will not be possible to expand a lot, this is due to the limitation of space in the super itself. System partitions occupy a certain amount of space in it, in response to "What does S=40% SE=10% and so on mean?" there is an example of how it works inside. So, perhaps your firmware weighs a lot, and there is simply not enough space in the super itself, you can fix it if you know what you are doing, you need to remove any garbage, applications from the system partitions.
"/" is system, including "/system/
"/vendor" is a vendor, including "/system/vendor", with the rest of the sections in the same way by analogy. Some partitions have a different mount point, this can be viewed in your fstab, it is located along the path /vendor/etc/*fstab*.
So, you first need to delete something from the system partitions, after which, according to the configuration in RO2RW (it is available in config.txt inside the archive, or in the first choice when installing where "max expansion"), distribute the size according to percentages or a fixed size, i.e. flash ro2rw again, or generate rw-super one more time.
Will RW disappear after the OTA software update?- Yes, in this case, after OTA, you need to boot into the system first, the process will take place, re-mark super for new data, after that you can make a new super through the system or through TWRP:
1. OTA installation
2. Reboot into the system
3. Preparing a new super, or rebooting in TWRP
4. Installing a new super via fastboot, or firmware the archive inside TWRP
How to flash a file via fastboot?- You need to move the finished file from the phone to the PC, throw RW-super.img into the folder with fastboot/adb, switch to fastboot mode on the phone, and enter the command in the console on the PC "fastboot flash super RW-super.img".
Read more about using fastboot in the branch of your device.
What are the differences between the first 4 options and the rest when first selected in the script?- The first four expand the sections based on the maximum size of the super, the rest expand on a fixed scale for each section, for example, it is more logical for OnePlus to choose one of the first 4, since there are a lot of sections, about 8, and it will be very large size to expand each by the same 200 MB.
I cannot delete or modify files from /system/app or from /product/app or from any other specific directory, but at the same time in this directory or I can create a file, and at the same time in the neighboring directory I can change files, the system is RW, how to fix it?- This happens due to the non-direct mounting of specific folders, it is called overlay filesystem, more about it here: https://wiki.archlinux.org/title/Overlay_filesystem
It specifically mounts any folder read-only. At the moment, you can delete or change or add to this directory only via TWRP, having previously flashed RO2RW by selecting the LiteRW option.
Or go to the terminal and write the commands:
Code:
su
magisk --path
The last command will show the path to the magisk directory, you will need to follow the path:
"The path that the magisk --path command displayed"/.magisk/mirror/
There will be partitions that Magisk mounts directly; by going to them, you will be able to change files without obstacles from OverlayFS.
I have a device with 32GB of memory, I do not know which option to choose so that the memory does not suffer?- The super section occupies a fixed size in the device's memory and has already been marked up by the manufacturer, i.e. even if the system takes up a conditional 2 GB, super still takes up all its conditional 6 GB in memory, I wrote above about how memory is distributed in super.
Why does the script at some point ask to delete some applications?- This means that the firmware weighs a lot, and after conversion to RW, it does not fit into super, my script suggests deleting some system applications, for example, in Chinese miui there are such stupid advertising things as TikTok, MiShop, etc. Applications are removed from temporary partitions that are being prepared for conversion to super, from the installed system you do not delete anything, well, if you only interrupt the process, after installing a new super, naturally the applications will disappear.
So why should I redistribute something, I didn't understand. I don't care how the system distributes its "empty space" there, they are still not used by me for files, because it's still a system partition. Just need RW super in the same form as it is. That's all. Is it possible somehow without distribution?- No, you can't, because it won't be original anyway, it won't affect user memory, it won't affect the OTA process if the firmware is pumping FullOTA, only the process of light (incremental) updates that weigh from 2mb to 800mb on average will be prohibited, and the process will not become faster. And if you don't care, then don't you care that there is free memory in the system partitions? in any case, you can fix it through the config as you need and give 1% for all partitions, or 10 or less MB for all partitions.
If all the tests turn out to be successful, I will start adding more features to the script, so I'm waiting for the tests, and also please fill out the Google form if RO2RW worked correctly or incorrectly, by doing this you help the development, as well as other people to understand how it works on their device and their ROM
Do not PM me about the script and help without permission, write to the support group
DOWNLOAD - SourceForge
TG Group
Telegram support chat for quick feedback
Donate only TG link https://t.me/mfpupdate/47
Credits:
- Thanks to the first link in a Google search for" e2fsck --help" link for clarification on disabling RO
- Many thanks to my own tests with the super section and the official Google utilits lpdump/lpmake/lpunpack as well as the --help menu for it
- Many thanks to the first Google search result for explaining tune2fs and resize2fs
- Thanks to the Magisk team for the BusyBox and bootctl binary
- Thanks to the kory-vadim with UKA for the make_ext4fs bibary, and thanks help menu make_ext4fs
- Thanks to SKKK for the erofs.unpack binary
- Thanks all test users
Please take the survey for more RO2RW statistics
Google Forms: Sign-in
Access Google Forms with a personal Google account or Google Workspace account (for business use).
docs.google.com
Also, the entire list from the survey will be available on this table
RO2RW Support list
Ответы на форму (1) Отметка времени,You Device name: Example "Poco F3",You Device Code: Example "Alioth",ROM: Example "ArrowOS Official 12.11.22",Was the installation successful?,Attach a log file. Located on the path /sdcard/NEO.LOGS/,A brief description of wishes or problems,Which version RO2R...
docs.google.com
Changelog:
Stable Beta 3.7.0.0:
[MAGISK][TWRP][ARM32/64][A8+]Universal Read Only to Read Write for android (RO2RW) | Auto converting SUPER "system partitions" to read/write mode
Read Only to Read Write for android (RO2RW) Update 03.01.2023 : Stable Beta v 3.7.2.1 The first truly working script, original and unique in its logic for all devices with a SUPER partition Universal auto RO2RW | EROFS-2-RW | F2FS-2-RW by...
forum.xda-developers.com
- Fixed non-removable logs. (To delete old logs from versions 3.6.2.1 and below, go to the /data/media/0/NEO.LOGS directory and you can delete them, or in TWRP and delete them
- Changed configuration logic for RW_SIZE and RW_SIZE_MOD parameters
- Changed the logical chain of appearance of SELECT MENU when there was a request for mount2ext4 or continue without mounting
- The logic has been completely redesigned, when in case of unsuccessful mounting, all partitions were not mounted, now everything will be mounted, except for unsuccessful ones during installation, only EXT4 is affected
- Completely redesigned config.txt, a simple one will open it and be surprised
- Now added support for forced start of the script (FOR TWRP), just configure the config as you need, in case of any failure, the script will fall into an error, do not be afraid
- Added a parameter to the config to disable timeout for the volume keys, so that the script does not fall into an error when you do not press the button for a long time
Stable Beta 3.6.2.0:
- Added avbctl for arm32, thanks for providing binaries: brigudav and Bodya-Kolibass
Stable Beta 3.6.1.1:
- Fixed work in arm32
- fixed chcon
Stable Betav3.6.0.0
- Add with only arm32 linker devices support (Support arm32)
Stable Betav3.5
- Added support for OTG and MicroSD
- Added LiteRW for Recovery mode. Some firmware is enough LiteRW
- Added manual configurator inside the script during execution in a running system through the terminal
- Added display of main paths to directories
- Fixed work for encrypted date if it is not available
- Fixed work "check RW and free size"
- Improved LiteRW code compared to LiteRW 3.0
Stable Beta 3.4.2
- Added the ability to check for RW partitions, and for free space in them. Access is available in TWRP and Terminal via termux
- Added the ability to delete pre-delete system applications
- There is an opportunity to choose "Forced deactivation of verivication and verity, or prepare patched vbmeta for manual firmware
- Fixed the work of ignoring the mounting of partitions for checking in the case of ext4
- Fixed code optimization in half of the code, cut the code thanks to universal functions
- Fixed a bunch of issues
- Fixed work install.sh in TWRP, after separating from update-binary
- Fixed work config.txt
- Fixed bash shell operation
- Fixed the calculation of free space in the super section
- Still need Samsung testers for F2FS
Beta 3.3
- Added e2fsck,tune2fs,resize2fs binaries from termux libraries
- Added the ability to ignore additional checks for ext4 systems, because of which images will not be mounted, because of which it is possible to bypass one of the errors in the previous version. But in this case DFE will not be installed
- Another fix for working with F2FS images
- Added an additional method for cases when you need to mount system images to migrate files to a new image, if direct mounting fails, an image dump will be created and it will already be mounted
- Fixed English language in the script
- Added "SKIP" option for DFE, if you don't know what it is, then press SKIP
- Moved to the bash shell, taken from the termux library, now the sh shell built into recovery / android will not be used.
- Executable script is now separated from update-binary
- Other minor fixes
- now u can use commands: RO2RW,ro2rw
Stable Beta 3.2
- Fixed work for F2FS systems, for Samsung. But you need to do additional manipulations for this, for example, to flash a custom kernel according to tests with a Samsung user comes out exactly like this.
- Fixed the problem of detecting an active slot
- The output of files has become with an informative file name like super.sparse.fastboot.active.slot._a.img
- Also, no patches are applied inside the active system, now you need to flash the same vbmeta through the rrecovery, or fastboot, it will also be output as patched and original in the case of a backup
Stable Beta 3.1.1
- Fix modified fstab for F2FS
Stable beta 3.1
- Add dfe (legacy mode) as an additional option
- Fix 55 error and need 9+gb free space for all devices
- Many text inscriptions for users have been corrected and new ones have been added so that users do not swear and understand what is happening
Beta 3.0.4:
- A lot of fixes when converting images
- Fixed a problem when dm-verity sometimes did not turn off
Beta 3.0.3:
- Fixed installation in Magisk
Beta 3.0.2:
- Small fixes
Beta 3.0.1:
- Slightly tweaked the calculator, some problems may have been fixed
Beta 3.0
- Maybe fixed the issue for some OnePlus devices
- Maybe fixed issue for new Samsung devices
Alexey NoOne in MFP, DFЕ, RO2RW, for Android 10+
t.me
- Added the ability to make a backup of the original super inside the custom recovery (TWRP,OFox)
- The methods for converting images from versions 2.8 and 2.9 are combined, and it seems to me that F2FS support has been added, in theory it should work, but testing is needed
Spoiler: Older
Beta 2.9
- The procedure for converting to EXT4.img has been redesigned, there is no longer a need to mount the file system, except in cases where you need to free memory (remove) any garbage from images
Beta 2.8
- Fixed counting and comparison of large numbers for some devices
ZeReF ft in MFP, DFЕ, RO2RW, for Android 10+
t.me
ZeReF ft in MFP, DFЕ, RO2RW, for Android 10+
look at the size how to fix it
t.me
ZeReF ft in MFP, DFЕ, RO2RW, for Android 10+
t.me
Alexey NoOne in MFP, DFЕ, RO2RW, for Android 10+
t.me
- Added check for free memory before creating RW-super.img. will loop until there is enough free space
- Added an inscription about updating the script for magisk, if there was an update, then you do not need to restart the system, otherwise it will be said that you need to restart the system
Alexey NoOne in MFP, DFЕ, RO2RW, for Android 10+
t.me
- Added the ability to backup the original super partition, both in row for recovery and sparse for fastboot
Alexey NoOne in MFP, DFЕ, RO2RW, for Android 10+
t.me
- Added extensive log file with output folder /storage/emulated/0/NEO.LOGS a.k.a /sdcard/NEO.LOGS
Alexey NoOne in MFP, DFЕ, RO2RW, for Android 10+
t.me
Beta 2.7
- Fixed a critical issue when the script was interrupted halfway through and was restarted, in which case data from system partitions could be deleted
- Fix metadata read, moved to android-tools binary from termux pkg
Toni Moon in MFP, DFЕ, RO2RW, for Android 10+
Screenshot (20 nov 2022 23:19:06)
t.me
- Fix install for magisk with hide magisk app
Toni Moon in MFP, DFЕ, RO2RW, for Android 10+
t.me
- Fix calculate size for fixed size like 200-250mb
Thequellu in MFP, DFЕ, RO2RW, for Android 10+
Not work 150,200,250 for me
t.me
- Fixed a bug of different binary files in ROM, moved to a single busybox
Beta 2.6
- Added mode for Magisk.
Spoiler: DEMO MAGISK
Your browser is not able to display this video.
- Fixed some bugs that I don't remember anymore
Beta2.5:
-Fix awk calculate for any device
Sergiocubano1 in MFP, DFЕ, RO2RW, for Android 10+
t.me
Sergiocubano1 in MFP, DFЕ, RO2RW, for Android 10+
t.me
-add config.txt and added option to expand partitions in % or size Mb
Alexey NoOne in MFP, DFЕ, RO2RW, for Android 10+
t.me
Beta2.4:
-Fix problem with a-only devices or like system partition name when not sustem_a/_b
Alexey NoOne in MFP, DFЕ, RO2RW, for Android 10+
Like this https://t.me/PocoF3DFE/65768 ?
t.me
Beta2.3:
-fix problem when "need -(minus)xxxx Mb free size"
Cookies in MFP, DFЕ, RO2RW, for Android 10+
Why me got -3835
t.me
Beta2.2:
-Fix problem when partition have name main or same name
Ngô Túc Thanh in MFP, DFЕ, RO2RW, for Android 10+
t.me
Ngô Túc Thanh in MFP, DFЕ, RO2RW, for Android 10+
t.me
Beta2.1:
- Fix this problem with RW for partition into TWRP ( works )
bad habbit in MFP, DFЕ, RO2RW, for Android 10+
t.me
- nject a crutch for large ROMs to fix the problem ( works with later miui cn on poco f3 )
Deleted Account in MFP, DFЕ, RO2RW, for Android 10+
t.me
- Maybe Fix for A-only devices with super partition ( need test )
Alexey NoOne in MFP, DFЕ, RO2RW, for Android 10+
t.me
- Inject binary for disable DM-verity
Beta2:
-first release for test
Changelog:
Beta 3.0
- Maybe fixed the issue for some OnePlus devices
- Maybe fixed issue for new Samsung devices
Alexey NoOne in MFP, DFЕ, RO2RW, for Android 10+
t.me
- Added the ability to make a backup of the original super inside the custom recovery (TWRP,OFox)
- The methods for converting images from versions 2.8 and 2.9 are combined, and it seems to me that F2FS support has been added, in theory it should work, but testing is needed
Changelog:
Beta 3.0.4:
- A lot of fixes when converting images
- Fixed a problem when dm-verity sometimes did not turn off
Beta 3.0.3:
- Fixed installation in Magisk
Beta 3.0.2:
- Small fixes
Beta 3.0.1:
- Slightly tweaked the calculator, some problems may have been fixed
Just flash the zip in recovery?
TheGhost1951 said:
Just flash the zip in recovery?
Click to expand...
Click to collapse
Good luck getting all the the instructions it is never just flash zip with this stuff and the telegram thread or whatever is probably the hardest telegram thread to figure out in all of telegram. I have over 200 telegram threads I watch normally you'll have pinned messages with download and another pinned message with instructions a to z laid. Not this guy you'll have to figure out the puzzle that is his way of doing things
Techguy777 said:
Good luck getting all the the instructions it is never just flash zip with this stuff and the telegram thread or whatever is probably the hardest telegram thread to figure out in all of telegram. I have over 200 telegram threads I watch normally you'll have pinned messages with download and another pinned message with instructions a to z laid. Not this guy you'll have to figure out the puzzle that is his way of doing things
Click to expand...
Click to collapse
That is one of the reasons I trust lebigmac script, he is through and instructions are clear!
TheGhost1951 said:
That is one of the reasons I trust lebigmac script, he is through and instructions are clear!
Click to expand...
Click to collapse
I have been into xda now for about 6 or 7 years. I was edger to learn and even built 3 custom roms back in android 9. Every year or 2 now google makes changes that are huge changes and I still find myself having to learn things like day 1 at times. The new EROFS kernels and roms is brand new I have no idea how they work. F2FS is samsung and thats one of the reasons I was interested because I have a tab s8 plus. The problem is for this to work it makes a copy of your super partition your system. I was trying to figure all of that out and they get pissed you dont understand all of it already. Well I tried flashing it on poco f3 because I thought I was on a RO rom because of EROFS and it failed and I had 13gb of img files in a couple of folders. It requires a lot of free space and if people have there phone filled up and start flashing it will fill it all the way up depending on how big your system is compared to storage. That should be mentioned its not.
Techguy777 said:
Good luck getting all the the instructions it is never just flash zip with this stuff and the telegram thread or whatever is probably the hardest telegram thread to figure out in all of telegram. I have over 200 telegram threads I watch normally you'll have pinned messages with download and another pinned message with instructions a to z laid. Not this guy you'll have to figure out the puzzle that is his way of doing things
Click to expand...
Click to collapse
TheGhost1951 said:
Just flash the zip in recovery?
Click to expand...
Click to collapse
Techguy777 said:
I have been into xda now for about 6 or 7 years. I was edger to learn and even built 3 custom roms back in android 9. Every year or 2 now google makes changes that are huge changes and I still find myself having to learn things like day 1 at times. The new EROFS kernels and roms is brand new I have no idea how they work. F2FS is samsung and thats one of the reasons I was interested because I have a tab s8 plus. The problem is for this to work it makes a copy of your super partition your system. I was trying to figure all of that out and they get pissed you dont understand all of it already. Well I tried flashing it on poco f3 because I thought I was on a RO rom because of EROFS and it failed and I had 13gb of img files in a couple of folders. It requires a lot of free space and if people have there phone filled up and start flashing it will fill it all the way up depending on how big your system is compared to storage. That should be mentioned its not.
Click to expand...
Click to collapse
I have added a FAQ, if there are any more questions, I will expand the FAQ
TheGhost1951 said:
That is one of the reasons I trust lebigmac script, he is through and instructions are clear!
Click to expand...
Click to collapse
My script also does RW-Super.img, if you use it from the system. In any case, I started to do the design, because I started to do work on another forum. Now it is similar to that on 4 pda
LeeGarChat said:
My script also does RW-Super.img, if you use it from the system. In any case, I started to do the design, because I started to do work on another forum. Now it is similar to that on 4 pda
Click to expand...
Click to collapse
Not very clear " if you use it from the system". I have no clue what you are saying here.
TheGhost1951 said:
Not very clear " if you use it from the system". I have no clue what you are saying here.
Click to expand...
Click to collapse
If you use a script from Termux or another terminal in the running system (that is, not via TWRP), after installing as a Magisk module. I'll fix it now, I'm bad at English
Working
izsdeaman said:
View attachment 5781557Working
Click to expand...
Click to collapse
Need "mount -o rw,remount /parts"
LeeGarChat said:
Need "mount -o rw,remount /parts"
Click to expand...
Click to collapse
your script works perfectly, partitions are both readable and writable, i flashed another system.img after running the script so it doesn't have rw yet.
Update to Stable beta 3.1
- Add dfe (legacy mode) as an additional option
- Fix 55 error and need 9+gb free space for all devices
- Many text inscriptions for users have been corrected and new ones have been added so that users do not swear and understand what is happening
Stable Beta 3.1.1
- Fix modified fstab for F2FS
I have used your Script with TWRP at Xiaomi Redmi Note 10 Pro (#sweet) and it works perfectly, partitions are both readable and writable.
Many thx
I used your script with TWRP as well on OnePlus Pro 9 in combination with lebigmac's script because his script doesn't make all folders / files in the main root storage R/W. Your script helped make it possible.
My main concern: In TWRP, if I try to place any file I backed up from the system to a folder / file that is usually R/O, I get Error:1 in twrp for a simple copy and paste job. Any reason for this? Sorry I am not an expert in android file systems.
immortalwon said:
I used your script with TWRP as well on OnePlus Pro 9 in combination with lebigmac's script because his script doesn't make all folders / files in the main root storage R/W. Your script helped make it possible.
My main concern: In TWRP, if I try to place any file I backed up from the system to a folder / file that is usually R/O, I get Error:1 in twrp for a simple copy and paste job. Any reason for this? Sorry I am not an expert in android file systems.
Click to expand...
Click to collapse
Need after mount partitions "mount -o rw,remount /system_root" for system. "mount -o rw,remount /vendor" for vendor and etc partitions.
Go to advance menu, mount. Mount all parts.
Go to advance menu. Terminal and write this commands