[ROM][UNOFFICIAL][LineageOS][19.1][dragon] -> 2023-01-11 (DISCONTINUED)

[followmsi]

LineageOS 19.1
​

Android 12

lineage-19.1-20230111-UNOFFICIAL-dragon.zip -> DISCONTINUED

Known issues:
- Camera is not working yet.
- SELinux is permissive.
- Our "old" Nivida codecs do have problems to play videos in Chrome-based browsers.
(Rename or remove /vendor/lib/libnvomx.so and reboot system to switch to
software video codecs.)
- Chrome browser starts slowly.
- As it looks like Widevine L1 has been revoked by end of August 2020.
- Maybe more issues ..

Installation:
1. Boot into TWRP
2. Wipe SYSTEM and DATA partitions !
3. Install ROM.zip
4. install gapps (arm64)
5. install Magisk.zip (25.2)
6. Wipe CACHE and DAVLIK
7. Reboot into system

Enjoy 12




Android 11

lineage-18.1-20220216-UNOFFICIAL-dragon.zip -> DISCONTINUED

Known issues:
- SELinux is permissive.
- Our "old" Nivida codecs do have problems to play videos in Chrome-based browsers.
(Rename or remove /vendor/lib/libnvomx.so and reboot system to switch to
software video codecs.)
- Chrome browser starts slowly.
- Camera/Video may stops working after some time in use.
- As it looks like Widevine L1 has been revoked by end of August 2020.

Fresh Installation / Upgrade from any other ROM:
1. Boot into TWRP
2. Wipe SYSTEM and DATA partitions ! (If you are encrypted, pls format DATA partition !)
3. Install ROM.zip
4. install gapps (arm64)
5. install Magisk.zip (21.x)
6. Wipe CACHE and DAVLIK
7. Reboot into system

Upgrade from previous lineage-18.x builds:
1. Boot into TWRP
2. Install ROM.zip
3. Re-Install Magisk 21.x
4. Wipe CACHE and DAVLIK
5. Reboot into system

Enjoy 11




Android 10

lineage-17.1-20201211-UNOFFICIAL-dragon.zip -> DISCONTINUED

Known issues:
- SELinux is permissive.
- Our "old" Nivida codecs do have problems to play videos in Chrome-based browsers.
(Rename or remove /vendor/lib/libnvomx.so and reboot system to switch to
software video codecs.)
- Camera/Video may stops working after some time in use.
- As it looks like Widevine L1 has been revoked by end of August 2020.

system-as-root (SAR)
For gapps installation issues and more information ..
Pls read first .. https://forum.xda-developers.com/showpost.php?p=80693701&postcount=1350

Fresh Installation / Upgrade from any other ROM:
1. Boot into TWRP
2. Wipe SYSTEM and DATA partitions ! (If you are encrypted, pls format DATA partition !)
3. Install ROM.zip
4. install gapps (arm64)
5. install Magisk.zip (20.x+)
6. Wipe CACHE and DAVLIK
7. Reboot into system

Upgrade from previous lineage-17.1 builds:
1. Boot into TWRP
2. Install ROM.zip
3. Wipe CACHE and DAVLIK
4. Reboot into system

- The ROM does contain it's own vendor.img ! (If you go back to Oreo, pls reinstall stock vendor.img)

Enjoy TEN




Android Pie

lineage-16.0-20191017-UNOFFICIAL-dragon.zip -> DISCONTINUED

Known issues:
- Encryption seems not to work - and has not been tested. -> Pls do not encrypt your data partition yet !
- Keymaster -> If you set Pattern, PIN or Password the Screen unlock may not work correctly.
Workaround for Pattern: On fresh boot you will need to wait a bit longer before you enter credentials.
The waiting time is required on fresh boot only, the following unlocks are working normally.
In case of problems pls use Update.ZIP_TWRP_flashable_pattern_pin_remover_V2.zip to remove pattern/pin or password.

Installation:
1. Boot into TWRP (latest available version)
2. Wipe system, cache, dalvik and data partitions ! ( If you have encrypted /data partition - pls "format" /data via TWRP first ! )
3. Install lineage-16.0-201Yxxyy-UNOFFICIAL-dragon.zip
4. Install Opengapps
5. install Magisk.zip (tested with 18.x)
6. Reboot into system ..

