yashsingh1/xdaforums huggingface dataset:
[Upgrading, Modifying and Unlocking] baconboy:
Thanks! I have been using fastboot, to no avail.

I downloaded your file. Did you install of them? MTK_Driver_ ext, Driver_Auto_Installer_.1632, and you think Win 8 driver?

EDIT: Win8 driver failed
[Upgrading, Modifying and Unlocking] baconboy:
It WORKED! I think it was the MTK USB driver v.1.0.8 that did it! All flashed, setting up now. Got that orange state message which boot up take FOREVER which worried me, but I think we're OK. For now. Thanks everyone for your patience!
[Upgrading, Modifying and Unlocking] baconboy:
I can't edit the build.prop with Root Explorer. It doesn't save, even though it looks like I have write access. Any ideas? I'm trying to make it so the lockscreen rotates (want it set to landscape)
[Upgrading, Modifying and Unlocking] dank2019:
I tried yesterday AOSP 11 from https://github.com/phhusson/treble_experimentations/releases/

system-roar-a64-ab-vanilla.img.xz

and it worked out of the box. No real issues until now.
[Upgrading, Modifying and Unlocking] baconboy:
So you have AOSP 11.0 v300.j ? And everything works? That's awesome, I'll try it too
[Upgrading, Modifying and Unlocking] dank2019:
Yes, everything I use in my daily work is working. Partially better then ASOP 10 ;)

View attachment 5159289
[Upgrading, Modifying and Unlocking] baconboy:
Time to upgrade! Thanks for trying it!

