yashsingh1/xdaforums huggingface dataset:
[Pixel C General] followmsi:
Pls install chrome (webview) via opengapps ..this should solve your problems.

Ongoing gapps issue since Oreo .. also on lineageos .. on all my devices.

Either use config file from opengapps or a package with chrome included.

On Pixel C you have plenty of space left in system partition.

Cheers
[Pixel C General] m+a+r+k:
Good to know for the future, thanks.
[Pixel C General] followmsi:
You can open any terminal app and enter "df" .. on every Android device actually. No root required.

$ df

Filesystem 1K-blocks Used Available Use% Mounted on

rootfs 1424892 4456 1420436 1% /

tmpfs 1426908 472 1426436 1% /dev

tmpfs 1426908 0 1426908 0% /mnt

/dev/block/platform/700b0600.sdhci/by-name/APP 3555040 1108560 2430096 32% /system

/dev/block/platform/700b0600.sdhci/by-name/VNR 299124 121980 170968 42% /vendor

/dev/block/platform/700b0600.sdhci/by-name/CAC 396744 468 388084 1% /cache

/dev/block/platform/700b0600.sdhci/by-name/UDA 25396556 15064268 10315904 60% /data

tmpfs 1426908 0 1426908 0% /sbin

/dev/block/loop0 60400 60 59032 1% /sbin/.core/img

/data/media 25396556 15064268 10315904 60% /storage/emulated
[Pixel C General] m+a+r+k:
Interesting, system 56% used on Pixel C compared to 90% (OpenGApps Pico) on Nexus 7 :)

Thanks for that.
[Pixel C General] Alxoom33:
Just uninstalled SuperSU using [MENTION=1143630]osmosis[/MENTION] UnSuperSU app and fastboot flash of the stock boot.img. Installed Magisk v. 15.1 and Magisk Manager 5.5.2. Installed [MENTION=5480152]followmsi[/MENTION]'s custom kernel and flashed Magisk 15.1.zip again in TWRP, rebooted and everything is working great!
[Pixel C General] nex_t:
Are the instructions from the first post of this thread, still available ?

I tried the firts steps, but i'm stock on " waiting for devices " after i type the command " fastboot flashing unlock "

I tried different adb USB drivers, different Fastboot tool versions, OEM Unlocking enabled, USB debugging enabled.

When i'm in fastboot, the tablet isn't recognized in Windows ( 10 X 64 ) Device Manager, but after i reboot in Android, it is

Any ideas how to fix this ???
[Pixel C General] nex_t:
I was able to unlock the bootloader, but after i installed the TWRP, bootloop - TWRP, i couldn't get into the OS, anymore, so i installed the factory image

What / where / am I doing wrong ?
[Pixel C General] hugehead83:
Check out my more recent post on this. I'm now using magisk instead of superSU but the process is the same. http://xdaforums.com/showthread.php?p=74789442

Sent from my LGLS992
[Pixel C General] bigtreiber:
I'm having problems with my Pixel C.

I went through the process with unlocking the bootloader, flashing TWRP, Gapps and Magisk (all went fine), wiped data and cache and tried rebooting the system.

Now I'm stuck with a "Google" Boot Screen (Black screen, white Google logo) and nothing happens.

Any ideas?

bigtreiber
[Pixel C General] Alxoom33:
If you are on Stock, why did you flash Gapps? Need to flash custom kernel. [MENTION=7929293]follwmsi[/MENTION] has a thread on XDA.
[Pixel C General] hugehead83:
I would suggest flash the full factory image and start over.

Sent from my LGLS992
[Pixel C General] m+a+r+k:
You didn't use the latest Magisk did you?

15.3 works. Anything later causes the bootloop you have.

Try flashing the boot.img of your present build https://developers.google.com/android/images and then Magisk 15.3 in TWRP.

You don't need GApps and you don't need custom kernel.

