yashsingh1/xdaforums huggingface dataset:
[Upgrading, Modifying and Unlocking] snoopy29:
How did you kill them? I've killed one KKM2, immediate bootloop and ignores all buttons.

I'm compiling lineage 17.1 without su, primarily for the KKM2 which can't edit /system, see the GSI thread for a binary. It's my daily driver and working great.
[Upgrading, Modifying and Unlocking] landsome:
Don't you get incredible battery drain on the KKM1 during phone calls? This is what simply kills the phone for me. I could get used to all the other minuses, but to lose 25-30% over one hour on the phone is terrible.
[Upgrading, Modifying and Unlocking] snoopy29:
It's only a 2000maH battery, I wouldn't expect much more from any other device, and it depends heavily on how far away you are from a mast.
[Upgrading, Modifying and Unlocking] landsome:
Thanks. I have a Sony XZ1c with about 1900mah battery left after years of use and an XZ2c with around 2000mah (to the extent that months of AccuBattery use can give an accurate estimate). One hour on the phone eats up about a third as much. I realize these were old flagships etc., but I find the difference huge. After 3-4 longer (but not very long) calls I basically have to recharge the KKM1.
[Upgrading, Modifying and Unlocking] fasser:
Both of them stopped booting overnight on their own. First was a KKM1 which I had for about a year and never flashed out of stock ROMs. After trying to factory reset it and reflashing with SP flash tools it even stopped responding to USB. It still shows the boot screens and sometimes can access recovery, but it looks like the partition table is damaged.

After that one failed I got a KKM2, tested it for a while on stock and after a few weeks started flashing AOSP. One night it just froze and, after a force reset, it doesn't even show the boot or battery status screens. It still connects via USB but looks like the preloader got damaged, so it won't continue to boot/recovery/fastboot or even enter META mode when signaled by SP flash.
[Upgrading, Modifying and Unlocking] fasser:
As @snoopy29 said, you have to remember that this phone's battery is quite small. In my case it's not a problem as my phone usage is very little, but I do find annoying how hot the terminal gets after a 10-15 minute conversation.
[Upgrading, Modifying and Unlocking] landsome:
That too. But I could live with a hot terminal consuming less battery. :)
[Upgrading, Modifying and Unlocking] landsome:
By the way, has anyone found a ROM with microG built in that works well (as a ROM, not only as microG)?

I don't mean a ROM where I can install microG (I have done that, with various degrees of success, on a couple of different ROMs), but one where it's built into the ROM itself - and is updated relatively frequently.
[Upgrading, Modifying and Unlocking] W0153R:
The lk.img attached to TWRP earlier in the thread didn't work for me with the A061C_V07_20201113 ROM for the KingKong Mini 2. I modified the lk.img in that ROM, at first to get rid of Orange State notification but got it to pass SafetyNet as well after also selecting the SafetyNet feature in Phh settings (on CAOS 11 308 but it should be universal).

Edit: Also, something I didn't see mentioned anywhere is that you have to allow unlocking in developer options before you can unlock the bootloader. I struggled with a "unlock failed" error for way too long..
[Upgrading, Modifying and Unlocking] snoopy29:
I've just had a 22 min conversation, phone up to ear. KKM2. Lineage 17.1 (my rom).

Battery loss - 3%. Screen a little warm but probably a lot from my ear. Back top section (motherboard) luke warm.

