yashsingh1/xdaforums huggingface dataset:
[Pixel C Original Android Development] EvansJD:
Tried last night but didnt work for me for some reason. Dont normally have any issues rooting/flashing.

Can you tell me what this actually means?

"Reboot into Pixel C coreboot bootloader"
[Pixel C Original Android Development] ZiggSVO:
just the bootloader, not fastboot bootloader
[Pixel C Original Android Development] cheep5k8:
You need to press power+volume down, and keep it pressed, even as the device turns off (if it was on in the first place). It will then turn on again in the coreboot (or maybe it's depthcharge) boot menu.

If the device was off in the first place, same thing: press power and vol down at the same time until it turns on to the bootloader menu.

You need to keep the buttons pressed for a good while, when the device is on maybe 15-20 seconds (?), but it will eventually reboot into the bootloader, optionally turning off in between.

Just keep in mind to keep the buttons pressed at all times until you see the bootloader menu.
[Pixel C Original Android Development] Evans_jd:
will try again tonight

thanks

---------- Post added at 02:55 PM ---------- Previous post was at 02:48 PM ----------

I get the following when trying the fastboot flash recovery command

FAILED (remote: unsupported command)
[Pixel C Original Android Development] cheep5k8:
OK, well, you've run into the fastboot issue. There's two options:

- If you're already rooted, you need to run fwtool

or

- If not, relock and unlock the bootloader again

BUT proceed with caution. Especially on relocking the bootloader. Best is if you post again with some details about the state of the device (what did you flash already, rooted or not, etc.)
[Pixel C Original Android Development] Evans_jd:
Thanks

I have TWRP now.

I had not done fastboot oem unlock

For my own sanity, if I want to go back to stock and locked bootloader do I just

fastboot oem lock ?

---------- Post added at 03:35 PM ---------- Previous post was at 03:23 PM ----------

bugger!

I ran it

now have "OS on your tablet is damaged. Needs recovery"

:(

---------- Post added at 03:46 PM ---------- Previous post was at 03:35 PM ----------

I got through to having TWRP installed, seemed fine

Without thinking (lesson 1, dont mess with tablet while in a conference call) I ran fastboot oem lock

not it only boots to fastboot or to coreboot

Lock state says locked

message below this says "OS on your tablet is damaged. Needs recovery"

help!

I'm an idiot!

---------- Post added at 04:35 PM ---------- Previous post was at 03:46 PM ----------

OK, so I rebooted it and its booting into TWRP but nothing else

Help me get back to stock please and I promise never to try again!
[Pixel C Original Android Development] brando56894:
If you don't want root, just download the stock images from google and flash them with fastboot. If you want root, just flash on of the root boot image in fastboot, however DO NOT flash supersu in twrp. Once the tablet boots into Android you will see a popup that says that your tablet is damaged and to contact the manufacturer, just ignore it, everything is fine.
[Pixel C Original Android Development] Evans_jd:
Update

I followed the instructions here

https://developers.google.com/android/nexus/images

And have reverted to stock :) phew!

I had to use the Fix Fastboot option inside TWRP first though as it fastboot kept failing before

I'm staying with stock!
[Pixel C Original Android Development] dkryder:
Good thing fix fastboot is available.
[Pixel C Original Android Development] followmsi:
Very nice work ... Thanks for this custom recovery.

I have an OTG USB adapter which detects the connected USB stick in Android, but not in TWRP.

Should OTG or MTP work in this TWRP ?

Thanks
[Pixel C Original Android Development] cheep5k8:
I might have not enabled it when building. I'm going to release a new version maybe end next week or so, I'll double-check then to make sure that OTG support is enabled.
[Pixel C Original Android Development] followmsi:
Thanks a lot !
[Pixel C Original Android Development] doumer:
good to hear – hoping for a version which doesn't force decryption ;)
[Pixel C Original Android Development] Me Gusta:
Man, seeing a dedicated developer like [MENTION=4867279]cheep5k8[/MENTION] makes me really excited for ordering a Pixel C some time soon!
[Pixel C Original Android Development] Scarfacez2007:
But I wondering if I can downgrade on my Pixel C? 6.0.1 (MXB48T) to 6.0.1 (MXB48K)?? ASAP
[Pixel C Original Android Development] followmsi:
You can use this TWRP and the xceed kernel with MXB48T.

Just flash recovery and the kernel .. Pls follow the instructions in the kernel thread.
[Pixel C Original Android Development] oRAirwolf:
I am not sure why, but I cannot flash this recovery after upgrading to MXB48T.

C:\>fastboot flash recovery twrp-2.8.7.0-dragon-ryu-01-19-2016-1.img
target reported max download size of 268435456 bytes
erasing 'recovery'...
(bootloader) erasing flash
OKAY [ 0.049s]
sending 'recovery' (13760 KB)...
OKAY [ 0.348s]
writing 'recovery'...
(bootloader) writing flash
OKAY [ 0.377s]
finished. total time: 0.777s

No matter how many times I flash it in Fastboot, it keeps booting to the Android with the red exclamation point. If I boot back into Android, then issue adb reboot bootloader, it goes to the red exclamation android. If I hold the power button and press volume up, it goes into the stock recovery. I am perplexed as to why it is going into the stock recovery after saying it successfully flashed TWRP.

Any ideas?

Update: Completely wiped the tablet and installed MXB48T again. Same problem :(

Update 2: Manually erased and flashed all partitions by hand, rather than using the flash-all.bat script. Still the same problem. I am wondering if maybe MXB48T broke TWRP.
[Pixel C Original Android Development] bill3508:
Still works if you just flash system and vendor off the previous build.
[Pixel C Original Android Development] beardymcgee:
I had the same issue only fixed it by flashing the modded XCEED kernel boot img first then rebooting then flashing the twrp img
[Pixel C Original Android Development] oRAirwolf:
I just flashed back to MXB48J and I am still having the same problem. I am beyond confused now.

If I flash twrp-2.8.7.0-dragon-ryu-01082016-2.img, which is an earlier build, it works with no problems. It's the latest build that is not working :(

[MENTION=4867279]cheep5k8[/MENTION] Is there anything I can do to help troubleshoot this?

Edit: I was able to flash twrp-2.8.7.0-dragon-ryu-01082016-2.img over MXB48T with no problems. I guess it must be something specific to the current version.
[Pixel C Original Android Development] henryhu:
I think that I have the same problem. When I flash the recovery and reboot into android, then into recovery, it's stock recovery.

However, if I flash the recovery, without booting into android, boot into the coreboot bootloader and enter recovery, it's TWRP.

So I guess that android replaces recovery with the stock version.

You can try just "fastboot boot twrp-....img", and that works, although it's not permanent.
[Pixel C Original Android Development] cheep5k8:
OK so, this is spot on.

The problem is that there's a script in /system that gets executed at each boot, that restores the recovery to default. If you flash SuperSU systemless (2.66 or 2.67) it gets disabled, but again, don't flash SuperSU on the Pixel C (at least not until Chainfire officially announces support for the Pixel C)

You basically have to delete /system/bin/install-recovery.sh right after flashing TWRP. So, go to fastboot, flash TWRP, go to the bootloader (not fastboot but the actual bootloader), boot into TWRP, mount /system and delete the file. That will make the recovery stick. The trick is not to boot into Android after flashing TWRP, but right into TWRP itself, and then delete that file.

I'll take care of that in the next kernel build. Well, not really next, as I'm about to post xCeeD v1-RC3, but in RC4 I'll take care of that automatically.
[Pixel C Original Android Development] oRAirwolf:
Thank you sir! I will update that guide I made.
[Pixel C Original Android Development] doumer:
just saw your update with working encryption support, thanks alot gonna try that later! can I just flash twrp and then latest supersu or is your kernel also needed?
[Pixel C Original Android Development] cheep5k8:
You will still need a modified kernel image (either my custom kernel or the modified stock kernel image, both are linked in the kernel thread OP).
[Pixel C Original Android Development] doumer:
ah okay thanks so instead flash the modified boot img (dragon-boot-encryptable-rooted-MXB48T-02102016-1.img) to retain encryption and than flash twrp, correct?

gonna try it as soon as i'm back home and report back if there are an problems with encryption enabled.

update: this doesn't seem to work with encryption. I can't mount data in twrp (only says internal storage 0mb) and therefore can't push the su.img to data and then superuser.apk complains about missing files so no root for me :(

update2: luckily phhusson's boot img works and gives me root sot at least I'm rooted again ;) still looking forward to a working twrp with encryption - if i can help by testing i'll gladly do.
[Pixel C Original Android Development] Nbay64:
[MENTION=4867279]cheep5k8[/MENTION] I can't seem to use my usb type-c drive while in TWRP. The recovery doesn't appear to recognize it. Any idea what the problem is? I really need to be able to use my type-c drive in TWRP so that I can save backups to my drive in order to save space on the tablet.
[Pixel C Original Android Development] scoobydu:
I could have sworn I read that chainfire wasn't updating supersu for the Pixel C because of the changes required for the Pixel C chromeos past.

Did I understand that correctly, or its being worked on as far as you know?
[Pixel C Original Android Development] charesa39:
That's what he said a few weeks ago. He said it would take up a lot of his time to make it compatible with ChromeOS boot images. However, from what I've read from [MENTION=4867279]cheep5k8[/MENTION], it would appear he has had a change of heart and is slowly integrating the changes into SuperSU? That would be awesome.
[Pixel C Original Android Development] scoobydu:
OK thanks, that would be cool if he is integrating :)

