RO2RW/DFE-NEO Update/News – Telegram
RO2RW/DFE-NEO Update/News
918 subscribers
35 photos
5 videos
20 files
67 links
Download Telegram
It seems I can implement dfe-neo updates after OTA. contact me those who have a ROM that is going to be updated via OTA with a small update, the so-called incremental ota which weighs no more than 1.5 GB, I usually don’t practice such updates in custom ROMs, so a stock is required and there is also root. don't PM me, contact me in the group @pocof3dfe via @LeeGarGold
1🔥1
🚀 New Release: DFE-NEO 2.4.6

📝Fixes:
- Fixed slot redirection and partition override functionality, no more TWRP issues regarding missing installed system.
- Fixed 'hide_not_encrypted' functionality.
- Improved overall functionality of additional noscripts dependent on Magisk/Kernelsu.
- Enhanced detection of installed DFE-NEO for more stability.
- Minor adjustments in NEO.config.

🗒️Additions:
- Added 'force_start' option.
- Added 'disable_verity_and_verification' option.

📥Download now from SourceForge: DFE-NEO 2.4.6

💸Support the developer with a donation in USD or RUB via Boosty: Donate

💸Support with a donation in EUR via Telegram: MFP Updates Channel

💲Additionally, you can support ongoing development and motivate faster releases of the new version RO2RW on Boosty: Support RO2RW Development

🔔 Reminder about DFE-NEOv2 Features:
- You can use DFE even without Magisk or Kernelsu. Basic DFE functionality will work.
- DFE-NEO can be installed immediately after flashing new firmware without the need to restart TWRP.
- After installing DFE-NEO right after flashing new firmware, you can install any other zip files.
- To stay unencrypted, you need to flash DFE-NEO every time after installing firmware or replacing vendor_boot, or in some cases, stock boot partitions.
- You don't need to format data when switching between firmwares.
- You can preserve data when switching between firmwares with the same structure but different vendors (e.g., AOSPA to Evolution, or Xiaomi.eu(A12) to StockMIUI(A14)), as long as the structure remains the same, including system programs and settings storage locations. However, this is not applicable when transitioning from MIUI to AOSP due to differing structures.
- After first use, you need to format the /data partition.
- When removing DFE-NEO, you need to format the /data partition.

#DFENEOv2 #dfe #dfeneo #Encrypted #Decrypted #dfe-neo #fix
🔥5🥰21👍1
RO2RW/DFE-NEO Update/News pinned «🚀 New Release: DFE-NEO 2.4.6 📝Fixes: - Fixed slot redirection and partition override functionality, no more TWRP issues regarding missing installed system. - Fixed 'hide_not_encrypted' functionality. - Improved overall functionality of additional noscripts…»
🚀 New Release: DFE NEO 2.4.7 - Disable Force Encryption - Native Early Override

📝 Fixes:
- Fixed boot search for first_stage_mount patching when recovery is present.
- Enhanced system for searching fstab and necessary *.rc files in /vendor/etc/init/hw for modification.
- Added 'custom_reset_prop' option in NEO.config:
- Note: This option will only work if Magisk/KernelSu is installed or if you have selinux=permissive.
- Custom props will be set at the stage where you specified.
- Example of usage:
- custom_reset_prop="--init my.prop=value my.prop2=value my.prop3=value --early-fs my.prop=value my.prop2=value my.prop3=value" and so on.
- Available stages: init: --init, --early-fs, --post-fs-data, --boot_completed.
- Otherwise, leave it blank.
- Added 'ro_hardware' option in NEO.config:
- Set up this option if you encounter error 36.1 fstab not found. This may occur if the ro.hardware variable differs between TWRP and the running system.
- You can check this in the TWRP terminal by entering the command getprop ro.hardware, and in the running system through any terminal. If the props differ, enter the value displayed in the running system.
- Otherwise, leave the value blank.

🗒️ Additions:
- GitHub repository available now: DFE NEO v2
- Discussion thread on 4PDA forum: 4PDA Discussion
- Join the Telegram discussion

📥 Download now:
2.4.7 from GitHub
Download from SourceForge

💸 Support:
Support the developer with a donation in USD or RUB via Boosty.
Support the developer with a donation in UER via Telegram.

