yashsingh1/xdaforums huggingface dataset:
[Upgrading, Modifying and Unlocking] landsome:
Also: I notice that phhusson's AOSP10 has a 'go' version as well. I assume it's Android Go. I imagine that would be pretty good on a low-powered device such as the KKM. In case someone decides to test it before I do. :)
[Upgrading, Modifying and Unlocking] mekaddisu:
Yeah, its the lineage-17.1-20200808-UNOFFICIAL-treble_a64_bvN.img.xz from the page mentioned. I never tried AOSP because I was going for a google free OS.
[Upgrading, Modifying and Unlocking] landsome:
Does flashing the patched lk via fastboot work with the normal recovery, or does TWRP have to be installed first?
[Upgrading, Modifying and Unlocking] Ce3apyc:
Yes, you can flash them separately.
[Upgrading, Modifying and Unlocking] landsome:
Thanks
[Upgrading, Modifying and Unlocking] landsome:
Played a little with AOSP 10 and LOS 17.1. My observations so far:

- Only issue I have found is battery usage reporting; and battery more generally. I've been using AccuBattery to charge below 100% on all my phones for a while now. It's always worked decently well in measuring battery capacity (over many charge cycles) on all sorts of ROMs. With Cubot it works very poorly in both AOSP and LOS, yet works well with stock.

Edit: In-call volume adjustment does not work. True both in AOSP and LOS (September 2020).

Edit: Another minor issue: sometimes, if using gestures rather than buttons for navigation (to conserve screen real estate), the recent apps gesture fails to work - in other launchers than default, both in AOSP and LOS. The solution is to revert briefly to default launchers (Quick and, respectively, Trebuchet), then go back to third-party launcher.

- This being said, battery life is much improved with these custom ROMs. A little better with LOS than with gapps-enabled AOSP, but not a huge difference. Consumption under idle (12 hours) is somewhere around 7-9% (wifi and bt on, sim data off). Battery was abysmal with original Cubot ROM.

- That's although, as far as I can tell, the stock Cubot ROM is essentially an AOSP 9 with very few modifications (battery, face unlocking app and a very few others apps, custom icons are obvious - there may be more under the hood). It even has a stock AOSP wallpaper and launcher (Quickstep).

- Incidentally, both the stock and the custom ROMs have the same automatic brightness problem: it defaults to a high level (80-85%) even in relatively dim environments and is generally poor in self-adjustment.

- With both custom ROMs, GPS works particularly well; locks in quite rapidly (among the best in phones I have used).

- Also, in both custom ROMs, including the gapps-enabled AOSP 10, the user experience feels perceptibly smoother than with the original ROM for some reason.

All in all, I think it makes a lot of sense to switch to Treble custom ROMs, either AOSP (vanilla or with gapps) or LOS. I would love one with microG but I have had a hard time making it work on LOS.
[Upgrading, Modifying and Unlocking] KTMuser:
I flashed phhuson AOSP 10.0 v222 from here: https://github.com/phhusson/treble_experimentations/releases

it was this one: system-quack-arm32_binder64-ab-go.img.xz

everything seems to work fine except in call volume adjustment.

does anyone have a solution how to get in call volume to be adjusted?
[Upgrading, Modifying and Unlocking] landsome:
Why the go version? I do not have this problem with the gapps version.
[Upgrading, Modifying and Unlocking] landsome:
September version of LineageOS is out: https://sourceforge.net/projects/andyyan-gsi/files/lineage-17.x/

Has anyone tried it? I stuck with AOSP over LOS, but would switch if LOS solved battery issues.
[Upgrading, Modifying and Unlocking] landsome:
Apologies. It does not work. I change volume in my bt headphones, but not via volume keys.

Edit: LOS exhibits the same behavior.
[Upgrading, Modifying and Unlocking] cest73:
Hello,

so far so good, tried the AOSP Treble and LOS 17.1 and found:

1. the front camera does not register.

2 the compas on LOS seems to work in the "GPS test" app quite well

3. lots of options on the status shade but no screenshot there (i miss that)

4. took the non-gapps LOS and am getting used to that yet (Aurora Store)

5. using the XDA Labs (works great!)

The icons are tiny! (4x5 layout) but the text seems okay ("large")

The battery seems to be okay, but no power profile can be changed and the max speed is locked to 1.8GHz (opposed to OEM 2.0 GHz)

Still failed to flash the lk_<somethink> from the TWRP, will read the thread over again...

the exact LOS used:

lineage-17.1-20200913-UNOFFICIAL-treble_a64_bvS.img.xz

