yashsingh1/xdaforums huggingface dataset:
[Upgrading, Modifying and Unlocking] moonraver:
focusing is still the same even in bad light conditions. But in Evolution ROM when I saw what Lineage OS and Lineage camera 13 can do - absolutely no lagging in any light conditions, focusing was the same in low light.................I think we are not getting the best from camera chip in Cubot's STOCK Rom. Somehow CUBOT takes sh.t about cameras since KKM to KKM3

I admit that I don' t understand this part. Maybe you should give me some instructions to add them into the flashing procedure

with LEOS I didn't have any problems with lockscreen. I didn't try headphones. In first steps I was only wondering why internet connection wasn't working - WIFI was connected with asterisk without internet access. I wasn't able to download any apps. There were no internet problems with Evolution ROM.

Now I am back on MOD4 Stock ROM.

Personally I think: Evolution ROM seemed to be a "clean flash" but LEOS was "dirty flash". If we manage this everything can work.
[Upgrading, Modifying and Unlocking] badcodelab:
sorry, it was a rhetorical question about misunderstanding why anyone else can't flash evolution rom (or any other gsi) cleanly over stock or mod4 rom
[Upgrading, Modifying and Unlocking] moonraver:
I think you can use Evolition X Rom without any problems (maybe with a little ones, needs to be more tested in details). ROM seemed clear to me. But it was full of google stuff that I don' t like.

Another thing makes me still angry since Android 11 was released. Maybe you could help me. Since A11 there is NO possibility to call 3rd party camera app from 3rd party app. U can pick which camera app to use from lockscreen but not from 3rd party app. For example: I am an OSM mapper and I use Osmand for mapping. When I want to make a photo in Osmand, I have to use only "system camera" or built-in Osmand camera. Both of them are bad. In A10 I used HedgeCam2 to capture from Osmand, but it is now impossible since improved security from A11 and versions above.

So:

- is there any Magisk or any different module to set different camera as "system" . I haven't found anything yet.

- is there any script or something to rewrite in system files to set different camera as "system"?

I know that developers of LeOS, Lineage OS can set the path to different camera to be "system" but it is a bit complicated for a common user like me.

Another question:

As I remember, there was a question on 4PDA how to increase "speaker volume during calls" via Engineer mode but there were no procedure steps. Don't you know how? I use ONLY speaker during calls and want to increase voice a bit. Music is loud enough but that call volume................

Thanx
[Upgrading, Modifying and Unlocking] moonraver:
Hey folks,

I've just updated flashing process for KKM3. It has been simplified and has possibility to flash updated EvolutionX ROM image from May. Everything has been tested by me.

Feel free to comment.
[Upgrading, Modifying and Unlocking] gfsLuc:
Hello

I want to use a custom ROM on my KKM2 Pro. Are there any instructions on how to get it working with custom roms?

I want to use it for bike navigation only (gps komoot etc).

Any recommendations for a good battery friendly ROM?

Thanks in advance
[Upgrading, Modifying and Unlocking] badcodelab:
the manual is here

sorry mate, can't help here, i believe your best option is to ask LeOS guys https://t.me/LeOS_Support

here is from that 4pda post:

i didn't try this, volume level is fine to me, search something volume/speaker related
[Upgrading, Modifying and Unlocking] Loopback7084:
After stripping down the MOD3 image, I've come to add a few apks back to an image... a process many many years ago I used to refer to as 'slipstreaming'... and back when I last did it.. ( Android 7 )... it was very straightforward. However, this image is android 12, and although I'm perfectly able to unpack & repack the image, and successfully boot and use it, no apps I add to the system.img will actually run. The process is thus:-

1) unpack super

2) resize2fs system img ( add space )

3) mount it

4) add the apks to ./system/app/[appname]/[app].apk

5) chmod the folder to 755 and the apk to 644 ( not entirely sure why this was found on searches )

6) unmount

7) resize2fs -M system

8) repack with lpmake

