Installing Custom ROM on Cubot KingKong Mini

[Alexbrz2]

Hi all! I have recently purchased a KKM2 as a gps tracker & bluetooth-forwarding device for my bbq equipment, and now thinking to upgrade it to LOs.

Before i start off, i am on the most recent original OS version. Is this procedure still the correct way to go? https://forum.xda-developers.com/t/...-on-cubot-kingkong-mini.4050815/post-84445303

With the use of LeOS-20-VNDK-a64-bvN.img

Or is there something that has changed or i have missed?

 

[moonraver]

Found KKM3 bug in latest V08 firmware:
NFC turns itself on after every phone restart even in SAFE mode.
Cubot support says that they don't have this bug.

Does anybody have this?

 

[badcodelab]

NFC turns itself on after every phone restart

not for me

btw any news on installing gsi on kkm3?

 

[moonraver]

not for me

btw any news on installing gsi on kkm3?

that's interesting, I have disabled a lot of google apps, maybe that could do that. Anyway, I don' t want to make a reset for now, will wait till next update.
No news about gsi flashing, I check 4pda forum everyday about KKM3 and they have many problems with that. Still no clear procedure how to flash.

 

[badcodelab]

No news about gsi flashing, I check 4pda

guys there shared new (3rd) modded stock (v08) rom with some tuned features https://4pda.to/forum/index.php?showtopic=1056175&view=findpost&p=121550784

also same user published his dump of evolute gsi which can be flashed via spft

Evolute.rar

drive.google.com

although it has some bugs he claims that it possible to flash any gsi over this dump via fastbootd

 

[moonraver]

guys there shared new (3rd) modded stock (v08) rom with some tuned features https://4pda.to/forum/index.php?showtopic=1056175&view=findpost&p=121550784

also same user published his dump of evolute gsi which can be flashed via spft

Evolute.rar

drive.google.com

although it has some bugs he claims that it possible to flash any gsi over this dump via fastbootd

I read it yesterday somehow............with web translator - it is a bit difficult to understand it this way.
do you mean to flash evolute gsi via spft and then any GSI via fastboot?

 

[badcodelab]

do you mean to flash evolute gsi via spft and then any GSI via fastboot?

seems like this, i don't know how he managed to install evolute gsi to his kkm3 in the first place
but this guy says after installing his dump of evolute gsi using spft it should be possible to flash other gsi builds using "ordinary" process in fastbootd mode
he also mentioned that he tried to flash a couple gsi roms but issue with a lock screen persisted

 

[moonraver]

not for me

btw any news on installing gsi on kkm3?

About that NFC problem............can you try this for me? I want to be sure if I need to make a hard reset of my KKM3. I have found something new - that bug occurs only when SIM card is inserted in the device. When there is no SIM card, NFC doesn't turn on by itself.

So the bug is present when:

1. KKM3 device is on and I remove SIM card. Then I insert SIM card (connecting 2G, 3G or 4G type of network) and NFC turns itself on immediately
2. KKM3 device has SIM card inserted and I reboot the device. It reboots and after reboot when the device detects that SIM card is inserted (connecting 2G, 3G or 4G type of network), turns NFC on immediately

Does your NFC turn on by itself in any of these 2 cases?
Thanx

 

[badcodelab]

i confirm, #1 is reproducible, kkm3 enables nfc after inserting sim card
#2 is still negative

 

[v.a.riabov]

Someone solved the problem with 15 fps shooting video on the main camera on KKM2?

 

[moonraver]

Someone solved the problem with 15 fps shooting video on the main camera on KKM2?

Try Protake app if it helps. This problem has KKM2 and KKM2 Pro. That was why I bought KKM3 but it has also this bug if ISO is higher than 400 (=15 fps). Otherwise it shoots 30 FPS. So I use Protake - it indicates some frame drops but for me it is still has the best video results.
I contacted Cubot support about year ago with this KKM2 and KKM2 Pro "low video FPS bug" but the support was VERY HARD TO UNDERSTAND ME. So I gave up. It seemed to me that they did NOT want to solve this maybe because the phone is low-cost.
Now the support is maybe a bit better - you will get the answer that developers will fix bugs in next update....... but that is all.
BTW: Custom ROMs did't also help to solve those 15 fps. I'm really sure that it is a matter of CUBOT camera drivers because the sensors in all KKMs are able to shoot 30 FPS.

 

