yashsingh1/xdaforums huggingface dataset:
[Pixel C Android Development] Deltalfa:
What were you doing when screen f*** off?
[Pixel C Android Development] Alxoom33:
My dog bit the Pixel C last night!

---------- Post added at 10:37 AM ---------- Previous post was at 10:34 AM ----------

I think he thought it was edibleðŸ˜£

Just a little cosmetic damage on top, protective glass cracked at top edge a few cm's to the left of the camera. # face palm!
[Pixel C Android Development] followmsi:
The dog .. seems to be a hungry one :)

Really bad luck!

But as you know - **** happens.

At least you know the reason for your new screen status :)
[Pixel C Android Development] Alxoom33:
Yeah, he's always hungry and grubbing for food! Luckily he bit the tablet just on the top edge, so everything still works. Only the top of the glass has 2 small breaks.
[Pixel C Android Development] revengers:
With this regard, I would suggest we name the next Android 8 something that is not edible at all. Since we are at "N" now, the next Andriod will be "O".

That said, Android OC (Oleoresin Capsicum) would make an excellent deterrent:laugh:
[Pixel C Android Development] Alxoom33:
Sorry, but my dog can't read. Also, he has trouble accessing the System/About devi e. Lol![emoji6]

---------- Post added at 01:37 PM ---------- Previous post was at 01:23 PM ----------

Is there an Android OTA update today?
[Pixel C Android Development] cam30era:
Yes. It's live now.
[Pixel C Android Development] followmsi:
Android 7.1.1 FINAL (NMF26H, Dec 2016)

system-vendor:

Update.ZIP_PixelC_Ryu_NMF26H-system-vendor.zip

stock kernel:

Update.ZIP_PixelC_Ryu_NMF26H-kernel-dragon.zip

Seems to be still the same bootloader .. bootloader-dragon-google_smaug.7900.27.0.img

Of course we have a "new" compiled 3.18 tegra kernel as well ..

Update.ZIP_PixelC_Ryu_tegra-3.18_KERNEL_NMF26H_v161205_followmsi.zip

kernel-tegra-3.18_v161205_NMF26H_boot.img

Installation:

1. Reboot into TWRP -> TWRP_dragon_3.0.2-23.img

2. Install Update.ZIP_PixelC_Ryu_NMF26H-system-vendor.zip

4. Install Update.ZIP_PixelC_Ryu_tegra-3.18_KERNEL_NMF26H_v161205_followmsi.zip

5. Install SR5-SuperSU-v2.78-SR5-20161130091551.zip

6. Reboot into system

And again .. due to supersu installation it will boot twice - no panic, it´s normal !

Enjoy ..
[Pixel C Android Development] Alxoom33:
Booted up great! Thank you! One question, I don't understand why with this "Final" update why I would get an OTA notification for last month's Android Beta update, NPF26H? Are we going to receive another "Beta" update this month?
[Pixel C Android Development] followmsi:
For me all the beta stuff is gone.

Normal december release which is 7.1.1 this time.

Aosp sources will be updated as well.

It seems you have another special issue :(
[Pixel C Android Development] redukt:
Got also the update message. And the full image download link ;)
[Pixel C Android Development] Alxoom33:
Are you still on the Beta release path. It seemed to me you flashed Android 7.0 at some point last month, which is a non-Beta build. Also, you have a new Pixel. Is it registered for the Android Beta program?

---------- Post added at 05:33 PM ---------- Previous post was at 05:32 PM ----------

1103.2? Same here.
[Pixel C Android Development] followmsi:
Just to understand better ..

You (both) were coming from nfp26h and used the update.zip for the new mf26h.

After reboot you were on the new version, according to "about this tablet" ?

But you still get beta notfications ?

Hmmmm ... I have no beta warning at boot anymore.

No beta symbol in the navbar anymore.

Just no beta anymore ;)

Are you part of beta enrollment ?

Maybe related ?

But strange indeed ...
[Pixel C Android Development] followmsi:
Never been part of the beta enrollment, just manual flashing.

I wiped the new Pixel C completetly, flashed manually TWRP, my tegra kernel boot.img and all the other images from November beta (nfp26h) via fastboot.

