yashsingh1/xdaforums huggingface dataset:
[Upgrading, Modifying and Unlocking] x53:
@msbln For KKM1 I'm not certain, because I own a KKM2 only. But KKM1 is

originaly shiped

with Android 9, where KKM2 is with Android 10. This note from TWRP states it very much. With KMM2 you can't mount /system in TWRP, not even read-only. You said with KKM1 you can mount /system read-only at least. So with that yo are better of with KKM1 ;).

Another question 1: whats with /data? Have you ever tried backup it using TWRP? Please have a look in /data/data using TWRP file manager. Do you see encryped files and directories?

Another question 2: Is there a way to remap or add softkeys to the nav bar? I would like to add some more functions e.g. long press Home shows an app menu of older apps. Or long press back button kills the app. Another way could be to add 2 more softkeys, but everything I tried (settings, third party apps, edit generic.kl), nothing worked.
[Upgrading, Modifying and Unlocking] birdibird:
I have KKM1 and KKM2. Indeed the latter uses dynamic partitions. You can flash a system.img by booting into fastbootd. My KKM1 has TWRP, the KKM2 not, but now TWRP 3.6.0 has been released I might have a try.

I am running LOS 18.1 on the KKM1 and crDRom v313+ on the KKM2.

Both have Magisk, both work flawless.

edit: What happened to the Telegram group?
[Upgrading, Modifying and Unlocking] x53:
TWRP-3.6.0_10 would be nice for KKM2, supports dynamic and encrypted partition. Is there a download available somewhere? At the other hand there are others means for backup und recovery images, e.g. adb pull userdata.img and fastboot flash userdata userdata.img. However backup data with TWRP 3.4 is possible when decrypted. Flash this vendor.img and format data partition in TWRP. This method works like Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip for KKM1.

Second question: How about Voice over Wifi running a custom rom? While VoLTE works like a charm with GSI ROMs when activated, VoWifi doesn't. Stock rom supports it. Is there a way to enable Wi-Fi Calling, too?
[Upgrading, Modifying and Unlocking] snoopy29:
The dynamic system where changes are held in ROM and lost on reboot is a real pain. If it were me I'd stick with V1 if you're going with a custom ROM as most ROM's contain SU (not magisk) which is impossible to hide from many apps like banking. It's why I created a custom Lineage 17 A/B-64 ROM just for v2 of this phone. This is still my daily driver and has been for ages, the only thing I haven't got round to is screen-brightness the same as every other ROM.

V2 has small motherboard changes to support the different battery vendor. Also the gasket around the phone is unfortunately a sticker not rubber so once opened you need a new one or loose the waterproofing.
[Upgrading, Modifying and Unlocking] x53:
To which rom do you rever? I know this behavior from stock rom. But not from lineage-18.1-20211108-UNOFFICIAL-treble_a64_bvS? Using LineageOS it's possible to remove su from xbin folder. So there should not be a problem in using banking apps? Or is there although? I did this this way:

adb root
adb shell
mount -o rw,remount /system
umount /system/xbin/su
rm /system/xbin/su
exit
adb reboot

What's with the screen brightness? Do you mean auto brightness? Never used that. I always adjust brightness manually using status bar.
[Upgrading, Modifying and Unlocking] snoopy29:
Yes this was the means I did it, but su returns after reboot because changes aren't retained.

PS, umount /system/xbin/su seems wrong it's a binary not a mounted path
[Upgrading, Modifying and Unlocking] x53:
I know. But without the umount command I couldn't remove su. I suppose it's because it was in use. I do not know. I didn't get an error. For me it did the work :)
[Upgrading, Modifying and Unlocking] snoopy29:
Hmm I've never heard of unmounting a file, it's not what the command does. I didn't try it so can't comment.

