yashsingh1/xdaforums huggingface dataset:
[Pixel C Android Development] followmsi:
[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.
[Pixel C Android Development] followmsi:
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 !
[Pixel C Android Development] gaufres:
Thanks both. That's it.

No su: bootloops.

Lineage extras su: bootloops

SuperSU: boots OK

Magisk: boots OK
[Pixel C Android Development] followmsi:
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
[Pixel C Android Development] 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 .. :)
[Pixel C Android Development] followmsi:
Thanks. No need for logs..clean install solves it.

Will have a look for migration build .. maybe we can get one.

Again, the supported and official way is clean install.

I know .. it's a pain ! ;)
[Pixel C Android Development] frauhottelmann:
Not a big deal. I can backup and restore my apps with oandbackup or something similar.
[Pixel C Android Development] followmsi:
Have a look here .. https://review.lineageos.org/#/c/156327/

This is working really good for me ..

Add script for official<->unofficial migrations

How to:

adb root

adb remount

adb shell stop

adb push build/tools/keys-migration-to.sh /data/local/tmp/

adb shell sh /data/local/tmp/keys-migration-to.sh official # unofficial

adb reboot recovery

Afterwards I was able to install official vesion with old data partition.

No permission problems in system .. cool !

Cheers

EDIT:

If you have problems to get "adb root" running, pls use the version below ...

lineage-14.1-20170614-UNOFFICIAL-dragon.zip
[Pixel C Android Development] frauhottelmann:
Works! Thanks a lot. If anybody is wondering, here is the script in question: keys-migration-to.sh

adb root worked without any problems with your last version and the los su addon.
[Pixel C Android Development] xda_jm:
So - I had to actually wipe everything to get the latest official 20170612-nightly-dragon installed.

I have however now the message showing up that I may have an outdated vendor image installed.

Required version is vendor Image N2G47W - I downloaded it also from google's page as google_devices-dragon-n2g47w-1a3740cf.tgz, extracted the image and flashed it to the pixel-c - but the error message still shows up.

Exact message is: A vendor image mismatch has been detected. Typically this means your vendor image is out of date. Please ensure your vendor image matches N2G47W.

Any hint what to do?
[Pixel C Android Development] followmsi:
Uploaded a zip file with the script and a small help file.

The coder of the script is actually the same who was helping for the signing part. ;)
[Pixel C Android Development] followmsi:
Pls download stock firmware from here ..

https://developers.google.com/android/images

https://dl.google.com/dl/android/aosp/ryu-n2g47w-factory-45c8abfa.zip

Unzip the factory image and use the included vendor.img to flash via TWRP.
[Pixel C Android Development] xda_jm:
Thanks. That worked.

Last question - I have installed:

1. lineage-14.1-20170612-nightly-dragon-signed.zip

2. open_gapps-arm64-7.1-nano-20170614.zip

3. SuperSU-v2.79.zip

and vendor.img from ryu-n2g47w-factory-45c8abfa.zip

The google-login failed all the time. I then changed the security -> Disabled 2 factor authentication after clearing all google app caches, and I got back in. After re-enabling the 2 factor authentication, google apps are not usable anymore.

It asks me to actually re-authenticate but always crashes. Whatever I do, it fails.

[Update]

Just did the installation, but instead of the open_gapps, I installed BeansGapps-Mini-7.1.x-20170610.zip.

Works flawless now.

Cheers
[Pixel C Android Development] followmsi:
New OMS version ..

lineageOMS-14.1-20170616-UNOFFICIAL-dragon.zip

lineageOMS-14.1-20170616-UNOFFICIAL-dragon.zip.md5sum

Changes:

- Latest kernel changes

- Latest device changes

- Latest OMS and LineageOS changes

Enjoy :)
[Pixel C Android Development] xda_jm:
You by chance have some more details on that? *Kernel/device changes ?

Thx
[Pixel C Android Development] followmsi:
device changes (OMS versions)

https://github.com/followmsi/android_device_google_dragon/commits/los-cm-14.1

kernel changes ( unicorn-xceed-followmsi kernel - still in use for OMS versions)

https://github.com/followmsi/android_kernel_tegra/commits/followmsi-kernel

Cheers
[Pixel C Android Development] jeffyca:
Congrats on getting this officially supported with LineageOS. Still surprised you haven't updated this thread to show its official now as I am sure the people will flock to install it that have the Pixel C.