Restored my old data via TWRP and rebooted .. all is was back to normal.

And the new update.zip works for me as expected .. like the other ones before.

We overwrite the complete system.img - there should be no beta left anymore ;)

Would like to understand the reason of this issue.
[Pixel C Android Development] Alxoom33:
I am enrolled in the Android Beta program. I am on the new version NMF26H and as soon as I updated I recieved a "System Update" notification for NPF26H (which I updated to in November). Strange...Perhaps there will be another beta update on the 15th.
[Pixel C Android Development] redukt:
Just leave the beta programm and after restart the update message is gone :)
[Pixel C Android Development] followmsi:
No .. there will be no beta anymore.

We are live now.

http://android-developers.blogspot.ch/2016/12/welcoming-android-711-nougat.html

No betas anymore !
[Pixel C Android Development] followmsi:
Expected something like this :)

Forget the beta program, we are faster here ;)

Cheers
[Pixel C Android Development] Deltalfa:
What about the terribile range of bluetooth?
[Pixel C Android Development] revengers:
NMF26H has been working fine for me for the last 1.5 hours. No radio issues with either BT or WiFi. Thanks followmsi for the hard work:cool:

To Deltalfa: Can you specify the problem you are experiencing with BT range, maybe we can look into it. Thanks:)
[Pixel C Android Development] Deltalfa:
BT range is terrible. Listening to music with headphone works only near the pixel or 1 meter at least. WiFi with fibra goes from 15 up to 20 with pixel poor 8-9 mbs. Does this new update port something speciale for radio?
[Pixel C Android Development] creeperlwd:
What is the difference between stock kernel and tegra kernel? can you get root with tegra kernel?
[Pixel C Android Development] followmsi:
The tegra kernel is based on latest Google sources .. pls find more information in this thread here.

Yes, you can root like stock kernel too.

Just tested v2.79 .. works fine like 2.78 SR5.
[Pixel C Android Development] revengers:
Two questions: 1. How did you replace SR5 with v2.29? 2. Will you be putting v2.79 on the Onedrive>Dragon; I would like to see what it will do for me.

Thanks

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

Never mind, I just saw v2.79 is available on Play Store from Chainfire. Reading makes life easier (sometimes):cool:
[Pixel C Android Development] followmsi:
Yes, I will upload to onedrive as well ..

But here you can find it first ..

http://xdaforums.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703

Or here ..

http://www.supersu.com/download

Use a freshly flashed boot.img and TWRP to install SuperSU.zip.

More information are here in this thread too ..
[Pixel C Android Development] Alxoom33:
It will also automatically update from the Google Play store.
[Pixel C Android Development] Alxoom33:
Can't seem to be able to edit build.prop. It saves as an empty build.prop file. Any ideas on how to successfully edit and save. I've been using Root Explorer pro RW enabled and text editor.
[Pixel C Android Development] followmsi:
Sounds like no space on system parititon anymore ..

Did you install .zip file or .img file ?

The .zip file does also resize (resize2fs) the system partition after flashing .. so we have plenty of space here.

Pls post output of the following 2 commands inside terminal emulator .. or similar app ..

mount

df

Cheers
[Pixel C Android Development] revengers:
FWIW, I use the free version of FX File Explorer System (Root) feature instead. It has worked fine when I need to edit read/write - no problems at all.
[Pixel C Android Development] revengers:
This is my Pixel C's output from df using Material Terminal:

dragon:/ $ su root

dragon:/ # df

Filesystem 1K-blocks Used Available Use% Mounted on

rootfs 1425032 4112 1420920 1% /

tmpfs 1426948 428 1426520 1% /dev

tmpfs 1426948 0 1426948 0% /mnt

/dev/fuse 25396556 6686848 18709708 27% /mnt/runtime/default/emulated

/dev/fuse 25396556 6686848 18709708 27% /mnt/runtime/read/emulated

/dev/fuse 25396556 6686848 18709708 27% /mnt/runtime/write/emulated

/dev/block/mmcblk0p4 3555940 2501740 1054200 71% /system

/dev/block/loop0 92656 3068 89588 4% /system/etc/hosts

