Develop Bugs

[Q] Possibly Softbricked Zenfone 2 after CyanogenMod 12.1 install

Hi guys, I have an issue with my Zenfone 2 (ZE551ML).
I flashed CyanogenMod 12.1 and everything was working fine. That is, until I decided I wanted to go back to stock ROM. That's when everything went wrong.
1) I went into recovery mode (using Power + Volume UP).
2) I wiped cache partition (probably my first mistake)
3) I restored to factory settings (possibly my second mistake)
4) After this I tried to flash the "recovery1.img" of the stock ROM I had.
5 ) That didn't work so I tried using ADB to flash different ".zip" files (all firmware downloaded from Asus website)
When that didn't work either, I abandoned and rebooted the phone. But it doesn't boot anymore.
It is stuck on the Asus screen and nothing happens.
Does anyone know if and how I can get out of this situation?
I must insist on the fact that I am only a novice. Until now I've only ever known iOS and have no knowledge whatsoever of how Android works.
I already posted my question here ("http://forum.xda-developers.com/general/xda-assist/possibly-softbricked-zenfone-2-t3248318") and was told I might want to try posting it here as well. I hope one of you can help me repair my mess !

Download one click root, the one with CWM recovery. Place the factory firmware on your external SD card. Run the one click batch file. Type ACCEPT, press enter, the type T4 for option 4, press enter. Let the phone boot into CWM recovery. Select the option to update from external SD, pick your file and wait about 5 mins. Back to stock you go. By the way, to get into fastboot press and hold volume up + power wait for vibration then quickly press volume down about 3 times you should be able to get to fast boot, the run the one click batch.

shawnchalfant said:
Download one click root, the one with CWM recovery. Place the factory firmware on your external SD card. Run the one click batch file. Type ACCEPT, press enter, the type T4 for option 4, press enter. Let the phone boot into CWM recovery. Select the option to update from external SD, pick your file and wait about 5 mins. Back to stock you go. By the way, to get into fastboot press and hold volume up + power wait for vibration then quickly press volume down about 3 times you should be able to get to fast boot, the run the one click batch.
Click to expand...
Click to collapse
Thanks for the reply. Do you have a link for the one click root with CWM Recovery ? Can't seem to find it... Also, when I connected my phone to the computer and opened oneclickroot (basic) it says my phone needs to have USB debugging activated (which it did).
I can't get into recovery mode anymore, the phone just loops back to fastboot with no error message.

You just need fast boot only. Look around the forum for the CWM root its here and esy to find.

shawnchalfant said:
You just need fast boot only. Look around the forum for the CWM root its here and esy to find.
Click to expand...
Click to collapse
Found it but it doesn't do anything. The device doesn't even appear when I type "adb devices" in cmd. Thanks for trying to help but I'll just send it somewhere it can be fixed. I must have deleted the whole OS and now the phone is just trying to reboot but there is nothing to reboot.

Boot into fastboot, Vol Up + Power, once it vibrates quickly press and hold volume down a few seconds. Fastboot should appear. Then run the batch file. Adb does not run in fastboot mode.

m3j said:
Found it but it doesn't do anything. The device doesn't even appear when I type "adb devices" in cmd. Thanks for trying to help but I'll just send it somewhere it can be fixed. I must have deleted the whole OS and now the phone is just trying to reboot but there is nothing to reboot.
Click to expand...
Click to collapse
there is still hope ... go for a lower version of recovery, boot (flash it in fastboot) and then keep the rom by keeping it in the external sd card renaming it to MOFDS_Update (i dont remember the name ). flashing should be done on its own...

search "Tutorial Upgrade / Downgrade / Unbrick Zenfone 2" in Asus ZenTalk. it helps for me

Thank you all for trying to help but I wasn't able to repair the phone.
I sent it back and by some miracle they accepted to give me my money back. Buying a new one now but I won't do anything stupid with it this time !

A lot of problems