Other changes weren't retained either, such as moving su to another file name. The operation was sucessful, just not stored on reboot.
[Upgrading, Modifying and Unlocking] linusuli:
Where can TWRP-3.6.0_10 be found? thanks.
[Upgrading, Modifying and Unlocking] kkm6761:
Good to know KKM2 has different battery, as in really different.

For the complaints about support from Cubot: they are valid, but they apply to all phone (Chinese mostly) makers out there. If you want support get iPhone or Pixel. I now have an older Pixel with GrapheneOS, which will become my car nav system or rooted "hacking" phone, when I get the coming Pixel 6a. Chinese phones are products that you change every year, so for something disposable and cheap, a de-googled LineageOS Chinese phone that can be upgraded to the latest Android, it is a very good buy.

I am now holding on (have the KKM1), because this year comes the KKM3. I am really wondering what it will be like, if it gets 64 bits system, what processor etc. Hopefully it is just like a small KK7. The J10 has the same display size as KKM1/2, but it has much larger bezels which makes it a bigger phone than the J8/Note 7, which has a 5.5 inch display and is of almost the same size (4 mm taller, 1 mm narrower) than iPhone 12/13 mini.
[Upgrading, Modifying and Unlocking] birdibird:
I moved to LeOS, a nice de-googling project.

https://leos-gsi.de/

Running LeOS A11 on one kkm2 (LOS based) and LeOS A12 on another kkm2. The latter is surprisingly smooth!

edit:

I recommend to try A12. The bugs I experienced were due to that my proximity sensor is broken. On another kkm2 it works fine.
[Upgrading, Modifying and Unlocking] kkm6761:
you run leos arm64? i see no arm32 binder64.

i now yet have resurrection remix, but it drains the battery in 4 hours in airplane mode. so i can't use the phone. i'll then try what you have. there is a rooted version? will xposed work without magisk?
[Upgrading, Modifying and Unlocking] birdibird:
always A64 (binder) version of course.

These A64 versions work:

https://leos-gsi.de/downloads/LeOS-R-GSI/Nov/

edit:

with this script you can install various apps to make the 'full' version if you have the mini version:

https://leos-gsi.de/downloads/HowTo/install.7z

(you will need linux or WSL for bash)

Telegram support group:

LeOS — GSI - no gapps will work !!! ...... out of maintenance / support still alive

Deutsch/englische LeOS support Gruppe.	ACHTUNG: KEIN OffTopic erlaubt. Wer dagegen verstößt wird entlassen ————————————German/English LeOS support group.	ATTENTION: NO OffTopic allowed. Whoever violates this will be fired

t.me
[Upgrading, Modifying and Unlocking] kkm6761:
the gsi you linked does not work for me, with or without wiping data/cache after flash.

I installed the mini version, not RW but RO.

https://leos-gsi.de/downloads/LeOS-R-GSI/Nov/Nov-LeOS-R-a64-RO-mini-bvS.img.xz

it works. i have root checker, and phone is rooted.
[Upgrading, Modifying and Unlocking] birdibird:
The dec .img I linked had a bug, so that's why. The builder will rebuild a jan version upcoming week.

Our phone can do both RO (VNDK) or RW (VNDKlite) versions.
[Upgrading, Modifying and Unlocking] kkm6761:
what is the difference practically between RO and RW? Rw has no write protection in system files?
[Upgrading, Modifying and Unlocking] birdibird:
correct
[Upgrading, Modifying and Unlocking] badcodelab:
any insights when or if it happens?

last summer asked this to cubot factory store at ali but they heard nothing

not sure if they are related to the real factory tho

btw how do you guys update custom roms on kkm2 without twrp? is there a way to perform a non-destructive update (i mean to keep user data and apps)?
[Upgrading, Modifying and Unlocking] landsome:
On KKM1 i just do a regular adb update of the new system and the old one is kept intact - if it's the same ROM (I use LiR now, AOSP and LOS in the past). Will try AOSP 12 soon, though.
[Upgrading, Modifying and Unlocking] birdibird:
With fastboot, just flash the updated rom as system.

