MoeSyndrome-vanilla-grus-20210430-1644.zip
12.3 MB
New #grus test build (4.9) with branch android-11.0 at commit 47e81e0642a1 ("BACKPORT: kbuild: clamp SUBLEVEL to 255").
π1
KudProject | CI Builds
twrp-3.5.2_9-k4.14-1-KudProject-X00T.img
Lol someone already forwarded before I even properly added what's actually changed
No rebuild for mido since no adjustments are needed, once it's on download server however it'll have same TWRP changes as X00T and grus
I won't support alioth for TWRP due to its virtual A/B partition layout
I won't support alioth for TWRP due to its virtual A/B partition layout
fw_grus_miui_GRUSGlobal_V12_5_1_0_RFBMIXM_c04478d703_11_0_signed.zip
74.3 MB
#grus firmware-only zip extracted from V12.5.1.0.RFBMIXM Global (currently limited to Mi Pilot)
Poor R bootloader
I have to rebuild TWRP for grus with AVB footer
I have to rebuild TWRP for grus with AVB footer
twrp-3.5.2_9-2-KudProject-grus.img
64 MB
#grus:
- Image now has arbitrary AVB footer since R bootloader won't accept images without AVB footer anymore
- Added 500 ms delay to TWRP startup due to chances that TWRP might complete this phase while touch driver is stalled, leading to no way to operate it
- Image now has arbitrary AVB footer since R bootloader won't accept images without AVB footer anymore
- Added 500 ms delay to TWRP startup due to chances that TWRP might complete this phase while touch driver is stalled, leading to no way to operate it
lineage-recovery-grus-20210528-1225.img
64 MB
#grus: LineageOS Recovery
dotOS-R-v5.0.1-grus-KudProject-20210528-1225.zip
1.3 GB
#grus: Test build with R blobs and cleanups.
R FIRMWARE AND FULL FORMAT REQUIRED
R FIRMWARE AND FULL FORMAT REQUIRED
lineage-recovery-grus-20210602-1745.img
64 MB
#grus: Another LineageOS Recovery build
π1
dotOS-R-v5.1.1-alioth-KudProject-20210616-1744.zip
1.2 GB
#alioth: Initial open testing. Build defaults to 60 Hz by default and can be changed on Developer options, that will be fixed later (string says 90 Hz, but it's 120 Hz after toggling it on). Some issues may arise, provide logcat and dmesg for such.
aliothin / Mi 11X may not be supported, try at your own risk.
aliothin / Mi 11X may not be supported, try at your own risk.
Specific instructions for #alioth:
- Download and decompress 3 grouped files above and flash to current active slot then reboot to recovery
- Format userdata first then ADB sideload ROM zip (not the other way around)
Installation via TWRP is not supported by me and no assistance will be given.
- Download and decompress 3 grouped files above and flash to current active slot then reboot to recovery
- Format userdata first then ADB sideload ROM zip (not the other way around)
Installation via TWRP is not supported by me and no assistance will be given.
I forgot with build fingerprint spoofing on alioth, but ugh, that can be saved for later day
KudProject | CI Builds
dotOS-R-v5.1.1-alioth-KudProject-20210616-1744.zip
Build is using 100% stock blobs since I'm (still) unable (and won't be able to I guess) to obtain BSP blobs to kang to, and copy pasting from other vendor repos are pain to be done.
If you're having so much security + paranoia on how exported props several MIUI blobs have done will be treated, might as well just use hentaiOS or AOSPA and completely ignore all my builds for alioth, otherwise enjoy the build.
If you're having so much security + paranoia on how exported props several MIUI blobs have done will be treated, might as well just use hentaiOS or AOSPA and completely ignore all my builds for alioth, otherwise enjoy the build.
KudProject | CI Builds pinned Β«Build is using 100% stock blobs since I'm (still) unable (and won't be able to I guess) to obtain BSP blobs to kang to, and copy pasting from other vendor repos are pain to be done. If you're having so much security + paranoia on how exported props severalβ¦Β»