yashsingh1/xdaforums huggingface dataset:
[Pixel C General] WhatZitT00ya:
Nope, not working (waiting for device)

Seems my device is not recognized in fastboot.

No problem with adb but it wont show up when I type fastboot devices...
[Pixel C General] beardymcgee:
Hey have you guys flashed the twrp yet if so go to advanced and click fix fast boot should fix the issue
[Pixel C General] WhatZitT00ya:
No custom recovery flashed.

All original.

edit: I got it!

(At least it works for me)

In Windows Device Manager, the Pixel C wasnt recognized correctly in fastboot mode. So there was an unknown device with an yellow triangle.

What I did is (my Windows is in german, so dont know the english labels exactly):

right click on the device

update driver

search for driver on the computer

now you dont point to the driver directory, instead choose "choose from a list of device drivers" (hope this translation is roughly right =) )

from the choose "Android Device" and then "Android Bootloader Interface"

This worked for me...
[Pixel C General] UK_Wildcats_Fans:
Thank you for putting together this guide. I just did it this weekend. I had trouble getting the ADB drivers to work but eventually got it to work using the PDAnet drivers. The SkipSoft tool is a good way for people to get their drivers. You may want to mention it in the OP.
[Pixel C General] Scarfacez2007:
Hello everyone I just wondering now new update 6.0.1 (MXC14G) and can root? ASAP
[Pixel C General] geckocavemen:
Is it necessary to use the custom kernel if using supersu 2.67? I've got a 2013 Nexus 7 that did not require a custom kernel to root and I was wondering if the Pixel C works the same way. Thanks.

Edited to add: after doing more reading it appears it is necessary to use the custom kernel due to the peculiarities of the Pixel C in relation to it starting life as a chromebook.
[Pixel C General] natezire71:
Why do we have to format userdata before flashing the modified boot.img? Seems unnecessary.

Would you have to do that every single time?
[Pixel C General] dkryder:
you want to format /data because it is initially encrypted. this establishes a non encrypted partition. [i think?]
[Pixel C General] vanydotk:
The new TWRP can decrypt the partition now so it shouldn't be necessary anymore, right?
[Pixel C General] dkryder:
as long as the partition is in an unencrypted state usable by the device and not just to allow tasks inside of twrp to be completed.
[Pixel C General] drewski_1:
i think it's up to your preference. encryption is more secure, but also slows the overall performance of the tablet.

at least this was the case on the Nexus 9. maybe with the X1 CPU this is less of an issue.

---------- Post added at 05:05 PM ---------- Previous post was at 04:43 PM ----------

my Pixel C arrives tomorrow and am collecting files needed for Root.

just to clarify, for installing SuperSU for root, i will flash 2.67 or higher at Step 8 of the Root section? instead of the push of su.img & install of superuser.apk that is in the guide.
[Pixel C General] natezire71:
I don't think so. The TWRP for the Pixel C still can't decrypt.
[Pixel C General] oRAirwolf:
As much as I appreciate [MENTION=4867279]cheep5k8[/MENTION] getting TWRP working on the Pixel C, it disappoints me that they don't really seem to have any interest in making a polished, official version.
[Pixel C General] natezire71:
I'm sure if we donated a Pixel C to one of the main TWRP devs, they'd be more willing.
[Pixel C General] timothydonohue:
twrp won't mount the data partition appropriately. i can push su.img and install superuser.apk while in recovery mode, but when i boot up into android, it keep telling me that i don't have root. so, i can't update superuser or install busybox, and more importantly, i can't install any of the more important apps that require root access. dang it.

edit: okay, maybe total fail because i did a few of the last few steps out of order. restarted at a data wipe near the end, reflashed kernel, su.img, and adb install of superuser.apk. so far, root access granted!

now to find a working setup for xposed that i can get going on this, as well as getting adaway up and running. need me some minminguard
[Pixel C General] drewski_1:
to answer my own question, yes, flashing Chainfire SuperSU 2.68 at Step 8 of Root works in lieu of the phh process outlined in the Guide :good:
[Pixel C General] Grims:
I am having a heck of a time getting this to work on the N Preview image. SuperSU or any other root app just tells me it cant install binaries.
[Pixel C General] dkryder:
is it necessary to delete /system/bin/install-recovery.sh?
[Pixel C General] rg1003:
Received my pixel C yesterday and joined the N beta. N installed fine but like others fastboot does not seem to recognize the device (Windows 10, OEM unlocking and USB debugging are both enabled, USB drivers installed and up to date via SDK Manager)

