Develop Bugs

[Q] Explanation Needed (Post-Root to Un-Root)

Okay, so I've just rooted my Nexus 7 tablet after being told a custom ROM would fix my GPS issues with my N7v2. I'm familiar with the rooting process, having done it to my HTC One. I rooted it successfully, installed the SuperSU and TWRP. Everything went smoothly, and then I realized, only minutes later, after browsing XDA, that Google JUST released an OTA to fix the issues.
So I browsed around and found this post: http://forum.xda-developers.com/showpost.php?p=44888268&postcount=97&nocache=1&z=675614455249160
I followed the instructions. I opened a CMD in the correct folder and ran the flash-all.bat. It ran... HOWEVER it generated a few errors. The errors in CMD were that it was unable to find files that are contained within the img-razor-jss15q.zip folder that was inside the downloaded TGZ archive. When I finally figured out how to use 7zip (never had a use for it before now), I ended up with a folder that looked like this (which is where I ran the CMD):
{
"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"
}
As you can see the image-razor-jss15q.zip was still inside that folder. I did not unzip it because I didn't know if I was supposed to or not.
At any rate, the tablet SEEMS to be fine. I rebooted into the bootloader and then to recovery and got the android with an exclamation mark which is what I ASSUME I'm supposed to have. TWRP is gone, at least.
I also looked at the system information and it's showing the build number as JSS15Q.
So my questions are simple:
1. Did I do this correctly and are the errors normal?
2. If "no" to 1, what do I need to do to fix it?
Edit: It appears I've put this in the wrong section, I apologize. I'd appreciate it if a moderator moved it for me. Thanks!!

Your first error was not correct but you figured it out and the next time around it was done right. If your tablet says JSS15Q then you successfully installed it
Twrp gone means the stock recovery in the image zip flashed correctly

Seems you've already answered your own question.
The guide could have probably better explained to extract the actual image files to your ADB/Fastboot folder.
I prefer to reflash the relevant images individually with
Code:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot erase system
fastboot flash system system.img
fastboot erase data
fastboot flash data data.img
fastboot erase cache
fastboot flash cache cache.img
I exclude the bootloader image when reflashing unless necessary due to the remote chance of bricking your device if it fails to flash completely.
http://forum.xda-developers.com/showthread.php?t=2404833

sfhub said:
Your first error was not correct but you figured it out and the next time around it was done right. If your tablet says JSS15Q then you successfully installed it
Twrp gone means the stock recovery in the image zip flashed correctly
Click to expand...
Click to collapse
Ah! The OP of that useful information! Thank you for that!
At any rate, regardless of the error, it still managed to work correctly. Still, though, while waiting for a response I figured "Well, I can just redo it but after extracting the relevant files to the main folder. This time it did not give me that set of errors but instead gave me these:
http://i.imgur.com/k6Mgn2I.png
I could not find those files anywhere in the included files so I'm not really worried about it because at this point the tablet seems to be working fine.

Username invalid said:
Seems you've already answered your own question.
The guide could have probably better explained to extract the actual image files to your ADB/Fastboot folder.
I prefer to reflash the relevant images individually with
Code:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot erase system
fastboot flash system system.img
fastboot erase data
fastboot flash data data.img
fastboot erase cache
fastboot flash cache cache.img
I exclude the bootloader image when reflashing unless necessary due to the remote chance of bricking your device if it fails to flash completely.
Click to expand...
Click to collapse
Well I wouldn't have rooted it in the first place had I known about the OTA. Regardless, I'm not sure what you mean by "you answered your own question"...?
I really don't care about the method so long as it works. I'm not actually interested in rooting this tablet, really. I love it as-is. I'll reserve all my tweaking for my phone.

Just a heads up for anyone who has TWRP or CWM installed, you can use this flashable .zip to update to latest OTA update. Download update. Reboot to recovery. Wipe Cache/Dalvik. Flash .zip. Reboot and you're done. Worked pefectly on mine and you won't lose your recovery in the process.
Edit: Just wanted to point out, this is obviously for those running stock ROM.