I haven't a problem with this performance.
[Upgrading, Modifying and Unlocking] snoopy29:
I'll test this myself in a moment. Curious, how did you modify it?
[Upgrading, Modifying and Unlocking] landsome:
Thanks. I have heard it's not a problem with the kkm2, just kkm1 it seems (it was in fact reported on this thread in its early days).
[Upgrading, Modifying and Unlocking] W0153R:
I looked up the Orange State message part, zeroed that (and the Red State message) out and underneath that is a flag (forgot what it's called) that gets set to the different states, I changed that to always report green.

Also, this seems to fix the bluetooth microphone echo for me. I made a crude little Magisk module to do it for me, I'll see if I can get a proper regex together..

Edit: the flag is called androidboot.verifiedbootstate and it's probably possible to modify it without lk.img..

Edit2: with regards to the bluetooth echo, the following regex's work for me:

sed -i ':a;N;$!ba;s%<route type="mix" sink="voice tx"\n[ ]*sources="Voice Call In"/>\n[ ]*%%g'

sed -i ':a;N;$!ba;s%<mixPort name="voice tx" role="sink" maxOpenCount="1" maxActiveCount="1">\n[ ]*<profile name="" format="AUDIO_FORMAT_PCM_16_BIT"\n[ ]*samplingRates="8000,16000,32000,44100,48000"\n[ ]*channelMasks="AUDIO_CHANNEL_IN_MONO,AUDIO_CHANNEL_IN_STEREO,AUDIO_CHANNEL_IN_VOICE_UPLINK,AUDIO_CHANNEL_IN_VOICE_DNLINK"/>\n[ ]*</mixPort>\n[ ]*%%g'

If someone smarter than me can make a Magisk module out of this.. I´ve got no clue where to start, I think post-fs-data.sh but I don't have time for it right now.
[Upgrading, Modifying and Unlocking] snoopy29:
If it's generic send to PHH for inclusion in his work and it'll make it into all the treble roms.
[Upgrading, Modifying and Unlocking] Vuche:
A quick review and summary of my installation of GSI AOSP treble on my King Kong Mini 1:

As I had already tried to install the original Cubot Android 10 firmware of the KKM2 on my KKM1, I had already unlocked the bootoader to backup my original KKM1 firmware with TWRP, mainly to have a backup of the nvram that had to be wiped after because of a different partitioning for Android 10. Basically I did good because the only way to restore IMEIs and full nvram was by restoring my full backup of the original Andoid 9 install.

I followed the steps I could find on this thread between page 1 and 9 after downloading PHH AOSP 10 and 11 trebel roms.

Only trouble I went through was that I directly installed AOSP 11 with gapps, but it kept telling me my phone wasn't certified and gapps was crashing every 2 seconds or so.

So I flash AOSP 10 to see if I had the same problem and everything went smoothly, with gapps working, so I set my account to install some basic apps. I then upgraded to the lasted AOSP 11 with gapps through fastboot, keeping everything without wipe. And it worked!

So now I have a working KKM1 with Android 11 and June security update! I didn't try calling or using GPS yet, but for the rest, everything looks neat and works fluently. And I guess I can trust AOSP that there's no malware or backdoor installed by default in it, so even better than if Cubot itself would provide us with a working Android 10 or 11.

Thanks for everyone who's helping in this forum, I still have to hit some thumbs up buttons now that I could install the latest ROM.
[Upgrading, Modifying and Unlocking] snoopy29:
How did you flash this, I've tried both

/fastboot flash lk /home/andrew/Downloads/lk-mod2.img

/fastboot flash lk2 /home/andrew/Downloads/lk-mod2.img

And receiving partition doesn't exist (in proper fastboot mode)
[Upgrading, Modifying and Unlocking] W0153R:
You have to use root on linux to flash it, I don't know about windows or mac. I think I only flashed lk, maybe I did both, but you have to be in one of the fastboot modes, I can't remember which. If it doesn't work in the first one, do fastboot reboot fastboot so you get the other fastboot (the screen on your phone will be different) and try again..
[Upgrading, Modifying and Unlocking] snoopy29:
Yeah did all that, no avail.

Also need to investigate how to create an overlay. As people probably know the screen brightness won't work until we create one and get it submitted.

PS) I'm maintaining a Lineage 17.1 ROM for this phone.

https://xdaforums.com/t/gsi-10-lineageos-17-x-gsi-all-archs.4004673/post-85439325
[Upgrading, Modifying and Unlocking] Lava79:
Hi everybody !

New owner of a KKM2 I would like to install LOS Rom, but last time I did was 2016 on a Redmi 3S.

I've read Highbiker's post message #163 but my english and smartphone's knowledge seem to be a little rusty.

Could someone tell me or point me a link to do so ?

Thanks.
[Upgrading, Modifying and Unlocking] CHAYIM:
הצלחתי לשורש את ה- KING KONG MINI2.

אני מצליח להזין את קבצי המערכת,

אבל בלי לשנות או למחוק.

האם יש לאחד פתרון?
[Upgrading, Modifying and Unlocking] Lava79:
Hi !

Google translate is not very good for translating hebrew.

Could you write your question in english in the thread ? You will have better chances for replies.

Have a nice day.
[Upgrading, Modifying and Unlocking] pjm77:
I've been testing Corvus OS last week and can confirm that there are no major glitches. It's very good in terms of battery compared to CAOS.

I used this file and flashed Gapps nano straight away before booting up.

Everything I need seems to be working - Bluetooth sound and calls (no echo problems), Magisk passes checks, camera works but seems zoomed in a bit.
[Upgrading, Modifying and Unlocking] snoopy29:
We need to sort the auto screen brightness. I'm building/maintaining gsi lineage releases for this phone but need to upskill on how to do the brightness module.
[Upgrading, Modifying and Unlocking] linusuli:
Hi, I'm late. Search for Duraspeed in the menu Settings-applications-Duraspeed, click on whatsapp and notifications arrive.
[Upgrading, Modifying and Unlocking] kkm6761:
does arm64 A/B work? i do not see a64 A/B.