Hi.
Yesterday, i rooted my phone and installed xposed. it worked great. But with that + busybox + amplify + supersu, the game i play a lot didn't let me play (unauthorized program detected).
so i try to delete supersu or amplify, but it still didn't work.
So i uninstall xposed, unrooted my phone.... But it still doesn't work!
so i uninstall the game and try to install it. but during installation (downloading data), it crashed.
So i did a factory reset, tried to install my game, but it always crashes during installation!
I'm desesperate!!! it never did this to me before!
Plus, i'm still in 139 version of asus. I tried to update it yesterday (to 160 version), but it crashed!!!!!!!! and it doesn't want to try to install it again (it's like there is no upgrade)
and there is some buggy moment when the keyboard doesn't appear ect...
I have enough! i desesperaly need help!!! my phone never got problem before except battery, but now, i'm desesperate! i shouldn't have try to root it!
is there something i can do? reinstall root and xposed and remove them with another way?
please, i really need your help ... if i have know it was this troublesome, i wouldn't try anything! i want my phone back!
Please, i really need you... thank you...

Sideload the firmware in recovery mode.

KillerNo2 said:
Sideload the firmware in recovery mode.
Click to expand...
Click to collapse
first, thank you for the answer.
but i'm really a noob... how do you do that? enter recovery mode (power +volume + ?) and then try to update the mobile?

nevew said:
first, thank you for the answer.
but i'm really a noob... how do you do that? enter recovery mode (power +volume + ?) and then try to update the mobile?
Click to expand...
Click to collapse
Follow the instructions in this thread

i succeeded making my game work (at least! i'm so damn happy!) by wiping cache partition.
but when i do "check updates", there is nothing.
But no problem, i'm scared of touching the phone again, i stay with the 139 version >__>.
thanks anyway, but i won't do anything with a computer. my phone can stay the way it is. i'm scared of having problem again... the only thing i'm gonna do, is using apk or this kind of thing. but no root anymore...

nevew said:
i succeeded making my game work (at least! i'm so damn happy!) by wiping cache partition.
but when i do "check updates", there is nothing.
But no problem, i'm scared of touching the phone again, i stay with the 139 version >__>.
thanks anyway, but i won't do anything with a computer. my phone can stay the way it is. i'm scared of having problem again... the only thing i'm gonna do, is using apk or this kind of thing. but no root anymore...
Click to expand...
Click to collapse
Go to the pre-rooted roms thread and download the latest rom.
Make sure you have the fastboot tools, put the rom.img file in there, rename to system.img if it isn't already and flash with fastboot...
1. Hold down volume up and power, keep holding until you get to download mode, press up volume.
2. Connct to PC. Go to the folder you have the fastboot tools in and hold SHIFT then press right mouse button and select "Open CMD window here".
3. Type "fastboot devices", if you have done everything right then you will get the serial number displayed otherwise you need to update drivers.
4 Type "fastboot flash system system.img".
It will break the rom into about 5 parts to flash, just let it go, it will give a prompt when finished...
5. Type "fastboot reboot", your phone will reboot, be updated and have root while leaving all apps there.
Be aware that there may be problems running xposed and that may have been what killed your phone...
If you do install anything, before doing the OTA again, reflash the pre-rooted rom again and you should be able to update with the OTA with no problem...
Good luck...

ultramag69 said:
Go to the pre-rooted roms thread and download the latest rom.
Make sure you have the fastboot tools, put the rom.img file in there, rename to system.img if it isn't already and flash with fastboot...
1. Hold down volume up and power, keep holding until you get to download mode, press up volume.
2. Connct to PC. Go to the folder you have the fastboot tools in and hold SHIFT then press right mouse button and select "Open CMD window here".
3. Type "fastboot devices", if you have done everything right then you will get the serial number displayed otherwise you need to update drivers.
4 Type "fastboot flash system system.img".
It will break the rom into about 5 parts to flash, just let it go, it will give a prompt when finished...
5. Type "fastboot reboot", your phone will reboot, be updated and have root while leaving all apps there.
Be aware that there may be problems running xposed and that may have been what killed your phone...
If you do install anything, before doing the OTA again, reflash the pre-rooted rom again and you should be able to update with the OTA with no problem...
Good luck...
Click to expand...
Click to collapse
thank you for your help!
but i won't do it ^^"...
i don't want to root my phone anymore (too much trouble, and the game i play a lot doesn't like root... i won't try it again. pissed me off 2 days ago that it didn't work even when i unrooted my phone)...
i just wait for the marshmallow update (and hope that the phone will propose me the update and i won't have to make it manually).
i won't try to touch my phone again, i won't do the same mistake...

Honor 7x with Lineage and TWRP, stuck in limbo

Hi all,
I installed TWRP on my Honor 7x, that went well.
Yesterday I decided to try to get Lineage working so:
- I installed EMUI 8, that went pretty smooth
- I installed Lineage OS 15.1. (without GApps)
- I flashed TWRP.
The issue I have now is that:
1) I can't install any APK in Lineage. Probably needs a factory reset/dalvik cache wipe.
2) I can't boot into TWRP. It stays stuck on the splash screen forever. This also means I can't install OpenGapps, SuperUser access (afaik), or anything else that requires root.
3) The bootloader is saying "FRP: Locked", which means I can't flash a new TWRP or a different ROM. When I try it fails with "command not allowed"
3) "fastboot oem unlock" fails saying I need to enable it in the developer options, but it's grayed out in the developer options because it's already unlocked.
4) I wanted to try the "dload" method but I can't find a good explanation on how to do it, and Huawei recently took all their downloads down, which means I can't find any UPDATE.app even if I knew how.
5) The other solution that *might* work is using "fastboot oem frp-unlock", but I need an unlock code for that (I assume the same one that you request for an OEM unlock from Huawei), and Huawei closed down the site that generated the codes.
So I'm stuck in a weird limbo where I can't move forward (install Gapps and use my phone as normal) nor backwards (go back to EMUI8).
Does anyone have any idea how I can fix this situation?