Nice work so far and thanks a lot!
[Upgrading, Modifying and Unlocking] landsome:
Great you like it! Flash the LK thing via sideload. Worked for me.
[Upgrading, Modifying and Unlocking] cest73:
what is the LK img payload? is it the kernel?
[Upgrading, Modifying and Unlocking] landsome:
Not sure, tbh
[Upgrading, Modifying and Unlocking] randomaccess0:
Magisk normal boot install (non-recovery mode)

I just want to share Information here for reference.

I have followed the instructions from this thread to install LineageOS 17.1 on my CUBOT KINGKONG MINI.

After this was running fine, the next step was root. Like already mentioned, magisk can be installed in the recovery and after booting the device in this recover-root-mode root is available, but the mobile network and sim detection is broken. I assume something is wrong with recovery boot args or the recovery kernel or se-policies or hardware initialization or whatever. Recovery-mode usually does not boot to a full operating system and so developers don't seem to care about correct initialization of hardware not needed to restore or update the device so much. As this was a nogo for me, I searched for a way to install magisk to the normal boot.img, despite the fact, that this device does not use a ramdisk, where magisk places itself.

In "[A Russian Development site that XDA doesn't trust and doesn't want me to mention]" I found a solution consisting of a modified boot.img, which has been patched by magisk and then the kernel was patched to use the ramdisk. Thanks to pndwal the boot.img is available here: https://xdaforums.com/showpost.php?p=83493745&postcount=41477

This information is provided without warranty. Everything you do is at your own risk.

1) unlock bootloader, flash twrp recovery from post #2 (not needed but still always handy), and vbmeta like pointed out in post #1. Make sure you are able to flash and boot custom images.

2) boot the phone, install latest magisk manager app (canary build)

3) copy the boot.img from linked post to the phone.

4) in magisk manager install magisk, unselect recovery mode and select the boot.img file. (make sure you are connected to the internet)

5) copy modified boot.img back to pc

6) restart phone to fastboot mode and flash modified boot.img

7) restart phone and enjoy magisk in normal boot mode and with working mobile network

8) when updating magisk DON'T LET MAGISK MANAGER FLASH THE IMAGE (direct installation). I tried that once and magisk didn't flash the boot partition but something else, maybe recovery. So always select boot.img to patch and flash that manually in fastboot mode

Happy rooting
[Upgrading, Modifying and Unlocking] cest73:
For the time I'm back to stock

Got those few Mediatek apps saved with my apk...

Anyone any luck with FM radio yet?

I got the type C to 3.5 converter plug but no dice yet

Also my KKM is still 4x1.8 ghz not 2.0, can anyone confirm stock runs 2.0GHz or 1.8?
[Upgrading, Modifying and Unlocking] pozip:
Hello, I am very interested that the radio works, I bought a C-jack adapter but the radio does not detect that it is connected and it does not work.

It would be interesting if you could activate the radio without the headphones connected and thus be able to use it.
[Upgrading, Modifying and Unlocking] birdibird:
I guess you mean PHH AOSP?
[Upgrading, Modifying and Unlocking] moctir:
Yes, this one.
[Upgrading, Modifying and Unlocking] birdibird:
You can consider dirty-flashing to AOSP 12.1 v416 or even to A13.

Worked for me.

I am on LeOS 20 (LOS based A13) now on my KKM2
[Upgrading, Modifying and Unlocking] moctir:
I might try that thanks. Is there any disadvantage to dirty flashing? I've only been using it a week so tempted to format and go again. Test both V416 and LeOS and see if I can get everything working. I haven't looked into Android 13 but I assume there are less bugs in A12.

Do you have issues with the charging light not going off when it's fully charged? I'd live with that though if the Bluetooth worked!
[Upgrading, Modifying and Unlocking] serj_sar:
I did everything according to your guide. I downloaded the firmware here: https://sourceforge.net/projects/tipzbuilds/files/GSIs/CorvusROM/Official/20221015 / but I still have a boot loop. What am I doing wrong?
[Upgrading, Modifying and Unlocking] birdibird:
I don't know if this makes a difference:

But did you first flash the new V07 Rom from the Cubot website with SPFlashtool, and selected in developer options OEM unlocking and USB debugging?

btw these steps are not needed at all:

fastboot flash boot boot.img

fastboot flash recovery recovery.img

this step is not recommended unless you get a message that there is not enough space for the gsi:

fastboot flash product product_gsi.img

this step is not recommend as it could cause problems:

fastboot -w

(wipe data/factory reset is enough)

So: these are the correct steps for all kkm devices:

-flash newest rom from Cubot with SPflashtool

-boot into the rom and select in developer options OEM unlocking and USB debugging

-reboot to fastboot/bootloader mode

-fastboot flashing unlock

-fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (the one from the Cubot rom you downloaded)

-fastboot reboot fastboot

-fastboot flash system GSI.img

-navigate to 'enter recovery' to enter recovery.

-wipe data/factory reset

restart system
[Upgrading, Modifying and Unlocking] moonraver:
I have found this procedure in LeOS wiki (see lower part of that article = when bootloop):

Standard Android 10 and above (with dynamic partition) · Wiki · LeOS / LeOS-Wiki · GitLab

Wiki for LeOS users

gitlab.com
[Upgrading, Modifying and Unlocking] serj_sar:
I do everything exactly like this

I get a hang on the logo are boot loop
[Upgrading, Modifying and Unlocking] serj_sar:
there is no ab partition on our devicesView attachment 5778165
[Upgrading, Modifying and Unlocking] moonraver:
1st I have to say that KKM3 is really a great device! Original ROM is really smooth and I had no problems.

But google is google so now I am trying to flash latest LeOS 19.1 bvS and I can confirm that it is NOT working as you have mentioned here. There was not enough space to flash so I had to use KKM2Pro procedure and delete "product" partition. After that, flash proces was successful. But after reboot it always stuck on Cubot logo with Orange state.

So I tried LeOS wiki procedure as I had mentioned before but with the same result.

Any advice?

Update:

Same results after flashing November LeOS 20 bvN, LeOS T, LeOS 19.1 bvN
[Upgrading, Modifying and Unlocking] serj_sar:
del
[Upgrading, Modifying and Unlocking] moonraver:
I have answer from harvey186 (LeOS) about flashing GSI images in KKM3 with picture from chat:

"As far as I remember no GSI was booting on kkm3."

Maybe next stock update will solve anything.

​
[Upgrading, Modifying and Unlocking] moonraver:
Has anybody noticed this on KKM3 running stock ROM?

Settings\Battery\Battery usage: "Battery usage data isn't available" ..........still after one week

The same issue I had on KKM(1).
[Upgrading, Modifying and Unlocking] Zaunkehlchen:
Hello,

my KKM2Pro is in an infinitive bootloop. It turns on into orange state and after 5 seconds it reboots again. All the time.

I have read how to remove orange state, but my Problem is that I can not leave the bootloop to go to fastboot again. Pressing the buttons in various combinations didn't help.

Do you have any idea how I can leave the orange state bootloop an connect it to my PC again?
[Upgrading, Modifying and Unlocking] moctir:
This happened me after trying to flash a custom vendor. As far as I can see your only option is to use SPFlash tool and recent to stock and then go again. Your best bet is to wait until the battery runs out as if you try to do it before then it will likely attempt to boot while using the tool is running and then will be bricked (until the battery runs out and you can use SP flash tool again).

The only other possibility is if you plug it in to your computer and type `adb devices`, sometimes you get a second where it will find the device during the bootloop. If you're fast enough you might be able to do something like `adb reboot recovery` or something that may work, but I think it's unlikely.
[Upgrading, Modifying and Unlocking] Zaunkehlchen:
Thank you for the help! It worked and I succesfully flashed Lineage 18.1!

My mistake was, that I flashed the wrong stock firmware. I thought I have the KKM2Pro but actually I have KKM2.

Am I right, that there is no way to long-term root the kkm2 (with normal but, not always booting from recovery)? From reading this thread I have this impression, but mayby I overlooked some posts.
[Upgrading, Modifying and Unlocking] moctir:
I think it is possible. So early in this thread I talk about the original KKM, on that I had to patch Magisk to recovery to get it to work and could root it through that. However I didn't get signal then because for some reason the IEMI was different when I booted to Recovery. Note this could have been fixed, there are ways to set the IEMI I just didn't use root enough to warrant it. I don't know the situation for the KKM2 but with the Pro Magisk worked as normal by patching it to Boot. So I would try Magisk with Boot first, if it doesn't work patch Recovery and see. If that does work, if you don't have signal check the IEMI compared to when you boot normally.
[Upgrading, Modifying and Unlocking] dank2019:
Hello, I flashed the LeOS 20 (AOSP 13) on my kkm1 yesterday. Most of the things look good.

One thing: the screen flickers from time to time. It looks like a CPU and GPU rendering issue. If I enable only HW rendering, the flickering is gone. However, the gpu-based screen is much brighter (in dark mode) than the cpu-rendered screen. I have not been able to change this. The contrast is also not the best (light gray letters on a slightly darker background). Does anyone have an idea what I can change?
[Upgrading, Modifying and Unlocking] Truelan:
my BAD MEMORY gave Hope torture to most people.