I too have the yellow triangle in device manager but when I select "choose from a list of device drivers" Android Device does not appear in the list.

adb recognizes the device but fastboot does not. All I get is "Waiting for fastboot command....". "fastboot devices" lists nothing, does not even state that no devices were found. "fastboot flashing unlock" and "fastboot oem unlock" do nothing.

Another odd bit of behavior is that even though "Pixel C" shows in Windows Explorer when I navigate to it Windows Explorer states the the "Pixel C" folder is empty.
[Pixel C General] drewski_1:
you may need to install more drivers.

http://developer.android.com/sdk/win-usb.html#top
[Pixel C General] dkryder:
my guess is you need to remove some older drivers that are still around. i suggest using a tip from WugFresh nexus tool kit and get a copy of usbdeview, look at the list of drivers for vendor 18d1. you can remove them all because windows will restore just the newer ones that you need for each device.
[Pixel C General] Grims:
I think I am getting lost somewhere here. We just want to copy the su.img to the /data but not install it? What good would that do? If I jsut copy it there SuperSU tells me binaries are not installed when I boot.
[Pixel C General] drewski_1:
did you install the Superuser.apk? guessing that is what uses the su.img that was pushed to /data

you mention SuperSU. i rooted MM (not N-Preview) with SuperSU by flashing the Zip (not installing from Play Store) and skipping the su.img & superuser.apk steps. are you using the RC-v2.70 that Chainfire created for the N-Preview?
[Pixel C General] Grims:
When trying to flash the su 2.88 zip it fails and aborts at the boot image step for me. Perhaps it's my copy I found, where did you get yours?

I am using the N preview exceed kernel linked in the OP, is that what you mean?
[Pixel C General] drewski_1:
flashing v2.68 aborted at boot image step for me too, but the other root files were installed and the exceed kernel is already modified for Root so that did not prevent SuperSU from rooting (at least on 6.0.1)

but you're trying on N-Preview so you should use v2.70, not v2.68 of SuperSU. i downloaded direct from Chainfire's site.

i haven't tried the N-Preview as i've read it's not yet "Daily Driver Worthy"

EDIT: N-Preview SuperSU thread http://xdaforums.com/apps/supersu/wip-android-n-preview-t3335726
[Pixel C General] charesa39:
Same thing happened to me except it recognized the device, but didn't actually recognize ADB or Fastboot when enabling USB Debugging. It was a pretty simple fix since I knew I had all the appropriate drivers since I downloaded the SDK Tools a long time ago when I first got my Nexus 5, and it's worked for every Nexus device since. I followed this guide as guidance: http://visualgdb.com/KB/usbdebug-manual/. You just have to manually point it towards the appropriate drivers.
[Pixel C General] Grims:
Yeah, I dont get it. I have the xceed kernel, I tried flashing 2.70, but same issue. After flashing superSU isnt even installed, and installing it manually just tells me I dont have the binaries.
[Pixel C General] Grims:
I gave up and flashed M and was rooted in a few minutes. Guess I'll just have to wait for the N techniques to get hashed out a bit more :)
[Pixel C General] backslashV:
cant flash anything. it says FAILED (remote: unsupported command)

even though i have an unlocked bootloader.
[Pixel C General] Grims:
I noticed mine was unusually picky over which USB port I had it plugged into. Sometimes one that was working fine would start giving me that message until I switched it. I also have a couple of micro to C adapters which wont work at all with ADB, but work fine otherwise.
[Pixel C General] bbubelis:
Can't Flash anything

I've tried every USB port on the PC. Tried rebooting both PC and Pixel C multiple times. I continue to get the FAILED error. Even tried using SkipSoft tool to flash image without success. Any suggestions will be greatly appreciated
[Pixel C General] drewski_1:
if you haven't fixed this, it sounds like the infamous security broken Fastboot.

if you have TWRP, there is a Fastboot Fix in (iirc) Advanced menu

also, if you have root it is fixable within Android.

http://xdaforums.com/showpost.php?p=64777133&postcount=96

