Database Develop

[Recovery] [v510_palman] [2014-12-09] TWRP 2.8.2.0

TWRP 2.8.2.0​Team Win Recovery Project 2.x, or twrp2 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.
This is not an official TeamWin TWRP build. I used TWRP sources found HERE, device tree that I created for TWRP that can be found HERE.
Changelog:
CHANGELOG for 2.8.2.0 - From TWRP webiste...
-Pull in all changes from Android 5.0 lollipop into TWRP
-Add decrypt support for Android 5.0 lollipop encrypted partitions including automatic decrypt when the default_password is in use
-Revert some changes to exFAT that were breaking exFAT support on some devices
-Other minor fixes and updates
Note: At this time we do not have a GUI representation for pattern unlock. You can still decrypt patterns though by translating the pattern dots to numbers. The pattern dots correspond to numbers in the following pattern:
1 2 3
4 5 6
7 8 9
So an upper-case L would translate to a password of 14789 entered on the keyboard. Eventually we plan to add a proper pattern unlock to TWRP but it is a relatively low priority at this point.
More info and changelog can be found on the official TWRP website HERE
Install Instructions:
With custom recovery already installed.
Download
Place zip file on phone
Reboot into recovery
Flash zip file through recovery
Reboot
With stock recovery - Need ADB installed.
Download zip file
Extract recovery.zip to a folder on your computer. Example c:\recovery
Open terminal window/command prompt, browse the the c:\recovery folder to execute following commands
adb reboot bootloader
fastboot flash recovery recovery.img
use vol +/- to scroll through menu to select recovery mode
press power button to reboot into updated recovery
profit!
Download:
Download HERE
Credits:
@Dees_Troy
TeamWin
Everyone involved with TWRP.
PS...Working on CM12 for V510 now

Thanks!
It doesn't seem to ask for a password to decrypt /data for encrypted devices though like it does on my N5.

Having some difficulty getting this to push through on the V50020d build. Thoughts?

apvikes28 said:
Having some difficulty getting this to push through on the V50020d build. Thoughts?
Click to expand...
Click to collapse
This is only for GPE 510 devices. There is another thread for your device.

NHLWil said:
Thanks!
It doesn't seem to ask for a password to decrypt /data for encrypted devices though like it does on my N5.
Click to expand...
Click to collapse
Can you flash the latest build, has today's date in it and see if it works now?
Thanks!

AndroidUser00110001 said:
Can you flash the latest build, has today's date in it and see if it works now?
Thanks!
Click to expand...
Click to collapse
It still didn't ask for a password, nor could I mount /data manually due to encryption. I even took out my SD card for giggles, thinking since TWRP was able to mount that, it could've been skipping trying to mount /data, but no dice.

AndroidUser00110001 said:
Can you flash the latest build, has today's date in it and see if it works now?
Thanks!
Click to expand...
Click to collapse
NHLWil said:
It still didn't ask for a password, nor could I mount /data manually due to encryption. I even took out my SD card for giggles, thinking since TWRP was able to mount that, it could've been skipping trying to mount /data, but no dice.
Click to expand...
Click to collapse
@AndroidUser00110001, maybe you need to have fstab.palman in the ramdisk, as described in this commit message: https://github.com/omnirom/android_bootable_recovery/commit/4eca40d7d8ff6968ed68a24686093cfb6f5f6373

NHLWil said:
It still didn't ask for a password, nor could I mount /data manually due to encryption. I even took out my SD card for giggles, thinking since TWRP was able to mount that, it could've been skipping trying to mount /data, but no dice.
Click to expand...
Click to collapse
Try twrp-2.8.2.0_v510-20141209.zip

AndroidUser00110001 said:
Try twrp-2.8.2.0_v510-20141209.zip
Click to expand...
Click to collapse
Still no change.

NHLWil said:
Still no change.
Click to expand...
Click to collapse
What exactly is going on because I am able to mount and do whatever I need to do.

