Related
SYSTEMLESS DevBase has been developed and physically tested on S7 Edge (G935F), so main thread containing the most detailed description you can find here:
>> [SAMSUNG][6.0+] SYSTEMLESS DevBase | Encryption support | Stock OTA updates <<
However, it should work on ALL SAMSUNG DEVICES running Android 6.0+, so if you are Galaxy S6 Edge (G925xx) owner - please place your feedback & discussion here to let me know about device-specific issues or to let me know that everything works perfect
---------------------------------------------------------------------------
Are you tired with traditional custom ROMs?
Do you miss custom ROMs but you would like to have encrypted /data (for privacy/security reasons)?
You are in the right place! I present you SYSTEMLESS DevBase - an SYSTEMLESS equivalent of my previous work (for older devices)
Prerequisites:
- Samsung device running stock or stock-based Android 6.0+ (mandatory!)
- Rooted device - SuperSU v2.76+ installed in SYSTEMLESS mode (mandatory!) (*)
- Stock, untouched /system partition (not mandatory, but recommended for working OTA)
- Stock recovery (not mandatory, but recommended for working OTA)
(*) NOTE: The latest CF-Auto-Root image for G925F contains SuperSU v2.74 which does not support SYSTEMLESS solutions (su.d is not triggered early enough). It is NOT enough to update it via PlayStore to the newest version and update su binaries! You need to update it using TWRP / FlashFire installable ZIP from THIS STABLE or THIS BETA thread. Alternatively you can use "EverRoot" -> "Inject SuperSU" option in FlashFire even if you are rooted already by CF-Auto-Root (it will update SuperSU in the same way as flashing ZIP).
SYSTEMLESS DevBase:
1. Benefits / main features:
- Works with encypted /data partition
- Working official OTA updates! (see Tips & Tricks)
- Does NOT perform any phisical modifications in /system
- Does NOT perform any additional changes/patches to the kernel
- Removed KNOX warnings (systemlessly removed SecurityLogAgent)
- It contains SYSTEMLESS BusyBox (bionic, the most stable and respected release)
- It allows you to easily modify most of files & apps in your /system - SYSTEMLESSLY (see Tips & Tricks)
- It does not interfere with Magisk! You can use Magisk in paralell with SYSTEMLESS DevBase if you need it for your favorite module.
2. Systemless Safe De-Bloat (more info below):
What does it mean and why is it called "safe"?
- ONLY apps available in stores will be systemlessly removed from the ROM, so you can easily (re)install any of these app if you like
- ONLY pre-installed system apps are will be systemlessly removed, DevBase installer never touch any updated app nor app installed manually from store
Thus, the following conclusions can be drawn:
1. If you install my SYSTEMLESS DevBase directly over working stock ROM - in most cases almost all these apps will remain untouched, because almost all apps have been updated already (stored on /data). But then you will be able to remove any useless app using the "Application manager" -> [Name_Of_App_To_Remove] -> MORE -> Uninstall updates. NOTE: App will disappear arter reboot and will be visible even in Titanium Backup!
2. If you perform "Wipe data" directly before installing SuperSU and my SYSTEMLESS DevBase (before you let to install app's updates) - then all apps listed below will be removed. If you would like to use any of these apps - just install it manually from appropriate store. Installed manually app will not be removed during the next DevBase update or re-install.
Removed apps list (depends on the device, should cover all devices starting from Galaxy S5):
ChatON
Chrome
Drive
Dropbox
EditorsDocs
Evernote
Excel
Facebook
FB Messenger
FB Pages Manager
Flipboard
Google+ / Photos
Group Play
Hangouts
Instagram
OneDrive
OneNote
PEN.UP
Play Books
Play Games
Play Movies
Play Music
Play Newsstand
PowerPoint
Skype
Smart Remote
WhatsApp
Word
NEW! Safe De-Bloat feature automatically detects and systemlessly removes apps not listed above, but present in your CSC package
3. Systemless CscFeature MOD (enabled some built-in, hidden features):
- Added shutter sound menu in Camera app
- Sending/receiving MMS without data on
- Show SMS/MMS sending time instead of receiving
- Added "Exit Internet" option to stock browser
- Added call button in Phone Logs (**)
- Added "Call/Message block" option in Settings
- Added symbols as secondary keys in Samsung keyboard (**)
- Call Recording (manual control, added "Record" button)
(**) may not work starting from Android 7.0 Nougat
Installation:
1. FlashFire app (recommended ***):
- Open file using "Flash ZIP or OTA" option
- UNTICK "Mount /system read/write" [extremely important for working OTA!]
- Enable "EverRoot" -> "Inject SuperSU" option if necessary (see NOTE above (*))
- Tap "FLASH"
2. TWRP recovery:
- Tap "Keep Read Only" on the Welcome screen [extremely important for working OTA!]
- Open file using "Install" option (use extSdCard or OTG storage in case of encrypted /data)
- Confirm flash by swiping right
- Tap "Reboot System"
NOTE1: One additional auto-reboot may be performed at first boot. It is not a bug (may be required for systemless build.prop support - see Tips & Tricks for more explanations)
NOTE2: Do not worry about red "mount /data failed..." messages displayed in TWRP in case of encrypted /data (installer will do the work anyway!)
(***) As far as I know - FlashFire is the only flashing tool with full access to /data during flash in case of encrypted devices. It is also the only tool which allows you to perform full backup/restore of partitions, including encrypted /data. It does NOT require custom recovery to work!
Credits: @Chainfire for systemless SuperSU and a lot of inspiration
Hit Thanks button if you like my work. If you really appreciate my work - feel free to buy me a beer
Download
>> Recent SYSTEMLESS DevBase <<
Note:
Check MD5 sum BEFORE flash (useful TOOL), because flashing damaged or incomplete ZIP files can lead to issues! Correct MD5 sum is shown on the AndroidFileHost website while downloading.
Changelog
Please visit MAIN THREAD - post #3
Tips & Tricks
1. OTA updates:
- Basically, the only thing you need to take OTA update is to perform "Full unroot" in the SuperSU app. However, a better way is to use "unroot2ota" terminal command, because this will not remove DevBase boot script from /su/su.d and the only thing you will need to re-activate SYSTEMLESS DevBase (and all your systemless MODs) after performing OTA update is just re-root your device with CF-Auto-Root.
- If you flashed custom recovery like TWRP - it is mandatory to restore your stock recovery (otherwise OTA will not work). You can do it using FlashFire app (the easiest way) - just open recovery.img file (extracted from your original FW) using "Flash firmware package" option, disable "Preserve recovery" option and then tap "FLASH". EDIT: Starting from version v1.2 there is a new "unroot2ota" feature which allow you to restore stock recovery using /system/recovery-fromm-boot.p file. There is no guarantee to perform it successfully (even if there is no error message) but in most cases it works well (tested on Nougat beta). Please go to recovery before you try to get OTA to check if you have stock recovery already after performing "unroot2ota" (if not - you need to use PC Odin to flash recovery.img packed in tar file).
- It is recommended to temporarily disable "Auto-update apps" in Play Store settings before you unroot your device. It will prevent updating applications covered by Safe De-Bloat list, as there apps will temporarily appear until you re-root the phone after performing OTA update.
Note (devices which use dm-verity): You should never allow /system modifications in TWRP, never allow to remount /system r/w in any app (e.g. Root Explorer, FlashFire, etc.) and never flash a ZIP file which could modify your /system or remount it r/w. Failure to follow these recommendations will break dm-verity verification and will cause, that your device may not be able to boot with the stock kernel (you will need to re-flash your original FW using PC Odin to make your device bootable).
2. Making your own modifications:
- You can systemlessly replace any existing system app by modded one. Just put modified app to /data/devbase/system/app or /data/devbase/system/priv-app and then reboot your device
- You can systemlessly replace jar or apk in /system/framework. Just put modified one to /data/devbase/system/framework and then reboot your device (NOTE: framework support has been added for advanced users -> there is high risk of bootloop if you do something wrong!)
- You can systemlessly add or override any line in /system/build.prop. Just put (only new or changed) line to /data/devbase/system/build.prop and then reboot your device (NOTE: one additional auto-reboot will be performed if /data/devbase/system/build.prop file has been added, modified or removed. It is not a bug - it is required for the changes in /data/devbase/system/build.prop to take effect!)
- You can systemlessly replace any existing file in /system/csc and /system/etc (but NOT in subdirectories). Just put modified copy of a file to /data/devbase/system/csc or /data/devbase/system/etc and then reboot device
Limitations: original app or file MUST physically exist with the same name in /system, you can NOT add a new app or file this way!
Example 1 (Ad-Blocking): Download the latest Ad-Blocking ZIP installer from THIS thread. Extract "hosts" file (placed in /system/etc inside ZIP file), then copy it to /data/devbase/system/etc, set rw-r--r-- (644) permissions and then reboot device
Example 2 (modded SystemUI): Create "SystemUI" directory in /data/devbase/system/priv-app and then put modified "SystemUI.apk" file into it. Set rwxr-xr-x (755) permissions to "SystemUI" directory, rw-r--r-- (644) permissions to "SystemUI.apk" and then reboot device
Example 3 (De-Bloating a bit more): You can just create empty directories in /data/devbase/system/app (or priv-app) corresponding to applications in /system/app (or priv-app). Alternatively (more advanced method), you can add an app to modded enforceskippingpackages.txt file (you can find it in /data/devbase/system/etc or /data/devbase/system/csc_contents, depending on the original location in /system) and increase number in the 1st line. Second method should not be used by beginners (without a basic knowledge related to UNIX text format)
3. How to manually maintain the newest ROM version:
If you do not care about OTA - you can manually update your device to the newest ROM available @ Sammobile, keeping your original CSC (you need multi-file original FW, I mean separate files for BL/AP/CP/CSC). You need to download 2 ROMs: ROM with the newest changelist and the latest ROM containing your original CSC. Extract both and open in PC Odin BL/AP/CP files from the ROM with highest changelist but open CSC file from the ROM containing your CSC (I recommend to use HOME_CSC_* file to avoid auto-wipe-data). Flash such "mix", re-root and enjoy
Reserved
There is new version available
Changelog
v1.1:
- Added SYSTEMLESS support for /system/framework
- Added SYSTEMLESS support for /system/build.prop (overrides & additions)
- Added major Android update detection (auto-remove mods for older API to prevent bootloops & FCs)
- Added BusyBox bionic (the most stable and respected release)
- Added logging to /data/devbase/last_boot.log (API & errors)
- Added SuperSU boot patcher version checker (exits su.d boot script if < 2.76)
- Added "Please DO NOT wipe /cache" warning in case of encrypted devices and TWRP recovery
- Minor changes & optimizations in the shell code
- Added SYSTEMLESS DevBase uninstaller
Download link:
>> SYSTEMLESS_DevBase_v1.1.zip <<
Since new version has many more features -> there are more possibilities of bootloop (especially if you are playing with framework mods). I have created DevBase remover to let you get out from bootloop. Of course uninstaller does NOT "know" which mod caused the problem, so it will not remove any file from /data/devbase directory, it will remove only /su/su.d/0000000devbase boot script to make your device bootable (again) so you can manually delete problematic mod:
>> SYSTEMLESS_DevBase_remover.zip <<
Another update:
v1.3:
- Fixed CscFeature MOD (e.g. G920I case, now should work with all Samsung devices/variants)
v1.2:
- Added info in Settings/About device/Software info/Build number (can be overrided by editing /data/devbase/system/build.prop)
- unroot2ota: added ability to restore stock recovery using /system/recovery-from-boot.p file (no guarantee)
- unroot2ota: check /system partition for common modifications before unroot
- Minor changes & improvements in the shell code
>> SYSTEMLESS_DevBase_v1.3.zip <<
Hi,
Hope somebody got some more tips or a fix for the following problem i have with my huawei mate 9 C432 (europe version) (bought 2nd hand with this problem)
* Phone came with not working touch at android lock screen ONLY (brown wallpaper, water dock, clock works, icons show like normal)
* When i go to recovery everything works fine, NO touchscreen problem at all.
* Couldnt get my product id number inside settings to generate unlock bootloader code so i used DC PHOENIX, DC UNLOCKER, HCU. FLashed the following with DC phoenix, this unlocked my bootloader.
- Flashed MHA-AL00A_HLMHAAL00AM00A063_Factory_firmware_China_Nonspecific_Android_7.0_EMUI_5.0.dgtks
- MHA-L29B_C432B185_Firmware_Switzerland_Nonspecific_Android7.0_EMUI5.0.APP
- L29B_C432B185_update_MHA-L29_hw_eu.APP
(In this order)
After Flashing these 3 files my phone boots like normal and STILL i get the same touchscreen problem at the lockscreen (brown wallpaper). Recovery works fine, fastboot also.
Then i decided to flash only the FACTORY FIRMWARE CHINA NONSPECIFIC 7.0 DGTKS file >>>>>> Now at this lockscreen the touchscreen magically works and i can do whatever i want in the settings (android 4.2 i believe). No problems at all. Problem is i cant stay at this HUAWEI ASCEND (bootlogo) firmware. I want Android 7 / 8 for Huawei mate 9.
After this i also flashed TWRP recovery and did a format CACHE, DALVIK, SYSTEM, DATA and then installed custom firmware RomAur-v2.2 from this forum.
After flash i get the freaking brown bridge lockscreen AGAIN with no working touchscreen. The phone doesnt give me any SETUP (language, wifi etc) option at all before lockscreen, with Samsung phone roms i usually have to setup the custom rom first. None of that here.
Highlighted some "maybe" important info??
===========================================================
Twrp Custom Rom RomAur-v2.2 flash log:
RomAur B197 v2.2 by auras76
>>> Mounting partitions
>>> Writing system
>>> Creating toolbox symlinks
>>> Setting permissions
>>> Flashing Boot
>>> Installing Busybox
>>> Installing Magisk...
**************************
* Magisk v14.0(1400) Installer
**************************
- Mounting /system, /vendor, /cache, /data
- Device Platform: arm64
- Constructin Enviremonment
- Adding addon.d survival script
- Found Boot Image: /dev/block/sdd32
- Unpacking Boot image
- Checking ramdisk status
- Stock boot image detected!
- Backing up stock boot image
- Patching ramdisk
- Repacking boot image
- Flashing new boot image
- Unmounting partitions
- Done
>>> Enable init.d...
***********************************
System/Less Module Template
***********************************
A simple init.d emulator (@korom42)
***********************************
- Magisk/Systemless Install
- Mounting /system(ro), /vendor(ro), /data, /cache ! Magisk is not installed!
>>> Unmounting partitions
>>> Installation Complete!
script succeeded: result was [>>> Installation Complete!]
Update partition details
....done
So hope it a bit clear for you guys, maybe you can help me??
What could this be? I was think about some corrupt touchscreen related files that are present on the internal space of the phone that are stuck in there and need to delete them?? Maybe some boot image that doesnt get flash.
THANKS
No help so i fixed it after spending too much money on tools and testing for days. Nevermind its fixed now.
Dramacydril said:
No help so i fixed it after spending too much money on tools and testing for days. Nevermind its fixed now.
Click to expand...
Click to collapse
hi
i have this problem too
if you fixed it please tell me how?
thanks
Rooting (super root) of this phone is complicated!
So i obtained actual root procedure from sceryavuz. Someone more experiemced please lets ask me the question:
So please tell me if i get it right. Also when I will be flashing the os I will do it from internal memory not SD card in case only fastboot could read SD card .
Goal: system rw, xposed, no sudden death
Complexity: hard
Troubleshooting : very hard (7/10)
Drm: 32.4.A.1.54, E6653
Kernel specification (stock)
Link list:
Fastboot oem unlock x(given code from site)
flashtool for sony devices 0.9.25.0 x64
patch kernel with tool
https://mirrorbits.lineageos.org/fu...neage-14.1-20190224-nightly-sumire-signed.zip
Nightly is flashable, SHA checksum where?
SHA:
https://download.lineageos.org/sumire
https://forum.xda-developers.com/attachment.php?attachmentid=4493759&d=1525538964 (zip)
xposed-v89-sdk25-topjohnwu.zip
https://forum.xda-developers.com/attachment.php?attachmentid=4393853&d=1516377687 (apk)
xposed installer 3.15 Magisk apk
Other links:
Link1
https://forum.xda-developers.com/xperia-z5/general/ftf-e66xx-patched-kernels-google-drive-t3688365
https://forum.android.com.pl/topic/...5-dual-wersje-ce1-brandy-polskich-operatorów/
Root procedure
1. Ta backup
2. Backup Service menu
3.
Windows 7 : Tap F8 while booting and select required option
Windows 8, 8.1, 10 : Read This Instructions
4. Install all drivers
5. Unlock bootloader
Fastboot oem unlock x(given code from site)
?
[
1. Can be downloaded stock rom via flashtool stock (No xposed) to extract and patch kernel with tool and to patch via flashtool (format data cache etc)
flashtool for sony devices 0.9.25.0 x64
* Do not know any further *
]
6.
Fastboot boot recovery.img
7. Backup
8. Backup all partition to internal memory
8a.
If your device is encrypted (sim unlock password not lock screen) then you need to decrypt it via operator
Uptade to 32.4.A.1.54 For DRM fix via guide by sceryavuz
9. Flash twrp
9-1) adb reboot bootloader
9-2) Copy recovery image to C drive and rename recovery image to recovery.img.
Type the following command to flash recovery image.
9-3)
fastboot flash recovery c:\recovery.img
9-4) Now type the following command to reboot bootloader.
9-5)
fastboot reboot-bootloader
9-6) and then type the following command to erase cache.
9-7)
fastboot erase cache
9-8) Now type the following command to reboot your device.
fastboot reboot
10. So the files to use:
1.Lineage os 14.1 xperia z5 (nomodelname) sumire rom newest. Zip
Link:
https://mirrorbits.lineageos.org/fu...neage-14.1-20190224-nightly-sumire-signed.zip
Nightly is flashable, SHA checksum where?
SHA:
https://download.lineageos.org/sumire
Data-system-caches format (without internal?)
2. Gapps 7.1 for cm14. 1 lineageos xperia z5 nomodelname shurimi. Zip
Link:
https://opengapps.org/
(ARM64, 7.1, pico (can be also full? already downloaded))
+ Md5 checksum for android
Reboot
....
Shutdown
Recovery
3. Magisk (with built in root method (zip), modded for xposed)
a) Zip root and framework (its somehow manifest change and linked so its systemless? the light modules like xsuite, edge etc work I quess, but heavy ones like gravitybox can be highly incompatible)
Link (php):
https://forum.xda-developers.com/attachment.php?attachmentid=4493759&d=1525538964 (zip)
xposed-v89-sdk25-topjohnwu.zip
b) GUI to enable framework
https://forum.xda-developers.com/attachment.php?attachmentid=4393853&d=1516377687 (apk)
xposed installer 3.15 Magisk apk
Disabling xposed via magisk allow also safetynet check for Android pay? I dont need it, just curious.
Do i need special one root method for this rom?
Magisk xposed instead of systemless edxposed
4. Adaway (systemless method), adaptive Google storage instead Apps2sd etc.
5. Is this Super-Root (kernel is patched to allow r/w for root user?) or I need fix?
Busybox is present or can I just flash it?
6. Super-Root of device (???)
su
Termux
echo 0 > /sys/kernel/security/sony_ric/enable
Lastly write this
Code:
busybox mount -o rw,remount,rw /system
____________________________________________________________________
Then I can use app to move for example ogyoutube to /system/app instead of typing cp -R /sdcard/Android/Data/com.xxx.org and rm
or linking like this
ln -s (path to be linked) (to location)
ln -s /sdcard/data/hosts /data/data/hosts
I can use Titanium Backup to remove sth via recovery f.e
or I can change fonts while system is running.
____________________________________________________________________
Questions
1.Ok i parsed these links (shurimi lineageos flashable and magisk root xposed) but idk if i can use full packet of gapps or mini. I have 520 MB free on my current Rom (es file Explorer present, checked via terminal) and gapps full is 522mb (i need pfx support on my device). The lineage uncompressed weight is approximately 4gb so i can use either mini (322 MB) or full (522), if i flash too big file it either hardbrick my CMOS on Emmc or just be refused by TWRP via fastboot.
Busybox is built in, magisk root my phone, adaptive storage should work. The cyanogenmod comes also with tools to modify navbar, change volume, navigation bar, modifing strings for buttons (should not Conflict with remap), global equalizer, but it should not conflict with my xposed modules ... BTW do you know a simple app or magisk module to apply fxes like flanger globally to audio channels or sound processor?
2. If kernel is patched and included in os System should be writable? Also Recovery should be linked, so device is full root device not root device (Recovery bootable and accesible from system) , right?
Other device (super root problem)
https://github.com/Nilhcem/hosts-editor-android/issues/28
If i need to have another patched kernel then im willing to not rather replace kernel img to flash with superrooted one because it always a risk that sth will be corrupted... Or you can send me via google drive prepatched Rom if its not as dangerous as it seems for me...
https://tunecomp.net/switch-cyanoge...de-on-cm1314-and-gain-access-to-system-files/
Abbility to modify system on cyanogenmod.
I had been using Aokp kanged Rom on Another device and I was able to modify system partition.
3. I should not apply Sony ric fix as follows
echo 0 > /sys/kernel/security/sony_ric/enable
busybox mount -o rw,remount,rw /system
Or
https://dammit.nl/20160406-how-to-f...oid-devices-with-supersu-systemless-root.html
_____________________________________________________
If verified ok i will tell if its working.
Edit 22.03.19
Please help me! Basic question is CAN I INSTALL FULL GAPPS INSTEAD PICO TO LINEGE OS 14.1 via TWRP??? (currently: system weight 4gb of 5.1, lineage os weight 4gb gapps weight 500mb)
Troubleshooting
I'll try my very best to get it released at 12:51:21 GMT +2.
Glad you didn't ask for a date. Otherwise I would have needed to scream at you for being demanding and disrespectful.
Kamilksie said:
Yes but builtin camera is googlecamera and i have only 8mp.
Click to expand...
Click to collapse
That's probably because of your gapps package.
With the bigger gapps you change camera app to google's
Try a new flash of the rom with pico gapps only, that should do the trick
Thanks, but this guide is only for phones running stock ROM version 32.0.A.6 and earlier, while I'm running 32.4.A.0.160
Really don't want to brick my phone, so are there any other more up-to-date guides out there?
Sent from my Xperia Z5 using XDA Labs
Here you go: https://forum.xda-developers.com/crossdevice-dev/sony/iovyroot-temp-root-tool-t3349597
Afaik, there's another solution, but I did it successfully that way.
Thanks, but this guide is only for phones running stock ROM version 32.0.A.6 and earlier, while I'm running 32.4.A.0.160
Really don't want to brick my phone, so are there any other more up-to-date guides out there?
Sent from my Xperia Z5 using XDA Labs
Here you go: https://forum.xda-developers.com/crossdevice-dev/sony/iovyroot-temp-root-tool-t3349597
Afaik, there's another solution, but I did it successfully that way.url]https://source.android.com/security/advisory/2016-03-18[/url]
uses CVE-2015-1805
so with newer ROM versions it most probably doesn't work,
downgrade / flash a Marshmallow version or an earlier one on which this method works
The others probably can give advice with which version they were successful with that approach,
better ask in that mentioned thread (iovyroot)
20MP only works with some apps, the others are blocked by the vendor binaries (On stock, it only works with Sony Cam btw). Please use the builtin camera for the full 20MP.Hi at all,
I have installed the latest rom on my Z5 Dual and it seems to work fine. But I have the problem that flashing of SuperSU did not work. I used the search bar but I have not found an answer to my problem. So I hope that I do not ask a question which is already answered.
I flashed via TWRP and flashed the following zips:
- latest Lineage 14.1 from the first page
- GApps for Arm64
- Gsam Root Companion V1.6 (this flash has worked)
- AdAway for systemless root (because on my Nexus 7 2012 where I first installed Lineage 14 only this worked)
- SuperSU (addonsu-14.1-arm64-signed.zip; did not work)
The first two zips where system and Gapps. For the other ones I don't know the order. But I have not seen an error in TWRP.
Could anyone help me what I have to do that I can use SuperSU?
The second point (not so important): TWRP has been oberwritten after flashing so that I cannot enter without flash it via Flashtool. But then I have to reflash the zip from Lineage. Is this normal? On my Xperia M dual this was the same way.
Try only flashing system, gapps and root for now, to isolate the issue. Once that works you can still take care of the rest.
For TWRP: We do not include init_sony, as all of the newer Bootloaders (got introduced sometime in M) can boot straight to TWRP. Use fastboot to flash twrp to FOTAKernel (fastboot flash FOTAKernel twrp.img). You can then boot to twrp by powering down your phone and pressing volume down+Power (let go after the vibration).
Gotcha. I just got the latest version (9.20.961291) and it'll take the picture in HDR but it crashes each time. Which one do you use?
It's the same (same developers + maintainers)
HTC camera app can work pretty well
TWRP - fix volume
https://drive.google.com/open?id=0B5DTiLDUqHi8cTBTZU9wZHZmUEU
Gotcha. I just got the latest version (9.20.961291) and it'll take the picture in HDR but it crashes each time. Which one do you use?
No LDAC on custom ROMs,
the following audio mod promises LDAC support and also works greatly on crDroid, LineageOS and RR:
https://forum.xda-developers.com/android/software/mod-quasaratmox-ultimate-sound-mod-t3479705
but take note that battery consumption will raise from e.g. 2-3% per hour to 6-8% per hour (net audio consumption + other battery users) due to sound processing (e.g. while listening to music via the included Sony Music app or PowerAMP)
This ROM will never pass SafetyNet, I've been following this for the last few months. It's an LOS decision (https://lineageos.org/Safetynet/) not specific to the Z5 version of the ROM.
This ROM will never pass SafetyNet, I've been following this for the last few months. It's an LOS decision (https://lineageos.org/Safetynet/) not specific to the Z5 version of the ROM.
No.
Does this ROM support microg (NoGApps) / UnifiedNlp?
Sent from my sumire using XDA LabsTry it with last stock Marshmallow using Flashtool.
Then start Boot up your phone, wait till the welcome message.
After that power down phone with power button + volume up.
Use Flashtool to flash recovery, after that boot up with power button + volume key down.
In recovery flash LineageOS, don't reboot after that, instead power off.
Now get back to Flashtool and flash the LineageOS supported boot.img
Sent from my Sony Xperia Z5 using XDA Labs
Updating partition details...
...done
Full SELinux support is present.
MTP Enabled
Installing zip file '/external_sd/ROM Things/lineage-14.1-20170720-UNOFFICIAL-sumire.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
E3004: This package is for device: E6633,E6653,sumire,sumire_dsds; this device is .
E:unknown command [log]
Updater process ended with ERROR: 7
Error installing zip file '/external_sd/ROM Things/lineage-14.1-20170720-UNOFFICIAL-sumire.zip'
How I'm going to fix it? It says: " this device is . ", I'm using an E6653.
How I'm going to fix it? It says: " this device is . ", I'm using an E6653.
Updating partition details...
...done
Full SELinux support is present.
MTP Enabled
Installing zip file '/external_sd/ROM Things/lineage-14.1-20170720-UNOFFICIAL-sumire.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
E3004: This package is for device: E6633,E6653,sumire,sumire_dsds; this device is .
E:unknown command [log]
Updater process ended with ERROR: 7
Error installing zip file '/external_sd/ROM Things/lineage-14.1-20170720-UNOFFICIAL-sumire.zip'
HoiFung said:
Look here and here a few replies.
https://forum.xda-developers.com/xp...gle-haozeke-s-lineageos-t3557646/post71068188
Sent from my Sony Xperia Z5 using XDA Labs
Click to expand...
Click to collapse
Thanks for your help.
One question, how I'm going to use this Updater-script?
Trying to installing it over recovery does not work.
Do I need to put the script into the ROM, or over Flash Tool?
Never mind found it here in ROM ZIP ( META-INF\com\google\android )
Hope repacking should be enough.
I am not a newbie, I had Xperia Z, Z1, Z2, Z3 Compact in past and havent meet problem like that (never)
This is what exactly am doing
Flash latest stock by Sony (7.1.1 bulid 160) in flashmode
Install TWRP recovery in fastboot by command fastboot flash recovery (path to recovery)
Ok, successfully booted to twrp by holding vol down and power when device is off
In twrp:
Wipe data, system, dalvik cache, cache, internal
Now, install zip, choose rom zip
Carbon logo in recovery, after some time it say installation is complete
Reboot phone
Stuck in bootloop
Am going creazy with that, am experienced user and I havent meet anything like that ever before, no idea how can I solve that
Tried even command
Fastboot erase boot
Fastboot erase system
Fastboot erase userdata
Fastboot erase cache
Then install boot in fastboot, flash recovery and rom in twrp....
Still the same
Really, its fu*kin creazy because i cant install any custom rom
It should work, although wiping internal memory is not needed since u flashed latest ftf (which will format internal memory)
Maybe u can try normal factory reset after flashing ftf and then flash this rom zip ?
Btw what model number do u have? E6553?
Can u boot with a modified kernel on stock ROM?I have huge problem. I cant boot this rom, no problem with installing, but when trying to boot, it results in never ending bootloop. Only way to fully boot the rom, is connect powered off phone to charger, any help...?
Try to clean the installation again?The 1207 build is very stable, been using it for 3 days and no issues so far.Hello all.
I' reduce the Ringer volume.
Source mixer_path.xml from lineage-14.1-....-UNOFFICIAL-sumire.zip
Here is FIX AUDIO download. TVRP
https://drive.google.com/open?id=0B5DTiLDUqHi8cTBTZU9wZHZmUEU
You obviously didn't search well enough https://forum.xda-developers.com/showpost.php?p=72710557&postcount=670
Two questions before I flash this:
Are the patches included for Substratum to work?
Does the kernel include SafetyNet patches so that it will pass SafetyNet checks?
https://www.google.com/url?q=[url]h...FjAAegQIBBAB&usg=AOvVaw1DeaZglbLngL5ix_gv4pYg[/url]
You also can use the integrated root manager built into Lineage, just flash the zip below and when u get into dev options, there would be root access options for apps, etcc...
And yes, that's normal when you haven't flashed the addon zip attached
https://forum.xda-developers.com/xperia-z5/orig-development/cm-14-1-lineageos-t3536846/post72751782
colorado48 said:
You also can use the integrated root manager built into Lineage, just flash the zip below and when u get into dev options, there would be root access options for apps, etcc...
And yes, that's normal when you haven't flashed the addon zip attached
Click to expand...
Click to collapse
https://forum.xda-developers.com/attachment.php?attachmentid=4189005&d=1498045807
https://forum.xda-developers.com/xperia-z5/orig-development/cm-14-1-lineageos-t3536846/post72336769
https://forum.xda-developers.com/xperia-z5/orig-development/cm-14-1-lineageos-t3536846/post72339685
https://forum.xda-developers.com/xperia-z5/orig-development/cm-14-1-lineageos-t3536846/post72196980
https://forum.xda-developers.com/xp...pment/cm-14-1-lineageos-t3536846/post72180567[/url]
https://forum.xda-developers.com/xperia-z5/orig-development/cm-14-1-lineageos-t3536846/post71985952
https://forum.xda-developers.com/xperia-z5/orig-development/cm-14-1-lineageos-t3536846/post71991115
https://forum.xda-developers.com/xperia-z5/orig-development/cm-14-1-lineageos-t3536846/post71992481
https://forum.xda-developers.com/xperia-z5/orig-development/cm-14-1-lineageos-t3536846/post71775731
https://forum.xda-developers.com/xperia-z5/orig-development/cm-14-1-lineageos-t3536846/post71585204
https://forum.xda-developers.com/xperia-z5/orig-development/cm-14-1-lineageos-t3536846/post71526368
EDIT : Problem solved just grab any custom ROM and flash it and you ready to go I used slimX
----------------------------------------------------------------------------------------------------------------------
I want to try stock sony nougat downloaded latest .378 but phone is not detected in flashtool I guess I keep getting this error
{
"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"
}
tried both latest Nougat .378 and MM 5.11 same error
Flashtool latest -0.9.23.2
01/039/2017 17:39:33 - INFO - Selected Bundle for Sony Xperia Z5(E6653). FW release : 32.3.A.0.378. Customization : Customized NOBA
01/039/2017 17:39:33 - INFO - Preparing files for flashing
01/042/2017 17:42:54 - INFO - Please connect your device into flashmode.
01/043/2017 17:43:36 - INFO - Device connected in flash mode
01/043/2017 17:43:37 - INFO - Opening device for R/W
01/043/2017 17:43:37 - INFO - Reading device information
01/043/2017 17:43:37 - INFO - Phone ready for flashmode operations.
01/043/2017 17:43:37 - INFO - Opening TA partition 2
01/043/2017 17:43:37 - INFO - Current device : Unknown: Nov 1 2016/03:26:21 - CB5A28A80G - 1295-0610_R5C - 1292-0963_32.2.A.5.11 - GENERIC_32.2.A.5.11
01/043/2017 17:43:37 - INFO - Closing TA partition
01/043/2017 17:43:37 - INFO - Start Flashing
01/043/2017 17:43:37 - INFO - Processing loader.sin
01/043/2017 17:43:38 - INFO - Checking header
01/043/2017 17:43:38 - INFO - Flashing data
01/043/2017 17:43:38 - INFO - Loader : S1_Root_f936 - Version : MSM8994_50 / Boot version : S1_Boot_MSM8994_LA1.2.2_42B / Bootloader status : ROOTED
01/043/2017 17:43:38 - INFO - Max packet size set to 4M
01/043/2017 17:43:38 - INFO - USB buffer size set to 4M
01/043/2017 17:43:45 - INFO - Parsing boot delivery
01/043/2017 17:43:45 - INFO - Ending flash session
01/043/2017 17:43:45 - ERROR - null
01/043/2017 17:43:45 - ERROR - Error flashing. Aborted
01/043/2017 17:43:45 - INFO - Device connected in flash mode
01/043/2017 17:43:46 - INFO - Device disconnected
Click to expand...
Click to collapse
https://forum.xda-developers.com/xperia-z5/orig-development/cm-14-1-lineageos-t3536846/post71239228
https://forum.xda-developers.com/xperia-z5/orig-development/cm-14-1-lineageos-t3536846/post71023276
https://forum.xda-developers.com/xperia-z5/orig-development/cm-14-1-lineageos-t3536846/post70878437
https://forum.xda-developers.com/xperia-z5/orig-development/cm-14-1-lineageos-t3536846/post70827062
https://forum.xda-developers.com/xperia-z5/orig-development/cm-14-1-lineageos-t3536846/post70801442
https://forum.xda-developers.com/xperia-z5/orig-development/cm-14-1-lineageos-t3536846/post70732221
https://forum.xda-developers.com/xperia-z5/orig-development/cm-14-1-lineageos-t3536846/post70721560
https://forum.xda-developers.com/xperia-z5/orig-development/cm-14-1-lineageos-t3536846/post70678193
https://forum.xda-developers.com/xperia-z5/orig-development/cm-14-1-lineageos-t3536846/post70657259
https://forum.xda-developers.com/xperia-z5/orig-development/cm-14-1-lineageos-t3536846/post70616934
https://forum.xda-developers.com/xperia-z5/orig-development/cm-14-1-lineageos-t3536846/post70605394
https://forum.xda-developers.com/xperia-z5/orig-development/cm-14-1-lineageos-t3536846/post70606616
https://forum.xda-developers.com/xperia-z5/orig-development/cm-14-1-lineageos-t3536846/post70602104
https://forum.xda-developers.com/xperia-z5/orig-development/cm-14-1-lineageos-t3536846/post70584410
https://forum.xda-developers.com/xperia-z5/orig-development/cm-14-1-lineageos-t3536846/post70584450
https://forum.xda-developers.com/xperia-z5/orig-development/cm-14-1-lineageos-t3536846/post70584554
https://forum.xda-developers.com/xperia-z5/orig-development/cm-14-1-lineageos-t3536846/post70581633
https://forum.xda-developers.com/xperia-z5/orig-development/cm-14-1-lineageos-t3536846/post70575685
https://forum.xda-developers.com/xperia-z5/orig-development/cm-14-1-lineageos-t3536846/post70526337
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 ****