yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] DespairFactor:
You can always disable verity without wiping, it's just verification that requires a wipe. I have faith that we can avoid requiring a wipe in the future and keeping verification enabled, but until then....

On another note, I pushed a new build 1.04 which focuses on lowering the max panel voltage again. I am trying to see what we can do with this due to all the reports of the panel draining high amounts of power, which I still haven't seen myself.
[Google Pixel 7 Pro] Lughnasadh:
For what it's worth, I had verity and verification disabled from the very beginning with the Pixel 6 Pro and continue to with the Pixel 7 Pro. With it disabled, I never had the red eio corruption error/message (hash mismatch), not even once, even when in similar situations to those that did get it (including flashing kernels), with the only difference being that I had those disabled.

But I hear ya about having to remember. 😬
[Google Pixel 7 Pro] JakeDHS07:
I was using Freak07 kernels on my Pixel 4 XL via what I mentioned before and never disabled verity or verification just flashed with EXKM. I'm hoping his kernels for this device will be as easy. I'll wait as well and see what happens.
[Google Pixel 7 Pro] roirraW "edor" ehT:
My understanding of the current situation must have been still out of sync. I had thought the AK3 Zip of this kernel still required Verity to be disabled, but additionally still required a factory reset to work with the kernel - despite Verity not normally requiring a factory reset. I now take the instructions in the OP at face value that no matter which way is used to flash (AK3 Zip or individual partitions), both Verity and Verification must be disabled.

Please let me know if my latest understanding is accurate. :)

Very cool about you fooling further with the panel voltages. It's fun to see what can be tweaked and gotten away with. That's always been my favorite part about technology - getting it to do things it shouldn't be able to do, even though I'm more like a power user, not a developer at all.

It is interesting, and it is a little tempting, but I'm going to keep banging my hard head against the wall for a while longer. LOL!

Unless Freak07 waits to release a kernel until the AK3 process is refined in a way that doesn't require Verity and Verification disabled, it'll likely be in the exact same boat as this and any other kernels for the Pixel 7/Pro. When the AK3 process was refined on the Pixel 6 Pro, that's when all the custom kernels started to be able to be flashed without disabling anything.
[Google Pixel 7 Pro] Wickidmasshole:
First pixel I've had in quite some time, happy to be back! I have no problem running with verity/verification disabled, in fact I'm pretty sure I ran my nexus 6p disabled the entire time to avoid corruption being a flashaholic.

To my understanding, I download and extract the stock firmware, then CMD in the folder then per OP, run: fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification

This will disable both and erase all my data, correct? Sorry for the n00bish question I just want to be sure before I go getting all flash happy. Thanks in advance!!
[Google Pixel 7 Pro] roirraW "edor" ehT:
It won't erase your data automatically, but when you reboot, it will let you know that your phone is corrupt and needs a factory reset, and prompt you to do that with the volume and/or power buttons, if memory serves correctly.
[Google Pixel 7 Pro] DespairFactor:
pixel 4 xl never had to disable these because it was patched in fstab by magisk
[Google Pixel 7 Pro] JakeDHS07:
And is that no longer possible?
[Google Pixel 7 Pro] DespairFactor:
Magisk has stopped doing this about a year ago, also the fstab is in vendor_boot, not in init_boot, which magisk patches
[Google Pixel 7 Pro] JakeDHS07:
So if the same patch is to be done this time around it will need a different implementation if I'm understanding. It's interesting that Magisk stopped doing that so long as I was successfully rooting and using my Pixel 4 XL with the current Magisk and the kernel up until my P7P arrived and still never disabled either one.
[Google Pixel 7 Pro] DespairFactor:
As capntrips has stated, he needs to look into patching the hash on init_boot
[Google Pixel 7 Pro] JakeDHS07:
Thank you for the info and explanation. I admit despite working with Android since 2010 I'm not well versed with kernels. Most of my flashing and development was helping with roms and troubleshooting. Let me know if there's anything I can do to help. I'm always looking to expand my knowledge.
[Google Pixel 7 Pro] jac0b:
Is AK3 included on the zip in your G drive?
[Google Pixel 7 Pro] DespairFactor:
yep it's just AK3 now
[Google Pixel 7 Pro] capntrips:
I patched vbmeta with the hashes of boot, dtbo, and vendor_kernel_boot, ran Hashtree Patcher on vendor_dlkm and vbmeta, and patched the vbmeta footer in init_boot:

Spoiler content hidden.

I'm not sure how much of that was actually required, since I didn't wipe until the bitter end, but I was able to boot the kernel with verity and verification enabled, but it still required a wipe:

Spoiler content hidden.

I had to mod avbtool to allow it to continue when it encounters a bad signature (updating the hashes breaks the signatures), so I'll try to generate a key and sign vbmeta and init_boot to see if that works without a wipe. Fortunately, I have an old PR from where I enabled AVBv2 signing vbmeta for the modified boot in magiskboot that I can adapt to Hashtree Patcher, so it won't be completely from scratch.
[Google Pixel 7 Pro] Annie the Eagle:
Does this Kernel still need a factory reset?
[Google Pixel 7 Pro] capntrips:
If you don't already have verity and verification disabled, then yes.
[Google Pixel 7 Pro] Nekromantik:
hope you find a way :) thanks for looking into it.
[Google Pixel 7 Pro] cultofluna:
Reboot to fastboot

Fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img

Fastboot -w

Fastboot reboot

Setup phone then..and root
[Google Pixel 7 Pro] capntrips:
To follow up, I signed vbmeta and init_boot with one of the test keys from the avb source:

Spoiler content hidden.

Unfortunately, it still bootloops then asks for a factory reset.

On the upside, the line about init_boot's hash not matching the descriptor is now gone from ramoops.

I'll try to sign the stock vbmeta with the same key to see if that causes the same behavior. I suspect the key changing is triggering it. Maybe flashing a custom avb key would prevent it.
[Google Pixel 7 Pro] capntrips:
I flashed the stock vbmeta signed with the same key and it booted without a wipe. I'm out of ideas. I'll skim through the changelogs for avb and /init, maybe it'll turn up something to blame.
[Google Pixel 7 Pro] Namelesswonder:
I hate AVB I hate AVB I hate AVB I hate AVB I hate AVB I hate AVB.

Spent the last 4 hours trying to get the flag to clear after I tripped it. Annoying me beyond belief, delaying the boot while it checks hashes and pops the message, always catching it right after it times out and shuts down, slowing down my testing. It just wouldn't reset no matter what I did, well other than disabling verity and verification, but then it would be set again after flashing stock. Let it factory reset, still wouldn't clear it. Tried flashing to the other slot, still nope. Wiped it, still nope. I've never had this issue before, it's always gone away with a flash.

Decided might as well return it since I originally wanted 256GB, so ordered another phone. Right after ordering I had the realization that many people had their issues with AVB cleared up after updates, so what about a downgrade?

Flashed 009.A2, let it factory reset, and no eio mode. 😑

Well, I guess I'll keep the new phone, return the old, and forfeit on the preorder bonus credit. I did want more storage.
[Google Pixel 7 Pro] binary**#:
Just to re-confirm, are all these three commands to disable verity checks the same:

fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
[Google Pixel 7 Pro] DespairFactor:
Yeah all three should work the same
[Google Pixel 7 Pro] DespairFactor:
I have rebased the kernel, lowered the voltage a bit more.

Release is 1.06
[Google Pixel 7 Pro] Jiggs82:
Hey whatever happened to the telegram chat Matt? lol and btw this can be flashed through EXKM app correct?

Thanks in advance..
[Google Pixel 7 Pro] DespairFactor:
I would use Kernel Flasher, I think EXKM will need an update to account for the init_boot.

Chat has been closed as there were too many people and it was attracting the wrong kind of attention.
[Google Pixel 7 Pro] Jiggs82:
Yup that worked for me, thanks bro!! and ahh gotcha but its all good :)
[Google Pixel 7 Pro] Golf c:
Ugh!

How's the phone Matthew?
[Google Pixel 7 Pro] DespairFactor:
It's basically a small upgrade over the 6 pro in every way
[Google Pixel 7 Pro] Golf c:
Hahaha. I noticed. I like it. Gave my 6pro to my girlfriend.

Not a big upgrade at all. But it's what I do.
[Google Pixel 7 Pro] zetsumeikuro:
The kernel flashed just fine through EXKM and even Franco (which is dated).
[Google Pixel 7 Pro] Rogue8o8:
Any comments on battery life with the kernel, like 100 to 50% screen on time?
[Google Pixel 7 Pro] zetsumeikuro:
Battery life is always subjective to personal usage. Flash it yourself and find out.
[Google Pixel 7 Pro] Rogue8o8:
You could simply say something in relation to coming from stock kernel and how it compares. I'm still waiting on my Pixel. With no local retailer I have to import it to my country. My preorder from Google was cancelled just like the 6 pro before without warning and I had to get it from an eBay seller.
[Google Pixel 7 Pro] rav101:
Just a heads up that I've used EXKM on this 7Pro although for a different kernel. It did work perfectly so I think it should be fine for Despair Kernel too 👍🏽
[Google Pixel 7 Pro] _Amaterasu_:
Does Flashing custom Kernel void warranty? Accubattery Shows a voltage of 4.287mV isnt that super high on Stock Kernel?
[Google Pixel 7 Pro] DespairFactor:
Yeah, I tried, it works fine now. It was an issue with how AnyKernel was flashing it at the time
[Google Pixel 7 Pro] rav101:
If you unlock your bootloader I think you have technically voided your warranty. Having said that, you can relock and set back to complete stock without any trace (IE unlike on Samsung where it tracks if you have ever unlocked bootloader) so it's a non-issue for warranty purposes as long as you can factory reset your phone and relock bootloader.
[Google Pixel 7 Pro] Lughnasadh:
No

Unlocking the bootloader doesn't void your warranty, In fact, Google provides instructions on how to do this on their download page.

Also, the Magnuson-Moss Warranty Act of 1975 may play a role in preventing companies from voiding your warranty when unlocking your bootloader and rooting.
[Google Pixel 7 Pro] flar2:
Hey now, EXKM is not dated, it's had like ten updates this year

Anyway, I've made the flasher tool in a way that can handle almost anything. Usually only the AK3 zip needs to be updated for new devices
[Google Pixel 7 Pro] xflowy:
how is battery life and temperature compared to the 6p? :)
[Google Pixel 7 Pro] Golf c:
Both are improved for me. That being said, it feels to me, like it's basically the the same phone with small improvements.
[Google Pixel 7 Pro] DespairFactor:
It's definitely better, basically the 6 pro was the prototype and the 7 pro was the real release
[Google Pixel 7 Pro] _Amaterasu_:
Is Root needed for a Custom Kernel?
[Google Pixel 7 Pro] roirraW "edor" ehT:
Only an unlocked bootloader, and follow the rest of the installation instructions from the first post.
[Google Pixel 7 Pro] swieder711:
I just bought EXKM in preparation for flashing this kernel. I already have Franco KM. Seems like EXKM is more up to date.

I am going to wait for the November update. I am prepared to wipe my device, if a work around to disabling verification is not available by than.
[Google Pixel 7 Pro] zetsumeikuro:
Whoops! My bad I just read my post again and I redact that statement. For some reason I ended up double quoting DespairFactor and I edited it it clearly state that Franco was dated (not EXKM) and deleted the wrong one. I went back and fixed it!
[Google Pixel 7 Pro] _Amaterasu_:
I did, what tool is needed for installing the custom kernel without Root?
[Google Pixel 7 Pro] flar2:
No worries, I'm just joking around. EXKM will live on as long as it needs to, even though I'm probably not making kernels for any new devices.
[Google Pixel 7 Pro] zetsumeikuro:
Lol, it definitely went over my head this time! I do miss your kernel. Used it exclusively on my Nexus devices and some of my Pixels.
[Google Pixel 7 Pro] roirraW "edor" ehT:
fastboot aka Platform-Tools
[Google Pixel 7 Pro] _Amaterasu_:
Working now, but where do I get the vbmeta.img from?

Need it for the first command "fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification"
[Google Pixel 7 Pro] roirraW "edor" ehT:
The Pixel factory image which matches your firmware version.

Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developers.google.com
[Google Pixel 7 Pro] JakeDHS07:
That can be found inside one of the official zips. Either the OTA or factory ones from Google. You have to unzip the initial download and then the image zip within that.
[Google Pixel 7 Pro] _Amaterasu_:
Working until the command : "fastboot flash vendor_kernel_boot vendor__kernel_boot.img"

fastboot: error: cannot load 'vendor__kernel_boot.img': No such file or directory

any ideas?

But it is in my folder
[Google Pixel 7 Pro] RogerF81:
What are the changes in 1.07 and 1.08?
[Google Pixel 7 Pro] capntrips:
There's an extra underscore in vendor__kernel_boot.img in the OP, so you can't do a straight copy and paste.
[Google Pixel 7 Pro] zoman7663:
Maybe try "fastboot flash vendor_kernel_boot.img"
[Google Pixel 7 Pro] roirraW "edor" ehT:
Yep, always copy and paste the filename from your folder.
[Google Pixel 7 Pro] lassetth:
C:\Users\hp>fastboot flash vendor_dlkm C:\Users\hp\Desktop\vendor_dlkm.img

target reported max download size of 261095424 bytes

sending 'vendor_dlkm_b' (35424 KB)...

OKAY [ 0.321s]

writing 'vendor_dlkm_b'...

FAILED (remote: failed to flash partition (vendor_dlkm_b))

finished. total time: 0.347s

Any help?
[Google Pixel 7 Pro] Lughnasadh:
Make sure you are in fastbootd instead of fastboot, if you aren't.
[Google Pixel 7 Pro] lassetth:
Ok, thanks, how to come to fastbootd? I found out "fastboot reboot fastboot", I tried but get message "faild........
[Google Pixel 7 Pro] roirraW "edor" ehT:
That's where you have to be in order to flash vendor_dlkm.

Moving Fastboot to Userspace | Android Open Source Project

source.android.com
[Google Pixel 7 Pro] Lughnasadh:
You can't flash that particular image in fastboot. That's the only one that needs to be flashed in fastbootd.

fastboot reboot fastboot

EDIT: Nanja'd by The Rode Warrior once again 😅
[Google Pixel 7 Pro] _Amaterasu_:
Okay worked fine. After u did it once, u can just install the updates of despair kernel without wiping data correct?
[Google Pixel 7 Pro] lassetth:
This is what I get "unknown reboot target fastboot"
[Google Pixel 7 Pro] roirraW "edor" ehT:
As long as you keep Verity and Verification disabled any time you flash an update to the phone's firmware (such as every month). The factory image zip's flash-all.bat, for example, is to flash vbmeta without any switches - which

enables

Verity and Verification. Any time you re-disable them from them previously having been enabled requires a wipe.

Verity alone doesn't require a wipe, you can disable and enable all you like, although right now the custom kernel won't work with Verity enabled, so there's no point now that you're on it. Disabling Verification does require a wipe, so if you let it get enabled again, and you disable it after, you'll have to wipe again.

Edit: Until/unless the AK3 method is perfected for the Pixel 7/Pro so that disabling Verity and Verification is no longer required - then, it's completely your option, but still - if you re-disable Verification later, you'll still have to wipe again.
[Google Pixel 7 Pro] roirraW "edor" ehT:
I'd suggest flashing all the partitions referenced in the OP back to stock (but still keep vbmeta's Verity and Verification disabled) and try again from the beginning.
[Google Pixel 7 Pro] lassetth:
Ok, thanks for helping.