Later: I see followmsi says Magisk 16.3 now works. Certainly 16.0 and 16.1 don't.
[Pixel C General] hugehead83:
Almost forgot about this! Thought I was the only one.

Sent from my LGLS992
[Pixel C General] followmsi:
Did install magisk 16.3 on fresh boot.img today .. no bootloop and no problems do far.
[Pixel C General] pkelly517:
You don't mention that you flashed a rom.

There's your problem.
[Pixel C General] bigtreiber:
Thx for the Information, that solved the Problem :) I tried Magisk V16 => Bootloop. It works with 15.3.

I'll try 16.3 tonight,

bigtreiber
[Pixel C General] m+a+r+k:
Good to hear. Thanks for the feedback.

---------- Post added at 20:07 ---------- Previous post was at 20:05 ----------

Great!

Don't forget to report back on Magisk 16.3.
[Pixel C General] kingzero666:
16.3 does not work either.
[Pixel C General] followmsi:
Pls don't make wrong statements here .. 16.3 works fine !

Just installed it on fresh boot.img

What are your problems ?

Pls more details !
[Pixel C General] kingzero666:
Yeah, got everything to work now. 16..3 works fine too.

If you're interested in what was going on, check here:

https://xdaforums.com/pixel-c/development/twrp-3-0-2-0v16-t3400503/page56#553
[Pixel C General] Beretta007:
Anyone help. I have remix OS on may tablet and want to restore the standard android OS. Anyone got any pointers. Can I just run custom recovery over the top or do I need to copy anything out first. Not bothered about the data

Thanks
[Pixel C General] Alxoom33:
Just flash the latest Google factory image.
[Pixel C General] wintermute000:
Trying to go from pure stock and step 1 unlock bootloader - but stuck at fastboot. I can get adb reboot-bootloader to work and my device says "waiting for fastboot" but the fastboot command just plain doesn't work and hangs.

I have the google driver installed and when the device is not in fastboot mode it comes up as a Nexus in device manager (have also flashed numerous other devices off this PC before). adb devices and adb reboot-bootloader works fine, just not fastboot and fastboot mode. Any ideas?

I've even downloaded sdk-manager and executed sdkmanager.bat extras;google;usb_driver and sdkmanager.bat platform-tools, and tried the fastboot it installs. I also tried re-installing minimal adb drivers package. I realise my problem is likely fastboot + usb drivers but I can't figure it out. ADB and normal operation is fine.

Every other nexus I've ever had its simply fastboot oem unlock but neither that nor fastboot flashing unlock does anything, just sits at <waiting for device> on the PC and nothing happens on the tablet (which is in the waiting for command fastboot screen and connected via a good quality anker cable).

EDIT fixed - for anyone who cares - to update the driver, you don't just run the command in sdk manager, but you have to manally go into device manager whilst the device is in fastboot mode, then point to the files it downloads in the extra directory
[Pixel C General] Shibang:
Has anyone tried Magisk 16.4 yet? Curious to know if that works or if 16.3 is the version to stay on for now.
[Pixel C General] Alxoom33:
Been using it since it was published. I think in March or April. Works fine although sometimes the widget will fc. I just reinstall the apk and a is well!
[Pixel C General] hugehead83:
I put it on this week with the June update. No problems! Definitely skip 16.0.
[Pixel C General] kbal86:
Hi there,

I'm trying to root and flash a ROM on my Pixel C, however I keep having a weird issue.

I have unlocked the bootloader and have flashed TWRP

C:\Pixel C>fastboot flash recovery twrp.img

target reported max download size of 268435456 bytes

erasing 'recovery'...

(bootloader) erasing flash

OKAY [ 0.109s]

sending 'recovery' (11872 KB)...

OKAY [ 0.325s]

writing 'recovery'...

(bootloader) writing flash

OKAY [ 0.390s]

finished. total time: 0.825s

