Related
[RECOVERY] [4/5/16] TWRP 3.0.2-0 - TeamWin Recovery Project
TeamWin is proud to present TWRP 3.0.2-0 for the Samsung Galaxy Tab Pro 8.4/10.1/12.2!
Youtube video: http://www.youtube.com/watch?v=RIvWVS_Rkxo
Full TeamWin credits are on the TWRP page on the TeamWin website: http://teamw.in/project/twrp2
Introduction:
Team Win Recovery Project or twrp2 for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's 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 feel.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Decryption of /data
Easy selection of internal/external storage
See changelog below for new features
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe cache & dalvik, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Source Code:
GitHub - https://github.com/omnirom/android_bootable_recovery
Gerrit for TWRP Official Device Configs - http://gerrit.twrp.me
Gerrit Instance - http://gerrit.omnirom.org
If you have made your own twrp build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
mondrianwifiue Device Config: TBD
Kernel: TBD
DOWNLOAD:
All official devices are listed at the top of the page on the Team Win website. Search for the device in the textbox.
http://twrp.me
Support:
Click http://webchat.freenode.net/?channels=twrp for live support or join us in #twrp on Freenode IRC servers
Changelog
3.0.2-0
- 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-0
-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
TWRP 3.0.0-2
Add F2FS back to samsung kernel
TWRP 3.0.0-1
Fixed MTP
TWRP 3.0.0-0
What’s new in 3.0.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
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 udpated 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!
You can track the progress of builds here
Head over to the devices page to find install instructions and download links.
TWRP 3.0.0-0 is out now for all currently supported devices.
What’s new in 3.0.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
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 udpated 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!
You can track the progress of builds here
Head over to the devices page to find install instructions and download links.
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)
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.
2.8.6.1
v2wifixx-
Use new kernel for booting properly on v2wifxx device
mondrianwifiue -
add f2fs to TWRP
mondrianlte -
add f2fs to TWRP
vienaltexx -
Fix brightness path
2.8.6.0
- Allow mulitple overlays for popup boxes (Dees_Troy)
- Add pattern style password entry for decrypt (Tassadar)
- Keyboard improvements (_that)
- Update AOSP base to 5.1 (Dees_Troy)
- Reduce theme count to 5 and rely on scaling (Dees_Troy)
- Various scaling improvements (Dees_Troy)
- Improved handling of resources in the GUI (_that)
- Make scroll bar size proportional to list size (_that)
- Allow scoll lists to render without a header (_that)
- Make console scroll per pixel with kinetic scrolling (_that)
- Support styles in XML to reduce XML size and improve consistentcy (Dees_Troy)
- Various other fixes and improvements (mdmower, bigbiff, codelover, etc)
2.8.5.0
- Scale the GUI - TWRP can read the theme's resolution and scale it up or down to fit the theme to your screen's resolution
- Improve thread handling and move input handling into the main rendering thread to improve stability
- Make MTP work even if unplugged and plugged back in
- Unify scrollable list code and make kinetic scrolling feel more natural
- Fix handling of mapped zip files for OTA updates (CM12 updater)
- USB keyboards should now work on all devices that support USB host mode via a USB OTG cable
- Add Cancel Backup capability
- Other small fixes and improvements
2.8.4.0
- MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
- Add flashing of boot and recovery images via the TWRP GUI (Find the Images button on the Install page)
- Fix some MTP related crashes and bugs
- Eliminate TWRP toggling USB IDs during boot if MTP is enabled
- Fix various adb sideload issues
- Improve threading of actions
- Eliminate separate thread for screen timeout
- Update libblkid to 2.25.0
- Use power button as back button on watch themes for easier navigation
- Add mutex locking to data manager
- Improve custom theme handling on encrypted devices
- Allow the stock theme to be offset by build flags so we can center a lower res theme on a higher res screen especially for watches with round screens
2.8.3.0
- MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
- MTP will now tell the host PC that storage is removed instead of disabling MTP completely
- MTP will now report the correct max file size based on the file system in use to the host PC (may fix transfer of large files)
- Update and improve fix permissions and make fixing contexts optional
- Update SuperSU in TWRP to 2.40 and update install process
- Make TWRP work properly on AArch64 (Nexus 9 is now built in true 64-bit binaries and libraries)
- Attempt to set correct permissions and contexts on all files placed in storage so backups will show in Android
- Fix kernel panic during MTP start on some devices
- Support unicode fonts on devices with True Type Font support
- Fix slider value not showing sometimes (vibration settings page)
- Toggle MTP off during adb sideload to set correct USB IDs
- Reduce library requirements for 5.0 L decrypt
- Other minor fixes and improvements
2.8.1.2
picassowifi
- fix build
2.8.1.1
mondrian3g
- Revert changes to exfat-fuse to fix writing to external sdcard as exfat
mondrianwifiue - 12/9/2014
- Revert changes to exfat-fuse to fix writing to external sdcard as exfat
picassowifi
- add encryption support
2.8.1.0
- MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
- TrueType Font support - optional as it takes up a decent amount of space so may not be available on all devices - thanks to Tassadar
- Temperature support - thanks to bigbiff
- Various other bugfixes and tweaks
2.8.0.1
mondrianwifiue only
- Disable Secure Erase to increase wiping speed
2.8.0.0
- Add MTP support to recovery thanks mostly to bigbiff with a little help from Dees_Troy
- Add command line capabilities - you can now execute various TWRP features via adb instead of the touchscreen
- Add support for color in the console and give error, warning, and highlight lines different colors
- Track backup and restore progress based on file sizes to provide a much more accurate indication of progress
- Improve handling of /misc thanks to mdmower
- Improve setting of time on Qualcomm devices thanks to [NUT]
- Allow using images on slidervalue GUI objects thanks to Tassadar
- Allow using variables and addition and subtraction in variables for easier theming
- Add support for 1440x2560, 280x280, and 320x320 resolutions and update 240x240
- Allow ui.xml file to include additional xml files to help break up the theme and make TWRP easier to maintain
- Other minor fixes and improvements
2.7.1.1
v2wifixx only
- fix contexts restore of backups
2.7.1.0
- Add GUI option to change or repair file systems on individual partitions. The change is destructive so backup your data including internal sdcard first. This option should make it a little easier to migrate a device from ext4 -> f2fs, for instance. If a developer has added f2fs support for your device and we don't have it in TWRP, please contact me via PM to arrange for it to be added.
- Various bugfixes to backup and restore
- Improvements to USB storage handling
- Added a class to search for files to make finding the correct brightness file automatic in most cases
- Various other bugfixes and tweaks
2.7.0.1
picassowifi
Fix ramdisk for booting
2.7.0.1
mondrianwifiue and mondrianwifilte
Add Qcom time fix
2.7.0.1
Galaxy Tab Pro 8.4:
Update theme thanks to nrage123 and Gunthermic to proper 1600x2560 (will submit to gerrit)
Update system splitting to fix issues with symlinks being counted as the target
Update size to not show /data/media for /data parition
2.7.0.0:
-Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
-Allow sideloading from /tmp on encrypted devices
-Check for a crypto footer before asking for a password to prevent user confusion
-Additional checks for validity to auto generated backup names
-Text wrap in the console output
-Proper caps lock support in the keyboard
-Mouse support via USB OTG for devices with a broken digitizer
-Improve scanning of storage locations for OpenRecoveryScript
-Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions thanks to Samer Diab
-Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
-Update SuperSU to 1.93 and improve installation process
-Added selinux contexts restoration to fix permissions
-Load RTC offset on Qualcomm devices to fix the date/time in recovery
-USB Mass Storage fixes Add SELinux support checking
-Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
-Add 4.4 decrypt support
-Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
-Various SELinux fixes and bug fixes
Note: 2.7 marks the first time that we are dropping support for older devices. We are doing this because of the SELinux support needed to install 4.4 Kit Kat ROMs. The non-TWRP parts of the recovery image have to be built in at least a 4.1 tree and the kernel that is included in the recovery image has to support writing SELinux contexts. We don't own most of the devices that we support so we depend on outside testers and developers to help us update devices. In many cases we can't find someone readily. Come to #twrp on Freenode if you want to help bring your device up to date. You can tell right away if your device will support 4.4 ROMs in 2.7. Boot TWRP and press the console button (the square-ish button either in the bottom middle or upper right) to view the console output. If it doesn't say "Full SELinux support" in the console, then your device still needs some work. Help us help you.
bigbiff said:
reserved
Click to expand...
Click to collapse
reserved
this is so awesome. finally. can we flash with flashily or is there a way without a computer. I'm not near one. stock recovery doesn't seem to flash zips. been awhile since i did it without a computer. donate will be sent. did i say how awesome this is lol. forget it. flashed the img file with flashify. works perfect. screen isn't full size but i think i read that you were aware of that. thanks again.
You might want to have the site admins fix the typo if you can: "Samsung Galaxy Tab Pro 8.1" should say 8.4. Kind of confused me at first.
The Theme is from a device that is 1200 x 1980. Ours is 1600 x 2560. I got a theme almost done but ran into issues I could not fix. The themes are pretty complicated for a xml noob like me. Bigbiff does not have the time to make one which I can tell you takes a lot of work. Hopefully someone with some xml talent will take up the cause. I asked a couple of TWRP themers from other devices but they are all busy with other things. Also this is the only device thus far with this portrait resolution. I tried to flash the zip file but that failed. The Odin method works perfectly.
nrage23 said:
The Theme is from a device that is 1200 x 1980. Ours is 1600 x 2560. I got a theme almost done but ran into issues I could not fix. The themes are pretty complicated for a xml noob like me. Bigbiff does not have the time to make one which I can tell you takes a lot of work. Hopefully someone with some xml talent will take up the cause. I asked a couple of TWRP themers from other devices but they are all busy with other things. Also this is the only device thus far with this portrait resolution. I tried to flash the zip file but that failed. The Odin method works perfectly.
Click to expand...
Click to collapse
Thanks for posting, saves me from posting it.
I am unable to do the theme because I don't have any devices with a higher resolution then 1080p. We mostly need the keyboard xml layout done so that the keyboard object knows the pixels to look at when a key on the image being rendered is pressed. Please PM me if you would like to help.
nrage23: did you flash 2.7 odin img and it worked, but the zip didn't?
bigbiff said:
Thanks for posting, saves me from posting it.
I am unable to do the theme because I don't have any devices with a higher resolution then 1080p. We mostly need the keyboard xml layout done so that the keyboard object knows the pixels to look at when a key on the image being rendered is pressed. Please PM me if you would like to help.
nrage23: did you flash 2.7 odin img and it worked, but the zip didn't?
Click to expand...
Click to collapse
I tried flashing the zip in the 2.6 build you had done and it said failed after trying to flash. So I booted to DL mode and Odin version worked just fine.
nrage23 said:
I tried flashing the zip in the 2.6 build you had done and it said failed after trying to flash. So I booted to DL mode and Odin version worked just fine.
Click to expand...
Click to collapse
Can you try the 2.7 files? If anyone has issues please use http://techerrata.com/bigbiff/mondrianwifue-recovery.img.tar
bigbiff said:
Can you try the 2.7 files? If anyone has issues please use http://techerrata.com/bigbiff/mondrianwifue-recovery.img.tar
Click to expand...
Click to collapse
Sorry it was the 2.7 .zip file I flashed via recovery that did not work and then I used Odin to get 2.7 .tar to work properly.
nrage23 said:
Sorry it was the 2.7 .zip file I flashed via recovery that did not work and then I used Odin to get 2.7 .tar to work properly.
Click to expand...
Click to collapse
I need to create an zip file for it tonight.
<deleted don't want borks on non 8.4 gtabpro> Also can you guys get me build.prop for the 10.1/12.2?
Thanks!
bigbiff said:
If you guys are willing you should be able to boot this on the other Galaxy tab pros. Also can you guys get me build.prop for the 10.1/12.2?
Thanks!
Click to expand...
Click to collapse
The others are all Exynos 5 based like the Note 10.1 2014 you made. The 8.4 is Qualcomm.
bigbiff said:
If you guys are willing you should be able to boot this on the other Galaxy tab pros. Also can you guys get me build.prop for the 10.1/12.2?
Thanks!
Click to expand...
Click to collapse
Build.prop from my rooted 10.1 is attached.
Not sure if I have the nerve to be the first to Odin the 8.4 recovery onto my 10.1.
smalis said:
Build.prop from my rooted 10.1 is attached.
Not sure if I have the nerve to be the first to Odin the 8.4 recovery onto my 10.1.
Click to expand...
Click to collapse
Do not do so. It is very different hardware.
crpalmer said:
Do not do so. It is very different hardware.
Click to expand...
Click to collapse
Thanks very much, I will wait.
nrage23 said:
The others are all Exynos 5 based like the Note 10.1 2014 you made. The 8.4 is Qualcomm.
Click to expand...
Click to collapse
Bah guess I should of looked Edited post above about trying to boot. I will download the exynos kernel and rebuild for 12.2 and 10.1.
bigbiff said:
Can you try the 2.7 files? If anyone has issues please use http://techerrata.com/bigbiff/mondrianwifue-recovery.img.tar
Click to expand...
Click to collapse
Okay that link I flash gives me 2.6.3.2.
I have tried flashing the one from TWRP site and it doesnt' flash it.
Might I make a small suggestion to in OP write instructions to flash/odin it..
Gunthermic said:
Okay that link I flash gives me 2.6.3.2.
I have tried flashing the one from TWRP site and it doesnt' flash it.
Might I make a small suggestion to in OP write instructions to flash/odin it..
Click to expand...
Click to collapse
We have flashing instructions for each device on the website. Which file did you flash that didn't work. The zip is broken, but people here say the tar works.
bigbiff said:
We have flashing instructions for each device on the website. Which file did you flash that didn't work. The zip is broken, but people here say the tar works.
Click to expand...
Click to collapse
odin openrecovery-twrp-2.7.0.0-mondrianwifiue.img.tar
Edit: After odin'ing 2.6.3 and doing 2.7 again it now shows.
1. Why does it only take 3/4 of screen?
2. What does the tab report that (in first screen) the recovery is not selinux enforcing?
UPDATE: I am no longer maintaining TWRP for devices that I do not possess. I am also no longer posting on XDA.
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 feel.
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 bootloader
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.2.1-0:
Code:
[LIST]Initial official release[/LIST]
Older Device-specific versions:
Code:
[LIST]N/A[/LIST]
Click to expand...
Click to collapse
TWRP Official Changelog
Current version: 3.2.1:
Code:
[LIST]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)[/LIST]
Older versions:
Code:
[SIZE="4"][COLOR="Green"]3.2.0:[/COLOR][/SIZE]
[LIST]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[/LIST]
[SIZE="4"][COLOR="Green"]3.1.1:[/COLOR][/SIZE]
[LIST]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)[/LIST]
[SIZE="4"][COLOR="Green"]3.1.0:[/COLOR][/SIZE]
[LIST]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 [URL="https://github.com/omnirom/android_bootable_recovery/commit/ce8f83c48d200106ff61ad530c863b15c16949d9"]here[/URL] (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[/LIST]
[SIZE="4"][COLOR="Green"]3.0.3:[/COLOR][/SIZE]
[LIST]Partial release to help support the release of the [URL="https://www.xda-developers.com/team-win-releases-their-first-official-twrp-app-in-the-play-store/"]Official TWRP app[/URL][/LIST]
[SIZE="4"][COLOR="Green"]3.0.2:[/COLOR][/SIZE]
[LIST]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.[/LIST]
[SIZE="4"][COLOR="Green"]3.0.1:[/COLOR][/SIZE]
[LIST]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[/LIST]
[SIZE="4"][COLOR="Green"]3.0.0:[/COLOR][/SIZE]
[LIST]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[/LIST]
[U]Additional Notes[/U]
[LIST]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![/LIST]
[SIZE="4"][COLOR="Green"]2.8.7.0:[/COLOR][/SIZE]
[LIST]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)[/LIST]
[U]Additional Notes[/U]
[LIST]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 [url]https://jenkins.twrp.me[/url] and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at [url]https://gerrit.twrp.me[/url] to help us keep devices up to date and working.[/LIST]
Click to expand...
Click to collapse
Downloads
Download
Latest Official versions
Sources
Device tree
Kernel source
Click to expand...
Click to collapse
Known Issues
None
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, or find us in our IRC channel below. 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
Additional Help/Support:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Click to expand...
Click to collapse
XDA:DevDB Information
TeamWin Recovery Project (TWRP), Tool/Utility for the HTC One E8
Contributors
Captain_Throwback, Dees_Troy, bigbiff, _that
Source Code: https://github.com/omnirom/android_bootable_recovery
Version Information
Status: Stable
Current Stable Version: 3.2.1-0
Stable Release Date: 2017-12-09
Created 2015-03-20
Last Updated 2018-08-14
Device-Specific Information
Reserved for FAQ (if needed)
Thumbs up, Cap!
Thanks for the official release.
If you have some spare time, could you consider material design ?
Sent from my HTC One_E8 dual sim using Tapatalk
DutchDanny said:
Thanks for the official release.
If you have some spare time, could you consider material design ?
Sent from my HTC One_E8 dual sim using Tapatalk
Click to expand...
Click to collapse
Use the Materialised theme.
When the stock theme is overhauled (expected with TWRP v3.0), I believe it will include some Material design elements.
@Captain_Throwback
I just flashed twrp 2.8.5.0 it's working great thanks.
I always had one problem which is when I press any button in the reboot menu there is a 5 second delay before it reboots.
All the previous versions had the same problem.
Is this permanent or can you fix it in future releases.
And the playstore twrp app doesn't have E8 on its menu, not even a single variant.
Can you please look into that too.
Thanks in advance.
iamsuperuser said:
@Captain_Throwback
I just flashed twrp 2.8.5.0 it's working great thanks.
I always had one problem which is when I press any button in the reboot menu there is a 5 second delay before it reboots.
All the previous versions had the same problem.
Is this permanent or can you fix it in future releases.
And the playstore twrp app doesn't have E8 on its menu, not even a single variant.
Can you please look into that too.
Thanks in advance.
Click to expand...
Click to collapse
The reboot "delay" is normal.
And there is no official TWRP app on the Play Store.
2.8.6.0 has been uploaded.
Captain_Throwback said:
2.8.6.0 has been uploaded.
Click to expand...
Click to collapse
after updating TWRP to 2.8.6.0, swipe to install function is not working.
anybody else experiencing the same?
EDIT: was using an old theme, after removing the theme, it's working fine now
ghost_razr said:
after updating TWRP to 2.8.6.0, swipe to install function is not working.
anybody else experiencing the same?
Click to expand...
Click to collapse
Update your theme, or remove it.
hi
any chance you can compile twrp for E9 plus?
-=knop=- said:
hi
any chance you can compile twrp for E9 plus?
Click to expand...
Click to collapse
I don't have it, so no.
does this work for m8sw variant? (dual sim - china unicom) ?
UPDATE: I tried it... works great! Thanks
2.8.7.0 is uploaded.
NOTE: If you have already updated to Lollipop, then it's possible the latest version will not work on your device. If you determine that this is the case, let me know - I can upload a beta M8 version that should work on the E8.
Captain_Throwback said:
2.8.7.0 is uploaded.
NOTE: If you have already updated to Lollipop, then it's possible the latest version will not work on your device. If you determine that this is the case, let me know - I can upload a beta M8 version that should work on the E8.
Click to expand...
Click to collapse
TWRP 2.8.7.0 has my sd write-protected
tried it with 2 SD cards is effective immediately back on ... and this write protection can be removed by anything neither format or the like can you please fix
snoopyhaeckers said:
TWRP 2.8.7.0 has my sd write-protected
tried it with 2 SD cards is effective immediately back on ... and this write protection can be removed by anything neither format or the like can you please fix
Click to expand...
Click to collapse
I think you may be confused by the system read-only prompt. Did you read the change log in the OP? Recovery can't write-protect your device. No kernel changes were made for this device, so it can't be anything the recovery did.
did it with two different SD cards once I tasted from the sd a zip as supersu 2:46 install this after read-only , 2.8.6.0 no problem working again wonderful, and the system is stock only Xposed framework and super su installed 'm back aud 2.8 . 6.0 thus, the problem for me is first solved .
snoopyhaeckers said:
did it with two different SD cards once I tasted from the sd a zip as supersu 2:46 install this after read-only , 2.8.6.0 no problem working again wonderful, and the system is stock only Xposed framework and super su installed 'm back aud 2.8 . 6.0 thus, the problem for me is first solved .
Click to expand...
Click to collapse
Just disable the read-only option. I don't really understand your issue (language barrier?). If the previous version works fine for you, feel free to continue using it.
Hi, could u make a recovery with f2fs supported for E8? Thank u very much....
schqiushui said:
Hi, could u make a recovery with f2fs supported for E8? Thank u very much....
Click to expand...
Click to collapse
Are there any ROMs that support it? Otherwise it serves no useful purpose.
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
TWRP 3.5.1 ReleasedMar 17, 2021
TWRP 3.5.1 is out now for most currently supported devices.
TeamWin has prepared a mini release before Android-11 support. The following features listed are common to both android-9.0 android-10.0 supported devices. Many thanks to all the listed contributors.
You can see the device builds under their respective Jenkins view at https://jenkins.twrp.me.
What's new in 3.5.1:
Android 9 Branch:
Fixes
Build compilation in 7.1 tree - CaptainThrowback
SAR: Don't follow symbolic links for block devices - bigbiff
SAR Update script name for clarity - CaptainThrowback
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
Link Download For All Galaxy J6
https://drive.google.com/file/d/1-4JbOg4w2PgPJDWeajAQvNV4eh2FKIoH/view?usp=drivesdk
Hi!
Can this tar file be flashed through odin?
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 ****