Development [KERNEL] CleanSlate T1.4.9 |S2S|AdBlock|VIB|BatterySvr [Jun 17]

Development [KERNEL] CleanSlate T1.4.9 |S2S|AdBlock|VIB|BatterySvr [Jun 17] - Google Pixel 7 Pro

tbalden's
CleanSlate kernel
for Google Pixel 7 Pro/7
The User Experience Kernel leaning towards Stock Stability plus UX features.
Rock stable stock approach, performance smooth and issue free
"No-Root is a State of Mind"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As always tbalden is here to bring you authentic new features first in line, to his heart's chosen phone, this year Pixel 7 Pro.
No root elevation (magisk) needed for all functions and preference switches through CS Config App

Release Calendar
Version 1.4.9 - 17 of June 2023
Version 1.4.4 - 10 of Jan 2023
Version 1.4.3 - 7 of Dec 2022
Version 1.4.2 - 20 of November 2022
Version 1.4.0 - 24 of October 2022
Should work on official ROM bases Jan 2022 sec level.
Special thanks
To @Freak07 for all his work on XDA and help
To @osm0sis , @capntrips for AnyKernel
To @Captain_Throwback
Features:
- Sweep to Sleep gestures - highly customizable
- DoubleTap & LongTap & SwipeUp on corner area gestures - new way to pull down android Notification Area or screen off
- Sweep/Tap gesture to force close foreground app - DETAILS HERE
- Battery Saver cut back max CPU freqs, 3 levels + touch boost limiter options
- Flashlight Notification/Call blinking (see video below)
- Vibrating Notification Reminder (DETAILS)
- Notification In-Pocket Booster boost notifications vibrations while phone is in pocket
- Vibration Booster boost haptic feedback strength (closer to Pixel4/Pixel3 levels)
- K.AdAway adblocking built-in kernel only, All browsers, Apps web-ads, except YouTube / streaming / Facebook ads
- SafetyNet pass - BASIC passes Basic, without Magisk/Rooting. CTS won't pass.
- ThinLTO + CFI security hardened Read: https://source.android.com/devices/tech/debug/cfi
- Kernel Log / Crash dump to internal storage/sdcard - no root/magisk needed, from Companion App use Kernel Log button
- VoLTE call properties patched in - no root/magisk needed for non supported carriers/countries and VoLTE calls.
- CleanSlate Companion / Config - rootless app to configure
Facts:
- no root required, use /sdcard/Android/data/org.cleanslate.csconfig/cache/uci_user.cfg file to configure 99% of the features without rooting. If you need tweak apps (e.g. EXKM / FK) you'll need rooting!
- built on top of kernel sources released by Google
- built with standard toolchain for stability and efficiency
- built with Control Flow Integrity sec hardening from Android S versions onwards
- kept stable, no tweakings, just features
- stable and reliable, keeping close to stock except addition of Usability features
Feature demo
Sweep2Sleep, DoubleTap notif pull down
--
Flashlight notification
--
Foreground App Kill gesture
Requirements
- Unlocked Pixel 7 Pro, stock or with magisk root and DISABLED VERITY
- Verity must be disabled from fastboot (when disabling it requires a data wipe!)
- From then, upon EACH manually sideloaded/installed system update, after applying but BEFORE booting system you MUST disable the verity from fastboot RIGHT AFTER THE UPDATE , or you'll need a wipe again!
- BACKUP: make sure you have a stock image downloaded (boot, dtbo, vendor dlkm img) from Google (https://developers.google.com/android/images) before installing this!
Installation Guide
Firstly install CleanSlate configuration and CleanSlate companion BETA program apps on your phone (both found down below in Download section). Set them up initially.
- When installing Premium version from Play Store, you should join the Beta program for both apps, and install the beta version! Otherwise features won't work.
- Non-rooted method: 0. download the installation zip, Unzip it to your PC.
Code:
0. if you didn't or just flashed an OTA: DISABLE VERITY, using a stock vbmeta.img (extracted from your device's ota zip):
0.1 in fastboot mode (adb reboot-bootloader), disable by flashing with the flags like this:
$ fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
0.2 if you do this disable step when it is yet enabled, then you'll also need a user data wipe:
$ fastboot -w
1. Flashing stuff: reboot to bootloader (if not already there):
$ adb reboot-bootloader
2. Flash boot image and dtbo img:
$ fastboot flash boot cleanslate-pantah-boot-xxxxxx.yyy--ZZZ.img
$ fastboot flash dtbo cleanslate-pantah-dtbo-xxxxxx.yyy--ZZZ.img
$ fastboot flash vendor_kernel_boot cleanslate-pantah-vendor-kernel-boot-xxxxxx.yyy--ZZZ.img
4. if everything went fine, reboot to FastbootD and flash vendor_dlkm modules image:
$ fastboot reboot fastboot
$ fastboot flash vendor_dlkm cleanslate-pantah-vendor_dlkm-xxxxxx.yyy--ZZZ.img
5. reboot (fastboot reboot), enjoy
- Kernel Manager (Kernel Flasher/FKM/EXKM) Rooted method (after disabling verity!):
- download the kernel manager AnyKernel installer zip instead and flash from the manager
Known bugs
- None, please tell
- please disable magisk modules before reporting issues, and please provide logs if possible
- if it cannot boot at all after flash because of signature verification, read vbmeta requirements (Android S)
Download
Android T
Non rooted, Android T images
Pixel7pro/7 (Cheetah/Panther) Images zip (DO NOT FLASH AS ZIP) for Android13 (2023.06.05)
CS 1.4.9: https://forum.xda-developers.com/attachments/cleanslate-pantah-images-230605-012-149-zip.5934323/
P7Pro/P7 Rooted installer for Kernel Manager installation (Kernel Flasher, EXKM/FKM...)
cleanslate-pantah-1.4.9.zip for P7pro and P7 CHEETAH/PANTHER (Jan update): https://forum.xda-developers.com/attachments/cleanslate-pantah-1-4-9-zip.5934321/
Pixel7pro/7 (Cheetah/Panther) Images zip (DO NOT FLASH AS ZIP) for Android13 (2023.01.05)
CS 1.4.4: https://forum.xda-developers.com/attachments/cleanslate-pantah-images-230105-002-144-zip.5806625/
P7Pro/P7 Rooted installer for Kernel Manager installation (Kernel Flasher, EXKM/FKM...)
cleanslate-pantah-1.4.4.zip for P7pro and P7 CHEETAH/PANTHER (Jan update): https://forum.xda-developers.com/attachments/cleanslate-pantah-1-4-4-zip.5806627/
Pixel7pro/7 (Cheetah/Panther) Images zip (DO NOT FLASH AS ZIP) for Android13 (2022.12.05)
CS 1.4.3: https://forum.xda-developers.com/attachments/cleanslate-pantah-images-221205-011-143-zip.5779343/
P7Pro/P7 Rooted installer for Kernel Manager installation (Kernel Flasher, EXKM/FKM...)
cleanslate-pantah-1.4.3.zip for P7pro and P7 CHEETAH/PANTHER (Dec update): https://forum.xda-developers.com/attachments/cleanslate-pantah-1-4-3-zip.5779345/
CS 1.4.2: https://forum.xda-developers.com/attachments/cleanslate-pantah-images-221105-001-142-zip.5766009/
[/B]
cleanslate-pantah-1.4.2.zip for P7pro and P7 CHEETAH/PANTHER (Nov update): https://forum.xda-developers.com/attachments/cleanslate-pantah-1-4-2-zip.5766007/
P7Pro/P7 Rooted installer for Kernel Manager installation (Kernel Flasher, EXKM/FKM...)
cleanslate-pantah-1.4.0.zip for P7pro and P7 CHEETAH/PANTHER (August update): https://forum.xda-developers.com/attachments/cleanslate-pantah-1-4-0v2-zip.5747767/
Non rooted, Android T images
Pixel7pro/7 (Cheetah/Panther) Images zip (DO NOT FLASH AS ZIP) for Android13 (2022.08.04)
CS 1.4.0: https://www.androidfilehost.com/?fid=14871746926876840163
[/B]
Config Applications
Companion App 3.3.x-- Donation premium on PlayStore
--- MUST Use BETA program for this phone:
https://play.google.com/store/apps/details?id=org.cleanslate.csservice[/B]
Configuration App 3.2.x -- Donation premium on playstore
--- MUST Use BETA program for this phone:
- additional features in premium app: App Themes, Profiles, Profile Switch QuickTiles
https://play.google.com/store/apps/details?id=org.cleanslate.csconfig
Companion App 3.3.10 -- Normal free download:
https://www.androidfilehost.com/?fid=14871746926876839886
Configuration App 3.2.12 -- Normal free download:
https://www.androidfilehost.com/?fid=14871746926876839887[/B]
Alternative download links on XDA: https://forum.xda-developers.com/t/...k-vib-batterysvr-oct-24.4509793/post-87642075
Donation:
If you appreciate this, don't forget to hit the Like button, or consider to Donate. Donations here
Thank you!
Donators Hall of Fame
Much appreciation and many thanks go to...
@velimirchek
@MarcoG:
@guidogsbn
@The Great Dane
@Whiskey103
@purple patch
@panosmdma
@sttw1fa
@jelive
@beartiger
@st_voss
@bigruss
@deagleone
@DroidIt!
@8bitbang
@Will972
@smallKING81
@mick_soul
@p50kombi
@K4Y3
@ dieter
@michaelbsheldon
@dioooi
@ali nz
@bstiti
@Oddvin94
@norgan
@lol8888
@twinnfamous
@cameljockey1
@Cryptycat7
@Pasqui1978
@4ntagonist
@turbo jjjang
@munkyvirus
@knopie
Src: https://github.com/tbalden/android_kernel_gs_raviole/tree/pantah-c-t
https://github.com/tbalden/google-modules-sec_touch/tree/pantah-c-t
https://github.com/tbalden/google-modules-synaptics_touch/tree/pantah-c-t
https://github.com/tbalden/google-modules-amplifiers/tree/pantah-c-t
https://github.com/tbalden/google-modules-lwis/tree/pantah-c-t
https://github.com/tbalden/google-modules-bcm4389/tree/pantah-c-t
Sharing policy:
As this is all GPL licensed kernel source, you can use it in your code, but don't forget about proper credit.

Changelogs and such for later use..

nice to see you here It´s been a pleasure as always

I <3 u
hehehehehe

Kcal would be nice. A lot of piss yellow screens out there.

It won't flash and now it's obvious, this is based of August update. Do you have a kernel for the October Google update?
Definitely excited to flash this!
And thank you for you helping the community and making these phones the way we like them to run…!

jgrimberg1979 said:
It won't flash and now it's obvious, this is based of August update. Do you have a kernel for the October Google update?
Definitely excited to flash this!
And thank you for you helping the community and making these phones the way we like them to run…!
Click to expand...
Click to collapse
All the firmware for the Pixel 7 so far are dated August - that has no correlation with what security update is on the phone:
VersionFlashDownloadSHA-256 Checksum13.0.0 (TD1A.220804.009.A2, Oct 2022)FlashLink8e7393e1bd7f86d76d75cdea988d5e4ebfded3a50fac26d774b9eb07152c1ed513.0.0 (TD1A.220804.009.A5, Oct 2022, JP carriers)FlashLinkc68659bdd1d2b0b9a1740daa1502acbbf1b535be5b7e5bada157c82ef5fbf5c513.0.0 (TD1A.220804.031, Oct 2022)FlashLink6152f6f3d8437be0ef840ed7056f15d0f52ba181a1d029ff84bd9d83c860d49f

roirraW edor ehT said:
All the firmware for the Pixel 7 so far are dated August - that has no correlation with what security update is on the phone:
VersionFlashDownloadSHA-256 Checksum13.0.0 (TD1A.220804.009.A2, Oct 2022)FlashLink8e7393e1bd7f86d76d75cdea988d5e4ebfded3a50fac26d774b9eb07152c1ed513.0.0 (TD1A.220804.009.A5, Oct 2022, JP carriers)FlashLinkc68659bdd1d2b0b9a1740daa1502acbbf1b535be5b7e5bada157c82ef5fbf5c513.0.0 (TD1A.220804.031, Oct 2022)FlashLink6152f6f3d8437be0ef840ed7056f15d0f52ba181a1d029ff84bd9d83c860d49f
Click to expand...
Click to collapse
OK not completely understanding but I appreciate the response. I see October and every kernel except despair won't flash. See the error. Is there a way for fixing this?
Thanks

jgrimberg1979 said:
OK not completely understanding but I appreciate the response. I see October and every kernel except despair won't flash. See the error. Is there a way for fixing this?
Thanks
Click to expand...
Click to collapse
Update your phone to the latest firmware.
If you already did your either running a module or something else changed the security patch state.
There's a check in the kernel.zip that checks for security patch state to be October 2022, which is the state of the latest firmware.
Despair kernel.zip simply lacks that check.
To circumvent the issue otherwise unzip the kernel.zip, locate anykernel.sh, locate the line that starts with "supported.patchlevels", delete the date after the "=" or adjust to your actual security patch state and rezip the kernel.zip.
But I'd rather update to latest firmware or troubleshoot why the security patch on your phone is off.

Nice to see this kernel here. I used to run this kernel on all of my HTCs... I wasn't planning to unlock the bootloader but maybe I have a reason now...
That disabling verity after every OTA thing sounds like a real pain though. Google just has to make everything so complicated, don't they? :/

EtherealRemnant said:
Nice to see this kernel here. I used to run this kernel on all of my HTCs... I wasn't planning to unlock the bootloader but maybe I have a reason now...
That disabling verity after every OTA thing sounds like a real pain though. Google just has to make everything so complicated, don't they? :/
Click to expand...
Click to collapse
hey
It´s actually not really complicated to keep verity/verification disabled once you get the hang of it. It´s just one more step/command during the monthly update routine. Or ticking a checkbox in the web kernel flasher.
If you haven´t unlocked bootloader yet, unlocking bootloader requires a wipe and you can combine that with the wipe required for disabling verity/verification flags.

Freak07 said:
hey
It´s actually not really complicated to keep verity/verification disabled once you get the hang of it. It´s just one more step/command during the monthly update routine. Or ticking a checkbox in the web kernel flasher.
If you haven´t unlocked bootloader yet, unlocking bootloader requires a wipe and you can combine that with the wipe required for disabling verity/verification flags.
Click to expand...
Click to collapse
Yeah it's not the worst thing imaginable but it's just another thing I didn't have to deal with on my OnePlus 9 along with the init_boot change is all. I have kind of been enjoying the whole having all my apps and features work without having to mess around with SafetyNet stuff so I'll have to think about it. I'm honestly quite happy with this phone stock, something I can't say for any other recent phone I have had.

EtherealRemnant said:
Yeah it's not the worst thing imaginable but it's just another thing I didn't have to deal with on my OnePlus 9 along with the init_boot change is all. I have kind of been enjoying the whole having all my apps and features work without having to mess around with SafetyNet stuff so I'll have to think about it. I'm honestly quite happy with this phone stock, something I can't say for any other recent phone I have had.
Click to expand...
Click to collapse
yes I agree. google put out some great phones with the p6pro and the p7pro.

Thanks for the kernel.
I´m on 13 Beta (QPR) Pixel 7 Pro and hopefully you are planning to realease CleanSlate kernel also for this version!?

DISABLE VERITY. That will be clean data? And we must to do that after any stock update?

krkhaha said:
DISABLE VERITY. That will be clean data? And we must to do that after any stock update?
Click to expand...
Click to collapse
Disabling verity and verification will cause you to wipe your phone if you are doing it for the first time. For updating, you must do it during the update process. The key is to not let your phone boot up with the stock, unmodified vbmeta.img or verity and verification will be enabled again. So disable these flags while you are updating. There are many ways to go about this, The easiest may be to update via Android Flash Tool, which has checkboxes to disable verity and verification. Pixel Flasher is another easy way.

Does the P7 already have all Wireguard kernel modules? Coming from a Pixel 4XL, pickup up my 7 this week and very hyped my favorite Kernel is back, awesome!
If Wireguard is still needed, any plans to integrate it in this version of the Kernel as well? (Using Cleanslate as daily driver because of WG support and the stuff like notification blinks etc.)

quorn23 said:
Does the P7 already have all Wireguard kernel modules? Coming from a Pixel 4XL, pickup up my 7 this week and very hyped my favorite Kernel is back, awesome!
If Wireguard is still needed, any plans to integrate it in this version of the Kernel as well? (Using Cleanslate as daily driver because of WG support and the stuff like notification blinks etc.)
Click to expand...
Click to collapse
For what it's worth,
Wireguard does get built-in by default with the Pixel 7. However, users are reporting that when using the Wireguard app it's reporting "userspace backend" rather than "kernel backend" as it should. Some adjustments may need to be made in the kernel if the app is reporting correctly.

Freak07 said:
Update your phone to the latest firmware.
If you already did your either running a module or something else changed the security patch state.
There's a check in the kernel.zip that checks for security patch state to be October 2022, which is the state of the latest firmware.
Despair kernel.zip simply lacks that check.
To circumvent the issue otherwise unzip the kernel.zip, locate anykernel.sh, locate the line that starts with "supported.patchlevels", delete the date after the "=" or adjust to your actual security patch state and rezip the kernel.zip.
But I'd rather update to latest firmware or troubleshoot why the security patch on your phone is off.
Click to expand...
Click to collapse
Great feedback! I am with you on doing it the right way but I don't do a full update not Ota and had Google flasher flash all partitions and disabled both verifications. What am I doing wrong?

jgrimberg1979 said:
Great feedback! I am with you on doing it the right way but I don't do a full update not Ota and had Google flasher flash all partitions and disabled both verifications. What am I doing wrong?
Click to expand...
Click to collapse
Can you share the output of the following commands?
Code:
adb shell getprop ro.build.id
adb shell getprop ro.build.version.security_patch

Related

[KERNEL] CleanSlate 🚀 R 2.6.9 |KCal|Dimmer|AdBlock|SafetyNet|FlashLight|Dtap [9 Apr]

tbalden's
CleanSlate kernel
for OnePlus 8
The User Experience Kernel leaning towards Stock Stability plus UX features.
Rock stable stock approach, performance smooth and issue free
"No-Root is a State of Mind"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
tbalden is here to bring you authentic new features first in line, this year OnePlus 8.
No root elevation (magisk) needed for all functions and preference switches through CS Config App

Release Calendar
Version 2.6.9 - 8 of Apr 2022
Version 2.6.3 - 31 of Jan 2021
Version 2.6.1 - 6 of Dec 2020
Version 2.6.0 - 22 of Nov 2020
Version 2.5.1 - 2 of Nov 2020
Version 2.5.0 - 25 of Oct 2020
Version 2.4.2 - 24 of Oct 2020
Version 1.2.6 - 20 of Sep 2020
Version 1.2.5 - 7 of Aug 2020
Version 1.2.3 - 10 of July 2020
Version 1.2.2 - 2 of July 2020
Version 1.2.0 - 8 of June 2020
Version 1.1.2 - 1 of June 2020
Version 1.1.1 - 22 of May 2020
Version 1.0.1 - 16 of May 2020
Version 1.0.0 beta4 - 12 of May 2020
Version 1.0.0 beta1 - 10 of May 2020
Version 1.0.0 alpha - 8 of May, 2020
Should work on official ROM base 11.0.x, 10.5.9-10.5.10
Features:
- Flashlight Notification/Call blinking (see video below)
- AdrenoBoost v2.2 - boost GPU for gaming
- Dynamic Schedtune Boost (EAS boosting) - credits to @joshuous
- Optimizations, compiled with Clang 10.0.1
- Vibrating Notification Reminder (DETAILS)
- Vibration power control / Notification booster In-Pocket
- Battery Saver - 3 levels with Touch limiting to cut back max freqs (Gestures & Extras / Advanced mode)
- K.AdAway adblocking All browsers, Apps, except YouTube / streaming
- Unlock Hider - SafetyNetPass kernel side hiding, no magisk needed (use boot image flash) - Android11 only
- Sweep to Sleep gestures - highly customizable
- DoubleTap & LongTap on corner area gestures - new way to pull down android Notification Area or screen off
- Sweep/Tap gesture to force close foreground app - DETAILS HERE
- Backlight Dimmer - possibility to use lower panel brightness (switch DC dimming off in Lab settings!)
- KCAL Color Control (credit to @savoca)
- WireGuard VPN kernel support
- Face down screen off - put phone face down to turn screen off
- Kernel Log / Crash dump to internal storage/sdcard - no root/magisk needed, from Companion App use Kernel Log button
- CleanSlate Companion / Config - rootless app to configure
Facts:
- no root required, use /sdcard/uci_user.cfg file to configure 99% of the features without rooting. If you need tweak apps (e.g. EXKM / FK) you'll need rooting!
- built on top of kernel sources released by Google
- built with standard toolchain for stability and efficiency
- kept stable, no tweakings, just features
- stable and reliable, keeping close to stock except addition of Usability features
Feature demo
DoubleTap notif pull down
Flashlight notification
--
Foreground App Kill gesture
Requirements
- Unlocked OnePlus 8 Pro, stock or with magisk root
- BACKUP: make sure you have a stock image downloaded (boot img) from OnePlus before installing this!
Installation Guide
Firstly install CleanSlate configuration and CleanSlate companion apps on your phone (both found down below in Download section). Set them up initially.
Copy unzipped hosts_k file to your sdcard (/sdcard/hosts_k) for k.adaway functionality in Chrome browser
- Non-rooted method: 0. download the non-rooted boot img
1. reboot to bootloader (adb reboot-bootloader)
2. temporary boot cleanslate_x.y.z_stock_20xx-xx-xx.img (fastboot boot cleanslate.......img)
3. if everything went fine, you can reboot to bootloader and flash the image: fastboot flash boot cleanslate.......img
4. reboot, enjoy
- Rooted method: 0. download the installer zip
1. install magisk and a capable kernel manager like EXKM/FrancoKernel
2. flash the cleanslate installer zip from the kernel manager
3. reboot, enjoy
Known bugs
- None, please tell
Download
Android 11
Installer zip
For Kernel Managers (EXKM,Franco etc)
Installer flashable 2.6.9 https://www.androidfilehost.com/?fid=14655340768118451133
OOS GLO 11.O.5 boot images
CleanSlate 2.6.9 non-rooted https://www.androidfilehost.com/?fid=14655340768118451132
Android 10
Installer zip
For Kernel Managers (EXKM,Franco etc)
Installer flashable 1.2.6: https://www.androidfilehost.com/?fid=8889791610682941427
If your Fingerprint hw is newer/doesn't work on custom kernels ---> installer flashable 1.2.7: https://www.androidfilehost.com/?fid=8889791610682949537
OOS EU 10.5.10 boot images
CleanSlate 1.2.6 non-rooted https://www.androidfilehost.com/?fid=8889791610682941426
Installer flashable 2.6.3 https://www.androidfilehost.com/?fid=17248734326145725766
OOS GLO 11.O.5 boot images
CleanSlate 2.6.3 non-rooted https://www.androidfilehost.com/?fid=17248734326145725768
Installer flashable 2.6.1 https://www.androidfilehost.com/?fid=10763459528675598573
OOS GLO 11.O.5 boot images
CleanSlate 2.6.1 non-rooted https://www.androidfilehost.com/?fid=10763459528675598574
Installer flashable 2.6.0 https://www.androidfilehost.com/?fid=10763459528675589036
OOS GLO 11.O.5 boot images
CleanSlate 2.6.0 non-rooted https://www.androidfilehost.com/?fid=10763459528675589035
Installer flashable 2.5.1 https://www.androidfilehost.com/?fid=10763459528675576264
OOS GLO 11.O.5 boot images
CleanSlate 2.5.1 non-rooted https://www.androidfilehost.com/?fid=10763459528675576267
Installer flashable 2.5.0 https://www.androidfilehost.com/?fid=10763459528675571430
OOS GLO 11.O.5 boot images
CleanSlate 2.5.0 non-rooted https://www.androidfilehost.com/?fid=10763459528675571429
Installer flashable 2.4.2 https://www.androidfilehost.com/?fid=10763459528675570860
OOS GLO 11.O.5 boot images
CleanSlate 2.4.2 non-rooted https://www.androidfilehost.com/?fid=10763459528675570861
Installer flashable 2.4.0 https://www.androidfilehost.com/?fid=10763459528675569819
OOS GLO 11.O.5 boot images
CleanSlate 2.4.0 non-rooted https://www.androidfilehost.com/?fid=10763459528675569820
Installer flashable 1.2.5: https://www.androidfilehost.com/?fid=8889791610682908254
OOS EU 10.5.10 boot images
CleanSlate 1.2.5 non-rooted https://www.androidfilehost.com/?fid=8889791610682908255
Installer flashable 1.2.3v2: https://www.androidfilehost.com/?fid=8889791610682890158
OOS EU 10.5.10 boot images
CleanSlate 1.2.3v2 non-rooted https://www.androidfilehost.com/?fid=8889791610682890159
Installer flashable 1.2.2: https://www.androidfilehost.com/?fid=8889791610682883255
OOS EU 10.5.9 boot images
CleanSlate 1.2.2 non-rooted https://www.androidfilehost.com/?fid=8889791610682883256
Installer flashable 1.2.0: https://www.androidfilehost.com/?fid=12420606652095398761
CleanSlate 1.2.0 non-rooted https://www.androidfilehost.com/?fid=12420606652095398762
Installer flashable 1.1.2v1 https://www.androidfilehost.com/?fid=4349826312261826723
Android OOS 10.5.8 boot images
CleanSlate 1.1.2 non-rooted https://www.androidfilehost.com/?fid=4349826312261823587
Magisk (stable) version 1.1.2 https://www.androidfilehost.com/?fid=4349826312261823588
Installer flashable 1.1.2 https://www.androidfilehost.com/?fid=4349826312261823586
Installer flashable 1.1.1 https://www.androidfilehost.com/?fid=4349826312261815973
Android OOS 10.5.8 boot images
CleanSlate 1.1.1 non-rooted https://www.androidfilehost.com/?fid=4349826312261815968
Magisk (stable) version 1.1.1 https://www.androidfilehost.com/?fid=4349826312261815969
Installer zip for Kernel Managers (EXKM,Franco etc)
Installer flashable 1.0.2 https://www.androidfilehost.com/?fid=4349826312261812201
Android OOS 10.5.8 boot images
CleanSlate 1.0.2 non-rooted https://www.androidfilehost.com/?fid=4349826312261812203
Magisk (stable) version 1.0.2 https://www.androidfilehost.com/?fid=4349826312261812202
Installer flashable 1.0.1 https://www.androidfilehost.com/?fid=4349826312261811591
Android OOS 10.5.8 boot images
CleanSlate 1.0.1 non-rooted https://www.androidfilehost.com/?fid=4349826312261811593
Magisk version 1.0.1 https://www.androidfilehost.com/?fid=4349826312261811592
Installer zip for Kernel Managers (EXKM,Franco etc)
Installer flashable 1.0.0 beta4: https://www.androidfilehost.com/?fid=4349826312261806461
Config Applications
Companion App 3.2.3 -- Donation premium on PlayStore:
https://play.google.com/store/apps/details?id=org.cleanslate.csservice
Configuration App 3.1.1 -- Donation premium on playstore:
- additional features in premium app: App Themes, Profiles, Profile Switch QuickTiles
https://play.google.com/store/apps/details?id=org.cleanslate.csconfig
Companion App 3.2.3 -- Normal free download:
https://www.androidfilehost.com/?fid=10763459528675588614
Configuration App 3.1.1 -- Normal free download:
https://www.androidfilehost.com/?fid=10763459528675587849
Donation:
If you appreciate this, don't forget to hit the Thanks button, Vote 5 stars on Thread, or consider to Donate. Donations here
Thank you!
Donators Hall of Fame
Much appreciation and many thanks go to...
@velimirchek
@MarcoG:
@guidogsbn
@The Great Dane
@Whiskey103
@purple patch
@panosmdma
@sttw1fa
@jelive
@beartiger
@st_voss
@bigruss
@deagleone
@DroidIt!
@8bitbang
@Will972
@smallKING81
@mick_soul
@p50kombi
@K4Y3
@ dieter
@michaelbsheldon
@dioooi
@ali nz
@bstiti
@Oddvin94
@norgan
@lol8888
@twinnfamous
@cameljockey1
@Cryptycat7
@Pasqui1978
@4ntagonist
@turbo jjjang
@munkyvirus
@knopie
Src: https://github.com/tbalden/android_kernel_oneplus_sm8250/commits/cleanslate
Special thanks to AnyKernel installer developer: osm0sis
To @flar2 for his original works
To @Freak07 for all his work on XDA and help
To @Captain_Throwback
Sharing policy:
As this is all GPL licensed kernel source, you can use it in your code, but don't forget about proper credit.
XDA:DevDB Information
CleanSlate Kernel for OnePlus 8, Kernel for the OnePlus 8
Contributors
tbalden
Source Code: https://github.com/tbalden/android_kernel_oneplus_sm8250
Kernel Special Features:
Version Information
Status: Beta
Current Stable Version: 2.6.0
Stable Release Date: 2020-11-22
Created 2020-05-10
Last Updated 2020-11-22

Reserved

Readmes Howtos

What the no root needed, I'm impressed. Will try this today many thanks....

- Update 1.0.0 Beta 2 -
Changes
- Added Notification Vibration based detection for Flashlight Notif/Notif Reminder features
--- Some notifications are not possible to be detected in the companion app, but this will do the detection on kernel side, when vibration mode is active on the phone
- Perf optimization patches (thanks to Freak07, flar2 and kristofpetho on this one)
Code:
msm: kgsl: run kgsl-workqueue as a high prio wq
kgsl: Increase priority of RT thread
PM: devfreq: Use high priority workqueue
msm: vidc: disable debug logs
msm: msm_bus: Kill transaction logging functionality
msm: kgsl: Turn debugfs off
msm_bus: remove tracer
drm/msm/sde: Omit debug logging code
drivers: msm: Don't copy fence names by default
staging: binder - Set binder_debug_mask=0 to suppress logging
selinux: Remove audit dependency
(cleanslate) ntf: vib: add notification detection to RTP call
CleanSlate 1.0.0 Beta2 Downloads:
Installer zip for Kernel Managers (EXKM,Franco etc)
Installer flashable 1.0.0 beta2: https://www.androidfilehost.com/?fid=4349826312261804973
Android OOS 10.5.6 global boot images
CleanSlate 1.0.0 beta2 non-rooted https://www.androidfilehost.com/?fid=4349826312261804972
Magisk version 1.0.0 beta2 https://www.androidfilehost.com/?fid=4349826312261804974
Companion App 2.6.9 -- Donation premium version from PlayStore here:
https://play.google.com/store/apps/details?id=org.cleanslate.csservice
Configuration App 2.12.5 -- Donation premium on playstore:
https://play.google.com/store/apps/details?id=org.cleanslate.csconfig[/size]
Companion App 2.6.9 -- Normal free download: https://www.androidfilehost.com/?fid=4349826312261804490
Configuration App 2.12.5 -- Normal free download: https://www.androidfilehost.com/?fid=4349826312261804489
Read first post in thread for installation details.

marvi0 said:
What the no root needed, I'm impressed. Will try this today many thanks....
Click to expand...
Click to collapse
Thanks for the feedback. I hope it will work out well!

