yashsingh1/xdaforums huggingface dataset:
[Upgrading, Modifying and Unlocking] Vilkoko:
Ouch !

I didn't see your reply, sorry. I made a factory reset in Recovery mode. I need to reinstall all apps, Silence included to run tests.

About Gmail, it wasn't Google apps I was looking for : just the web page to check my mail. I'll try that again soon.

Thanks for your help

Edit1: still the same : can send sms, can't receive. Can browse web, can't load sign in gmail page

I didn't check if I could receive SMS with the Stock Rom, I installed LeOS straight out of the box. Maybe there is a problem with this Cubot device : that's why I wanted to reinstall the Stock to run tests.

Edit 2: I made a factory reset again, through Parameters. The phone can't boot because it's stuck in the configuration wizard. It won't pass the Localization screen when I press "next", goes back to Internet settings. If I do it again a message pops up to explain the Wizard has crashed and Wizard start all over from the beginning (with Snoopy). Stuck in a loop here.

Considering this, can my Custom rom be corrupted somehow?

Edit 3: Went to recovery via Fastboot, factory reset in recovery mode again. Phone boots but back to "Edit 1" state
[Upgrading, Modifying and Unlocking] birdibird:
Which LeOS version are you using exactly? (month etc)
[Upgrading, Modifying and Unlocking] Vilkoko:
I took LeOS-20 of january as harvey186 says in devices list that KKM2 "LeOS-20-VNDKLITE-a64_bvN is working". This is the version I used.
[Upgrading, Modifying and Unlocking] birdibird:
Ok, try the LeOS-20-VNDK-a64_bvN version.

That one is running on my kkm2
[Upgrading, Modifying and Unlocking] Vilkoko:
Ok I'll do that and report to you tomorrow. January version too?
[Upgrading, Modifying and Unlocking] Vilkoko:
I flashed with the rom LeOS-20-VNDK-a64-bvN.img

Then

-Enter recovery

-Wipe data/factory reset. It says "E: : fota installation aborted" and "E: : No such file or directory"

-Reboot system now

Stuck in configuration loop again : can't pass the Localization screen, wizard crashes and starts again.
[Upgrading, Modifying and Unlocking] birdibird:
did you do oem unlocking, usb debugging in dev options, flashing unlock, vbmeta in bootloader and you flashed system in fastbootd?

otherwise: flash the latest cubot rom and start over
[Upgrading, Modifying and Unlocking] Vilkoko:
Yes I did it that way. Problem not solved.

I tried with a friend's sim card from another network provider, the third one. It worked ! I could send and receive sms.

Problem comes from my provider, not from KKM2. Thanks for your help
[Upgrading, Modifying and Unlocking] birdibird:
Happy to hear you got it pinned down!
[Upgrading, Modifying and Unlocking] birdibird:
Does anyone speak Russian and can download TWRP 3.5.1 for the Kingkong Mini 2 here: https://4pda.to/forum/index.php?showtopic=966952&st=3380#entry112557860
[Upgrading, Modifying and Unlocking] badcodelab:
you don't need to speak russian for this

to download any file from 4pda you just have to be logged in (create an account)

crap, i forgot about captcha in russian
[Upgrading, Modifying and Unlocking] birdibird:
Yes, the captcha in handwritten cyrillic is a bit hard :-)

thanks for the file!
[Upgrading, Modifying and Unlocking] badcodelab:
in case this helps i can give you a hint - it's always 4 digit number like pin code but spelled in a way "one thousand two hundred twenty four"

no worries, ask in dm next time
[Upgrading, Modifying and Unlocking] birdibird:
Yes, I figured, but couldn't read it ;-)
[Upgrading, Modifying and Unlocking] birdibird:
EDIT: This vendor is from an older version of the Cubot rom. I have v11 installed and wifi is not working.

I am trying to make a new patched vendor myself, as my 1st version lost sim card access.

---