AndroidUser00110001 said:
What exactly is going on because I am able to mount and do whatever I need to do.
Click to expand...
Click to collapse
And your device is encrypted running Lollipop?
With my N5, TWRP prior to 2.8.2.0 was not able to decrypt the /data partition on Lollipop. It would simply ask for the password, but would always fail. 2.8.2.0 fixed this.
However, with 2.8.2.0 on palman, it never even asks for the password . . . it just says it's unable to mount /data. The decryption routine doesn't appear to be working at all for me.

NHLWil said:
And your device is encrypted running Lollipop?
With my N5, TWRP prior to 2.8.2.0 was not able to decrypt the /data partition on Lollipop. It would simply ask for the password, but would always fail. 2.8.2.0 fixed this.
However, with 2.8.2.0 on palman, it never even asks for the password . . . it just says it's unable to mount /data. The decryption routine doesn't appear to be working at all for me.
Click to expand...
Click to collapse
Can you get a log? Is your data partition encrypted? I am guessing you are running the stock ROM?
I can mount data and wipe data. Not sure what issue you are having unless I am not understanding what you are trying to explain.

AndroidUser00110001 said:
Can you get a log? Is your data partition encrypted? I am guessing you are running the stock ROM?
I can mount data and wipe data. Not sure what issue you are having unless I am not understanding what you are trying to explain.
Click to expand...
Click to collapse
Yes, my data partition is encrypted. TWRP 2.8.2.0 on the N5 supports decrypting data. TWRP 2.8.2.0 on the N5 will ask for your password as soon as it boots, and when you input the proper password, it will decrypt data so it can be mounted.
TWRP 2.8.2.0 on palman does not ask for the password as soon as it boots, thus data is not decrypted. The exact error is:
"Could not mount /data and unable to find crypto footer"

AndroidUser00110001 said:
TWRP 2.8.2.0​PS...Working on CM12 for V510 now
Click to expand...
Click to collapse
OMG if you can get CM12 out for the V510 GPE device I am sure you would become an instant hero to thousands of users...

jk8260 said:
OMG if you can get CM12 out for the V510 GPE device I am sure you would become an instant hero to thousands of users...
Click to expand...
Click to collapse
invisiblek will be working on it with me. I have CM11 booting but with some hardware issue and I cannot get my CM12 build to boot yet. I am actually giving him my v510 so he can finish up the build. I am maintaining the d850 and just don't have enough time right now to continue with the v510.
I would say CM12 for the v510 in a week.

AndroidUser00110001 said:
invisiblek will be working on it with me. I have CM11 booting but with some hardware issue and I cannot get my CM12 build to boot yet. I am actually giving him my v510 so he can finish up the build. I am maintaining the d850 and just don't have enough time right now to continue with the v510.
I would say CM12 for the v510 in a week.
Click to expand...
Click to collapse
Awesome news! That will open up a whole new world for kernel development too. Really looking forward to it. Thank you for your hard work. Takes hours/days to get there.

AndroidUser00110001 said:
invisiblek will be working on it with me. I have CM11 booting but with some hardware issue and I cannot get my CM12 build to boot yet. I am actually giving him my v510 so he can finish up the build. I am maintaining the d850 and just don't have enough time right now to continue with the v510.
I would say CM12 for the v510 in a week.
Click to expand...
Click to collapse
This would definitely be great for the GPE! Looking forward to updates...

Any news on getting CM12 out for the V510 GPE, fingers crossed…

The device tree page won't come up. The link is broken.

AndroidUser00110001 said:
invisiblek will be working on it with me. I have CM11 booting but with some hardware issue and I cannot get my CM12 build to boot yet. I am actually giving him my v510 so he can finish up the build. I am maintaining the d850 and just don't have enough time right now to continue with the v510.
I would say CM12 for the v510 in a week.
Click to expand...
Click to collapse
Bump: Any Status or Beta's??

Data partition F2FS on stock?

Hell, I've decided to restore stock on my Moto and sell it, as I'm pretty sure I'm going to settle with the OnePlus One I also got with their offers.
I think I recall while flashing ROMs for this device I had to reformat Data to EXT4, but now when I go to change the FS again I don't have option for F2FS.
Could one of you please load up recovery, go into Wipe > Advanced Wipe > check "Data" choose "Repair or Change File System" and verify what the line "current file system" says for you?
Would be much appreciated.

Shemploo said:
Hell, I've decided to restore stock on my Moto and sell it, as I'm pretty sure I'm going to settle with the OnePlus One I also got with their offers.
I think I recall while flashing ROMs for this device I had to reformat Data to EXT4, but now when I go to change the FS again I don't have option for F2FS.
Could one of you please load up recovery, go into Wipe > Advanced Wipe > check "Data" choose "Repair or Change File System" and verify what the line "current file system" says for you?
Would be much appreciated.
Click to expand...
Click to collapse
Mine says EXT4.

My data partition is on F2FS on stock lollipop.

sivarticus85 said:
Mine says EXT4.
Click to expand...
Click to collapse
Which partition did you check?

divergens said:
My data partition is on F2FS on stock lollipop.
Click to expand...
Click to collapse
I wonder why TWRP does not have option to change to F2FS, I'm using 2.8.4.1

Shemploo said:
I wonder why TWRP does not have option to change to F2FS, I'm using 2.8.4.1
Click to expand...
Click to collapse
I just tried booting TWRP 2.8.4.0 and I don't see an option for F2FS either. Was this available before in older versions of TWRP? I never bother to switch from the stock recovery to TWRP at any point.

Shemploo said:
Which partition did you check?
Click to expand...
Click to collapse
You asked for the Data partition.
I brought it up in the TWRP thread. Maybe someone there can answer this for us.

sivarticus85 said:
You asked for the Data partition.
I brought it up in the TWRP thread. Maybe someone there can answer this for us.
Click to expand...
Click to collapse
divergens said:
I just tried booting TWRP 2.8.4.0 and I don't see an option for F2FS either. Was this available before in older versions of TWRP? I never bother to switch from the stock recovery to TWRP at any point.
Click to expand...
Click to collapse
Yes, it was in a previous version, I remember changing partitions cause of ROM not working.
Its interesting that both of your partitions are different. Did neither of you change them?

Shemploo said:
Yes, it was in a previous version, I remember changing partitions cause of ROM not working.
Its interesting that both of your partitions are different. Did neither of you change them?
Click to expand...
Click to collapse
I never purposefully changed partitions via TWRP, in fact I never have used TWRP on my Moto X yet. All the flashing I have done was with fastboot.
Now that you mention it, I remember my data partition being EXT4 back in kitkat. I don't know if it changed because of lollipop. I did flash a lollipop image from motofirmware at one point. However, then I went back to kitkat using Motorola's official kitkat image and took the OTA to lollipop.

Yeah I never purposefully changed it either. Twrp just doesn't format it to f2fs like it should. I wonder if doing a factory reset from within the stock recovery will revert it back?
Edit: Yeah that did it. Stock recovery reverts it back to f2fs. Verified by checking it twrp again afterward. That's the only way to get back as of right now.

Ha! - I got the same thing, I booted the latest TWRP and checked the partition, it's listed as F2FS, it would seem that 4.4.x is EXT4 and the upgrade to Lollipop changes is to F2FS, very interesting.
UPDATE: It looks like the option to change FS to F2FS is there when you install a theme, I got it under TWRP Materiel theme, but it seems that this might just be a button designed in case the function is introduced as it actually does not convert the FS.
UPDATE2: After loading the Material theme to get the Change FS to F2FS, the log says "mkfs.f2fs binary not found, using rm -rf to wipe"
Seems something is missing from the latest TWRP release?

I think twrp don't have f2fs because its not really cross platform mountable. Ext4 can be mounted easily with windows, Linux or Mac so it makes things easier for "devs", " tweakers" to just have ext4 support.

TWRP can't decrypt /data on CM12.1

