Hi, I decided to unlock bootloader on my Xiaomi Mi 11 Lite 5G NE. I downloaded Mi Unlocker, and did everything as it was described on the internet: enabling debugging functions, unlocking OEM, logging to Mi Account etc, installing all required drivers etc. The problem is that after entering fastboot mode there's literally no device in Device Manager associated with my phone, so neither Mi Unlocker, nor fastboot can detect my phone. I tried reinstalling drivers, restarting PC, changing cables, ports, different version of adb, fastboot, and MI Unlocker with no result.
One thing that helped (but only for a minute) was doing factory reset, and then fastboot mode image changed to some older one, and then it appeared in device list, and Mi Unlocker detected it, but sadly there was an error saying "Couldn't verify device", and then fastboot exited, and after rebooting previous (newer) image appeared, and problem was back. Then I thought: hey, maybe I have too old system? So I upgraded it to MIUI 13, and now the problem is still there, but fastboot image has been reduced to only barely visible label.
Maybe I'm using obsolete drivers? Maybe you have some recent drivers, or maybe I should try another PC/linux booted from pen?
install mi pc suite 3.2.1.3111 for the drivers and check in windows/peripherals if drivers are corrected installed
Nope, it didn't help. I forgot also to mention, that phone is discoverable by adb, and I can execute adb reboot bootloader without any problems
Try (with minus - there are two diff modes):
adb reboot-bootloader
The same thing happens FASTBOOT label, and no device is detected.
Any other advices? I tried with Linux, but with the same results
Okay it's strange, but now I tried logging in to my Google account and switching most of debugging options in developer settings to on, and now it appeared as fastboot device after reboot, and I was able to unlock it
But now, unfortunately, when I wanted to flash something to phone, then fastboot disappeared again - wtf is going on?
Have you tried a different USB cable?
fibur said:
But now, unfortunately, when I wanted to flash something to phone, then fastboot disappeared again - wtf is going on?
fibur said:
But now, unfortunately, when I wanted to flash something to phone, then fastboot disappeared again - wtf is going on?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
I can help you! Please check PM.
mvikrant97 said:
I can help you! Please check PM.
Click to expand...
Click to collapse
{
"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"
}
Okay, the issue was broken USB port, now it works perfectly
Related
Hello there,
my issue is that when i go in bootloader mode, i have a blackscreen, then my phone switch off. The system ui (custom rom Crdroid) and the recovery (orange fox) are working well.
I recognize also that when i reboot, i don't have anymore the MI logo where you have the status of your bootloader when it's unlocked.
More of it, when i plug it on windows , i cannot access to its usb storage (i tried also in mounting it through twrp, but same issue), nothing appears. For example, with an "adb devices" cmd command, no device can be found.
When i check the Windows devices manager, i can see an "unknown usb device" (i tried to force to reinstall drivers on it like the latest google usb driver, but windows refuse it, saying that it has the best and latest one for it).
{
"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"
}
Debugging mode is well enabled
Drivers have been reinstalled (the latest miflashtool install all what is needed)
Nothing appears on my smartphone when i plug it to windows (before i had a notification ot choose in charge mode, usb mode, etc...)
Plug to different usb port has been done without succeess
The phone doesn't appear in miflashtool obv
Restoring a previous backup didn't change the issue (i'm using the custom rom crdroid).
I guess all the things are linked but how i can fix it if i don't have access anymore to my bootloader mode to be able to flash some *.img via fastboot or if i cannot transfer files to my phone to operate in recovery, and more WHAT to do?
I hope you guys, will be able to help. The issue can be really annoying, and stuck me in "no rom update and no transfers of anything possible" situation.
Thank you beforehand
@bonbonboy
Try flashing the firmware through recovery from here https://androidfilehost.com/?fid=11410963190603850663 then reboot device and send it to bootloader via command adb reboot bootloader
It works like a charm!
Mi logo back, adb commands run, usb transfers work and no more error in the device manager.
You saved my day :good::good::good: Thanks a lot !
Hi! I think I hard bricked my Redmi Note 4. I tried to install Lineage OS 16, unlocked bootloader and installed TWRP. However, after installing the Lineage OS it keept boot looping. I did all the procedure of wiping davilk, data, cache and system, then went to install and I added this packages: Lineage OS 16, Gapps, Lineage SU addon, unlock_bootloader ZIP, Lazyflasher and Universal DM-Verity, ForceEncrypt.
After flashing it just turned off and now I cannot turn it on. I held power button for 5 minues, nothing. Can't enter fastboot, screen doesnt turn on at all. When I plug it to charger it blinks red notification light. When I connect it to the PC I hear the Windows 10 notification sound but Windows says it cannot recognize the device.
I'm desperate, I think I've tried everything. Please HELP!
If you have the Snapdragon version, try to put it in EDL mode (entering it with the test points, you have to remove the back cover) and reflash an official rom with Mi Flasher. Then you go from the beggining in order to install your custom rom.
I tried that but I can not make it to short the circuits. I followed this inctruction https://forum.xda-developers.com/redmi-note-4/help/xrn4-sd-4-gb-64gb-black-screen-flash-t3761858 but I can't get anything other than "Qualcomm HS-USB Diagnostics 900E". Idk if I need a special kind of metal to short it or maybe the pins are shown incorrectly. I have the Snapdragon version.
UmbraOG said:
I tried that but I can not make it to short the circuits. I followed this inctruction https://forum.xda-developers.com/redmi-note-4/help/xrn4-sd-4-gb-64gb-black-screen-flash-t3761858 but I can't get anything other than "Qualcomm HS-USB Diagnostics 900E". Idk if I need a special kind of metal to short it or maybe the pins are shown incorrectly. I have the Snapdragon version.
Click to expand...
Click to collapse
The pins shown are correct. Try with sharp scissors or a tiny plier. An option is a cable with solid core.. If you get "Qualcomm HS-USB Diagnostics 900E" you are ready to go to Mi Flash, there is no problem that "9008" does not show up..
I did it, this is what I get from MiFlash
{
"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"
}
UmbraOG said:
I did it, this is what I get from MiFlash
Click to expand...
Click to collapse
you get it imidiatelly or at the end? If you get it at the end, try to ignore it and start the phone.. Otherwise try changing at the right bottom of mi flasher to "clean all" and try again. Also i found something here at the k20 threads, you uncheck the check point from the condifuration of the mi flash..
Cleaning the checkpoint thing worked and MiFlash said the flash was successful, but the phone still doesn't turn on or give any signs of being alive. I guess the only hope now is to give it to repair when the whole covid thing ends. Anyways, thanks for helping me.
Good evening,
So I wasn't aware of this DPI bootlooping issue until it happened to me today. I tried changing my DPI to 1000, since it worked to me before (not yet MIUI 11)
Here are some points to consider:
> USB debugging OFF
> bootloader LOCKED
>basically just stock pocophone f1 without any trace of modding.
>Mi Flash Unlock might unlock my bootloader, but I dont want to lose personal data. I tried logging in and my account has permissions to unlock. I only consider this as a last resort. (Is this feasible by the way?)
Here are some things I discovered
1. Using command prompt:
> fastboot devices - detects my phone
> adb devices - detects my phone if I select "Connect with MIAssistant" on stock recovery
> adb shell wm density -doesn't work (I think because bootloader is locked)
> fastboot flash recovery - doesn't work either(bootloader locked)
"adb devices" did not work at first. I tried doing it on fastboot to no avail.
But after some time exploring, "adb devices" worked when selecting "Connect to MIAssistant" on stock recovery
2. It actually is not "not booting", because I tried connecting a mouse using OTG when the loading circle appeared, then a very small mouse cursor appeared.
Here is a picture
{
"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"
}
3. What I can tell is, it actually boots but encounters a problem when trying to display with that DPI setting. Correct me if I am wrong with #2 and #3.
Is there any solution to this without wiping my personal data?
Edit1: My solution here: https://forum.xda-developers.com/poco-f1/how-to/pocophone-f1-flash-stock-rom-locked-t4084979
Issue Solved with flashing stock rom. I will edit the post with a link on a new thread on how I did it even with a locked bootrom and USB debugging OFF. I hope that new thread will help others in this same problem.
hii please help fast
i have same problem i also have bootloader unlocked
i tried command in adb "adb shell density reset"
but it shows error closed
please replay soon
Kunalkp123 said:
hii please help fast
i have same problem i also have bootloader unlocked
i tried command in adb "adb shell density reset"
but it shows error closed
please replay soon
Click to expand...
Click to collapse
you need to time it correctly, or use adb's wait for device command
Can I copy somehow the files from my dead phone to PC, using fastboot command? Maybe by EDL mode
hi guys please help me ive tried everything i saw on the internet but still no luck,
i tried reinstalling the usb driver but its still the same.
any suggestions from you guys?
maybe theres other way?
TIA
Which OS? Which drivers do you use? What do you see in device manager? Is your phone really in fastboot mode?
Another way is to use Linux OS, fastboot should work without any special drivers.
bonluis said:
hi guys please help me ive tried everything i saw on the internet but still no luck,
i tried reinstalling the usb driver but its still the same.
any suggestions from you guys?
maybe theres other way?
TIA
Click to expand...
Click to collapse
possibly what you are missing are the Qualcomm drivers for xiaomi mi a3
What's the command that you used to detect the phone while it's fastboot mode ? My guess it's ''adbdevices'' , if you did that you should try ''fastboot devices '' .
docrates1975 said:
possibly what you are missing are the Qualcomm drivers for xiaomi mi a3
Click to expand...
Click to collapse
Qualcomm drivers are for EDL mode. For fastboot and ADB, drivers come from Google.
docrates1975 said:
possibly what you are missing are the Qualcomm drivers for xiaomi mi a3
Click to expand...
Click to collapse
I already installed that but still no show
_mysiak_ said:
Qualcomm drivers are for EDL mode. For fastboot and ADB, drivers come from Google.
Click to expand...
Click to collapse
Already tried Google USB driver
_mysiak_ said:
Which OS? Which drivers do you use? What do you see in device manager? Is your phone really in fastboot mode?
Another way is to use Linux OS, fastboot should work without any special drivers.
Click to expand...
Click to collapse
This might be my last resort :crying:
{
"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"
}
Bre3eze said:
What's the command that you used to detect the phone while it's fastboot mode ? My guess it's ''adbdevices'' , if you did that you should try ''fastboot devices '' .
Click to expand...
Click to collapse
it worked bro thanks!
but i cant use adb right?
No , you can't use adb while in fastboot mode , only when phone is booted into system and you allow the device . Glad it worked
Dear I have a xiaomi my a3 when I go from a custom rom to a stock the phone that I do in fastboot mode, the bootloader is blocked,
and if it does not come out I have turned it off and when I start it it remains in fastboot mode, please help me with this topic.
Stay tuned to your comments
I followed the steps, but I can't get into bootloader mode. Please help. When I reboot to bootloader, the screen is blank and doesn't respond to fast boot commands.
Turn off phone then hold volume up and plug into computer to get to bootloader mode (screen should still be off)
If computer doesnt recognize fastboot mode then your computer is lacking the right driver
I did follow the steps and downloaded both the google USB driver and driver for my device model from sony mobile communications via 'install OEM drivers'. Did I miss anything? In fact, how do I remove and reinstall both drivers if they are faulty?
RP1408 said:
I did follow the steps and downloaded both the google USB driver and driver for my device model from sony mobile communications via 'install OEM drivers'. Did I miss anything? In fact, how do I remove and reinstall both drivers if they are faulty?
Click to expand...
Click to collapse
I remember window 10 and 11 block driver if you install normal through double click. You need to get to device manager and update driver manually. Google it
i tried but still the same problem. From this screenshot , could you make out anything regarding anything ive might have missed. i installed the google usb driver and fastboot driver by the device manager as stated in the previous comment.
{
"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"
}
RP1408 said:
i tried but still the same problem. From this screenshot , could you make out anything regarding anything ive might have missed. i installed the google usb driver and fastboot driver by the device manager as stated in the previous comment.View attachment 5805835
Click to expand...
Click to collapse
Boot windows in safe mode, and disable driver certification and reinstall the driver.
RP1408 said:
i tried but still the same problem. From this screenshot , could you make out anything regarding anything ive might have missed. i installed the google usb driver and fastboot driver by the device manager as stated in the previous comment.View attachment 5805835
Click to expand...
Click to collapse
Hey, man I had a problem with the drivers in bootleader mode on my 5 IV as well. Which had the Android under Other Devices with a question mark, meaning it couldn't find the drivers.
You could try forcefully installing the drivers for the device as I explained how to do in my post here: https://forum.xda-developers.com/t/...-and-flashing-firmwares.4537183/post-88051049
Make sure you don't have US version because you can't unlock bootloader on it
RP1408 said:
i tried but still the same problem. From this screenshot , could you make out anything regarding anything ive might have missed. i installed the google usb driver and fastboot driver by the device manager as stated in the previous comment.View attachment 5805835
Click to expand...
Click to collapse
There's a Sony driver you jeed to use, SA2000 or some weird name. Did you get that one? Install it by right clicking on the Android device name with yellow warning triangle. Select the install disk manually and assign that one to manually install