Is there any benefit to running SuperSU versus the LineageOS su addon? I have been using the LineageOS su addon since it became official and haven't noticed anything out of the ordinary.
[Pixel C Android Development] followmsi:
Changed the first page a bit .. maybe some more changes later on.

I am using Magisk right now .. pls use the supersu tool you like most. ;)

No recommendation from me.

All are working fine .. some have more features some less.

Cheers
[Pixel C Android Development] J_M_H:
Hello followmsi.

I did not see a Monday (6/19) build for Lineage OS. Any reason for that?

With the end of Google support coming soon, I'm thankful that you took the time and effort to keep this device alive.
[Pixel C Android Development] followmsi:
Build server problems ...

https://jenkins.lineageos.org/view/all/job/android/buildTimeTrend

Several builds were failing .. have asked for new dragon build.

If this will not happen we need to wait till Monday again.

Cheers
[Pixel C Android Development] GonzoKSV:
Did anything happen according the build Server? Well, I'm satisfied with lineage :)

Gesendet von meinem Pixel C mit Tapatalk
[Pixel C Android Development] frauhottelmann:
The new weekly is online and working fine on my Pixel C...
[Pixel C Android Development] GonzoKSV:
I have allready seen it, too. Great! Thanks for information!

Gesendet von meinem Pixel C mit Tapatalk
[Pixel C Android Development] followmsi:
As I know LineageOS is using a new build server now.

Don't know if this is just a temporary solution until the origin build server is fixed.

Hopefully the next dragon builds are not affected anymore :)

[MENTION=592660]frauhottelmann[/MENTION]

The migraiton script has been changed as well .. to fix official to unoffical migration.

https://review.lineageos.org/#/c/156327/6..7/build/tools/keys-migration-to.sh

Cheers
[Pixel C Android Development] followmsi:
Quick update ..

The July patches have been arrived ..

The official LineageOS version will need the July vendor.img beginning of next week.

Pls use the following vendor_N2G48B_2017-07.img or extract from factory image.

July kernel updates have been commited as well ..

https://github.com/LineageOS/androi...mmit/f09ee40b4a635c81fb1ec92e10373a1e7080cd4f

The OMS sources have not been updated until now !

As I will leave for vacation very soon the OMS ROM will arrive a bit later .. approx. 3 weeks from now.

Sorry, but it's holiday season :)

Happy holidays !
[Pixel C Android Development] followmsi:
This has been discussed in spring this year ..

Here are some more infos ..

https://github.com/followmsi/android_kernel_tegra/commit/59f8c10b61fe286315d7a631903fed542e1270d5

Pls use this kernel ... tegra-3.18_unified_dragon_kernel_10_v200305.zip (inside KERNEL/OLD folder)

https://xdaforums.com/showpost.php?p=81938531&postcount=842

As the patch makes problems it has been taken out again .. same like in latest kernel/rom versions too.

https://xdaforums.com/showpost.php?p=82065729&postcount=852

Same for "standard" kernel in ROM .. the patch has been taken out again.
[Pixel C Android Development] followmsi:
This is an old installer package .. just used latest TWRP 3.4 ..

Update.ZIP_TWRP_dragon_3.4.0-0.zip

Are you able to sideload ?
[Pixel C Android Development] followmsi:
Disable "Hardware-accelerated video decode" in chrome://flags/ .. this should still work to bypass video issues in Chrome.
[Pixel C Android Development] Alxoom33:
Thank you for providing the zip TWRP installation file. I tried to sideload. But, after Verfying update package... I got the following error messages:

E: footer is wrong

Update package verification took 0.1 s (result 1)

E: signature verification failed

E: error 21

Install from adb competed with status 2.

Installation aborted.
[Pixel C Android Development] Alxoom33:
That was easy!
[Pixel C Android Development] Elektron60:
I use the given Kernel and the 1102 version but i stuck on Google.

What do i wrong?

Sorry, my fault it's LOS 18 !

Do we have a new Thread?
[Pixel C Android Development] 12paq:
LOS 18 is posted and labeled as untested and has been reported not to boot.

For a daily driver use LOS 17.1 it runs nearly perfectly.

Also, LOS 17.1 includes the most current "unified kernel". Flashing the latest kernel is redundant and unnecessary.
[Pixel C Android Development] followmsi:
Los-18.0 is new build and supposed to be tested. .. still need logcat :)

