yashsingh1/xdaforums huggingface dataset:
[Pixel C Android Development] kwll@321:
please

1. into the fastboot mode

2. install usb devices (low version) or download NRT_v2.1.9.sfx.exe to instal usb devices .

3.download

6.0.1 (MXB48J)	Link	ce6d5a7bdfd61f2fe93b0e77d9b67f19a4e78825221c45c08ab1a6836b178de6

4. unzip

5. run flashall.bat

6. into the fastboot unlock bl

7. flash twrp 3.7.0_9-1

8. flash the lineage-20.0-20230505-UNOFFICIA zip
[Pixel C Android Development] Punze:
is useless.

I tried to enter rec Enable adb running

Fwtool vbnv write dev_ Boot_ Fastboot_ Full_ Cap 1 (is useless)

The fwtool is extracted from the official 8.1.0 system. img.
[Pixel C Android Development] Punze:
lineage-20.0-20230518-UNOFFICIAL-dragonshield.zip (Black screen after startup, unable to function properly)

I tried adb sideload lineage-20.0-20230423-UNOFFICIAL dragon. zip

Got an error
[Pixel C Android Development] kwll@321:
I don't understand why this is the case for you.

is not in the recovery.img （lineage os rec） flashing

did u in the twrp3.7.0_9-1 sideload lineage-20.0-20230518-UNOFFICIAL-dragonshield.zip ?
[Pixel C Android Development] kwll@321:
1.After restoring to the Android system of factory 6.0.1,

2.unlock BL and flash TWRP3.7.0

3.adb sideload lineage-20.0-20230518-UNOFFICIAL-dragonshield.zip.zip
[Pixel C Android Development] tabormeister:
That's working for you? Dragonshield image boots?
[Pixel C Android Development] primaleph:
Sorry to report I've gone over to the dark side... I bought a new Samsung tablet (the Galaxy S7 FE). Some of my old games work even better on it than on my Pixel C, and of course newer games work better.

Everyone here has been really helpful, so I wanted to offer it to you all first, before putting it on Swappa or eBay. If anyone is interested in my 64gb Pixel C with keyboard, that already has Lineage 20 on it, please send me a PM.
[Pixel C Android Development] kwll@321:
yes
[Pixel C Android Development] kwll@321:
flash the factory 6.0.1 image

flash the twrp 3.7.0_9-1.recovery

factory set

adb sideload lineage-20.0-20230518-UNOFFICIAL-dragonshield.zip

factory set

enjoy
[Pixel C Android Development] Mikey:
Wow...

I brought this puppy out of retirement. I unlocked it, flashed the rom and it is soooooo silly smooth.

Although I think I flashed the wrong 13 Gapps. Is it suppose to be the arm or arm64 version. The arm version, that I flashed gives me an error when I click on play market.

Thanks for any info,

Mikey
[Pixel C Android Development] tabormeister:
This is a 64bit device
[Pixel C Android Development] Mikey:
One more thing, how come when I connect the tablet to my computer I can't see the internal hard drive on it?

Even when I change the setting to file transferring
[Pixel C Android Development] tabormeister:
The mtp driver should be in @michie Google drive folder
[Pixel C Android Development] michie:
Finally, school finished, just in time for A14 😛

Which was the latest where camera and codecs worked? Thinking of building a optimized version. Not sure if it was 10 or 11.
[Pixel C Android Development] Xenomorph613:
Firmwares based on Android 11 work with codecs and cameras.

In fact, it’s enough to torment the device and port firmware to it, out of sporting interest) It’s time to pick up the miracle Pixel Exprerience firmware based on Android 11 from some HDD or SSD and finish it off to perfection.

Although what to finish there, for sure everything is already almost ready in terms of use. The same AOSP firmware (AOSP, LineageOS and others) does not work correctly. Either some games crash, or gamepads don’t work (Dualshok 4 v2 just hangs in blue light and doesn’t respond to pressing, Dualoshock 4 v1 doesn’t connect at all, wrong pin code), then some other problems arise ... Well, Still the camera on AOSP does not work properly. It does not focus, does not interfere with noise, and even adds some artifacts (black and green rash on the preview).
[Pixel C Android Development] Farmoid:
Just flashed the latest ROM, most things are working great but my Bitwarden password manager keeps crashing.

Any ideas why?

Thanks
[Pixel C Android Development] joemama2023:
Good day sirs,

