Database Users

Run Android on your PC or Laptop..for real.

Want to run Android on your PC or Laptop?
This is pretty cool, did it this morning.
If you have troubles with getting your internet to work in it, what I did was put my EVO in USB tethering mode,plugged it into my PC..then booted the PC and it worked great.
1. Download Android from here..android-x86-1.6-r2.iso
2. Download UNetBootin
Now you have a few choices... either just burn the ISO to a cd (and boot your computer off it) or use unetbootin to make a usb thumb drive bootable with the ISO image on it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here are some better more detailed instructions.....
http://www.youtube.com/watch?v=Wrena1bNl18 -- cheesy video of it on my pc.

ok so this looks bad a** but like is it a dual boot? or is it if you dont have the memory card you cant run it? im running ubuntu and think this would be pretty sweet if you have the UI of this but still have the functioning of ubuntu

bubba1114 said:
ok so this looks bad a** but like is it a dual boot? or is it if you dont have the memory card you cant run it? im running ubuntu and think this would be pretty sweet if you have the UI of this but still have the functioning of ubuntu
Click to expand...
Click to collapse
I just booted up off a thumb drive so it doesn't effect your current os... you could also burn the ISO on to a cd and bootup off the CD...
You don't actually install this on your hard drive or anything. You could, but it'd be kinda pointless.

Would be very cool to run on a Netbook, see how android translates as a Netbook OS.

how about froyo2.2??

I tried it on my laptop Dell E4200 but I cannot run it. I tried all LIVE modes but nothing happened.

mine gets stuck on detecting android x86. I even tried burning the disk and got stuck in the same place. I really want to try this.

This is sick!! Can anyone think of any possible way to install apk files???? Can I add Google Apps somehow??

You can boot from Virtual PC too
Hi, i have successfully booted from Windows Virtual PC software..
You need to :
1. Download Windows Virtual PC
2. Go Bios to enable CPU virtualization technology(newer pc would have this function)
3. install the Windows Virtual PC software
4. Create a virtual disk
5. Give it any name
6. Go to Settings for that Virtual Disk
7. Search for dvd drive and point it to the android iso
8. Boot up the Virtual Drive you have created
9. select the third option, debug, and follow the instruction there, you should type exit twice to boot into android
10. Wella you have reached android
10a. Make sure you got a ethernet connection on your pc
10b. Try either ethernet port 1 or 2 to get connected to the internet by editing in the android ethernet settings.
Hope this helps

matthenry87 said:
This is sick!! Can anyone think of any possible way to install apk files???? Can I add Google Apps somehow??
Click to expand...
Click to collapse
I would assume that the OS uses the flash drive as a filesystem- so put the APKs on the flash drive, download a file manager from the web and install using the file manager.
Also I can't get this to work in VirtualBox, it says the ISO file is invalid.

I read about this months ago but never did give it a go. I can only imagine how awesome this would be to run on a computer that has a touchscreen monitor.
That said... once windows releases a few of their tablets and we have the option to boot into android.............. AWESOME!!!

This is confusing...no matter how I try to start it, it always comes to a black screen with an underscore that blinks every couple of seconds

This came out just in time.....not even 3 days ago I was looking at live android, which has been discontinued as it seems

Mac OSX
I got a Macbook Pro and I wanted to try, so I used Parrells desktop and mounted the ISO as as a Windows 7 (unsure if that was right) but it seemed to work just fine
Check it out!
Android on OSX -

Got it running on my Acer Aspire one, wifi works and I can connect to the internet! this is awesome!

Wow, I can run it under VirtualBox on Fedora 13... nice. Unfortunetaly I do not have touch screen so handling is a little bit tricky.

i got it running in virtualbox. just set up a virtual system and use ubuntu linux as the virtual system to be created and use the defaults to create the system

I got it running on an HP DV6 laptop coppied it to a usb drive booted up and it works fine and the internet, nice work thanks for this

it runs great under vmware workstation 7. even internet works I just wished the real market was pre-installed. im pretty sure someone will get froyo into a iso now that this version is getting attention

will the touchscreen be usable if you install android on a Tablet or UMPC?
I'm getting a Sony Vaio UX this week and that would be a realy cool android device!!

Mango USB Tethering - Confirmed Working

While this version of mango might not have the ICS, I just confirmed that the following method works to get USB tethering with Mango.
The following works for Windows 7 x64 (Using either the HTC Drivers or the Qualcomm drivers). All my machines are x64 so I am not sure if this works for x86 systems.
Tether:
Download the HTC Drivers from the bottom of this post[/url]
Or try the Qualcomm drivers attached to this thread if those don't work.
Extract the zip
The XAP dosent work with the DVP so ignore it for now.
Open the phone dialer.
Dial ##634# (Engineering Mode)
If you do not see a wine glass when booting, you need to remove the old EM app and then dial
Slide open your keyboard
Tap the black area of your screen
Press QWERTYUIOP
Scroll down to service center
Click on Composite
Type in *#301#
Wait for your phone to reboot
Install the drivers for the phone with the files in the zip. You do not need to edit these INF files.
Note that you have to right click the unknown device, update drivers, browser, let me pick, all, I have disc, and then browse to where you extracted your drivers
In the device manager (you should be there already) right click on the first HTC USB modem and go to properties
Then go to advanced and enter +CGDCONT=1,"IP","EPN.TMOBILE.COM" into the Extra initialization commands box (Note that these settings are for t-mobile. If you do not use t-mobile please download and find your connection info at http://forum.xda-developers.com/showthread.php?p=21421101. Replace epn.tmobile.com with your carriers connection info.
Click ok
In your task tray, right click on the network icon and go to network and sharing center
click on Set up a new connection or network
Setup dial-up
HTC USB Modem (Or Qualcomm Usb Modem)
In the phone number field type *99#
Click connect
Have fun
Untether
If you want to untether, follow steps 6-11 and click on Zune to bring your phone back into normal operating mode
Notes
You will notice that there are 4 drivers. Two of them are USB (should be the first two) and the other two should be the diagnostic drivers (COM Ports). The diagnostic drivers currently do nothings so you really dont need to install them.
If you are installing the Qualcomm drivers, make sure you select the Qualcomm HS-USB Modem 9202 and not the Qualcomm HS-USB Ethernet Adapter 9202 driver
Thank me if this works for you

thanks for this, trying right now. At step #13 when you enter in the Composite Mode password, I see no OK button or any way to apply the password. Slide out keyboard Enter button does nothing. How is this done so that the reboot will happen?

Woops it is *#301#

thanks. I'm running Win7 32bit and the extracted drivers don't work for steps 15 and 16. Also, when in Composite Mode there are 4 "unknown device" listings in Device Manager. I tried updating the driver for each of these with the USBModeSwitch x86 driver and it didn't work.
any ideas?

bbowman said:
thanks. I'm running Win7 32bit and the extracted drivers don't work for steps 15 and 16. Also, when in Composite Mode there are 4 "unknown device" listings in Device Manager. I tried updating the driver for each of these with the USBModeSwitch x86 driver and it didn't work.
any ideas?
Click to expand...
Click to collapse
Not sure. Yes there are 4 devices: 2 serial devices and 2 modems.
Try to see if the x86 drivers were modified correctly.
Or check out this:
Standa99 said:
WinXP 32-bit drivers: test&work.
Click to expand...
Click to collapse

Thanks.
Works perfectly.

palmbluetooth said:
Thanks.
Works perfectly.
Click to expand...
Click to collapse
are you running a 64 or 32bit OS? Still unable to get mine to work on my Win7 32bit laptop.

bbowman said:
are you running a 64 or 32bit OS? Still unable to get mine to work on my Win7 32bit laptop.
Click to expand...
Click to collapse
Works perfectly for me on Windows 7 Ultimate x64, I had to add the modem to all the unidentified drivers and then setup a connection on each one to see which one was the right one to use. If you are only setting up the connection on one of the drivers then you may be picking the wrong one.

I've tried all of them. has anyone gotten this to work on a 32bit system?

bbowman said:
I've tried all of them. has anyone gotten this to work on a 32bit system?
Click to expand...
Click to collapse
I will try this on my dad's x86 windows laptop tonight.

bbowman said:
I've tried all of them. has anyone gotten this to work on a 32bit system?
Click to expand...
Click to collapse
I've tryed, but it failed to work here on a Vista 32bit...

I just added Qualcomm drivers I found online. They work the same but I thought it would be better than the HTC Drivers everyone else is using. I did upload some x86 Drivers I found. They should work but I have no way to test.
Let me know if you have any questions.

Now that tethering is working well. I wonder if internet sharing will ever be available for our phone.

Kloc said:
Now that tethering is working well. I wonder if internet sharing will ever be available for our phone.
Click to expand...
Click to collapse
rubbing salt on that wound eh
=( you know it won't

the Qualcomm drivers worked like a champ on my Win7 32bit system. hooray for Mango tethering! thanks dude!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

bbowman said:
the Qualcomm drivers worked like a champ on my Win7 32bit system. hooray for Mango tethering! thanks dude!
View attachment 748755
Click to expand...
Click to collapse
You are welcome!

Hi Guys,
just wondering if anyone on Vodafone UK has managed to get this working yet?
Best wishes from a wet and windy North Yorkshire,
DaFfY

If you have a chance to read the service manual posted by Negrbob, you will found: WIFI chip: integrated Broadcom solution of BCM4329 WiFi/Bluetooth/FM SoC
Hey, this is important for WIFI tethering. Since the manual is created on 2011/03/04, is that mean phone manufactured after that date should have BCM4329?

I am on Windows 7 x64 Ultimate, and can't get this to work. Have tried both the drivers without any success. I have received two different errors: 692 and 651. I am not sure about the second error number, however, it was some cryptic hardware-related message when dialing the number.
Any help is appreciated.

Errors when you dial *99#? My instructions were for T-Mobile btw. You carrier might varry.

kies don't recognizing my device (Galaxy S3)

kies don't recognizing my device (Galaxy S3) & I never face problems by installing kies 2.5 on my laptop which runing with windows xp service pack 3 , by connecting my phone with kies it just freezes on connecting window also in device manager showing exclamation mark on samsung mobile MTP device
see the images :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I also tried this [SOLUTION] Samsung Mobile MTP Device -- CODE 10 error at Devicemanager but this solution was on win7 can any help me to do any thing more to solve it on win xp sp3

Is your phone rooted?
Sent from my GT-I9300 using xda premium

UrbanDrawer said:
Is your phone rooted?
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
no brother not rooted

With the phone disconnected from the PC run Control Panel/Add Remove Programs uninstall SAMSUNG USB Driver for Mobile Phones and reboot.
Then from C:\Program Files\Samsung\Kies\USB Driver
install SAMSUNG_USB_Driver_for_Mobile_Phones.exe
If that does not help, from regedit remove
HKEY_CURRENT_USER\Software\Samsung\Kies\DeviceDB
then from explorer delete %USERPROFILE%\AppData\Roaming\Samsung

Odia said:
With the phone disconnected from the PC run Control Panel/Add Remove Programs uninstall SAMSUNG USB Driver for Mobile Phones and reboot.
Then from C:\Program Files\Samsung\Kies\USB Driver
install SAMSUNG_USB_Driver_for_Mobile_Phones.exe
If that does not help, from regedit remove
HKEY_CURRENT_USER\Software\Samsung\Kies\DeviceDB
then from explorer delete %USERPROFILE%\AppData\Roaming\Samsung
Click to expand...
Click to collapse
Iam not founding (DeviceDB) see this

aliasss said:
Iam not founding (DeviceDB)
Click to expand...
Click to collapse
Thats ok, it just means your phone has never been connected sucessful, continue with the other commands.

Odia said:
Thats ok, it just means your phone has never been connected sucessful, continue with the other commands.
Click to expand...
Click to collapse
after deleting %USERPROFILE%\AppData\Roaming\Samsung & reinstalling samsung usb drivers nothing more happend after connecting my device problem of samsung mobile MTP device still exist what to do now

Odia said:
then from explorer delete %USERPROFILE%\AppData\Roaming\Samsung
Click to expand...
Click to collapse
just to your information because iam using windows xp service pack 3 so that link will appear like this :
C:\Documents and Settings\All Users\Application Data\Samsung
& according of your commands I DELETE this folder without any advantage & I still looking for U further

Have you tried to delete the SAMSUNG Mobile MTP Device from Device Manager and re-add it?
or try another USB port, you could also try clean the micro USB port on the phone.

Odia said:
Have you tried to delete the SAMSUNG Mobile MTP Device from Device Manager and re-add it?
or try another USB port, you could also try clean the micro USB port on the phone.
Click to expand...
Click to collapse
yes i does every thing & by the way this problem exist with alot of people R U seen this :
[SOLUTION] Samsung Mobile MTP Device -- CODE 10 error at Devicemanager
but this solution applied on win7 also I tried it on my windows version but I don't found keys with that name .....

aliasss said:
yes i does every thing & by the way this problem exist with alot of people R U seen this :
[SOLUTION] Samsung Mobile MTP Device -- CODE 10 error at Devicemanager
but this solution applied on win7 also I tried it on my windows version but I don't found keys with that name .....
Click to expand...
Click to collapse
Install latest Microsoft Media Player for Windows XP.

Odia said:
Install latest Microsoft Media Player for Windows XP.
Click to expand...
Click to collapse
any link please !

aliasss said:
any link please !
Click to expand...
Click to collapse
www.google.com

I'm experiencing the same (sort of) issue: When I connect my S3 to my PC using an USB cable it shows up as a I9300 phone in Windows Explorer (see attached Explorer.jpg). I can access both the Phone memory (internal SD card) as well as the external SD card. All relevant drivers have been installed correctly (no red crosses).
However, when I start Kies it tries to connect to the S3. It recognizes the phone (see attached Kies.jpg), but keeps stuck in "Connecting...". Starting "Solve connection problems" from Kies results in re-installation of the drivers which, again, runs correctly. But still, the issue remains.

Odia said:
Install latest Microsoft Media Player for Windows XP.
Click to expand...
Click to collapse
by installing kies 1st time it required install (wmfdist11) & I installed it this one i thought was for media player what you say !?

ADB driver connection

Has anyone been able to get the Turbo 2 to connect via ADB? I have debugging selected and the drivers says installed correctly for Android ADB interface in the Windows device properties. Yet Helium doesn't connect and adb devices command returns nothing.
Anyone been able to get adb interface running on Turbo 2?

rayjr13 said:
Has anyone been able to get the Turbo 2 to connect via ADB? I have debugging selected and the drivers says installed correctly for Android ADB interface in the Windows device properties. Yet Helium doesn't connect and adb devices command returns nothing.
Anyone been able to get adb interface running on Turbo 2?
Click to expand...
Click to collapse
Yes but I know if you update to Windows 10 it can cause issues you need to reinstall moto drivers
Sent from my XT1585 using XDA Premium 4 mobile app

My Turbo 1 connect just fine not T2 I'll try it again when the wife brings it back

I had a small issue. I think mine cleared up when I installed Vysor, and installed the drivers through that.
http://koush.com/post/universal-adb-driver
Give this a shot and let me know how it goes. btw, Vysor is pretty fun.

Solution update (2017-2018 version) for recent Ubuntu-based Linux and Windows 10
(NOTE: I am unable to post complete URLs due to having an insufficient number of XDA Forum posts at this time. The bulk of this post and the information contained within is available by searching for my GitHub account (maxieds) and selecting the most obvious pinned repo description. My GitHub page is also linked off of my XDA Forum profile just to be clear. )
Preface: I realize that this thread is somewhat dated, but so is this antique 2015-era phone, so I figured it's worth pointing out a recent solution to those patient Google searchers who like me are still using the device. This solution (works for me on a recent 2017 Debian-derivative Linux box, and/or a loaner Windows 10 laptop) is to avoid the proprietary Motorola software and drivers you will stumble onto from the official ADB links from Android Studio. All you need is the standard Google USB drivers and a more recent list of phone USB device ID properties. I haven't tested, and so cannot confirm, but I suspect that this method should get ADB up and functioning on other hard-to-configure deviant phones using the list of Linux udev supported configurations from this recent (and often updated): <GITHUB>/M0Rf30/android-udev-rules. My modification for the DROID TURBO 2 phone is forked <GITHUB>/maxieds/android-udev-rules. If you find this information helpful, I'd appreciate it if you would STAR my repo on GitHub (<GITHUB>/maxieds/android-udev-rules/stargazers). As a variant of the the old Unix joke goes in obscure 20-year-old Slashdot references: How do we fix Windows? ... Well, I propose we port WINE to Windows ... With this in mind and in this spirit, let's port the oh-so-wonderful Linux UDEV config to Windows.
NOTE: the DROID TURBO 2 didn't work out-of-the-box on Ubuntu either however, even after installing other variants of the udev rule sets, so my mod is necessary to fix at least this stubborn class of Motorola devices. One possible explanation for why this device doesn't work like nearly every other Android phone is a USB3 bug where file explorer, etc. works on the same USB port, but ADB fails. The purported non-software work around is to chain the phone's USB connection in serial to a cheap self-powered USB hub that effectively masks this bug, but I had no such luck with this experimental fix and of course your mileage may vary. More likely, the cause is that the phone preempts the typical detection sequence by changing the id of it's ATTR{idProduct}=="2ea4" to ATTR{idProduct}=="2ea5" (or some other related ID) when it is connected through USB debugging for use with ADB. See the following image detailing the respective dmesg and lsusb changes pre/post enabling USB debugging on a device connected via USB in Linux:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
===== Ok, so here, goes with the updated device details: =====
Recent (2017,2018) Solution for Using the DROID TURBO 2 Phone with ADB:
Recently, I finally got into Android development using my Motorola DROID TURBO 2 phone ... only to find that the phone isn't recognized out-of-the-box on either Linux or Windows. After searching around for a while, I finally have found a solution on Linux, which I then "ported" to Windows 10 using the stock Google USB drivers which are easy to find and install with Android studio. The solution is essentially this:
on Linux (after installing Android Studio / ADB / Android Tools in Ubuntu):
Use this updated udev file to get the TURBO 2 recognized: <GITHUB>/maxieds/android-udev-rules. The working forked file basically required setting a few non-standard udev options and inputting the complete device spec found with
Code:
lsusb
LSUSB Outputs: Bus 001 Device 0XX: ID 22b8:2ea5 Motorola PCS, where the XX is a decimal integer local to the running linux box
Click to expand...
Click to collapse
. After following the instructions at the referenced link, running
Code:
adb devices
from your favorite terminal should display the device. Now happy ADB and Android debugging to you and your ancient phone! (AND please be sure to STAR my repos!)​
in Windows 10 (Enterprise): First, install the Google USB Driver using the SDK manager in Android Studio (under Extras). This puts the driver files in (on my local text box) "Program Files (x86)\Android\android-sdk\extras\google\usb_driver\*". I had to right-click, install and enter the administrator password for the local box to install this. At this point, you can open up "Computer Management > Device Manager" (as ROOT) and see if your phone is automatically recognized by the stock Google USB driver. Mine is not, so we have more work to do. From the GitHub repo (<GITHUB>/maxieds/AndroidADBExtraUSBConfig) I have created, copy the two files under android_google_usb_driver_mod into the default folder for the Google USB Driver files (linked on Windows 10 as above). Repeat the process to install the driver.
Hopefully, now you can get the Motorola DROID TURBO 2 device up and developing with ADB and Android Studio! :good:
---------- Post added at 09:40 AM ---------- Previous post was at 09:32 AM ----------
Since I was unable to post the links to the GitHub repos relevant to the recent solution to this problem, maybe this will get past the XDA Forum filters. Here's a QR-Code to the Wiki page on my repo where you can find complete information and files for implementing the custom USB setup needed to get the DROID TURBO 2 phone working out-of-the-box with ADB under Android Studio: <img src='https://chart.googleapis.com/chart?cht=qr&chl=https%3A%2F%2Fgithub.com%2Fmaxieds%2FAndroidADBExtraUSBConfig%2Fwiki%2FFirstBootConfigurations&chs=180x180&choe=UTF-8&chld=L|2' alt=''>. A link to the original image file (which should have been displayed in the above post) using the repo site is also provided as follows: <img src="https://github.com/maxieds/AndroidADBExtraUSBConfig/blob/master/images/idproduct-discrepancy-illustrated.png" alt="" />.

[Guide] Fix for device not working in fastboot / unable to install official driver in Windows 10 / 11

If you are getting the error as in the screenshot below, this solution is for you.
1. Download the attachment "Generic Driver.zip" and extract it
2. Click on "Update Driver" in the dialog in the screenshot.
3. Browse my computer for drivers
4. Let me pick from the list of available drivers
5. Show all devices
6. Have Disk
7. Point it to the extracted folder and click OK.
8. You will see 3 new items in the box now Choose "Android bootloader interface" in the list and click next
9. It will show you a warning. Ignore it and press Yes
That's all! Enjoy
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Oneplus USB drivers were not enough on my win11 pc but your method worked, thanks very much

Hi,
I am facing the same issue, after updating to windows 11 my one plus 7T driver stopped working...i tried all the possible solutions I the forums, from updating driver of Generic driver, Qualcomm drivers, and USB driver...nothing has worked...in fact I saw many members posting to update the android driver in device manager in the other devices tab which solves the issue...many have an android option but on my device there isn't any android option..i don't know what to do..I'm very frustrated and tensed as to what needs to be done...please if any on can help me personally it wud be really great.

anuahmed89 said:
Hi,
I am facing the same issue, after updating to windows 11 my one plus 7T driver stopped working...i tried all the possible solutions I the forums, from updating driver of Generic driver, Qualcomm drivers, and USB driver...nothing has worked...in fact I saw many members posting to update the android driver in device manager in the other devices tab which solves the issue...many have an android option but on my device there isn't any android option..i don't know what to do..I'm very frustrated and tensed as to what needs to be done...please if any on can help me personally it wud be really great.
Click to expand...
Click to collapse
[Guide] Fix Device Not Showing Up In Fastboot Mode (Windows 10/11)
You sir are saint...I've been trying to get fastboot to recognize my OP6T for the last 8 hours. Thank you so much!
forum.xda-developers.com

in my case, the other devices it doesnt show when i connect it with usb and it also doesnt show USB CONNECTED notification on my status bar? it would be really helpful if someone can help with the fix, Thankks and Appreciated.

I just went through the same exercise. However, I did not want to download drivers from unknown source (or even worse - run some *magical* driver fixing executable), right?
I am using Samsung Galaxy Tab A7 Lite and the ADB drivers came from Samsung and adb was working.
However, once I put the tablet in fastboot mode the USB re-enumerated and Samsung drivers didn't cut it!
Inspecting DeviceManager gave me the USB\VID_18D1&PID_4EE0 and Google search shows this is actually a Google VID. The rest is history: Downloaded (signed!) driver from Google (specifically this) and voila - life is good!
I hope this may help others avoiding wizardry with unsigned drivers.

I didn't think I'd get to ask something like this but here I am:
I can't get the phone to be detected while it is bootloader mode to my PC. I always updated and rooted my phone without any issue but with f.15 I can't.
All drivers are fine because I've rooted f.13 like one month ago so i really don't know what to do.
I remember once I had to install "Android Bootloader Interface" but now when I'm in bootloader mode my PC doesn't see the phone. No "unknown android" under window devices manager, nothing.
When the phone is ON I see "ADB Interface" in devices manager, when it's OFF nothing shows up in the list like the PC doesn't see I've plugged my phone.
What am I missing?
Thx in advance

Dieppy said:
I didn't think I'd get to ask something like this but here I am:
I can't get the phone to be detected while it is bootloader mode to my PC. I always updated and rooted my phone without any issue but with f.15 I can't.
All drivers are fine because I've rooted f.13 like one month ago so i really don't know what to do.
I remember once I had to install "Android Bootloader Interface" but now when I'm in bootloader mode my PC doesn't see the phone. No "unknown android" under window devices manager, nothing.
When the phone is ON I see "ADB Interface" in devices manager, when it's OFF nothing shows up in the list like the PC doesn't see I've plugged my phone.
What am I missing?
Thx in advance
Click to expand...
Click to collapse
Not sure if this will help but I would run "usbview" to see what is enumerated. Since the tree is very bid these days with many hubs and USB devices already connected you might first plug-in anything known to the same USB port to see where on the tree it sits. Then plug-in the phone and look at the same spot ("bark at the same tree" ;-) )
If you nave a NIX system "lsusb" will do you similar service. Both are driver independent. Then (if the phone is recognized) get the VID and PID and google what got enumerated and you may end-up with the right driver.
In the case nothing is detected at this low level the only explanation I would have is that the boot doesn't initialize the USB interface on the phone. That would be weird and nasty.

Hey
While trying to install drivers using have disk I encounter a problem. After navigating to the android-usb.inf file I press ok and it rolls back to asking me where is the disk. I tried disabling driver enforcement but to didn't work. It's like windows doesn't want to work. I am using a win 11 copy via parallels on an M1 Mac.