Elektron has 2 Pixel C devices with same MAC address . For this reason he should test older kernel with patch for it.

But the problem with the MAC address patch .. its hanging on google logo .. sometimes.

If old kernel boots successful he should get MAC address from device and not standard MAC. (11:22:33)

Hope this helps ..
[Pixel C Android Development] followmsi:
As said . It's an old package just with new recovery image.

Installation from older TWRP version should work.

Need to see how footer needs to look like .. not sure if it will pass verification of "lineage" recovery.

You can play with updater-script in twrp update.zip .. to align with lineage-17.1 ROM spdater-script.

Meta-inf/com/google/android/updater-script.

Not sure when I will find time to check this stuff ..
[Pixel C Android Development] followmsi:
Android 10 - November 2020

lineage-17.1-20201106-UNOFFICIAL-dragon.zip

Changes:

- Google security updates -> November 2020

- Switched to "unified" kernel.

- 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 :p
[Pixel C Android Development] Elektron60:
It works! Hopefully without mac issues.

Thank you!
[Pixel C Android Development] Murmel2k:
Tried it again. Didn't change anything :(
[Pixel C Android Development] setmaster:
Yep. Still not working. Even with new 2020-11-06 release.
[Pixel C Android Development] ipdev:
[MENTION=5648034]Peregr1ne[/MENTION]

sudo fastboot flash boot /home/knoppix/Desktop/KNOPPIX/parking/platform-tools/twrp.img

With this command, you are trying to flash twrp to the boot partition.

To boot only (not install) TWRP you would use.

fastboot boot /home/knoppix/Desktop/KNOPPIX/parking/platform-tools/twrp.img

To install twrp you need to flash it to the recovery partition.

fastboot flash recovery /home/knoppix/Desktop/KNOPPIX/parking/platform-tools/twrp.img

Cheers. :cowboy:
[Pixel C Android Development] Elektron60:
The mac issue is not gone.
[Pixel C Android Development] followmsi:
https://xdaforums.com/showpost.php?p=83871211&postcount=1989
[Pixel C Android Development] schoerb:
The same for me. Problem appears with Chrome, Vivaldi, Brave.

Only Firefox and Kiwi Browser play the videos in Twitter.
[Pixel C Android Development] setmaster:
The browsers are not the only problem. I use the tablet for my childs. Cartoon Network and other apps are not working, too. I guess they use the chrome engine to display HTML stuff and videos.
[Pixel C Android Development] followmsi:
This might be DRM problem too ..

Pls use root explorer or boot into TWRP to remove/rename "/vendor/lib/liboemcrypto.so".

Reboot into system and test all your stuff again .. works better ?

But nvidia codecs will be disabled this way.
[Pixel C Android Development] Peregr1ne:
Thanks! I'm pretty sure I have this time attempted to flash it the right way, still no joy it seems, I must be doing something else incorrectly :confused::(

knoppix@Microknoppix:~$ fastboot flash recovery /home/knoppix/Desktop/KNOPPIX/parking/platform-tools/twrp.img
target reported max download size of 268435456 bytes
erasing 'recovery'...
[COLOR="Red"]FAILED [/COLOR](remote: unsupported command)
finished. total time: 0.002s

at least the 3rd line now says erasing recovery...but it is still reporting a FAIL because of an unsupported command...

is it clear from above which command is not supported? and am I right in saying it is not supported by the pixel (remote wrt knoppix system)?

after this I can boot into recovery, but I'm pretty sure this is still TWRP recover, they used to look very very different on phones&tablets that I worked with before....

Android Recovery

google/ryu/dragon

8.1.0/OPM8.190605.005/5749003

...

assuming this is indeed stock recovery, is there any way in which I could you that to upgrade to TWRP and get 17.1 installed?
[Pixel C Android Development] Murmel2k:
This did the trick for me. Thank you! Just for my curiosity: Whats the reason for the nvidia codecs not working? Too outdated and not maintained anymore for recent android version? Or can we expect this to work again at some point?
[Pixel C Android Development] frov:
Root cause: Pixel C (Dragon) was revoked for Widevine in Sept; result of that is that HD playback does not work, apps like Netflix don't run, my Dutch TV app Ziggo stopped working, etc.

