My Mi A2 has got BRICKED!!!!!!!! when i am trying to flash stock rom i MI FLASH TOOL phone doesnt support because USB DEBUGGING MODE not enabled. i cant open my phone for brick. So now what can i do?
can you put phone in fastboot?
DiesFrae said:
can you put phone in fastboot?
Click to expand...
Click to collapse
yes. in fastboot. and command "fastboot oem edl" its not working, says Waiting for device
Oline1032 said:
yes. in fastboot. and command "fastboot oem edl" its not working, says Waiting for device
Click to expand...
Click to collapse
did you check if fasboot reads your device?
cmd: fastboot devices
DiesFrae said:
did you check if fasboot reads your device?
cmd: fastboot devices
Click to expand...
Click to collapse
i checked command "fastboot devices" but it show blank. no message
Oline1032 said:
i checked command "fastboot devices" but it show blank. no message
Click to expand...
Click to collapse
it should show an ID for your device. Have you installed latest adb & fastboot drivers?
link to adb drivers https://androidfilehost.com/?fid=24686681827312411
DiesFrae said:
it should show an ID for your device. Have you installed latest adb & fastboot drivers?
Click to expand...
Click to collapse
yes latest adb + fastboot installed. and i had done unlock bootloader + flashing unlock critical with this adb+fastboot
Oline1032 said:
yes latest adb + fastboot installed. and i had done unlock bootloader + flashing unlock critical with this adb+fastboot
Click to expand...
Click to collapse
fastboot should reads your device. try running cmd.exe as admin and switch to another USB port or cable and see the results. just make sure that fastboot devices shows an ID
DiesFrae said:
fastboot should reads your device. try running cmd.exe as admin and switch to another USB port or cable and see the results. just make sure that fastboot devices shows an ID
Click to expand...
Click to collapse
not working:crying::crying::crying::crying::crying:
Oline1032 said:
not working:crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
ask on telegram group then man, i don't know what's going on tbh
Try edl mode
Fastboot oem edl
Oline1032 said:
My Mi A2 has got BRICKED!!!!!!!! when i am trying to flash stock rom i MI FLASH TOOL phone doesnt support because USB DEBUGGING MODE not enabled. i cant open my phone for brick. So now what can i do?
Click to expand...
Click to collapse
Hello, I currently have the same problem. Today I was converting my xiaomi mia2 to mi6x. Everything was normal, until at one point of the transfer miflash gave an error and the transfer stopped, checking the logs I find that simply the USB stopped working, the phone now does not signal by the usb. Now we have a paperweight, apparently. I have researched and apparently can try to repair the phone using the "test point method", which forces the EDL mode on the phone for a few seconds that you should take to flash the rom from MiFlash.
Please check this and try to do so, for the moment I have no tools because we have to disassemble the phone. I hope you have appropriate tools and you can tell me if it works! -> https://en.miui.com/thread-3524265-1-1.html
This other guide is for the A1, but it has information that may be able to help you. -> http://en.miui.com/thread-1680467-1-1.html
EDIT: I can confirm that I solved the brick with this method.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Related
Hi, today i tried to install MIUI 10 following this video: https://www.youtube.com/watch?v=eD5ftq6lTKo
When i could installed it, i tried to re-lock the bootloader with this other video: https://www.youtube.com/watch?v=9C47rmEKkys
But when i reboot the phone, on screen was this message: The system is destroyed, press power button to shutdown.
I tried to unlock again the bootloader to install the system but i receive this message from cmd: FAILED (remote: Token Verify Failed, Reboot the device
)
I don´t know what to do, i tried with test points to flash with miflash, i tried with miflash unlock but i don´t have an account of xiaomi.
when i use this command: fastboot flashing unlock_critical i receive this message: Command not support: the display is not enabled'
Somebody help me :crying:
Flash stock ROM with mi flash
I tried that but miflash show this message: Mismatching image and device. Only have a success message when i flash the wayne rom but ends on 1 second but doesn't install the system.
On htcmania says because the drivers are wrong but i reinstalled from the tutorial ones, google drivers, and miflash drivers and always says the same.
Now i trying with EMMC dongle program(cracked) and it seems like it´s installing the system, but since yesterday, it looks last forever.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Well that program does not did anything, i discover that when the phone is on fastboot mode and plug off the battery, miflash make a process success but it last 24s and don´t do anything, maybe that could be useful for something.
I don´t know what more to do with my phone.
Click to expand...
Click to collapse
If ur bootloader is unlocked try
Fastboot reboot edl
Now try to flash with mi flash in this mode
Note: your phone will look like it's turned off (black screen) in this mode
---------- Post added at 02:35 AM ---------- Previous post was at 02:29 AM ----------
I noticed that you where trying to flash Wayne images in the photo that u attached? Do u own a mi A2 or a 6x?
If you convert your mi A2 to 6x you cannot relock your bootloader
And make sure to delete system update folder and change some Dev conf file to flash miui on your android one device
That command (Fastboot reboot edl) doesn't work, when i send it i get this error: Device is already locked!
The only way my phone can be on edl mode is by Test points, and the miflash says that my phone have a locked bootloader if i try to flash the system.
What is the output of this command
Fastboot oem unlock
hv2002 said:
What is the output of this command
Fastboot oem unlock
Click to expand...
Click to collapse
Araxielfenix said:
Click to expand...
Click to collapse
https://youtu.be/ypDU78c4w_Y
Hey guys
I just bought a new Mi 9 Lite and instantanously wanted to unlock it.
so i did all the steps and then tried to connect with mi unlock the first time to see how long the waiting period is
After i booted into fastboot with volume down + power i connected the phone to the computer and it suddenly went black.
Only in the upper corner it showed a cut off text saying: "any key to shut down" -> see attached photo
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Mi Unlock didnt detect it, and neither did Adb fastboot...
Do you know a fix? i really dont want to send it back...
And im pretty certain this was not my mistake, as i tried it multiple times
Same happens when you try to boot into fastboot with "adb reboot bootloader" ?
BTW to see if your device is properly recognized while you are in Fastboot you should use "Fastboot devices" not "adb devices"
Also make sure you installed all required drivers (Qualcomm ones and the drivers you install from within MiFlash)
the reason is windows 10, on 7 it works
k3lcior said:
Same happens when you try to boot into fastboot with "adb reboot bootloader" ?
BTW to see if your device is properly recognized while you are in Fastboot you should use "Fastboot devices" not "adb devices"
Also make sure you installed all required drivers (Qualcomm ones and the drivers you install from within MiFlash)
Click to expand...
Click to collapse
Thanks for your fast answer!
I just tried it again, and adb as well as fastboot devices do recognize the phone.
The blackscreen from fastboot only appears upon opening the mi flash unlock tool... In the exact same moment...
As you said i tried "adb reboot bootloader", but the same happened upon opening the tool.
I couldnt find the qualcomm ones though, didnt know where to install them from...
Btw. if it helps i have Windows 8.1
But havent had Problems with the Mi9 or Redmi 4 Prime unlock (which just now worked fine)
Romancier said:
I couldnt find the qualcomm ones though, didnt know where to install them from...
Click to expand...
Click to collapse
https://androidfilebox.com/tool/qualcomm-qdloader-hs-usb-driver-32-bit-64-bit/
k3lcior said:
androidfilebox....com/tool/qualcomm-qdloader-hs-usb-driver-32-bit-64-bit/
Click to expand...
Click to collapse
Installed it, and even re-installed all the usual drivers. Still, the black screen pops up as soon as i open the unlock tool...
Check if your phone isn't fake one.
This is unusual for an official Xiaomi device.
arvarobert said:
Check if your phone isn't fake one.
This is unusual for an official Xiaomi device.
Click to expand...
Click to collapse
How would i check?
Also its not from china, but from a well known german vendor so guarantee would be no problem. But everything is fine and believable, so i would have no reason to be suspicious.
I guess i will try with another computer next week or something. Maybe its USB 2.0 or something..
At least thats what that thread suggests: https://forum.xda-developers.com/redmi-note-5-pro/help/help-press-key-to-shutdown-fastboot-t3816021
Thanks for your suggestions!!!
Romancier said:
How would i check?
Also its not from china, but from a well known german vendor so guarantee would be no problem. But everything is fine and believable, so i would have no reason to be suspicious.
I guess i will try with another computer next week or something. Maybe its USB 2.0 or something..
At least thats what that thread suggests: https://forum.xda-developers.com/redmi-note-5-pro/help/help-press-key-to-shutdown-fastboot-t3816021
Thanks for your suggestions!!!
Click to expand...
Click to collapse
Is your phone recognized in device manager when you are in fastboot?
Also i heard there is some bug/incompatibility with Ryzen CPU's, do you have Ryzen or Intel?
k3lcior said:
Is your phone recognized in device manager when you are in fastboot?
Also i heard there is some bug/incompatibility with Ryzen CPU's, do you have Ryzen or Intel?
Click to expand...
Click to collapse
Indeed it is recognizes in adb as well as in fastboot.
It's an old Thinkpad im working on, so its an Intel. I still only have simple Usb-ports.
But im surprised as it has worked with the Mi 9 also a few weeks ago...
I have a Nokia 8 model TA-1052 (this is NB1, correct?). It has a locked bootloader and is running Android 9.
I understand the HMD service for unlocking the booloader is no longer available and the only option now is using a Hikari's website.
Before I try Hikari's method I want to make sure that fastboot is working (I understand it is required?).
With the phone connected, the command "adb devices" show the phone listed but any fastboot command seems to not being able to find the phone (e.g. "fastboot devices" returns nothing).
Am I missing anything?
Thank you.
Assuming you are on Windows what does device manager show when you put the phone into fastboot mode?
Obviously you need a working driver for fastboot mode which is separate from the adb driver - how did you install the drivers and which ones did you use?
dt_matthews said:
Assuming you are on Windows what does device manager show when you put the phone into fastboot mode?
Obviously you need a working driver for fastboot mode which is separate from the adb driver - how did you install the drivers and which ones did you use?
Click to expand...
Click to collapse
I don't have any specific Nokia drivers installed. The only USB driver showing (that seem to be related) is "ADB Interface".
I know that for some people the Nokia driver comes on the phone but mine isn't. Where can I get the driver from?
EDIT: in download mode the Win10 Device Manager shows an unknown "Android" device under other devices
There is a free unlock method with a tutorial on how to unlock: https://www.techmesto.com/guide-unlock-bootloader-nokia-android-phones/
emufan4568 said:
There is a free unlock method with a tutorial on how to unlock: https://www.techmesto.com/guide-unlock-bootloader-nokia-android-phones/
Click to expand...
Click to collapse
Thanks that worked
emufan4568 said:
There is a free unlock method with a tutorial on how to unlock: https://www.techmesto.com/guide-unlock-bootloader-nokia-android-phones/
Click to expand...
Click to collapse
This is an essential part of unlocking the bootloader.
emufan4568 said:
There is a free unlock method with a tutorial on how to unlock: https://www.techmesto.com/guide-unlock-bootloader-nokia-android-phones/
Click to expand...
Click to collapse
i just unlocked my phone with this tool and somehow it's back to android 8.1 oreo, is that the normal behavior?
Hi, i used the methode in the link above but now my phone is stuck on the Nokia logo and won't boot to OS.
I can let the batterij drain and power it on but then i get this message in the picture.
Manually getting it into download mode is impossible (holding combo keys volume down and power looks like that doesn't work)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Some idea how to fix this? Luckely its not my daily driver but a testdevice.
I have it working again, let battery fully drain, then i could get into download mode (holding vol- while plugging usb) then I could run the tool again (had to request new OTP) and now it just boot normally
Hi Dears
i was planing to flash full rom by enhanced tool , by the worng i deleted the partition which shoud not to flash with new rom ( the below partictions ) , how can i flash the full rom . i can boot to fastbootd
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
if you have deleted the cow partitions you can flash the payload.bin via fastbootd (the payload.bin can easily be flashed with FastbootEnhance via fastbootd)
Unfortunately, i flashed fastboot command and the phone died
MsuatafaKhatab said:
Unfortunately, i flashed fastboot command and the phone died
Click to expand...
Click to collapse
People really need to stop trying to flash with fastboot. You should have used Fastboot Enhance. It's pretty straightforward and if you accidentally cleared one partition you shouldn't have in FBE (it's kind of hard to tell with your English if you did or not, sorry), you could have tried to flash just that one partition with fastboot instead of using a script. OnePlus is your only hope now.
Will it go back into to fastboot...?
If you can try and set slot to A . if you get back to fastboot do this
" fastboot getvar current-slot " it should tell you what slot you on...A or B
if you on B then use this to set A active . Use this command to set A active
" fastboot set_active other " or " fastboot set_active a "
Canuck Knarf said:
Will it go back into to fastboot...?
If you can try and set slot to A . if you get back to fastboot do this
" fastboot getvar current-slot " it should tell you what slot you on...A or B
if you on B then use this to set A active . Use this command to set A active
" fastboot set_active other " or " fastboot set_active a "
Click to expand...
Click to collapse
Unfortunately the phone dead not charge no vibration no edl mode , computer not configured it
MsuatafaKhatab said:
Unfortunately the phone dead not charge no vibration no edl mode , computer not configured it
Click to expand...
Click to collapse
RMA.
You've no other option
MsuatafaKhatab said:
Unfortunately, i flashed fastboot command and the phone died
Click to expand...
Click to collapse
& Unfortunately no so solution to bring it back (only official MSM auth)
dladz said:
RMA.
You've no other option
Click to expand...
Click to collapse
This will be online or send device to them
MsuatafaKhatab said:
This will be online or send device to them
Click to expand...
Click to collapse
Mail.
MsuatafaKhatab said:
This will be online or send device to them
Click to expand...
Click to collapse
If you can't get to EDL or otherwise then it'll most likely be a swap or a board change.
Unless they have a lower level flash which I'm not aware of.
None of this can be done remotely.
You can take the back off ...Ground out test points if your up to that...or send back save yourself the head ache .
OnePlus 10 Pro - QDLoader HS-USB - EDL Test Point [9008] MSM
Hello The test point on this phone was shared by me for the first time on the internet. But there is no software available to install it. So my phone is still dead. 9008 usb Requirements to establish a connection: - Disconnect the battery - Plug...
forum.xda-developers.com
Canuck Knarf said:
You can take the back off ...Ground out test points if your up to that...or send back save yourself the head ache .
OnePlus 10 Pro - QDLoader HS-USB - EDL Test Point [9008] MSM
Hello The test point on this phone was shared by me for the first time on the internet. But there is no software available to install it. So my phone is still dead. 9008 usb Requirements to establish a connection: - Disconnect the battery - Plug...
forum.xda-developers.com
Click to expand...
Click to collapse
That'll void his warranty, not great advice buddy
I've already searched for it and can't find anything. The closest I've got is to installing the USB driver. I opened driver_install.exe and still can't find the driver in Device Manager. I have OEM unlocking and USB debugging on. I also have my MI account linked and the unlock folder in C:\.
AlvaroE said:
I've already searched for it and can't find anything. The closest I've got is to installing the USB driver. I opened driver_install.exe and still can't find the driver in Device Manager. I have OEM unlocking and USB debugging on. I also have my MI account linked and the unlock folder in C:\.
Click to expand...
Click to collapse
Check this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
https://new.c.mi.com/global/post/101245
https://en.miui.com/unlock/index.html
NOSS8 said:
Check this
View attachment 5737777
https://new.c.mi.com/global/post/101245
https://en.miui.com/unlock/index.html
Click to expand...
Click to collapse
but the latest version on https://en.miui.com/unlock/index.html is 6.5.224.28
AlvaroE said:
View attachment 5738201 but the latest version on https://en.miui.com/unlock/index.html is 6.5.224.28
Click to expand...
Click to collapse
Not important, the path and the drivers are.
NOSS8 said:
Not important, the path and the drivers are.
Click to expand...
Click to collapse
Oh MiUsbDriver.exe is there thanks!
but i get this with or without phone connected in fastboot mode
AlvaroE said:
Oh MiUsbDriver.exe is there thanks!
View attachment 5738207 but i get this with or without phone connected in fastboot mode
Click to expand...
Click to collapse
Just connect the phone but not in Fastboot mode.
NOSS8 said:
Just connect the phone but not in Fastboot mode.
Click to expand...
Click to collapse
I instead used the driver from the driver folder
AlvaroE said:
I instead used the driver from the driver folder
Click to expand...
Click to collapse
Yeap, now edit your thread title by adding [SOLVED].
Cant unlock bootloader with several versionsofunlock tools.
Latest tool v2 alpha builds recognizes phone when it is started mi ui. Then it reboot phone to fastboot , windows gling glang sound and then tool shows no phone connected. Tried wuth 2 cables. Checked devicemanager- when mi note 9 in fastboot it appears as android with esclamation mark.
Tried to reinstall adb drivers and also usb qualcom. Same.
In windows or in ubuntu note 9 is always recognizes and can accesss its internal storage.
dzincha said:
Cant unlock bootloader with several versionsofunlock tools.
Latest tool v2 alpha builds recognizes phone when it is started mi ui. Then it reboot phone to fastboot , windows gling glang sound and then tool shows no phone connected. Tried wuth 2 cables. Checked devicemanager- when mi note 9 in fastboot it appears as android with esclamation mark.
Tried to reinstall adb drivers and also usb qualcom. Same.
In windows or in ubuntu note 9 is always recognizes and can accesss its internal storage.
Click to expand...
Click to collapse
Use the official tool and install the drivers (remove the drivers previously installed before and restart).
https://new.c.mi.com/global/post/101245
https://en.miui.com/unlock/index.html
Tried version in link- same situation.
Looks like problem is that windows is loosing connection when phone goes in Fastboot.
This is how device manager looks like when phone in fastboot
dzincha said:
Tried version in link- same situation.
Looks like problem is that windows is loosing connection when phone goes in Fastboot.
This is how device manager looks like when phone in fastboot
Click to expand...
Click to collapse
https://avalonsciences.com/wp-conte...Signature-Verification-on-Windows-8-or-10.pdf
Tried to turn off signature verification, but then bittlocker started to behave strange at boot up/couldnt enter code - 8 numbers.
Then tried to reinstall one of 4 ubuntu laptops. There got boot failure, prepared usb with another tool, then got another boot failure.
Maybe there are tools for Linux to do bootloader unlock?
dzincha said:
Tried to turn off signature verification, but then bittlocker started to behave strange at boot up/couldnt enter code - 8 numbers.
Then tried to reinstall one of 4 ubuntu laptops. There got boot failure, prepared usb with another tool, then got another boot failure.
Maybe there are tools for Linux to do bootloader unlock?
Click to expand...
Click to collapse
I had the case with an Intel W10 PC, as soon as I launched Miunlock the device disappeared, I tried all without success but with an Amd W10 PC, no problem (sometimes it's the opposite).
There are other ways to unlock the bootloader but I don't recommend them (do a search), too risky, anyway if you have a driver problem it won't change anything.
https://forum.xda-developers.com/t/...oader-of-xiaomi-devices-on-mac-linux.3782444/