Develop Bugs

Hi i need your help plz experienced people i need your help

Ive been trying to install stock rom my my z2 plus and i wanted to install the indian version but when i try to do so,after i type the command adb reboot edl the just restarts and ive tried to do it plenty of times but it just restarts again and a few days back when i tryed installing it this wasnt the problem,it was something about cannot recieve mi hello packet and it showed that message for like ten seconds in the mi flash tool and then it failed.Plz urgent help required

I faced the similar issue. Here is what worked for me
Quoting from this post
https://forum.xda-developers.com/lenovo-zuk-z2/how-to/rom-zui-3-5-243st-z2-plus-z2-t3745636/page63
I found one working solution via a lot of Google Searching..
I guess TWRP makes thing different from stock recovery (not sure, I am no expert). Since earlier when I didn't have TWRP, just stock 2.5 ZUI and stock recovery, there adb reboot edl worked fine
Here it is, what allowed me EDL mode,
1. Switch off the phone
2. Pressing Volue up+down key
3. Connecting cable while the step two is being performed.
(This immidiately brings the phone to Fastboot mode window)
4. Running ADB command fastboot -i 0x2b4c oem reboot-edl
(Surprisingly while in fastboot mode via this 1.2.3 method, adb devices doesn't show any device but the command worked)
5. Proceeding with QFIL 1.9 Flash.
Click to expand...
Click to collapse

[BRICKED] Stuck in android 8.1 bootloop

I just bricked my phone :crying: :crying:
I wanna get back to the official rom, after trying android P (without make it work).
(the rom is from http://en.miui.com/download-354.html)
But I run the wrong script and take the flash_all_lock.img
And my device is stuck on android 8.1 bootloop (It boot, but i get an animated line loop ...)
Any ideas or tricks before i get it back to warranty ?
Thanks

Unlock bootloader and flash again. You can find a guide to unlock bootloader at the beginning of this guide.

BubuXP said:
Unlock bootloader and flash again. You can find a guide to unlock bootloader at the beginning of this guide.
Click to expand...
Click to collapse
But since I flashed the official rom with data whipe, I'm unable to go to dev option and enter OEM Unlocking .... And Fastboot respond me that my device is locked

Seems like my only option left is to boot into EDL mode ...
But seems fastboot oem edl does not work I don't lnow how to handle the problem

droopeur said:
Seems like my only option left is to boot into EDL mode ...
But seems fastboot oem edl does not work I don't lnow how to handle the problem
Click to expand...
Click to collapse
Have you tried to switch the active slot?
Try if it boots using
fastboot set_active a
or
fastboot set_active b
If not working, can you enter recovery (power on with Volume up button pressed)?
If you can enter recovery, hold down the power button for 3-5 seconds and then press and release the Volume up button, to make commands appear. Then your only hope is to install the OTA update zip from there (copy the OTA in a microSD card, there is a thread where you can find the link to the OTA zip).
In my opinion, "OEM unlocking" in developer options MUST be always keep active, because incidents like this could happen, and because even without modding, an OTA could go wrong resulting in your same situation.
I was in your same situation (OEM unlocking disabled and then I locked bootloader with a custom ROM installed) with a Nexus 5X.
I don't remember well how I fixed it, but I remember entering in Qualcomm download mode (should be the same EDL mode) and loading a file found after many hours of research in strange forums and sites.

BubuXP said:
Have you tried to switch the active slot?
Try if it boots using
fastboot set_active a
or
fastboot set_active b
Click to expand...
Click to collapse
In fact, both work, but my phone still stucked at the bootloader (infinite line animation in both cases).
BubuXP said:
If not working, can you enter recovery (power on with Volume up button pressed)?
If you can enter recovery, hold down the power button for 3-5 seconds and then press and release the Volume up button, to make commands appear. Then your only hope is to install the OTA update zip from there (copy the OTA in a microSD card, there is a thread where you can find the link to the OTA zip).
Click to expand...
Click to collapse
Yes I can enter recovery and I have already tried this, but I always end up with the error:
Code:
E: Unknow volume for path [/sideload/package.zip]
Verifying update package...
Update package verification took 17.3 s (result 0)
Installing update...
E:Error il /sideload/package.zip (Status 1)
Installation aborted
BubuXP said:
In my opinion, "OEM unlocking" in developer options MUST be always keep active, because incidents like this could happen, and because even without modding, an OTA could go wrong resulting in your same situation.
I was in your same situation (OEM unlocking disabled and then I locked bootloader with a custom ROM installed) with a Nexus 5X.
I don't remember well how I fixed it, but I remember entering in Qualcomm download mode (should be the same EDL mode) and loading a file found after many hours of research in strange forums and sites.
Click to expand...
Click to collapse
Yes of course !
But I revert to stock rom with Mi Flash and I click on Flash all and lock, since the telephone should have been "brand new" it should not have any problems but ...
I have to enter EDL mode, but don't know how to do it since modified fastboot executables does not activate it it just reboot the phone...
Deep flash cable may help but not shure if it works, or I may have to disassemble the device to find EDL pins...

after unlock bootloader type fastboot flashing unlock_critical and flash with miflash tool

LUNARIO said:
after unlock bootloader type fastboot flashing unlock_critical and flash with miflash tool
Click to expand...
Click to collapse
But since I can't activate OEM I can't unlock bootloader....

try this http://www.xiaomitool.com/ not sure if it works on our phone but maybe can unlock the bootloader so you can use miflash

Have you sideloaded the zip? I think it's better to copy the OTA zip to microSD than ADB sideload.
droopeur said:
I have to enter EDL mode, but don't know how to do it since modified fastboot executables does not activate it it just reboot the phone...
Deep flash cable may help but not shure if it works, or I may have to disassemble the device to find EDL pins...
Click to expand...
Click to collapse
There should be only two methods for entering EDL:
1- request authorization in en.miui.com forum. Sometimes the admins accept requests to give an account one EDL flash permission (but I don't know if it works with AndroidOne devices).
2- finding the test point in the phone's motherboard.

Hi guys,
i tried to install this twrp but it doesnt work...
so i searched on internet and i found another article, i tried to check the current partition and install in another way
for first:
fastboot getvar current-slot
after i do this
fastboot boot_b recovery.img
and then
fastboot set_active b
so nothing to do....but right now my MI A2 lite not boot.
i try again to check my partition but this time i have no replay.
i have unlocked bootloader but i cant go to recovery and i cant boot!!
someone can help me please?

I HAVE THE SAME PROBLEM
everything you said is completely simillar to mine. Can someone help us? Or did you already fix it? Please help me i need my phone working.

I have same problem fastboot flash but after that, it started to reboot automatically. The phone was automatically turning off and on. I again did a "clean all and lock" via miflash tool but still now, no result!
I can boot into recovery without having any problem. But when I boo to setup country date....etc, it starts its auto rebooting process,
Any help ?

droopeur said:
But since I can't activate OEM I can't unlock bootloader....
Click to expand...
Click to collapse
Same situation here. I am desperate!! Did you solve it?

Isso resolve
steledama said:
Same situation here. I am desperate!! Did you solve it?
Click to expand...
Click to collapse
gadgetsfarm.com/download-mi-a2-lite-fastboot-rom-v9-6-4-download/[/url]

How to unbrick?
Hey guys. I bricked my Mi2 Lite as well. Is there any step by step way to unbrick?

had the same problem, was stuck in the bootloop even after I flashed img with MiFlash! NOTE: MY BOOTLOADER WAS UNLOCKED!!! (LUCKLY I DID NOT TRIED FLASH ALL AND UNLOCK!)
headed to this thread
Code:
fastboot flashing unlock
fastboot flashing unlock_critical
did not work, I get error saying FAILED
but after i used
Code:
fastboot oem edl
I went to MiFlash and used "Clean all" option (again note DON'T use "Clean all and lock"!!!). It took around 5 minutes to flash and my notif. light blinked whole the time. After it say "Success" I was able to normaly boot the phone again

Find "Mi A2 Lite toolkit V 1.0.4.2" and use it to flash stock 8.1, it will do all the magic with a few clicks, just don't interrupt it until your phone restarts and you get the "Welcome" screen. After you can do the upgrade to Pie via OTA.

Hi, where i can find MI A2 Lite Tool Kit? i open my device and i can put in EDL mode., my computer detect my pone in EDL mode, but i can not know do.
I like bypass FRP, can anybody help me
Thanks.
mr_techno said:
Find "Mi A2 Lite toolkit V 1.0.4.2" and use it to flash stock 8.1, it will do all the magic with a few clicks, just don't interrupt it until your phone restarts and you get the "Welcome" screen. After you can do the upgrade to Pie via OTA.
Click to expand...
Click to collapse

Hi all,
I also had same problem and I just resolve it.
My phone was in bootloop mode after stock rom flashing...
You don't need apply "fastboot oem edl" !
Just be sure your device is unlocked.
Download first stock rom (V9.6.4.0.ODLMIFF Firmware for Mi A2 Lite). If you flash last ROM, it don't work.
Flash it with XiaoMiFlash tool (don't forget to enable "Clean All") in bottom of the tool.
After reboot, you can apply OTA updates.
Enjoy !

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.

[RMN8Pro][Global] Bootloop fix

Evening guys, let's fix the Bootloop of our RMN8Pro if we have installed a menu Recovery TWRP faulty/unsuitable or we have installed a ROM that does not belong to our smartphone.
This method is valid for China to global or Global to global.
NOT FOR INDIAN (sorry about that)
You'll need:
ADB files
Fastboot ROM V10.4.5.0.PGGEUXM
Download both files and unzip them in C:/ADB (if you don't have that folder... just create it)
You will need to rename the file extension of the file <<begonia_eea_global_images_V10.4.5.0.PGGEUXM_20191007.0000.0000_9.0_eea_f796762f8a.tgz>> from .tgz to .rar
Let's go!!
Turn the phone off, turn it on in fastboot mode (by pressing both POWER and VOL- ) and connect the phone to the PC with its USB cable.
Open a CMD command console (in administrator mode) in C:/ADB and type this (press enter when finished typing):
Code:
fastboot devices
If you have the drivers installed and everything goes well, a series of alphanumeric characters will appear, such as for example:
Code:
a6ghfxfv6 fastboot
Perfect, we can go on.
Next we will flash one by one the files needed to revive the phone.
Write the following lines and press enter at the end of each of them (wait for the files to be installed between line and line):
Code:
fastboot boot boot.img
fastboot flash system.img
fastboot flash vendor.img
fastboot flash cust cust.img
fastboot flash recovery recovery.img
When you're done, restart the phone with:
Code:
fastboot reboot
Congratulations, you have your RMN8Pro fixed.

klurosu said:
Evening, let's fix the Bootloop of our RMN8Pro if we have installed a menu Recovery TWRP faulty/unsuitable or we have installed a ROM that does not belong to our phone.
This method is valid for China to global or Global to global.
NOT FOR INDIAN (sorry about that)
You'll need:
ADB files
Fastboot ROM V10.4.5.0.PGGEUXM
Download both files and unzip them in C:/ADB (if you don't have that folder...create it)
You will need to rename the file extension of the file <<begonia_eea_global_images_V10.4.5.0.PGGEUXM_20191007.0000.0000_9.0_eea_f796762f8a.tgz>> from .tgz to .rar
Let's go!!
Turn the phone off, turn it on in fastboot mode (by pressing both POWER and VOL- ) and connect the phone to the PC with its USB cable.
Open a CMD command console (in administrator mode) in C:/ADB and type this (press enter when finished typing):
If you have the drivers installed and everything goes well, a series of alphanumeric characters will appear, such as for example:
Perfect, we can go on.
Next we will flash one by one the files needed to revive the phone.
Write the following lines and press enter at the end of each of them (wait for the files to be installed between line and line):
When you're done, restart the phone with:
Congratulations, you have your RMN8Pro fixed.
Click to expand...
Click to collapse
So, this is basically a guide of how to flash the images through fastboot, right? Why not just use MiFlash when we are in fastboot mode?

polfrank said:
So, this is basically a guide of how to flash the images through fastboot, right? Why not just use MiFlash when we are in fastboot mode?
Click to expand...
Click to collapse
Because it doesn't work???
Don't believe me?, Just try
send from an RMN8 Pro (xiaomi.eu custom rom)

Miflash will work if in fastboot and have an MI account had requested to unlock BL.
Don't believe me? You try.

idog8818 said:
Miflash will work if in fastboot and have an MI account had requested to unlock BL.
Don't believe me? You try.
Click to expand...
Click to collapse
You still need authorized account Sherlock.
(Omg this guys...)
send from an RMN8 Pro (xiaomi.eu custom rom)

klurosu said:
You still need authorized account Sherlock.
(Omg this guys...)
send from an RMN8 Pro (xiaomi.eu custom rom)
Click to expand...
Click to collapse
if you don't apply for the Mi account to unlock BL, how will you able to flash anything? Only 2 mins for a new account.....What the problem will be?

idog8818 said:
if you don't apply for the Mi account to unlock BL, how will you able to flash anything? Only 2 mins for a new account.....What the problem will be?
Click to expand...
Click to collapse
Read again (this time read well please) 2 posts above
send from an RMN8 Pro (xiaomi.eu custom rom)

klurosu said:
Read again (this time read well please) 2 posts above
send from an RMN8 Pro (xiaomi.eu custom rom)
Click to expand...
Click to collapse
Read again but didn't get it. What do you mean ....

idog8818 said:
Read again but didn't get it. What do you mean ....
Click to expand...
Click to collapse
That you still need an Authorized Xiaomi's Account to do that with the old method dude.
send from an RMN8 Pro (xiaomi.eu custom rom)

klurosu said:
That you still need an Authorized Xiaomi's Account to do that with the old method dude.
send from an RMN8 Pro (xiaomi.eu custom rom)
Click to expand...
Click to collapse
What do you mean by Authorized Xiaomi's Account?? As far as I know, there're 2 types of Mi accounts we commonly talk here.
1. Normal Mi account: used to unlock BL and this can be used in miflash to flash rom, I've tried 100 times in fastboot, and works every time. I registered this account I guess 5 years ago when I need to request unlock BL on note 3 . As I said above, it needs 2 mins to register.
2. Authorised service account: This is not we can easy to register, It's for Mi service center or developers for repair/develop purposes. If no rec, no recovery, blank screen, it can be recovered by SP flash tool, which will need this type of account. This is also why users in following post looking for unbricking.
[GUIDE] [begonia] UNBRICK - stuck on DA mode / Authorised Service Account required
https://forum.xda-developers.com/re...a-mode-authorised-t4000433/page7#post81175069
---------- Post added at 01:20 AM ---------- Previous post was at 01:17 AM ----------
I can prove this by my bricked redmi note 8 pro.
I used my mi account to unlock BL, flashed global rom, but I cannot use it in SP FLASH TOOL to restore because my MI account is not an Authorised Service Account

Hello,
I have a nex Redmi Note 8 pro, I unlocked it after I use Ifixit.. to install twrp, the phone was in bootloap, after I tried to flash with fastboot commands. Now the phone is off and I have a black screeen. I can't power it on (vol + or -) does not work. power on no more. It is not recognized with miunlock. No fastboot nor recovery. Please help me how I can do?

nutellamarco said:
Hello,
I have a nex Redmi Note 8 pro, I unlocked it after I use Ifixit.. to install twrp, the phone was in bootloap, after I tried to flash with fastboot commands. Now the phone is off and I have a black screeen. I can't power it on (vol + or -) does not work. power on no more. It is not recognized with miunlock. No fastboot nor recovery. Please help me how I can do?
Click to expand...
Click to collapse
At the moment you only can do a deep flashing in EDL mode, and need an authorized account... You need to contact someone with this type of account and flash... ( And give some money...)

nutellamarco said:
Hello,
I have a nex Redmi Note 8 pro, I unlocked it after I use Ifixit.. to install twrp, the phone was in bootloap, after I tried to flash with fastboot commands. Now the phone is off and I have a black screeen. I can't power it on (vol + or -) does not work. power on no more. It is not recognized with miunlock. No fastboot nor recovery. Please help me how I can do?
Click to expand...
Click to collapse
Some people are saying they managed to bring to life a phone without rocovery without fastboot mode.search and maybe you find a way. As i remember they said with phone turned off you press volume - and power and you have about 5 seconds to flash. I don't know more details.i wish you success

hello
thanks for your ideas, I can't enter in fastboot mode nor recovery. The screeen is black. When I tried with spflash, when I push together vol+ and vol- i hear a noise, but nothing happens with spflash.
I am trying. I think it is loosed.

nutellamarco said:
hello
thanks for your ideas, I can't enter in fastboot mode nor recovery. The screeen is black. When I tried with spflash, when I push together vol+ and vol- i hear a noise, but nothing happens with spflash.
I am trying. I think it is loosed.
Click to expand...
Click to collapse
as far as I know spflash tool should be ready to flash,. it means with all the files selected, the combination is keeping vol+ and connect the USB cable to PC port, I recommend you search in Google about flashing mediatek devices... Good luck

Literally this guide is really about just how to flash with fastboot instead of Mi Flash(tool which can use anyone with Xiaomi Phone - doesn't require Authorized Service ACC)
nutellamarco said:
hello
thanks for your ideas, I can't enter in fastboot mode nor recovery. The screeen is black. When I tried with spflash, when I push together vol+ and vol- i hear a noise, but nothing happens with spflash.
I am trying. I think it is loosed.
Click to expand...
Click to collapse
I had this problem at the weekend(Stuck at EDL mode - tried to flash with SP tool but without success(needed service acc - brom error)), you can use SP flash tool with authorized service acc - fastest way, maybe there will be some cracked security file in the future as one for redmi 6. Or do battery trick. You are stick at EDL mode and cannot reboot from it. You can wait to discharge your phone(Tooks ~2 day with pushed power button) then connect into computer and when the led turn less bright use vol - + power to get into fastboot or disconnect battery and reconnect with pushed vol - to get into fastboot(I have used this three times because of installing wrong recovery).

Aglik-x said:
Literally this guide is really about just how to flash with fastboot instead of Mi Flash(tool which can use anyone with Xiaomi Phone - doesn't require Authorized Service ACC)
I had this problem at the weekend(Stuck at EDL mode - tried to flash with SP tool but without success(needed service acc - brom error)), you can use SP flash tool with authorized service acc - fastest way, maybe there will be some cracked security file in the future as one for redmi 6. Or do battery trick. You are stick at EDL mode and cannot reboot from it. You can wait to discharge your phone(Tooks ~2 day with pushed power button) then connect into computer and when the led turn less bright use vol - + power to get into fastboot or disconnect battery and reconnect with pushed vol - to get into fastboot(I have used this three times because of installing wrong recovery).
Click to expand...
Click to collapse
Thanks a lot for your reply
I will do that. But How I can know that phone is on to discharge battery? Best regards

nutellamarco said:
hello
thanks for your ideas, I can't enter in fastboot mode nor recovery. The screeen is black. When I tried with spflash, when I push together vol+ and vol- i hear a noise, but nothing happens with spflash.
I am trying. I think it is loosed.[/QUOTE
My oneplus 6 I used to do kind of the same thing... With the phone plugged and everything ready to flash... I used to press - plus power button and it would starting the process..
Click to expand...
Click to collapse

petenoni said:
nutellamarco said:
hello
thanks for your ideas, I can't enter in fastboot mode nor recovery. The screeen is black. When I tried with spflash, when I push together vol+ and vol- i hear a noise, but nothing happens with spflash.
I am trying. I think it is loosed.[/QUOTE
My oneplus 6 I used to do kind of the same thing... With the phone plugged and everything ready to flash... I used to press - plus power button and it would starting the process..
Click to expand...
Click to collapse
I try this method, the spflash does not start
I tried all touche combinaisons.
I will wait until the battery were empty and try again.
Thanks for your reply
Click to expand...
Click to collapse

bootloop fix worked for me
I try to post this yesterday but nothing happened so what i did was...
i installed TWRP and in twrp i wipe all data , system, vendor and reboot phone. that was wrong and i stuck in bootloop. so i go back to fastboot and type commands as u say....
fastboot boot boot.img
fastboot flash system.img
fastboot flash vendor.img
fastboot flash cust cust.img
fastboot flash recovery recovery.img - nothing worked
maybe u forgot some commands.... so i use...
fastboot boot boot.img -dont use, it didnt work
fastboot flash system system.img -ok
fastboot flash vendor vendor.img -ok
fastboot flash cust cust.img -ok
fastboot flash recovery recovery.img - but instead of official recovery i used TWRP.img and after reboot a finally boot into TWRP and i flash xiaomi.eu rom and after reboot magisk and all works fine. im not developer but this method worked for me and excuse my english i have global device

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.