[ROM][UNOFFICIAL][LineageOS][18.1][dragon] -> 2021-04-06

Search This thread

BeniS98

Senior Member
Apr 16, 2018
58
13
8
As far as I know, only Chrome is having an issue taking longer to load than usual. I feel it's gotten better with this last version he realease but still an issue. From my understanding, that is more of a google apps issue rather than the LOS rom. Not 100 though at this time.
But why other ROMs does not have this issue. Does not sound like a Google issue.
 

m+a+r+k

Senior Member
Aug 29, 2013
331
80
58
Highlands, Scotland
My Pixel C is slow and laggy and driving me nuts. So I replaced it.
Tried Lineage and Pixel Experience.
I want to turn my Pixel C into a Home Hub device and I thought it would be easy with Ambient Mode, but it's not there in either ROM.
Any reason why not?
 

b8842dc0

Senior Member
Nov 11, 2015
157
52
48
Thanks @followmsi for keeping our Pixel C devices going strong. This morning, I upgraded mine to the new lineage 18.1. Using the beta version of OpenGapps 11.0 Everything seems to be working great. I disabled the built-in Chrome browser to avoid issues, which wasn't a problem anyway, as I use Firefox all of the time, already. Nice work!
 
  • Like
Reactions: followmsi

poloxo53

Member
Jun 15, 2012
15
4
23
Hi all,
I'm following this tread since a long time now, used to flash my pixel C with Linageos 15, then 17 and just tried to go to 18.1 as 17.1 is discontinued...
I've made a Dalvik/Cache/system swipe before install but after reboot it ask me for a password to uncrypt the device...but I never set up any password or activated any encryption.
Now I'm a little bit stuck because I don't have access to my data (Storage folder) anymore even with TWRP (3.4.0).
Could you help please ? I'm not very used to pass trought my computer with ADB but if that's the only solution I can try with your good advices. :)
 

Alxoom33

Senior Member
May 18, 2011
4,923
1,751
253
New York
www.sack-ip.com
Hi all,
I'm following this tread since a long time now, used to flash my pixel C with Linageos 15, then 17 and just tried to go to 18.1 as 17.1 is discontinued...
I've made a Dalvik/Cache/system swipe before install but after reboot it ask me for a password to uncrypt the device...but I never set up any password or activated any encryption.
Now I'm a little bit stuck because I don't have access to my data (Storage folder) anymore even with TWRP (3.4.0).
Could you help please ? I'm not very used to pass trought my computer with ADB but if that's the only solution I can try with your good advices. :)
Update your TWRP recovery. Your's is out of date.😄
 
  • Like
Reactions: followmsi

poloxo53

Member
Jun 15, 2012
15
4
23
Thank for your advices, I've updated the Recovery but still the same issue yesterday.
Then I tried to flash password-pin-erase.zip but it didn't work on the first reboot just after... but only after 2 or 3 reboot later...
So I managed to get back my data to save it and then to make a factory reset.

Anyway the test with "default_password" as password didn't worked either.

In the meantime I tested Pixel Experience but doesn't managed to get it work as all system applications stop working on first boot, generating a lot of popup and make the tablet impossible to use.
I'll try again to flash Lineage 18.1 from @followmsi with Gapps included at 1st and the nupdate to last version.
 

bra1niac

Senior Member
Jan 26, 2018
56
17
8
Samsung Galaxy Tab S5e
Is anyone having trouble updating magisk since the Feb 6th release of 18.1? I get "unable to detect target image" when updating from within the magisk app. I just want to know whether or not its just me before I dig deeper into Magisk.
 

ipdev

Senior Member
Feb 14, 2016
1,262
1,343
153
Is anyone having trouble updating magisk since the Feb 6th release of 18.1? I get "unable to detect target image" when updating from within the magisk app. I just want to know whether or not its just me before I dig deeper into Magisk.
The new version of Magisk has some issues.

There are quite a few "I did not read or search before I posted this." and "Me too." posts.
If you dig though them, you find some devices had issues while others had no issues with the update.

That being said, if you tried the direct install method and received an error. You have now have a broken boot image.
You will need to install an older magisk patched or a stock boot image from the rom you are using.

Then use the Magisk app to patch your boot.img file.
Magisk and Manager were merged, it is now just Magisk.

Then fastboot boot the new patched boot image to make sure it works.
If it works you can then fastboot flash it or install it with TWRP.

The problem seems to be related to MagiskHide.
If you unhide the Magisk app (what was called Manager) and toggle MagiskHide off, you should not have an issue patching a boot.img file of using the direct install method.
You can hide the Magisk app and toggle MagiskHide on after the update.

Cheers. :cowboy:
 

brackenhill_mob

Senior Member
Aug 3, 2005
235
40
58
Berkhamsted
Is anyone having trouble updating magisk since the Feb 6th release of 18.1? I get "unable to detect target image" when updating from within the magisk app. I just want to know whether or not its just me before I dig deeper into Magisk.
If you are trying to update to v22 be aware that you cannot do this from within the app. You need to download the APK file and rename it to have a .zip extension then flash this from within twrp.

It's working well on my Pixel :)
 

poloxo53

Member
Jun 15, 2012
15
4
23
After some more attempts I finally managed to get 20201230_lineageos 18.1 more or less working on my PixelC...
I said that because YouTube app is closing as soon as I try to open it for instance.
I tried also to upgrade to 20210206 release from @followmsi but I got a bootloop after flashing. So I came back to 1st release.
Is anybody facing the same issue?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 13
    LineageOS 18.1

    Made a quick test build today ..

    Backport of Wifi-Display (Miracst) for Android 11.
    Tested screen mirroring to Samsung TV only.

    And we are testing Android lowmemory killer on 18.1 .. same config like on 17.1 before.

    As said above .. Chrome is still opening slowly .. will take longer to solve this one.

    lineage-18.1-20210315-UNOFFICIAL-dragon.zip

    Changes:
    - Backport of Wifi-Display (Miracst) for Android 11.
    - Switched from Kernel lowmemory killer to Android LMKD.
    - New HWC_composer
    - Some hacks to improve camera/video
    - Patched frameworks/base to support microG

    Enjoy :p
    10
    LineageOS 18.1

    The monthly security updates ..

    lineage-18.1-20210406-UNOFFICIAL-dragon.zip

    Changes:
    - Google Security updates -> April 2021
    - Backport of Wifi-Display (Miracst) for Android 11
    - Patched frameworks/base to support microG
    - Latest LineageOS changes for Android 11

    Enjoy :p
    3
    I had this and Chrome taking over a minute to load and e-mail app and other memory intensive stuff being very slow. I put it down to lack of memory and in the end I gave up as it was unusable and I moved on.
    Pixel C currently being used as a digital photo frame in living room.
    I'd love to turn it into a smart hub but there is no Ambient Mode in this ROM :-(
    I haven't had your chrome issues. Just some slowing down on occasion. Pixel C is still a useful tablet, at least for me.
    3
    Honestly I'm blown away at how usable mine still is, especially as like a forum/browsing device
    I agree! Keep thinking it will break or brick soon and I'll have to move on. But its still going strong!
    3
    Hi all. :D

    My original Pixel C screen finally died awhile ago..

    Recently I took a gamble on a used Pixel C.
    Good price. Small scratch on the screen that is only noticeable when the screen is off (and you are looking for the scratch).

    I got it the other week, unlocked the bootloader and updated it to the last version.
    ryu-opm8.190605.005

    Then did a complete clean install of Lineage 18.1.

    What I normally do is a little over-kill. You can skip the fastboot erase part. ;)

    Boot into bootloader.
    Bash:
    fastboot erase boot
    fastboot erase recovery
    fastboot reboot bootloader
    fastboot erase system
    fastboot flash recovery /home/ip/ip/twrp/twrp-3.5.0_9-0-dragon.img

    Boot into recovery.
    1. TWRP-> Wipe-> Format Data (Type yes) and press enter.
    2. TWRP-> Reboot-> Recovery (Ignore the warning about no system installed).
    3. TWRP-> Wipe-> Advanced Wipe-> (Select all the partitions) and Swipe to Wipe.
    4. TWRP-> Reboot-> Recovery (Ignore the warning about no system installed).
      The last reboot to recovery basically just cleans up so you start with a nice clean recovery log.​

    All partitions are clean and formatted properly.
    Save for boot, there is no option in TWRP to erase the boot partition.
    Boot will be replaced when a new rom is flashed so not a big deal.

    Install rom. (Using ADB Sideload)
    1. TWRP-> Advanced-> ADB Sideload-> Swipe to Start Sideload.
      adb sideload lineage-18.1-20210206-UNOFFICIAL-dragon.zip
    2. TWRP-> Advanced-> ADB Sideload-> Swipe to Start Sideload.
      adb sideload open_gapps-arm64-11.0-stock-20210130-UNOFFICIAL_TEST.zip
    3. TWRP-> Advanced-> ADB Sideload-> Swipe to Start Sideload.
      adb sideload magisk-debug.zip
      Magisk canary 21410. app-debug.apk renamed to magisk-debug.zip
    4. Reboot to system.

    Then updated Magisk.

    Update to Magisk 22001
    Updated Magisk app.
    - Update Magisk -> Direct install method failed.
    - Update Magisk -> Patch boot image worked.

    Fastboot booted the magisk patched image to test.
    It booted and Magisk was 22001. (Temporary)
    I was then able to used the Direct install method to install.


    Then updated ROM to the 20210304 build.


    Boot into recovery.
    1. TWRP-> Advanced-> ADB Sideload-> Swipe to Start Sideload.
      adb sideload lineage-18.1-20210304-UNOFFICIAL-dragon.zip
      OpenGApps and Magisk backup scripts ran, no need to manually reflash them.​
    2. Reboot to system.

    Clearing the caches before rebooting to system is generally not necessary.
    If you have an issue with a cached file then clear the cache(s).
    Cache(s) are rebuilt on boot so, it will add a little bit to boot time as the caches are being built.

    The Magisk backup script was installed when I originally flashed 21410 in TWRP.
    Using the direct install method or using fastboot to flash the patched boot image, will not install the backup script.


    The next two Magisk update did not go so well.

    Update to Magisk 22003 (and 2204)
    Updated the Magisk app.
    - Update Magisk -> Direct install method failed.
    - Update Magisk -> Patch boot image worked.

    Fastboot booted the magisk patched image to test.
    It booted and Magisk was current. (Temporary)
    - Update Magisk -> Direct install method failed.
    - Used fastboot to flash the patched boot image to the device.


    ---

    I have a question about the codecs.
    I know there was an issue with Netflix when they were purging old device from the L1 certified list.

    What is currently not working using the Nvidia Hardware codec?

    This last week I streamed shows and movies with:
    • Amazon Prime Video
    • HBO Max
    • Netflix

    I did not have an issue streaming.
    I normally used for two to three hours at a time. Even four hours, I still had no issues.

    Cheers all. :cowboy:

    PS.
    I use personal builds of OpenGApps.
    [ROM][flo|deb][UNOFFICIAL][LineageOS 18.1] -> 2021-01-06 xda thread - Post 3,267 - Link

    Feel free to use is you want. :)

    PPS.
    I am currently back on ryu-opm8.190605.005 for testing Magisk patching issue.
    There are a bunch of oddities with 2204 and this device.
  • 61

    EmPczMv.png

    LineageOS 18.1

    Android 11

    lineage-18.1-20210406-UNOFFICIAL-dragon.zip

    Known issues:
    - SELinux - we are still permissive !
    - Our "old" Nivida codecs do have problems playing videos in Chrome browser.
    - As it looks like Widevine L1 has been revoked by end of August 2020.
    - MAC address is fixed and device specific MAC will be ignored.
    - Maybe more .. ?

    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 :p




    Android 10

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

    Known issues:

    - Encryption seems to work .. needs more testing.
    - Camera/Video may stops working after some time in use.
    - SELinux - we are still permissive !
    - MAC address is fixed and device specific MAC will be ignored.
    - Our "old" Nivida codecs do have problems playing videos in Chrome browser.
    - 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 :p




    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/folders/0By6p5AdQfavBUTZmNWJoaU1iazg
    https://androidfilehost.com/?w=files&flid=289293

    Enjoy LineageOS on your Pixel C .. :)
    23
    Android 10 - July 2020

    lineage-17.1-20200707-UNOFFICIAL-dragon.zip

    Changes:
    - Google security updates -> July 2020 (android-10.0.0_r40)
    - Patched framework/av to bring back "wifi-display" in android 10.
    - Patched framework/base to support microG
    - Latest LineageOS changes for Android 10

    The ROM does contain it's own vendor.img !

    Enjoy the summer :p
    21
    Android 10 - August 2020

    lineage-17.1-20200804-UNOFFICIAL-dragon.zip

    Changes:
    - Google security updates -> August 2020 (android-10.0.0_r41)
    - Patched framework/av to bring back "wifi-display" in android 10.
    - Patched framework/base to support microG
    - Latest LineageOS changes for Android 10

    The ROM does contain it's own vendor.img !

    Enjoy the summer :p
    17
    Android 10 - November 2019

    Still no go for Camera .. will take longer.
    Tested with opengapps beta (11/05) and Magisk 20.1 ..

    lineage-17.0-20191107-UNOFFICIAL-dragon.zip

    Changes:
    - Google security updates -> November 2019 (10.0.0_r11)
    - Latest LineageOS changes for Android 10 -> still a lot of lineage stuff is missing.

    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

    The ROM does contain it's own vendor.img !

    Enjoy :p
    16
    Android 10

    Vukan API is fixed now .. had to take prebuilt libs from Nivida shield firmware. :)
    Lineage has shipped trebuchet launcher .. and some more (minor) changes.

    lineage-17.0-20191025-UNOFFICIAL-dragon.zip

    Changes:
    - Fixed Vulkan API
    - Added new health HAL and more changes .. thanks to @NYCHitman1
    - Latest LineageOS changes for Android 10 -> still a lot of lineage stuff is missing.

    The ROM does contain it's own vendor.img !

    Enjoy :p
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone