[UNOFFICIAL] TWRP 3.0.0-0 for the Pixel C (dragon-ryu) :: Current: 02-11-2016-1

Search This thread

cheep5k8

Senior Member
Sep 26, 2012
587
1,067
Berlin
This is UNOFFICIAL TWRP for the Pixel C. That said, the TeamWin team greatly helped me in getting this working. But at the same time, neither TeamWin nor me take any responsibility whatsoever for any undesired outcome resulting from any kind of use of this project and project files! If you don't exactly know what you're doing then just walk away and do something good. Don't touch any options of which you don't exactly know what they're for!

What works:

* So far, everything; encryption support should work, but some feedback on this would be welcome

Problems:

* The GUI will be sometimes slow, sometimes super slow. This is probably due to the high screen resolution of the Pixel C.

How to install:

- Unlock bootloader
- In the bootloader, run "fastboot flash recovery <.img file>"
- Reboot into Pixel C bootloader
- Boot into recovery (or later on/from Android through "adb reboot recovery")

If the recovery doesn't stick after booting into Android:

- Do the install procedure as above
- Do NOT reboot into Android
- Press Vol-Down + Power until you see the bootloader menu
- Select "Boot into Android Recovery"
- When in TWRP, mount system
- Using TWRP's File Manager, or using adb, delete the file "/system/bin/install-recovery.sh"
- Reboot

After doing this, OTAs won't work any longer, but they wouldn't work anyway after installing TWRP. Just so you know ;)

DOWNLOAD

twrp-3.0.0-0-dragon-ryu-02-11-2016-1.img
SHA1 hash: 3e97aae6cc18975683eda2bd3732faaecec14166

Changelog

:: 01-19-2016-1

- Removed screen timeout by default, since the GUI is very slow and the screen unlock slider is very hard to use

- Added an option to fix the Fastboot Full Cap flag directly from TWRP; you find the option in "Advanced". If the Pixel C should ever not let you flash in fastboot, boot into TWRP, select Advanced -> Fix Fastboot, swipe to confirm, and you're set.

:: 02-11-2016-1

- Rebased on twrp/android-6.0 branch (i.e. upgraded to TWRP 3.0.0-0)

The recovery is based on the Pixel C stock kernel.
 
Last edited:

DaConcho

Senior Member
Nov 18, 2014
111
44
Salt lake city, UT
Awesome! I can survive without root for the time being but being able to enable multiwindow would be amazing!

Thanks!

Edit: I am getting a FAILED (remote: unsupported command) error and cant flash this. Anyone know a work around?
 
Last edited:

brando56894

Senior Member
Dec 16, 2010
1,881
257
Jersey City
Worked fine for me with "fastboot flash recovery [image name]" did you unlock your bootloader? Also root works just fine, you just have to boot from your PC.

Sent from my Pixel C using Tapatalk
 

DaConcho

Senior Member
Nov 18, 2014
111
44
Salt lake city, UT
Worked fine for me with "fastboot flash recovery [image name]" did you unlock your bootloader? Also root works just fine, you just have to boot from your PC.

Sent from my Pixel C using Tapatalk

I did unlock my bootloader but can't get anywhere. Tried updating my sdk, drivers everything. I guess I will have to keep playing with it.

Edit: I relocked my bootloader, and then unlocked it again and now it is working. If anyone else runs into this give it a try.
 
Last edited:

dkryder

Senior Member
Sep 26, 2013
467
113
Google Pixel 3a
Google Pixel 5a
it successfully installed on my pixel c. is reachable as the Android Recovery option. and boots to bootloader to allow boot of boot.img
this is a good thing. thanks to all involved.
it's been 1 month since release and good way to celebrate.
 
Last edited:

doumer

Senior Member
Jun 7, 2010
484
71
Stuttgart
hooray thanks! just to clarify: I need encryption disabled to use twrp or just to flash SuperSU?
I'm currently using phhusson's noverity boot-img to boot and with a modified vendor img root is working fine while encryption is enabled ... just having to boot via fastboot every time is a bit awkward. And since I don't know what happens if the device got stuck and reboots itselfe without the modfied boot it would be awesome to have at least a nandroid backup ;)
 

cheep5k8

Senior Member
Sep 26, 2012
587
1,067
Berlin
hooray thanks! just to clarify: I need encryption disabled to use twrp or just to flash SuperSU?
I'm currently using phhusson's noverity boot-img to boot and with a modified vendor img root is working fine while encryption is enabled ... just having to boot via fastboot every time is a bit awkward. And since I don't know what happens if the device got stuck and reboots itselfe without the modfied boot it would be awesome to have at least a nandroid backup ;)