Shadowsalyer said:
Hi all,
I installed TWRP on my Honor 7x, that went well.
Yesterday I decided to try to get Lineage working so:
- I installed EMUI 8, that went pretty smooth
- I installed Lineage OS 15.1. (without GApps)
- I flashed TWRP.
The issue I have now is that:
1) I can't install any APK in Lineage. Probably needs a factory reset/dalvik cache wipe.
2) I can't boot into TWRP. It stays stuck on the splash screen forever. This also means I can't install OpenGapps, SuperUser access (afaik), or anything else that requires root.
3) The bootloader is saying "FRP: Locked", which means I can't flash a new TWRP or a different ROM. When I try it fails with "command not allowed"
3) "fastboot oem unlock" fails saying I need to enable it in the developer options, but it's grayed out in the developer options because it's already unlocked.
4) I wanted to try the "dload" method but I can't find a good explanation on how to do it, and Huawei recently took all their downloads down, which means I can't find any UPDATE.app even if I knew how.
5) The other solution that *might* work is using "fastboot oem frp-unlock", but I need an unlock code for that (I assume the same one that you request for an OEM unlock from Huawei), and Huawei closed down the site that generated the codes.
So I'm stuck in a weird limbo where I can't move forward (install Gapps and use my phone as normal) nor backwards (go back to EMUI8).
Does anyone have any idea how I can fix this situation?
Click to expand...
Click to collapse
small chance you enable root from developer options. (i think it will be adb only)
if so , maybe can use adb shell and "dd" to write recovery to correct partition.
problem is many of the available twrp do not boot on custom rom .
example code. (if you do wrong , it may be bad)
Code:
dd if=/ext_sdcard/twrp_Recovery_ramdisk.img of=/dev/block/mmcblk0p32

It seems like I'm allowed to use dd in ADB shell, but before I run it, what do you mean by " problem is many of the available twrp do not boot on custom rom . "? I thought recovery was independent of the ROM? And does it mean flashing twrp like that could brick my phone?

Shadowsalyer said:
It seems like I'm allowed to use dd in ADB shell, but before I run it, what do you mean by " problem is many of the available twrp do not boot on custom rom . "? I thought recovery was independent of the ROM? And does it mean flashing twrp like that could brick my phone?
Click to expand...
Click to collapse
Like what you have , twrp stuck on splash screen

I managed to unlock the FRP with DC-unlocker. Sucks that it costs money but it worked!
Now Im stuck in a TWRP boot loop though.

Shadowsalyer said:
I managed to unlock the FRP with DC-unlocker. Sucks that it costs money but it worked!
Now Im stuck in a TWRP boot loop though.
Click to expand...
Click to collapse
At this point you should have access to fastboot though, right? I'd try a different TWRP instead. Perhaps try this one: https://drive.google.com/file/d/1ZYo7Ndte3vlLcUSadD6jIgfBi1oxa0Pb/view?usp=drivesdk

Just to clarify, it gets stuck on TWRP splash screen. When I turn off the phone, it immediately boots up again into TWRP. I tried getting into fastboot mode with all kinds of combinations of button presses, but no luck. Not even Volume Up + USB cable works

smokinjoe2122 said:
At this point you should have access to fastboot though, right? I'd try a different TWRP instead. Perhaps try this one: https://drive.google.com/file/d/1ZYo7Ndte3vlLcUSadD6jIgfBi1oxa0Pb/view?usp=drivesdk
Click to expand...
Click to collapse
Sorry, only saw your answer after sending my other reply. In theory I should have access to fastboot mode. However, everytime I start up I get into TWRP, which doesn't work. I tried Volume up, volume down, both, with and without power button, with and without cable, and no dice.

Shadowsalyer said:
Sorry, only saw your answer after sending my other reply. In theory I should have access to fastboot mode. However, everytime I start up I get into TWRP, which doesn't work. I tried Volume up, volume down, both, with and without power button, with and without cable, and no dice.
Click to expand...
Click to collapse
I have seen this happen before , solution was to wait for dead battery, or disassemble to unplug battery
---------- Post added at 04:51 PM ---------- Previous post was at 04:47 PM ----------
Shadowsalyer said:
Sorry, only saw your answer after sending my other reply. In theory I should have access to fastboot mode. However, everytime I start up I get into TWRP, which doesn't work. I tried Volume up, volume down, both, with and without power button, with and without cable, and no dice.
Click to expand...
Click to collapse
This is because after the frp unlock, it needed to see a factory reset, and it usually needs to be done with stock recvery.
So will have to wait till battery is dead and and plug in usb while holding volume button. Should then load to fastboot. Where it is best to flash stock recovery to clear the recovery bootloop. The bootloop is do to the fact yo unlocked frp and now phone needs to wipe/data

Shadowsalyer said:
Sorry, only saw your answer after sending my other reply. In theory I should have access to fastboot mode. However, everytime I start up I get into TWRP, which doesn't work. I tried Volume up, volume down, both, with and without power button, with and without cable, and no dice.
Click to expand...
Click to collapse
it sucks this happened to yu but im glad i am not the only one that dc-unlocker deleted my fastboot after i unlocked the frp and i cant boot fastboot for nothing if you find a solution please contact me. my phone is doing the exact same thing booting straight too twrp no mater what combinations i use

dcraffam said:
it sucks this happened to yu but im glad i am not the only one that dc-unlocker deleted my fastboot after i unlocked the frp and i cant boot fastboot for nothing if you find a solution please contact me. my phone is doing the exact same thing booting straight too twrp no mater what combinations i use
Click to expand...
Click to collapse
i just took mine apart and discconected the battery and still no luck that program deleted my fastboot

Please can you tell me the process to install twrp I have the L24

I waited all the way till the battery drained, stuck in the USB, and it booted to ROM! Sadly it immediately shut off again because the battery is dead (even with keeping the USB in). I'm going to keep trying though.

I can't get into fastboot mode. I can get into the ROM by letting the battery drain completely on the TWRP splashscreen, and then sticking in the USB cable. However, no button combination or "adb reboot bootloader" or rebooting to bootloader from the ROM brings me to the bootloader. I wonder if it's still there. Any ideas?

