Hello,
I have tried installing the google drivers and the drivers from the Razer support site, but I keep getting the error message 'This device cannot start. (Code 10)'.
I would like to lock the bootloader.
I have tried running adb reboot bootloader into command prompt, then running fastboot oem lock but it just comes up with < waiting for device > and nothing I have done has resolved this.
Any help on this matter would be greatly appreciated .
try these ones: https://adb.clockworkmod.com/
those are the only drivers working with my newer PC, AMD x470 Chipset
If you still have problems you can try using an older Windows 7 like Laptop
sanicwowguy said:
Hello,
I have tried installing the google drivers and the drivers from the Razer support site, but I keep getting the error message 'This device cannot start. (Code 10)'.
I would like to lock the bootloader.
I have tried running adb reboot bootloader into command prompt, then running fastboot oem lock but it just comes up with < waiting for device > and nothing I have done has resolved this.
Any help on this matter would be greatly appreciated .
Click to expand...
Click to collapse
Just forget about it. This phone cannot be rooted
Related
i got the samsung drivers, adb, fastboot,
but when i boot to bootloader (vol up+down +power) adb doesnt find any device. is that normal? fastboot oem unlock doesnt work, i presume b/c adb isnt recognizing my phone.
Some help please. Thanks
David 617 said:
i got the samsung drivers, adb, fastboot,
but when i boot to bootloader (vol up+down +power) adb doesnt find any device. is that normal? fastboot oem unlock doesnt work, i presume b/c adb isnt recognizing my phone.
Some help please. Thanks
Click to expand...
Click to collapse
ADB will not find the phone in bootloader mode. If you type fastboot devices, it should show your phone. Check device manager and see if you have an unrecognized device showing. If you do, try manually installing the drivers by clicking the update driver button under the unrecognized device's properties window.
try reinstalling the drivers...or you may need to use the google drivers in the sdk/adb package instead. Also when you plug the device into pc, go into device manager and see if shows up as android device. If it comes up unkown, then manually push the driver update.
^Ninja'd lol
fastboot devices comes up blank.
in device manager my phone comes up as other devices - android 1.0
i guess my driver is bad. where can i get a good one?
(i just installed the one from samsung.. same thing.)
what have you used
Make sure to download the software from sdk that is for the newest update of android. I think it is 4.0.3 there is like 5 things in that folder. You will need all of them, and after they download type "adb devices" in the command window and it should show the serial #.
Sent from my Galaxy Nexus using XDA App
Randroidran said:
Make sure to download the software from sdk that is for the newest update of android. I think it is 4.0.3 there is like 5 things in that folder. You will need all of them, and after they download type "adb devices" in the command window and it should show the serial #.
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
did that. i dont have any issues untill i am in the bootloader. adb works fine before i reboot.
I'm assuming your driver is not loaded properly. Download this driver and unzip it. Install it by using the update driver wizard in device manager. I used this same driver on my work laptop (windows 7) and have had zero issues.
thx ill try now
.
.
.
works!
thx a million
I've previously managed to get my tokenID from htcdev without any problems on various handset but lately I've come across a few issues.
For example I'm trying to unlock the bootloader for this DesireHD but when trying to get the tokenID I get an error saying no devices attached.
My computer has installed the correct drivers and it shows up on device manager. I am able to 'adb devices' when the handset has booted up but when in fastboot / bootloader nothing comes up when running the same command.
Is it something to do with my Android SDK folder?
Is there a way to come around this because if I want to do similar process with other devices I need to understand what I need to do before.
Thanks
Schizophonic said:
I've previously managed to get my tokenID from htcdev without any problems on various handset but lately I've come across a few issues.
For example I'm trying to unlock the bootloader for this DesireHD but when trying to get the tokenID I get an error saying no devices attached.
My computer has installed the correct drivers and it shows up on device manager. I am able to 'adb devices' when the handset has booted up but when in fastboot / bootloader nothing comes up when running the same command.
Is it something to do with my Android SDK folder?
Is there a way to come around this because if I want to do similar process with other devices I need to understand what I need to do before.
Thanks
Click to expand...
Click to collapse
Adb does not work in bootloader, just with a fully booted device. You have to use fastboot command in fastboot usb
Trying to unlock my bootloader and I'm having the dreaded problem of adb, fastboot and google usb drivers not working.
Tried the idiotic Sony documented way of installing Android SDK and development tools, tried 15 Second ADB, Flashtool and Minimal ADB installers - after doing all three of these and then running Flashtool it informs me that drivers need to be installed for the device.
Running "fastboot devices" results in no message at all, running "fastboot device" results in a "waiting for device" message.
Any ideas please?
diji1 said:
Trying to unlock my bootloader and I'm having the dreaded problem of adb, fastboot and google usb drivers not working.
Tried the idiotic Sony documented way of installing Android SDK and development tools, tried 15 Second ADB, Flashtool and Minimal ADB installers - after doing all three of these and then running Flashtool it informs me that drivers need to be installed for the device.
Running "fastboot devices" results in no message at all, running "fastboot device" results in a "waiting for device" message.
Any ideas please?
Click to expand...
Click to collapse
Do a search on how to install unsigned drivers on windows 10, that should fix your problem
Cheers that fixed it although using BCEDIT didn't I had to use the restart method.
diji1 said:
Cheers that fixed it although using BCEDIT didn't I had to use the restart method.
Click to expand...
Click to collapse
Cool
Now don't forget to backup your TA partition before unlocking your bootloader...
Happy rooting
I need a little help. I tried to unlock and root my phone. I was on build NDE63X. I was able to unlock the device no problem, but then ran into some issue with the root. I'm not sure what happened. Now I am stuck in bootloop.
I am trying to sideload the OTA NDE63X through ADB. However, adb isn't recognizing my device. If I type "fastboot devices" then it pulls up my device. I have tried to uninstall my drivers and reinstall the drivers and every time the driver says "Android Bootloader Interface". I don't know if that is the problem or not. Any help would be appreciated.
Thanks!
charr83 said:
I need a little help. I tried to unlock and root my phone. I was on build NDE63X. I was able to unlock the device no problem, but then ran into some issue with the root. I'm not sure what happened. Now I am stuck in bootloop.
I am trying to sideload the OTA NDE63X through ADB. However, adb isn't recognizing my device. If I type "fastboot devices" then it pulls up my device. I have tried to uninstall my drivers and reinstall the drivers and every time the driver says "Android Bootloader Interface". I don't know if that is the problem or not. Any help would be appreciated.
Thanks!
Click to expand...
Click to collapse
unplug the phone
switch off the phone
press power + volume down
does it go in Fastboot mode ?
I have searched the net high and low for a answer to this question but nothing I have tried works.
I have used every adb and fastboot installer i could find, but nothing i do get fastboot working on my 5t. ADB is recognised and i can reboot to the bootloader from a command shell. But as soon as i type "fastboot devices" it shows nothing.
I have been into device manager and it shows issues with the fastboot driver, i have tried everything i can think of to fix this issue.
I would really love to root my 5t and and have never encountered this many issues on any of my previous devices.
Running a 64gb OP5T and Windows 10
Thank you for your help
I have now re-installed windows 10, re-installed all drivers and ADB and fastboot. ADB is still working but nothing from fastboot. It's recognised properly in device manager but nothing shows up when I type fastboot devices or fastboot OEM unlock. Any tips would be great.
http://www.codeshuffle.in/2016/12/kenzo-fastboot-adb-connection-fix.html
check this link specially driver signature enforcement disable part, it may help
When you say "nothing shows up", what exactly is the response?
How are you getting into the bootloader? Use this from recovery or system:
Code:
adb reboot bootloader
Then proceed.
ADB is working fine. But as soon as I reboot to fastboot mode the phone doesn't respond. I can't work it out have tried everything.
djmcnz said:
When you say "nothing shows up", what exactly is the response?
Click to expand...
Click to collapse
^^
It just says waiting for device or says nothing and brings up a new line. I'm guessing the fastboot driver is the problem. I have installed the Oneplus drives included with the phone. I've installed the universal ones, still nothing.
Is there an individual fastboot driver I could manually install through device manager?
Appreciate the help.
The issue is finally fixed! I went into device manager and changed the driver from a list of drivers on my pc to WINUSB and now its working
Same problem here pal, how did you change driver to winusb, seems I've got all the gear just no idea... By gear I mean files/drivers lol. Rooted so many devices I thought this would be easy, looking forward to getting it sorted. I love a custom rom