KudProject | CI Builds
648 subscribers
10 photos
405 files
31 links
Continuous integration builds from @KudProject are posted here. Not all builds are tested; proceed at your own risk! See main channel for project-related links and updates.

Device tags (reference only):
#X00T #alioth #ginkgo #grus #mido #scale #ulysse
Download Telegram
XenonHD but it's Nougat: https://1drv.kudnet.id/Android/XenonHD/7.1.2/GalaxyS4/20220527/

It's rock hard, in the Exynos.

#ja3gxx
trinket.dtb
321.1 KB
laurus-q-oss dtb changes rebased over LA.UM.8.11.r1-05800-NICOBAR.0

Will probably boot on laurel_sprout too since they are 97% similar, but please try.

#laurus #laurel_sprout
trinket.dtb
324.4 KB
ginkgo-q-oss dtbs rebased to LA.UM.8.11.r1-05800-NICOBAR.0, which I originally planned to test myself but I have to figure out how to actually handle madness of repacking and so I leave it here and take a rest for now.

#ginkgo
I guess I have to do AnyKernel way later
Forwarded from Redmi Note 10 Pro | Updates (ayran 🇺🇦)
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.
Forwarded from 𝕻𝖗𝖔𝖋𝖊𝖘𝖘𝖔𝖗'𝖘 𝕻𝖗𝖔𝖏𝖊𝖈𝖙 (𝕻𝖗𝖔𝖋𝖊𝖘𝖘𝖔𝖗 𒆜𝖘𝖕𝖕𝖍 𝖙𝖊𝖆𝖒 𒆜)
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
Forwarded from KudProject Updates (Archived) (Albert I (krasCGQ) くらすさん 🌻👻)
KudProject | CI Builds
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.
Besides that: rebased #ginkgo dtb[o] finally boots, but anything else requires that I have to rebase MiCode imports over R tag.
*checks notes*

I'll drop something after Nekomiya release is public on Patreon
Forwarded from KudProject Updates (Archived) (Albert I (krasCGQ) くらすさん 🌻👻)
Recent developments of digital privacy in Indonesia is hitting a rock bottom, as the government is imposing a broadly defined, new whole level of invasive censorship (attempt) that basically apply to virtually anything on the internet. The MR5/2020 mandates that any eligible entities (well, virtually all) to register as Electronic Service Provider (PSE) or risk to be blocked in Indonesia. That isn't the bad news, however. The actual bad news instead come from the invasive approach on how to force platforms to comply with Indonesian regulations against prohibited digital content, which is not only a burden for foreign companies especially those working on the other side of Earth, but also essentially rips off anyone in Indonesia their right to internet privacy as government and law enforcement agencies can request access (without need of court order and must be complied) to general data and contents of private communications (essentially, backdooring) under this regulation.

Add that to lackster of laws that define limits on what government and related entities can do in regards of privacy of their citizens, and I can't imagine to what extent they will abuse this.

This isn't just privacy-disrespecting, but essentially also kills off the meaning of privacy altogether. Not only the government itself is a joke when it comes to cyber security, this regulation just makes it that privacy is simply an element that must not exist in today's sovereign Indonesia.

HRW report from 2021 on how invasive this regulations can be:
https://www.hrw.org/news/2021/05/21/indonesia-suspend-revise-new-internet-regulation
Forwarded from KudProject Updates (Archived) (Albert I (krasCGQ) くらすさん 🌻👻)
KudProject | CI Builds
Recent developments of digital privacy in Indonesia is hitting a rock bottom, as the government is imposing a broadly defined, new whole level of invasive censorship (attempt) that basically apply to virtually anything on the internet. The MR5/2020 mandates…
Out of everything, why privacy concerns I say? Out of all recent data breaches from Indonesian platforms, they only care about imposing more censorship than fixing cyber security and improving ways to protect privacy (instead they opt to stab it even more). Awesome!
twrp-3.7.0_9-0.1-KudProject-ja3gxx.img
8 MB
First series of CI builds after 5 months.

A test TWRP for #ja3gxx to see how it's going on.

Bash and tzdata have been excluded from now on as the recovery becomes too big and we are limited to just 8 MB partition.

Powering off from recovery does not work.
twrp-3.7.0_9-0.1-KudProject-ido.img
23.6 MB
android-9.0 based recovery for Redmi 3 / #ido.

Data decryption is not working currently, adb sideload is not tested, stability testing is further needed.
KudProject | CI Builds
twrp-3.7.0_9-0.1-KudProject-ido.img
twrp-3.7.0_9-0.2-KudProject-ido.img
23.6 MB
New update:
- Data decryption now works, tested on MoKee 90.0 only
- Workaround for early ADB init

#ido
twrp-3.7.0_9-1-KudProject-ido-debug.img
23.9 MB
Recovery image from https://t.me/KudProject/908 with logcat included, since apparently some #ido hardware combinations are having a black screen