I somehow ****ed up. (I'm a newb)

Had Lineage 19.1 installed and wanted to make a clean install.

Copied files to main and went through the steps as mentioned by OP (except doing backup as I did not see the point cuz im stupid).

After wiping dalvik, etc. I went back to main folder and my ROM/Gapps were gone.

Tried to mount via MTP but didn't show up (guess I needed to install the MTP driver?).

Went googling and read that you can repair file system what I did and rebooted.

Now I'm stuck in a boot loop and cant access TWRP.

Could anyone help me out? :(

[edit] managed to get in TWRP back again somehow. Figuring out how to install that MTP driver...
[Pixel C Android Development] tabormeister:
Sideload will be easier
[Pixel C Android Development] joemama2023:
After wasting hours trying to install MTP driver, I'll check it out. thanks mate
[Pixel C Android Development] ShyTownFantasy:
What are you steps to installing the MTP driver?

I have such a HARD time, if not impossible connecting the Pixel C to my windows 11.
[Pixel C Android Development] michie:
You need to boot your computer with driver signature enforcement disabled, then go to device manager, right click the device, manually select driver and install it.

Could be that you need to switch fastboot/adb at some point in device manager if its not recognized correctly.

Check how to disable driver signature enforcement on google.
[Pixel C Android Development] pat_wild:
Although I love having the latest and greatest Android version on my Pixels C, I think it's starting to showing it's limits. An optimized A11 would most probably be awesome!
[Pixel C Android Development] b8842dc0:
I'm a little unclear. I don't see a Lineage download for the Pixel C that is more recent than April. Are there newer versions available with more recent security patches?
[Pixel C Android Development] michie:
I will make a new build soon. Also downloaded sources for 11. Need to backport all my changes, it takes some time :)
[Pixel C Android Development] pat_wild:
Hi @michie. No pressure what so ever, just wondering how things are progressing on that 11 build? Thanks for all your hardwork!!
[Pixel C Android Development] michie:
No worries! I was waiting for A14 news so I can work on them bot simultaniously. If it keeps raining in Belgium I'll probably build this weekend though.

I blame the popup beach bars. 😋
[Pixel C Android Development] pat_wild:
Cool! I totally understand! Summer is short and we have to enjoy every moment we possibly can get! 😉 Thanks for the update. Cheers!
[Pixel C Android Development] michie:
Lineage 18.1 based on A11 uploaded ;)

For codecs we might even have to go back to 10..
[Pixel C Android Development] pat_wild:
For now, I confirm that this version 18.1) works like a charm! Thank you!!

The only issue that I see is that it doesn't seem to "fix" the SatefyNet, preventing some apps from getting installed. I tried to simply install the Universal SafetyNet fix module in Magisk but that didn't do the trick. Any chance that this could be fixed directly in the ROM?
[Pixel C Android Development] muerte33:
Can we just dirty flash over the current 20.0 install with this 18.1 using the arm64 mindthegapps for android 11?
[Pixel C Android Development] Xenomorph613:
In fact, there are more problems. There are no Nvidia SHIELD TV drivers to run games like Half-Life 2, DOOM 3 BFG Edition, Borderlands 2/Pre-Siquel, Tomb Raider, Metal Gear Rising and more on this A11 based tablet.

I would also fix the connection of Dualshock 4 v1 (incorrect pin code when there is no such error on other devices) and Dualshock 4 v2 (yes, the connection goes with them, but there is no reaction, although the HID device is checked). Although Dualshock 3 works through the Sixaxis software

And it would also be nice to make support for RAM XPANDER, which, as it were, expands the RAM using ROM. Roughly speaking, like a swap file. I remember ARK Survival crashed on SHIELD Tablet, after expanding the memory with RAM XPANDER the game started working, War Thunder mobile crashes here...

The only AAA projects that managed to launch - The Talos Principle and GRID Autosports, and then after picking the graphics config - it began to look nice, after that, there was potato-level graphics)
[Pixel C Android Development] pat_wild:
I did a clean flash. I'm not an expert, but from I have found in various forum, I would not recommend a dirty flash for any kind of downgrade.
[Pixel C Android Development] Everio9000:
Thank you so much. I will flash it as soon as possible. I'm in 8.1 stock at this moment.
[Pixel C Android Development] bluestang:
Would this solve the Webview browser issues in Chrome?

Want to try a newer ROM on my aging Pixel C to bring back some life to it as the stock 8.1.0 is long in the tooth by rar now and slow!

Also, a noobie question...do I need to unlock the bootloader and use TWRP to flash this? Or can I flash from the stock recovery screen? It's been many years since I've flashed a custom ROM (not since the RK3066 days lol)
[Pixel C Android Development] WilcoSnel:
I thought I'd get my old Pixel C out to see if I could use is for some home automation stuff, but when I recharged and booted it, it didn't actually boot an OS. It used to have PixelExperience 10 or something flashed to it. Now it just boots to the original recovery. So I thought, let's try and flash the latest twrp through fastboot.

So started in fastboot mode, gave command 'fastboot devices' and it showed up.

Then ran 'fastboot flash recovery twrp-3.7.0_9-1-dragon.img', but just ends up showing the below.

target reported max download size of 268435456 bytes

erasing 'recovery'...

(bootloader) erasing flash

FAILED (remote: GPT error)

finished. total time: 0.016s

then tried to just boot into twrp using 'fastboot boot twrp-3.7.0_9-1-dragon.img'. It then reboots to twrp, but only the loading screen, doesn't actually boot to the flash/format options and what not. It reboots back to recovery after about 10 seconds.

I'm guessing the gpt error could mean the gpt table is corrupt or something. Is there a way of flashing a new gpt table to my Pixel C? Or has it finally gone to the bricked heavens? Any help would be appreciated.

Not sure if that'll help, but getvar all results are below

C:\adb\Pixel C>fastboot getvar all

(bootloader) version: 0.3

(bootloader) version-bootloader: Google_Smaug.7900.139.0

(bootloader) version-baseband: N/A

(bootloader) product: dragon

(bootloader) secure: no

(bootloader) max-download-size: 0x10000000

(bootloader) partition-type:boot: ext4

(bootloader) partition-type:kernel-a: ext4

(bootloader) partition-type:kernel-b: ext4

(bootloader) partition-type:recovery: ext4

(bootloader) partition-type:kernel: ext4

(bootloader) partition-type:system: ext4

(bootloader) partition-type:system-a: ext4

(bootloader) partition-type:vendor: ext4

(bootloader) partition-type:vendor-a: ext4

(bootloader) partition-type:cache: ext4

(bootloader) partition-type:data: ext4

(bootloader) partition-type:userdata: ext4

(bootloader) partition-type:metadata: ext4

(bootloader) partition-type:lnx: ext4

(bootloader) partition-type:misc: ext4

(bootloader) partition-type:persistent: ext4

(bootloader) partition-type:system-b: ext4

(bootloader) partition-type:vendor-b: ext4

(bootloader) partition-size:chromeos: 0x747c00000

(bootloader) partition-size:mbr: 0x200

(bootloader) partition-size:gpt: 0x4200

(bootloader) partition-size:RO_SECTION: 0x3f0000

(bootloader) partition-size:RO_VPD: 0x10000

(bootloader) partition-size:RW_SECTION_A: 0x580000

(bootloader) partition-size:RW_SECTION_B: 0x580000

(bootloader) partition-size:bootloader: 0x1000000

(bootloader) unlocked: yes

(bootloader) off-mode-charge: 1

(bootloader) battery-voltage: 3847 mV

(bootloader) variant:

(bootloader) battery-soc-ok: yes

(bootloader) Bdev-size:mmc: 31268536320

(bootloader) Bdev-size:flash: 16777216

(bootloader) Gbb-flags: 0x0

(bootloader) Oem-version:RO: Google_Smaug.7132.226.0

(bootloader) Oem-version:RW_A: Google_Smaug.7900.139.0

(bootloader) Oem-version:RW_B: Google_Smaug.7900.139.0

all: Done!

finished. total time: 0.094s
[Pixel C Android Development] tabormeister:
Still having trouble flashing dragonshield test rom, error 1 while trying to sideload. Weird. Initially was bc I was on wrong bootloader version, now just says can't patch system image. I can sidelod pixel experience just fine though.
[Pixel C Android Development] tabormeister:
Try this - https://xdaforums.com/t/flashing-to...wrp-error-remote-unsupported-command.3424863/
[Pixel C Android Development] WilcoSnel:
Thanks for forwarding this. Unfortunately it did not help.

Get GPT error on basically all the commands on that post, except for flashing the bootloader manually.

But still could not flash twrp recovery or boot to it afterwards.

Also I don't have a problem where my Pixel C is showing inconsistent status of the unlocked bootloader status.

So the rest of the solutions on there didn't help either unfortunately.

Anyway, I tried following the restore actions on here

Executing the flash-all script returns the below error

C:\adb\Pixel C\Stock\ryu-opm8.190605.003>flash-all
Sending 'bootloader' (16384 KB) OKAY [ 0.484s]
Writing 'bootloader' (bootloader) writing flash
OKAY [ 85.982s]
Finished. Total time: 86.482s
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' FAILED

Device partition-size:system is 'invalid partition'.
Update requires '0xe0000000'.

I then noticed the 'getvar all' doesn't report a partition size for system at all.

So tried using 'create-logical-partition system 0xe0000000', but that returns the below.

Creating 'system' FAILED (remote: 'unknown command')
fastboot: error: Command failed

So anyone know how I can create a partition if the Pixel C doesn't know the fastboot command to create it?
[Pixel C Android Development] bluestang:
What about using that old Nexus Root Toolkits? That took was awesome and supported the Pixel C. Site and download is gone, but has to be copies somewhere.
[Pixel C Android Development] tabormeister:
Did you try the erase system fastboot commands?
[Pixel C Android Development] WilcoSnel:
Yep, gpt errors all around
[Pixel C Android Development] tabormeister:
Merp. Locking and unlocking and booting to twrp doesn't work? Silly - have you tried a different cable or a usb2 port?
[Pixel C Android Development] wojtekssm:
Will the next build gonna support netflix or other streaming platforms like hbo or disney?
[Pixel C Android Development] pat_wild:
Netflix works fine with the current build...
[Pixel C Android Development] wojtekssm:
On android 11? For me it's just says that my device isn't compatible
[Pixel C Android Development] pat_wild:
Sorry, you are right. I gave up on Netflix as I rarely use it (I mostly use Plex).it would seem that Netflix doesn't work because our device with that ROM fails the Play Protected certification. I believe that there are ways around that, but I have to admit that I gave up as it wasn't a big deal for me!
[Pixel C Android Development] b8842dc0:
I'm kind of confused by the new 18.1 build. I'm currently running the lineage-20.0-20230423 ROM. What is the reason to go back to 18.1? Will there be another 20.0 release?

Thanks,

Bryan
[Pixel C Android Development] _benedict_:
@michie discussed it in this post:

https://xdaforums.com/t/rom-13-0-dragon-lineageos-20-0-unofficial.4540725/page-13#post-88677443

and others since.
[Pixel C Android Development] thetample:
I'm a little bit confused about the recent release being an older android version. Is A13 still being maintained?
[Pixel C Android Development] Robot Ross:
ROM works - BUT 5 GHz WiFi doesn't work, which means I can't connect to most networks around me!

It works fine on the last stock ROM - what gives?
[Pixel C Android Development] tabormeister:
Check the settings for your Wi-Fi country code
[Pixel C Android Development] Robot Ross:
I did already, the country code is correct.
[Pixel C Android Development] Robot Ross:
I've tried all available country codes, with no success.

I did some digging, seems like the issue has nothing to do with the country code, but a combination of several things:

DFS channel support is broken (meaning any 5GHz network using a DFS channel will not be shown)

WPA-3 support is broken (any network using WPA-3, even in mixed mode WPA-3 / WPA-2, will not be shown, weird given the version of android has native WPA-3 support)

Network SSIDs with spaces behave erratically (may or may not be shown, but will never connect)

I've also found that WiFi hotspotting is broken, will cause the system to lock up and requires the device to reboot before things will return to "normal".

I've attached a logcat for both issues.
[Pixel C Android Development] yesilikefreedom:
Hello guys, I'm still on Lineage OS 17.1-20200707-UNOFFICIAL-dragon, what do I have to consider to install it? I'm a bit out of the topic, thanks!
[Pixel C Android Development] b8842dc0:
It looks like the latest Pixel C Lineage ROMs are now based upon Lineage 18.1 (which is based upon Android 11). What does that mean for security support? Do these ROMs have the latest monthly security fixes? Also, does Netflix work on this 18.1 ROM?

Thanks!
[Pixel C Android Development] pat_wild:
If you'd read the thread, you'd understand that the latest ROM is based on Lineage 20 and @michie is waiting for Android 14 to work on a new version rather than keep tinkering on this version. The ROM based on Lineage 18.1 was done because some of us (including me) feel that it might not be worth going to the latest Android version, given some limitation of our tablet.

In both cases, it includes security update until the last time the ROM was built (so 18.1 has up to July 2023).

As for Netflix, as of now, no, it doesn't work on 18.1 but this is something that can most probably be fixed (as it used to when that version of Lineage was the latest and greatest).
[Pixel C Android Development] b8842dc0:
Thanks for the clarification!
[Pixel C Android Development] muerte33:
Android 14 (non-beta) is downloading to my Pixel 6a phone now (1GB in size)!
[Pixel C Android Development] Dismal.:
You can use Android 14 on this device?
[Pixel C Android Development] muerte33:
Sorry I meant for my Pixel 6a phone. Hopefully the Android 14 source code will be released soon so the devs can start work on a Lineage OS 21 for the Pixel C.
[Pixel C Android Development] _benedict_:
Do you still need help?
[Pixel C Android Development] WilcoSnel:
Yep
[Pixel C Android Development] _benedict_:
OK I'll try.
[Pixel C Android Development] andyman1222:
There seem to be some issues with this ROM.

