yashsingh1/xdaforums huggingface dataset:
[Pixel C Original Android Development] Istvan_86:
Hello,

After a few unexpected days of hard work I try to flash your ROM today, after the backup + factory reset I try to install the ROM and it gets stuck on this part (photo is attached below). Then I wipe all (except internal storage) and try to flash through recovery the Update.ZIP_PixelC_Ryu_MXC89H-system-vendor.zip, wipe all (except internal storage) then flash the ROM again and I get stuck in the same point.

What can I do?

Thanks in advance.
[Pixel C Original Android Development] ilpolpi65:
I had the same error......today I was curious to try DU...playing a bit with the ROM...backup ..and I decided to give another chance to cvano ; the installation went OK.

So from stock to cvano error....from stock to DU to cvano all OK. Strange !!!
[Pixel C Original Android Development] ggow:
Thanks for that extra bit of information

I'll take a look into why that might be the case, no sure at the moment.
[Pixel C Original Android Development] Istvan_86:
Hello,

Whats is cvano? and thanks for your answer mate.

---------- Post added at 12:03 AM ---------- Previous post was at 12:02 AM ----------

Can I provide you some kind of log or similar?

Thanks!!
[Pixel C Original Android Development] ilpolpi65:
sorry ..I meant Cyanogenmod
[Pixel C Original Android Development] ggow:
If you could provide the recovery log, that would be great. Had an initial look, it seems the restore function of the backup script which is run when installing the rom is not returning for some reason.
[Pixel C Original Android Development] Istvan_86:
Ok, so I must Flash update.zip with system vendor MXC89H + DU + CM13, right?

Thanks again.
[Pixel C Original Android Development] ilpolpi65:
Sorry I can't I'm on N4

---------- Post added at 12:13 AM ---------- Previous post was at 12:07 AM ----------

Yes ...you can flash vendor- Du-backup Du-factory reset-flash Cyanogenmod
[Pixel C Original Android Development] Istvan_86:
Thanks again mate I´ll try it tomorrow and post the results.
[Pixel C Original Android Development] Murmel2k:
Hi,

can someone tell my, why I have to flash a vendor.img seperately? When the Dirty Unicorns ROM was released, I thought, it was due to the early state of developement. But since this Cyanogemod-ROM also needs a vendor.img to be flashed, it seems to be a Pixel C related issue.

And what are the implications of having a wrong vendor.img? The starting posting says, that I should flash MXC89F. But on the Google Developer Page there seems to be a newer version. Would Cyanogenmod also work with that?.

Thanks!
[Pixel C Original Android Development] ggow:
The vendor.IMG is the new way of distributing the proprietary binaries that would normally live in the /system partition on most older devices.

CM-13 will work with the newer vendor.IMG.
[Pixel C Original Android Development] Murmel2k:
Thx for the clarification. I guess, I have to flash the vendor.img via fastboot? Or is also flashing via recovery possible?
[Pixel C Original Android Development] ggow:
I always flash it via fastboot, never tried from the recovery.
[Pixel C Original Android Development] parakleet:
I wiped and flashed and re downloaded for a week.

Always got that screen.

Frustrated as hell left it on that screen for a weekend and on Monday open the lid and I was staring at the Cyanogenmod setup screen.

I have no explanation.

Hope that helps.
[Pixel C Original Android Development] nic.:
Is there any way to flash gapps after setup has ran? I have a full Kali chroot, that I do not want to lose, but I tested flashing gapps, and they all fc on boot.
[Pixel C Original Android Development] NYCHitman1:
Nope. Gapps were meant to be flashed inline with the ROM. Your alternative would be to push the necessary bits via ADB.
[Pixel C Original Android Development] greco2003:
Installed rom loving it but when I boot it up it says there's an internal problem contact device manufacturer anyone know why runs fine...
[Pixel C Original Android Development] NYCHitman1:
That's because the system build.prop doesn't match the vendor build.prop. Not a big deal though.
[Pixel C Original Android Development] greco2003:
How to fix or is it possible to fix thank you
[Pixel C Original Android Development] NYCHitman1:
That's up to [MENTION=5749760]ggow[/MENTION]
[Pixel C Original Android Development] ggow:
I'll fix it in a later release as NYChitman1 said its not a big deal.
[Pixel C Original Android Development] NYCHitman1:
This is the fix: https://github.com/DirtyUnicorns/an...mmit/5470fd684e912ddea6baa14918167065283274b1

EDIT: Shoot me a PM and I can show you how to cherry-pick this commit.
[Pixel C Original Android Development] ggow:
Thanks, I'm going to have a go.

From what I read I need to add the DU repository as a remote, fetch and then use the git cherry-pick <commit-ref>

Been reading quite a bit about git which I have been meaning to do for ages.
[Pixel C Original Android Development] NYCHitman1:
Precisely.

Add remote, fetch remote, cherry-pick hash.
[Pixel C Original Android Development] ggow:
That worked: https://bitbucket.org/pixelc/android_device_google_dragon/commits/all

:)
[Pixel C Original Android Development] ggow:
temasek build of CM-13

- I have built temasek's unofficial CM-13 ROM.

- I have a Nexus 6 on which I have always run this ROM since been available and it is my favourite so far

- If anyone is interested I can post it sometime this weekend
[Pixel C Original Android Development] sxg75:
[MENTION=5749760]ggow[/MENTION] in short what are benefits from temaseks cm13? thanks in advance!

some would prefer "pure" cm13, so maybe that made it easier to decide.

also: is there some short faq about "what works/what works not" against stock pixel c marshmallow?

sorry, many Qs but alas, thanks in advance!
[Pixel C Original Android Development] redukt:
I've running Temasek on my OPO for a while. It's a great rom and I'm interested for testing it on the Pixel C. Will you give regular updates on it? Thx in advance :)
[Pixel C Original Android Development] ggow:
Yes, I'll make a separate thread that will get regular updates.

When I post it, I'll put a summary of the extras.

This will be separate to the pure cm13 ROM.
[Pixel C Original Android Development] sxg75:
Getting stuck while installing via TWRP, latest version.

Was coming from stock N4 preview, then downgraded to latest stock MM image (by flashing system/vendor .zips from the other thread).

After factory resetting, while flashing CM13 it hangs while “detected filesystem ext4 for /dev/block/platform/700b0600.sdhci/by-name/APP

... Please see screen...

Do I Have to downgrade Bootloader also?
[Pixel C Original Android Development] ggow:
Shouldn't have to downgrade the bootloader, but for completeness of information I am running the MM bootloader.

I am using the recovery by [MENTION=2489052]NYCHitman1[/MENTION] posted here.

Don't know if this makes a difference.

I should have a chance to look into this sometime in the coming week.
[Pixel C Original Android Development] NYCHitman1:
Take a peek at your fstab.
[Pixel C Original Android Development] Istvan_86:
Hi mate,

Your steps doesn´t work for me.... I need look in to something more.

Any advices?

Thanks anyway mate.
[Pixel C Original Android Development] king tsoi:
Hi, after a couple hours of work, I finally got it installed. It runs very well, thanks for the good work!

For some reasons I am not able do it using twrp, I can flash it in twrp, but after that it always reboot into recovery.

At the end I tried to flash it using nexus root toolkit and it worked.

So far the only thing not working is the keyboard, Bluetooth turn on automatically when I attach it to the tablet,

I am able to pair it as well, but none of the keys works. I am thinking maybe it is because the ROM don't have the .kl file for the keyboard.

I wonder If anyone can extract it from the stock ROM and share it? Many thanks!
[Pixel C Original Android Development] ilpolpi65:
you could try to use Nexus root toolkit as mentioned from [MENTION=7235732]king p[/MENTION]ost looks is working ok
[Pixel C Original Android Development] king tsoi:
update: turns out the .kl file does exsit in the cm rom but i ve found the Vendor_18d1_Product_5018_Version_0102.idc is missing,

i don't know if this file matters, i extract it from the stock ROM and put it in the system, reboot, unpair the keyboard and pair it again.

Now it works totally fine.
[Pixel C Original Android Development] ggow:
Is this vendor...idc for the Pixel C Keyboard?

If so I'll include it in the next release.

EDIT: Added to my device tree. The file clearly says it's for the Pixel C Keyboard :)
[Pixel C Original Android Development] ggow:
Thanks for the hint, taking a look now.

EDIT: Not seeing anything obvious :confused:
[Pixel C Original Android Development] Istvan_86:
Thanks for your answer, I´m searching Nexus root toollkit and I can´t find it, I found Skipsoft android toolklit.

I´m a bit desperated, nothing is working for me after CM13 install fails. What options is the most suitable for me in NRT?
[Pixel C Original Android Development] ilpolpi65:
http://www.wugfresh.com/nrt/
[Pixel C Original Android Development] Istvan_86:
Yeah yeah I have it downloaded and installed, I thin kthat I should use the option Flash Stock + Unroot with Soft-Bricked/bootloop checked I´m right?

