yashsingh1/xdaforums huggingface dataset:
[Upgrading, Modifying and Unlocking] x53:
With lineage-18.1-20220217-treble_a64_bvS I had the bluetooth headset echo problem (usingwith KKM2). I solved the problem by editing audio_policy_configuration.xml and audio_policy_configuration_bluetooth_legacy_hal.xml in /vendor/etc

@covexx: For informational purposes only, somewhere at 4PDA people had published vendor_NoCrypt.img and TWRP v3.5.1 for KKM2. Vendor_NoCrypt.img disables FBE at data partition, so data has no FBE with AES-256-XTS anymore. But think about it. It's a big security issue (don't lose your phone) und you have to erase data in the first place. Encrypted data will not be deciphered! IMHO for KKM2 there is no other way for disabling encryption (look at Settings > Security > Encryption). I haven't tried it yet with stock rom. But with custom roms it works for sure. Btw TWRP v3.5.1 enables access to dynamic partition, e.g. system. Only to backup/restore a unencrypted data partition you can stick with TWRP 3.4.0.

Mod Edit: Link removed.
[Upgrading, Modifying and Unlocking] Lukas+:
From #205 by @birdbird I also tried the Corvus OS, that I'm still using.

So, for example, this should be a working configuration for KKM2:

Corvus 16.8 Avalon Beta Official (Android 11);

Magisk 22.1 (maybe the last version, or one of the latest, with magisk manager "alone");

PhoneSky.apk in data/adb;