Keep in mind with the kkm2 you will need to reboot into fastbootd first from bootloader mode with fastboot reboot fastboot
[Upgrading, Modifying and Unlocking] kkm6761:
Now with LeOS, battery is fine. Something in ResurrectionRemix just kills battery life, even in airplane mode.

I don't know when. But it coming this year is a certainty. The KKM has quite a following, even though tiny. Unless the new iPhone SE3 is based on the 12/13 mini, there just is no phone the size of KKM, smaller than iphone SE1 (but thicker). Quite a few modders, so I hope they'll make it more root friendly too. We'll see. It is the only player, Palm phone and Rakuten mini are not that available. I also find that Palm botched its market research. KKM1 has good battery life for normal use (who intensively uses phone on small screen?). Palm/Rakuten mini not.
[Upgrading, Modifying and Unlocking] badcodelab:
thanks

do you mean just skip step with flashing vbmeta, boot and recovery from the manual?

do i need to run "flashing unlock" command before?
[Upgrading, Modifying and Unlocking] birdibird:
You only need to flash the new updated rom, nothing else
[Upgrading, Modifying and Unlocking] landsome:
Just flash system
[Upgrading, Modifying and Unlocking] birdibird:
I found a working TWRP for the kkm2.

unofficial twrp 3.4.0 Root Cubot Kingkong Mini 2 - unofficial twrp

Download unofficial twrp 3.4.0 root Cubot Kingkong Mini 2, user who own Cubot Kingkong Mini 2 can root it by following the below Instructions

unofficialtwrp.com

Flash with SPflashtool or fastboot.
[Upgrading, Modifying and Unlocking] Lava79:
Hi !

Tried the UNOFFICIAL TWRP 3.4.0 linked by birdibird. Did :

1. adb rboot boatloader

2. fastboot flashing unlock ( works like an erase user data )

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

fastboot flash boot boot.img

fastboot flash recovery TWRP.img

4. fastboot reboot recovery

( TWRP replaces the 2nd CUBOT's fastboot, could be considering as the official's recovery )

5. access TWRP recovery