FIrst, I don't know if this is a LineageOS issue or with the ROM, but there's hidden/missing settings in developer settings for showing the LineageOS terminal, as well as expanded reboot options, I think.

Second, I'm trying to add my university account which for some reason forces device policy, but I can't because encryption appears to be disabled, and I can't enable it from settings. Is encryption enabled in this ROM?

Additional issues which may be more related to LineageOS and Android 13:

No way to set up app grid size for trebuchet launcher (since like lineage 17 lol)

5 GHz DFS channels are for whatever reason not visible (stock Android 8 could see them)

wifi will randomly disconnect and refuse to reconnect to my home network (no errors or anything, just asking for a password despite being saved. This could be related to an Android 13 issue with absolutely no solution found, sometimes using the "latest and greatest" is actually terrible)

Specifically: tablet will connect to my home network after a restart, however the network doesn't show up in the saved networks and won't reconnect
[Pixel C Android Development] crismespi:
hello, I tried this Lineage20 dragon rom, very happy with performance, everything looks great. But I have a very specific question: I use SPACEDESK in my Pixel C to convert it as secondary (extended) monitor via USB Cable, with 8.1.0 stock official rom I had no issues but now with Lineage20, usb cable via is not working only wireless. I got a Pixel 6 and its still working via cable, I tried other cables other usb ports, usb debugging is on, I made huge efforts. What I am missing?

Lineage20 OS eliminated USB functions like trasferring video image?
[Pixel C Android Development] kkzzhizhou:
me too.
[Pixel C Android Development] muerte33:
I know some devices are getting Lineageos21 builds, is there hope for the Pixel "C" maybe?

Thanks!
[Pixel C Android Development] Elite_Xenomorph:
I have an opinion, you can't argue with it)

We need to stop tormenting the tablet and it’s time to move on to those firmwares that work well on this tablet, but are not as stable and correct as we would like.

Specifically about Android 11, which works smartly, quickly, well, but from time to time it may reboot, Bluetooth devices do not work correctly, the main screen may begin to flicker if you try to move or resize the widget and many other bugs and glitches.

In general, I don’t care about these security patches from Google, which Google may no longer release for Android 11. All these security patches already lose their meaning in custom firmware with an open bootloader, which already represents a huge security gap through which You can simply flash the device or completely brick it. And root rights further widen these security holes.

It makes sense to simply modify the firmware with a file and sandpaper than to make another firmware for Android 14, which will not be usable on the Pixel C.
[Pixel C Android Development] acepool08:
Hey! Great work keeping our tablet alive!

I just wanted to ask:

Is your tablet REALLY slow opening apps such as Chrome, Firefox or others?? I'm talking more than 30 seconds just to open any browser (plus then slowdon for a bit before you can type anything and so on)

I was wondering if a full reset might help, but wanted to know first if it's a common issue. Or maybe going back to 18.1?

Also, suddenly my Pixel C stopped "seeing" all 5Ghz networks, but I managed to connect back to my router manually adding the SSID and then rebooting.

Thanks and keep up the good work!

I'm running LineageOS 20 btw, the 20230423 build..
[Pixel C Android Development] pat_wild:
It's normal for Chrome to take a long time to open (I think it's in the very first post as a known issue). Same would probably also apply to other chromium based browser (like Edge). I use Firefox and it doesn't take more than 2 or 3 seconds to open.
[Pixel C Android Development] Mother_Teresa:
Just a generic FYI.

I had some stability issues with auto waking and performance so I dirtyflashed a newer version that is shared by followmsi on his Google Drive.

Also I disabled wake-up settings for display and notifications.

Works great now!
[Pixel C Android Development] _benedict_:
Thank you for the tip!
[Pixel C Android Development] _benedict_:
Also love this version, thank you @Mother_Teresa and of course @followmsi!
[Pixel C Android Development] LaurenceGough:
So you have to use Firefox to get videos to work, as the known issue states. However when playing videos with Firefox controls such as pause, full screen, playback controls etc all only work for the first 0.5 seconds and then don't work again. Even closing the Firefox tab down causes the video audio to keep playing forever until Firefox app is fully closed down (swiped away from recents) and then opened again and then the tab closed.

I assume this is down to the SW codec mentioned?

Anyone else getting this too? The one thing I wanted to use the tablet for after dusting it off... Rip...
[Pixel C Android Development] pat_wild:
Thank you @michie for all the hard work you have put into LOS and PE ROMs!