the alternative (which i did this morning) is to Re-lock & Re-unlock the bootloader (your data will be wiped)
[Pixel C General] houtx2:
Excellent step by step instructions, worked like a charm. Thanks so much! :svetius:
[Pixel C General] backslashV:
No I had nothing, everything was wiped and locking and unlocking the bootloader didn't help. I had to rma.
[Pixel C General] Realvz:
I am totally new to Android and just got a Pixel C. If I root my device will I stop receiving updates to Android N?
[Pixel C General] oRAirwolf:
Yes. You will need to manually flash any device updates after rooting. You can always return it to stock if you want to, though.
[Pixel C General] nigelhealy:
Guide may be fastboot version specific. On mine "fastboot flashing unlock" is not valid but I've unlocked plenty of other devices so I knew "fastboot oem unlock" is the correct command
[Pixel C General] oRAirwolf:
Yeah newer nexus devices use the fastboot flashing unlock command.
[Pixel C General] nigelhealy:
Well one of us is confused then.

The Fastboot command is down the client (Windows, Linux, etc) and its commands are not specific to the Android devices being connected to. I don't see your logic how the device (Pixel C vs ) is able to inform the client (say Linux) to know it must be using a different command.

You'd be right if you said Fastboot clients are evolving and using different commands, but I don't see how different devices (Pixel C) causes fastboot syntax changes.

---------- Post added at 04:18 PM ---------- Previous post was at 04:15 PM ----------

So i followed this guide and am now rooted. Phew, the end of those Youtube ads.

I had an issue where I had the "downloads" and media process all screwed up, no guide could fix so I had to do a factory reset and go back to scratch against after bootloader unlocked. I don't know what I did wrong 1st time, I may have rushed things.
[Pixel C General] oRAirwolf:
Yeah, I'm not really sure what to tell you other than the Nexus 5X, Nexus 6P, and Pixel C all require that you use fastboot flashing unlock and you cannot unlock them using fastboot oem unlock, regardless of what fastboot version you are using on the host PC.
[Pixel C General] nigelhealy:
Odd.

My Pixel C refused fastboot flashing unlock, I tried it a few times thinking there might be a typo and it

did actually successfully

use fastboot oem unlock. I'm using Ubuntu PC, the command worked and I then proceeded with the root howto guide.

Probably means both commands work but depends what you're using as the PC OS. Suggest the OP updated I just happened to remember oem unlock from the Nexus 4, 5, 7 2012, 7 2013, 9, 10 I've owned and rooted. Unless the OP is updated with the proven working alternative command those with whatever is different on my setup may get stuck.
[Pixel C General] drewski_1:
OEM Unlock did not work for me.

may depend on the fastboot version installed?
[Pixel C General] nigelhealy:
That's my guess. I just suggest OP updated as seems we have two working commands so try one or the other. Everything else was exactly as per the guide, buttons etc.
[Pixel C General] pkelly517:
It may depend on the drivers.

I recently unlocked a friend's N6P, and it required 'flashing'. I had to update some drivers to get my Win7 computer to see it in bootloader mode.

It may be related, but I never used 'flashing'in any other unlock prior to that device, up to the N5X.
[Pixel C General] dmnhnterz:
Updating after root with custom kernel.

Thanks very much for the guide. It worked nicely. However, I have a few questions with regards to updating.

1) What is the best way to update after obtaining root the first time ? Is it a matter of flashing system.img and vendor.img from newest factory image and then reflashing su.img and superuser.apk? Or

2) is it better to wait for updated kernel? With updated kernel, would we need to do these steps each time or can we avoid wipe as long as it is not a large update, I.e., going from Android M to Android N?
[Pixel C General] Psychteach1:
trouble with rooting

I have not found this after reading through data posted here, so here goes:

I followed the guide on the first page of this post;; but ran into this problem...after flashing su img, and recovery the unit will not boot back into android...it insists on booting into recovery. I have tried this both with and without wiping all data, but the problem persists

any suggestions?

Thanks in advance

charlie.
[Pixel C General] Swamphound:
I was able to root using this guide for latest build of MM using the latest kernel posted. However I met with your same issue using the Xceed v6.10 N preview kernel. Using the v7 kernel posted in the thread I was able to get to the Android boot splash but it bootlooped from there. I flashed N preview images and we'll just have to be patient until OP can hopefully update.
[Pixel C General] oRAirwolf:
I'll update it when a new official version comes out. Probably when N comes out officially.
[Pixel C General] nigelhealy:
Did you do it to the letter including the final / on the adb push?
[Pixel C General] Psychteach1:
yes. Here's a question: part of the op's instructions are to format data from within twrp. Doesn't that delete all data...the op even indicates that it will wipe the unit. If so, might that not account for a lack of system reboot?
[Pixel C General] nigelhealy:
Forced encryption can cause problems. A full date wipe inside TWRP removes encryption.

