yashsingh1/xdaforums huggingface dataset:
[Upgrading, Modifying and Unlocking] veloc_h:
in https://xdaforums.com/t/installing-custom-rom-on-cubot-kingkong-mini.4050815/post-81964483 it is said: "attached TWRP is only valid for firmware CUBOT_KINGKONG_MINI_9101C_V06_20191121. Cubot has released a new one and you can try to use the TWRP with it, but there is no guarantee it will work correctly."

My firmware is from 2020:

CUBOT_KINGKONG_MINI_9101C_V15_20200609

"btw offline charging and VoLTE is working." ok, thanks for the information. On the first page of this thread someone mentions that the compass does not work (I would use the mini as a bicycle gps, therefore I would love to use a compass). I have only read the first 9 pages and the last 2 or 3 pages because I thought, that only the first 9 pages are about the mini one version.
[Upgrading, Modifying and Unlocking] W0153R:
I recently reinstalled my phone, mainly to finally update it, and had the bluetooth echo when calling again. Because I reinstalled it without magisk and wanted to stay without root, I started looking for another way to solve it. I found out that vendor isn't part of the GSI and that's probably why the problem still exists. Another way to solve it is to modify vendor.img from the original ROM and flash that.

To modify vendor.img, the result of which is attached, I took the following steps:

# Get raw image

simg2img vendor.img vendor.raw.img

# Make some room to work in

dd if=/dev/zero bs=4096 count=4096 >> vendor.raw.img

# Make filesystem use the available space

resize2fs vendor.raw.img

# Create a directory to mount the image to

mkdir ./mount

# Mount image

mount -t ext4 -o loop vendor.raw.img ./mount/

# Make modifications to audio_policy_configuration.xml

sed -i ':a;N;$!ba;s%<route type="mix" sink="voice tx"\n[ ]*sources="Voice Call In"/>\n[ ]*%%g' ./mount/etc/audio_policy_configuration.xml

sed -i ':a;N;$!ba;s%<mixPort name="voice tx" role="sink" maxOpenCount="1" maxActiveCount="1">\n[ ]*<profile name="" format="AUDIO_FORMAT_PCM_16_BIT"\n[ ]*samplingRates="8000,16000,32000,44100,48000"\n[ ]*channelMasks="AUDIO_CHANNEL_IN_MONO,AUDIO_CHANNEL_IN_STEREO,AUDIO_CHANNEL_IN_VOICE_UPLINK,AUDIO_CHANNEL_IN_VOICE_DNLINK"/>\n[ ]*</mixPort>\n[ ]*%%g' ./mount/etc/audio_policy_configuration.xml

# Unmount image

umount ./mount/

# Resize image to minimal size

resize2fs -M vendor.raw.img

# Create sparse image

img2simg vendor.raw.img vendor.echofix.img

I then flashed it with the following steps:

# Reboot to bootloader

adb reboot bootloader

# Reboot to fastboot

fastboot reboot fastboot

# Flash vendor

fastboot flash vendor vendor.echofix.img

I still have to fully test it but it seems to be working..
[Upgrading, Modifying and Unlocking] axisdee:
UPDATED! I was able to advance in the guide but stuck in another step...

So I got a KKM2Pro and wanted to root and ungoogle it and/or install a custom ROM.

