yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] DocMAX:
I have massive problems with WIFI and Cellular Nework. Any clues?
[Android Software/Hacking General [Developers Only]] Hellera:
Hello friends, this DFE-NEO is a realy good work but it doesn't work on my Oneplus 6T A/B device. I tried with many custom ROMs (Android 12 or even 13)... everytime I have error 255 at the begining of flashing it. Doesn't matter... with formating data or without... the same error 255... On my other phone, Redmi Note 10 Pro works fine (dynamic partition). I'll be happy with any advice, thank you.
[Android Software/Hacking General [Developers Only]] Abel10:
Hey! May I ask what does error code: 127 mean? @LeeGarChat
[Android Software/Hacking General [Developers Only]] Android developer2:
I ran it on Samsung Galaxy A13 SM-A135F

To change the file system to read write

When I activated through TWRP the system did not boot at all

And when I activated through magisk, the device remained in bootloop

Apart from your script, there is no other way to change the device, not even by editing the img because it is an F2FS file system

I would appreciate your assistance

Thank you
[Android Software/Hacking General [Developers Only]] LeeGarChat:
Both error code not mine, need read recovery log. If u send me it, I help you

This this script not for Make RW, this is DFE, it's different think

U can Yousef translate, just translate all line in english.sh into .zip file, rename it on CN.sh and u get different languages

Yes. Why not?
[Android Software/Hacking General [Developers Only]] Camis:
Redmi Note 8T - I got error 255.
[Android Software/Hacking General [Developers Only]] American_Jesus:
What recovery are you using?

Try it with latest official TWRP, older recoveries won't probably work.
[Android Software/Hacking General [Developers Only]] Camis:
OrangeFox Recovery.
[Android Software/Hacking General [Developers Only]] American_Jesus:
I had the same error with OrangeFox, use the latest official TWRP instead
[Android Software/Hacking General [Developers Only]] bozinsky73:
Hi, is there a way to revert to encrypted system after DfE has been flashed (I mean another zip file to flash, not a fastboot restore ..)

Thanks
[Android Software/Hacking General [Developers Only]] LeeGarChat:
If u use neo method, then just flash original boot.img. after this u need do format data (factory reset)
[Android Software/Hacking General [Developers Only]] Abel10:
Sorry for my late answer! I flashed it with a different recovery (also ROM installation), and there wasn't any error code anymore. Thank you for your answer!
[Android Software/Hacking General [Developers Only]] lPolarisl:
What are the steps to make this work exactly ?
[Android Software/Hacking General [Developers Only]] Chumbimba:
Hiiii im using it, but now dfe dont let me put a password and its a new problem, bc i always used dfe and not have that problem, i need dfe bc it let me use sd as internal correctly, the roms of my phone have that problem and dfe solve it, but now if i use dfe cant set a pasword and the phone always stays unlock, do exists a way that can i only patch fstab.qcom? without losing the passwords? (android 11, redmi 7a)
[Android Software/Hacking General [Developers Only]] LeeGarChat:
I don’t quite understand you, can’t you set a lockscreen password through the settings?

flash and use the arguments from the file. otherwise, if you don't need something that is included in arguments.txt, then edit it, or adjust the arguments during installation, there is such a possibility. you can also use this for magisk as well

Sorry for the long replies, I don't get notifications about someone posting here
[Android Software/Hacking General [Developers Only]] clewis.it:
Hello. I have a recently updated mediatek device with Android 11. Decryption on TWRP is broken for this device, so I have tried to disable forced encryption with this zip. Works well, except that the fingerprint sensor and WiFi doesn't work when encryption is disabled. Any ideas on why this happens?
[Android Software/Hacking General [Developers Only]] LeeGarChat:
I do not know how to fix it, since this user did not share the instructions
[Android Software/Hacking General [Developers Only]] lopestom:
Simple. We only enable Developer settings

and we saw the option that makes WiFi switch MAC addresses automatically. This is programmed by the company for the device.

