yashsingh1/xdaforums huggingface dataset:
[Upgrading, Modifying and Unlocking] birdibird:
It is updated hardware drivers, vendor security etc.

Not necessary if you don't want to bother.

I didn't notice yet any difference hardware wise, but will update here if I do.
[Upgrading, Modifying and Unlocking] moonraver:
I'll be really into it if it helps with "crackling" sound and solves my problem with calling via USB-C dongle with headphones :)))

Please check it out!

Anyway, thank you for that procedure you wrote.
[Upgrading, Modifying and Unlocking] dank2019:
AOSP 12 and King Mini 1 (KKM1)

Hi, has anyone AOSP 12 (e.g. the treble one) successfully running with the KKM1? I always have the problem, that my phone can't establish a data connection everything else looks fine. But without a mobile data connection, its more or less unusable. Any idea what I do wrong? Downgrade to 11 works (after wipe) with the same provider configuration without any problem.
[Upgrading, Modifying and Unlocking] ken.N:
Hi @birdibird, thank you so much for your dedicated work. I follow your steps and I got stuck after this step:

- fastboot reboot fastboot

the phone restarts with orange mode and then this screen bellow, there is no any "dead android" screen. Did I miss something ?
[Upgrading, Modifying and Unlocking] birdibird:
That's correct, that's fastbootd mode.
[Upgrading, Modifying and Unlocking] ken.N:
@birdibird, thank you for your reply. so what do I suppose to do next ? because from pc, in the cmd:

C:\Users\KEN\Desktop\platform-tools>fastboot reboot fastboot

Rebooting into fastboot OKAY [ 0.002s]

< waiting for any device >

it keeps hanging like that and I can not type anything. Please help me.
[Upgrading, Modifying and Unlocking] birdibird:
Have you tried replugging the usb cable to your phone?
[Upgrading, Modifying and Unlocking] ken.N:
@birdibird Yes I tried unplug the cable, then plug the cable in, my pc recognized the connected device by the windows sound, but no help. The cmd still hung for waiting the device. I read some comments mentioned that after:

- fastboot reboot fastboot

the phone will display a "dead android" screen, but mine is not. Do you think there's something wrong with my phone ?

Also, I succeeded re-flash the phone with CUBOT_KINGKONG MINI2_A061C_V10_20220119 rom with SP flash tool. then I tried all your steps again but the problem is still there.

This is platform version I used:

C:\Users\KEN\Desktop\platform-tools>adb --version

Android Debug Bridge version 1.0.41

Version 33.0.2-8557947

Installed as C:\Users\KEN\Desktop\platform-tools\adb.exe
[Upgrading, Modifying and Unlocking] badcodelab:
on windows you need to switch driver in device manager from Other > ? KINGKONG MINI

to Android Phone > Android Bootloader Interface
[Upgrading, Modifying and Unlocking] birdibird:
You should not wait for the dead Android, I didn't write that anywhere. That only shows if you boot into recovery and we are working in fastbootd.

Your phone was rebooted perfectly into fastbootd as I said.

I think you only have to do ctrl-c in the command prompt to stop the command prompt waiting, unplug the cable from your phone, and then enter the fastboot flash system command and then plug the cable back in.

That should work.
[Upgrading, Modifying and Unlocking] moonraver:
Absolutely correct! First, he must deal with installing correct drivers in Windows for that second FASTBOOT mode too and not to forget to run Windows with DISABLE DRIVER VERIFICATION just for sure!!! I was dealing with these 2 things for a looong time to understand why it always stuck on < waiting for any device >
[Upgrading, Modifying and Unlocking] ken.N:
guys, I DID IT !!!!! @badcodelab @moonraver I follow your advice, Disable Driver Verification in windows, then switch driver in device manager, it works perfectly.

@birdibird you are right, the fastboot screen is right and there is no problem with it. It's windows driver issue.

Thank you guys for greatly dedicated support. @badcodelab @moonraver @birdibird
[Upgrading, Modifying and Unlocking] badcodelab:
unfortunately it was partially a lie

KINGKONG MINI 2 Pro

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

cubot.net

helio p22, 4/64, others - identically same with kkm2, nothing to be excited about

ps: no more off-top posts about other devices :)
[Upgrading, Modifying and Unlocking] moonraver:
Nothing to be really excited of, but:

1. 8 cores/8 threads, same 12 nm FinFET technolgy, same year of SoC production = EATS more of 3000mAh battery in my opinion

2. what about that fake second back camera? will it be the same?

3. maybe finally better FPS for main back camera? this new camera module can be different

4. arm 64-bit Andorid architecture, not arm 32-bit with 64 binder
[Upgrading, Modifying and Unlocking] TrickyJoe:
Flashed stock older version firmware (was trying to install twrp) and updated leos 12 system june version. Mobile data works fine.
[Upgrading, Modifying and Unlocking] dank2019:
I installed leos12. Mobile data works without any issues. Thank you.
[Upgrading, Modifying and Unlocking] badcodelab:
maybe, but not sure about NEW camera module

full specs https://cubot.net/phones/Kingkong-mini2-pro-specs/82

fake 2nd camera eye is present
[Upgrading, Modifying and Unlocking] moonraver:
SAR values (EU) in W/kg from official manual on CUBOT website. Distance can be 0,5 - 1,5 cm.

KKM2 PRO vs KKM2

Head: 1,139 W/kg vs. 0,566

Body-worn: 1,04 vs. 0,907 (distance 0,5 mm for KKM2 only)

Hotspot: 1,04 vs. 1,408

Limbs: 1,887 vs. 2,891

Make your own opinion.
[Upgrading, Modifying and Unlocking] rubenvd:
I'm trying to get lineage OS 19 to run on my KKM2. The reason for this is that the phone always hangs every time I get a notification while the phone is on standby, be it whatsapp or facebook. It's completely blocked and I can only recover it by longpressing the power button. Pretty annoying. I'd thought to get some more info on the error by checking logs, which of course is only available if the device is rooted, so might as well just upload another OS.

I was following the steps as explained in post #163. After the step "fastboot reboot fastboot", the device is locked in a bootloop, and showing the following message:

Orange State
Your device has been unlocked and can't be trusted
Your device will boot in 5 seconds

But yeah it doesn't boot at all. Is there any recovery procedure available, or a way to get into fastboot mode so I can continue the procedure?
[Upgrading, Modifying and Unlocking] moonraver:
Question is: do you have a right image file? I mean a64-bvS or a64-bvN.

If you want to go back to stock, it is simple. Just follow this:

CUBOT_CUBOT_KINGKONG MINI2_A061C_V10_20220119_CUBOT Firmware

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

Then you can do the flash procedure again:

Enable developer options:

OEM unlocking

USB debugging

Under windows (check if you have correctly installed drivers for ADB state):

adb devices

adb reboot bootloader

fastboot flashing unlock

(file from the stock ROM from cubot.net)

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

fastboot reboot fastboot

Now check AGAIN if you have installed MTK drivers correctly in windows

fastboot flash system (CustomROMname.img)

After finish: VOLUME DOWN and select POWER OFF.

Run into Recovery mode and WIPE DATA/FACTORY RESET

If you have bootloop (files from stock rom):

- fastboot flash boot boot.img

- fastboot flash recovery recovery.img

If you don't want to be tracked, forget about Linege, it is not fully degoogled.

Use LeOS instead: https://leos-gsi.de/

I have tried LeOS:

- A12 AOSP based,

- A12 lineage based,

- A11 lineage based,

- A10 lineage based (this one is fastest and smoothest for KKM2, with no bugs and with many customizations)
[Upgrading, Modifying and Unlocking] rubenvd:
After asking this question, I found this recovery procedure and I succesfully reflashed my KKM2. The thing I did wrong in the procedure was to take the KKM1 firmware and burn it on my KKM2. Rookie mistake...

Anyway, after reflashing the KKM2 stock rom, it seems my original bug was fixed. So I'll stay now on just android until I see this bug pop up again. Thanks for your help anyway, and thanks for the suggestion of LeOS.
[Upgrading, Modifying and Unlocking] plusdy88:
@Ce3apyc, with or without custom ROM, not on kingkong mini, but mini 2, I unlocked mine and I can boot into fastboot mode and into recovery mode (and "normal"), but I still wonder how to now access root to delete google bloat?

Anyone using the mini 2 also?
[Upgrading, Modifying and Unlocking] moonraver:
If you use STOCK rom, just disable apps in settings, many of them (included system apps) can be disabled in KKM2. I don't recommend uninstalling because of dependencies (own experiences).

If they can not be disabled just use adb shell:

How to uninstall carrier/OEM bloatware without root access

If you want to get rid of carrier/OEM apps from your phone, here's how you can uninstall bloatware from your device without root access!

www.xda-developers.com
[Upgrading, Modifying and Unlocking] plusdy88:
Thanks moonraver! I am working through your linked docu, will report back 🙂
[Upgrading, Modifying and Unlocking] kkm6761:
Well, KKM2 Pro is out, looks like KKM and KKM2. Processor is MTK6762, 4GB RAM. It indeed is overpriced. For double that you can get iPhone 12/13 mini.

For consistency, it is called KKM2 Pro, but it is renamed to Spotlight.

For KKM2 owners, it just is not worth the "upgrade".
[Upgrading, Modifying and Unlocking] badcodelab:
$130, still overpriced tho
[Upgrading, Modifying and Unlocking] kkm6761:
130 is ok, I paid 80 for KKM1 in promotion. did not see the 130 price. Pocket is overpriced for being almost the same so many years later.
[Upgrading, Modifying and Unlocking] badcodelab:
really?

from my experience pocket is way better than kkm2 and i believe should be even better than kkm2pro
[Upgrading, Modifying and Unlocking] kkm6761:
It has nfc, which is nice. hard to change custom rom being unisoc chip.
[Upgrading, Modifying and Unlocking] moonraver:
higher SAR values, no protection against water and dust, not rugged
[Upgrading, Modifying and Unlocking] badcodelab:
is it so significant?

agree, it's also thicker (13.1mm)
[Upgrading, Modifying and Unlocking] JairoK:
King Kong Mini 2 Pro firmware - https://www.cubot.net/platform/Support/detail/id/625/cid/82.html- have anybody tried to flash it on non Pro ?
[Upgrading, Modifying and Unlocking] Vuche:
Won't work. I tried for the fun of it!

Flash with SP Flash tool and scatter file from the KKM2Pro will give you device error (not the same board, MT6762 Vs MT6761).

Flashing KKM2 V10 original ROM, then boot into the setup screen to make sure everything works, then flash super.img from KKM2PRO will work, but won't boot pass the white Cubot start screen.

I guess your better off installing AOSP or LeOS using birdibird instructions on page 23, especially if you use your KKM on a daily basis.
[Upgrading, Modifying and Unlocking] kkm6761:
is kkm2pro arm32/64 binder or arm64?
[Upgrading, Modifying and Unlocking] badcodelab:
arm64
[Upgrading, Modifying and Unlocking] Truelan:
I bought and test gsi rom on KKM2Pro.

just same as KKM2 flashing process.

no need to flash boot, recovery.

Don't forget flashing blank vbmeta.

if you flash GSI Rom, you should use Arm64 A/B Rom. not A only.

phh's suggested treble checking app was right.

but you could not flash because of insufficient space.

so you should delete ( not erase) product partition.

list what gsi I flashed and result.

1. eremitein's A11 ROM

- android logo loop.

- maybe work. but, I waited about 15 minutes. so, gave up.

2. A12 GSI ROM include PHH's : flashed but, could not install apk.

- most flashed and booted.

- could not install apk. don't know why. I have no time to inspect.

- PHH's gsi v414, v415 does not worked.

3. Corvus 3.2S

- only rom that could install apk's.

- little buggy in some built-in app. but does not affect much.

- about 20 hours have no problem.
[Upgrading, Modifying and Unlocking] kkm6761:
i never managed to boot corvus on kkm1. stuck on crow.
[Upgrading, Modifying and Unlocking] Truelan:
just duplicated thread.
[Upgrading, Modifying and Unlocking] Truelan:
I'm idiot.

I found that apk copied from my pc does not accept A12 Rom.

so i changed to direct download and all A12 Rom(with some exception) worked perfect.
[Upgrading, Modifying and Unlocking] orangestate:
So i got myself a KKM2 Pro. This is an native arm64, not an binder64.

The procedure was nearly the same as in #163.

This is what I did:

Download KKM2 Pro stock rom from Cubot website and unpack it somewhere.

Download product_gsi.img from this post.

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

adb reboot bootloader

once in bootloader mode

fastboot flashing unlock

Then confirm unlock on the phone

Note the location of the vbmeta.img, boot.img and recovery.img files from the stock ROM

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

fastboot flash boot boot.img

fastboot flash recovery recovery.img

reboot to fastboot

fastboot reboot fastboot

After device is in real fastboot mode (the screen is different to that of bootloader fastboot mode)

flash product_gsi.img as per aforementioned post

fastboot flash product product_gsi.img

finally flash system

fastboot flash system SYSTEM.img

I used system-squeak-arm64-ab-vndklite-gapps-secure.img.xz from phh.

Device boots and looks fine, but no further tests were made yet. Will report back if i had time to test.

Bonus steps:

i also flashed lk_patched.img to remove the orange state warning. I modified the stock v02 lk.img.

reboot to bootloader

adb reboot bootloader