[MENTION=631273]Chainfire[/MENTION], thanks, if thats the case :)
[Pixel C Original Android Development] drewski_1:
in the kernel thread, he said 2.67+ would work.

i just flashed 2.68 on my new Pixel C with the Xceed kernel and it's working fine.

there was an error message about modding the boot.img during the Flash in TWRP, but the kernel already has the modifications needed for Root so you can ignore that.
[Pixel C Original Android Development] scoobydu:
Cool thanks.

That was what was confusing me to be honest, as I have rooted my Nexus 9 and supersu modifies the original boot.img itself, so I wondered why we needed to flash another kernel too for the Pixel C? Perhaps for another reason.
[Pixel C Original Android Development] brando56894:
Chainfire said that most likely because he doesn't have a Pixel C and knows very little about it, I think Cheep5k8 offered to help Chainfire since he already had a working systemless root and the knowledge to help, so that's probably the reason for the change of heart.
[Pixel C Original Android Development] drewski_1:
Chainfire said that he DOES own a Pixel C.

It's more the whole Frankenrom thing of hybrid Chrome OS + Android

Edit: http://xdaforums.com/showthread.php?p=65839947

Sent from my Moto X
[Pixel C Original Android Development] dkryder:
i read awhile ago on github discussion for twrp code that the failed to unmount /system issue in twrp has been fixed in 3.0.0.2. i had noticed this bug when in twrp to delete the recovery script file.
[Pixel C Original Android Development] drewski_1:
my USB-C OTG cable hasn't arrived yet, but can someone verify that OTG is working in TWRP?

i have the 32GB tablet so would like to backup to External :D

thanks!
[Pixel C Original Android Development] followmsi:
No, it's not working. :(

USB-C seems to be different.

Hopefully [MENTION=4867279]cheep5k8[/MENTION] will look into this issue ..
[Pixel C Original Android Development] drewski_1:
Thanks! ?
[Pixel C Original Android Development] minieod:
trying to debug on my side - but twrp wont allow modifications

i just got the tablet today, with intent to put N on it. ive unlocked the bootloader and loaded twrp 3.0.0.0 on. ... once in, i swipe to allow modifications, and nothing mounts. i get the "internal storage (0 MB)" issue

current system installed is stock mxb48t and xceed 6.10 for M ... it seems twrp is acting like it is encrypted and cant access it.

id like to get twrp working properly on M build before updating to N.

thoughts?

edit: i was forgetting to format data in twrp menu to decrypt. got it now
[Pixel C Original Android Development] sniperfox47:
[MENTION=4867279]cheep5k8[/MENTION] Sorry to bother you, but do you have the source for your TWRP build anywhere? Took a look on your github and didn't see anything, was wonderingg if you had released it. I'd love to go digging through and see if I can't figure out what the problem with encryption is, but I'd rather not recreate the wheel from scratch if you've already done so.
[Pixel C Original Android Development] cheep5k8:
Ummm... It's right there:

https://github.com/md5555/android_bootable_recovery_dragon
[Pixel C Original Android Development] sniperfox47:
*smacks my head* Well... I feel like an idiot now. I'm just blind. Thank you xD
[Pixel C Original Android Development] minieod:
[MENTION=4867279]cheep5k8[/MENTION] - 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
[Pixel C Original Android Development] redukt:
+1

And USB OTG support would be a dream (for making Nandroids on sticks) :)
[Pixel C Original Android Development] cheep5k8:
Yeah I will look into it, I need to buy some USB-C OTG adapter first, or an USB-C usb stick ;)
[Pixel C Original Android Development] cheep5k8:
3.0.2-0 Update is planned - but I can't guarantee that I get to it before the weekend...
[Pixel C Original Android Development] followmsi:
Off topic .. But how to unpack your current twrp.img ?

My normal unmkbootimg tells me .. error: not an Android Image

How to unpack correctly ?

Thanks a lot !
[Pixel C Original Android Development] minieod:
Yeah that's totally fine. Just wanted to confirm if one was on the way.

Thanks for all you do!
[Pixel C Original Android Development] cheep5k8:
It's a ChromeOS boot image.