This is a patched vendor.img for the Cubot kkm2, from here originally posted on 4pda

With this vendor you can use your kkm2 unencrypted, so you can access your data from twrp 3.5.1 even when your phone doesn't start anymore.

(downside is of course that anyone else can too).

unpack and flash in fastbootd with fastboot flash vendor vendor_NoCrypt.img

then reformat /data

(you will loose your data, so backup first!)

Thanks @badcodelab
[Upgrading, Modifying and Unlocking] Vilkoko:
A hint for those stuck in the LeOS Configuration wizard loop at the begining : don't change langage when asked in the first screen (just after Snoopy flag), even if it detected your country through the sim card. You'll be able to change it afterwards.

I left "English", can't explain why, but it worked for me.
[Upgrading, Modifying and Unlocking] Vilkoko:
I can't get the Notification dot on app icon with Silence or Simple sms, although I activated it in KKM2 parameters and application parameters too. Is it possible to get it ?
[Upgrading, Modifying and Unlocking] birdibird:
I never was stuck here. Which LeOS version are you using?
[Upgrading, Modifying and Unlocking] Vilkoko:
Hi. I use january version of LeOS 20 (tried both vnd and vndlite versions)
[Upgrading, Modifying and Unlocking] birdibird:
The Jan version had some issues.

Try the feb one.

And, are you on the newest Cubot rom?
[Upgrading, Modifying and Unlocking] Alexbrz2:
Hi all! I have recently purchased a KKM2 as a gps tracker & bluetooth-forwarding device for my bbq equipment, and now thinking to upgrade it to LOs.

Before i start off, i am on the most recent original OS version. Is this procedure still the correct way to go? https://xdaforums.com/t/installing-custom-rom-on-cubot-kingkong-mini.4050815/post-84445303

With the use of LeOS-20-VNDK-a64-bvN.img

Or is there something that has changed or i have missed?
[Upgrading, Modifying and Unlocking] moonraver:
Found KKM3 bug in latest V08 firmware:

NFC turns itself on after every phone restart even in SAFE mode.

Cubot support says that they don't have this bug.

Does anybody have this?
[Upgrading, Modifying and Unlocking] badcodelab:
not for me

btw any news on installing gsi on kkm3?
[Upgrading, Modifying and Unlocking] moonraver:
that's interesting, I have disabled a lot of google apps, maybe that could do that. Anyway, I don' t want to make a reset for now, will wait till next update.

No news about gsi flashing, I check 4pda forum everyday about KKM3 and they have many problems with that. Still no clear procedure how to flash.
[Upgrading, Modifying and Unlocking] badcodelab:
guys there shared new (3rd) modded stock (v08) rom with some tuned features https://4pda.to/forum/index.php?showtopic=1056175&view=findpost&p=121550784

also same user published his dump of evolute gsi which can be flashed via spft

Evolute.rar

drive.google.com

although it has some bugs he claims that it possible to flash any gsi over this dump via fastbootd
[Upgrading, Modifying and Unlocking] moonraver:
I read it yesterday somehow............with web translator - it is a bit difficult to understand it this way.

do you mean to flash evolute gsi via spft and then any GSI via fastboot?
[Upgrading, Modifying and Unlocking] badcodelab:
seems like this, i don't know how he managed to install evolute gsi to his kkm3 in the first place

but this guy says after installing his dump of evolute gsi using spft it should be possible to flash other gsi builds using "ordinary" process in fastbootd mode

he also mentioned that he tried to flash a couple gsi roms but issue with a lock screen persisted
[Upgrading, Modifying and Unlocking] moonraver:
About that NFC problem............can you try this for me? I want to be sure if I need to make a hard reset of my KKM3. I have found something new - that bug occurs only when SIM card is inserted in the device. When there is no SIM card, NFC doesn't turn on by itself.

So the bug is present when:

KKM3 device is on and I remove SIM card. Then I insert SIM card (connecting 2G, 3G or 4G type of network) and NFC turns itself on immediately