fastboot flash lk lk_patched.img
[Upgrading, Modifying and Unlocking] moonraver:
What about back camera? Does it still record video with 15 fps?

What about back speaker? Is it still weak during PHONE CALL?
[Upgrading, Modifying and Unlocking] moonraver:
New phone - CUBOT POCKET 3???!!

Something new is maybe going to be announced soon. Cubot has made a new empty place on their support web site called POCKET 3 for this year 2022.

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

My next question:

Has anybody tested KKM2 PRO yet? From youtube tests I can see that back camera can finally capture 30fps video (not like KKM2 - 15fps) but I am really interested in back speaker during calls if it is still weak like in KKM2.
[Upgrading, Modifying and Unlocking] Vuche:
And apparently from Cubot website support, a new King Kong 6 should be coming soon too! Hopefully with 5G support?
[Upgrading, Modifying and Unlocking] badcodelab:
i'll quote myself from another thread:

also cubot's support ensured me it'll have nfc too but not fingerprint scanner

and we should wait couple months...

KingKong 6

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

cubot.net
[Upgrading, Modifying and Unlocking] moonraver:
I have noticed a serious problem in latest official KKM2 Stock Rom (CUBOT_KINGKONG MINI2_A061C_V10_20220119 ...........release date 2022-06-13).

There is a problem with camera focusing (it takes long time or can not be focused at all) in 3rd party apps especially Hedgecam2 and Opencamera either in this Stock ROM or in custom ROMs installed after this latest Stock ROM. Probably Cubot have made some changes in camera drivers.

With flashing Stock ROM CUBOT_KINGKONG MINI2_A061C_V07_20201113 (or with custom ROM afterwards) camera focusing works great as usually.
[Upgrading, Modifying and Unlocking] Vuche:
Did you try with a custom ROM after installing the official V10 if it has the same issue? I'll try it later today on mine.

Please send a message with bug description to Cubot, they might correct the problem in the next update (or not!)

Thanks anyway for the information.

Edit: sorry, I just read your post throughouly and see you tried other ROMs after the update ...
[Upgrading, Modifying and Unlocking] badcodelab:
sorry folks but
[Upgrading, Modifying and Unlocking] moonraver:
Forget about Cubot support. I have tried it for many times, it is completely useless!!! You will ask a question and will get answer for something else. Like they don't read it at all.
[Upgrading, Modifying and Unlocking] moonraver:
Please send a link, couldn't find it. I am really interested. I have almost bought KKM2 Pro but it seems that camera is still weak as well as Helio P22. Maybe this will be better one. Thanx
[Upgrading, Modifying and Unlocking] badcodelab:
official fb page https://www.facebook.com/CUBOTOFFICIAL/

no any info yet
[Upgrading, Modifying and Unlocking] badcodelab:
kkm3 specs https://cubot.net/phones/KingKong-Mini-3-specs/86

looks pretty similar to pocket 3

https://aliexpress.com/item/1005004791273659.html

start of sale on october, 17th

CUBOT Mobile

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
[Upgrading, Modifying and Unlocking] kkm6761:
Ok, Cubot is killing compact phones. Since KKM, there is no progress. Pocket3/P30 is the same size is Qin 2 Pro, but with 0.5" smaller screen, KKM3 is almost same size as iPhone mini (narrower), but also with almost 1" smaller screen. Cubot phones have huge bezels (I am not asking edge to edge) and are very thick, almost as my old Samsung flipphone.
[Upgrading, Modifying and Unlocking] badcodelab:
kkm3 is smaller and thinner than atom l and also has 0.5'' bigger screen

sounds good enough for me

the only concern is about camera, just hope they put in something reliable this time
[Upgrading, Modifying and Unlocking] moonraver:
exactly! camera is something what should be improved. 20 Mpx should be enough but what about sensor's size and size of senzors's pixel?

BTW: have you mentioned that there is NO back speaker? I wonder where it is....
[Upgrading, Modifying and Unlocking] moonraver:
A really BIG thank you for this procedure. It really saved me a lot of time after buying KKM2 Pro today.
[Upgrading, Modifying and Unlocking] moonraver:
Today I bought a new KKM2 PRO. KKM3 has price over 200 Euros (device not officially announced yet) and is bigger with same battery............so not much suitable for me.

Is somebody interested in a small comparison KKM2 vs KKM2 Pro? At least in this moment I can say that there is a big improvement in camera. I have tested StockROM and now I am testing LeOS BvN ROM.
[Upgrading, Modifying and Unlocking] moonraver:
Has anybody noticed that Cubot King Kong Mini 3 has NO loudspeaker???!!! At least on it's back side as usually. I'm still waiting for user manual to be announced on website especially for SAR values.
[Upgrading, Modifying and Unlocking] badcodelab:
and what?