( unable to flash LOS17 ROM because I didn't know which location to choose to flash )

SO, I DID AFTER :

1, 2, 3 ( with flashing offical recovery )

4. fastboot reboot fastboot

5. fastboot flash system LOS17.img

6. fastboot reboot boatloader

7. fastboot flash recovery TWRP.img

8. fastboot reboot recovery

9. acces TWRP recovery, unable to flash magisk, no verity opt, and gapps,

because system need to be launched otherwise u got no system folder and no possibility to install.

SO, DID :

1,2,3,4,5,

6. launched sytem

7. same as 6,7,8.

9. This time ( at least ! ), i was able to launch install of magisk, no verity and gapps ( for LOS17, arm(32)-9.0 not arm64 nor android 10 )

BUT, the installations are not working :

"invalid zip file format"

"error installing zip file /external_sd"

"failed to mount /system_root (invalid argument)"

Tried by "internal storage" too but got folders with letters and numbers reaching to nothing and impossible to find zip's files.

So guys, where did i miss something ?
[Upgrading, Modifying and Unlocking] rebeco:
I triyed with adb sideload in order to install Magisk zip file, but did not work because twrp cannot mount system partition.
[Upgrading, Modifying and Unlocking] birdibird:
which los17 image are you using? It needs to be a rw -> vndklite

long time ago that I actively used twrp (that was on my kkm1), but just from memory you will need to flash decrypt and factory reset/format data in twrp and flash the system.img with twrp or fastboot or spflashtool afterwards to be able to have twrp access the rom.

-> this is from memory, so please tell me if I am wrong.

I flashed this twrp on this device (kkm2) just to test it, and noticed that it could not access my rom as it is encrypted (the original recovery could). I think 3.6.0 should be able to solve that?
[Upgrading, Modifying and Unlocking] Lava79:
Hi !

I did format data in TWRP before flashing Magisk, but even like this I always got :

Failed to mount /system root

Failed to mount /data

It seems for me that we have to flash Magisk before installing TWRP, dont u think ?
[Upgrading, Modifying and Unlocking] rebeco:
Im using stock rom, dont know about a lOS for the kkm2 version.

I was triying this:

Rooting Cubot KingKong Mini 2 | Deadbadger

Jakub Kaderka personal webpage, electronic hacking, projects,etc.

deadbadger.cz

But cannot use this:

fastboot flash system YOUR_SYSTEM_IMAGE.img

(where put the correct image file name for lOS17)

The reason, it says the system partition does not exist.
[Upgrading, Modifying and Unlocking] birdibird:
did you fastboot reboot fastboot?

try this one: https://leos-gsi.de/downloads/LeOS-S/Jan/LeOS-S-VNDKLITE-a64-bvS.img.xz
[Upgrading, Modifying and Unlocking] rebeco:
Yes, I did. But the phone reboot with the message "orange state" and reboot again into fastboot.
[Upgrading, Modifying and Unlocking] Lava79:
@rebeco : the "orange state" is normal thing, u got it soon u unlock the bootloader.

But, the bootloop in the "fastboot recovery"... Normallly u got a "dead android"...

Where did u get the .img u r flashing ? From the stock rom on Cubot's site ?

If it's not, do it, try from scratch : Power+VolUp, go bootloader, and flash everything from beginning.
[Upgrading, Modifying and Unlocking] birdibird:
Orange state you can solve by flashing a patched lk.img with SPFlashtool. I shared mine already before, but I will attach it here again.
[Upgrading, Modifying and Unlocking] Lukas+:
Hi. I've installed a

LeOS-S-VNDKLITE-a64-bvS

from here

Index of /downloads/LeOS-S/Dec

and it works perfectly, also for intensive everyday use.

As for every today ROM installed in dynamic partitions, there are problems in real full usage of su binaries, but for now it's the best I found, from here, page 16.
[Upgrading, Modifying and Unlocking] Lukas+:
I used TWRP 3.4.0 with Android 10 stock of my kkm2, but it wasn't able to mount in write mode the system, and I know it's a common problem.

Are you able to make it work, yes?
[Upgrading, Modifying and Unlocking] birdibird:
I only tested twrp on my already installed LeOS S phone, but it couldn't read the contents because it's encrypted as I said above. If I have a test device again, I will be able to play around and test things.
[Upgrading, Modifying and Unlocking] Lava79:
Hi !

Tried LeOS-Q version, good rom.

But the only thing i need is a LOS ( or LOS like ) rom + OpenGapps ( or another gapps like ).

Tried in a multiple way with adb/fastboot and with or without TWRP to install gapps but no way...

Any idea how i could do it ?

Because i'm becoming goat ! French version of "going nuts" !
[Upgrading, Modifying and Unlocking] rebeco:
Do u replace the original lk.img with this one? And then flash the stock rom?
[Upgrading, Modifying and Unlocking] rebeco:
Are u talking about the KKM2 version? I will try with orange state avoid.
[Upgrading, Modifying and Unlocking] birdibird:
You can flash lk.img in SPFlashtool (only on lk, not on lk2). Don't need to flash anything else at that moment.
[Upgrading, Modifying and Unlocking] Lava79:
@birdibird : The lk-patched.img u provided works fine with KK2.

I thought i have to flash every time i have to flashing unlock,

but once i did it, the orange state message never appeared again.

Anyone ever had the : "Invalid sparse file format at header magic" message before flashing rom ?
[Upgrading, Modifying and Unlocking] birdibird:
Yes, ignore that.
[Upgrading, Modifying and Unlocking] Lukas+:
Yes, KKM2. My orange state is shown every boot (I will delete it in the future).
[Upgrading, Modifying and Unlocking] Lukas+:
I also tried installing TWRP with

LeOS vndklite a64 bvs

but with the same android 10 stock result.

Only it's author (of LeOS) says it's because from android 12 .xml files are compressed in a way old TWRP (3.4.0) can't process. So, at the end, it's a problem over another. It's not out a 3.5.0 TWRP for KKM2 (good for dynamic partitions) yet and there's a new Android 12 problem related. It's not easy staying without a TWRP working.
[Upgrading, Modifying and Unlocking] Lukas+:
Because that guide is not complete. It makes you do a lot of dirties flashing. It's better (supposed we're in fastboot with boatloader unlocked and flashing too):