Then when I restart the tablet and go to open the recovery, it goes to the normal Android one and says 'No Command', whenever I've flashed TWRP it's always gone directly into that and never back into Android recovery.

Am I missing something?
[Pixel C General] hugehead83:
Check out my post on this. I'm now using magisk 16.4 instead of superSU but the process is the same. http://xdaforums.com/showthread.php?p=74789442
[Pixel C General] kbal86:
That was the exact post I was following actually, my only issue is TWRP isn't showing up.

The overall rooting procedure doesn't really change:

- Do initial configuration and let it finish setting up

- Enable developer options

- Enable USB debugging

- Unlock Bootloader from ADB:

adb reboot bootloader

fastboot oem unlock

fastboot reboot

- Install TWRP from ADB:

adb reboot bootloader

fastboot flash recovery <twrp img file name>

fastboot reboot-bootloader

- Hold the power button+VolumeDown (7-10 seconds) to get to the bootloader menu and select Recovery. TWRP should be there.

- Use TWRP install menu to Install SuperSU.

So these two aren't working for me, I flash TWRP and when I go into the bootloader it's not there.

Am I using a wrong version?
[Pixel C General] hugehead83:
Hmm possibly? Or maybe a corrupt download? Maybe re-download from the source in the OP of this thread? Or try an older version of TWRP?

I'm out of ideas now :(
[Pixel C General] tevil:
guys so heres my issue, my screen stopped working after a few of the last android updates. I have no way to get into any settings to enable debugging or dev mode. All I can do is get to fastboot. Would I be able to unlock my bootloader and flash TWRP and a rom? Im trying to see if flashing to an older version or custom rom will fix this issue since it obviously started after their updates.

also I have no way to restore since my recovery partition is corrupted..... odd since this tablet has never been rooted at all.
[Pixel C General] Mother_Teresa:
If you can boot to fastboot and use adb you can do a lot.

Check this older topic fe. and flash the kernel also, posted in Pixel C Android Development.

You can just boot to a TWRP recovery image without the need to have flashed it if you want.
[Pixel C General] tevil:
I unlocked my bootloader and was able to boot to TWRP using the wugtoolkit. I was wondering though If I could install a custom ROM through that without having TWRP fully installed. If I install a custom ROM would I still need to worry about the force encrypt or would it pretty much wipe everything anyway?

Thanks

edit:

its just not working, I was wrong and it has to be hardware related. Even in TWRP it no longer works with touch. Im going to actually pull the thing apart, reseat some of the cable and clean it all up and see whats going on. Im disappointed that this pricey device didnt really last that long, I actully did like this tablet.
[Pixel C General] Mother_Teresa:
Hard to say what is what.

Can you manage to just flash some original image?

I would worry about the rest after you managed to get it to work etc.

The toolkit may be outdated also, I just make sure my PC has the drivers to connect to the device to push or load as I please.

TWRP needs not be installed, it can be just used when you let the device boot to a twrp image.

Again, flash a factory image with bootloader and all etc (will wipe device) and go from there.
[Pixel C General] tevil:
I know its hardware now. I was able to boot to temp TWRP and it still didnt work so its not anything with googles software since TWRP is well before that. . My stock android recovery is blown out for some reason (little android with exclamation = no command) but can get to the further in reset menu. that worked once then not again. I figured if I could Cyo on there or something it might work again but without touch on the recovery menu for TWRP Im not getting to far.

I was thinking of just pulling the screen off and trying to heat gun the main board and see if a reflow might help. At this point Ive really go nothing else to lose as its just a big bright dead screen right now.
[Pixel C General] Alxoom33:
Do you have adb and fastboot working?
[Pixel C General] tevil:
I have the drivers working, The ADB and FASTBOOT work through the toolbox so technically yes. I could just install them on the machine and they should work.
[Pixel C General] Alxoom33:
You might want to try Lineage OS. See OP.

https://r.tapatalk.com/shareLink/to...share_tid=3591152&share_fid=3793&share_type=t