same as pocket, phone speaker should work fine in both ways
[Upgrading, Modifying and Unlocking] badcodelab:
sorry folks again but can't hide this

cubot's support is kind to me and here are some news about the cameras

front - 5MP OV5670

rear - 20MP Samsung ISOCELL 2T7 (S5K2T7SP) or 20MP Sony IMX350 (which one is better?)

unfortunately you can get one or another by total random :(

View attachment 5731231

tiny upd: cubot's ali shop says that first devices have samsung sensors

and now we've got a price

$110 during the first week of sale

ps: probably we need to create a separate thread for kkm3 now
[Upgrading, Modifying and Unlocking] birdibird:
A new KKM2 firmware has been released:

CUBOT_CUBOT_KINGKONG MINI2_A061C_V11_20220817_CUBOT Firmware

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

maybe they did listen?
[Upgrading, Modifying and Unlocking] birdibird:
Ok, I flashed the new firmware over my current LeOS 19.1 system.

Here is how you do that:

-Open SPFlashtool and select the scatter txt

-UNTICK super and userdata (!!!!!!!!!)

-optional (removes Orange state):

double click the paths at lk and lk2 and select my patched lk img

-click download and connect your phone

-after flashing disconnect the phone and long press the powerbutton while holding volume up and then boot into bootloader (fastboot) mode

-open a terminal in the folder of the firmware

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

-reboot to fastbootd: fastboot reboot fastboot

-fastboot flash vendor vendor.img

now you can reboot your phone back into the system

optional for Magisk users: repatch the boot.img which comes with this firmware
[Upgrading, Modifying and Unlocking] moonraver:
It is a bit strange that scatter file in stock firmware for King Kong Mini 2 Pro is aimed for MediaTek Helio P35 (MT6765) SoC instead of MediaTek Helio P22 (MT6762). Basically both SoCs look the the same and there are differences only in clock speeds. Hadware info shows P22 on board.
[Upgrading, Modifying and Unlocking] birdibird:
Maybe an idea to copy the scatter file of the kkm2 into the kkm2 pro folder and then try to flash the kkm2 pro firmware with that scatter file of the kkm2 on the kkm2.....
[Upgrading, Modifying and Unlocking] moonraver:
No need to............everything works fine as is. It is only a bit confusing that after loading scatter file and during flashing it shows different SoC in SP Flash Tool. After my small comparison it shows that both SoC are the same with different clock speed of memory and CPU.
[Upgrading, Modifying and Unlocking] birdibird:
Do you mean you now have the kkm2 pro firmware on your kkm2?
[Upgrading, Modifying and Unlocking] moonraver:
NO. I have KKM2 PRO now. And when you flash original Stock ROM from Cubot website according their instructions with SP FlashTool you have to load a scatter file and afterwards it shows a picture of your SoC in SP FlashTool that you are going to flash. With KKM2 it showed correct MT6761 = Helio A22, but with KKM2 Pro it shows MT6765 = MediaTek Helio P35 instead of MT6762 = MediaTek Helio P22.
[Upgrading, Modifying and Unlocking] veloc_h:
is it possible to flash a cubot kingkong mini2 firmware on kingkong mini 1st version (the hardware is - apart from the battery 3000mAh vs. 2000mAh- the same, isnt' it?
[Upgrading, Modifying and Unlocking] moonraver:
Somebody wrote here already that it was not working..........but give it a try :)
[Upgrading, Modifying and Unlocking] veloc_h:
@moonraver

@birdibird, who set up a manual for mini2 here

, wrote to me:

"

Just don't do this step:

-fastboot reboot fastboot

(there is no fastbootd mode on the kkm1)

the rest is the same."

a special advice (bricking risk, especially if there doesn't exist a stable twrp (on the twrp there isn't a version for Cubot mini 1), which I wouldn't give to others without knowing the details...

I don't mind calculated risks by the way, but only because of degoogling I won't take the risk without further information. on https://xdaforums.com/t/aosp-12-1-leos-ungoogled-gsi.4356501/post-86790923 one can read: "Not working: VoLTE, offline charging." by the way...
[Upgrading, Modifying and Unlocking] birdibird:
@veloc_h There is a working TWRP for the KKM1, search this thread.

But you do not need TWRP for flashing LeOS.

Just use the original firmware of the kkm1 and flash as I said.

Also, I am not clear what you mean above with risks.

btw offline charging and VoLTE is working.