Develop Bugs

Bricked ZL550 - Any ideas?

I bricked my U.S. market ZL550 Zenfone 2. My bad, I spent the last two weeks desperately trying everything I could think of to get Link2SD to mount an Ext2 or 4 partition on my SDXC card, and I wasn't at all surprised when it hung on the Asus logo while booting on Saturday.
Anyway, I can't get it to boot normally again. Using fastboot, I flashed recovery, boot and droidboot from the latest Asus ROM, Z008-WW-2.18.40.7, but when I try to flash the system image zip, I get a bunch of errors and a "fail" message on the phone.
I tried sideloading the image with adb but adb won't connect to the phone in recovery mode. Also tried copying the image zip to the SD Card but that wouldn't load, it would only look for MOFD_SDUPDATE.ZIP.
I can return it, I'm not exactly thrilled with it anyway. Anyone have any ideas of what I might try before sending it back?
Thanks! Carl

ConnCarl said:
I bricked my U.S. market ZL551 Zenfone 2. My bad, I spent the last two weeks desperately trying everything I could think of to get Link2SD to mount an Ext2 or 4 partition on my SDXC card, and I wasn't at all surprised when it hung on the Asus logo while booting on Saturday.
Anyway, I can't get it to boot normally again. Using fastboot, I flashed recovery, boot and droidboot from the latest Asus ROM, Z008-WW-2.18.40.7, but when I try to flash the system image zip, I get a bunch of errors and a "fail" message on the phone.
I tried sideloading the image with adb but adb won't connect to the phone in recovery mode. Also tried copying the image zip to the SD Card but that wouldn't load, it would only look for MOFD_SDUPDATE.ZIP.
I can return it, I'm not exactly thrilled with it anyway. Anyone have any ideas of what I might try before sending it back?
Thanks! Carl
Click to expand...
Click to collapse
I'm surprised!! Why do you need link2sd??? with 32 GB Internal, I have 118 Apps installed along with movies and music. Still I have space( I have not used SD Card).
Anyways,
From what you mentioned, you seem to have a ZE551ML. And you Installed Z008-WW-2.18.40.7. It should be Z00A and not Z008. Please download the correct firmware and try out.:good:
Thumb-rule,
ZE550ML = Z008
ZE551ML = Z00A
I guess thats what you did Wrong

Thanks for pointing that out! It's actually a 16GB 550.

I'd go and connect it to pc on fastboot and wipe everything via command. Ex. Fastboot erase system, data, cache. Then flash a stock Rom from Asus via adb sideload

ConnCarl said:
Thanks for pointing that out! It's actually a 16GB 550.
Click to expand...
Click to collapse
for MOFD_SDUPDATE.zip to work, you need to place it on the external sd card and reboot into recovery. It will automatically start to install.
Placing it on the Internal card wont help.
---------- Post added at 08:58 AM ---------- Previous post was at 08:57 AM ----------
lordpipa said:
I'd go and connect it to pc on fastboot and wipe everything via command. Ex. Fastboot erase system, data, cache. Then flash a stock Rom from Asus via adb sideload
Click to expand...
Click to collapse
I wouldnt recommend that.
He is unable to use adb properly. And if he messes up something, he might even lose his warranty

lordpipa said:
I'd go and connect it to pc on fastboot and wipe everything via command. Ex. Fastboot erase system, data, cache. Then flash a stock Rom from Asus via adb sideload
Click to expand...
Click to collapse
Tried all that. Many times.

ConnCarl said:
Tried all that. Many times.
Click to expand...
Click to collapse
When i restored from stock via ADB, I was going from a preroot, bricked, because I updated and was getting the little error bot.. After i sideload the image, i still had to factory reset. I'm just guessing, but you did try and do the factory reset after fastboot/ADB.