---------- Post added at 02:31 PM ---------- Previous post was at 02:06 PM ----------

Tablet back to life with NRT!!!!!!

Really thanks for all your help mate.
[Pixel C Original Android Development] sxg75:
Ok now back to topic pls?
[Pixel C Original Android Development] NYCHitman1:
Can you link me to your source again?
[Pixel C Original Android Development] ggow:
Should be linked on the OP.

https://bitbucket.org/pixelc/android_device_google_dragon/commits/all
[Pixel C Original Android Development] NYCHitman1:
Not seeing anything outlandish. Might be something in CM's source that is messing with the flash.
[Pixel C Original Android Development] ggow:
Thanks for taking a look, guessed the same too.
[Pixel C Original Android Development] NYCHitman1:
Check their build/vendor repo
[Pixel C Original Android Development] ggow:
I have identified and fixed the issue with the installation getting stuck.

The problem was in the android_vendor_cm repository within the backuptool.sh script.

I will fork the project and add my changes then link it in the OP.

New ROMS will be up shortly :)
[Pixel C Original Android Development] ggow:
New Build is Up

- Dated 20 Jun 2016

- Fixed installation getting stuck

- Using the recovery by [MENTION=2489052]NYCHitman1[/MENTION] posted here.

EDIT:

- Added support for the Pixel C Keyboard
[Pixel C Original Android Development] sxg75:
After some Days testing... Great Rom. I love CM13 purity :good:
[Pixel C Original Android Development] zurtu:
Hey, my keyboard is still not working. I paired it with the Tablet in the Bluetooth Settings but I can't use it. Any suggestions? Can anybody verfiy that the keyboard is working?
[Pixel C Original Android Development] ggow:
Did you try re-pairing it. I don't own the keyboard so can't test.

See here for more info: http://xdaforums.com/showpost.php?p=67385292&postcount=77

I included the missing .idc file but was unsure if this made a difference.
[Pixel C Original Android Development] zurtu:
Perfect, repairing did the trick! Thanks.
[Pixel C Original Android Development] sxg75:
Keyboard works great except the fact that its connection times out too fast; is there some way hidden setting that allows to stay online longer as in stock M?
[Pixel C Original Android Development] ggow:
New Build is Up

- Dated 28 Jun 2016

- Merged 2554 commits from Google's "chromeos-3.18" kernel branch into cm-13.0 kernel
[Pixel C Original Android Development] Murmel2k:
Anyone else having trouble to get the 20160628 version to boot? Could this have something to do with my old vendor.img? I didn't flash a new version, because my Win 7 is flawed and doesn't recognize my Pixel C as compatible for the fastboot driver. (My Windows really needs a reinstall)
[Pixel C Original Android Development] badwiring:
Yes, same with latest Temasek. Stuck on Google logo. Tried repeatedly. I'm on the latest vendor image.
[Pixel C Original Android Development] ragesoss:
How is the process of getting it to an official CM build going? Are there specific requirements that haven't been met yet? Anything others can help out with?
[Pixel C Original Android Development] ggow:
Both seem to work fine here. I'm on the latest vendor.img if that helps.
[Pixel C Original Android Development] ggow:
I have sent an email to various people including Steve Klondik but have had no response yet.
[Pixel C Original Android Development] ragesoss:
Did you send one to devrel with all the required info? https://wiki.cyanogenmod.org/w/Doc:_Submitting_A_Port

I'm willing to be the wiki maintainer, if there's not already someone else for that role.
[Pixel C Original Android Development] ggow:
Also sent one to that address also :)

Cool, yes we will need a wiki maintainer - will let you know as soon as I hear from them. Maybe I'll ping them again this week.
[Pixel C Original Android Development] ggow:
New Build is Up

- Dated 08 Jul 2016