🔔 Reminder about DFE NEO v2 Features:
- DFE can be used without Magisk or Kernelsu. Basic DFE functionality will work.
- DFE NEO can be installed immediately after flashing new firmware without restarting TWRP.
- You can install other zip files after installing DFE NEO right after flashing new firmware.
- To stay unencrypted, flash DFE NEO every time after installing firmware or replacing vendor_boot, or in some cases, stock boot partitions.
- No need to format data when switching between firmwares.
- Preserve data when switching between firmwares with the same structure but different vendors (e.g., AOSPA to Evolution, or Xiaomi.eu(A12) to StockMIUI(A14)), as long as the structure remains the same, including system programs and settings storage locations. However, this is not applicable when transitioning from MIUI to AOSP due to differing structures.
- After first use, format the /data partition.
- When removing DFE NEO, format the /data partition.

#DFENEOv2 #dfe #dfeneo #Encrypted #Decrypted #dfe_neo #fix
1👍1👎1🔥1
RO2RW/DFE-NEO Update/News pinned «🚀 New Release: DFE NEO 2.4.7 - Disable Force Encryption - Native Early Override 📝 Fixes: - Fixed boot search for first_stage_mount patching when recovery is present. - Enhanced system for searching fstab and necessary *.rc files in /vendor/etc/init/hw for…»
I'm excited to announce the latest update for the XDA discussion thread on DFE-NEO! Check it out
XDA Discussion Thread

For Russian-speaking users, don't forget to visit our thread on 4PDA:
4PDA Discussion Thread

Stay tuned for more updates and feel free to join the discussion!
👍5🥰1
Is it worth integrating additional patching methods into dfe neo v2, namely neo v1 (magisk init method) and legacy (direct modification of fstab)?
Anonymous Poll
9%
Add neo v1
20%
Add legacy
57%
Add neo v1 + legacy
28%
Not worth it
👍1
I just successfully ran DFE-NEO on my K20pro/mi9tpro with EvoX A14 and Derpfest A14 ROM. Which create a fake super in the system block. That’s not the point, the point is that the boundaries are expanding. Soon I will also integrate support for devices that do not have super, but have fisrt_stage_mount
🔥9🥰1
This week I will be working on a complete restructuring of the code so that there is no long piece of text in one file. I’ll scatter everything into small files and refer to them for specific tasks as functions. I will also restructure the error output and add a log file. I hope by the end of the week I will have released the first version 2.5.x
🔥6🥰1
DFE-NEO 2.5.0 status release
Beta-6 https://news.1rj.ru/str/PocoF3DFE/70373/87166

Super = A-only-Recovery : works
Super = A-only-KernelSu-App : works
Super = A-only-MagiskApp: works
Super = A-B-Recovery: works
Super = A-B-KernelSu-App : works
Super = A-B-MagiskApp : works
Super = A-B-KernelSu-App-after-OTA : works
Super = A-B-MagiskApp-after-OTA : works

Non-super = A-B-Recovery: in testing 🔄
Non-super = A-B-KernelSu-App : ineed testing ⁉️
Non-super = A-B-MagiskApp : need testing ⁉️
Non-super = A-B-KernelSu-App-after-OTA : need testing ⁉️
Non-super = A-B-MagiskApp-after-OTA : need testing ⁉️
DFE-NEO 2.5.0 status release
Beta-7
https://news.1rj.ru/str/PocoF3DFE/70373/87198

Super = A-only-Recovery : works
Super = A-only-KernelSu-App : works
Super = A-only-MagiskApp: works
Super = A-B-Recovery: works
Super = A-B-KernelSu-App : works
Super = A-B-MagiskApp : works
Super = A-B-KernelSu-App-after-OTA : works
Super = A-B-MagiskApp-after-OTA : works

Non-super = A-B-Recovery: works
Non-super = A-B-KernelSu-App : works
Non-super = A-B-MagiskApp : works
Non-super = A-B-KernelSu-App-after-OTA : not supported with auto
Non-super = A-B-MagiskApp-after-OTA : not supported with auto
👍4
🚀 New Release: DFE NEO 2.5.0 - Disable Force Encryption - Native Early Override

📝 Fixes:

- Rewritten code by 90%.
- Most of the binary files now do not depend on system ones, all thanks to built-in toybox and bosybox.
- Completely reworked all output UI text.
- Changed the order for where_to_inject=auto, the order is as follows -> super->vendor_boot->boot.

📝 New Features

- Added the ability to install DFE using the Magisk app and KernelSu app.
- Note: this is not a module! These applications are simply used as applications to install the archive. You need to open the application, go to the module menu, and press the install button, select DFE.zip.
- Added support for updating DFE through Magisk/KernelSu after installing OTA updates for the firmware. After the installation is complete, install DFE through the application.
- Added support for devices that use system and other partitions as a block under super. In other words, modernization of old devices for dynamic partitions. In them, super is defined by a non-standard path and is not called super partition at all.
- Added support for devices without a super partition, but the device must have A/B partitions.

📝Explanation

- Added support for installation from the system using Magisk or KernelSu.
- The first case: after installing an over-the-air update, there is no need to reboot the phone into TWRP, it is enough to flash the archive via Magisk/KernelSu and simply restart the device, the data will remain unencrypted and DFE will be preserved.
- The second case: when you decide to install DFE, but for some reason cannot install it through TWRP. The sequence for such cases in the installation is as follows:
1. Launch the Magisk/KernelSu application.
2. Install dfe.zip.
3. Restart the phone into stock recovery or TWRP or into fastboot mode.
4. Format the data. For fastboot, it is the command fastboot erase userdata.
5. Start the system.

🗒 Additions:
- GitHub repository available now: DFE NEO v2
- Discussion thread on 4PDA forum: 4PDA Discussion
- Join the Telegram discussion

📥 Download now:
2.5.0 from GitHub
Download from SourceForge

💸 Support:
Support the developer with a donation in USD or RUB via Boosty.
Support the developer with a donation in UER via Telegram.

Reminder about NEOv2 Method
- The NEOv2 method of patching fstab is based on the standard first_stage_mount
- These are the partitions where the mounting options specify first_stage_mount parameter in the fstab file located in the ramdisk of the boot partition.
- The V2 method involves creating an ext4 partition, which needs to be written somewhere, into super or into inactive partitions for A/B devices. Then you need to specify the new mount point in fstab, and we get the result that the new partition will be mounted before the system is initialized and before reading the init file from the system. Thus, the noscript copies all files from /vendor/etc/init/hw to the new partition, modifies these files as needed, and the system unsuspectingly executes our new commands during startup.
👍95🔥1🥰1
RO2RW/DFE-NEO Update/News pinned «🚀 New Release: DFE NEO 2.5.0 - Disable Force Encryption - Native Early Override 📝 Fixes: - Rewritten code by 90%. - Most of the binary files now do not depend on system ones, all thanks to built-in toybox and bosybox. - Completely reworked all output UI…»
🚀 New Release: DFE NEO 2.5.1 - Disable Force Encryption - Native Early Override

📝 Fixes:
- Improved patching of .rc files when fstab is defined in different .rc files and the system has more than one fstab in the system
- Changed fstab search function for vendor and ramdisk boot image
- Fixed bug of reading NEO.config when it was crookedly edited
- Added fresh versions of magisk Magisk-kitsune-v27-R65C33E4F, Magisk-Delta-v27.0

*** The only difference between the regular version and the Lite version is that the Lite version lacks Magisk installation zip files

🗒 Additions:
- GitHub repository available now: DFE NEO v2
- Discussion thread on 4PDA forum
- Discussion thread on XDA forum
- Join the Telegram discussion

📥 Download now:
2.5.1 from GitHub
Download from SourceForge

💸 Support:
Support the developer with a donation in USD or RUB via Boosty.
Support the developer with a donation in UER via Telegram.

Reminder about NEOv2 Method
- The NEOv2 method of patching fstab is based on the standard first_stage_mount
- These are the partitions where the mounting options specify first_stage_mount parameter in the fstab file located in the ramdisk of the boot partition.
- The V2 method involves creating an ext4 partition, which needs to be written somewhere, into super or into inactive partitions for A/B devices. Then you need to specify the new mount point in fstab, and we get the result that the new partition will be mounted before the system is initialized and before reading the init file from the system. Thus, the noscript copies all files from /vendor/etc/init/hw to the new partition, modifies these files as needed, and the system unsuspectingly executes our new commands during startup.
👍82🔥2🥰1
Fuck you. To get shit done and integrate a goddamn competent legacy mod, I gotta juggle a fuckin' thousand variables. And don't get me started on that converter bullshit to RW format, gotta deal with the vendor section crap too. But you know what? While I'm at it, I'm brewing up some wicked ideas for ro2rw version 4. Like, seriously, some mind-blowing shit. HMHMHMHMHMH. Once I wrap up version 2.6, I'm diving headfirst into ro2rw. And let me tell you, the real game-changer here is my revamped lptools_new utility. With that bad boy, I can twist and turn the super partition like nobody's business. Fuck, it's gonna be epic.

So, here's the deal. I need some cash to keep my motivation levels up. Hit me up with some dough, whether it's in USD or RUB via Boosty (https://boosty.to/leegar/donate). Or if you're feeling fancy, you can slide some EUR my way via Telegram (https://news.1rj.ru/str/mfpupdate/172). Let's make shit happen, folks. 💰
👍6🥰4😁21
3👍1
Please open Telegram to view this post
VIEW IN TELEGRAM
Please open Telegram to view this post
VIEW IN TELEGRAM