My weird problem is that (I don't have TWRP or Magisk) Root Checker says my phone is rooted, Super SU seems to work, but Ad Away lets ads display in apps and I can't edit or even copy the build.prop. Which makes me think I don't have root or just partial root?
[Upgrading, Modifying and Unlocking] dank2019:
The phh treble is already rooted (no supersu necessary). I use AFWall+, which needs root and its working.
[Upgrading, Modifying and Unlocking] landsome:
Amazing, really!
[Upgrading, Modifying and Unlocking] baconboy:
I'm downloading

system-roar-a64-ab-vanilla.img.xz

Will flashing it delete everything on my phone or is an upgrade?
[Upgrading, Modifying and Unlocking] dank2019:
I did only the install via TWRP - no wipe. So it worked like an upgrade. All my data are still there.
[Upgrading, Modifying and Unlocking] landsome:
Does twrp work well for you?

And does in-call volume change work in 11?

How about battery life?
[Upgrading, Modifying and Unlocking] baconboy:
I just tried this and it DID NOT WORK. Ended up in a boot loop. Avoid!
[Upgrading, Modifying and Unlocking] baconboy:
So 11 seems to work well. I have lost aptx codec, which might be a deal breaker. Also a permanent Serial Console Enabled notification. What is that?

Adaway can no longer change the hosts file. Can't edit the prop file. Root checker says I'm rooted. WHAT
[Upgrading, Modifying and Unlocking] landsome:
You had working aptx on custom Android 10 roms?
[Upgrading, Modifying and Unlocking] baconboy:
Yeah on the previous one you can select it in Developer options
[Upgrading, Modifying and Unlocking] dank2019:
I would expect, that serial console checker enabled is a feature, which they use to debug / test:

Serial console enabled Performance is impacted. To disable, check bootloader

I recently created an Android emulator with Android version R. It showing an Android system notification "Serial console enabled Performance is impacted. To disable, check bootloader" Can someone

stackoverflow.com

I have no impact on my performance so far. Battery life looks similar to ASOP 10. So, I disabled this warning.
[Upgrading, Modifying and Unlocking] kkm6761:
Any help please? Not a single guide in this thread worked for me. I got the kingkong mini for the sole purpose of modifying it. Is a full recap possible?
[Upgrading, Modifying and Unlocking] landsome:
What is the problem specifically? The OP worked for all of us here...
[Upgrading, Modifying and Unlocking] birdibird:
I installed LOS 18.1 over LOSQ 17.1 and it works fine.

I just flashed the .img in TWRP and wiped cache and art cache.
[Upgrading, Modifying and Unlocking] kkm6761:
I have had a lot of problems, but have figured them out. I have only started so I have basically no knowledge, had to read/learn adb/fasstboot, spflash for mtk, etc.. for example and am not an advanced linux/gnu user.

After a full flash I have "TEE key write" and my IMEI numbers have changed. In fact they change after every factory reset. But that is not the main issue for the moment.

Having gone the installation process with TWRP, after installing magisk and disable dm-verity-forceencrypt, it was unable to mount /nvdata. Now the phone is stuck on Cubot logo. I'll try to figure that out by again starting from zero.

Ultimately I want to install/port Graphen OS. I am working my hard way towards it.
[Upgrading, Modifying and Unlocking] landsome:
Unfortunately I cannot help with twrp. I failed to install it. I use adb to sideload. So no magisk either. But some AOSPs and Lineages come rooted, and that is enough for me.
[Upgrading, Modifying and Unlocking] landsome:
That's great. Unfortunately twrp failed for me, so I will have to sideload.
[Upgrading, Modifying and Unlocking] kkm6761:
How did it fail? I have to say that I installed it on the first king kong mini firmware (2019), not on the later updates (2020).
[Upgrading, Modifying and Unlocking] landsome:
I failed on the 06/19 update, if you are referring to original roms
[Upgrading, Modifying and Unlocking] birdibird:
Did you flash twrp of post 33 with spflashtool?

edit:

I must say, LOS 18.1 feels a lot smoother than 17.1.

Very nice work!

I didn't get Magisk to work here, but superuser is fine too.

Next I will try to install Xposed and MicroG etc. Did anyone do that already?
[Upgrading, Modifying and Unlocking] kkm6761:
I am unable to root with magisk and I am confused with regards to OP. He says with magisk you have to patch recovery and boot.

I have twrp (so no more OEM recoery). When through twrp I install magisk, upon reboot I get magisk app asking me to download magsik zip. do I still have to patch boot?

I see no clear details in this guide: https://unofficialtwrp.com/unofficial-twrp-3-3-1-root-cubot-king-kong-mini/
[Upgrading, Modifying and Unlocking] kkm6761:
Ok, who has magisk root? How did you get it? I did all of youtube and internet, nothing works for the king kong mini. That is all I get.

Edit: I'll now try patching recovery.img, which will make me lose twrp.
[Upgrading, Modifying and Unlocking] kkm6761:
Holding Volume Down+Power buttons boots to Factory Mode. I have translation.

When in standard Recovery Mode (by holding Volume Up+Power buttons and then selecting "recovery mode", you see the "android" and "no command". You have to press Power button and Volume Up (a short press, no holding), then you get in Recovery Mode.
[Upgrading, Modifying and Unlocking] kkm6761:
Well, so I personally figured everything out that was written in these 7 pages. I must say the quite a mediocre job of clarifying the issues by developers, not saying they don't have skills. I'll make a summary. The basics all work (with the right files!!!!!) on the latest king kong mini firmware (CUBOT_KINGKONG_MINI_9101C_V15_20200609), with twrp 3.3.1 and magisk 20.4.
[Upgrading, Modifying and Unlocking] birdibird:
Did anybody managed to get Magisk working on 18.1? On 17.1 all worked fine, but I can't get Magisk to work on 18.1

besides that, I love my LineageOs 18.1. So smooth and no bugs on the KKM and in my idea the battery life is a bit better than with 17.1
[Upgrading, Modifying and Unlocking] KuRiXY:
Hi! I see there is a new king kong mini 2, same hardware, more battery and android 10.

We can download the official firmware from cubot.net, but can we install this rom on king kong mini 1?

Thanks!
[Upgrading, Modifying and Unlocking] landsome:
A good question. You can always try. and report back.. :)
[Upgrading, Modifying and Unlocking] birdibird:
Ok, I found out how to run Magisk on LineageOS GSI 18.1. I will share it here step by step.

->I am presuming you already installed GSI 17.1 or 18.1 succesfully and it works. For brand new installations of a GSI see elsewhere in this topic

-> I am using SPFlashtool in this guide. You might also be able to use fastboot or flash .img in TWRP, but SPFlashtool is easy and straightforward and it works.

In SPFlashtool always make sure 'Download Only' is selected and untick the box next to 'Name' to deselect everything, then double click on the path of the item you want to flash to select the correct .img file.

0) prepare:

-download and unpack Andy Yan's GSI 18.1 a64_bvS version (20210111 or newer)

-download from post #33 the root.rar file and unpack only TWRP

-download and unpack the boot.img from the link from post #58

1) switch the phone off and flash with SPFlashtool the downloaded GSI 18.1 on system and TWRP on recovery. You can skip this if you already have TWRP and the newest GSI.

2) boot the GSI and connect the phone to the pc. Make sure in developer options usb debugging and rooted debugging are switched on

3) copy boot.img to the phone

4) install the latest Magisk Manager (8.0.5 or newer), change update channel to beta (it should say 21.2 or newer)

5) install Magisk, unselect recovery mode and select the boot.img file (make sure you are connected to the internet)

6) copy the magisk_patched .img file from the Download folder back to your pc

7) adb root and adb shell

8) type echo $PATH, and copy output to a text file on your pc

9) switch the phone off and flash with SPFlashtool the magisk_patched .img on boot

10) disconnect the phone and while holding volume-up power on the phone and choose to boot recovery

11) in TWRP mount /system

12) connect the phone and adb root (probably still active)

13) adb pull /system/init.environ.rc

14) edit on the pc the init.environ.rc file and add an extra line under 'on early-init':

export PATH /sbin:(the $PATH output which you copied into a text file goes here without these parentheses)

15) adb push ./init.environ.rc /system

16) still in TWRP go in file manager to /system/system/xbin

17) delete su

done.

reboot into a LineageOS 18.1 with a working Magisk
[Upgrading, Modifying and Unlocking] landsome:
You're amazing. I just cannot install TWRP. Tried it countless times with SPFTool. I load everything OK, then on attempting to restart into the new recovery I end up in an endless reboot and so I have to install via fastboot, then try again, then the reboot cycle a.s.o. I just don't get it... :)

I tried to install TWRP via SPF with the files in post #33, alone, with a system and various other combinations. Nothing works.
[Upgrading, Modifying and Unlocking] birdibird:
Did you follow all the steps? eg:

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

flashed Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip

use the patched lk or patch it yourself

which cubot rom did you start with? I used v15.
[Upgrading, Modifying and Unlocking] landsome:
I started with one of the custom ROMs (either AOSP10 or LOS17.1). I had already fastbooted vbmeta, but I tried to SPFlash TWRP both with and without it (and with and without the files in the #33 post ROOT file set.)

I did not get to flash Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip because I was never able to get into TWRP.
[Upgrading, Modifying and Unlocking] landsome:
One more step-by-step guide, please? :) How did you get microG to work?

I ask because signature spoofing is disabled in LOS? Did you do it by flashing nanodroid (I assumed you did that via TWRP, which I cannot install for the life of me..)
[Upgrading, Modifying and Unlocking] birdibird:
Did you get Magisk to work? You could follow the same adb steps I guess with the original recovery.

Then you can install MicroG in Magisk.
[Upgrading, Modifying and Unlocking] landsome:
Can I install Magisk without installing first TWRP?
[Upgrading, Modifying and Unlocking] birdibird:
yes
[Upgrading, Modifying and Unlocking] s_licciardello:
Hi, I made a Telegram group for tips and modding for Cubot KingKong Mini: @cubotmini

Someone have king mini 2?
[Upgrading, Modifying and Unlocking] 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

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)

adb reboot bootloader

4.) once in bootloader mode (quoted from #39)

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)

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

fastboot reboot fastboot

8.) After device is in real fastboot mode (the screen is different to that of bootloader fastboot mode)

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:

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:

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.
[Upgrading, Modifying and Unlocking] birdibird:
Great, well done!

Why did you choose 17.1 and not 18.1? In my experience it runs better.
[Upgrading, Modifying and Unlocking] highbiker:
LOS18.1 is also flashable to the KKM2. LOS17.1 was my first test. I think I will stay on LS18.1.

I was not able to install TWRP on KKM2. Maybe the original firmwares (KKM vs KKM2) are too different or I'm doing something wrong, but i face the same problem as landsome (see #155). I tried it multiple times using fastboot and SP_Flashtools, but neither worked. Always got bootloops enforcing reflashing of stock firmware via SP_Flashtools.

I used the TWRP from post #33.

My

unsuccessful

attempts were:

1.) via fastboot. Instead of flashing stock recovery (see 6.) in my post above #163), I flashed recovery_TWRP.img.

2.) via fastboot after "fastboot reboot fastboot" (see 7.) in my post above #163) I got this error

fastboot flash recovery recovery_TWRP.img
Sending 'recovery' (20056 KB) OKAY [ 1.211s]
Writing 'recovery' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed

3.) flash via SP_FlashTools I used the following settings:

View attachment 5213069

recovery_TWRP.img from post #33.

lk-modified.img: patched lk.img to avoid Orange State (Is working when flashed via fastboot)

vbmeta.img: I tried both, one from post #33 and the original one from stock firmware.

Does anyone have any hint what I might have done wrong? If not, that could indicate that TWRP is currently not working on the KKM2.
[Upgrading, Modifying and Unlocking] landsome:
My only guess is that flashing TWRP may not work after having previously done all the other stuff (vbmeta, new OS). It does not make much sense, but given that I have given it almost two dozen tries in every single combination, I am at a loss.
[Upgrading, Modifying and Unlocking] birdibird:
Did you try to start again: flash the original Cubot rom and then TWRP?
[Upgrading, Modifying and Unlocking] landsome:
About half a dozen times. Why half a dozen? Tried with SPF and alternatively fastboot, with and without the rest of the files in the ROOT folder in post #33. Always the bootloop and having to flash AOSP/LOS via fastboot to get out of it. Then back to stock ROM etc.

One thing I did not do, but I don't think I have it in me to try again, is check out some of the older stock ROMs (always tried with the latest).
[Upgrading, Modifying and Unlocking] sawasLT:
Hello , am kinda new here and i want to instal Los to kkm2 but am getting always stuck on

=>Fastboot mode...

and i can not chane nothing , i can not fid the device via

Fastboot devices

or adb devices , i deed to hold power button for 15s

then i can start again with the adb reboot bootloader and after that move am stuck again in the bleck screen on my phone with just

=>fastboot mode...

and i can not do nothing , can some one help :D :D
[Upgrading, Modifying and Unlocking] highbiker:
Hi,

it could be a driver issue. Make sure you have installed the correct drivers (see Post #122).

If this was not the problem, make sure your fastboot is of the actual version. Yout can get the actual verison from here:

https://developer.android.com/studio/releases/platform-tools
[Upgrading, Modifying and Unlocking] sawasLT:
thx for the answer , i updated the drivers and downloaded and used the actual fastboot version but am stil getting the same

looking thru powershell it says

step1

\platform-tools> adb devices

List of devices attached

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

KKMN2201127005290 device

step2

\platform-tools> adb reboot bootloader

\platform-tools>

then it is not showing nothing more ..

the phone is schowing after reboot

=>fastboot mode ... ( on the bottom left corner )

nothing more

Device maniger says:

-adroid phone

-android adb interface
[Upgrading, Modifying and Unlocking] highbiker:
Until here everything is fine. My phone just says "fastboot mode ..." in the bottom left too, after issuing adb reboot bootloader

now your computer should list the device after issuing

fastboot devices

if not, windows is not recognizing the phone correctly, I think.

My device manager also lists the device as

Android Phone -> Android ADB Interface

At first I also had the problem that my KKM2 was not found via "fastboot devices" in windows.

You have two options now, both are working for me:

1.) Using windows.

2.) Using linux

1.) Windows

I dont know which driver package solved it, but i installed many. Here is a (I hope complete) list of drivers I installed:

MTK USB driver v.1.0.8

minimal_adb_fastboot_v1.4.3 (There are also drivers included. but be sure to use the current version of fastboot for flashing)

WIN8 driver from cubot website (terminated with two failures)

MediaTek_Preloader_USB_VCOM_Drivers_Setup_Signed

2.) Linux

If you are familiar with linux, you can try that (linux via virtual box and KKM2 over USB-3.0-Controller (xHCI) is sufficient, I also did that with my KKM2)

in linux you can install fastboot and adb via:

sudo apt-get update
sudo apt-get install android-tools-adb
sudo apt-get install android-tools-fastboot

linux recognized my kkm2 directly after installing both. So I think additional drivers are also installed by these packages.

but sadly the fastboot version installed by android-tools-fastboot is too old for issuing

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

