[Recovery] TWRP 3.3.1-K1
- Thread starter Kutep0v
- Start date
@JJohnson1988 is right.
Were changed string MD5 everywhere to use digest or Digest instead. SHA2 is default and better for digest creation due to decreased collision space compared to MD5 and SHA1. See https://en.m.wikipedia.org/wiki/SHA-2.
Testing is over. Thank you!
Last edited:
Hello! I need help with testing. If someone really wants to help, click on the LINK. Details on the same link.
Testing is over. Thank you! If you have something to say, do it right now using the link above.
So those changes will be included in next release?
Yes, and also something else.
I did not receive any error reports. Еverything is fine... at least I want to believe in it. I've been using test recovery for a week and haven't found any problems.
david72262
Senior Member
Nothing more, just the latest changes from the TWRP repository. I always try to update having at least one feature from me, so this feature will be is LED Manager.Hmm,something else,I'm all ears.
I doubt that K4 will be released in the near future. There were no changes in the TWRP repository, and I don't want to release an "empty" update. But who knows, maybe something will change during this time. Honestly, now I have no more ideas how to further develop my recovery.
Hi. I think this is a bad idea. You can't use TWRP with a half broken touchscreen. Of course, you can control with the mouse via USB-OTG, but it's very inconvenient. CWM is the right solution in your case, since you can use the volume buttons to navigate.
Tq for the answer. It kinda ok to be able to use mouse via usb-otg but yes not very inconvenient if emengencyHi. I think this is a bad idea. You can't use TWRP with a half broken touchscreen. Of course, you can control with the mouse via USB-OTG, but it's very inconvenient. CWM is the right solution in your case, since you can use the volume buttons to navigate.
Any logs? On which TWRP was the backup done? Backups are incompatible with other TWRPs and vice versa.
This happens not only on our device and specifically this TWRP. There is no information. It's known that a bit more often happens with 7.1 ROM, and only the fact that TWRP can't open addon.d, because it's not a directory (??!) while backup. Earlier saw on OnePlus 3, that addon.d directory, for unknown reasons, became a bold file. It will help reinstall the ROM and create new backups.
Last edited:
TWRP 3.2.0-K1
- 3.2.0 version
- LED Manager
- NTFS support for USB-OTG
- Fix compile error with IGNORE_MISC_WIPE_DATA in some trees
- Fix more compile errors in bootloader_message_twrp
- Better compatibility across 8.0.0 trees
- minui: Fix building graphics_overlay.cpp
- minui: Move graphics_overlay.h down that we have all structs defined
- minui: Add missing <linux/ion.h> for 'struct ion_handle_data'
- minui: Only include graphics_adf.h if we do not build with MSM_BSP
- minui: Do not overwrite previously set CFLAGS
- Fix build error in old 5.0 tree
- ADB Backup: fix compilation error for remove
- vold_decrypt: FDE Keymaster 3.0 support
- FBE for Pixel 2
- Fix issues building with LineageOS cryptfs_hw
- Support v2 fstab format
- ADB Backup: Fix gzip backup and restore
- ADB Backup: add ability for TWRP GUI to restore
- Improve greek translation
- Improve automatic detection of QCOM RTC fix
- Fix compile error in bootloader_message_twrp on 6.0 tree
- Auto detect possible use of legacy props
- Fix mkfs.f2fs build error
- Fix 'No OS' on System_Image restore after wipe
- Fix a few build errors
- Add libraries needed in 8.0 for e2fsck and tune2fs
- Make legacy props an option disabled by default
- Update to AOSP 8.0 base
- DO NOT MERGE Android 8.0 stuff
- Remove duplicate entries & Improve Chinese translation
Great work my friend. Restoring and backing up roms requires 1/3 of time taken by official twrp. Awesome work. Using it since 3.1.1 k1 version.
Similar threads
- Locked
- Locked
Top Liked Posts
-
There are no posts matching your filters.
-
131
Features
- Increased backup/restore speed. Restore is three times faster than on other TWRPs.
- Improved EFS and Firmware backup. Backups are incompatible with other TWRPs and vice versa.
- Improved AROMA hack. Almost all (or all?) AROMA archives should work fine.
- LED Manager. Monitor the battery level and charging state.
Source code
XDA:DevDB Information
TWRP 3.3.1-K1, Tool/Utility for the OnePlus One
Contributors
Kutep0v
Version Information
Status: Stable
Current Stable Version: 3.3.1-K1
Stable Release Date: 2018-06-01
Created 2017-04-11
Last Updated 2019-06-0155TWRP 3.2.3-K1
- Fixed userdata decryption on Pie (thanks to Ketut P. Kumajaya)
- Added ability to backup Recovery and Persist partitions
- Added Busybox 1.29.3 binary. This should solve the problems with busybox-binded scripts.
- Don't skip decryption when installing mapped zips. This should solve the problems with some addon.d scripts.
---------- git log ---------- - Hide navbar while running operations
- minuitwrp: Remove unused variables
- Fixed: undefined ANDROID_ROOT is an error.
- recovery: Get a proper shell environment when using toybox
- toybox: create getprop symlink on SDK 27
- Fix Check_Lifetime_Writes on AB devices
- twrp: Fix unsigned compare compile warning.
- minuitwrp: Support haptics drivers registered with LED class framework
- minuitwrp: Respect TARGET_RECOVERY_PIXEL_FORMAT config.
- vold_decrypt: use ANDROID_ROOT for additional compatibility
- Add option to use ro.serialno for generating device id
- Fix sha2 generation persistence.
- twrp: use ANDROID_ROOT environment variable
- vold_decrypt: Actually depend on init.recovery.vold_decrypt.rc
- vold_decrypt: Add in recovery vold and vdc
- partition: Update f2fs format code
- Fix the long broken format function
- Allow excluding file-based encryption from the TWRP build
- Make adb use a custom prop for adb root
- Add tool to dump a crypto footer on FDE devices
- TWRP: add an option to exclude the TWRP app
- uncrypt: fix f2fs ioctl argument for pin_file
- f2fs: support f2fs by setting unmovable bit for package file
- install: mkfs.f2fs: specify sector size for target image size
- add sload.f2fs for recovery format
- recovery: format f2fs with encrypt/quota
- libcryptfslollipop: set key_size before use
- Use Oreo unzip provided by system/core/libziparchive
- prebuilt: resolve libext2_misc.so dependency for mke2fs
- recovery: updater: Fix SymlinkFn args
- Add more specific error codes for uncrypt failures
- updater: Allow devices to suppress BLKDISCARD
- Don't copy local mke2fs.conf for O-MR1
- Remove duplicate ext4 flags from Android.mk
- Set a dummy CM_PLATFORM_SDK_VERSION if it doesn't exist
- Remove leftover mounts.h~HEAD
- Remove remaining pieces of supersu
- enable md5sum digest verification
- Fix installing OTAs without decrypting
- Fix ld.config.txt errors on Android 8.1 system root devices
- language: italian: Fix SELinux support label
- Remove SuperSU
- toolbox: prevent executing tools
- Cleanup TWRP flags
- Revert "minuitwrp: drm: wait for last page flip to complete"
- Revert "updater: Remove some obsoleted functions for file-based OTA."
- Revert "kill package_extract_dir"
- Enable arm64 neon scrypt implementation
- ADB Backup: fix md5 check on restore. Add debug capability. Fix backup of images after tarred partitions with too much padding Add more md5 logging. Skip digest check if selected. Change ADB Backup version to 3 for new fixes to image padding.
- partitionmanager: signal when Mount_To_Decrypt partitions are mounted
- TWRP: vold_crypto: Allow custom strace path
- vold_decrypt: Code cleanup
- TWRP: Added TW_CLOCK_OFFSET flag to further adjust the clock.
- TWRP: Move the valid current time up to trigger fix on more devices. For example on my device, the LG V20 (US996), the default time comes back as 2016 which doesn't trigger the fixup code. The actual time I picked was pretty arbitrary, but close to the current date, since we're checking if said date/time is reasonably accurate without the fixup code.
- Skip decryption when installing mapped zips
- minuitwrp: drm: wait for last page flip to complete
- minuitwrp: use a separate draw buffer for DRM as well
- minuitwrp: drm: fix RECOVERY_BGRA pixel format
- Merge "external/scrypt: use proper nativehelper headers" into android-8.1
- Merge "scrypt doesn't need <machine/cpu-features.h>." into android-8.1
- Merge "scrypt: Don't hardcode gtest path." into android-8.1
- Merge "otafault/tests: Replace pathmap with commands_recovery_local_path" into android-8.1
- Merge "applypatch: Fix bad AOSP merge" into android-8.1
- Merge "applypatch: Remove obsolete pathmap changes" into android-8.1
- Revert "Remove the obsolete package_extract_dir() test"
- toybox: microcom is not present in the lineage 14.1 source.
- external/scrypt: use proper nativehelper headers
- scrypt doesn't need <machine/cpu-features.h>.
- scrypt: Don't hardcode gtest path.
- otafault/tests: Replace pathmap with commands_recovery_local_path
- applypatch: Fix bad AOSP merge
- applypatch: Remove obsolete pathmap changes
- toybox: Fix build for android 8.1
- Merge "GitHub: Add issue and pull request templates" into android-8.1
- Merge "ext4crypt: keymaster: fix missing include" into android-8.1
- Language: Add version info to copying_log in turkish lang.
- Update Turkish translations.
I did a short test, everything is working fine, well, as far as possible on an ancient phone that barely holds encryption. Hope there is no critical errors.
P.S. Now I want to talk about the future of this project.
You probably noticed that I often disappear for a long time. There is a reason for this. My circle of interests is constantly changing. Today I can be engaged in Android development, and tomorrow something completely different. And this "tomorrow" came, quite a while ago. I'm not interested in these Android related stuff. I just use the phone, no more flashing ROMs, kernels, mods and even security updates. As I said, the update will be released at the weekend, and I did it. I don't know what's next. It's difficult to do what not interests me and what I don't use. Perhaps this is the latest update, but I want to believe that it's not. I'm surprised that there are so many "flashaholics" left. Thank you for being with me all this time.44TWRP 3.2.0-K1
- 3.2.0 version
- LED Manager
- NTFS support for USB-OTG
- Fix compile error with IGNORE_MISC_WIPE_DATA in some trees
- Fix more compile errors in bootloader_message_twrp
- Better compatibility across 8.0.0 trees
- minui: Fix building graphics_overlay.cpp
- minui: Move graphics_overlay.h down that we have all structs defined
- minui: Add missing <linux/ion.h> for 'struct ion_handle_data'
- minui: Only include graphics_adf.h if we do not build with MSM_BSP
- minui: Do not overwrite previously set CFLAGS
- Fix build error in old 5.0 tree
- ADB Backup: fix compilation error for remove
- vold_decrypt: FDE Keymaster 3.0 support
- FBE for Pixel 2
- Fix issues building with LineageOS cryptfs_hw
- Support v2 fstab format
- ADB Backup: Fix gzip backup and restore
- ADB Backup: add ability for TWRP GUI to restore
- Improve greek translation
- Improve automatic detection of QCOM RTC fix
- Fix compile error in bootloader_message_twrp on 6.0 tree
- Auto detect possible use of legacy props
- Fix mkfs.f2fs build error
- Fix 'No OS' on System_Image restore after wipe
- Fix a few build errors
- Add libraries needed in 8.0 for e2fsck and tune2fs
- Make legacy props an option disabled by default
- Update to AOSP 8.0 base
- DO NOT MERGE Android 8.0 stuff
- Remove duplicate entries & Improve Chinese translation
41Frequently asked questions
Q: Why backups are incompatible with other TWRPs and vice versa?
A: Some components have been improved or simply is not supported in other versions.
- EFS backup is not supported in the official version. Other unofficial versions don't backup one important partition, which is also part of the EFS.
- Firmware backup is not supported in the official version. Other unofficial versions uses an unreliable method of modem partition backup.
- System Image is not supported in the official and other unofficial versions.
Q: What is the difference between System and System Image backup?
A: Different backup methods.
- System – files method. Create usual archive by packing all files from a system partition. Not available since version 3.2.1-K2.
- System Image – dd method. Create exact partition dump by reading every single block from a system partition.
Q: Charging LED broken in this recovery too?
A: No, it works. Since 3.2.0-K1 release included LED Manager. Logic:
- If the battery status is "Charging", then:
— If the battery capacity is "Low" (1-14), then turn on the red LED.
— If the battery capacity is "Mid" (15-89), then turn on the yellow LED.
— If the battery capacity is "High" (90-100), then turn on the green LED. - If the battery status is "Discharging", then:
— If the battery capacity is "Low", then blink the red LED.
— If none of the cases is true, then turn off LED. - If the battery status is "Full", then turn on the green LED.
- If none of the cases is true, then turn off LED.
36TWRP 3.1.1-K3
- Backup and restore a little bit faster
- Charge LED (request)
- More debuggable
- Fix typos/inconsistencies in German language
- Show scrollbar on TWRP Settings
- SHA2: Enable in landscape and watch xml
- twrpTar: Fix uninitialized current_archive_type
