yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] andy.marsh:
I'm on Pixel OS android 13. Before decrypting my device all of my banking apps were working now after wiping storage, reinstalling rom and decrypting data 2 of my banking app either show root detected or tamper detected. My safety net is passed and my device is not rooted.
[Android Software/Hacking General [Developers Only]] strannij:
Thank you so much, what a great job you've done!

Works perfectly on my OnePlus Nord 200 5g!

With hide de encryption mode and auto add apps to magisk deny list all my banking apps and even Google wallet/nfc pay is working! The only tiny issue is when I deselect YouTube/music from magisk deny list it gets added again after reboot. But it's not a big issue. Thank you again, you rock!
[Android Software/Hacking General [Developers Only]] weskerty:
Thanks 👉👈
[Android Software/Hacking General [Developers Only]] onolox:
Let me see if I understood, I have an miui 13 android 12 with magisk and twrp .81.

1) DISABLE DINAMIC REFRESHRATE, I'm on miui 13, what is exactly this option? I need to use it?

2) "Reflash current Recovery for Recovery", I need to set this option to true to have twrp working after installation of dfe neo?

3) There's a bug for me, when I start the script it shows various languages with instructions about volume buttons, and ended in an unknow language for me. I'm using de default zip, no modifications. To be able to use it I deleted all languages except english.

I used it and worked fine!

@LeeGarChat thanks for your contributions!
[Android Software/Hacking General [Developers Only]] GauriSpears:
It's a great script but I prefer KernelSU to Magisk. Any ideas how to make it work with KernelSU (it's compatible with magisk modules but loads them in a different place)?
[Android Software/Hacking General [Developers Only]] Hauk92:
Hello, first of all nice work @LeeGarChat !

However it doesn't work on my Poco X5 5g with lineageos 21. There are some differences in the vendor partition. No clue if it is a problem of the specific lineage version for the device or if it's a problem with Android 14 LindeageOS.

Differences/problems I spotted:

Grepping the fstab name fails due to no path in mount_all --late (for $path_original_fstab):

[...]

/tmp/neov2/neo_inject_a/init.target.rc-on late-fs

/tmp/neov2/neo_inject_a/init.target.rc- wait_for_prop hwservicemanager.ready true

/tmp/neov2/neo_inject_a/init.target.rc: #exec_start wait_for_keymaster

/tmp/neov2/neo_inject_a/init.target.rc- start console

/tmp/neov2/neo_inject_a/init.target.rc- mount_all --late

[...]

This is also why check 36.7 fails, because there is no fstab.qcom present even though ro.hardware=qcom.
[Android Software/Hacking General [Developers Only]] OffsetPikachu55:
hi, attempting to flash 2.4.0 to 2.4.4 gives error 1 on pixel 3 with latest twrp, it fails at "- Remapping partitions and slot" and only 1.5.3.015-BETA as a magisk module works (sometimes)
[Android Software/Hacking General [Developers Only]] LeeGarChat:
Good day, this issue should be resolved in 2.4.7. Otherwise, please send me your recovery.log after the unsuccessful installation of the .zip file.

Use DFE-NEO v2. Version 2.x.x employs a different integration method into systems, no longer relying on Magisk.
[Android Software/Hacking General [Developers Only]] Rstment ^m^:
Did the script go open source? Or still closed... sigh
[Android Software/Hacking General [Developers Only]] LeeGarChat:
he was always open. This is just a set of commands for the shell
[Android Software/Hacking General [Developers Only]] RootedLee:
wow LeeGarChat, you created an "egg-laying wool-milk-sow" of a tool here - extraordinarily impressive! Kudos to your skill-set!!
[Android Software/Hacking General [Developers Only]] RootedLee:
A little gift to you and the English-/ non-Russian speaking folks here = the majority as a matter of fact: README_en.md for your GitHub page :)

[EDIT] oh, one more thing: did you explain the difference between the regular and the "Lite" versions somewhere? Is it only that the "Lite" versions don't contain the four Magisk editions? I think it would make sense to include that in both ReadMe's, too.
[Android Software/Hacking General [Developers Only]] RootedLee:
I'm getting an error trying to install v.2.4.7 via TWRP 3.7.0:

- Remapping partitions and slots
Updater Process ended with Error 118
Error installing zip file 'arm64-v8a-en-DFE-NEO-2.4.7-Lite.zip'

Nokia 6.1 [A/B], stock fresh install LineageOS 20 (Android 13)

Data wiped, reboot back into TWRP, Data mounted

Tried both available TWRP Android targets, _9.0 and _12.0

The older Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip installs with no error but is useless for Android 13.