[v.a.riabov]

Try Protake app if it helps. This problem has KKM2 and KKM2 Pro. That was why I bought KKM3 but it has also this bug if ISO is higher than 400 (=15 fps). Otherwise it shoots 30 FPS. So I use Protake - it indicates some frame drops but for me it is still has the best video results.
I contacted Cubot support about year ago with this KKM2 and KKM2 Pro "low video FPS bug" but the support was VERY HARD TO UNDERSTAND ME. So I gave up. It seemed to me that they did NOT want to solve this maybe because the phone is low-cost.
Now the support is maybe a bit better - you will get the answer that developers will fix bugs in next update....... but that is all.
BTW: Custom ROMs did't also help to solve those 15 fps. I'm really sure that it is a matter of CUBOT camera drivers because the sensors in all KKMs are able to shoot 30 FPS.

Thx! I hope support have solve the problem somehow!

 

[veloc_h]

I flashed CUBOT_KINGKONG MINI2_A061C_V11_20220817 on my kingkong mini (Version1).
Now the compass works (the kingkong mini is used only for bicycle navigation)!
However I get the message "tee key / google key" because I formatted the whole file structure (option automatic formatting) without backup (not the best thing to do...)
There is a workaround, but I would have to install magisk

[Discussion] Magisk - The Age of Zygisk.

This is a discussion and help thread for the newer versions of Magisk. The main goal of this thread is to help users migrate to Magisk v24+ SafetyNet Basic integrity Pass CTS profile match Pass Play Protect certification Device is certified...

forum.xda-developers.com

"Installing Magisk for the first time REQUIRES a full data wipe" according to https://topjohnwu.github.io/Magisk/install.html, which I would like to avod.

in order to flash with magisk zygisk support

Not Verify

My Phone (Cubot Power, Android 8.1) always shows a red text in the top right corner of the screen saying "Not Veify". It shows this message since I reinstalled my stock rom with the SP Flash tool. If anyone knows a way to get rid of this message...

forum.xda-developers.com

or to edit the build.prop

How to remove "not verify" red text on a mediatek android phone

This error as seen in the screenshot below is usually as a result of formatting certain partitions on a mediatek android phone while flashing firmware i.e flashing firmware using format all + download

www.hovatek.com

The other possibility would be to install e.g. LeOS GSI or Caos Treble GSI and install Osmand+ using f-droid (minimum google with LeOS). Does the compass work in LeOS or Caos?
It seems easy to flash a custom rom with the help of
fastboot flash LeOS according to

Standard Android 10 and above (with dynamic partition) · Wiki · LeOS / LeOS-Wiki · GitLab

Wiki for LeOS users

gitlab.com

Which partitiions do I have to format before flashing LeOS?

 

[x53]