Rooting question:

anyone managed to have phone rooted in normal boot mode following guide on page 8? i had an error, I could not solve. i was unable to write the new init file.

then, i rooted the phone using recovery method. for some reason, the phone could not boot in twrp, nor in normal mode, nor even fastboot, it only booted in root mode. i had to uninstall magisk to get back to normal three boot choices.

xposed framework does not work on KKM, at least I could not get it to work. riru edxposed could not install. i already uninstalled magisk, so have not tried with lsposed, nor at least virtualxposed.

why am I going through all this trouble? to delete/hide the clock/date from lockscreen. found no way of getting that done, other than buying a samsung. so much for android customization.
[Upgrading, Modifying and Unlocking] pjm77:
Check the file I linked - it has a64_ab in it's name. BTW I'm using Ocatvi OS this week and it looks even better than Corvus. No idea about rooting - all ROMS I flashed so far: CAOS, Corvus and Octavi work flawlessly with Magisk so I went with that.

BTW I'm pretty sure you can remove clock from lockscreen in all the ROMS I mentioned above using built-in customization apps. No need for Xposed.
[Upgrading, Modifying and Unlocking] kkm6761:
Ok. I'll try them out. Other than for customization I don't need root. Lineage OS can has no option for hiding clock in lock screen, there is only a choice of 3 clocks.
[Upgrading, Modifying and Unlocking] pjm77:
Ooops, Ocatavi OS turns out to be crap. Very nice, very customizable but unfortunately buggy and horrible battery life. Back to Corvus OS.
[Upgrading, Modifying and Unlocking] kkm6761:
which build do you guys usually use? normal or vndklite/lite? what is the difference/better?
[Upgrading, Modifying and Unlocking] kkm6761:
how did you flash Corvus OS? It apparently works only with snapdaragon chipsets. for mtk selinus must be set to permissive. how did you do that? did you use lite version?
[Upgrading, Modifying and Unlocking] pjm77:
Nothing fancy, I just flashed the file I linked using fastboot:

https://sourceforge.net/projects/tipzbuilds/files/GSIs/CorvusROM/Beta/20210825/A64/Corvus_v16.8-Avalon-treble_a64_ab-25082021-Beta-Official-0000.img.xz/download

fastboot flash system [image name]

I had CAOS ROM before, my device had TWRP flashed, patched boot image to prevent the alert message on the bootscreen was flashed, Magisk was installed (but it didn't work properly - couldn't pass the checks) and encryption was disabled using the script posted earlier in this thread.

Oh, and I'm not 100% sure but I think I had to resize system partition using TWRP to be able to flash gapps (to avoid error 70).

That's literally all I did and I ran this ROM for a week or so with only minor glitches (like bluetooth icon disapperaring from status bar now and then) so it definitely works.

PS. And to avoid any misunderstanings - I've got Kingkong Mini - the older one. I'm not sure what SELinux is, I keep seeing people mentioning it often but didn't bother to learn what it actually is. I did nothing in particular to disable or enable it, I just followed the tutorial from the beginning of the thread, flashed CAOS over stock and then Corvus over CAOS.

