yashsingh1/xdaforums huggingface dataset:
[Google Pixel ROMs, Kernels, Recoveries, & Other De] sanogueralorenzo:
Hello thanks for the reply but that didn't work. Basically I relocked and couldn't boot into the system to go to dev options and enable unlock bootloader.

Only solution I found was to use ./fastboot continue so it booted into the system and I was able to enable that option again.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] crossen0:
I had tried that but still didn't work
[Google Pixel ROMs, Kernels, Recoveries, & Other De] franciscofranco:
These devices aren't bricked unless the bootloader is destroyed. There's always a way out of ****.

Look, I don't know what you're doing. This works, period. Rooting the Pixels is finnicky, as well as flashing a custom recovery since it involves changing a lot of different things. Following instructions is enough to get it all working on its first try. I only rooted the Pixels once, and it was ****-free. Read the instructions and everything worked just fine. Kept flashing new Kernels on top of it and re-rooted just fine on top of the new Kernel releases.

If things go haywire just start over on top of fresh Android installation. You don't even need to wipe anything, just flash the system images on top of everything and you get a pristine installation. There's nothing we can do here for you or anyone else. It's a simple process and everything is written in the respective threads on how to do it.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] kinesics:
i get the following error

it sends the command ok and then it gives me

(bootloader) Flashing active slot "b"

FAILED (remote: partition [fk-r6.gz] doesn't exist

Im using fastboot flash fk-r6.gz fk-r6.gz as my command
[Google Pixel ROMs, Kernels, Recoveries, & Other De] joetheshmo:
Use fastboot flash kernel fk-r6.gz

You got that error because the syntax for this command is fastboot flash <partition> <file>

Specifying fk-r6.gz as the partition threw the error because it doesn't know that partition (and rightfully so)

Hope this helps!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] franciscofranco:
In the OP:

fastboot flash kernel fk-r6.gz
[Google Pixel ROMs, Kernels, Recoveries, & Other De] qwer777:
Correct me if I'm wrong, but this hasn't been released yet has it?

Not asking for a release date or anything, just making sure I didn't miss a post with it.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] joetheshmo:
You're correct
[Google Pixel ROMs, Kernels, Recoveries, & Other De] blaze9090:
Will there be flashable zips?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] joetheshmo:
Soon
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Turbojugend:
Don't really use custom kernels too much, but decided to try this one out. Am on rooted 7.1.1, sent me into a boot loop. Was in fastboot and used fastboot flash kernel fk-r6.gz and it said it worked, so I don't know what went wrong. Oh well.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] franciscofranco:
Can be many things. Things are still pretty finnicky with root/custom Kernels/custom recoveries (I'll assume you're rooted and flashed TWRP).
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Turbojugend:
Yep. Figured it was something funky. I am going to stick with stock rooted until things start coming around. Keep up the good work!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] ssglackey:
I have 0C temperature reading in the notification bar, anybody else?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] shinesthru:
Should the safety net patch disable the modified bootloader message? Or is that unrelated?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] joetheshmo:
Unrelated
[Google Pixel ROMs, Kernels, Recoveries, & Other De] kingmikel:
Hey [MENTION=3292224]franciscofranco[/MENTION] good to see you giving the Pixels some love! I just got my pixel and this is the first thing I'm going to flash! Which of the two Pixels did you pick up?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] shinesthru:
I love when this forum is quiet. It just means the product is rock solid and there's nothing to discuss. Props, [MENTION=3292224]franciscofranco[/MENTION].
[Google Pixel ROMs, Kernels, Recoveries, & Other De] jrtomsic:
Speaking of solid, I'm getting upwards of 7.5 hours screen time with r6, with 10% to spare. In r2 I got just under 6 hours at 4% remaining. That's pretty damn solid.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] ssglackey:
Anyone has 0C CPU temperature reading in the notification bar when the service is enabled in the FKU settings?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] herandy:
I'm mostly getting 4-5 hours. Did you change anything?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] jrtomsic:
I have the FKUpdater app, and I've set the quick-setting tile to power saving mode. Not sure what that does in the system but that's basically the only thing I've tweaked. I don't play many games, and I don't have any awful battery-suck apps like facebook installed. Mostly camera and Reddit.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] milan187:
I just hope next release bring flashable zips as it's a bit of a pain to flash with PC everytime. I play a lot, lol.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] shinesthru:
This has more to do with a stable recovery than the kernel.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] phishfi:
Coming from Franco kernels for the Galaxy Nexus, Nexus 5, and Nexus 6, I couldn't even wait until my battery was fully charged before installing this kernel.

Thank you, Franco, for an amazing experience. Already have your pro app installed and waiting for it to stay automatically updating!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] milan187:
I think RC1 is pretty stable now. Either way. As long as I got the kernel I guess.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] bonzai299:
Having loved your kernel for the Galaxy Nexus, I'm beyond excited that you're dipping into the Pixel goodness. Not sure if I ever said it back then, but thanks for all of the hard work you've put/are putting into these.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] pahlerc1:
wanna give this a go but currently have RC1 and SuperSU 2.79 installed w elementalX.. do I just use fastboot to flash franco kernel, then use fastboot to temp boot TWRP, flash TWRP zip, then flash SuperSU? thanks

Update: tried fastboot flashing over my setup; stuck in bootloop to TWRP.. tried flashing SuperSU, didn't work. tried flashing stock boot.img via fastboot.. didn't work... not sure what happened but fastboot flashed stock google image and just gonna wait it out till Jan image is released
[Google Pixel ROMs, Kernels, Recoveries, & Other De] jduenes:
What the heck guys I get like 3-4 with not heavy usage. Just some browsing some Snapchat and texting!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] quangtran1:
That behavior is expected. A kernel image resides in the boot image. You overwrote that slot's boot image when you flashed the kernel. The proper order here is: stock boot image, kernel, then TWRP, then SU.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] pahlerc1:
cool thanks for the reply. just finished getting twrp, root, and everything set back up and finished.. just gonna stay where I am at now until new image comes out for january. happy new years
[Google Pixel ROMs, Kernels, Recoveries, & Other De] quangtran1:
Same to you.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] iPwn_:
[MENTION=3292224]franciscofranco[/MENTION] whatever the audio changes in this kernel are make the headphone output quite a bit louder than the stock kernel by default.

That's pretty problematic for a lot of in-ear headphone owners, since it reduces the useful volume control range to just the first 2 out of the 15 steps, especially if they don't have root to preserve SafetyNet and can't try to counteract it with negative analog output gain values in FKU.

On the stock kernel, the first 4 or 5 volume steps are all tolerable on IEMs.

By default on r6, volume at 2/15 is too soft and 3/15 is pain-causing levels of loud.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] グリッチ:
I like this kernel, will you update the kernel to support the January security patches?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] kinesics:
You can use December's kernel while he updates.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] deniros:
I have just got the phone, and I'm happy to see I'm reunited with Franco and his kernal.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] ssglackey:
My pixel can connect to wireless display (how to enable cast http://graesen.com/2015/03/how-i-got-wireless-display-miracast-to-work-on-my-nexus-6/) receiver, however no picture is being transferred and after a while connection is terminated. With N5 or N7 2013 I have no issue. I am not sure if this is kernel related or not.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] mrZoSo:
But will it run properly and/or be safe, on a system that already has the January update?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] kinesics:
Yes I'm running like that right now no issues. Just don't have the Jan kernel updates.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] mrZoSo:
Good deal, thanks kinesics! Going to flash it now and get FKU2.1

Always ran Franco Kernels in the past. Been away from Nexus/Pixel phones too long, did a Windows phone for a bit , then an S6,,, never again though! LOL

---------- Post added at 02:14 PM ---------- Previous post was at 01:46 PM ----------