I just decided to move to CM12.1 on my Droid Turbo (XT1254) after the 1/27 Snapshot (YOG7DAO3J1) was posted. I am running this with TWRP 2.8.7.0, BHB27 Kernel, and OpenGAPPS 5.1. So far, almost everything has been fantastic and the performance of the device is like night and day compared to the Verizon software.
My problem is that the CM12.1 ROM has my device encrypted to begin with, which is nice but giving me trouble. I can't get into TWRP to install Xposed framework or other .zips via ADB. I have tried the following:
Disabling require password on startup
Changing the password in Android
Changing the password from root ADB shell
Using a pin
Trying "default_password"
Can anyone give me a solution or some advice? Any help is greatly appreciated!

Having same issue with TWRP not recognizing any decryption password given... Any ideas out there? Is TWRP incompatible with Droid Turbo HW Encryption, or ?

P_6 said:
Having same issue with TWRP not recognizing any decryption password given... Any ideas out there? Is TWRP incompatible with Droid Turbo HW Encryption, or ?
Click to expand...
Click to collapse
This thread is kinda old and I assumed nobody really knew what was going on with it either. I ended up just not using the encryption. The first time around mine was encrypted without me knowing, which was the issue. I just wiped all partitions and flashed the ROM again...

I am having a similar issue so i thought i would chime in, despite the older thread. I had a stock ROM that was encrypted and I was able to unlock and root with SunShine fine. Flashed on TWRP 2.8.7 and ran into a "Unable to mount storage. Failed to decrypt data" error. Updated to TWRP 3.0.0 and still have the same issue. Still working through a resolution as the phone is still functional if I just boot normally. When you mentioned you wiped all partitions, what process did you use? If i can just get access to the interal storage I can flash a ROM and be good to go.

Asyt said:
I am having a similar issue so i thought i would chime in, despite the older thread. I had a stock ROM that was encrypted and I was able to unlock and root with SunShine fine. Flashed on TWRP 2.8.7 and ran into a "Unable to mount storage. Failed to decrypt data" error. Updated to TWRP 3.0.0 and still have the same issue. Still working through a resolution as the phone is still functional if I just boot normally. When you mentioned you wiped all partitions, what process did you use? If i can just get access to the interal storage I can flash a ROM and be good to go.
Click to expand...
Click to collapse
So far, the only way I have been able to get encryption working with CM12.1 on the Droid Turbo is to do the folllowing (Note: This assumes you have bootloader unlocked and TWRP installed as your recovery):
Part 0: Make sure you have what you need
1. Stock Droid Turbo Firmware SU4TL for your device
2. The version of CyanogenMod 12.1 that you need. I recommend a Snapshot, but it's up to you.
3. TWRP 3.0.0 or later for your Droid Turbo.
Part 1: Final set up (Yes, we do this first)
1. Download CM12.1 & Download OpenGapps arm for 5.1
2. Wipe device (system, data, cache, internal storage), copy CM12 install zip and opengapps install zip via USB to device.
3. Flash CM12 and OpenGapps in TWRP
4. Set up device how you want it to be (install your apps, set up your accounts, etc).
5. Set whatever lock-screen PIN / Password / Pattern you are going to want on your phone in general!
6. Make a Nandroid backup of your 100% set up phone in TWRP
7. Copy your backup TWRP folder to your PC.
Part 2: Encrypt device and put everything back how we want it.
1. Flash stock Verizon firmware (SU4TL) via Fastboot. Do not flash stock Recovery, but put back TWRP if you did somehow (I use a simple bash script I have attached below).
2. Boot device, go through initial set up, don't download apps (we're going to be wiping the device soon).
3. Make sure your battery is 80%+ charged, and your device is plugged in.
4. Set a password or PIN on your phone.
5. Encrypt your device (this will be fairly fast, as /data is empty, but you should be asked for your encryption password on boot.)
6. Reboot to recovery. TWRP will ask you for your password to decrypt. It should work with no problem.
7. Copy your backed-up TWRP folder with your CM12 install to your device via USB. The TWRP folder goes in the Internal Storage root directory.
8. Still in TWRP (Do not reboot), go to Restore, and select the backup you just copied over. This will replace the stock rom with your CM12 backup.
9. Your CM12 install will be restored, but your device will remain Encrypted.
10. Reboot into CM12. Win.
You will need to decrypt your device every boot with the password that you selected when you initially encrypted your device. Your lock-screen password CAN BE DIFFERENT. That is why I do it this way. I have a fairly long password to decrypt my device on boot-up, but a pattern as my lock screen. That way I can quickly get into my phone during daily use without having to constantly type in a fairly complicated password.