KKM3 device has SIM card inserted and I reboot the device. It reboots and after reboot when the device detects that SIM card is inserted (connecting 2G, 3G or 4G type of network), turns NFC on immediately

Does your NFC turn on by itself in any of these 2 cases?

Thanx
[Upgrading, Modifying and Unlocking] badcodelab:
i confirm, #1 is reproducible, kkm3 enables nfc after inserting sim card

#2 is still negative
[Upgrading, Modifying and Unlocking] v.a.riabov:
Someone solved the problem with 15 fps shooting video on the main camera on KKM2?
[Upgrading, Modifying and Unlocking] moonraver:
Try Protake app if it helps. This problem has KKM2 and KKM2 Pro. That was why I bought KKM3 but it has also this bug if ISO is higher than 400 (=15 fps). Otherwise it shoots 30 FPS. So I use Protake - it indicates some frame drops but for me it is still has the best video results.

I contacted Cubot support about year ago with this KKM2 and KKM2 Pro "low video FPS bug" but the support was VERY HARD TO UNDERSTAND ME. So I gave up. It seemed to me that they did NOT want to solve this maybe because the phone is low-cost.

Now the support is maybe a bit better - you will get the answer that developers will fix bugs in next update....... but that is all.

BTW: Custom ROMs did't also help to solve those 15 fps. I'm really sure that it is a matter of CUBOT camera drivers because the sensors in all KKMs are able to shoot 30 FPS.
[Upgrading, Modifying and Unlocking] v.a.riabov:
Thx! I hope support have solve the problem somehow!
[Upgrading, Modifying and Unlocking] veloc_h:
I flashed CUBOT_KINGKONG MINI2_A061C_V11_20220817 on my kingkong mini (Version1).

Now the compass works (the kingkong mini is used only for bicycle navigation)!

However I get the message "tee key / google key" because I formatted the whole file structure (option automatic formatting) without backup (not the best thing to do...)

There is a workaround, but I would have to install magisk

https://xdaforums.com/t/discussion-magisk-the-age-of-zygisk.4393877/

"Installing Magisk for the first time REQUIRES a full data wipe" according to https://topjohnwu.github.io/Magisk/install.html, which I would like to avod.

in order to flash with magisk zygisk support

https://xdaforums.com/t/not-verify.3870242/post-87713751

or to edit the build.prop

How to remove "not verify" red text on a mediatek android phone

This error as seen in the screenshot below is usually as a result of formatting certain partitions on a mediatek android phone while flashing firmware i.e flashing firmware using format all + download

www.hovatek.com

The other possibility would be to install e.g. LeOS GSI or Caos Treble GSI and install Osmand+ using f-droid (minimum google with LeOS). Does the compass work in LeOS or Caos?

It seems easy to flash a custom rom with the help of

fastboot flash LeOS according to

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

Wiki for LeOS users

gitlab.com