Shadowsalyer said:
I can't get into fastboot mode. I can get into the ROM by letting the battery drain completely on the TWRP splashscreen, and then sticking in the USB cable. However, no button combination or "adb reboot bootloader" or rebooting to bootloader from the ROM brings me to the bootloader. I wonder if it's still there. Any ideas?
Click to expand...
Click to collapse
Seems to be a f-up situation either way.
You have adb DD available, found out before.
Don't know if maybe flashing stock recovery is good idea at this point.
I think fastboot.img can be flashed with DD too, but don't try till someone can confirm.
If flash stock recovery clears the loops, maybe best to do full-ota manual flashing.

I managed to get an UPDATE.APP file and extract fastboot.img from it, as well as all the other .img files. If someone can tell me what to flash and how (with dd), I think Im set.

Shadowsalyer said:
I managed to get an UPDATE.APP file and extract fastboot.img from it, as well as all the other .img files. If someone can tell me what to flash and how (with dd), I think Im set.
Click to expand...
Click to collapse
Fastboot.img is the large part the bootloader. If flashing it goes bad, might be dead phone after, just rember that.
Will add a list of partition names and command s for you soon.
here is a list of oreo partitions and there /dev/blk/** number
and here is an example of code to save images with dd assuming you put the images on your extrnal-sdcard in folder called oreo-images
Code:
dd if=/dev/block/mmcblk0p5 of=/mnt/ext_sdcard/oreo-images/fastboot.img
Do that save first and compare the md5 of the file from update.app to this file.
or just check the md5 before making the copy
Code:
adb shell md5sum /dev/block/mmcblk0p5
If you are conviced you need to flash the images, here is example of writing the image assuming files are in sdcard folder oreo-update-images
Code:
dd if=/mnt/ext_sdcard/oreoupdate-images/fastboot.img of=/dev/block/mmcblk0p5
As I have said, this might be bad advise , I have not done fastboot.img flashing before. But on other devices it is same as lk.img or uboot.img, There is danger in flashing it incorrectly. That is why my suggestion was to flash no-check-recovery and do manael update with "echo -update_package" commands.
Along with the statement that fastboot.img is similar to lk.img or uboot.img on other phones, Your fastboot cannot be gone. because phone boots.
but do let us know how it goes.

I agree it would be better to flash recovery if possible. I assume I need the NoCheck-Recovery image from this thread? https://forum.xda-developers.com/honor-7x/how-to/manual-update-to-oreo-beta-emui-8-bnd-t3767044
And what partition do I have to flash it to? I'm guessing either /dev/block/mmcblk0p28 (erecovery ramdisk) or /dev/block/mmcblk0p32 (recovery ramdisk)? I'm not sure what the difference is between erecovery and normal recovery.
(didn't flash fastboot yet, wanted to see if recovery was doable).

Shadowsalyer said:
I agree it would be better to flash recovery if possible. I assume I need the NoCheck-Recovery image from this thread? https://forum.xda-developers.com/honor-7x/how-to/manual-update-to-oreo-beta-emui-8-bnd-t3767044
And what partition do I have to flash it to? I'm guessing either /dev/block/mmcblk0p28 (erecovery ramdisk) or /dev/block/mmcblk0p32 (recovery ramdisk)? I'm not sure what the difference is between erecovery and normal recovery.
(didn't flash fastboot yet, wanted to see if recovery was doable).
Click to expand...
Click to collapse
To recovery_ramdisk. 32
What about check md5 of fastboot partition, that will be helpful to know if it did get wiped out.?

Hmm seems like I'm not allowed to use dd after all:
HWBND-H:/ $ dd if=/storage/7C96-7E17/BND-RECOVERY-NoCheck.img of=/dev/block/mmcblk0p32
dd: /dev/block/mmcblk0p32: Permission denied
And here I was thinking I was close to solving it...
Also can't run md5sum on the fastboot partition, since that needs root as well.

MIUI 10 Update from China 10.0.6.0 OEDCNFH to Global 10.0.1.0 OEDMIFH problems

Really need help!
I successfully unlocked my Mi Max 3 using the official process. 14 day wait. No issues...booted back into MIUI 10' restored backup from MiCloud and was back to normal, except now it showed "unlocked" on startup screen.
It was running CN MIUI 10 V10.0.6.0 OEDCNFH
I had been reading that it was possible to flash the device with the global version of the ROM
I had several Google related issues with the Chinese ROM so I downloaded the MiFlash tool (2018.5.28.0), got the ROM from here: https://xiaomifirmware.com/roms/latest-official-miui-roms-for-xiaomi-mi-max-3/
and tried to flash it with Global 10.0.1.0 OEDMIFH
Result was the error "flash crclist error"
screenshot here
https://1drv.ms/u/s!ArN9mSbbMVT8gohpA03ob7X2FhjspQ
After this, the device is stuck in Fastboot mode and seems to no longer have a bootable ROM. Booting into recovery mode with vol up + power and restarting that way also just boots back into Fastboot.
I downloaded the Fastboot version of the ROM the phone was originally running 10.0.6.0 OEDCNFH and tried to flash that.
It also failed with the same error.
This user had the same issue with a Mi8:
https://forum.xda-developers.com/mi-8/help/failed-to-install-global-rom-via-mi-t3851636
The thread did not help me. There seems to be almost nothing related to this issue "flash crclist error" on XDA
My phone is not bootable now. No idea what to try next, I am a total novice in this area. I have since been reading about Anti Rollback Protection, I just don't know if this has anything to do with my issue. My device is not dead....it is booting into Fastboot, and I can still see it in MiFlash. If anyone could advise me I would be very grateful.

https://forum.xda-developers.com/mi-max-3/how-to/to-youre-stuck-edl-mode-black-screen-t3837846/page2
See my post there on page 2. It should fix your issue.

The path of the rom seems too long.
Create a new folder at the root of your C drive and give it a name without spaces, move all the contents of the extracted rom to that folder and try to flash again

opasha - thanks for reply
opasha said:
https://forum.xda-developers.com/mi-max-3/how-to/to-youre-stuck-edl-mode-black-screen-t3837846/page2
See my post there on page 2. It should fix your issue.
Click to expand...
Click to collapse
Hi and thank you for responding to my question.
I have tried the steps in your thread as follows:
1) Download Global Stable fastboot 10.0.1.0 from this thread: https://forum.xda-developers.com/mi-...-t3827503/amp/
2) Open MiFlashTool and navigate to 10.0.1.0 fastboot rom. At the bottom select 'Clean All Only' (do NOT select clean all and lock).
3) Hold power, volume up and volume down together for 10 seconds after plugging into PC. Your pc should detect your phone in EDL mode. Hit REFRESH button at the top of MiFlashTool and it will show up as COM XX or XXX for your USB connection. Try whichever USB port works. Then hit refresh. Then click Flash.
When I try step 3, what you describe does not seem to be the behaviour I am seeing. If I hold volume up + volume down + power simultaneously for 10 seconds, the device reboots straight back into the Fastboot screen (the one with the bunny). Is this normal? If not, what screen should be displayed on the device? There is no sign of MiFlash tool detecting the device differently at this point (COM XX or XXX)
When I refresh MiFlash it detects the device as pictured:
https://1drv.ms/u/s!ArN9mSbbMVT8gpEJOYos6rGjNSM8vQ
If I flash it, it produces the same "flash crclist error" pictured here:
https://1drv.ms/u/s!ArN9mSbbMVT8gpEIec-cB8pUMAVqLg
FYI the only way I can get the device to start in anything other than the Fastboot screen is to hold down the VOLUME UP key + power. This boots it into the Mi-Recovery 3.0 screen where I can see the Main Menu with 3 buttons: Reboot - Wipe Data - Connect with MiAssistant
Reboot goes back to Fastboot
Wipe Data also just reboots into Fastboot.
Connect with MiAssistant prompts to connect to Mi PC suite with diagram of device + USB cable + URL (I tried this but PC suite (version 3.2.1.3111_2717) does not recognise my device....this was also the case when the phone was working normally). If I don't try to connect with USB cable at this point it times out after about 30 seconds and boots back into the Fastboot screen.
The remaining steps in your thread did not seem to apply after step 3 failed.
No idea what to do. I posted this on MIUI forums too. Some people are suggesting I use ADB and install TWRP but I would need an idiots guide, I don't have any experience with either and would have no idea what I was doing....and I'm finding it extremely difficult to unearth anything useful from the **vast** number of Android related sites and forums relating to ROMs etc. For example, I can't find anything helpful about "flash crclist error". Maybe I should ask Xiaomi support?
At this point I just need to get *any* working ROM onto the device. I would not have unlocked it and attempted the switch from Chinese to Global if I hadn't read so much advice that this could be done very simply and without issues as long as the bootloader was unlocked. If you have any other advice for me please let me know!
Thanks again.

richard.rea said:
Hi and thank you for responding to my question.
I have tried the steps in your thread as follows:
1) Download Global Stable fastboot 10.0.1.0 from this thread: https://forum.xda-developers.com/mi-...-t3827503/amp/
2) Open MiFlashTool and navigate to 10.0.1.0 fastboot rom. At the bottom select 'Clean All Only' (do NOT select clean all and lock).
3) Hold power, volume up and volume down together for 10 seconds after plugging into PC. Your pc should detect your phone in EDL mode. Hit REFRESH button at the top of MiFlashTool and it will show up as COM XX or XXX for your USB connection. Try whichever USB port works. Then hit refresh. Then click Flash.
When I try step 3, what you describe does not seem to be the behaviour I am seeing. If I hold volume up + volume down + power simultaneously for 10 seconds, the device reboots straight back into the Fastboot screen (the one with the bunny). Is this normal? If not, what screen should be displayed on the device? There is no sign of MiFlash tool detecting the device differently at this point (COM XX or XXX)
When I refresh MiFlash it detects the device as pictured:
https://1drv.ms/u/s!ArN9mSbbMVT8gpEJOYos6rGjNSM8vQ
If I flash it, it produces the same "flash crclist error" pictured here:
https://1drv.ms/u/s!ArN9mSbbMVT8gpEIec-cB8pUMAVqLg
FYI the only way I can get the device to start in anything other than the Fastboot screen is to hold down the VOLUME UP key + power. This boots it into the Mi-Recovery 3.0 screen where I can see the Main Menu with 3 buttons: Reboot - Wipe Data - Connect with MiAssistant
Reboot goes back to Fastboot
Wipe Data also just reboots into Fastboot.
Connect with MiAssistant prompts to connect to Mi PC suite with diagram of device + USB cable + URL (I tried this but PC suite (version 3.2.1.3111_2717) does not recognise my device....this was also the case when the phone was working normally). If I don't try to connect with USB cable at this point it times out after about 30 seconds and boots back into the Fastboot screen.
The remaining steps in your thread did not seem to apply after step 3 failed.
No idea what to do. I posted this on MIUI forums too. Some people are suggesting I use ADB and install TWRP but I would need an idiots guide, I don't have any experience with either and would have no idea what I was doing....and I'm finding it extremely difficult to unearth anything useful from the **vast** number of Android related sites and forums relating to ROMs etc. For example, I can't find anything helpful about "flash crclist error". Maybe I should ask Xiaomi support?
At this point I just need to get *any* working ROM onto the device. I would not have unlocked it and attempted the switch from Chinese to Global if I hadn't read so much advice that this could be done very simply and without issues as long as the bootloader was unlocked. If you have any other advice for me please let me know!
Thanks again.
Click to expand...
Click to collapse
Sorry, didn't realize this was new to you. Your fastboot mode is fine. Ignore my step 3 (my apologies for not clarifying since this step is not needed for you since your phone is in fastboot). All you need to do is have your phone flash this version of miui global through Miflash Tool. Let it reboot on its own.

can not flash ROM
opasha said:
Sorry, didn't realize this was new to you. Your fastboot mode is fine. Ignore my step 3 (my apologies for not clarifying since this step is not needed for you since your phone is in fastboot). All you need to do is have your phone flash this version of miui global through Miflash Tool. Let it reboot on its own.
Click to expand...
Click to collapse
I can not flash the ROM Global Stable fastboot 10.0.1.0 (or any other ROM I have tried)
In the MiFlash tool I get the error "flash crclist error" as I have tried to explain in my previous posts.

richard.rea said:
I can not flash the ROM Global Stable fastboot 10.0.1.0 (or any other ROM I have tried)
In the MiFlash tool I get the error "flash crclist error" as I have tried to explain in my previous posts.
Click to expand...
Click to collapse
You're not extracting properly. Use 7zip. Then extract the folder and point Miflash to this extracted folder. - make sure inside this folder there are simply files and no other single folders - single folders within single folders usually means you have to extract again.

Just run the damn flash-all.bat for God sake...

SOLVED thank you!
opasha said:
You're not extracting properly. Use 7zip. Then extract the folder and point Miflash to this extracted folder. - make sure inside this folder there are simply files and no other single folders - single folders within single folders usually means you have to extract again.
Click to expand...
Click to collapse
You were right. I extracted using 7Zip instead of Winzip. Pointed MiFlash at the extracted folder. 10.0.1.0 Global flashed successfully.
**HUGE** thanks to you for your replies and help. Painful learning curve for me. Very happy to get my phone working again, this time with the ROM I wanted.
Thanks again
best regards

so im on the same version but xiaomi.eu... 10.0.6.0 can i go downgrade that global? using same method?

flashed over x.eu 10.0.6.0 with Global 10.0.1.0 using Miflash with fastboot rom, it rebooted into recovery screen saying "this version cannot be installed on this device"...at this point i started crying lol.
Plugged into mi suite to see if i could recover back to original china rom it shipped with, discovered the BL was locked again, unlocked again via mi tool and hey presto, it booted up with fully working Global rom!
I'm now in a good place.

flashed over x.eu 10.0.6.0 with Global 10.0.1.0 using Miflash with fastboot rom, it rebooted into recovery screen saying "this version cannot be installed on this device"...at this point i started crying lol.
Plugged into mi suite to see if i could recover back to original china rom it shipped with, discovered the BL was locked again, unlocked again via mi tool and hey presto, it booted up with fully working Global rom!
I'm now in a good place.

never ending boot after stock ROM install

My Mi A2 Lite had stock rom v10.0.18.0, unlocked bootloader, Magisk v20.3 and TWRP using Offain v3.3.1.
I wanted to try dotOS custom ROM and followed this tutorial:
https://github.com/tkchn/daisyinstall
I begin with step 1 installing daisy global image v10.0.18.0 with flash_all.sh.
First time the script froze in the beginning.
I restarted it and it finished without errors but the following boot never ends.
I tried the same procedure with v10.0.3.0.
No errors and a never ending boot.
I tried to reinstall twrp from Offain using fastboot.
It looks OK but I can not press any button because the first twrp screen is frozen.
Now I can only enter fastboot.
adb does not recognize the device but fastboot seems to be working.
I am woried about my batery. I cannot see if it is charging because the boot is never ending. When I left fastboot without connecting USB cable I can turn off the phone but if I connect the charger the phone begins to work as if booting again and again.
What can I do to install the stock ROM without issues?

renatogui said:
My Mi A2 Lite had stock rom v10.0.18.0, unlocked bootloader, Magisk v20.3 and TWRP using Offain v3.3.1.
I wanted to try dotOS custom ROM and followed this tutorial:
https://github.com/tkchn/daisyinstall
I begin with step 1 installing daisy global image v10.0.18.0 with flash_all.sh.
First time the script froze in the beginning.
I restarted it and it finished without errors but the following boot never ends.
I tried the same procedure with v10.0.3.0.
No errors and a never ending boot.
I tried to reinstall twrp from Offain using fastboot.
It looks OK but I can not press any button because the first twrp screen is frozen.
Now I can only enter fastboot.
adb does not recognize the device but fastboot seems to be working.
I had frozen twrp screen before but usually managed to fix just by restarting the phone and using twrp offain in adb.
I am woried about my batery. I cannot see if it is charging because the boot is never ending. When I left fastboot without connecting USB cable I can turn off the phone but if I connect the charger the phone begins to work as if booting again and again.
What can I do to install the stock ROM without issues?
Click to expand...
Click to collapse
1- Download this: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
2- Create a new folder on your C drive and name it: adb
3- Extract & place everything from the platform-tools into your adb folder
4- Download this: https://drive.google.com/open?id=1SKIlWS-y6kNI4YIE2Sj4_9CcRJ9W0xTh
5- Extract & place it to your adb folder
6- Reboot your phone to TWRP and wipe it, then reboot to bootloader
7- Connect your phone to your PC
8- Go into the daisy_global_images_V10.0.9.0.PDLMIXM_9.0 folder and run: flash_all.bat
A window will pop up and install the stock mi a2 lite rom. Let it finish then your phone boot up. You will have to update your phone since this stock rom that I linked is a pretty old one.
Someone had a similar question in another forum, so I just copy my answer from there. If you have adb already installed you can ignore the first 3 steps.
I had frozen twrp screen a couple of times but managed to fix it by restarting the phone and re-open the powershell window in adb. I use twrp-daisy-3.2.3-0-offain.img

I'm afraid I cannot do step 6 as my TWRP is not working any more.
The remaining procedure I already did with 2 different daisy images V10.0.18.0 and 10.0.3.0.
In both cases the stock ROM was installed but the phone didn't finish to boot.
Why do you think it would be different if I use V10.0.9.0?
You said you fix frozen TWRP restarting the phone and re-openning the powershell in adb. My phone did not restart and adb does not work.

I was thinking I did not try to install stock image using MiFlash tool. I can do it if I get a windows computer available.
I saw people suggesting fastboot oem edl but I could not find a clear explanation of the procedure.
I understood that I must use MiFlash in that case too but the steps are not clearly defined and I need a windows computer anyway.
Does someone have a step by step to use fastboot oem edl?

renatogui said:
I'm afraid I cannot do step 6 as my TWRP is not working any more.
The remaining procedure I already did with 2 different daisy images V10.0.18.0 and 10.0.3.0.
In both cases the stock ROM was installed but the phone didn't finish to boot.
Why do you think it would be different if I use V10.0.9.0?
You said you fix frozen TWRP restarting the phone and re-openning the powershell in adb. My phone did not restart and adb does not work.
Click to expand...
Click to collapse
No particular reason behind 10.0.9.0 ... I just had that uploaded to my drive and when I posted this to another forum I didn't wanted to "waste" time to search for a link so I just used mine. Anyways u have to wipe your phone before installing stock rom.
The way I fixed mine is not working for you so Im afraid Im out of ideas.
Hope someone can help you out with it

thanks, anyway for your kind and quick answer.

I'd suggest giving MiFlash a try. Because a few times I tried flashing with the script file bundled with the stock ROM, I also had some bootloops, but MiFlash fixed the issue. When it comes to EDL flashing:
1 - Grab the 20160401 version of MiFlash from here : https://www.xiaomiflash.com/download/ (You need this version because it's the only MiFlash version that's capable of EDL flashing, mind you, you need a Windows PC and 64-bit hardware for this)
2 - Connect the phone in fastboot mode and type this command :
Code:
fastboot oem edl
Hit enter, this will take the phone into EDL mode, which means the screen will go black and the notification LED will start blinking.
3 - Now you're in EDL mode, open the MiFlash version I mentioned and Browse to find the location the stock ROM is stored, then hit refresh so that the software can recognize the phone.
4 - Hit flash to start flashing, but remember EDL flashing is a very fragile process, so make sure you don't lose power/shutdown the app while it's doing its job. After a successful flash, the app will say it is successful. Unplug the phone and start holding the power button to reboot. If you want to lock the bootloader, make sure to hold vol down as well and go into fastboot then re-lock the bootloader with :
Code:
fastboot oem lock
5 - Voila!

Thank you marstonpear for the detailed answer.
I will try MiFlash this evening and will post the result here.
I am very glad to count with more experienced people in fixing my errors.

Hello marstonpear,
I downloaded daisy image v10.0.13.0 that was suggested in XiomiFlash how to and try to flash it.
I got the error "mismatch image and device". This is very strange. Never had this before flashing with fastboot.
Do you think I could scrambled mi A2 lite so MiFlash cannot recognize it as a mi A2 lite anymore?
The only different think I did was interrupting my first flasing try using ^C when it was frozen.
I made 2 other tries after this with no errors. The only problem was the never ending boot.
My next try will be using image v10.0.18.0, the one I had installed before all this problems begin.

renatogui said:
Hello marstonpear,
Click to expand...
Click to collapse
marstonpear said:
I'd suggest giving MiFlash a try.
Click to expand...
Click to collapse
Quote marstonpear, like the quote above so that he get notification about your comment.
BTW, I never see this error before, you can try to google it.

coolwei1 said:
Quote marstonpear, like the quote above so that he get notification about your comment.
BTW, I never see this error before, you can try to google it.
Click to expand...
Click to collapse
I'm sorry. I tried hard how to quote and did'nt find.:cyclops:
I am almost learning...

marstonpear said:
I'd suggest giving MiFlash a try. Because a few times I tried flashing with the script file bundled with the stock ROM, I also had some bootloops, but MiFlash fixed the issue.
Click to expand...
Click to collapse
mismatched image and device error when MiFlashing image.
There are some sugestions about erasing the first 2 lines in flashing script ( where the daisy ROM is cheched in the image and the hardware) and flash again.
I am not sure this is a good idea. I'm affraid things could become worse.
But I am sure there is a Xiaomi Mi A2 Lite writen in the phone box and the image I used was daisy_global_images_V10.0.13.0.PDLMIXM_20190813.0000.00_9.0_5d0d486f04
What is next step?

renatogui said:
mismatched image and device error when MiFlashing image.
There are some sugestions about erasing the first 2 lines in flashing script ( where the daisy ROM is cheched in the image and the hardware) and flash again.
I am not sure this is a good idea. I'm affraid things could become worse.
But I am sure there is a Xiaomi Mi A2 Lite writen in the phone box and the image I used was daisy_global_images_V10.0.13.0.PDLMIXM_20190813.0000.00_9.0_5d0d486f04
What is next step?
Click to expand...
Click to collapse
If you're sure your device is daisy - Mi A2 Lite, you can delete the first line of the .sh or .bat to skip verification. Simplest way to verify your device is indeed Mi A2 Lite is checking the back cover of the phone and seeing the androidone logo there. If the logo is there go on with the procedure of deleting the first line of the code, then flashing it. Never interrupt the flashing process as it may cause the device's hardware to fail afterwards. I'd suggest using 10.0.13.0 for flashing as that one is the latest ROM that's provided as full version by Xiaomi. If you're still using Linux/MacOS to flash the firmware, I had an issue before on my Mac that didn't let me flash the stock ROM: flash_all.sh was wrongly formatted, so I had to add "./" (dot slash without the quotation marks) to the beginning of every line in the code that began with "fastboot" to make it work.
TL;DR : If device is daisy and you're on Windows, delete the first line and try again. If device is daisy and you're on Linux/MacOS, add "./" in front of every line that starts with "fastboot" in flash_all.sh

marstonpear said:
If you're sure your device is daisy - Mi A2 Lite, you can delete the first line of the .sh or .bat to skip verification. Simplest way to verify your device is indeed Mi A2 Lite is checking the back cover of the phone and seeing the androidone logo there. If the logo is there go on with the procedure of deleting the first line of the code, then flashing it. Never interrupt the flashing process as it may cause the device's hardware to fail afterwards. I'd suggest using 10.0.13.0 for flashing as that one is the latest ROM that's provided as full version by Xiaomi. If you're still using Linux/MacOS to flash the firmware, I had an issue before on my Mac that didn't let me flash the stock ROM: flash_all.sh was wrongly formatted, so I had to add "./" (dot slash without the quotation marks) to the beginning of every line in the code that began with "fastboot" to make it work.
TL;DR : If device is daisy and you're on Windows, delete the first line and try again. If device is daisy and you're on Linux/MacOS, add "./" in front of every line that starts with "fastboot" in flash_all.sh
Click to expand...
Click to collapse
Yes, there is the androidone logo in the back.
I had to interrupt the flashing the very first time because it stop before end like frozen.
You say I can damaged the hardware doing this?

renatogui said:
Yes, there is the androidone logo in the back.
I had to interrupt the flashing the very first time because it stop before end like frozen.
You say I can damaged the hardware doing this?
Click to expand...
Click to collapse
Yes the flash storage on the phone can be damaged just by interrupting the flashing process, especially while EDL flashing. So make sure you kill other unnecessary processes on your PC before you start flashing so it does not hang again.

marstonpear said:
If you're sure your device is daisy - Mi A2 Lite, you can delete the first line of the .sh or .bat to skip verification.
TL;DR : If device is daisy and you're on Windows, delete the first line and try again. If device is daisy and you're on Linux/MacOS, add "./" in front of every line that starts with "fastboot" in flash_all.sh
Click to expand...
Click to collapse
Now I know the reason of mismatching. All the scripts bundled with Xiaomi_Mi_A2_Lite_V10.0.13.0.PDIMIXM_20190807.0000.00_Global_9.0_XFT are made for jasmine. I will find another image more trustworthy than this one.

marstonpear said:
Yes the flash storage on the phone can be damaged just by interrupting the flashing process, especially while EDL flashing. So make sure you kill other unnecessary processes on your PC before you start flashing so it does not hang again.
Click to expand...
Click to collapse
I used the image v10.0.13.0 from https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
I check the scripts to verify if they are for daisy and flashed using MiFlash20191206.
At the end I got this error:
Not catch checkpoint [\$fastboot -s.*lock] .flash not done
:crying:

renatogui said:
I used the image v10.0.13.0 from https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
I check the scripts to verify if they are for daisy and flashed using MiFlash20191206.
At the end I got this error:
Not catch checkpoint [\$fastboot -s.*lock] .flash not done
:crying:
Click to expand...
Click to collapse
for others having the same probem I've learn in another thread that this error is issued because I did not choose the lock option below right of MiFlash tool. That is why it didn't catch the lock checkpoint. But the end of the message is not true because at this checkpoint, the flashing is already done. I simply turn the phone off and on again and the boot was normal.
Thanks for all that help me specially marstonpear.
Thread closed... until next problem.