/dev/block/mmcblk0p5 112064 111688 376 100% /vendor

/dev/block/mmcblk0p6 396744 6748 389996 2% /cache

/dev/block/dm-0 25396556 6686848 18709708 27% /data

dragon:/ #

...and mount:

dragon:/ $ su root

dragon:/ # mount

rootfs on / type rootfs (ro,seclabel,size=1425032k,nr_inodes=356258)

tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)

devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)

none on /dev/cpuctl type cgroup (rw,relatime,cpu)

none on /dev/cpuset type cgroup (rw,relatime,cpuset,noprefix,release_agent=/sbin/cpuset_release_agent)

adb on /dev/usb-ffs/adb type functionfs (rw,relatime)

proc on /proc type proc (rw,relatime,gid=3009,hidepid=2)

sysfs on /sys type sysfs (rw,seclabel,relatime)

selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)

/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,seclabel,relatime,mode=755)

pstore on /sys/fs/pstore type pstore (rw,seclabel,relatime)

none on /acct type cgroup (rw,relatime,cpuacct)

tmpfs on /mnt type tmpfs (rw,seclabel,relatime,mode=755,gid=1000)

/dev/fuse on /mnt/runtime/default/emulated type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)

/dev/fuse on /mnt/runtime/read/emulated type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)

/dev/fuse on /mnt/runtime/write/emulated type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)

none on /config type configfs (rw,relatime)

/dev/block/mmcblk0p4 on /system type ext4 (ro,seclabel,noatime,data=ordered)

/dev/block/loop0 on /system/etc/hosts type ext4 (rw,seclabel,noatime,data=ordered)

/dev/block/mmcblk0p5 on /vendor type ext4 (ro,seclabel,noatime,data=ordered)

/dev/block/mmcblk0p6 on /cache type ext4 (rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,errors=panic,data=ordered)

tmpfs on /storage type tmpfs (rw,seclabel,relatime,mode=755,gid=1000)

/dev/fuse on /storage/emulated type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)

/dev/block/dm-0 on /data type ext4 (rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,errors=panic,data=ordered)

/dev/block/loop0 on /su type ext4 (rw,seclabel,noatime,data=ordered)
[Pixel C Android Development] followmsi:
You have a lot of space in system left.

You have a Adblocker like AdAway, which is loop mounting (RW) the hosts file.

But your system partiton is still mounted read-only.

The root explorer should manage the RW mounting.

As you don't have the problem, your root explorer seems to work ..

Cheers
[Pixel C Android Development] followmsi:
Your system is 100% full .. make a resize2fs to get the full partition space.

Cheers
[Pixel C Android Development] Alxoom33:
Thanks, but I'm not sure how to do that on this device? Can I resize the Vendor partition, as well.

I am afraid of experimenting blindly on this.

Edit: figured it out, I think...Let's see how this flash System.Vendor.zip goes...
[Pixel C Android Development] followmsi:
Install the system-vendor.Zip and you have resized system.img. :)

I will make a 1MB .Zip for the resizing only .. tomorrow.

You can run the command in terminal emulator .. on mounted /system.

resize2fs /dev/block/platform/700b0600.sdhci/by-name/APP

Check with df afterwards ...

Cheers
[Pixel C Android Development] Alxoom33:
I used resize function in TWRP/Wipe/Advanced. System now at 71% Vendor still at 100%

Thanks

---------- Post added at 09:51 PM ---------- Previous post was at 09:21 PM ----------

Great! I was able to modify build.prop and install custom Nav bar! Awsome. Thanks...

Still wondering why the beta build NPF26H is a more advanced build, it is a later letter, i.e. P is after M, so woulden't it make sense that it is a more advanced build?

It says Pixel XL instead of C due to the edits.
[Pixel C Android Development] followmsi:
You managed with TWRP .. perfect.

As promised yesterday .. here is a small .ZIP file for this purpose. ( 480 KB )

- filesystem check of system and vendort partition

- resize2fs of system and vendor filesystem (to full partition size)

Update.ZIP_PixelC_Ryu_resize2fs_system_vendor.zip

To be installed via TWRP.