Which partitiions do I have to format before flashing LeOS?
[Upgrading, Modifying and Unlocking] x53:
Has anyone an idea how to increase earpiece volume? In comparison to other phones earpiece volume is way to low during calls, particular in noisy enviroments. I own two KKM2. With both i'm unsatisfied. Using stock rom or gsi rom doesn't matter because they all use audio_policy_configuaration*.xml in the vendor partition (hope I'm right). So I'm open to any suggestion, e.g. editing these audio-xml files (but where?) , changing earpiece physically with a louder one (ist there any?), hidden menus (*#*#???#*#*), whatever....
[Upgrading, Modifying and Unlocking] moonraver:
I was dealing with increasing volume of BACK speaker of all KKMs. I wasn't successful but I can give you a hint but you must be really careful and first read something about this. It is called Engineer mode:

MTK EngineerMode in stock rom of KKM3 - dial *#*#3646633#*#*

Find codes for KKM2, maybe it is the same as KKM3
[Upgrading, Modifying and Unlocking] x53:
Thanks for your reply. I already tried MTK EngineerMode. But I couldn't find anything related to earpiece volume. Had I missed something?
[Upgrading, Modifying and Unlocking] moonraver:
I have found something. Maybe this could help you:

https://xdaforums.com/t/guide-mtk-using-engineering-mode-to-increase-audio-output.2746861/

How to Increase Maximum Volume on Mediatek-Based Android Devices through Engineer Mode

Android devices often have varying levels of “maximum” volume output – even if you’re using the same exact headset between devices. This may not always be

appuals.com
[Upgrading, Modifying and Unlocking] x53:
Thanks, unfortunately it doesn't work and the KKM2 Engineering Mode does a little differ to other devices. So I was going to "Hardware Testing" -> Audio -> Volume -> Voice. IMHO here I found nothing to set earpiece gain a little louder.

Enclosed the whole list of items I could change:

- NB, WB, SWB

- Receiver, Receiver_SV, HAC, Headset, Headphone, Speaker, Speaker_SV, Headset(5-pole), Headset(5-pole+ANC),TTY,Lpbk_Handset,Lpbk_Headset,Lpbk_Handsfree, USB

- GSM (here is nothing to change)

- UL Gain: integer between 72 and 252

- Sideton Gain (Stf): 0 ... 240

- DL Gain: here you can define 7 steps from Index 0 to Index 6

I thought Receiver and UL Gain 252 does the trick, but no luck. In the second item I miss "Earpiece" in the toggle menu. However thanks a lot for trying.
[Upgrading, Modifying and Unlocking] moonraver:
A new device from Cubot is comming..........Kingkong Power

CUBOT FILE DOWNLOAD

Cubot Offical Website for Smartphones and Wearables. Simple and Trust, Cubot aims to be a credit worthy high-tech corporation in the world.

cubot.net

Seems like it is not "mini" but something with bigger battery. Device with similar name "Cubot Power" has been released in 2018 with 6000 mAh battery.
[Upgrading, Modifying and Unlocking] birdibird:
I once formatted a mtk device without backing up nvdata and was able to restore serial and imei with a MTK tool.

What sometimes also works is to flash back the original rom, then backup nvdata (eg with twrp) and then reflash the new rom and restore nvdata

You don´t have to format anything before flashing LeOS. Just follow the instructions on the LeOS wiki.

For Magisk you also do not have to wipe anything. Just patch the boot.img in the Magisk, flash it then with SPflashtool or fastboot (in bootloader) or twrp.

Compass works in LeOS
[Upgrading, Modifying and Unlocking] ghoster76:
Hi folks, has anyone here rooted the King Kong Mini 3 yet?
[Upgrading, Modifying and Unlocking] badcodelab:
@ghoster76 check this link out

Cubot KingKong mini 3 - Обсуждение - 4PDA

Cubot KingKong mini 3 - Обсуждение, Смартфон, 4.5"

4pda.to

you can use google translate to read the post
[Upgrading, Modifying and Unlocking] moonraver:
yesterday I flashed their v08 MOD4 ROM. It has Magisk onboard so I uninstalled most of Google suff. The rom is smooth. There are some small changes in settings and UI tweaks. I installed Bromite webview,new AGPS provider. Finally the Battery usage is present. It has a better opportunity do degoogle phone when LeOS can not be still flashed.

I would like to try a raw support but their link to magisk raw module called "test.apk" is not available - link is dead. Don't you have that file?

BTW: Have you tried that Evolute GSI?
[Upgrading, Modifying and Unlocking] badcodelab:
the link isn't dead, at 4pda you have to be logged in to be able to download attached files

please tell us if you find gcam working with this module

this guy somehow managed to install evolute gsi over his modded rom and shared the dump with it

Cubot KingKong mini 3 - Обсуждение - 4PDA

Cubot KingKong mini 3 - Обсуждение, Смартфон, 4.5"

4pda.to
[Upgrading, Modifying and Unlocking] birdibird:
Cool. Did you manage to flash LeOS arm64 over it?
[Upgrading, Modifying and Unlocking] moonraver:
I strongly don't think that gcam will work because there is "Camera GO" app included in this ROM. If it works they will not add this type of camera app. But I will give it a try and test some gcam apps.
[Upgrading, Modifying and Unlocking] moonraver:
No I didn't but I tried to flash the latest LeOS GSIs based on A12 and A13. Result is still the same - bootloop.
[Upgrading, Modifying and Unlocking] birdibird:
I hope you flashed the arm64 version and not the a64 version?

(we are talking about the kkm3 with that custom rom and then LeOS on top of it and then factory reset, just to double check?)
[Upgrading, Modifying and Unlocking] moonraver:
yes arm64

stock rom flashed with spflash tool and afterwards LeOS GSIs.

BTW: In addition, I have tried DSU Loader in Stock Rom with GMS but it gave me a "red state" during boot logo and turns off. I am still wondering why DSU Loader is not working at all.
[Upgrading, Modifying and Unlocking] moonraver:
Good news about KKM3 camera!

I have tried Magisk RAW module (thanx to badcodelab and 4pda guys) a while ago and differences between RAW (DNG) and JPEG (with 100% quality) are really markable.

I used HedgeCam2 2.15 with DNG Raw format and now I will try raw with OpenCamera.
[Upgrading, Modifying and Unlocking] birdibird:
Forget DSU.

Sorry, I thought you had flashed the custom rom of 4pda above, and LeOS on top of that. Give it a try.
[Upgrading, Modifying and Unlocking] badcodelab:
really? could you please share some samples?

4pda guys said raw is pretty useless at kkm3 and you can't get a lot from it

perhaps that's why they didn't include full gcam
[Upgrading, Modifying and Unlocking] moonraver:
And they were true, there are no differences between RAW JPG and JPG,they have the same size. But it starts to be visible when you choose DNG Raw in OpenCamera or Hedgecam2. If you know something about photography you will know what I am talking about next.

These two pictures were captured in more dynamic light conditions (imagine what would it look like in good light conditions!!), with tripod, timer 2 sec., ISO 12, F1/8, shutter speed 1/20, focused almost on the center. DNG file is without any post-processing. Best results in details can be seen in 100% zoom = 1:1

DNG has to be zipped because extension is not supported to attach here.
[Upgrading, Modifying and Unlocking] moonraver:
HOW TO FLASH "EvolutionX" ROM TO KKM3 PHONE

Join the Evolution X Discord Server!

This is the Evolution X custom ROM Discord server. We provide support and assistance here for all Evolution X users. | 26962 members

evolution-x.org

- Pixel UI, Android 13, a

- lot of customizations

- lot of Google stuff

1. If you have Stock Rom, just do a factory reset. Otherwise flash official STOCK Rom with SPFlash tools from CUBOT

2. Turn on the phone after flashing,skip first steps

- enable developer options

- enable OEM unlocking

- enable USB debugging

- connect phone, confirm always trust connection

3. open command prompt in WIN:

- adb devices

- adb reboot bootloader

- fastboot flashing unlock, Volume UP confirms

(prepare "vbmeta.img" file from the stock ROM)

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

4. SPFlash tool

- download latest SPFlash tools (contains "download only" mode):

- download EvolutionX "super" image posted on 4PDA (security updates from February 2023, arm64, bvN):

Evolute.rar

drive.google.com

- load scatter file from Stock Rom, deselect all images

- insert ONLY "super" img file from EvolutionX ROM

- make sure that "DOWNLOAD ONLY" mode is selected!!!

- press Download and connect phone, wait till the end of flashing

- disconnect phone

5. If anybody wants to have updated EvolutionX ROM, just download image you want:

Releases · ponces/treble_build_evo

Script and patches for building PHH-Treble Evolution X - ponces/treble_build_evo

github.com

- fastboot reboot fastboot

- fastboot flash system (ROM_name.img)

Wipe cache, Wipe data/factory reset

BUGS/EXPERIENCES (February ver. 7.6.1 bvN and May ver. 7.9 vndklite)

- max brightness is about 1/3 lower than in STOCK ROM

- lineage OS Camera ver.13 onboard, focusing in good light conditions is a bit faster (in low light is still problematic), video has constantly 30 fps even in low light conditions!!! = big improvement, the "wave effect" during refocusing is still a present but not so visible, shots only 4.9 MP photos, no manual mode

- 2 GCam apps have been tested but they keep crashing

- both ROMs are a bit laggy compared to STOCK Rom

- orange state during boot is present (maybe lk or lk2 needs to be flashed with SPFlash tools)

- no problems with lockscreen

- audio wasn't tested

- 2G can be allowed (for using in SOS mode or somehow) but preferred network can be set only 3G or LTE

Thanx to guys from 4PDA and birdibird and badcodelab.
[Upgrading, Modifying and Unlocking] moonraver:
HOW TO FLASH MODDED STOCK ROM TO KKM3 PHONE

1. Flash official STOCK Rom with SPFlash tools from CUBOT ("firmware upgrade" only mode)

2. Turn on the phone after flashing, skip first steps

- enable developer options

- enable OEM unlocking

- enable USB debugging

- connect phone, confirm always trust connection

3. open command prompt in WIN:

- adb devices

- adb reboot bootloader

- fastboot flashing unlock, Volume UP confirms

- fastboot reboot fastboot, scroll to Power off

4. SPFlash tools (download latest from net with "download only" mode):

- load scatter file from STOCK rom, deselect all images

- download either MOD3 or MOD4 images:

CUBOT_KINGKONG_MINI_3_C031C_V08_20221206_MOD3.7z

drive.google.com

CUBOT_KINGKONG_MINI_3_C031C_V08_20221206_MOD4.7z

drive.google.com

- insert all images from MODDED ROM (images will be automaticaly included in selection for flashing)

- make sure that "DOWNLOAD ONLY" mode is selected!!!

- press Download and connect phone, wait till the end of flashing

- disconnect phone

5. VOL UP+POWER for a few seconds, release POWER = 1st. fastboot mode

- fastboot reboot recovery

- In Recovery mode select Wipe cache and Wipe data/factory reset

- reboot phone

Magisk is included. RAW Magisk module is in attachment. Do not forget to select DNG in camera apps to have a better quality pictures.

Advantages:

- no Orange states

- no other warnings during boot

- phone is also charging when it is turned OFF (KKM2 and KKM2Pro were not charging with custom ROMs)

BUG/HINT in MOD4:

- access to Engineer mode is NOT from dialer (*#*#3646633#*#*) but via settings/system/show systemUI Tuner/additional programs/engineer mode

- separated "notification volume" and "ring volume" is buggy - both levels are moving at the same time

- integration of Pixel sounds and sound picker is buggy - when you select from pixel sounds (ogg) and try to increase or decrease volume of ringtone then settings are freezing and need to be killed. This is not happening when you select your own MP3 ringtone. Changing location of ringtones didn't help. Probably it is a matter of OGG files.

- I de-bloted most of Google stuff and battery now shows 17 days of standby after 1st charging!!!

Thanx to guys from 4PDA and birdibird and badcodelab.
[Upgrading, Modifying and Unlocking] badcodelab:
thx, the difference is visible but what about focus speed?

sometimes in low light on stock rom camera can't focus at all, is it better with dng raw?

thank you for the manuals!

as i see you haven't managed to flash custom gsi with skipping flashing evolution dump, right?

i don't get how did that guy manage to install evolute in a first place?

also klud at 4pda mentioned some other bugs like

- locksreen doesn't work

- tws headphones get connected but sound keeps come out from the speaker

did you have these too?