Hey... You can use TWRP even with encryption enabled, you just can't write anything to /data.

However for the next build I'm going to enable TWRP's decryption option and see if it works with the Pixel C. If it does I'll post a new build this evening (European Time).

I tried the systemless SuperSU on a decrypted /data partition but it wouldn't work (bootloop), clearly there's a lot of ground to cover here, but like I said maybe the decryption functionality will help us here.

EDIT: I'm also working on a boot.img with disabled forced encryption. Looks like we're going to get proper root very soon.
 

Khaon

Senior Member
Apr 3, 2012
1,271
1,677
Louvain-la-Neuve, Belgium
This is UNOFFICIAL TWRP for the Pixel C. That said, the TeamWin team greatly helped me in getting this working. But at the same time, neither TeamWin nor me take any responsibility whatsoever for any undesired outcome resulting from any kind of use of this project and project files! If you don't exactly know what you're doing then just walk away and do something good. Don't touch any options of which you don't exactly know what they're for!

What works:

* Well, basically everything IN TWRP works, it's just that without a kernel that disables forced encryption this is not of very much use. I tried flashing SuperSU, but it wouldn't work properly.

Problems:

* The GUI will be sometimes slow, sometimes super slow. This is apparently still a problem with how TWRP uses the graphics mode that is used on the Pixel C. Best is if you immediately disable the screen lock once you boot into TWRP because the unlock slider is abysmally sluggish.


How to install:

- Unlock bootloader
- In the bootloader, run "fastboot flash recovery <.img file>"
- Reboot into Pixel C coreboot bootloader
- Boot into recovery (or later on/from Android through "adb reboot recovery")

DOWNLOAD

2.8.7.0-01082016-1


Hello thank you for this. Yesterday I tried to build as well twrp but it wasn't fully working.
I just imported this config with TW_INCLUDE_L_CRYPTO := true && TW_INCLUDE_CRYPTO := true

I didnt copy paste the twrp.fstab I added but added its path to BOAR_smthing.

Also I used omnirom's android-6.0 revision with dragon's device tree.

The recovery seems to boot, as
Code:
adb devices
returns XXXXXx recovery.

Also I can reach the device's shell with adb shell. Just the screen stays black.

I was wondering if I missed something. Is your device tree available online ?
 

cheep5k8

Senior Member
Sep 26, 2012
587
1,067
Berlin



Hello thank you for this. Yesterday I tried to build as well twrp but it wasn't fully working.
I just imported this config with TW_INCLUDE_L_CRYPTO := true && TW_INCLUDE_CRYPTO := true

I didnt copy paste the twrp.fstab I added but added its path to BOAR_smthing.

Also I used omnirom's android-6.0 revision with dragon's device tree.

The recovery seems to boot, as
Code:
adb devices
returns XXXXXx recovery.

Also I can reach the device's shell with adb shell. Just the screen stays black.

I was wondering if I missed something. Is your device tree available online ?

Not yet. I'm going to upload it later on to the TWRP devs for official inclusion.

You need to merge the minui patch so TWRP can use DRM for video on the Pixel C; there is no fb0 device.
 
  • Like
Reactions: Khaon

dkryder

Senior Member
Sep 26, 2013
467
113
Google Pixel 3a
Google Pixel 5a
there were some new boot images out today. i flashed one of them. when i boot to recovery the sdcard is not able to be mounted. do you have any suggestions on what i need to do or look at in order to get it fixed?
 

cheep5k8

Senior Member
Sep 26, 2012
587
1,067
Berlin
there were some new boot images out today. i flashed one of them. when i boot to recovery the sdcard is not able to be mounted. do you have any suggestions on what i need to do or look at in order to get it fixed?

Because /data is (force-)encrypted. I uploaded a new TWRP build with various fixes but decryption doesn't work.

What I also found out is that the boot image for the Pixel C is NOT an Android boot image (!), but a ChromeOS one. This puts a lot of things in doubt, for example I am not sure if systemless SuperSU can handle this.

But, I'm working on all that ;) (working on boot img without forced encryption right now, but so far it doesn't want to boot completely)
 

cheep5k8

Senior Member
Sep 26, 2012
587
1,067
Berlin
OK guys, if you really want actual SuperSU, and other root stuff, and decrypted /data, here's how it works but it's complicated and will only work tethered as far as I can tell.