Cheers
[Pixel C Android Development] Alxoom33:
Yes, the TWRP Advanced wipe, fix file system made it easy. Thank you for the zip, though.

I take it you flash the zip and then reflash System.Vendor.zip?

Does the zip do anything that the TWRP fix dosn't exept making it easier?

---------- Post added at 10:30 PM ---------- Previous post was at 10:27 PM ----------

BTW, you can now enable Google Assistant without changing the device type to Pixel XL. Only need to add "ro.opa.eligible_device=true" wipe the Google App data and reeboot.
[Pixel C Android Development] followmsi:
The .Zip file here (Update.ZIP_PixelC_Ryu_resize2fs_system_vendor.zip) is supposed for installation AFTER you have applied system.img and vendor.img via fastboot !

After you installed system/vendor via fastboot you can run it to get more free space for other installations inside system partition.

If you install system-vendor.zip file via TWRP there is no need anymore - as the resize has been already done.

And No .. it just makes it easier :)
[Pixel C Android Development] followmsi:
Android 7.1.1 (N4F26I, Jan 2017)

system-vendor:

Update.ZIP_PixelC_Ryu_N4F26I-system-vendor.zip

stock kernel:

Update.ZIP_PixelC_Ryu_N4F26I-kernel-dragon.zip

Seems to be still the same bootloader .. bootloader-dragon-google_smaug.7900.27.0.img

Of course we have a "new" compiled 3.18 tegra kernel as well ..

Update.ZIP_PixelC_Ryu_tegra-3.18_KERNEL_N4F26I_v170103_followmsi.zip

kernel-tegra-3.18_v170103_N4F26I_boot.img

Installation:

1. Reboot into TWRP -> TWRP_dragon_3.0.2-23.img

2. Install Update.ZIP_PixelC_Ryu_N4F26I-system-vendor.zip

3. Install Update.ZIP_PixelC_Ryu_tegra-3.18_KERNEL_N4F26I_v170103_followmsi.zip

4. Install SR1-SuperSU-v2.79-SR1-20161221223537.zip

5. Reboot into system

And again .. due to supersu installation it will boot twice - no panic, it´s normal !

Enjoy ..
[Pixel C Android Development] revengers:
Works like a charm, many thanks again!

---------- Post added at 01:37 PM ---------- Previous post was at 01:35 PM ----------

...and one (stupid) question: Do we need to re-apply the Update.ZIP_PixelC_Ryu_resize2fs_system_vendor.zip ?
[Pixel C Android Development] followmsi:
Depends .. use the resize2fs.zip if you install system.img / vendor.img via fastboot only.

The monthly Update.zip from this thread does include resizing as well.

You can use "df" command to verify your current free space on system partition.

You can re-run the resize2fs.zip all the time .. no problem.
[Pixel C Android Development] revengers:
Thanks!
[Pixel C Android Development] cam30era:
[MENTION=5480152]followmsi[/MENTION],

I'd like to unencrypt, but don't really need TWRP nor root. Would you mind making a fastboot flashable stock boot image with encrytable (rather than force encrypt) kernel?
[Pixel C Android Development] followmsi:
Here you are ...

kernel-tegra-3.18_v170104_N4F26I_encryptable_boot.img

Since Android 7 it´s the "forcefdeorfbe" flag, we need to change it to "encryptable". (fstab.dragon)

I will not do this on regular base - It's an one time boot.img :)

Thanks for understanding ..
[Pixel C Android Development] cam30era:
:o

Thanks, I do appreciate it. Does there exist a kitchen that I can use to modify future kernels?

Thanks, again.

Edit: removed my ignorant comment about the link. :o
[Pixel C Android Development] followmsi:
I was expecting this question .. regarding future kernels. :)

Unfortunately there is no "kitchen" for Pixel C existing.

You need to do it manually ... on linux system.

1. unpack stock boot.img

2. gunzip ramdisk

3. modify fstab.dragon

4. gzip ramdisk

5. repack boot.img

Here on XDA you will find some help ..

For example here ... https://xdaforums.com/pixel-c/help/unpack-repack-boot-img-info-to-build-t3367835

Once you understood the "chromium" part it's the same like "normal" android.

Sorry, but I will not have the time to help you better ..