railed said:
Just a heads up for anyone who has TWRP or CWM installed, you can use this flashable .zip to update to latest OTA update. Download update. Reboot to recovery. Wipe Cache/Dalvik. Flash .zip. Reboot and you're done. Worked pefectly on mine and you won't lose your recovery in the process.
Click to expand...
Click to collapse
Hey cool, thanks for that! I'm sure people will find this useful!

wolfbuck22 said:
Well I wouldn't have rooted it in the first place had I known about the OTA. Regardless, I'm not sure what you mean by "you answered your own question"...?
I really don't care about the method so long as it works. I'm not actually interested in rooting this tablet, really. I love it as-is. I'll reserve all my tweaking for my phone.
Click to expand...
Click to collapse
You can still receive OTAs with root. You just need to reflash the stock recovery which only takes a few seconds.
wolfbuck22 said:
It ran... HOWEVER it generated a few errors. The errors in CMD were that it was unable to find files that are contained within the img-razor-jss15q.zip folder that was inside the downloaded TGZ archive.
At any rate, the tablet SEEMS to be fine. I rebooted into the bootloader and then to recovery and got the android with an exclamation mark which is what I ASSUME I'm supposed to have. TWRP is gone, at least.
I also looked at the system information and it's showing the build number as JSS15Q.
So my questions are simple:
1. Did I do this correctly and are the errors normal?
Click to expand...
Click to collapse

Username invalid said:
You can still receive OTAs with root. You just need to reflash the stock recovery which only takes a few seconds.
Click to expand...
Click to collapse
I only tried the flash-all.bat once. It ran with the errors. Tablet still worked even with errors. Had regular recovery back and everything.
Though, I wasn't satisfied so I went back and unzipped those files to the main folder and re-ran the flash-all.bat again. That time it gave me a different set of errors but the tablet seems to be working just fine so I'm not exactly worried about it.

wolfbuck22 said:
Ah! The OP of that useful information! Thank you for that!
At any rate, regardless of the error, it still managed to work correctly. Still, though, while waiting for a response I figured "Well, I can just redo it but after extracting the relevant files to the main folder. This time it did not give me that set of errors but instead gave me these:
http://i.imgur.com/k6Mgn2I.png
I could not find those files anywhere in the included files so I'm not really worried about it because at this point the tablet seems to be working fine.
Click to expand...
Click to collapse
Those missing .sig files are expected. Google did not sign their factory restore images which is why you need an unlocked bootloader to flash them

sfhub said:
Those missing .sig files are expected. Google did not sign their factory restore images which is why you need an unlocked bootloader to flash them
Click to expand...
Click to collapse
Great. Thank you so much, everything appears to be working fine at this point.
I may venture into the custom ROM realm later but for now I'm quite happy with the Nexus 7's stock ROM (never had a pure Android device before).

[Help] I think I may have bricked my phone

