Lineage 14.1 encryption - Honor 5X Questions & Answers

Lineage 14.1 encryption - Honor 5X Questions & Answers

So I know CM 13 used full disk encryption. With Android 7.0 file based encryption was introduced. Does anyone know if the new Lineage 14.1 uses full disk encryption or the newer file based encryption. I'm full disk encrypted right now but I'd happily start over with file based encryption if that is the case.

Not sure about this but can you can recovery working when using encryption in CM13? TWRP for me just says cannot mount data

Since it's nougat, it is probably file based encryption

Since they usually just pull down commits from upstream to the CM14 source, I'm pretty sure that yes indeed, file based encryption is in use.

Related

Custom Lineage based roms and full disk encryption

Is it possible to encrypt using any of the custom roms? I have tired Lineage, CrDroid and DotOs and when i encrypt phone, it never finishes encrypting and doesn't boot any more.
Is this something to do with these being Treble roms?

I'm about to buy the Xiaomi Redmi Note 5 Plus, but lack of encryption would be a show-stopper for me. Encryption doesnt work, even for Lineageos 14 ? (android 7).
I'm not sure of the statuses of Lineageos 14/15, just looking into it right now. I can live with LineageOS 14 for now, but not without encryption.

Mee too. Unable to find Custom ROM ENCRYPTED. It seems nobody concerned about encryption. Original ROM (MIUI9) is encrypted by default with File Based Encryption (FBE). A phone without encryption is called "a public phone". Is Treble causing trouble or TWRP need TWRP-FBE? Anyone success in encryption please create a thread "List FBE ROM including TWRP-FBE."

