Ok. Right now I'm trying to root my nexus. I'm stuck at installing the usb driver. I tried following this tutorial /showthread.php?t=613217 but every time i choose the driver and it searches it tells me it "couldn't find a better match for my hardware" and the driver doesn't install. I've tried 2 different computers, a macbook pro dual booted with Win XP media center Sp 2 and a dell XP media center Sp 3. No luck with either of them. Anyone tell me what I'm doing wrong please? its getting really anoying
magma9495 said:
Ok. Right now I'm trying to root my nexus. I'm stuck at installing the usb driver. I tried following this tutorial /showthread.php?t=613217 but every time i choose the driver and it searches it tells me it "couldn't find a better match for my hardware" and the driver doesn't install. I've tried 2 different computers, a macbook pro dual booted with Win XP media center Sp 2 and a dell XP media center Sp 3. No luck with either of them. Anyone tell me what I'm doing wrong please? its getting really anoying
Click to expand...
Click to collapse
I'm having the same issue myself i think.
Look under N1 Q&A and find the topic "N1 Bricked"
Glad to know im not the only one
I have a iMac and I never even had to worry about drivers.
Just download/install/setup the Android SDK and the rest is automatic.
I have a tutorial called ADB 4 Dummies that will walk you through installing the android sdk 2.2(froyo) and setting up your environments. Step by step for every system.
First thing, unplug your Phone from computer, uninstall ALL drivers and try from scratch.
Also, if you're using windows, when you're done and you plug in your phone, don't choose to "automatically find drivers" instead manually point it to the drivers folder in the SDK.
Don't worry, it's not bricked. lol.
mrandroid said:
I have a iMac and I never even had to worry about drivers.
Just download/install/setup the Android SDK and the rest is automatic.
Click to expand...
Click to collapse
Followed your tutorial, got adb and everything to work, adb will recognize my Motorola Cliq, but for some reason my nexus doesn't show up. When i do adb devices no devices come up
magma9495 said:
Followed your tutorial, got adb and everything to work, adb will recognize my Motorola Cliq, but for some reason my nexus doesn't show up. When i do adb devices no devices come up
Click to expand...
Click to collapse
Hmmmm....
There are 2 modes to the bootloader HBOOT and Fastboot.
Make sure you're phone is in fastboot mode... it should say FASTBOOT USB highlighted in red on top. If it doesn't, use the volume down key, select Fastboot and hit the power button once to switch the phone to fastboot.
Remember, "adb devices" works while your phone is turned on regular. If your phone is in Fastboot mode use "fastboot devices"
Ok, are you using windows? If you are;
Turn off your phone and boot it back up in Bootloader mode. (trackball+pwr, or volume down+pwr)
Once it's on bootloader, plug it in to the computer.
See if the computer asks for any drivers, etc. If it does point it to the Drivers folder in the SDK. If it doesn't... go into your Device Manager. (Right click on MY COMPUTER, click on MANAGE and when computer management opens up, go to Device manager from the list on the left). Look to see if there are any icons with an Exclamation mark and yellow background. If there is, right click on it, select update driver and point it to the drivers folder in the sdk.
Basically there should be a menu on top that says "Android Phone" and when you expand that selection you'll see "Android Bootloader Interface".
nope, no luck with that either, I tried it both on windows XP and windows 7. same error each time. Could it be a problem with my device? because Snow Leopard doesn't recognize the nexus as a storage device or anything
Damn. I think i'm out of options. Last thing to try:
- Turn on phone regular.
- Plug in through USB to computer (try a different USB cable, even if that one worked with the CLIQ, try a different USB port also.)
- On Phone: GO to settings, Application Settings, Development, USB Debugging, (if it's checked on, check it off then on again) make sure it's ON.
Go into your Android SDK folder, go into the TOOLS folder. Now click on DDMS. See if it lists your device...
Last thing would be to go back through the Device Manager, and click on SCAN HARDWARE while your phone is plugged in... It has to be on that list somewhere, whether it's a bad driver, etc, it should still appear in your device manager somehow.
alright that didnt work, but, i got it, i just kept unplugging and plugging back in my phone until adb recognized it. then i got fastboot to run and now i have superuser . But now im stuck at another point. I'm trying to do the recovery.img file. I tried in mobile terminal "flash_image recovery /sdcard/recovery.img" but it told me something like "flash_image not found" I saw that i could do this via fast boot but i dont know how to do that. how would i do fastboot on Mac?
http://www.myhangoutonline.com/tutorials/nexus-one/6-upgrade-nexus-one-recovery
when i try to do the fastboot command i get "-bash: fastboot: command not found" i dont think i have fastboot set up right
have you tried typing in "./" before the command? I found that that was one of my mistakes I did when I first rooted my phone
tried that, entered "./fastboot-mac flash recovery recovery.img" and i just get "waiting for device"
I believe you can also try "./fastboot-mac flash recovery ./recovery.img"
Alright I flashed a clockwork recovery through the app manager in the market. Is there any way I can apply the other recovery with an update.zip?
Also, thanks so much for all the help guys!!!!!!!!!!
you can do it through terminal emulator, if you go to amonra's recovery thread he tells you how.
this is the link http://forum.xda-developers.com/showthread.php?t=611829
fastboot somtimes doesn't come in the SDK... download the version for your system from here: http://www.myhangoutonline.com/tutorials/nexus-one/5-unlock-nexus-one-bootloader
place it in your androidsdk/tools folder
Related
Ok, I get into Fastboot on my DELL S7 it just keeps on saying "Starting Fastboot USB download protocol" and other stuff in red text above, besides that I need to install the driver on my computer for Fastboot but Windows 7 says "Windows was unable to install your Fastboot" I guided windows to the driver folder in Fastboot+ADB which I got from the Clockwork Mod 5.0 RECOVERY Flash thread.
I really want to flash this clockwork mod http://forum.xda-developers.com/showthread.php?t=1334487
EDIT: Fastboot working, ok I have another problem I flashed the CWM 5.0 IMG file thru fastboot, but how to go into CW recovery? isn't it Power + Up Volume, but that takes me to the Dell update system.
EDIT 2 : I got everything working, used my brain instead of working blindly. Thanks anyways.
ikutoisahobo said:
Ok, I get into Fastboot on my DELL S7 it just keeps on saying "Starting Fastboot USB download protocol" and other stuff in red text above, besides that I need to install the driver on my computer for Fastboot but Windows 7 says "Windows was unable to install your Fastboot" I guided windows to the driver folder in Fastboot+ADB which I got from the Clockwork Mod 5.0 RECOVERY Flash thread.
I really want to flash this clockwork mod http://forum.xda-developers.com/showthread.php?t=1334487
EDIT: Fastboot working, ok I have another problem I flashed the CWM 5.0 IMG file thru fastboot, but how to go into CW recovery? isn't it Power + Up Volume, but that takes me to the Dell update system.
EDIT 2 : I got everything working, used my brain instead of working blindly. Thanks anyways.
Click to expand...
Click to collapse
Where did you find the driver during the fastboot screen? I'm having the same problem and any help would be definitely appreciated. What stock android did you have before installing CWR?
Ok, I had ADB drivers for a Motorola CLIQ and it worked, just select choose from list of installed drivers and selct Android Interface or ADB interface or whatever wityh ADB or android in it. Tyhen run cmd and ttpe fastboot.exe or fastboot
I see a few posts where folks cant get their computer to install the fastboot driver from the FASTBOOT+ADB.ZIP but then they say they got it working, but nobody has said how! I have XP sp3 and cant get the computer to install a fastboot driver. The ANDROID PHONE device is empty as well as the ANDROID USB DEVICE. I get adb interface when I plug in my Epic but I even tried uninstalling it and seeing if the steak would install but no go. Any suggestions?
PfcKirk said:
I see a few posts where folks cant get their computer to install the fastboot driver from the FASTBOOT+ADB.ZIP but then they say they got it working, but nobody has said how! I have XP sp3 and cant get the computer to install a fastboot driver. The ANDROID PHONE device is empty as well as the ANDROID USB DEVICE. I get adb interface when I plug in my Epic but I even tried uninstalling it and seeing if the steak would install but no go. Any suggestions?
Click to expand...
Click to collapse
Yeah, that's right.
This is how it is download ADB which is basically downloading the SDK.
And if you have an Android phone or something just install the drivers for it, usually downloads adb drivers for it too, or if that doesn't work try downloading MOTOROLA CLIQ USB or ADB drivers....as I had them installed when I plugged in the phone.
Put device in fastboot mode
Connect device
Open up Device Manager
Click on "Fastboot" or whatever it says
Click on "Update driver"
Click on "Browse my computer for driver"
Click on "Let me pick from a list of device drivers on my computer"
Click on "Have Disk"
Find your fastboot drivers
SO recently got a nexus one and for some reason i cant get it to be recognized by adb, i have tried everything, updating drivers, reinstalling adb, trying diferent usb cables, different usb ports, but for some reason no matter what i try adb doesnt recognize any device. it recognizes my atrix just fine, but not the nexus. and the nexus is also rooted and has cwm but somehow the bootloader says ship s-on. it all seems prtty wierd. any ideas?
I had the same problem once. ADB recognized other devices I had but not the N1.
The driver from this thread got it working for me.
http://forum.xda-developers.com/showthread.php?t=613217
Unlocking the bootloader doesn't control whether the secuflag is on or off. If you Nexus One cannot be found by adb, check if you really have working abd drivers. Use this tool to see what usb drivers are installed and delete everything related to the Nexus One and let them reinstall:
http://download.cnet.com/USBDeview/3000-2094_4-10614190.html
If that doesn't work, plug your N1 to your pc for the last time, then press Windows key + r so the "run" box shows up. Type in devmgmt.msc (device management) and press enter. See if something called "android phone" has a yellow triangle. Download and unzip the attached archive. Right click this "android phone" and choose to update its drivers. Locate to the folder you just unzipped and then let the drivers install.
Now it should work just fine. Cheers.
baseballfanz said:
I had the same problem once. ADB recognized other devices I had but not the N1.
The driver from this thread got it working for me.
http://forum.xda-developers.com/showthread.php?t=613217
Click to expand...
Click to collapse
already tried that driver and same thing
Theshawty said:
Unlocking the bootloader doesn't control whether the secuflag is on or off. If you Nexus One cannot be found by adb, check if you really have working abd drivers. Use this tool to see what usb drivers are installed and delete everything related to the Nexus One and let them reinstall:
http://download.cnet.com/USBDeview/3000-2094_4-10614190.html
If that doesn't work, plug your N1 to your pc for the last time, then press Windows key + r so the "run" box shows up. Type in devmgmt.msc (device management) and press enter. See if something called "android phone" has a yellow triangle. Download and unzip the attached archive. Right click this "android phone" and choose to update its drivers. Locate to the folder you just unzipped and then let the drivers install.
Now it should work just fine. Cheers.
Click to expand...
Click to collapse
still nothing with reinstalling
gunna try restoring stock firmware and see what happens
not even going back and flashing stck firmware will let it connect to adb
USB debugging is ON, right...?
but thats probably not the problem.
driver issue, most likely. try installing sdk here
"The Google USB driver is a downloadable component for the Android SDK, available from the SDK Manager"
Aceyo said:
USB debugging is ON, right...?
but thats probably not the problem.
driver issue, most likely. try installing sdk here
"The Google USB driver is a downloadable component for the Android SDK, available from the SDK Manager"
Click to expand...
Click to collapse
as i told the other 2, it is not a driver issue, it turns out the guy i got it from had work done on it before it was shipped, thinking something internal is the issue
Hi all.
I'm trying to S-Off my HTC first, but I can't get the phone to connect to ADB while in debug mode. It connects to ADB fine while in recovery mode, but apparently it needs to be in debug mode for moonshine to work. The phone is unlocked and rooted and I installed the HTC drivers. In the device manager it comes up as an Android device in recovery mode, but as a portable storage device in debug mode.
Can anyone tell me what I'm doing wrong?
nikpmr said:
Hi all.
I'm trying to S-Off my HTC first, but I can't get the phone to connect to ADB while in debug mode. It connects to ADB fine while in recovery mode, but apparently it needs to be in debug mode for moonshine to work. The phone is unlocked and rooted and I installed the HTC drivers. In the device manager it comes up as an Android device in recovery mode, but as a portable storage device in debug mode.
Can anyone tell me what I'm doing wrong?
Click to expand...
Click to collapse
Does it show up when typing adb devices in the command prompt?
Thanks for the reply.
No, not unless the phone is in recovery mode. Fastboot works as well. However when the phone is on and in debug mode I get nothing.
nikpmr said:
Thanks for the reply.
No, not unless the phone is in recovery mode. Fastboot works as well. However when the phone is on and in debug mode I get nothing.
Click to expand...
Click to collapse
Hmmm sounds like what happened to me once it was a frustrating situation but all that was needed was an update to the ADB drivers for the device. Sadly I'm away from my computer right now so it'll be a while until I can actually whip something up to help you, sorry
Try to force ADB to redetect with adb kill-server.
abrahammmmmmm_ said:
Hmmm sounds like what happened to me once it was a frustrating situation but all that was needed was an update to the ADB drivers for the device. Sadly I'm away from my computer right now so it'll be a while until I can actually whip something up to help you, sorry
Click to expand...
Click to collapse
Okay, let me know when you have some time. Thanks again!
I tried the kill-server command to no avail. The computer just plain doesn't recognize it as an Android device. I will try on my Linux computer and see if that makes any difference.
nikpmr said:
Okay, let me know when you have some time. Thanks again!
I tried the kill-server command to no avail. The computer just plain doesn't recognize it as an Android device. I will try on my Linux computer and see if that makes any difference.
Click to expand...
Click to collapse
Is your computer windows 7, 8 x32 or x64bit? I can probably do it today if you've got a windows 7 x64bit computer since I wont have to do much looking
I'm running win 7 64 bit. Thanks again for your help!
nikpmr said:
I'm running win 7 64 bit. Thanks again for your help!
Click to expand...
Click to collapse
NOTE THAT YOUR PHONE SHOULD NOT BE CONNECTED DURING THIS PROCESS
I already searched & set up the update folder so you don't have to do all the dirty work d:\
Ok Well I'm just going to make this quick and not really got through the basics like how to unzip things because if you don't know how to do that you probably shouldn't be trying to get s-off on your phone anyway so I'll just assume you already know how.
Step 1. open control panel select hardware and sound and open Device Manager with the administrative logo one the side.
Step 2. Near the top or somewhere on this list there's supposed to be a drop down that reads "adb devices, adb android, adb, android, adb drivers etc. Mine shows Android USB Devices it actually just varies based on computer I can't really go to the specifics of it but I'm sure you can find it.
Step 3. Select that dropdown menu and right click whatever shows (there should only be one thing) and then select Update Driver Software and choose the option that says Browse my computer for driver software and locate the htc drivers folder which should already be unzipped, select the whole folder and have the option to include subfolders checked. click next or whatever it says to finish
Step 3 Now you must remove your device from the Portable Devices dropdown menu to ensure all drivers are detected for the phone, to do this right click on HTC First and just select remove, wait until it's done. and now just reconnect your device and let all the drivers install and it should now be done!
Make sure you look at the screenshots I attached to make sure you don't accidentally remove or update something else also because that's where the drivers folder is an i'm pretty sure you'll need that
A reboot of the computer is recommended btw
Ask questions if you have any
View attachment 2459140
View attachment HTC_drivers_Win7_x64.zip
View attachment 2459141
Wow, that's quite explanatory, thank you! Unfortunately I only see the category ADB Devices when the phone is connected and in recovery mode, and I only see the category Portable Devices when the phone is connected, booted, and in debug mode. (Neither of these categories are visible when the phone is disconnected from the computer.) I did however try installing the drivers you gave me with the phone connected and in recovery mode, but to no avail; after the phone boots ADB Devices disappears and Portable Devices appears. Uninstalling Portable Devices doesn't help either; it just reinstalls when I reconnect the phone.
I am trying to get the category ADB Devices to appear in the Device manager when the phone is turned on and in debug mode so that I can use ADB while the phone is booted.
Got it working. I had to go to device manager > portable devices > HTC First and replace the driver with Generic USB Composite Device Driver.
Boom. Everything working. Weird.
nikpmr said:
Got it working. I had to go to device manager > portable devices > HTC First and replace the driver with Generic USB Composite Device Driver.
Boom. Everything working. Weird.
Click to expand...
Click to collapse
How exactly did you replace the HTC First driver with the Generic USB Composite Device Driver?
Ok I've been at this for hours trying to get adb to recognize the tablet in recovery mode and to no avail. I've tried every trick and random driver i can find on here and still am unable to get adb to recognize the tablet while waiting for a sideload .bin file. While in normal mode while up and running adb devices command find sit np but once it goes into recovery it's gone.
I type adb devices and it comes back null. I've tried killing and restarting the daemon server and that isn't it. I've tried uninstalling and reinstalling the drivers. There is even an ADB composite driver listed in the device manager and yet once the tablet is in recovery mode it seems to disappear.
I tried doing a factory reset and wiping the cache. i'm drawing a blank on this. I've also tried changing usb ports and cables on the computer. It's just not working.
Any ideas?
You may need to disable driver signature enforcement
then install drivers.
After that you may still need to follow this guide
http://forum.xda-developers.com/showpost.php?p=62561874&postcount=2
This was written for a different FIRE so yours will be KFFOWI instead of KFARWI in the guide.
I did this and in worked for me..
There are two options to restore stock at the bottom of this link, it all depends what version you have. See if it helps...
http://forum.xda-developers.com/showpost.php?p=62986666&postcount=4
or you could also try this to get into Amazon Custom recovery:
adb reboot recovery
Yeah, most likely a driver issue. Try different drivers until you find one that actually works!
Well I just thought of this when I woke up, could it be that I'm using minimal ADB and fastboot or should that not make a difference?
As long as your device is listed when doing a "adb devices" or "fastboot devices" should make no difference. But yes, minimal should be fine.
But it is usually a good idea to have the latest version.
I think your issue is with getting to Amazon recovery. If in recovery, there should be a menu. See that menu here in post #3:
http://forum.xda-developers.com/amazon-fire/general/amazon-fire-2015-tips-tricks-t3214544
Tuvan03 said:
Ok I've been at this for hours trying to get adb to recognize the tablet in recovery mode and to no avail. I've tried every trick and random driver i can find on here and still am unable to get adb to recognize the tablet while waiting for a sideload .bin file. While in normal mode while up and running adb devices command find sit np but once it goes into recovery it's gone.
Click to expand...
Click to collapse
You're talking 2 different modes here: (1) Recovery mode: You see menu options on tablet. Windows can't ever recognize device while in recovery mode; no driver appears in Win Device Manager. (2) Sideload mode: After you select "apply update from ADB" and press power button and you see yellow text on tablet saying to sideload the file. Fire appears in Device Manager. If no driver installed (or messed up), it's under "Other" with the name KFFOWI as @gray-beard said. That's what you need to install drivers for in order for sideload to work. I doubt Minimal adb is the problem. You're probably just not all the way into sideload mode. If problems persist, open the console window from the folder containing adb.exe.
gray-beard said:
You may need to disable driver signature enforcement
then install drivers.
After that you may still need to follow this guide
http://forum.xda-developers.com/showpost.php?p=62561874&postcount=2
This was written for a different FIRE so yours will be KFFOWI instead of KFARWI in the guide.
I did this and in worked for me..
Click to expand...
Click to collapse
Many Thanks Gray Beard, it's reloading the stock firmware now. I was just trying to go through the pick your device drivers thing too quickly and needed to do the see all devices to be able to see the adb drivers to get them loaded.
A pint of the finest dwarven ale to you (with a name like gray beard i couldn't resist)
EDIT: I did all this just to try to restore OTA updates, yet i hit the update button now that it's restored with the factory firmware and it's saying no updates found. hmm
After doing lots of reading and trying many things I cannot connect in fastboot mode. I tried on two computers, holding volume down and plugging in usb cable. In CMD I run fastboot status and it just stays on <waiting for device>. I have connected other Android phones so maybe that is somehow messing up the device drivers, but I reinstalled them. Also when I run adb reboot fastboot from CMD, the phone restarts normally and not to fastboot but the volume down at least shows blank screen.
My goal is to get root, so whatever is easiest.
LuminousOne said:
After doing lots of reading and trying many things I cannot connect in fastboot mode. I tried on two computers, holding volume down and plugging in usb cable. In CMD I run fastboot status and it just stays on <waiting for device>. I have connected other Android phones so maybe that is somehow messing up the device drivers, but I reinstalled them. Also when I run adb reboot fastboot from CMD, the phone restarts normally and not to fastboot but the volume down at least shows blank screen.
My goal is to get root, so whatever is easiest.
Click to expand...
Click to collapse
If you have used that computer for other phones previously, that might be the problem, Winodws is asigning the wrong driver. In your picture you have devices with warning triangles (no drivers). Try manually assigning the Sony driver. Depends on what you're doing, but you need a different driver for when you want to use ADB, so start the phone into recovery, connect it to your PC and look again in the device manager and manually add the Google USB driver.
If you are using windows10 and trying to install drivers, it doesn't tell you that the install failed. Restart the machine in safemode and look for 'driver signing disabled'
Didgesteve said:
If you have used that computer for other phones previously, that might be the problem, Winodws is asigning the wrong driver. In your picture you have devices with warning triangles (no drivers). Try manually assigning the Sony driver. Depends on what you're doing, but you need a different driver for when you want to use ADB, so start the phone into recovery, connect it to your PC and look again in the device manager and manually add the Google USB driver.
If you are using windows10 and trying to install drivers, it doesn't tell you that the install failed. Restart the machine in safemode and look for 'driver signing disabled'
Click to expand...
Click to collapse
It's unclear to me which driver should be added to which device. For example should the Sony or Google driver be added to the section Android Devices, Portable Devices, or Sony?
LuminousOne said:
It's unclear to me which driver should be added to which device. For example should the Sony or Google driver be added to the section Android Devices, Portable Devices, or Sony?
Click to expand...
Click to collapse
I'm not sure what you're trying to do. If you want to flash a rom, you want flashmode, volume down (-) then plug in the USB. If you want fastboot it's volume up (+) then plug in the USB..
MTP driver is wrong, you need to uninstall it and re-install the sony driver. Windows chooses the wrong driver by default and you have to manually add it yourself to make it work.
Having said that you mentioned that you are getting ADB commands to work, so I'm confused, perhaps the google driver is in place, but the Sony one is not.
You need both, when the phone is in fastboot it's presented as a different device than when connected via ADB.
Hope that helps explain a bit.
But if you're having issues with the drivers, should you really be going down the unlocking road? It doesn't get you many advantages and breaks a whole heap of sh*t.
LuminousOne said:
It's unclear to me which driver should be added to which device. For example should the Sony or Google driver be added to the section Android Devices, Portable Devices, or Sony?
Click to expand...
Click to collapse
I had this problem before. My fault before was install drivers in usb-debugging mode, then a change to fastbook/flash, and then the phone is not recognized or connection properly - despite me thinking I had correctly installed the drivers.
Took me months to figure it out. Boot into windows, then connect your phone in all modes, flash mode, fastbook mode, standard, and usb debugging - and for each mode - install the Sony driver again.
The result will be, that for every mode - when you go to device manager - you won't see an exclamation mark. If you ever see an exclamation mark again - install the driver. You get the idea.
Regards,
I finally found the f**kin problem the invalid driver was hiding under "other devices" only when the phone was in fastboot mode. Basically I followed the instructions of user2021355 from here.
Start Windows in test mode (instructions)
download driver from https://developer.sony.com/develop/drivers/
in admin command prompt run adb reboot bootloader
if the above step failed, you have a problem with adb and the solution is something different
open device manager and carefully search for any errors. I found mine hidden under "other devices"
right click on the errored driver and choose update
choose browse my computer
select the driver you downloaded from step 2
verify if working by running fastboot devices and you should get a serial number
Didgesteve said:
should you really be going down the unlocking road? It doesn't get you many advantages and breaks a whole heap of sh*t.
Click to expand...
Click to collapse
I thought the only thing it broke was the camera and there's a DMR fix for that. Does it mess up something else?
LuminousOne said:
I thought the only thing it broke was the camera and there's a DMR fix for that. Does it mess up something else?
Click to expand...
Click to collapse
Some banking and games apps don't like rooted phones.
Not sure about android pay.
Hi
I ve the yellow exclamation mark in device manager -> other devices -> "Android"
When I point to the Xperia_XZ1_Compact_driver/ folder (from https://developer.sony.com/file/download/xperia-xz1-compact-driver// ), windows cant find a driver.
same is when pointing to the drivers from here: https://developer.android.com/studio/run/win-usb
I ve the G8441
sheedy1900 said:
Hi
I ve the yellow exclamation mark in device manager -> other devices -> "Android"
When I point to the Xperia_XZ1_Compact_driver/ folder (from https://developer.sony.com/file/download/xperia-xz1-compact-driver// ), windows cant find a driver.
I ve the G8441
Click to expand...
Click to collapse
Add the driver manually.
Didgesteve said:
Add the driver manually.
Click to expand...
Click to collapse
At least for me it wasn't enough to add the driver manually (I think because the invalid driver would still be there). So you need to right click on it, update, then browse to the downloaded driver.
OK I got it working with installing the driver, win10 bootet with disabled Driver Signature enforcement
LuminousOne said:
At least for me it wasn't enough to add the driver manually (I think because the invalid driver would still be there). So you need to right click on it, update, then browse to the downloaded driver.
Click to expand...
Click to collapse
I think we have different ideas of what adding the driver manually is
sheedy1900 said:
OK I got it working with installing the driver, win10 bootet with disabled Driver Signature enforcement
Click to expand...
Click to collapse
i have the problem as you and I'm also on win10. can you share how you installed the fastboot driver?
the adb and mtp drivers work fine for me, just fastboot is not working
unsigned driver under W10
try this one
https://www.maketecheasier.com/install-unsigned-drivers-windows10/
Gesendet von meinem viennalte mit Tapatalk
I have the same problem with my Sony XZ1 Compact G8441.
'adb devices' shows my phone, after 'adb reboot bootloader' phone goes into fastboot mode (I think), the one with blue LED, but 'fastboot devices' does not show any connected devices. Same when pressing Volume Up or Volume Down while plugging the phone in.
After some reading I figured it was a driver issue, so I tried installing drivers from Sony XZ1 Compact driver and Sony Fastboot Driver.
Tried installing through device manager, right-click on faulty 'Android' under 'Other Devices', update driver, browse to download location.
With 'Sony XZ1 Compact driver' it found no installable drivers.
With 'Sony Fastboot Driver' it found an installable driver but had an error. Error said something like 'Did not find "Android ADB Interface", installation failed'.
I tried figuring out what you guys meant by 'installing driver manually' but I don't understand. Is it what I tried above, or something else?
My goal is to be able to install TWRP, which needs an unlocked Bootloader first. I followed the instructions on the official Sony Website for that.
Sorry. Delete this.
Gnorv said:
After some reading I figured it was a driver issue, so I tried installing drivers from Sony XZ1 Compact driver and Sony Fastboot Driver.
Click to expand...
Click to collapse
If you're using Windows 10 you'll have thought that you'd have installed the drivers, but W10 fails on driver install and doesn't tell you.
Start the pc in 'safe mode' (hold shift while restarting), then choose 'driver signing disabled', install the drivers agiain. This time it should work.
Didgesteve said:
If you're using Windows 10 you'll have thought that you'd have installed the drivers, but W10 fails on driver install and doesn't tell you.
Start the pc in 'safe mode' (hold shift while restarting), then choose 'driver signing disabled', install the drivers agiain. This time it should work.
Click to expand...
Click to collapse
No, that did not help. The same problem remains. Phone is recognized when powered on by 'adb devices' but not recognized after typing 'adb reboot bootloader' and 'fastboot devices'.
Thanks for your suggestion though.
I got the problem that no matter what i do i can't install the driver.
Booting windows 10 with driver check disabled does not solve my problem.
Once i selected the driver to install i end up with a questionmark in the device manager above the android device. Taking a closer look reveals that there seems to be no driver installed.....
Any advice?
I tried:
1. Booting with driver signature check disabled
2. Switching windows 10 into test Mode
I booted ubuntu from a live usb stick and went from there. That works like a charm without the need of installing any drivers
Both solutions do not work....