• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

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

Search This thread

iamkardde

Member
Sep 28, 2016
13
3
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 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..
i dont wanna start over and end up back with marshmallow
 

iamkardde

Member
Sep 28, 2016
13
3
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

Resolved! INSANE, rarely heard of or dealt with driver issues. I mentioned WUGs and i gotta say that program Doth Rock!
 

gnome9er

Member
Oct 16, 2010
37
1
40
langley
twitter.com
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?
 

Alxoom33

Senior Member
May 18, 2011
4,956
1,762
New York
www.sack-ip.com
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.

Sent from my Pixel C using Tapatalk

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

Sent from my Pixel C using Tapatalk
 
Last edited:

bbawden

Member
May 14, 2010
48
2
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
 
Last edited:

Markeee

Senior Member
Sep 29, 2012
1,048
219
South Florida
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 ?
 

pkelly517

Senior Member
Dec 28, 2011
1,672
1,681
Can see Houston from here
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 ?
OEM unlock wipes data, not system.

It's best to unlock before you set up. Then there's nothing to backup or lose.

Sent from my Pixel C using Tapatalk
 
  • Like
Reactions: Markeee

nigelhealy

Senior Member
Aug 3, 2012
1,540
444
Preston
OEM unlock wipes data, not system.

True

OEM unlock wipes data, not system.
It's best to unlock before you set up. Then there's nothing to backup or lose.

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.
 
  • Like
Reactions: Markeee

Markeee

Senior Member
Sep 29, 2012
1,048
219
South Florida
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.

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
 
  • Like
Reactions: Alxoom33