Long story short, I installed Cyanogenmod and TWRP only to be continually bombarded with those stupid warnings Google has recently introduced (the yellow one about the unlocked bootloader and custom ROM and the red one about the software being corrupt) as well as a warning about the software being corrupt after the phone had booted into the ROM. In an effort to get rid of all 3 warnings I started experimenting (couldn't find anything online) and so re-locked the bootloader both via adb as well as via developer options > unmarked "enable bootloader unlocking". Now TWRP is throwing up a password prompt to decrypt the partition and passed that, my phone is no longer able to boot into Cyanogen as it just gets stuck at the boot screen logo.
I've tried wiping Dalvik, cache, system etc. but so far its not many any difference. I thought about installing the vanilla ROM to hopefully bypass it but since I only have access to fastboot mode, I can't use the adb push command to transfer anything to the sdcard.
Am I screwed? :crying:

No you aren't, just enable OEM unlock and USB debugging. And flash a factory image and start over. There may be another way without flashing back to stock but I cant think of it ATM.

The problem is I can't do that. Attempting to use the OEM unlock command is blocked by the bootloader setting in the ROM. An oh so nifty feature of android v6. And since I can't boot into the ROM, I don't see anyway of unlocking the bootloader in the first place.
What's truly retarded is that u could do this on any android v6 device. As far as I can tell, it's a replicable way to brick any phone =\

if you can still get into TWRP you're fine. You may lose all of the data in the encrypted partitions though.
if you can't perhaps you can flash via ADB.
for future reference, never do OEM lock if you're not completely stock.

I can get into twrp but it doesn't help me any. I can't wipe any partitions because they're encrypted by the locked bootloader. I have no idea what else I can do.

dccxviii said:
I can get into twrp but it doesn't help me any. I can't wipe any partitions because they're encrypted by the locked bootloader. I have no idea what else I can do.
Click to expand...
Click to collapse
can you flash on top of the locked partitions?

I may not be explaining clearly. I have nothing I can flash. With the partitions locked, the .IMG is hidden from twrp. I can't push anything to the sdcard either as I have no way of executing that command whilst in recovery or fastboot mode?

dccxviii said:
I may not be explaining clearly. I have nothing I can flash. With the partitions locked, the .IMG is hidden from twrp. I can't push anything to the sdcard either as I have no way of executing that command whilst in recovery or fastboot mode?
Click to expand...
Click to collapse
if im not mistaken, you can use an OTG cable and access those files via TWRP

2x4 said:
if im not mistaken, you can use an OTG cable and access those files via TWRP
Click to expand...
Click to collapse
Don't know what a OTG cable is. I also don't see the point. The cyaanogenmod IMG is useless as it clearly was never designed to boot on a device with a locked bootloader. Otherwise I'd be able to get into the ROM to begin with.
The only way I see that I can resolve this is by unlocking the bootloader and bypassing the ROM bootloader lock setting without booting into the ROM to do it. That's the lynchpin that's screwing me over.
Thanks for trying to help.

dccxviii said:
Don't know what a OTG cable is. I also don't see the point. The cyaanogenmod IMG is useless as it clearly was never designed to boot on a device with a locked bootloader. Otherwise I'd be able to get into the ROM to begin with.
The only way I see that I can resolve this is by unlocking the bootloader and bypassing the ROM bootloader lock setting without booting into the ROM to do it. That's the lynchpin that's screwing me over.
Thanks for trying to help.
Click to expand...
Click to collapse
youd have to flash the stock image not the CM image if this was even going to work, since that one can work with the bootloader locked.
this is an otg cable.
{
"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"
}

2x4 said:
youd have to flash the stock image not the CM image if this was even going to work, since that one can work with the bootloader locked.
this is an otg cable.
Click to expand...
Click to collapse
Well the issue there is as I've said before, how can I push the file to the phone when I dont have access to the adb push command? There is no pre exiating vanilla .IMG on the phone. Only the CM .IMG I used in the first place.

dccxviii said:
Well the issue there is as I've said before, how can I push the file to the phone when I dont have access to the adb push command? There is no pre exiating vanilla .IMG on the phone. Only the CM .IMG I used in the first place.
Click to expand...
Click to collapse
I was saying put the stock image on a USB drive, plug USB drive into OTG cable, plug OTG cable into phone, boot into TWRP recovery, mount USB-OTG drive, flash from there

Lol. Fun times. If people simply read, these things wouldn't happen.
This ought to work.
http://forum.xda-developers.com/showthread.php?t=3053783
Sent from my Nexus 5X using Tapatalk

PiousInquisitor said:
Lol. Fun times. If people simply read, these things wouldn't happen.
This ought to work.
http://forum.xda-developers.com/showthread.php?t=3053783
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thanks for the link, Good to know.
I was aware locking it would cause this issue but wasn't aware someone had already found a solution.
thanks!

2x4 said:
youd have to flash the stock image not the CM image if this was even going to work, since that one can work with the bootloader locked.
this is an otg cable.
Click to expand...
Click to collapse
Interesting idea. I bought one (micro USB to USB A) and tried to mount it but no dice. TWRP has 2 radials under selectable storage to mount. Internal and USB OTG. But selecting the "USB OTG" radial doesn't do anything. It doesn't move the highlighted radial to that option. Could it be due to my OTG setup? USB A female to micro USB male to micro USB female to USB C male ( micro usb female to usb c male part came with the phone since usb c is not popular yet).
Edit: OK, i finally figured out a way to transfer files over. No commands required (File explorer to the rescue). That said, does anyone know where I can get a vanilla .img? Googles official page only has them in .tgz. Tried extracting the .tar and then extracting the files in the .tar it and re-compressing in .zip that TWRP can understand (TWRP therefore sees my created zip file) but i just hit an error: "Could not find 'meta-inf/com/google/android/update-binary" etc. when trying to install it.

PiousInquisitor said:
Lol. Fun times. If people simply read, these things wouldn't happen.
This ought to work.
http://forum.xda-developers.com/showthread.php?t=3053783
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Doesn't work. Error: "Failed (remote: device is locked. cannot erase). I think its coming up against the same issue TWRP's built in formatting functions get hit by in this scenario.
Looks like this solution suffers from the same chicken and egg scenario i'm currently in.
Honestly, now that Google has introduced these spam error messages even when you're able to run CM, it ain't worth it. I may have to abandon CM in favour of vanilla Android seeing as there doesn't appear to be a way around them *sigh*.

dccxviii said:
Interesting idea. I bought one (micro USB to USB A) and tried to mount it but no dice. TWRP has 2 radials under selectable storage to mount. Internal and USB OTG. But selecting the "USB OTG" radial doesn't do anything. It doesn't move the highlighted radial to that option. Could it be due to my OTG setup? USB A female to micro USB male to micro USB female to USB C male ( micro usb female to usb c male part came with the phone since usb c is not popular yet).
Edit: OK, i finally figured out a way to transfer files over. No commands required (File explorer to the rescue). That said, does anyone know where I can get a vanilla .img? Googles official page only has them in .tgz. Tried extracting the .tar and then extracting the files in the .tar it and re-compressing in .zip that TWRP can understand (TWRP therefore sees my created zip file) but i just hit an error: "Could not find 'meta-inf/com/google/android/update-binary" etc. when trying to install it.
Click to expand...
Click to collapse
Use 7Zip if you are on Windows. That will open the tar file and allow you to pull what you need.
Now that you figured out how to transfer files, put a rom zip on your phone and install it via TWRP. Then enable OEM Unlock and USB Debugging. Then do whatever you want with fastboot.
Sent from my Nexus 5X using Tapatalk

dccxviii said:
Doesn't work. Error: "Failed (remote: device is locked. cannot erase). I think its coming up against the same issue TWRP's built in formatting functions get hit by in this scenario.
Looks like this solution suffers from the same chicken and egg scenario i'm currently in.
Honestly, now that Google has introduced these spam error messages even when you're able to run CM, it ain't worth it. I may have to abandon CM in favour of vanilla Android seeing as there doesn't appear to be a way around them *sigh*.
Click to expand...
Click to collapse
Have you seen this thread:
http://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740
It may be your only way back.
Spam error messages? Do you mean the bootloader unlock warning that you can easily replace?
You could have used this tool:
http://forum.xda-developers.com/nex...-change-bootlogo-images-imgdata-tool-t3240052
Or flashed this zip:
http://forum.xda-developers.com/nexus-5x/themes-apps/bootloader-theme-material-bootloader-t3298420
*sigh*
Sent from my Nexus 5X using Tapatalk

SlimSnoopOS said:
Use 7Zip if you are on Windows. That will open the tar file and allow you to pull what you need.
Now that you figured out how to transfer files, put a rom zip on your phone and install it via TWRP. Then enable OEM Unlock and USB Debugging. Then do whatever you want with fastboot.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
That's the problem. Its impossible to do that without first unlocking the bootloader. And I can't unlock the bootloader because I can't get into the ROM. And I can't get into the ROM because its screwed by the locked bootloader. You begin to understand the infinite loop i'm in?
Attempting to flash any ROM other than (i hope) vanilla results in an error cascade as TWRP can't mount any of the partitions because its locked out by the locked bootloader to begin with. TBH I may hit the same issue with a vanilla ROM anyway as theoretically, it should suffer from the same issue. Namely TWRP's inability to mount/write to any partition due to the locked bootloader to begin with.

dccxviii said:
That's the problem. Its impossible to do that without first unlocking the bootloader. And I can't unlock the bootloader because I can't get into the ROM. And I can't get into the ROM because its screwed by the locked bootloader. You being to understand the infinite loop i'm in?\
Attempting to flash any ROM other than (i hope) vanilla results in an error cascade as TWRP can't mount any of the partitions because its locked out by the locked bootloader to begin with. TBH I may hit the same issue with a vanilla ROM anyway as theoretically, it should suffer from the same issue. Namely TWRP's inability to mount/write to any partition due to the locked bootloader to begin with.
Click to expand...
Click to collapse
You cant flash the stock images without an unlocked bootloader. Your only option is the LGUP Tool.
http://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740

Installing Custom ROM on Cubot KingKong Mini

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?

Lg G8 AT&T boot_b.bin lost, fastboot loop

hello my name is petrus and i have a lg g8 LMG820M ATT with unlocked bootloader, i installed a custom rom ArrowOS 12.1 that worked perfectly, however i went to root with qfil and accidentally ended up replacing boot_b.bin by boot_a.bin , now the phone is stuck on fast boot screen
it already starts directly in fastboot and the text "ACTICE A/B slot - _a" no longer appears on the fastboot screen, there was no backup of boot_b.bin so I don't know how to solve it
Is there anything I can do to get it back? Or did he become a piece of garbage?
{
"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"
}

vini14zimm said:
hello my name is petrus and i have a lg g8 LMG820M ATT with unlocked bootloader, i installed a custom rom ArrowOS 12.1 that worked perfectly, however i went to root with qfil and accidentally ended up replacing boot_b.bin by boot_a.bin , now the phone is stuck on fast boot screen
it already starts directly in fastboot and the text "ACTICE A/B slot - _a" no longer appears on the fastboot screen, there was no backup of boot_b.bin so I don't know how to solve it
Is there anything I can do to get it back? Or did he become a piece of garbage?
View attachment 5656703
Click to expand...
Click to collapse
No, not a piece of garbage lol. Given the tools available for the G8; qfil, the programmers firehose, engineering abl, it's almost impossible to brick the device.
So, lesson learned; always make a backup. It sounds like you copied the boot partition for the slot that had at&t rom on it, to the slot that had ArrowOS on it? If so, sounds like just finding a copy of the ArrowOS boot partition should work?
Which version are you running? Someone may have that boot partition available.

AsItLies said:
No, not a piece of garbage lol. Given the tools available for the G8; qfil, the programmers firehose, engineering abl, it's almost impossible to brick the device.
So, lesson learned; always make a backup. It sounds like you copied the boot partition for the slot that had at&t rom on it, to the slot that had ArrowOS on it? If so, sounds like just finding a copy of the ArrowOS boot partition should work?
Which version are you running? Someone may have that boot partition available.
Click to expand...
Click to collapse
yes that was exactly it, i understand i will never do anything without backup, i was using Arrow-v12.1-alphalm-UNOFFICIAL-20220627
so if someone has lg g8 and is using Arrow v12.1 alpham send boot_b.bin and I copy it using QFIL will my device boot again?

vini14zimm said:
yes that was exactly it, i understand i will never do anything without backup, i was using Arrow-v12.1-alphalm-UNOFFICIAL-20220627
so if someone has lg g8 and is using Arrow v12.1 alpham send boot_b.bin and I copy it using QFIL will my device boot again?
Click to expand...
Click to collapse
Well, if all that's changed is the boot partition it should boot again. But I checked on tele group and no one responded with it.
You may have to download the rom and see if you can extract the boot partition from it.

II have the same problem, were you able to solve it?

i need help

yonaikymatos said:
II have the same problem, were you able to solve it?
Click to expand...
Click to collapse
I'm trying to extract this boot_b.bin from the room that AsItLies said, but I'm not going to lie I don't have much knowledge of how to do this so I still haven't been able to extract this file
It's very difficult to extract one without knowing how to do it but I'm still trying

vini14zimm said:
I'm trying to extract this boot_b.bin from the room that AsItLies said, but I'm not going to lie I don't have much knowledge of how to do this so I still haven't been able to extract this file
It's very difficult to extract one without knowing how to do it but I'm still trying
Click to expand...
Click to collapse
Okay, think this is what you need. BUT!! I'm not 100% it is... SO! first thing you do is back up the boot image from the slot you want to replace it with this one. That way, if it doesn't work, you can just reflash the one you backed up and you're none the worse.
Second: IF, when flashing this image to the boot partition (loading it in qfil speak), you get a warning message about 'over flow of data' (or something to that effect), immediately stop, do not continue, as that's an indication it will not only not work but make your situation worse. Good luck
sorry, xda not allowing me to attach, follow this gdrive link for file.

vini14zimm said:
I'm trying to extract this boot_b.bin from the room that AsItLies said, but I'm not going to lie I don't have much knowledge of how to do this so I still haven't been able to extract this file
It's very difficult to extract one without knowing how to do it but I'm still trying
Click to expand...
Click to collapse
I already solved it I'm going to attach the boot_b .bin
https://drive.google.com/file/d/1DANvrF-iklHQxr3bIOixv9orD376oG8U/view
the file is boot-a Android 11 Canadienc.bin
flash using qfil on a boot_b

AsItLies said:
Okay, think this is what you need. BUT!! I'm not 100% it is... SO! first thing you do is back up the boot image from the slot you want to replace it with this one. That way, if it doesn't work, you can just reflash the one you backed up and you're none the worse.
Second: IF, when flashing this image to the boot partition (loading it in qfil speak), you get a warning message about 'over flow of data' (or something to that effect), immediately stop, do not continue, as that's an indication it will not only not work but make your situation worse. Good luck
sorry, xda not allowing me to attach, follow this gdrive link for file.
Click to expand...
Click to collapse
I put arrowOS-boot.img in place of boot_b.bin using Qfil but I'm still at the fast boot screen, is there anything else I can do?

yonaikymatos said:
I already solved it I'm going to attach the boot_b .bin
https://drive.google.com/file/d/1DANvrF-iklHQxr3bIOixv9orD376oG8U/view
the file is boot-a Android 11 Canadienc.bin
flash using qfil on a boot_b
Click to expand...
Click to collapse
for some reason it's not being possible to put your boot-a Android 11 Canadienc.bin in place of my boot_b.bin , when I try to get this message Send image fail:Firehose Fail:FHLoader Failrocess fail , it doesn't seem like a good sign

vini14zimm said:
for some reason it's not being possible to put your boot-a Android 11 Canadienc.bin in place of my boot_b.bin , when I try to get this message Send image fail:Firehose Fail:FHLoader Failrocess fail , it doesn't seem like a good sign
View attachment 5659247
Click to expand...
Click to collapse
Don't use a usb 3.0 port when using qfil. You have to use a usb 2.0 port. Qfil is old software and was not designed for the higher speeds.
This is important whether making a backup of a partition of flashing a partition, either way with 3.x ports the image can get corrupted.

AsItLies said:
Don't use a usb 3.0 port when using qfil. You have to use a usb 2.0 port. Qfil is old software and was not designed for the higher speeds.
This is important whether making a backup of a partition of flashing a partition, either way with 3.x ports the image can get corrupted.
Click to expand...
Click to collapse
I put it in a usb 2.0 port and it was the same, this file does not seem to be compatible
Is there anything else I can do to save the device?

vini14zimm said:
I put it in a usb 2.0 port and it was the same, this file does not seem to be compatible
Is there anything else I can do to save the device?
View attachment 5664851
Click to expand...
Click to collapse
I'd suggest joining the tele group for that rom and asking there if anyone can give you the version of the boot partition you need.

AsItLies said:
I'd suggest joining the tele group for that rom and asking there if anyone can give you the version of the boot partition you need.
Click to expand...
Click to collapse
kinda had the same problem lol on 2023... anyways tried to fix it the way of netmsm, deleting all partitions, hard bricked i could say, kinda worked, but as far as i could do, it went to fastboot loop, to LG Bootlloooping lol, any recommendations

Installation hangs at verifying installation file

While trying to install an OS on my Pixel 2 XL using either LOS or TWRP recoveries, my PC and the 2 XL hangs after the adb sideload OSinstallpackage.zip command. I have tried installing various versions of LOS and even tried installing the last Google OTA package for this phone. TWRP just says tha the package is being installed indefinitely, LOS recovery says verifying installation file. The PC just has a blinking cursor under the sideload command line, no install progress is displayed. Up until recently, this problem didn’t exist and I don’t know what changed. Does anyone out there have any idea how to resolve this problem?

How long have you waited? Large files can take a while to process.

V0latyle said:
How long have you waited? Large files can take a while to process.
Click to expand...
Click to collapse
I have waited 15-20 minutes. Typically, on the PC, you start to see the percentage of installation almost immediately when everything is working correctly.

neilth said:
I have waited 15-20 minutes. Typically, on the PC, you start to see the percentage of installation almost immediately when everything is working correctly.
Click to expand...
Click to collapse
True.
It sounds like the issue is with TWRP. If you boot into OEM recovery, are you able to sideload the OEM OTA?
Have you tried different USB cables?
Are your ADB Platform Tools up to date? Using tools like Minimal ADB is not recommended; make sure you're using the original SDK Platform Tools from here.

V0latyle said:
True.
It sounds like the issue is with TWRP. If you boot into OEM recovery, are you able to sideload the OEM OTA?
Have you tried different USB cables?
Are your ADB Platform Tools up to date? Using tools like Minimal ADB is not recommended; make sure you're using the original SDK Platform Tools from here.
Click to expand...
Click to collapse
I am getting the same issue whether I use TWRP or LOS recovery. My ADB Platform Tools are the latest version. How do I get back to OEM recovery once I have used non OEM operating systems on the phone? And yes, I have tried several USB cables.

neilth said:
I am getting the same issue whether I use TWRP or LOS recovery.
Click to expand...
Click to collapse
Hmm. Let's still try the OEM recovery.
neilth said:
My ADB Platform Tools are the latest version.
Click to expand...
Click to collapse
Good.
neilth said:
How do I get back to OEM recovery once I have used non OEM operating systems on the phone?
Click to expand...
Click to collapse
Just reflash the stock boot image from the factory image, then use the key combo to force a boot into recovery
neilth said:
And yes, I have tried several USB cables.
Click to expand...
Click to collapse
Well...there's only so many possibilities.

Does your USB connection transfer data fine in other cases? Maybe you just need to clean the port.
You could try connecting a USB drive directly to the phone and flash from that.
Or flash a file that's already on the phone - but that requires that TWRP can decrypt your data, and ISTR that TWRP hasn't been updated to the newest encryption scheme.

V0latyle said:
Hmm. Let's still try the OEM recovery.
Good.
Just reflash the stock boot image from the factory image, then use the key combo to force a boot into recovery
Well...there's only so many possibilities.
Click to expand...
Click to collapse
I downloaded the last released official factory OTA zip of the operating system for the Pixel 2 XL from Google. How do I proceed to get the stock boot image and install it on my phone?

runekock said:
Does your USB connection transfer data fine in other cases? Maybe you just need to clean the port.
You could try connecting a USB drive directly to the phone and flash from that.
Or flash a file that's already on the phone - but that requires that TWRP can decrypt your data, and ISTR that TWRP hasn't been updated to the newest encryption scheme.
Click to expand...
Click to collapse
Everything was fine with this phone running LOS 19.1. Last week I attempted to upgrade to the unofficial release of LOS 20 using the published LOS upgrade instructions and now I can’t even get LOS 19.1 to install again for some reason after having wiped the phone’s partitions.

neilth said:
I downloaded the last released official factory OTA zip of the operating system for the Pixel 2 XL from Google. How do I proceed to get the stock boot image and install it on my phone?
Click to expand...
Click to collapse
Factory images and OTA images are not the same.
Factory images for Taimen
Extract, then extract the image-device-builnumber.zip inside it. You'll find the boot.img in this archive.

V0latyle said:
Factory images and OTA images are not the same.
Factory images for Taimen
Extract, then extract the image-device-builnumber.zip inside it. You'll find the boot.img in this archive.
Click to expand...
Click to collapse
Thanks, I’ll have to see if I can try this tomorrow or Friday.

Yes, good advice from V0latyle. Flashing factory usually fixes things.

neilth said:
Thanks, I’ll have to see if I can try this tomorrow or Friday.
Click to expand...
Click to collapse
I downloaded and extracted the last (12/20) factory image from Google. I have the boot.img file you mentioned, how do I install it on my phone in the correct place?

neilth said:
I downloaded and extracted the last (12/20) factory image from Google. I have the boot.img file you mentioned, how do I install it on my phone in the correct place?
Click to expand...
Click to collapse
Just flash everything as Google instructed on the page (flash-all or flash tool). Note that this will delete the data on your phone.

There was nothing on my phone to delete! I ran the flash-all.bat file which successfully installed the Dec. 2020 Android 11 OS, but did not resolve the issue with the adb sideload command hanging when attempting to install a non Google OS such as LOS.

Well, at least you've eliminated some possibilities. To my mind, this means that:
- the USB connection is working
- fastboot works
- hardware problem unlikely
What remains:
- wrong USB driver on the PC - I believe it uses a different driver in recovery - check device manager with the phone connected in recovery
- wrong adb version on your PC
- defective recovery (but you tried different ones, I think)
- you doing sideload wrong - post screens from phone and PC

runekock said:
Well, at least you've eliminated some possibilities. To my mind, this means that:
- the USB connection is working
- fastboot works
- hardware problem unlikely
What remains:
- wrong USB driver on the PC - I believe it uses a different driver in recovery - check device manager with the phone connected in recovery
- wrong adb version on your PC
- defective recovery (but you tried different ones, I think)
- you doing sideload wrong - post screens from phone and PC
Click to expand...
Click to collapse
Here are your requested screenshoots of the computer’s command prompt window where I run fast boot and adb commands, the phone screen showing the LOS recovery hung at "verifying update package" and a third shot of device manager showing the presence of the Android ADB Recovery Interface while my phone is connected to my computer via USB and in Recovery. I hope that you see something that I am missing here, I don’t see anything that stands out as a problem. Thanks for your assistance.
{
"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"
}

LeMobile is not the correct driver - for some reason Microsoft occasionally suggests it, but it's for some obscure phone. Try the Pixel driver package from Google.

I suspected that LeMobile driver might be the problem. I just tried using another computer after installing the latest Google Android support software on it and I finally got LOS 20 installed on it. I will be correcting the incorrect USB driver on my laptop, which I had previously been using to use adb and fastboot on the phone as needed.
I want to thank you two for your assistance with my problem here!

I have the same connection issue. It was resolved by connecting the phone through a USB hub.
I think what's happening is that the USB tries to connect at a baud rate which is too high for the phone in recovery mode.
If you don't have a hub to try this with, other options are to try using a different USB port, try a different (older) computer, or various USB cables laying around.
On a related note here:
I've been looking into whether it's possible to slow down the USB port via editing the USB driver settings on Linux Mint. There are threads about this topic with some reported success on certain computer brands, but at this stage, it seems the simplest solution to connect a Pixel 2 XL is to just buy a USB hub.
NB. this problem doesn't exist for my smaller Pixel 2 (not XL) phone.