- The ROM does contain it's own vendor.img ! (If you go back to Oreo, pls reinstall stock vendor.img)

And big thanks to @NYCHitman1 (Dirty Unicorn) !
Without his work the Android Pie project would not have been possible !


I have uploaded the last official Lineage Oreo build to androidfilehost.com ..
lineage-15.1-20200221-nightly-dragon-signed.zip - -> DISCONTINUED


SOURCES:
https://github.com/followmsi/manifests/tree/dragon-lineage-18.1

DOWNLOADS:
https://drive.google.com/drive/fold...oaU1iazg?resourcekey=0-4krcBcSF3tnMFvgcP4kMvw
https://androidfilehost.com/?w=files&flid=289293

Enjoy LineageOS on your Pixel C .. [/B]

 

[followmsi]

RESERVED

 

[followmsi]

Here you are ..

 

[minieod]

TWRP loop for me. Installs with no errors but won't boot into the os

I did a dirty (coming from AOSP 7.1.2) and then clean install. Haven't factory refreshed yet.

Tried wiping again and flashing back to aosp and having the same issue.

Any thoughts?

edit: now trying to pull some data off my tablet to do a full wipe, i dont NEED to do this, but would like to...but twrp wont recognize MTP on my system (win 10) ... problems problems today

 

[followmsi]

TWRP loop for me. Installs with no errors but won't boot into the os

I did a dirty (coming from AOSP 7.1.2) and then clean install. Haven't factory refreshed yet.

Tried wiping again and flashing back to aosp and having the same issue.

Any thoughts?

edit: now trying to pull some data off my tablet to do a full wipe, i dont NEED to do this, but would like to...but twrp wont recognize MTP on my system (win 10) ... problems problems today

Did you format system ?
Pls do as first step.

If you boot loop install boot.img via fastboot.

No problems here.. it's quite fast !
Also dirty installation .. kept all my settings.

EDIT:
Mtp should work .. correct driver in Windows ?
We are using abd and mtp at the same time.
A Windows driver is on the share as well ..

 

[followmsi]

Made a LineageOMS version as well ..
lineageOMS-14.1-20170418-UNOFFICIAL-dragon-followmsi.zip

Based on LineageOMS sources ...
https://github.com/LineageOMS

Enjoy

 

[Reuben_skelz92]

Made a LineageOMS version as well ..
lineageOMS-14.1-20170418-UNOFFICIAL-dragon-followmsi.zip

Based on LineageOMS sources ...
https://github.com/LineageOMS

Enjoy [/QUOT

Is the nav bar laid out like stock

 

[minieod]

Did you format system ?
Pls do as first step.

If you boot loop install boot.img via fastboot.

No problems here.. it's quite fast !
Also dirty installation .. kept all my settings.

EDIT:
Mtp should work .. correct driver in Windows ?
We are using abd and mtp at the same time.
A Windows driver is on the share as well ..

Hey follow

Yep did all of that. Formatted system, flashed boot.img, and no issues with mtp prior to the boot loops.

I went ahead and did a complete userdata reset and am sampling the O DP1 now ..I'm sure it'll work fine when (if) I come back to 7.x

 

[gaufres]

Officialness

Thanks for building this. Hoping to try it out this weekend.

I'm hoping you intend to submit this build officially to LineageOS, so we continue to get updated builds. As you probably remember Cyanogen didn't accept the Pixel C. Hopefully with LineageOS things are better.

 

[followmsi]

Thanks for building this. Hoping to try it out this weekend.

I'm hoping you intend to submit this build officially to LineageOS, so we continue to get updated builds. As you probably remember Cyanogen didn't accept the Pixel C. Hopefully with LineageOS things are better.

You are not the first asking me this question ..

Here some more information ..
https://wiki.lineageos.org/submitting_device.html

Who is the maintainer ? .. me

- Changing vendor stuff .. monthly
- Applying kernel patches .. monthly
- Applying possible device tree patches and changes .. monthly
- Etc.

Here is the manifest for LOS ..
https://github.com/followmsi/manifests/tree/dragon-lineageos-cm-14.1
Also for the people who like to build their own verison

- As you may see we are removing 2 LOS repos today, due to build errors.
- This needs to be fixed on code level first - commited on LOS github.

- The stock google vendor.img needs to be integrated into the LOS Installer
Still not clear how this is done for "official" lineageos .. also from legal point of view.
Actually I need to get information here ... How is this done for other ROMs having a dedicated vendor.img ?

- The missing integrated kernel building was impemented a few minutes before
https://github.com/followmsi/androi...mmit/316a7e0e87b191bcf11b8de55778ddec83fac2f8
https://github.com/followmsi/android_kernel_tegra/commit/3e3e24c41db74693efc2fc74efaf6286b1c06013

You see there a few issues left ..
The ROM works perfectly but its not ready to be official yet.

Don't want to force and push a go live now .. No need to rush !

Hope you have a better understanding now ..

Cheers

 

[followmsi]

Made a LineageOMS version as well ..
lineageOMS-14.1-20170418-UNOFFICIAL-dragon-followmsi.zip

Based on LineageOMS sources ...
https://github.com/LineageOMS

Enjoy [/QUOT

Is the nav bar laid out like stock

No !

The OMS version is the same like lineageOS but including OMS - to be ready to install substratum .. etc.
Made a version for Nexus 10 as well .. it seems to work fine.

Just have installed the ROM .. works fine - but did no special customizations or anything else.

Hope this helps ..

 

[gaufres]

Debugging bootloop

Did you format system ?
Pls do as first step.

If you boot loop install boot.img via fastboot.

Unfortunately this is also bootlooping for me. I've tried the steps above.

How can I help debug this? I was not able to use logcat. Does logcat work for you?

 

[followmsi]

Unfortunately this is also bootlooping for me. I've tried the steps above.

How can I help debug this? I was not able to use logcat. Does logcat work for you?

You did flash boot.img via fastboot ?
The ROM installation had no errors ?
What version of bootloader are you using .. .50 for 7.1.2 ?
Do you see the LOS logo (boot animation) when you boot-loop ?

Are you able to make a md5 hash ..Or similar to compare ?
File corrupt ?
Pls post a hash value to compare .. maybe onedrive is the problem.
Was not the first time a file was corrupted.

I am testing several ROMs and kernels in the last days .. no problems at all.

EDIT:
Which version of TWRP ?

EDIT2:
For your understanding.. logcat will start a short time after Android is booting.(boot animation)
But if you not pass the boot.img we have another issue. (Google logo)

 

[gaufres]

Re: Debugging bootloop

You did flash boot.img via fastboot ?

Yes. No errors.

The ROM installation had no errors ?

None.

What version of bootloader are you using .. .50 for 7.1.2 ?

I think so. Version 7900.50.0 from n2g47d.

Do you see the LOS logo (boot animation) when you boot-loop ?

It doesn't get that far.

I see the unlocked bootloader warning. After thirty seconds it beeps, as expected. Then white "Google" text is then displayed for two or three seconds.

But after that it reboots into TWRP (blank screen, then unlocked bootloader warning, then beep, then white "Google" text, then TWRP).

Are you able to make a md5 hash ..Or similar to compare ?

The update zip I'm installing from TWRP is lineage-14.1-20170417-UNOFFICIAL-dragon-followmsi.zip, which I downloaded from OneDrive. It has SHA256 hash

d124b4048f096317f593fa5dbf313ceaebbddd4352f0422276a86fd5f6707902

The boot.img I'm flashing with fastboot comes from the above zip. So it might be redundant for me to say the boot.img has SHA256 hash

cde8c7376d2d8d9d35ea5558473a669f91a27b0489f21b7a3cdb79af4a4ba931

Pls post a hash value to compare .. maybe onedrive is the problem.
Was not the first time a file was corrupted.

I'm kinda hoping that is the problem, because otherwise this will be a pain to debug!

I am testing several ROMs and kernels in the last days .. no problems at all.

Good. Weird.

Which version of TWRP ?

Your build of 3.1.0-0.

For your understanding.. logcat will start a short time after Android is booting.(boot animation)
But if you not pass the boot.img we have another issue. (Google logo)

Thanks for the explanation. So it might be boot.img given the boot sequence I described above?

 

[badwiring]

I always get the TWRP bootloop if I boot before installing SuperSU. That happened with DU and with this.
I also had some issues with the setup wizard crashing. It was skipping the step of connecting wifi, and then it would crash when I tried to enter a Google account (which wouldn't have worked anyway without wifi.) I tried different gapps, same result. Finally I managed to swipe open settings and connect to wifi and now I'm set.

Now that I've got it running (OMS variant) it's great.

 

[followmsi]

Yes. No errors.



None.



I think so. Version 7900.50.0 from n2g47d.



It doesn't get that far.

I see the unlocked bootloader warning. After thirty seconds it beeps, as expected. Then white "Google" text is then displayed for two or three seconds.

But after that it reboots into TWRP (blank screen, then unlocked bootloader warning, then beep, then white "Google" text, then TWRP).



The update zip I'm installing from TWRP is lineage-14.1-20170417-UNOFFICIAL-dragon-followmsi.zip, which I downloaded from OneDrive. It has SHA256 hash

d124b4048f096317f593fa5dbf313ceaebbddd4352f0422276a86fd5f6707902

The boot.img I'm flashing with fastboot comes from the above zip. So it might be redundant for me to say the boot.img has SHA256 hash

cde8c7376d2d8d9d35ea5558473a669f91a27b0489f21b7a3cdb79af4a4ba931

I'm kinda hoping that is the problem, because otherwise this will be a pain to debug!



Good. Weird.



Your build of 3.1.0-0.



Thanks for the explanation. So it might be boot.img given the boot sequence I described above?

[HashChecker]
[File]/storage/emulated/0/download/lineage-14.1-20170417-UNOFFICIAL-dragon-followmsi.zip
[MD5]C79F1066186FF36C55643E264B3647E2
[SHA1]4DDD0A811FE22359D745335AA563023E95E808D3
[SHA256]D124B4048F096317F593FA5DBF313CEAEBBDDD4352F0422276A86FD5F6707902

At least the sha256 matches

Good bootloader
Good TWRP version ..

Do you install supersu at last step of your installation procedure ?
After you did install the ROM in TWRP, pls install supersu.zip (2.79 -sr3) as last step.

It will boot twice for the first time .. but then it should boot normally.

 

[followmsi]

I always get the TWRP bootloop if I boot before installing SuperSU. That happened with DU and with this.
I also had some issues with the setup wizard crashing. It was skipping the step of connecting wifi, and then it would crash when I tried to enter a Google account (which wouldn't have worked anyway without wifi.) I tried different gapps, same result. Finally I managed to swipe open settings and connect to wifi and now I'm set.

Now that I've got it running (OMS variant) it's great.

The SetupWizard is related to gapps .. the beans version seems to run perfectly.
Opengapps seems still to have issues on certain devices.

Will check supersu topic ..

Thanks for the feedback !

 

[gaufres]

I always get the TWRP bootloop if I boot before installing SuperSU.

Do you install supersu at last step of your installation procedure ?

Thanks both. That's it.

No su: bootloops.
Lineage extras su: bootloops
SuperSU: boots OK
Magisk: boots OK

 

[followmsi]

Thanks both. That's it.

No su: bootloops.
Lineage extras su: bootloops
SuperSU: boots OK
Magisk: boots OK

Cool !

Found the issues as well ..

It's related to DM-verity .. even some config is missing.
Or the overwrite of build_fingerprint is related.
Need to investigate ..

Both supersu and magisk are removing the DM-verity checks in ramdisk.(boot.img)

As I always install supersu, I never realized.

Just compiling a new version .. changed the sources.
https://github.com/followmsi/androi...mmit/aae5804e75f4133ec82253cf6b2afbe39e46a56a

Removing DM-verity from fstab .. should solve this issue, also without supersu.

At later stage we can enable again, if it's working fine.

Thanks for your help testing ..

Cheers

 

[followmsi]

New release ..

lineage-14.1-20170421-UNOFFICIAL-dragon-followmsi.zip

Changes:
- Integrated kernel compiling - using DU branch
- disabled DM-verity -> should fix proper booting even without supersu/magisk.
- General LineageOS changes -> fresh repo sync from today .. https://download.lineageos.org/

Installation:
1. Boot into TWRP
3. Install lineage-14.1-20170421-UNOFFICIAL-dragon-followmsi.zip
4. install SuperSU-v2.79-201612051815.zip (optional)
6. Reboot into system ..

- The ROM installer will keep your existing gapps installation.
- If you had SuperSu installed before you need to install it again - as we overwrite the boot.img completely.

A new OMS version will come later ..

Enjoy ..