yashsingh1/xdaforums huggingface dataset:
[Upgrading, Modifying and Unlocking] Rainles7:
Hello i want to turn this phone into router when i am at home, sharing the unlimited data internet to my PC thru usb cable or Wifi, my problem is that when i get a call it switches to 3G from 4G, and it has a micro disconnection in the switch, and of course lower speed during the call, but i looked for a fix, and i ended up finding about VoLTE (4g calls), if i could enable that i could force the phone to stay in 4g and have propper internet with being able to call and receive calls. I have checked phone specifications and its supoused to support VoLTE.

Edit: i installed stock rom, idk if my simcard doesnt have VoLTE activated, but i cant use it.

BTW anyone has any idea how to root stock ROM for King Kong Mini? its my first time rooting stock rom, i tried flashing both SuperSu and Magisc through TWRP recovery, but they simply not appear when i turn on the phone.
[Upgrading, Modifying and Unlocking] acmahello:
hello everybody. i new one and try to format and download with spflash. and get Remove Not Verified Red Text Watermark on the screen.

And i contac to cubot admin and them reply adays with keys kkm3 you need down file SN_Writer_Tool_exe with 2 imei of your phone when you get pass .remove usb and with boot normal.

and help me how to up another rom to ArrowOS and new Evolution X ( only 1 file img)
[Upgrading, Modifying and Unlocking] cablephone:
I also get WiFi errors after installing LineageOS 18 (vanilla image) on a KKM2. It always says: Failed to connect. 2.4 or 5 GHz does not seem to make a difference. Any idea?
[Upgrading, Modifying and Unlocking] landsome:
No idea, sorry. 2.4ghz always worked for me
[Upgrading, Modifying and Unlocking] acmahello:
i was flash lineage-20.0-20230815-UNOFFICIAL-arm64_bvS.img.xz kkm3 and work . lineage 21 new not boot and i try flash more :

ArrowOS-13.1-arm64_bvN-Unofficial.img work

LeOS-U-VNDK-arm64- no playstore_bvN.img

SuperiorOS_A12L-RO-arm64-bvN no playstore

AfterLife_A13-RO-arm64-bgN-slim_20240119 no faceid

ColtOS_A13-RO-arm64-bgN-slim_20240124 no faceid

system-td-arm64-ab-vanillako no playstore

DerpFest-arm64_bvN-14.0-unofficial-20231221 work ok and evolution and evolution plus work ok well choose rom bellow 4G can flash . i use adb fastboot to flash

AlphaDroid-RO and RisingOS work but not try much.

Bliss rom i can't flash because large 4G .everyone can help me how flash big rom
[Upgrading, Modifying and Unlocking] cablephone:
I found out that it's not the frequency but the security protocol.

I just tried an old WiFi access point which only supports 2.4GHz and it worked but then I made sure to set the hotspot on my travel laptop to 2.4GHz and it failed. It's noteworthy that 5GHz are listed though. Same error trying to connect to a Zyxel NWA55AXE access point which can do both 2.4 and 5.

So I changed the security protocol from WPA2-PSK to WPA-PSK and the phone was able to connect, even to the 5GHz network. And the WiFi hotspot on the travel laptop works too if I disable WiFi security.

So the KKM2 phone is actually able to connect to 5GHz networks. But it cannot connect to any network which requires WPA2-PSK, apparently. Since many networks use WPA2, that would be a major bug! Can anyone confirm?

Same issue on KKM3 with stock rom.
[Upgrading, Modifying and Unlocking] pyro68:
Hello, test both 2,4 and 5ghz on WPA2-AES. No problem with kkm3 with stock rom and arrowos 13.1 .
[Upgrading, Modifying and Unlocking] Vilkoko:
Hello,

I lost my KKM2 and bought a new KKM2 Pro.

I'd like to install Lineage. Is lineage-19.1-20240419-UNOFFICIAL-arm64_bgN-vndklite.img.xz from Andyyan suitable ?

I plan to use this p 25 tutorial, is it still up to date ?

Thank you
[Upgrading, Modifying and Unlocking] sgbmzm:
Thanks! I want to use a MODDED STOCK ROM but not to have magisk, which means I don't want to have root privileges. How do you do that? Do I need another boot file?
[Upgrading, Modifying and Unlocking] ylavi:
KKM3

Starting from V08 stock ROM, I have tried both

https://xdaforums.com/t/installing-custom-rom-on-cubot-kingkong-mini.4050815/page-36#post-89099238 (first)

and

https://xdaforums.com/t/installing-custom-rom-on-cubot-kingkong-mini.4050815/page-34#post-88637555 (after)

(Thanks to the authors of those)

Despite what is written at the second link about the screen lock working, I have not found it to work. Many GSIs I found boot-loop/fail to boot so I don't even get as far as trying the lock screen settings.

Does anyone have a reproducible method for installing a Treble-Droid-based GSI on the KKM3?

I'm not inclined to try MOD4 because of the Magisk, and am looking for TD in order to have the PHH MTK fixes (among others) because my KKM(1) experience with Bluetooth has been poor and I hope that those fixes may help on the KKM3.

Thanks
[Upgrading, Modifying and Unlocking] FasterPhoneMaster:
Hi! Can someone install Treble Info to KKM3 and post screenshot of the "details" tab here? I would like to know what Treble Info says about "Linker namespace isolation". Is the VNDK on lite mode or not?

That information could help to understand why some builds boot and some does not.
[Upgrading, Modifying and Unlocking] badcodelab:
View attachment 6118270

are you going to try adapting gsi to kkm3?
[Upgrading, Modifying and Unlocking] FasterPhoneMaster:
Thanks! VNDK is not in lite mode so there are others compability issues. I don't what might be the issue.

I have been able to flash evolution_arm64-ab-vndklite-7.9.4-unofficial-20230702 successfully to KKM3 (see here) but when I try to flash OTA update the phone will bootloop. Definitely the phone can boot GSI ROMs but some builds do not work for some reasons.
[Upgrading, Modifying and Unlocking] veloc_h:
flashed gsi with Android 14 on a KKM1 (upgraded to KKM2)

Therefore Luka's sequence did not work. ADB would not see in bootloader mode the areas „System“, „Vendor“ and„Product“ , which are inside of Super. In FastbootD-Mode the command „flash“ increases automatically the size of the original Vendor Partition (was written somewhere on 4pda.to, via google translate).

My steps:

fastboot flashing unlock

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

fastboot flash boot boot.img

fastboot flash recovery recovery.img

These three img files are from the most recent cubot kkm2 rom. I used flashtool version 2020, not the original Cubot flash tool

fastboot reboot fastboot

]fastboot erase system] not sure about this. I had messed up my kkm by formatting everything, therefore vram... was lost. Via flash tool I flashed the cubot kkm2 rom on my kkm1 (I also did a format).

fastboot flash system system-td-arm32_binder64-ab-vanilla.img
[Upgrading, Modifying and Unlocking] ylavi:
The point of that being to get the base install including vendor and product from the KKM2 ROM, even though you are installing a non-stock system on top?

What benefit does a KKM(1) get from doing that?
[Upgrading, Modifying and Unlocking] ylavi:
I would like to share my conclusions from another few hours of attempts to get a GSI working with lockscreen.

As I think someone mentioned earlier, there is a connection between encryption (FBE) and the lock screen; I could see that the commands to set up a lock screen fail due to an encryption system issue.

I tried installing modified vendor partitions with various changes to fstab but mostly when I enabled encryption the GSI wouldn't boot (unlike the stock system).

Reluctantly I gave up on this and will use the KKM3 with stock system for now.
[Upgrading, Modifying and Unlocking] cest73:
Sorry to hear, I didn't get the FM app to work either.

Still it's a nice phone and does alot even without the radio receiver.
[Upgrading, Modifying and Unlocking] landsome:
afaik, the radio does not work in stock either
[Upgrading, Modifying and Unlocking] cest73:
hello,

I tried that procedure but somehow ended up with the sim cards not being active at all - be it fastboot or TWRP each reboot landed me in the said state (no mobile networking)

After flashing to stock i have it back to work .

For the while the sim was not accessible, the phone subsystem was constantly restarting with an error message on Lineage OS

It seems I still lack some information?
[Upgrading, Modifying and Unlocking] cest73:
So far I figured few minor things and errors so I figure I share here for reference

1. I have my KKM running LOS17.1 with stock boot and recovery

2. It is really easy to end up in a recovery boot-loop the way I do it when following the first few posts info, IMHO we need a recap on that

3. The "boot" and "recovery" images are definitely the appropriate kernel with belongings payloads. The "lk" still eludes me, so more reading ahead (time is so short)

4. The Magisk, while seeming the way to go is damn complicated with the payload ping-pong from phone to PC then to phone and back... :silly: that eluded me in the start totally

5. How in the hell did I get TWRP and avoided boot loop with recovery kernel (had GSM working) in the first attempt? Beginner luck?
[Upgrading, Modifying and Unlocking] landsome:
That is strange. I went through that procedure a dozen times and it worked every time.
[Upgrading, Modifying and Unlocking] cest73:
If i had any idea how i managed that (possibly not rebooting one or two times when i should) I would share it right away :silly:
[Upgrading, Modifying and Unlocking] landsome:
Just followed OP, avoiding twrp like the plague. (BTW, AOSP gives you root, unlike LOS.)
[Upgrading, Modifying and Unlocking] cest73:
Ditto :highfive: (TWRP)

But like the LOS better than the AOSP, trying Open Gapps nano next (needs clean install with data wipe on top)
[Upgrading, Modifying and Unlocking] landsome:
AOSP with open gapps works fine in my case.
[Upgrading, Modifying and Unlocking] birdibird:
I've got LOS 17.1 working fine with magisk.

But: If I look at the storage space, it says that I only have a total of 4GB!

How is that possible? Any ideas how to solve that?

edit:

To answer my own question:

I flashed TWRP from post 33 with spflashtool

and with TRWP formatted data and internal storage and flashed Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip

This solved it.

All working fine now.

I am running the oct 12 LOS 17.1 with TWRP, Magisk, microG, Riru, EdXposed, FakeGapps, Fdroid and Aurora successfully

update: I moved to [UNOFFICIAL] LineageOS Q Mod //LOSQ
[Upgrading, Modifying and Unlocking] birdibird:
For anyone who lost the sim signals: this has to do with lk.img.

Make sure you use the correct version.

I upgraded first to the newest official rom from Cubot (v15).

So I had to manually hex edit the lk.img file from that rom, erasing the Orange State message in the file (replacing by 00, google how to do that).

After flashing that edited version, sim signal worked and no Orange State message appeared.
[Upgrading, Modifying and Unlocking] landsome:
On both AOSP and LOS calls drain the battery like crazy. Has anyone had a different experience (and, if yes, found a solution)?
[Upgrading, Modifying and Unlocking] birdibird:
[UNOFFICIAL] LineageOS Q Mod //LOSQ

does not give me any problems with battery drain
[Upgrading, Modifying and Unlocking] landsome:
Thanks. I meant battery drain in calls specifically (otherwise I am fine).

Everything else works ok?
[Upgrading, Modifying and Unlocking] Dutcheee:
I’ve got my KIngkong mini for about a week now.

I really love it. I bought is as a super small rugged backup phone with all the basic options.

I tried over & over but can’t get TWRP working. I tried it with ADB, but when I reboot in to recovery, it’s just recovery and no TWRP.

How do you copy the IMG files with SP tools like in post #33 of this thread?

Using the how-to in post #39 I succesfully flashed LOS 17.1, AOSP GO and now run LOSQ. Don’t forget to data wipe & wipe cache after installing new ROM. Googleapps gave me some headaches. Front cam doesn’t work and in call volume neither. Battery drains withun a day, but I cannot compare to stock, since I ditched the chinese stock rom on day one.

Thanks for all the tutorials in this thread, very helpful! What a great phone, now I just need Root, TWRP and the front cam going and it is usable as a new daily driver:good:
[Upgrading, Modifying and Unlocking] landsome:
I was unable to flash TWRP either. In-call volume is also a no go. But front cam works on both AOSP and LOS17.1. And AOSP gives you root by default. Have not tried LOSQ yet - though if the battery drain during calls continues, I may give it a try.

In my experience, battery life on stock was about as much as on AOSP and LOS.
[Upgrading, Modifying and Unlocking] sauka1:
I have been using LOS on kingkong mini for a few weeks. The first few days I ran without simcard (only wifi) had around 40-50% battery left after 16h of standby with minimal screen time. Just a couple of apps running in the background sending data to various databases.

After putting in a simcard the battery drain started. I even disabled wifi to run only on mobile data but the full battery can drain in less than 12h. Nothing else in terms of settings and usage was changed so I’m suspicious that the sim / mobile data is causing the battery drain. I even tried disabling 4G and run 3G instead to save some power but it didn’t help much.

Have you found a solution to this issue?
[Upgrading, Modifying and Unlocking] landsome:
Same problem here. Tried two different SIMs / providers. I think it's inherent with the phone, no way around it. Also, as noted above, phone calls drain battery massively.

It's the same on LOS and AOSP, in my experience, and it was worse on stock, I think.

It's what prevents me from using it as a daily driver.
[Upgrading, Modifying and Unlocking] baconboy:
Hi! I'm thinking about picking one of these up (and wearing it on my wrist). It seems like rooting and flashing AOSP is a bit tricky still? Or is it all fine and dandy now and everything works? I won't be using the SIM slot. Thanks for all your hard work on this device!
[Upgrading, Modifying and Unlocking] landsome:
Fine and dandy flashing AOSP, which gives you root.
[Upgrading, Modifying and Unlocking] cest73:
When will we get a dedicated section for pur KKM phones?
[Upgrading, Modifying and Unlocking] baconboy:
That's awesome! So no problems with it? Which instructions should I follow in this thread, do you know? Thanks!
[Upgrading, Modifying and Unlocking] landsome:
Those on page one (the OP). Worked ok for me - and I have tried them dozens of times (switching among ROMs).

And do a search for an LK file to get rid of the annoying unlocked bootloader message (no other benefit, though).
[Upgrading, Modifying and Unlocking] baconboy:
So everything on AOSP works? Which ROM are you on now, the one from OP? Battery life OK? It's important as I'm trying this out as a "watch" haha
[Upgrading, Modifying and Unlocking] landsome:
Latest AOSP10 (not 11) by phhusson here: https://github.com/phhusson/treble_experimentations/releases, as instructed in OP (a/b arm32 binder64).

Not "everything" - as discussed here on the forum. No battery usage report. No in-call volume adjustment (but I use headphones).

Battery life better than stock (make sure no app disrupts sleep). But calls eat battery up quickly (same in stock).

All in all, very dependable.
[Upgrading, Modifying and Unlocking] baconboy:
Thanks! So I want system-quack-arm32_binder64-ab-gapps.img.xz? 10.0 v222?

And sorry when it says: Unzip the stock ROM and reboot the device to bootloader, connect via USB and unlock via:

Code:

sudo fastboot flashing unlock

how do I initiate that ADB to input the code? And where do I do it? In the root of the phone?

Also did you use magisk or TWRP? Thanks again!
[Upgrading, Modifying and Unlocking] landsome:
Install minimal adb & fastboot tool.

Do not try to install either magisk or, my advice, twrp.
[Upgrading, Modifying and Unlocking] mxjohn944:
How is Bluetooth on the King Kong Mini with AOSP / LineageOS? I'd like to use the King Kong Mini as a control unit for some Bluetooth based gear. This means that the phone does not have to be particularly powerful (no beefy CPU or anything), but it needs to have good, stable Bluetooth support, because the Bluetooth gear (using Bluetooth LE) needs to be communicated with every ~4-5 minutes or so.

Form factor wise, the KKM would be perfect. Rugged, small (so it does not take up much room when I carry it with me in addition to my main phone), IPS screen (avoids burn-ins). This is why I am trying to make it work for me.

But I tried the KKM with its stock Android installation, and its Bluetooth connectivity is sometimes really bad. BTLE devices sometimes aren't connected at all. Now, the ROM on the KKM uses Project Treble. So I wonder if slapping AOSP on it would even change anything. I suspect that Bluetooth issues could be caused by bugs below the HAL / HIDL, and therefore out of reach of any custom Android installation.

But if the bug lies in some Cubot extras in their Android installation, then AOSP might help.

So - any information on Bluetooth (LE)?
[Upgrading, Modifying and Unlocking] landsome:
All I can report it aosp works ok with bt headphones. Nothing more sophisticated.
[Upgrading, Modifying and Unlocking] baconboy:
Excellent! Downloaded. So you don't use Magisck or TWRP, the image is already rooted?
[Upgrading, Modifying and Unlocking] cest73:
Bluetooth works without issues for me with LOS 17.1 and torque lite although the screen drains the nimble 2000mah battery quite fast
[Upgrading, Modifying and Unlocking] mxjohn944:
I am stuck in the Orange State. I did flash the patched lk.img file, but the device still reboots after 5 seconds. I am confused what steps truly are necessary, this thread has gotten huge by now, and contains lots of steps that may not be required. So, what did you do to solve the reboot problem?

EDIT: Nevermind, I forgot to flash the vbmeta.img with the command from the OP: fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
[Upgrading, Modifying and Unlocking] landsome:
Yes, and Magisk and TWRP are problem prone on the kkm
[Upgrading, Modifying and Unlocking] mxjohn944:
What problems are those? I didn't install either of those, I'm just curious.
[Upgrading, Modifying and Unlocking] birdibird:
No, they are not a problem. I have TWRP and Magisk and they are working fine. See my posts 2 pages ago.
[Upgrading, Modifying and Unlocking] landsome:
Happy to know it works. I had a hard time doing it (and then stopped trying).
[Upgrading, Modifying and Unlocking] landsome:
Anyone tried AOSP11 or LOS18 on the KKM?
[Upgrading, Modifying and Unlocking] baconboy:
My KingKing Mini is nearly here, but can anyone confirm if you can double tap the screen to wake?

I am going to try to put this on my wrist like a watch. Is there an APK or mod that can add tilt to wake like an Android Watch does anyone know?

I'll post pictures of the 3D watch case (if it works)
[Upgrading, Modifying and Unlocking] landsome:
Not on aosp
[Upgrading, Modifying and Unlocking] baconboy:
Thanks! Also boo! Any apps that might wake it up? maybe a face unlock or tilt to unlock?
[Upgrading, Modifying and Unlocking] landsome:
LOS has more options related to these things than AOSP, but I do not remember all the details. No face unlock, tho.
[Upgrading, Modifying and Unlocking] gunar74:
Does anyone have Magisk rooted with working front camera?

If I have Magisk, front camera does not work...

Another problem is, that I can not pair new blutooth devices. It shows the pairing screen for a second, then disappears. If I am fast and the device does not need a PIN code, I can press confirm and pair. If it needs a PIN code, I have to flash back stock boot.img, pair, then flash magisk_patched again.
[Upgrading, Modifying and Unlocking] baconboy:
What's the latest ROM everyone's using? Just received my new Mini and gonna flash AOSP 10 from here https://github.com/phhusson/treble_experimentations/releases?after=v300.a
[Upgrading, Modifying and Unlocking] landsome:
That's the one. Or one of the Android 10 LOSs - by Andy Yan or the LOSQ project.

Please report your impressions here.
[Upgrading, Modifying and Unlocking] baconboy:
No one tried the v11 from that page yet? I am not brave enough
[Upgrading, Modifying and Unlocking] baconboy:
I hate adb! I'm failing at the first hurdle in the OP.

Upgraded to new official Cubot ROM with SPFlash, enabled OEM Unlocking and USB Debugging. Installed Official Cubot Windows 10 drivers (well, tried, not sure it worked?).

Recovery mode, no dice. Please see pics

View attachment 5153449

Phone doesnt show up in Windows in recovery mode. When I boot it up with volume down button I get a list in Chinese. Where am I supposed to initiate the first ADB command? In the phone folder on the PC right?

What's wrong?
[Upgrading, Modifying and Unlocking] baconboy:
Also guide says

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

Where is vbmeta.img? I don't have that and it's not in the OP. OP is very confusing!
[Upgrading, Modifying and Unlocking] gunar74:
Sudo is a Linux command as far as I know, leave it and begin the command with fastboot. Also you need fastboot mode, not recovery. Turn on phone with VOL+, select Fastboot in the middle and confirm with VOL-. Vbmeta.img is part of the stock ROM, you will find it in the package.
[Upgrading, Modifying and Unlocking] baconboy:
Thank you so much! So I do the fastboot and vbmeta.img commands in a PowerShell window in the stock ROM folder?
[Upgrading, Modifying and Unlocking] gunar74:
Better to copy vbmeta.img to the platform-tools folder, I think. This is the folder, where the fastboot.exe, adb.exe etc. files exists. Of course, without fastboot.exe, the command will not work.
[Upgrading, Modifying and Unlocking] baconboy:
I only have the minimal_adb_fastboot_v1.4.3_setup file in the OP. Should I download and install the platform-tools?
[Upgrading, Modifying and Unlocking] gunar74:
No, it is enough, what you have.
[Upgrading, Modifying and Unlocking] baconboy:
Stuck like this now. Any pointers? It's not showing up under ADB Devices. In Device Manager is shows up as Unknown USB Device (Device Descriptor Request Failed). I have installed the drivers!

View attachment 5155273

View attachment 5155275
[Upgrading, Modifying and Unlocking] baconboy:
This is so confusing. So in Fastboot, the phone can't be seen.

When I boot the phone, I can see it in File Explorer, look at the contents, and it shows up in ADB Devices. Still get the USB error in file manager.

Any tips?
[Upgrading, Modifying and Unlocking] gunar74:
You need to have the MTK driver auto installer. I think I have downloaded it, but now I can not find on Cubot's site.

The file name: WIN7-WIN8 驱动_EXE_v5.1453.03.rar

Google it.
[Upgrading, Modifying and Unlocking] baconboy:
OK, I've tried it on another computer. No errors, all installed ok. BUT

The phone isn't recognized when I click Fastboot mode. Doesn't show up under Adb devices. It does show up when booted normally.

What's going on? Is my fast boot screwed? When I click fastboot mode in reboot nothing happens.

Thanks for all your patience!
[Upgrading, Modifying and Unlocking] baconboy:
OK, in fastboot mode the phone shows up in device manager as Android, drivers are not installed.

I googled and installed WIN7-WIN8 驱动_EXE_v5.1453.03.rar

Didn't work
[Upgrading, Modifying and Unlocking] gunar74:
You may try another USB port. If you have a chance, use USB 2.0 port, not 3.0.
[Upgrading, Modifying and Unlocking] baconboy:
Different computers, all the USB ports, different cables. Think it's just the phone! I'll have to use it stock. Oh well! Won't be too bad I guess
[Upgrading, Modifying and Unlocking] landsome:
First, the KKM has no recovery, just fastboot. Which, as noted above, is what you need.

Second, I also failed to get fastboot to work withe the provided MTK drivers. I used one of these, do not remember which (I may have even used Win8 drivers on Win 10): https://mega.nz/file/BlhQmLyS#fyJ--UBjcbMynubQmzva-mi9ZJgwv4PgPNhbCrr8erQ

(This is my mega drive, I will keep the files online for one week or until you confirm the download.)