fastboot -w

fastboot reboot fastboot

fastboot erase system

fastboot flash system system.img

fastboot reboot

Every data will be lost, you restart the system as new. I prefer also not having the external memory formatted as internal when I do this, but maybe it's not a problem. If this commands doesn't work I'll try with another Rom.
[Upgrading, Modifying and Unlocking] birdibird:
fastboot -w is only needed if you don't use factory reset/data wipe from recovery and not needed if you upgrade a rom to a new version and you want to keep your userdata.

But it will also wipe the internal media card! Otherwise just use fastboot erase data if you need to wipe data but not the entire internal media card.
[Upgrading, Modifying and Unlocking] birdibird:
You can flash my lk.img from above with fastboot flash lk lk.img or with spflashtool. (only once needed)
[Upgrading, Modifying and Unlocking] racht:
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 ..
[Upgrading, Modifying and Unlocking] x53:
When offline charging the KKM2 screen backlight is permanet on! Is this right? Means I shutdown the phone and put the charger on. After that I get a charging battery symbol for at least 2 minutes, I guess. After that a simple white symbol for the charging process is shown. Seconds later this simple charging animation disappers but the backlight is still on. The whole night the display shines! Thats annoying! When pressing the power button the simple charging animation appears and disappears but the backlight remains. So the only solution is to charge the phone powered on.

Btw, at first I didn't get the logo editor to work. With Windows 10 it won't even start and Windows 7 throwed an .net error. The solution was to toggle "Unblock" within the file properties (general tab) of Ionic.Zip.dll, logo.exe, LogoBuilder.exe and Tips.dll.
[Upgrading, Modifying and Unlocking] Lava79:
Hi everybody !

I did something wrong with my KKM2 :

- flash boot logo with a photo I would like instead of the Cubot logo,

- got pbs with rebooting

- flash boot.img then and recovery.img, thinking that it could resolved the pb.

BUT, now phone stuck on black screen with blue led appearing sometimes when on charge.

Impossible to get to recovery or fastboot even with power+Vol-/+

Hope I didn't f*** too much, please help.
[Upgrading, Modifying and Unlocking] kkm6761:
if you can't get into fastboot, you will probably have to use SPflash and reinstall stock firmware. will delete data.

another question for anyone that could answer: resurrection remix just drains me battery, I have found no way around. it also is the only rom that I have found working on KKM (corvus os does not boot without disabling or setting SELinux to permissive). how can I hide/delete lockscreen clock/date on lineage os with adb commands without root? i tried with magisk, but the xposed framework does not install correctly, and virtual xposed just just not work as it should.
[Upgrading, Modifying and Unlocking] birdibird:
use spflashtool to flash the original logo.