PS2. Termux says 'Enforcing', whatever it means. Hope it helps.
[Upgrading, Modifying and Unlocking] kkm6761:
i have no twrp, stock recovery, reflashed lineage os, enable root debugging, and with abd root typed adb shell setenforce 0, to disable selinux. did clean and dirty flash, with normal and lite corvus images, but it remains stuck at corvus crow boot animation. in the meantime tried out resurrection remix and havoc os. ressurection os can hide lockscreen clock. now will try /e/.
[Upgrading, Modifying and Unlocking] kkm6761:
/e/ comes with gapps. app launcher is like iPhone.
[Upgrading, Modifying and Unlocking] landsome:
What's so great about Corvus?
[Upgrading, Modifying and Unlocking] pjm77:
For me it was battery life. I had issues with both original Phhusson and CAOS, I usually had to recharge in the middle of the day even with moderate usage. With Corvus I've got 30%-50% battery left in the evening. Plus it's rather polished and customizable. No major problems (maybe except zoomed-in camera, but all I really take photos of are shopping lists and gym program so I don't give a f...). No Bluetooth problems (another major issue on many ROMS).
[Upgrading, Modifying and Unlocking] kkm6761:
I could not try. It did not work. Customization is great from what I have seen. I use have tried Resurrection Remix, and it has all the customization I want need, especially clock delete from lockscreen and date delete from quick setting panel and more. I don't use phone as normal smartphone, only VOIP. I have front and rear cameras physically removed. want it as minimalist as can be. i just don't have the skills to port GrapheneOS, and even then there is no customization.

i see the king kong 7 looks quite good, plus is it has sim tray instead of sim cover. it also comes with nfc, would could be useful for unlocking phone. if king kong 3 mini can be similar, while retaining max 120mm x 60mm size and min 4 inch screen it would be great.
[Upgrading, Modifying and Unlocking] landsome:
Happy to hear that. In my case battery life is pretty bad with AOSP (gapps), somewhat better with LOS (no gapps).

Are you getting this battery life with gapps or without?
[Upgrading, Modifying and Unlocking] pjm77:
Small update. I was planning to go back to Corvus OS because I found Octavi OS very unstable, battery draining etc. I managed to narrow down that these things happened only when listening to the music on bluetooth headphones. Today I changed some bluetooth settings - namely "enable gabeldorsche", "bluetooth AVRCP version" (from 1.4 to 1.6), bluetooth MAP version (from 1.2 to 1.4) in developer options and Phh Treble Settings/Other Settings/Bluetooth workarounds set to "Mediatek". Some of it must have done something because I just spent 3 hours listening to the music in the gym and messing around with the phone on purpose - unlocking it, starting random apps, multitasking etc. Not a single glitch, not a single restart, very reasonable battery consumption. I'll keep testing but this looks promising.
[Upgrading, Modifying and Unlocking] pjm77:
With gapps. But to be honest it looked similar without gapps. I ran the phone without gapps for an evening and battery consumption wasn't dramatically different.
[Upgrading, Modifying and Unlocking] kkm6761:
so you are back on octavi? i like it too, it was actually my favorite not having tried corvus.
[Upgrading, Modifying and Unlocking] pjm77:
I was planning to flash the phone again with Corvus since Octavi crapped itself constantly (reboots, unable to unlock lockscreen, 50% battery gone in two hours and stuff like that). But since I changed these bluetooth options yesterday - not a single problem. I hope it stays this way because I like Octavi more and I'm so tired with all this flashing and setting up.
[Upgrading, Modifying and Unlocking] kkm6761:
i locked bootloader on custom gsi, now phone does not boot.
[Upgrading, Modifying and Unlocking] msbln:
One Day with King Kong

device: KingKongMini 1

stock [A9]: CUBOT_KINGKONG_MINI_9101C_V15_20200609 (latest)

custom [A11]: system-roar-arm32_binder64-ab-gapps.img (AOSP 11.0 v313)

recovery: TWRP_3.3x (from the 2nd post)

ROM is working fine (after I registered* it because Playstore told me to).

Otherwise no glitches at all and reasonably smooth. *uncertified-device-problem...

Originally I wanted

AOSPvanilla

and flash

BiTGApps

zip via TWRP

but I ran into /system couldn't be mounted ... Aborted...

Also tried to install Magisk23 but no luck. Same problem.

And I couldn't work out how to deal with SP-Flash-Toolv5.1904 on virtual.Win10. It worked once (and saved my ass after a stupid "fastboot erase boot"-maneuver) but never again. Maybe a working SPFlashTool-setup can resolve the mount-problem above.

Btw, when in bootloop try Vol.Down+Power than slide over to Vol.Up until dark screen and vibrate,

than release the buttons. Play patiently and you will finally reach the "Boot selection mode". This game made me crazy but always worked.

Conclusion:

Not exactly 100% success, but what do I have now?

A partially rooted KK1 with Android11 and Google-functionality

Not to bad :)

Thanks go out to all of you 🤝
[Upgrading, Modifying and Unlocking] msbln:
APN, RIL, IMS - Dual Sim Problem

