How to Unbrick Xiaomi Mi A2 lite? - Xiaomi Mi A2 Lite Questions & Answers

Hi I recently try to flash a Stock Android One to my Xiaomi Mi a2 lite (Global Version of Redmi 6 pro).
I used Mi flashtool and I download a Fastboot Image file that matches my device model but my phone is bricked
the notification light is blinking when ever I push the power button. And I cannot know when my phone is charging there are no display that my phone is charging and when I press the Volume down and Power button I cannot access the Fastboot mode so I just simply attached my phone to the Computer and I shocked when I heared of a sound that my device was read by the computer but the phone is dead that time so I use the Miflash tool and It detect my phone but when I use powershell and command fastboot devices it doesnt recognized or detecting my phone.
So I decided to flash the rom to my phone because it can detect it, but Its taking too long to flash, 1500 seconds has passed but the flashing is not finish so I decided to unplug my phone but the xiaomi flash tool is still flashing so I thought that the app is corrupted so I just exit the app and open it again and do the flashing again but 2000 seconds has passed and still its the same thing I unplug the phone and the flashing still continue so I decided to stop it.
After some time I try to plug my device again but the computer dont recognized the phone anymore, the connected device sound has not triggered and the miflash tool has not recognized my phone anymore and the blinking notification light is not present too.
Please anyone help me I need this phone to attend my Online Classes please.

Similar situation here. Tried to flash Magisk. Stuck on a boot loop. Then I tried to flash Global a2 lite ROM.
Now my phone is stuck in EDL mode with 900E Drivers I see random numbers in MiFlash. When I install 9008 drivers I see the COM10 and the same random numbers on the device info in the MiFlash tool.
Taking like 30 minutes to flash and never ends. If someone has the Auto unbrick Mi a2 Lite software
please post it here so we can try to flash with this one.

Related

bricked mi max(?)

hello everybody.
i got a 3/64gb mi max and tried to flash twrp and the miui 8 eu version.
For some reason the phone bricked (flashing the MI logo and then nothing).
i managed to get it on edl mode, i downloaded the official chinese and eu roms but no matter which one i try to flash i get this message and it doesnt go on after that.
any suggestions ?
the phone goes into EDL mode, and also goes into fastboot mode when i keep the vol - and power button. It's working but i can't flash the official rom cause of this message and when i try to flash TWRP, the screen flashes the MI logo and then nothing.
Same problem I had when flashing the latest EU ROM using TWRP with a locked bootloader. Here's what I did to fix it:
1. Make sure you have the latest Qualcomm USB drivers installed
2. Start up Miflash, make sure the right fastboot package is selected
3. Connect your phone to the PC. Hold down Power, Vol- and Vol+ together until you get a short vibration.
4. Check Windows Device Manager. Under Ports, you should see a Qualcomm 9008 QDLoader device. If you see a 9000 port or whatever, disconnect the phone, reconnect it and hold down all three buttons again.
5. Press Refresh in Miflash, you should see a COM10 device. Flashing should be successful.
oatcooky said:
Same problem I had when flashing the latest EU ROM using TWRP with a locked bootloader. Here's what I did to fix it:
1. Make sure you have the latest Qualcomm USB drivers installed
2. Start up Miflash, make sure the right fastboot package is selected
3. Connect your phone to the PC. Hold down Power, Vol- and Vol+ together until you get a short vibration.
4. Check Windows Device Manager. Under Ports, you should see a Qualcomm 9008 QDLoader device. If you see a 9000 port or whatever, disconnect the phone, reconnect it and hold down all three buttons again.
5. Press Refresh in Miflash, you should see a COM10 device. Flashing should be successful.
Click to expand...
Click to collapse
Just tried it. Same message shows up unfortunately
I have the same Problem, bat i use a old Version of Mi Flash. IT works better
Gesendet von meinem Mi Max mit Tapatalk
May i know what windows version you're using it..?, coz old version of MiFlash tool doesn't support running under 32bit system.
Maybe you can try using latest version of MiFlash tool..
You can download it from here..
If official link above doesn't work..just download from here..
Hope it's help..
You must also mark option "Flash all" in MiFlesh.
There is a solution. I have tried everything but mistake was to obvious to posiible really. I was using wrong ROM version to flash it. Had "can not read from port ..." or "can not received hello packet data".
Firts of all download miflash beta. Then check your processor type because this is what define your rom. I thought that my Mi Max 64GB is a hydrogen ROM. Wasted because of that about 30 hours of my precious life Then I realised that my ROM is helium. I downloaded helium_global_images_V8.1.9.0.MBDMIDI_20170103
Flashed it for a first time.
google:
Discussion Solved Bootloop, Cannot receive hello packet, Object reference not set to an

