RO2RW Update Stable Betav3.6.0.0

Happy New Year!🎉🥳

Changelog:
- Add with only arm32 linker devices support (Support arm32):

If all the tests turn out to be successful, I will start adding more features to the noscript, 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 noscript and help without permission, write to the support group


Full changelog
Download SF
XDA link
4PDA link (Full instructions but in Russian)

Please take the survey for more RO2RW statistics
Google Forms link

Also, the entire list from the survey will be available on this table
Google Docs

Donation TG only
Donation from Russian people - PM

Update channel @mfpupdate
Support chat @PocoF3DFE

RO2RW Update Stable Betav3.7.0.0

Changelog:
- 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 noscript (FOR TWRP), just configure the config as you need, in case of any failure, the noscript 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 noscript does not fall into an error when you do not press the button for a long time

If all the tests turn out to be successful, I will start adding more features to the noscript, 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 noscript and help without permission, write to the support group


Full changelog
Download SF
XDA link
4PDA link (Full instructions but in Russian)

Please take the survey for more RO2RW statistics
Google Forms link

Also, the entire list from the survey will be available on this table
Google Docs

Donation TG only
Donation from Russian people - PM

Update channel @mfpupdate
Support chat @PocoF3DFE

Brief summary about LeBigMac and its noscript. To be honest, for a second I really thought that this developer had talent. She asked me in DM on XDA "How did you solve the problem with large ROMs". Well, I have nothing to hide, I am a developer with a completely open logical code, I answered that it was a crutch in the form of deleting some programs, at the user's choice. Then, after a couple of days in her SystemRW thread, I see that she is working on the AutoDebloat feature. Well, I think, did she really come up with something wonderful, some kind of algorithm for auto-detection of unnecessary programs? Now I looked at her release of the latest program, as a separate component, and was really disappointed. She did not come up with anything smarter than how to delete the PRE-registered list of programs to be deleted, WHICH must be filled in advance in the configuration file. I have been thinking about a custom file for a long time, and this will be implemented in a single large MFP-NEO project, in which there will be a software package combined into one single structure URI/RO2RW/DFE/DFE-NEO/Custom-Patches. I just really thought for a second that I could pay tribute to LeBigMac, but apparently not this time.

Briefly about the development process. We are writing and completely rewriting all functions to unify them, I also revised the approach to the noscript code, I make it more understandable and easy to read. All the developments that I find, as well as any solutions to certain problems, everyone can track in my telegram group in the blog topic. At the moment, due to my work, I can't devote much time to this hobby, so writing the noscript is a little bit stubborn.

Summary of DFE-NEO. I'm going to study the wonderful noscript Zackptg5 Universal DM-Verity, ForceEncrypt, Disk Quota Disabler, which I used before the implementation of my project, in some cases my noscript does not work properly on some, those problems that are in DFE-NEO have already been studied and understood because for which it does not work properly, but to implement a set of problems, some parts of the code need to be rewritten, and this is not subject to manual correction by the end user.

Summary of RO2RW: A set of new features will be implemented and existing issues will be fixed where possible, including no longer requiring a disabled selinux. Trial support for converting RW2RO EXT4-2-F2FS, F2FS-2-EXT4, EXT4-2-EROFS will be implemented, that is, conversion to different file systems.

URI summary : Support for installing different ROM versions will be implemented, additional support for reading installation files. "First install - then patch" mode - a function that first installs the ROM using the means that the developers put in the installation package, and only then everything else will be patched based on the already installed firmware, as well as support for factory fastboot ROM formats that manufacturers provide for Miflash, for example, and etc

it turned out to fully make RW for Samsung devices, I conduct tests in one person😏

I hope to have the strength to make a new version soon...😔

I want to test a new DFE method, but for this I need some person who is not afraid to lose data during tests. It's too late for me to make a backup to restore my data

https://news.1rj.ru/str/PocoF3DFE/74414/74441

Damn, you guys are getting annoying with the questions about MIUI 14, this question is fucking stupid, since there is an answer in the discussion thread on XDA in the FAQ section, this problem has been solved for a long time, even when nobody knew about it, and if you are too stupid to understand, just go fuck yourself!
🤦‍♂🤦‍♂🤦‍♂😡😡😡‼️‼️🤬🤬🤬🤬


Or ask this dumb question to lebigmac, this dumb question is worthy of such a developer, since she still doesn't know what's going on, don't know with her together
https://forum.xda-developers.com/t/noscript-ro2rw-pec2rw-erofs2rw-universal-partition-expander-and-converting-to-rw.4521131/

soon new dfe method:
- Not needed RW
- Not needed Magisk
- Not needed Reflash after flashing new recovery
- It is not necessary to have TWRP
- Only need reflash after flashing new ROM or Update ROM

Preparing for the new RO2RW and DFE, manual instructions, use a translator to translate the text
https://telegra.ph/Podgotovka-RO2RW-i-DFE-03-04

Only for ARM64 at the moment
Preliminary preparation for the new RO2RW, and the new DFE method! you can do it now, thus preparing your device for further automatic noscripts from me. This preparation will be needed if:
Your ROM is too big and won't fit in the super partition after converting to RW
You will want to use the new DFE method which will not need magisk and will also work on ROMs that have RO status
If you want to take part in tests and community development in this direction
If you want to read about what the noscript does and how to do it manually, you can go to this link
https://telegra.ph/Podgotovka-RO2RW-i-DFE-03-04

ZIP - https://news.1rj.ru/str/mfpupdate/130

Steps to work with this zip file via booted android:
1. Backup you data and internal storage, and transfer it on you PC or external storage
2. Flash .zip via magisk like module, waiting complite
3. Reboot device into recovery
4. if you have custom recovery (TWRP/OFOX) go to terminal and write command "format_data"
5. if you have stock recovery , reboot to recovery and do factory reset

Steps to work with this zip file via TWRP:
1. Backup you data and internal storage, and transfer it on you PC or external storage
2. Flash zip
3. reboot TWRP
4. Go to terminal and write command "format_data"

Release Announcement for dfe-neo 2.2.0 Beta

I am thrilled to present the latest version of dfe-neo, version 2.2.0 beta. In this release, significant improvements have been made compared to version 2.1.0, especially in the neo_inject image handler. Additionally, the fstab patching function has been reworked, now without any bugs.

Key Changes Compared to Version 1.5.x:

* NEO.config File Enhancements:
* New options added: remove_pin, wipe_data, where_to_inject, path_to_inject, magisk.
* Removed options such as hide_not_encrypted, fix_120hz_for_miui, safatynetfix due to the implementation of a new fstab injection method.

Revolutionary Injection Method:

* The new injection method completely eliminates dependency on magiskinit, making dfe-neo a fully standalone product.
* dfe-neo is now compatible with read-only systems, supports both A-only and AB devices, and seamlessly integrates with both KSU and MAGISK without requiring root access from either.

How the New Method Works:

1. The noscript locates the vendor partition and moves all files from /vendor/etc/init/hw/* to a new directory.
2. Modifying a Line in init.target.rc in initrd.img to Redirect the Path for the New fstab during Late Mount:.
3. Injects the modified fstab into the same new directory.
4. Writes this directory to super or the inactive vendor_boot or boot slot, depending on user choice.
5. Modifies fstab in vendor_boot and boot to indicate a new mount point during the fist_stage_mount stage, enabling the mounting of replaced files from the new partition into the original /vendor/etc/init/hw.

Installation and Update Instructions:

*First Installation (Device Encrypted):*

1. Enter TWRP.
2. Install DFE-NEO.ZIP.
3. Perform a data format (format data) with confirmation.
4. Reboot into the system.

*First Installation with New Firmware (Device Encrypted):*

1. Install the new firmware.
2. Reinstall TWRP.
3. Reboot into TWRP.
4. Flash DFE-NEO.
5. Perform a data format (format data) with confirmation.
6. Reboot into the system.

*Firmware Update (Device Already Decrypted):*

1. Install the new firmware.
2. Reinstall TWRP.
3. Reboot into TWRP.
4. Flash DFE-NEO.
5. Reboot into the system.

Please note that due to the new injection method, some features tied to magisk, such as hide_not_encrypted, are no longer available. Additionally, it is now necessary to reboot TWRP immediately after installing a new system image for AB devices.


Download Available on SourceForge: dfe-neo 2.2.0 Beta

Download Available on SourceForge: dfe-neo 2.2.1 Beta
Cleaned up the code.
Added language files. Available in 4 languages.

I’ll now think about how to implement support for external noscripts in order to return functionality to dfe-neo. there are difficulties in selinux, but I understood something, I will test it this weekend