I won't write too much about how I get the decryptable part working as I don't want to get in the way of your development. I'm sure the intentions are the best. :cowboy:

But the mentioned user says that:

He not wrote How zip file is installed: TWRP or Magisk module?!? He not wrote what device - Soc have?!

About fingerprint issue so very companies place additional locks. Perhaps this has to do with dm-verity protection?

Also, many users are using the original vbmeta.img file (which has protections enabled) and this can happen since many devices have TWRP without modifying the vbmeta.img file. Therefore, I can only assume that it is necessary to delve into the firmware files for any and all fingerprint related searches and perhaps WiFi as well.
[Android Software/Hacking General [Developers Only]] clewis.it:
Yep, you're right, I didn't give any of that information. I'm using the "Non-EU" version of the Unihertz Atom XL. This uses TEE keys, whatever that means. Bootloader is unlocked, TWRP based on the android 10 kernel release is installed. Vbmeta was flashed with --disable-verification and --disable-verity. The same vbmeta file was flashed for vbmeta, vbmeta-system, and vbmeta-vendor. It was the one that the AtomXL Dev supplied, so I don't know if it was modified or not. I will find out.

Edit: per the dev, it's the result of the LOS build process. Currently it's only used as a dummy to deactivate AVB.

I installed DFE NEO using TWRP. I used the defaults at first, then tried adjusting the options. Since vendor is read only, I had to install magisk. I tried with both the built-in magisk, and with the latest magisk apk. Same issue occurs.

Let me know if you have any other questions or advice for me.
[Android Software/Hacking General [Developers Only]] katanasamana:
Good bro
[Android Software/Hacking General [Developers Only]] Paresh Kalinani:
When using DFE-NEO with Hide Encryption, how do I verify if it worked on my device?

Should I check the build.prop for ro.dfe.neo.state or something else?
[Android Software/Hacking General [Developers Only]] LeeGarChat:
Go to terminal

getprop ro.dfe.neo.state
[Android Software/Hacking General [Developers Only]] Paresh Kalinani:
I first tried with hiding encryption on OnePlus 6T running Android 13 but then after setting a lock, I booted to TWRP where it needed my PIN to decrypt the storage, else it was all encrypted.

So I flashed DFE again as follows:

- Flashed my ROM to both slots (A/B)

- Normal "wipe" in TWRP

- Reboot TWRP

- Flash DFE with arguments as follows

- Tried to format data (read below)

- Reboot to System

Agruments:

- DFE-NEO

- DEFAULT DFE QUOTA AVC

- reinstall current recovery? YES

- install build-in DFE-NEO Magisk v25.2? YES

- Hide encryption? NOT HIDDEN

- additional features? NO

When I go to format data, it said

Formatting Data using mke2fs...

mke2fs -t ext4 -b 4096 /dev/block/sda17 60076219

process ended with ERROR: 1

Unable to wipe data.

Unable to format to remove encryption.

Updating partition details...

...done

Not left with another choice, I went ahead and changed the TWRP setting to just do "rm -rf" without actually formatting.

Went to format data again and it just did rm -rf in the background, quickly successful.

Booted to the ROM and voila! Instead of saying "unencrypted" in settings, it said Encrypted.

However, this says decrypted :

OnePlus6T:/ # getprop ro.dfe.neo.state

decrypted

Booted to TWRP again and it still needs the PIN or else it doesn't let me see my files. As per my understanding, shouldn't I be able to see my internal storage in TWRP without providing any decrypting PIN to it?
[Android Software/Hacking General [Developers Only]] LeeGarChat:
Yes, you clearly have something wrong. I think I know what the problem is. And in principle, I knew for a long time, maybe two months ago. This month, towards the end, I think I will release a new version that will be part of one big project. I went to it for a very long time, and all enthusiasts will be able to use a convenient tool for their experiments. At the moment, the development of dfe-neo as a separate project is suspended
[Android Software/Hacking General [Developers Only]] Paresh Kalinani:
Thank you, that gives hopes. Happy to hear that!

