[ROM] [05 JUL 2020] LineageOS-14.1

[DB126]

hmm ...

this doesnt work for me. Updated twrp to 3.1.1-1, wiped the whole System, rebooted and flashed Lineage, Gapps and SuperSu. But the boot-loop still appears.

Edit: with lineageOS 13. its working now. Thanks.

Appreciate the update. You could try returning to Lineage 14.1 or try a different Nougat based ROM. I have been pumping AospExtended (AEX) of late for it's speed, stability and feature set. I'm a longtime CM/Lineage user but AEX provides the best experience on an Android device I have had to date. All the goodness of pure AOSP with a nice set of optional extensions.

 

[jlbrown1]

@ggow,

Any update on Bluetooth? I have tried many different methods, including the ones in this thread, to no avail. The tablet sees the headphones, it just will not pair.

Are there log files somewhere that I could post that would help?

Thanks!

J

 

[DB126]

@ggow,

Any update on Bluetooth? I have tried many different methods, including the ones in this thread, to no avail. The tablet sees the headphones, it just will not pair.

Are there log files somewhere that I could post that would help?

FWIW - I have had no problems pairing a small collection of BT test devices (keyboard, mouse, earbuds, speaker, receiver) on AEX for Thor. Rather surprising as BT connectivity issues have dogged virtually all custom ROMs for HDX devices from Android 5.1 forward. Maybe just got lucky with my portfolio. That said, it's nice not having to switch to my phone to stream music to the home audio setup, etc.

 

[stauraum]

Appreciate the update. You could try returning to Lineage 14.1 or try a different Nougat based ROM. I have been pumping AospExtended (AEX) of late for it's speed, stability and feature set. I'm a longtime CM/Lineage user but AEX provides the best experience on an Android device I have had to date. All the goodness of pure AOSP with a nice set of optional extensions.

I've tested now Lineage 14, AOSP and Slim. All are 7.1-roms. All not working. Reflashed Lineage 13 and now the tablet is working again.

Can the be a problem with the bootloader after selecting "encrypt this device"?

 

[DB126]

I've tested now Lineage 14, AOSP and Slim. All are 7.1-roms. All not working. Reflashed Lineage 13 and now the tablet is working again.

Can the be a problem with the bootloader after selecting "encrypt this device"?

You could try reflashing the vulnerable bootloader but I doubt that will help. In all likelihood one of numerous (over a dozen) 'hidden' partitions was touched by the encryption attempt. At present there is not a comprehensive catalog of contents and, more importantly, a means for restoring back to 'stock'.

@draxie - thoughts?

 

[draxie]

Locked bootloader?

You could try reflashing the vulnerable bootloader but I doubt that will help. In all likelihood one of numerous (over a dozen) 'hidden' partitions was touched by the encryption attempt. At present there is not a comprehensive catalog of contents and, more importantly, a means for restoring back to 'stock'.

@draxie - thoughts?

Given that hashes and signatures are checked before loading
each new stage in the boot process, the bootloader must be
good, if the device is able to boot at all. On the other hand,
based on what works and what doesn't, I'd say the bootloader
is likely locked.

 

[stauraum]

Given that hashes and signatures are checked before loading
each new stage in the boot process, the bootloader must be
good, if the device is able to boot at all. On the other hand,
based on what works and what doesn't, I'd say the bootloader
is likely locked.

Yesterday i've re-unlocked the bootloader. Every output says success. But i'm unable to boot any 7.x Android. hmm ... freaky ...

 

[DB126]

Yesterday i've re-unlocked the bootloader. Every output says success. But i'm unable to boot any 7.x Android. hmm ... freaky ...

I'm sticking with this at least conceptually. Nougat encryption is implemented differently than Android 4.4-6.x and remains a work-in-progress. The link below offers a laymen's perspective on some of the issues and hints at the problem you are currently experiencing. Me thinks the keys (or at least a flag) are resident in an area of permanent storage that remains untouched by standard partition wipes. Android 7.x based ROMs notice that and balk during boot while 6.x and lower ROMs are clueless to the previous device state. Good luck.

https://blog.cryptographyengineering.com/2016/11/24/android-n-encryption/

 

[draxie]

FBE == ext4 encryption

I'm sticking with this at least conceptually. Nougat encryption is implemented differently than Android 4.4-6.x and remains a work-in-progress. The link below offers a laymen's perspective on some of the issues and hints at the problem you are currently experiencing. Me thinks the keys (or at least a flag) are resident in an area of permanent storage that remains untouched by standard partition wipes. Android 7.x based ROMs notice that and balk during boot while 6.x and lower ROMs are clueless to the previous device state. Good luck.

https://blog.cryptographyengineering.com/2016/11/24/android-n-encryption/

OK. So, I've done some reading on the new FBE in Nougat...
https://source.android.com/security/encryption/file-based
https://blog.compass-security.com/2016/10/android-7-0-security-features-direct-boot/
http://www.delaat.net/rp/2016-2017/p45/report.pdf

