Installing Custom ROM on Cubot KingKong Mini

[smartomato_reloaded]

I sold it. but as I remember, most of gsi does not work.
corvus official gsi worked well.
but before start, you better do factory reset from stock recovery.

Would you please share more details? So far trying the methods here for KKM3 mostly results in getting stuck on cubot's splash screen or bootloops.

 

[moonraver]

I sold it. but as I remember, most of gsi does not work.
corvus official gsi worked well.
but before start, you better do factory reset from stock recovery.

If I can ask...............why did you sell your KKM3 phone?

 

[Truelan]

Would you please share more details? So far trying the methods here for KKM3 mostly results in getting stuck on cubot's splash screen or bootloops.

fastboot flashing unlock
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot reboot fastboot
fastboot flash product product_gsi.img
fastboot flash system SYSTEM.img
fastboot -w

navigate to 'enter recovery' to enter recovery.
wipe cache
wipe data/factory reset
restart system

pruduct_gsi.img is attached in another post.
find yourself.
only CORVUS ROM WORKED.
I also failed A13. stuck in cubot logo.
I don't know about other A12 rom.

 

[Truelan]

If I can ask...............why did you sell your KKM3 phone?

first, Stock rom interface was not good.
Second, some app(and game) interface does not match well.
Third, tired using and trying gsi rom.

 

[badcodelab]

only CORVUS ROM WORKED

could you please specify the build name?
or share download link?

i tried almost the same steps except wiping data

 

[moonraver]

first, Stock rom interface was not good.
Second, some app(and game) interface does not match well.
Third, tired using and trying gsi rom.

The truth is that the screen has a problematic ratio and is 2 mm thinner than KKM/2/2Pro. This is something I am worried about, I am still waiting for my KKM3 til 4th of December. I can still cancel my purchase.
I don't play games at all. I mainly use Osmand for navigation and for mapping. Of coarse I hope that camera will be a bit better than KKM2 Pro to make better photos during mapping. Haven't you tried Osmand on KKM3? .
Ok so now what device do you use instead of KKM3?

 

[moonraver]

The truth is that the screen has a problematic ratio and is 2 mm thinner than KKM/2/2Pro. This is something I am worried about, I am still waiting for my KKM3 til 4th of December. I can still cancel my purchase.
I don't play games at all. I mainly use Osmand for navigation and for mapping. Of coarse I hope that camera will be a bit better than KKM2 Pro to make better photos during mapping. Haven't you tried Osmand on KKM3? .
Ok so now what device do you use instead of KKM3? Recommend some .............

 

[Truelan]

The truth is that the screen has a problematic ratio and is 2 mm thinner than KKM/2/2Pro. This is something I am worried about, I am still waiting for my KKM3 til 4th of December. I can still cancel my purchase.
I don't play games at all. I mainly use Osmand for navigation and for mapping. Of coarse I hope that camera will be a bit better than KKM2 Pro to make better photos during mapping. Haven't you tried Osmand on KKM3? .
Ok so now what device do you use instead of KKM3?

KKM2Pro.
performance was not good, but enough for normal usage. also better screen ratio.
and find some way to solve led issue.
in phh setting, turn on "disable hardware backlight".

PS. I does not use osmand. so dont know about that.
but, I tested some game.
genshin run in lowest setting. 20-30fps.
punishing gray raven at middle setting 40-60fps.

 

[Truelan]

could you please specify the build name?
or share download link?

i tried almost the same steps except wiping data

corvus s4.0 official.
search phh gsi wiki.

 

[smartomato_reloaded]

corvus s4.0 official.
search phh gsi wiki.

I'm sorry to bother, but I've been trying with those files yet still stuck at splash screen loop. Would you mind to share exact filename of the file you tried? Any missing details? Please understand my insistence, I've being trying to flash a GSI since day 16 (same day they released the stock rom).

 

[Truelan]

I'm sorry to bother, but I've been trying with those files yet still stuck at splash screen loop. Would you mind to share exact filename of the file you tried? Any missing details? Please understand my insistence, I've being trying to flash a GSI since day 16 (same day they released the stock rom).

I used arm64 bgn slim lite.
try fastboot -w in bootloader.
try fastboot -w in fastboot mode.
and in recovery, do factory reset/wipe data.
data partition does not compatible with new rom.
you should format and wipe all data.
I guess, flashing some other rom destroyed cache or data partition.
above two command also wipe but also flashing some partiton.

 

[smartomato_reloaded]

I used arm64 bgn slim lite.
try fastboot -w in bootloader.
try fastboot -w in fastboot mode.
and in recovery, do factory reset/wipe data.
data partition does not compatible with new rom.
you should format and wipe all data.
I guess, flashing some other rom destroyed cache or data partition.
above two command also wipe but also flashing some partiton.

Thanks for the attention. No luck so far tho, as soon as I flash any gsi I get the stuck at splash screen. May be my specific phone, I've seen reports of this on other treble compatible phones. I'm gonna keep trying and reporting here.

Ps. Weird things on my KKM3 I noticed so far and may help:

• Stock Rom comes with scatterfile for MT6768?
• Managed to get magisk on stock and weirdly it boots with vbmeta with just --disable-verity while not booting if I use --disable-verification
• After reflashing stock with spflashtool, the stock images have checksums different from the images I get by using the readback tool, magisk only worked after patching the boot.img from the readback process

 

[Truelan]

Thanks for the attention. No luck so far tho, as soon as I flash any gsi I get the stuck at splash screen. May be my specific phone, I've seen reports of this on other treble compatible phones. I'm gonna keep trying and reporting here.

Ps. Weird things on my KKM3 I noticed so far and may help:

• Stock Rom comes with scatterfile for MT6768?
• Managed to get magisk on stock and weirdly it boots with vbmeta with just --disable-verity while not booting if I use --disable-verification
• After reflashing stock with spflashtool, the stock images have checksums different from the images I get by using the readback tool, magisk only worked after patching the boot.img from the readback process

I dont know about magisk.
I does not use magisk.
I just flash gsi.
if magisk patched, some gsi does not boot at all.
so that I does not use magisk.
and while flashing vbmeta, those two option should put together, not separatly.

and I dont know why MT6768.
no error happen while flashing.
just guess that, P65 and G85 are almost same maybe.

 

[smartomato_reloaded]

I dont know about magisk.
I does not use magisk.
I just flash gsi.
if magisk patched, some gsi does not boot at all.
so that I does not use magisk.
and while flashing vbmeta, those two option should put together, not separatly.

and I dont know why MT6768.
no error happen while flashing.
just guess that, P65 and G85 are almost same maybe.

Yes, when trying to flash gsi im using stock boot.img and no magisk, also putting both --disable commands on vbmeta.

 

[moctir]

So I installed Vanilla AOSP 11 on my King Kong Mini Pro 2 but there are some issues. Like a few others here there is an echo when I talk on a bluetooth headset, someone in this thread build a vendor.img to fix this but I'm not sure it was for the Pro 2 as it caused a bootloop for me. It seems the issue is in audio_policy_configuration.xml and audio_policy_configuration_bluetooth_legacy.xml where I need to remove "Voice Call In" and "voice tx" as described here. However with root I do not have permission to edit it in /vendor/etc or /system/etc even after mounting /. Would anyone know how to do this?

Also, a bigger problem is bluetooth audio for media files does not play thought the headset or speakers but uses the phone speaker instead. I've seen a few workarounds for this but they haven't worked, I'm hoping the fix for the echo will fix that too though.

 

[smartomato_reloaded]

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

Sorry to bother again, I can't never boot after using this command, even in stock, it always bootloops. I would like to ask the version of platform tools you are using and if you could share your vbmeta.img file.

 

[birdibird]

So I installed Vanilla AOSP 11 on my King Kong Mini Pro 2 but there are some issues. Like a few others here there is an echo when I talk on a bluetooth headset, someone in this thread build a vendor.img to fix this but I'm not sure it was for the Pro 2 as it caused a bootloop for me. It seems the issue is in audio_policy_configuration.xml and audio_policy_configuration_bluetooth_legacy.xml where I need to remove "Voice Call In" and "voice tx" as described here. However with root I do not have permission to edit it in /vendor/etc or /system/etc even after mounting /. Would anyone know how to do this?

Also, a bigger problem is bluetooth audio for media files does not play thought the headset or speakers but uses the phone speaker instead. I've seen a few workarounds for this but they haven't worked, I'm hoping the fix for the echo will fix that too though.

Isn't it working with PHH's bluetooth setting for mediatek?

 

[moctir]

Isn't it working with PHH's bluetooth setting for mediatek?

Unfortunately not.

 

[birdibird]

Unfortunately not.

Which vanilla AOSP have you tried?
Did you eg also try AndyYan´s los based gsi's?

Andy Yan's personal builds // GSI - Browse Files at SourceForge.net

sourceforge.net

 

[moctir]

Which vanilla AOSP have you tried?
Did you eg also try AndyYan´s los based gsi's?

Andy Yan's personal builds // GSI - Browse Files at SourceForge.net

sourceforge.net

I didn't try Lineage no, this is AOSP 11 v313 arm64, I think I chose vndklite. I previously tried V311. I wanted to stick with 11 but now I'm regretting not going with the most up to date 12. I've installed everything so don't really want to reflash....