I was too quick to celebrate :(

I tested all the slots, simcard and sdcard, they are all working.

But setting up SimX for data and SimY for call posed a problem.

1. The phone doesn't get any provider setting messages (???)

2. Manual APN-setting brought data to life but broke calling.

The phone probably has one modem only,

I never tested the SimXdata-SimYcall-scenario on stock extensively,

so I don't know if rom related.

Edit:

It was simcard-related, due to a call-number-porting quirck ... another simcard and the dual-simcard-performance was alright. Hardware and ROM seem fine.
[Upgrading, Modifying and Unlocking] msbln:
KK1 - Popping up the hood (just4fun)
[Upgrading, Modifying and Unlocking] msbln:
Holding Volume Up + Power gives me "Boot Selection Mode"

What's the proper name for that btw? "Preloader Menu"?

When I hold VolDown+Power it seems to normal boot.

Isn't it supposed to boot into recovery?

When I select Recovery in "Boot Selection Mode",

TWRP is launched.
[Upgrading, Modifying and Unlocking] msbln:
Is it possible to reach the "Android Recovery" with TWRP installed?

Because in my case the TWRP cannot mount /system, which makes it not very useful.
[Upgrading, Modifying and Unlocking] gmlai:
I am on stock rom on a kkm2. I can get phone call and data working at the same time only on the same SIM and setting 4g calling on. Receiving a call on the other SIM makes data stopping.
[Upgrading, Modifying and Unlocking] pjm77:
So battery is basically removable?

That's great news, I'll keep it in mind for the future.
[Upgrading, Modifying and Unlocking] samsungcubot:
Hi,

I flash with the last LOS 18 my MINI 2 , its good

But windows dont recognize phone... "Phh-treble vanilla device"

And impossible to find drivers (or instal original mini2 drivers under)...

Help please

resolved!
[Upgrading, Modifying and Unlocking] robrazil:
After 7 months since my last email with CUBOT support, I contacted them again to talk about the android 10 release for KKM1 and the someone called Setlla answered me: "The mini1 will not be upgraded to Android 10."

I said that is insane to buy the same mobile (KKM2) that I have already (KKM1) with the same architecture and hardware only to have CUBOT's android 10 official.

So... I am give up of CUBOT brand and I will encourage the people give up too.

The KKM1 was the 1st and the last product that I bought of them.
[Upgrading, Modifying and Unlocking] landsome:
On the contrary, I think the fact that they sold a KKM2 which is for-all-purposes identical to KKM1 is a good reason not to bother updating anything.

Seriously now, though, these kinds of phones are almost by design sell-and-forget pieces of hardware.

BTW, did anyone try the pre-release AOSP12 or LOS19?
[Upgrading, Modifying and Unlocking] samsungcubot:
hi!

on my mini2, los 18.1 work great, but impossible in twrp to do somethings

impossible to mount system... (ex: system_root invalid argument...)

please help

(ps: yes los19 works)
[Upgrading, Modifying and Unlocking] x53:
With KKM2 in TWRP it's impossible to mount system. Because KKM2 is shiped with Android 10 means dynamic partition respectively super partition. Thats a big difference to older android versions, e.g. explaned on youtube. On stock rom at least you can get read-only access to system using magisk. Most other custom roms have su buildin. So changes to /system can only be done "systemless". There is a buildin magisk module for. However it's very inconvenient in comparision to previous android versions (before 10). Is there a way to patch system offline and flash later? E.g. dismantle super.img to system and other partitions, patch the individual things, bundle partitions together back to super.img and flash it to KKM2? At the other hand cubot stock firmware contains system.img but flash tools doesnt flash it, only super.img. Why? What is system.img used for?

OK, forget system, but how did you manage to access data partition? TWRP can mount data but all files are encrypted. With stock rom I had no success in running an unencrypted data partition. I tried format data with ext4 like descripted here. And I tried to apply DM-Verity Disabler or no-verity-opt-encrypt. But every time I rebooted stock rom, data was encrypted again. Without access to system partition those (old?) scripts wont work anymore. Is there another way for Android 10 (adb sideload, flash tool, ...)? TWRP would be nice for backup and revocery data partition. Have you found other ways for backup data partition? How do I get rid of encrypted data partition? Is this only possible with custom rom?

Btw KKM2 battery is not like the KKM1! It looks like this. It's a Li-Polymer 3.000mAh battery, named CBT-A061.

Flash Tool is very nice. With that you can remedy all flashing mistakes and begin from the start, nice phone.
[Upgrading, Modifying and Unlocking] msbln:
Same here, TWRP cannot mount /system. #287

I might try and return to the stock "Android Recovery" which promises exactly that.

Or will that be

also

read-only? Any experiences?
[Upgrading, Modifying and Unlocking] msbln:
In my case (KK1) I can mount every partition displayed in TWRP.

The TWRP-FileManager displays all the contents, so I assume encryption is successfully not in place. Backing up/restoring therefore should work. Only thing is that mounting /system is read-only.
[Upgrading, Modifying and Unlocking] msbln:
When it comes to modem modes and dual sim scenerios the following app I found really handy:

4G LTE Only Mode - Apps on Google Play

Lock your phone in 4G/3G/2G network and stay in chosen network

play.google.com

Gives you easy access to the 'hidden' Phone Info menu.
[Upgrading, Modifying and Unlocking] msbln:
Ok, but is that also true for the KK1 which was shipped with Android 9 ?

I couldn't mount /system writable from TWRP either.

Yet I haven't tried using the stock "Android Recovery" option.