dd if=twrp.img of=unpacked.img ibs=65536 skip=1
unmkbootimg unpacked.img
[Pixel C Original Android Development] oRAirwolf:
OTG is no longer used with USB Type C.

I asked Benson Leung on Google + about this. This was his reply:
[Pixel C Original Android Development] drewski_1:
However it's called, we want to Nandroid to it directly in TWRP ;)
[Pixel C Original Android Development] NYCHitman1:
[MENTION=4867279]cheep5k8[/MENTION] - I was able to compile 3.0.2-0 off of what you had originally started.

Something I noticed was that your 3.0.0-0 version of TWRP seems to suffer from not properly mounting partitions (particularly /system). I took a look and it seemed that you may have mapped the call to twrp.fstab wrong. The copy-to dir should be recovery/root/etc/twrp.fstab. Just wanted to give you a heads up.

Currently, I'm trying to figure out how to debug this MTP issue as it's irritating the hell out of me that I can't use MTP in recovery right now, but SU is evading me atm.

adb shell twrp set tw_mtp_debug 1

Then enable and disable MTP in mount settings to collect the data in recovery.log.

EDIT: Do you know if vboot flags are required for the kernel to allow boot into system? It seems that SU can't be flashed inline w/ ROM because the boot.img being signed stops the ramdisk from being unpacked and modified during SU flash.
[Pixel C Original Android Development] cheep5k8:
Hey,

just a quick note in between: I don't think that any vboot flags must be set to boot into system. The only system boot related setting that I know of is that upon boot, the boot gets marked as success in the SPI flash.
[Pixel C Original Android Development] NYCHitman1:
The irony is that my builds refuse to boot when vboot and verity have been disabled. I've been trying to figure out why, but haven't come across anything yet.
[Pixel C Original Android Development] dkryder:
NYCHitman1 said, "Something I noticed was that your 3.0.0-0 version of TWRP seems to suffer from not properly mounting partitions (particularly /system). I took a look and it seemed that you may have mapped the call to twrp.fstab wrong. The copy-to dir should be recovery/root/etc/twrp.fstab. Just wanted to give you a heads up."

check the twrp github issues as it was reported that the unmount /system was a problem with twrp although not specifically how it was fixed, just that it had been fixed in 3.0.2.0.
[Pixel C Original Android Development] NYCHitman1:
Regardless, the declaration is incorrect as to where it's currently mapped to. That's why I mentioned it to him.
[Pixel C Original Android Development] minieod:
Awesomeness and hopefully a working 3.0.2.0 soon!
[Pixel C Original Android Development] NYCHitman1:
http://xdaforums.com/showthread.php?p=66557703
[Pixel C Original Android Development] oRAirwolf:
Is anybody else having trouble with [MENTION=2489052]NYCHitman1[/MENTION] 's version of TWRP? I cannot get it to mount the data partition and I can't see any of my files on my SD card. I am flashing it on a clean install of MXC89F.
[Pixel C Original Android Development] dkryder:
there are several reports , not specifically pixel c, on twrp github about issues with mount /data and/or reading partitions with the 3.0.2 build. i'm not sure if the issue is in the pixel c build because i have not used that build yet.
[Pixel C Original Android Development] NYCHitman1:
Are you decrypted?
[Pixel C Original Android Development] scamish76:
Upon finding out DU was released for the PIxel C, i wanted to give it a go... however, Im also having an issue getting TWRP to work with a fresh MXC89F install. I have previously unlocked the bootloader and installed XceeD, but when I flash TWRP, I can only boot into recovery (TWRP). I also cannot mount system or view contents of sdcard.
[Pixel C Original Android Development] followmsi:
On stock you are forceencrypted.

TWRP has still some issues with encrypted data partiton.

Are you able to format data inside TWRP ?

Afterwards can you copy supersu 2.72 via adb push to new formatted data partiton ?

If possible, install SuperSU.zip and boot normally into system again.

All done in TWRP no reboots in between.

If you cannot copy and install SuperSu 2.72 you have to install xceed kernel or other stock rooted kernel to be able to boot into system.

Strange issue .. you are not alone. :)
[Pixel C Original Android Development] scamish76:
thanks you for the quick reply. I wasnt able to format data until I reflashed XceeD, after TWRP. Now things are working correctly as they should. :good:
[Pixel C Original Android Development] followmsi:
I have made a new version of TWRP .. this version is able to mount USB-OTG storage. :)

Update.ZIP_TWRP_dragon_3.0.2-0_v4.zip

Now we should try the following steps ..

1. Full encrypted unrooted stock device as starting point.

2. Install new TWRP version via fastboot. (Extract the recovery.img from .zip)

