Development [KERNEL]Despair Kernel

Search This thread

reaper000

Senior Member
Aug 3, 2009
1,448
1,123
OnePlus 9
I flashed your initial 2.04, it wouldn't boot. Tried reflashing the entire 12.1 stock rom to get a bootable device.
No dice.
Unfortunately, it looks like I'm gonna have to do a full internal storage wipe and clean install...
 

reaper000

Senior Member
Aug 3, 2009
1,448
1,123
OnePlus 9
Yeah, the dirty flash would have included all that... still bootlooped.
Only a totally clean flash has gotten me booting.

Not blaming anyone -- that's the acknowledged risk we all take when flashing stuff
 

DespairFactor

Recognized Developer / Inactive RC
Mar 13, 2013
6,000
13,080
Toronto
I flashed your initial 2.04, it wouldn't boot. Tried reflashing the entire 12.1 stock rom to get a bootable device.
No dice.
Unfortunately, it looks like I'm gonna have to do a full internal storage wipe and clean install...
you flashed a file that I never said was good to flash. Also, the initial 2.04 was from several hours ago and it is running on my device right now.
 
  • Like
Reactions: shag_on_e and yyz71

reaper000

Senior Member
Aug 3, 2009
1,448
1,123
OnePlus 9
you flashed a file that I never said was good to flash. Also, the initial 2.04 was from several hours ago and it is running on my device right now.

Look, I already said (post #325) I'm not blaming anybody -- including you, @DespairFactor -- for my troubles. I appreciate your work and will continue to use it because you put out damn good product. I've used your kernels/ROMs for years.
However, I have every right to post my experience with flashing that product. Which is all I did. Perhaps it was a bad download, a bad flash, whatever. As a dev, I would think you need to know it didn't go for me. But then you accused me of "flashing a file that I never said was good to flash"?!?
@DespairFactor: See your own post -- #319 -- on this thread.
To me, that post "New 2.04 released with DAC support fixed" , is you saying 2.04 was good to flash. I'm not sure how anybody can read that differently. Heck, I even tapped "Like" on it.
 
Last edited:
  • Like
Reactions: xtravbx

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    heard some people are hiding out in here https://t.me/despairkernelnew
  • 40
    Mission:
    The purpose of this project is to increase efficiency of the Pixel 6 series devices by merging functional patches with minimal bloat.

    If you submit bug reports without a log, you may be prosecuted...or executed.

    Disclaimer:
    If your device fails to comply with your standards of what you consider functioning, I am not liable. This is provided free of charge and does not come with a warranty. Although, if you provide a log, I can provide some sort of assurance that I will look into your issue.

    Installation:
    To install kernel on a rooted device with EXKM/FKM


    - Download ZIP and flash using the manual flasher in the app

    To manually flash kernel updates

    -Download ZIP for kernel and the current boot.img
    -Use the below commands to flash from bootloader/fastboot
    -fastboot reboot fastboot
    -fastboot flash vendor_dlkm vendor_dlkm.img
    -fastboot reboot bootloader
    -fastboot flash dtbo dtbo.img
    -fastboot flash boot boot.img
    -fastboot flash vendor_boot vendor_boot.img

    Links:

    Telegram:


    Downloads:

    Source:
    https://github.com/DespairFactor/raviole

    Credits:
    Google
    19
    V1.17 is being built and uploaded to support February patch
    17
    1.21 is out for A12 and 2.01 is out for A12L, I am done updating for the day
    16
    Can this be flashed over top of Kirisakura kernel, or does factory boot image need to be restored first?
    I'd take the safest approach and just flash back the stock images, and then flash the new kernel to avoid any potential mishaps.
    Yes..you can if you want..
    No need to restore stock images
    It works, because it will overwrite the same files which comes with Kiri. I went back to Kiri from despair without restoring stock files.

    actually @RetroTech07 is right here. You should restore stock images via fastboot/fastbootd to avoid issues.


    In the case of boot.img, dtbo.img and vendor_boot.img you probably can flash the kernel.zips over the other without running into any issue.

    But since vendor_dlkm.img gets flashed on this device as well and sits on the super partition, you want to flash back the stock vendor_dlkm.img via fastbootd (not via any kernel manager while the phone is running!). The reason for that: While flashing vendor_dlkm in fastbootd, the vendor_dlkm partition actually gets resized to their original size inside the super partition.
    While the device is running and either a kernel.zip containing a vendor_dlkm.img is flashed or a vendor_dlkm.img is restored via the option in EXKM/FKM app, vendor_dlkm.img is only dd´ed to the partition, essentially cutting a bit of the original size off, as the resizing part that´s happening when flashing via fastbootd is not happening there.

    It´s not a problem in itself, as all vendor_dlkm.img´s shipped by the custom kernels available are smaller than the vendor_dlkm from stock firmware is.
    However when hopping between kernels, I´d always restore the stock images via fastboot/fastbootd.
    15
    Upon a bit of testing, I have decided to re-release 1.12 but based on January source. I am seeing a lot smoother/faster UX/UI on this build than 1.14 and 1.15