Installing Custom ROM on Cubot KingKong Mini

Search This thread

Truelan

Member
Aug 25, 2021
32
5
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.

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.
 

moonraver

Senior Member
May 29, 2022
76
13
first, Stock rom interface was not good.
Second, some app(and game) interface does not match well.
Third, tired using and trying gsi rom.
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?
 

moonraver

Senior Member
May 29, 2022
76
13
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? Recommend some .............
 

Truelan

Member
Aug 25, 2021
32
5
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?
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.
 

Truelan

Member
Aug 25, 2021
32
5
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).
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.
 
Nov 27, 2022
5
1
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.
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
 

Truelan

Member
Aug 25, 2021
32
5
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
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.
 
Nov 27, 2022
5
1
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.
Yes, when trying to flash gsi im using stock boot.img and no magisk, also putting both --disable commands on vbmeta.
 

moctir

Member
Nov 16, 2017
39
13
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.
 

birdibird

Senior Member
Apr 9, 2005
411
36
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.
Isn't it working with PHH's bluetooth setting for mediatek?
 

moctir

Member
Nov 16, 2017
39
13

Attachments

  • Screenshot_20221130-195826.png
    Screenshot_20221130-195826.png
    57.7 KB · Views: 1

moctir

Member
Nov 16, 2017
39
13
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    well, the new stock build has arrived https://cubot.net/platform/Support/detail/id/680/cid/86.html
    has anybody tried to flash gsi over it?


    anyway thanks for sharing
    Bad news............Yesterday I tested new KKM3 firmware (new fresh flash with cable):
    CUBOT_KINGKONG MINI3_C031C_V08_20221206
    January GSI LeOS 19.1 and December LeOS 20 aren't working. Booting still hangs on Cubot logo.

    Differences in new firmware:
    - still smooth, maybe a little bit smoother
    - Battery usage still not showing in Settings
    - "Battery optimization" option with list of all applications can not be found anywhere in settings. I can only call this option when app like Netguard asks for excluding from optimization. Optimization can be set only separately for every app in Settings/App
    - more of Material Me setting in apps
    - default "Display size" and "Font size" is smaller
    - default launcher has new option "Home screen layout". Icons placement can be from 5x3 to 6x5
    - camera with no improvements (still testing)
    - Wellbeing can not be disabled still, other google apps can be disabled
  • 7
    UPDATE 2021
    The original post was for the first King Kong Mini, for instructions for the King Kong Mini 2 go to page 9 in this thread:
    https://forum.xda-developers.com/t/...-on-cubot-kingkong-mini.4050815/post-84445303

    ======================

    The Cubot King Kong Mini was released in Q4 2019. It is one of the smallest Android phones on the market with a 4" screen. Like many cheap Mediatek devices, one cannot be sure of how "safe" or "secure" these devices are, so the security/privacy conscious may want to consider installing a custom ROM. Here are the instructions for installing Android AOSP on the Cubot King Kong Mini. Note: I am not responsible for any bricked devices.

    Download the Stock Rom from here and SP Flash Tool just in case you need to reinstall Stock. Download a system image, note you need to use an A/B arm32 image with 64 bindings. For example AOSP 9 is here.

    This process probably can be done with SP Flash Tool but I wasn't able to manage it due to the disable-verification flag required.

    Unzip the stock ROM and reboot the device to bootloader, connect via USB and unlock via:
    Code:
    sudo fastboot flashing unlock

    Note this will erase all data. Then on your computer navigate to the folder with the unzipped ROM (for me was NA_mt6761p_d936p_9101cmp_chuanqi_cc_256gbitp24d3_p_lte_3m-fdd-cs_mul_20191121-210020_songlixin_PC) and type
    Code:
    fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

    If you do not do this it seems to work without it but then it will bootloop when you try to switch it on. From here on it's standard.
    Code:
    fastboot flash boot boot.img
    fastboot flash recovery recovery.img

    Unzip the .xz image file you wish to use and type:
    Code:
    fastboot flash system SYSTEM.img
    where SYSTEM is the name of whatever image downloaded.


    Root
    For root install magisk manager and you have to patch the recovery to get root (not just boot as flashing boot alone doesn't give you root). So in magisk get it to patch you boot and recovery images and then put those on your computer, go to bootloader and use:
    Code:
    fastboot flash boot magisk_patched_boot.img
    fastboot flash recovery magisk_patched_recovery.img

    You can read more about magisk from recovery here.

    To get root then you need to reboot to recovery, hold power button + volume up and select Recovery. This will appear to boot as normal but you will have root when you do it this way and not when you boot normally. Unfortunately I do not have reception when I do this but do have root, other users have this problem but I have not found a solution.


    Note that I thought I bricked my phone a few times before getting this as nothing would happen after a failed boot and I couldn't switch it on, however what happens is you can't do anything until the battery has almost completely discharged, then when you hit the power button you'll get the no battery sign and when you plug in you can get to Recovery again. This is quite annoying if you've charged it quite high as you'll have to wait a long time to discharge and be tapping on the power button a lot!!


    What doesn't work
    Battery usage doesn't work, this can probably be fixed following this guide. If I get time I will attempt this.

    Other things to note, there is no TWRP yet so I don't have decent recovery options, this also makes it harder to use certain ROMS as you can't flash things like gapps if you install a ROM without it.
    The battery life is definitely worse using AOSP GSI than stock, maybe that vendor overlay would help with that though.

    I hope that helps others.
    5
    Hi,
    I have got the Cubot King Kong Mini 2 and I can confirm that exchanging the system to LOS17.1 is possible too.
    I did nearly the same as mekkadisu did (#39) for KKM1, but had to do a
    Code:
    fastboot reboot fastboot
    before flashing the system.



    This is what I did:
    1.) Flash the newer OS for King Kong Mini 2 from King Kong's site using the instructions and flash tool already there (quoted from #39).

    2.) Enable developer options by tapping the build number in Settings -> About Phone 7 times, Enable USB Debugging and Allow Bootloader Unlock from developer options (quoted from #39).

    3.) (quoted from #39)
    Code:
    adb reboot bootloader

    4.) once in bootloader mode (quoted from #39)
    Code:
    fastboot flashing unlock

    5.) Then confirm unlock on the phone (quoted from #39)

    6.) Note the locaton of the vbmeta.img, boot.img and recovery.img files from the stock ROM (quoted from #39)
    Code:
    fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
    fastboot flash boot boot.img
    fastboot flash recovery recovery.img

    7.) Now I did not flash the system directly, but rebooted to fastboot
    Code:
    fastboot reboot fastboot

    8.) After device is in real fastboot mode (the screen is different to that of bootloader fastboot mode)
    Code:
    fastboot flash system SYSTEM.img

    I used the lineage-17.1-20210114-UNOFFICIAL-treble_a64_bvS.img.xz



    Why did I do the "fastboot reboot fastboot":
    without rebooting to fastboot but direclty flashing the system, I got this error:
    Code:
    fastboot flash system lineage-17.1-20210114-UNOFFICIAL-treble_a64_bvS.img
    Sending sparse 'system' 1/10 (131068 KB)           OKAY [  4.898s]
    Writing 'system'                                   FAILED (remote: 'This partition doesn't exist')
    fastboot: error: Command failed

    After rebooting to fastboot it worked:
    Code:
    fastboot flash system lineage-17.1-20210114-UNOFFICIAL-treble_a64_bvS.img
    Resizing 'system'                                  OKAY [  0.004s]
    Sending sparse 'system' 1/5 (262140 KB)            OKAY [ 19.088s]
    Writing 'system'                                   OKAY [  4.061s]
    Sending sparse 'system' 2/5 (262140 KB)            OKAY [ 19.596s]
    Writing 'system'                                   OKAY [  4.036s]
    Sending sparse 'system' 3/5 (262140 KB)            OKAY [ 19.943s]
    Writing 'system'                                   OKAY [  4.048s]
    Sending sparse 'system' 4/5 (262140 KB)            OKAY [ 20.290s]
    Writing 'system'                                   OKAY [  3.721s]
    Sending sparse 'system' 5/5 (177556 KB)            OKAY [ 13.090s]
    Writing 'system'                                   OKAY [  2.879s]
    Finished. Total time: 110.773s

    I'm not an expert in flashing mobile devices, so I don't know, why I had to to that. I would be very happy if an expert could reply and maybe give me a hint as to what the problem was.
    4
    I see that there are all kinds of instructions floating around in this thread with all kind of extra commands that you do not need to use at all.

    Here is my comprehensive HowTo for our King Kong Mini 2:

    For the KKM2 we need a A64 or A64binder32 image.
    It can be either VNDK or VNDKLITE.
    VNDKLITE is only needed if you want to use a read/write system.
    If you use a systemless root version, e.g. Magisk, you do not need VNDKLITE necessarily but you can always choose it if you want.

    I am using LeOS Android 12.1 on my kkm2 as I want to be as degoogled as possible.
    Because it is so light, the battery time is quite good.


    - download and unpack the gsi.img.xz file you chose
    - put the unpacked .img together with the vbmeta.img file (attached below) in e.g. your home folder
    - in Linux make sure the android-tools package is installed, in Windows make sure platform-tools is installed

    - Boot into your phone, go to settings, about phone and tick 7 times on build number. Developer options will be activated
    - In settings again there will now be Developer options (probably under system). Switch on OEM/bootloader unlocking and USB debugging
    - connect your phone with the cable to the computer
    - open a terminal or command prompt in the folder of the .img files and tick these commands:
    - adb devices
    (the phone should give a message to trust the computer)
    - adb reboot bootloader
    (phone reboots into bootloader/fastboot mode)
    - fastboot flashing unlock
    (you will be asked on the phone to confirm unlocking it)
    - fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
    -fastboot reboot fastboot
    (phone reboots in fastbootd mode)
    -fastboot flash system GSI-VNDK(lite)-a64-bvN.img
    (on the phone choose):
    -Enter recovery
    -Wipe data/factory reset
    -Reboot system now

    That's all.

    when upgrading your gsi, you only need to flash system again in fastbootd and don't need to data/factory reset (dirty flashing). Sometimes this also works between gsi's, but not always.

    (ps:
    you can skip the adb part by booting into bootloader/fastboot mode:
    -hold volume up button while long pressing the power button on the phone
    -in the little menu move with volume up to fastboot and select it with volume down)

    It is known that with some PHH based gsi's the sound sometimes crackles a bit on some Mediatek devices. It is not yet clear what causes it.
    I am playing around with these settings, somehow the crackling is being influenced by the brightness settings. The weird thing is that on our KKM1 with LineageOS A11, we don't have these crackling problems. Please share your experiences with this.

    Phh Treble settings
    Misc features
    tick:
    -Use linear screen brightness
    -Force Enable Camera2APIHAL3
    -Bluetooth workarounds / Mediatek

    in developer options I changed:
    -Animator duration scale .5x

    happy flashing!
    3
    Note to moderators : we have been polluting the Kingkong Mini / Kingkong Mini 2 thread with news, speculations and comments on the Cubot Pocket since April 23rd.
    I think, both KKM / KKM2 and Pocket lovers would benefit from a split of the thread…

    Cobus.
    I have moved the posts relating to the Pocket HERE. You can continue the conversation there. As and when development takes place for this device, you can make a request for a new forum as described by my colleague @Timmmmaaahh! above.
    3
    anyone knows how to replace the boot image on KKM2 ?
    there's logo-verified.bin in default rom files ..
    would be also nice to replace the colorful "charging" screen when phone is switched off

    p.s. successfully loaded the logo-verified.bin in editor from here :
    logo editor
    edited and flashbed back with
    fastboot flash logo logo.bin
    Sending 'logo' (873 KB) OKAY [ 0.046s]
    Writing 'logo' OKAY [ 0.024s]

    battery animation is in the same file.


    Anyone managed to remove 5sec delay with open bootloader?
    The orange state is easy to remove, but delay remains ..