untick the rest. you don't have reinstall the whole stock firmware for only the logo
[Upgrading, Modifying and Unlocking] landsome:
Any experiences with AOSP 12 on KKM1?
[Upgrading, Modifying and Unlocking] x53:
The MTK EngineerMode in stock rom is very helpful (dial *#*#3646633#*#*). I know there is a similar but downgraded alternative within lineageos (dial *#*#4636#*#*). For that reason I tried to integrate it into lineageos, unfortunatly unsuccessful. I did copy the EngineerMode.apk into the folder /system/priv-app/EngineerMode and set permissions like the other system apps. But dialing *#*#3646633#*#* didn't work, not even after reboot. Maybe there is more to copy, not only this system apk. Any suggestions or is my project doomed to fail? :) In my opinion the best thing of stock EngineerMode is to set a certain cell id. Never saw that at other phones e.g. samsung. Or is a similar app to install out there?
[Upgrading, Modifying and Unlocking] birdibird:
Sorry, no experience on KKM1 but on KKM2 it is very smooth :cool: (LeOS)
[Upgrading, Modifying and Unlocking] x53:
Today I tried LineageOS 19.0 but I didn't get system rw access. adb root & adb disable-verity didn't work out like it does with LineageOS 18.1. There is simply no system partition to mount. So mount -o rw,remount /system doesn't work (error: /system not in /proc/mounts). df does show no overlay system partition either. Any suggestions for getting rw access to system partition running LineageOS 19.0?
[Upgrading, Modifying and Unlocking] landsome:
Thanks. Same old issues of kkm2 apply? (BT echo in calls etc.)
[Upgrading, Modifying and Unlocking] kowalskie:
Hi. Actually iḿ using the KKM2 with the latest A10 Stock. Wich version of LeOS have u installed? Does calling work with VoLTE and without annoyning echos while speaking? Is the Wifi connecting now stable? Regards

kowalskie
[Upgrading, Modifying and Unlocking] birdibird:
Works all good.

btw BT echo has been gone for a long time already also in A11.
[Upgrading, Modifying and Unlocking] birdibird:
no problems with wifi and echos. VoLTE I didn't test
[Upgrading, Modifying and Unlocking] kowalskie:
Thanks for your quick answer. Could you test volte related test-call for me? Stays the LTE/4G or VoLTE Symbol on top of the screen while having a call?
[Upgrading, Modifying and Unlocking] birdibird:
Sorry, my operator doesn't support it
[Upgrading, Modifying and Unlocking] Md652:
I want to replace the cubot logo and also the home screen image (in system.img) as well as delete the search box on the home screen, can anyone help?
[Upgrading, Modifying and Unlocking] kkm6761:
I am on Lineage OS 19 on KKM1. Looks to work normally.

I don't have any solution, but I too wanted to work on that. Don't know when, so hope someone else can help. To replace home screen image in system would need root.

I don't like the way root works in KKM.
[Upgrading, Modifying and Unlocking] Md652:
I am of course rooted but I want more than that also to edit the system.img file or another partition to burn rom with a different logo and a different screenshot
[Upgrading, Modifying and Unlocking] landsome:
Does

Does LeOS have the typical A12 large pill shaped quick tiles / toggles?

EDIT: I installled LeOS R (A11) and it works fine so far.
[Upgrading, Modifying and Unlocking] birdibird:
Yes, as all A12 :)
[Upgrading, Modifying and Unlocking] landsome:
Not Samsung. They kept the old toggles in UI4. :)
[Upgrading, Modifying and Unlocking] birdibird:
Sorry: as all pure A12 ;)
[Upgrading, Modifying and Unlocking] landsome:
So no pure variant of AOSP-based A12 with old-style toggles? Too bad...
[Upgrading, Modifying and Unlocking] covexx:
Does anybody has a TWRP for KKM2 with decrypt support? I found https://unofficialtwrp.com/twrp-3-4-0-root-cubot-kingkong-mini-2/ and it says "twrp decrypt" not supported. KKM2 has a File Based Encryption (FBE). I have a rooted device, I have owner PIN, can boot and access the device with adb, but forgot the secondary user pattern. It seems there is no other way than bruteforcing the pattern and I only found a scripting thru TWRP - https://github.com/timvisee/apbf - but it has to support decrypt.
[Upgrading, Modifying and Unlocking] landsome:
Hi! Did you eventually try /e/ with KKM? Did it work?