Has anyone an idea how to increase earpiece volume? In comparison to other phones earpiece volume is way to low during calls, particular in noisy enviroments. I own two KKM2. With both i'm unsatisfied. Using stock rom or gsi rom doesn't matter because they all use audio_policy_configuaration*.xml in the vendor partition (hope I'm right). So I'm open to any suggestion, e.g. editing these audio-xml files (but where?) , changing earpiece physically with a louder one (ist there any?), hidden menus (*#*#???#*#*), whatever....

 

[moonraver]

Has anyone an idea how to increase earpiece volume? In comparison to other phones earpiece volume is way to low during calls, particular in noisy enviroments. I own two KKM2. With both i'm unsatisfied. Using stock rom or gsi rom doesn't matter because they all use audio_policy_configuaration*.xml in the vendor partition (hope I'm right). So I'm open to any suggestion, e.g. editing these audio-xml files (but where?) , changing earpiece physically with a louder one (ist there any?), hidden menus (*#*#???#*#*), whatever....

I was dealing with increasing volume of BACK speaker of all KKMs. I wasn't successful but I can give you a hint but you must be really careful and first read something about this. It is called Engineer mode:
MTK EngineerMode in stock rom of KKM3 - dial *#*#3646633#*#*
Find codes for KKM2, maybe it is the same as KKM3

 

[x53]

Thanks for your reply. I already tried MTK EngineerMode. But I couldn't find anything related to earpiece volume. Had I missed something?

 

[moonraver]

Thanks for your reply. I already tried MTK EngineerMode. But I couldn't find anything related to earpiece volume. Had I missed something?

I have found something. Maybe this could help you:

[GUIDE][MTK] Using Engineering mode to increase audio output

So i've heard people saying that engineered mode doesn't work now ill explain how to use it rightfully and you'll find the difference yourself. (works on any rom) Basics: -Level- it means the level on your volume slider 0 for minimum when slider...

forum.xda-developers.com

How to Increase Maximum Volume on Mediatek-Based Android Devices through Engineer Mode

Android devices often have varying levels of “maximum” volume output – even if you’re using the same exact headset between devices. This may not always be

appuals.com

 

[x53]

Thanks, unfortunately it doesn't work and the KKM2 Engineering Mode does a little differ to other devices. So I was going to "Hardware Testing" -> Audio -> Volume -> Voice. IMHO here I found nothing to set earpiece gain a little louder.

Enclosed the whole list of items I could change:
- NB, WB, SWB
- Receiver, Receiver_SV, HAC, Headset, Headphone, Speaker, Speaker_SV, Headset(5-pole), Headset(5-pole+ANC),TTY,Lpbk_Handset,Lpbk_Headset,Lpbk_Handsfree, USB
- GSM (here is nothing to change)
- UL Gain: integer between 72 and 252
- Sideton Gain (Stf): 0 ... 240
- DL Gain: here you can define 7 steps from Index 0 to Index 6

I thought Receiver and UL Gain 252 does the trick, but no luck. In the second item I miss "Earpiece" in the toggle menu. However thanks a lot for trying.

 

[moonraver]

A new device from Cubot is comming..........Kingkong Power

CUBOT FILE DOWNLOAD

Cubot Offical Website for Smartphones and Wearables. Simple and Trust, Cubot aims to be a credit worthy high-tech corporation in the world.

cubot.net

Seems like it is not "mini" but something with bigger battery. Device with similar name "Cubot Power" has been released in 2018 with 6000 mAh battery.

 

[birdibird]

I flashed CUBOT_KINGKONG MINI2_A061C_V11_20220817 on my kingkong mini (Version1).
Now the compass works (the kingkong mini is used only for bicycle navigation)!
However I get the message "tee key / google key" because I formatted the whole file structure (option automatic formatting) without backup (not the best thing to do...)
There is a workaround, but I would have to install magisk

[Discussion] Magisk - The Age of Zygisk.

This is a discussion and help thread for the newer versions of Magisk. The main goal of this thread is to help users migrate to Magisk v24+ SafetyNet Basic integrity Pass CTS profile match Pass Play Protect certification Device is certified...

forum.xda-developers.com

"Installing Magisk for the first time REQUIRES a full data wipe" according to https://topjohnwu.github.io/Magisk/install.html, which I would like to avod.

in order to flash with magisk zygisk support

Not Verify

My Phone (Cubot Power, Android 8.1) always shows a red text in the top right corner of the screen saying "Not Veify". It shows this message since I reinstalled my stock rom with the SP Flash tool. If anyone knows a way to get rid of this message...

forum.xda-developers.com

or to edit the build.prop

How to remove "not verify" red text on a mediatek android phone

This error as seen in the screenshot below is usually as a result of formatting certain partitions on a mediatek android phone while flashing firmware i.e flashing firmware using format all + download

www.hovatek.com

The other possibility would be to install e.g. LeOS GSI or Caos Treble GSI and install Osmand+ using f-droid (minimum google with LeOS). Does the compass work in LeOS or Caos?
It seems easy to flash a custom rom with the help of
fastboot flash LeOS according to

Standard Android 10 and above (with dynamic partition) · Wiki · LeOS / LeOS-Wiki · GitLab

Wiki for LeOS users

gitlab.com

Which partitiions do I have to format before flashing LeOS?

I once formatted a mtk device without backing up nvdata and was able to restore serial and imei with a MTK tool.
What sometimes also works is to flash back the original rom, then backup nvdata (eg with twrp) and then reflash the new rom and restore nvdata

You don´t have to format anything before flashing LeOS. Just follow the instructions on the LeOS wiki.

For Magisk you also do not have to wipe anything. Just patch the boot.img in the Magisk, flash it then with SPflashtool or fastboot (in bootloader) or twrp.

Compass works in LeOS