godgib said:
When i restored from stock via ADB, I was going from a preroot, bricked, because I updated and was getting the little error bot.. After i sideload the image, i still had to factory reset. I'm just guessing, but you did try and do the factory reset after fastboot/ADB.
Click to expand...
Click to collapse
I can't sideload the image, because I can't connect with ADB.

ConnCarl said:
I can't sideload the image, because I can't connect with ADB.
Click to expand...
Click to collapse
but you can get into recovery, it's just when you click on "ADB update" your computer doesn't see the phone, that's my understanding...

Right, correct. I can get into recovery, and fastboot works, but not ADB.

ConnCarl said:
Right, correct. I can get into recovery, and fastboot works, but not ADB.
Click to expand...
Click to collapse
It sounds like you still in fastboot and not recovery. This is what recovery looks like and then you put in it "Apply update ADB sideload."
{
"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"
}

Yep, that is exactly what it looks like. But when I try to sideload, it times out. ADB won't see the phone.

ConnCarl said:
Yep, that is exactly what it looks like. But when I try to sideload, it times out. ADB won't see the phone.
Click to expand...
Click to collapse
I'm pretty sure if it timse out using ADB sideload then it should also timeout when you type ADB deviecs, but try it you should see your serial number sideload.... If you don't then
1. Make sure you have ADB 1.42 with intel drives 1.9
2. Use the stock cable.
3. In device manager make sure there's no unknown Android devices.
4. if ADB still doesn't work then try and flash via fast boot a new boot.img and recovery.img.
5. If you do get to the point where you can sideload...
6. Downloaded the ASUS firmware with WW not CN.
7. Also make sure the firmware package doesn't have ext .zip.zip, because of unknown file ext in windows.

Not sure if this works but you can give it a try.
Have you boot it with Temp CWM?
Delete all cache, including those of under advanced section
install zip file should work to install your full rom. since you stated you cant adb to detect.

Thanks everyone for all the suggestions!
I was just sort of reviewing godgib's screen grab when it slowly dawned on me that at least part of the solution had been staring me in the face all along.
It had never occurred to me that adb might not be able to connect even though fastboot could. Then when I read "you need adb 1.0.32 or newer to sideload to this device", it started to make sense. I upgraded adb and connected but still couldn't sideload. After reviewing godgib's methodical list, I realized it was a driver problem. Once I squared that away, sideload went without a hitch.
Interesting side note...I don't know what build I had originally, but it had to be at least a month old or so. I figured I might as well get the latest release, so I went with Z008_WW_2.18.40.7, and I updated boot/droidboot/recovery while I was at it. The funny thing was that when it booted, it was set for 250 dpi and everything was tiny.
Luckily, since adb was finally working (thanks again godgib) I was able to send "adb shell wm density 480" to put it back to normal.
Thanks again, everyone!
Carl

Glad you got it working...
Sent from my ASUS_Z00AD using XDA Free mobile app

godgib said:
Glad you got it working...
Sent from my ASUS_Z00AD using XDA Free mobile app
Click to expand...
Click to collapse
Appreciate that.
Of course now auto-rotate is borked. I'll have to either wait for a patch or downgrade.

Did you ever figure out the sdcard problem? I just got the same card and want to do the same thing. But the phone wont see the second partition at all.

i have similar problem too