Good luck !
[Pixel C Android Development] cam30era:
[MENTION=5480152]followmsi[/MENTION],

Thank you very much! :svetius:
[Pixel C Android Development] Alxoom33:
7.1.2 beta program has arrived.
[Pixel C Android Development] followmsi:
Yes .. made some Update.ZIP packages for the BETA ..

Android 7.1.2 BETA (NPG05D):

Update.ZIP_PixelC_Ryu_NPG05D-system-vendor.zip

Update.ZIP_PixelC_Ryu_NPG05D-kernel-dragon.zip

Update.ZIP_PixelC_Ryu_tegra-3.18_KERNEL_NPG05D_v170104_followmsi.zip

kernel-tegra-3.18_v170104_NPG05D_boot.img

The "tegra-3.18" kernel binary is still unchanged from January, 4th.

There is a new bootloader as well .. bootloader-dragon-google_smaug.7900.50.0.img

I did not install the BETA until now .. no experience in terms of SuperSU.

Not much time today .. maybe tomorrow.

Cheers
[Pixel C Android Development] GonzoKSV:
Did anybody test root with followmsis new beta update?
[Pixel C Android Development] Alxoom33:
Yes, working great!
[Pixel C Android Development] followmsi:
Confirmed :)

Just installed the beta update.zip and supersu 2.79 sr3 .. all works fine.
[Pixel C Android Development] Alxoom33:
I like this new build, very smooth and fast! My problem is that I can't copy my overlay file 15 MB's into the vendor file in System. The vendor file is too small, only 110 MB's of which only 379 Kb's free. In my N6 the vendor file is 277 MB's with room to spare. Does anyone know how could I enlarge the vendor file? Thanks.
[Pixel C Android Development] followmsi:
Update.ZIP_PixelC_Ryu_resize2fs_system_vendor.zip

The partition size is approx. 300mb.

dragon:/ $ df

Filesystem 1K-blocks Used Available Use% Mounted on

rootfs 1425024 4172 1420852 1% /

tmpfs 1426952 428 1426524 1% /dev

tmpfs 1426952 0 1426952 0% /mnt

/dev/block/platform/700b0600.sdhci/by-name/APP 3555940 2494328 1045228 71% /system

/dev/block/platform/700b0600.sdhci/by-name/VNR 301596 111776 183596 38% /vendor

/dev/block/platform/700b0600.sdhci/by-name/CAC 396744 420 388132 1% /cache

/dev/block/platform/700b0600.sdhci/by-name/UDA 25396556 10985864 14394308 44% /data

/dev/block/loop0 93680 5352 86364 6% /su

/dev/fuse 25396556 10985864 14394308 44% /storage/emulated

dragon:/ $

After resize script you will have 38% use only.

Cheers

EDIT:

Checked the regular monthly Update.ZIP script .. which was also used for the BETA Update.ZIP.

Until now I have resized the system partition only, but not the vendor partition. :(

The vendor partition will not be resized - unless you install "Update.ZIP_PixelC_Ryu_resize2fs_system_vendor.zip" afterwards.

This will be fixed for the next monthly Update.ZIP packages -> the system and vendor partition will be resized at the same time.
[Pixel C Android Development] Alxoom33:
Thank you! I'll give it a try?

URGENT! PLEASE READ! [MENTION=5480152]followmsi[/MENTION] and fellow users. Just an FYI, yesterday I found Osiris ransomware has been copying all of my files in internal storage. I deleted a lot of files before I realized nearly everything was compromised. It renames your files as .Osiris and then locks them down. I formatted my data in TWRP and restore my data from the Nandroid I made before updating to 7.1.2. Not sure where I got it from, but I suggest that you check your files depositary, just in case. Most of my downloaded files after my last backup were from your One Drive for updating to 7.1.2 although the malware could have come from other sources that I accessed in the late couple of days.

Thanks
[Pixel C Android Development] followmsi:
There is no ransomware in my repository.

Is your computer also affected by Osiris ?

I hope you will find the real source of your ransomware problem soon.

Good luck !
[Pixel C Android Development] Alxoom33:
Thanks, that's great! I just wanted to let you and other users know.

No, neither my phone nor computer appear affected. But I am still checking. I have now installed Norton and Malwarebytes on my devices.

---------- Post added at 01:38 PM ---------- Previous post was at 01:10 PM ----------

I tried reflashing the resize2fs_system_vendor.zip but the vendor file properties still show only 108MB's with 379Kb's available. Not sure if there is something that I might be doing wrong. Have also tried manually resizing the System with TWRP in the Advanced Wipe feature. Same result. Unfortunately, I don't know how to only resize the vendor file.

Thanks
[Pixel C Android Development] followmsi:
Are you talking about the vendor.img file ?

Vendor file properties ?

But you can resize the vendor.img or system.img as well, after convertion to RAW image, like in my Update.zip packages.

Resize the vendor.img to approx. 150 MB, loop mount, copy your stuff into mounted vendor, unmount - done.

You can replace the stock vendor.img inside the Update.zip and flash it via TWRP.

Now you have included your custom vendor.img :)

I was talking about your live vendor partition :)

The resize2fs.zip is just for your current running vendor partition.
[Pixel C Android Development] Alxoom33:
I wish I knew what you are saying...sorry, LOL, I don't know how.

---------- Post added at 06:00 PM ---------- Previous post was at 05:58 PM ----------

Bad news, my computer is infected, as well. Looks like it was from an email attachment. Don't know if my phone is affeced. I don't think so...fingers crossed.
[Pixel C Android Development] GonzoKSV:
Great. Later today I will take a look on. Is it necessary to update the bootloader to bootloader-dragon-google_smaug.7900.50.0.img before I try the new beta? I was searching for a while but I haven't found it without downloading the whole firmware on the nexus page...
[Pixel C Android Development] followmsi:
If you install Update.ZIP_PixelC_Ryu_resize2fs_system_vendor.zip via TWRP you can check your "live" vendor filesystem size with the command "df" afterwards.

Like I did above ..

/dev/block/platform/700b0600.sdhci/by-name/VNR 301596 111776 183596 38% /vendor

As I understood you want to modify a vendor.img before flashing it onto the device ?

If so, you need to follow the steps ..

1. Resize the vendor.img file

2. loop mount

3. copy your stuff into mounted vendor

4. unmount

5. flash via TWRP or repack to sparse image for fastboot installation.

Hopefully you will find and "kill" all the osiris stuff on all your devices.

Good luck !
[Pixel C Android Development] followmsi:
Yes, it`s strongly recommended to use latest available bootloader - bootloader-dragon-google_smaug.7900.50.0.img

installation:

fastboot flash bootloader bootloader-dragon-google_smaug.7900.50.0.img

fastboot reboot-bootloader

Yes, you need to download full factory image to get the bootloader binary.

For convenience I have uploaded the bootloader.img to the onedrive folder as well.
[Pixel C Android Development] GonzoKSV:
Thanks a lot!
[Pixel C Android Development] followmsi:
The monthly security update ... for the non beta users :)

7.1.1 (N4F26O, Feb 2017)

Update.ZIP_PixelC_Ryu_system-vendor_N4F26O.zip

Update.ZIP_PixelC_Ryu_kernel_dragon_N4F26O.zip

Update.ZIP_PixelC_Ryu_kernel_tegra-3.18_v170104_N4F26O_followmsi.zip

PixelC_Ryu_kernel_tegra-3.18_v170104_N4F26O_followmsi_boot.img

The "tegra-3.18" kernel binary is still unchanged from January, 4th.

Installation:

1. Reboot into TWRP -> TWRP_dragon_3.0.2-23.img

2. Install Update.ZIP_PixelC_Ryu_system-vendor_N4F26O.zip

3. Install Update.ZIP_PixelC_Ryu_kernel_tegra-3.18_v170104_N4F26O_followmsi.zip

4. Install SR3-SuperSU-v2.79-SR3-20170114223742.zip

5. Reboot into system

And again .. due to supersu installation it will boot twice - no panic, it´s normal !

Enjoy ..
[Pixel C Android Development] Alxoom33:
Doesn't the new Bootloader get installed when you flash the two zip files that you provided, w/o fastboot?