By the way, I also tried the legacy mode and something surprised me.

What I did:

When DFE-NEO couldn't work,

1. Booted to TWRP

2. Decrypted using my pattern lock

3. Flashed DFE-NEO ZIP

4. Selected DFE legacy mode

5. Wiped data and dalvik

6. Format Data - typed 'yes' ( it again resulted in :

Formatting Data using mke2fs...

mke2fs -t ext4 -b 4096 /dev/block/sda17 60076219

process ended with ERROR: 1

Unable to wipe data.

Unable to format to remove encryption.

Updating partition details...

...done

FYI - I have seen the above error in some youtube videos where they show how to flash a ROM to OnePlus 6T and the error is never spoken about, just skipped.

7. Set "rm -rf instead of formatting" in TWRP settings

8. Format Data - typed 'yes'

9. Rebooted to system

It asked me for a screen-lock! The older one, that I had set just before performing the above steps.

It was weird for me to boot into a ROM after a whole wipe and the ROM showing me lock-screen in the beginning.

So I entered the pattern, it unlocked, skipped the LineageOS setup and the settings said "Encrypted"

I booted to TWRP and as expected, it asked me for a pattern as well, for decrypting the storage. :(

And then, as I finally had nothing on my phone yet, I thought I'd try the ZIP from the DFE deprecated thread.

Apparently it worked in decrypting the internal storage... or just making it unusable to the system? You can read what happened, here : https://xdaforums.com/t/deprecated-...uota-disabler-11-2-2020.3817389/post-87953277

Edit: "The Unable to format to remove encryption" got resolved if I didn't immediately format data but rebooted again to TWRP and then formatted data. However, that still took me nowhere. The system still said "Encrypted" and TWRP on next boot asked for the pattern lock to decrypt data.
[Android Software/Hacking General [Developers Only]] ashish1989:
The dfe neo doesn't work with my device Oneplus 6 whereas the old and deprecated one worked fine. I am talking about this

https://xdaforums.com/t/deprecated-...ncrypt-disk-quota-disabler-11-2-2020.3817389/
[Android Software/Hacking General [Developers Only]] magnumoZeus:
that's exactly also happening with me, he is not the only one,

device: RMX2151 realme 7 (rm6785)

fresh rom installed with dfe neo file, the encryption is removed though.

btw great work, keep it up

why dont you turn on email notifications from user profile settings, itll notify you for every mention
[Android Software/Hacking General [Developers Only]] KProject:
Thanks!

Your save my life from A13 encryption 👍
[Android Software/Hacking General [Developers Only]] LeeGarChat:
Summary of DFE-NEO. I'm going to study the wonderful script Zackptg5 Universal DM-Verity, ForceEncrypt, Disk Quota Disabler, which I used before the implementation of my project, in some cases my script 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.

My Telegram support group and link to full message blog
[Android Software/Hacking General [Developers Only]] magnumoZeus:
Device : RMX2151 aka REALME 7

chip set: mtk6785

ROM: crdroid v9.0 a13(also tried other Roms)

Problem:

Can't set screen lock after flashing dfe neo zip

Crash URL: https://paste.crdroid.net/amfT5a

Matlog:

time: 1673639014850

msg: java.lang.IllegalStateException: Remote stack trace:

at com.android.server.locksettings.SyntheticPasswordManager.createPasswordBasedSyntheticPassword(SyntheticPasswordManager.java:834)

at com.android.server.locksettings.LockSettingsService.initializeSyntheticPasswordLocked(LockSettingsService.java:2836)

at com.android.server.locksettings.LockSettingsService.setLockCredentialInternal(LockSettingsService.java:1798)

at com.android.server.locksettings.LockSettingsService.setLockCredential(LockSettingsService.java:1716)

at com.android.internal.widget.ILockSettings$Stub.onTransact(ILockSettings.java:571)

stacktrace: java.lang.RuntimeException: An error occurred while executing doInBackground()

at android.os.AsyncTask$4.done(AsyncTask.java:415)

at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:381)

at java.util.concurrent.FutureTask.setException(FutureTask.java:250)

at java.util.concurrent.FutureTask.run(FutureTask.java:269)

at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:305)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1137)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:637)

