DerpFest 12 but SnuggyWuggy build: SharePoint link

Currently based on Ivan Kupala's vendor and ROM sources haven't been synced with February updates yet. Ships with firmware like that of official YAAP and POSP builds. Also ships with GrapheneOS Camera instead of AOSP one.

Flash via fastboot using fastboot update, then reboot to recovery and factory reset if you're moving away from any ROM other than hentaiOS/helluvaOS or SnuggyWuggy derived ROM builds.

Don't bug Pokorny (alioth official maintainer) about issues with this build. Let him live in peace.

#alioth

#grus: Just another SHRP build, I have to clean up device tree behavior.

*> Fixed ADB sideload
*> Include magiskboot into build

SHRP features should work correctly now.
#grus

The add-on rescue for above build; flash after recovery. #grus

Another Derped Snuggy build, which was supposed to be release one (based on Among Us 2 vendor)

Clean flash required, even from previous build posted here before. Installation instructions is same as that of hentaiOS or hentai-based builds.

As usual do not bug Pokorny for all issues encountered on this build.

Picture is just so you all don't stupidly forward stuffs here and there, especially you Skaye and RDS.

https://1drv.kudnet.id/Android/DerpFest/12/RedmiK40/20220430/

I keep forgetting to post this, so fuck the styling. Dirty flashable from 20220429 build, based on latest GouramiLabs build which changelog will only be on May release of hentaiOS.

Other changes:
Updated GrapheneOS Camera to v29
Added F-Droid Privileged Extension from CalyxOS (for testing, but due to complicated checks F-Droid most of the time will refuse to do unattended install with it so it'll probably be removed again)

When new security patch drops out, new build will only be available after both DerpFest merged it and hentaiOS has released a build based on it not under GouramiLabs umbrella.

Most likely final DerpFest build to come.

This is not on KudProject channel because DerpFest is already dead and most builds released after this announcement are related to bug fixes only.

Upstream:
*> Fixed an issue causing some apps like Bilibili Asia to not launch
*> Fixed NPE in Wallpaper Picker (if that even affects publicly released build)

Device-specific changes:
*> Updated GrapheneOS Camera to v37
*> Increased WiFi 5 GHz signal tolerance
*> Pulled default/supl APN configs for Indonesia from each respective providers + the rest from iQOO 8 Pro

Same procedures from this release post apply here as well. Indonesian users might need to reset their APN settings to default to get changes reflected especially those marked as hidden.

#alioth

XenonHD but it's Nougat: https://1drv.kudnet.id/Android/XenonHD/7.1.2/GalaxyS4/20220527/

It's rock hard, in the Exynos.

#ja3gxx

I guess I have to do AnyKernel way later

There has been an incident regarding the Android 13 port pushed on the channel before. If you have downloaded it, please do NOT flash it!

It has come to our attention that a group intending to cause harm has been circulating a zip designed to brick phones under the guise of being a build of Android 13.

If you get a suspicious private message claiming to have an Android 13 build or flashing anything at all, please treat it with caution and get it to the attention of a group admin. Please be cautious about what you flash on your device or what commands you execute.

If you see anything referencing @realstoplamers or messages from @pIafonakk @jopa_shlepatel @ivan_anrysenko @vit140 @notden56700 @real_linuxoid @DirolhackCHECK_BIO @dakaer @WhiteYaki (these are the people known so far) please block them and report it to the admins

It's always a good idea to be cautious about what you're flashing on your device, but at the moment you're encouraged to be extra vigilant.

The patch() function which its not a patcher
Its just used to repartition the target with 4mb
Which its targeting sensitive partition such as ur vendor and boot loader

I need to rephrase the caption meanwhile:
What the patch() shell function does is that first it sets target block device to R/W, and then proceed with overwriting ABL and vendor partitions (both A-only and A/B) with 4 MB chunks (bs=4M) of zeroes (if=/dev/zero) 10 times (count=10). This is being masqueraded as "Step 1/2."

To make it even more redundant (as to maximize the destructive action): it then overwrites every partition that can be found with exactly same amount of chunks. This is being masqueraded as "Step 2/2." On many partitions, this will actually overwrite the entire block with zeroes, since they're usually smaller than first 40 MB it's overwriting.

What an unfunny joke, because A/B payload flashing flow is supposed to be Step 1 flashing partitions, and Step 2 is the post-processing procedures that should be faster and not vice versa.