Error 7 on TWRP when flashing SM-t817t with Lineage 14.1

I have a rooted SM-t817t and have been attempting to flash Lineage 14.1 to it through TWRP 3.1.0-1_ashyx.
I have tried to flash with the gts210ltexx and the gts210wifi and the results are the same, receive the Error 7 message.
After reading up on other threads I attempted to alter the script to either tell it that the ROM is for the gts210ltexx or just remove it entirely and still getting the error.
Also attempted to run it without authentication.
I have read that the t817x tablets can be flashed with the t810 ROMs but have had zero success with doing so at this time.
I am unsure how to proceed from this point.

TheBigby said:
I have a rooted SM-t817t and have been attempting to flash Lineage 14.1 to it through TWRP 3.1.0-1_ashyx.
I have tried to flash with the gts210ltexx and the gts210wifi and the results are the same, receive the Error 7 message.
After reading up on other threads I attempted to alter the script to either tell it that the ROM is for the gts210ltexx or just remove it entirely and still getting the error.
Also attempted to run it without authentication.
I have read that the t817x tablets can be flashed with the t810 ROMs but have had zero success with doing so at this time.
I am unsure how to proceed from this point.
Click to expand...
Click to collapse
Format (not wipe) DATA and if that doesn't work FORMAT the system partition.
If neither works then maybe you should use an updated twrp.

ashyx said:
Format (not wipe) DATA and if that doesn't work FORMAT the system partition.
If neither works then maybe you should use an updated twrp.
Click to expand...
Click to collapse
Thank you for the advice, I will update to the latest TWRP and then format the data and try that. Will report back with results.

After formatting the data and updating to the latest TWRP, 3.2.3-1, I come across the same error 7.
Have updated the script filed to make certain no trace of verification exists for the ROM and still receive the error.
Have now attempted at least five different ROMS all with the same results.
The following is a summarized look at the details it gives.
Installing zip file 'lineage.zip'
Checking for Digest file...
Skipping Digest check: no Digest file found
Warning: No file_contexts
detected filesystem ext4 for /dev/block/platform/15540000.dwmmc0/by-name/SYSTEM
Patching system image unconditionally...
E1001: Failed to update system image.
Updater process ended with ERROR: 7
Error installing zip file '/lineage.zip'
Updating partition details...
Failed to mount '/hidden' (Invalid argument)
...done

Update: I have now wiped data but have not yet formatted it. I believe I will need to install Magisk for that.
However based on other recommendations I have come to find out about the encryption on the Samsung storage and that it might be causing the issue.
I have tried to circumvent this by formatting the data into ext2 then back to ext4 and restarting recovery, but so far this has not worked. The error 7 message persists regardless.
Will come back with further updates.

TheBigby said:
Update: I have now wiped data but have not yet formatted it. I believe I will need to install Magisk for that.
However based on other recommendations I have come to find out about the encryption on the Samsung storage and that it might be causing the issue.
I have tried to circumvent this by formatting the data into ext2 then back to ext4 and restarting recovery, but so far this has not worked. The error 7 message persists regardless.
Will come back with further updates.
Click to expand...
Click to collapse
You didnt read my previous post correctly.
You don't need Magisk to FORMAT DATA.
The FORMAT DATA button is right there under the wipe options.
However what you did would have formatted DATA anyway.
Now do the same for the system partition after formatting DATA.
Do not reboot just check DATA and SYSTEM can be mounted then try and install the zip again.

