[ROM][UNOFFICIAL][LineageOS][18.1][dragon] -> 2021-05-05

Search This thread

ipdev

Recognized Contributor
  • Feb 14, 2016
    1,320
    1
    1,462
    Google Nexus 10
    Nexus 7 (2013)
    Does your build include resizing of the system partition, or should this still be done before flashing Gapps from within TWRP?
    The post I linked to was in a thread for a different device.
    For Nexus 7 (2013) [deb/flo] you have to (re)partition to install newer roms.

    That was the post I gave a link to my fork of OpenGApps and a link to downloads.
    A bit cleaner and easier to keep one post updated instead of posting links and notes across threads.

    Installing GApps (OpenGApps, BitGApps, NikGApps, MindTheGapps, ..) has nothing to do with resizing.

    Resizing, if needed, happens when a rom is installed.
    Partitioning is different from resizing an image.

    When you flash an image in recovery it basically restores a backup to a specific partition. As long as the image is equal to or smaller than the partition, it will restore the image. If the image is smaller than the partition it is being restored to, there is unused/extra space in the partition. To make the extra space available, you have to resize (expand) the image to use the whole partition space.

    When you wipe/format a device you are just erasing what is stored in the partition.

    The only time a partition size changes is if you manually change them.
    Once the partition for system is (re)partitioned to say 1.2G, it will always have 1.2G allocated for system even if the system image you flash is only 850M. System will only have 850M available since the rest of the (system partition) is unallocated. So you have to resize system to fill the whole (system partition) to be able to use the 1.2G space allocated.


    Pixel C [Dragon] is built using the stock partition sizes.
    No need to partition or resize.
    followmsi - android_device_google_dragon (BoardConfig - Line 72) - GitHub - Link

    Dragon has a 3.5G system. ;)
    LineageOS 18.1 only uses 1.2G (1263M) leaving the rest of system free for Gapps.

    Cheers. :cowboy:
     

    j04nd03

    Member
    Nov 9, 2015
    28
    8
    Installing GApps (OpenGApps, BitGApps, NikGApps, MindTheGapps, ..) has nothing to do with resizing.

    [..]

    Pixel C [Dragon] is built using the stock partition sizes.
    No need to partition or resize.

    [..]
    Dragon has a 3.5G system. ;)
    LineageOS 18.1 only uses 1.2G (1263M) leaving the rest of system free for Gapps.

    Cheers. :cowboy:

    Thanks for the clarification.

    I wasn't sure because here you wrote
    "LineageOS recovery (dragon) can not install OpenGApps or MindTheGapps.
    OpenGApps fails on size."

    Cheers, JD
     
    • Like
    Reactions: ipdev

    funguy2

    New member
    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.

    !!!!!!
    attention do not execute "fastboot erase recovery" this command has destroyed my tablet
    !!!!!!!

    # fastboot getvar unlocked
    unlocked: yes
    Finished. Total time: 0.000s

    # fastboot getvar secure
    secure: yes
    Finished. Total time: 0.000s

    # fastboot --version
    fastboot version 31.0.1-7187441

    version-bootloader: Google_Smaug.7900.139.0
    product: dragon

    # fastboot flash recovery twrp-3.5.1_9-0-dragon.img
    ..
    Writing 'recovery' FAILED (remote: 'unsupported command')
    fastboot: error: Command failed


    # fastboot boot twrp-3.5.1_9-0-dragon.img
    ..
    Booting FAILED (remote: 'image verification failed')
    fastboot: error: Command failed

    Same problem with stock image

    # ryu-opm8.190605.005-factory-25b457f3\ryu-opm8.190605.005>flash-all.bat
    Sending 'bootloader' (16384 KB) OKAY [ 0.548s]
    Writing 'bootloader' FAILED (remote: 'unsupported command')
    fastboot: error: Command failed
    Rebooting into bootloader OKAY [ 0.000s]
    Finished. Total time: 0.000s
    --------------------------------------------
    Bootloader Version...: Google_Smaug.7900.139.0
    Baseband Version.....: N/A
    Serial Number........: unknown variable
    --------------------------------------------
    extracting android-info.txt (0 MB) to RAM...
    Checking 'product' OKAY [ 0.000s]
    Checking 'version-bootloader' OKAY [ 0.016s]
    Checking 'partition-size:system' OKAY [ 0.016s]
    Snapshot cancel FAILED (remote: 'unknown command')
    fastboot: error: Command failed
    Press any key to exit...


    .. and adb "fwtool vbnv write dev_boot_fastboot_full_cap 1" is not possible because twrp or recovery is deleted

    basically the same problem as in thread:
    .. with not solution

    now i own a tablet for the trash can
     
    Last edited:

    ipdev

    Recognized Contributor
  • Feb 14, 2016
    1,320
    1
    1,462
    Google Nexus 10
    Nexus 7 (2013)
    !!!!!!
    attention do not execute "fastboot erase recovery" this command has destroyed my tablet
    !!!!!!!

    # fastboot getvar unlocked
    unlocked: yes
    Finished. Total time: 0.000s

    # fastboot getvar secure
    secure: yes
    Finished. Total time: 0.000s

    # fastboot --version
    fastboot version 31.0.1-7187441

    version-bootloader: Google_Smaug.7900.139.0
    product: dragon

    # fastboot flash recovery twrp-3.5.1_9-0-dragon.img
    ..
    Writing 'recovery' FAILED (remote: 'unsupported command')
    fastboot: error: Command failed


    # fastboot boot twrp-3.5.1_9-0-dragon.img
    ..
    Booting FAILED (remote: 'image verification failed')
    fastboot: error: Command failed

    Same problem with stock image

    # ryu-opm8.190605.005-factory-25b457f3\ryu-opm8.190605.005>flash-all.bat
    Sending 'bootloader' (16384 KB) OKAY [ 0.548s]
    Writing 'bootloader' FAILED (remote: 'unsupported command')
    fastboot: error: Command failed
    Rebooting into bootloader OKAY [ 0.000s]
    Finished. Total time: 0.000s
    --------------------------------------------
    Bootloader Version...: Google_Smaug.7900.139.0
    Baseband Version.....: N/A
    Serial Number........: unknown variable
    --------------------------------------------
    extracting android-info.txt (0 MB) to RAM...
    Checking 'product' OKAY [ 0.000s]
    Checking 'version-bootloader' OKAY [ 0.016s]
    Checking 'partition-size:system' OKAY [ 0.016s]
    Snapshot cancel FAILED (remote: 'unknown command')
    fastboot: error: Command failed
    Press any key to exit...


    .. and adb "fwtool vbnv write dev_boot_fastboot_full_cap 1" is not possible because twrp or recovery is deleted

    basically the same problem as in thread:
    .. with not solution

    now i own a tablet for the trash can
    Hi. :)

    Sorry to hear you are having issues. :(

    I use those same steps on most devices that support fastboot.
    Newer devices use fastboot_d to modify critical partitions. Slightly different if fastboot_d is also used.
    Some devices [Example: OnePlus 6T] do not let you modify critical partitions using fastboot. (no fastboot_d).


    I skimmed the thread you linked.

    One thing to note, try using a USB 2.0 port.
    USB 3.0 and/or USB-C ports can cause unexpected/unwanted issues with some devices.
    You can normally use a USB hub that has a 2.0 port if you do not have a USB 2.0 port on your computer.
    I still use a USB 2.0 port for flashing every device, including a Pixel 5.​

    Did you try different cables and USB ports?

    Connection issues can cause the failed command so, make sure you test different cables and USB ports.
    Just because the device can connect and is recognized in fastboot does not always mean it is a proper connection.
    Basic commands like erase will work. Flash will push it to the device but the device can not write the image.

    The cable I used for years (a USB 3.0 rated cable), works with all but two of my devices.
    My OnePlus 6T would work with adb and partially with fastboot.
    Now I just use the USB 2.0 rated cable that worked with my OnePlus 6T for everything.

    Newer versions of fastboot do not seem to play well with older devices.
    The snapshot error that halts the fastboot update is because it is not supported by the device.
    Same thing happens on other/older devices.

    You have to unzip image-ryu-opm8.190605.005.zip and then flash each partition by name.
    Not sure if it will boot, normally you have to factory reset/format cache and data in stock recovery to get it to boot.
    fastboot -w (fastboot format cache and data) generally errors out with newer fastboot.

    It is one of the reasons I stopped using the fastboot -w and fastboot format commands on older devices.

    This is the script I used to flash ryu-opm8.190605.005 the last few weeks while testing Magisk canary builds.
    I unzip image-ryu-opm8.190605.005.zip to a directory then run the script from there.
    You may need to make adjustments for Windows.

    Code:
    fastboot erase boot
    fastboot erase recovery
    fastboot reboot bootloader
    fastboot erase system
    fastboot erase vendor
    #
    fastboot flash recovery recovery.img
    fastboot flash system system.img
    fastboot flash vendor vendor.img
    fastboot flash boot boot.img

    Skip the erase parts and just flash boot, system, vendor and recovery again.
    If boot, system and vendor flash you might be able to boot it?

    Try fastboot -w and see what happens.
    Note: this will erase cache and data then try to format both.

    I do not remember for sure but, I think this might be your issue.
    secure: yes


    Hope something here helps you figure out what path to look down.

    Hope you can recover.
    Do not give up too quick. ;)

    I have not been actively using this device in a while so, I do not remember all the oddities and quirks.
    Sorry, I do not have much time this week so, I will not be able to look into it until the weekend.

    Cheers. :cowboy:
     
    • Like
    Reactions: followmsi

    funguy2

    New member
    Hi!
    Thanks for your feedback and encouraging words :cry:

    have now tried it on a linux machine with ubuntu, usb2 and a fastboot version from 2016 (version flag was not yet available in this version).

    [email protected]:# lsusb
    ..
    Bus 003 Device 059: ID 046d:c534 Logitech, Inc. Unifying Receiver
    Bus 003 Device 058: ID 0bda:5412 Realtek Semiconductor Corp. 4-Port USB 2.0 Hub
    Bus 003 Device 057: ID 18d1:5201 Google Inc.
    Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

    .. but with the same errors as in my previous post:
    Code:
    [email protected]:/../PixelC/ryu-opm8.190605.005/image-ryu-opm8.190605.005# fastboot erase boot
    ******** Did you mean to fastboot format this ext4 partition?
    Erasing 'boot'                                     FAILED (remote: 'unsupported command')
    fastboot: error: Command failed
    
    [email protected]:/../PixelC/ryu-opm8.190605.005/image-ryu-opm8.190605.005# fastboot erase recovery
    ******** Did you mean to fastboot format this ext4 partition?
    Erasing 'recovery'                                 FAILED (remote: 'unsupported command')
    fastboot: error: Command failed
    
    [email protected]:/../PixelC/ryu-opm8.190605.005/image-ryu-opm8.190605.005# fastboot reboot bootloader
    Rebooting into bootloader                          OKAY [  0.001s]
    Finished. Total time: 0.052s
    [email protected]:/../PixelC/ryu-opm8.190605.005/image-ryu-opm8.190605.005# fastboot erase system
    ******** Did you mean to fastboot format this ext4 partition?
    Erasing 'system'                                   FAILED (remote: 'unsupported command')
    fastboot: error: Command failed
    
    [email protected]:/../PixelC/ryu-opm8.190605.005/image-ryu-opm8.190605.005# fastboot erase vendor
    ******** Did you mean to fastboot format this ext4 partition?
    Erasing 'vendor'                                   FAILED (remote: 'unsupported command')
    fastboot: error: Command failed
    
    [email protected]:/../PixelC/ryu-opm8.190605.005/image-ryu-opm8.190605.005# fastboot flash recovery recovery.img
    Sending 'recovery' (13200 KB)                      OKAY [  0.356s]
    Writing 'recovery'                                 FAILED (remote: 'unsupported command')
    fastboot: error: Command failed
    
    [email protected]:/../PixelC/ryu-opm8.190605.005/image-ryu-opm8.190605.005# fastboot flash system system.img
    Sending sparse 'system' 1/9 (261398 KB)            OKAY [  7.931s]
    Writing 'system'                                   FAILED (remote: 'unsupported command')
    fastboot: error: Command failed
    
    [email protected]:/../PixelC/ryu-opm8.190605.005/image-ryu-opm8.190605.005# fastboot flash vendor vendor.img
    Sending 'vendor' (130771 KB)                       OKAY [  3.543s]
    Writing 'vendor'                                   FAILED (remote: 'unsupported command')
    fastboot: error: Command failed
    
    [email protected]:/../PixelC/ryu-opm8.190605.005/image-ryu-opm8.190605.005# fastboot flash boot boot.img
    Sending 'boot' (9068 KB)                           OKAY [  0.242s]
    Writing 'boot'                                     FAILED (remote: 'unsupported command')
    fastboot: error: Command failed
    [email protected]:/../PixelC/ryu-opm8.190605.005/image-ryu-opm8.190605.005#
    
    #
    [email protected]:/../PixelC/ryu-opm8.190605.005/image-ryu-opm8.190605.005# fastboot -w
    Erasing 'userdata'                                 FAILED (remote: 'unsupported command')
    fastboot: error: Command failed
    [email protected]:/../PixelC/ryu-opm8.190605.005/image-ryu-opm8.190605.005#
    
    #
    [email protected]:/../PixelC/ryu-opm8.190605.005/image-ryu-opm8.190605.005# /../Xperia_Z2-Tablet/old_try/FlashTool/x10flasher_lib/fastboot.linux.64 -w
    erasing 'userdata'...
    FAILED (remote: unsupported command)
    finished. total time: 0.001s
    [email protected]:/../PixelC/ryu-opm8.190605.005/image-ryu-opm8.190605.005#
    
    #
    [email protected]:/../PixelC/ryu-opm8.190605.005/image-ryu-opm8.190605.005# fastboot boot recovery.img
    creating boot image...
    creating boot image - 13518848 bytes
    Sending 'boot.img' (13202 KB)                      OKAY [  0.351s]
    Booting                                            FAILED (remote: 'image verification failed')
    fastboot: error: Command failed
    [email protected]:/../PixelC/ryu-opm8.190605.005/image-ryu-opm8.190605.005#
    
    [email protected]:/../PixelC/ryu-opm8.190605.005/image-ryu-opm8.190605.005# /../old_try/FlashTool/x10flasher_lib/fastboot.linux.64 boot recovery.img
    creating boot image...
    creating boot image - 13518848 bytes
    downloading 'boot.img'...
    OKAY [  0.343s]
    booting...
    FAILED (remote: image verification failed)
    finished. total time: 0.346s
    [email protected]:#

    My guess is that my problem is the following implementation:

    # nvstorage: Add new flag VBNV_DEV_BOOT_FASTBOOT_FULL_CAP (https://chromium.googlesource.com/c...ot/+/9101df2fe3ed4f0e8b65121ffc1c7e8b2d65b35d)
    Add a new flag to nvstorage for controlling fastboot capabilities offered in firmware in dev-mode. By default, value of this flag would be ignored in normal mode. Thus, when fastboot-based recovery is
    entered from normal mode, only limited capability would be available in firmware.

    After switching to dev-mode, this flag can be set automatically by user script after performing the wipe or it can be set manually using crossystem. When fastboot-based recovery is entered from dev mode and
    this flag is set, it will provide full fastboot capability in the firmware.

    thus in the "limited fastboot functionality" almost only read functions are available, see https://chromium.googlesource.com/c...e-smaug-7900.B/src/fastboot/capabilities.c#39

    And are therefore rejected by fastboot due to the missing flag (VBNV_DEV_BOOT_FASTBOOT_FULL_CAP):
    Error "unsupported command"
    # fastboot.c, https://chromium.googlesource.com/c...are-smaug-7900.B/src/fastboot/fastboot.c#1429
    Code:
        /* Check if this function is allowed to be executed */
        if (fb_cap_func_allowed(fb_func_table[i].id) == FB_CAP_FUNC_NOT_ALLOWED) {
            FB_LOG("Unsupported command\n");
            fb_add_string(out_buff, "unsupported command", NULL);
            cmd->type = FB_FAIL;
            return FB_SUCCESS;
        }

    The error "image verification failed"
    # fastboot.c, https://chromium.googlesource.com/c...are-smaug-7900.B/src/fastboot/fastboot.c#1083
    Code:
        if (VbVerifyMemoryBootImage(&cparams, &kparams, kernel, kernel_size, 0)
            != VBERROR_SUCCESS) {
            if ((!fb_device_unlocked()) ||
                (vbnv_read(VBNV_DEV_BOOT_FASTBOOT_FULL_CAP) == 0)) {
                /*
                 * Fail if:
                 * 1. Device is locked, or
                 * 2. Device is unlocked, but full fastboot cap is not
                 *    set.
                 */
                fb_add_string(&cmd->output, "image verification failed",
                          NULL);
                return FB_SUCCESS;
            }

    and this is the reason why fastboot getvar secure shows "secure: yes"
    # fastboot.c, https://chromium.googlesource.com/c...ware-smaug-7900.B/src/fastboot/fastboot.c#359
    Code:
        case FB_SECURE: {
            if (fb_cap_func_allowed(FB_ID_FLASH) == FB_CAP_FUNC_NOT_ALLOWED)
                fb_add_string(output, "yes", NULL);
            else
                fb_add_string(output, "no", NULL);
            break;
        }

    Thus, in my opinion, there are only the following options for a solution:

    a) Set the flag in NVRAM without ADB, possibly via USB recovery or similar - no idea how

    b) the mysterious PixelC "developer switch"
    .. quote from https://groups.google.com/a/chromium.org/g/chromium-os-discuss/c/VKK3WXKg7lE
    "Our primary kernel dev was told by a Pixel C dev that the "developer switch" is behind the front camera flex and you would need to remove the screen to get access to it. This arose when we were trying to root the Pixel C and flashing SuperSU via TWRP caused the bootloader to relock the partitions as read-only, even though all fastboot commands were still available, we were given a tool by the pixel devs that allowed us to set a flag that would unlock the partitions once again. (link to thread)"
    .. also no idea how

    c) using crossystem? and set full fastboot capability in the firmware using fwtool, but how?!

    d) Fusée Gelée hardware exploit?

    e) Gbb-flags?

    f) ?

    for an idea or a tip, I would be very grateful 👍


    best regards and many thanks
     
    Last edited:
    • Like
    Reactions: followmsi and ipdev

    dsapac

    Senior Member
    Mar 4, 2011
    208
    103
    Murska Sobota
    Google Pixel C
    I updated from previous build Just flashed rom gapps and magisk I changed webview to bromide and for now I use bromide browser instead of Firefox For Youtube I use Vanced and it's working great for 1080p and up Problem is still that a lot of apps have delay when loading Netflix is working in sd quality App from my IPTV provider doesn't have any problem From the most part device is snappy and responsive
     
    • Like
    Reactions: Alxoom33

    ipdev

    Recognized Contributor
  • Feb 14, 2016
    1,320
    1
    1,462
    Google Nexus 10
    Nexus 7 (2013)
    Hi all. :D

    Have an issue that very well is a local issue.
    Might also explain issues other users have on this and/or other devices.
    I think something became corrupt or a settings flag is not getting reset.

    Since this post became long, I put most of the details in a hide tag.

    I did not have this issue a month or two ago, since then I have flashed Stock Google multiple times testing Magisk.

    Magisk canary 22006 includes a regression fix that affected dragon.

    You can again use the Direct install method in Magisk (22006+) on dragon.

    ---

    Stock Recovery takes under a minute to Format/Factory reset.
    LineageOS Recovery takes under a minute to Format data/factory reset.
    I ran a l18 dragon build to get LineageOS recovery for dragon.

    Stock and LineageOS recovery can format data even if it is an empty partition.

    Lineage Recovery (fastboot erased userdata)
    Example:
    Start at 23:00:38 Done at 23:01:15. (37 Sec.)

    ---

    Did not matter what version of TWRP I used.
    • twrp-3.1.0-0-dragon.img
    • twrp-3.2.3-0-dragon.img
    • twrp-3.3.1-2-dragon.img
    • twrp-3.4.0-0-dragon.img
    • twrp-3.5.0_9-0-dragon.img
    • twrp-3.5.1_9-0-dragon.img

    Reverted back to using 3.5.1_9-0

    TWRP Recovery takes ten minutes (give or take) to format data.
    Example:
    Start at 14:47:38 Done at 14:58:13. (10 Min. 35 Sec.)

    If I erase userdata (data) in fastboot then boot into TWRP.
    TWRP can not decrypt and asks for a password.

    This leaves TWRP in a useless state since I can not format or wipe or install.
    Cache, Data, System and Vendor can not be mounted.

    If I format userdata in fastboot, stock recovery or Lineage recovery.
    TWRP will boot without asking for a password and I can format, wipe and install.

    This is the same issue I had with Google stock when testing Magisk and data was actually encrypted.
    For testing Magisk, I could use adb sideload and install magisk since it was patching boot.
    Stock boot image backup was lost since it could not be save to data.

    ---

    Go though the format, wipes and do a clean install of Lineage and OpenGApps.

    For magisk I have to use a boot image patched using the Magisk app.

    - See below for reason. -

    Booted into system (Lineage 18.1), I am unencrypted as expected.
    Code:
    dragon:/ # getprop | grep crypto
    [ro.crypto.state]: [unencrypted]

    Booted into TWRP, I show encrypted. WTF?
    Code:
    ~ # getprop | grep crypto
    [ro.crypto.state]: [encrypted]
    [ro.crypto.type]: [file]

    If I flash Magisk in recovery..

    TWRP shows encrypted, Magisk finds it and patches the boot image accordingly.
    Patch with flag KEEPVERITY=[true] KEEPFORCEENCRYPT=[true]

    LineageOS show nothing, Magisk finds it and patches the boot image accordingly.
    Patch with flag KEEPVERITY=[true] KEEPFORCEENCRYPT=[false]

    ---

    I have done a few things that I would never suggest to others to try. 🙃
    - I made a restore plan, best as I could, for each step.
    - Realized I could very well HARD brick the device.


    I even erased persist and let it regenerate on boot with Lineage 18.1.
    Still was encrypted when booted into TWRP. :(
    This broke the ability to LOCK/UNLOCK bootloader.
    The oem unlock option was even greyed out and not accessible in the stock (Google) rom.

    I dumped PST before I erased persist.
    'persist' is not the bootloader partition name.
    I am using the common name so others could not just fastboot erase NameOfpartition.

    I was not sure that PST was persist but, it seemed my gamble was correct?
    Restoring the dump fixed locking/unlocking bootloader. ;)

    ---

    Anyone have an idea of where an encryption flag might still exist after erasing/formatting partitions or what may have become corrupt ?

    Cheers all. :cowboy:
     
    Last edited:
    • Like
    Reactions: followmsi

    TooYellow

    Member
    Jun 20, 2010
    47
    9
    NYC
    I had the Feb build and Nik gapps stock installed. The tablet ran fine but felt like a device running an OS three versions past its EOL. After installing the 202010406 build I got a boot loop. I fixed it by manually uninstalling nik and decided on installing Nik gapps core instead.

    The tablet now performs like it was built for Android R! Scrolling is way smoother, switching apps is zippier, overall faster UI response. I don't know if it was the new build or swapping to a smaller gapps package but I'm loving it. Chrome is still slow though.

    Just wanted to share my experience in case people are having sluggishness like I was.
    My primary uses: google news, youtube, instagram, Firefox, kindle, google books
     
    • Like
    Reactions: _benedict_

    Tiesemans

    Member
    Jun 19, 2018
    32
    1
    DB
    I have such a stupid situation.

    After ADB sideloading 202010406 build I lost my TWRP and Magisk.
    Thinking I was smart I also sideloaded TWRP 3.5.2_9-0-guacamole-recovery.img
    My bad ... bootloop hallo, with TWRP logo continuesly flashing.
    I restored it by using
    fastboot getvar current-slot
    this will return your <letter>

    then do
    fastboot flash boot_<letter> <filename>.img
    You can continue forward.

    So now I am desperately trying to fastboot via bootloader fastboot boot and flash TWRP recovery.img ...
    But when I do so I end up in bootloader :S loop.
    When I restore via fastboot the lineage recovery all is well again :S
    What am I doing wrong here?!
    Honestly I think the lastest TWRP for oneplus 7 pro is not compatible with current nightly 18.1 Lineage boot/recovery?!
     
    Last edited:

    ipdev

    Recognized Contributor
  • Feb 14, 2016
    1,320
    1
    1,462
    Google Nexus 10
    Nexus 7 (2013)
    I have such a stupid situation.

    After ADB sideloading 202010406 build I lost my TWRP and Magisk.
    Thinking I was smart I also sideloaded TWRP 3.5.2_9-0-guacamole-recovery.img
    My bad ... bootloop hallo, with TWRP logo continuesly flashing.
    I restored it by using


    So now I am desperately trying to fastboot via bootloader fastboot boot and flash TWRP recovery.img ...
    But when I do so I end up in bootloader :S loop.
    When I restore via fastboot the lineage recovery all is well again :S
    What am I doing wrong here?!
    Honestly I think the lastest TWRP for oneplus 7 pro is not compatible with current nightly 18.1 Lineage boot/recovery?!
    This OT (Off Topic) for this thread.
    This thread is for Pixel C (Dragon)

    If you are having trouble on a OnePlus 7, you will be better off searching and/or asking in one of the OnePlus 7 Pro threads.
    OnePlus 7 Pro - xdaForums - Link

    [RECOVERY][3.4.0-10][U][guacamole]Official/Unofficial TWRP recovery for OnePlus 7 Pro - xdaThread - Link

    Note about TWRP:
    If your device has a separate recovery partition, you can flash TWRP to recovery.
    If your device is Recovery-In-Boot, you need to patch the boot image with TWRP using the TWRP installer zip for your device.
    I remember when I was looking at OP 7(s), one of them did have a separate recovery partition.

    Users in the OnePlus 7 threads will be able to help you more since, they have the device.

    Good luck. :)

    Cheers. :cowboy:
     

    rkjnsn

    New member
    Oct 31, 2008
    4
    5
    In case it helps anyone else, I was running into the following error when trying to flash MindTheGapps from TWRP:

    Code:
    Could not mount /mnt/system! Aborting

    The error turned out to be that /etc/recovery.fstab was using tabs for separators, but the MindTheGapps script was expecting it to use spaces. I was able to solve the problem by editing META-INF/com/google/android/update-binary in MindTheGapps-11.0.0-arm64-20210412_124247.zip. I replaced this line (line 44):

    Bash:
    grep -v "^#" /etc/recovery.fstab | grep " $1 " | tail -n1 | tr -s ' ' | cut -d' ' -f1

    With this one, which should work with both tabs and spaces:

    Bash:
    grep -v "^#" /etc/recovery.fstab  | grep "[[:space:]]$1[[:space:]]" | tail -n1 | tr -s [:space:] ' ' | cut -d' ' -f1
     

    ipdev

    Recognized Contributor
  • Feb 14, 2016
    1,320
    1
    1,462
    Google Nexus 10
    Nexus 7 (2013)
    In case it helps anyone else, I was running into the following error when trying to flash MindTheGapps from TWRP:

    Code:
    Could not mount /mnt/system! Aborting

    The error turned out to be that /etc/recovery.fstab was using tabs for separators, but the MindTheGapps script was expecting it to use spaces. I was able to solve the problem by editing META-INF/com/google/android/update-binary in MindTheGapps-11.0.0-arm64-20210412_124247.zip. I replaced this line (line 44):

    Bash:
    grep -v "^#" /etc/recovery.fstab | grep " $1 " | tail -n1 | tr -s ' ' | cut -d' ' -f1

    With this one, which should work with both tabs and spaces:

    Bash:
    grep -v "^#" /etc/recovery.fstab  | grep "[[:space:]]$1[[:space:]]" | tail -n1 | tr -s [:space:] ' ' | cut -d' ' -f1
    Nice find. :D

    MindTheGapps - GitLab - get_block_for_mount_point - Link

    If you are signed up on GitLab, please bring this to their attention.
    MindTheGapps - GitLab - Link

    If not, let me know and I will bring it to their attention on your behalf.

    Cheers. :cowboy:

    PS.
    Sorry all for a bit of OT. 🙃
     
    Last edited:

    Top Liked Posts

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

      The monthly security updates ..

      lineage-18.1-20210505-UNOFFICIAL-dragon.zip

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

      Enjoy :p
      4
      Any plans to make this enforcing?
      Or an official build?

      Enforcing mode will come later .. for now you can switch manually. (setenfoce 1)

      And no more official builds .. at least not by me.
      3
      In case it helps anyone else, I was running into the following error when trying to flash MindTheGapps from TWRP:

      Code:
      Could not mount /mnt/system! Aborting

      The error turned out to be that /etc/recovery.fstab was using tabs for separators, but the MindTheGapps script was expecting it to use spaces. I was able to solve the problem by editing META-INF/com/google/android/update-binary in MindTheGapps-11.0.0-arm64-20210412_124247.zip. I replaced this line (line 44):

      Bash:
      grep -v "^#" /etc/recovery.fstab | grep " $1 " | tail -n1 | tr -s ' ' | cut -d' ' -f1

      With this one, which should work with both tabs and spaces:

      Bash:
      grep -v "^#" /etc/recovery.fstab  | grep "[[:space:]]$1[[:space:]]" | tail -n1 | tr -s [:space:] ' ' | cut -d' ' -f1
      2
      I have such a stupid situation.

      After ADB sideloading 202010406 build I lost my TWRP and Magisk.
      Thinking I was smart I also sideloaded TWRP 3.5.2_9-0-guacamole-recovery.img
      My bad ... bootloop hallo, with TWRP logo continuesly flashing.
      I restored it by using


      So now I am desperately trying to fastboot via bootloader fastboot boot and flash TWRP recovery.img ...
      But when I do so I end up in bootloader :S loop.
      When I restore via fastboot the lineage recovery all is well again :S
      What am I doing wrong here?!
      Honestly I think the lastest TWRP for oneplus 7 pro is not compatible with current nightly 18.1 Lineage boot/recovery?!
      This OT (Off Topic) for this thread.
      This thread is for Pixel C (Dragon)

      If you are having trouble on a OnePlus 7, you will be better off searching and/or asking in one of the OnePlus 7 Pro threads.
      OnePlus 7 Pro - xdaForums - Link

      [RECOVERY][3.4.0-10][U][guacamole]Official/Unofficial TWRP recovery for OnePlus 7 Pro - xdaThread - Link

      Note about TWRP:
      If your device has a separate recovery partition, you can flash TWRP to recovery.
      If your device is Recovery-In-Boot, you need to patch the boot image with TWRP using the TWRP installer zip for your device.
      I remember when I was looking at OP 7(s), one of them did have a separate recovery partition.

      Users in the OnePlus 7 threads will be able to help you more since, they have the device.

      Good luck. :)

      Cheers. :cowboy:
      2
      Nice find. :D

      MindTheGapps - GitLab - get_block_for_mount_point - Link

      If you are signed up on GitLab, please bring this to their attention.
      MindTheGapps - GitLab - Link

      If not, let me know and I will bring it to their attention on your behalf.

      Cheers. :cowboy:

      PS.
      Sorry all for a bit of OT. 🙃
      Thanks for the pointer to the repo. I sent a merge request.
    • 61

      EmPczMv.png

      LineageOS 18.1

      Android 11

      lineage-18.1-20210505-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