at java.lang.Thread.run(Thread.java:1012)

Caused by: java.lang.IllegalStateException: Fail to enroll user password when creating SP for user 0

at android.os.Parcel.createExceptionOrNull(Parcel.java:3036)

at android.os.Parcel.createException(Parcel.java:3012)

at android.os.Parcel.readException(Parcel.java:2995)

at android.os.Parcel.readException(Parcel.java:2937)

at com.android.internal.widget.ILockSettings$Stub$Proxy.setLockCredential(ILockSettings.java:1213)

at com.android.internal.widget.LockPatternUtils.setLockCredential(LockPatternUtils.java:706)

at com.android.settings.password.ChooseLockPassword$SaveAndFinishWorker.saveAndVerifyInBackground(ChooseLockPassword.java:1052)

at com.android.settings.password.SaveChosenLockWorkerBase$Task.doInBackground(SaveChosenLockWorkerBase.java:137)

at com.android.settings.password.SaveChosenLockWorkerBase$Task.doInBackground(SaveChosenLockWorkerBase.java:133)

at android.os.AsyncTask$3.call(AsyncTask.java:394)

at java.util.concurrent.FutureTask.run(FutureTask.java:264)

... 4 more

Caused by: android.os.RemoteException: Remote stack trace:

at com.android.server.locksettings.SyntheticPasswordManager.createPasswordBasedSyntheticPassword(SyntheticPasswordManager.java:834)

at com.android.server.locksettings.LockSettingsService.initializeSyntheticPasswordLocked(LockSettingsService.java:2836)

at com.android.server.locksettings.LockSettingsService.setLockCredentialInternal(LockSettingsService.java:1798)

at com.android.server.locksettings.LockSettingsService.setLockCredential(LockSettingsService.java:1716)

at com.android.internal.widget.ILockSettings$Stub.onTransact(ILockSettings.java:571)
[Android Software/Hacking General [Developers Only]] KProject:
In setup wizard?

Before set up password when warning screen "apply password on boot blablabla" choose no.
[Android Software/Hacking General [Developers Only]] Hellera:
Hello friends, I have a problem with DFE on my OnePlus 6T.... I cannot flash it in twrp, every time it shows me 255 error. I tried to flash it in magisk like a module, it works but after formating (with yes) everything is gone... On my other phone with dinamyc partition works fine, without problems... So, any ideeas to solve this? Any help is welcome... Thank you
[Android Software/Hacking General [Developers Only]] KProject:
Maybe you need to hide not encrypted status?

Or try using OLD DFE Method?
[Android Software/Hacking General [Developers Only]] Paresh Kalinani:
Solved this using the latest unofficial TWRP. Which TWRP do you use?
[Android Software/Hacking General [Developers Only]] Hellera:
Thanks for the reply, but which is the OLD DFE Method?

If is about this, I tried without succes, no effect...

[Deprecated] Universal DM-Verity, ForceEncrypt, Disk Quota Disabler [11/2/2020]

Hi all! For the past couple of months, I've been looking into making a more universal solution to disable dm-verity and forceencrypt. Needing to take different zips, modify them for different devices, and then cross your fingers when you switch...

xdaforums.com
[Android Software/Hacking General [Developers Only]] Hellera:
I'm using the latest official TWRP, 3.7.0_9.0

Wich TWRP do you suggest?
[Android Software/Hacking General [Developers Only]] Paresh Kalinani:
9.0? Are you on OOS 9?

I used the one called TWRP-3.6.0_11-2-OP6xT.zip for Android 11.

By the way, did DFE work on 6T with dynamic partitions?
[Android Software/Hacking General [Developers Only]] Hellera:
No, I'm usinng ricedroid A13... that's my problem... dfe doesn't work on 6t... btw, 6t is an a/b partition device
[Android Software/Hacking General [Developers Only]] littlecrap:
Flashed DfE and it's a success, encryption status no but I can't access the SD card in mix explorer also in files app I can't copy or move them.

Any solutions?
[Android Software/Hacking General [Developers Only]] amdev0101:
Any luck on 6t with dynamic partitions? Im testing nethunter on unofficial paranoid android and need to be decrypted
[Android Software/Hacking General [Developers Only]] not_the_droid_ur_lookin4:
Tried this 10 times already, so just before I go completely loopy... could anyone please share if this is supposed to work on a Samsung S10 running A13 (custom/crDroid)? I think the S10 doesn't use A/B. Am I trying to do something that's simply not possible? Or should I keep trying? Thanks.

Also... decompressed the zip file but there is no arguments.txt file so I made one, copied in the code shown in the op, changed to legacy etc, saved it, and then re-zipped the archive only to be told that it's an invalid zip file.

Has anyone else had this problem? Isn't there supposed to already be an arguments.txt file in the zip? Any idea what to do in order to flash the zip with the arguments.txt file? Thanks.
[Android Software/Hacking General [Developers Only]] solar666:
Cannot comment on the first part related to S10.

But for sure looking to the zip I can say that there is a arguments.txt file present inside. Look at the screenshot.

What I see as well is that the latest version is giving the same "invalid zip" message when I want to change something inside zip and I just used the version before "DFE-NEO-1.5.3.014-BETA.zip" as this was not having such issues. The change between are just two added new languages as far as I understood.
[Android Software/Hacking General [Developers Only]] picchishaitan:
I tried for 2 days to get past Error 255 but failed.

I'm on Redmi Note 6 Pro installing ArrowOS (A13) with latest TWRP.

Anyone have any solutions?
[Android Software/Hacking General [Developers Only]] KindaFlax:
I seem to be in over my head. This was linked as a method of decryption in a more basic article I was following. After running it, I seem to have a non-functional super partition. That, along with the fact I can't access storage from my pc (picture) and I can't install the stock ROM through fastboot, means my phone is soft bricked.

Is this something that makes any sense to someone here that knows what they're doing? If so, I would tremendously appreciate your help.

Interestingly, if I flash an "empty" super.img file from the bootloader of another ROM it goes through.

After some more fiddling (erasing, flashing empty, re-extracting some files) the issue seems solved so I can't concretely say this caused it in any way
[Android Software/Hacking General [Developers Only]] cr4sh-lab:
Nice
[Android Software/Hacking General [Developers Only]] Huexxx:
Very good work!

BTW: Applied over Xiaomi Sweet - EvoX
[Android Software/Hacking General [Developers Only]] Huexxx:
Hi @LeeGarChat , it seems to fail to work over a new device.

Let me explain the situation:

- Device is Xiaomi Chiron.

- A-only, non dynamic partitions.

- Original cust partition is used as vendor.

- EROFS is ported on kernel.

- System and Vendor partitions are not mounted by kernel, they are mounted on for first stage init, so fstab is on /vendor (/dev/block/by-name/cust) and ramdisk.

- After patching the rom with DFE-NEW, with the same config that works fine on Sweet, I get a bootloop.

- Encryption is only set on ext4 data partition (f2fs without encryption is also especified).

Any ideas to make it work?

Thanks in advance.

include $(CLEAR_VARS)
LOCAL_MODULE := fstab.qcom
LOCAL_MODULE_TAGS := optional
LOCAL_MODULE_CLASS := ETC
LOCAL_SRC_FILES := etc/fstab.qcom
LOCAL_REQUIRED_MODULES := fstab.qcom_ramdisk
LOCAL_MODULE_PATH := $(TARGET_OUT_VENDOR_ETC)
include $(BUILD_PREBUILT)