( I'm a newbie in this context. My only experience is with flashing LineageOS by TWRP on already rooted S4 mini and then, on another S4 mini, unlock/rooting with Odin and install TWRP and flash LineageOS)

My KKM2Pro is already with the C021C_V02_20220718 firmware/stock rom version.

I'm working on linux ubuntu 20.04 with adb, android-tools-adb and android-tools-fastboot packages version 1:8.1.0+r23-5ubuntu2 from the official repositories.

In the end I'm looking for root and LeOS (which seem some people installed on KKM2Pro) or any rom without groogle (Lineage OS or AOKP would be good but are not available for KKM2Pro). Perfect would also be with TWRP but from what I read on this thread nobody tried on KKM2Pro.

I'm also available to contribute (with my limited knowlegde) to the creation of a custom rom based on the stock rom without groogle for this device.

From what I've read I have to unlock the bootloader before anything else, so I started by following the guide by oragestate.

Keeping the numeration:

7. fastboot reboot fastboot gives me "fastboot: usage: unknown reboot target fastboot". If I do fastboot reboot only it results in "< waiting for any device >"

And the screen is not "different to that of bootloader fastboot mode".

8. If I try fastboot flash product product_gsi.img, I get

Is this related to the GSI partitions? What is the solution?

De-Bloater detects product partition. Treble Check detects A-only system partition.

In the meantime, after step 6 and before step 7, I installed Magisk, patched the stock boot.img (without the vbmeta patch option) and flashed it with the same command fastboot flash boot boot_magisk_patched.img. So the root is done!

Now I need to solve the product partition problem and decide on which custom rom to install...

Thank you!
[Upgrading, Modifying and Unlocking] steve8x8:
Um, what would be wrong with AndyYan's LOS builds? (Don't have a 2pro to try them myself.)
[Upgrading, Modifying and Unlocking] axisdee:
Honestly it's just my ignorance with personal builds because of the seeming lack of details or descriptions from the authors so I cannot decide: first if it will brick my device; and second if is what I'm looking for or not...

I'm yet to understand if there is a good rom for this device...

I'm open to contribute (with my limited knowlegde) to the creation of a custom rom based on the stock rom without groogle.
[Upgrading, Modifying and Unlocking] birdibird:
Are you talking about the original Cubot rom or a GSI?

On the GSI's of A11 and A12.1 the bluetooth echo has been gone for already a long time (~a year).
[Upgrading, Modifying and Unlocking] birdibird:
You are adding steps which are NOT needed and making it more complicated in that way.

-You do NOT need these 2 steps if you come from the original rom:

fastboot flash boot boot.img

fastboot flash recovery recovery.img

-You do NOT need to flash a product_gsi image: there is enough space for a GSI on the device. Just flash the gsi system image
[Upgrading, Modifying and Unlocking] axisdee:
Thank you for teach me!

I just add the step to root with Magisk.

Although the device came with the last version, I'm just trying to follow the entire guide to make sure nothing is undone.

The error in step 8 is because "there is enough space for a GSI on the device"? And what do you mean "Just flash the gsi system image"? Is this flashing the custom rom that I eventually will choose with fastboot flash system SYSTEM.img command?

In the stock rom downloaded archive there is no system.img but there is a super.img... Which leads to my next question: if I install a flash a custom rom and I want to flash again the stock rom, what file do I flash?
[Upgrading, Modifying and Unlocking] W0153R:
I'm using CAOS 11 v316-220321 and the bluetooth echo is definitely there. Also, I couldn't find any mention of a fix on the treble github. But I didn't search any further on the issue within the available GSI's, I just searched for where audio_policy_configuration.xml came from and decided to fix it there.

And I haven't found any issues with my fix.
[Upgrading, Modifying and Unlocking] badcodelab:
just use flashtool and follow the manual from cubot https://cubot.net/platform/Support/detail/id/663/cid/82.html
[Upgrading, Modifying and Unlocking] birdibird:
yes, only fastboot flash system system.img in fastbootd

the super.img in the stock rom contains system.img, vendor.img and product.img.

If you reboot to fastbootd mode (fastboot reboot fastboot from bootloader mode) you can flash them seperately
[Upgrading, Modifying and Unlocking] kkm6761:
Anyone had this issue? I have no more LTE connection. I have reset phone on Lineage OS, does not work, on stock ROM, still does not work, and I have tried many SIMs that all work on iPhone.

Any hint to solve this?
[Upgrading, Modifying and Unlocking] birdibird:
is the APN correct?
[Upgrading, Modifying and Unlocking] kkm6761:
Yes, it is. Same as indicated by Lycamobile for Android. Not different than iOS.

On web browser it shows net::ERR_INTERNET_DISCONNECTED

