yashsingh1/xdaforums huggingface dataset:
[Pixel C General] gtaadicto92:
I installed Remix OS, everything installed perfectly and then I flashed twrp but the /data partition is broken, inside TWRP it shows "unable to mount /data (invalid argument)" or something like that. If i boot the OS it goes back to twrp recovery. Rebooting from bootloader does the same thing. What can I do?

I flashed the Remix OS again and everything went back to normal, but i want root for adaway and stickmount :(
[Pixel C General] choder:
I have the exact same error. Have not found a fix for it yet.
[Pixel C General] CroSladi:
Edit: FIXED - Did I just brick my Pixel C?

Edit: FIXED. Never mind. I fixed it by doing the following steps:

1. Re-flash TWRP recovery

2. Shut down tablet

3. De-plug USB cable

4. Boot into recovery

Hi guys,

I'm stuck in a bootloop when I try access TWRP recovery. I executed the following steps:

1. Unlock bootloader

2. Flash TWRP recovery

3. Step 5 of "Install Root" (flash new kernel) instead of Step 1 of "Install Root"

It all happened because I had issues with the USB cable and at one point didn't know which steps I already executed.

What can I do now? Can I somehow flash back the original kernel?

Thanks,

Michael

Edit: Current situation: Bootloop with standard Android boot animation when I try to access TWRP. So I can't access TWRP.

Edit2: I flashed this kernel: dragon-boot-encryptable-rooted-01092016-1.img and TWRP version: twrp-2.8.7.0-dragon-ryu-01-19-2016-1.img
[Pixel C General] numbthumb:
Looking for su.img and SuperUser.apk

Great guide, thank you. The link to su.im, and SuperUser.apk only provides the xceed kernel. Any idea where I can get the right su.img and SuperUser.apk files for our device?
[Pixel C General] NYCHitman1:
It's not needed any longer. SuperSU now supports Dragon.
[Pixel C General] rustak:
I hope that the original post can be updated, at the very least with a note that these instructions are unnecessary and in some cases incorrect (e.g. the versions of TWRP linked can't properly handle encrypted data). I restarted with a full factory flash, and was successful in rooting by:

1. flashed TWRP recovery from http://xdaforums.com/pixel-c/development/twrp-3-0-2-0v16-t3400503 using fastboot -- this prompted me for a decryption pin and properly decrypted /data

2. pushed a SuperSU .zip file from the same author's files folder as above to /sdcard via adb

3. flashed SuperSU zip via TWRP

4. rebooted

No need to wipe your userdata (other than the initial wipe to unlock your bootloader), and no need to fiddle with su.img and other bits, now that SuperSU supports the pixel C directly.
[Pixel C General] Mother_Teresa:
I also flashed another kernel from [KERNEL] xceed :: v6.10 (Marshmallow) + 8.xx (N Preview).
[Pixel C General] oRAirwolf:
I am waiting for the official release of Nougat to update the instructions. In the meantime, I will put a disclaimer saying that my procedures are out of date.
[Pixel C General] GonzoKSV:
Did anyone try to unlock the bootloader via Ubuntu? Does that work with fastboot adb from the repository?

I would do the following steps on a factory fresh Pixel:

Update to newest nougat version. Enable unlock bootloader and usb debugging.

1. Unlock via fastboot/adb

2. Push followmsis TWRP

3. No format data once again to decrypt (does TWRP now support encrypted data?)

4. Flash supersu via TWRP

5. Updates are still not OTA but possible via TWRP.

Would it work like that or do I have forgotten anything?
[Pixel C General] followmsi:
Yes, it should handle encrypted data partition now.

TWRP should ask for password, to be able to access encrypted data partition.
[Pixel C General] GonzoKSV:
Great! Thanks a lot for your work and support!
[Pixel C General] spencer92a:
Now as the factory image for Nougat is online, for recovery and supersu, it works like it has worked before, after i flashed the factory images via fastboot, i've followed this steps:

1. flash twrp via fastboot

2. reboot the device, after rebbot turn it of

3. reboot in the Recovery

4. push supersu 2.76 to sdcard

5. flash supersu

6. reboot and enjoy

by now it works without Problems
[Pixel C General] penguinyaro:
What kernel are you using? The factory boot.img? xceed-v8.02-NPD90G.img?
[Pixel C General] spencer92a:
the factory one
[Pixel C General] xnaquada:
How To: Root the PixelC / Android N(7.0)

I threw together a quick writeup, because why not :)

Standard disclaimer: Perform these actions at your own risk. I take no responsibility for your actions, nor the outcome of any information/actions outlined below. If you don't know what you're doing, take the time to look around XDA and read, learn and ask questions. I'm not responsible for any damage, nor am I tech support.

This post assumes the reader has some general competency around flashing, including but not limited to:

Your bootloader is already unlocked.

You have up to date adb and fastboot drivers available/installed.

You know how to install SuperSU from TWRP

You know how to flash the official android images from Google

Make sure you're good with the above before proceeding further.

Rooting:

Following these steps will erase all data on your device - backup anything you want first.

Fresh install Android N factory image from the official site - clean flash (flash-all) --Keep your life simple, don't mess around with a dirty flash on a major OS update

Android N starts up as normal.

Get SuperSU 2.76 on the device storage -- either from USB transfer from your computer or by downloading it with the tablet

Turn USB debugging on in Android N

Reboot to bootloader

Flash followmsi's TWRP (3.0.2-21.img)

Reboot directly to recovery (TWRP)

Wait for a minute or three for TWRP to provide an interactive environment (not frozen, but looks like it for a bit)

When TWRP Loads, swipe to allow modifications in TWRP (this can be tricky due to the very slow performance of TWRP-- just keep trying, I find a slow swipe works better; it can take multiple attempts)

Now you're in TWRP proper - Install SuperSU as normal - again, be patient with the UI

Reboot the device as prompted by TWRP - notice the warning that it can take a few minutes and/or loop a few times. Let it sit.

Device reboots, probably more than once, this is fine.

You're back in N - rooted -:good:
[Pixel C General] backslashV:
Thanks. Two questions:

1. Can I just boot into TWRP and not flash it?

2. Why do I need to allow modifications? Does it work without allowing it? I'm asking because I don't need this to root my nexus 6p.
[Pixel C General] MVP__911:
Guys please I need some help :'(

My Pixel C goes in loop (TWRP loop)!!!

when I try to turn it on, it always enters custom recovery

I can't go to the launcher and using it as normal

^

the problem happen, after installing custom recovery :(

I think custom recovery overwrite the Android.img or whatever :(

My device current status: Unlock bootloader + loop (TWRP) < I tried full data wipe from TWRP but nothing happend :(

also I can enter Bootloader mode (for writing commend) by hold down both of vol down + power button

plz help guyz, all I need is get rid of custom recovery loop -_-

*am new to Google devices and I feel it's alot much harder than Xperia rooting and flashing custom recovery (I missed Xperia Flashtool)
[Pixel C General] followmsi:
1. fastboot boot recovery twrp.img

2. No, you don't need to allow modifications.

SuperSU would be installed "systemless" anyway.

Gods luck!

---------- Post added at 09:41 PM ---------- Previous post was at 09:38 PM ----------

1. Try "fastboot reboot" in fastboot mode.

2. Format data partition

If both is not working flash back stock recovery.

Sorry, can't help you better here.
[Pixel C General] MVP__911:
Don't worry everthing is right now :)

^I solve the problem by using WugFresh

anyway thanks for the advise :highfive:
[Pixel C General] Alxoom33:
What did you do?
[Pixel C General] backslashV:
I rooted following [MENTION=4277121]xnaquada[/MENTION] guide, but some apps that require /system mounting show the following error:

Could not remount /system

Does anyone know why this happens and what is the solution?

(I've tried remounting using the command

mount -o remount,rw /system

but I get "Device or resource busy"
[Pixel C General] nigelhealy:
I have not got your problem, dont know why you have this problem but I'm familiar with the remount readwrite of /system. Are you IN the /system folder at the time? That is the usual reason that remount command fails. CD to something like /sdcard and then try again. e.g. cd /sdcard
[Pixel C General] backslashV:
No I'm not in /system. I input the command on my PC. Could the SELinux : Enforcing be the problem? Or is there something related to root that has not yet been sorted out with Android 7? Many apps are able to gain root access but then are unable to function. For example, the app BetterBatteryStats fails to install as a system app. The error "Could not remount /system" was given by an app called "/system app mover". GMD Gestures cannot get past the "Check root access" screen even though root is granted.

Very strange!!
[Pixel C General] nigelhealy:
If it was a permission issue you would get a different error. No this an active use of system. How are you doing this from the PC? Try different methods hoping to not be using system. Try a terminal app? Adb shell?

If you need root then su first, then it will trigger asking SuperSU for root, e.g. if you were using a terminal app then that app would ask for root.

Good luck.
[Pixel C General] backslashV:
on pc

adb shell
su
mount -o rw,remount,rw /system

In terminal I get the same "Device or resource busy" message.
[Pixel C General] nigelhealy:
Well "unbusy" as much as possible, close all apps, etc. Try rebooting, etc.

If system is being used then you can't use that remount, you'd have to unbusy by recovery.
[Pixel C General] backslashV:
I ran the command immediately after boot, so no apps are open. How do I unbusy?
[Pixel C General] nigelhealy:
I can't help in that I dont have your problems, just giving ideas.

I have one app which refused to work and so I went back to MM to give time for a N fix. I suggest if you can't fix then Go back and wait.
[Pixel C General] MVP__911:
I fixed the problem by WugFresh tool (repair loop tool)
[Pixel C General] CrazyPeter:
This method compatible with file based encryption?
[Pixel C General] nigelhealy:
So I just now did a clean erase and install of the N release and I also then got hit with the /system readwrite busy problem.

I was kind of right need to do it in a terminal, seems the best terminal is from busybox, so I installed busybox then a terminal prog and it worked just fine. In my case I was needing for Adaway to modify /system/hosts file. I chose in this specific case to configure Adaway to write to a /data file and link it to /system so I don't need to readwrite permission every time Adaway needs an update (so just a one-time system readwrite need and then system can remain readonly).

Yes it is that simple.

http://androiding.how/make-system-writable-android-7-0-nougat/
[Pixel C General] Mother_Teresa:
I used this redditpost:

If you are on Android Nougat with systemless root and cannot get adaway to apply, you need to flash a file in recovery. You can get the file here: http://xdaforums.com/showthread.php?t=2190753
[Pixel C General] jasonc7649:
Hello,

My new pixel c won't request the rsa fingerprint, any tips?
[Pixel C General] Alxoom33:
I haven't seen FBE on the Pixel C running NRD90R Android 7.0, yet. Nothing for fbe in Settings/Developer options. Have you?
[Pixel C General] Reuben_skelz92:
So if I root and have twrp will updates still install as normal
[Pixel C General] nigelhealy:
I did that of encryption on N, boot into N then boot into TWRP it can't read anything, sideload supersu, then boot, then use a root app to boot into recovery. TWRP can read if you reboot from an unlocked state but couldnt on a cold boot.

I'm not on N now (still waiting for app support to catch up) so I'm typing from memory.

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

Assume no, assume you see an update and then download the zips and flash in TWRP and if you want root and anything else flash that also.
[Pixel C General] Reuben_skelz92:
OK thanks. Also is there away to adjust the screen color settings?
[Pixel C General] cam30era:
Strange boot behavior

After unlocking bootloader, every time I boot, the device boots to bootloader first with the message:

"Bootloader is unlocked and OS verification is OFF. Device will continue booting in 30 seconds."

Then it subsequently boots to OS. Stock NRD90R. No root, no modifications, stock recovery.

I relocked bootloader and it boots as expected.

Is this behavior normal?
[Pixel C General] hugehead83:
Yes, that's by Google's design. No way to disable it unfortunately. Pretty much the biggest caveat of the unlocked bootloader.
[Pixel C General] cam30era:
Appreciate feedback. What a PITA....
[Pixel C General] nigelhealy:
I have a Moto phone and when you unlock its bootloader it has a long wait with the unlocked bootloader warning, but some clever person found a fastboot flash logo.bin file which removes the warning and the wait. I just did it on my Moto G4 Play.

Anyone have an idea if this can be done for the Pixel C?
[Pixel C General] Alxoom33:
Probably not, due to the unique Pixel C architecture. There was a great article/rant by [MENTION=4867279]cheep5k8[/MENTION] on the difficulties of working with this device.

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

Yea, but you need to deal with it if you want an unlocked/rooted Pixel C. At least until someone develops a fix.
[Pixel C General] theethut:
how to unlock bootloader in pixel c android n nrd90r

thanks
[Pixel C General] cam30era:
Did you read the OP (Original Post)? Detailed instructions there. Method and commands haven't changed for unlocking bootloader.
[Pixel C General] theethut:
i try follow in OP in step 4 (fastboot flashing unlock) but the devices show Waiting for fastboot command... it not go to step 5
[Pixel C General] cam30era:
Are you sure you have an updated Android SDK on your PC, and the correct drivers? What is the response if you type "fastboot devices"?
[Pixel C General] theethut:
thank you . i forgot to update android sdk.
[Pixel C General] cam30era:
Glad to be of assistance.
[Pixel C General] iamkardde:
Re-rooting is Supposed to be simple!

I have been rooted properly for months. Somehow the nougat -R updated OTA and put me back in stock. Lost twrp, though still have bootloader unlocked.

I have updated wug's and android sdk last night. Trying steps in nx. root toolkit, I keep getting hung up at "fastboot not found" or "waiting 4 device". I even reinstalled

adb/fastboot minimal.. And my device is waiting for fastboot command! :( PLEASE HELP! Im thinking I forgot a step or 2..

---------- Post added at 11:02 PM ---------- Previous post was at 10:31 PM ----------

i dont wanna start over and end up back with marshmallow
[Pixel C General] iamkardde:
Resolved! INSANE, rarely heard of or dealt with driver issues. I mentioned WUGs and i gotta say that program Doth Rock!
[Pixel C General] gnome9er:
i too lost my root cuz of update. the even harsher thing is i totally cant figure out how it was i rooted it in the first place. so many confusing directions, but i started fresh, flashed 7.0 then set it up and booted to fastboot where i then flashed recovery with twrp, then volume down+power then recovery where i flashed Supersu just to get stuck in a bootloop... what did i miss here? a wipe? i started flashing a bunch of those Update zips im so tired of this tablet why is it being like this? what did i miss here?
[Pixel C General] Alxoom33:
Does anyone know why flashing Suhide v. 0.55 after SuperSu 2.78 SR 1 causes a bootloop?

Recovers from the bootloop after flash Suhide rm v. 51.

---------- Post added at 03:59 PM ---------- Previous post was at 03:57 PM ----------

Anyone know why flashing suhide v. 055 after SuperSU 2.78 SR 1 causes a bootloop?

Recovers after flashing superhide rm v. 051.

Edit: Found out that Suhide is not yet compatible with Android 7.1.1, including 7.1 on any device. The bootloop is the expected result of such flash...
[Pixel C General] sgibbers17:
Is there been an update for unlocking the bootloader for v7.1.1? I can't get the fastboot drivers to install.
[Pixel C General] nigelhealy:
Why would a ROM affect fastboot?
[Pixel C General] Alxoom33:
Use WUG Nexus Toolkit on XDA if you are not proficient in ADB/fastboot.
[Pixel C General] sgibbers17:
I couldn't get the fastboot drivers to install on 2 different PCs so I thought that the update may have changed the fastboot or is blocking it somehow. I even downloaded the latest fastboot drivers off of google's website.
[Pixel C General] sgibbers17:
I can't seem to get my RSA fingerprint prompt to show up. I have tried to revoke USB debugging authorizations but still not RSA prompt.
[Pixel C General] bbawden:
Apologies if this has been answered, but how do I update the Android version to the latest (I have a notification about a new version) without losing root, and without wiping?

Thanks

ETA: I am currently on Marshmallow, so the notification at the moment is for 7.0, not 7.1.x
[Pixel C General] hugehead83:
Follow this guide :)
[Pixel C General] bbawden:
Fab, thanks.
[Pixel C General] Markeee:
Its been a while since I first got my Nexus 6 and unlocked the boot loader

Now I have a Pixel C coming

If I remember correctly when you unlock it wipes the system so its a good idea to backup & unlock as soon as you get it before you setup everything ?
[Pixel C General] pkelly517:
OEM unlock wipes data, not system.

It's best to unlock before you set up. Then there's nothing to backup or lose.
[Pixel C General] nigelhealy:
True

Almost, some manufacturers complain about warranty, so what I do is unbox, minimum setup, check all the hardware is working, speakers, microphone, Wifi, BT, no light bleed, it is the actual unit I ordered (storage choice, etc) and THEN I unlock, setup again then do all the laborsome tasks of install and config all my apps.

But to be honest, to setup all my apps is < 30 mins total effort. I use mine for work and play and so lots of Office365, Cisco, VPN type as well as the usual.
[Pixel C General] Markeee:
Nice reply thanks

I got 2 64gig Pixel C's coming Monday one for me and one for my kid

I think I snagged some decent deals got one brand new off ebay shipping straight from google for $450.00

and one mint condition off Swappa $340 shipped excited waiting for them
[Pixel C General] johnbravado:
I just got my pixel c and was attemopting to root it per your quide but i can seem to get fastboot flashing unlock to work. computer sits at waiting for response and pixel sits at waiting for fastboot command. how long should a response take?

It seems when I do fastboot devices nothing comes up.
[Pixel C General] cam30era:
If you are on Windows 10, have a look here > https://xdaforums.com/pixel-c/help/adb-recognized-fastboot-t3471150
[Pixel C General] sabrdawg:
I just got my tablet and it's on 8.0. Does anyone have rooting instructions for this version? Thanks so much! :)
[Pixel C General] hugehead83:
Rooting Google Pixel C Running Android 8.1.0

I just got my 4th "advanced replacement" Pixel C tablet (Screen defects for the first two; inductive charging circuit failure on the last one.

Download:

- Latest Kernel from followmsi's posts

- Latest TWRP

- Latest SuperSU

I pushed the latest December factory image to it (Android 8.1.0): Latest factory image

Just extract and run the "flash-all.bat" from ADB.

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.

I installed it from a USB drive, but you can also do an ADB push to get the file to the data partition via USB cable:

adb push <superSU zip file name> /data

Install > choose SuperSU zip file and go

- Wipe cache/dalvik

- Reboot (it might reboot 2-3 times on its own)

- Test with Root Checker App. You should be rooted at this point.

- Optionally (I think?) install the latest modified kernel:

Reboot to TWRP

adb push <kernel zip file name> /data

Install > choose kernel zip file and go

For future monthly build updates, go to followmsi's thread for files & instructions.

Hope this helps,

-Will
[Pixel C General] m+a+r+k:
As above but:

Make sure to use latest adb/fastboot.

unlock bootloader command for me was

fastboot flashing unlock

I was able to root with latest 3.2.0.0 TWRP and Magisk 14.5.

I didn't use the followmsi kernel.
[Pixel C General] sabrdawg:
Wow, thx guys! This helps me a TON! You rock :D
[Pixel C General] sabrdawg:
Well, I've downloaded all the files and am ready to go, aside from the face I'm having a fastboot issue. At first, I couldn't figure out where to get the drivers from, but then after doing a lot of research, I discovered that I can open device manager, right click on the device, and manually install the driver by selecting Android>fastboot. My device now shows as connected when powered on, and I even got the confirmation pop-up to enable USB debugging, however, once I enter fastboot via "ADB reboot bootloader," the screen says, <waiting for device> and nothing happens. Here's a screenshot. Thanks in advance! :)
[Pixel C General] m+a+r+k:
Did you try:

fastboot oem unlock

It seems to vary between devices, maybe their age and current OS.

Latest version adb I got is 1.0.39 dated 12 May.

Did you go into Developer Options and select "oem unlocking" first?

Is the USB setting in notification set to media (MTP)?

Just so you know when it works:

You will be prompted on the tablet screen with a warning about unlocking the bootloader.

Press the power button to unlock the bootloader.

The device will reboot and say "Bootloader is unlocked and OS verification is OFF. Device will continue booting in 30 seconds." You will also hear an audible beep. You will then see some spinny stuff. This is the userdata being formatted.

When complete, the device will boot back into the bootloader and say

Waiting for fastboot command...
[Pixel C General] sabrdawg:
Thank you :) I was able to get my bootloader unlocked and 8.1.0 flashed! However, I'm stuck in a TWRP bootloop. I'm trying to resolve that at the moment. This process has been a LOT of trial and error, however not without reward! ?
[Pixel C General] Alxoom33:
Fastbboot flash your stock boot image and then retrace your steps.
[Pixel C General] sabrdawg:
Thanks! After much tinkering, I got everything to work! I ended up reinstalling the drivers while in recovery, and was able to ADB push the kernel, SuperSU, and the AOSP ROM. Once I flashed the ROM, all was well! :)
[Pixel C General] m+a+r+k:
Glad you got there. It can be nerve-wracking at times, but, as you say, rewarding and a great learning experience.
[Pixel C General] sabrdawg:
It definitely was! :) I have one more question and then I should be good to go. Which gapps work successfully with this version? I downloaded the only one I could find for 8.1.0, and while it installs without issue, I get the "Google Play Services has stopped" pop-up when it says "checking info" while waiting to log in to Google.
[Pixel C General] Alxoom33:
If you flashed the factory 8.1 image, you don't need gapps. Only need that for AOSP roms.
[Pixel C General] sabrdawg:
Oops...I should have specified I'm on the AOSP ROM :P
[Pixel C General] m+a+r+k:
When installing ROMs on my Nexus 7 I always use Open GApps Pico especially as the system partition is close to being full.

I don't see the need to fill the system partition with aps you'll update anyway and get stored elsewhere.

I've had trouble with Beans Gapps.

On the Pixel C I'm stock 8.1.