so you have to update fastboot to the latest version by using

mkdir ~/Android && cd ~/Android
wget https://dl.google.com/android/repository/platform-tools-latest-linux.zip && unzip platform-tools-latest-linux.zip
echo "alias adb='~/Android/platform-tools/adb'" >> ~/.bash_aliases && source ~/.bash_aliases
echo "alias fastboot='~/Android/platform-tools/fastboot'" >> ~/.bash_aliases && source ~/.bash_aliases

after that you should be able to do the flashing

But maybe others have have found easier ways. Maybe directly via SP_FlashTool? I didn't found a way to flash the LOS System directly via SP_FlashTool, because the SP_FlashTool does not list a "system" entry (see post #165). Does anybody have a hint here?
[Upgrading, Modifying and Unlocking] sawasLT:
thx , the answer war after instaling everithing ... the instalation from " minimal_adb_fastboot_v1.4.3 "

finally found the fastboot device , lets see now gonna try to instal /Los :P
[Upgrading, Modifying and Unlocking] sawasLT:
hallo ,

am getting the error

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system lineage-17.1.img

target reported max download size of 134217728 bytes

sending sparse 'system' 1/10 (131068 KB)...

OKAY [ 5.053s]

writing 'system' 1/10...

FAILED (remote: This partition doesn't exist)

finished. total time: 5.063s

i try to do a " fastboot reboot fastboot "

but am geting .

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot fastboot

fastboot: usage: unknown reboot target fastboot

em i stupid and old or am doing something wrong ?

am using the vbmeta boot and recovery from the original rom from the cubot website
[Upgrading, Modifying and Unlocking] highbiker:
thats exactly the error I got and thats why I had to do the fastboot reboot fastboot

indicates that you are using the fastboot from Minimal ADB, but thats not the actual version. You need the actual fastboot version from here: https://developer.android.com/studio/releases/platform-tools

fastboot --version should print

fastboot version 30.0.5-6877874
[Upgrading, Modifying and Unlocking] sawasLT:
thx , i managet to instal Los 17.1

now am getting a loat of app stop working and stuf on camera and recorder and sutch

i wanna try to add gapps via adb side loader , hope it will work , thil now guys thx for the help your amazing , last time i was playng around with phones was as i jailbreaked my 3gs to pineapple :D
[Upgrading, Modifying and Unlocking] sawasLT:
now am again with a problem , o downloaded the open_gapps-arm64-10.0-tvmini-20210206.zip

so am in android recovery , going to apply update from adb

in cmd ,

adb sideload open_gapps-arm64-10.0-tvmini-20210206.zip

and am gething the error on my phone screen

E:signature vertification filed

E:error: 21

instal from adb completed with status2.

instalation aborted.

E:fota installation aborted

E:: no such file or directory

E:Fota instalation aborted

E:: bad file descriptor

cmd shows

adb sideload open_gapps-arm64-10.0-tvmini-20210206.zip

serving: 'open_gapps-arm64-10.0-tvmini-20210206.zip' (~47%) adb: failed to read command: No error

sorry if am naggy :D
[Upgrading, Modifying and Unlocking] kkm6761:
A long time, sorry. I am away right now. Don't have anything with me. I'll make a sticky with the main files. There is a TWRP file that does not work. So anyone managed to have both root with magisk and TWRP?

How is KingKong Mini 2 doing with 1000mAh extra battery?
[Upgrading, Modifying and Unlocking] highbiker:
Good to hear that LOS is running :)

I dont use gapps, so I just can give a guess.

The LOS for KKM2 is a 32-bit System with 64-bit binder. You could try arm gapps (32-bit) instead of arm64.
[Upgrading, Modifying and Unlocking] highbiker:
My KKM2 is still on the first battery charge, my experiences are therefore a bit vague. But with a bit of Wi-Fi usage, few GPS-tests, permanently connected via LTE during the day and in flight mode at night, the battery life is about 3 days.
[Samsung Galaxy Note 10+ Questions & Answers] bingookela:
hi everybody,

i have SM-N9750 and i want install firmware SM-N9760 into SM-N9750 then my phone has brick or running normal or some funtion not running??? i dont know what happen after install firmware.

Someone can answear and help me.

Thanks