Installing Custom ROM on Cubot KingKong Mini
- Thread starter moctir
- Start date
I also tried installing TWRP with
LeOS vndklite a64 bvs
but with the same android 10 stock result.
Only it's author (of LeOS) says it's because from android 12 .xml files are compressed in a way old TWRP (3.4.0) can't process. So, at the end, it's a problem over another. It's not out a 3.5.0 TWRP for KKM2 (good for dynamic partitions) yet and there's a new Android 12 problem related. It's not easy staying without a TWRP working.
Because that guide is not complete. It makes you do a lot of dirties flashing. It's better (supposed we're in fastboot with boatloader unlocked and flashing too):Im using stock rom, dont know about a lOS for the kkm2 version.
I was triying this:
Rooting Cubot KingKong Mini 2 | Deadbadger
Jakub Kaderka personal webpage, electronic hacking, projects,etc.deadbadger.cz
But cannot use this:
fastboot flash system YOUR_SYSTEM_IMAGE.img
(where put the correct image file name for lOS17)
The reason, it says the system partition does not exist.
fastboot -w
fastboot reboot fastboot
fastboot erase system
fastboot flash system system.img
fastboot reboot
Every data will be lost, you restart the system as new. I prefer also not having the external memory formatted as internal when I do this, but maybe it's not a problem. If this commands doesn't work I'll try with another Rom.
fastboot -w is only needed if you don't use factory reset/data wipe from recovery and not needed if you upgrade a rom to a new version and you want to keep your userdata.
But it will also wipe the internal media card! Otherwise just use fastboot erase data if you need to wipe data but not the entire internal media card.
You can flash my lk.img from above with fastboot flash lk lk.img or with spflashtool. (only once needed)
anyone knows how to replace the boot image on KKM2 ?
there's logo-verified.bin in default rom files ..
would be also nice to replace the colorful "charging" screen when phone is switched off
p.s. successfully loaded the logo-verified.bin in editor from here :
logo editor
edited and flashbed back with
fastboot flash logo logo.bin
Sending 'logo' (873 KB) OKAY [ 0.046s]
Writing 'logo' OKAY [ 0.024s]
battery animation is in the same file.
Anyone managed to remove 5sec delay with open bootloader?
The orange state is easy to remove, but delay remains ..
there's logo-verified.bin in default rom files ..
would be also nice to replace the colorful "charging" screen when phone is switched off
p.s. successfully loaded the logo-verified.bin in editor from here :
logo editor
edited and flashbed back with
fastboot flash logo logo.bin
Sending 'logo' (873 KB) OKAY [ 0.046s]
Writing 'logo' OKAY [ 0.024s]
battery animation is in the same file.
Anyone managed to remove 5sec delay with open bootloader?
The orange state is easy to remove, but delay remains ..
Last edited:
When offline charging the KKM2 screen backlight is permanet on! Is this right? Means I shutdown the phone and put the charger on. After that I get a charging battery symbol for at least 2 minutes, I guess. After that a simple white symbol for the charging process is shown. Seconds later this simple charging animation disappers but the backlight is still on. The whole night the display shines! Thats annoying! When pressing the power button the simple charging animation appears and disappears but the backlight remains. So the only solution is to charge the phone powered on.
Btw, at first I didn't get the logo editor to work. With Windows 10 it won't even start and Windows 7 throwed an .net error. The solution was to toggle "Unblock" within the file properties (general tab) of Ionic.Zip.dll, logo.exe, LogoBuilder.exe and Tips.dll.
Btw, at first I didn't get the logo editor to work. With Windows 10 it won't even start and Windows 7 throwed an .net error. The solution was to toggle "Unblock" within the file properties (general tab) of Ionic.Zip.dll, logo.exe, LogoBuilder.exe and Tips.dll.
Hi everybody !
I did something wrong with my KKM2 :
- flash boot logo with a photo I would like instead of the Cubot logo,
- got pbs with rebooting
- flash boot.img then and recovery.img, thinking that it could resolved the pb.
BUT, now phone stuck on black screen with blue led appearing sometimes when on charge.
Impossible to get to recovery or fastboot even with power+Vol-/+
Hope I didn't f*** too much, please help.
I did something wrong with my KKM2 :
- flash boot logo with a photo I would like instead of the Cubot logo,
- got pbs with rebooting
- flash boot.img then and recovery.img, thinking that it could resolved the pb.
BUT, now phone stuck on black screen with blue led appearing sometimes when on charge.
Impossible to get to recovery or fastboot even with power+Vol-/+
Hope I didn't f*** too much, please help.
if you can't get into fastboot, you will probably have to use SPflash and reinstall stock firmware. will delete data.
another question for anyone that could answer: resurrection remix just drains me battery, I have found no way around. it also is the only rom that I have found working on KKM (corvus os does not boot without disabling or setting SELinux to permissive). how can I hide/delete lockscreen clock/date on lineage os with adb commands without root? i tried with magisk, but the xposed framework does not install correctly, and virtual xposed just just not work as it should.
another question for anyone that could answer: resurrection remix just drains me battery, I have found no way around. it also is the only rom that I have found working on KKM (corvus os does not boot without disabling or setting SELinux to permissive). how can I hide/delete lockscreen clock/date on lineage os with adb commands without root? i tried with magisk, but the xposed framework does not install correctly, and virtual xposed just just not work as it should.
use spflashtool to flash the original logo.
untick the rest. you don't have reinstall the whole stock firmware for only the logo
The MTK EngineerMode in stock rom is very helpful (dial *#*#3646633#*#*). I know there is a similar but downgraded alternative within lineageos (dial *#*#4636#*#*). For that reason I tried to integrate it into lineageos, unfortunatly unsuccessful. I did copy the EngineerMode.apk into the folder /system/priv-app/EngineerMode and set permissions like the other system apps. But dialing *#*#3646633#*#* didn't work, not even after reboot. Maybe there is more to copy, not only this system apk. Any suggestions or is my project doomed to fail? 
In my opinion the best thing of stock EngineerMode is to set a certain cell id. Never saw that at other phones e.g. samsung. Or is a similar app to install out there?
In my opinion the best thing of stock EngineerMode is to set a certain cell id. Never saw that at other phones e.g. samsung. Or is a similar app to install out there?Sorry, no experience on KKM1 but on KKM2 it is very smooth
(LeOS)Today I tried LineageOS 19.0 but I didn't get system rw access. adb root & adb disable-verity didn't work out like it does with LineageOS 18.1. There is simply no system partition to mount. So mount -o rw,remount /system doesn't work (error: /system not in /proc/mounts). df does show no overlay system partition either. Any suggestions for getting rw access to system partition running LineageOS 19.0?
Thanks. Same old issues of kkm2 apply? (BT echo in calls etc.)Sorry, no experience on KKM1 but on KKM2 it is very smooth
Hi. Actually iḿ using the KKM2 with the latest A10 Stock. Wich version of LeOS have u installed? Does calling work with VoLTE and without annoyning echos while speaking? Is the Wifi connecting now stable? RegardsSorry, no experience on KKM1 but on KKM2 it is very smooth
kowalskie
Thanks for your quick answer. Could you test volte related test-call for me? Stays the LTE/4G or VoLTE Symbol on top of the screen while having a call?
Similar threads
Top Liked Posts
-
1
-
2Overview and specifications (only partial for now) of the new Cubot Pocket.
Height : 119 mm. :-(
Where is the impovement compared to the KKM / KKM2 ?
The latest model of 2022 (Pocket) has the same form factor and the same screen as a rugged phone of 2019 (KKM) !
Come on, Cubot ! The viewable screen you use measures 90.9 * 45.4 mm (my calculations. I don't own a KKM / KKM2). With the same screen, you can create a phone that would be 100 * 52 mm (screen to body ratio : 79 %. Nothing exceptional).1 -
7UPDATE 2021
The original post was for the first King Kong Mini, for instructions for the King Kong Mini 2 go to page 9 in this thread:
https://forum.xda-developers.com/t/...-on-cubot-kingkong-mini.4050815/post-84445303
======================
The Cubot King Kong Mini was released in Q4 2019. It is one of the smallest Android phones on the market with a 4" screen. Like many cheap Mediatek devices, one cannot be sure of how "safe" or "secure" these devices are, so the security/privacy conscious may want to consider installing a custom ROM. Here are the instructions for installing Android AOSP on the Cubot King Kong Mini. Note: I am not responsible for any bricked devices.
Download the Stock Rom from here and SP Flash Tool just in case you need to reinstall Stock. Download a system image, note you need to use an A/B arm32 image with 64 bindings. For example AOSP 9 is here.
This process probably can be done with SP Flash Tool but I wasn't able to manage it due to the disable-verification flag required.
Unzip the stock ROM and reboot the device to bootloader, connect via USB and unlock via:
Code:sudo fastboot flashing unlock
Note this will erase all data. Then on your computer navigate to the folder with the unzipped ROM (for me was NA_mt6761p_d936p_9101cmp_chuanqi_cc_256gbitp24d3_p_lte_3m-fdd-cs_mul_20191121-210020_songlixin_PC) and type
Code:fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
If you do not do this it seems to work without it but then it will bootloop when you try to switch it on. From here on it's standard.
Code:fastboot flash boot boot.img fastboot flash recovery recovery.img
Unzip the .xz image file you wish to use and type:
where SYSTEM is the name of whatever image downloaded.Code:fastboot flash system SYSTEM.img
Root
For root install magisk manager and you have to patch the recovery to get root (not just boot as flashing boot alone doesn't give you root). So in magisk get it to patch you boot and recovery images and then put those on your computer, go to bootloader and use:
Code:fastboot flash boot magisk_patched_boot.img fastboot flash recovery magisk_patched_recovery.img
You can read more about magisk from recovery here.
To get root then you need to reboot to recovery, hold power button + volume up and select Recovery. This will appear to boot as normal but you will have root when you do it this way and not when you boot normally. Unfortunately I do not have reception when I do this but do have root, other users have this problem but I have not found a solution.
Note that I thought I bricked my phone a few times before getting this as nothing would happen after a failed boot and I couldn't switch it on, however what happens is you can't do anything until the battery has almost completely discharged, then when you hit the power button you'll get the no battery sign and when you plug in you can get to Recovery again. This is quite annoying if you've charged it quite high as you'll have to wait a long time to discharge and be tapping on the power button a lot!!
What doesn't work
Battery usage doesn't work, this can probably be fixed following this guide. If I get time I will attempt this.
Other things to note, there is no TWRP yet so I don't have decent recovery options, this also makes it harder to use certain ROMS as you can't flash things like gapps if you install a ROM without it.
The battery life is definitely worse using AOSP GSI than stock, maybe that vendor overlay would help with that though.
I hope that helps others.5Hi,
I have got the Cubot King Kong Mini 2 and I can confirm that exchanging the system to LOS17.1 is possible too.
I did nearly the same as mekkadisu did (#39) for KKM1, but had to do a
before flashing the system.Code:fastboot reboot fastboot
This is what I did:
1.) Flash the newer OS for King Kong Mini 2 from King Kong's site using the instructions and flash tool already there (quoted from #39).
2.) Enable developer options by tapping the build number in Settings -> About Phone 7 times, Enable USB Debugging and Allow Bootloader Unlock from developer options (quoted from #39).
3.) (quoted from #39)Code:adb reboot bootloader
4.) once in bootloader mode (quoted from #39)Code:fastboot flashing unlock
5.) Then confirm unlock on the phone (quoted from #39)
6.) Note the locaton of the vbmeta.img, boot.img and recovery.img files from the stock ROM (quoted from #39)
Code:fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img fastboot flash boot boot.img fastboot flash recovery recovery.img
7.) Now I did not flash the system directly, but rebooted to fastboot
Code:fastboot reboot fastboot
8.) After device is in real fastboot mode (the screen is different to that of bootloader fastboot mode)Code:fastboot flash system SYSTEM.img
I used the lineage-17.1-20210114-UNOFFICIAL-treble_a64_bvS.img.xz
Why did I do the "fastboot reboot fastboot":
without rebooting to fastboot but direclty flashing the system, I got this error:
Code:fastboot flash system lineage-17.1-20210114-UNOFFICIAL-treble_a64_bvS.img Sending sparse 'system' 1/10 (131068 KB) OKAY [ 4.898s] Writing 'system' FAILED (remote: 'This partition doesn't exist') fastboot: error: Command failed
After rebooting to fastboot it worked:
Code:fastboot flash system lineage-17.1-20210114-UNOFFICIAL-treble_a64_bvS.img Resizing 'system' OKAY [ 0.004s] Sending sparse 'system' 1/5 (262140 KB) OKAY [ 19.088s] Writing 'system' OKAY [ 4.061s] Sending sparse 'system' 2/5 (262140 KB) OKAY [ 19.596s] Writing 'system' OKAY [ 4.036s] Sending sparse 'system' 3/5 (262140 KB) OKAY [ 19.943s] Writing 'system' OKAY [ 4.048s] Sending sparse 'system' 4/5 (262140 KB) OKAY [ 20.290s] Writing 'system' OKAY [ 3.721s] Sending sparse 'system' 5/5 (177556 KB) OKAY [ 13.090s] Writing 'system' OKAY [ 2.879s] Finished. Total time: 110.773s
I'm not an expert in flashing mobile devices, so I don't know, why I had to to that. I would be very happy if an expert could reply and maybe give me a hint as to what the problem was.3With 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.3anyone knows how to replace the boot image on KKM2 ?
there's logo-verified.bin in default rom files ..
would be also nice to replace the colorful "charging" screen when phone is switched off
p.s. successfully loaded the logo-verified.bin in editor from here :
logo editor
edited and flashbed back with
fastboot flash logo logo.bin
Sending 'logo' (873 KB) OKAY [ 0.046s]
Writing 'logo' OKAY [ 0.024s]
battery animation is in the same file.
Anyone managed to remove 5sec delay with open bootloader?
The orange state is easy to remove, but delay remains ..