I wasn't able to find any info about this Error 118.

Do I need to configure something in the NEO.config file? Or try and older version < 2.4.7?

[EDIT]: when installing DFE-NEO-2.3.0.zip, I get:

error 24.1: Neo is designed only for devices with a super partition!
Exiting the script

I thought my Nokia had a super partition because someone here @xda said so, but maybe that person wasn't right.. :censored:
[Android Software/Hacking General [Developers Only]] LeeGarChat:
I'm looking at fstab nokia 6.1 and understand that I will be able to add support for your device type. those without super A/B

# Android fstab file.
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK

#TODO: Add 'check' as fs_mgr_flags with data partition.
# Currently we dont have e2fsck compiled. So fs check would failed.

# A/B fstab.qcom variant
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
/dev/block/by-name/system /system ext4 ro,barrier=1,discard wait,slotselect,verify,first_stage_mount
/dev/block/by-name/vendor /vendor ext4 ro,barrier=1,discard wait,slotselect,first_stage_mount
/dev/block/bootdevice/by-name/userdata /data ext4 noatime,nosuid,nodev,barrier=1,noauto_da_alloc,discard,lazytime,errors=panic wait,check,latemount,formattable,fileencryption=ice,quota,reservedsize=128M
/dev/block/bootdevice/by-name/misc /misc emmc defaults defaults
/dev/block/bootdevice/by-name/modem /vendor/firmware_mnt vfat ro,shortname=lower,uid=0,gid=1000,dmask=227,fmask=337,context=u:object_r:firmware_file:s0 wait,slotselect
/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,slotselect
/dev/block/bootdevice/by-name/dsp /vendor/dsp ext4 ro,nosuid,nodev,barrier=1 wait,slotselect
/dev/block/bootdevice/by-name/persist /mnt/vendor/persist ext4 noatime,nosuid,nodev,barrier=1 wait

# Removeable
/devices/soc/c084000.sdhci/mmc_host* auto auto defaults wait,voldmanaged=sdcard1:auto,encryptable=userdata
/devices/*/xhci-hcd.0.auto* auto auto defaults voldmanaged=usb:auto

# ZRAM
/dev/block/zram0 none swap defaults zramsize=60%,max_comp_streams=8
[Android Software/Hacking General [Developers Only]] RootedLee:
Wow, really? That's awesome news. Thanks for checking, I really appreciate that, LeeGarChat :giggle: !!
[Android Software/Hacking General [Developers Only]] RootedLee:
the vendor/etc/fstab.qcom file from my LineageOS 20 is slightly different than the one you posted. Since even small differences might be significant, I feel I should provide it to you, here:

# Android fstab file.
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK

#TODO: Add 'check' as fs_mgr_flags with data partition.
# Currently we dont have e2fsck compiled. So fs check would failed.

# A/B fstab.qcom variant
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
/dev/block/by-name/system /system ext4 ro,barrier=1,discard wait,slotselect,first_stage_mount
/dev/block/by-name/vendor /vendor ext4 ro,barrier=1,discard wait,slotselect,first_stage_mount
/dev/block/bootdevice/by-name/userdata /data ext4 noatime,nosuid,nodev,barrier=1,noauto_da_alloc,discard,lazytime,errors=panic wait,check,latemount,formattable,=ice,quota,reservedsize=128M
/dev/block/bootdevice/by-name/misc /misc emmc defaults defaults
/dev/block/bootdevice/by-name/modem /vendor/firmware_mnt vfat ro,shortname=lower,uid=0,gid=1000,dmask=227,fmask=337,context=u:object_r:firmware_file:s0 wait,slotselect
/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,slotselect
/dev/block/bootdevice/by-name/dsp /vendor/dsp ext4 ro,nosuid,nodev,barrier=1 wait,slotselect
/dev/block/bootdevice/by-name/persist /mnt/vendor/persist ext4 noatime,nosuid,nodev,barrier=1 wait

# Removeable
/devices/soc/c084000.sdhci/mmc_host* auto auto defaults wait,voldmanaged=sdcard1:auto,encryptable=userdata
/devices/*/xhci-hcd.0.auto* auto auto defaults voldmanaged=usb:auto

# ZRAM
/dev/block/zram0 none swap defaults zramsize=2147483648,max_comp_streams=8
[Android Software/Hacking General [Developers Only]] LeeGarChat:
write me the complete installation process on your phone. I'm a little confused and unsure. For a quick discussion, write to me in telegram