First, download this boot image: dragon-boot-encryptable-01092016-1.img

Now here are the steps:

- make sure you have a stock boot.img handy in case something goes wrong (as usual I can not take responsibility but chances of bricking are extremely slim if you know what you're doing)
- boot into fastboot
- flash the above boot image to boot ("fastboot flash boot dragon-boot....")
- flash the TWRP recovery (latest version) ("fastboot flash recovery twrp-dragon-...")
- hold power+vol down pressed.. the device will turn off, keep it pressed even as it turns off, it will turn on again and you are in the coreboot menu
- select "Android Recovery" which will start TWRP
- in TWRP, select system as read only when it asks ("never write onto the system partition").. my boot image does not disable dm-verity which seems to be still in effect, so if you change /system, the Pixel will refuse to boot (even though it's unlocked... no idea)
- once in TWRP, go to "Wipe" and then choose at the bottom "Format Data" (just wiping will not work)
- when that's done stay in the recovery
- get SuperSU 2.66 from somewhere and flash it through TWRP (using sideload for example)
- when it's done, go to "Backup" in TWRP and only backup boot (the kernel) - no password - no compression
- somehow copy the backed up kernel from the device to your computer ("adb pull" for example), but in no case let the Pixel boot into Android
- when that's done, tell TWRP to boot back into the bootloader

Now get ready to be real quick...

- boot (just boot, not flash) the TWRP backed up boot image (it's 32MB large and called boot.emmc.win, but it's all good): "fastboot boot boot.emmc.win" (and now you have to be rather quick)
- It will boot up for a second and then go back to the "The OS will boot in 30 seconds screen"
- Again press power+vol down and hold it, even as the device turns off, until you're in the coreboot bootloader
- There, choose fastboot again
- And once again boot the boot.emmc.win image ("fastboot boot boot.emmc.win")

- Now let it boot up
- If everything went OK you should be in Android, with decrypted /data, and SuperSU should be installed and working

If you want to avoid being encrypted again (although SuperSU should survive that) you will have to boot tethered everytime using that boot.emmc.win image.

Known Issues: Somehow because /data is decrypted, "Security" settings in Android will crash. Hopefully you don't need anything in there. You might also want to skip setting a lock pattern or pin when doing the initial setup, it might crash too.

So far, I tried installing AdAway using root which worked just fine.

If someone figures out how make this untethered: you da real MVP!
 

ZiggSVO

Senior Member
How to install:

- Unlock bootloader
- In the bootloader, run "fastboot flash recovery <.img file>"
- Reboot into Pixel C coreboot bootloader
- Boot into recovery (or later on/from Android through "adb reboot recovery")

DOWNLOAD

2.8.7.0-01082016-2 UPDATE: Includes various fixes from first build; decryption of data does NOT yet work

So, followed these instructions and whenever I try to reboot into recovery I get the no command screen. Am I missing something? lol
Edit: So figured thats the stock recovery stuff. Got to the stock recovery but can't get into twrp
2nd Edit: I redownloaded the file and didnt rename it shorter this time and now it works...weird :p
 
Last edited:

xploitnt

Senior Member
Mar 3, 2013
261
180
34
Tempe, AZ
Thank you so much for this! Aside from the laggy UI, which isn't an issue since we got TWRP (f yes!!!), this is amazing. Do you foresee any issues flashing fonts? I am not familiar with ChromeOS and Android structure combination as it seems there is a lot of talk about. Flashing a file that replaces the stock fonts with the ones of my choosing hypothetically should not pose a problem to /system/fonts/, correct? Thank you for your work :D
 

Top Liked Posts

  • There are no posts matching your filters.
  • 20
    This is UNOFFICIAL TWRP for the Pixel C. That said, the TeamWin team greatly helped me in getting this working. But at the same time, neither TeamWin nor me take any responsibility whatsoever for any undesired outcome resulting from any kind of use of this project and project files! If you don't exactly know what you're doing then just walk away and do something good. Don't touch any options of which you don't exactly know what they're for!

    What works:

    * So far, everything; encryption support should work, but some feedback on this would be welcome

    Problems:

    * The GUI will be sometimes slow, sometimes super slow. This is probably due to the high screen resolution of the Pixel C.

    How to install:

    - Unlock bootloader
    - In the bootloader, run "fastboot flash recovery <.img file>"
    - Reboot into Pixel C bootloader
    - Boot into recovery (or later on/from Android through "adb reboot recovery")

    If the recovery doesn't stick after booting into Android:

    - Do the install procedure as above
    - Do NOT reboot into Android
    - Press Vol-Down + Power until you see the bootloader menu
    - Select "Boot into Android Recovery"
    - When in TWRP, mount system
    - Using TWRP's File Manager, or using adb, delete the file "/system/bin/install-recovery.sh"
    - Reboot

    After doing this, OTAs won't work any longer, but they wouldn't work anyway after installing TWRP. Just so you know ;)

    DOWNLOAD

    twrp-3.0.0-0-dragon-ryu-02-11-2016-1.img
    SHA1 hash: 3e97aae6cc18975683eda2bd3732faaecec14166

    Changelog

    :: 01-19-2016-1

    - Removed screen timeout by default, since the GUI is very slow and the screen unlock slider is very hard to use

    - Added an option to fix the Fastboot Full Cap flag directly from TWRP; you find the option in "Advanced". If the Pixel C should ever not let you flash in fastboot, boot into TWRP, select Advanced -> Fix Fastboot, swipe to confirm, and you're set.

    :: 02-11-2016-1

    - Rebased on twrp/android-6.0 branch (i.e. upgraded to TWRP 3.0.0-0)

    The recovery is based on the Pixel C stock kernel.
    5
    @cheep5k8 - havent heard from you in a bit in this thread - any plans to update to 3.0.2.0? it solved the encryption issues on other platforms

    having issues with the 2-11 build on NPC91K

    3.0.2-0 Update is planned - but I can't guarantee that I get to it before the weekend...
    4
    OK guys, if you really want actual SuperSU, and other root stuff, and decrypted /data, here's how it works but it's complicated and will only work tethered as far as I can tell.

    First, download this boot image: dragon-boot-encryptable-01092016-1.img

    Now here are the steps:

    - make sure you have a stock boot.img handy in case something goes wrong (as usual I can not take responsibility but chances of bricking are extremely slim if you know what you're doing)
    - boot into fastboot
    - flash the above boot image to boot ("fastboot flash boot dragon-boot....")
    - flash the TWRP recovery (latest version) ("fastboot flash recovery twrp-dragon-...")
    - hold power+vol down pressed.. the device will turn off, keep it pressed even as it turns off, it will turn on again and you are in the coreboot menu
    - select "Android Recovery" which will start TWRP
    - in TWRP, select system as read only when it asks ("never write onto the system partition").. my boot image does not disable dm-verity which seems to be still in effect, so if you change /system, the Pixel will refuse to boot (even though it's unlocked... no idea)
    - once in TWRP, go to "Wipe" and then choose at the bottom "Format Data" (just wiping will not work)
    - when that's done stay in the recovery
    - get SuperSU 2.66 from somewhere and flash it through TWRP (using sideload for example)
    - when it's done, go to "Backup" in TWRP and only backup boot (the kernel) - no password - no compression
    - somehow copy the backed up kernel from the device to your computer ("adb pull" for example), but in no case let the Pixel boot into Android
    - when that's done, tell TWRP to boot back into the bootloader

    Now get ready to be real quick...

    - boot (just boot, not flash) the TWRP backed up boot image (it's 32MB large and called boot.emmc.win, but it's all good): "fastboot boot boot.emmc.win" (and now you have to be rather quick)
    - It will boot up for a second and then go back to the "The OS will boot in 30 seconds screen"
    - Again press power+vol down and hold it, even as the device turns off, until you're in the coreboot bootloader
    - There, choose fastboot again
    - And once again boot the boot.emmc.win image ("fastboot boot boot.emmc.win")

    - Now let it boot up
    - If everything went OK you should be in Android, with decrypted /data, and SuperSU should be installed and working

    If you want to avoid being encrypted again (although SuperSU should survive that) you will have to boot tethered everytime using that boot.emmc.win image.

    Known Issues: Somehow because /data is decrypted, "Security" settings in Android will crash. Hopefully you don't need anything in there. You might also want to skip setting a lock pattern or pin when doing the initial setup, it might crash too.

    So far, I tried installing AdAway using root which worked just fine.

    If someone figures out how make this untethered: you da real MVP!
    3
    +1

    And USB OTG support would be a dream (for making Nandroids on sticks) :)

    Yeah I will look into it, I need to buy some USB-C OTG adapter first, or an USB-C usb stick ;)
    3
    OK, so, I'm running the device unencrypted now, but there are many issues still to resolve.