ashyx said:
You didnt read my previous post correctly.
You don't need Magisk to FORMAT DATA.
The FORMAT DATA button is right there under the wipe options.
However what you did would have formatted DATA anyway.
Now do the same for the system partition after formatting DATA.
Do not reboot just check DATA and SYSTEM can be mounted then try and install the zip again.
Click to expand...
Click to collapse
Formatted the data and the system. Verified they were both mounted. Then attempted to flash the ROM.
Error 7 message still appearing. As does the unable to mount hidden.

TheBigby said:
Formatted the data and the system. Verified they were both mounted. Then attempted to flash the ROM.
Error 7 message still appearing. As does the unable to mount hidden.
Click to expand...
Click to collapse
What device is the ROM intended for?

ashyx said:
What device is the ROM intended for?
Click to expand...
Click to collapse
Have tried multiple ROMs, all intended for either the t810 or the t815. They include Lineage, Resurrection Remix, Paranoid Android, AOSP, and a couple more besides.

TheBigby said:
Have tried multiple ROMs, all intended for either the t810 or the t815. They include Lineage, Resurrection Remix, Paranoid Android, AOSP, and a couple more besides.
Click to expand...
Click to collapse
It may be that the system partition sizes are different?

Unknown. I have tried reflashing the stock firmware and that still failed in Odin.
I have given up at this point and restored from a backup. Thanks for the help however.

Same issue with Lineage 15.1

TheBigby said:
I have a rooted SM-t817t and have been attempting to flash Lineage 14.1 to it through TWRP 3.1.0-1_ashyx.
I have tried to flash with the gts210ltexx and the gts210wifi and the results are the same, receive the Error 7 message.
After reading up on other threads I attempted to alter the script to either tell it that the ROM is for the gts210ltexx or just remove it entirely and still getting the error.
Also attempted to run it without authentication.
I have read that the t817x tablets can be flashed with the t810 ROMs but have had zero success with doing so at this time.
I am unsure how to proceed from this point.
Click to expand...
Click to collapse
Can you share root procedure for the sm-t817t my roommate has one for sale, I'll only buy it if I can root it though.

twrp-3.6.1_11-1_gta4xlwifi para galaxy tab s6 lite ONEUI ONLY

twrp-3.6.1_11-1_gta4xlwifi
Descarga
twrp-3.6.1_11-1_gta4xlwifi.img | by Tickbaby for Galaxy Tab S6 Lite
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
en tar
twrp-3.6.1_11-1_gta4xlwifi
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com

Someone tested?

Yes and works

ARIES4RR said:
Yes and works
Click to expand...
Click to collapse
How did you install it? I tried zipping it to a tar file with 7-zip and flashing it from AP with Odin but that didn't work.
Never mind. Got it with fastboot. But backup fails and that's my reason for wanting TWRP.

Change the name TWRP-3.6.1_11-1_GTA4XLWIFI.IMG by
recovery.img
and create.
recovery.tar
and pass it with Odin

ARIES4RR said:
Change the name TWRP-3.6.1_11-1_GTA4XLWIFI.IMG by
recovery.img
and create.
recovery.tar
and pass it with Odin
Click to expand...
Click to collapse
I didn't rename it, so that's why it didn't work with Odin. But as I said, I managed to flash it with fastboot anyway. But it still won't backup, probably because data is encrypted.

hi

here it is in tar
twrp-3.6.1_11-1_gta4xlwifi
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
pass with odin

Why use TWRP when you have Lineage Recovery? Lineage Recovery is better.

Backup option work?

Plzz make for LTE variant

Just made a version for the LTE variant (modified prop.default).
Issues I've found:
Encrypted data partition can't be mounted.
LineageOS fails to install ota updates, because update zip is stored in data partition.
Backup option is not working correctly unless data are decrypted.
Mind the gapps installer fails because it can't mount system_ext partition.
Tested on my SM-P615.