Usually when I enabled data, it showed LTE near the signal strenght bar. Now when data enabled it shows no LTE, but and data is disabled, it shows signal strength bar with exclamation mark. It should not be that way.
[Upgrading, Modifying and Unlocking] Rackam el Roig:
Hi.

Thank you for the instructions.

I've followed instructions, and it seemed that it went all OK, but when I restart the phone, it gets stuck in the Fastboot Mode, and I can't find the way to exit this.

Pressing vol up + power takes me to the boot menu: if I select Recovery, it shows the "No command" message. Both Fastboot and Normal modes get the phone in Fastboot Mode.

Anybody with this problem?

Thanks!
[Upgrading, Modifying and Unlocking] kkm6761:
Your boot.img is probably corrupted.

To enter recovery menu, it shows "no command", send command pressing and releasing simultaneously volume up and power buttons.
[Upgrading, Modifying and Unlocking] kkm6761:
Solved. Clean reflashed stock rom, and clean reflashed lineage os 18.1. LTE works.
[Upgrading, Modifying and Unlocking] Rackam el Roig:
If anyone with the same problem as mine, I finally flashed Lineage 18.1 on my King Kong Mini 2 with these steps:

Reflash stock rom with the 2020 one from here: https://www.cubot.net/platform/Support/detail/id/419/cid/60.html

Enable USB debugging and Allow Bootloader Unlock.

Unlock bootloader.

Flash ONLY the stock vbmeta with command:

fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

After entering the fastbootd mode

fastboot reboot fastboot

flash Lineage 18.1 with this rom: lineage-18.1-20220217-UNOFFICIAL-treble_a64_bvS.img.xz

And now I have Lineage 18.1 working in the KKM2 with no issue. :)

Thanks!
[Upgrading, Modifying and Unlocking] kkm6761:
Lineage 18.1 with gapps did not work for me. I had to register Android ID. App that needed GSF now works, but notification of Google Services still appears.
[Upgrading, Modifying and Unlocking] pjm77:
Hi people. I'm struggling here quite a bit. I'm on the latest KKM2 stock firmware. I'm trying to install TWRP 3.51 and it's not going well. What I'm doing is:

enable developer options, enable OEM unlocking, enable USB debugging

adb reboot bootloader

fastboot flashing unlock

fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (from stock ROM)

fastboot flash boot boot.img (from stock ROM)

fastboot flash recovery recovery.img (TWRP 3.51)

fastboot reboot fastboot (to get to fastbootD mode)

fastboot flash vendor vendor.img (the one that's supposed to decrypt data partition)

reboot into TWRP

Can't mount data, can't wipe it, can't format it, can't repair file system, can't flash any zips (wanted to flash magisk)...

What am I doing wrong?

Also, I've got three versions of SP Flash Tool and in all of them only "Firmware Update" mode is available and it's not possible to untick any of the images. I can only flash everything or nothing.
[Upgrading, Modifying and Unlocking] birdibird:
LeOS-20-VNDKLITE-a64_bvN boots fine on the KKM2 :)
[Upgrading, Modifying and Unlocking] moonraver:
hmmmmmmmmmm.............I am waiting now for LeOS R from November to be uploaded. But your post has really changed my priority. Now I would like to try LeOS-20-VNDKLITE-arm64_bvN.

BTW1: I still haven't found a good explanation between VNDK and VNDKLITE or between bvN and bvS. I thought that VNDKLITE and bvS was RW but there are VNDKLITE bvN versions.........I am a bit confused. Can you explain it to me? I am interested in root versions - which one to choose?

BTW2: How do you feel running LeOS 20? I tried LeOS 19.1 on my KKM2 month ago but I realized that every Android 11 based ROMs (=same as vendor) run really smoother than any A12 versions. That is why I am asking you. KKM2 has A10 vendor image and this LeOS 20 is 3 steps higher.

Thanx
[Upgrading, Modifying and Unlocking] birdibird:
VNDK VS VNDKLITE: According to @harvey186 files are unshared on VNDKLITE and shared on VNDK, which makes VNDK roms a bit smaller.

I quote him from the Telegram group:

The difference between bvS and bvN roms is that bvS has phh-su app included.

You can use Magisk on both VNDK and VNDKLITE bvN versions (I have tested both).

see also:

LeOS-Files

LeOS-Cloud - make Love not Waste

leos-cloud.de

and open which_version.txt
[Upgrading, Modifying and Unlocking] moonraver:
Does anybody have an idea how proceed with KKM3 flashing? Is it the same procedure like with KKM2 or KKM2 Pro? Has anybody tried it yet?

And what about DSU Loader? Has anybody tried flashing with this feature yet?

Thanx a lot.

BTW:

LeOS-20-VNDKLITE-arm64_bvN boots fine on KKM2 Pro.
[Upgrading, Modifying and Unlocking] badcodelab:
i'm going to try in a few days

just got my parcel with kkm3 yesterday, yet testing

hope the process will be similar to kkm2/pro, stock rom is quite buggy and unfriendly in ux

just to clarify

am i right, this file is only needed for rooting device on bvN (su-less) gsi roms?
[Upgrading, Modifying and Unlocking] moonraver:
I flashed product_gsi.img only for KKM2 Pro for enlarging space for custom ROMs.

I have to wait for my KKM3 til 4th of December.
[Upgrading, Modifying and Unlocking] moctir:
Thanks for this, I just for the KKM Pro 2 and this worked perfectly, not too different from my original instructions for the original KKM though for some reason I can't install Magisk, has anyone managed this on the Pro 2?
[Upgrading, Modifying and Unlocking] moctir:
I just noticed this bluetooth echo so I'll check this out shortly, thanks for that and the details on how you did it!
[Upgrading, Modifying and Unlocking] badcodelab:
well, i tried kkm2pro's way several times with different gsi roms (los 19, 20-td, secure, vndklite, pe)

also used magisk (25.2) for patching boot and flashed it to get root

no luck, always getting bootloop or bootstuck

even tried replace flashing product_gsi.img mentioned above with command:

fastboot resize-logical-partition product 38000

luckily flash tool brings kkm3 back to live

have no ideas how to solve this riddle, please help
[Upgrading, Modifying and Unlocking] moonraver:
Well, this is my procedure for KKM2 Pro. Please see the BOLD part below - that could help:

- adb reboot bootloader

- fastboot flashing unlock

(files from the stock ROM)

- fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

########################################

IF THERE IS A BOOTLOOP after whole flashing procedure add this commands:

- fastboot flash boot boot.img

- fastboot flash recovery recovery.img

########################################

- fastboot reboot fastboot

- fastboot flash product product_gsi.img =rezise parititon, file is in attachment

- fastboot flash system (ROM.img)

+

Wipe Cache and WIPE DATA/FACTORY RESET

If this won't help you, there is only way to solve this - to contact harvey186 to ask for help with A12 flashing procedure. He is the main LeOS master :)

Another way how to do it is DSU Loader. This option is in Developer menu and available from A11 versions. In Play store or F-Droid (or somewhere else) there is an app that cooperates with DSU Loader and can help you to have 2 ROMs on the same device. I haven' t tried it yet but have read about it. Main advantage is that you don't have to flash ROM with fastboot commands.
[Upgrading, Modifying and Unlocking] badcodelab:
thanks mate, this is exactly what i did using this post by @orangestate as a manual

and it stuck on a splash screen every time

i've heard about dsu sideloading but as far as know it has some limitations for memory space
[Upgrading, Modifying and Unlocking] moctir:
Damn it, I just tried to flash this and am now in a boot loop. I can't seem to get to recovery with either of the volume buttons, any suggestions?
[Upgrading, Modifying and Unlocking] difkey:
Yes, of course it's possible. But you will lose google keys. This is problem. How to recover keys - I don't know.
[Upgrading, Modifying and Unlocking] birdibird:
I don't know what you mean with google keys.

Sometimes when you use SPflashtool with format all (NEVER DO THAT!) you can loose your serial key, IMEI, nvdata, nvram etc, which can be a problem or not with running your phone, and some of it you can resolve with a mtk toolkit. Again: it is not recommended! And if you play around with it you should backup nvdata etc!

Is that what you mean?
[Upgrading, Modifying and Unlocking] difkey:
Yes, that's exactly what I meant.
[Upgrading, Modifying and Unlocking] Truelan:
anyone know about gsi rom issue on kkm2 pro?

when fully charged. LED turns on and never turn off until power off.

PS. I flashed gsi on KKM3. same process, like kkm2pro. nothing special.
[Upgrading, Modifying and Unlocking] badcodelab:
looks like you're lucky, i tried many times

what gsi build did you flash?
[Upgrading, Modifying and Unlocking] Truelan:
I sold it. but as I remember, most of gsi does not work.

corvus official gsi worked well.

but before start, you better do factory reset from stock recovery.
[Upgrading, Modifying and Unlocking] moonraver:
I had the same problem with KKM2Pro. Restart didn't help. Only 2 things helped:

- power off and then power on

- Lineage OS based LeOS R and S = android settings/battery/battery led - just klicked on led color options
[Upgrading, Modifying and Unlocking] smartomato_reloaded:
Would you please share more details? So far trying the methods here for KKM3 mostly results in getting stuck on cubot's splash screen or bootloops.
[Upgrading, Modifying and Unlocking] moonraver:
If I can ask...............why did you sell your KKM3 phone?
[Upgrading, Modifying and Unlocking] Truelan:
fastboot flashing unlock

fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

fastboot flash boot boot.img

fastboot flash recovery recovery.img

fastboot reboot fastboot

fastboot flash product product_gsi.img

fastboot flash system SYSTEM.img

fastboot -w

navigate to 'enter recovery' to enter recovery.

wipe cache

wipe data/factory reset

restart system

pruduct_gsi.img is attached in another post.

find yourself.

only CORVUS ROM WORKED.

I also failed A13. stuck in cubot logo.

I don't know about other A12 rom.
[Upgrading, Modifying and Unlocking] Truelan:
first, Stock rom interface was not good.

Second, some app(and game) interface does not match well.

Third, tired using and trying gsi rom.
[Upgrading, Modifying and Unlocking] badcodelab:
could you please specify the build name?

or share download link?

i tried almost the same steps except wiping data
[Upgrading, Modifying and Unlocking] moonraver:
The truth is that the screen has a problematic ratio and is 2 mm thinner than KKM/2/2Pro. This is something I am worried about, I am still waiting for my KKM3 til 4th of December. I can still cancel my purchase.

I don't play games at all. I mainly use Osmand for navigation and for mapping. Of coarse I hope that camera will be a bit better than KKM2 Pro to make better photos during mapping. Haven't you tried Osmand on KKM3? :).

Ok so now what device do you use instead of KKM3?
[Upgrading, Modifying and Unlocking] Truelan:
KKM2Pro.

performance was not good, but enough for normal usage. also better screen ratio.

and find some way to solve led issue.

in phh setting, turn on "disable hardware backlight".

PS. I does not use osmand. so dont know about that.

but, I tested some game.

genshin run in lowest setting. 20-30fps.

punishing gray raven at middle setting 40-60fps.
[Upgrading, Modifying and Unlocking] Truelan:
corvus s4.0 official.

search phh gsi wiki.
[Upgrading, Modifying and Unlocking] smartomato_reloaded:
I'm sorry to bother, but I've been trying with those files yet still stuck at splash screen loop. Would you mind to share exact filename of the file you tried? Any missing details? Please understand my insistence, I've being trying to flash a GSI since day 16 (same day they released the stock rom).
[Upgrading, Modifying and Unlocking] Truelan:
I used arm64 bgn slim lite.

try fastboot -w in bootloader.

try fastboot -w in fastboot mode.

and in recovery, do factory reset/wipe data.

