Installing Custom ROM on Cubot KingKong Mini

moctir

Member
Nov 16, 2017
27
9
3
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.
 
Last edited:

Ce3apyc

Member
May 5, 2014
6
1
0
Almaty
TWRP+Encryption Disabling+Magisk Root

Actually there is TWRP for this model ported from alcatel by NickyNS. You can pick up it from here.
You can flash it with fastboot along with the patched lk which is to disable the "Orange state" message. After flashing it you should enter TWRP right with the next step (without booting to OS). On this stage you might want to disable encryption in order to have full-fledged backup-recovery option in TWRP next time you use it. To do so you will have to format data partition. After that step you will loose all you applications and user data for them, so you should backup it previously. After you format the data, flash Magisk first, then flash encryption disabling script from this post. Now you can boot to OS.

Note, that 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.
 

Attachments

Last edited:

Tom Mix

Senior Member
Oct 7, 2007
354
54
48
well well, finally and serranoltexx successor?

i ordered one yesterday and am looking forward to get an suiteable replacement for my S4 MiNi [serranoltexx]
 

robrazil

Senior Member
Nov 6, 2010
67
10
38

moctir

Member
Nov 16, 2017
27
9
3
Based on the second poster here and someone else who sent me a pm, I believe the TWRP is safe, I haven't tested it myself yet but I plan to at some point and will post here when I do. When I'm using it as my primary device and everything is working okay it's hard to justify messing with it more at the moment!
 

robrazil

Senior Member
Nov 6, 2010
67
10
38
i ordered one yesterday and am looking forward to get an suiteable replacement for my S4 MiNi [serranoltexx]
I did it to replacement my old Samsung J1 ace, very similar of S4 Mini, and I'm not regretful for that.

---------- Post added at 01:37 PM ---------- Previous post was at 01:08 PM ----------

Based on the second poster here and someone else who sent me a pm, I believe the TWRP is safe, I haven't tested it myself yet but I plan to at some point and will post here when I do. When I'm using it as my primary device and everything is working okay it's hard to justify messing with it more at the moment!
I understood but the point is if the TWRP source is confiable. I asked the official TWRP Team about the unofficials TWRP on websites in my last post, and they answer: "Hello, we do not run that site, so I cannot confirm the validity of their images."
So, I wonder how safe the unofficial TWRP images are.
 

robrazil

