Development [KERNEL] [blu_spark r65] [A12L]

[c19932]

hey guys I really need some help here

I recently installed the Jan update on my pixel 6, rooted with magisk. I then installed this kernel through FKM. Now I can't get my pixel 6 to boot. When I restart, it tells me my device is corrupt. I press power to continue, and it still gets stuck at the "google" splashscreen. I can't even access recovery.

I really don't feel like wiping and reinstalling every app. If anyone has any idea how to boot again please let me know.

I tried reflashing a factory image, but when it gets to "system", it tells me system partition not found.

EDIT: it seems like flashing this kernel via FKM on Jan build will mess up the partitions.
On my active slot, system partition can't be find.
On my inactive slot, system partition is too small to "fastboot flash system"

I don't even know how to unbrick my pixel 6 at this point

 

[bobbarker2]

hey guys I really need some help here

I recently installed the Jan update on my pixel 6, rooted with magisk. I then installed this kernel through FKM. Now I can't get my pixel 6 to boot. When I restart, it tells me my device is corrupt. I press power to continue, and it still gets stuck at the "google" splashscreen. I can't even access recovery.

I really don't feel like wiping and reinstalling every app. If anyone has any idea how to boot again please let me know.

I tried reflashing a factory image, but when it gets to "system", it tells me system partition not found.

EDIT: it seems like flashing this kernel via FKM on Jan build will mess up the partitions.
On my active slot, system partition can't be find.
On my inactive slot, system partition is too small to "fastboot flash system"

I don't even know how to unbrick my pixel 6 at this point

Flashing the kernel did not mess up your system partitions, you must have done something out of order or wrong.

What are the step by step procedures you took? Are you on Magisk Canary?

To get your device booting again follow the instructions in OP about returning to stock.

 

[Dillonjaf]

blu_spark_r45 (A12)

New build is up!

Build is unified for raviole, should work both on Pixel 6 (tested) and Pro variant.
You can use FKM download kernel feature, just import the link bellow in the app flash section.
FKM download config: HERE


Changelog:



Keep in mind: I will give no active support for custom ROMs (including stock based ones).
I am mostly interested on debugging stuff in stock ROM (with logs and reproducible steps to replicate the issue).


No mirrors please
Don't forget to hit thanks, it's free

Are CIFS and NFS modules not yet included with the kernel?

Not sure how I would check

Cheers

 

[eng.stk]

Are CIFS and NFS modules not yet included with the kernel?

Not sure how I would check

Cheers

Nope not yet. Will try to remember for the next build

 

[Hecke92]

hey guys I really need some help here

I recently installed the Jan update on my pixel 6, rooted with magisk. I then installed this kernel through FKM. Now I can't get my pixel 6 to boot. When I restart, it tells me my device is corrupt. I press power to continue, and it still gets stuck at the "google" splashscreen. I can't even access recovery.

I really don't feel like wiping and reinstalling every app. If anyone has any idea how to boot again please let me know.

I tried reflashing a factory image, but when it gets to "system", it tells me system partition not found.

EDIT: it seems like flashing this kernel via FKM on Jan build will mess up the partitions.
On my active slot, system partition can't be find.
On my inactive slot, system partition is too small to "fastboot flash system"

I don't even know how to unbrick my pixel 6 at this point

Did you find a solution mate?

 

[bobbarker2]

@nguyenson91hp Your attachment shows checking off Google Play Services components in the Zygisk denylist. However USNF removes Google Play Services from the denylist automatically.

magisk: Remove Play Services from DenyList earlier · kdrag0n/[email protected]

This ensures that GMS will never start before it's removed from the DenyList, even if another module's service.sh is blocking our script. Suggested-by: osm0sis <[email protected]>

github.com

You'll notice on reboot that GPS in the denylist if you have USNF installed.

 

[bobbarker2]

Nope not yet. Will try to remember for the next build