Rut Roh! FKU2.1 doesn't work with r6 running Jan. update.

No biggie though, I can wait until Franco updates it.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] kinesics:
It works just not on the pixel. He's waiting on TWRP to be 100%
[Google Pixel ROMs, Kernels, Recoveries, & Other De] mrZoSo:
I knew the updater part wouldn't work, thought I couldn't get in to the other areas of the app too, but I figured it out.

Just been doing too many things at once ,, lol
[Google Pixel ROMs, Kernels, Recoveries, & Other De] milan187:
Any updates for Jan security?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] mrZoSo:
Last I heard, Franco hasn't updated it yet, as he is working on the recovery flashable zip.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] kinesics:
Is it safe to say we might just get a February update?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] jrtomsic:
Don't expect anything. It's safe to say he'll post it when it's ready.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] trizzv:
How do I flash this kernel if I'm coming from ElementalX?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] joetheshmo:
Same as coming from stock afaik since you are using fastboot flash kernel command.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] trizzv:
Do I flash the purenexus ROM again and then TWRP and then flash this kernel? How do I fastboot?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] robotnikz:
When do we get a new version? [emoji13] is it currently usable for 7.1.1 January update?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] trizzv:
Everytime i try flashing i get this error message

C:\Users\---\Documents\FASTBOOT KERNEL FRANCO\platform-tools>fastboot flash kernel fk-r6

target reported max download size of 536870912 bytes

sending 'kernel' (24168 KB)...

OKAY [ 0.639s]

writing 'kernel'...

(bootloader) flash size too large

FAILED (remote: flash failed)

finished. total time: 0.810s
[Google Pixel ROMs, Kernels, Recoveries, & Other De] mrZoSo:
Try this:

adb reboot bootloader

fastboot flash kernel fk-r6.gz
[Google Pixel ROMs, Kernels, Recoveries, & Other De] milan187:
It's too bad there is no updates or response from Franco. He is usually good at that.

Going to try other kernels now.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] danaff37:
Did you unzip the kernel? Or double click it And then copy it to your folder?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] trizzv:
Thanks but mrsozo was right just needed to add ".gz" at the end.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] mrZoSo:
Yes, been running it with no issues.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] hectorcde:
Someone who already tried this kernel, does it improve battery life?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] trizzv:
Yes. I used to get 4-5 hrs on stock now I average 6 hrs with the same usage as before.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] jrtomsic:
Yes, noticeably.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] hectorcde:
what rom are you using with it?stock with root or custom?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] jrtomsic:
Stock, rooted. 7 hours screen time isn't uncommon. Currently at 6 with 20% battery left.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] mngdew:
I followed the flash instruction in the OP, but mine boot loops to the recovery.

What am I doing wrong?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] mngdew:
So I found my own solution. It was the TWRP-RC1 causing the boot loop issue.

I was able to boot the system correctly when I flashed franco kernel after flashing back to the stock recovery.

I temporarily boot the TWRP recovery and reflashed the SuperSU to re-enable the root.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] rknee:
I was reading comments around the internet that the January update may have broken previous safetynet patch. Will getting r7 be relatively easy with new patch?

Sorry previous comment was posted prior to looking at r6 release date

Also tried looking at the changelog but getting the 'not found' message

Root checker indicating

Safetynet request =success

Response signature validation= fail (Response payload validation fail)

NMF26U,r6,TWRP,supersu
[Google Pixel ROMs, Kernels, Recoveries, & Other De] trizzv:
Has anyone adjusted kernel settings including CPU gov/screen/GPU/I/O Schedulers and seen better battery results?

If so what were the changes
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Taebom:
Stock Franco settings work best for me
[Google Pixel ROMs, Kernels, Recoveries, & Other De] PsiPhiDan:
I'm on PureNexus with EX kernel. I'd love to try this one. I've gathered from this thread that I need to flash the stock boot.img first. Where does one find that?