Senior Member
Nov 6, 2010
67
10
38
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!!
This is a very important information. When I did a update firmware the usb cable disconnected and the mobile died. Black screen. The side buttons died too. Only blue led turn on when the usb cable is connected on PC. The windows 10 only recognized the mobile as "unknown usb device (device descriptor request failed)". I thought that had lose the mobile. A few days later when I connect the mobile in the PC, the battery image was showed on screen with 18% of charge and I saw in that moment that I could flash the firmware again.
I flashed official firmware and the mobile worked again but now it died again... because I did a wrong recovery boot. I will wait discharge the battery again. :( :crying:
 

moctir

Member
Nov 16, 2017
27
9
3
This is a very important information. When I did a update firmware the usb cable disconnected and the mobile died. Black screen. The side buttons died too. Only blue led turn on when the usb cable is connected on PC. The windows 10 only recognized the mobile as "unknown usb device (device descriptor request failed)". I thought that had lose the mobile. A few days later when I connect the mobile in the PC, the battery image was showed on screen with 18% of charge and I saw in that moment that I could flash the firmware again.
I flashed official firmware and the mobile worked again but now it died again... because I did a wrong recovery boot. I will wait discharge the battery again. :( :crying:
Yes, indeed there were three times I thought I had totally bricked and each time I was so annoyed with myself! The key is to not charge it much until you are happy with the ROM you put on.
The amount of drivers I tried to use for different OS' when I got that "unknown USB device" on Windows and Linux didn't detect it was all a waste of time!
 

robrazil

Senior Member
Nov 6, 2010
67
10
38
Well... the battery image appeared again and I uploaded firmware again. I installed the Magisk in the boot recovery, because this only way to install the Magisk on devices that are using system-as-root, but the Magisk disable my 2 SIM cards. When I boot without Magisk, all back to normal.
I serched for any solution for that but I didn't find.
So, my conclusion is that the Magisk not works to Cubot King Kong Mini. How can I stay with a phone with no SIM card?
I give up.
 

moctir

Member
Nov 16, 2017
27
9
3
For me I can only get root when I patched Magisk to Recovery and then boot to Recovery and it doesn't see my SIM card but I have root, so I reboot every time I need root which is a bit annoying...
 

robrazil

Senior Member
Nov 6, 2010
67
10
38
It is very complicated everytime when need "root", to have power off and on the mobile in recovery boot mode. Besides that, run out of SIM card working is not an option.
I will try to get support of this issue with Magisk Team.
Thank you for share your experience.
 
Jul 20, 2014
42
8
0
Neumarkt in der Oberpfalz
Actually there is TWRP for this model ported from alcatel by NickyNS. You can pick up it from here.
You can flash it with fastboot along with the patched lk which is to disable the "Orange state" message. After flashing it you should enter TWRP right with the next step (without booting to OS). On this stage you might want to disable encryption in order to have full-fledged backup-recovery option in TWRP next time you use it. To do so you will have to format data partition. After that step you will loose all you applications and user data for them, so you should backup it previously. After you format the data, flash Magisk first, then flash encryption disabling script from this post. Now you can boot to OS.

Note, that 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.
Hello,
Does anybody can confirm, that this is working with the new firmware?
 

moctir

Member
Nov 16, 2017
27
9
3
I tried the TWRP a few days ago and was able to boot to it but I couldn't mount it to see my files, it asked for a password and I tried "default_password" and creating a password for the phone but that also didn't work. A possibility is to change the file format to ext2 and then to ext4 but I didn't want to try it when I couldn't back it up.
 

Ce3apyc

Member
May 5, 2014
6
1
0
Almaty
I tried the TWRP a few days ago and was able to boot to it but I couldn't mount it to see my files, it asked for a password and I tried "default_password" and creating a password for the phone but that also didn't work. A possibility is to change the file format to ext2 and then to ext4 but I didn't want to try it when I couldn't back it up.
You will not be able to mount and/or use the backup feature of the TWRP until you disable an encryption by formating the data partition and running the script (just press "Cancel" in the TWRP to be able to do that when it asks for the password). Read my original post very carefully. There is a complete sequence of steps in it. Have you tried the TWRP with the last firmware? How did the rest of the system work?
 

moctir

Member
Nov 16, 2017
27
9
3
You will not be able to mount and/or use the backup feature of the TWRP until you disable an encryption by formating the data partition and running the script (just press "Cancel" in the TWRP to be able to do that when it asks for the password). Read my original post very carefully. There is a complete sequence of steps in it. Have you tried the TWRP with the last firmware? How did the rest of the system work?
I'm using treble AOSP Android 9 so not the latest firmware. I thought disabling the verification when installing that would be enough but maybe I do need to do those other steps. I can see the /system directory through TWRP so that's probably because that's the one I flashed, but I can't see the internal storage otherwise.
 

robrazil

Senior Member
Nov 6, 2010
67
10
38
I tried the TWRP a few days ago and was able to boot to it but I couldn't mount it to see my files, it asked for a password and I tried "default_password" and creating a password for the phone but that also didn't work. A possibility is to change the file format to ext2 and then to ext4 but I didn't want to try it when I couldn't back it up.
You need to put the "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip" file into SD card or internal memory to install by TWRP. This file disable the asking of password. Worked for me.
 

Attachments

rndmname

New member
Apr 7, 2020
1
0
0
Anyone else having problems with sensors on this phone? Rotating and compass do not work for me. That's what you get for buying a cheap Chinese phone, I guess.

EDIT: Downgrading firmware back to CUBOT_KINGKONG_MINI_9101C_V06_20191121 seems to fix some problems, rotation works, but compass is still buggy.
 
Last edited:

oiseau1201

Senior Member
May 31, 2017
193
66
0
Tried to install root on a friends kkm but I can't get it working in the os. Is there any chance to get it working there? I am only able to get root access in twrp. Maybe an gsi with root is that possible?
 
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone