My rednote is not being recognised by my Win10 PC when in fastboot mode. ADB is fine but the moment it boots into fastboot, it disappears. I've tried numerous different drivers now, and restarted the PC to disable driver signature but nothing seems to work. Fastboot mode is recognised when the phone is connected to my linux laptop.
Is there a trick to it? Or a guaranteed set of drivers that work both adb and fastboot?
I want to unlock my phone but cannot run the official MiUnlock tool.
LesGirauds said:
My rednote is not being recognised by my Win10 PC when in fastboot mode. ADB is fine but the moment it boots into fastboot, it disappears. I've tried numerous different drivers now, and restarted the PC to disable driver signature but nothing seems to work. Fastboot mode is recognised when the phone is connected to my linux laptop.
Is there a trick to it? Or a guaranteed set of drivers that work both adb and fastboot?
I want to unlock my phone but cannot run the official MiUnlock tool.
Click to expand...
Click to collapse
there is hundreds of tutos in youtube, go and check them
tutibreaker said:
there is hundreds of tutos in youtube, go and check them
Click to expand...
Click to collapse
And I've viewed a number of them. Could you link to one that actually works?
Seriously, I'm not stupid. I've tried a number of supposed solutions. I'm not a Windows geek, it's true, but I'm happily techie on UNIX platforms. Maybe this is something other than the actual driver. I'm more than happy to learn.,
LesGirauds said:
And I've viewed a number of them. Could you link to one that actually works?
Seriously, I'm not stupid. I've tried a number of supposed solutions. I'm not a Windows geek, it's true, but I'm happily techie on UNIX platforms. Maybe this is something other than the actual driver. I'm more than happy to learn.,
Click to expand...
Click to collapse
For those who have problems installing , you need to create a new folder called "Desktop" in C:/Users/*Your user*
LesGirauds said:
My rednote is not being recognised by my Win10 PC when in fastboot mode. ADB is fine but the moment it boots into fastboot, it disappears. I've tried numerous different drivers now, and restarted the PC to disable driver signature but nothing seems to work. Fastboot mode is recognised when the phone is connected to my linux laptop.
Is there a trick to it? Or a guaranteed set of drivers that work both adb and fastboot?
I want to unlock my phone but cannot run the official MiUnlock tool.
Click to expand...
Click to collapse
This is exactly my problem on Redmi note 11S. I already tried a lot of drivers and tutorials and still no succes. In linux fastboot works.
PS: Les Girauds, you can unlock bootloader by mtkclient (linux), not just via official tool (Mi unlock). I already did it.
Magic Cucumber said:
you can unlock bootloader by mtkclient
Click to expand...
Click to collapse
Thanks, might give that a go.
I tried another UNIX based unlock solution yesterday (a python prog from GitHub) and whilst it didn't work cleanly (nor successfully unlock the device) I did see in the garbled error message returned about having to wait 121 hours. So maybe the phone will be successfully unlocked on Tuesday!
tutibreaker said:
For those who have problems installing , you need to create a new folder called "Desktop" in C:/Users/*Your user*
Click to expand...
Click to collapse
Thanks, that's worked. The Yt video didn't show for me so I copied it's URL and opened in a separate browser window. The video went through the process for Win 11 but I guess it's the same for Win10 (my system), and it worked so that's OK. Weird thing is, it was only an install of the generic adb drivers which I'd installed previously anyway, and had been using for some time, doing updates on my Lenovo tablet etc. So they were there and working once upon a time. I can only assume that the process of installing the MiUnlock screwed them up somehow.
@Magic Cucumber - it might be worth you simply reinstalling the standard adb platform tools, It might give you back fastboot access
Magic Cucumber said:
you can unlock bootloader by mtkclient (linux),
Click to expand...
Click to collapse
Thank you. It worked. The MIUnlock said I had to wait but mtkclient did it immediately.
Now I'm going to flash a custom ROM, and maybe twrp, just have a device I'm happier with. Xiaomi phones maybe good value but I don't like the stock software.
Related
Short story: can't get identifier token, stuck on "waiting for device".
Hi everyone I have scanned around and feel confident I have a unique or difficult situation trying to root my HTC One. I have the phone drivers installed, the latest 4.1.0.001 msi to be precise, and the phone responds more or less to the computer when it's in Android. So the issue is with fastboot state, for which I tried the normal HTC drivers, then other drivers I was able to find for Fastboot around XDA, and finally the Universal Naked Driver which supports HTC One for ADB. I am able to use the command adb reboot-fastboot and then I return a blank list from the command adb devices or fastboot devices. I have PDA net on the phone, and have it set to "connect automatically". There is a sign that something is awry when I plug the phone up to the PC and PDAnet immediately returns "can't connect, HTC Sync Error = -1". I went into windows and allowed unsigned drivers for ADB, and uninstalled other drivers, deleted files, and rebooted each time I switched drivers in attempt to get a response from the phone in Fastboot.
usb debugging is enabled. In fastboot, the Universal Naked driver returns the following error:
Port_#0004.Hub_#0003
This device cannot start. (Code 10)
A request for the USB BOS descriptor failed.
Btw Universal Naked Driver seems to be the MOST functional returning a lot of info about the device, and the second driver I dl'ed was apparently for HTC One X and didn't work at all.
Shortcuts I have taken: yeah I didn't install the entire android SDK I just got the package off XDA and also tried Hasoon's solution. I didn't install the entire large HTC Sync app either, but I don't think either of these are required.
Basically on my ATT htc one, I will never get this thing unlocked if it is REFUSING to recognize the device while it's in Fastboot, halting the process by making a bootloader unlock impossible.
Plz help and I won't return it for an S4!! I don't wanna. A beer to he who saves me the trip back to ATT store.
zWiLLX said:
Short story: can't get identifier token, stuck on "waiting for device".
Hi everyone I have scanned around and feel confident I have a unique or difficult situation trying to root my HTC One. I have the phone drivers installed, the latest 4.1.0.001 msi to be precise, and the phone responds more or less to the computer when it's in Android. So the issue is with fastboot state, for which I tried the normal HTC drivers, then other drivers I was able to find for Fastboot around XDA, and finally the Universal Naked Driver which supports HTC One for ADB. I am able to use the command adb reboot-fastboot and then I return a blank list from the command adb devices or fastboot devices. I have PDA net on the phone, and have it set to "connect automatically". There is a sign that something is awry when I plug the phone up to the PC and PDAnet immediately returns "can't connect, HTC Sync Error = -1". I went into windows and allowed unsigned drivers for ADB, and uninstalled other drivers, deleted files, and rebooted each time I switched drivers in attempt to get a response from the phone in Fastboot.
usb debugging is enabled. In fastboot, the Universal Naked driver returns the following error:
Port_#0004.Hub_#0003
This device cannot start. (Code 10)
A request for the USB BOS descriptor failed.
Btw Universal Naked Driver seems to be the MOST functional returning a lot of info about the device, and the second driver I dl'ed was apparently for HTC One X and didn't work at all.
Shortcuts I have taken: yeah I didn't install the entire android SDK I just got the package off XDA and also tried Hasoon's solution. I didn't install the entire large HTC Sync app either, but I don't think either of these are required.
Basically on my ATT htc one, I will never get this thing unlocked if it is REFUSING to recognize the device while it's in Fastboot, halting the process by making a bootloader unlock impossible.
Plz help and I won't return it for an S4!! I don't wanna. A beer to he who saves me the trip back to ATT store.
Click to expand...
Click to collapse
i would say you havent installed the drivers. best thing to download to get your HTC one to recognize in any mode is the HTC sync manager. i know its kinda annoying but the phone will get recongized in every mode and the initial plug in just requires a few minutes to detect, download, and install the drivers.
syaoran68 said:
i would say you havent installed the drivers.
Click to expand...
Click to collapse
I did try the "stripped" HTC One drivers found here on XDA.. I mean http://forum.xda-developers.com/showthread.php?t=2217396 seems pretty straightforward!
But yes at this point in the game why not give the full bloatware a try, thx
are you using the all in one toolkit? i have also found that installing the htc sync software helped alot of people with driver problems
Is your phone actually in fastboot mode?
Gave it a shot; my win 8 laptop still has no ability to recognize the phone in device manager with HTC BMP, Sync Manager, or HTC Driver Installer.. which are the the 3 related programs I've installed.
The HTC driver recognizes the device (while in Fastboot) as My HTC, while the Universal Naked Driver calls it something different I believe, but neither are working to allow adb or fastboot to list the device, and both drivers have the same error as to why the device can't start: "a request for the USB BOS descriptor failed"
BenPope said:
Is your phone actually in fastboot mode?
Click to expand...
Click to collapse
Hey Ben Pope thanks for asking, yes it's in the white screen saying ***LOCKED*** in pink at the top. And yes I get into fastboot by adb reboot-bootloader most of the time because it's easier than the button pressing (which I've done also).
One weird thing I did notice is that "FASTBOOT" is shown with a red background when the device goes into the mode, however if I use the volume up/dn buttons and navigate, the text changes to "FASTBOOT USB", and persists that way until it's re-booted. Don't know if that matters, but at least if it's totally abnormal, there could be something funky going on in the firmware.
Thanks.
skinsfanbdh said:
are you using the all in one toolkit? i have also found that installing the htc sync software helped alot of people with driver problems
Click to expand...
Click to collapse
I tried Hasoon's toolkit but because it calls fastboot oem getidentifiertoken or whatever it is, the result is "waiting for device" which stops the process in its tracks even while the phone is in the white screen, where it got from responding to the prior command the toolkit sent which I believe is adb reboot-bootloader.
Currently I installed the 48mb "stripped" sync software from the link a few posts prior; do you think I should go with the non-stripped version?
zWiLLX said:
Gave it a shot; my win 8 laptop still has no ability to recognize the phone in device manager with HTC BMP, Sync Manager, or HTC Driver Installer.. which are the the 3 related programs I've installed.
The HTC driver recognizes the device (while in Fastboot) as My HTC, while the Universal Naked Driver calls it something different I believe, but neither are working to allow adb or fastboot to list the device, and both drivers have the same error as to why the device can't start: "a request for the USB BOS descriptor failed"
Click to expand...
Click to collapse
there is a thread around for people who are having issues with windows 8. the soulution for you problem is probably in that thread
---------- Post added at 11:01 AM ---------- Previous post was at 10:59 AM ----------
zWiLLX said:
Hey Ben Pope thanks for asking, yes it's in the white screen saying ***LOCKED*** in pink at the top. And yes I get into fastboot by adb reboot-bootloader most of the time because it's easier than the button pressing (which I've done also).
One weird thing I did notice is that "FASTBOOT" is shown with a red background when the device goes into the mode, however if I use the volume up/dn buttons and navigate, the text changes to "FASTBOOT USB", and persists that way until it's re-booted. Don't know if that matters, but at least if it's totally abnormal, there could be something funky going on in the firmware.
Thanks.
Click to expand...
Click to collapse
to use fastboot commands it needs to say fastboot usb
---------- Post added at 11:03 AM ---------- Previous post was at 11:01 AM ----------
zWiLLX said:
I tried Hasoon's toolkit but because it calls fastboot oem getidentifiertoken or whatever it is, the result is "waiting for device" which stops the process in its tracks even while the phone is in the white screen, where it got from responding to the prior command the toolkit sent which I believe is adb reboot-bootloader.
Currently I installed the 48mb "stripped" sync software from the link a few posts prior; do you think I should go with the non-stripped version?
Click to expand...
Click to collapse
when it says waiting for device you have to close that cmd screen and if your phone says fastboot usb it will start but you have to manually close the first window
hey SkinsFan, I tried the thread here and downloaded the ADB drivers to replace my Android 1.0 device. Other than those new drivers, I had done a lot of those steps. However, the PC says "The third party INF does not contain digital signature information", and rejects the ADB drivers linked from there, despite already allowing unsigned drivers in Windows settings.
Actually now I can't re-install the "naked driver" and matters are worse because the PC is now saying a hash file is missing for them, despite being installed an hour ago. So I guess I'll restart and try again, possibly unistalling HTC Sync since it was the new addition.
as far as closing the cmd window, this isn't doing anything to make the device recognized by the PC and it isn't therefore showing in adb devices or fastboot devices.
Still working on it thanks!
zWiLLX said:
hey SkinsFan, I tried the thread here and downloaded the ADB drivers to replace my Android 1.0 device. Other than those new drivers, I had done a lot of those steps. However, the PC says "The third party INF does not contain digital signature information", and rejects the ADB drivers linked from there, despite already allowing unsigned drivers in Windows settings.
Actually now I can't re-install the "naked driver" and matters are worse because the PC is now saying a hash file is missing for them, despite being installed an hour ago. So I guess I'll restart and try again, possibly unistalling HTC Sync since it was the new addition.
as far as closing the cmd window, this isn't doing anything to make the device recognized by the PC and it isn't therefore showing in adb devices or fastboot devices.
Still working on it thanks!
Click to expand...
Click to collapse
when your phone is in bootloader does it say fastboot usb at the top?
i think the links for drivers are for samsung devices he said its copied from his other thread. you need to get drivers from somewhere else
As I said, after "adb reboot-bootloader", left untouched, it says "FASTBOOT", but when I use a volume key to navigate just one click, it changes its tune to "FASTBOOT USB". I don't know whats going on with that ...
The samsung drivers are there but I believe Android ADB interface drivers can be universal , not sure, but now can't get back my Naked driver! working on that now
zWiLLX said:
As I said, after "adb reboot-bootloader", left untouched, it says "FASTBOOT", but when I use a volume key to navigate just one click, it changes its tune to "FASTBOOT USB". I don't know whats going on with that ...
The samsung drivers are there but I believe Android ADB interface drivers can be universal , not sure, but now can't get back my Naked driver! working on that now
Click to expand...
Click to collapse
Hey, I know your issue I can help on TeamViewer? Don't worry, I won't harm your PC
try pressing the power button while in bootloader. does it switch between hboot and fastboot usb?
MacHackz said:
Hey, I know your issue I can help on TeamViewer? Don't worry, I won't harm your PC
Click to expand...
Click to collapse
I am open to that! Could you give a preview on what you're thinking? Have teamviewer running. I will warn you I've lost ability to install the Universal Naked Driver via a "missing hash file" despite having it installed hours ago.
@skinsfanbdh yes. But again, it starts off intially (before a volume keypress) as "fastboot" not "fastboot USB", then changes.
zWiLLX said:
I am open to that! Could you give a preview on what you're thinking? Have teamviewer running. I will warn you I've lost ability to install the Universal Naked Driver via a "missing hash file" despite having it installed hours ago.
@skinsfanbdh yes. But again, it starts off intially (before a volume keypress) as "fastboot" not "fastboot USB", then changes.
Click to expand...
Click to collapse
yea it has to be plugged it to the computer first
zWiLLX said:
I am open to that! Could you give a preview on what you're thinking? Have teamviewer running. I will warn you I've lost ability to install the Universal Naked Driver via a "missing hash file" despite having it installed hours ago.
@skinsfanbdh yes. But again, it starts off intially (before a volume keypress) as "fastboot" not "fastboot USB", then changes.
Click to expand...
Click to collapse
Hey, I replied to your email PM me your TeamViewer info
MacHackz said:
Hey, I replied to your email PM me your TeamViewer info
Click to expand...
Click to collapse
Hey guys, Im experiencing similar problems. How exactly did you guys solve it?
Thanks
MacHackz said:
Hey, I replied to your email PM me your TeamViewer info
Click to expand...
Click to collapse
Hey, I´m experiencing the same problem here. Could you help me too?
Kenchinito said:
Hey, I´m experiencing the same problem here. Could you help me too?
Click to expand...
Click to collapse
Sorry for the very slow reply. Unfortunately, we won't know why HTC didn't play nicely with my Lenovo/Win8 laptop. However, I was quick to try a different older netbook I had lying around. At first, nothing happened, and I got used to the Sense UI enough to tolerate it.
But, I couldn't wifi tether and a few other unacceptable details, so I tried again last week with the same netbook that didn't seem to work the first time, and voila! Flawless. Maybe a reboot of that kicked it into gear, but both ADB and Fastboot were recognizing the HTC as a specific device, as opposed to the lenovo which found a ghost device with no name.
I am guessing too many android devices were installed and in the registry as USB devices, disorienting the PC, even though they were uninstalled, perhaps their drivers lingered as shared drivers. In theory I had S3 S4, HTC, possibly S2 and Motorola drivers all present.
The key is, keep the drivers on a folder on your phone with adb fastboot etc, and try a couple diff laptops. You'll know it worked when the device is recognized via "devices" with its unique number in both adb and fastboot.
Now running Revolution HD Google Play after trying CM 10.2 and Revolution HD Sense. CM did not work very smoothly with a lot of force crashes (navigation and music) and I can strongly recommend RevolutionHD google play edition.
Beware though, the first wipe takes out all the contacts and pictures etc, unfortunately, because I thought they would be spared.
Hey there,
After upgrading windows 8 to 8.1, I cannot get my phone into fastboot. It seems that previously installed drivers on W8 are now gone.
Any idea how to fix this?
jimilegolas said:
Hey there,
After upgrading windows 8 to 8.1, I cannot get my phone into fastboot. It seems that previously installed drivers on W8 are now gone.
Any idea how to fix this?
Click to expand...
Click to collapse
Install the drivers again.
I've had the same problem in windows 8.1... Fastboot device cannot be recognized by the system, but i don't know why; the problem was "Error enumerating device id". If you see hardware id, it doesn't exists and the driver won't be found. I returned to windows 7.
gregbradley said:
Install the drivers again.
Click to expand...
Click to collapse
Mind if you shared a way of doing that?
Installing the official sony flashtool with its drivers didn't help + every other way I tried (that worked when I had 8) also resulted in failure.
PS:When I connect it in fastboot, windows says that "drivers malfunctioned, unknown USB device"
jimilegolas said:
Mind if you shared a way of doing that?
Installing the official sony flashtool with its drivers didn't help + every other way I tried (that worked when I had 8) also resulted in failure.
PS:When I connect it in fastboot, windows says that "drivers malfunctioned, unknown USB device"
Click to expand...
Click to collapse
Have you tried the drivers from flashtool (Not the sony one, the one by androxyde here on xda)
gregbradley said:
Have you tried the drivers from flashtool (Not the sony one, the one by androxyde here on xda)
Click to expand...
Click to collapse
Yes, but I cannot install them.
Sent from my Xperia T using xda app-developers app
jimilegolas said:
Yes, but I cannot install them.
Sent from my Xperia T using xda app-developers app
Click to expand...
Click to collapse
You have to do it safe mode or something similar
read this from flashtool.net
http://www.flashtool.net/disabledrivers.php
gregbradley said:
You have to do it safe mode or something similar
read this from flashtool.net
http://www.flashtool.net/disabledrivers.php
Click to expand...
Click to collapse
I've done that, but I still get the same windows usb error :/
jimilegolas said:
I've done that, but I still get the same windows usb error :/
Click to expand...
Click to collapse
OK, not sure what the issue is then, can you get access to a win7 machine? There are no issues with drivers on win7
gregbradley said:
OK, not sure what the issue is then, can you get access to a win7 machine? There are no issues with drivers on win7
Click to expand...
Click to collapse
Guess this is the only option now.
Anyway, thanks.
jimilegolas said:
Guess this is the only option now.
Anyway, thanks.
Click to expand...
Click to collapse
Same problem here. See my post: http://forum.xda-developers.com/showpost.php?p=46645468&postcount=129
No solution found... Yet
fastboot for windows 8.1 over linux and this is my option to work fastboot on win 8.1
pietrucci said:
Hi,
Seems my usb drivers don't work anymore in Windows 8.1. Tried every version of usb-drivers, removed existing drivers, disabled digital signing again but no succes.
Anyone with a solution already?
Click to expand...
Click to collapse
load wubi (windows ubuntu installer) over the link http://wiki.ubuntuusers.de/Wubi
than install ubuntu, on harddrive C:// and reboot your Pc
Now you have a linux in your current system, you can remove ubuntu (linux) in Programms & feautures list in windows.
now reboot reboot the system and isntall in ubuntu fastboot.
you musst give in the terminal sudo apt-get fastboot
and now you can flash your bootloader in linux.
but you musst sudo bevor you type fastboot flash type sudo fastboot flash boot boot.img
you say it is easy
gooogle wubi (windows ubuntu installer)
im here.. me too facing the same weird problem.
in 8.1 os it worked at first but then it didnt recognizing my device. reinstalled the 8.1 os and tested and same result. worked at first then fu**ed up again.
hope someone will get ride of this prob in 8.1ois :/
Same..
Exactly the same problem here. On windows 8, no issue. After updating to 8.1, "Error enumerating device id". I've tried everything, but nothing.
I had my xperia without kernel, and I REALLY needed Fastboot, so I had to go to a W7 pc, and no issue then.
Ohh, and I can't disable driver verification on W8.1 . When i'm in advanced boot menu, I just can't press any key. The keyboard doesn't work, and I have to Hard Reboot. Any idea?
EDITED
This worked for me : http://www.droid-now.com/2013/10/fix-working-fastboot-drivers-windows-8-1-x64/
So now I can use fastboot/ flashmode, but only if I connect the phone to an usb 3.0 port. On 2.0 the issue is still there.
fedemyth said:
Exactly the same problem here. On windows 8, no issue. After updating to 8.1, "Error enumerating device id". I've tried everything, but nothing.
I had my xperia without kernel, and I REALLY needed Fastboot, so I had to go to a W7 pc, and no issue then.
Ohh, and I can't disable driver verification on W8.1 . When i'm in advanced boot menu, I just can't press any key. The keyboard doesn't work, and I have to Hard Reboot. Any idea?
EDITED
This worked for me : http://www.droid-now.com/2013/10/fix...ndows-8-1-x64/
So now I can use fastboot/ flashmode, but only if I connect the phone to an usb 3.0 port. On 2.0 the issue is still there.
Click to expand...
Click to collapse
Nice share brotha.
I want to make it work for x32 bit
Sent from my LT25i using XDA Premium 4 mobile app
As I see the only way to get access to fastboot and flash mode is to use windows 8 or lower.
Here is the cause of our problem and there is no solution so far: http://blogs.msdn.com/b/usbcoreblog...8-0-but-fail-on-windows-8-1-with-code-43.aspx
EDIT: I used the old XP machine of my parents to unlock the bootloader and everything worked fine
well w8.1 certainly cannot use fastboot if you plug it into USB 2.0 port..as microsoft has change it usb policies in w8.1, the only way to use fastboot in w8.1 is to plug into a USB 3.0 hub, and install your driver the same way before..
Hello!
I am trying to root my phone, which requires and unlocked bootloader.
Here are the steps i have completed:
1. Got the unlock code.
2. Installed adb and fastboot drivers.
3. Installed HiSuite
4. Connected the phone to my desktop (windows 10).
Here i have to mention that the pc recognises my phone, and it is listed under devices. USB debugging and OEM unlock are enabled.
5. I opened cmd in the folder where abd is installed. Checked that abd devices finds my phone (which it does).
Here is where the problem comes in. After booting phone into fastboot (using adb reboot bootloader), i tried to find my phone using the command fastboot devices.
This doesn't find the phone. If i try to unlock anyways, it gets stuck on waiting for devices. I tried the same steps on a laptop (also running windows 10) and the problem stays the same.
Help is appreciated.
EDIT: solved the problem by using a windows 8 installed laptop.
Uninstall HiSuite, it may interfere with the phone's connection. It is not used when unlocking/root.
monoxian said:
Uninstall HiSuite, it may interfere with the phone's connection. It is not used when unlocking/root.
Click to expand...
Click to collapse
Thank you for your reply, but this didn't work.
To add a detail, the reason i installed HiSuite was, because in fastboot mode it says:
"Please install HiSuite and connect your phone to your computer with an USB cable.
Nastmi said:
Thank you for your reply, but this didn't work.
To add a detail, the reason i installed HiSuite was, because in fastboot mode it says:
"Please install HiSuite and connect your phone to your computer with an USB cable.
Click to expand...
Click to collapse
You can try using this tool to unlock bootloader:
http://forum.xda-developers.com/p9/development/tool-srk-tool-huawei-bootloader-root-t3374068
I personally used this and worked flawlessly, make sure to get the latest version of it if you do.
If you are in fastboot&rescure mode, try the command "fastboot devices" and see if the device is detected, if not try unplugging and replugging phone
monoxian said:
You can try using this tool to unlock bootloader:
http://forum.xda-developers.com/p9/development/tool-srk-tool-huawei-bootloader-root-t3374068
I personally used this and worked flawlessly, make sure to get the latest version of it if you do.
If you are in fastboot&rescure mode, try the command "fastboot devices" and see if the device is detected, if not try unplugging and replugging phone
Click to expand...
Click to collapse
Will try the tool when i get home from school, but fastboot devices doesn't detect my device.
EDIT: The tool didn't work. It is stuck on waiting for device.
Fixed the problem by unlocking on another laptop (has windows 8).
Nastmi said:
Fixed the problem by unlocking on another laptop (has windows 8).
Click to expand...
Click to collapse
Glad to hear that you got it working, I had windows 10 and that worked on mine =\
Sent from my iPhone using Tapatalk
I already enabled OEM Unlock and USB Debugging in Developer options.
then I connected my LG G4 H811 to PC and confirmed MTP.
adb devices just shows:
List of devices attached
If I select USB charge instead of MTP, the adb devices shows:
List of devices attached:
LGH811***** device
Then I can do "adb reboot bootloader"
Phone shuts down and get on fastboot with this "waiting for device" I got stuck there.
Does anyone know the reason? Really need to unlock bootloader and then root my phone.
Thanks
Sent from my SM-A800F using XDA-Developers mobile app
Yeah I'm experiencing this too as well! I just recently updated to 20p and I am trying to root again. I was able to use fastboot to install twrp before. Don't know why this is happening.
This is what I did
In fatsboot I saw in device manager my phone was "rats I don't remember-something bootloader device" I chose update driver and browse my filkes and chose the marshal one. after that everything worked fine. Sry I'm an anxious person. Hopes this helps and if not or I could help more ask me more and hopefully I'll be more mellow lol.
Bootloader unrecognized
I used the app shared above and used it to locate the driver and ended up having to roll back to a previous driver and it worked in my case.
wish0 said:
In fatsboot I saw in device manager my phone was "rats I don't remember-something bootloader device" I chose update driver and browse my filkes and chose the marshal one. after that everything worked fine. Sry I'm an anxious person. Hopes this helps and if not or I could help more ask me more and hopefully I'll be more mellow lol.
Click to expand...
Click to collapse
[email protected] said:
I used the app shared above and used it to locate the driver and ended up having to roll back to a previous driver and it worked in my case.
Click to expand...
Click to collapse
Can one of you share a link to the driver you used?
MaRz0o said:
Can one of you share a link to the driver you used?
Click to expand...
Click to collapse
I'm at work won't get off for another 13 hours but like the post maybe two above here it was Marshall something. Go to device manager look for the boot loader adb interface can't remember exactly what it's called and double click it and use the menu option to rollback not update the driver and you should be good. I tried everything else including the one touch and only the rollback worked.
For my computer, it shown up as something like "Kedacom USB Device" in the Device Manager, but I rolled back that driver from 11 to 9 and it worked beautifully!
chromiumfan said:
For my computer, it shown up as something like "Kedacom USB Device" in the Device Manager, but I rolled back that driver from 11 to 9 and it worked beautifully!
Click to expand...
Click to collapse
Do you have the driver? I have none to roll back to.
Okay...
Okay so yeah it says kedacom usb device, that gives me the waiting for device error...in device manager when im in fastboot mode find kedacom device and click on it to see android bootloader interface. Right click on the android bootloader interface and choose update driver, browse my computer for driver software, then let me pick from a list of device drivers on my computer. From there I choose marshal London bootloader interface. From there everything works... don't have to restart computer of phone, everything works together perfect. Either it came with my computer or its from this install of adb... the 15 sec adb installer http://forum.xda-developers.com/showthread.php?t=2588979. Try my steps see if it works!
wish0 said:
Okay so yeah it says kedacom usb device, that gives me the waiting for device error...in device manager when im in fastboot mode find kedacom device and click on it to see android bootloader interface. Right click on the android bootloader interface and choose update driver, browse my computer for driver software, then let me pick from a list of device drivers on my computer. From there I choose marshal London bootloader interface. From there everything works... don't have to restart computer of phone, everything works together perfect. Either it came with my computer or its from this install of adb... the 15 sec adb installer http://forum.xda-developers.com/showthread.php?t=2588979. Try my steps see if it works!
Click to expand...
Click to collapse
I am having the "waiting for device" issue. But I dont have the "Marshal London" drivers. I have adb 15 sec drivers installed. Any idea where I could get them?
okay another try..
Okay have you tried, while the waiting for device prompt is up, instead of telling your computer you want to select from the list of drivers, to choose automatic: search online for the driver?
[EDIT: It's all good now... A stupid mistake of mine]
Ok, everything was fine... I was on PE and everything was normal. Then I wanted to try something out and cleared everything in TWRP and rebooted to fastboot, because I needed a different version of TWRP...
But once in fastboot and connected to my PC adb couldn't detect my device (list of devices attached is empty), so I can't flash twrp -> I can't do anything! I'm simply stuck in fastboot...
After a bit of googling i found out that I somehow had the wrong drivers installed, so I went into device manager and it showed some kind of "kedacom usb drivers". I tried every tutorial that is on the internet, but nothing worked. In the end I somehow got it changed to the regular "Android device -> Android ADB Interface"(how it used to- and should be?) from those "kedacom usb drivers" and I thought I found the solution, but it still doesn't recognize my device in adb I also tried the MiFlash tool - same thing
Is it possible that my mistake was not enabling usb-debugging beforehand and can I somehow get out of fastboot?
I would be so grateful if anyone was able to help me
Moischen said:
Ok, everything was fine... I was on PE and everything was normal. Then I wanted to try something out and cleared everything in TWRP and rebooted to fastboot, because I needed a different version of TWRP...
But once in fastboot and connected to my PC adb couldn't detect my device (list of devices attached is empty), so I can't flash twrp -> I can't do anything! I'm simply stuck in fastboot...
After a bit of googling i found out that I somehow had the wrong drivers installed, so I went into device manager and it showed some kind of "kedacom usb drivers". I tried every tutorial that is on the internet, but nothing worked. In the end I somehow got it changed to the regular "Android device -> Android ADB Interface"(how it used to- and should be?) from those "kedacom usb drivers" and I thought I found the solution, but it still doesn't recognize my device in adb I also tried the MiFlash tool - same thing
Is it possible that my mistake was not enabling usb-debugging beforehand and can I somehow get out of fastboot?
I would be so grateful if anyone was able to help me
Click to expand...
Click to collapse
what the
why dint u just save the new twrp to internal, boot to twrp, flash the new twrp image as recovery m thats it reboot to twrp and it will be the new one you flashed.
you dint have to wipe anything or use pc
Mooatreides said:
what the
why dint u just save the new twrp to internal, boot to twrp, flash the new twrp image as recovery m thats it reboot to twrp and it will be the new one you flashed.
you dint have to wipe anything or use pc
Click to expand...
Click to collapse
Yeah, good question... But it's too late for that now
Try another pc
emprazol said:
Try another pc
Click to expand...
Click to collapse
same thing
Manually install adb driver
Moischen said:
same thing
Click to expand...
Click to collapse
One time, I had such an issue with drivers, what I did is use a free VM machine software on Windows to install a Linux distro (or you could dual boot it), and from Linux it worked to detect my device.
On the other hand, there are really probably easier ways to fix your issue, but who knows, it may help and does not take too long.