hello
unit 800x480 rk3188 single din 7" flip up similar to KD-C0109 =
*MCU:MTCC-KLD5-V2. 97
*Kernel : 3.0.101+ [email protected] #108
*Build : rk3188-userdebug 5.1.1 LMY48Y eng.hac.20160411.083226
so i wanted to try a new firmware from huifei server but somehow it failed and now it s stuck in recovery mode. stupid me i didnt make a backup.
now everytime i try to flash a firmware i have an error when checking parameter :
"E:can't open /dev/block/rknand_parameter
E:bad dest path /parameter"
I tried to flash some mtcc kdl stock firmware available on huifei server but same error.
So can someone help me please or give me a link to flash back to my previous firmware.
recovery system version : v5.1
i guess i maybe damaged the RK nand flash data somehow, so is there a way to fix that with RKBatchTool app? if yes, how can boot the device in the correct mode please?
device various name: sk-c0109-us, pumpkin KD-C0109-us-a or kd8600.
well i found the same pb on 4pda.ru ( http://4pda.ru/forum/index.php?showtopic=704934&view=findpost&p=53248094) and i tried to put my device in loader mode to be able to use RKBatchTool but with no success. i tried every method on their website (http://4pda.ru/forum/index.php?showtopic=704934&view=findpost&p=44580369). i tried as well the sd_firmware_tool (sdupdate.img thing) but no lock.
i have 1usb (front) + 2usb back (normal + dvr) and dont know which one to use. i tried to check inside to short pins but seems to be a BGA nand.
so please if someome has similar device as mine and know how to put in loader mode, will be really appreciated. thx.
Hy,
i also have the same problem. After loading a wrong ROM onto my RK3188, my unit is stucked in bootscreen.
EVERY image file i could found, is rejected with this rknand errors
Also i get this errors if i boot directly from the SD card (turn off my unit, plug power out, insert SD, plugin power). I wrote Malaysk a email and hope he has a idea
hi
use a kit kat 4.4.4 firmware with sd_firmware_tool method. after use DSA 5.1.1 firmware if u want lollipop. i havent managed to use a FUSE firmware.
marcel.ng886 said:
hi
use a kit kat 4.4.4 firmware with sd_firmware_tool method. after use DSA 5.1.1 firmware if u want lollipop. i havent managed to use a FUSE firmware.
Click to expand...
Click to collapse
Had the same issue.
I can confirm that if you are having this issue you need a version 4.4 recovery. No current ROM that includes a 5.1 recovery will work.
You can use the SD Firmware tool with any 4.4 ROM (assuming you have a MTCB/C unit) and also with DSA8310's Lollipop ROM as this one also includes a 4.4 recovery..
After you have a working recovery you can flash a 4.4.4 FUSE ROM - I flashed Malaysk's October ROM and it works flawless.
You could also take any 5.1 ROM you like, decompress it with imgRePacker, replace the 5.1 recovery.img with a 4.4. image, edit the parameters.parm file to match the new layout, rebuild the update.img file with the same imgrePacker and flash.
One detail about the SD Firmware Tool. In order for it to work the way it was intended you have to insert it in the GPS slot and then SIMULTANEOUSLY apply +12V and ACC power.
I was simply unable to do this with the unit in the car, I had to take it out and power it from my car battery charger, only way it worked. So if it does not seem to work at first don't despair
m00n61 said:
Had the same issue.
I can confirm that if you are having this issue you need a version 4.4 recovery. No current ROM that includes a 5.1 recovery will work.
You can use the SD Firmware tool with any 4.4 ROM (assuming you have a MTCB/C unit) and also with DSA8310's Lollipop ROM as this one also includes a 4.4 recovery..
After you have a working recovery you can flash a 4.4.4 FUSE ROM - I flashed Malaysk's October ROM and it works flawless.
You could also take any 5.1 ROM you like, decompress it with imgRePacker, replace the 5.1 recovery.img with a 4.4. image, edit the parameters.parm file to match the new layout, rebuild the update.img file with the same imgrePacker and flash.
One detail about the SD Firmware Tool. In order for it to work the way it was intended you have to insert it in the GPS slot and then SIMULTANEOUSLY apply +12V and ACC power.
I was simply unable to do this with the unit in the car, I had to take it out and power it from my car battery charger, only way it worked. So if it does not seem to work at first don't despair
Click to expand...
Click to collapse
I had 5.1 recovery and ran into same issue with Malaysk 5.1 FUSE ROM. I restored system with DSA prerooted ROM and was also able to install factory 5.1 ROM with no issues. Only Malaysk ROM is giving me this issue.
Is there any other way to install Malaysk ROM? I really want to try it.
huuhuubaer said:
Hy,
wrong ROM onto my RK3188, my unit is stucked in bootscreen.
EVERY image file i could found, is rejected with this rknand errors
Also i get this errors if i boot directly from the SD card (turn off my unit, plug power out, insert SD, plugin power). I wrote Malaysk a email and hope he has a idea
Click to expand...
Click to collapse
i also have the same problem. After loading a rom malaysk 1024x600 rk3188. My radio is 1024x600 and rk3188, error mcu img aborted and no work my radio more...
PD: My head unit
MTCC KLD6 2.97
5.1.1 - 1024x600
RK3188 Quad core
16gb rom
1gb ram
Repair method 100%
http://forum.xda-developers.com/showpost.php?p=67184851&postcount=50
I need help.
emudem said:
Repair method 100%
http://forum.xda-developers.com/showpost.php?p=67184851&postcount=50
Click to expand...
Click to collapse
Hi, I need your help. I bought a car unit a few months ago, I had problems with bluetooth service, and the online store sent me an image for update. When I updated from "about the device" and restarted the device, it did not pass the screen with the logo "lollipop multimedia on vehicle navigation syntem". My problem, is that the store where I bought it on the internet, does not answer my message again.
I think that my problem is the same described in this post. And I don't know wich firmware should I download.
I'm new in this. Thank you!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
juandiego85 said:
Hi, I need your help. I bought a car unit a few months ago, I had problems with bluetooth service, and the online store sent me an image for update. When I updated from "about the device" and restarted the device, it did not pass the screen with the logo "lollipop multimedia on vehicle navigation syntem". My problem, is that the store where I bought it on the internet, does not answer my message again.
I think that my problem is the same described in this post. And I don't know wich firmware should I download.
I'm new in this. Thank you!
Click to expand...
Click to collapse
Hello There,
I was in the same boat.
My unit had Lolipop 5.1.1. and I tried to install with many LP 5.1.1 Firmwares to recover my bricked system, but nothing worked.
I read it in the forums that the SD Card boot process works well with all Android 4.X.X Firmwares. So i tried it with this one below,
https://mega.nz/#F!zRRkVThb!DYBC0LRK-o34ZxDObQo73Q!bRQ3EJQD
File name: KLD_rk3188_h_2016-02-26.RAR (Mine is a Klyde RK3188 MTCC unit., so you will have to find a corresponding Android 4.X,X Firmware that suits your device)
I followed the SD card boot up process mentioned below, with this firmware KLD_rk3188_h_2016-02-26.RAR.
https://forum.xda-developers.com/showpost.php?p=67184851&postcount=50
To my Surprise, the System accepted the Android 4.4.4 Firmware and I was able to boot my device successfully.
Later, I have asked the people where I bought this DVD to send me the correct and updated firmware for Android 5.1.1, which suits my device.
Now, I put the update.img file of the latest Android 5.1.1 firmware to the root of another SD card and updated my system going to Settings -> System Updates.
I checked the box, where it said "Wipe everything and Install"
The Systems restarted and it accepted the new Android 5.1.1 Firmware and the system booted back in successfully with Android 5.1.1 .
I hope this helps someone in the future.
God Bless,
Shaju Mathew
Related
Hi there,
I've been working on rooting my htc one X bought in Australia locked to vodafone and now unlocked and used for a while.
I had been planning on rooting the phone for a while and after reading up multiple posts I chose to use the XDA developers video to root the phone. As the video is not very clear towards the end on the processes. But I completed the process somehow with reference to other videos and processes. However, after reading up on the best available ROMs I chose the CM11 with a basic process explained here (unable to post link)- however, that didnt help me much as there's just a basic description of what's to be done (helpful for advanced users).
But as this is my first attempt to rooting my device, I had to look up youtube on videos describing the rooting process for HTC one X. And found another video by the same author -
The author uses another ROM for the process but said this was a universal process. And I ended up copying only the CM11 zip folder of the ROM and not the Gapps zip file. Then his process didn't allow me to boot into recovery as my phone would get to the 'HTC - quietly brilliant' screen and get hang. Then I figured that the recovery image he had in the onexroot folder was an old one so I replace it with the latest image of recovery - recovery-clockwork-touch-6.0.4.8-endeavoru. And tried again, but with no luck.
Then I went in to the HBOOT menu and selected recovery and followed the process of installing from zip file and completed the entire installation process but the phone would go in to a boot loop when I rebooted. I followed some other processes to resolve this and ended up messing up the rom image on the phone. So now i'm unable to do anything with the phone as the stock rom is wiped out and so is the custom rom. I've tried the process of sideloading the zip files but I keep getting an error message of 'device not found'. I tried using the TWRP recovery as well for pushing files, but the the phone is non responsive on the main menu screen of TWRP itself. So I've flashed back to CWM recovery but am out of ideas on how to recover the phone.
Current status of the phone:
Bootloader - Unlocked
CMW - recovery-clockwork-touch-6.0.4.8-endeavoru
Sorry for the long description, but any help will be highly appreciated.
Thanks!
rubendayal said:
Hi there,
I've been working on rooting my htc one X bought in Australia locked to vodafone and now unlocked and used for a while.
I had been planning on rooting the phone for a while and after reading up multiple posts I chose to use the XDA developers video to root the phone. As the video is not very clear towards the end on the processes. But I completed the process somehow with reference to other videos and processes. However, after reading up on the best available ROMs I chose the CM11 with a basic process explained here (unable to post link)- however, that didnt help me much as there's just a basic description of what's to be done (helpful for advanced users).
But as this is my first attempt to rooting my device, I had to look up youtube on videos describing the rooting process for HTC one X. And found another video by the same author -
The author uses another ROM for the process but said this was a universal process. And I ended up copying only the CM11 zip folder of the ROM and not the Gapps zip file. Then his process didn't allow me to boot into recovery as my phone would get to the 'HTC - quietly brilliant' screen and get hang. Then I figured that the recovery image he had in the onexroot folder was an old one so I replace it with the latest image of recovery - recovery-clockwork-touch-6.0.4.8-endeavoru. And tried again, but with no luck.
Then I went in to the HBOOT menu and selected recovery and followed the process of installing from zip file and completed the entire installation process but the phone would go in to a boot loop when I rebooted. I followed some other processes to resolve this and ended up messing up the rom image on the phone. So now i'm unable to do anything with the phone as the stock rom is wiped out and so is the custom rom. I've tried the process of sideloading the zip files but I keep getting an error message of 'device not found'. I tried using the TWRP recovery as well for pushing files, but the the phone is non responsive on the main menu screen of TWRP itself. So I've flashed back to CWM recovery but am out of ideas on how to recover the phone.
Current status of the phone:
Bootloader - Unlocked
CMW - recovery-clockwork-touch-6.0.4.8-endeavoru
Sorry for the long description, but any help will be highly appreciated.
Thanks!
Click to expand...
Click to collapse
flash Philz recovery 5.15.9 mount sd card copy gaps.zip to your folder after this flash again CWM latest version go in recovery install rom.zip after this gapps.zip after this go in fastboot and flash the boot.img from rom.zip via fastboot with the command fastboot flash boot boot.img
Thant said:
flash Philz recovery 5.15.9 mount sd card copy gaps.zip to your folder after this flash again CWM latest version go in recovery install rom.zip after this gapps.zip after this go in fastboot and flash the boot.img from rom.zip via fastboot with the command fastboot flash boot boot.img
Click to expand...
Click to collapse
Hi,
Thanks for your reply. Philz recovery has an updated version available however, in its download screen it is not clear which version corresponds to the One X. There are versions of the software for One V and One S. Could you suggest which one would be the right one?
Thanks.
rubendayal said:
Hi,
Thanks for your reply. Philz recovery has an updated version available however, in its download screen it is not clear which version corresponds to the One X. There are versions of the software for One V and One S. Could you suggest which one would be the right one?
Thanks.
Click to expand...
Click to collapse
Nevermind that. I found the right one after a little more search philz_touch_6.19.3-endeavoru.zip
hope that's okay.
rubendayal said:
Nevermind that. I found the right one after a little more search philz_touch_6.19.3-endeavoru.zip
hope that's okay.
Click to expand...
Click to collapse
The lastest Philz have problem with mounting sd card like CWM and TWRP for this I say to install 5.15.9
rubendayal said:
Nevermind that. I found the right one after a little more search philz_touch_6.19.3-endeavoru.zip
hope that's okay.
Click to expand...
Click to collapse
Hi Thant,
I was able to mount the sd card in Philz, but not sure how to copy the data. Unable to find information on that online.
Any suggestions?
rubendayal said:
Hi Thant,
I was able to mount the sd card in Philz, but not sure how to copy the data. Unable to find information on that online.
Any suggestions?
Click to expand...
Click to collapse
you must to see the device to your computer but on latest Philz sd mount not working install 5.15.9
Thant said:
you must to see the device to your computer but on latest Philz sd mount not working install 5.15.9
Click to expand...
Click to collapse
Hi Thant,
Thank you so much for your help. You were completely right. I downloaded the 5.15.9 version and that let me connect the phone as a usb device and I mounted the device as usb in recovery and copied the gapps. however, there was an issue with the latest CWM that didnt let me install the ROM but philz recovery did the trick. Then again I installed the latest cwm and installed the gapps..wiped the factory data and went back to the fastboot menu, flashed the boot.img from the Rom's folder and rebooted. And now I have the android 4.4.4 working just fine!
Thank you once again for all your help! really appreciate it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello everyone. I was with Android 7 on my ZS570KL and returned to 6 for a tutorial found on the internet and worked, but all the sensors of the device were disabled (screen rotation, gyroscope, approximation, fingerprint [only registers up to 93% and gives error], and all the others). How do I reactivate? I came back to Android 7, formatted the device several times, and nothing solves!
What tutorial and why?
No information = no help
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I do not remember where I found the tutorial and the files, but the process is this:
1. Download http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZS570KL/UL-Z016-WW-4.12.40.1698-user.zip
2. Download https://mega.nz/#!tp9DSQ4b!3wdDLsh3BBtPju8G74xlDjLJ9QywFaoLs1T11mMt3QQ
3. Unzip FlashTools64_20161125.zip
4. Unzip UL-Z016-WW-4.12.40.1698-user.zip and move out files under firmware-update to FlashTools folder
5. Put downgrade.bat, boot.img, recovery.img to FlashTools folder
6. Reboot phone to bootloader and click downgrade.bat
The reason was to swap the conventional root SU through the Magisk. I tried to reinstall 7 just by replacing the original recovery available here in XDA, but the process was not going to restart, so I followed that one to try to return and reinstall everything. It worked, I got back to 6, but I did not know everything. It looks like a computer without the drivers installed.
I'd downgrade again, if it was me, this time I'd install a stock Rom (MM) from ASUS. Then test everything again. If everything is good to go then I'd root and upgrade.
Changing the OS in the middle doesn't help if you have a problem.
Especially if it just builds upon the foundations of the previous OS...
Did you flash a complete N rom or do an update?
The ROMs I try are exactly those of the Asus site. I tried the downgrade again to version 4.12.40.1698 and realized something when I flash in recovery mode. The following error messages appear:
Unmount of /firmware failed: no such volume
Mount: failed to mount /dev/block/bootdevice/by-name/mdtp at /firmware: No such file or directory
Unmount of /firmware failed, no such volume
What is it? How to solve?
I need the original kernel and recovery of the latest firmware released, can anyone make it available?
AndreSantoro84 said:
I need the original kernel and recovery of the latest firmware released, can anyone make it available?
Click to expand...
Click to collapse
These recovery images are from nenebear59, thanks to him !
Z016-WW-5.14.44.2212_recovery :
For 2.15GHz CPU
For 2.4GHz CPU
Thank you very much! Now I need the "persist.img" file, of the same rom, can you make it available? I thank you!
I downloaded the source code kernel from the Asus site, and the compressed file has a sensor folder. I downloaded the kernel zip file to my memory card and tried to install via recovery, however the following message appears: E: footer is wrong / E: signature verification failed. How do I get install by recovery or via flash in cmd?
I followed this tutorial (https://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061) and managed to recover the fingerprint reader, but the others are still turned off. I really need the correct file! Somebody help me, please!
I got it! I used the persist.img of the global rom of the Xiaomi Mi Mix and the sensors came back! Apparently it's a universal file that caters to any device. You can close the topic!
Hi.. i intend to downgrade my asus Zenfone 3 Deluxe to lollipop, can you upload files needed to repair issues please?
thank you!
equinoks said:
Hi.. i intend to downgrade my asus Zenfone 3 Deluxe to lollipop, can you upload files needed to repair issues please?
thank you!
Click to expand...
Click to collapse
Really??
Ryder. said:
Really??
Click to expand...
Click to collapse
sorry from nougat to marshmallow
There isn't android lollipop for the asus zenfone 3 series. They came out with marshmallow.
AndreSantoro84 said:
I got it! I used the persist.img of the global rom of the Xiaomi Mi Mix and the sensors came back! Apparently it's a universal file that caters to any device. You can close the topic!
Click to expand...
Click to collapse
HELLO! I'm having a similar issue. 5 times my Zs570kl end up stuck in Asus logo boot screen after being charging all night (with alarming overheating) . I had to wipe the device with factory reset every time to get it working again. Last time, when finally booted up, all sensor were off, and I couldn't make them work no matter how much I try factory reseting again. I think i could try to install the persist.img file you mention, could you help me to find it? Thanks so much in advance for your help.
Asus Z016D (ZS570KL) 2.15 SKU WW_user_5.15.44.2562 build
equinoks said:
Hi.. i intend to downgrade my asus Zenfone 3 Deluxe to lollipop, can you upload files needed to repair issues please?
thank you!
Click to expand...
Click to collapse
Come on. To downgrade, you need to download the official rom from the Asus website (version WW-4.12.40.1698 - do not forget to check if your device is 2.15 or 2.4 ghz). Downloaded, need to put the rom inside a micro sd card (can not be internal storage, need to be in sd). In addition, it must be with the original recovery (the version is indifferent), if it is in TWRP it will not work. Once you have done this, you will have access to recovery mode, go to the "install zip from sd card" option, locate the zip file of the rom and install it, and just wait. Having problems, report here.
cazadormoron said:
HELLO! I'm having a similar issue. 5 times my Zs570kl end up stuck in Asus logo boot screen after being charging all night (with alarming overheating) . I had to wipe the device with factory reset every time to get it working again. Last time, when finally booted up, all sensor were off, and I couldn't make them work no matter how much I try factory reseting again. I think i could try to install the persist.img file you mention, could you help me to find it? Thanks so much in advance for your help.
Asus Z016D (ZS570KL) 2.15 SKU WW_user_5.15.44.2562 build
Click to expand...
Click to collapse
Hello! To reinstall the sensors is very simple (both work to find out the way, but then it gets simple hahaha). Download the adb files (it is available here in the forum, and inside the folder put the persist.img that I will make available here.) Access the fastboot mode on the device, connect to the computer, and open the command prompt inside the folder. Open the CMD, type the following command line: fastboot flash persist persist.img and press enter. The file will be rewritten and after that the sensors will be reconfigured. Restart the device. Having problems, report here.
Solved!
AndreSantoro84 said:
Hello! To reinstall the sensors is very simple (both work to find out the way, but then it gets simple hahaha). Download the adb files (it is available here in the forum, and inside the folder put the persist.img that I will make available here.) Access the fastboot mode on the device, connect to the computer, and open the command prompt inside the folder. Open the CMD, type the following command line: fastboot flash persist persist.img and press enter. The file will be rewritten and after that the sensors will be reconfigured. Restart the device. Having problems, report here.
Click to expand...
Click to collapse
THANK YOU ANDRE!!! I'm really really happy to tell you that everything worked PERFECTLY. I wasn't sure if I need to unlock the bootloader and flash root first, so I tried to do it. I've been able to unlock the bootloader, but for some reason, when I flash the bootroot.img following the instructions from this post - https://forum.xda-developers.com/ze...v-liftoff-zs570klpro-official-unlock-t3557276 -, I get the asus logo boot loop. Anyway, without the root I flash the persist file and, as you said, all the sensors were reconfigured.
Again, muito muito obrigado!!!
cazadormoron said:
THANK YOU ANDRE!!! I'm really really happy to tell you that everything worked PERFECTLY. I wasn't sure if I need to unlock the bootloader and flash root first, so I tried to do it. I've been able to unlock the bootloader, but for some reason, when I flash the bootroot.img following the instructions from this post - https://forum.xda-developers.com/ze...v-liftoff-zs570klpro-official-unlock-t3557276 -, I get the asus logo boot loop. Anyway, without the root I flash the persist file and, as you said, all the sensors were reconfigured.
Again, muito muito obrigado!!!
Click to expand...
Click to collapse
If you want to root, flash the twrp and then supersu zip from twrp
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.
TWRP+Encryption Disabling+Magisk Root
Actually there is TWRP for this model ported from alcatel by NickyNS. You can pick up it from here.
You can flash it with fastboot along with the patched lk which is to disable the "Orange state" message. After flashing it you should enter TWRP right with the next step (without booting to OS). On this stage you might want to disable encryption in order to have full-fledged backup-recovery option in TWRP next time you use it. To do so you will have to format data partition. After that step you will loose all you applications and user data for them, so you should backup it previously. After you format the data, flash Magisk first, then flash encryption disabling script from this post. Now you can boot to OS.
Note, that attached TWRP is only valid for firmware CUBOT_KINGKONG_MINI_9101C_V06_20191121. Cubot has released a new one and you can try to use the TWRP with it, but there is no guarantee it will work correctly.
well well, finally and serranoltexx successor?
i ordered one yesterday and am looking forward to get an suiteable replacement for my S4 MiNi [serranoltexx]
moctir said:
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.
Click to expand...
Click to collapse
I saw 2 places talking about TWRP in King Kong Mini but I don't know if is safe:
- https://unofficialtwrp.com/unofficial-twrp-3-3-1-root-cubot-king-kong-mini/
- https://www.getdroidtips.com/twrp-recovery-cubot-kingkong-mini/
robrazil said:
I saw 2 places talking about TWRP in King Kong Mini but I don't know if is safe:
- https://unofficialtwrp.com/unofficial-twrp-3-3-1-root-cubot-king-kong-mini/
- https://www.getdroidtips.com/twrp-recovery-cubot-kingkong-mini/
Click to expand...
Click to collapse
Based on the second poster here and someone else who sent me a pm, I believe the TWRP is safe, I haven't tested it myself yet but I plan to at some point and will post here when I do. When I'm using it as my primary device and everything is working okay it's hard to justify messing with it more at the moment!
Tom Mix said:
i ordered one yesterday and am looking forward to get an suiteable replacement for my S4 MiNi [serranoltexx]
Click to expand...
Click to collapse
I did it to replacement my old Samsung J1 ace, very similar of S4 Mini, and I'm not regretful for that.
---------- Post added at 01:37 PM ---------- Previous post was at 01:08 PM ----------
moctir said:
Based on the second poster here and someone else who sent me a pm, I believe the TWRP is safe, I haven't tested it myself yet but I plan to at some point and will post here when I do. When I'm using it as my primary device and everything is working okay it's hard to justify messing with it more at the moment!
Click to expand...
Click to collapse
I understood but the point is if the TWRP source is confiable. I asked the official TWRP Team about the unofficials TWRP on websites in my last post, and they answer: "Hello, we do not run that site, so I cannot confirm the validity of their images."
So, I wonder how safe the unofficial TWRP images are.
moctir said:
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!!
Click to expand...
Click to collapse
This is a very important information. When I did a update firmware the usb cable disconnected and the mobile died. Black screen. The side buttons died too. Only blue led turn on when the usb cable is connected on PC. The windows 10 only recognized the mobile as "unknown usb device (device descriptor request failed)". I thought that had lose the mobile. A few days later when I connect the mobile in the PC, the battery image was showed on screen with 18% of charge and I saw in that moment that I could flash the firmware again.
I flashed official firmware and the mobile worked again but now it died again... because I did a wrong recovery boot. I will wait discharge the battery again. :crying:
robrazil said:
This is a very important information. When I did a update firmware the usb cable disconnected and the mobile died. Black screen. The side buttons died too. Only blue led turn on when the usb cable is connected on PC. The windows 10 only recognized the mobile as "unknown usb device (device descriptor request failed)". I thought that had lose the mobile. A few days later when I connect the mobile in the PC, the battery image was showed on screen with 18% of charge and I saw in that moment that I could flash the firmware again.
I flashed official firmware and the mobile worked again but now it died again... because I did a wrong recovery boot. I will wait discharge the battery again. :crying:
Click to expand...
Click to collapse
Yes, indeed there were three times I thought I had totally bricked and each time I was so annoyed with myself! The key is to not charge it much until you are happy with the ROM you put on.
The amount of drivers I tried to use for different OS' when I got that "unknown USB device" on Windows and Linux didn't detect it was all a waste of time!
Well... the battery image appeared again and I uploaded firmware again. I installed the Magisk in the boot recovery, because this only way to install the Magisk on devices that are using system-as-root, but the Magisk disable my 2 SIM cards. When I boot without Magisk, all back to normal.
I serched for any solution for that but I didn't find.
So, my conclusion is that the Magisk not works to Cubot King Kong Mini. How can I stay with a phone with no SIM card?
I give up.
For me I can only get root when I patched Magisk to Recovery and then boot to Recovery and it doesn't see my SIM card but I have root, so I reboot every time I need root which is a bit annoying...
It is very complicated everytime when need "root", to have power off and on the mobile in recovery boot mode. Besides that, run out of SIM card working is not an option.
I will try to get support of this issue with Magisk Team.
Thank you for share your experience.
Ce3apyc said:
Actually there is TWRP for this model ported from alcatel by NickyNS. You can pick up it from here.
You can flash it with fastboot along with the patched lk which is to disable the "Orange state" message. After flashing it you should enter TWRP right with the next step (without booting to OS). On this stage you might want to disable encryption in order to have full-fledged backup-recovery option in TWRP next time you use it. To do so you will have to format data partition. After that step you will loose all you applications and user data for them, so you should backup it previously. After you format the data, flash Magisk first, then flash encryption disabling script from this post. Now you can boot to OS.
Note, that attached TWRP is only valid for firmware CUBOT_KINGKONG_MINI_9101C_V06_20191121. Cubot has released a new one and you can try to use the TWRP with it, but there is no guarantee it will work correctly.
Click to expand...
Click to collapse
Hello,
Does anybody can confirm, that this is working with the new firmware?
I tried the TWRP a few days ago and was able to boot to it but I couldn't mount it to see my files, it asked for a password and I tried "default_password" and creating a password for the phone but that also didn't work. A possibility is to change the file format to ext2 and then to ext4 but I didn't want to try it when I couldn't back it up.
moctir said:
I tried the TWRP a few days ago and was able to boot to it but I couldn't mount it to see my files, it asked for a password and I tried "default_password" and creating a password for the phone but that also didn't work. A possibility is to change the file format to ext2 and then to ext4 but I didn't want to try it when I couldn't back it up.
Click to expand...
Click to collapse
You will not be able to mount and/or use the backup feature of the TWRP until you disable an encryption by formating the data partition and running the script (just press "Cancel" in the TWRP to be able to do that when it asks for the password). Read my original post very carefully. There is a complete sequence of steps in it. Have you tried the TWRP with the last firmware? How did the rest of the system work?
Ce3apyc said:
You will not be able to mount and/or use the backup feature of the TWRP until you disable an encryption by formating the data partition and running the script (just press "Cancel" in the TWRP to be able to do that when it asks for the password). Read my original post very carefully. There is a complete sequence of steps in it. Have you tried the TWRP with the last firmware? How did the rest of the system work?
Click to expand...
Click to collapse
I'm using treble AOSP Android 9 so not the latest firmware. I thought disabling the verification when installing that would be enough but maybe I do need to do those other steps. I can see the /system directory through TWRP so that's probably because that's the one I flashed, but I can't see the internal storage otherwise.
moctir said:
I tried the TWRP a few days ago and was able to boot to it but I couldn't mount it to see my files, it asked for a password and I tried "default_password" and creating a password for the phone but that also didn't work. A possibility is to change the file format to ext2 and then to ext4 but I didn't want to try it when I couldn't back it up.
Click to expand...
Click to collapse
You need to put the "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip" file into SD card or internal memory to install by TWRP. This file disable the asking of password. Worked for me.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
robrazil said:
You need to put the "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip" file into SD card or internal memory to install by TWRP. This file disable the asking of password. Worked for me.
Click to expand...
Click to collapse
Thanks, I'll check it out!
Anyone else having problems with sensors on this phone? Rotating and compass do not work for me. That's what you get for buying a cheap Chinese phone, I guess.
EDIT: Downgrading firmware back to CUBOT_KINGKONG_MINI_9101C_V06_20191121 seems to fix some problems, rotation works, but compass is still buggy.
Never tried compass but haven't had any problems with rotation.
Tried to install root on a friends kkm but I can't get it working in the os. Is there any chance to get it working there? I am only able to get root access in twrp. Maybe an gsi with root is that possible?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- = EDGE PURE EDITION = -
Custom ROM based on Stock firmware RPDS31.Q4U-39-26-4-2
This custom ROM uses stock kernel without modification. The source for the stock kernel is not released by the OEM.
Preliminary requirements:
- Unlocked bootloader.
- New and Clean Stock firmware is required!
- TWRP installed;
- Micro SDCard or USB flash drive should be formatted to exFAT.
What's done:
- Removed the restriction on writing to the system, which in Android 10 is in Read Only (r/o) mode by default, which eliminates the possibility of modifying it. In this firmware it is possible to mount the system in Read Write (r/w) mode. Encryption is preserved in this case.
- System passes SafetyNet test, device is certified (in Magisk settings activate "Magisk Hide" function, in "Magisk Hide" tab give permission for Google Play Services, perform Google Play reset);
- Cleaned and lightened the system;
- Built in additional system color accents;
- Built in and updated to the latest versions at the time of firmware and Apps release . YouTube removed, because I use YouTube Vanced;
- Installed apps AdAway ad blocker, Command Center 2;
- Ringtones, notifications, alarms sounds have been replaced.
🛠 Installation:
1. Extract the system image from the archive (see tab "Download") and copy it to the SD Card.
Also copy the "Magisk Installer" archive Magisk-disable-dm-verity-v21.4.zip in to the SD Card.
2. Reboot the device into bootloader mode and then into TWRP.
3. Installing the ROM image. In the "Install" tab in the lower right corner, click the "Install img" button and select the firmware image. A window will open, where you will need to select the "Super" partition. "Swipe to confirm".
4. Go to the "Reboot" section and reboot the device back to Recovery.
5. Go to "Wipe" and do a "Swipe to Factory Reset ".
6. Install "Magisk-disable-dm-verity-v21.4.zip". Reboot in to the System.
7. When the boot is complete make the initial settings.
8. Launch the "Magisk Manager" app and update it. You will be asked to configure the work environment. Agree. Phone will automatically reboot itself when setup is done.
Download
Edge_R_Pure_Edition_02-1
Edge_Q_Pure_Edition_nowrz_04-2
Advanced
YouTube Vanced v.14.21.54 Black Magisk
Proven, absolutely trouble-free version of YouTube Vanced.
To prevent in Play Market from updating in to the stock YouTube app, you need to add empty file with the name "enable_detach" (without extension) into the folder "/cache" (at the root of file system) using RootExplorer and rebooting your phone. One minute after the reboot, the application will unbind from the Market.
Enjoy!
Can i Flash from Lineage or need stay in stock?
VitilinVk said:
Can i Flash from Lineage or need stay in stock?
Click to expand...
Click to collapse
"New and Clean Stock firmware is required"
Upgraded Edge Pure Edition!
- created an image in a different format which reduced its size by 6 GB;
- full mount of system in r/w and r/o, allowing the system to boot up fully if you forget to put the system in r/o after making edits to the system partitions;
- updated GApps to the base of 27/02/21.
I'm not sure if you actually know the rules but wrz are not allowed
Upgraded Edge Pure Edition!
- updated ROM to the latest versions of stock firmware QPD30.114-80-4 (09 March 2021) ;
- updated GApps to the base of 12/03/21.
Upgraded Edge Pure Edition!
- Chrome bug fixed
Updated the ROM to a version based on Android 11(R).
Anyone using this daily?
I use. Why can't this ROM be used as the main firmware?
Hi, I tried installing the android 11 version of this from after clean restoring to stock. I installed the .img to the super partition and the phone wont boot. I get the "unable to open block device /dev/block/loop (20, 19, 18, 17): no such device or address. Any help? Thanks
Have you fully read and followed all the points in the instructions? Have you installed Magisk?
To install Edge_R_Pure_Edition, the firmware RPD31.Q4U-39-26-4, Android 11, must be installed on the device.
Download Stock Android 11
Nicktsaab said:
I get the "unable to open block device /dev/block/loop (20, 19, 18, 17): no such device or address.
Click to expand...
Click to collapse
This message appears because TWRP is not adapted to Android 11. Ignore it.
ilia3367 said:
Have you fully read and followed all the points in the instructions? Have you installed Magisk?
To install Edge_R_Pure_Edition, the firmware RPD31.Q4U-39-26-4, Android 11, must be installed on the device.
Download Stock Android 11
Click to expand...
Click to collapse
Ahh thank you, I was trying to install on the Android 10 base. Thanks!
what is the difference between r and q? android 10 and 11 i assume?
also ive been out of the rom loop for quite a while (lg g8, just got unlock like a month ago), what is wrz and why is it not allowed? just curious.
im having a weird issue. i bought 2 edges recently, and wanted to install this rom. both are on final android 10 firmware, and im flashing the q img. obviously both are bootloader unlocked and using twrp 3.5.2.
i followed instructions on one, and it went perfectly fine no issues. on the second whenever i flash the image it wont boot and the twrp log has a few errors about partitions. also there are 2 super partitions listed. even restoring my bone stock twrp image or flashing the factory fimware i have the same issue and the twin super partitions persist. the phone will boot on the stock rom fine however.
edit: weirdness continues, now all of the sudden the rom image flashed perfectly fine, when i rebooted back to twrp for magisk.zip i had no errors. however there STILL is 2 supers listed. but i flashed magisk and booted to system... and it boots. idk.
in the select partition to flash to menu the partitions listed (in order) are: boot, dtbo, boot logo, recovery, super, vbmeta, vbmeta system, super. ive tried both instances of super and both had problems except for this time where it succeeded (i did the first instance this time).
i should also note that this was like this when i made my initial twrp backup, there were 2 super partitions in the backup menu. but, the other phone that had no issues, did NOT have 2 super partitions at any point. again... idk.
Unfortunately, I didn't understand a lot of it, because I don't know English very well.
The fact that in TWRP in Backup you see two Super partitions, it's not a big deal. Choose both, but in fact your backup will have one Super partition.
its just strange but i guess if it works.
but im also having issues with applications. for one, the asus gallery and file browser that are bundled always ask for storaage permissions, even if i grant them they wont launch and keep asking for permissions. wipe data, force stop, grant permissions again, nope they still ask for permissions. i dont know whats going on with them. also i cant set a picture wallpaper. not with gallery, google photos, google gallery, nothing. i get a notification that says "error, could not load media" every time i do it no matter what app i try to use. live wallpapers are fine.
There should be no such problems. This behavior can only be when you try to make these applications (Asus Gallery, Asus File Manager) system applications using, for example, RootExplorer.
I don't have this problem even after restoring a backup.
Install ROM on a clean, re-installed stock firmware.
Hey guys.. Ive been a visitor in XDA forums for quite a while... And i been running root and custom FW with more or less every samsung from S2 and up...
But i just got my self a note10+ (atleast thats what ive been told) and i wanted to root it up and throw a custom FW on it to run in Samsung Dex...
So i succeded updating the FW. I unlocked the bootloader in dev. options. and unlocked it again in download mode by holding the vol. up. key!
But since then i had problems... every time i run a FW in Odin... Then if i dont get a error saying
SW REV. CHECK FAIL(BOOTLOADER) DEVICE: B BINARY 7
pit_flash_binary - Unsupported version
Then i succeds but when its going to erase everything after the reboot from download mode then it starts up and stops right after... And then i can only go recovery mode and download mode... How do i just write the correct firmware and have it start up like normal... just wanna undo it all... Do i need some kind of samsung support software in windows? and how do i know if it is a note10+ ... Even though download mode says SM-N975F... But still i get error when i flash a FW downloaded with Frija for that model...
Hope to get some help
oh btw... it connects as this when im in download mode:
"Checking Connected Devices: SAMSUNG Mobile USB Modem #2 ( COM12 )"
is that normal?
bump?
Hey there,
SW REV. CHECK FAIL(BOOTLOADER) DEVICE: 8 BINARY 7
Click to expand...
Click to collapse
This, as far as I understand just means that the bootloader on your phone is on a newer version than the one in the firmware you're trying to flash. Usually flashing just stops there.
Then i succeds but when its going to erase everything after the reboot from download mode then it starts up and stops right after...
Click to expand...
Click to collapse
You COULD try to simply boot into recovery and wipe the device once, the phone would usually do that on its own but sometimes fails. Mind describing what exactly happens?
how do i know if it is a note10+ ... Even though download mode says SM-N975F...
Click to expand...
Click to collapse
For that, you either need the original packaging or just trust on what Odin-mode is telling you.
But still i get error when i flash a FW downloaded with Frija for that model...
Click to expand...
Click to collapse
I kinda don't trust Frija. For me, Bifrost always worked like a charm. Use it to download the firmware for your SM-N975F and give it your correct region code.
For flashing, some people use Heimdall, I think Odin is pretty simple (as far as simplicity in modding goes).
By the way, if all fails, you could try installing LineageOS 19.1, throw in openGAPPS for Googles apps and Magisk/Lygisk for root (if needed).
Good luck and have fun!
Cheers!
I found out i got EXACKLY the same issue as the guy writing on this thread:
Need help with semi-bricked Note 10 Plus (SM-N975F) - Stuck on recovery/download mode
Didn't know where to post this exactly, to be honest. This will be a long post I was flashing AOSP roms in the phone. Tried to go back to One UI for the VoLTE thing In one of the AOSP roms I couldn't install it in Lineage Recovery (older version...
forum.xda-developers.com
Nic0_ said:
You COULD try to simply boot into recovery and wipe the device once, the phone would usually do that on its own but sometimes fails. Mind describing what exactly happens?
Click to expand...
Click to collapse
Already tryed still nothing... But what happens after a 100% succes in Odin is:
Then it reboots and after a few secs it says "Erasing device" for like 0.5 sec... And then it only goes black screen... At black screen then i can only go download mode if i press both volume buttons at the same time for 1 sec. Or recovery mode if i press vol up and power. And thats only if i have a USB-C connected ofcourse.
And whats the issue is... when it stops erasing the device... Why does it stops after 0.5 secs? it normally goes like 2-5 secs ... But also ... After it stops and in black screen... If i continue into download mode and open up the bootloader then...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I been around TWRP, Original recovery and Lineage recovery... But as the guy writes on the other thread. Then it shows 0 MB on the data partition, and i have to format it before it shows up again with 223 (or something)GB again...
Hey there,
Could you try switching file systems around? TWRP lets you format your partitions with stuff like ext4, f2fs and some other file systems. On several custom ROMs, the file system sometimes is the difference between a system working or bootlooping.
Good luck and have a nice day.
Cheers!
Already tryed exfat and f2fs and then back to ext4
I might have found a solution
I tried to update firmware N9750 android 11 to android 12 with (Ap file + odin patched). I don't flash bl ,cp,csc files . the phone screen shows a software error, need to open the smart switch software on the computer to recover. I open the smart switch on the computer and it does not recognize the phone. odin patched still recognizes the phone is connected. i reset odin and flashed 1 BL file. phone booted again with bootloader + AP file is android12. and modem and csc are android 11
1: Try flash combination firmware?
2 : Try download firmware stock new bootloader
Download odin patched
Try flash firmware files one by one
restart phone go download mode flash file BL ..done
restart phone go download mode flash file AP
restart phone go download mode flash file CP
restart phone go download mode flash file CSC
If ok flash full 5 file
sorry my english is not good
someone could help please?
S20 FE bootloop after security update
So I never posted here but I usually pass by some topics so sorry for any mistake in creating this discussion. Today I deleted some stuff from my S20 FE and downloaded via OTA the march security update in my device, then I was caught by surprise...
forum.xda-developers.com