[ROM][OFFICIAL][LineageOS][15.1][dragon] / [Lineage-16.0] -> 20190806

I have 16.0 (Android P) running on my Pixel C without issue.
[Pixel C General] Mother_Teresa:
It took me flashing my Pixel 2 XL to understand your issue.

I hope you did not break it yet ;)

The no command 'dead android' screen was new for me also.

In that screen press the power and click the volume-up. After the volume-up button is released you should get to the screen with a menu where you can choose, fe, to load 'adb mode'.

Also from there you can boot to 'bootloader' for sideload etc.
[Pixel C General] tevil:
yes I can get to that, thats how I was doing everything. Im learning these issues are all common with this tablet. To me this should call for some kind of recall on the device. this was not a cheap tablet. I havent opened it yet, just no time right now. The thing is I have a hunch that its not actually "the screen" thats the problem but something on the board causing the screen not to communicate with the rest of it. I thought trying the reflow might help. I tried chilling it in the freezer for a while first and that did nothing.
[Pixel C General] Mother_Teresa:
I bet you have a fair sense on such. Just wanted to make sure you managed to use that new menu (as it was new to me) ;)

Being able to flash all software would make me look for hw issue also if you get booboos.

I once opened up as much as I managed with a screwdriver of some laptop with a broken screen...

Poking here and there on a wire under the screen and wiggling/abusing it like the monster I am made the screen work.

It is now my backup pc.
[Pixel C General] tevil:
Im going to give it all a shot. Have to break out my heat gun for it since the screen is basically glued in place. Maybe tonight if I get time. Ill def let everyone know what I find out. one major problem I have though is Im not able to actually shut the tablet down. Since I can only use the physical buttons all I can do it reset it so Ill be working on it all while its on which bothers me.
[Pixel C General] tevil:
well took the screen off and wouldnt you know as soon as I disconnected the ribbons the screen no longer works at all. The lights on the back will turn on as if the tablet is working but the screen never lights up. Im assuming the screen has shorted. Im not going to buy another screen for this since its relativly pricey. Maybe if someone has a screen theyd like to sell cheap off their broken C or donate, Ill give it a shot and see if the screen is/was the issue or something internal. At least it might help solve other peoples issues.

Thanks all
[Pixel C General] 12paq:
Sorry you're having problems with your Pixel C.

I was too. However, I just bought my 2nd Pixel C from eBay for $122.00. It was in great shape and seems to be near new. Go take a look. They're going really cheap on eBay now. Probably way cheaper than a new screen.

Good luck!
[Pixel C General] austin12301:
Issue flashing TWRP

I am having a issue when I use ADB on my Windows laptop. When it is plugged into the laptop it shows up in device manager as Pixel C but when I use ADB to reboot into the boot loader I cant send commands anymore and it shows up in device manager as a "Unknown device".

Any ideas?
[Pixel C General] Alxoom33:
I believe you need to download updated drivers from the Andriod Development website.
[Pixel C General] austin12301:
So I tried installing the diver via these instructions on the android dev site but that didn't solve the problem and I also tried the guide to make a .INF file and install it but Windows said it was not signed and would not let me install it.

stackoverflow .com/questions/34775508/where-is-the-windows-adb-driver-for-the-pixel-c

developer .android .com/studio/run/win-usb

Sorry for the weird spaces, XDA wont let me post links until I've had more post on the site
[Pixel C General] bosartig:
I've been jackin with the same issue for 2 days. I've dl'ed the google usb driver in sdk tools, etc. Windows just doesn't want to cooperate.
[Pixel C General] Farmoid:
When the device shows as 'Unknown Device' in the device manager, you need to force update the driver with the adb driver found in the Android SDK.

This allows the device to be seen in fastboot.
[Pixel C General] Mother_Teresa:
You can reboot Windows with advanced options to allow installing unsigned drivers.
[Pixel C General] tevil:
all the ones I see are like 200+