Then I should fastboot flash the kernel, reflash TWRP (why?) and then SuperSU?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] joetheshmo:
The stock boot.img can be found in the factory image from Google. You need to flash TWRP and SuperSU after because they both reside in the boot.img and since you essentially just wiped them out with the stock boot.img they need to be replaced.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] PsiPhiDan:
Don't kill me for asking but where does one find this? Google didn't help and neither did searching this forum. I would think it would be a common download that's easy to find on XDA?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] joetheshmo:
http://bfy.tw/9m0l
[Google Pixel ROMs, Kernels, Recoveries, & Other De] PsiPhiDan:
I Googled "Google Pixel Stock Boot.img" and found nothing. I love a good LMGTFY, but it's not like I didn't look. Apparently that's not what I'm supposed to be Googling. But seriously, why wouldn't these links be on their own XDA thread? Seems odd. They usually are in my previous phone experiences.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] joetheshmo:
Because these devices are owned by Google and Google puts out the full images for every device. You can find certain users that host the stock boot.img on their AFH but I don't know any off the top of my head.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Golf c:
https://developers.google.com/android/images
[Google Pixel ROMs, Kernels, Recoveries, & Other De] PsiPhiDan:
Downloading the factory image zip now. So do u extract the zip, find a file called boot.img, then use adb reboot bootloader command and then flash it from there?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] joetheshmo:
Yep you got it! :good:
[Google Pixel ROMs, Kernels, Recoveries, & Other De] PsiPhiDan:
Last question: can I rename this long bootloader file name? I'm assuming it's irrelevant? It's currently called bootloader - sailfish 8996 blah blah blah.img

Can I just rename it boot.img like people always refer to it as?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] joetheshmo:
Bootloader and boot.img are different files
[Google Pixel ROMs, Kernels, Recoveries, & Other De] PsiPhiDan:
This is what I got when I unzipped the factory image from Google. I don't see any boot.img file. Am I overlooking something??
[Google Pixel ROMs, Kernels, Recoveries, & Other De] maflin18:
Yes. Unzip the compressed folder inside of the original zip. It's in there.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] joetheshmo:
Open the image zip inside of that zip

Edit: woops sorry I'm late to answer.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] kingmikel:
Try this

https://xdaforums.com/pixel/how-to/stock-kernel-boot-img-t3547513
[Google Pixel ROMs, Kernels, Recoveries, & Other De] PsiPhiDan:
Great idea, thank you! I did extract it myself but that will be very helpful to others in my shoes.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] franciscofranco:
Pushed r7, includes all the latest security patches + full merge of a newer branch from Google called EAS-experimental which contains a lot of patches for the scheduler & backports from upstream. Also added support to bypass two wlan wakelocks some of you complain about (present on stock rom/Kernel), and added support for USB fast charge (when charging through your computer for example).

Still having some issues with AK2 support, so this way is still cleaner and ****-free for everyone.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] trizzv:
If I have fk-r6, do I need to flash the stock or can I just go ahead and fastboot this r7? Thanks
[Google Pixel ROMs, Kernels, Recoveries, & Other De] TonikJDK:
I just flashed straight to r7. Seems perfectly fine.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] franciscofranco:
Just fastboot.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] TonikJDK:
Much appreciated sir, all good here except I am still missing HBM. I will figure that out someday I am sure, probably need to flash back to stock and start over. Sent you and the cat some food. Thank it for me, it's QC is the best.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] franciscofranco:
Thanks. Can you run this command for me and show me the output (just right after you try to access HBM):

adb shell dmesg | grep denied