@LeeGarGold
[Android Software/Hacking General [Developers Only]] RootedLee:
Great - can chat with you on TG tonite, am out of the door now 🙋‍♂️
[Android Software/Hacking General [Developers Only]] GauriSpears:
None of 2.x.x versions work for me. Poco X4 pro, Matrixx firmware. Screenshot of 2.4.7 is attached. The latest which works is DFE-NEO-1.5.3.015-BETA.zip but KSU modules don't work after it (I suppose because of Magisk stuff in 1.x.x, any Magisk module breaks all KSU modules).
[Android Software/Hacking General [Developers Only]] RootedLee:
For those who missed it:

Multi Functions Program - Browse /DFE-NEO/DFE-NEO-2.5.0 at SourceForge.net

Read Only to Read Write for android…

sourceforge.net

Release DFE-NEO 2.5.0 (Magisk-app/KernelSu-App suported) · leegarchat/dfe-neo-v2

Изменения в версии 2.5.0 (Disable Force Encryption Native Early Override) Изменения Переписан код на 90%. Большая часть бинарных файлов теперь не зависят от системных, все за счет встроенных toybo...

github.com

Now even with support for devices w/o super-partition, which is huuuge !!
[Android Software/Hacking General [Developers Only]] LeeGarChat:
New release: 2.5.1

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

Release DFE NEO 2.5.1 - Disable Force Encryption - Native Early Override · leegarchat/dfe-neo-v2

🚀 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 on...

github.com
[Android Software/Hacking General [Developers Only]] GauriSpears:
Thanks! It finally works for Matrixx firmware.
[Android Software/Hacking General [Developers Only]] Termostato54:
Hi friends,

I have a Galaxy Tab S8 LTE SM-X706B and there is no TWRP for it already. I'm trying to flash "arm64-v8a-en-DFE-NEO-2.5.1" through Magisk. The entire installation process seems to be going correctly. Then I reboot into recovery and do a factory reset to delete the user data, but then when I restart, it doesn't finish booting.

There is no problem because I can later restore it through Odin, but I can't decrypt it! Any ideas on how to make the script work without having TWRP? 🤔
[Android Software/Hacking General [Developers Only]] GauriSpears:
Maybe adb sideload dfe.zip ?
[Android Software/Hacking General [Developers Only]] RootedLee:
The new methods you introduced in 2.6.0 BETA 1 look amazing - full tweakability, I'd say :cool:
[Android Software/Hacking General [Developers Only]] Termostato54:
The only way the script seems to install successfully is through Magisk, but when I reboot to recovery to format data partition and then restart, it does not finish booting, it shows the Samsung logo forever 🤷‍♂️
[Android Software/Hacking General [Developers Only]] LeeGarChat:
It seems that for Samsung it is necessary to patch the security section as well, I forgot what they call it. I'll run tests on my Galaxy tab s7 plus as soon as I get the strength to mess around with the firmware a bit, restoring via Odin.

I would advise you to contact the branch of your device to clarify exactly how you need to patch fstab, because you can configure patching in detail in NEO.config, including specifying additional lines for patching. Just for such cases. Also, disabling integrity most likely needs to be done
[Android Software/Hacking General [Developers Only]] Termostato54:
I have tried all the combinations of options that the script offers and I always get the same result.

Do you think that by contacting Samsung I will get any response? I'll try but I'm a little skeptical about the answer they can give me.

Thanks for taking the time to research! I should have thought better before buying a Samsung Tab, no TWRP, no Fastboot, difficult to decrypt...
[Android Software/Hacking General [Developers Only]] LeeGarChat:
Why do you need to remove data encryption if there is no way to change the ROM and there is no TWRP?

Regarding the parameters, what I was talking about does not apply to the parameters that the script offers. I talked about the manual setting `FSTAB_PATCH_PATERNS`, in this parameter you need to set specific patterns to delete. As far as I understand, for the Knox partition you also need to set the parameters for removing encryption. check how to patch fstab in Multidisabler in their thread, it also disables encryption for Samsung

[Pie/10/11] [System-as-root] Multidisabler: disables encryption, Vaultkeeper, auto-flash of stock recovery, proca, wsm, cass, etc.

The multi-disabler started life on the Exynos S10 range, the first Samsung devices to launch with Android 9 (Pie). Since then, it has grown to support a great many Samsung devices running either Android 9, 10 or 11, and with either an Exynos or a...

xdaforums.com
[Android Software/Hacking General [Developers Only]] Termostato54:
That is a very good question. I hope a compatible version of TWRP is released soon and be able to make nandroid backups. It is very tedious to make modifications that can cause bootloops if you do not have a nandroid to recover.

I would also like to make R/W certain system files (e.g. build.prop) to make some modifications.

I'm going to take a look in that thread 🧐
[Android Software/Hacking General [Developers Only]] veekay:
This works perfectly when first setting up a new rom, but I have noticed after reflashing the same rom or doing an upgrade that the data partition seems to encrypt itself again? I flash the zip file again, but it says it is already installed.
[Android Software/Hacking General [Developers Only]] moresat:
when I try to install it I get error 21. what is this?
[Android Software/Hacking General [Developers Only]] EmPiFree:
Is there a known issue with WhatsApp regarding DFE? Somehow WhatsaApp doesn't see my app, as an official app. Even it is. On other phones I can normally verificate my number.
[Android Software/Hacking General [Developers Only]] veekay:
I'm guessing there is no way to disable this and have encryption turned back on that doesn't involve formatting the data partition again?

Since this doesn't survive between rom flashes I'd like to remove it, but don't want to start all over again setting up my phone.
[Android Software/Hacking General [Developers Only]] RootedLee:
@veekay

1. root your ROM

2.a) backup all apps & data with Swift Backup (free) to SD

2.b) manually backup apps like WhatsApp

3. backup internal data manually

4 install new ROM

5. restore internal data

6. install Swift Backup and restore apps & data

done
[Android Software/Hacking General [Developers Only]] veekay:
That what I did when moving from A10 and not about to go through that process again unless absolutely needed.
[Android Software/Hacking General [Developers Only]] chermyX:
changed ro to rw will cause a problem, for example:

-m /system -p ro--to--rw

this has no problem because the whole "system" does not have any other "ro" chars:

system /system ext4 rw wait,logical,first_stage_mount

but if you modify other line like:

-m /product -p ro--to--rw

it will change into:

prw /product ext4 ro wait,logical,first_stage_mount

so this bug can be caused reboot continuously.

version: arm64-v8a-en-DFE-NEO-2.6.0-beta-1-lite

thanks for the script anyway, i'm so glad that i can disable the /data encryption finally <3
[Android Software/Hacking General [Developers Only]] Gueste4555:
Can the script work on a Samsung Galaxy S9+ (Exynos 9810), a Samsung Galaxy S21 FE 5G (Snapdragon 888), a Samsung Galaxy S24 Ultra 5G (Snap 8 Gen 3) and a Samsung Galaxy TAB S9 Ultra 5G Tablet ( Snap 8 Gen 2)?

Can it decrypt Data and disable forced encryption?

Finally, if I install TWRP on a Samsung Galaxy TAB S9 Ultra 5G Tablet (Snap 8 Gen 2) and flash the DFE script, will the data be accessible? and the system will start?
[Android Software/Hacking General [Developers Only]] asislife20:
With the newest version I am able to successfully remove encryption ad make R/W. However when I try to set a lock screen it just loops back and asks me to set a lock screen, or settings crashes. Anyone have any ideas?
[Galaxy A3, A5, A7, A8, A9 Q&A, Help & Troubleshoot] HannahSolo:
6/6/22 Update.

I've just called PayJoy Mexico. I explained the situation, they asked for a bunch of questions to make sure I was the user, and they told me they were going to do something on the system to remove the locks. If it didn't worked they recommended me to go to a technician so they could change the base board.

It didn't worked. :(

Now I got bad memory because I can't remember the password and an expensive... brick. Sigh.
[Galaxy A3, A5, A7, A8, A9 Q&A, Help & Troubleshoot] blackhawk:
The phone has to have service on their phone system for their fix to work... call them back.
[Galaxy A3, A5, A7, A8, A9 Q&A, Help & Troubleshoot] tutibreaker:
That is the MDM locked, only the agent who activate it can remove it
[Galaxy A3, A5, A7, A8, A9 Q&A, Help & Troubleshoot] HannahSolo:
Hi. Thank you for your answer.