- July 2016 Security Patches Included
[Pixel C Original Android Development] raiden:
Any update on getting it submitted to Cyanogenmod? I wonder why they weren't responding.
[Pixel C Original Android Development] ggow:
No response yet :(
[Pixel C Original Android Development] king tsoi:
Will this one reboot randomly like the stock from does?
[Pixel C Original Android Development] sxg75:
Had no random reboot - neither on stock, neither on this rom which I have been using since nearly one month now.
[Pixel C Original Android Development] raiden:
I have also submitted an email to Cyanogenmod about submitting your Pixel C code to devrel@cyanogenmod.org and I received a response back basically saying the submission has been forwarded to the right person but that person responsible is currently on vacation. Sounds like some good news.

Also, your ROM is running very stable (except the random weak wifi signal @ 5Ghz) but one feature that's missing is the 'Double tap to wake' feature. I have this feature enabled on my Nexus 6p + Nexus 9. I notice there's already a 'Double tap to sleep' enabled in the ROM but the wake feature would be great.
[Pixel C Original Android Development] ggow:
That is good news, thanks for letting me know. Double tap to wake implementation is problematic. In one of [MENTION=4867279]cheep5k8[/MENTION], he explained that it would need to change to the EC firmware which is not practical at the moment.
[Pixel C Original Android Development] streilu:
Anyone else has problems with the clock not updating in statusbar?

Gesendet von meinem Pixel C mit Tapatalk
[Pixel C Original Android Development] ggow:
Yes, I am having the same problem, it's on my TODO list :)
[Pixel C Original Android Development] maxafe:
I can't install this ROM. After installation (incl. Gapps) there is a bootloop with the Google logo, but no error. I use TWRP 3.0.2-21 from followmsi. Other TWRP versions don't work neither. (The ROM "DU" is working.)
[Pixel C Original Android Development] Malganor:
Thanks for ROM! I was wondering if I could encrypt after putting CM on my tablet. Thank you.
[Pixel C Original Android Development] pyrocide:
Im seeing some mixed results for wifi speeds in the first few pages.

How is the wireless in general on CM vs stock? Is there still the random drops and other issues etc?
[Pixel C Original Android Development] ggow:
New Build is Up

- Dated 08 Aug 2016

- August 2016 Security Patches Included

- Lastest vendor.img (MXC89L) is linked in the OP
[Pixel C Original Android Development] ExtraFluffyYo:
great rom! However, I still have the status bar clock not updating. I wiped and clean flashed the rom.

Was this fixed during this update?
[Pixel C Original Android Development] ggow:
No, I haven't had enough time to look into it yet.
[Pixel C Original Android Development] parakleet:
Will Not Boot

Clean flash.

Latest vendor image.

Stuck on Google image without animation.

Any Thoughts?

Thanks
[Pixel C Original Android Development] Murmel2k:
Just to provide a hint, of someone has the same problem: I could not flash a new vendor image or the Google Stock images over fastboot. For almost any command fastboot reported

FAILED (remote: unsupported command)

Also the Fix fastboot option in TWRP didn't help. For me it worked booting into the recovery, connecting over adb in shell mode (adb shell) and entering following command:

fwtool vbnv write dev_boot_fastboot_full_cap 1

Afterwards fastboot worked again.
[Pixel C Original Android Development] Murmel2k:
Meh.

Now I have tried every release since the one in the quote. And with none of them I get past the Google logo, even with thw new vendor image. Last working cm-13 is 20160608.

Can someone provide an idea, what could be wrong?
[Pixel C Original Android Development] parakleet:
Same Here

I have had the same issue not being able to push past 20160608.

I have however updated the vendor image.
[Pixel C Original Android Development] dkryder:
my guess would be there is an issue with the stock recovery re-install sequence. my experience was most boot loop issues are due to that problem.
[Pixel C Original Android Development] ggow:
- I have tried to reproduce the issue here

- At least for me there seems to be no issue.
[Pixel C Original Android Development] dkryder:
out of curiosity, what did you do to try reproduce the issue?
[Pixel C Original Android Development] parakleet:
Agreed.

I have flashed a dozen devices, hundreds of times at this point successfully and some not.

Am I missing something this time?
[Pixel C Original Android Development] ggow:
- I went back to stock

- Starting at the 20-06-2016 build of CM

- I flashed each update incrementally

- The files I used were the CM.zip, opengapps nano, and SuperSU-2.76 directly after each other

- I used to reboot from recovery to fastboot to avoid the bootloop issue. As dkryder said the issue should be fixed in the latest TWRP.

- On my device all of them boot just fine.

Let me know if the process to failure is different.
[Pixel C Original Android Development] dkryder:
that's just it, when you try to reproduce failure you do not do things the known correct way. it's like when installing gapps on cm the correct way is to flash immediately after cm not after letting cm boot once. so you can not reproduce those error messages you get by booting once, then flashing gapps by flashing cm , then gapps, then boot. i do not use cm so i can't say what those who fail are doing wrong but this similar issue, the boot loop, comes about in android 6 or 7 when you boot to system instead of recovery immediately after a flash, at least until twrp took care of it. i think they ask a question now about that file.
[Pixel C Original Android Development] parakleet:
No Dice

So i loaded up all 6 files.

1) cm-13.0-20160620-UNOFFICIAL-dragon