- Update 1.0.0 Beta 3 -
Changes
- Add: Vibration Power set (haptics)
--- Control the Vibration power of haptics, vibrations
- Add: Notification Booster in Pocket
--- Notification type vibrations boosted when phone screen's is off and proximity sensor is covered (e.g. in your
pocket)
- New config app version for the new settings
- Build: use clang-10.0.1 from now on
- Fix: Possible fix for KAdAway feature for Chrome ad blocking
- NEW FEATURE IS NOT TESTED (I HAVE NO DEVICE), PLEASE REPORT YOUR FINDINGS, Attach DMESG if errors
CleanSlate 1.0.0 Beta3 Downloads:
Installer zip for Kernel Managers (EXKM,Franco etc)
Installer flashable 1.0.0 beta3: https://www.androidfilehost.com/?fid=4349826312261805632
Android OOS 10.5.6 global boot images
CleanSlate 1.0.0 beta3 non-rooted https://www.androidfilehost.com/?fid=4349826312261805631
Magisk version 1.0.0 beta3 https://www.androidfilehost.com/?fid=4349826312261805633
Cleanslate Configuration App 2.12.6 Free version Download
https://www.androidfilehost.com/?fid=4349826312261805614
Read first post in thread for installation details.

@scott.hart.bti
KAdaway might be fixed in this beta3
Also additional features need testing for Vibration power setting (dampening / strengthening possibility)
And additional In pocket notification vib boosting too

tbalden said:
@scott.hart.bti
KAdaway might be fixed in this beta3
Also additional features need testing for Vibration power setting (dampening / strengthening possibility)
And additional In pocket notification vib boosting too
Click to expand...
Click to collapse
Nice. You've been busy! . Vibration control doesn't seem to be working. I pulled a log. When you turn on the vibration control and test the vibration, it returns an odd vibrate feeling and even if you set the level to 0, it does not change the intensity of the weird vibrate. It's hard to describe. It's not a solid crisp vibrate .. instead it's like something is loose and rattling around type vibrate. Ad blocker doesn't seem to be working. Tested with the same website you mentioned before.

scott.hart.bti said:
Nice. You've been busy! . Vibration control doesn't seem to be working. I pulled a log. When you turn on the vibration control and test the vibration, it returns an odd vibrate feeling and even if you set the level to 0, it does not change the intensity of the weird vibrate. It's hard to describe. It's not a solid crisp vibrate .. instead it's like something is loose and rattling around type vibrate. Ad blocker doesn't seem to be working. Tested with the same website you mentioned before.
Click to expand...
Click to collapse
Thanks so much for testing. I'll check the log.
I guess this isn't going to be too easy without the device. The patch is based on patches for the op7 devices, so might be that it is totally useless as it is.
Sent from my Pixel 4 XL using Tapatalk

scott.hart.bti said:
Nice. You've been busy! . Vibration control doesn't seem to be working. I pulled a log. When you turn on the vibration control and test the vibration, it returns an odd vibrate feeling and even if you set the level to 0, it does not change the intensity of the weird vibrate. It's hard to describe. It's not a solid crisp vibrate .. instead it's like something is loose and rattling around type vibrate. Ad blocker doesn't seem to be working. Tested with the same website you mentioned before.
Click to expand...
Click to collapse
OK, found an issue with the vibration percentage parameter read, got it from another wrong setting name, and so it was constantly high (~70%). Will correct that, add also some more logs, and also found another issue with vibration detection for "In pocket" boosting... probably actually getting the vibration power stronger than stock won't really work (it will only rattle on high settings, like it did on op7pro), but at least setting it lower for haptics and non-in-pocket vibrations can be done, and leave a stronger vibration power for in-pocket notifications...
I'll bake a new beta right now and post it here....

tbalden said:
OK, found an issue with the vibration percentage parameter read, got it from another wrong setting name, and so it was constantly high (~70%). Will correct that, add also some more logs, and also found another issue with vibration detection for "In pocket" boosting... probably actually getting the vibration power stronger than stock won't really work (it will only rattle on high settings, like it did on op7pro), but at least setting it lower for haptics and non-in-pocket vibrations can be done, and leave a stronger vibration power for in-pocket notifications...
I'll bake a new beta right now and post it here....
Click to expand...
Click to collapse
@scott.hart.bti
Here are beta4 installer and boot imgs, more logs and fix for the percentage issue:
Installer zip 1.0.0 beta4 https://www.androidfilehost.com/?fid=4349826312261806343
boot img non rooted: https://www.androidfilehost.com/?fid=4349826312261806342
magisk boot img: https://www.androidfilehost.com/?fid=4349826312261806344

tbalden said:
@scott.hart.bti
KAdaway might be fixed in this beta3
Also additional features need testing for Vibration power setting (dampening / strengthening possibility)
And additional In pocket notification vib boosting too
Click to expand...
Click to collapse
tbalden said:
@scott.hart.bti
Here are beta4 installer and boot imgs, more logs and fix for the percentage issue:
Installer zip 1.0.0 beta4 https://www.androidfilehost.com/?fid=4349826312261806343
boot img non rooted: https://www.androidfilehost.com/?fid=4349826312261806342
magisk boot img: https://www.androidfilehost.com/?fid=4349826312261806344
Click to expand...
Click to collapse
Perfect. It is now working, however as you mentioned if it is set too high it'll have the awful rattle vibrate effect. Not sure if anything can be changed, but I went through the levels and anything above 40 causes the effect. 40 and below are safe.

scott.hart.bti said:
Perfect. It is now working, however as you mentioned if it is set too high it'll have the awful rattle vibrate effect. Not sure if anything can be changed, but I went through the levels and anything above 40 causes the effect. 40 and below are safe.
Click to expand...
Click to collapse
Thank you!
That means we have a tiny bit of plus compared to the stock, about 15 percent relatively. I'll change the applied rate in the kernel to match your findings, so that 100 percentage set in the app will be devided to map to non rattling values.
I had the very same on op6 when first I tried.
Sent from my Pixel 4 XL using Tapatalk

tbalden said:
Thank you!
That means we have a tiny bit of plus compared to the stock, about 15 percent relatively. I'll change the applied rate in the kernel to match your findings, so that 100 percentage set in the app will be devided to map to non rattling values.
I had the very same on op6 when first I tried.
Sent from my Pixel 4 XL using Tapatalk
Click to expand...
Click to collapse
Nice! Keep up the good work. Glad to see you and flar already pumping out stable kernels. :good:

Updated original post with the final beta 4:
- fixing vibration power control settings

Finally got to create a summary video of CleanSlate kernel features. Unfortunately I don't yet have the OnePlus 8 or 8 Pro, but the features look more or less the same on OnePlus 8/Pro.. (Except AOD dimmer, it's not present on Op8/Pro)
Enjoy!
Feature demo
Sent from my Pixel 4 XL using Tapatalk

scott.hart.bti said:
Nice! Keep up the good work. Glad to see you and flar already pumping out stable kernels. :good:
Click to expand...
Click to collapse
@scott.hart.bti
Thanks for the support and testing... I want to bump to stable version just around today, but one last thing I've tried to resolve, which I managed to fix on Pixel4XL, and it is the safetynet CTS pass without magisk/magisk-hide, thru kernel method. Just yesterday I tested the fix on Pixel4XL android 10, but now I am looking for op8 testing.
So the goal here is to still have Safetynet CTS passed, but without root/magisk/magisk-hide, only by kernel level "hide".
Simply temporarily booting (fastboot boot) the image and then without any magisk patched in, try the SafetyNet attestation, either in a separate app https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample&hl=en_US or thru magisk installer Check SafetyNet is a good test too.
Also please test whether the Fingerprint scanner still functions with that:
Here's the 10.5.8 EU bootimage repacked with kernel source 10.5.5 based cleanslate with the patch, no magisk in it:
https://www.androidfilehost.com/?fid=4349826312261810100

tbalden said:
Thank you!
That means we have a tiny bit of plus compared to the stock, about 15 percent relatively. I'll change the applied rate in the kernel to match your findings, so that 100 percentage set in the app will be devided to map to non rattling values.
I had the very same on op6 when first I tried.
Sent from my Pixel 4 XL using Tapatalk
Click to expand...
Click to collapse
tbalden said:
@scott.hart.bti
Thanks for the support and testing... I want to bump to stable version just around today, but one last thing I've tried to resolve, which I managed to fix on Pixel4XL, and it is the safetynet CTS pass without magisk/magisk-hide, thru kernel method. Just yesterday I tested the fix on Pixel4XL android 10, but now I am looking for op8 testing.
So the goal here is to still have Safetynet CTS passed, but without root/magisk/magisk-hide, only by kernel level "hide".
Simply temporarily booting (fastboot boot) the image and then without any magisk patched in, try the SafetyNet attestation, either in a separate app https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample&hl=en_US or thru magisk installer Check SafetyNet is a good test too.
Also please test whether the Fingerprint scanner still functions with that:
Here's the 10.5.8 EU bootimage repacked with kernel source 10.5.5 based cleanslate with the patch, no magisk in it:
https://www.androidfilehost.com/?fid=4349826312261810100
Click to expand...
Click to collapse
Safetynet passes, but no fingerprint hardware available as per the message showing on the lockscreen. Also unable to enroll new fingerprint

scott.hart.bti said:
Safetynet passes, but no fingerprint hardware available as per the message showing on the lockscreen. Also unable to enroll new fingerprint
Click to expand...
Click to collapse
Oh that's unfortunate... I thought it might help as it is. But I'll think a bit more which of these affect safety net and which not so maybe we could have both
Thanks for the test!
Sent from my Pixel 4 XL using Tapatalk

[ROM][UNOFFICIAL][8.1] LineageOS 15.1 for Amazon Fire HD8 7/6th gen (douglas/giza)

⏱ Change log / Release Notes
2022-06-14 [douglas] [giza]
Updated sdcardFS to 2.0.
Updated the exFAT driver.
Fixed detection of external SDs.
2022-06-13 [douglas] [giza]
Rebased the entire tree, did a general cleanup
Fixed MicroG support (Signature Spoofing)
Fixed and re-enabled sdcardFS
Fixed direct Magisk installation/update
Enabled USB MIDI support
Enabled OTG ethernet support
Disabled binder logging
Enabled OpenGLES AEP
2022-01-02 [douglas] [giza]
Fixed USB tethering.
Added mediatek perf support.
Updated vendor blobs to the latest FireOS version.
Defined the vendor security patch.
2021-11-07 [douglas] [giza]
Fixed video recording on douglas.
2021-10-31 [douglas] [giza]
Fixed some DRM leftovers.
Added initial microG support.
Added exFAT support.
Fixed audio stream.
Added ged support.
Updated security patch to October 2021.
2021-10-03 [douglas] [giza]
Completely disabled sdcardfs.
Purged a lot of mtk/amazon logging.
Fixed missing symbols/libraries.
Reworked the audio configurations.
Fixed all the sensors.
2021-09-16 [douglas] [giza]
Fixed camera on douglas.
2021-09-12 [douglas] [giza]
Cleaned up wi-fi blobs/configs/service definitions.
Kanged the wi-fi HAL from a 8.1 mediatek device.
2021-09-07 [douglas] [giza]
Fixed swapped volume keys.
Show internal storage by default in the file manager.
Added option to reboot to hacked bootloader using ADB.
Disabled the update recovery function.
Added support for more SDs/USBs with other formats.
2021-09-05 [douglas] [giza]
Fixed over the air (OTA) updates.
Fixed Magisk/GAPPs installation.
The build is now signed with dev-keys.
Fixed installation of the ROM on giza.
Addressed a few SELinux denials.
2021-09-03 [douglas] [giza]
Audio works fine, incuding the mic.
DRM works fine, reports L1.
Video playback works partially fine.
Disabled camera as it doesn't work.

Reserved

Reserved

Rortiz2 said:
Magisk
For some weird reason, Magisk zip won't work (because of shims, wtf) so you'll need to manually patch your boot image with the Magisk Manager app and you'll need to flash it to boot_x with hacked fastboot mode or to boot with TWRP.
Click to expand...
Click to collapse
Fastboot is informed of the exploit so fastboot flash boot <path> will work.

SamDungUser said:
Fastboot is informed of the exploit so fastboot flash boot <path> will work.
Click to expand...
Click to collapse
No, fastboot isn't informed of the exploit, fastboot flash boot will overwrite the microloader and will brick the device.

Rortiz2 said:
No, fastboot isn't informed of the exploit, fastboot flash boot will overwrite the microloader and will brick the device.
Click to expand...
Click to collapse
Didn't know that. I think that's why I had to erase the boot partition just so I can install a rom again. it was able to boot to twrp so I just rebooted to hacked BL and erased then boot back and flash a rom in twrp

SamDungUser said:
Didn't know that. I think that's why I had to erase the boot partition just so I can install a rom again. it was able to boot to twrp so I just rebooted to hacked BL and erased then boot back and flash a rom in twrp
Click to expand...
Click to collapse
Yes that's possible, because TWRP restores the microloader (boot-exploit). Great to hear that you could recover it.

if you need to check the md5 upload the file and use https://emn178.github.io/online-tools/md5_checksum.html

The rom is abnormally large? When selecting the aroma package barely anything fits, in 7.1.2 it fit 5x more apps using th aroma package also 400 MB for the rom? what's causing this? how can I make the system partition bigger?

SamDungUser said:
The rom is abnormally large? When selecting the aroma package barely anything fits, in 7.1.2 it fit 5x more apps using th aroma package also 400 MB for the rom? what's causing this? how can I make the system partition bigger?
Click to expand...
Click to collapse
If I'm allowed to ask, what's aroma? And yeah, the ROM size it's quite normal since Android O includes vndk and hidls.

It feels really snappy compared to 14.1. I guess that's because of a different launcher?

dontpanic-xda said:
It feels really snappy compared to 14.1. I guess that's because of a different launcher?
Click to expand...
Click to collapse
I don't think the launcher has something to do with the snappiness. I guess Android Oreo it's more optimized than Android 7. You also need to keep in mind that I've updated the GPU drivers (kernel-side, mali).

Wow, great job @Rortiz2 ! Respect and thank you!

Rortiz2 said:
If I'm allowed to ask, what's aroma? And yeah, the ROM size it's quite normal since Android O includes vndk and hidls.
Click to expand...
Click to collapse
Aroma is an open gapps installer it includes all apps and offers a gui installer. Also, I found out what causes the screen issue. Apparently just installing a SELinux switcher app will cause the issue where if you put it to sleep by pressing the power button and you press the power button again to take it out of sleep nothing happens. I don't know how just installing a selinux switcher causes the screen issue and the Bluetooth crashes

SamDungUser said:
Aroma is an open gapps installer it includes all apps and offers a gui installer. Also, I found out what causes the screen issue. Apparently just installing a SELinux switcher app will cause the issue where if you put it to sleep by pressing the power button and you press the power button again to take it out of sleep nothing happens. I don't know how just installing a selinux switcher causes the screen issue and the Bluetooth crashes
Click to expand...
Click to collapse
Why would you set SELinux to enforcing..? Sepolicies aren't yet prepared to do so... Anyway, I don't have any clue about aroma, use the standard gapps package I guess.

Rortiz2 said:
Why would you set SELinux to enforcing..? Sepolicies aren't yet prepared to do so... Anyway, I don't have any clue about aroma, use the standard gapps package I guess.
Click to expand...
Click to collapse
I want to have it on enforcing to get safetynet to pass

SamDungUser said:
I want to have it on enforcing to get safetynet to pass
Click to expand...
Click to collapse
Alright, I guess I'll try to fix sepolicies then. Don't expect it to be quick though, this takes a lot of time.

I'm really impressed with this ROM. Running Services reports nearly 800 MB free after boot and it's definitely snappier. Also, viewing Settings with a pure black background is probably my favorite feature.
One thing I did run into was that during the install of GApps, it seemed to stall after the Installation Complete message. I just rebooted manually and it was all fine. Great job, Rortiz2

rom installs fine but it looks like it freezes after "installation compete" for opengapp.
Used the link above for openapp. Did not choose a different variation.

📳🔥 PixelFlasher, a GUI tool for flashing / updating / rooting / managing Pixel phones.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DESCRIPTIONAs the name suggests this is an application to flash (update) Pixel™ phones (possibly all Google™ made phones/tablets, YMMV.)
PixelFlasher at its core is a UI layer (with bells and whistles) on top of adb / fastboot commands, hence many of its features can be used on non Pixel devices as well. (YMMV).
The executable is self contained and does not require Python™ to be installed on the system.
Basic mode: Should suit most users. Some of the features in basic mode are:
Simple UI interface, click and go. No more command line, no more placing all files in one directory.
boot.img management UI, select the boot.img file to patch and click the patch button. Fully Automated patching with Magisk (without manual steps) and perform upgrades without losing root.
No more manually extracting files transferring to the phone, patching / re-flashing and doing multiple reboots.
No more setting airplane mode and clearing storage to retain Safetynet passing.
Display details of boot.img (or init_boot.img for Pixel 7 / 7 Pro).
SHA1 checksum.
Origin (file it was extracted from).
Whether it is patched or not, and if it is patched.
What version of Magisk was used to patch it.
On what device it was patched.
Date of patching.
The SHA1 of the source boot.img file.
Option to Live boot from a choice of boot.img or patched image.
Flash just the boot / init_boot image.
Choose to keep data or wipe data while flashing.
Ability to flash even if multiple devices are connected to the computer.
Option to flash to inactive slot.
Display information about the phone.
ID
Hardware model.
Device architecture.
Current installed firmware (build).
If it is rooted with Magisk.
Magisk version (Magisk Tools).
Magisk Manager version (the app).
List installed Magisk modules.
Connection mode (Adb | Fastboot | Sideload | Recovery).
Bootloader version.
Active slot.
Android OS API version.
Convenient quick links to download Android platform tools or device firmware.
Magisk Manager installation UI, screenshot. Supported versions:
stable (official)
beta (official)
canary (official)
debug (official)
alpha
delta
special build that disables modules, used to recover from bootloops due to bad module(s) when safe mode does not work.
Magisk Backup Manager, screenshot.
List all Magisk backups currently on the device.
Highlight the one that is backup of the current installed version.
Delete backups.
Manually add backup from PC.
Auto Backup: PixelFlasher figures out what needs to be backed up, and if it finds it on the PC, it creates the backup.
Magisk modules management, enable / disable modules selectively, this comes in handy to disable suspect modules before an upgrade screenshot:
Name
Version
Description
Enabled / Disabled.
Display Android Platform Tools (SDK) version and warn / block if the version is old.
Install APK (an app) file from the computer onto the device.
Advanced features are hidden to keep the interface simple and easy to follow.
A lot of checks and validations for smooth operation.
Automatic check for program updates.
Package (Application) Manager, screenshot:
Disable (Freeze)
Enable
Uninstall
Install APK
Download APK
Multi-Select
Show Package Details.
Expert mode: (should only be turned on by experienced users). In addition to the basic features, you get:
The ability to flash custom ROM (with or without patching boot.img)
Option to flash to both slots.
Option to flash to inactive slot.
Options to disable verity and or verification.
Ability to change the active slot.
Ability to live boot to custom boot.img (temporary root).
Ability to boot to recovery.
Ability to flash custom image: boot, recovery, radio, kernel, ...
Ability to sideload an image.
Lock / Unlock bootloader.
Option to gain temporary root (good for testing or checking things out).
SOS Disable Magisk modules to get out of bootloop (experimental).
Prerequisites
Android SDK Platform-Tools.
Android Pixel phone factory image or Android Pixel phone full OTA image.
Bootloader unlocked phone (see excellent guide links in credits section below).
InstallationPixelFlasher doesn't have to be installed, just double-click it and it'll start.
Check the releases section for downloads.
Supported platforms
Windows
MacOSX
Linux
UsageBasic Mode
First thing to do is select Android™ Platform Tools, if Android™ Platform Tools is already in your PATH environment, the application will detect it and pre-populate it.
Otherwise you'd have to select where it is installed.
You can download the lastest Android™ Platform Tools by clicking the
next to it.
If you have multiple versions, you can select another version, although it is best to always use the most recent version (The selected version will be identified and displayed.)
Hit the Scan button to detect connected devices, the application will detect all connected devices
(in adb, fastboot, sideload, recovery modes) and populate the combo box (2).
Select your device from the list in the combo box. The following information about the connected device is displayed.
(1st field) Rooted devices will be identified with a checkmark ✓. Note: If you want PixelFlasher to detect root, or automatically use Magisk to patch boot.img, you need to grant root permissions to shell in Magisk.
(1st field) Non-Rooted devices will be identified with a ✗.
(1st field) Devices in fastboot mode will be identified with a ? (in fastboot mode, root status cannot be determined).
(2nd field) (adb), (f.b), (sid) or (rec) to indicate connection mode adb / fastboot / sideload / recovery.
(3rd field) Device ID.
(4th field) Device hardware.
(5th field) Current running firmware (in fastboot mode current firmware cannot be determined).
Next select the factory or full OTA zip file (don't unzip), the application will recognize the phone model from the image name and validate the SHA-256 checksum.
You can download factory images by clicking the
next to it. You can download full OTA images from here.
Note: Because both firmware package and full OTA are complete images, you can upgrade to any newer version without worrying about jumping versions (downgrades might work, but are not recommended).
Process the factory image. PixelFlasher will extract boot.img (or init_boot.img for Pixel 7 / 7 Pro) file from the factory image and populate it in the list below (5).
Select boot.img (or init_boot.img for Pixel 7 / 7 Pro) from the list, the selected file can be patched (6), or flashed (10).
Optional: Select this option if you want to patch the boot.img (or init_boot.img for Pixel 7 / 7 Pro) with Magisk. If Magisk is not already installed on your phone, PixelFlasher will install it for you. Your phone does not need to be rooted to create a patched file. This would be the typical choice for monthly updates.
This option will allow updating the phone without losing root (not even temporarily).
Note: See note above for granting root permissions to shell.
Whether the phone is rooted or not, the whole process is without any manual step.
If you want to flash (10) a patched boot.img (or init_boot.img for Pixel 7 / 7 Pro) select the newly added entry.
The following details are listed.
Indicates that the selection is patched.
SHA1 is (shortened for display only) sha1 of boot.img (or init_boot.img for Pixel 7 / 7 Pro)
Source SHA1 (shortened for display only) SHA1 of source boot.img extracted from the image (This should be the same as SHA1 of an unpatched boot.img)
Package Fingerprint is just the filename portion of the image (without the extension).
Patched with Magisk indicates the version of Magisk used to patch the image (if applicable).
Patched Method indicates what method PixelFlasher used to create a patch (possible options: root, app, uiautomator, manual)
Patched on Device indicates the device model that performed the patching. You should always use patched images that match the model of the device that it will be flashed on.
Date is the either the date the boot.img was extracted, or the date it was patched.
Package Path indicates the file from which boot.img (or init_boot.img for Pixel 7 / 7 Pro) was extracted.
Select the Flash Mode
If factory firmware is selected in step 4:
Keep Data: In this mode -w flag is removed from the flash scripts so that data is not wiped. This is commonly known as dirty flashing.
WIPE all data: As the text suggests, this will wipe your data, use it with caution!
If this mode is selected PixelFlasher will ask for confirmation during the flashing phase.
Dry Run: In this mode, the phone will reboot to bootloader, and then mimic the flash actions (i.e. reboot into bootloader) without actually flashing anything (it prints to the console the steps it would have performed if dry run was not chosen). This is handy for testing to check if the PixelFlasher properly is able to control fastboot commands.
If full OTA image is selected in step 4:
Full OTA: Will flash full OTA image in sideload mode. Features of this mode:
This will always flash to inactive slot similar to how OTA updates happen on the phone.
If something goes wrong during flashing, the active flash is uneffected and the phone boots back to active functional slot.
If you flash to both slots (ie flash twice in a row) then both slots would be bootable.
Your phone's bootloader does not have to be unlocked to be able to flash full OTA image (stock boot only).
Optional: Open Magisk Modules Manager and disable (uncheck) modules known to cause issues during upgrades (the below list has never caused issues for me, so I keep them enabled YMMV).
Flash Pixel Phone This is the final step, to actually flash the phone in the selected Flash Mode.
Note: Unlike the previous versions of the PixelFlasher, all the options are dynamic, i.e. depending on what you select before clicking the Flash button, there is no more concept of prepared package. PixelFlasher will first present you the selected options and ask for your confirmation if you want to proceed with flashing.
Expert Mode
To enable the export mode use the File Menu | Advanced Configuration and select Enable Advanced Options
In this mode the following additional options are exposed (green bounding boxes), below notes are more for enumeration than a guide, as they should be trivial and obvious to an expert.
Option to Change the Active Slot (the inactive slot is automatically selected).
Option to reboot to Recovery.
Options to Lock / Unlock bootloader, Option to disable Magisk modules when bootlooping.
Apply Custom ROM. This replaces the factory ROM image with the selected file.
PixelFlasher extracts boot.img from the ROM image and displays below for selection or patching. Please make sure to read the documentation of the chosen ROM, as each custom ROM instructions could be different.
To be clear, this is what PixelFlasher does internally when this mode is selected, please understand it, and don't use it if the selected ROM guide does not fit the bill. You've been warned!
Keeps stock bootloader and radio images.
Replaces the stock ROM image with the selected custom ROM image.
Flashes in the chosen Flash Mode just like a stock image, i.e. bootloader, custom ROM and radio images in the original order that they were in the stock firmware.
Patching boot.img can be performed if the option is selected. You can select any of the listed boot.img.
Flash Mode is similar to basic flash mode described above in step 7.
Custom Flash. select this to switch from flashing a Factory Image to flashing a single file.
Browse to select a a valid image file (.img or .zip). Or select a boot.img from the list above and click on the paste button to paste the selected boot.img into the file selection. Choose the dropdown to select image type.
boot (can be flashed to Live or boot) - Expected file type .img
bootloader - Expected file type .img
dtbo - Expected file type .img
product - Expected file type .img
radio - Expected file type .img
recovery - Expected file type .img
super_empty - Expected file type .img
system - Expected file type .img
system_ext - Expected file type .img
system_other - Expected file type .img
vbmeta - Expected file type .img
vbmeta_system - Expected file type .img
vbmeta_vendor - Expected file type .img
vendor - Expected file type .img
vendor_boot - Expected file type .img
vendor_dlkm (the device will be put into fastbootd mode during this operation) - Expected file type .img
image - Expected file type .zip
SIDELOAD - Expected file type .zip
Select the appropriate flash options. Note: For Tensor devices (Pixel 6, Pixel 6a, Pixel 6 Pro, Pixel 7, Pixel 7 Pro) When Flash to both slots option is selected, Pixelflasher flashes each slot individually to overcome a Google bug that fails with the option --slot=all
Credits
First and foremost Magisk by John Wu which made rooting Pixel™ phones possible, without it none of this would have mattered.
Big thanks to [ryder203], [t-ryder] for his valuable ideas, feedback and testing. Your contributions are very much appreciated.
[Homeboy76] and [v0latyle] at xda for their excellent guides [here and here] on Pixel™ series phones. This program could not have been possible without their easy to follow guides.
I strongly encourage all beginners to follow those guides rather than use this program, it is important to understand the basic steps involved before diving into one click tools or advanced tasks.
Marcel Stör's nodemcu-pyflasher source code which jump started my introduction to wxPython and eventually this program.
JackMcKew for pyinstaller Github Actions.
Endless counts of xda members and their posts that tirelessly answer questions and share tools. Too many to enumerate.
Disclaimer
Code:
*******************************************************************************
PLEASE DO YOUR PART AND READ / SEARCH / RESEARCH BEFORE USING THIS PROGRAM
AND/OR ATTEMPTING ANY MODIFICATIONS ON YOUR DEVICE.
THIS PROGRAM ASSUMES THAT YOU ALREADY KNOW HOW TO AND HAVE ALREADY UNLOCKED
YOUR BOOTLOADER, ALREADY ROOTED YOUR DEVICE, AND KNOW HOW TO USE ANDROID SDK
PLATFORM-TOOLS, ETC.
THIS TOOL IS SIMPLY MY QUICK WAY OF UPDATING THE FIRMWARE WHILE ROOTED WITH
MAGISK, WITHOUT LOSING DATA / REQUIRING A WIPE.
MODIFYING YOUR DEVICE COMES WITH INHERENT RISKS, AND IT'S NOT MY RESPONSIBILITY
IF YOU LOSE YOUR DATA OR BRICK YOUR DEVICE. THE TOOL I SHARE HAVE WORKED FOR ME,
BUT THAT DOESN'T MEAN THAT YOU MAY NOT RUN INTO PROBLEMS. **BACKUP YOUR DATA.**
*******************************************************************************
No Donation
I've been asked quite few times about donation, (here, here ... just to list a few).
I'll put it here so that my stance is clear.
This program will remain totally free, ad free, even donation free, it's my way to give a little back to the community that has given me years of support and joy.
You can contribute by helping the next newcomer to learn the ropes and navigate through the maze of information.

Device specific support threads:
Google Tablet
Google Pixel 7 Pro
Google Pixel 7
Google Pixel 7a
Google Pixel 6 Pro
Google Pixel 6
Google Pixel 6a
Google Pixel 5
Troubleshooting:
See this post.
Generate Sanitized support.zip file (File Menu) and submit that with your report.

Latest Release:
June 23, 2023 v5.3.3.0 release
#79 Bug-fix: Package Manager column stays unsorted when filtered.
Warn users that extract the contents of firmware and use the image inside as firmware, which is no good.
Warn users of Android Platform-Tools 34.0.3 about potential issues and suggest using 33.0.3
Package manager bug fixes and improvements.
Spoiler: Older Releases
June 21, 2023 v5.3.2.0 release
Added support for Pixel tablet (tangorpro).
For future devices, fixed a bug to auto detect init_boot partition and flash init_boot instead of boot even if the device is newer than the PixelFlasher and is not in PixelFlasher's list.
Disable Patch buttons if device is not in adb mode.
Reboot to system after lock / unlock bootloader if No Reboot option is not selected.
Increase sleep after reboots to various modes to assure that slow devices have time to be detected.
Updated Readme and screenshots.
Minor improvements and bug fixes.
June 16, 2023 v5.3.1.2 release
Set Active slot now automatically reboots to system after setting the slot, unless "No Reboot" option is selected.
Update Ubuntu 20.04 build to be aligned to the same methods that Ubuntu 22.04 build uses.
Improve confidence value calculation when comparing compressed sha1 against normal sha1 to account for shift.
Do not abort when the sha1 comparison confidence value is low, leave the choice to the user.
Update Windows builds (both) as wxPython wheel path changed, rely on a more persistent URL instead.
June 06, 2023 v5.3.0.0 release
Added Github Action build on Windows 2019 with Python 3.8 to support Windows 7.
PixelFlasher now supports loading and processing Samsung Firmware (at least my Samsung's ), it would extract AP, BL, CSC, Home_CSC ... and then extract boot.img.lz4 from AP and unpack the lz4.
When creating a patch from the set boot.img, PixelFlasher will also create boot.tar to be flashed as AP to retain root.
If there was a way to pre-load odin with the extracted files, flashing could also be automated.
I know, what does PixelFlasher have anything to do with Samsung firmware? I added it for my own use.
June 03, 2023 v5.2.0.2 release
#76 Get a better build with Github action to support more Linux based platforms (no functionality changes).
June 01, 2023 v5.2.0.1 release
Bug fix #78 Error when opening a shell console on Linux / Mac
June 01, 2023 v5.2.0.0 release
Update build workflows
Add payload_dumper functionality to PixelFlasher to handle OTA files, thanks to vm03 for sharing source code.
Added rules engine code to better / easier management of the UI widgets enabling / disabling.
Auto detect Pixel OTA image and extract boot / init_boot / vbmeta for patching and flashing.
Add Full OTA mode, which flashes full OTA image, while optionally retaining root, and best of all, for A/B devices, both slots are bootable, you can even have one rooted and one not.
May 25, 2023 v5.1.0.2 release
Skip testing fastbootd in dry run mode if Android platform tools version is > 34, is it no longer supports fastbootd (at least 34.0.3 does not)
v5.1.0.1 release notes:
Exception handling when device is not in the listed Pixel devices.
v5.1.0.0 release notes:
Support for Android platform tools version 34.0.3, and automatic setting of ANDROID_PRODUCT_OUT environment to workaround a regression introduced in version 34.0.3
Temp workaround to avoid selecting root method patching when Magisk Delta is detected.
Nicer looking / clearer manual patching dialog.
When a Pixel device is selected, PixelFlasher now displays additional information about the device's support.
Things like: Device name, version end date, security update end date, Android version, name, codename, release date, end date.
Boot image list box now displays the applied PixelFlasher patch method.
Auto-resize boot image list box columns for better readability.
Precautionary cleanup up of leftover files on the phone in case root detection software keys on presence of such files.
#77 added attrict3 to requirements.txt in case it helps with certain builds (it shouldn't be needed).
Bug fixes and improvements.
May 21, 2023 v5.0.1.0 release
Added workflow for building on MacOS 13.
ComboBox behavior on Mac is different than Windows, make adjustments.
Ability to set PixelFlasher working directory (no UI).
Speed up startup.
Popup device selection after Wifi adb connect.
Clear Device list after adb kill-server.
May 19, 2023 v5.0.0.1 release
#75 Bug fix, when device is in bootloader, type error.https://github.com/badabing2005/PixelFlasher/issues/74
#74 Added Support for Pixel 7a (lynx)
Configuration option to define the file manager to use on Linux (default: Nautilus)
Configuration option to define the terminal emulator to use on Linux (default: gnome-terminal).
Support for additional types of Factory / ROM files.
Checksum validation of firmware / ROM files (if part of the checksum is in the name, otherwise just display)
New advanced option, ability to choose the patching method (with recommendations).
Added Recovery Image patching option.
Advanced option to enable the use of busybox shell (default off).
Auto detect firmware / rom with init_boot and use init_boot for creating patches, this way future firmware don't have to be manually added to PixelFlasher.
Auto detect devices with init_boot and use init_boot for flashing, this way future devices don't have to be manually added to PixelFlasher.
Auto-popup the detected devices dropdown after a scan, to make it obvious to select that next. (Thanks @pndwal for the idea)
Show SHA-256 of adb and fastboot binaries, as Google keeps on messing up Android Platform-tools, it's necessary to whitelist / blacklist specific binaries.
#66, when checking the patched files internal SHA1, provide a confidence rating.
Check, valdiate and warn if necessary when flashing an image patched with Magisk Zygote64_32, as there are wipe implications, provide links to documentation.
Added fastbootd testing to Dry Run.
Added Github actions to build all the targets on Github.
Code refactoring, bug fixes and improvements
Apr 30, 2023 v4.10.0 release
Added no reboot option, with this option selected, after flashing is completed, the phone will not reboot to system, giving a chance to take other actions before reboot.
Added built-in file editor, you can now edit the flash script before running, in case you want to customize it (needless to say, should only be used if you know what you're doing)
Added a button to open an explorer in working directory, useful for people who want full control, perform manual actions by following guides, but using PixelFlasher to do the prep work.
Made the Firmware and Rom Process buttons, full with text. It wasn't obvious for some.
Detect and handle Magisk Zygote64_32 automatically, thanks to @Namelesswonder for adding the necessary marker.
Apr 27, 2023 v4.9.0 release
Added support for installing / creating patch with @Namelesswonder Magisk zygisk64_32 (stable, beta, canary, debug versions).
Support for recognizing Lineage firmware and extracting / patching boot.
Display 32 bit capabilities of the device.
Utilize New Magisk 26.x flags as needed (patch support for more devices).
Disable Flash to Inactive slot and Flash to both slots button if the device is not A/B device.
Partition Manager can now list the partitions even if the devices is not rooted.
Added Custom Patch button, which allows selecting a boot file from disk and getting a patched file back to save to disk (all on the PC).
Added Open Folder button to open a file browser to the directory of the selected boot image.
Added Reboot to Download button (Odin mode).
Added Reboot to Safe Mode button.
Storage reorganization, store patched files next to the stock file, and set the patch name to clearly indicate both source and target sha1.
Various additional validation checks.
Bug fixes and other improvements.
Apr 10, 2023 v4.8.2 release
Include additional Magisk versions in the check to display a warning dialog when the user has installed one of the known versions to have issues.
Display USNF related flag values when selecting a device.
Check the downloaded Google firmware checksum to match the one in the filename and warn if it does not.
Link to download Google USB Driver is added in the help menu.
Added more visual troubleshooting event flows.
Install APK now defaults to Non Market.
Added Install APK cancel option.
You can now select an app in package manager and right click to launch it on the phone.
Minor bug fixes and other improvements.
Mar 14, 2023 v4.8.1 release
#47 Feature request: Added partition manager - Allows to erase partitions, and / or dump / backup partitions to PC.
Added more visual troubleshooting event flows.
Added warning message for when Android platform tools versions 34.0.0 and 34.0.1 are used.
Improved support.zip redactions.
Added Support.Zip generator button on the Main screen.
APK Install option can now set the ownership to Play Store Market (useful for Android Auto)
Check and warn the user when Magisk Canary versions 25207, 25208, 25209 and 25210 are being used.
Bug fixes and other improvements.
Feb 12, 2023 v4.8.0 release
#50 Support for Android 14 Developer Preview for Pixel 7 and Pixel 7 Pro
#48 Do not allow patching with hidden Magisk (stub) and adb shell not granted root rights.
Block using Android Platform Tools version 34.0.0 and display a warning because it has known issues
Disable Magisk Backup Manager button if root access to adb shell is not granted.
Button to Open adb shell connected to the selected device.
Work in Progress: Generate graphical activity log to visualize the activity and speed up troubleshooting.
Feb 05, 2023 v4.7.0 release
Added Magisk Backup Manager:
List all Magisk backups currently on the device.
Highlight the one that is backup of the current installed version.
Delete backups.
Manually add backup from PC.
Auto Backup: PixelFlasher figures out what needs to be backed up, and if it finds it on the PC, it creates the backup.
Added Reset on Magisk Manager package name setting to reset to default: com.topjohnwu.magisk
Linux / Mac build.sh now switches to the PixelFlasher folder if it is run from elsewhere.
Magisk installer improvements:
When installing Magisk Alpha or Delta, PixelFlasher updates the configuration to match the package name to the respective Magisk package.
Magisk installer window displays the package name.
You can now copy to clipboard, the download URL and package ID.
Magisk Manager columns are now wider for better readability.
Package Manager improvements:
Added Search / Filter option.
Show count of filtered packages.
Application Name (label column).
"Get Application Names" Button to resolve all package application names. This is a slow process, hence PixelFlasher caches them.
Button to download (pull) APKs from the device. (Multiple downloads in one shot is also supported).
Other under the hood improvements.
When selecting a firmware or ROM file, sha256 is printed to console and displayed on hover, to validate if it matches the published sha256.
More verbose logging that helps with troubleshooting.
Double click on "ADB Connected Devices" to invoke adb kill-server which is handy at times, specially when dealing with Wifi ADB.
Moved existing links under Help Menu | Links, and added few more handy links.
Added timestamp to support.zip filename.
On request, spinning cursor with text "Please be patient ..." is now displayed in red.
Flashing to inactive slot is now in basic configuration instead of advanced configuration.
Preparation work for version 5.0 DB improvements.
#40 Handle locale related exceptions which were causing PixelFlasher to not launch on some Windows 11 systems.
Add the ability to download and install a special Magisk version that has modules loading intentionally disabled. Required to get out of bootloops and manage to disable modules.
Credit to gecowa6967 at XDA.
Dec 05, 2022 v4.6.0 release
Added single click button to easily flash just the boot/init_boot (stock or patched) to the phone.
#39 Display Flash Option changes in the console, and allow flashing to inactive slot in basic mode.
#39 Do the Magisk backup only when rooted.
Decouple OTA sideload from needing factory image.
Other minor improvements.
Dec 04, 2022 v4.5.0 release
New look (Artwork / Icons), compliments of @t-ryder (thank you), based on Material design icons.
New Feature: Package Manager, Install / Uninstall / Freeze (disable) / Unfreeze (enable) packages even system ones (root not required). Handy with Wifi ADB.
Use latest Python updated packages.
Ubuntu 22.04 support.
Miscellaneous improvements.
Nov 09, 2022 v4.4.0 release
New feature: Font and Font size should be configurable by the user #33
New feature: Added WiFi-ADB connect / disconnect button. Left click to connect, Right click to disconnect.
Handy to access a device remotely.
Note: This only works in adb mode, so no fastboot or flashing features work for remote devices, but for patching / installing apks, managing Magisk modules it works well (basically anything that is done in adb).
I personally use this to test patching on remote devices, and also use it to access / install apps to my watch.
Ground work for future features: Get installed Package list, and list which are disabled, enable / disable / uninstall apps. (Will be available in future release).
Move Flash Option Flash to inactive slot to Basic mode from Advanced mode..
Minor UI Improvements
If Magisk does not create a backup attempt to trigger Magisk to create one.
Update readme to include Pixel 7 / 7P specific info.
Oct 27, 2022 v4.3.1.0 release
Bug Fix: Magisk modules not listed on MacOS / Linux
Oct 16, 2022 v4.3.0.1 release
Bug fix: #30 Error during firmware processing file extraction phase.
PixelFlasher-Linux is now labeled PixelFlasher-Ubuntu (It is built on Ubuntu which is not compatible with all Linux flavors. Even though PixelFlasher-Kali is more compatible, it is still not a one size fits all solution.)
Oct 15, 2022 v4.3.0 release
New: You can now download and install alpha and delta Magisk versions in addition to the official stable, beta, canary and debug versions.
Bug fix: Generating support.zip file was modifying the main db file unnecessarily.
Bug fix: When patching with Magisk Manager the version of Magisk Manager was not being displayed in the boot images table.
Bug fix: MacOS downloaded Magisk had space in the file path, which was causing failed installation.
Oct 13, 2022 v4.2.0 pre-release
Support for Pixel 7, 7p (init_boot extraction and patching / flashing).
Added Pixel 7 / 7p partitions flashing options to custom flash.
Improved patching process using boot_patch, add more patch file validations.
Check for Magisk backup and trigger Magisk to backup if missing.
Add more logging messages for troubleshooting.
Code optimization / improvements.
Bug Fix #28 Error when opening download link without a device selected.
Added set_version script to easily set the product version.
Print path of the selected boot to console, for easy copy / paste.
Oct 05, 2022 v4.1.4 release
Rooted Magisk patching will now automatically back up stock-boot.img (more to come).
Bug Fix #27, handle version exception.
Oct 05, 2022 v4.1.3 release
Bug Fix: Extract Magisk Manager version properly.
Oct 04, 2022 v4.1.2 release
include busybox binaries for different Android architectures (arm64-v8a, armeabi-v7a, x86_64, x86)
don't use hidden Magisk for patching, as it is a stub only.
Oct 03, 2022 v4.1.1. release
Bug Fix: Bundle busybox with PixelFlasher to be used for unzipping Magisk.
Bug Fix #25, use the Magisk Manager version number instead of Rooted Magisk version number.
Cosmetic changes and a bit more logging.
Oct 03, 2022 v4.1.0 pre-release
Patching is now fully automatic with or without root.
PixelFlasher uses installed Magisk Manager binaries to create a patch (root binaries are only used if Magisk Manager is not available / accessible)
UIAutomator no longer necessary, neither asking the user to manually patch and click ok when done.
Added an option to set a hidden Magisk package name so that PixelFlasher can find the Magisk and use it, the user still has a choice to use root binaries.
Speed improvements for device property reading.
Speed improvements for Magisk modules reading.
NOTICE:
I'm marking this release as pre-release because I just found out that unzip is not normally available on the phone, which this new patching mechanism uses.
On my test phones they were available.
Unless you have unzip on your phone, you should avoid using this version.
Sorry about this oversight.
Sep 25, 2022 v4.0.0 pre-release
New Feature: On supported devices, where device is not yet rooted (or adb shell su not allowed), an option to control the Magisk Manager GUI (drive UI) to programmatically control the app through UIAutomator and create a patched boot.img
See Patching flow chart for details.
New Feature: Detect if Magisk Manager is at a higher version than installed Magisk, warn the user of a potential rare corner case and offer a choice of patching method.
New Feature: Temporary Root, when flashing if you choose this option, the phone will be flashed with unpatched boot.img, but Live boot to patched boot.img to provide a temporary root.
New Feature: Warn the user to flash both bootloader slots if their device is a Tensor device (Pixel 6, Pixel 6a, Pixel 6 Pro), if current version of OS is lower than Android 13.
New Feature: Flash to inactive slot. Unlike OTA flashing factory image flashing is always done on the current active slot, with this option selected, PixelFlasher will write to inactive slot. This allows one to revert to current working state in case anything goes wrong. This feature combined with Temporary Flash provides best method to test a new firmware without risking losing current working setup.
Note: You should avoid this option if you are on a Tensor device and are upgrading from Android 12 to Android 13 (see the previous feature).
New Feature: Detect and operate on devices that are in Sideload or Recovery mode.
New spinner to indicate PixelFlasher activity.
Renamed Reload button to Scan, to better reflect the button's function. After a scan print the count of devices found.
PixelFlasher previously used MD5 to uniquely identify boot images (patched or otherwise), with version 4.0.0 PixelFlasher now uses SHA1 instead of MD5.
This has no bearing on the functionality, it just better aligns with Magisk way of identifying and tagging boot images.
PixelFlasher now extracts the embedded SHA1 of a Magisk Patched images (only available in newer devices) and assures that it matches the source boot.img's SHA1.
This is just an extra validation.
Code cleanup / refactoring, adding more validations and exception handling.
Print debug details when encountering non compliant Magisk modules.
Firmware link now takes you to the device's download page instead of just the general download page.
To better reflect the file details, transferred and stored boot.img files are now suffixed by their shortened SHA1, while magisk_patched.img files are now suffixed by shortened SHA1 of their source boot.img.
Allow sideload even if bootloader is locked.
Sep 04, 2022 v3.7.0 release
New Feature: Install Magisk into the phone, PixelFlasher displays information about the latest available Magisk versions (stable, beta, canary, debug) and offers the choice to install a selection.
New Feature: Install compatible apk file onto the device from PixelFlasher menu.
Check Android Platform Tools version and warn if it is old.
Block flashing when stock flash_all.bat file is tampered with.
Don't bother with flashing if bootloader is locked.
More validations and exceptions handling.
Improved logging.
Aug 24, 2022 v3.6.0 release
When a device is selected, the Bootloader version is displayed. (Useful for Pixel 6* devices with ARB). Works in adb and fastboot modes.
Added a button to dump full device info (useful for troubleshooting). Works in adb and fastboot modes.
Improved tooltips.
Aug 21, 2022 v3.5.1 release
Fix: Incorrect warning is displayed when Flash on both slots is selected.
The contents of the generated flash-phone.bat file will now be displayed on console even if verbose option is not selected, this helps the user know exactly what commands would be executed before clicking the OK button.
Aug 19, 2022 v3.5.0 release
Add support for fastboot --force flag (to help fix partition issues, caution it will wipe data) see this.
Split image flashing to all slots into two separate single slot flashing to bypass a Google bug on Pixel 6* devices, see this by @Namelesswonder
July 18, 2022 v3.4.0 release
Improvements to the boot extraction / categorization.
Live boot option directly from the selected boot.img UI, even though it was possible to live boot previously through the advanced menu, it is now super easy to select a boot.img (patched or otherwise) and Live boot to that image with a click of a button.
Added warning message in the splash screen and the help about menu, to inform users not to fall for opportunists who are claiming to be the developer of PixelFlasher with a donate button next to the download link. Reminder to all, this program will always be free, ad free, donation free; you should not be solicited for any form of payment.
June 26, 2022 v3.3.5 release
Fix Lock / Unlock bootloader buttons being reversed.
June 12, 2022 v3.3.4 release
Bug fix on MacOS / Linux
Improved notice message about Fastboot process.
June 06, 2022 v3.3.3 release
Bug Fix: When choosing custom ROM, the ROM file was not being copied to the package directory.
Update Documentation and screenshots.
May 25, 2022 v3.3.2 release
Handle system codepage.
Add configurable codepage setting in advanced settings to be able to override the value.
Selected boot color is now blue instead of red to avoid thinking that it has a problem.
After Flashing, clear connected device to avoid using device in case it is not yet ready.
Fix: Paste boot button should be hidden in basic mode.
Always print md5 of Magisk_patched (previously only verbose mode displayed it).
Wait 10 seconds instead of 5 seconds after reboot before issuing next command.
May 21, 2022 v3.3.1 release
Change encoding from utf8 to ISO-8859-1
Button to paste the currently selected boot.img into custom flash file selection.
Several Mac version improvements, thanks to rhetorican for reporting and testing.
UI improvements
Fix: On low resolution screens, the application startup position is high enough to clip the top part.
Fix: On low resolution screens, the patch icon is too large and dis-proportional to the rest of the UI
Better dark mode handling on Mac / Linux
Increase the wait during flashing to account for slower devices.
Further improvements on support.zip redaction process.
Other minor fixes and additional validations.
May 05, 2022 v3.3.0 release
MacOS build.
Handle Magisk module.prop with comments.
Exception handling on magisk module errors.
boot.img management improvements.
Removed old Powershell script.
More checks and validations.
support.zip now includes sanitized PixelFlasher.db
May 04, 2022 v3.2.0 release
Help menu option to create support.zip file, which sanitizes (redacts user names and device IDs) of the log files.
This makes it super easy to provide support.zip file when something goes wrong and need to report it.
In boot management, delete firmware cache of the selected boot.img if it is the last boot.img used from that firmware.
Handle space characters in username.
Console is now responsive when processing firmware file.
More checks and validations.
Update readme with instructions on how to build PixelFlasher on MacOS.
May 02, 2022 v3.1.1 release
Handle UTF-8 Encoding.
May 02, 2022 v3.1.0 release
Fixed a missing step in the final flashing of boot.img
Decoupled Firmware / ROM processing from selecting the files, now we have a separate button to process, makes it clearer and does not give the impression that selecting the file is hanging.
Added splash screen (v3.0.1), the GUI refresh hiccup is gone.
Made the boot.img management delete function more extensive.
I flashed my phone with the May drop using this version.
April 30, 2022 v3.0.0 release
New workflow, no more package preparation, select options and flash all dynamic.
boot.img caching and management UI with details about the state of boot.img files.
Faster as there is no more need to zip a package.
Other optimizations and improvements.
Update documentation.
April 20, 2022 v2.4.1 release
Bug Fixes: Error message during flashing, introduced by code reshuffle.
It turns out that some Magisk Modules don't set the id, which was expected to be present, which caused Magisk module management screen not to display.
April 19, 2022 v2.4.0 release
Magisk modules management, enable / disable modules selectively, this comes in handy to disable suspect modules before an upgrade.
Autoscroll the console.
Code cleanup.
April 17, 2022 v2.3.0 release
Optional automatic check for updates feature.
Added help menu links to:
- Report an issue
- Feature Request
- PixelFlasher Project Page
- PixelFlasher Community (Forum)
- Homeboy76's Guide
- V0latyle's Guide
- Open Configuration Folder
- Check for New Version
Icons for menu items.
Link to download Pixel Firmware.
Link to download Android Platform Tools.
Unlock Bootloader.
Lock Bootloader.
SOS (experimental) - disable Magisk modules to get out of bootloop.
Additional flashing options:
- product
- system
- system_ext
- system_other
- vbmeta_system
- vbmeta_vendor
Added sideload flashing option.
Updated documentation.
Further improved console messages for troubleshooting.
Linux build using Github Actions.
Manual build for Kali Linux.
April 11, 2022 v2.2.2 release
Linux support.
Remember last window position.
List Magisk modules, when Magisk is detected.
Added fastboot verbose option.
Added more checks and validations.
Added more details when errors are encountered.
Cleaner message box (better formatting).
Notice to the user in case fastboot drivers are not setup properly.
More plumbing work for the new upcoming workflow.
Add notes on how to build the Linux version.
April 06, 2022 v2.1.0 release
Setup dedicated profile directory.
Put logs in the profile directory and maintain log history.
Plumbing for Linux support (just the flashing part is left to do).
Plumbing for new workflow.
Bugfix to handle name conflict in ROM filename.
Various minor improvements.
Update documentation.
April 03, 2022 v2.0.1.0-pre release.
Major refactoring
Added Advanced (Expert) mode UI.
Basic mode keeps UI simple and hides expert features.
Support for setting active slot.
Reboot options (recovery, system, bootloader)
Moved custom ROM options to expert mode.
Added custom flashing to expert mode, can now flash to live (temporary root), or custom flash any image to any partition.
Moved flashing to both slots, disabling verity / verification to expert mode.
Many other improvements, validations and checks.
Updated documentation.
March 24, 2022 v1.2.0.1-alpha release.
Added Advanced Configuration menu which unlocks advanced features such as:
- Flashing to both slots
- Disabling Verity
- Disabling Verification
- (More features to come)
The UI will now display the chosen Android Platform Tool's version.
Added an option to toggle verbose console output (help troubleshooting, more verbosity to come).
Stability fixes.
March 22, 2022 v1.1.5-alpha release.
Some users were having issues with 7zip, add 7z.dll to the bundle.
Add fallback mechanism to use python libraries for unzipping when 7zip fails (it would be slower)
March 22, 2022 v1.1.4-alpha release.
Bug Fix: Handle space characters in paths.
March 17, 2022 v1.1.3-alpha release.
Visual indicator if the phone is root and Magisk Tools is found.
Bug Fix: KeyError 'flash_vbmeta'
March 17, 2022 v1.1.0-alpha release.
Changelog
10x speed improvement for full package creation, down from 180 seconds to 18 seconds.
Bug Fix: When using patch option with custom ROM, the boot.img of the custom ROM is now correctly patched.
Add support for flashing vbmeta (experimental) with or without disabling verity and or verification. (This is currently only supported through preferences file)

Reserved

Is there an option to disable Verity and verification just curious

a g bell said:
Is there an option to disable Verity and verification just curious
Click to expand...
Click to collapse
Very easy to add that, curious what would be the use case?
I'm currently setting KEEPVERITY=true and KEEPFORCEENCRYPT=true
I'm not sure what you mean by disable verification though.

I have recently had problems when flashing factory images. They flash fine for me but will not boot leaving the message your device is corrupted bla bla bla disabling Verity and verification in FB fixes the issue they boot straight up.
I would find the option useful
It's this in fastboot: fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
Of course the using vbmeta.img from what your flashing

a g bell said:
I have recently had problems when flashing factory images. They flash fine for me but will not boot leaving the message your device is corrupted bla bla bla disabling Verity and verification in FB fixes the issue they boot straight up.
I would find the option useful
Click to expand...
Click to collapse
I know how to disable Verity, but how do you disable verification? you know the flag for it?

badabing2003 said:
I know how to disable Verity, but how do you disable verification? you know the flag for it?
Click to expand...
Click to collapse
Sorry l just use fastboot commands

a g bell said:
It's this in fastboot: fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
Of course the using vbmeta.img from what your flashing
Click to expand...
Click to collapse
Just so it is clear.
This would be the normal steps for the latest oriole image
which flash-all does (-w removed to keep data)
Code:
fastboot flash bootloader bootloader-oriole-slider-1.0-8062051.img
fastboot reboot-bootloader
fastboot flash radio radio-oriole-g5123b-93368-211225-b-8029609.img
fastboot reboot-bootloader
fastboot update image-oriole-sq1d.220205.004.zip
Do you extract vbmeta from image-oriole-sq1d.220205.004.zip and then run
Code:
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
as a last step?
or do you just do
Code:
fastboot update --disable-verity --disable-verification image-oriole-sq1d.220205.004.zip
as the last step of flash-all
The two options I gave you are Magisk patching options, so you leave those as default? which would be KEEPVERITY=true and KEEPFORCEENCRYPT=true (That is what the app does)

badabing2003 said:
Just so it is clear.
This would be the normal steps for the latest oriole image
which flash-all does (-w removed to keep data)
Code:
fastboot flash bootloader bootloader-oriole-slider-1.0-8062051.img
fastboot reboot-bootloader
fastboot flash radio radio-oriole-g5123b-93368-211225-b-8029609.img
fastboot reboot-bootloader
fastboot update image-oriole-sq1d.220205.004.zip
Do you extract vbmeta from image-oriole-sq1d.220205.004.zip and then run
Code:
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
as a last step?
or do you just do
Code:
fastboot update --disable-verity --disable-verification image-oriole-sq1d.220205.004.zip
as the last step of flash-all
The two options I gave you are Magisk patching options, so you leave those as default? which would be KEEPVERITY=true and KEEPFORCEENCRYPT=true (That is what the app does)
Click to expand...
Click to collapse
l copied the vbmeta.img then flashed with the disable commands added that was after l had the flashed the ROM of course

badabing2003 said:
Just so it is clear.
This would be the normal steps for the latest oriole image
which flash-all does (-w removed to keep data)
Code:
fastboot flash bootloader bootloader-oriole-slider-1.0-8062051.img
fastboot reboot-bootloader
fastboot flash radio radio-oriole-g5123b-93368-211225-b-8029609.img
fastboot reboot-bootloader
fastboot update image-oriole-sq1d.220205.004.zip
Do you extract vbmeta from image-oriole-sq1d.220205.004.zip and then run
Code:
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
as a last step?
or do you just do
Code:
fastboot update --disable-verity --disable-verification image-oriole-sq1d.220205.004.zip
as the last step of flash-all
The two options I gave you are Magisk patching options, so you leave those as default? which would be KEEPVERITY=true and KEEPFORCEENCRYPT=true (That is what the app does)
Click to expand...
Click to collapse
I would not worry about changing anything on this topic. Your script is using a full factory image and Magisk v24. This extra step was fixed when Magisk v24 was released...
Only the Ota updates are affected and need to be altered.
Basically if you stick to the full factory image and Magisk v24, you can forget about the extras steps.
Edit: this all was discuss in the Pixel 6 rooting guides.

vandyman said:
I would not worry about changing anything on this topic. Your script is using a full factory image and Magisk v24. This extra step was fixed when Magisk v24 was released...
Only the Ota updates are affected and need to be altered.
Basically if you stick to the full factory image and Magisk v24, you can forget about the extras steps.
Edit: this all was discuss in the Pixel 6 rooting guides.
Click to expand...
Click to collapse
Yes but l am not referring to rooting l am referring to downloading and flashing a factory then facing a Verity issue causing the flashed ROM to not boot. Nothing to do with root access.

vandyman said:
I would not worry about changing anything on this topic. Your script is using a full factory image and Magisk v24. This extra step was fixed when Magisk v24 was released...
Click to expand...
Click to collapse
It' true that my tool uses the factory image, but I don't have control over the Magisk version, it uses whatever is installed on the phone.

a g bell said:
Yes but l am not referring to rooting l am referring to downloading and flashing a factory then facing a Verity issue causing the flashed ROM to not boot. Nothing to do with root access.
Click to expand...
Click to collapse
You can use notepad++ and open your flash=all.bat file. Add your own fastboot script at the end.
The verify disable method was only needed to root back in October. There was no reason otherwise to change the flash-all script at all if you were not rooting. I must have overlooked something since then!
Is there a link on this that is new?

a g bell said:
l copied the vbmeta.img then flashed with the disable commands added that was after l had the flashed the ROM of course
Click to expand...
Click to collapse
doesn't the step `fastboot update image-oriole-sq1d.220205.004.zip` reboot to normal when it completes?
So you try to go back to fastboot mode and then flash the vbmeta with disabling options?
That's going to be tricky to automate, if I add the step after the ROM update, it will never get there.
I created a feature branch to add this (no UI, just through preferences file, this way it keeps it away from normal users, besides it complicates the UI and confuses people)
After finishing it all, I realized that the phone will not be in the bootloader mode.
I know that when the Pixel 6 / Pro first came out (Before Magisk handled it), we had to disable verity and verification, but those options were added to the ROM update line, we didn't had to flash vbmeta separately, I wonder if you do that would it work.
Actually like @vandyman why do you still need to do this if you're using the latest magisk?
Something is different on your phone?

@badabing2003 It would be great to have an opthio to disable Verity and verification flags via this UI. It could be an advanced user choice just in case.
It is true that with latest Magisk root, flags are not a matte anymore, but some times the third-party kerenl or other roms will make the phone not boot leaving the message your device is corrupted...

badabing2003 said:
doesn't the step `fastboot update image-oriole-sq1d.220205.004.zip` reboot to normal when it completes?
So you try to go back to fastboot mode and then flash the vbmeta with disabling options?
That's going to be tricky to automate, if I add the step after the ROM update, it will never get there.
I created a feature branch to add this (no UI, just through preferences file, this way it keeps it away from normal users, besides it complicates the UI and confuses people)
After finishing it all, I realized that the phone will not be in the bootloader mode.
I know that when the Pixel 6 / Pro first came out (Before Magisk handled it), we had to disable verity and verification, but those options were added to the ROM update line, we didn't had to flash vbmeta separately, I wonder if you do that would it work.
Actually like @vandyman why do you still need to do this if you're using the latest magisk?
Something is different on your phone?
Click to expand...
Click to collapse
Everytime l downloaded and flashed a factory image it wouldn't boot and gave me the message your phone is corrupted. So l tried to fix it this issue and disabling Verity and verification they way l posted worked and the flashed factory image then booted.So l thought this would be a useful option for you to add.

a g bell said:
Everytime l downloaded and flashed a factory image it wouldn't boot and gave me the message your phone is corrupted. So l tried to fix it this issue and disabling Verity and verification they way l posted worked and the flashed factory image then booted.So l thought this would be a useful option for you to add.
Click to expand...
Click to collapse
Yeah, but that was not my question, I hear you, you have a legitimate need, but I need to know an answer to this
Which you quoted but did not answer.
I'm also curious if you're using the latest Magisk 24301 because that problem should have been addressed by Magisk.
@bush911
Same concern, if the device is not in bootloader mode after applying the ROM, and the device is boot looping, and you have to manually get the phone out of boot loop and reboot to bootloader, then adding the option is kind of moot.
As for UI, is it really necessary? once you add it to the preferences file, it will remember and use it all the time.

badabing2003 said:
Yeah, but that was not my question, I hear you, you have a legitimate need, but I need to know an answer to this
Which you quoted but did not answer.
I'm also curious if you're using the latest Magisk 24301 because that problem should have been addressed by Magisk.
@bush911
Same concern, if the device is not in bootloader mode after applying the ROM, and the device is boot looping, and you have to manually get the phone out of boot loop and reboot to bootloader, then adding the option is kind of moot.
As for UI, is it really necessary? once you add it to the preferences file, it will remember and use it all the time.
Click to expand...
Click to collapse
Yeah sorry my friend using the XDA app it's a nightmaret anyway it completes the flash then just hangs on the your device is corrupted screen. I have been using the flash all .bat as well to flash.

Development [Kernel][14.06.2023][Android 13.0.0 Stable]Kirisakura_Raviantah 1.1.0 for Pixel 7/Pro aka "Pantah"

Kirisakura-Kernel for the Pixel 7/Pro
Hello everyone,
To keep it short: Here is Kirisakura - Kernel for the Google Pixel 7 Pro aka Cheetah and the Pixel 7 aka Panther, together Pantah.
I would appreciate if everybody that flashes the kernel, reads at least once through this opening post and the following ones.
The kernel aims to keep most of the subsystems updated, way ahead of the stock kernel, thereby improving security, stability and performance!
This includes Linux-Stable, F2FS-Stable and kernel/common!
If that got you curious, have a read about linux-stable and why it is important here. The stable-process is not the same for every subsystem, but the general idea, rule of thumb and benefits are applicable for other subsystems as well.
By merging linux-stable regularly we get most security updates months ahead of the stock kernel and also before they even end up in the android security bulletin.
The kernel includes a lot of improvements and contributions from other developers as well. Without those contributtion this kernel would not exist as it is.
A big part of improvements originate from @arter97´s, @kdrag0n´s and @Sultanxda´s work. Many others contributed in some way or another to this kernel.
A big thanks to all of them at this place!
Now lets continue with a list of features in the next paragraph!
Features:
Main Features:
- Based on latest A13 kernel sources from Google, Kernel is made for Android 13 Stable
- Linux-Stable-Upstream included to 5.10.183
- Compiled with prebuilt Google clang 17.0.2
- Backport entire RCU subsystem to linux 6.0
- Lazy RCU which should result in power-savings while the device is lightly-loaded or idling, more information here
- Backport Maple tree from Linux 6.1
- improve preallocations from maple tree (affects especially android)
- reduce necessity to rewalk the maple tree
- Per VMA-locks in conjunction with Maple Tree RCU-Mode (improve app launch time, this feature in general benefits greatly from lazy rcu!)
- further improve maple tree/per-vma locks introduced in an earlier release
- Dynamic Energy Models depending on device state
- make TEO-Cpuidle util-aware (improves latency, performance and decreases energy consumption for certain workloads, more information here)
- improve CPU throttling behaviour
- improvements to uclamp, prevent capacity inversion (reduce missed frames)
- greatly speed up camera launch time!
- merged kernel/common (improvements to android-common-kernel straight from google)
- MM subsystem reworked (more info and some patchsets linked in this post)
- Multi-gen LRU backported/reworked and enabled (more info here, here as well and here) to improve mm and reduce cpu cycles, latest V15 state
- pelt multiplier tied into powerhal to speed up scheduler during interaction (more info here)
- prevent frequency spikes caused by small transient tasks when the device is idle(more info here)
- tie mechanism to prevent frequency spikes caused by small tasks also into powerhal
- scheduler improvements for RT (realtime) tasks
- introduce and setup PMU limiter (prevents CPU from spiking to max when it isn´t needed, based on PMU reads, more information here)
- improve camera performance by tuning the powerhal during recording
- bias tasks of rt, sf and ta groups to prefer high capacity cpus during app launches, interactions
- improve app launches via powerhal
- restrict maximum CPU-Freqs during screen off/ idle to 1.4GHZ for all clusters to save power
- introduce unfair f2fs rwsems to prevent writer starvation and improve IO perf under heavy load
- fuse: give wakeup hints to scheduler to speed up compress/decompress in internal storage (details)
- enable RCU_BOOST (details here), also fix RCU_BOOST behaviour
- F2FS-Stable updated
- merge and enable f2fs block_age-based extent cache (improve the accuracy for data temperature classification, reduce the garbage collection overhead after long-term data updates)
- TCP backports from mainline
- SSG IO scheduler for reduced overhead and less CPU cycles (more lightweight and android optimized)
- scheduler backports from linux-main
- mm updates from linux-main
- locking updates frm linux-main
- improve memory performance by tweaking google´s eh zram implementation
- fix sysfs endpoint for googles eh zram
- affine IRQS to CPU 7 during camera usage for improved performance as it tends to overload the little cores
- use bbr as default TCP congestion algorithm (fasted algo according to this excellent research from @kdrag0n found here )
- include bbrv2 from google, more info here
- Enable support for TTL spoofing
- important patches from kernel/common for 5.10 (here are more details)
- increase priority of GPU work
- several updates from QPR beta, and a few from Pixel 6 that googles missed to include in the pixel 7 kernel
- improve thermals
- change compaction proactiveness based on device state for improveed memory management
- improve ZRAM usage
- reduce overhead
- improve performance and efficiency by properly wiring up pixel_sched with teo util awareness (thanks @ada12 for spotting this!)
- update to cpuset/cgroup subsystem (speeds up camera launches, device unlocks etc as cpusets are switched on those conditions, patches reduce overhead in those conditions)
- flashing the kernel will preserve root
CleanSlate Features
- CleanSlate Features from @tbalden, big applause here! (s2s, notification booster, battery saver, flashlight notifications. Please note: cleanslate features that work otherwise with rooted devices like kadaway (adblocking) are not implemented on this kernel since I´m running rooted)
- Check the CleanSlate thread for more information about those features
- The CleanSlate thread also contains the apps that allows you to control those features!
- If you consider those features useful, maybe consider purchasing the apps in the PlayStore or a small donation to @tbalden, he deserves it! Don´t forget to switch to beta channel for those apps, as this is needed for device running A13!
Various Optimizations:
- update several drivers to use power efficient workingqueues (for example wlan driver)
- f2fs: reduce timeout for uncongestion
- f2fs: Demote GC thread to idle scheduler class
- f2fs: set ioprio of GC kthread to idle
- tcp: enable advanced tcp, give user more options for tcp alorithm
- mm: vmstat: use power efficient workingqueues
Wakelock Blocker:
- advanced wakelock blocker with the ability to block kernel wakelocks (dangerous, use with caution, please read this for further info). You should only block kernel wakelocks in case you face uncontrollable scenarios, like company wifi causing a wakelock to be active 100% of the time! Blocking kernel wakelocks to "improve" battery life almost always backfires and causes issues!
Powerhint Module:
- restrict little cluster to 1,4ghz mid cluster to 1,4ghz and big cluster to 1,4ghz during screen off, to reduce battery usage for example during music playback
- only use little cores during screen off/device suspend
- account for scheduler and other changes done to the kernel
- boost memory interface controller during interaction (decreased missed frames, improved soc efficiency according to google docs)
- tie pelt multiplier into the powerhal (more info here)
- prevent frequency spikes caused by small transient tasks during idle operation (more info here)
- boost scheduler using the pelt multiplier during fingerprint unlock operation
- setup and control PMU limiter via powerhal (more info here)
- switch between default and custom idle energy model on device is being interacted with / device idle.
- reduce missed frames during scrolling/device interaction by adjusting uclamp boosts
- dynamically adjust target load for memory interface during interaction.
- remove dynamic GPU policy change as it´s causing instability and is unneeded due to GVFS period
- implement handling during video recording of CPU like Google did on QPR A13
- more small improvements
DOWNLOAD:
Downloads are attached to the release posts linked below in the changelog section.
Please note that androidfilehost is currently not working properly.
Link to AFH:
Spoiler
Deprecated afh download, still here for old releases:
https://www.androidfilehost.com/?w=files&flid=336658
Changelog:
Android 13.0.0 Stable (not QPR beta!)
1.0.0 Initial Release | Mirror for Download in case AFH is not working
1.1.0 https://forum.xda-developers.com/t/...-pixel-7-pro-aka-pantah.4509795/post-87743627
1.2.0 https://forum.xda-developers.com/t/...-pixel-7-pro-aka-pantah.4509795/post-87822161
1.2.1 https://forum.xda-developers.com/t/...-pixel-7-pro-aka-pantah.4509795/post-87878321
1.2.2 https://forum.xda-developers.com/t/...-pixel-7-pro-aka-pantah.4509795/post-87944505
1.2.3 https://forum.xda-developers.com/t/...-pixel-7-pro-aka-pantah.4509795/post-87960183
1.2.4 https://forum.xda-developers.com/t/...-pixel-7-pro-aka-pantah.4509795/post-88108123
1.3.0 https://forum.xda-developers.com/t/...-pixel-7-pro-aka-pantah.4509795/post-88286027
Raviantah_1.0.0 https://forum.xda-developers.com/t/...-pixel-7-pro-aka-pantah.4509795/post-88316285
Raviantah_1.0.1 https://forum.xda-developers.com/t/...-pixel-7-pro-aka-pantah.4509795/post-88323527
Raviantah_1.0.2 https://forum.xda-developers.com/t/...-pixel-7-pro-aka-pantah.4509795/post-88399915
Raviantah_1.0.4 https://forum.xda-developers.com/t/...-pixel-7-pro-aka-pantah.4509795/post-88497279
Raviantah_1.1.0 https://forum.xda-developers.com/t/...-pixel-7-pro-aka-pantah.4509795/post-88645103
Requirements
- vbmeta flags for verity/verification disabled (this requires a wipe if you´re coming from stock with those flags enabled), check the FAQ for information on how to do this
- unlocked Bootloader
- USB-Debugging in developer options enabled
- latest adb and fastboot binaries
- working adb and fastboot environment so you can flash back to stock in case something goes wrong
- working magisk environment (a device rooted with latest magisk, use stable in case you want to be absolutely safe)
- IMPORTANT: Unrelated to the kernel, but update both slots of your phone to A13 before you flash anything to your device!
- it´s handy to have a backup and a way to return back to stock (check the faq for that)
- make sure to download the correct kernel version for your firmware. (you can´t flash a kernel made for stable firmware on a QPR beta or dev preview and expect there to be no isses, the release posts mention which firmware the respective kernel releases are compiled for)
- this kernel is tested on stock google firmware. If you want to use it on custom roms you´re kind of on your own as I can´t account and give support for any changes custom roms apply that could render the kernel incompatible. (e.g. if you´re custom rom is still on the previous months update, there may be issues flashing an updated kernel for the next month on top or custom roms requiring specific kernel changes to work correctly )
- it´s always best to start on stock images and don´t have another custom kernel flashed when flashing this kernel for the first time. consecutive flashes can just be installed on top, if not I´ll mention it in the release post
- read the first and second post, there's a lot of valuable information
How to flash the Kernel:
1a. Make sure you tick all the requirements above
1b. Make sure to flash the release made for your firmware! Usually the release post contains information on that
1. Download the kernel.zip (unified for both devices) and the correct powerhint module depending on your device (Pixel 7 = panther || Pixel 7 Pro = cheetah)
2. Flash the powerhint module via magisk manager as you would any other magisk module! Make sure to flash the latest one. It will be mentioned in the release post if there´s an update.
3. Flash the kernel.zip via EXKM, FKM or kernel flasher. Root will be preserved.
4. Reboot and profit.
Donations:
Donations are not mandatory but very welcome if you want to support development or just buy me a coffee/tea/beer
If you like my work: http://paypal.me/freak07
Credits:
@osm0sis for all his work on AK3.
@tbalden for being the best HTC, Pixel, OnePlus and Asus wingman!
@capntrips for all his work on the pixels, avb, hashtree patcher, the counsel and the kernel flasher!
@LeeDroid and @mwilky for their awesome roms and work I used on multiple devices!
@Captain_Throwback for all the mentoring and guidance!
@Eliminater74 for bringing me into the game and the Inspiration
@nathanchance for his upstream guidance and assistance
@RenderBroken for helping me out
@flar2 for all his work
@joshuous for all the help he provided to me in the past!
@arter97 for giving me advice
@kdrag0n for his help and advices!
@topjohnwu for magisk and his entire work!
Source Code: https://github.com/freak07

F.A.Q:
Question: How do I check the state of avb flags for verity/verification on my phone?
Answer: Check @capntrips post here and get the magisk module for this from here. After flashing the magisk module reboot your phone. You can now use the commands from @capntrips post to check.
Question: How do I update my phone to a new monthly update if this kernel is installed?
Answer: The easiest solution is to just use any full firmware package to update your phone to the new stock firmware. You can do so with the android web flash tool, a factory image or a full OTA image.
An excellent guide on how to use the factory image to do so was posted by @roirraW "edor" ehT on this thread. Feel free to use this as a reference.
I also posted what I do each month to update my phone here.
This also serves as the easiest way to return back to stock, if you don´t like the kernel and feel not comfortable flashing anything via fastboot.
Just remember to disable verity/verification vbmeta flags each time you update your phone as described in the next question below.
If you boot once, without them disabled a wipe is required to disable them again.
Question: How do I disable the vbmeta flags for verity/verification?
Answer: The easiest solution is to use the android web flash tool and tick the correct checkbox.
Alternatively extract the vbmeta.img from the matching factory image and flash it in fastboot via:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Please note that disabling those flags will require a full wipe for the device to boot if coming from flags enabled state!
And a further note: You need to repeat this command every time you flash a full firmware zip ( a factory image or a full OTA.zip) to update the firmware of your phone as those contain a vbmeta image. Otherwise the flags will be reset to default enabled and it will require another wipe to disable them again! As with the firmware.zips, you need to tick the checkbox in the webflasher every month you update your phone or flash a firmware there!
Question: How do I return back to stock?
Answer: Extract boot.img, dtbo.img, vendor_kernel_boot.img and vendor_dlkm.img from the matching factory image provided on googles download page.
Flash those images via fastboot/fastbootd and you will be back on stock kernel. If you don't know the fastboot commands to flash the images, check the instructions how to flash those images in post #4.
Alternatively dirty flash the whole firmware without wiping by using either the android web flash tool, a factory image or a full OTA image. If you disabled the vbmeta flags, don't forget to disable them again (or tick the correct options on the web flash tool) after flashing a full firmware package and re-root.
Kernel flasher has the capability to backup those partitions as well, but if your phone doesn´t boot, because you flashed a kernel for stable firmware on dev preview that backup will not help you.
Question: Does this kernel include a mod similar to the well known KCAL modification?
Answer: No it does not, as KCAL is tapping into a QCOM specific driver and that´s not included in the tensor source as it´s based on exynos.
There´s a very powerful app called CF Lumen from @Chainfire, that serves the same purpose and even includes far more options that were available from kernelspace. Link to the thread here.
Question: How to report bugs properly?
Answer: Have a look at post #3 in the linked thread. The linked guide is a pretty good starting point.
Before reporting any bug make sure you´re running on a supported firmware. Usually I'm announcing in the release post, the firmware the kernel.zip is compatible with, but most of the time the kernel is updated when a firmware update drops.
Please make also sure you're running a stock configuration.
That´s means you´re not using any mods, tweaks in kernel managers or other root tweaks , magisk modules, xposed/lsposed etc, scripts or other modifications that alter various functions like sound mods, data traffic, sleeping behaviour, scheduler, magical battery tweaks etc.
Try to describe the issue as detailed as possible! Give your exact setup, like rom, magisk version, kernel version.
Is the issue reproducible? Does it happen frequently?
Please make sure to meet the points described above, provide logs as detailed in the link above, otherwise debugging is a lot more time consuming and harder. (kernel flashing apps usually support exporting logs of flashes too) If these requirements aren´t met and I don´t find time to either reproduce the issue myself or I´m not able to reproduce the issue myself, reports might just be ignored. If you can already reproduce the issue and provide logs it greatly limits the amount of time I have to spent until I figure out how to reproduce it.
Question: What about unlocking, rooting, passing safetynet, apps detecting root/modifications and other topics that are vaguely related, but not really subject of this thread?
Answer: If you want to modify your phone via root/magisk in any way you need to unlock the bootloader. Unlocking will result in safetynet not passing. This has nothing to do with the kernel. At the moment of writing this, safetynet not passing can be worked around with a magisk module called "Universal SafetyNet Fix".
Not passing safetynet is unrelated to the kernel since hardware attestation is enforced on nearly all newly released devices now.
If you´re not passing safetynet banking apps might for example be detecting root. There are various tricks to hide root/modifications to the phone from banking apps or others but that´s not really subject of this thread.
I recommend taking a look at this excellent collection of helpful threads from @roirraW "edor" ehT!
It can be found following this link!
Question: I get a device corrupted message after flashing the kernel or just reboot to bootloader. How to get rid of it?
Answer:
There seems to be an issue with verity on Pixel devices that can trigger randomly. That means even if the expected hashes match the device refuses to boot due to this bug.
Short answer, flash magisk patched init_boot.img via fastboot, afterwards flash stock init_boot.img. That should clear this situation.

AOSP Build Environment and Standalone Kernel builds (monolithic builds)
I´m sure some of you followed the movement towards the Generic Kernel Image (GKI) and Qcoms adaption to it called QGKI.
You can find more information about GKI following this link.
What does that mean for custom kernels and this custom kernel?
The last few years the kernel on android devices was more or less compiled as a monolith. That means the kernel is in the zImage with all (most) drivers compiled inline.
However with GKI this changed. There´s the base kernel image while vendor/device specific drivers are compiled as dynamically loadable kernel modules.
On last years devices like the Pixel 5 (using a 4.19 kernel) and this years devices with SD888 on a 5.4 kernel base, there was the possibility to change the QGKI kernel back into a monolithic kernel image. (building the drivers that are on stock kernel external modules back into the zImage to end with a monolithic kernel)
On the Pixel 6 I wasn´t able to achieve this yet. Same goes for the Pixel 7. But during my tries I also wondered if maybe finally the time has come to follow suit, instead of trying to enforce old ways, when there´s a new way going forward.
What does that mean. This means that at this point the kernel is shipped as images that are to be flashed via fastboot. At a later stage I´m sure we can modify anykernel3 to allow flashing zips again, but at this early stage fastboot flashable images will be provided.
Those images can be flashed the same way the device is rooted, therefore I think everybody should be able to flash it easily since the device can´t be rooted any other way.
The kernel was compiled using the aosp kernel build environment. Information about it can be found on the documentation page from google.
This kernel needs to be compiled in the aosp kernel build environment just like the stock kernel. All necessary and modified repos are available on my github. Otherwise please refer to the aosp build environment and the instructions there.

Fastboot commands:
This serves just as a reference to restore the images via fastboot. This is not to install the kernel.
Flash the images in this order:
Boot to bootloader:
Either select Reboot to bootloader option via magisk manager, use the button combinations or run the following command while in the OS:
or type:
Code:
adb reboot bootloader
Now in fastboot flash boot.img, dtbo.img and vendor_kernel_boot.img
Commands:
Code:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vendor_kernel_boot vendor_kernel_boot.img
Now boot to fastbootd
Code:
fastboot reboot fastboot
Once in fastbootd:
Code:
fastboot flash vendor_dlkm vendor_dlkm.img
4. Reboot either via buttons
or by typing
Code:
fastboot reboot
5. Profit!

Prebuilts for custom roms.

last one I promise

So glad to see you here

Woowoo, let's GOOOO

Kiri is here! Thanks for this awesome kernel!

So unfortunately we´re at the moment out of ideas and options for the vbmeta verity/verification disable requirement. @tbalden and me tried a few things and failed with our final idea this morning, which worked on a similar device.
Maybe somebody finds a way so we can actually flash custom images with the avb/vbmeta flags enabled, but at the moment not. I didn´t want to delay the release any further so here we go.
I understand this is a pain for many, but unfortunately that´s how it is now. It was a pain for me too, because on the final test, we really hoped it would work, but we we´re trapped in the wipe ourselves.
Anyway, have fun everyone with the release. It basically includes everything from the Pixel 6 kernel, as they branches are similar.

Well this is awesome. Haven't modified my phones since Pixel 4 but this is very enticing

This made me smile. Loved your kernel on the P6P. So glad to see it available for my P7P.
QQ: Is High Brightness Mode (HBM) supported in this kernel?

nice to see you on here
I do hope its a firmware issue and next month update fixes issue and then workaround you guys been testing for flashing without disabling verity and verification works

@Freak07
Thank You very much for this kernel!
May I ask if this one from CleanSlate is included? How is this works?
VoLTE call properties patched in - no root/magisk needed for non supported carriers/countries and VoLTE calls.

Duuuuude! This kernel sounds amazing. And the Powerhint module? WHAT?!
Probably moving to the 7 Pro this weekend so this is very welcome!
Thanks
Edit: I'm a little confused: should we flash the zip as usual through EXKM/Kernel flasher or use the fastboot commands from post #4??
Because the OP also mentions the usual way of flashing...

Very excited for the kernel, thanks for your hard work!

Ghisy said:
Duuuuude! This kernel sounds amazing. And the Powerhint module? WHAT?!
Probably moving to the 7 Pro this weekend so this is very welcome!
Thanks
Edit: I'm a little confused: should we flash the zip as usual through EXKM/Kernel flasher or use the fastboot commands from post #4??
Because the OP also mentions the usual way of flashing...
Click to expand...
Click to collapse
I think that was just a copy and paste from the older P6 thread (also now deprecated for that device, from what I understand). Just use EXKM or Kernel Flasher and you'll be good to go!
Edit: and the companion zip in Magisk Manager. Whoops. In other words, you don't need to manually flash each image to install the kernel.

i5lee8bit said:
I think that was just a copy and paste from the older P6 thread (also now deprecated for that device, from what I understand). Just use EXKM or Kernel Flasher and you'll be good to go!
Click to expand...
Click to collapse
Nope,
The powerhint module was never actually depreciated, on P6 he was able to have it included in the kernel zip and it auto-installed into magisk at the same time.
That isn't working here at the moment so you have to manually flash it yourself again

i5lee8bit said:
I think that was just a copy and paste from the older P6 thread (also now deprecated for that device, from what I understand). Just use EXKM or Kernel Flasher and you'll be good to go!
Click to expand...
Click to collapse
Sorry, maybe I wasn't being clear: should I use quote #1 or #2 down there?
Freak07 said:
How to flash the Kernel:
1a. Make sure you tick all the requirements above
1. Download the kernel.zip (unified for both devices) and the correct powerhint module depending on your device (Pixel 7 = panther || Pixel 7 Pro = cheetah)
2. Flash the powerhint module via magisk manager as you would any other magisk module
3. Flash the kernel.zip via EXKM, FKM or kernel flasher. Root will be preserved.
4. Reboot and profit.
Click to expand...
Click to collapse
Freak07 said:
Fastboot commands:
Flash the images in this order:
Boot to bootloader:
Either select Reboot to bootloader option via magisk manager, use the button combinations or run the following command while in the OS:
or type:
Code:
adb reboot bootloader
Now in fastboot flash boot.img, dtbo.img and vendor_kernel_boot.img
Commands:
Code:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vendor_kernel_boot vendor_kernel_boot.img
Now boot to fastbootd
Code:
fastboot reboot fastboot
Once in fastbootd:
Code:
fastboot flash vendor_dlkm vendor_dlkm.img
4. Reboot either via buttons
or by typing
Code:
fastboot reboot
5. Profit![/SPOILER]
Click to expand...
Click to collapse

Ghisy said:
Sorry, maybe I wasn't being clear: should I use quote #1 or #2 down there?
Click to expand...
Click to collapse
The fastboot commands are for if or when you want to return to stock.

Development [ROM][13][CHEETAH] Discontinued Official crDroid v9.5 EOL

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/13.0/README.mkdn
Flashing Instructions:
Pre-installation:
[*]Gapps Included
[*]Magisk 25.0 or newer for root (after first boot) - (Download from here)
First time installation:
Only for Official builds moving forward!!!!
Flash May Firmware from Web Flash Tool
Reboot to Fastboot
Unlock bootloader
Go thru first boot
reboot to bootloader
in cmd enter fastboot set_active other
repeat step 1
Reboot to Fastboot
fastboot flash vendor_boot vendor_boot.img in fastboot (located here)
Reboot to Recovery
Select adb update
Open cmd and type adb sideload rom_name.zip
DO NOT FLASH GAPPS, THEY ARE INCLUDED
Update installation:
OTA or
download rom zip, reboot to recovery, adb update, adb sideload rom zip
Sources:
ROM: https://github.com/crdroidandroid
Kernel: https://github.com/crdroidandroid/android_kernel_google_pantah
Download:
ROM: Download
Changelog: https://crdroid.net/cheetah/<9.3>#changelog
Known issues:
Verizon Wifi Calling
Visit official website @ crDroid.net
crDroid Community Telegram
crDroid Updates Channel
Donate to help our team pay server costs

Changelog:
Official build is live!!
===== 22 May, 2023 =====
- Resync Rom Source
- Fix SafetyNet Again (thank You Pixel-Dust)
- Fix the memory leak during high speed recording
- SystemUI: Import more QS Header resources
- SystemUI: Hide notification icon area if headsup is visible
- Messaging: Use light icons on conversations select menu
- Launcher3: Corrected some permissions
- Some other small Launcher3 changes
- Configure font spacing for various clock fonts
- Added double-line clock position setting
- Added lockscreen text size settings
- Moved lockscreen clock customization to lockscreen settings
- Updated bionic
- Fixed system crash if font contains invalid/null font data
- Fixed not setting proper call volume for LE Headset
- Fixed an issue where device asks for PUK code instead of SIM PIN
- Removed colorkt and themelib support
- Some small SystemUI changes and optimizations
- Updated Aperture
- Updates to bionic, libcore, freetype, giflib and libhevc
- Updated Webview to 113.0.5672.77
- Updated translations
==== 05 May, 2023 =====
=== Rom Source ===
- Initial crDroid 9.5 release
- Updated to May 2023 security patches (android-13.0.0_r43)
- Added pixel style lockscreen weather based OmniJaws
- opengl: fix resource leak when dlsym failed
- Switch latest clang to 17.0.1
- Updated themed icons
- Updated translations
- Allow pause/suspend app feature with parallel space
- Settings: Expose radio info (*#*#4636#*#*)
- Added QS Header Image option
- Wallpaperpicker: fix overlapping when scrolling
- WallpaperPicker2: Remove the use of smaller images for thumbnails
- Updated libvpx, bionic
- Updated translations
- Add a toggle to force LTE_CA
- Added back 2 button navigation
- Fixed/Reworked switch to unlink ringtone and notifications volume
- Fixed process can't start because of mPendingStart is true problem
- Fixed SystemUI restart due to network traffic meter
- NetworkTraffic: Simplify stats calc to prevent issues
- PixelPropsUtils: Spoof user build
- Settings: Show memory usage in app info
- SystemUI: Rework dismiss all view in QS
- SystemUI: Handle more exceptions for firewall
- Prevent crash with pin protected user and taskview
- Fix hang when dumping local window
- Updated Webview to 112.0.5615.136
- Updated bionic, lmkd, sqlite
- Updated translations
=== Device ===
May Security Patch
New Kernel: MadKali thanks @Duhjoker
Removed Scrolling Tweaks/Fix Lags
===== 24 April, 2023 =====
-Resync Rom Source
-Qs Header Images
-Fix Safetynet OOTB
-Fixed NGA
-Other Tweaks and Optimizations
04/19/23
===== 19 April, 2023 =====
=== Rom Source ===
- Initial crDroid 9.4 release
- Updated to April 2023 security patches (android-13.0.0_r41)
- Resync Rom Source
=== Device ===
-Added Pixel-Framework
-Added Pixel 7 Pro Exclusive Features
-Clear Calling
-Quick Tap
-Now Playing
-Adaptive Charging
-Reverse Charging

04/11: Updated Initial Flashing instructions to make sure you that march firmware on both slots.
04/11: initial instructions updated again for official builds soon.
04/12: official build is live!!

omariscal1019 said:
Changelog
Click to expand...
Click to collapse
Hi,
Cheers for making it official
Is clean flash needed coming from your previous builds?
Thanks...
Sébastien.
PS: download links is not valid yet? Device is not listed on the website.

Panther going official too?

5.1 said:
Hi,
Cheers for making it official
Is clean flash needed coming from your previous builds?
Thanks...
Sébastien.
PS: download links is not valid yet? Device is not listed on the website.
Click to expand...
Click to collapse
its a place holder still waitnig on a few things and no dirty flash is ok but its the same build as on my gdrive

Best rom ever made for Pixel 7 Pro, thank you for your hard work.

Welcome and Congrats for official !

stompysan said:
Panther going official too?
Click to expand...
Click to collapse
probably yeah

Builds are live same build as 04/07

This Dev is on Point and is building some of the finest Roms I've used. Thank you Dev for bringing this wonderful build to us

Great!
This is truly the Best Rom Ever, as displayed in the launcher.
It is a pleasant surprise to see this go official so soon.
This is the smoothest Rom for our device so far, out of various Roms I have tried, yet feature rich and quite customizable too. Battery life is way better than stock too (thanks in part to Kiri kernel for that too), among various other things.
Thanks again for all your time and effort.

i would love to try this out but included kiri kernel means we need to root and flash powerhint module...unless you found a way to include this with ROM
i need to run unroot for my work app.
wish it had radioactive kernel as default.

[email protected] said:
i would love to try this out but included kiri kernel means we need to root and flash powerhint module...unless you found a way to include this with ROM
i need to run unroot for my work app.
wish it had radioactive kernel as default.
Click to expand...
Click to collapse
Actually running better without the Powerhint module...
Give it a try..im also running unrooted

Question, the phone vibrates every time is locked, in my pocket and on movement (like walking). Very short vibrations like when the phone gets unlocked. When it is standing still, it does not happen. Why is it happening?. Running crDroid 9.3.

[email protected] said:
i would love to try this out but included kiri kernel means we need to root and flash powerhint module...unless you found a way to include this with ROM
i need to run unroot for my work app.
wish it had radioactive kernel as default.
Click to expand...
Click to collapse
U can disable verity/verification and flash radioactive or anything else u like. I root and flash mentioned above.. Running amazing.

SirRhor said:
Question, the phone vibrates every time is locked, in my pocket and on movement (like walking). Very short vibrations like when the phone gets unlocked. When it is standing still, it does not happen. Why is it happening?. Running crDroid 9.3.
Click to expand...
Click to collapse
Enable "pocket detection"

I have tried to install this rom so many times from february to today but i havent got it correct ones can anybody help me please? if any one of you succed i can make a Paypal donation to you!

95an said:
I have tried to install this rom so many times from february to today but i havent got it correct ones can anybody help me please? if any one of you succed i can make a Paypal donation to you!
Click to expand...
Click to collapse
How are you flashing? Make sure you start with fresh base flash from Google flash page with latest image. This ROM doesn't say what security patch it's based off of yet so you have to wait and see .. usually what I do, is flash factory firmware from Google flash page, plug in my phone , select disable verity and flags, flash straight thru, once it finished flashing and phone boots up, I then flash vendor boot via fastboot flash vendor_boot ( vendor location ).img once it says successful in fastboot screen in cmd I reboot to recovery, i go into update - via adb and select flash via adb - once it goes into adb mode in recovery I go on PC and run adb sideload lineagexxxx.zip and allow to flash... Takes about 3-5 minutes ... Once I get status 0 I reboot into recovery again, apply update via adb, and flash gapps , and once they complete, I reboot to system, once I see system boot up successfully, I then rebooted into recovery and sideload adb magisk. It patches the boot.img and once I get status ∅ I reboot and set up. Once I'm done setting up and land in homescreen I go into magisk and >> install >> direct install and then reboot. You will get " magisk has to do something blah blah blah, ignore the message and direct install and then reboot. Mind you this is just in case. Once it reboots I go back into magisk and see that it shows latest installed magisk version and set up from then on. You will need some of these modules , although I advise installing all the ones shown... I personally configure deny list as such in the picture... Reboot and Google pay works and cts passes. Good luck.

So ahh
I can slap this on a Pixel 7, riight...
Any word on a Pixel 7 version
Thanks for your hard work.

Database Info

welcome