Installing Custom ROM on Cubot KingKong Mini

Search This thread
By:
Advanced…
M

moonraver

Senior Member
May 29, 2022
83
13
badcodelab said:
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
Click to expand...
Click to collapse
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
 
  • Like
Reactions: serj_sar
M

moonraver

Senior Member
May 29, 2022
83
13
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.
 
Last edited:
B

birdibird

Senior Member
Apr 9, 2005
435
46
Zaunkehlchen said:
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.
Click to expand...
Click to collapse
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!)
 
F

FasterPhoneMaster

Member
Jan 8, 2020
22
6
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.
Screenshot_20230126-002239_%CD%E0%F1%F2%F0%EE%E9%EA%E8.png

Screenshot_20230126-002245_%CD%E0%F1%F2%F0%EE%E9%EA%E8.png

Commands:
fastboot devices
adb reboot bootloader
fastboot reboot fastboot
fastboot resize-logical-partition product 38000
fastboot flash system system.img
fastboot reboot bootloader
fastboot reboot-recovery

1. Go to the developer menu and enable USB debugging. In the on state, connect the device to the computer and transfer it from charging mode to file transfer mode. Connect with a good short cable directly, without any magnetic connectors and other pranks;

2. Open the console and type there:
adb devices

Look at the phone screen, it will ask for pairing. Check the box "remember the choice" and agree - in the console you should see the number of your device. If it doesn’t appear, enter again:
adb devices

We don’t touch the phone with our hands anymore, we do everything from the console.

3. We put the phone into bootloader mode FASTBOOT. To do this, enter the command:
adb reboot fastboot

The phone should reboot and you will see FASTBOOT on the screen.

4. Check if our device is available via the console. (Remember about the drivers and that the phone should be visible in the system in the off state?). We request the phone with the command:
fastboot devices

In the console, you should see the number of your device.

5. Command:
fastboot resize-logical-partition product_a 38000