Based on the above, FBE _should_ only directly affect /data,
(i.e. other partitions _may_ be implicated if the TEE uses them,
but I'm not convinced that matters, since the TEE is consulted
only if FBE is turned on, which is indicated in the filesystem).

On the other hand, the ext4 filesystem needs to be reformatted
to get rid of the FBE flags. I suspect that TWRP does NOT do this.
At least, the feedback it gives (I've just done a _complete_ wipe
of my test Thor, checking _ALL_ available checkboxes) only says
"wiping" for both /data and /data/media, but it says "formatting"
for cache and system...

I'd suggest testing the following **after** making a backup:

adb shell su -c "make_ext4fs /dev/block/mmcblk0p23"

This should not have any adverse effects (beyond obliterating
*all* data on /data *including* /data/media), since Android will
set this up properly again. I've just tested this after verifying
that 'wipe' still left (or re-created) some files on /data...
I sideloaded AEX (since data was pristine, I couldn't push the
ZIP anywhere...) and everything worked as expected.
NB: I have *not* verified that this solves the encryption issue,
only that it won't make things worse...

 

[DB126]

OK. So, I've done some reading on the new FBE in Nougat...

...On the other hand, the ext4 filesystem needs to be reformatted
to get rid of the FBE flags. I suspect that TWRP does NOT do this.
At least, the feedback it gives (I've just done a _complete_ wipe
of my test Thor, checking _ALL_ available checkboxes) only says
"wiping" for both /data and /data/media, but it says "formatting"
for cache and system...

FWIW - TWRP does have the ability format/reformat/resize various partitions including /data. Believe it's buried under the Advance menu. That said, the adb command is probably cleaner/easier/quicker. And safer IMHO as there is no temptation to resize which is usually fatal on Android.

 

[draxie]

Are you sure?

FWIW - TWRP does have the ability format/reformat/resize various partitions including /data. Believe it's buried under the Advance menu. That said, the adb command is probably cleaner/easier/quicker. And safer IMHO as there is no temptation to resize which is usually fatal on Android.

That functionality must have been removed from the version of TWRP I'm using...
The only remotely similar functionality under Advanced in @ggow's 3.1.1-1 build is
Partition SD Card, and when you try to run that with Internal Storage, you get an
error message saying 'You must select a removable device'.

In any case, all I meant was that the Advanced Wipe for Data and Internal Data
does not appear to reformat...

 

[stauraum]

OK. So, I've done some reading on the new FBE in Nougat...
https://source.android.com/security/encryption/file-based
https://blog.compass-security.com/2016/10/android-7-0-security-features-direct-boot/
http://www.delaat.net/rp/2016-2017/p45/report.pdf

Based on the above, FBE _should_ only directly affect /data,
(i.e. other partitions _may_ be implicated if the TEE uses them,
but I'm not convinced that matters, since the TEE is consulted
only if FBE is turned on, which is indicated in the filesystem).

On the other hand, the ext4 filesystem needs to be reformatted
to get rid of the FBE flags. I suspect that TWRP does NOT do this.
At least, the feedback it gives (I've just done a _complete_ wipe
of my test Thor, checking _ALL_ available checkboxes) only says
"wiping" for both /data and /data/media, but it says "formatting"
for cache and system...

I'd suggest testing the following **after** making a backup:

adb shell su -c "make_ext4fs /dev/block/mmcblk0p23"

This should not have any adverse effects (beyond obliterating
*all* data on /data *including* /data/media), since Android will
set this up properly again. I've just tested this after verifying
that 'wipe' still left (or re-created) some files on /data...
I sideloaded AEX (since data was pristine, I couldn't push the
ZIP anywhere...) and everything worked as expected.
NB: I have *not* verified that this solves the encryption issue,
only that it won't make things worse...

COOL! This solved my issue! Many thanks to all of you!

Regards

 

[arshileus]

Hello,

Maybe it's offtopic for here, but i really need to find proper way for rooting kindle fire hdx.
I was looking for in different posts, but can't find.
Please, help me.

 

[DB126]

Hello,

Maybe it's offtopic for here, but i really need to find proper way for rooting kindle fire hdx.
I was looking for in different posts, but can't find.
Please, help me.

Responded to this inquiry in another thread.

 

[ggow]

New Build is Up

- Dated 11 December 2017
- LineageOS upstream
- December security patches

 

[CocoBun]

It says two new touchscreen gesture options have been added for lowering and raising the media volume in the changelog on lineagos.org but how do you get to it? I couldn't find anything about it in settings

 

[DB126]

It says two new touchscreen gesture options have been added for lowering and raising the media volume in the changelog on lineagos.org but how do you get to it? I couldn't find anything about it in settings

Looks like it may not be available for all devices: https://xdaforums.com/lineage/help/media-volume-gestures-t3716236

 

[pxrave]

- Dated 11 December 2017
- LineageOS upstream
- December security patches

Very nice
Thanks again

Any chance to update TWRP too?

 

[ggow]

Very nice
Thanks again

Any chance to update TWRP too?

Yes, I'll be updating twrp soon

 

[TacoLoco]

Are there any plans for Lineage 15.1?