3. Directly boot into recovery, not into system in between.

4. Install SuperSu.zip 2.72, not below, from USB stick.

5. Before you reboot you have to format /data partition inside TWRP.

6. Reboot into system and check unencrypted /data and root status !

Next step is encryption for TWRP ... to enable TWRP to access encrypted /data partitions..

Maybe we can fix this as well ?

SuperSu has also new parameters for ramdisk patching .. "keep forceencrypted" ..

Needs all to be tested ... :)

Cheers
[Pixel C Original Android Development] drewski_1:
can you post a link to your TWRP test version?

EDIT: Just saw the thread in the General section :good:
[Pixel C Original Android Development] followmsi:
http://xdaforums.com/pixel-c/general/twrpdragon3-0-2-0v4-twrpdragon3-0-2-0v5-t3379040

Cheers
[Pixel C Original Android Development] greco2003:
3.0.0-0 will this version flash vendor.img or should i just push it through fastboot?? Thanks
[Pixel C Original Android Development] Freak07:
I think you have to use fastboot.
[Pixel C Original Android Development] followmsi:
It's activated on v4 .. for vendor.img and system.img - needs to be tested .. please go ahead.

Thanks
[Pixel C Original Android Development] YevOmega:
Got the no command error after deleting that file in [MENTION=4867279]cheep5k8[/MENTION] 's instructions. Ideas [MENTION=2489052]NYCHitman1[/MENTION] ? Tried everything. Flashed N image file by file, then M. The former got me back to the no command error. Flashing M has me stuck at the Google logo on boot. :mad:

Edit: Fixed it after hours of work, literally. Gonna be back on DP3 soon, but idk how to install SuperSU now because I can't get TWRP. If I use the method without deleting the file, it doesn't stick.
[Pixel C Original Android Development] Istvan_86:
Hi mate,

I have exactly the same issue in the same build than you after unlock bootloader and install TWRP. How did you solve the problem?

Also I´m using xceed kernel.

Thanks in advance.
[Pixel C Original Android Development] drewski_1:
Try the TWRP from [MENTION=5480152]followmsi[/MENTION]

http://xdaforums.com/pixel-c/general/twrpdragon3-0-2-0v4-twrpdragon3-0-2-0v5-t3379040

Working good for me + USB access enabled!
[Pixel C Original Android Development] Istvan_86:
Really nice mate,

Finally after try all TWRP versions available the same version that you post here solved my problems but I also wipe data in TWRP. After that all goes fine.

Thanks for all your help guys.
[Pixel C Original Android Development] Mustkeg:
So I have to wipe /data in TWRP before I can mount and backup /data in TWRP? :silly:
[Pixel C Original Android Development] Istvan_86:
Yes I did that and all problems gone. Hope this do the same for you :good:
[Pixel C Original Android Development] NYCHitman1:
I did tell you that from the get-go lol
[Pixel C Original Android Development] Istvan_86:
Hi,

Sorry didn´t try to steal any credits or similar, english isn´t my native language and sometimes I can´t express myself as good as I want.

I read a lot of post and forums, ask a lot of people, all help me (you the most xD), and sometimes is hard to express al the ideas in my mind or the steps that I did trying to solve the issues that I have.

Sorry again if my latest post looks bad :(

Anyway, back to our problem, I hope that Mustkeg can fix the issues he has.
[Pixel C Original Android Development] NYCHitman1:
Yes, that is correct. Getting the encryption libs functional in TWRP is still a WIP.

EDIT: Try this
[Pixel C Original Android Development] MVP__911:
could U help me guys please

TWRP LOOP is killing me :(

am new to google devices

what is the easiest way to solve the problem?
[Pixel C Original Android Development] NYCHitman1:
Flash a kernel.
[Pixel C Original Android Development] MVP__911:
thanks for the tring to help me :)

by the way I solved the problem by using WugFresh tool <3
[Pixel C Original Android Development] ReVaNzz:
Bricked??

Hi, I'm getting this error too when trying to flash again whatever "FAILED (remote: unsupported command)".

I flashed the TWRP version posted here once, and when rebooting the device just get into bootloader, no OS nor recovery mode works, it always drives me to bootloader.

Also there is a message on bootloader screen saying "OS on your tablet is damaged. Needs Recovery".

With all this mess, it seems fastboot is the only working tool, but when I try to flash recovery, OS, whatever... I get this back message "FAILED (remote: unsupported command)".

Any ideas?? :( :crying:
[Pixel C Original Android Development] vman00:
Sounds like you have to update your drivers for when your devices is in fastboot. I had to update my android studio tools to android oero versions to the commands to work.