data partition does not compatible with new rom.

you should format and wipe all data.

I guess, flashing some other rom destroyed cache or data partition.

above two command also wipe but also flashing some partiton.
[Upgrading, Modifying and Unlocking] smartomato_reloaded:
Thanks for the attention. No luck so far tho, as soon as I flash any gsi I get the stuck at splash screen. May be my specific phone, I've seen reports of this on other treble compatible phones. I'm gonna keep trying and reporting here.

Ps. Weird things on my KKM3 I noticed so far and may help:

Stock Rom comes with scatterfile for MT6768?

Managed to get magisk on stock and weirdly it boots with vbmeta with just --disable-verity while not booting if I use --disable-verification

After reflashing stock with spflashtool, the stock images have checksums different from the images I get by using the readback tool, magisk only worked after patching the boot.img from the readback process
[Upgrading, Modifying and Unlocking] Truelan:
I dont know about magisk.

I does not use magisk.

I just flash gsi.

if magisk patched, some gsi does not boot at all.

so that I does not use magisk.

and while flashing vbmeta, those two option should put together, not separatly.

and I dont know why MT6768.

no error happen while flashing.

just guess that, P65 and G85 are almost same maybe.
[Upgrading, Modifying and Unlocking] smartomato_reloaded:
Yes, when trying to flash gsi im using stock boot.img and no magisk, also putting both --disable commands on vbmeta.
[Upgrading, Modifying and Unlocking] moctir:
So I installed Vanilla AOSP 11 on my King Kong Mini Pro 2 but there are some issues. Like a few others here there is an echo when I talk on a bluetooth headset, someone in this thread build a vendor.img to fix this but I'm not sure it was for the Pro 2 as it caused a bootloop for me. It seems the issue is in audio_policy_configuration.xml and audio_policy_configuration_bluetooth_legacy.xml where I need to remove "Voice Call In" and "voice tx" as described here. However with root I do not have permission to edit it in /vendor/etc or /system/etc even after mounting /. Would anyone know how to do this?

Also, a bigger problem is bluetooth audio for media files does not play thought the headset or speakers but uses the phone speaker instead. I've seen a few workarounds for this but they haven't worked, I'm hoping the fix for the echo will fix that too though.
[Upgrading, Modifying and Unlocking] smartomato_reloaded:
Sorry to bother again, I can't never boot after using this command, even in stock, it always bootloops. I would like to ask the version of platform tools you are using and if you could share your vbmeta.img file.
[Upgrading, Modifying and Unlocking] birdibird:
Isn't it working with PHH's bluetooth setting for mediatek?
[Upgrading, Modifying and Unlocking] moctir:
Unfortunately not.
[Upgrading, Modifying and Unlocking] birdibird:
Which vanilla AOSP have you tried?

Did you eg also try AndyYan´s los based gsi's?

Andy Yan's personal builds // GSI - Browse Files at SourceForge.net

sourceforge.net
[Upgrading, Modifying and Unlocking] moctir:
I didn't try Lineage no, this is AOSP 11 v313 arm64, I think I chose vndklite. I previously tried V311. I wanted to stick with 11 but now I'm regretting not going with the most up to date 12. I've installed everything so don't really want to reflash....
[Upgrading, Modifying and Unlocking] mekaddisu:
Yes, those are from the stock rom. I've edited my post and added that detail, thanks.

I never tried TWRP as the one mentioned here was unofficial. Pretty much everything I've tried works except for the battery usage details; I'm content with the percentage. Granted, I haven't done any testing, I just use it as my daily phone. What I normally use would be phone, text, BT, GPS, etc.
[Upgrading, Modifying and Unlocking] landsome:
Thanks. Very helpful.
[Upgrading, Modifying and Unlocking] landsome:
Which version specifically of the 17.1 did you use, please?

(I assume it's the arm32 binder64 AB version by Andy Yan here: https://sourceforge.net/projects/andyyan-gsi/files/lineage-17.x/)

Also, did anyone get to compare LOS17.1 and AOSP10?