Really sorry. maybe just should not writing about flashing.

I just flashed for test and I sold KKM3. it does not match my needs.

so that, I does not write and forgot about process.

Just only I remember is almost same. but now, as a result, completly different.

and one more time, sorry.

I still cannot recall my memory.

when I first received, I imedately flashed gsi.

I tried to boot crdroid GSI. but struck in cubot logo.

and all phh based GSI happend same.

and I saw red state. not orange state. so I recheck my process.

red state changed to orange state. but same.

so I tried almost same, but little different base gsi. that is corvus gsi.

maybe I did some different process I thought.

busy day makes my memory blank.

these are process options what I could select possibly when does not work.

only one thing I remember, but does not certain, is

system load failure -> in stock recovery, factory wiping -> done.

1. delete product partition instead of flashing product.img

2. flash "blank" vbmeta.img instead of stock vbmeta.img

3. fastboot -w in bootloader mode, not fastbootd mode.

4. after flashing gsi, don't fastboot -w.

5. factory wiping via stock recovery.

6. if you see some partion error(It is certain - cache partition) in fastbootd or stock recovery,

you should solve that.

mean, that error does not shown up when next boot(fastbootd or stock recovery) process.

maybe flashing gsi process delete some partiton.

I does not type any command related to partition creating.

one more time, really sorry. maybe these process does not help anything.
[Upgrading, Modifying and Unlocking] badcodelab:
well, the new stock build has arrived https://cubot.net/platform/Support/detail/id/680/cid/86.html

has anybody tried to flash gsi over it?

anyway thanks for sharing
[Upgrading, Modifying and Unlocking] moonraver:
OTA update still not available
[Upgrading, Modifying and Unlocking] moonraver:
Bad news............Yesterday I tested new KKM3 firmware (new fresh flash with cable):

CUBOT_KINGKONG MINI3_C031C_V08_20221206

January GSI LeOS 19.1 and December LeOS 20 aren't working. Booting still hangs on Cubot logo.

Differences in new firmware:

- still smooth, maybe a little bit smoother

- Battery usage still not showing in Settings

- "Battery optimization" option with list of all applications can not be found anywhere in settings. I can only call this option when app like Netguard asks for excluding from optimization. Optimization can be set only separately for every app in Settings/App

- more of Material Me setting in apps

- default "Display size" and "Font size" is smaller

- default launcher has new option "Home screen layout". Icons placement can be from 5x3 to 6x5

- camera with no improvements (still testing)

- Wellbeing can not be disabled still, other google apps can be disabled
[Upgrading, Modifying and Unlocking] moonraver:
KKM3 bug found: Capturing video In FPS 30 mode with auto mode (=not manual mode)

There is one thing I found out yesterday that annoys me a bit. I'm going to send this to Cubot (useless) support and hope they will read it at least.

Camera captures video with the highest value of ISO = 400!!!. It is a matter of stock camera and many other 3rd party camera apps using Auto mode. So if you want to capture videos with 30 FPS in low light conditions (ISO higher than 400) your video will be too dark to see something.

In addition, the highest video FPS from stock camera is only 23 instead of 30 FPS.
[Upgrading, Modifying and Unlocking] birdibird:
The kkm2 can work with permanent root.

Just flash a gsi with b?S (inbuilt SU root) or if you flash a b?N version you can patch boot.img with Magisk and flash the patched boot.img with spflashtool or fastboot.

I have the kkm2 working with LeOS 20 A64 vndklite bvN and Magisk.

(=Android 13!)
[Upgrading, Modifying and Unlocking] FasterPhoneMaster:
There is a report that it is possible to flash lineage-20-light build to KKM3. According to user he was using modded stock firmware before flashing.

https://sourceforge.net/projects/andyyan-gsi/files/lineage-20-light/

Spoiler content hidden.

Spoiler content hidden.
[Upgrading, Modifying and Unlocking] birdibird:
The instructions you share are quite standard for a gsi, but do not mention the modded firmware. Where can it be found? Do you have a link?
[Upgrading, Modifying and Unlocking] moonraver:
and what about disabling vbmeta

How do you know that it is a screenshot from KKM3?? There is nothing written in Russian language about KKM3.

And where can I find that report? There is only a link to image
[Upgrading, Modifying and Unlocking] FasterPhoneMaster:
You can find discussion from 4pda forum:

https://4pda.to/forum/index.php?showtopic=1056175&st=1960#entry120412753

However, someone else tested those instructions after my message but failed like people here (endless bootloop). But I still think that the first user was able to flash a specific GSI LOS 20. At least the screenshot has same resolution than KKM3 and the same user has posted other KKM3 related stuff to the forum.

https://4pda.to/forum/index.php?showtopic=1056175&st=1980#entry120434752

Maybe there is something that we are missing? I don't understand Russian but there was some talk about "specific keys" to unbrick devices after failed OTA (common issue). Can flashing those keys affect to rom flashing? I don't know what those are.

https://4pda.to/forum/index.php?showtopic=1056175&st=1580#entry119691637
[Upgrading, Modifying and Unlocking] moonraver:
I have translated it and read it. They still have problems with bootloop. That flashing procedure that someone wrote about was a standard procedure for flashing GSIs and wasn't working. So there is still no progress.

I'll keep watching that Russian forum to get some news.
[Upgrading, Modifying and Unlocking] FasterPhoneMaster:
Others has not been able to flash LOS build but according to the screenshot it is possible. The user who did it has done many mods to the phone. Maybe some of those can have effect?

Root: https://4pda.to/forum/index.php?showtopic=1056175&st=1280#entry119405117

Remove Orange State: https://4pda.to/forum/index.php?showtopic=1056175&st=1440#entry119559233

Modded firmware: https://4pda.to/forum/index.php?showtopic=1056175&st=1660#entry119898930
[Upgrading, Modifying and Unlocking] FasterPhoneMaster:
They now posted firmware dump of the LOS 20 installation (KKM3). However, there are many issues.

https://drive.google.com/file/d/1MzP77dKzK6voi6oNwD47VuWA-fkRqHPe/view

https://4pda.to/forum/index.php?showtopic=1056175&st=2020#entry120499560
[Upgrading, Modifying and Unlocking] moonraver:
Solution for better videos and photos with KKM3

I have made couple of tests with 3rd party apps and here are some results.

Better videos:

Almost constant 30 FPS, no low ISO problems: PROTAKE app (free for auto mode) from Aurora (Play) store although there is still present a re-focusing problem (my settings: H.265, 32 Mbps, 30 FPS).

Better photos:

Hedgecam 2 from Aurora (Play) store. My settings: JPEG quality 100%, NO filtering = NR, edge enhancment, hot pixel etc.
[Upgrading, Modifying and Unlocking] badcodelab:
as far as i remember the conversation was about restoring imei and firmware after accidental flashing via spft in format mode

as for gsi nobody from 4pda could reproduce successful flashing so far
[Upgrading, Modifying and Unlocking] FasterPhoneMaster:
But there is already firmware dump available of successfully LOS 20 installation. So it is possible to flash GSI. Now we just need to figure out how to reproduce it. Or then there is different hardware on some units...
[Upgrading, Modifying and Unlocking] badcodelab:
yep, i didn't say that i don't believe that guy or it's impossible

here in this thread there is also a guy who claims he managed to install corvus gsi

something significant in the process is still missing tho
[Upgrading, Modifying and Unlocking] FasterPhoneMaster:
Has anyone here tried to flash LOS 20 firmware dump via SP Flash Tool (KKM3)
[Upgrading, Modifying and Unlocking] Vilkoko:
Hello,

I installed LeOS-20-VNDKLITE-a64_bvN.img on my new KKM2, it works fine except for the SMS : I can send SMS but I can't receive SMS. This seems very odd to me.

I tried SimpleSMS and Silence apps, same result.

Really stuck here, if anyone can help... 🙏
[Upgrading, Modifying and Unlocking] birdibird:
Strange, on mine Silence is working fine.

Did you set it to the standard sms app in settings?
[Upgrading, Modifying and Unlocking] Vilkoko:
@birdibird

Thanks for answering.

Yes, Silence is set as default sms app.

Why would it be able to send but not to receive ? Something is wrong.

I tried these:

- swapping sim slots

- changing sim (other network provider)

- restart billion times

- checking smsc number

None succeeded.

Don't know if it's related to my problem, but I can't sign in Gmail web page (not app): "Unable to connect" either Wifi or 4G.. Other web pages are ok.

I think I will return to stock rom, then try flash again... It takes hours when you're not familiar with process.

Any other solutions appreciated.
[Upgrading, Modifying and Unlocking] birdibird:
You don't need to go back to stock!

Just do a factory reset in settings, and try again.

(if it doesn't work, let me know and I will try to help)

Google apps are not supported by LeOS, that is the point of that gsi.