Top Liked Posts

  • There are no posts matching your filters.
  • 32
    The instructions in this guide are outdated and way more complicated than necessary. Once the official release of Android 7.0 Nougat becomes available/rooted, I will update the procedures in this thread. In the meantime, I recommend referencing this post along with the original instructions.

    A massive shout out to @cheep5k8 for all the hard work he did in getting root and recovery working on the Pixel C. Please donate to him if you can. He deserves it.

    Disclaimer: This will wipe your device. Backup anything important before you start. I mostly made this guide for selfish reasons. cheep5k8 has done a great job but some of the instructions are a little vague. I like being spoon fed and I wanted a resource to refer to in the future. You know the drill. If it breaks, not my problem. Post in the forums or hop onto the XDA IRC channel.

    There may be more efficient ways to do this, but this will get you where you need to be. If you find any problems or have any suggestions, feel free to reply (BE VERY SPECIFIC WITH STEPS) and I will do my best to update the instructions.

    Prerequisites:
    • ADB/Fastboot - Minimal ADB and Fastboot
    • ADB/Fastboot Drivers - I recommend using Wugfresh's Nexus Root Toolkit and using the full driver installation guide. Alternatively, you can install them yourself using the official Google Drivers (no installer)
    • An easy way to access the ADB prompt is to navigate to the directory that ADB is installed in, hold shift and right click inside the directory. This will give you an expanded right click menu that includes an option to "Open command window here." Select this option and a command prompt will open that is already in the ADB directory, saving you from having to do a bunch of cd nonsense. You can check to see if your device is recognized in ADB by typing "adb devices." If ADB and the driver are all working correctly, it should come back with something like "5A20001071 device." You can also check to make sure your device is recognized in fastboot by booting to the bootloader and typing "fastboot devices." It will show something similar.
    Necessary Files:

    Device Prep:

    Enable developer mode
    1. Go to Settings > About tablet
    2. Tap on Build Number 7 times until it says "You are now a developer"
    Enable OEM Unlocking
    1. Go to Settings > Developer options
    2. Enable OEM Unlocking
    3. Tap on Enable when a disclaimer pops up
    Enable USB Debugging (ADB)
    1. Go to Settings > Developer options
    2. Enable USB debugging
    3. Tap on OK when prompted with a disclaimer
    4. If the ADB USB driver has been installed, you will see a popup that says "The computer's RSA key fingerprint is: xx:xx:xx:xx(blah blah)"
    5. Check the box next to "Always allow from this computer"
    6. Tap on OK

    Unlock Bootloader:
    1. Open ADB prompt (see prerequisites)
    2. Input the following:
      Code:
      adb reboot-bootloader
    3. The device will now boot into the bootloader and say
      Code:
      Waiting for fastboot command...
    4. Input the following to unlock the bootloader:
      Code:
      fastboot flashing unlock
    5. You will be prompted on the tablet screen with a warning about unlocking the bootloader.
    6. Press the power button to unlock the bootloader.
    7. 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 the green android with some spinny stuff. This is the userdata being formatted.
    8. When complete, the device will boot back into the bootloader and say
      Code:
      Waiting for fastboot command...
    9. Boot back into Android by inputting:
      Code:
      fastboot reboot
    10. Your Pixel C will be reset, so you will need to re-enable USB debugging. Connect to your wireless network and then skip past everything else in the initial setup, as all of this setup info will be wiped again later on. Refer to the "Enable USB Debugging (ADB)" steps above to re-enable USB debugging.

    Install Custom Recovery:
    1. Open ADB prompt (see prerequisites)
    2. Input the following:
      Code:
      adb reboot-bootloader
    3. The device will now boot into the bootloader and say
      Code:
      Waiting for fastboot command...
    4. With the Pixel C in the Fastboot bootloader and the recovery file in your ADB directory, input the following:
      Code:
      fastboot flash recovery (replace with custom recovery filename).img
      Example:
      Code:
      C:\>fastboot flash recovery twrp-2.8.7.0-dragon-ryu-01082016-2.img
      target reported max download size of 268435456 bytes
      erasing 'recovery'...
      (bootloader) erasing flash
      OKAY [  0.054s]
      sending 'recovery' (13760 KB)...
      OKAY [  0.349s]
      writing 'recovery'...
      (bootloader) writing flash
      OKAY [  0.375s]
      finished. total time: 0.783s
    5. Reboot into Recovery using the physical buttons. If you reboot the device back into Android, it will write over the custom recovery with the stock one. This will be fixed in the future.
      Code:
      Power + Volume down until screen turns off, keep pressing volume down to boot into Coreboot Bootloader. Navigate to Reboot into Android Recovery with volume down and then press power to select.

    Install Root:
    1. In TWRP, navigate to Wipe > Format Data
    2. Type "yes" in the warning prompt and wait for the userdata partition to format. Again, this will wipe your tablet.
    3. Press the Home button at the bottom when the format is complete
    4. Navigate to Reboot > Bootloader to boot back into Fastboot
    5. In the ADB prompt, flash the new kernel:
      Code:
      fastboot flash boot (replace with xCeeD kernel filename).img
      Example:
      Code:
      C:\>fastboot flash boot xceed-kernel-google-dragon-02-01-2016-RC1.img
      target reported max download size of 268435456 bytes
      erasing 'boot'...
      (bootloader) erasing flash
      OKAY [  0.064s]
      sending 'boot' (6220 KB)...
      OKAY [  0.161s]
      writing 'boot'...
      (bootloader) writing flash
      OKAY [  0.197s]
      finished. total time: 0.426s
    6. Reboot into Android. The device may boot twice.
      Code:
      fastboot reboot
    7. Reboot back into Recovery. Power + Volume down until screen turns off, keep pressing volume down to boot into Coreboot Bootloader. Navigate to Reboot into Android Recovery with volume down and then press power to select.
    8. In TWRP, navigate to Mount and check only Data
    9. In the ADB prompt move su.img to /data:
      Code:
      adb push su.img /data
      Example:
      Code:
      C:\>adb push su.img /data
      5677 KB/s (33554432 bytes in 5.772s)
    10. In TWRP, navigate to Mount and uncheck Data
    11. In TWRP, navigate to Reboot > System
    12. Perform initial device setup
    13. Once you are at the home launcher, re-enable USB debugging (Refer to Device Prep)
    14. In the ADB prompt, install superuser.apk:
      Code:
      adb install Superuser.apk
      Example:
      Code:
      C:\>adb install Superuser.apk
      8612 KB/s (6227998 bytes in 0.706s)
              pkg: /data/local/tmp/Superuser.apk
      Success
    15. Install Busybox from the Play Store: link

    Congrats. You are now rooted (not in the Australian sense).
    6
    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:
    1. Following these steps will erase all data on your device - backup anything you want first.
    2. 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
    3. Android N starts up as normal.
    4. Get SuperSU 2.76 on the device storage -- either from USB transfer from your computer or by downloading it with the tablet
    5. Turn USB debugging on in Android N
    6. Reboot to bootloader
    7. Flash followmsi's TWRP (3.0.2-21.img)
    8. Reboot directly to recovery (TWRP)
    9. Wait for a minute or three for TWRP to provide an interactive environment (not frozen, but looks like it for a bit)
    10. 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)
    11. Now you're in TWRP proper - Install SuperSU as normal - again, be patient with the UI
    12. 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.
    13. Device reboots, probably more than once, this is fine.
    14. You're back in N - rooted -:good:
    5
    Yeah, ext4 is a filesystem -- you can't flash an image to that in TWRP.

    As for MTP access - it's not the fstab. It's the sysfs path which is different. The init.rc has to be modified to include this path creation for instances other than on boot.

    Thanks for your hints .. there were a few smaller issues.
    Finally I have manged it :)

    Uploaded new version .. as TWRP flashable zip !

    Update.ZIP_TWRP_dragon_3.0.2-0_v4.zip
    Just made a fresh backup to my usb-stick via USB-OTG .. :)

    Finally we can make OTG on Pixel C !

    Thanks for all your help ..

    Cheers
    4
    P.S. One thing to add, for those who bought SuperSU Pro, you can install that too from the Play Store instead of installing the APK, but at the moment, it will say that the su binary is outdated (because the xCeeD kernel comes with 2.66, but SuperSU is already at 2.67). There needs to be a somewhat better solution but it's a bit hard to come up with it.

    xCeeD v1-RC4 will have SuperSU updated to 2.67, and I'm thinking of how to make it possible to flash the normal SuperSU ZIP in TWRP. I will probably modify TWRP in some way to make that possible.