include $(CLEAR_VARS)
LOCAL_MODULE := fstab.qcom_ramdisk
LOCAL_MODULE_STEM := fstab.qcom
LOCAL_MODULE_TAGS := optional
LOCAL_MODULE_CLASS := ETC
LOCAL_SRC_FILES := etc/fstab.qcom
LOCAL_MODULE_PATH := $(TARGET_RAMDISK_OUT)
include $(BUILD_PREBUILT)

/dev/block/bootdevice/by-name/boot /boot emmc defaults recoveryonly
/dev/block/bootdevice/by-name/recovery /recovery emmc defaults recoveryonly

/dev/block/by-name/system /system erofs ro wait,first_stage_mount
/dev/block/by-name/cust /vendor erofs ro wait,first_stage_mount

/dev/block/bootdevice/by-name/cache /cache ext4 nosuid,nodev,noatime,discard,nobarrier wait,check,formattable
/dev/block/bootdevice/by-name/cache /cache f2fs nosuid,nodev,noatime,discard,fsync_mode=nobarrier,background_gc=off wait,check,formattable
/dev/block/bootdevice/by-name/userdata /data ext4 nosuid,nodev,noatime,discard,nobarrier,noauto_da_alloc,errors=panic wait,check,latemount,fileencryption=ice,quota,reservedsize=128M
/dev/block/bootdevice/by-name/userdata /data f2fs nosuid,nodev,noatime,discard,fsync_mode=nobarrier,background_gc=off wait,check,latemount,formattable,quota,reservedsize=128M
/dev/block/bootdevice/by-name/persist /mnt/vendor/persist ext4 nosuid,nodev,noatime,barrier=1 wait
/dev/block/bootdevice/by-name/dsp /vendor/dsp ext4 ro,nosuid,nodev,barrier=1 wait
/dev/block/bootdevice/by-name/modem /vendor/firmware_mnt vfat ro,shortname=lower,uid=1000,gid=1000,dmask=227,fmask=337,context=u:object_r:firmware_file:s0 wait
/dev/block/bootdevice/by-name/bluetooth /vendor/bt_firmware vfat ro,shortname=lower,uid=1002,gid=3002,dmask=227,fmask=337,context=u:object_r:bt_firmware_file:s0 wait
/dev/block/bootdevice/by-name/misc /misc emmc defaults defaults
/devices/soc/a800000.ssusb/a800000.dwc3/xhci-hcd.0.auto/usb* auto auto defaults voldmanaged=usb:auto
[Android Software/Hacking General [Developers Only]] naagiovanna:
hi, can you give me the order to install it, like do i have to install this zip first then magisk and custom or? btw sorry bad English im using google translate
[Android Software/Hacking General [Developers Only]] duke_mac_l:
No need to flash magisk. There is a option to do this during the installation of the zip.
[Android Software/Hacking General [Developers Only]] American_Jesus:
Always last, it in first post.

1. ROM

2. Any other zip

3. Magisk (optional)

4./LAST NEO-DFE
[Android Software/Hacking General [Developers Only]] Reddycak:
Android writes that my storage is decrypted but twrp cant see any folders and files in internal storage and from pc I cant access too. Phone: Redmi 9 lancelot with newest lineageos 20
[Android Software/Hacking General [Developers Only]] mir2480:
Hello, could someone explain to me how I can make this method work for motorola android 12? I have twrp, but I can't get it to work because of "data"
[Android Software/Hacking General [Developers Only]] joydeb.taldi:
Is it possible to flash DFE-NEO without pressing the volume buttons? Because the volume buttons on my device are broken. Please help.
[Android Software/Hacking General [Developers Only]] solar666:
You can use the arguments.txt file inside the zip according to your needs. Just extract it modify it and put your arguments.txt back into the zip.

There is one switch "force reading arguments" which you need to set to yes if you don't want to use the volume keys. But be sure to adjust the other switches as well to your needs.
[Android Software/Hacking General [Developers Only]] joydeb.taldi:
Thanks mate for helping.