The Widevine Revocation Tracked sadly also listed our beloved Dragon as such victim: https://t.me/wvcrl and look for 'Dragon'.

Renaming liboemcrypto then brings back working apps, but not at the same level as before.

Can use an app like this one to check the Widevine support level: https://play.google.com/store/apps/details?id=com.androidfung.drminfo
[Pixel C Android Development] huunn:
FAIL: lineage-18.0-20201102-UNOFFICIAL-dragon.zip

1. After flashing lineage-18.0-20201102-UNOFFICIAL-dragon.zip, my pixel c didn't boot up from google logo. A recovery with LineageOS logo replaced TWRP (maybe because of update recovery in dev option turned on).

2. Previously worked ADB drivers seemed not to be compatible in fastboot mode. Device manager only shows 'unknown device'. 'Fastboot devices' command shows no device. So I couldn't flash TWRP.img in fastboot mode.

3. I managed to sideload LineageOS 17.1 with ADB (apply update menu), but sideloading the smallest gapps failed with 'status 70' error (not enough space in system partition?)

4. Sideloading LineageOS 17.1 with 'update system recovery' option on did not bring back TWRP.

I'm stuck with recovery with limited functions and no gapps. Unless, you're familiar with fixing issues, I do not recommend lineage-18.0-20201102-UNOFFICIAL-dragon.zip or later version until enough testing.

Edit. thanks to [MENTION=892369]EnginEAR[/MENTION], using Linux terminal, I was able to boot into TWRP and replace Lineage OS recovery with TWRP.

1. $ sudo fastboot flash recovery twrp-3.4.0-0-dragon.img

2. reboot to TWRP

3. replace existing system recovery with TWRP
[Pixel C Android Development] EnginEAR:
./fastboot flash recovery twrp-3.4.0-0-dragon.img

https://dl.twrp.me/dragon/twrp-3.4.0-0-dragon.img

I was able to use a VirtualBox VM with a minimal Ubuntu installed (and Android SDK, of course).

I also used the pico version of OpenGApps and Magisk 21.0.

Hope this helps.
[Pixel C Android Development] Alxoom33:
Thanks! I was able to sideload the TWRP-dragon 3.4.zip installer with latest Lineage recovery. Got TWRP!

Fastboot still not working for some reason.
[Pixel C Android Development] michie:
Try this to get your device recognized in windows:

https://xdaforums.com/android/general/tool-adb-fastboot-installer-tool-windows-t3999445/amp/

Some win 10 update also broke it for me and this was the only way to get it working again.
[Pixel C Android Development] Alxoom33:
Thanks, I'll give it a try!
[Pixel C Android Development] Vartom:
You should also check if the tablet is locked to execute fastboot commands.

fastboot getvar all

Check the status secure parameters.
[Pixel C Android Development] Murmel2k:
What f****** s*** is this? So some random asshole decides that my device is too "old", flips a switch and breaks a perfectly working device?

Is there a way to fake another device?
[Pixel C Android Development] Peregr1ne:
For me this unfortunately did not resolve anything, the result is still the same wether on Win10, on VM-Linux or on pendrive-Knoppix: once in fastboot mode there is little to no communication with the tablet anymore :confused:

I'm going to see if I can achive anything using the fwtool - I'm really lost here as I don't think the tablet is bricked or anything, but I just cannot fathom what needs to be done to resolve this.