Haptic Feedback control/strength? I was using my Pixel 4a for a bit and was really surprised by how much weaker the Haptic Feedback is on the 6 by default.

Btw I think its funny how everyone still says " hit Thanks on my post" but its "Like" now, since XDA changed their forums a while ago.

Edit: Weird, I flashed the kernel in FKKM and now it will only go to Fastboot with "Enter reason: boot failure". I saw FKKM patch vendor_boot and vendor_dklm. Now I have to "return to stock" and flash the magisk patched boot.img again.

I updated to January by downloading the entire update and doing a flash-all.bat without the -w flag.

I booted once into stock then rebooted to fastboot and did a fastboot flash boot magisk_patched_boot.img. Everything was working fine, root achieved and safetynet passing. Went into FKKM, downloaded the latest version of the kernel and flashed it/rebooted. Now I'm stuck in Fastboot mode.

Did I miss a step? I've always updated like this in the past.

 

[eng.stk]

Haptic Feedback control/strength? I was using my Pixel 4a for a bit and was really surprised by how much weaker the Haptic Feedback is on the 6 by default.

Btw I think its funny how everyone still says " hit Thanks on my post" but its "Like" now, since XDA changed their forums a while ago.

Eventually, I'm actually quite satisfied with the 3 levels provided by userspace, so it's not urgent for me.
I like the 4a a lot, hated the haptics. It's like an earthquake no matter what is signaling, absolute garbage.

Well most of us maybe don't care about the social networking crap every service try to inject on people.
Maybe that's why people leech on the goods but forget to hit the button nowadays...

 

[bobbarker2]

Bah now I have that "your device is corrupt" crap. Trying to get into fastbootd to flash vendor_dlkm.img. Is there a way to do that from fastboot?

Edit: Nevermind, just did flash-all.bat again. But now everytime I reboot my phone I get the "your device is corrupt" message. I just hit the power button and it boots fine. Though its odd, why can't I flash the kernel? I'm on Magisk Canary, modules disabled, using the same tools as everyone else. And what is causing the "your device is corrupt" message, even though it isn't.. rooted and passing safetynet.

 

[eng.stk]

Bah now I have that "your device is corrupt" crap. Trying to get into fastbootd to flash vendor_dlkm.img. Is there a way to do that from fastboot?

Oriole or Raven?
That seems like messed up verify stuff, maybe something you flashed in between?
Did you always use canary 23016 to patch you stuff? Other zip namely if using anykernel3, must use the version that has magisk tools from 23016
Did you verify the kernel zip and does it indeed flash all the partitions (logs?)
Unless you solve that on stock rooted first, flashing this kernel will not make any difference.

 

[cultofluna]

Bah now I have that "your device is corrupt" crap. Trying to get into fastbootd to flash vendor_dlkm.img. Is there a way to do that from fastboot?

Edit: Nevermind, just did flash-all.bat again. But now everytime I reboot my phone I get the "your device is corrupt" message. I just hit the power button and it boots fine. Though its odd, why can't I flash the kernel? I'm on Magisk Canary, modules disabled, using the same tools as everyone else. And what is causing the "your device is corrupt" message, even though it isn't.. rooted and passing safetynet.

Run flash all bat again ...and add --disable-verity --disable verification to the fastboot update line.

Example:
fastboot --disable-verity --disable-verification update image-oriole -xxxxxxxxxxxx.zip

 

[bobbarker2]

@cultofluna Oh I thought the new Magisk Canary allowed to skip those arguments. I'll give it a try now, thanks.

@eng.stk I'm on Oriole.

I was on November build rooted, safetynet passing with no corrupt device message prior to updating to January. I then updated to January and flashed stock rooted boot.img and no device corrupt message.

I only had a problem when I used FKKM to flash your kernel. I'm sure it's some weird quirk on my device. I do have FKKM logs if those are helpful.

Archive: /data/data/com.franco.kernel/files/blu_spark_r29-pxl6_eeba43b91.zip - Pastebin.com

Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.