Device bricked - white LED only flashing when connected to USB cable, no EDL possible

Hi
I need really some good ideas.
My Mi Mix 2 bricked first when I was flashing the global rom via TWRP.
Installation worked out, I choose restart system in TWRP and then the screen got black and nothing happened any more.
At that time device was in EDL mode and was detected by MiFlash.
After some days I solved the "cannot receive hello package" issue and MiFlash started to flash the system (I choose China stable as first recovery).
Unfortunately MiFlash was not successful, I got the "Not enough storage is available to process this command.(0x80070008; Max buffer sector is 256)" failure message and since that the device is more or less fully dead:
no reaction at all on any hard button combinations
no EDL detected
no fastboot
The only reaction I see is the white LED light flashing when connected to a USB cable, but the PC does not recognize the device at all anymore.
Any idea how I can bring back the device to life?
Thnx
no one any idea to support?
How did you solve it man
why don't you try to use deep flashing cable to get edl mode

MiFlash: Device in EDL not showing up in MiFlash device list.

Hi,
I was trying to flash Lineage OS on my Whyred, and installed non-ARB ROM over MiUi 10 and my device is now bricked.
I can see my phone in EDL mode, as I can see "Qualcomm HS-USB QDLoader 9008" in the device manager.
I have also installed all the drivers from MiForum thread-784616-1-0. (I don't have right to post complete link)
Even after restart and power cycling the phone, my device does not show in MiFlash tool, and I get "Length cannot be less than zero. Parameter name: length" error. I have tried three different versions on MiFlash tool.
I am on Win10 64 bit
I have unlocked bootloader with TWRP installed before the brick happen.
EDIT:
I tried QFIL methods but it was unsuccessful.
Qfil tool detects the phone without issue, but flashing fails with the following error:
Code:
ERROR: Only nop and sig tag can be received before authentication.
1. none of the custom rom has ARB switched on! how did you brick your phone by flashing Linage??? I cannot understand
2. you cannot JUST go in to EDL mode with RN5pro since Xiaomi has removed the pressing volumes and power button 30 seconds to get in to edl mode! you have remove BACK PANEL of rn5p and short the testpoints with metal & plug the usb in with pc in order to ender edl mode!
3. even if you enter in edl more! miflash will ONLY flash if your MI account has been authorised from china!
now what exactly is your device state? can you reboot enter in fastboot mode?
fastboot roms cannot be placed in LONGGGG paramiters! put it in C drive and rename folders to smaller.. like C:\1 and put all the unzipped Tz files here to flash!
if you cannot flash by mi then you should consider Qualcom Qfil flasher! , RN5p is snapdragon device and can be flashed with QFIL!
YasuHamed said:
1. none of the custom rom has ARB switched on! how did you brick your phone by flashing Linage??? I cannot understand
2. you cannot JUST go in to EDL mode with RN5pro since Xiaomi has removed the pressing volumes and power button 30 seconds to get in to edl mode! you have remove BACK PANEL of rn5p and short the testpoints with metal & plug the usb in with pc in order to ender edl mode!
3. even if you enter in edl more! miflash will ONLY flash if your MI account has been authorised from china!
now what exactly is your device state? can you reboot enter in fastboot mode?
fastboot roms cannot be placed in LONGGGG paramiters! put it in C drive and rename folders to smaller.. like C:\1 and put all the unzipped Tz files here to flash!
if you cannot flash by mi then you should consider Qualcom Qfil flasher! , RN5p is snapdragon device and can be flashed with QFIL!
Click to expand...
Click to collapse
I don't know how it got bricked AFTER installing Lineage OS.
Current situatiuon
1) Mi Flash tool does not list/detect my phone even though I am in EDL mode.
2) Qfil tool detects the phone without issue, but flashing fails with following error:
Code:
ERROR: Only nop and sig tag can be recevied before authentication.
Did you try this method?
[email protected] said:
Did you try this method?
Click to expand...
Click to collapse
Yes, and the above error is after trying this method.

[Help needed from Devs] Note 5 Pro Unbrick Project