9) reflash the NAND, optionally wipe data ( depending on how much I've butchered the ROM ).

Everything "else" works... apart from the APKs I've added... ( they 'appear' as apps but not correctly - icons are "off" and the won't execute... ( see attached )... really grateful of any help... what am I doing wrong...?
[Upgrading, Modifying and Unlocking] ylavi:
EDIT: Never mind, I ordered a KKM3 and you'd surely tell me that I should try the ROMs myself.

Hi all

As I mentioned quite some time ago I have a KKM (1) which works except for the USB port (it charges but no data). This is now an issue for me as I need the USB connection now. In any case, an upgrade would be a treat :)

I'm thinking of getting the KKM3 but wonder if staying with the same size and shape (i.e. KKM2Pro) might be preferable for some reason. I would much appreciate if someone with a clear picture of the options would please summarise for me what is known. Obviously some things are subjective.

Which of these devices have a stable custom ROM option? (i.e. as of now because if switching ROM I would want to do it straight away and then stay with it)

If no custom ROM is stable yet (or they are stable enough but features which are important for me don't work) I'd continue to use the stock ROM (I'm still on KKM stock). But are there any significant issues with the stock ROMs? (besides the obvious "they're Chinese and not open")

The screen dimensions and pixel density of the KKM3 are different - enough to disturb and prefer the 2Pro? or does one get used to it?

Thanks!
[Upgrading, Modifying and Unlocking] Uusername:
Post removed - Stupid Question
[Upgrading, Modifying and Unlocking] M0g13r:
cubot King Kong mini 2 pro

---------------------------------------------

files from CUBOT_KINGKONG MINI2 Pro_C021C_V03_20220914

patched lk .... removed orange and red state ... and boot wait of 5 sec. but looks like its not working on this device

patched logo .... removed ugly cubot logo :)

flash with:

-----------------

adb reboot bootloader

fastboot flash lk lk_patched_v3.img

fastboot flash logo logo.bin

fastboot reboot

View attachment 5951215
[Upgrading, Modifying and Unlocking] R.C..K:
Good day. I will ask for an opinion. I wanted to replace an old 4" KKM2. I bought a KKM2 Pro, which I returned because of a poor quality camera. In the HedgeCam2 and OpenCamera applications, after turning off NoiseReduction and EdgeEnhancement, all photos were red, sunsets could not be photographed. Red dots and spots were on every photo even on a sunny day. So I decided to buy a Pocket, which I also returned because the Camera2API doesn't work there at all. I tried all the firmwares released by Cubot on both the KKM2Pro and Pocket phones. In the old KKM2, everything is fine with the first firmware works NR and EE on Off. I'm afraid to buy KKM3 or Pocket3 so I don't return it too.
[Upgrading, Modifying and Unlocking] badcodelab:
if you're looking for a good camera you should avoid this manufacturer, sad but true

kkm3 has nearly same poor quality camera (i believe mostly because of lazy developers who give us only basic functionality)

try another brands like mode1 grip or balmuda phone if it suits you with supported japanese lte bands

perhaps blackview n6000 (release on 24th of july with $150-$160 price) will be a good deal but very thick (18mm)
[Upgrading, Modifying and Unlocking] R.C..K:
badcodelab. Thanks for the Blackwiev N6000 tip, I'll keep an eye out. But they sell KKM3 here, I would like to know if it also takes pictures in red and it is possible to use the OC and HC2 application with the filters turned off. It didn't work on Pocket, that was the reason for the return. A good phone is ruined by a poor-quality photo sensor.

For a preview of KKM2 Pro photos:
[Upgrading, Modifying and Unlocking] FasterPhoneMaster:
I flashed Evolution X rom to KKM3. Thanks for the instructions! After the first flash I updated to evolution_arm64-ab-vndklite-7.9.4-unofficial-20230702 version. I have not fully tested it yet but at least it booted nicely and basic functions seems to be working. Interestingly security patch level is reported as "5th december 2022" even so that the build is from July 2023. I don't if the security level was downgraded from the February 2023 version or is it just reported incorrectly.

Also, first I tried to flash evolution_arm64-ab-pico-7.9.4-unofficial-20230702 but the flashing ended to an error. I don't know what might be the reason for that.
[Upgrading, Modifying and Unlocking] badcodelab:
you have to resize product partition before flashing system

fastboot resize-logical-partition product 38000 or use product_gsi.img from this post

but anyway you likely face a bootloop if you flash gsi over stock rom
[Upgrading, Modifying and Unlocking] aidaho:
I'm trying to flash LineageOS 17.1 on fresh out-of-the-box KKM2 Pro, but no matter what I do, I'm getting "No command" screen.

Here are the steps I've took:

1. Downloaded CUBOT_KINGKONG MINI2 Pro_C021C_V03_20220914 firmware

2. Flashed it with SPFlashTool.

3. Allowed device unlock.

4. adb reboot bootloader

5. fastboot flashing unlock, made sure it succeeded

Using files from the stock firmware:

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

7. fastboot flash boot boot.img

8. fastboot flash recovery recovery.img

9. fastboot reboot fastboot

10. fastboot flash product product_gsi.img

11. fastboot flash system lineage-17.1-20210808-UNOFFICIAL-treble_arm64_bvS.img using image from https://sourceforge.net/projects/andyyan-gsi/files/lineage-17.x/

I've tried from scratch skipping steps 7,8,10, as suggested by someone in thread but I've got the same result: "No command" screen.

Please help.
[Upgrading, Modifying and Unlocking] badcodelab:
mate you can't downgrade android version, try anything based on a11 or higher

e.g. los18 should work https://sourceforge.net/projects/andyyan-gsi/files/lineage-18.x/
[Upgrading, Modifying and Unlocking] aidaho:
Oh, I did not know that. Thank you!
[Upgrading, Modifying and Unlocking] Holle88:
So first things first, i managed to flash KKM3 with that EvoX ROM, works and feels smooth for me BUT: I can`t set a PIN (or password) in the settings. it feels, like is unwrittable (no permission to wrote).

SETTINGS App freezes and wants to send a report when crashes. Sometimes it`s not crashing, but you type in a Pin and confirm second time and nothing ever happens.

so i decided to try another EvoX (newest Version).

Can you explain how you do an fastboot flash system, when the actual system.img is inside of "super".img???

because you get an error, that tells you: partition not found, which totally makes sens because it`s inside of the super partition.

so how can i replace the system.img inside of the super partition to download it with the flash tool again?

Or may i can live with that first EvoX ROM, but then i want to know how i can solve the password/PIN issue...

thanks a lot.

how did you updated it? flash system system.img doesn`t work, because image.img is inside of super....
[Upgrading, Modifying and Unlocking] FasterPhoneMaster:
I was on stock ROM and flashed the super image first by following instructions written by @moonraver .

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

Then I just upgraded to newer EvoX build as guided in phase 5. evolution_arm64-ab-pico-7.9.4-unofficial-20230702 build did not boot but evolution_arm64-ab-vndklite-7.9.4-unofficial-20230702 was successful. I did not do any partition resizing like @badcodelab suggested.

The first booting after flashing evolution_arm64-ab-vndklite-7.9.4-unofficial-20230702 was very long. First I thought that the phone was stuck and I even pressed volume buttons like maniac because I was frustrated but it did boot after all :) .
[Upgrading, Modifying and Unlocking] Holle88:
at my end it says system partition doesn`t exist, so i can not flash system.img ... the must be some kind of missing link....

i did exactly the same....
[Upgrading, Modifying and Unlocking] FasterPhoneMaster:
I had issues with command "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img" since I used older SDK platform tools version (the command is different in the old version). I updated my SDK tools after the unsuccessful flashing attempt of "evolution_arm64-ab-pico-7.9.4-unofficial-20230702" and flashed vbmeta.img once again. Then I was able to boot evolution_arm64-ab-vndklite-7.9.4-unofficial-20230702 in the first try but I don't know if vbmeta.img and updating SDK tools had anything to with it.
[Upgrading, Modifying and Unlocking] schokokex:
about kkm3:

got the mod4 installed (because of battery usage working) and trying to debloat (product / system).

anyone doing the same? what gapps are safe to delete if i keep gms core?

magisk (internal) update 26.3 crashes mod4, anyone else same?
[Upgrading, Modifying and Unlocking] mxjohn944:
I got a new KKM3, and was studying this thread to see how I can flash a custom image. I Intend to flash LineageOS 20 on it.

What I understand thus far:

1. "orange state" problem is still unfixed.

2. This is not an a/b system.

3. It is fully 64-bit, not 32-bit with a 64-bit binder.

Some instructions resize partitions. Is this really necessary?

And, these instructions are for EvolutionX : https://xdaforums.com/t/installing-custom-rom-on-cubot-kingkong-mini.4050815/page-34#post-88637555 - can they also be used for LineageOS 20 instead?
[Upgrading, Modifying and Unlocking] badcodelab:
it's been fixed in mod3/4

you need to use a/b builds

true

you can try a standard procedure for kkm2pro from this post but it didn't work for most everyone here with kkm3

you have to flash los over evox dump by the link from the instruction
[Upgrading, Modifying and Unlocking] mxjohn944:
Okay, but the b Partition is de facto nonexistent (= set to zero capacity)?

And why do I need to flash EvoX first? LineageOS and EvoX are GSIs. What does EvoX do that LineageOS doesn't?
[Upgrading, Modifying and Unlocking] badcodelab:
the answer is above

not evox but this particular dump with evox

unfortunately i don't know what and how the author of the modded rom and this evox dump managed to flash evox in the first place
[Upgrading, Modifying and Unlocking] mxjohn944:
Success! LineageOS 20 is on the King Kong Mini 3 now.

I did a combination of the steps from the "HOW TO FLASH MODDED STOCK ROM TO KKM3 PHONE" instructions, KKM2 Pro instructions, and "HOW TO FLASH "EvolutionX" ROM TO KKM3 PHONE" instructions. Note that I did not use the SP Flash Tool - I only used fastboot.

1. In the existing Cubot vendor Android installation, enable developer options.

2. In the now-accessible developer options, enable OEM unlocking and USB debugging.

3. Connect the phone to the PC. When the dialog box pops up that asks you if you trust the PC for debugging, select "always trust connection" and press OK. Run adb devices to confirm that the device is properly accessible.

4. Run: adb reboot bootloader. This places the device in fastboot mode.

5. Run: fastboot flashing unlock. Confirm unlocking by pressing volume up.

6. Now go into the directory containing the mod3 or mod4 files. (I used mod4.) Run these commands:

fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
fastboot --disable-verity --disable-verification flash vbmeta_vendor vbmeta_vendor.img
fastboot flash boot boot.img
fastboot flash lk lk.img
fastboot flash lk2 lk2.img
fastboot flash logo logo.bin

7. Now, the "super" image must be flashed. I used the one from EvolutionX, but I think the ones from the mod3/mod4 packages should work too. When using EvolutionX, unpack the RAR archive, which only contains a single file called Super. That's the EvolutionX super image. Then, run: fastboot flash super Super (If using the mod3/mod4 super images, replace "Super" with whatever the super images are called there.) If you see the "Invalid sparse file format at header magic" line from fastboot, ignore it.

8. Go into the FastbootD mode by running: fastboot reboot fastboot

9. Once there, flash LineageOS. The KKM3 is a native ARM 64-bit machine, and uses the A/B partition scheme. I got a LineageOS 20 GSI from Andy Yan's personal builds. I chose to go vanilla, that is, without any GAPPS, and with built-in superuser. Following the legend fro the website I linked to, I downloaded lineage-20.0-20230815-UNOFFICIAL-arm64_bvS.img , and flashed it with: fastboot flash system lineage-20.0-20230815-UNOFFICIAL-arm64_bvS.img

10. In the fastboot UI, I selected "Enter recovery". There, I wiped the cache, and wiped data/did a factory reset.

11. Finally, through the fastboot UI, I rebooted the system (I did not select "reboot to bootloader").

And now I got LineageOS 20 on the KKM3. Did not test it much yet. But I hope these instruction help others.
[Upgrading, Modifying and Unlocking] badcodelab:
mod3/4's super consist of product, system and vendor partitions

super from evox dump has only system and vendor partitions

so i don't think it will work same way but thank you for the alternative manual

have you tried to skip the step with flashing evox?

how about display brightness comparing to stock?

other guys noticed lower max brightness on gsi roms
[Upgrading, Modifying and Unlocking] mxjohn944:
I just tried to flash the super.img from MOD4. Its system partition is too small for LineageOS 20, and IIRC, placing LineageOS on the product partition won't work (a stock Android must be present in the system partition).

As for the brightness, it seems the same to me, but I did not pay much attention to this before flashing.
[Upgrading, Modifying and Unlocking] badcodelab:
thanks for testing @mxjohn944!

do you see any significant issues on los?

does lockscreen work normally? can you set pin code or graphic key and unlock the device?
[Upgrading, Modifying and Unlocking] cnfuzd:
Success here too -- with Leos20-GSI install on KKM3 -- seems I reported to wrong forum? See my report from Wed 11Oct

Cubot KingKong Mini 3

Hi All, Noob here... This is a my "Thanks" to the forum and especially LeOS dev(s)! And to help people looking for a nice *SMALL* smartphone. After 2 weeks(!) of study online I took the plunge to buy a new KKM3 (Cubot KingKong Mini 3) , (Stock...

xdaforums.com
[Upgrading, Modifying and Unlocking] mxjohn944:
Did you see the lockscreen problems with LeOS as well?
[Upgrading, Modifying and Unlocking] cnfuzd:
No problems. I set randomized a PIN lock. Works fine.

As you know KKM3 has no fingerprint sensor. so my inability to get Face Unlock working is quite inconvenient/annoying. I read somewhere that (google?) removed face Unlock because not very secure - but I dont care about that - convenience more important for me,

I try to enrol face - but enerolment never progresses past "Cente you face if the circle" which I do, but no progress beyond that, just this message displayed below the whilrling circle: "Steps: 3 Remaining:3"
[Upgrading, Modifying and Unlocking] cnfuzd:
Oh, and suddenly today i found I cannot access youtube.com : "connection denied" . Same with google.com. stiil investigating - maybe a retsriction embedded in Leos20-GSI ?
[Upgrading, Modifying and Unlocking] Wacek1962:
Hello. I installed Cubot kkm 2 pro system lineage-20.0-20231017-UNOFFICIAL-arm64_bvN-vndklite.img.xz on my smartphone and I cannot connect to the Internet. Maybe someone solved this problem? thanks greetings
[Upgrading, Modifying and Unlocking] Wacek1962:
Hello. Very complicated for me, so I went back to Lineage 19. Thank you for your help
[Upgrading, Modifying and Unlocking] dank2019:
I am stuck in step 9 (I used mod4). When deploying lineage-20.0-20231017-UNOFFICIAL-arm64_bvS.img I get the following error:

$ fastboot flash system lineage-20.0-20231017-UNOFFICIAL-arm64_bvS.img
Invalid sparse file format at header magic
Resizing 'system' FAILED (remote: 'Not enough space to resize partition')
fastboot: error: Command failed

Any idea, what's wrong?
[Upgrading, Modifying and Unlocking] mxjohn944:
Use the Super file from the EvolutionX link I posted. You can download it there as a RAR archive, called "Evolute.rar".
[Upgrading, Modifying and Unlocking] dank2019:
This solved the issue. Thank you! One more with KKM3 und LineageOS running ;-)
[Upgrading, Modifying and Unlocking] dank2019:
Any idea, why I've no internet connection with the lineage (lineage-20.0-20231017-UNOFFICIAL-arm64_bvS.img). Browser and F-Droid can't connect via Wifi. A ping via adb shell is working. Something blocked?
[Upgrading, Modifying and Unlocking] dank2019:
It feels like I'm to stupid. I tried lineage 20 and LeOS. Both are working in general. I'm able to connect to Wifi. I can see it on adb shell:

34: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 3000
link/ether cd:73:14:13:17:ee brd ff:ff:ff:ff:ff:ff
inet 192.168.178.64/24 brd 192.168.178.255 scope global wlan0
valid_lft forever preferred_lft forever
inet6 2003:fa:a73e:3600:8dcc:ea4:c00c:bc1a/64 scope global temporary dynamic
valid_lft 7105sec preferred_lft 1619sec
inet6 2003:fa:a73e:3600:8f1f:69b6:2b8a:dcb/64 scope global dynamic mngtmpaddr stable-privacy
valid_lft 7105sec preferred_lft 1619sec
inet6 fe80::cde1:a5a4:2550:78e2/64 scope link stable-privacy
valid_lft forever preferred_lft forever
35: wlan1: <BROADCAST,MULTICAST> mtu 1500 qdis

I'm able to ping google from cmdl:

tdgsi_arm64_ab:/ $ ping www.google.com
PING www.google.com (142.250.185.228) 56(84) bytes of data.
64 bytes from fra16s53-in-f4.1e100.net (142.250.185.228): icmp_seq=1 ttl=60 time=113 ms

But I cant connect from any application. For sure: The problem am I. But what do I wrong?

Something blocked in general in the images due to the "su"? Someone with a hint?
[Upgrading, Modifying and Unlocking] teasheep:
If anyone is interested: I still use the Cubot KingKong mini (first version) and just upgraded successfully to AOSP 12 with GoGapps. Everything works. But I had to disable animations to make it feel a bit faster. Battery life is ok.
[Upgrading, Modifying and Unlocking] dank2019:
Another learning I had: Network is working on EvolutionX.

What do they different from LineageOS?

... I would like to have an OS without all the Google tools.
[Upgrading, Modifying and Unlocking] dank2019:
So, I found some images where network is working with KKM3:

- EvolutionX (contains all the google staff)

- ArrowOS-13.1-arm64_bvN-Unofficial.img (without google)

Does boot, boot the network issue described above:

- LeOS-20-VNDKLITE-arm64_bvS.img

- lineage-20.0-20230815-UNOFFICIAL-arm64_bvS.img

- lineage-20.0-20231017-UNOFFICIAL-arm64_bvS.img

- SparkOS-13.8-arm64_bvN-Unofficial.img

Not working for me (by several reasons, e.g. bootprocess does not finish, bootloops etc.):

- derpfest_arm64-ab-mini-unofficial-20231119.img

- evolution_arm64-ab-vndklite-7.9.7-unofficial-20230823.img

- evolution_arm64_bgN_slim-8.0.2-unofficial-20231112.img

- PixelOS_Beta_treble_arm64_bN-slim-14.0-20231117.img

- ProjectElixir_3.13_arm64_bgN-13.0-20231105-0917-OFFICIAL.img

- system-td-arm64-ab-vanilla-13.img

Problem with the "working" images above is, that screen lock does not work.
[Upgrading, Modifying and Unlocking] blooldxda:
The link to "Evolution.rar" is down. Could you reupload please? thanks a lot.
[Upgrading, Modifying and Unlocking] Old_Mil:
Not sure what you are asking? I have been using a Blackview n6000 for about a week and am pretty happy with it.
[Upgrading, Modifying and Unlocking] mxjohn944:
Sure, I just need a recommendation for a file hosting service that is suitable. Is Mega okay? I hesitate to use my personal Google Drive.
[Upgrading, Modifying and Unlocking] blooldxda:
Mega should be fine. Thank you so much for uploading it again :)
[Upgrading, Modifying and Unlocking] R.C..K:
Yes, pictures, photo and videos in RED. LCD brightnes RED
[Upgrading, Modifying and Unlocking] mxjohn944:
Here you go.