Stelios333 said:
Just made a version for the LTE variant (modified prop.default).
Issues I've found:
Encrypted data partition can't be mounted.
LineageOS fails to install ota updates, because update zip is stored in data partition.
Backup option is not working correctly unless data are decrypted.
Mind the gapps installer fails because it can't mount system_ext partition.
Tested on my SM-P615.
Click to expand...
Click to collapse
#3 I would much prefer to have backup than encrypted data, if that were an option. Is there a way to keep LOS from re-encrypting data? I know that in earlier versions, once you formatted the data partition, it didn't get encrypted again unless you flashed a stock ROM. Or is this a GSI thing?

To prevent lineageos from re-encrypt data open /vendor/etc/fstab.exynos9611 in an text editor, find a line which starts with "/dev/block/platform/13520000.ufs/by-name/userdata" and remove
fileencryption=aes-256-xts parameter (don't forget to remove also the comma!).
WARNING: That should be done after wiping. The instructions are device specific!

Stelios333 said:
To prevent lineageos from re-encrypt data open /vendor/etc/fstab.exynos9611 in an text editor, find a line which starts with "/dev/block/platform/13520000.ufs/by-name/userdata" and remove
fileencryption=aes-256-xts parameter (don't forget to remove also the comma!).
WARNING: That should be done after wiping. The instructions are device specific!
Click to expand...
Click to collapse
Let me see if I have the steps right. I already have LOS up and running. I flash TWRP and boot to it. Then format the data partition to get rid of encryption. Then edit as per the above and reboot. Is that right?

This is why Linux4 abandoned TWRP for the platform. TWRP seems so problematic! Everyone should switch back to Lineage Recovery. Data is encrypted for good reason on the devices. You don't need a backup option in recovery plus why use TWRP when you can use an official looking recovery? OTA updates on LOS Recovery aren't hideous with logs and it looks official and fits with Lineage! Use Lineage Recovery, NOT this crap excuse of a recovery. Lineage Recovery can be found on the official lineage website for the official version of 19.1 and the unofficial version for unofficial 19.1 can be found at lineage.linux4.de

SamDungUser said:
This is why Linux4 abandoned TWRP for the platform. TWRP seems so problematic! Everyone should switch back to Lineage Recovery. Data is encrypted for good reason on the devices. You don't need a backup option in recovery plus why use TWRP when you can use an official looking recovery? OTA updates on LOS Recovery aren't hideous with logs and it looks official and fits with Lineage! Use Lineage Recovery, NOT this crap excuse of a recovery. Lineage Recovery can be found on the official lineage website for the official version of 19.1 and the unofficial version for unofficial 19.1 can be found at lineage.linux4.de
Click to expand...
Click to collapse
You do it your way and I'll do it mine. I DON'T LIKE LOS RECOVERY!! And I DO NEED the backup option, thank you very much.

lewmur said:
You do it your way and I'll do it mine. I DON'T LIKE LOS RECOVERY!! And I DO NEED the backup option, thank you very much.
Click to expand...
Click to collapse
TWRP is unsuitable for the device because /data is encrypted therefore backup won't work and decrypting data is unsafe.

SamDungUser said:
TWRP is unsuitable for the device because /data is encrypted therefore backup won't work and decrypting data is unsafe.
Click to expand...
Click to collapse
I guess you neglected to read the post that tells you how to keep LOS from re-encrypting the data partition. I DON'T WANT IT ENCRYPTED!! I have been using Android devices for close to a decade without encryption and have NEVER had a problem. I have a belt. I don't need suspenders too. (And LOS when it was Cyanogenmod.)

lewmur said:
I guess you neglected to read the post that tells you how to keep LOS from re-encrypting the data partition. I DON'T WANT IT ENCRYPTED!! I have been using Android devices for close to a decade without encryption and have NEVER had a problem. I have a belt. I don't need suspenders too. (And LOS when it was Cyanogenmod.)
Click to expand...
Click to collapse
Due to the issues with TWRP, Linux4 might block your recovery from being able to install LOS.