It is hard to know what step you did wrong, typo or missed. Just do it to the letter.

The lack of boot makes me think you had either a bum download, you didn't download the files but links to the files which can happen sometims, typo or you just didn't do it all.

If its not booting then probably download the stock image and do a full fresh install, begin with it booting then do it all again with fresh downloads and check the files have decent sizes.
[Pixel C General] drewski_1:
i'm rooted on N Preview 1 using PHH's su-nocrypt kernel & his Superuser app from Play Store.
[Pixel C General] Swamphound:
Nice! I used that on my 6P awhile back to root the N preview but didn't think to see if it was available for pixel C. I'll run that down and Ty for the heads up.
[Pixel C General] drewski_1:
oh, forgot the link to the Kernels

http://superuser.phh.me/nexus/ryu/

NPC56P is for Preview 1

there are versions for Preview 2, but (for me) they appear to cause reboots into Safe Mode so I reverted to N Preview 1
[Pixel C General] Swamphound:
Yeah I saw that so I think I'll just see what shakes out. Thank you so much for sharing though. Stock Preview 2 seems to be running well on my device. Hopefully some magic will come with the next update.
[Pixel C General] NYCHitman1:
Updated TWRP to 3.0.2-0

Link: https://www.androidfilehost.com/?fid=24521665358594788

[MENTION=2666750]oRAirwolf[/MENTION]
[Pixel C General] drewski_1:
Any chance USB drive access is working now? :fingers-crossed:
[Pixel C General] NYCHitman1:
MTP is still broken. I'm working on debugging that though.

EDIT: Looks like the sysfs path is FUBAR because natively TWRP looks for