Where:
resize-logical-partition - repartition the logical partition...
product_a - in subsystem "a" (have you studied the topic about Treble Project and know about a/b markup?) ))
38000 - for a size of 38000Kb (why so many - it's not clear, probably just took it with a margin)

6. Flashing the system itself:
fastboot flash system path to .img
7. further commands:
fastboot reboot bootloader
fastboot reboot-recovery
After rebooting in Recovery, you can disconnect the device from the computer. Next, we reset the user data using the factory / data reset menu item (in my opinion, I write from memory) , then
turn it on and use it.
 
B

birdibird

Senior Member
Apr 9, 2005
435
46
FasterPhoneMaster said:
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.
Screenshot_20230126-002239_%CD%E0%F1%F2%F0%EE%E9%EA%E8.png

Screenshot_20230126-002245_%CD%E0%F1%F2%F0%EE%E9%EA%E8.png

Commands:
fastboot devices
adb reboot bootloader
fastboot reboot fastboot
fastboot resize-logical-partition product 38000
fastboot flash system system.img
fastboot reboot bootloader
fastboot reboot-recovery

1. Go to the developer menu and enable USB debugging. In the on state, connect the device to the computer and transfer it from charging mode to file transfer mode. Connect with a good short cable directly, without any magnetic connectors and other pranks;

2. Open the console and type there:
adb devices

Look at the phone screen, it will ask for pairing. Check the box "remember the choice" and agree - in the console you should see the number of your device. If it doesn’t appear, enter again:
adb devices

We don’t touch the phone with our hands anymore, we do everything from the console.

3. We put the phone into bootloader mode FASTBOOT. To do this, enter the command:
adb reboot fastboot

The phone should reboot and you will see FASTBOOT on the screen.

4. Check if our device is available via the console. (Remember about the drivers and that the phone should be visible in the system in the off state?). We request the phone with the command:
fastboot devices

In the console, you should see the number of your device.

5. Command:
fastboot resize-logical-partition product_a 38000

Where:
resize-logical-partition - repartition the logical partition...
product_a - in subsystem "a" (have you studied the topic about Treble Project and know about a/b markup?) ))
38000 - for a size of 38000Kb (why so many - it's not clear, probably just took it with a margin)

6. Flashing the system itself:
fastboot flash system path to .img
7. further commands:
fastboot reboot bootloader
fastboot reboot-recovery
After rebooting in Recovery, you can disconnect the device from the computer. Next, we reset the user data using the factory / data reset menu item (in my opinion, I write from memory) , then
turn it on and use it.
Click to expand...
Click to collapse
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?
 
M

moonraver

Senior Member
May 29, 2022
83
13
FasterPhoneMaster said:
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.
Screenshot_20230126-002239_%CD%E0%F1%F2%F0%EE%E9%EA%E8.png

Screenshot_20230126-002245_%CD%E0%F1%F2%F0%EE%E9%EA%E8.png

Commands:
fastboot devices
adb reboot bootloader
fastboot reboot fastboot
fastboot resize-logical-partition product 38000
fastboot flash system system.img
fastboot reboot bootloader
fastboot reboot-recovery

1. Go to the developer menu and enable USB debugging. In the on state, connect the device to the computer and transfer it from charging mode to file transfer mode. Connect with a good short cable directly, without any magnetic connectors and other pranks;

2. Open the console and type there:
adb devices

Look at the phone screen, it will ask for pairing. Check the box "remember the choice" and agree - in the console you should see the number of your device. If it doesn’t appear, enter again:
adb devices

We don’t touch the phone with our hands anymore, we do everything from the console.

3. We put the phone into bootloader mode FASTBOOT. To do this, enter the command:
adb reboot fastboot

The phone should reboot and you will see FASTBOOT on the screen.

4. Check if our device is available via the console. (Remember about the drivers and that the phone should be visible in the system in the off state?). We request the phone with the command:
fastboot devices

In the console, you should see the number of your device.

5. Command:
fastboot resize-logical-partition product_a 38000

Where:
resize-logical-partition - repartition the logical partition...
product_a - in subsystem "a" (have you studied the topic about Treble Project and know about a/b markup?) ))
38000 - for a size of 38000Kb (why so many - it's not clear, probably just took it with a margin)

6. Flashing the system itself:
fastboot flash system path to .img
7. further commands:
fastboot reboot bootloader
fastboot reboot-recovery
After rebooting in Recovery, you can disconnect the device from the computer. Next, we reset the user data using the factory / data reset menu item (in my opinion, I write from memory) , then
turn it on and use it.
Click to expand...
Click to collapse
and what about disabling vbmeta
FasterPhoneMaster said:
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.
Screenshot_20230126-002239_%CD%E0%F1%F2%F0%EE%E9%EA%E8.png

Screenshot_20230126-002245_%CD%E0%F1%F2%F0%EE%E9%EA%E8.png

Commands:
fastboot devices
adb reboot bootloader
fastboot reboot fastboot
fastboot resize-logical-partition product 38000
fastboot flash system system.img
fastboot reboot bootloader
fastboot reboot-recovery

1. Go to the developer menu and enable USB debugging. In the on state, connect the device to the computer and transfer it from charging mode to file transfer mode. Connect with a good short cable directly, without any magnetic connectors and other pranks;

2. Open the console and type there:
adb devices

Look at the phone screen, it will ask for pairing. Check the box "remember the choice" and agree - in the console you should see the number of your device. If it doesn’t appear, enter again:
adb devices

We don’t touch the phone with our hands anymore, we do everything from the console.

3. We put the phone into bootloader mode FASTBOOT. To do this, enter the command:
adb reboot fastboot

The phone should reboot and you will see FASTBOOT on the screen.

4. Check if our device is available via the console. (Remember about the drivers and that the phone should be visible in the system in the off state?). We request the phone with the command:
fastboot devices

In the console, you should see the number of your device.

5. Command:
fastboot resize-logical-partition product_a 38000

Where:
resize-logical-partition - repartition the logical partition...
product_a - in subsystem "a" (have you studied the topic about Treble Project and know about a/b markup?) ))
38000 - for a size of 38000Kb (why so many - it's not clear, probably just took it with a margin)

6. Flashing the system itself:
fastboot flash system path to .img
7. further commands:
fastboot reboot bootloader
fastboot reboot-recovery
After rebooting in Recovery, you can disconnect the device from the computer. Next, we reset the user data using the factory / data reset menu item (in my opinion, I write from memory) , then
turn it on and use it.
Click to expand...
Click to collapse
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
 
F

FasterPhoneMaster

Member
Jan 8, 2020
22
6
You can find discussion from 4pda forum:
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.
I installed this lineage-20.0-20230109-UNOFFICIAL-gsi_arm64_vS.img.xz, which started up, the rest did not want to get up either
Click to expand...
Click to collapse
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.
Good afternoon! The Chinese sent the key, removed the red inscription. Instructions in the archive.
Click to expand...
Click to collapse
 
M

moonraver

Senior Member
May 29, 2022
83
13
FasterPhoneMaster said:
You can find discussion from 4pda forum:
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.

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.
Click to expand...
Click to collapse
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.
 
F

FasterPhoneMaster

Member
Jan 8, 2020
22
6
F

FasterPhoneMaster

Member
Jan 8, 2020
22
6
moonraver said:
I'll keep watching that Russian forum to get some news.
Click to expand...
Click to collapse
They now posted firmware dump of the LOS 20 installation (KKM3). However, there are many issues.
Known bugs: The screen lock does not work, it connects to the WIFI network, but there is no Internet access, it is impossible to enter the engineering mode, it is not possible to install apk from internal memory, it can be installed using ADBAppControl.
Click to expand...
Click to collapse
 
M

moonraver

Senior Member
May 29, 2022
83
13
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.
 
Last edited:
V

Vilkoko

Member
Feb 13, 2023
11
0
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... 🙏
 
B

birdibird

Senior Member
Apr 9, 2005
435
46
Vilkoko said:
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... 🙏
Click to expand...
Click to collapse
Strange, on mine Silence is working fine.
Did you set it to the standard sms app in settings?
 
  • Like
Reactions: Vilkoko
V

Vilkoko

Member
Feb 13, 2023
11
0
@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.
 
B

birdibird

Senior Member
Apr 9, 2005
435
46
Vilkoko said:
@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.
Click to expand...
Click to collapse
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.
 
Last edited:
  • Like
Reactions: Vilkoko
You must log in or register to reply here.

Similar threads

E
[17Oct08] Samsung SGH-i780 WM6.1 Build 20273 ROM - V5X HH5 KITCHEN
Replies
3K
Views
1M
M
m-Khadem
spocky12
[LG Ks20] [20Oct09] WM6.1 KisS20.5b Rom (5.2.20755) [WWE]
Replies
2K
Views
710K
backlashsid
backlashsid
S
  • Locked
[ROM] [HP iPAQ hx2000] [WM6.5] For reference only
Replies
2K
Views
810K
toki
toki
W
How to root Lenovo A2010 and a few custom ROMs
Replies
860
Views
321K
K
Knightrish
I
  • Locked
all in one sim unlock tool
Replies
1K
Views
1M
the-equinoxe
the-equinoxe

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 7
    M
    moctir
    UPDATE 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:
    Code: 
    fastboot flash system SYSTEM.img
    where SYSTEM is the name of whatever image downloaded.


    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.
    View
    5
    H
    highbiker
    Hi,
    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
    Code: 
    fastboot reboot fastboot
    before flashing the system.



    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.
    View
    4
    B
    birdibird
    I see that there are all kinds of instructions floating around in this thread with all kind of extra commands that you do not need to use at all.

    Here is my comprehensive HowTo for our King Kong Mini 2:

    For the KKM2 we need a A64 or A64binder32 image.
    It can be either VNDK or VNDKLITE.
    VNDKLITE is only needed if you want to use a read/write system.
    If you use a systemless root version, e.g. Magisk, you do not need VNDKLITE necessarily but you can always choose it if you want.

    I am using LeOS Android 12.1 on my kkm2 as I want to be as degoogled as possible.
    Because it is so light, the battery time is quite good.


    - download and unpack the gsi.img.xz file you chose
    - put the unpacked .img together with the vbmeta.img file (attached below) in e.g. your home folder
    - in Linux make sure the android-tools package is installed, in Windows make sure platform-tools is installed

    - Boot into your phone, go to settings, about phone and tick 7 times on build number. Developer options will be activated
    - In settings again there will now be Developer options (probably under system). Switch on OEM/bootloader unlocking and USB debugging
    - connect your phone with the cable to the computer
    - open a terminal or command prompt in the folder of the .img files and tick these commands:
    - adb devices
    (the phone should give a message to trust the computer)
    - adb reboot bootloader
    (phone reboots into bootloader/fastboot mode)
    - fastboot flashing unlock
    (you will be asked on the phone to confirm unlocking it)
    - fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
    -fastboot reboot fastboot
    (phone reboots in fastbootd mode)
    -fastboot flash system GSI-VNDK(lite)-a64-bvN.img
    (on the phone choose):
    -Enter recovery
    -Wipe data/factory reset
    -Reboot system now

    That's all.

    when upgrading your gsi, you only need to flash system again in fastbootd and don't need to data/factory reset (dirty flashing). Sometimes this also works between gsi's, but not always.

    (ps:
    you can skip the adb part by booting into bootloader/fastboot mode:
    -hold volume up button while long pressing the power button on the phone
    -in the little menu move with volume up to fastboot and select it with volume down)

    It is known that with some PHH based gsi's the sound sometimes crackles a bit on some Mediatek devices. It is not yet clear what causes it.
    I am playing around with these settings, somehow the crackling is being influenced by the brightness settings. The weird thing is that on our KKM1 with LineageOS A11, we don't have these crackling problems. Please share your experiences with this.

    Phh Treble settings
    Misc features
    tick:
    -Use linear screen brightness
    -Force Enable Camera2APIHAL3
    -Bluetooth workarounds / Mediatek

    in developer options I changed:
    -Animator duration scale .5x

    happy flashing!
    View
    3
    T
    TNSMANI
    Cobus089 said:
    Note to moderators : we have been polluting the Kingkong Mini / Kingkong Mini 2 thread with news, speculations and comments on the Cubot Pocket since April 23rd.
    I think, both KKM / KKM2 and Pocket lovers would benefit from a split of the thread…

    Cobus.
    Click to expand...
    Click to collapse
    I have moved the posts relating to the Pocket HERE. You can continue the conversation there. As and when development takes place for this device, you can make a request for a new forum as described by my colleague @Timmmmaaahh! above.
    View
    3
    R
    racht
    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 ..
    View

New posts