Could you please elaborate a little? What do you mean it has to have service on their phone system? Do I ask PayJoy to call me to the phone? (It won't allow me to dial anthing) Or just use the same number that was registered with them and have the phone turned on while they try to fix it?

Thanks.
[Touch HD General] eire77:
hey guys...just looking for some help. its not a big problem but i just got my hands on my HD yesterday and everytime i check whats running in the backround...theres Active Sync.

i close it and check back 2 minutes later and there it is again!

i noticed this on my diamond after i update it with the latest WWE ROM but didn't take to much notice of it because i was giving it to the girlfriend.

is it meant to run in the backround??

i haven't even connected it to the laptop yet

cheers,

Phil
[Touch HD General] bedav:
Same problem for me !
[Touch HD General] jentech:
I tried this http://xdaforums.com/showthread.php?t=423540 from the Diamond forum, but it doesn't seem to work.
[Touch HD General] eire77:
cheers mate,

i'm gonna give that a go and i'll let you know how i get on
[Touch HD General] david-v:
I have the same on my old device, Mitac Mio A701. This is probably normal for Windows mobile device. Check out this thread too. there are solutions for this...
[Touch HD General] eire77:
the most simple and elegant solution:

just add activesync to exclusive list in the task manager...

1. when you'll check and get activesync on (uninvited)

2. go to task manager.

3. Click and hold on the word Activesync and then select from the pop-up "add to exclusive".

4. go to exclusive tab and thick activesync (repllog.exe).

done. worked for me many times (many ROMs)

i've tried this one (thanks to KukurikU) ...and so far so good.

i think its still running in the backround somewhere but i can't see it.

will try the other ones suggested...for a permanent fix later

cheers
[Touch HD General] buggybug0:
yes you are right, you only prevented the application UI from running, the processes that's related to activesync are still running. there are several of them, so you may only have killed 1 or 2.

i don't understand why you want to kill activesync permanently. how do you sync your contacts and calendars and all that? :S
[Touch HD General] eire77:
i don't wanna kill it permanently...i just don't want it running in the backround and the fix that i applied works fine for me but i don't understand why its running??
[Touch HD General] Moe5508:
Kill ActiveSync Process when idle

Please see this...which I believe is an elegant solution to ActiveSync continous running...

http://xdaforums.com/showpost.php?p=2135727&postcount=1
[Android Head-Units] ppl24:
Hello, I'm new here !

I bought this Android car radio (https://fr.aliexpress.com/item/3280..._list.0.0.72ab5e5bmptYkx&gatewayAdapt=glo2fra) years ago.

But today it goes to black screen without reason and the reset button just restart the unit which goes to black screen - I tried to ask to the vendor but i get no answer..

Could you help me to find the original firmware/rom to perhaps make it work again ?

Thanks for you support
[Samsung Galaxy Tab S8] drjoe1:
So I have a 45W charger, thinking about purchasing a 65W charger. I know The Tab S8 Plus only goes to 45W.

My question: are there any advantages to using an emark enabled cable?

I'm getting super fast charge notice with a 60W cable, no emark.

In my google searches, someone mentioned you can get "super fact charging 2.0" if you use an emark cable. Other pages said you only need emark above 60W. I found this comment on one site "... the Samsung Note 10+ or S20 Ultra which supports 45W fast charging. With these devices, the maximum electrical current is 4A, therefore it also requires a 5A cable with E-Mark. "

Does anyone know the ins and outs of this?

Thanks,

Joe
[Samsung Galaxy Tab S8] blackhawk:
Get the recommended Samsung OEM brick and use the cable that comes with it. For the N10+ the 25w brick/cable fast charges fine and lasts for years if you don't roll up the cable.

Charging issues are hard to troubleshoot and non OEM bricks/cables only add to that burden.

At $20 a pop the 25w brick/cable is a no brainer.
[Samsung Galaxy Tab S8] drjoe1:
So I have managed to answer my own question:

With a normal 3.1A US0b-C to USB-C cable, my 45W power supply is throttled back to 25W. It is reported as "Superfast Charge" mode by the tablet. Using Ampere, it reports that the battery is being charged at 5A at 4.2V --~ 21W

I bought a 100W E-Mark cable, and it now reports "Superfast Charge 2.0" -- and now Ampere reports it has bumped up to 7.5A at 4.36 V. So it is bumped up to 32W. Still not seeing 45W, though.

So it would seem to be charging 50% faster with the new cable.

Joe
[Samsung Galaxy Tab S8] jocker96:
I ues this combo for my s8+:

Anker PowerPort III 65W

Anker PowerLine III-Flow

It gives me 28W which is plenty fast for me. I can also use same charger for all of my devices, my laptop included
[OnePlus 7T Pro (Regular & McLaren) Guides, News...] gumka77:
All most daily use.

Color OS 12.1 H.14 Closed Beta 3 Released For Oneplus 7, 7 pro, 7T, 7T Pro – Download The Full Zip Here

OnePlus is turning its focus to its mid-range portfolio after upgrading the OnePlus 9 and OnePlus 8 series to Android 12. For the OnePlus Nord, the company has now launched the first public beta build of OxygenOS 12 based on Android 12. ColorOS 12 C.14 & C.21 for Oneplus 8, 8 pro & 8T have also...

techibee.in

Regards
[OnePlus 7T Pro (Regular & McLaren) Guides, News...] gumka77:
reserved