1st post here.
Seems like basic problem but I cannot get adb connected to my G1.
I started off on process of upgrading to CM 6.1 but when I was about to put recovery image on phone I discovered flash_image program was not found. Then set off on the adb route but am now stuck. Tried searching but not found answer. Here is what I have done/tried so far:-
PC is XP Pro SP3
G1 V1.6 rooted via Universal method (su works ok via Term)
Downloaded and installed latest SDK in c:\Android-sdk
USB debugging is enabled on phone
SD card is not mounted
When I run "adb devices" (from C:\android-sdk\platform-tools) it fails with
msg "error: protocol fault (no status)"
The basic usb connection to PC is known to be working ok (have copied files to phone sd card etc. no problem if I mount it)
The installation of usb drivers seemed to go ok although I had to do it manually from folder \android-sdk\google-usb_driver
When I look at usb devices with USBDeview there are 3 related to Android phone (all enabled).
1. HTC Android phone usb device (connected)
2. USB Mass storage device (not connected)
3. Android composite ADB interface (not connected)
Further info...
I see other people have had the same problem (with other phones as well) but cannot find any specific reason or fix that works.
I have reinstalled latest sdk rev08
Unintsalled and reinstalled latest google usb drivers (ver 4) endless times
Usb driver install appears to all go ok
In XP Device Manager I get Android Phone device which expanded shows single Android Composite Interface Device which has staus enabled and working ok
I have no "Other" usb devices etc. showing up in Device Manager
USBDeview shows 3 usb devices for Android phone. The connected one shows the htc serial no. The ADB composite interface is not connected and has no serial number.
I have tried different usb ports, cables, and another standard G1 phone - all gives same results
I noticed the adb_usb.ini file had no device id in it, I ran "update adb" as per comment note at top of adb_usb.ini but still got not entries in file.
Someone surely must have solution to this. I cannot believe a G1 phone does not work/been tested with sdk adb.
Maybe some source code guru can tell me under what conditions adb gives the "protocol error: no status" msg.
Or could someone with a working G1 adb usb connection post their adb_usb.ini etc.
Have spent 2 days on and off fiddling with this sdk now. :-(
Thanks
Shame you didn't spend some of that two days reading the site rules and the fact that not only is there Q&A section but also try posting in the ADB threads that are littered around these forums.
Catch me on irc, link in sig and I'll see what can be done.
I have read the Q&A and plenty of guides on how to setup adb including those on here. My problem seems a bit dfifferent from most others in that i have tried all the usual suggestions and they have not worked - Why I else would I bother posting detailed info here?
If you some links to threads which address problem please post them.
dalek1999 said:
I have read the Q&A and plenty of guides on how to setup adb including those on here. My problem seems a bit dfifferent from most others in that i have tried all the usual suggestions and they have not worked - Why I else would I bother posting detailed info here?
If you some links to threads which address problem please post them.
Click to expand...
Click to collapse
he offered help via irc, so you should think about accepting it.
anyway he ment that this has (almost) NOTHING to do with development and should have been posted in Q&A.
concerning your problem: i have no idea try if you can connect to fastboot.
dalek1999 said:
I have read the Q&A and plenty of guides on how to setup adb including those on here. My problem seems a bit dfifferent from most others in that i have tried all the usual suggestions and they have not worked - Why I else would I bother posting detailed info here?
If you some links to threads which address problem please post them.
Click to expand...
Click to collapse
So what does helping you get adb setup help android G1 Developmet?
Sent from my HTC Dream using XDA App
lolmensch said:
he offered help via irc, so you should think about accepting it.
anyway he ment that this has (almost) NOTHING to do with development and should have been posted in Q&A.
concerning your problem: i have no idea try if you can connect to fastboot.
Click to expand...
Click to collapse
fastboot uses fastboot.exe, not adb.exe. Adb works while in recovery or while booted.
Hi XDA
I am new to the Android scene but not new to hacking and moding in general. I have an Asus Transformer that I've been trying to root for over a day now with out success.
I've been following this guide since I don't want to remove the information from my tablet as I actually want to gain root to back up some applications before I continue further down the CWM and mod's path.
http://forum.xda-developers.com/showthread.php?t=1125714
I have adb setup and can access the device in apx mode, when running the batch script for root, the terminal shows that it's copying data, and I see output successful written twice on the tablet it's self, If i further continue the CWM batch script I get a 3rd successful message appear on the tablet.
I reboot the transformer and enter normal mode, and ensure debugging is actively set, and a little bumblebee icon is in the bottom status bar, I then proceed to run the root_app batch which should open up su for me.
However even though I don't receive any error messages and only successful ones, it just wont root! I've tried replacing the boot.img and recovery.img from another post on rooting, to see if this would give any success alas non was given.
I am now completely lost on what I can do next, I don't understand why this wont work for me, whilst it seems to work correctly for everyone else.
The details of the transformer as current:
Android 3.1
Kernel 2.6.36.3-00001-gf377a2b
Build hmj37.ww-epad-8.4.4.5-201105271
Dock EP101-0209
I am using windows 7 64 with drivers installed and asus sync installed.
Nvidia USB Boot-recovery driver for mobile devices
Date 31/01/2011
Version 1.1.1.0
Please can I get some direction from the XDA community on this issue since I've got over 20 tabs open in my browser looking information up and yet nothing seems to help, as stated I don't want to loose my data just yet since I really want to back up a couple of apps of importance to me, hence I am having to use this rooting method for now.
I would of posted in the above linked thread but XDA wont let me since I am a new member.
Please can someone shed some light on this for me? I am willing to rip out the boot.img from the transformer my self, and mod it given the commands and little help since I can't see what else I can do.
Bump
Can someone please move this to applicable transformer area? This thread is being viewed but not answered, and I think I need a dev to look at it
Is there anyone here who can confirm the drivers I am using for apx are ok? I did pull them from the package which is part of the guide I linked and was following.
More info
Well i've ensured that JDK and SDK are installed that all parts are updated and installed according to the adb guide, and yet still nothing...
.
Here is a sample output on the transformer after running root.bat
imageshack.us/photo/my-images/204/20110622112439.jpg
Restricting new users is actually pretty S**T i can't post in correct threads, I can't add links to images to show my outputs what a way to welcome new people!!
With regards to running the root_app.bat which gives the superuser permissions, I have debugging enabled, and I see my tablet in windows I can explore the file system and I see it listed as Transformer TF101 under portable devices.
Driver Provider Microsoft
Driver date: 21/06/2006
Driver Version 6.1.7600.16385
Could it be a problem with this driver?
Stop looking and start answering I am getting really F*** off here, I've had no sleep and i am still no further forward, 2days of hell for something that people are reporting as the fastest and easiest root ever!
What driver version do you have listed in windows when you have the tablet connected under debug mode? please at least someone help me with that answer so I can continue this dam search for a fix.
Anyone?
If you could please just confirm if your using the same drivers when having the tablet on in normal mode, and connected with debug option active.
Going to spam this now so I can link into the original guides tread.
Spam to unlock my account 1.
Spam to unlock my account 2.
Spam to unlock my account 3.
Spam to unlock my account 4. Should be unlocked so i can post in dev section.
FIXED!
Ok so i finally got pissed off with this and having a strong suspicion it was a driver level issue only I ripped all the drivers out for normal mode, with and with out debugging.
I re-installed the device and the drivers fresh from ASUS website (again) and low and behold it's working.
I believe the reason for my issue was a corrupt MTP driver, I recently did the asus sync update and that caused a number of sporadic errors! (Adobe AIR completely disappeared out my system!)
Anyway, thanks to the XDA community NOT (69 views not a single confirmation of driver version I was asking for!) I WILL help others and since I've spammed this thread enough to unlock the dev threads it's now being posted and linked there for the benefit of others!
3hours sleep 2 days of messing = pissed off but finally relived user of transformer!
Big shout to the dev's who have made the tools in the first place you're doing a great job, and I hope to assist, with guides, testing and maybe a mod or two.
Q&A for [ROM][KITKAT]BeanStalk-4.4.4065-OC2 [4.4.4](14/10/09)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Windows 8 USB Problems
Hi! I installed this rom since the cyanogenmod one had been giving me problems and huge slowdowns.
Everything seems to work amazingly, but for some reason can't get it to connect to windows 8 through USB.
It was working with the other rom, now it is detected but it just says Android, like it's not detecting which driver to use, and cannot access as external harddrive nor make it work using adb.
Any help/ideas will be deeply apreciated.
demon000 said:
Hi! I installed this rom since the cyanogenmod one had been giving me problems and huge slowdowns.
Everything seems to work amazingly, but for some reason can't get it to connect to windows 8 through USB.
It was working with the other rom, now it is detected but it just says Android, like it's not detecting which driver to use, and cannot access as external harddrive nor make it work using adb.
Any help/ideas will be deeply apreciated.
Click to expand...
Click to collapse
I wanted to answer as quickly as possible, however I am not completely firm on the answer.
I had win8 on my latest laptop for about 10 min when I bought it. I only sorta remember something it was going to be good at. Something about , after a boot, being able to walk backwards into the bios level to drop off various settings. Not unlike, telling it that there is new hardware to be expected next boot?
Please, anybody, jump in here if you want before I find a way to back this up.
Keep at it tho. It would be hard enough to get the answer you want dealing with strait Android+(all of the *.apk combos out there).
Will try.....
Try this?http://systems.engr.ucr.edu/tutorials/documents/Windows%208%20Hotkeys%20Complete.pdf
TRom's has always been great for random PC stuff http://www.tomshardware.com/reviews/windows-8-review,3334-4.html
Here's an update, I managed to make some progress (I was getting error code 28) and found this at stackoverflow:
"If the device is listed in Device Manager as Other devices -> Android but reports an error code 28:
Google USB Driver didn't work for me. You could try your corresponding OEM USB Drivers, but in my case my device is not listed there.
So, install the latest Samsung drivers: SAMSUNG USB Driver v1.5.33.0
Restart the computer (very important)
Go to Device Manager, find the Android device, and select Update Driver Software.
Select Browse my computer for driver software
Select Let me pick from a list of device drivers on my computer
Select ADB Interface from the list
Select SAMSUNG Android ADB Interface (this is a signed driver). If you get a warning, select Yes to continue.
Done!"
Now I can use adb for debugging but still can't access my device folders (Internal and External SD Cards), maybe I need to change something on my phone configuration (It is already allowing USB debugging)
I'm so ashamed now ... I didn't knew how to activate mass storage.
Thanks for the help!
@wantowan2. Love this ROM and kernel. Was wondering if you could add virtualcdrom support via a few commits please.
https://github.com/CyanogenMod/andr...mmit/979aa0d835ddca5fdbaab47bcd9aa7f7d359feb0
https://github.com/CyanogenMod/andr...mmit/1736943179733a4629e0eaa773848bdeeaeefec1
HDMI tvout issue
My HDMI tvout does not work via MHL for this ROM.
Could somebody check HDMI tvout via MHL for this ROM?
Hi there.
I got my hands on this CUBOT X6 with broken screen. I can see the screen just fine BUT can't operate it from its bottom half approximately.
I would like to use this Android phone as a security camera to watch my garage, but without control, I'm stuck
What I'm trying to achieve here is to:
a) start up the phone and load a security app to it
b) control the phone via some "Android Control"-like app (without using the phone's broken screen)
c) set it up as a security camera and let it take pictures for me
Can anyone pls point me to some links here on the forum to solve my below listed problems ? ( and YES I've spend searching and reading this and few other forums for the last few hours and found just what is listed below)
So....
1. The phone was locked with swipe password with the posibility to control only the top three dots, the other ones are dead, NO USB Debugging available, Phone was set to CHARGE ONLY mode when connected to PC via USB - I managed to download stock ROM and Flashed it but....
2. It asks for a few details and requires you to click NEXT which is in the botom of the screen which is touch-dead. So i have searched and found this tread: http://forum.xda-developers.com/show....php?t=2786395 But....
3. The phone is STOCK rom with absolutely no settings = no USB Debugging enabled and I do not know how to "modify the default.prop" http://forum.xda-developers.com/show...9&postcount=17 when the screen is dead and no usb debuging is enabled = Can't access the file system (or can I ? )
4. The phone is not detected by the Android Control app at all.
5. The recovery is in Chineese ! I tried translating it via Google Translate via pictures, but that did not shows/offers me the option for entering the command prompt (as advised in tread mentioned in point 3)
I'm too lame in this Android/Linux based sea, so if anyone is willing to help me here (if you think its possible to achive my goals a-c) please give me some step by step guide how to do that. (links to treads would be enough)
Thanks a lot !
SparrowCZ said:
Hi there.
I got my hands on this CUBOT X6 with broken screen. I can see the screen just fine BUT can't operate it from its bottom half approximately.
I would like to use this Android phone as a security camera to watch my garage, but without control, I'm stuck
What I'm trying to achieve here is to:
a) start up the phone and load a security app to it
b) control the phone via some "Android Control"-like app (without using the phone's broken screen)
c) set it up as a security camera and let it take pictures for me
Can anyone pls point me to some links here on the forum to solve my below listed problems ? ( and YES I've spend searching and reading this and few other forums for the last few hours and found just what is listed below)
So....
1. The phone was locked with swipe password with the posibility to control only the top three dots, the other ones are dead, NO USB Debugging available, Phone was set to CHARGE ONLY mode when connected to PC via USB - I managed to download stock ROM and Flashed it but....
2. It asks for a few details and requires you to click NEXT which is in the botom of the screen which is touch-dead. So i have searched and found this tread: http://forum.xda-developers.com/show....php?t=2786395 But....
3. The phone is STOCK rom with absolutely no settings = no USB Debugging enabled and I do not know how to "modify the default.prop" http://forum.xda-developers.com/show...9&postcount=17 when the screen is dead and no usb debuging is enabled = Can't access the file system (or can I ? )
4. The phone is not detected by the Android Control app at all.
5. The recovery is in Chineese ! I tried translating it via Google Translate via pictures, but that did not shows/offers me the option for entering the command prompt (as advised in tread mentioned in point 3)
I'm too lame in this Android/Linux based sea, so if anyone is willing to help me here (if you think its possible to achive my goals a-c) please give me some step by step guide how to do that. (links to treads would be enough)
Thanks a lot !
Click to expand...
Click to collapse
Hello and thank you for using XDA Assist.
We cannot provide technical support nor can other members reply to your posts here on XDA Assist and there is no forum specifically for the Cubot devices at this time but I see that you have already posted an identical message in the General Forum at http://forum.xda-developers.com/showthread.php?t=2728355 which is a reasonable place to start where members familiar with your device might be able to advise you. I also see a number of references to your model from a site search at http://forum.xda-developers.com/sitesearch.php?q=cubot x6 which might be worth reviewing. Since your device is relatively uncommon, please be patient and give the experts there plenty of time to respond.
Good luck!
This thread is closed.
The mystery: I cannot establish a USB connection between my Pixel 7 Pro (Android 13) and PC (Windows 11). When I try, the PC makes that characteristic "connected device" sound, but Windows Explorer doesn't discover the Pixel, nothing shows up anywhere in the Windows Device Manager, and the ADB command
.\fastboot device
returns nothing. The Pixel is similarly not discoverable as a bluetooth device to the PC, although it IS to other devices (like my earbuds).
This is the first task I have attempted since I performed a factory reset (and walked through the automated Pixel setup process) last night. I have spent the last three and a half hours reading Android forums, testing USB port-cable permutations, and installing and uninstalling drivers. There is no obvious solution to this problem within the first ten pages of Google search results. I would be beyond grateful for any possible insight, but please, take a moment to review what I have attempted already before you expend any effort helping me troubleshoot.
The Pixel CAN connect to an older laptop running Windows 10, appearing both in the Windows Device Manager (which says my drivers are up to date) and in File Explorer (where I can access the internal memory). But ADB similarly returns nothing on the ADB
.\fastboot devices
command. Also, my old phone (a Samsung Galaxy S20 FE 5G running Android 13) connects fine--both by USB and by bluetooth--to all three devices.
So the PC (Windows 11) connects to the Galaxy and the laptop (Windows 10) connects to the Pixel (kinda), which fairly well eliminates the possibility of an issue related to my hardware or USB cables. But the PC (Windows 11) won't connect to the Pixel--not anymore. Everything worked just fine when I unlocked the Pixel's bootloader a few weeks ago.
What I need now is to recover the functionality of the USB and bluetooth connectivities between the Pixel and the PC running Windows 11, especially for file transfers. For several reasons, WiFi reliant solutions are untenable for my situation. I also need to re-lock the bootloader by any method (not necessarily with the PC). As mentioned above, ADB has not succeeded in finding the device on either platform.
Finally, in case it's relevant: when I open the Pixel's USB Preferences menu, I cannot switch from "USB controlled by...This device" to "USB controlled by...Connected device"--in both cases, the Pixel returns a "couldn't switch" dialogue. And yes, I have of course enabled USB debugging.
If you took the time to comb through all those particulars, Thank you. I'm getting desperate for some thoughtful expertise, and while I'm open to retrying anything for the fifth or sixth time, (maybe I somehow missed the magic driver package), it is a special kind of tribulation to review the same tired list of perfunctory solutions to a different problem. I promise, the solution I need isn't one of the usual suspects.
I spent $800 on this device. That's a lot of money for me. It feels absurd and unfair that such a basic functionality--one that far more affordable devices have been delivering reliability for decades--should be missing from the Pixel 7 Pro. Please please please help me!
Ummm, USB debugging is not only what is needed here. While you are in developer settings scroll down to "Default USB configuration" and tap on it directly. Then you will see a number of choices. I think the top one titled "File transfer / Android Auto" is the one you need. Or maybe try PTP???
Let us know if this helps.
jaseman said:
Ummm, USB debugging is not only what is needed here. While you are in developer settings scroll down to "Default USB configuration" and tap on it directly. Then you will see a number of choices. I think the top one titled "File transfer / Android Auto" is the one you need. Or maybe try PTP???
Let us know if this helps.
Click to expand...
Click to collapse
Thanks for your speedy reply! I had File transfer / android Auto selected, but then switching to P2P allowed me to review the internal storage! I can't believe it. However I still need to figure a way to get ADB to find the device so I can lock the bootloader, and i still can't figure out how to solve the Bluetooth connectivity..
GodieDan said:
Thanks for your speedy reply! I had File transfer / android Auto selected, but then switching to P2P allowed me to review the internal storage! I can't believe it. However I still need to figure a way to get ADB to find the device so I can lock the bootloader, and i still can't figure out how to solve the Bluetooth connectivity..
Click to expand...
Click to collapse
Have you tried putting in Fastboot mode and then connect to computer?
schmeggy929 said:
Have you tried putting in Fastboot mode and then connect to computer?
Click to expand...
Click to collapse
Putting what in fastboot mode?
GodieDan said:
Putting what in fastboot mode?
Click to expand...
Click to collapse
Your phone in Fastboot Mode aka bootloader Mode.
Uninstall any previous android USB driver you have installed, and install the official Google USB driver instead. You need to install it two times probably. First in Android mode and second in bootloader mode, after all that it should show up correctly. If not, check your cable and PC USB port
If possible, give a lsusb output on your PC, see if the phone's there or not
yurishouse said:
Uninstall any previous android USB driver you have installed, and install the official Google USB driver instead. You need to install it two times probably. First in Android mode and second in bootloader mode, after all that it should show up correctly. If not, check your cable and PC USB port
If possible, give a lsusb output on your PC, see if the phone's there or not
Click to expand...
Click to collapse
I'm sorry, i don't understand what you mean when you say install it in android mode or bootloader mode?
Yeah, you probably just need to install the official USB driver from Google. That was a problem that numerous people had when the Pixel 7 series first released.
GodieDan said:
I'm sorry, i don't understand what you mean when you say install it in android mode or bootloader mode?
Click to expand...
Click to collapse
So you trying to unlock the Bootloader and you don't even know what Bootloader mode or Fastboot is? Maybe you should do some reading first. What do you mean by absurd that the Pixel doesn't have basic functionality? You said you have no problem with a Windows 10 computer, Windows 11 is the problem not the phone. Again I would do some reading on XDA, especially the guides on unlocking and rooting, because you don't seem to have a clue on what you are doing.
schmeggy929 said:
So you trying to unlock the Bootloader and you don't even know what Bootloader mode or Fastboot is? Maybe you should do some reading first. What do you mean by absurd that the Pixel doesn't have basic functionality? You said you have no problem with a Windows 10 computer, Windows 11 is the problem not the phone. Again I would do some reading on XDA, especially the guides on unlocking and rooting, because you don't seem to have a clue on what you are doing.
Click to expand...
Click to collapse
If you look at his second post (#3 of this thread) he says he wants to "lock" his bootloader not unlock it. Unless of course it was a typo. Maybe we should point him to the thread, Help I've bricked my device now what do I do".
yeah...the "absurdity" doesn't fall on the Google Pixel in this case, but with Microsoft Windows...
So, the first thing you need to do is see what is the device being identified as in Device Manager -- it easily could be "Unknown Device" or even identified as something totally different & wrong (Samsung android device, MTP device, etc.). Regardless, it NEEDS to be identified as Android Composite ADB Interface (and Android Bootloader Interface when in Bootloader Mode). When this was happening to many members in the main rooting thread on this forum, it was determined that you can't simply just "Uninstall" it, but you also need to "delete device driver" as well (if option is available)! Most users are able to simply install the driver and sometimes just have to point it to the Google USB Windows Driver folder (that I hope you followed the suggestions of the other members in this thread and got it proper from the source from Google's developer's website), but I suggest going beyond it and pointing the device driver (Update, Browse My computer for drivers, Let me pick from a list, have disk, and choose the .inf file) to the exact .inf file.
Also, since it seems you aren't too experienced in all this, I really do suggest you use the official Google Android Flash Tool to re-lock your bootloader! There are countless members from the past 7 years that have HARD BRICKED their device because they have done things wrong -- the Android Flash Tool will do everything automatedly in the correct fashion as to not hard brick your device when re-locking the bootloader.
But you absolutely need to get your usb drivers correct in order for the tool to work...
schmeggy929 said:
So you trying to unlock the Bootloader and you don't even know what Bootloader mode or Fastboot is? Maybe you should do some reading first. What do you mean by absurd that the Pixel doesn't have basic functionality? You said you have no problem with a Windows 10 computer, Windows 11 is the problem not the phone. Again I would do some reading on XDA, especially the guides on unlocking and rooting, because you don't seem to have a clue on what you are doing.
Click to expand...
Click to collapse
We'll I'm certainly not above learning new vocabulary but but in this case I don't think the issue is having read too little. Do you mean recovery mode? So far there is no custom recovery available for the Pixel 7 Pro, but yes I did try with the phone in the stock recovery
I have read every relevant article on XDA and three other forums and nothing has helped so far. I promise you I would not have posted if I could find the solution elsewhere.
Also the phone doesn't work fine on the windows 10 system. I was able to view my files but I couldn't read, write or execute ADB commands. I do consider USB file transfer to be a basic functionality, and windows 11 is backwards compatible with every storage device since punch cards.
Anyways I'm no pro, but I have had success with rooted devices in the past. For my benefit it would be helpful to be assiduous with language choice.
.
H
bobby janow said:
If you look at his second post (#3 of this thread) he says he wants to "lock" his bootloader not unlock it. Unless of course it was a typo. Maybe we should point him to the thread, Help I've bricked my device now what do I do".
Click to expand...
Click to collapse
I there, yes, my objectitve was to lock the bootloader, not unlock it. However I got that part figured out at least, by getting the phone replaced (i had fortunately splurged on the extra protection). But also I never bricked my device, and as best I can tell, the issue at hand isn't related to the rooting, or everything would be working again with the new phone. I wanted to re-lock the bootloader because everything was just getting to be so unstable. This was never a problem on my Nexus 6p, but that was two devices ago. Also, is it just me, or are there generally fewer benefits to rooting than there were in the teenies?
Hi there
simplepinoi177 said:
yeah...the "absurdity" doesn't fall on the Google Pixel in this case, but with Microsoft Windows...
So, the first thing you need to do is see what is the device being identified as in Device Manager -- it easily could be "Unknown Device" or even identified as something totally different & wrong (Samsung android device, MTP device, etc.). Regardless, it NEEDS to be identified as Android Composite ADB Interface (and Android Bootloader Interface when in Bootloader Mode). When this was happening to many members in the main rooting thread on this forum, it was determined that you can't simply just "Uninstall" it, but you also need to "delete device driver" as well (if option is available)! Most users are able to simply install the driver and sometimes just have to point it to the Google USB Windows Driver folder (that I hope you followed the suggestions of the other members in this thread and got it proper from the source from Google's developer's website), but I suggest going beyond it and pointing the device driver (Update, Browse My computer for drivers, Let me pick from a list, have disk, and choose the .inf file) to the exact .inf file.
Also, since it seems you aren't too experienced in all this, I really do suggest you use the official Google Android Flash Tool to re-lock your bootloader! There are countless members from the past 7 years that have HARD BRICKED their device because they have done things wrong -- the Android Flash Tool will do everything automatedly in the correct fashion as to not hard brick your device when re-locking the bootloader.
But you absolutely need to get your usb drivers correct in order for the tool to work...
Click to expand...
Click to collapse
Howdy, thanks for this. I just wrote a long reply but I can't seem to find it now, so I'll go ahead and give you the upshot again.
In my device manager, i have located a driver called "Android ADB Interface" under the grouping of "LeMobile Android Device" (by itself), and sure enough, it has a yellow-triangle warning icon. Before I take any action, i want to be clear -- your advice is that I uninstall the driver AND delete it manually? The context menu gives me the option to update the driver (when I search automatically, windows tells me the best drivers are already installed), disable device and uninstall device. Do you suggest I choose uninstall and then download the correct driver? If so, please would you provide me with the right link? I know from recent experience that there are a lot of drivers out there which look pretty good, and obviously none of them have worked doe me
GodieDan said:
Hi there
Howdy, thanks for this. I just wrote a long reply but I can't seem to find it now, so I'll go ahead and give you the upshot again.
In my device manager, i have located a driver called "Android ADB Interface" under the grouping of "LeMobile Android Device" (by itself), and sure enough, it has a yellow-triangle warning icon. Before I take any action, i want to be clear -- your advice is that I uninstall the driver AND delete it manually? The context menu gives me the option to update the driver (when I search automatically, windows tells me the best drivers are already installed), disable device and uninstall device. Do you suggest I choose uninstall and then download the correct driver? If so, please would you provide me with the right link? I know from recent experience that there are a lot of drivers out there which look pretty good, and obviously none of them have worked doe me
Click to expand...
Click to collapse
It might help to show what it states in the "Device status" in Properties.
But, regardless of what it says, YES uninstall the driver AND delete it manually. Windows automatically searching is usually wrong more often than not in my experience -- but especially in the case of special hardware connected to the computer.
Again, when reconnecting the device and after it installs the (most likely wrong) driver, please heed what I stated before:
simplepinoi177 said:
...Most users are able to simply install the driver and sometimes just have to point it to the Google USB Windows Driver folder (that I hope you followed the suggestions of the other members in this thread and got it proper from the source from Google's developer's website), but I suggest going beyond it and pointing the device driver (Update, Browse My computer for drivers, Let me pick from a list, have disk, and choose the .inf file) to the exact .inf file.
Also, since it seems you aren't too experienced in all this, I really do suggest you use the official Google Android Flash Tool to re-lock your bootloader! There are countless members from the past 7 years that have HARD BRICKED their device because they have done things wrong -- the Android Flash Tool will do everything automatedly in the correct fashion as to not hard brick your device when re-locking the bootloader.
But you absolutely need to get your usb drivers correct in order for the tool to work...
Click to expand...
Click to collapse
You are correct that there are multiple sources for the drivers and adb/fastboot -- ultimately the best place to get them is direct from Google's android developers website. For Windows USB drivers; here is the link from this website: https://developer.android.com/studio/run/win-usb
Just extract the .zip to a folder, and refer to that folder when doing the aforementioned steps I laid out (in orange)...
hope this helps...!
simplepinoi177 said:
It might help to show what it states in the "Device status" in Properties.
But, regardless of what it says, YES uninstall the driver AND delete it manually. Windows automatically searching is usually wrong more often than not in my experience -- but especially in the case of special hardware connected to the computer.
Again, when reconnecting the device and after it installs the (most likely wrong) driver, please heed what I stated before:
You are correct that there are multiple sources for the drivers and adb/fastboot -- ultimately the best place to get them is direct from Google's android developers website. For Windows USB drivers; here is the link from this website: https://developer.android.com/studio/run/win-usb
Just extract the .zip to a folder, and refer to that folder when doing the aforementioned steps I laid out (in orange)...
hope this helps...!
Click to expand...
Click to collapse
Wow, thank you for the speedy reply!
1. Having splurged on the protection plan, yesterday i went to best buy and replaced my device, and I'm no longer interested in messing with the bootloader. So where ADB is concerned, I don't need it. What i DO need is the functionality of making file transfers between my PC and my phone. Do you still suggest I look for the ADB driver on the developer website, or is there something more basic (and hopefully reliable)?
2. The device status reads:
"
The device cannot start. (Code 10)
The specified request is not a valid operation for the target device.
"
I spent a few minutes googling around about those errors, no luck yet.
3. It would be straightforward to uninstall (or disable) the device, but when I do, I worry it will be difficult to locate where the drivers are hiding (to delete manually). Under the "Driver" tab I clicked "Driver Details" and found the directories for three files, winusb.sys and two .dll files. Are these the culprits? Might there be others anywhere?