I found the solution.
Format data using TWRP, then resize the partition with adb shell :
resize2fs /dev/block/mmcblk0p50 51G
(my original size of filesystem /dev/block/mmcblk0p50 was 52.1G (you can find it with the command "df -h /dev/block/mmcblk0p50")
The encryption process need to take some place at the end of the partition or it will fail - this thread has helped me : github.com/CyanogenMod/android_device_motorola_xt907/issues/3
You can debug also the problem with the adb logcat command.

[SM-T825][UNOFFICIAL] 20180911 Treble Project

I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
If you want to check firmware - please make backup. Better to store all partitions, at least efs and may be modem.
As we all know - the tablet does not support treble. And we do not have a separate partition, with enough space (about 450mb) to place the whole vendor there.
As a result, I created a solution and tried to make it as much easy as possible for daily use.
I created 2 files - system.img/vendor.img as ext4 images and put it in to the system partition. And then on early init I mounting real system partition as /system_src and then mount system.img as /system and vendor.img as /vendor.
Also I created twrp treble's version for easy use /system and /vendor. It's can wipe new system\vendor partitions, you can restore images to system/vendor in the same way, as we use for boot/recovery.
How to
Prepare - need only once
1. in the current twrp make full wipe (at least we need clean /system, because later we fill all /system by 2 files: system.img/vendor.img)
2. you need flash my twrp with treble support (sm-t825-twrp_3.2.3-0_treble.img): https://drive.google.com/file/d/1GJMrHI4wkePXh8JmF_jgxBSly38B5tu1/view?usp=sharing
3. flash zip with new system.img/vendor.img as ext4 images: https://drive.google.com/file/d/14lwrnM85CoxcpjTUiJ0yfbGHXLa7k0DB/view?usp=sharing
Installation
1. download treble zip from Links and flash it as usual zip. It will flash boot.img and /vendor partition (this is part, specific for our tablet only)
2. download any treble system (64bit System A-only) image from: https://forum.xda-developers.com/project-treble/trebleenabled-device-development, if it not a .img file - extract it, then copy to sdcard/extsd card and then flash image as system_image in twrp (Install - switch to Install Image and flash as System Image)
3. some images require vendor's modification, in oreo some firmware has a 90 rotate, some 270, in my treble zip 90, if you see - image rotated on 180 - flash zip from Additional Links
4. if you wanna back to original lineage\rr without treble - you need flash normal twrp version and make full wipe or just flash stock firmware via odin
Known Issues
sound 2 skeakers only for now
fingerprint
keys light dnw on some firmwares
Links
2. 20180911: fix rotate, back to stock sound (fix bt, quad speakers): https://drive.google.com/file/d/1e_mzosWYL7bv29n613OKZpvSZPXMh26k/view?usp=sharing
1. 20180802: initial treble: https://drive.google.com/file/d/14lwrnM85CoxcpjTUiJ0yfbGHXLa7k0DB/view?usp=sharing
Few notes about item 2: your tablet has wrong image orientation, panel horizontal, sensor - vertical, as result troubles with show right image in right orientation. In 7.0-8.1 this problem was fixed by adding ro.sf.hwrotation=270 in build.prop. For pie this way dnw. Google remove this option and update configstore with new ISurfaceFlingerConfigs. It was added new method: primaryDisplayOrientation. Problem was in adding new configstore sources in the 15.1 sources. Finally I had successfully builded configstore 1.0/1.1 from 16.0 in 15.1.
Additional Links - need only for some oreo images, if image rotated on 180
2. 20180911: https://drive.google.com/file/d/1S4mvXFcX-d2xoZEp9b9dG3ywUhybT6U2/view?usp=sharing
1. 20180802: initial fix rotate: https://drive.google.com/file/d/1JKGu7vudrU0bJPEdkGwBVFkyCJpsHLLs/view?usp=sharing
Magisk
For some reason original Magisk dnw with our treble. It's somehow connect to sepolicy and I'm almost sure about it connected to our treble way with loop0/loop1 mount.
Finally I made small update of the original latest Magisk and it's working. Only one thing was done by me: inside zip in the binary magiskinit file I remove seclabel (seclabel u:r:magisk:s0) for magisk services.
Fixed 17.1 Magisk beta: https://drive.google.com/file/d/1lMhM8ceaJoy5pHRHjCsxxG2C9e5sB5Ot/view?usp=sharing
17.1 Magisk beta manager (this apk also inside Magisk, but cann't be installed automatically during Magisk install), install it as normal apk after install Magisk: https://drive.google.com/file/d/1qCoVPUxvvxopCGfIpoHdAnKueNIxMXal/view?usp=sharing
GApps
https://opengapps.org
Almost all firmware say about wrong vendor version. This is normal, just press OK.
Checked firmwares
AospExtended (need rotate 270 patch): https://forum.xda-developers.com/pr...evelopment/rom-aospextended-rom-v5-5-t3797509
Cosmic-OS: https://forum.xda-developers.com/pr...ment/cosmic-ospulsar8-1-0201805243-2-t3794806
DroidOnTime: https://forum.xda-developers.com/pr...pment/official-droidontime-dotos-2-x-t3794338
Havoc-OS: https://forum.xda-developers.com/pr...-device-development/rom-havoc-os-8-1-t3819050
Lineage: https://forum.xda-developers.com/pr...evice-development/lineage-phh-treble-t3767690
OmniROM Treskmod (need rotate 270 patch): https://forum.xda-developers.com/pr...development/rom-8-1-omnirom-treskmod-t3818188
Pixel Experience (it's requere register custom firmware): https://forum.xda-developers.com/pr...e-development/8-1-0-pixel-experience-t3796011
Resurrection Remix: https://forum.xda-developers.com/pr...opment/resurrection-remix-phh-treble-t3767688
let's experiment together!

Wow! Man, you rock! My Favourite dev! Thanks for Your hard work!

Thanks for this. One question, do we use A/B or A images?

Peeps1513 said:
Thanks for this. One question, do we use A/B or A images?
Click to expand...
Click to collapse
Forgot: system a only

Valera1978 said:
Forgot: system a only
Click to expand...
Click to collapse
And what did You think about the bugs You have mentioned? (Fingerprint, deepsleep, speakers) Fixable or not?

deepsleep, speakers - this is the common tab s3 problems (same in the original lineage), a bit later will back to it.
fingerprint - need to check, in the treble mode shim libs dnw because of linker in the system, also service from vendor don't see libs in system - i.e. some limitations. For camera I made workaround: launch second cameraserver service with my shim lib in environment, but this way dnw for fingerprint. It should be something easy to fix, but I still don't see it.

Valera1978 said:
deepsleep, speakers - this is the common tab s3 problems (same in the original lineage), a bit later will back to it.
fingerprint - need to check, in the treble mode shim libs dnw because of linker in the system, also service from vendor don't see libs in system - i.e. some limitations. For camera I made workaround: launch second cameraserver service with my shim lib in environment, but this way dnw for fingerprint. It should be something easy to fix, but I still don't see it.
Click to expand...
Click to collapse
Really appreciate your work :highfive:

Nice project. Good stuff.

I finally settled on HAVOC after much playing around but am facing an issue trying to install magisk (16.7), no success yet . When I searched [ROM][TREBLE] Havoc-OS 8.1 it seems that magisk has been installed on other devices so could it be a vendor issue? Any help would be appreciated. phh supersu seems to be fine though.

Peeps1513 said:
I finally settled on HAVOC after much playing around but am facing an issue trying to install magisk (16.7), no success yet . When I searched [ROM][TREBLE] Havoc-OS 8.1 it seems that magisk has been installed on other devices so could it be a vendor issue? Any help would be appreciated. phh supersu seems to be fine though.
Click to expand...
Click to collapse
Yep. I've tested treble but no sucess atm for me. Better stay with non-treble lineage, as most of the things work just fine. Maybe in future if Valera fix some things on treble bulid (if ever). Hope Dev focus on oreo lineage than treble project (which is good stuff, but not good enough as daily driver)

I want to leave a feedback after almost a month with treble roms
I have to change my mind: treble is fantastic! Such a great thing, very helpfull for all of us. I was running Valera's lineage 15.1 as daily driver for about 2 months.
In regular non-treble bulid almost everything work. Bad thing were performance (slow animations) and not working deepsleep.
I was happy but not at al. That wasnt this what i was looking for. Then i found again this thread and again give a try (longer) :fingers-crossed:
I am running now treble omnirom for few weeks. Worst things i find is: magisk did not work (very sad, tried multiple versions with no luck, other users report magisk is working for them) and my bluetooth headphones arent working (probably our side bug too)
In plus: no random reboots, performance is very good, no slow downs, deepsleep problem almost gone (drain 6% overnight connected to wifi)
Didnt find any other bugs
I am really happy now. It would be exelent with magisk and bluetooth audio working
Great job, i stick with treble for now :laugh:

Thanks for your great work, Valera!
Have anyone tried this on SM-T820 (Wi-Fi only version)?

imder said:
Thanks for your great work, Valera!
Have anyone tried this on SM-T820 (Wi-Fi only version)?
Click to expand...
Click to collapse
Work only with T825

Any updates Master?

@Valera1978
Could you PLEASE make this for us left out t820 owners???

How does this rom with Lineage compare to your non-treble build? Any reason to switch if I want to stick with Lineage?

robsmith11 said:
How does this rom with Lineage compare to your non-treble build? Any reason to switch if I want to stick with Lineage?
Click to expand...
Click to collapse
You better wait for Pie relase. Valera is working on it.

suzook said:
@Valera1978
Could you PLEASE make this for us left out t820 owners???
Click to expand...
Click to collapse
Without device this is impossible. Look like somehow vendors is differ in 820/825, and I need device to understand, what is wrong, why vendor from 825 dnw on 820 (except ril, may be gps). It should be something simple. Because on my another samsung's tablet on exynos no diffs at all. Treble for wifi version I had made based on lte version in first attempt.

robsmith11 said:
How does this rom with Lineage compare to your non-treble build? Any reason to switch if I want to stick with Lineage?
Click to expand...
Click to collapse
I'll update non-treble build soon. And treble too. During working on treble I had fixed some stuff, like hexedit finger libs to remove shim lib. But I need fix audio in calls again first.
About pie - I dont see any reason to start work on it right now, it's too early, it still has a lot of problems. Better spend this time to make something cool - may be even make samsung port from note 9 or tab s4 with dex and some stuff.
But if you don't want use treble (I agree, it's may be too complicate with special twrp and additional partitions), I think I can prepare integrated pie system images with simple flash without any additional manipulations, like you flash lineage.

Valera1978 said:
Without device this is impossible. Look like somehow vendors is differ in 820/825, and I need device to understand, what is wrong, why vendor from 825 dnw on 820 (except ril, may be gps). It should be something simple. Because on my another samsung's tablet on exynos no diffs at all. Treble for wifi version I had made based on lte version in first attempt.
Click to expand...
Click to collapse
Man, if you would be somehow able to build a unified or a separate treble rom for 820, you would be the greatest man on xda! Cause we have no support for 820 anymore...

[Project Treble][SM-T580][SM-T585] 20190401

Hi just flashed the new blissrom gsi and everything seems to be good except that the headphone jack is not working. Haven't tried a different gsi yet to see if it happens on them also or if it is a problem with our tablets. By the way this on a sm-t580

twfs said:
Hi just flashed the new blissrom gsi and everything seems to be good except that the headphone jack is not working. Haven't tried a different gsi yet to see if it happens on them also or if it is a problem with our tablets. By the way this on a sm-t580
Click to expand...
Click to collapse
I just flashed Pixel dust on my sm-t580 and the headphone is ignored.
All sounds play thru the speaker just like you didn't install a headphone.
Also the sound settings are ignored, audio playing at full volume.
Even if I changed it to all soft or even off.
The same is with Viper Os.
There is also the problem that you can't install a bigger open gaps because of the partation isn't large enough.
Thanks for the first version for our tablet.

BT audio does not work in all treble firmware

So every time I boot I get a message that says:
There's an internal problem with your device. Contact your manufacturer for details.
Is this normal after flashing Pixel Experience GSI?
Also had this issue with Resurrection Remix as well

thenubknownasepic said:
So every time I boot I get a message that says:
There's an internal problem with your device. Contact your manufacturer for details.
Is this normal after flashing Pixel Experience GSI?
Also had this issue with Resurrection Remix as well
Click to expand...
Click to collapse
I'm guessing that it will happen when your custom ROM is on a different build number from the underlying official build.
Whatever it is, I think you can just ignore it - as long as both are up-to-date, you should encounter no actual errors.
The mismatch is probaly between the build fingerprint mentioned in the build.prop file in the system partition and the build.prop file in the vendor image, specifically the ro.vendor.build.fingerprint key.

RichyE said:
I just flashed Pixel dust on my sm-t580 and the headphone is ignored.
All sounds play thru the speaker just like you didn't install a headphone.
Also the sound settings are ignored, audio playing at full volume.
Even if I changed it to all soft or even off.
The same is with Viper Os.
There is also the problem that you can't install a bigger open gaps because of the partation isn't large enough.
Thanks for the first version for our tablet.
Click to expand...
Click to collapse
I dont know about the headphones, but i have the same problem with audio always at full volume rr gsi

hi how r u
is there any problem with havoc 2.9 please?
any bugs?

Thanks @Valera1978 for this Treble implementation. I am a huge fan of Treble, as it opens a wide range of ROMs to this tablet. Do you continue development on it? It seems come to a stop?
There is another Treble implementation for this Exynos, this is for Galaxy A3 2017 (A320FL). Maybe that can help.

Please could you make a version that supports AB system images?

@Valera1978
Does it support Android 10

this project supports android 10 can someone tell me please

@Chris_0147 the project is dead, you'd better to sell the device. i'll do that also. it's too old and no developer wants to develop anymore something for it. i tried any a10/a11 gsi rom, all are not supported.

I've been looking at previous comments ,OK , I understand it doesn't support 10 and 11 but has anyone tried installing Pie and then upgrading to 10 or 11.

Nope

You can try and tell us

Chris_0147 said:
You can try and tell us
Click to expand...
Click to collapse
Very helpful, I was hoping for something more constructive

[ROM][12.1][UNOFFICIAL][wt88047x] LineageOS 19.1

Important information:
This thread is for LineageOS 19.1 opensource builds for Wingtech WT88047, marketed as Redmi 2 by Xiaomi. The following will not be supported in this thread:
Custom Kernels
Mods
Modified system files
Xposed
Magisk
What's not working:
SELinux Permissive
Encryption
Connecting to some Bluetooth Classic devices
Installation:
If you are on the stock OS, you will first need a custom recovery. You can get the recommended Lineage recovery here.
If you are coming from stock or other ROMs, you need to do a factory reset, and resize your partitions with this tool. It is highly recommended to flash it using ADB sideload.
As always, make sure to backup before installing this ROM.
For more detailed instructions, please visit:
Install LineageOS on wt88047
Download link:
SourceForge
Recommended Google Apps package:
MindTheGapps
Recommended Firmware:
Google Drive
Bug reports:
How to submit a bug report
Gitlab Issues
Donate to support development:
Donate via PayPal to tipzrickycheung
Donate via PayPal to nicknitewolf
Donate via PayPal to LineageOS
Source Code:
Device tree
Kernel
LineageOS Github
Contributors
@tipzrickycheung, @althafvly, @nicknitewolf, Lineage Team
ROM OS Version: 12.x S
ROM Kernel: Linux 3.10.x
ROM Firmware Required: M8936FAAAANUZM-1.33887.1.41528.1
Based On: LineageOS

Reserved

New update!
20220218
- Fixed Bluetooth
- Baseband and IMEI now detected
Download

Perfect Android 12, basically everything works fine, thank you very much for your work.
However, there are also some problems: 1. The size of the "oem partition" is insufficient and needs to be expanded. The expansion zip provided by you cannot be used. 2. Some animations of the settings application are missing, such as the last two pictures. 3. The system time will return to the compile time after restarting.
I can not speak English
Are you in Coolapk?

pinksheer said:
Perfect Android 12, basically everything works fine, thank you very much for your work.
However, there are also some problems: 1. The size of the "oem partition" is insufficient and needs to be expanded. The expansion zip provided by you cannot be used. 2. Some animations of the settings application are missing, such as the last two pictures. 3. The system time will return to the compile time after restarting.
I can not speak English
Are you in Coolapk?
Click to expand...
Click to collapse
Yup, I am on Coolapk

pinksheer said:
Perfect Android 12, basically everything works fine, thank you very much for your work.
However, there are also some problems: 1. The size of the "oem partition" is insufficient and needs to be expanded. The expansion zip provided by you cannot be used. 2. Some animations of the settings application are missing, such as the last two pictures. 3. The system time will return to the compile time after restarting.
I can not speak English
Are you in Coolapk?
Click to expand...
Click to collapse
About the expansion zip, you need to have the stock partition layouts to start with.

New update!
20220219
- Fixed LiveDisplay
- Added SEPolicy Changes
- Added Binder and lmk kernel backports
Note:
Enforcing now boots but adb, camera, baseband, etc. no longer works with enforcing turned on. Builds are still shipped with permissive.
Download

I'm just popping in to say this looks very promising! Thanks for caring about this device. Please don't give up with this build

New update!
20220227
- Fixed Hotspot (Can be fixed for 18.1 too)
- Software navkeys now works properly
Note:
Enforcing now boots but adb, camera, baseband, etc. no longer works with enforcing turned on. Builds are still shipped with permissive.
Download

hi developer wt88047 @tipzrickycheung how fixed for twrp error E2001 : Failed to update vendor image? for flashing build lineageos unofficial 19
now iam dowgrade lineage os unofficiall 18.0 build from @nicknitewolf its work

BangJhon.id said:
hi developer wt88047 @tipzrickycheung how fixed for twrp error E2001 : Failed to update vendor image? for flashing build lineageos unofficial 19
now iam dowgrade lineage os unofficiall 18.0 build from @nicknitewolf its work
Click to expand...
Click to collapse
Use the partition expand package first

pinksheer said:
Perfect Android 12, basically everything works fine, thank you very much for your work.
However, there are also some problems: 1. The size of the "oem partition" is insufficient and needs to be expanded. The expansion zip provided by you cannot be used. 2. Some animations of the settings application are missing, such as the last two pictures. 3. The system time will return to the compile time after restarting.
I can not speak English
Are you in Coolapk?
Click to expand...
Click to collapse
I think I might have fixed bug 3, will push an update when appropriate.

one by one step i try, no fixed this message, from recovery all path, partisi, i not working instal lineage os based 19.0

New update!
20220228
- Fixed TimeKeep (?)
Note:
Enforcing now boots but adb, camera, baseband, etc. no longer works with enforcing turned on. Builds are still shipped with permissive.
Download

Thanks for the release! Today I tried to install this, but I got error 1 in TWRP saying "failed to update vendor image". Is it required to add a dedicated treble vendor partition with this tool? Just asking because this may have to do with the system partitioning otherwise.

RandomNewbie said:
Thanks for the release! Today I tried to install this, but I got error 1 in TWRP saying "failed to update vendor image". Is it required to add a dedicated treble vendor partition with this tool? Just asking because this may have to do with the system partitioning otherwise.
Click to expand...
Click to collapse
No, and we don't support using that tool.

tipzrickycheung said:
Use the partition expand package first
Click to expand...
Click to collapse
I am unable to install the partition expand package that you have provided (resize_wt88047x_v6.zip) on my device. TWRP gives me this error - "Can not extract update-script. Do you have it in package?". I have the 8gb variant. Any help is appreciated!

SaneComputing said:
I am unable to install the partition expand package that you have provided (resize_wt88047x_v6.zip) on my device. TWRP gives me this error - "Can not extract update-script. Do you have it in package?". I have the 8gb variant. Any help is appreciated!
Click to expand...
Click to collapse
Update your TWRP.

New update!
20220323
Android 12L!
Note:
Enforcing now boots but adb, camera, baseband, etc. no longer works with enforcing turned on. Builds are still shipped with permissive.
Download

Still using latest twrp but error show up everytime

TWRP with decryption

I have a problem with the latest TWRP (twrp-3.6.2_9-0-beryllium.img downloaded here: https://eu.dl.twrp.me/beryllium/). When I browse the storage, the `sdcard` folder only has garbled names in it. I found out that this is due to decryption lacking in TWRP. Since TWRP doesn't ask me to decrypt when I boot into recovery, I assume that it's not supported on the version I am using. Is there a version for Android 12 (I use the latest Lineage OS) that supports decryption? Thanks.

nukul4r said:
I have a problem with the latest TWRP (twrp-3.6.2_9-0-beryllium.img downloaded here: https://eu.dl.twrp.me/beryllium/). When I browse the storage, the `sdcard` folder only has garbled names in it. I found out that this is due to decryption lacking in TWRP. Since TWRP doesn't ask me to decrypt when I boot into recovery, I assume that it's not supported on the version I am using. Is there a version for Android 12 (I use the latest Lineage OS) that supports decryption? Thanks.
Click to expand...
Click to collapse
Use TWRP by REIGNZ which support decryption of A12+ encrypted ROMs. Check my collection.

Better Mobile App

welcome