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 !
Related
Hello XDA Guys,
I have my Memo Pad ME172V broken while I was trieng to Root it and I have used the command "adb reboot bootloader"
so it went down and did not came back again
when I start it it goes directly to this screen " No USB cable connected"
{
"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"
}
and when I connect it to My PC I find in device manager uninstalled device "WM8950 USB Device"
I tried to install a driver for it it only accept Android ADB driver and APX driver but not running as one so I can not use ADB command with it or APX mode
After I install the driver the logo on the screen changes to a green android man with a yellow helmet and written "Ready for download"
I tried everything I know till now
Using power and volumes button in many different combinations
also tried to use Easyflash
changing the USB windows Driver
but no luck at all
PLEASE HELP ME
Thanks
Same issue here man - a friend has given me theirs to try and fix. Did you sort it out?
I've tried multiple Fastboot drivers, but fastboot devices doesn't see anything.
Any Help From XDA Profissionals
Hey Guys, any one here Can help Me
I am not an expert, but does the device still recognise external SD?
If so, maybe this will work:
1. Download a stock util from here https://www.mediafire.com/folder/23ycdy8i4f8mu/ASUS-me172v
(I previously used http://www.mediafire.com/download/3rn6cnzh95va6np/SD_RESTORE_UTIL_20130724_STOCK.ZIP)
2. Format external SD in FAT32 (so at least 4GB microSD card)
3. Extract contents of the stock util zip to the root of the SD
4. Put SD in the device and hope it'll boot from there, so you can restore a previous flash.
Maybe the device has to be rooted for this to work, in that case look here: http://forum.xda-developers.com/showthread.php?t=2216390&page=27 and search Google for Me172vRootUtil_v0.1.zip
I hope this works, and if not, maybe someone else can help you!
hi guys..
same condition.anyone has solve it..? device was working but i only went to fastboot mode then "ready for download"..
So I've been researching this all day.. A friend gave me his phone and asked me to fix it. I charged it, and tried to boot it up, but all I'm seeing is the bootloader. I've tried to enter Fastboot, Recovery mode and Factory Reset, but all it does when I try to select an option with the power-button is go to the "next item". Pressing the volume up button also takes it to the "next item". Pressing the volume down button does nothing, which is weird, because that's the button that's supposed to go to the "next item".
Now, I've tried installing HTC sync manager on my computer in the hopes of maybe being able to do something, but whenever I try to install it, it gives me this error (sorry for the Swedish, it's just saying that an error occured during the installation of something, device component? That last word might be translated wrong):
{
"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"
}
This is what the bootloader looks like:
I've tried a few ADB commands, to no avail. Running
Code:
adb devices
returns an empty list. The same thing applies to
Code:
fastboot devices
Trying to run any other fastboot command just says "< waiting for device >"
I'm not able to boot up the Android OS, or anything else for that matter. Trying to turn the phone off boots it up into the bootloader again, forcing me to leave it plugged in so that it doesn't run out of battery.
The drivers appear to be installed just fine on my computer, even though I can't seem to install HTC Sync Manager:
I'm running out of ideas, and I'm not sure what to Google for anymore. I'm not sure what's been previously done to this phone. Is it possible to just, completely reset it through a computer, using a USB cable, even though I'm having difficulties doing the things mentioned above? If yes, how? What to Google for?
Thanks,
/Nanashi
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
Hello everyone!
This is my first post here so I hope everything I try to explain is according to the rules as far as I read it.
I need to root my Doogee S88 pro mobile since I need test and develop some AR stuff. The standard apps are not accesible by the playstore so I need to bypass that. For doing that I need to root my phone (this is what I read at least).
So... I installed the doggee usb drivers from their website for my phone, usb debugging is activated and OEM is activated as well. I downloaded the most recen platform tools and the usb-cable should be fine since I find the phone with
Code:
adb devices
I execute the following commands:
Code:
adb devices
adb reboot bootloader
fastboot devices
I get the small Fastboot text in the lower left corner. Then if I try to execute
Code:
fastboot flashing unlock
or
fastboot flashing unlock-critical
I only get back <waiting for device>
As said I installed the usb drivers provided by doogee. But: In the device manager I can see the following:
{
"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"
}
Also I periodically (every 10 seconds) hear the sound as if a usb-device is disconnected. Afterwards the device manager refreshes the list.
So... it is a driver issue? I tried updating the drivers but picking manually the folder where driver files are located leads to no result. Automatic search as well. If it is a driver issue - where can I get the appropriate driver files? Thank you for any hint.
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
Unfortunately that didnt help either. Dunno... What I did was: I switched to my Lnux OS and over there it worked out of the box (only needed to install adb and fastboot from repositories).
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