After flashing vbmeta's Verity and Verification disabled I have reset the phone "fastboot -w"?
[Google Pixel 7 Pro] Agenesis:
Only the vbmeta thing requires a wipe right? fresh installs of this kernel doesn't require a factory reset?
[Google Pixel 7 Pro] lassetth:
I flashed the system img. booted up, flashed vbmeta thing, erased sytem, booted up. So now flashing the kernel. Ok?

Can flash via Franco KM first time I flash the kernel if I root??
[Google Pixel 7 Pro] simplepinoi177:
I'm pretty inexperienced with kernels and verity & verification, so please be gentle...

But, as I understand it, in order to apply this kernel, one would have to wipe one's device (at least applying it for the first time)? I've only ever applied Flash kernel and Caesium kernel back on my Pixel 2 XL which was very simple and straightforward to apply; we just used TWRP. A simpler time we didn't have to worry about verity & verification, I guess.

I know it states that verity & verification needs to be disabled, and those who are experienced and familiar with what that entails should automatically know that that entails wiping the device, but for those who might new at applying (this) kernels and/or trying to find a way to start their knowledge on the matter, if @DespairFactor could include that warning and caveat in the OPs on the subject, so it's clear and blatant to any of those/us that that's what will be required....that would be (y)

Thanks!
[Google Pixel 7 Pro] craigacgomez:
I think it's pretty clear in the "Disclaimer" section in the OP which clearly mentions that a wipe is needed after disabling verity and verification.
[Google Pixel 7 Pro] roirraW "edor" ehT:
No roughness intended. :)

As @craigacgomez said:
[Google Pixel 7 Pro] _Amaterasu_:
Where is the difference between 1.08 and 1.06?
[Google Pixel 7 Pro] roirraW "edor" ehT:
You're welcome!

I haven't wiped it that way, so I have no idea if fastboot will wipe with that switch when it's not flashing anything. I seem to recall that on the Pixel 6 Pro, the phone will prompt you to factory reset when it notices that it's corrupted due to the disabling of Verification.
[Google Pixel 7 Pro] roirraW "edor" ehT:
GitHub - DespairFactor/pantah

Contribute to DespairFactor/pantah development by creating an account on GitHub.

github.com
[Google Pixel 7 Pro] _Amaterasu_:
Last Time updated 5 days ago, I guess. 1.06 was "lowered a Voltage a bit more".
[Google Pixel 7 Pro] lassetth:
Can flash the kernel via Franco KM first time I flash after I root (flashed vbmeta thing and wiped)? Or must I the first time flash the kernel follow the steps in OP?
[Google Pixel 7 Pro] cultofluna:
If you've verity/ verification disabled , you can install the kernel for the first time via EX, Franco or kernel flasher app, without any issue
[Google Pixel 7 Pro] lassetth:
Ok, very good (verity/ verification disabled)! Thanks! Installed with no problem.
[Google Pixel 7 Pro] DespairFactor:
Yeah sorry I haven't pushed source yet for the new builds, I haven't had time yet and likely won't until next week.
[Google Pixel 7 Pro] _Amaterasu_:
What did you changed in 1.08 versus 1.06? If I want the undervolt changes u did in 1.06 I am fine, if I use the 1.08 version right?
[Google Pixel 7 Pro] DespairFactor:
Yes sir, those have stayed:)
[Google Pixel 7 Pro] Agenesis:
I changed the governor to schedutil and now my device doesn't overheat anymore. What a night and day difference.
[Google Pixel 7 Pro] SeanHacker:
Yes they/he/she/it/that/the (you get it hopefully) could've said something coming from stock. But again, battery life is so subjective considering everything that comes into play in terms of that. Location, settings, apps, runtime, numbers of calls, number of texts, face unlock vs fingerprint, incoming/outgoing emails, they don't live in your home... This list can go on and on forever. You're basically asking about the meaning of life dude. It's a question that only those that can't understand will ask. Hope you find peace in whatever you choose. 😘
[Google Pixel 7 Pro] RogerF81:
That's strange - I'm using the stock sched_pixel, and my thermals are much better than they have been on the Pixel 6 Pro, no matter if I'm on stock kernel or on Despair.
[Google Pixel 7 Pro] t0m2k:
what about scrolling/ui performance? anything different?
[Google Pixel 7 Pro] Agenesis:
The little (1.8ghz) and medium cores (2.3ghz) gets locked to their max speed during media playback with the default kernel. I tried to disable the x1 cores to reduce heat but that made the fp reader stop working. schedutil allowed the device to downclock during media playback.

From my testing the little cluster is responsible for ui responsiveness and the big cluster is responsible for media. The x1 cores aren't used at all for media playback.

No difference.
[Google Pixel 7 Pro] Paz9:
Is this actually happening to other people too?
[Google Pixel 7 Pro] Lughnasadh:
Not for me. During media playback on stock kernel using Poweramp for media and EXKM to determine frequencies, my frequencies for the little and middle cores are not locked at 1.8 GHz and 2.3 GHz respectively. In fact, the little cores fluctuate from the lowest to highest frequencies and the middle cores hit the lowest frequencies but don't even seem to hit the highest frequency (2.3 GHz).
[Google Pixel 7 Pro] Agenesis:
Can you try twitch?
[Google Pixel 7 Pro] Lughnasadh:
About 10 1/2 minutes on Twitch. Several notifications came in during this time which may have skewed the numbers a bit.
[Google Pixel 7 Pro] Agenesis:
Yeah looks exactly like my results. Are your cores toasty too? Anything above 55c the left side of the phone starts heating up.

Tunein radio does this too with the news playing. The phone is visibly warm if I let the app play overnight. My main concern is unnecessary battery drain. Heat = energy loss obviously.
[Google Pixel 7 Pro] Tracker31:
1.09 released. Is there any changelog?

Is the right folder is "pantah"?

Can I flash it just on ex Kernel manager Luke normal Kernel??
[Google Pixel 7 Pro] Lughnasadh:
So your little and middle cores don't get locked at their maximum frequency as you originally said? Temps below. Not heating as much as yours. Ambient temperature is 68 degrees F.

Apologies to M for the somewhat off topic posts...
[Google Pixel 7 Pro] swieder711:
Git hub for changelog

and you have to disable-verification on vbmeta before flashing.
[Google Pixel 7 Pro] Tracker31:
Thanks, I am already rooted and disabled not wanted options. Just considering pantah is right folder and if apps like ex kernel are ready for new init settings.
[Google Pixel 7 Pro] zoman7663:
Yes, "pantah" is correct folder (for 7 and 7 Pro, so Dev combined the names of both devices). EX flashes kernel fine. Been using myself.
[Google Pixel 7 Pro] Tracker31:
Thanks for your help. Just flashed 1.09 with ex kernel and it's working great and stable. Thanks for your work on it. Really appreciate
[Google Pixel 7 Pro] Jiggs82:
Any chance of making a kernel for qpr beta 3?😁
[Google Pixel 7 Pro] xstefen:
They only released prebuilt modules afaik, not buildable src
[Google Pixel 7 Pro] RogerF81:
V1.10 didnt' boot for me for some reason. I don't have logs, though, unfortunately.
[Google Pixel 7 Pro] DespairFactor:
Meant for QPR, I thought it may work on both, I have moved it to its own folder
[Google Pixel 7 Pro] xstefen:
Did you start with the kernel/manifest repos or just pull kernel/common. If from manifest, what bazel build command actually works?
[Google Pixel 7 Pro] DespairFactor:
Bazel doesn't work, you need to use the legacy command
[Google Pixel 7 Pro] xstefen:
I did get further with build.sh for sure, bazel fails immediately, gg with their new instructions. I miss monolithic kernels :(

thx m8