sorry for the noob question : how can I flash OTA over this kernel (w/o root)? Sideload OTA -> then flash the kernel again?
Thanks!
Thanks!
Anyone?sorry for the noob question : how can I flash OTA over this kernel (w/o root)? Sideload OTA -> then flash the kernel again?
Thanks!
1. sideload ota from ADBsorry for the noob question : how can I flash OTA over this kernel (w/o root)? Sideload OTA -> then flash the kernel again?
Thanks!
Can I flash this on top ofAndroid T stable 13 - Dec qpr1 updates
- update: latest google sources
- adblock hosts file updated
CleanSlate T 1.4.3 Downloads:
Android T images zip (tp1a 2022-12-05)
Pixel7/pro (not flashable, contains images) CS 1.4.3: https://forum.xda-developers.com/attachments/cleanslate-pantah-images-221205-011-143-zip.5779343/
Magisk with Kernel manager installation
If using a kernel manager like Kernel Flasher, EXKM or FKM, here's an anykernel installer zip.
If you did manual (fastboot) flashing earlier before trying to install this, then this method will most likely fail at flashing vendor_dlkm as a manual fastboot flash resizes the partition to a likely smaller one and this won't fit. If you did that, you'll need to flash back to stock/magisk and only then use this installer zip.
Kernel installer zip for P7Pro/P7 (cheeta/panther) 1.4.3 (use with kernel flasher/EXKM,FKM): https://forum.xda-developers.com/attachments/cleanslate-pantah-1-4-3-zip.5779345/
Read first post in thread for installation details.[/color]
No, the kernel only can do the volte trick
If you flash all the partitions in the zip, I think you don't need to revertCan I flash this on top of
Kirisakura kernel or do I need a revert back to stock before flashing
So I have to do it manually and not use one of the Kernel installers?If you flash all the partitions in the zip, I think you don't need to revert
Most likely yes, as the dlkm partition, when installed manually like on Kiri, will be resized and then the ak3 flasher will fail when the dlkm partition doesn't fit any more. Stock vendor dlkm size is by default somewhat bigger and manual flashing will resize it.So I have to do it manually and not use one of the Kernel installers?
I don't know the commands for flashing each partition is there a guide that I can follow?If you flash all the partitions in the zip, I think you don't need to revert
- Update - 1.4.4 -Android T stable 13 - Jan updates
- update: latest google sources
- adblock hosts file updated
Thanks master![]()
I dirty flashed my february update via ADB commands, so I think your warning in red pertains to my situation. So I need to fastboot flash the stock init_boot.img (unroot my device), flash zip at the link above (https://forum.xda-developers.com/attachments/cleanslate-pantah-1-4-5-zip.5837137/) with EX Kernel manager, and re-fastboot flash the magisk-patched februrary init_boot.img to regain root? Is the zip in the link the same as the files zip and img file you attached to the post? Is the zip file when flashed through EX Kernel manager the only file I need to worry about?- Update - 1.4.5 -Android T stable 13 - Feb updates
- update: latest google sources
- adblock hosts file updated
CleanSlate T 1.4.5 Downloads:
Android T images zip (tp1a 2023-02-05)
Pixel7/pro (not flashable, contains images) CS 1.4.5: https://forum.xda-developers.com/attachments/cleanslate-pantah-images-230205-002-145-zip.5837115/
Magisk with Kernel manager installation
If using a kernel manager like Kernel Flasher, EXKM or FKM, here's an anykernel installer zip.
If you did manual (fastboot) flashing earlier before trying to install this, then this method will most likely fail at flashing vendor_dlkm as a manual fastboot flash resizes the partition to a likely smaller one and this won't fit. If you did that, you'll need to flash back to stock/magisk and only then use this installer zip.
Kernel installer zip for P7Pro/P7 (cheeta/panther) 1.4.5 (use with kernel flasher/EXKM,FKM): https://forum.xda-developers.com/attachments/cleanslate-pantah-1-4-5-zip.5837137/
Read first post in thread for installation details.[/color]
The warning is for the case when you manually flashed the custom kernel vendor dlkm image from fastbootd.I dirty flashed my february update via ADB commands, so I think your warning in red pertains to my situation. So I need to fastboot flash the stock init_boot.img (unroot my device), flash zip at the link above (https://forum.xda-developers.com/attachments/cleanslate-pantah-1-4-5-zip.5837137/) with EX Kernel manager, and re-fastboot flash the magisk-patched februrary init_boot.img to regain root? Is the zip in the link the same as the files zip and img file you attached to the post? Is the zip file when flashed through EX Kernel manager the only file I need to worry about?
I apologize. Brain dead moment. This is a kernel update. I was thinking this was an update for the cleanslate companion and/or config app. oops!!!The warning is for the case when you manually flashed the custom kernel vendor dlkm image from fastbootd.
If after that you have manually updated with the OTA with adb sideload then it isn't a warning for that case, as that will reset the vendor dlkm partition size to a bigger one where cleanslate kernel from EXKM or Kernel flasher will fit in.
So if you didn't explicitly flash the cleanslate (or other kernel) from fastbootd then you can ignore this warning. And even if so, an OTA sideload will set the bigger stock vendor_dlkm size at flash time which will work.
Apps should work fine in that combination.
I'll try to come up with a new ak3 zip that should actually work with fkm and kernel flasher as well.
Apps should work fine in that combination.Has anyone tired the kernel on Ancient OS?
Was hoping to use the kernel flasher in FKM but i can see from the previous messages that it wont go well? also bought a copy of the kernel config app on playstore, will it play nice with the free service app from here?
Can you please share the info page, what's the device name it detects? Seems like the device have doesn't fit with stock naming under lineageWhy don't I have Battery Saver mode?
P/s: I use lineagesOS 20.0
![]()
[dev.mnt.blk.product]: [sda30]Can you share the outcome of this command?
It seems like your device or model name might be modified by magisk?
Code:adb shell $ getprop | grep product
Thanks
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
Thanks, I also had the idea if that it doesn't work out, then I'll upload it here, so I just did that here (I'll link it in the original post as well).There you go! I hope @tbalden is okay with this? If not I'll delete quickly.