Press any key to shutdown - Xiaomi Mi 8 Questions & Answers

I can't seem to get either Mi Suite or fastboot to detect my device connecting via USB....I can connect it via USB fine to transfer files, but when connecting in fastboot mode, the phone immediately goes dark and shows "Press any key to shutdown"
someone please help!

Use windows 7 to install fastboot rom.
Windows 10 does not recognize the device on fastboot mode.

Related

[Q] Got factory cable but unknown device

Hi everyone. I need help to solve my brick phone trouble.
This my history:
I tried to flash a Moto X 1058 with a different firmware to be able to introduce a subsidy unlock code. That menu is locked on carrier's original firmware. So, did it with a wrong version and mess the phone, now it restarts automatically with a "boot failure" message and battery is not charging with wall charger.
I got this factory cable mentioned in another post and when is plugged screen says "Battery ok" "Transfer mode: USB Connected" in green text, but Windows won't recognize, says: "Unknown device". Y already tried different ports, different computers, uninstalling and reinstalling drivers but nothing.
I must say that before to use the factory cable, have the "battery low" red text message and once in any of those multiple press-hold keys sequence attempts (CAN'T REMEMBER WICH ONE) I was able to connect to the phone and windows recongnized via "fastboot device", but couldn't do a flash process due to the low battery state.
Any advise? Thanks in advance.
go_nathan said:
Hi everyone. I need help to solve my brick phone trouble.
This my history:
I tried to flash a Moto X 1058 with a different firmware to be able to introduce a subsidy unlock code. That menu is locked on carrier's original firmware. So, did it with a wrong version and mess the phone, now it restarts automatically with a "boot failure" message and battery is not charging with wall charger.
I got this factory cable mentioned in another post and when is plugged screen says "Battery ok" "Transfer mode: USB Connected" in green text, but Windows won't recognize, says: "Unknown device". Y already tried different ports, different computers, uninstalling and reinstalling drivers but nothing.
I must say that before to use the factory cable, have the "battery low" red text message and once in any of those multiple press-hold keys sequence attempts (CAN'T REMEMBER WICH ONE) I was able to connect to the phone and windows recongnized via "fastboot device", but couldn't do a flash process due to the low battery state.
Any advise? Thanks in advance.
Click to expand...
Click to collapse
so fastboot isn't working when you are on the screen that says "battery ok" "transfer mode: usb connected"? Your post is a little confusing. It sounds like you are trying to use rsd or something to flash back to stock FW. You can just do all of this manually through fastboot commands.
all you need to do is download the correct FW for your phone at http://sbf.droid-developers.org/ghost_rcica/list.php
unzip the file
put all the contents (not the folder but the contents in the folder) in the same directory that your fastboot.exe is in
run all of these commands http://forum.xda-developers.com/showthread.php?p=46712761&highlight=flash+stock#post46712761
and your done
jayboyyyy said:
so fastboot isn't working when you are on the screen that says "battery ok" "transfer mode: usb connected"? Your post is a little confusing. It sounds like you are trying to use rsd or something to flash back to stock FW. You can just do all of this manually through fastboot commands.
all you need to do is download the correct FW for your phone at http://sbf.droid-developers.org/ghost_rcica/list.php
unzip the file
put all the contents (not the folder but the contents in the folder) in the same directory that your fastboot.exe is in
run all of these commands http://forum.xda-developers.com/showthread.php?p=46712761&highlight=flash+stock#post46712761
and your done
Click to expand...
Click to collapse
Sorry if I was not clear. What I mean is...
Windows does not recognize the phone with the normal usb cable (the one that cames with the phone), says "uknown device".
Now, I try holding Volume Down + Power buttons, then connect the phone via factory cable and screen says "Battery ok, USB connected", but pc (windows 7) still does not recognize the phone, says "unknown device". I already tried to uninstall and reinstall drivers and different computers, but still the same.
There was only one time when the phone (even with low battery pattern) was recognized by windows with the standard usb cable, but can't remenber wich buttons I pressed.
By the way, I read english better than can write it, hope you can understand but most of all, I beg you can help.
Regards.
go_nathan said:
Sorry if I was not clear. What I mean is...
Windows does not recognize the phone with the normal usb cable (the one that cames with the phone), says "uknown device".
Now, I try holding Volume Down + Power buttons, then connect the phone via factory cable and screen says "Battery ok, USB connected", but pc (windows 7) still does not recognize the phone, says "unknown device". I already tried to uninstall and reinstall drivers and different computers, but still the same.
There was only one time when the phone (even with low battery pattern) was recognized by windows with the standard usb cable, but can't remenber wich buttons I pressed.
By the way, I read english better than can write it, hope you can understand but most of all, I beg you can help.
Regards.
Click to expand...
Click to collapse
windows isn't going to recognize it when it is "fastboot mode" which is the mode where is says "usb connected" or whatever. That is where you run fastboot commands from. If you open a command prompt window (in the directory that your fastboot.exe is in) then you can run "fastboot devices" and it will show that the phone is connected. From there you run the fastboot commands to fix your phone.
mmm no, unknown device it's button sequence matter.
jayboyyyy said:
windows isn't going to recognize it when it is "fastboot mode" which is the mode where is says "usb connected" or whatever. That is where you run fastboot commands from. If you open a command prompt window (in the directory that your fastboot.exe is in) then you can run "fastboot devices" and it will show that the phone is connected. From there you run the fastboot commands to fix your phone.
Click to expand...
Click to collapse
In fact fastboot did not work cause windows don't recognized the devices ("fastboot devices" did not list any device). Drivers were installed in the computer correctly but was a matter on how buttons was pressed.
So if this can help any one with the "UNKNOWN DEVICE" status in windows I did it this way, with the device administrator open (only to monitor the status of your device) in windows pc do this:
1.- Factory cable connected to the phone (so the phone did not restart automatically)
2.- Press POWER button until the phone get off. Before release the power button, disconnect factor cable.
3.- Press POWER + VOLUME DOWN for about 5 seconds, then release POWER BUTTON and keep holding VOLUME DOWN until the screens turns on.
4.- Screen says Connect USB Data Cable. Connect Factory cable. Screen says: "Battery Low" "Transfer mode: usb connected"
5.- Now hold VOLUME DOWN + VOLUMEN UP + POWER BUTTON, the phone turns off.
6.- When screen turns off, release VOLUME UP and POWER button. Screen must says "Battery OK" "Transfer mode: USB Connected"
7.- Windows must recognize the phone and install the drivers.
Try:
fastboot devices
...and your phone must be listed. I recommend to do a
fastboot erase cache
I have a downgrade security warning due to a lock bootloader. Once fastboot could connect to the phone, collect the neccesary data with
fastboot oem get_unlock_data
And follow instructions on https: / / motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
Sometimes you recieve a "your device does not qualify for bootloader unlocking" message, it's only a Device ID string mistake. Be sure to type or paste it correctly. Try again and don't forget to agree the terms below.
I could unlock the bootloader and my phone startup with a previous flash (the one that bricks my phone due to wrong firmware in a locked bootloader phone).
I hope this can help you too. Best regards

Can't Connect to PC and Stuck in Bootloop

I Updated my Lenovo A7000+ then the Update Failed, and now it's Stuck in Bootloop and I Search the internet to Fix it but I need to connect to PC, I Connect it to PC and Didn't Recognize then I Install Lenovo USB Drivers and Still Not Recognize, and now how do i connect this phone to pc.
1. Remove the battery
2. Get into twrp mode by pressing volume and power buttons at a time
3. Now connect to pc with usb cable
4. Your phone will get detected perfectly
5. Do what ever you want

Phone not detected

Hello,
I was on 10.0.7 version, rooted with magisk.
I had error while installing 10.0.8 version, then I downloaded 10.0.7 full rom, and used flash_all_except_data.bat.
Then after rebooting, it runs infinitely on loading animation (colors bar).
When I enter in fastboot, fastboot logo is displayed, but pc doesn't recognize phone anymore (fastboot devices show nothing).
[UPDATE]
I managed to boot with wiping data from recovery (Xiaomi stock recovery).
Now I can use the phone, but I don't have wifi (maybe something messed with vendor).
And I can't flash it because it is not recognized in fastboot mode (tried 3 W10 PCs, and 1 W7, it doesn't show in device manager)...
Can you help me ?
This is because the phone presents different device identifiers to the computer in these modes, and different drivers are needed, so it is possible to have proper drivers installed for one mode, but not the other. The fastboot program is simple and will just show the < waiting for device > message forever if drivers are missing. However, the same message may appear if the drivers are installed correctly, but the phone is not in the proper state with fastboot device IDs.
Make sure you aren't using a USB 3.0 port. Trying changing ports. The USB cable might also be the problem.
try using a direct usb 2.0 port on the pc ....
Otherwise reboot everything , erase cache first ?
Fastboot erase cache
or
Keep the phone connected and reboot the recovery , the led should come on then.
Keep the phone connected in the bootloader and reboot the pc.
If the problem still exists the let me know
What's the exact error ? Waiting for device
When the phone is in the bootloader is it recognized as fastboot usb (in red text) and what does the device manager in windows say about a android phone ?
MIN313 said:
This is because the phone presents different device identifiers to the computer in these modes, and different drivers are needed, so it is possible to have proper drivers installed for one mode, but not the other. The fastboot program is simple and will just show the < waiting for device > message forever if drivers are missing. However, the same message may appear if the drivers are installed correctly, but the phone is not in the proper state with fastboot device IDs.
Make sure you aren't using a USB 3.0 port. Trying changing ports. The USB cable might also be the problem.
try using a direct usb 2.0 port on the pc ....
Otherwise reboot everything , erase cache first ?
Fastboot erase cache
or
Keep the phone connected and reboot the recovery , the led should come on then.
Keep the phone connected in the bootloader and reboot the pc.
If the problem still exists the let me know
What's the exact error ? Waiting for device
When the phone is in the bootloader is it recognized as fastboot usb (in red text) and what does the device manager in windows say about a android phone ?
Click to expand...
Click to collapse
In fastboot mode nothing shows in device manager, with 3 different cables, with 4 different computers (3x W10, 1xW7).
I tried connecting with a live cd of CentOS.
Same results, adb connect when phone is started, but when I go in fastboot mode nothings shows in lsusb or dmesg...
Looks like the phone doesn't connect to pc in fastboot, very very strange...

Recovering from bad bootloader flash

I have an XZ1C that I seemed to have damaged the bootloader during a flashing operation.
I have a working OS and can reboot the device with adb without problems via an "adb reboot bootloader" call.
When the device comes back, I'm unable to install the device drivers since the USB IDs are different than are supported from the regular XZ1C driver. My device is reporting as VID 0FCE PID 0DDE. This still seems like an Xperia IDE, but the ID is not supported from the regular Xperia driver.
Does anyone have any ideas how I can reflash the proper bootloader, or have pointers to a specific driver that might work given the odd mode that I've managed to mangle my XZ1C into?
Much thanks!
I didn't understand, what you mean with I can reboot the device via adb....
From my personal view : if the bootloader is broken, no connection via adb could be possible, no fastboot is possible and so on....
Maybe I'm wrong?
If the device is available, is the USB debugging in the Dev menu and OEM unlock enabled? Could you accept the fingerprint?
The VID/PID combo of 0FCE:0DDE is the fastboot device identifier.
If you're trying to get to flash mode, the procedure is to:
- Disconnect the phone from USB.
- Power off the phone.
- Hold the Vol-Down button.
- While holding Vol-Down, connect the phone to your computer via USB.
This will activate flash mode with a VID/PID of 0FCE:B00B.
You can tell the difference between the two by the color of the notification LED.
Fastboot mode has a blue notification LED, while the flash mode color is green.
Not sure I understand fully what you mean but if you're running windows, change the driver manually to Android ADB device once it's plugged in. Windows should recognize fastboot mode at that point you can flash a new boot image.

Is there anyway at all to enter recovery mode without volume + button?

Greetings.
I have working Redmi Note 9. The problem is I forget the passcode. And the only way to remove it, it seems, by entering recovery mode. But mine is broken, it's board level so simply changing the button wont do anything. The volume - is working fine tho.
Or is there any way to remove the code without going to recovery?
Thanks )))
You'll need following things on your pc:
Android SDK platform tool
Drivers specific to your phone
USB debugging enabled on your device
Then on your phone:
OEM unlocked or Bootloader unlocked.
After you have all prerequisites,
Connect your device to PC using the USB cable and in PowerShell enter the following commands,
adb devices
It shows all devices connected to your PC.
Confirm that your device is connected by ensuring the correct build number.
For booting into recovery mode, use the following command,
adb reboot recovery

Categories

Resources