pastebin.com

And just fyi Magisk Canary updated.

 

[eng.stk]

@cultofluna Oh I thought the new Magisk Canary allowed to skip those arguments. I'll give it a try now, thanks.

@eng.stk I'm on Oriole.

I was on November build rooted, safetynet passing with no corrupt device message prior to updating to January. I then updated to January and flashed stock rooted boot.img and no device corrupt message.

I only had a problem when I used FKKM to flash your kernel. I'm sure it's some weird quirk on my device. I do have FKKM logs if those are helpful.

Archive: /data/data/com.franco.kernel/files/blu_spark_r29-pxl6_eeba43b91.zip - Pastebin.com

Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.

pastebin.com

And just fyi Magisk Canary updated.

Skipping Dec build may have soemthing to do with that maybe, who knows.
There must be something particular triggering those verity issues some of you guys encountered.
I flash lot's and lot's of zips and never had anything similar. And most people are ok also.

Did you have any Magisk module installed previously, custom ROMs mods etc?

 

[bobbarker2]

Skipping Dec build may have soemthing to do with that maybe, who knows.
There must be something particular triggering those verity issues some of you guys encountered.
I flash lot's and lot's of zips and never had anything similar. And most people are ok also.

Did you have any Magisk module installed previously, custom ROMs mods etc?

Stock rom, no mods, disabled all magisk modules prior to flashing. I don't think skipping Dec had anything to do with it since a lot of people skipped it due to the issues it caused. And I've had problems flashing the kernel prior to this.. when I was on the November version, I tried flashing the kernel with FKKM and EKM and my phone would only boot to fastboot. So I just ran stock rooted.

Haven't had any "corrupt" problems until now.

It's hard to keep up with what to do/what not to do when tinkering with this device since there are so many people with different results doing the same operations.

 

[bobbarker2]

Run flash all bat again ...and add --disable-verity --disable verification to the fastboot update line.

Example:
fastboot --disable-verity --disable-verification update image-oriole -xxxxxxxxxxxx.zip

Edit: Nevermind, I must of had an extra space the cmdline didn't like.

Edit2: Now it won't boot. It goes into Android Recovery and gives me the options to Try Again or Factory Wipe. Great.

 

[cultofluna]

Edit: Nevermind, I must of had an extra space the cmdline didn't like.

Edit2: Now it won't boot. It goes into Android Recovery and gives me the options to Try Again or Factory Wipe. Great.

Yea .
I forgot to mention that first time disabling verity will require wipe ..

 

[Galaxea]

Edit: Nevermind, I must of had an extra space the cmdline didn't like.

Edit2: Now it won't boot. It goes into Android Recovery and gives me the options to Try Again or Factory Wipe. Great.

I had the same issue when flashing the DEC patch. I had to sideload the OTA to fix it then root again with Magisk by booting the rooted image.

 

[bobbarker2]

I had the same issue when flashing the DEC patch. I had to sideload the OTA to fix it then root again with Magisk by booting the rooted image.

So you did a sideload of the OTA and did a fastboot boot Magisk_boot.img and flashed the kernel then?

Yea .
I forgot to mention that first time disabling verity will require wipe ..

Thanks . Fortunately it somehow flashed to the inactive slot so I was able to switch active slots and not factory reset.

But according to root guide (and Magisk git) since 23016 we no longer need to disable verity/verification.

 

[cultofluna]

So you did a sideload of the OTA and did a fastboot boot Magisk_boot.img and flashed the kernel then?



Thanks . Fortunately it somehow flashed to the inactive slot so I was able to switch active slots and not factory reset.

But according to root guide (and Magisk git) since 23016 we no longer need to disable verity/verification.

Only if you're using magisk..you should not have a problem..
If you try i flash a custom img ..you will....
Im disabling verity in every update...so i can mess around without any issue...

 

[Gordietm]

Has anyone flashed this kernel on the 6 Pro?