[GUIDE] Unlock Bootloader, Install Custom Recovery, and Root the Pixel C (2/4/2016)

[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!

Sent from my Pixel 2 XL using Tapatalk

 

[hugehead83]

I put it on this week with the June update. No problems! Definitely skip 16.0.

 

[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?

 

[hugehead83]

Check out my post on this. I'm now using magisk 16.4 instead of superSU but the process is the same. http://forum.xda-developers.com/showthread.php?p=74789442

 

[kbal86]

Check out my post on this. I'm now using magisk 16.4 instead of superSU but the process is the same. http://forum.xda-developers.com/showthread.php?p=74789442

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?

 

[hugehead83]

Am I using a wrong version?

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

 

[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.

 

[Mother_Teresa]

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.

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.

 

[tevil]

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.

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.

 

[Mother_Teresa]

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.

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.

 

[tevil]

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.

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.

 

[Alxoom33]

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.

Do you have adb and fastboot working?

Sent from my Pixel 2 XL using Tapatalk

 

[tevil]

Do you have adb and fastboot working?

Sent from my Pixel 2 XL using Tapatalk

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.

 

[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.

Sent from my Pixel 2 XL using Tapatalk

 

[Mother_Teresa]

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.

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.

 

[tevil]

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 'sideload' etc.

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.

 

[Mother_Teresa]

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.

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.

 

[tevil]

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.

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.

 

[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

 

[12paq]

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

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!