UPDATE: no joy with fwtool, it appears I cannot (or don't know how to) run execute the file correctly on the tablet - possibly because I cannot get it in the correct folder and set the right file properties...?

Anyone any suggestions / hints / tips / ....?
[Pixel C Android Development] huunn:
Using Linux terminal, I was able to boot to TWRP and repalce Lineage OS recovery with TWRP. I appreciate your advice.:good:

Still wonder why windows' cmd didn't work.

1. $ sudo fastboot flash recovery twrp-3.4.0-0-dragon.img

2. reboot to TWRP

3. replace existing system recovery with TWRP
[Pixel C Android Development] followmsi:
What did you do to make it working .. this time. ?
[Pixel C Android Development] Grigori88:
What am I doing wrong?
[Pixel C Android Development] Alxoom33:
Backed up my internel storage to my computer.

Did a full wipe/reformat of internal memory with stock recovery.

Sideloaded your latest LOS 1.7.zip. Thanks [MENTION=1038414]follomsi[/MENTION]

Went into Settings/System/Developer Options and activated latest LOS Recovery, by toggling the "Update recovery" toggle.

Booted into LOS Recovery and sideloaded the 3.4 TWRP.zip installer. Thanks [MENTION=1038414]follomsi[/MENTION]

Booted into TWRP Recovery and flashed gapps and Magisk.

Restored internal storage from computer.

Restored TWRP data backup that I had made for 17.1 back in October. Updated to latest November gapps.

Key was activating LOS RECOVERY in Developer Options. Not sure if I even still needed TWRP?

Can you flash .img files in LOS RECOVERY?

Btw, still can't fastboot to the Dragon on my windows 10 computer; although adb is working, and fastboot is working with my Pixel2 XL.

---------- Post added at 02:02 PM ---------- Previous post was at 01:57 PM ----------

Just want everyone to know I'm not asking for etas.[emoji85]

I'm curious about the current status of LOS 18 for Dragon? Is there going to be a new thread, or should we look for news and updates here? Thanks [emoji4]
[Pixel C Android Development] Peregr1ne:
It appears you are running into exactly the same issue that I am encountering - please let me know if you have found a fix!

I'll post in this thread if & when I have...

---------- Post added at 09:11 PM ---------- Previous post was at 09:02 PM ----------

Perhaps this is something I can try as well - except for that I don't understand what it is you mean exactly...

Did sideloading the LOS.zip (assuming you are referring to the 500+MB rom file from [MENTION=5480152]followmsi[/MENTION]) also upload some sort of a recovery?

And is it possible to somehow activate this using the Developer Options? What is the exact name of that option, I can't seem to find anything with recovery in the name in my Developer Options....:confused:
[Pixel C Android Development] Alxoom33:
Yes. Please read my post carfully. I was exact about what I did.

Went into Settings/System/Developer Options and activated latest LOS Recovery, by toggling the "Update recovery" toggle.

Please repeat exactly. I don't know what else I can add to my post.
[Pixel C Android Development] Peregr1ne:
The reason I asked is that this option for me doesn't appear to be there :confused:

Should it be in the "Memory"-section or perhaps in the "Debugging"-section?

Those seem the most likely to me, they have five toggles each in my tablet.
[Pixel C Android Development] Alxoom33:
Are you looking in November 17.1 build? I'll try to post a screenshot below. Use the search feature in Settings.

View attachment 5136529
[Pixel C Android Development] Peregr1ne:
Ahhh, perhaps that is part of the confusion on my side at least: after a factory reset I'm back to stock-Android-8.1.0 and I'm looking for this option in stock-Android-Developer-Options...

All my attempts to install any new recovery seem to grind to a halt on the following part, wether from Win10, VM-linux, or pendrive-knoppix, it seems there is no communication (anymore) once the tablet is in fastboot mode, in knoppix this looks like (twrp 3.4.0.0):

knoppix@Microknoppix:~$ fastboot flash recovery /home/knoppix/Desktop/KNOPPIX/parking/platform-tools/twrp.img
target reported max download size of 268435456 bytes
erasing 'recovery'...
[COLOR="Red"][B]FAILED [/B][/COLOR](remote: unsupported command)
[Pixel C Android Development] brackenhill_mob:
Make sure you have the latest version of Android tools.
[Pixel C Android Development] Alxoom33:
You need to read my post more carfully, so you don't make these mistakes.

As I wrote, you need to adb sideload latest LOS 17.1.zip file. You can use adb in stock recovery, you don't need to fastboot!
[Pixel C Android Development] NYCHitman1:
You forgot the instructions for throw this tablet out the window lol
[Pixel C Android Development] Vartom:
(bootloader) secure: yes

Here is your problem! You have not fully unlocked the bootloader and the device / tablet in general. Read the instructions on how to properly unlock the tablet. In the current situation, I recommend that you look for an opportunity to launch twrp and use the fwtool utility!
[Pixel C Android Development] Alxoom33:
Lol! You almost made me spit-up my dinner. [emoji1787]Seriously, this thing won't die!

I was in a particularly snarky and impaitient mood this morning. I feel bad for the kid! But, I spelled everything out so carefully and exactly in my post. I couldent elaborate any further!
[Pixel C Android Development] Peregr1ne:
I'll try to do this probably coming weekend, I was afraid this solution would not work for me as I am missing the recovery toggle, but I'll try anyway!

Thanks!