Google no longer makes android tablets correct?
[Pixel C General] dictionary:
This is driving me up a wall. I can't get win10 to recognize the Pixel C in Fastboot. I've tried multiple drivers, and nothing is working. Does anyone have ones that will actually work? I'd truly greatly appreciate it.
[Pixel C General] Alxoom33:
Try changing cables.
[Pixel C General] dictionary:
Already tried that, lol. Thanks though. I've been around Android for a long long time, but this is one of the few devices that's just weird out the gate. It's a combination between the device, and Win 10. I might have to flash a linux distro just to unlock bootloader and install recovery
[Pixel C General] Alxoom33:
Did you install updated google drivers recently? Also try turning off and re authorizing USB recovery. Reboot computer and try again.
[Pixel C General] Mutiur81:
Yes I too was getting this issue. Switched to Ubuntu for fastboot commands.
[Pixel C General] madejackson:
I had the same issue and managed to get past it via downloading the latest driver directly from google and then installing them manually via device manager via "Have Disk".
[Pixel C General] Alxoom33:
Didn't work for me. Drivers are up to date. My computer recognizes the Pixel C and my Pixel 2 XL; Fastboot works fine with the P2XL, but not with the Pixel C. There must be an issue with Pixel C at this point. Started about 2 months ago.

o_Oo_Oo_O
[Pixel C General] Mambobuzzz:
Is it possible to relock bootloader?
[Pixel C General] Alxoom33:
Yes, but it will wipe clean all of your user data and internal storage. So make a backup on your computer to restore after locking the bootloader.
[Pixel C General] Mambobuzzz:
Use FWUL, had the same problem. Solved it sooo..
[Pixel C General] Mambobuzzz:
Ok. Thanks.
[Pixel C General] Mattzalem:
Hello and thanks for your work!

I search for su.img, and SuperUser.apk, do you know where i can dowload this files safely?
[Pixel C General] Alxoom33:
That's really old tech. Look for latest Magisk apks
[Pixel C General] fossy123:
Hi guys.

I have a big problem with my Pixel C Tablet.

After turnig off i wanted to start the tablet nomally but I get the little green Android with message "no command" - "Kein Befehl".

OK. I tried to install the backup but it wont start. It always ends up to the little green Android.

Now I installed ADB on PC etc. downloaded the original ROM and wantet to make a new clean installation.

But my biggest problem is that I can not unlock the boot loader because I did not activated the OEM unlock on my tablet while it was working.

So is there any possibility to get a new installation on my Pixel?

I also tried sideload. But here I get a message: "fastboot flash ....... command failed"

I tried different USB cables and USB 2.0 and 3.0 ports. But nothing helped.

The command "fastboot devices" brings "6130000644 fastboot". So communication works.

fastboot flash recovery twrp.img

Sending 'recovery' (16520 KB) OKAY [ 0.437s]

Writing 'recovery' FAILED (remote: 'unsupported command')

fastboot: error: Command failed

ADB sideload with stock zip brings:

Total xfer: 0.00x

On tablet:

Finding update package....

Opening update package......

Veryifying update package.......

E: footer is wrong

Update package veryfication took 0.0s (result 1).

E: Signature veryfication failed

E: error 21

E: failed to open driver control: No such file or directory

Installation aborted.

Can anyone help me???

Thanks a lot

Mathias
[Pixel C General] krakard:
EDIT :

My bad ! I am on the Lineage ROM ! thanks !

now i try to make the keyboard work and I will be very happy
[Pixel C General] Punze:
fwtool

drive.google.com

Fwtool

Extract from official Android 8.1.0
[Pixel C General] charesa39:
A little search goes a long way: http://xdaforums.com/showthread.php?t=3034811
[Pixel C General] Scarfacez2007:
It's worked but need for busybox too?
[Pixel C General] beardymcgee:
Search the play store for busy box installer...
[Pixel C General] Alexanderbeldan:
This did not work for me. I had to put:

fastboot oem unlock

Thanks for the great guide.
[Pixel C General] oRAirwolf:
That is very odd. Google changed it to fastboot flashing unlock and that is the command I used when writing the guide. Anybody else know what may be causing the discrepancy here?
[Pixel C General] vevmesteren:
Android Ota updates will continue rolling in our will I have to update manually after doing this? Pixel is coming soon want to have all my ducks in order for us arrival...

So excited
[Pixel C General] oRAirwolf:
Yeah, if you modify it, you will no longer be able to accept OTA updates.
[Pixel C General] Rabbit1623:
Thank you

I finial rooted my Pixel C, it worked. thx again.

but I find a problem on my Pixel C, I cant use Shadowsocks with NAT mode, VPN mode is ok.

other root app worked as usual, just Shadowsocks.
[Pixel C General] vevmesteren:
So if I want to install updates? Install them them from the googly source and loose root?

Keep tabs on the XDA forum? Install updates manually?

thanks
[Pixel C General] oRAirwolf:
Yeah, updates will have to be installed manually from the images. Hopefully people will start releasing some ROM's for this device that come pre-rooted.

[MENTION=4395895]BeansTown106[/MENTION], you are our only hope!
[Pixel C General] vevmesteren:
For my own educations sake. My rooted nexus devices receive updates even when rooted. Why not this one?
[Pixel C General] doumer:
I'm already rooted with phhusson's boot-img and modified vendor img (to retain encryption). will updating to the latest OTA (manually via fastboot) and following this guide give me root and retain encryption? my data shouldn't be lost since I already did the flashing unlock step, right?
[Pixel C General] charesa39:
Well, technically, you will receive the OTA. You just won't be able to apply it if you have modified anything (ie. system, boot, custom recovery, etc.).
[Pixel C General] jptechnical:
Thanks for the awesome walkthrough! I have been waiting on rooting for just this post.

Here is my question... can I get rid of the Bootloader Unlocked and OS Verification message at startup? I would just change the bootloader option, but I don't' want to undo the hard work I just did. If it isn't an option, I can live with it, I have had the same message on my Chromebooks since day 1, so it isn't as if it is new to me.

-JP
[Pixel C General] ilpolpi65:
same here
[Pixel C General] oRAirwolf:
I don't know of a way to get rid of that, sadly. I find the 30 second wait to be completely unnecessary. Hopefully a badass dev like [MENTION=4867279]cheep5k8[/MENTION] can find a way to disable that.
[Pixel C General] Doug2507:
Has anyone written a kernel that allows it to be overclocked yet?
[Pixel C General] bill3508:
No we just have the one. I'd be more interested in getting the a53 cores enabled if possible.
[Pixel C General] Doug2507:
Good point. When i ran HWBPrime only 4c were enabled. I put this down to the benchmark, didn't realise a53 wasn't enabled....
[Pixel C General] bill3508:
Yeah they are disabled for some reason. Not sure if we'll ever get to the point where we can fix that.
[Pixel C General] Doug2507:
Think i might just rtb and grab 820 when its released...
[Pixel C General] wangsiyu:
After unlocking,boot will pause for 30s everytime.Is there a way to skip it?
[Pixel C General] Rox598:
Nope
[Pixel C General] WhatZitT00ya:
Hi!

Fastboot doesnt work for me.

I can boot into bootloader with the ADB command but when I try to unlock the bootloader with "fastboot flashing unlock" nothing happens.

I only get the message "waiting for device"

Hope you can help me with this. I cant find a fix for my problem.

ADB driver seems to installed correctly (no yellow triangle in device manager), in fastboot there is a yellow unknown device triangle.

Had no problem with the Nexus 6P, the Pixel C drives me crazy...
[Pixel C General] JoeDat:
Yeah, this didn't work for me either. Had to use 'fastboot oem unlock'. Unlocked fine.