Micro G installer revived 2.6.0.3 (latest while I'm writing);

SElinux permissive;

Riru manager;

Exposed manager 4.5.7;

Riru 22.4;

Edexposed framework 0.5.0.6 YAHFA;

App settings Reborn 1.4.1 (for now doesn't work with latest telegram and that's not easy installing older one, moreover I found ASR 1.5 worst of 1.4.1. It doesn't work with latest Brave browser but with a bit older works);

Fonter 2.6 (no Telegram o TurboTel for now).

Well, these were the first in order...

For now I did anything else for TWRP and I really don't know if there's someone with a TWRP working on dynamic partition.

If someone knows something...

Certainly that's not the newest or the powerful configuration, but it's stable, perfect and complete for everyday use, fast, very nice.

I've problems only in buying app in Google Play Store with phone operator, (Vodafone, wind...), but I think I will solve.
[Upgrading, Modifying and Unlocking] kkm6761:
Teaser of KKM3 that should come this year. Looks like it retains the same size, but new styling and side sim slot.

Yes I did. It worked normally. I have KKM1.
[Upgrading, Modifying and Unlocking] landsome:
Great! Did they announce it officially?
[Upgrading, Modifying and Unlocking] kkm6761:
kind of.
[Upgrading, Modifying and Unlocking] linusuli:
Hi, when i flash kkmn2 whit "super" is Ok, but not

Hi, were you able to fix this? The same thing happens to me
[Upgrading, Modifying and Unlocking] x53:
@linusuli: Worst case, take flashtool and start over flashing original stock rom. But maybe it suffices flashing the original logo.bin.
[Upgrading, Modifying and Unlocking] linusuli:
Well, Linux not detected Android and w10 say usb descriptor error...😅
[Upgrading, Modifying and Unlocking] x53:
Thats very unfortunate. Sadly I can say for me it did work. Means I did start flashtool, select download tab, download-Agent=MTK_AllInOne_DA.bin, Scatter-loading File=MT6761_Android_scatter.txt, select Firmware Upgrade and hit the download button. After that plugin the KKM2. The bootloop should stop and the stock rom should load. Maybe you have a problem with the usb driver?
[Upgrading, Modifying and Unlocking] Khaver89:
Can Someone update the guide to install any(safe) custom rom on this device? BCS i read all the thread but cant understand some passages, Ty guys :)

(I dont want to Stick with this chinese spyware) :(
[Upgrading, Modifying and Unlocking] PINI12:
Friends ask for help about the Root

I installed TWRP and after hours of searching, I found a method to unencrypt files by installing certain files and because I didn't know what the role of each file was, I installed all of them:

Disable_Dm-Verity_ForceEncrypt.zip

DisableForceEncryption.zip

FCrypt_Disabler.zip

no-verity-opt-encrypt-6.0.zip

(I was desperate and didn't understand what each file did exactly)

Then I installed Magisk Zip by the recovery and the Magisk APK

All installations went through TWRP with no errors at all including the Magisk Zip

But I haven't taken root yet and I still have a question mark instead of a green vi

Did I do something wrong?

What are the steps that need to be done and are they important to order?
[Upgrading, Modifying and Unlocking] pikas81:
I have black screen too and unworking buttons since 4 days ago. How long will take discharging battery in this state? I try around 10 times a day to power up the phone. I'm very patient but I'm thinking on disassemble phone and battery despite losing the warranty.
[Upgrading, Modifying and Unlocking] moctir:
Usually it would discharge for me in about 2 days so not sure why it's taking so long. Have you tried plugging it in and switching it on after that time?
[Upgrading, Modifying and Unlocking] pikas81:
Yes, I connect it every 2 days to the computer for a few seconds preventing it from recharging, today it has been 10 days since the screen is black and the buttons do not respond, I only get blue light when connecting it to the computer. The phone was fully charged when it stopped working. I tried to flash lineageos following this guide with no luck, then I flashed stock rom, the phone worked perfectly, but I forgot to lock the bootloader. The phone stopped working after using the command "fastboot flashing lock".

I have cut a usb cable to be able to measure the voltage that the phone gives by the usb, this being 0.5v in this state, and with the battery fully charged. After these 10 days it continues to give a voltage of 0.5v. I imagine that when the battery runs out, the usb will not give any voltage, but I am afraid that the phone as it is now is not consuming battery. Can anyone confirm if disassembling the battery gives the same result as waiting for it to run out?
[Upgrading, Modifying and Unlocking] PINI12:
I tried to burn recovery_TWRP.img together with lk_patched.img and vbmeta.img (solve the BOOTLOOP problem)

Burning failed (probably because I burned a revised BOOT file for Root before)

And the phone went off and nothing could be done. I unscrewed the screws and removed the battery and everything went back to normal.

It took me 5 minutes of work instead of waiting a month for the battery to discharge
[Upgrading, Modifying and Unlocking] pikas81:
Thanks dude! I will do it too, and post the result.
[Upgrading, Modifying and Unlocking] pikas81:
It doesn't work for me, it seems to be totally bricked, I will try to discharge battery manually with the hope of that works.
[Upgrading, Modifying and Unlocking] pikas81:
Finally I could bring it to live flashing stock rom with SP Flash Tool, both files downloaded from here:https://www.cubot.net/index.php/platform/Support/detail/id/311/cid/8.html (I suggest you to download the instructions posted in that site)

At first, I tried it in linux (with SP Flash Tools downloaded from another site), the last version of SP Tools didn't recognize the MT6761_Android_scatter.txt, and v5.18 recognized it, but flash process was stuck at 0%.

Then I tryed at win 10 with downloaded files from cubot website and it worked (no VCOM drivers need to be installed)

My battery was empty, but after flashing I had to wait arround 2 minutes while usb wire was connected to phone, to see the empty battery icon.

After that, I could turn on my phone.
[Upgrading, Modifying and Unlocking] googlag:
Hi everybody. Is there any chance to get phone work better if i install aosp10 treble or los17 treble?

for example, will this release work - https://xdaforums.com/project-trebl...velopment/aosp-10-0-quack-phh-treble-t3992559 ?

what means "go" in realese name? system-quack-arm32_binder64-ab-go.img.xz

has it built-in su?
[Upgrading, Modifying and Unlocking] savarikas:
10 days tried many things (all unstable). I stick to the first stock rom mostly because its faster and troublefree. Quality sucks btw. The phone could nt stand a sudden splash of water and had to be dissasempled to dry. For root I will try kingo spywarebecause because I can kill the session the old fashioned way ;)
[Upgrading, Modifying and Unlocking] dank2019:
Root Access

Hi,

after I've seen this thread I immediately ordered a Cubot Mini ;). Today, I was able to manage most of the things, TWRP, AOSP and unencrypt are installed. I definitively want root access, e.g. to enable the firewall. Sadly, Magisk is somehow not working. I installed the manager and downloaded the zip (several times). After TWRP install of the zip, the manager still shows me the zip is pending. I tried several things like reinstall and factory reset.

Has someone an idea, how I can get my root access.

Thanks
[Upgrading, Modifying and Unlocking] PINI12:
Steps:

1: Enable debugging in key options and enable OEM unlock

2: Unlock OEM by Minimal ADB and Fastboot commands:

adb devices

adb reboot bootloader

fastboot flashing unlock (volume key up for confirmation)

fastboot reboot

3: Copy the zip files to the card memory

4: Install all IMG files with SP TOOL When the phone is off

Important Warning: Select SP TOOL "Download Only" and not Format and Download

5: Get into recovery Format data of internal memory

Do not exit recovery

but go back to the installation menu and install Magisk Zip and Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip

reboot system

The files:

https://f2h.io/krrm5huqaz4z
[Upgrading, Modifying and Unlocking] dank2019:
Yes, it works fine. AOSP 10 is running on my cubot, now.

---------- Post added at 12:57 PM ---------- Previous post was at 12:56 PM ----------

AOSP 10 (system-quack-arm32_binder64-ab-vanilla.img.xz) from https://github.com/phhusson/treble_experimentations/releases gaves me root out of the box.
[Upgrading, Modifying and Unlocking] pikas81:
Lineageos 17.1 works like a charm at my kkm, even battery duration it's really good. I use a sip account to receive calls (it drains a lot of battery) and an openvpn tunnel, I have both services connected all the day and I have battery enough for a day without charging, until I go to bed.
[Upgrading, Modifying and Unlocking] mekaddisu:
Which method did you use to flash 17.1? You mentioned in an earlier post you couldn't run it after installing using twrp. I'm getting my KKM soon and I was hoping to go directly to 17.1.
[Upgrading, Modifying and Unlocking] moctir:
Did you use the generic LineageOS image? Also does "battery usage" show you anything if you check it?
[Upgrading, Modifying and Unlocking] landsome:
So what is currently NOT working with Android 10 (AOSP and/or Lineage)? Could somebody please summarize this?
[Upgrading, Modifying and Unlocking] mekaddisu:
I am now on 17.1 and here are the steps I followed:

1. Flash the newer OS from King Kong's site using the instructions and flash tool already there.

2. Follow these steps and a few commands in the first post to unlock the bootloader and install the treble 17.1 img:

Enable developer options by tapping the build number in Settings -> About Phone 7 times

Enable USB Debugging and Allow Bootloader Unlock from developer options

While connected to the computer with USB debugging turned on, issue the following command from the computer:

adb reboot bootloader

Once in bootloader mode

fastboot flashing unlock

Then confirm unlock on the phone

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

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

Unzip the .xz image file you wish to use (I used the treble build) and type:

fastboot flash system SYSTEM.img

Reboot and that's it.

I did root the same way the original post suggests but I didn't find much use for it, especially since debloating apps can only be done from recovery (root doesn't work on normal boot) and the removed apps are still present during normal boot.
[Upgrading, Modifying and Unlocking] landsome:
If i understand correctly, the boot.img & recovery.img files are those of the latest stock rom. Have you tried TWRP and it failed?

Also, anything significant that does not work?

Thanks.
[Upgrading, Modifying and Unlocking] linusuli:
thank you very much, no problem with the drivers. remove the battery and try to connect it to the flashtool again.
[Upgrading, Modifying and Unlocking] linusuli:
Well, I removed the battery and the kkm2 is up and running again.
[Upgrading, Modifying and Unlocking] linusuli:
Hi, fastbootd doesn't work on linuxmint or w10. When I do "fastboot reboot fastboot" or it says it doesn't exist or if it does it reboot the mobile back to recoveri. the other, "fastboot flash system" says it doesn't exist and "fastboot flash super" does record but doesn't boot, it stays brick. finally and after all that I do flashtool and flash preloader, boot and recovery ... because that also stays like stone. I'm sorry, I don't speak enough English and I use google translator.
[Upgrading, Modifying and Unlocking] x53:
I use Win7 and have no problems. For detaching the battery I had opened my KKM2, too. But there is no need for I've learned later. Flash Tool stops boot loop so there is no need for detaching the battery. In Windows Device Manager my KKM2 is recognized as USB\VID_0E8D&PID_201D&REV_0223 (Section "Android Device" and "portable Devices"). Have you read readme.txt for Windows 10 shipped with the cubot MTK driver? Look at point 6.) ... Please customize your kernel VID/PID). Maybe you have to edit drivers inf files for your mobile and reinstall it again. Just a hunch?! When you can use ADB or transfer files then fastboot and fastbootd should work too. Have you unlocked your KKM2?
[Upgrading, Modifying and Unlocking] linusuli:
nothing, there is nothing to do. system does not find it and super flashes it but at startup it starts in fastboot.
[Upgrading, Modifying and Unlocking] Lukas+:
Really? Not a joke? Uhhhh! It should be great! The new king Kong mini 3 aka black turtle aka mountain tire aka... we will see. But I would like it to be more powerfull, even if more expansive, with not one but 2 cameras, or an optical zoom, an optical stabilizer (I need it), a little bit more complete front camera, because cameras are not so bad! I know, there are dimension problems if you start putting this and that but... That's why we pay it! Do you imagine it with a dimensity 1200? I would like a bit more internal memory, if possible, and support for largest external memory! I would like a 6 or 8 mb RAM to serve, and I would like the same screen fundamentals, with squared angles and camera out of the screen. I'll pay the price it is, 500, 700, till 900 euros, yes. I would like a screen you can see also under the sun.

I don't know why at Cubot make 30 instead of 31, with a premium 4 (or a little more!) inches phone.

A lot of people know this phone, and everyone recognize it's one of a kind.

Maybe I also would prefer kkm3 with the symbolic kkm2 Cubot plate in the rear, but it's so nice so!

Come on, Cubot let's put into that great case a super hardware!
[Upgrading, Modifying and Unlocking] Lukas+:
@kkm6761, where did you found it?
[Upgrading, Modifying and Unlocking] ylavi:
Hi - I haven't posted about KKM before; I guess this is the best thread for my questions:

1. (On-topic, but maybe already not relevant to me :() My KKM1 still runs the stock ROM. I haven't wanted to risk flashing it yet. Is there a custom ROM which is considered by most to be reliable/stable and not have anything significant in the "not working" list?

2. (Maybe off-topic but KKM-related) Last week the USB connection on my phone stopped working. It still charges but when connected to computer and car head unit neither side notices the connection. In the day or two previously I had (a) installed a new app or two and (b) charged it with a charger I had used before but not often (Micro USB I think 2W + Micro-USBC adapter). Has anyone had a USB failure like this and resolved it? I use Android Auto in the car on my commute and it's a problem not having it working.

Thanks!
[Upgrading, Modifying and Unlocking] linusuli:
Hello. i found three types of recovery. one with Chinese letters, another with nothing and the one that comes out after "fastboot reboot fastboot" that asks me where I want to start: recovery, fastboot or system boot. the only way to boot directly to fastboot is "fastboot reboot bootloader" and in this case it does not find the "system" partition, i can burn the "super" partition but after "fastboot reboot" it only starts in "fastboot" mode.:cry:
[Upgrading, Modifying and Unlocking] kkm6761:
For 500 I'd get iPhone mini. iPhone mini sells for 200 too much for me to buy it. I too would like cubot to make a more upscale/simple style mini phone, for slightly more money. but not too much.

the teaser was posted on cubot website in community section.
[Upgrading, Modifying and Unlocking] kkm6761:
I'd say lineage os 18 or 19.

does usb connect to pc and data work? are you sure the cable is not an issue? try with another cable on pc. probably the car fries data wires of cable (don't know if possible and how).
[Upgrading, Modifying and Unlocking] ylavi:
No, as I said it doesn't connect to a computer either and that was tested with another cable as well. I just checked both cables with another phone (one in the car, the other on the computer) and in both cases the phone was detected. So the issue is with the phone. The question remains: is there any possibility that it's just a software issue...?
[Upgrading, Modifying and Unlocking] Lukas+:
No, I'll never buy an Iphone, but I understand what you say. If I can, or If I could, I'll pay a bit more for a much powerfull mini 2, or 3, because 2 has been better of what I thought. So said, if I can, or if I could, I'll give Cubot a try also for a more expansive device: this was what I wanted to say.

Design, materials, ruggedness, software, hardware, I think they worked very well on KKM2, and I think that if there were written, I don't know, Samsung, or I phone, or Oneplus, instead of Cubot, there where a lot more thought the streets.

More than this, it's a phone you can write a message running, always new, and when I finished a call, I take it with thumb and index and I put in pocket making it turning on itself.

At the same time, with telegram, whatsup, 50 internet pages on browser, heavy PDF opened (ancient books, large manuals), Xgimp (when it works!), Android Open Office with a huge mass of .odt documents opened and usually some other app opened it's smooth and secure.

I also have Nova launcher pro and My gestures working.

I've not had the same stability from more celebrated devices.

So I think that if Cubot should try to release a premium compact device, compatibly with my resources, obviously, I'll buy it.
[Upgrading, Modifying and Unlocking] x53:
@ylavi: Does the cubot flash tool recognise your phone? To answer you first question: Currently I'm satisfied with Andy Yans LineageOS 18.x running build lineage-18.1-20220217-UNOFFICIAL-treble_a64_bvS.img.xz. But without an working USB port my answer for you is pointless.
[Upgrading, Modifying and Unlocking] Lukas+:
At page 18 or 19, or 17, there's the complete software I decided for, a Corvus OS and everything about Magisk, because with super su I've not had time to do what I wanted to try.

I suffer a Bluetooth eco when speaking at phone in car, I ear the other person and me too.

Also my... in english... the two thinks you put on your ears for listening music, for example, and you plug it via USB... well, it doesn't work more on my phone. The system doesn't recognize it even if I can use its button to stop and play the music.

Everything else is the same, or better.

I tried also a Leo's custom ROM (page 16?), and It's good.

Everytwo the ROM I used (and use) I found it here, in this forum, by other guys.

If I'm in you, for what I know, I'll sync my datas via Wi-Fi with PC (for not losing them) and then I'll format. But... I'm not there... you only can decide the better.
[Upgrading, Modifying and Unlocking] ylavi:
@x53 - Thanks, haven't checked the flash tool yet but I don't see much reason to be optimistic. But it has occurred to me that I have dropped the phone a few times recently so maybe one of those falls broke something. I'm hoping that maybe it's just that the ribbon between the main board and the USB board popped out partially.

@Lukas+ - Thanks for your answer. Your English was good enough to understand.
[Upgrading, Modifying and Unlocking] Lukas+:
That's an obvious question, but however have you searched in settings, in USB connections, where you have, you know, charge only, pictures, files, also in the form of Mtp, Ftp... that thinks? Certainly you did it, but, who knows...
[Upgrading, Modifying and Unlocking] linusuli:
Well, I've already found fatsbootd, I've already found system and I've been able to flash it ... but it still doesn't start, it starts fastboot ...:unsure:
[Upgrading, Modifying and Unlocking] x53:
@Lukas+: With which ROM do you have Bluetooth echo problems? Stock rom shouldn't have eco problems. With LineageOS 18.x I have had echo problems, too. But I solved it. Maybe editing audio_policy_configuration.xml and audio_policy_configuration_bluetooth_legacy_hal.xml in /vendor/etc is the same solution for other roms?
[Upgrading, Modifying and Unlocking] Lukas+:
16.8 Avalon Beta Official (Corvus Os).

I know it's not the only.

I don't know, I'm sure you're write, but here everything I edit goes away after a reboot.

Maybe I should work on the firmware alone and then flash it in the phone, it's that I'm not used to do this because first of Android 10 out of the box firmwares (with dynamic partitions) I was able to change everything on the smartphone exactly after, after a reboot.

I'll save you're post and maybe I'll try but, well, not tomorrow or Thursday...

However, sincerely, there's no ROM in this forum that is not better of Android 10 stock, and really there's a street for every way.

Leo's if you don't want Google services more, Corvus if you want a very very nice customization in a smooth system, and so on.

But, for editing, I don't say nothing I've not tried in the same... everything... because... for example... ADB shell... works? Yes, but after a reboot that's what it was. I confess you I'm also a bit bored because, for me, I say what I like and what I think a system should be, I should download and compile from source code a late Android pie, as it was on KKM1, so I'll have the old really writable non dynamic partitions, and then install the GSI I prefer, but I'll need a new PC for doing this and, you know, I started with HTC Touch in 2008, if I remember, and in 2022 I must loose the warranty 'cause I would decide the fonts, I say the fonts, of the operative system of my device. Eh eh eh eh: it's possible in windows '98.

I'm saying that I'll go from the original software even if Bluetooth stays there... and more: It's only for the community, with the little or nothing I can give, that I buy Android, Android stock is ridicolous, we're in 2022 and there's not a really efficient and costumizable contex menu. But there's scoped storage! I'll give you Bluetooth and also Wi-Fi, but put away that... from me. So, if it's possible to solve this echo problem: ok, great, compliments to who knows. But, for me, even if it's not possible... I'll listen also my voice... so I'm sure I'm not wrong!
[Upgrading, Modifying and Unlocking] x53:
What's the highest fps for recorded videos using stock rom? Can somebody with stock rom have a look please, e.g. using mediainfo or another tool? I tried with lineageos different camera apps but all record with 14,8fps. I haven't found settings to change this. Is there a technical reason? Why not 25 (PAL) or 29,97 (NTSC)? Another question is the support for the Camera2 API, e.g. for taking RAW images. LineageOS says KKM2 doesn't support it (persist.vendor.camera.HAL3.enabled = 0). Could here someone have a look please too, e.g. use Camera2 API Probe. Maybe there is a way to enable it using MTK engeneer mode (dial *#*#3646633#*#*) ?