Database Develop

CM13 Encryption and TWRP

In years past on the Nexus 5, I've been able to encrypt my phone and still flash nightlies with TWRP, it would just prompt me for my lockscreen password. When I first got my Victara, there were issues with it, so I just no longer bothered encrypting my phone.
I'd like to start encrypting my phone again with my new job, before I blow my phone up has anyone been successful encrypting with CM13 and TWRP 2.8.7.1 (latest)?

With CM13, TWRP v2.8.7.1 and my Moto X 2014 (XT1096), when my phone was encrypted, upon entering recovery, it would ask me for a password. Unfortunately, no matter what I entered, it wouldn't accept it. I went back to no encryption until TWRP works with it.
If you need encryption, there is a work-around. I copied the build to /cache (vice /sdcard) and was able to upgrade fine with each nightly.

newtoncd said:
If you need encryption, there is a work-around. I copied the build to /cache (vice /sdcard) and was able to upgrade fine with each nightly.
Click to expand...
Click to collapse
Once the update is downloaded to the /cache dir, how exactly do you accomplish the update? Do you follow the typical update method (https://goo.gl/mC6kaN), just doing so with the cache dir?

cableghost said:
Once the update is downloaded to the /cache dir, how exactly do you accomplish the update? Do you follow the typical update method (https://goo.gl/mC6kaN), just doing so with the cache dir?
Click to expand...
Click to collapse
From that URL (section 5 under updating manually), whenever you see /sdcard, just point TWRP recovery to /cache.
Even with encryption turned on, TWRP can see the /cache directory just fine.

newtoncd said:
From that URL (section 5 under updating manually), whenever you see /sdcard, just point TWRP recovery to /cache.
Even with encryption turned on, TWRP can see the /cache directory just fine.
Click to expand...
Click to collapse
Thanks; I'll give it a try.

I was able to encrypt/decrypt CM13 with TWRP 2.8.7.5, but couldn't get it to decrypt after updating to 3.0. Having trouble tracking down a link for 2.8.7.5, but I must have gotten it from somewhere around here.

fsad said:
I was able to encrypt/decrypt CM13 with TWRP 2.8.7.5, but couldn't get it to decrypt after updating to 3.0. Having trouble tracking down a link for 2.8.7.5, but I must have gotten it from somewhere around here.
Click to expand...
Click to collapse
Interesting. I heard from the TWRP Dev directly saying that decrypting was not possible because they did not have a moto x 2014 to work on and create specific code for it.
As long as I can update, that should be okay. I haven't tried the loading update into cache yet, though.
MotoX2014, via TapaTalk

[RECOVERY][T713] TWRP 3.3.0-0 Touch Recovery [OFFICIAL]

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.
DOWNLOAD: https://dl.twrp.me/gts28vewifi
BUGS:
If you have found a bug, please consider posting it to our github issues log and then I'll report to Dess_Troy. If you have a significant problem that cannot be answered in this thread, your best bet is to PM Dees_Troy directly, 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!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
XDA:DevDB Information
[RECOVERY][T713] TWRP 3.3.0-0 Touch Recovery [OFFICIAL], ROM for the Samsung Galaxy Tab S2
Contributors
LuK1337, luca020400, Olivier
Source Code: https://github.com/TeamWin
ROM OS Version: 2.3.x Gingerbread
Version Information
Status: Testing
Created 2017-01-27
Last Updated 2019-04-15

-snip-

LuK1337 said:
-snip-
Click to expand...
Click to collapse
Thanks. It's great to have a proper version of TWRP.

No love for 2015 versions on TWRP site

it works with T719, so thank you

deleted

It also works with the T813. Great to have a real recovery on this device.

Ever since TWRP 3.1.0-0 twrp can no longer read my encrypted data partition probably due to commit f628cbfc5e77a3a358c95ef7f1e47bbb1505b9d0 on the TeamWin github for the gts28vewifi (I can't post the direct link because my account is too new).
Is there any reason the encryption blobs were swapped out and how would I go about getting twrp to read my encrypted data partition again. I've already tried wiping everything, reflashing and reencrypting but it didn't help.

radiocarbon said:
Ever since TWRP 3.1.0-0 twrp can no longer read my encrypted data partition probably due to commit f628cbfc5e77a3a358c95ef7f1e47bbb1505b9d0 on the TeamWin github for the gts28vewifi (I can't post the direct link because my account is too new).
Is there any reason the encryption blobs were swapped out and how would I go about getting twrp to read my encrypted data partition again. I've already tried wiping everything, reflashing and reencrypting but it didn't help.
Click to expand...
Click to collapse
I am on it.

radiocarbon said:
Ever since TWRP 3.1.0-0 twrp can no longer read my encrypted data partition probably due to commit f628cbfc5e77a3a358c95ef7f1e47bbb1505b9d0 on the TeamWin github for the gts28vewifi (I can't post the direct link because my account is too new).
Is there any reason the encryption blobs were swapped out and how would I go about getting twrp to read my encrypted data partition again. I've already tried wiping everything, reflashing and reencrypting but it didn't help.
Click to expand...
Click to collapse
Actually, I think the issue with decryption is with qcom_common. The following commit is needed (which exists on the android-7.1 branch): https://github.com/TeamWin/android_...mmit/c4dab0d6d73f05b70091761e536b751dc9328f49

radiocarbon said:
Ever since TWRP 3.1.0-0 twrp can no longer read my encrypted data partition probably due to commit f628cbfc5e77a3a358c95ef7f1e47bbb1505b9d0 on the TeamWin github for the gts28vewifi (I can't post the direct link because my account is too new).
Is there any reason the encryption blobs were swapped out and how would I go about getting twrp to read my encrypted data partition again. I've already tried wiping everything, reflashing and reencrypting but it didn't help.
Click to expand...
Click to collapse
Please try latest ( 3.1.1-1 ) build.

LuK1337 said:
Please try latest ( 3.1.1-1 ) build.
Click to expand...
Click to collapse
It works now, thank you very much.

Hi, would this be compatible with gts210veltexx

Alpha1BA said:
Hi, would this be compatible with gts210veltexx
Click to expand...
Click to collapse
No, T813 recovery probably is.

Hello, think I need some help with setting up this particular tab... None of the recovery images listed on the official site (plus the unofficial one here) work properly. Any 3.1.0+ one would say "Failed to mount /data (invalid arguments)" and not show me my internal storage and data (shows /system and SD card alright though), and lower version ones would just boot to TWRP splash screen then reboot, without getting to the main menu. I'm running the latest Nougat update (T713XXU2BQD3) if that matters.

AndyYan said:
Hello, think I need some help with setting up this particular tab... None of the recovery images listed on the official site (plus the unofficial one here) work properly. Any 3.1.0+ one would say "Failed to mount /data (invalid arguments)" and not show me my internal storage and data (shows /system and SD card alright though), and lower version ones would just boot to TWRP splash screen then reboot, without getting to the main menu. I'm running the latest Nougat update (T713XXU2BQD3) if that matters.
Click to expand...
Click to collapse
You can't mount data if you come from stock. It is encrypted and twrp doesn't support it so you got to format it to ext4 in order to mount it.

LuK1337 said:
You can't mount data if you come from stock. It is encrypted and twrp doesn't support it so you got to format it to ext4 in order to mount it.
Click to expand...
Click to collapse
Ugh. It had been a while since I touched any recent Samsung devices, didn't know I had to do extra work around encryption. Used a lot of other devices but TWRP handles all of them with a default key, that's why I'm quite baffled why it doesn't here. Thanks for the quick save though.

AndyYan said:
Ugh. It had been a while since I touched any recent Samsung devices, didn't know I had to do extra work around encryption. Used a lot of other devices but TWRP handles all of them with a default key, that's why I'm quite baffled why it doesn't here. Thanks for the quick save though.
Click to expand...
Click to collapse
Samsung uses different encryption and we only support AOSP one.

LuK1337 said:
Samsung uses different encryption and we only support AOSP one.
Click to expand...
Click to collapse
Alrighty, can understand. Can there be a notice somewhere up this thread or the TWRP device landing page about it?

Is LineageOS 14.1 the only rom for this t713wifi. I cant find any stock rooted.

[RECOVERY][OFFICIAL] TWRP 3.1.1 for Exynos

Disclaimer: Usual disclaimer applies. I've tested this recovery but it might not work due to a different ROM / device / moon phase / etc. Use at your own risk.
Introduction
After working with upstream TWRP developers and fixing some bugs (in TWRP itself and in this port) this device finally has an official port
There were various builds available at different times (some with bugs) but most of them should now be fixed.
Features
Works
backup/restore
installing zips
ADB
MTP
Screen turns off
Basically the rest of this list
format /data
Adoptable storage
Decrypt /data
Doesn't work (please ask if you need this)
Encrypted backup (set password for /data/data)
USB-OTG
Untested
Backup/restore of stock system / data.
Installation instructions
Warning: only use it on the G800F/M/Y, NOT on the G800H! I only tested the G800F, but think G800M/Y will also work. G800H will most likely NOT work, as it is based on a different SoC (Qualcomm).
Download the recovery image from twrp.me. It also includes some installation instructions.
There are more extensive installation instructions over at the LineageOS ROM installation instructions.
I personally prefer using Heimdall, but you can also use Odin. Commands in Download/Odin mode (power off, then press home+Volume-Down+power):
Code:
heimdall flash --RECOVERY recovery.img
If you're using the stock ROM, use:
Code:
heimdall flash --RECOVERY recovery.img --no-reboot
When you come from the stock ROM you have to make sure the stock ROM doesn't overwrite TWRP: Pull the battery, wait 5 seconds, insert it again, and press home + volume up + power to enter TWRP and replace the stock ROM from there.
If you already have TWRP or LineageOS, it's much easier to install from there, see twrp.me.
Another method is using ADB (from your computer). I used it a lot during testing:
Code:
adb root
adb push twrp-3.1.1-1-kminilte.img /dev/block/mmcblk0p10
Changelog
Code:
2017-07-10:
* fix formatting /data while the partition is encrypted
(device is not encrypted by default)
* add support for adoptable storage
* accept kminiltexx etc. for flashing basebands
2017-06-20:
* ADB
* MTP at the same time as ADB
* Screen turns fully off
* fix for restoring backups made using `adb backup --twrp`
Source code
Kernel: https://github.com/TeamWin/android_kernel_samsung_kminilte/tree/cm-14.1
Device: https://github.com/TeamWin/android_device_samsung_kminilte/tree/cm-14.1
This recovery is built using a LineageOS tree. Instructions are similar to the instructions for building LineageOS for the S5 mini. Differences are: you don't need to patch the source (skip that step) and the last step is mka recoveryimage instead of mka bacon - this only builds the recovery resulting in much faster builds. Also see the official build instructions.
Thanks
Other people who have worked on this project:
Team Win, of course, for the recovery itself! In particular bigbiff which has worked with me to make this device official.
hennymcc
RVR
---
Note to moderators: this is my first DevDB thread started on XDA so I may have made mistakes.
XDA:DevDB Information
Team Win Recovery Project, ROM for the Samsung Galaxy S5 Mini
Contributors
ayke, hennymcc, RVR
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Version Information
Status: Stable
Current Stable Version: 3.1.1
Stable Release Date: 2017-06-20
Created 2017-06-24
Last Updated 2017-07-09

Thanks!

OFFICIAL TWRP...I can't believe it
Great work on this one...many thanks.

Thanks a million @ayke ! However, I found some bugs I'd like to submit some bugs I discovered:
- Recovery is not SEANDROID enforcing" message when booting TWRP, didn't cause any trouble for me but still - it was fine in your previous unofficial build
- Some zip files (tested with latest modem flashable zip) report "This package is for kminiltexx devices; this is a kminilte", so it doesn't flash and fails with ERROR:7
I can confirm that decrypting a File-Based encrypted /data partition works, I didn't test the backup tool though.
P.S. Is it possible to add support for adopted storage, that would be awesome!
Nevertheless - thanks for making this device officialy supported!

Friedensfurz said:
Thanks a million @ayke ! However, I found some bugs I'd like to submit some bugs I discovered:
- Recovery is not SEANDROID enforcing" message when booting TWRP, didn't cause any trouble for me but still - it was fine in your previous unofficial build
Click to expand...
Click to collapse
The current kernel used upstream is somewhat older and hasn't enabled SELinux yet. I don't see why you would want enforcing SELinux in TWRP, though.
Friedensfurz said:
- Some zip files (tested with latest modem flashable zip) report "This package is for kminiltexx devices; this is a kminilte", so it doesn't flash and fails with ERROR:7
Click to expand...
Click to collapse
I think I have a fix for that, please test https://aykevl.nl/download/2017-06-25-recovery-fix-ota-asserts.img (not tested by me)
Friedensfurz said:
I can confirm that decrypting a File-Based encrypted /data partition works, I didn't test the backup tool though.
Click to expand...
Click to collapse
Nice!
Friedensfurz said:
P.S. Is it possible to add support for adopted storage, that would be awesome!
Click to expand...
Click to collapse
I might look into it. I don't use it at the moment but am considering it.
EDIT: I have fixed it, it will be included in the next build.

any chance for g800h support?

sasukesama said:
any chance for g800h support?
Click to expand...
Click to collapse
Not from me. The G800H is a completely different device. I have a G800F so I can't test it.

ayke said:
I think I have a fix for that, please test https://aykevl.nl/download/2017-06-25-recovery-fix-ota-asserts.img (not tested by me)
Click to expand...
Click to collapse
Sorry, but the build doesn't fix the wrong device id issue - still throws error " This is for kminiltexx your device is kminilte. Anyway - maybe the next build will fix it[emoji6]

Friedensfurz said:
Sorry, but the build doesn't fix the wrong device id issue - still throws error " This is for kminiltexx your device is kminilte. Anyway - maybe the next build will fix it[emoji6]
Click to expand...
Click to collapse
Can you give a link to where you downloaded this zip? Then I can test it myself.

I also get the device error with latest official and 2017-06-25-recovery-fix-ota-asserts.img.
Tried to flash one of Spookcity's kernels, you can find it here (search for "test9" that is what I used lately).
https://github.com/Spookcity/ROMS-G800F/issues/10#issuecomment-301915315
The latest pre-official TWRP 3.1.1-0 works (says kminiltexx).

ayke said:
Can you give a link to where you downloaded this zip? Then I can test it myself.
Click to expand...
Click to collapse
This file causes problems with the device id: http://pt.tapatalk.com/redirect.php...1_22.05.2017_DRE-flashable.zip&au_id=13587482
It is a TWRP flashable baseband file, hope this helps

@Friedensfurz @Pat750
I couldn't find a (still online) kernel from Spookcity and I'd rather not flash a new modem unless I know why I should do that. So I haven't verified it.
But here's another build you can try. My previous attempt was incomplete.
https://aykevl.nl/download/2017-06-27-recovery-fix-ota-asserts-2.img
On my device I've verified it has a ro.product.device property of kminiltexx.

ayke said:
@Friedensfurz @Pat750
I couldn't find a (still online) kernel from Spookcity and I'd rather not flash a new modem unless I know why I should do that. So I haven't verified it.
But here's another build you can try. My previous attempt was incomplete.
https://aykevl.nl/download/2017-06-27-recovery-fix-ota-asserts-2.img
On my device I've verified it has a ro.product.device property of kminiltexx.
Click to expand...
Click to collapse
Yeah,I removed all of my test build links from my google drive, but have a thread on here. I already sent you this though. I will test your new build and see if it helps.
Edit:
Yep,fixed. Good work Ayke!
Sent from my SM-G800F using Tapatalk

Friedensfurz said:
...
I can confirm that decrypting a File-Based encrypted /data partition works, I didn't test the backup tool though.
...
Click to expand...
Click to collapse
I'm having a few issues with TWRP 3.1.1 where "wipe / format data" (where you have to key "yes") generates the following error msg (I posted a similar msg in Slim Rom 7 thread):
Code:
Error:unable to wipe /data unknown file system 'auto'
unable to format encryption.
I'm now wondering whether decrypting the data partition from within TWRP will address my format data issue reported above.
Can I ask how you did this? I've dug around the TWRP menus but nothing has jumped out at me (maybe it's something you need to run from the terminal?)
Many thanks!

fidoedidoe said:
I'm having a few issues with TWRP 3.1.1 where "wipe / format data" (where you have to key "yes") generates the following error msg (I posted a similar msg in Slim Rom 7 thread):
Code:
Error:unable to wipe /data unknown file system 'auto'
unable to format encryption.
I'm now wondering whether decrypting the data partition from within TWRP will address my format data issue reported above.
Can I ask how you did this? I've dug around the TWRP menus but nothing has jumped out at me (maybe it's something you need to run from the terminal?)
Many thanks!
Click to expand...
Click to collapse
I have the same problem

Here also this message in unofficial builds, don't tried it, but I think its still present in this version.

fidoedidoe said:
I'm having a few issues with TWRP 3.1.1 where "wipe / format data" (where you have to key "yes") generates the following error msg (I posted a similar msg in Slim Rom 7 thread):
I'm now wondering whether decrypting the data partition from within TWRP will address my format data issue reported above.
Can I ask how you did this? I've dug around the TWRP menus but nothing has jumped out at me (maybe it's something you need to run from the terminal?)
Many thanks!
Click to expand...
Click to collapse
I still haven't found a method to decrypt the /data volume from within TWRP (a reference earlier in the thread implied it was possible)..the hope being this would mitigate the "wipe / format data" error:
Code:
Error:unable to wipe /data unknown file system 'auto'
unable to format encryption.
What I did discover was that when reverting to an older version of TWRP (2.8.x) using Odin, " format data" (where you have to type "yes" to proceed) didn't error. I'm not sure whether that cured the issue, but after that I updated TWRP image back to 3.1.1.0 and installed my ROM as normal.
Still looking for a recognised method to wipe encrypted /data volume from within latest stable TWRP if anyone has any experience of that.
EDIT
Another thread suggests (to my untrained eye) that "unknown file system 'auto" may be related to how twrp.fstab is configured.
I'm very much out of my here ( so apologies for the crude suggestion), but could it be that another build of a TWRP image is needed where twrp.fstab is changed to allow "format data" to work, ie substitute "fstype" from "auto" to "ext4" as outlined below :
Code:
...
/data ext4 /dev/block/mmcblk0p21 length=-16384
...

fidoedidoe said:
I still haven't found a method to decrypt the /data volume from within TWRP (a reference earlier in the thread implied it was possible)..the hope being this would mitigate the "wipe / format data" error:
Code:
Error:unable to wipe /data unknown file system 'auto'
unable to format encryption.
What I did discover was that when reverting to an older version of TWRP (2.8.x) using Odin, " format data" (where you have to type "yes" to proceed) didn't error. I'm not sure whether that cured the issue, but after that I updated TWRP image back to 3.1.1.0 and installed my ROM as normal.
Still looking for a recognised method to wipe encrypted /data volume from within latest stable TWRP if anyone has any experience of that.
EDIT
Another thread suggests (to my untrained eye) that "unknown file system 'auto" may be related to how twrp.fstab is configured.
I'm very much out of my here ( so apologies for the crude suggestion), but could it be that another build of a TWRP image is needed where twrp.fstab is changed to allow "format data" to work, ie substitute "fstype" from "auto" to "ext4" as outlined below :
Code:
...
/dataext4/dev/block/mmcblk0p21length=-16384
...
Click to expand...
Click to collapse
I got it to work by formatting/repairing/changing filesystem in TWRP. Just try some combinations, it will work eventually

Yes, I think it's because of the 'auto' in the fstab. I've set it to ext4 in this build (for data and cache):
https://aykevl.nl/download/2017-07-03-recovery.img
This build also contains the previous fixes (adoptable storage, fixing the kminiltexx error).
If it fixes the issue for you, I'll push the change for inclusion in the next official build.
I didn't see any negative consequences of changing the FS type in fstab. Even setting the fstab entry to 'f2fs' mounts /data as usual (as ext4) so I think it's safe.

ayke said:
https://aykevl.nl/download/2017-07-03-recovery.img
Click to expand...
Click to collapse
Can someone test this change? Then I'll integrate it in the official build.

[TWRP][E5823] Latest TWRP 3.2.1 for Z5 Compact

Updated TWRP for the Z5 Compact
REQUIRES:
- Unlocked bootloader
- Have Fastboot drivers installed on the PC you use for flashing
FEATURES:
- MTP support
- ADB root
- Reboot to Bootloader
- SD Card access
Not working (for now):
- Decryption <- working on it when I have time
Changelog:
23.02.2018
- Backup/Restore fix for USB OTG
- small fstab tuning (thanks @GreyLeshy)
- DL link updated - Now you will have access to all builds inside GDrive folder
22.02.2018 - 2
- Fix SD Card (again) on latest build
22.02.2018
- USB OTG fixed
15.02.2018
- Possibly fixed decryption, need feedback
13.02.2018
- Fixed SD card
7.02.2018
- First build
DOWNLOAD LINK
Google Drive
Instructions:
- Connect phone to PC in Fastboot mode
- Open Command Prompt and type
Code:
fastboot flash recovery recovery-name.img
- Take off the cable and boot into recovery by holding Power + Vol Down until you feel a vibration
Disclaimer: I am merely distributing the ready image. I will do my best to keep this thread up-to-date with the latest TWRP releases and provide fixed images in case there is a bug, I can help you to solve some problems but do not expect any timeframe.
I am not responsible for any bricked phones, missed alarms or thunderstorms. What you do with your phone is your own choice. Happy flashing!
Credits:
@TwrpBuilder for making this, all credits go to them
and all other maintainers and contributors to the code

trax7 said:
Needs testing:
- Decryption
Click to expand...
Click to collapse
Decryption is not working
Good job anyway, we have an updated TWRP at least!!

Don't need decryption and everything else works fine!! Strange how md5 checksum is now Digest!! Must be an Oreo thing
Sent from my Sony Xperia Z5 Compact using XDA Labs

@trax7
I own a Zuk Z2, on it the decryption problem was caused by unaligned/updated vendor blobs. I hope this can give you an hint on how to fix decryption.

Doe.it said:
Decryption is not working
Good job anyway, we have an updated TWRP at least!!
Click to expand...
Click to collapse
You tried with a password? Try with factory reset (not wipe data) and it should work... Note that you will lose data so be sure to copy it somewhere first.

trax7 said:
You tried with a password? Try with factory reset (not wipe data) and it should work... Note that you will lose data so be sure to copy it somewhere first.
Click to expand...
Click to collapse
I am encrypted everyday on my phone (I have set a password), I am using latest official stock firmware, decryption doesn't work returning a "failed decryption" message.

Thank you!

Hello trax7,
first of all ... many, many, many thanks for the provision of a current TWRP !!!!!
I searched for it so long !!!
Not working (for now):
- Decryption
- You tell me
Click to expand...
Click to collapse
For the moment I found three things for need of improvement:
1. When going into Recovery, the purple lamp (at the top of the case) does not light up.
2. Double touch the screen, doesn't wake up / switch on the screen again.
3. When starting a backup, I get five error messages:
unable to locate /persistent partition for backup calculations,
unable to locate /misc partition for backup calculation,
unable to locate /firmware partition for backup calculation,
unable to locate /persist partition for backup calculation,
unable to locate /ta partition for backup calculation,​... but the backup of the five partitions "boot, cache, data, recovery and system" runs through error-free.
However - I'm glad that we have became a current TWRP for our device!
And if one day the decryption works, I will be happy!

rm43115 said:
Hello trax7,
first of all ... many, many, many thanks for the provision of a current TWRP !!!!!
I searched for it so long !!!
For the moment I found three things for need of improvement:
1. When going into Recovery, the purple lamp (at the top of the case) does not light up.
2. Double touch the screen, doesn't wake up / switch on the screen again.
3. When starting a backup, I get five error messages:
unable to locate /persistent partition for backup calculations,
unable to locate /misc partition for backup calculation,
unable to locate /firmware partition for backup calculation,
unable to locate /persist partition for backup calculation,
unable to locate /ta partition for backup calculation,​... but the backup of the five partitions "boot, cache, data, recovery and system" runs through error-free.
However - I'm glad that we have became a current TWRP for our device!
And if one day the decryption works, I will be happy!
Click to expand...
Click to collapse
That's weird... I haven't experienced any of those bugs Maaybe just the purple lamp but I haven't even paid attention to that lol
Edit: Yes, purple LED does not light up. However the recovery did not complain at all during backups and locking and unlocking the screen is just fine. Are you using E5823 or E5803?

What about encrypted data partition. Is it possible to fix decrypting?

jw96 said:
What about encrypted data partition. Is it possible to fix decrypting?
Click to expand...
Click to collapse
At the moment no, but you can try and test whether it picks it up after a factory reset... Backup ur data tho.

trax7 said:
That's weird... I haven't experienced any of those bugs Maaybe just the purple lamp but I haven't even paid attention to that lol
Edit: Yes, purple LED does not light up. However the recovery did not complain at all during backups and locking and unlocking the screen is just fine. Are you using E5823 or E5803?
Click to expand...
Click to collapse
Ha, last night I found the problem for the strange error messages during the backup (it's not a problem of your TWRP-version):
In the .TWRPS file these partitions (persist, persistent, misc, firmware, ta) are still registered for backup from the old TWRP-version I used before.
I just had deleted the .TWRPS file and have created it again ... AND ... ERROR GONE!
I use E5823, but I would not call the problems with the violet lamp and the double-touch-unlock-screen an error ... rather a nice-to-have feature.
I mean, do not waste time with these banalities, if you do not know the solution.

USB OTG storage support
Hello trax7,
at the coming weekend I want to test the decryption of the TWRP - during preparation I realize that "USB OTG storage support" is missing.
Is it possible to implement "USB OTG storage support"?

rm43115 said:
Is it possible to implement "USB OTG storage support"?
Click to expand...
Click to collapse
@Trax , add to fstab
Code:
/usb-otg auto /dev/block/sda1 /dev/block/sda

Doe.it said:
Decryption is not working
Good job anyway, we have an updated TWRP at least!!
Click to expand...
Click to collapse
Doe.it said:
I am encrypted everyday on my phone (I have set a password), I am using latest official stock firmware, decryption doesn't work returning a "failed decryption" message.
Click to expand...
Click to collapse
jw96 said:
What about encrypted data partition. Is it possible to fix decrypting?
Click to expand...
Click to collapse
Decryption can't be achieved by only password. It requires a factory reset (not wipe data!). This is a security measure and each Android device creates their own password for encrypted data partition. So any other passwords such as lock screen security pin won't work. All ways go to performing a factory reset. In addition, in order not to have encrypted data partition again, fstab inside boot image must be modified.
rm43115 said:
Hello trax7,
at the coming weekend I want to test the decryption of the TWRP - during preparation I realize that "USB OTG storage support" is missing.
Is it possible to implement "USB OTG storage support"?
Click to expand...
Click to collapse
Yes, it is possible. Your device support OTG on it's stock fstab. After we get our works done, we will look onto this too!
Stay tuned!
berkanktz​

GreyLeshy said:
@Trax , add to fstab
Code:
/usb-otg auto /dev/block/sda1 /dev/block/sda
Click to expand...
Click to collapse
@GreyLeshy: Can I add it manually?

rm43115 said:
Can I add it manually?
Click to expand...
Click to collapse
Yes, You can with Android Image Kitchen

New build posted, USB OTG fixed as per @GreyLeshy 's suggestion.

trax7 said:
New build posted, USB OTG fixed as per @GreyLeshy 's suggestion.
Click to expand...
Click to collapse
THANK YOU!!!!
Now I can test the decryption this weekend ... if my children let me.
trax7 said:
Changelog:
22.02.2017
-USB OTG fixed
15.02.2017
-Possibly fixed decryption, need feedback
13.02.2017
- Fixed SD card
7.02.2017
- First build
Click to expand...
Click to collapse
You mean 2018 and not 2017.

In the latest two builds SD card access is broken again (or at least I can't access it). Reverting to recovery_suzuran-130218.img SD card access works again.

OP3T ROM Built From CAF Source Code - Encryption Unsuccessful

Hi! I followed the steps here to build stock CAF Android for my device.
I made the factory images and OTA zip, and it said everything was successful.
When I flash the factory images, it says that it's looking for a "QC Reference Phone" and my phone identifies as either msm8996 or oneplus3 (can't remember) so it won't flash.
When I flash the OTA zip, it says that this phone is a "oneplus3" and it needs "msm8996" so it wouldn't flash either, but I got around that by removing the checks in the updater script.
So I've got it flashed onto my device, but I'm facing a problem:
Once it's flashed, it boots, but then says Encryption Unsuccessful, and to factory reset my phone. However, if I do that, I get the same error.
Also, I noticed that when I run fastboot commands like "fastboot format userdata" it tells me
Code:
Couldn't parse erase-block-size '0x'.
Couldn't parse logical-block-size '0x'.
Could anyone help with this? I can even pay like 20$ if I get a good solution
Thanks

Have you tried completely wiping your data from TWRP? That is erasing everything from the "Format Data" option under "Wipe". You need to enter "yes" from the keyboard to confirm. This basically does the same thing as fastboot format user data. Try this, and let us know what happens.

thes3usa said:
Have you tried completely wiping your data from TWRP? That is erasing everything from the "Format Data" option under "Wipe". You need to enter "yes" from the keyboard to confirm. This basically does the same thing as fastboot format user data. Try this, and let us know what happens.
Click to expand...
Click to collapse
Do I do this before or after flashing the zip file?
Thanks, Nate

Follow these steps.
Wipe System/Data/Cache
Flash Zip
Reboot back into Recovery
Wipe all data as I've mentioned in the above post
Reboot.

thes3usa said:
Follow these steps.
Wipe System/Data/Cache
Flash Zip
Reboot back into Recovery
Wipe all data as I've mentioned in the above post
Reboot.
Click to expand...
Click to collapse
Thanks for the help. I flashed it, rebooted back to recovery, and chose Format Data - "yes" and it says:
Code:
Failed to mount '/data' (Device or resource busy)
Failed to mount '/data' (Device or resource busy)
Unable to recreate /data/media folder.
You may need to reboot recovery to be able to use /data again
Updating partition details...
Failed to mount '/data' (Device or resource busy)
...done
Unable to mount storage
I rebooted anyways just to see, and it goes like normal on the OnePlus logo, then the boot animation, and then I get the same screen. https://imgur.com/a/hD8Zm
Rebooted again back to recovery and did the same format, and that time it worked successfully. I rebooted back into the OS, and same error.

NateDev said:
Thanks for the help. I flashed it, rebooted back to recovery, and chose Format Data - "yes" and it says:
Code:
Failed to mount '/data' (Device or resource busy)
Failed to mount '/data' (Device or resource busy)
Unable to recreate /data/media folder.
You may need to reboot recovery to be able to use /data again
Updating partition details...
Failed to mount '/data' (Device or resource busy)
...done
Unable to mount storage
I rebooted anyways just to see, and it goes like normal on the OnePlus logo, then the boot animation, and then I get the same screen. https://imgur.com/a/hD8Zm
Click to expand...
Click to collapse
Seems like your data partition is completely corrupt. You may want to try the Unbrick tool, to get your device back working. "Fastboot Format Userdata" was the last thing you could do, and it doesnt work.

Are you sure the build compiled correctly? I've never seen something like this happen, and it's quite weird. It's happened to me, but under completely different circumstances.
Are you on the recommended TWRP? That is Acuicultors TWRP for the 3/3T? It is bug free.

thes3usa said:
Seems like your data partition is completely corrupt. You may want to try the Unbrick tool, to get your device back working. "Fastboot Format Userdata" was the last thing you could do, and it doesnt work.
Click to expand...
Click to collapse
What's weird though is when I was trying this before and got this issue, I went back and flashed OxygenOS and it booted fine. This attempt now was straight off of OxygenOS and it doesn't work.
Do you think it's still worth trying the Unbrick tool, as OOS worked fine inbetween? idk but maybe it could be more of an issue with the ROM, but I built it with no modifications straight from OnePlus' GitHub.
EDIT: Didn't see your second post, about the build compiling.
It looks like it compiled correctly, didn't show any errors, and the final message was green, not red.
I'm on the TWRP from twrp.me, is that the reccomended one?
EDIT2: Tried this TWRP https://androidfilehost.com/?fid=746010030569948067, I flashed the ROM and when I go to format data, it says:
Code:
mkfs.f2fs -t 0 -r 16384 /dev/block/sda15 process ended with ERROR: 1
Unable to wipe Data.
Unable to format to remove encryption
That line about encryption is interesting, is there a way to disable encryption on the 3T? I saw this https://forum.xda-developers.com/oneplus-3t/how-to/disable-dm-verity-force-encryption-op3t-t3688748 but idk if it would as it says its only for OOS.
Then I just tried this https://android.stackexchange.com/questions/98228/removing-encryption-from-recovery to remove encryption but the boot just gets stuck on the boot animation, even after setting it to on and reflashing, so I'm going to hope I didn't brick my phone and am going to try the unbrick tool if flashing stock does nothing.
Thanks for your help

NateDev said:
What's weird though is when I was trying this before and got this issue, I went back and flashed OxygenOS and it booted fine. This attempt now was straight off of OxygenOS and it doesn't work.
Do you think it's still worth trying the Unbrick tool, as OOS worked fine inbetween? idk but maybe it could be more of an issue with the ROM, but I built it with no modifications straight from OnePlus' GitHub.
EDIT: Didn't see your second post, about the build compiling.
It looks like it compiled correctly, didn't show any errors, and the final message was green, not red.
I'm on the TWRP from twrp.me, is that the reccomended one?
EDIT2: Tried this TWRP https://androidfilehost.com/?fid=746010030569948067, I flashed the ROM and when I go to format data, it says:
Code:
mkfs.f2fs -t 0 -r 16384 /dev/block/sda15 process ended with ERROR: 1
Unable to wipe Data.
Unable to format to remove encryption
That line about encryption is interesting, is there a way to disable encryption on the 3T? I saw this https://forum.xda-developers.com/oneplus-3t/how-to/disable-dm-verity-force-encryption-op3t-t3688748 but idk if it would as it says its only for OOS.
Then I just tried this https://android.stackexchange.com/questions/98228/removing-encryption-from-recovery to remove encryption but the boot just gets stuck on the boot animation, even after setting it to on and reflashing, so I'm going to hope I didn't brick my phone and am going to try the unbrick tool if flashing stock does nothing.
Thanks for your help
Click to expand...
Click to collapse
Sorry for the late reply, got a little busy there.
Did you flash OOS after flashing the Custom Build? If you did so, and it worked, it may not be the device, it may be the build.

thes3usa said:
Sorry for the late reply, got a little busy there.
Did you flash OOS after flashing the Custom Build? If you did so, and it worked, it may not be the device, it may be the build.
Click to expand...
Click to collapse
Yea I flashed OOS after my custom build, which does point to the build being the problem.
That's weird because everything completed with no errors, and I used the source straight from OnePlus.
And, seeing how inactive they are on GitHub, doesn't look like I'll be getting a solution from them anytime soon
Is there a similar ROM source code that I could use? I'm looking for barebones CAF, basically. I saw this: https://github.com/AOSP-CAF but I don't even know if it's possible to configure that for the 3T without extensive work, as it looks to just be a generic build.

NateDev said:
Yea I flashed OOS after my custom build, which does point to the build being the problem.
That's weird because everything completed with no errors, and I used the source straight from OnePlus.
And, seeing how inactive they are on GitHub, doesn't look like I'll be getting a solution from them anytime soon
Is there a similar ROM source code that I could use? I'm looking for barebones CAF, basically. I saw this: https://github.com/AOSP-CAF but I don't even know if it's possible to configure that for the 3T without extensive work, as it looks to just be a generic build.
Click to expand...
Click to collapse
You should try LineageOS's source, if you're looking for barebones. Can't say it's similar to CAF though. If you're an Amateur at these stuff, use Sources that are already readily built for the 3T, so you can do your own customizations without having to worry about the build failing.

thes3usa said:
You should try LineageOS's source, if you're looking for barebones. Can't say it's similar to CAF though. If you're an Amateur at these stuff, use Sources that are already readily built for the 3T, so you can do your own customizations without having to worry about the build failing.
Click to expand...
Click to collapse
Is LineageOS CAF based or AOSP? I searched but couldn't find a clear answer. If it's indeed CAF I will probably go ahead and try that.
Sucks that OnePlus's own GitHub for building for the 3T fails, and I kinda would have liked the experience of bringing up the system from the most barebones it could get, but if I can't even get an initial build to boot up with no modifications whatsoever, then I'll have to do Lineage.
I'll keep my OSS sources on my PC for the next week or 2 and resync and rebuild in the hopes that they change something that fixes it.
Thanks for your help

NateDev said:
Is LineageOS CAF based or AOSP? I searched but couldn't find a clear answer. If it's indeed CAF I will probably go ahead and try that.
Sucks that OnePlus's own GitHub for building for the 3T fails, and I kinda would have liked the experience of bringing up the system from the most barebones it could get, but if I can't even get an initial build to boot up with no modifications whatsoever, then I'll have to do Lineage.
I'll keep my OSS sources on my PC for the next week or 2 and resync and rebuild in the hopes that they change something that fixes it.
Thanks for your help
Click to expand...
Click to collapse
LineageOS is AOSP based, but has one of the most trusted sources, that are confirmed to be working.
It's OnePlus. Obviously their sources are going to be messed up. Look at their absolutely horrible Camera2 API Implementation. It's the reason why we need so many add-on fixes for HDR+ and other features to be working on the front camera.
Try resyncing the Repo, or completely start the sync over from scratch. Who knows, maybe your saved sources are messed up, and that's what causing the build error.
Good luck with the building!

thes3usa said:
LineageOS is AOSP based, but has one of the most trusted sources, that are confirmed to be working.
It's OnePlus. Obviously their sources are going to be messed up. Look at their absolutely horrible Camera2 API Implementation. It's the reason why we need so many add-on fixes for HDR+ and other features to be working on the front camera.
Try resyncing the Repo, or completely start the sync over from scratch. Who knows, maybe your saved sources are messed up, and that's what causing the build error.
Good luck with the building!
Click to expand...
Click to collapse
"It's OnePlus. Obviously their sources are going to be messed up. Look at their absolutely horrible Camera2 API Implementation. It's the reason why we need so many add-on fixes for HDR+ and other features to be working on the front camera." Haha yep you're right lol.
Thanks, I'll try LOS and keep trying OnePlus's sources, and I will resync as well incase that's the issue.
Thanks so much for all your help