A BIG SORRY for a long post. But I am sure its worth reading step by step. Because many peoples are stucked in same situation, no straight forward solution for this issue is available till now. All solutions are based on 50/50 success ratio.
I think if my issue is resolved then it can become WORLD's FIRST SOLUTION to UNBRICK NOTE 5 PRO with 100/100 success ratio.
About Me: I am an ordinary Android user since years. I know how to root and install TWRP and Custom ROMs on any Android Phone. I am not a Developer, every thing discussed here is purely gained by experiments by playing with my phone.
After playing with my bricked phone I reach at a point where I am hopeless and I think at this stage a Developer can help me only, who have deep knowledge of android OS. That's why I called Devs to help me.
About Phone I have Note 5 Pro Global (whyred)M1803E7SG. Phone is under warranty but unfortunately Front Glass of my phone is broken few months ago but still working, so Mi Service Center refused to accept my phone under warranty due to broken Front Glass. Tried to repair my phone by a local Phone Service Shop, thay have all professional tools like UMT, Avangers, MedusaPro etc. but they were also unable to repair my phone. Now I have no option left other than I should repair it by myself.
Phone was on ARB4, was working fine. Bootloader Unlocked and I have rooted it long time ago and was playing with it since it is rooted by flashing different Custom ROMs on daily basis.
Currently phone was working fine on Masik X 4.1 ROM. Some days ago I flashed Masik X 5.0 ROM via TWRP on my phone and after reboot phone became dead and went to EDL 9008 mode. I noticed that I flashed Masik X 5.0 for Note 6 Pro (tulip) ROM on it mistakenly.
Journey Stats Here:
1 - After bricking my phone I tried to flash fastboot ROM for whyred in EDL mode, phone flashed successfully but still stucked in EDL mode. Tried all fastboot ROMs from ARB2 to ARB4 but still no sign of life, phone was not coming out of EDL mode. Also tried "test anti4.zip" files as well but phone is still in EDL mode after a successful flashing.
2 -After that I tried to flash fastboot ROM of Note 6 Pro (tulip) in EDL mode, after flashing complete when I tried to turn ON my phone, I noticed that phone try to start with vibrate and charging light blinks for a while but nothing on Screen and phone dead again. I checked with USB cable attached to laptop, nothing appear in Device Manager. Here I opened my phone and bring it to EDL mode via Test Point method.
3 - Then after searching on internet I saw on a forum where another person was in same situation. He mentioned his phone display was turning ON on a Mi 6X (wayne) ROM but with "Press any key to shutdown" message on screen. So tried same with Mi 6X (wayne) ROM. Phone is turning ON with "Press any key to shutdown". So I started playing with Mi 6X ROM. I started replacing Mi 6X ROM file with Note 5 Pro files one by one and flashing my phone again and again with every one new file (took so many hours in playing with my phone:crying. Initially had many issues like: missing keymaster64.mbn file as Mi 6X uses keymaster64.mbn but Note 5 Pro is using keymaster.mbn file (so corrected .xml and .bat files according to need), Unable to mount Persist partition in TWRP (corrected it by terminal method in TWRP by using command "make_ext4fs /dev/block/bootdevice/by-name/persist", phone was going to Fastboot for a while, Not going to recovery mode, No USB detection on laptop in Device Manager. Fastboot lasts for a half second and then phone goes off.
In short at the end finally I noticed only three files "abl.elf, pmic.elf, xbl.elf" from Mi 6X ROM are responsible for turning my phone ON.
4 - So I replaced "abl.elf, pmic.elf, xbl.elf" files from Mi 6X ROM with Note 5 Pro ROM files and flashed my phone with this new modified ROM in EDL mode. Phone turned on without any "Press any key to shutdown" message on screen. Now phone can go to fastboot mode and detected on USB on my laptop. But not going to Recovery mode, after pressing Vol UP + Power Button, only a black screen and nothing happening on my laptop Device Manager (no driver at all). In fastboot mode I flashed "PitchBlack-whyred-2.9.0-20190501-1030-OFFICIAL" recovery (initially I tried TWRP Recovery for whyred but in TWRP phone was not detected as MTP device on my laptop, so I used Pitchblack Recovery) and after issuing boot command to recovery.img I can go to Pitchblack recovery mode, phone detected on USB port as "Note 5 Pro", MTP drive appear in My Computer, I can copy/paste files in phone Storage. In Recovery mode I flashed Official "miui_HMNote5Global_V10.3.1.0.PEIMIXM_d4d2c9f2aa_9.0" ROM. Phone flashed successfully but after reboot phone went to EDL mode again. So I revived it again with modified ROM.
5 - After revival I tried to boot phone in normal way, I noticed that MI Splash screen is blinking with behavior: Splash screen appears fine for a while and on second blink Screen is inverted then 3rd blink Screen fine and 4th blink screen inverted and so on till I reach to MIUI10 welcome screen. On welcome screen the behavior is same like once fine then inverted. But here my touch screen is not working, I can't go after this screen. Phone is not allowing to touch Next button. I can charge my phone with charger connected. Phone detected as "Note 5 Pro" on my laptop.
6 - I rebooted phone to fastboot mode, tried to flash "whyred_global_images_V10.3.1.0.PEIMIXM_20190522.0000.00_9.0_global_8201319a7e" with MiFlash but can't flash due to "Product Mismatch" warning by MiFlash. Tried Mi 6X ROM and MiFlash started flashing fine.
7 - Then I flashed "boot.img, recovery.img, cust.img, system.img" files by using fastboot flash xx xxx.img commands for Note 5 Pro. Fastboot flashed all files successfully. But after rebooting phone behavior is same like blinking inverted screen and touch not working.
8 - Now I am helpless at this stage. Tried all ways to revive my phone. Nothing else is remaining as I think. No other file is remaining which I can try.
HELP REQUIRED FROM A Developer
I reached on a stage where my phone is now "Semi Unbricked" but is still useless for me. But I hope some Developer can help me to revive my phone.
My Note 5 Pro is converted to Mi 6X but touch screen is not working. Screen is working fine in Pitchblack Recovery mode, phone is responding in Fastboot mode but as it is the fastboot mode of Mi 6X on a Note 5 Pro so it is useless for my phone.
Kindly assist me further so I can replace Mi 6X fastboot with original Note 5 Pro fastboot so that I can flash Note 5 Pro ROM on it.
Waiting for a very positive and prompt reply.
Regards!
Any body knows about display/touch driver files inside Android OS???
My touch screen is not working at all on MIUI Welcome screen. I want to embed Display Driver files in ROM so I can go forward ahead of this Welcome Screen.
I have tried so many ROMs from different Xiaomi models, replaced so many files one by one, spent too much time on doing this all. But the only combination of files works mentioned below:
abl.elf (must be from wayne ROM)
pmic.elf (must be from wayne or tulip ROMs, both working)
xbl.elf (must be from wayne ROM)
All other files from whyred ROM are OK to flash to bring my phone alive.
ROMs Used:
whyred_global_images_V10.3.1.0.PEIMIXM_20190522.0000.00_9.0_global_8201319a7e
wayne_images_V10.3.3.0.PDCCNXM_20190514.0000.00_9.0_cn_1d4725ac4d
tulip_global_images_V10.3.2.0.PEKMIXM_20190426.0000.00_9.0_global_2264f9bd86
Now I concluded all this mess as: I can never go back to whyred original ROM. The only way left is to use my phone as a Mi 6X by name if touch screen of my mobile gets start working.
Some body please help me in replacing Display Driver files of whyred with wayne files.
Kindly assist me to pass through this step. I want to see what's working and what's not after MIUI Welcome Screen. e.g. IMEI, BT, WIFI, SOUND, CALL etc......
Please help

Redmi 1s hard bricked

Hello everyone, I have and old Xiaomi Redmi 1s which is having an issue.
When I connect the phone to charging cable the red led blinks once and then nothing happens
When I connect the phone to pc. The pc recognizes it with the name something Qualcomm and nothing happens in the phone same red led blinks and then nothing
When the phone is connected to pc without the battery the mi logo flashes and turns off in every 2 sec, and when I press just the vol down button the fastboot mode flashes and stays there.
I have tried flashing .tgz fastboot rom from fastboot by miflash tool. But nothing happens same situation.
Plzz Help me.
Hi, I've successfully resuscitated my redmi 1W. The steps are the same except you have to select the redmi 1S rom from Xiaomi. LEt me know if you need help
The downside is that the phone now has a generic serial number. (If you know of now to reinsert the phone serial number, please let me know) So if you have apps that needs to detect the phone serial number, please do not follow these steps.
Redmi 1W recovery steps

Categories

Resources