/sys/class/android_usb/android_0/*

BUT this path doesn't exist on Dragon. Dragon uses

/config/usb_gadget/g1/functions/*

BUT that path is created on boot where MTP is stored.
[Pixel C General] 530farm:
Does this allow to to keep the tablet encrypted? Can you just flash a supersu zip in this twrp like most devices ?
[Pixel C General] NYCHitman1:
The data partition is not force encrypted, if that's what you mean. Also, if you read through the thread -- you'll find that flashing SuperSU in recovery is not recommended as it sets off one of the failsafe flags on Dragon (Pixel C).
[Pixel C General] ironhead65:
Regarding not being able to flash / OTA if you root, you can if you use something like Flashfire:

h t t p s ://play.google.com/store/apps/details?id=eu.chainfire.flash

I've done OTA on my Nexus 5 and Nexus 7, as well as flashed Factory images - maintaining my data each time. Using that also removed the "You have an UPDATE nag", since well, it gave me the ability to update + maintain root and Xposed. I've not tried this with the Pixel C, however, I would not be surprised if it worked just fine.

---------- Post added at 09:27 AM ---------- Previous post was at 09:10 AM ----------

I would also be super interested in this. As fast as this is, I feel ripped off now. I know it must have been thermal or other reasons, but come on! It comes WITH The cores in there! Unless they are just waiting to SPRING a "performance" gain with Android N (just enable the extra cores!!)?

---------- Post added at 10:19 AM ---------- Previous post was at 09:27 AM ----------

Looks like it is a hardware lilmitation:

http://www.greenbot.com/article/287...-to-know-about-nvidias-new-tegra-x1-chip.html

Instead of using the ARM implementation, Nvidia decided to do their own "Clustered" setup, which means only high performance or low performance at the same time. Seems useless to me, but I did not do the trade analysis.
[Pixel C General] hugehead83:
I just ADB'd this in and rebooted to recovery to confirm 3.0.2-0, but now a system reboot just goes straight into recovery. Do I need to re-apply the kernel and/or SU as well?

Thanks for posting!
[Pixel C General] NYCHitman1:
System reboot into recovery = your kernel isn't being detected. Reflash it.
[Pixel C General] hugehead83:
Of course that fixed it--thanks!
[Pixel C General] DanRyb:
Could it be anything else? Any time I modify the system partition while booted into TWRP, I'm unable to then boot into the OS. I mostly make changes to /system/vendor (add in overlay folder and add in my overlay APKs since my OS isn't rooted) and I also replace the NotoColorEmoji font with another one. But now I just keep booting into recovery. I've tried reflashing the boot img but no luck. Are we unable to modify system? If it matters I'm trying with Android N DP2. I was able to do what I'm trying to do on N DP1...

Edit: NM. I used PHH's nocrypt boot image and now it booted just fine
[Pixel C General] mrnovanova:
I'm able to see my device in adb however when I put it in fastoot all I see is "waiting for fastboot command" no matter what command I put in. Dug a bit deeper and found that in device manager I see Pixel c when the device is on and Unknown device while in fastboot. Did a little bit of diggin and found that the way to fix it was here http://stackoverflow.com/questions/34775508/where-is-the-windows-adb-driver-for-the-pixel-c however that is greek to me. I'm not advanced enough to understand whatever they mean. Tried downloding latest drivers but the is no EXE to install them and when I try to update drivers within the file of the drivers I downloaded. Nothing works. Not sure what to do. Any suggestions?
[Pixel C General] nigelhealy:
I run Linux (as it is better than Windoze) and I found the device causes Fastboot hiccup fixed by unplugging and reconnecting the cable.
[Pixel C General] hugehead83:
Make sure you're using a "Benson Leung approved" USB cable. If you can use it to transfer files to/from, it's probably ok.

The archive you downloaded probably has the actual driver files without an executable installer. Go back to where the "unknown device" is in your Device Manager, then right-click and select Properties, then click the Driver tab, then the Update Driver button. Choose the "Browse" option and point the wizard to the folder where you have extracted the driver.
[Pixel C General] mrnovanova:
You're telling me to do exactly what I described doing. Not sure how that helps. Maybe I did it wrong.:(
[Pixel C General] shadow_empire1:
Update rooted to MXC89F

Hi,

(sorry if already answered)

I am currently on M5C14J (rooted, TWRP recovery) and want to update to MXC89F.

If I let my system autoupdate, my pixel c just goes to TWRP and nothing else happens.

Do I have to manually update my pixel with the factory image, or is there another way?

thx
[Pixel C General] NYCHitman1:
You need to manually flash the factory images.
[Pixel C General] newsted44:
stuck on the "green android with some spinny stuff"

Hey Ya'll!!!

Ive been rooting and flashing roms since my HTC Hero back 1000 years ago. All usually goes well and when I bought this Pixel C, I read all the lit and forums, waited a few days and started the process in this thread this morning. all did NOT go well!

I am stuck on the userdata being formatted process, also known in the OP as "the green android with some spinny stuff". Totally bummed out! I am able to get back to "Waiting for fastboot command" and of course the red triangle android of stock recovery, but I have no clue what to do now. Im on Windows 10 and adb and fastboot have been working fine for other devices.

Any help?

Thanks!

Newsted
[Pixel C General] susvin:
Stuck in recovery

Edit:

Flashed twrp 3.0.2.0. Reboot bringing back to recovery. Read that its due to faulty kernel. Actually, I just want twrp to flash DU ROM.

In that case, which kernel shall I flash?
[Pixel C General] tuffgongfl:
That happened to me too. I was able to Power Off and then it booted up normally.

It was also suggested to try re-flashing the kernel.
[Pixel C General] susvin:
I tried 3 times, with several tries for rebooting. I was not flashing any kernel thinking that I dont need root as was aiming for DU.

Will now flash any kernel to proceed :)

Thanks!
[Pixel C General] NYCHitman1:
I'll try to create a new TWRP image tonight if I have time. Haven't been able to work on fixing MTP at all, so the same issues would be persistent through this version.

It's weird because I don't have any issues in recovery, but others are. Peculiar, indeed.
[Pixel C General] newsted44:
Stuck on "erasing" user data step.

I can reboot and get fastboot access, though flashing partitions manually continues to fail with multiple cables and both windows 7 and 10. I suspect because I am stuck before being able to boot and re-enable USB debugging, but I have been wrong before.

Is being stuck on the user data erase step common? Any idea what I should do now? Is this a silly question? I've never had an issue before that I couldn't resolve reading the forums. But this is the ogar.

Peace,

Newsted
[Pixel C General] followmsi:
Did you already flash TWRP ?

There is a fix fastboot option.

Try this one first.
[Pixel C General] NYCHitman1:
Here's that link to the updated version of TWRP for Dragon. I think I fixed flashing vendor images via recovery also.
[Pixel C General] drewski_1:
DU is pre-rooted.

I also had reboots to recovery when trying to reboot from TWRP.

I rebooted to Bootloader and then manually issued "Fastboot Reboot" command.

Not sure if there is something put in a staging area during the DU or SuperSU install, but the tablet rebooted twice and then went into the OS fine.