[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

Unable to do the initial fastboot boot "twrp.img" file

Every time I'm trying to run the "fastboot boot twrp-3.2.1-0-taimen.img" command for my Pixel 2 XL (or any twrp .img file for the P2XL for that matter except the alpha version), I am constantly stuck at "downloading 'boot.img' . . ." (attached image #2). Attached image #1 shows that I unlocked my bootloader.
On the computer terminal, the "downloading 'boot.img' . . ." message will stay there until I either start my phone again or restart the bootloader. I am also 100% certain I have been in the correct directory this entire time otherwise I don't think I would have even made it this far. Attached image #3 shows where the twrp.img file is. Line 1 on my terminal also shows that.
I'm at a loss. Any help would be appreciated.
{
"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'm assuming if I see "DEVICE STATE - unlocked" on the fastboot screen, the bootloader should be unlocked)

https://imgur.com/a/w4DWq
If the attached images do not load, then I have uploaded the images on Imgur

did you unlock the critical partition as well? Maybe that's the problem?

anthony.moua95 said:
Every time I'm trying to run the "fastboot boot twrp-3.2.1-0-taimen.img" command for my Pixel 2 XL (or any twrp .img file for the P2XL for that matter except the alpha version), I am constantly stuck at "downloading 'boot.img' . . ." (attached image #2). Attached image #1 shows that I unlocked my bootloader.
On the computer terminal, the "downloading 'boot.img' . . ." message will stay there until I either start my phone again or restart the bootloader. I am also 100% certain I have been in the correct directory this entire time otherwise I don't think I would have even made it this far. Attached image #3 shows where the twrp.img file is. Line 1 on my terminal also shows that.
I'm at a loss. Any help would be appreciated.
(I'm assuming if I see "DEVICE STATE - unlocked" on the fastboot screen, the bootloader should be unlocked)
Click to expand...
Click to collapse
Are you on 8.0 or 8.1? If on 8.1, did you update via OTA, side load, or factory image flash??

Badger50 said:
Are you on 8.0 or 8.1? If on 8.1, did you update via OTA, side load, or factory image flash??
Click to expand...
Click to collapse
I am on 8.1 and updated it via OTA.

anthony.moua95 said:
I am on 8.1 and updated it via OTA.
Click to expand...
Click to collapse
Hmmmm, interesting, dealing with another member on another thread having the same problem you are, except he side loaded 8.1.
I'm hoping one of the RC's or Developers can chime in. I think this is where the A/B partitions cause headaches. Reason being, after your OTA, you now are on partition B. I'm thinking that adb automatically recognizes partition A by default. So when you are trying to fastboot anything, there is essentially no OS to flash to. I think you may have to flash the stock factory image to both partitions to be able to root. Having said all that, I could be way off base, which is why I'm hoping for some help in this matter :good:

Have you tried a different cable yet?

Badger50 said:
Hmmmm, interesting, dealing with another member on another thread having the same problem you are, except he side loaded 8.1.
I'm hoping one of the RC's or Developers can chime in. I think this is where the A/B partitions cause headaches. Reason being, after your OTA, you now are on partition B. I'm thinking that adb automatically recognizes partition A by default. So when you are trying to fastboot anything, there is essentially no OS to flash to. I think you may have to flash the stock factory image to both partitions to be able to root. Having said all that, I could be way off base, which is why I'm hoping for some help in this matter :good:
Click to expand...
Click to collapse
Oh geeze, this is something I can't be bothered with at the moment with my current situation (living and working in Thailand). I appreciate all the input that you have given on this thread though! I think I will just keep my phone where it is at now then (unlocked bootloader, 0 modifications, 8.1.0). But I will continue to follow and see if there are any definitive or streamlined solutions to this potential problem in the (near) future. Adaway and Viper4Android are still very important enough reasons for me to root.
I will also add that when I tried rooting via the magisk method (patch_boot.img), I kept getting a message along the lines of
"target didn't report max-download-size
sending 'boot' (x KB)...
FAILED (remote: Requested download size is more than max allowed)
finished. total time: 0.123s"
Although even though despite always getting a message like this, I was able to somehow get root successfully one time. I decided to unroot and try to duplicate the root result but to no avail. Also got that annoying "internal problem with your device" message and followed @topjohnwu's tutorial only to get the "target didn't report max-download-size...FAILED (remote: Requested download dize is more than max allowed)" message again.
My laptop is currently running Manjaro (based on Arch Linux) but I can't imagine it being the reason I keep getting that "target didin't report max-download-size" message.

ilal2ielli said:
Have you tried a different cable yet?
Click to expand...
Click to collapse
Unfortunately I only have one USB-A to USB-C cable (a Sony one).

equlizer said:
did you unlock the critical partition as well? Maybe that's the problem?
Click to expand...
Click to collapse
I've tried numerous times and it always gave me a fail message or acknowledgement that my phone was already unlocked I'm giving up until I see a more streamlined answer to this potential problem

Make sure you adb/fastboot is up to date, it has caused many headaches for people trying to use older versions.

Badger50 said:
Hmmmm, interesting, dealing with another member on another thread having the same problem you are, except he side loaded 8.1.
I'm hoping one of the RC's or Developers can chime in. I think this is where the A/B partitions cause headaches. Reason being, after your OTA, you now are on partition B. I'm thinking that adb automatically recognizes partition A by default. So when you are trying to fastboot anything, there is essentially no OS to flash to. I think you may have to flash the stock factory image to both partitions to be able to root. Having said all that, I could be way off base, which is why I'm hoping for some help in this matter :good:
Click to expand...
Click to collapse
Exact thing happend to me. I sideloaded and I was stuck on partition B
I had to fully erase and start from scratch via full image method. Sucks but I got it going

anthony.moua95 said:
Unfortunately I only have one USB-A to USB-C cable (a Sony one).
Click to expand...
Click to collapse
I'd say try to get another cable ASAP, especially if anything else you do doesn't work.
When I first was attempting to unlock my bootloader, nothing worked when I was using third-party cables.
Luckily, my laptop had a USB-C port, so I was able to use the stock USB-C cable and I haven't had any problems since.

trim81 said:
Exact thing happend to me. I sideloaded and I was stuck on partition B
I had to fully erase and start from scratch via full image method. Sucks but I got it going
Click to expand...
Click to collapse
Kinda what I thought. How did you erase BTW? The interesting thing is that some of their adb commands won't work properly. Explain if you please how you did it so these guys can get back up to speed. Thanks for the input :good:

Badger50 said:
Kinda what I thought. How did you erase BTW? The interesting thing is that some of their adb commands won't work properly. Explain if you please how you did it so these guys can get back up to speed. Thanks for the input :good:
Click to expand...
Click to collapse
I'm on my mobile right now so I can't detail it but you would go to Google a site to download the full image. Then run the flashall command to wipe and start from scratch.
I was lucky I had a titanium backup for my apps.. I had to wipe eveything and start fresh.

trim81 said:
I'm on my mobile right now so I can't detail it but you would go to Google a site to download the full image. Then run the flashall command to wipe and start from scratch.
I was lucky I had a titanium backup for my apps.. I had to wipe eveything and start fresh.
Click to expand...
Click to collapse
Ok cool, that's the only way I know how to do it as well. Cool beans, thanks bro :good:

Hey, I had the exact same problem.
Posted a couple of times on the thread guide for root with magisk, ended with the same answer: fastboot/adb up to date ? Files where they should be ? (they dont need to be on the same folder as fastboot you know..., but they keep asking that...), and so on...
Tonight, latest attempt, instead of using my usb-c port, and my usb-a 3.0 port, I get back on my old laptop with 2.0 usb-a port and... It worked !
Just using 2.0 instead of 3.0 did the job ! You should try it

cavolo said:
Hey, I had the exact same problem.
Posted a couple of times on the thread guide for root with magisk, ended with the same answer: fastboot/adb up to date ? Files where they should be ? (they dont need to be on the same folder as fastboot you know..., but they keep asking that...), and so on...
Tonight, latest attempt, instead of using my usb-c port, and my usb-a 3.0 port, I get back on my old laptop with 2.0 usb-a port and... It worked !
Just using 2.0 instead of 3.0 did the job ! You should try it
Click to expand...
Click to collapse
Dude, if that's the answer, which it probably is, I'm gonna pull my hair out. Been trying everything I can to these folks out. And it's a flippin 8 dollar cable! Oh well, live and learn

I know tou probably did this already but I did not see it posted.
You did enable developer settings and enable oem unlock in developer settings?

Is there a solution to this issue? I have followed every set of directions I can find on XDA and beyond, wiped and wiped, locked and unlocked my phone a few different times. Tried different cables and different ports on my computer. No matter what I do, I am stuck at the "downloading boot" after trying to flash TWRP. Thanks in advance for any help.

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?

Question Xiaomi K40 Became A Brick

Hi peeps, my Xiaomi K40 now became a brick because it can't be installed any ROM, I've tried using TWRP and also mi flash tool but nothing helps.
When using TWRP I've tried two methods:
1/ adb sideload
2/ Install from a zip file which is pushed to device using adb push command(because now the device doesn't have any OS)
But in both cases it shown:
Failed to mount '/system_root' (Block device required)
Failed to mount '/system_ext' (Block device required)
Failed to mount '/product' (Block device required)
Failed to mount '/vendor' (Block device required)
Failed to mount '/odm' (Block device required)
Click to expand...
Click to collapse
I've also tried to wipe all data using Advance Wipe option to repair the partition but no hope.
Any one has solution for this case? thanks in advance!

Flash your device in EDL mode.
Please refer to the post below on how to bypass edl mode authentication.
[GUIDE] How to bypass authentication and flash in EDL with NO auth for FREE!​
Thanks to VD171 for his post.

I think your device is having a Snapdragon Chipset. Sorry but you may try to search on google for contact to person who has authorised edl account to flash a Snapdragon based phone.

Learn more about it in this video

reborn2020 said:
Hi peeps, my Xiaomi K40 now became a brick because it can't be installed any ROM, I've tried using TWRP and also mi flash tool but nothing helps.
When using TWRP I've tried two methods:
1/ adb sideload
2/ Install from a zip file which is pushed to device using adb push command(because now the device doesn't have any OS)
But in both cases it shown:
I've also tried to wipe all data using Advance Wipe option to repair the partition but no hope.
Any one has solution for this case? thanks in advance!
Click to expand...
Click to collapse
do you still have your fastboot mode on your phone?

mvikrant97 said:
Learn more about it in this video
Click to expand...
Click to collapse
Mi flash didn't recognized my phone.
khazzey said:
do you still have your fastboot mode on your phone?
Click to expand...
Click to collapse
Yes I do.

no bypass for STUCKDRAGON devices for EDL Mode so sad the phone became literally bricked

reborn2020 said:
Mi flash didn't recognized my phone.
Yes I do.
Click to expand...
Click to collapse
listen to me, first if you are on windows 10 you should disable driver signature enforcement on your pc search it on google after disabling you should restart your pc, next step is to install xiaomi flash tool latest (02262021) version after installing the software open it, at the right upper of the software you will see drivers click it and click install after installing, reboot your phone into fastboot mode using volume down and power button, connect your phone to pc and click refresh on xiaomi flash tool if you're phone is detected please come back here let me know

khazzey said:
listen to me, first if you are on windows 10 you should disable driver signature enforcement on your pc search it on google after disabling you should restart your pc, next step is to install xiaomi flash tool latest (02262021) version after installing the software open it, at the right upper of the software you will see drivers click it and click install after installing, reboot your phone into fastboot mode using volume down and power button, connect your phone to pc and click refresh on xiaomi flash tool if you're phone is detected please come back here let me know
Click to expand...
Click to collapse
I did this before but no hope, I don't know if the problem is I'm using a macbook and run windows 10 via bootcamp, I don't have an actual windows computer.
P.S, I upload the latest status.
{
"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"
}

last week I was in a similar situation like yours just twrp and all partition screwed up.
well what saved me was to put dot os 5.2 on a USB c pen drive and then simply installing it from trwp (choosing USB pen as source) after literally 5-10 minutes phones came back to life.
let me know if it works for you.
also if twrp throws any error during installation just ignore them for me after flash completed phone booted just fine

ale82to said:
last week I was in a similar situation like yours just twrp and all partition screwed up.
well what saved me was to put dot os 5.2 on a USB c pen drive and then simply installing it from trwp (choosing USB pen as source) after literally 5-10 minutes phones came back to life.
let me know if it works for you.
also if twrp throws any error during installation just ignore them for me after flash completed phone booted just fine
Click to expand...
Click to collapse
I put a miui rom in a usb type c then connect into my phone, then boot into TWRP, and in Install option, I didn't see any option likes "USB pen"

reborn2020 said:
I put a miui rom in a usb type c then connect into my phone, then boot into TWRP, and in Install option, I didn't see any option likes "USB pen"
Click to expand...
Click to collapse
I said USB pen to make sure you choose it from TWRP install I think the righ name is external storage or something similar anyway it seems you are doing things the right way I am quite sure u ll bring phone back to life.
I think muiu room is just fine, should it fails try crDroid or dot os (do not try arrow or lineage)

Bruh I have a very simple solution I guess it might help you
Well first update to latest official twrp custom recovey for your device then
Navigate to Wipe
advance Wipe
Select data and choose Repair or Change File System
Press Repair File System to see if this fixes the issue. If not, continue.
Press Change File System, choose Ext2, and swipe to confirm.
now switch back to Ext4 and swipe to confirm.
i hope this might help you BTW then flash your first custom rom using a sd card or usb if succeeded then flash every stuff as usual

Anurag3100 said:
Bruh I have a very simple solution I guess it might help you
Well first update to latest official twrp custom recovey for your device then
Navigate to Wipe
advance Wipe
Select data and choose Repair or Change File System
Press Repair File System to see if this fixes the issue. If not, continue.
Press Change File System, choose Ext2, and swipe to confirm.
now switch back to Ext4 and swipe to confirm.
i hope this might help you BTW then flash your first custom rom using a sd card or usb if succeeded then flash every stuff as usual
Click to expand...
Click to collapse
Thanks, I've tried this before, unfortunately still can't solve my problem. Finally I decided to bring my phone to a technician.

Try fastboot erase userdata in cmd after taking your device to fastboot mode
Kinda check different twrp I think your twrp is having any problems plz flash your twrp once again
I hope this will surely work for you my friend.

reborn2020 said:
Thanks, I've tried this before, unfortunately still can't solve my problem. Finally I decided to bring my phone to a ttechnic
Click to expand...
Click to collapse
Bro try different formats then change to Ext4 well try this twrp https://dl.twrp.me/alioth/twrp-3.6.0_11-0-alioth.img.html umm i hope this will help you out completely.

if you still have your fastboot mode (turn off then hold power + vol. down), you should check your pc driver if adb and fastboot driver installed properly, then try flashing stock rom (dont relock your bootloader), I think what cause the brick is encrypted storage that get accessed by twrp, even if you decrypt it using password, you can still brick the phone by manually mount some partition in twrp

Thank you all of your help, peeps. Finally I solved my problem by the help of a technician. Because only technician has access to Xiaomi internal tools, these are "Hardware-Level" which could help in these cases.

He
reborn2020 said:
Thank you all of your help, peeps. Finally I solved my problem by the help of a technician. Because only technician has access to Xiaomi internal tools, these are "Hardware-Level" which could help in these cases.
Click to expand...
Click to collapse
Hello, glad you solved your issue, but can you please explain briefly how hardware was bricked since you were already able to reach fastboot & twrp? Since it's known that when you can boot to fastboot, it's a softbrick

Alipk52 said:
He
Hello, glad you solved your issue, but can you please explain briefly how hardware was bricked since you were already able to reach fastboot & twrp? Since it's known that when you can boot to fastboot, it's a softbrick
Click to expand...
Click to collapse
I can boot to fastboot but I can't do anything with fastboot becuase I wiped out anything on my phone include "firmware" maybe, I don't know, sorry but this's not my major so I can't explain.