2) cm-13.0-20160628-UNOFFICIAL-dragon

3) cm-13.0-20160708-UNOFFICIAL-dragon

4) cm-13.0-20160806-UNOFFICIAL-dragon

5) open_gapps-arm64-6.0-nano-20160612

6) SUPERSU_276<- yes i shortened the filename

ran them all through and no dice.

I also tried other combinations

The only combination that works is 1,5,6.

the inclusion of files 2-4 incrementally or stand alone results a simple Google image.

Fastboot continue does not resolve either.

I tried TWRP 2.8.7 ,3.0.0.0 & 3.0.2-2
[Pixel C Original Android Development] ggow:
Is anyone having any success using the latest version of this ROM?

It works for me just fine, but some more feedback would be nice.
[Pixel C Original Android Development] Murmel2k:
Hello,

thanks for your effort. Sorry had no time the last weeks. But I will go through the procedure flashing all versions of CM-13 this weekend. I will also try to flash a complete stock image to see, if the new versions of cm will work afterwards.
[Pixel C Original Android Development] Auberginenzwerg:
How do i flash the vendor.img

Hey Guys,

How do i Flash the Vendor.img ?
[Pixel C Original Android Development] parakleet:
DL image from OP

If your running latest TWRP just like you would flash a ROM there is a button in lower right side to flash image instead.

Hitting the button will allow you to select the .img and apply it to the appropriate portion of the disk; Boot, Recovery, Vendor etc.

apply to vendor and your good to go.
[Pixel C Original Android Development] Murmel2k:
Hi, some more news from me.

First I've flashed every cm-release in the order you provided and it did not work. Stucked at the Google logo as always.

Afterwards I've installed the latest Marshmallow Stock image from Google (it deletes everything on your internal storage). Then I had to reflash TWRP, followed by (only) the latest cm-13 build and the nano open-gapps. And voilà: Everything works. But I don't know, what exactely made the difference.
[Pixel C Original Android Development] wulvyrn:
When using google hangouts, sending SMS message, it immediately crashes when i type a letter in the send box. Any ideas?
[Pixel C Original Android Development] miscom:
It's been running great for me. I came from Android 7.

Flashed latest TRWP

Erased system, data, dalvik, cache (everything)

Flashed ROM and gapps by sideloading
[Pixel C Original Android Development] Murmel2k:
Had another weird bug today. The last few days my Pixel C had the bug, where the time doesn't update, but i didn't bother much. Yesterday night I left my Pixel C with 4% charge and not attached to the charger. Today I came back from work and it expectedly went out in the meanwhile. I've charged it a bit, turned it on and it was showing the wrong time.

I was not able to change the time manually or by turning off and on the time syncing over internet. Due wrong date/time I also was locked out of every website, that use ssl. I also wasn't able to change the time with tools like lock synch, which uses root to update the time ('unknown error ...' and the number -526404640,000 as 'local offset'). I even wasn't able to change the time, after I wiped and reflashed a fresh cm-13 and started setting up android again.

After reflashing the google stock image I am able to change the time again.
[Pixel C Original Android Development] ggow:
Looking into it, haven't had much time recently but will get to the bottom of it.
[Pixel C Original Android Development] miscom:
[MENTION=5749760]ggow[/MENTION],

I have been trying to compile your ROM from sources but for the life of me I cannot figure out the local_manifests XML file.

Can you post it here? Thanks.
[Pixel C Original Android Development] ggow:
I don't use a local_manifests file. Just clone the repos manually
[Pixel C Original Android Development] Murmel2k:
Ah, no need to hurry. I was aware, that there was some bug messing up the clock. But I wasn't aware, that this bug is capable to survive a complete wipe and a fresh installation of the ROM, so I thought, that this is a different issue that I should report.
[Pixel C Original Android Development] miscom:
I just experienced the same issue with the time set to December 31, 1999.

Any idea how to fix this without wiping? It seems that wiping s sa temporary fix
[Pixel C Original Android Development] miscom:
Something else: The clock is stuck at 7:22pm. It's been at 7:22pm since my last post.

Also, in TWRP Recovery the clock is working fine, but still started counting from 7:22 pm.

The issue started after the battery died.

On reboot from TWRP, Android displays the last date/time set in TWRP and stays there stuck. Time doesn't change. Now it's 7:35 pm December 31, 1999

Well, the clock on the taskbar is stuck at 7:32pm BUT the clock under settings --> Date & TIme is showing 7:42. So, the clock in Settings is moving.

But if I try to change the time, it doesn't change. So weird.