Everything was going well, about to start the install when a message came up drivers not installed. Needless to say now I'm stuck.
Screen says Now send the package you want to apply
to the device with "adb sideload <filename>"
Drivers were installed now there not, and they refuse to install. Help please
richport29 said:
Everything was going well, about to start the install when a message came up drivers not installed. Needless to say now I'm stuck.
Screen says Now send the package you want to apply
to the device with "adb sideload <filename>"
Drivers were installed now there not, and they refuse to install. Help please
Click to expand...
Click to collapse
Koush's Universal ADB Drivers.
Thank you
Related
Hi,
I hope someone can help me out. I recently updated to 4.4.1 via Clockworkmod. The update worked fine but now I'm unrooted. I still have the SU app, it just doesn't do anything. Is there a way to remove it without rooting again? If not what's the easiest way to root the device (bootloader is unlocked and currently have stock recovery)? The first time I rooted the bootloader was locked and the process I used unlocked and rooted in the same step.
Thanks for your help!
keep the app. reflash a custom recovery, then flash the latest supersu in your custom recovery. there, youre rooted again.
simms22 said:
keep the app. reflash a custom recovery, then flash the latest supersu in your custom recovery. there, youre rooted again.
Click to expand...
Click to collapse
Thanks. Don't want to mess anything up so any info you can provide on how to flash a custom recovery while unrooted would be greatly appreciated.
danotoriusodo said:
Thanks. Don't want to mess anything up so any info you can provide on how to flash a custom recovery while unrooted would be greatly appreciated.
Click to expand...
Click to collapse
http://lmgtfy.com/?q=how+to+flash+custom+recovery+fastboot
danotoriusodo said:
Thanks. Don't want to mess anything up so any info you can provide on how to flash a custom recovery while unrooted would be greatly appreciated.
Click to expand...
Click to collapse
flashing a recovery, a rom, a kernel, and a mod doesnt require root. the only thing that requires root are apps that need root to work.
simms22 said:
flashing a recovery, a rom, a kernel, and a mod doesnt require root. the only thing that requires root are apps that need root to work.
Click to expand...
Click to collapse
Tried sideloading 4.2.2 before I rooted again and can't get my phone recognized in sideload. Now I can't even restart my phone. Tried using a different usb port and cable and nothing. I'm reading the only way to restart my phone is to wait for the battery to drain. Is there anything else I can try? Thanks.
danotoriusodo said:
Tried sideloading 4.2.2 before I rooted again and can't get my phone recognized in sideload. Now I can't even restart my phone. Tried using a different usb port and cable and nothing. I'm reading the only way to restart my phone is to wait for the battery to drain. Is there anything else I can try? Thanks.
Click to expand...
Click to collapse
What do you mean you can't restart it? Is it frozen? Try holding down the power button for about thirty seconds. It seems to be the equivalent of removing the battery.
Saturn2K said:
What do you mean you can't restart it? Is it frozen? Try holding down the power button for about thirty seconds. It seems to be the equivalent of removing the battery.
Click to expand...
Click to collapse
Got it. Thanks. Any idea why it wouldn't recognize the device? I downloaded the driver package from SDK manager and tried to update from the extras folder but it said my package was up to date. The only weird thing is the driver is showing up as Samsung Android phone in device manager. I tried uninstalling, restarted the computer, reconnected my phone and it still says Samsung.... Again, any help is greatly appreciated. Thanks.
danotoriusodo said:
Got it. Thanks. Any idea why it wouldn't recognize the device? I downloaded the driver package from SDK manager and tried to update from the extras folder but it said my package was up to date. The only weird thing is the driver is showing up as Samsung Android phone in device manager. I tried uninstalling, restarted the computer, reconnected my phone and it still says Samsung.... Again, any help is greatly appreciated. Thanks.
Click to expand...
Click to collapse
Maybe read my edit below first. What follows is the manual way for doing this. There's a program that'll do all of this for you if you don't want to mess with this.
Try installing the Google Android USB drivers.
http://developer.android.com/sdk/win-usb.html
To install the USB drivers, first boot your phone into the bootloader (hold volume down and the power button while the phone is off). Then go into your device manager in windows. You'll either see something flagged with some yellow icon or you'll need to find some entry that says something about Android or your phone. Right click on that and hit update drivers. Unzip the latest_usb_driver_windows.zip somewhere and then point the driver updater at that folder. It'll find and install drivers. Voila, fastboot should now recognize your phone.
Then follow the steps for getting into the bootloader, flashing the custom recovery, and then flashing superuser from the custom recovery.
Edit: OR, just use the Nexus Root Toolkit http://www.wugfresh.com/nrt/
It has an option for installing drivers, installing the custom recovery, etc. It's very straightforward.
Saturn2K said:
Maybe read my edit below first. What follows is the manual way for doing this. There's a program that'll do all of this for you if you don't want to mess with this.
Try installing the Google Android USB drivers.
http://developer.android.com/sdk/win-usb.html
To install the USB drivers, first boot your phone into the bootloader (hold volume down and the power button while the phone is off). Then go into your device manager in windows. You'll either see something flagged with some yellow icon or you'll need to find some entry that says something about Android or your phone. Right click on that and hit update drivers. Unzip the latest_usb_driver_windows.zip somewhere and then point the driver updater at that folder. It'll find and install drivers. Voila, fastboot should now recognize your phone.
Then follow the steps for getting into the bootloader, flashing the custom recovery, and then flashing superuser from the custom recovery.
Edit: OR, just use the Nexus Root Toolkit http://www.wugfresh.com/nrt/
It has an option for installing drivers, installing the custom recovery, etc. It's very straightforward.
Click to expand...
Click to collapse
Thanks for your help. I can definitely try the Nexus root Toolkit but I'd really like to get comfortable doing it manually.
The issue I keep running into is with the drivers. I uninstalled the drivers, installed them again while in the bootloader and it said successful (shows up as Android device > Android Bootloader Interface). Then when I enter recovery and select adb..., device manager lists it as an "Other Device > Nexus 5" with the yellow triangle. I try again there to update the drivers from the same folder that they installed in via the SDK and I get an error that the device driver software can't be found. I have usb debugging mode checked and selected always allowed for this computer. I've tried "adb devices" and nothing is recognized. Any thoughts?
danotoriusodo said:
Thanks for your help. I can definitely try the Nexus root Toolkit but I'd really like to get comfortable doing it manually.
The issue I keep running into is with the drivers. I uninstalled the drivers, installed them again while in the bootloader and it said successful (shows up as Android device > Android Bootloader Interface). Then when I enter recovery and select adb..., device manager lists it as an "Other Device > Nexus 5" with the yellow triangle. I try again there to update the drivers from the same folder that they installed in via the SDK and I get an error that the device driver software can't be found. I have usb debugging mode checked and selected always allowed for this computer. I've tried "adb devices" and nothing is recognized. Any thoughts?
Click to expand...
Click to collapse
Did you flash a custom recovery while you were in the bootloader? I'm don't think adb works in the stock recovery, but I could be wrong.
As long as you have the bootloader working, that's all you really need. You just need to flash the custom recovery. Then put some superuser.zip onto your storage, boot into the recovery, and flash it.
As for the driver issue, I only did what I told you. If doing it manually didn't work, I'd try the toolkit.
Saturn2K said:
Did you flash a custom recovery while you were in the bootloader? I'm don't think adb works in the stock recovery, but I could be wrong.
As long as you have the bootloader working, that's all you really need. You just need to flash the custom recovery. Then put some superuser.zip onto your storage, boot into the recovery, and flash it.
As for the driver issue, I only did what I told you. If doing it manually didn't work, I'd try the toolkit.
Click to expand...
Click to collapse
I think the whole point of sideloading is that you can have everything stock if that's what you want. I'm going to try the toolkit because I've tried and tried and can't get the sideload to work. When the phone is turned on I can type "adb devices" and my serial number comes up. I can eneter "adb reboot bootloader" and the phone restarts. It's just when I get to recovery it tells me "device not found". Thanks again for your help and if you or anyone else has any suggestions I'm all ears.
danotoriusodo said:
I think the whole point of sideloading is that you can have everything stock if that's what you want. I'm going to try the toolkit because I've tried and tried and can't get the sideload to work. When the phone is turned on I can type "adb devices" and my serial number comes up. I can eneter "adb reboot bootloader" and the phone restarts. It's just when I get to recovery it tells me "device not found". Thanks again for your help and if you or anyone else has any suggestions I'm all ears.
Click to expand...
Click to collapse
Hmm, from your reply, I'm not sure if you're getting into recovery or not. There's the bootloader and there's recovery, they're separate things. Once you're in the bootloader, you choose to go into the recovery. Then, in the recovery, you choose to "apply update from ADB." Then you issue the adb sideload command from your computer.
Saturn2K said:
Hmm, from your reply, I'm not sure if you're getting into recovery or not. There's the bootloader and there's recovery, they're separate things. Once you're in the bootloader, you choose to go into the recovery. Then, in the recovery, you choose to "apply update from ADB." Then you issue the adb sideload command from your computer.
Click to expand...
Click to collapse
Thanks but that's what I've been doing and what's driving me crazy. ADB works when the phone is on. It recognizes my device and reboots on command. I get to the bootloader where it still recognizes my device. Once I select recovery, the phone comes up with the yellow triangle in device manager and I can't sideload after I select the option. A friend of mine who;s sideloaded before watched me do it and was just as confused. Any other suggestions?
**Update**
So for some reason the driver package installed via the SDK manager doesn't have the Nexus 5 "hardware id". I needed to add these three lines in the .inf file within the usb drivers folder:
;Google Nexus 5
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_D001
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001&REV_0232
One I added those and updated the driver I was able to sideload.
Thanks again for your help
I am really confused since having to use ADB and flashboot. I am thoroughly confused that someone has not simply written step by step instructions for this in a sticky so newbies like myself can follow. With that in mind I am trying to change from CWM to TWRP. I have the files but completely oblivious on how to get things to work again. I go into a command propt and start adb or flashboot but cant seem to get it to find the device. Now I cannot find the instructions I used to install CWM. Can somoene kindly help with either a link or instructions to make this change so I can be good and flash some ROM's?
Thanks,
crazysane said:
I am really confused since having to use ADB and flashboot. I am thoroughly confused that someone has not simply written step by step instructions for this in a sticky so newbies like myself can follow. With that in mind I am trying to change from CWM to TWRP. I have the files but completely oblivious on how to get things to work again. I go into a command propt and start adb or flashboot but cant seem to get it to find the device. Now I cannot find the instructions I used to install CWM. Can somoene kindly help with either a link or instructions to make this change so I can be good and flash some ROM's?
Thanks,
Click to expand...
Click to collapse
1) Power your phone off and once its off hold down power + volume down until its booted into HBOOT/Fastboot mode (bootloader).
2) Place your TWRP img file in the platform-tools folder where your adb/fastboot files are.
3) Shift + Right click inside of the platform-tools folder and open as a command prompt.
4) If you're not already, switch to fastboot mode and assure it says "Fastboot USB" or just fastboot at the top (don't remember if it says USB or not) and then in the command window type the following command and press enter: 'fastboot flash recovery name.img'. Replace "name" with the file name of your TWRP img.
5) It should say "successful" and then from there you can navigate to your new TWRP recovery via the bootloader by navigating with the volume keys and selecting the "Recovery" option by pressing the power button once its selected.
Download links for latest TWRP: http://teamw.in/project/twrp2/226
Direct download link for latest TWRP can be found here
S1L3nTShaDoWz said:
1) Power your phone off and once its off hold down power + volume down until its booted into HBOOT/Fastboot mode (bootloader).
2) Place your TWRP img file in the platform-tools folder where your adb/fastboot files are.
3) Shift + Right click inside of the platform-tools folder and open as a command prompt.
4) If you're not already, switch to fastboot mode and assure it says "Fastboot USB" or just fastboot at the top (don't remember if it says USB or not) and then in the command window type the following command and press enter: 'fastboot flash recovery name.img'. Replace "name" with the file name of your TWRP img.
5) It should say "successful" and then from there you can navigate to your new TWRP recovery via the bootloader by navigating with the volume keys and selecting the "Recovery" option by pressing the power button once its selected.
Download links for latest TWRP: http://teamw.in/project/twrp2/226
Direct download link for latest TWRP can be found here
Click to expand...
Click to collapse
Really appreciate what you said but I am running into the issue in the command prompt. When I type the commands it says
error: device not found
I have rebooted both phone and computer but it never seems to find the device now and not sure what to do.
Do you have any suggestions on do I start adb and run any commands, SU, fastboot, or what? I know its working because the computer sees the devices by an external drive. The phone is able to go into fastboot on reboot as well. I just do not know where my dilemma is.
Do you have USB debugging enabled under developer options?
adavit said:
Do you have USB debugging enabled under developer options?
Click to expand...
Click to collapse
yes I do and as I said it sees the device as other storage.
crazysane said:
Really appreciate what you said but I am running into the issue in the command prompt. When I type the commands it says
error: device not found
I have rebooted both phone and computer but it never seems to find the device now and not sure what to do.
Do you have any suggestions on do I start adb and run any commands, SU, fastboot, or what? I know its working because the computer sees the devices by an external drive. The phone is able to go into fastboot on reboot as well. I just do not know where my dilemma is.
Click to expand...
Click to collapse
I'd assume this means you haven't installed the proper drivers? Well actually I'm not really sure these even relate to the fastboot drivers BUT worth a shot to fix your problem!
Download HTC Sync Manager from here and install it and let it install the proper drivers for your M8 (with phone powered on of course) and once they are installed and it's done make 100% sure you UNINSTALL HTC Sync Manager after, only the program, not the drivers themselves.
After that re-attempt it and also as the other guy said, enable USB debugging all though I don't think it will do anything unless the phones booted into Android(may be wrong).
Also see if you can get ADB to work while the phone is running. Instructions for testing ADB would be turn the phone on, enable USB debugging and in the command prompt type
Code:
adb devices
and if it pops up your device then you should be good. If it doesn't then it's most likely related to the drivers and I would recommend you uninstall all drivers and remove every trace of them. My prefered method of uninstalling them is using Device Manager (windows tool) to uninstall the drivers and then use USBDeview to remove the rest/traces/etc.
S1L3nTShaDoWz said:
I'd assume this means you haven't installed the proper drivers? Well actually I'm not really sure these even relate to the fastboot drivers BUT worth a shot to fix your problem!
Download HTC Sync Manager from here and install it and let it install the proper drivers for your M8 (with phone powered on of course) and once they are installed and it's done make 100% sure you UNINSTALL HTC Sync Manager after, only the program, not the drivers themselves.
After that re-attempt it and also as the other guy said, enable USB debugging all though I don't think it will do anything unless the phones booted into Android(may be wrong).
Also see if you can get ADB to work while the phone is running. Instructions for testing ADB would be turn the phone on, enable USB debugging and in the command prompt type
Code:
adb devices
and if it pops up your device then you should be good. If it doesn't then it's most likely related to the drivers and I would recommend you uninstall all drivers and remove every trace of them. My prefered method of uninstalling them is using Device Manager (windows tool) to uninstall the drivers and then use USBDeview to remove the rest/traces/etc.
Click to expand...
Click to collapse
OK finally found the phone and flashed putting TWRP on it for recovery. Thank you very much. Using the ADB and FASTBOOT are things I guess I truly need to learn. So, with that I thank you and now I feel good about beginning my ROM flashing.
crazysane said:
OK finally found the phone and flashed putting TWRP on it for recovery. Thank you very much. Using the ADB and FASTBOOT are things I guess I truly need to learn. So, with that I thank you and now I feel good about beginning my ROM flashing.
Click to expand...
Click to collapse
May I ask what you did to get it working? Was it the developer options? HTC Sync Manager drivers? something else?
& you're welcome!
crazysane said:
yes I do and as I said it sees the device as other storage.
Click to expand...
Click to collapse
Sorry, I was kinda skimming your reply and watching TV at the same time (big mistake lol). I'm glad that you were able to get everything work.
S1L3nTShaDoWz said:
May I ask what you did to get it working? Was it the developer options? HTC Sync Manager drivers? something else?
& you're welcome!
Click to expand...
Click to collapse
I basically went in and did the adb devices. Once it seemed to see it I had to do the adb reboot bootloader then do the flashboot flash recovery twrp img. Now I have it working and about to flash santod's NuSense ROM since I used it on my thunderbolt that was recently replaced by this. Wish me luck LOL.
Hello. After doing some things in TWRP I got stuck in a boot loop. I wiped all storage so that I could just sideload a ROM, but I can't sideload because ADB is not working properly. I've installed Android SDK and the drivers for my phone, however no ADB commands would work. I decided to attempt to update the drivers but going into device manager shows that there is no Android ADB Interface like usual. Help please?
ItsGflow said:
Hello. After doing some things in TWRP I got stuck in a boot loop. I wiped all storage so that I could just sideload a ROM, but I can't sideload because ADB is not working properly. I've installed Android SDK and the drivers for my phone, however no ADB commands would work. I decided to attempt to update the drivers but going into device manager shows that there is no Android ADB Interface like usual. Help please?
Click to expand...
Click to collapse
Put the phone in download mode and re-flash the firmware using LG-Flash tool. I've been there and the driver resolution issue on anything above Windows7 didnt work. Even the Adb Sideload.
Hi, I've deleted all storage from my device and all I've got now is TWRP recovery.
I', trying to push a rom through fastboot but my PC won't recognize my device, I have Universal ADB Drivers intalled, also I've got Samsung ADB drivers istalled, and Android SDK installed; yet my device won't show up when I'm in fastboot and typing 'adb devices'.
Obviously I cannot turn Debugging on since I don't have a system.
so...
what CAN I do?
thanks
Lidor167 said:
Hi, I've deleted all storage from my device and all I've got now is TWRP recovery.
I', trying to push a rom through fastboot but my PC won't recognize my device, I have Universal ADB Drivers intalled, also I've got Samsung ADB drivers istalled, and Android SDK installed; yet my device won't show up when I'm in fastboot and typing 'adb devices'.
Obviously I cannot turn Debugging on since I don't have a system.
so...
what CAN I do?
thanks
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?t=2788632
Use drivers and setup from this guide.
I'm trying to unlock my bootloader to install a custom rom. "adb devices" command works fine but "fastboot devices" doesn't return anything. In windows device manager i haven't updated drivers because i dont know where to download them. Any help with drivers? I have an "android bootloader interface" option there but windows warns me that it might not be compatible and might break everything.
Download the Universal adb drivers from google
vuittion said:
Download the Universal adb drivers from google
Click to expand...
Click to collapse
I have done this, but it didn't help
enkerrohah said:
I have done this, but it didn't help
Click to expand...
Click to collapse
Download Tool all in one for flashing recovery and unlock bootloader. For One Plus 6. Check in XDA. Install necessary drivers. In developer option,usb debugging and file transfer for OTG.
sschacko said:
Download Tool all in one for flashing recovery and unlock bootloader. For One Plus 6. Check in XDA. Install necessary drivers. In developer option,usb debugging and file transfer for OTG.
Click to expand...
Click to collapse
Just downloading the adb drivers from google's own site made it work on another PC. I think my problem is that Windows has installed the wrong drivers for me. When i plug a device in for the first time, it says something like "setting up your device". I think during that point it installed wrong drivers on my own PC. On my brothers PC everything works like it's supposed to. Any idea how to get Windows to install the drivers again?
enkerrohah said:
Just downloading the adb drivers from google's own site made it work on another PC. I think my problem is that Windows has installed the wrong drivers for me. When i plug a device in for the first time, it says something like "setting up your device". I think during that point it installed wrong drivers on my own PC. On my brothers PC everything works like it's supposed to. Any idea how to get Windows to install the drivers again?
Click to expand...
Click to collapse
Problem persist when you try to install Drivers without valid signature in Windows 10.. Try to DIsable Driver Signature Enforcement..
Link to do it https://windowsreport.com/driver-signature-enforcement-windows-10/
Then try to install Drivers from this link :- https://drive.google.com/file/d/1L7EZGx5mgeQYXO19Vsp9FWu9GXhF45Qs/view
Let me know if that helps..
I have quit the same problem expected that i already have my bootloader unlock and usb debugging turn on...
im trying to flash twrp image, after failed yesterday to apply pixen os11. I had access to fasboot mode and to flash zip etc and my drivers was instaled but now my laptop didn't reconize my phone when plug in in fastboot and is on other devices in my devices manager. I tried to install updates manualy but nothing happened.
i dont know if it is related but i did update windows between my secon attempt to flash pixen os. Maybe the drivers were update in the same occasions ? Because a i have no others problems when my phone is boot normally and can acess to internal storage from my computer.