Maybe it's a SELinux denial or something. That thing is finnicky.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] trizzv:
Does schedutil help battery life?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] TonikJDK:
It's not even there to access.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] kinesics:
Thank you franco!! I thought we became your forgotten child lol
[Google Pixel ROMs, Kernels, Recoveries, & Other De] franciscofranco:
Exactly. Now run the command I gave you after accessing that page.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] franciscofranco:
It's a governor from upstream, I don't know much about it, should be pretty simple just taking hints from the scheduler, but I don't know if it's ready to use daily. Asking if it's gives better battery life or not is just a very simple and stupid way to put things into perspective when there's so much work involved, and with different goals I'm sure. Try it if you want to, but don't expect me to give much input about it since I don't it that well.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] TonikJDK:
Regarding where the HBM option isn't in the app. Here is a full file that has a handful of denies on Franco just after I started it. It didn't like the grep so it is the full output.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] trizzv:
LOL.

If ur purpose is to create a kernel that improves battery life/performance, how is it a simple and stupid way lol.

It's like if you work at a pizzeria and u made a new topping and I asked if it tasted good and u said it's a stupid and simple way to put things in perspective
[Google Pixel ROMs, Kernels, Recoveries, & Other De] bbender716:
I don't think he meant any offense just was being honest that he hadn't had a chance to test and have definitive results. I think Franco has earned more than the benefit of the doubt around here.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] mngdew:
Why am I having such a hard time flashing kernels? Everytime I flash a kernel, my device boot loops. The only way to make things work is flash the factory image. Only after then, flashing kernel doesn't trigger boot loop.

Can someone explain this issue I'm having?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] joetheshmo:
What command are you using to flash kernels? What SDK is your fastboot environment?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] schaggo:
Feel somewhat dumb for asking this, but... it's all a bit different to the previus Nexus procedure!

SuperSU still lives in the ramdisk, so after flashing the kernel, it will be gone and must be reflashed. Right?

This cannot be flashed online with FlashFire yet, offline fastboot flashing it is the current way to go. Supposedly same applies to fastbooted TWRP image. Right?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] TonikJDK:
Correct.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] schaggo:
Uh-ooh...

- Finding boot image
--- Boot image: /dev/block/sda19
- Extracting ramdisk
--- Failure, aborting

Anyone else sharing the same when trying to flash SuperSU 2.79 SR3 from fastboot booted twrp RC1? It worked with fk r6, which I was running until just now.

Edit: ok, doesn't work anymore on r6. I'll see what I can find out and will update here.

Edit: this is getting weirder and weirder and I'm getting more and more confused!

C:\sailfish>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot_a' (24821 KB)...
OKAY [ 0.596s]
writing 'boot_a'...
OKAY [ 0.297s]
finished. total time: 0.892s

C:\sailfish>fastboot flash boot_a fk-r7.gz
target reported max download size of 536870912 bytes
sending 'boot_a' (19140 KB)...
OKAY [ 0.456s]
writing 'boot_a'...
FAILED ([B][COLOR="red"]remote: image is not valid[/COLOR][/B])
finished. total time: 0.550s

So I can root and boot on stock kernel/boot, but the latest fastboot binary doesn't accept the gzipped package with "image is not valid". An older fastboot version does accept the package, but the device bootloops. Same on r6 which I had running before. What's happening here?

Nvm. Retard is being retarded. Read below for solution.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] GIKE:
It's safe to flash this kernel with flashify?

If not, will wait to flash it with fastboot at home.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] milan187:
No, can't.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] franciscofranco:
Yeah there's a bunch of denials. I really need to get the AK2 game together. My attemps were painful and I ran into either bootloops or the contents of the ramdisk weren't being copied over etc. But I need it to address the denials.

I didn't include that governor, Google did, I just merged their branch. I just don't know much about it specially since there's way more into it than just "battery" or "performance".

In the OP the command is right there: fastboot flash kernel kernel_binary

fastboot only.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] TonikJDK:
So that is how I do it.

Fastboot boot TWRP then install SU. Last night I had trouble at first. Couldn't get root. So I double checked my SU zip and it had a different name than the one on Chainfire website. Both said SR3 but were different.

Downloaded it again and it worked fine the first try.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] schaggo:
Godd**n fu**in automatisms. Working now. Prolly gonna buy FKU right away after that as a thanks although I use EXKM. Geez... :mad: