Database Users

How do you get your Adam to be recognized as a APX Device

3. INSTALL DRIVERS (Windows only)
Your Windows PC will show a notification that a device “APX” has been detected. If you get a
“Found new hardware” dialog box asking where to install drivers from - choose “list or specific
location”. If you don't get this dialog, open the Device Manager via System in the Control
Panel, find and double-click the “APX” device, and click the update driver button.
Select the “usbpcdriver” folder inside the extracted Adam Recovery Kit as the driver location.
You may receive a warning that the driver is not certified or signed by Windows – choose to
install it anyway.
I'm trying to install the new update, but when i get to this portion of the instructions, I cannot for the life of me get the computer on Windows XP to recognize my device as a APX file. It's not even an option in the control panel in add new hardware. The computer keeps trying to recognize it as nvida harmony device
i saw this webpage about it and it directed me to a nvida webpage and i have absolutely no idea which one to install or whatso...
http://androidforums.com/gtablet-support-troubleshooting/253801-nv-flash-full-factory-reset.html
help :X!

Not sure if this will help, but here is some info on recovering Adam. It mentions APX...
http://www.notioninkhacks.com/forum...px&sid=91f02de37f2a51935594d9a48f299488#p2278

Also check out the GTAB forums, as the problems will probably be similar. I think Windows 64-bit and APX drivers may not play nice, for example.

NVM....i read the stupid instructions wrong. it's power button and VOLUME DOWN ........grrrrrrrrrr

How to get ADB interface for Lenovo IdeaPad S2110AF

Since I bought the Lenovo IdeaPad S2110AF from NY, I was searching for how to root the device and I found this thread http://forum.xda-developers.com/showthread.php?t=1896899.
But I was unable to get the ADB interface on Windows 7 x64 laptop and I found the same problem is there for most of the users. Finally last night, I could fix this issue and root my tablet. How I did it:
Download the "S2110-Root.zip" file through the above URL. and extract it to a folder.
1. Enable USB debugging under Settings-> Developer options.
2. Connect tab to computer using the provided data cable.
3. The driver for OTP will be installed in Windows. But the ADB interface may not be installed automatically.
4. Go to Device Manager (Right click My Computer and Properties, the click Device Manager).
5. You can see Other Devices-> Android
6. Right click on that and click Update driver software.
7. Click "browse my computer for driver software"
8. Click "Let me pick from a list of device drivers on my computer" rather than browsing and selecting the driver folder.
9. Click Next and then click "Have Disk" .
10. Then choose the drivers folder and the inf file (in extracted files) - \S2110-Root\Drivers\android_winusb.inf
11. Then select the ADB interface and click OK.
12. Ignore any warning message (like not signed)
That is it. Now you got an ADB interface. You will see as Samsung device on the device manager, never mind it.
Now you got the ADB interface and follow instruction to root through the URL.
Note: I am not sure is this a right place, but I just wanted to post this, it may help someone

I had some problems getting root to work.
I found out to use root with adb the display must be on and unlocked.
I started to work on recovery.img, finally I extracted it and took a look on it. Seems not too hard to get it modified and after do some play with custom roms.

Error 10 : ADB Drivers

I tried a hell lot to install ASUS Zenphone adb drivers on my PC( on Windows 7, 8 and 10).
I got the same error everywhere. Error 10. Driver not installed properly.
I searched the Internet for hours without success.
I hope XDA community has some answers.

i got the same problem as you , my zenfone 5 detected as unknown device , i solved with adjusting usb when plug in to laptop like slowly inserting the usb to laptop port and keep adjusting untill its detected. weird dont know why its happen like that , all other phones that i've connect to my laptop detected with easy except for that zenfone 5.

Did you already download from Asus Official Website ? @ceomaverick
Try use this one.
Step:
1. Download and Extract the file from .ZIP
Link: http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE500CL/ASUS_Android_USB_drivers_for_Windows_20150212.zip
2. Go to Device Manager, right click ' Asus Android ADB Interface '.
3. Update Driver Software, then choose ' Browse from My Computer for Driver Software'
4. Select Folder where you extract the .Zip file, check 'Include Subfolder' then klik 'Next'
5. Wait while system searching and installing the driver.
6. Finsih
Hope it will help you.
Thanks

OK, some progress here.
Find the Asus 8.0.0.2 drivers or the 8.0.0.3 ones.
Do the Add Legacy Hardware thing for the ADB Composite Interface -- it will install as "Code 10" not started.
Highlight that device and select update device...ask it to search windows online for the update.
In Win7 this will take a long time, in Win10 it will take just a second BUT be nicely hidden. Click View Optional Updates and then click Driver Updates and then select the ADB Composite interface.
In Win7 it completes quickly w/o reboot. In Win10 you have to reboot.
But with that, the ADB Composite Interface will function.
Now do the Add Legacy hardware thing for the Bootloader -- again, installs as Code 10
Put your phone into fastboot
Select the Bootloader device and do the update-from-windows thing.
Win7 does it directly, Win10 you have to navigate through the Update wizard as before
Now the fastboot interface is presented as working...

Failed to flash my google glass EE2

I tried to flash my google glass EE2 via my laptop which is currently running windows 10. I have done the following steps:
1. Update the Google USB Driver from android studio sdk manager
2. Download the new image file and unzip it
3. Open windows powershell from inside unzip image folder.
4. Run adb devices (Show my google glass in list)
5. Then adb reboot-bootloader
6. Then turn off the device with physical button and restart with camera and power button until “Press volume key to select, and press the power key to accept.” screen shows up.
7. Then run fastboot devices (Here I stuck, No list of devices, no message nothing happens)
Note:- I updated the driver as well via these steps but still end with no success
1. Connect your Android device to your computer's USB port.
2. From Windows Explorer, open Computer Management.
3. In the Computer Management left pane, select Device Manager.
4. In the Device Manager right pane, locate and expand Portable Devices or Other Devices, depending on which one you see.
5. Right-click the name of the device you connected, and then select Update Driver Software.
6. In the Hardware Update wizard, select Browse my computer for driver software and click Next.
7. Click Let me pick from a list of available drivers on my computer
8. Click Next with Show all devices selected.
9. Click Have disk.
10. Click Browse and then locate the USB driver folder. For example, the Google USB Driver is located in android_sdk\extras\google\usb_driver\.
11. Select android_winsub.inf file and click Open.
12. Click Next to install the driver with Android ADB Interface selected.
13. Confirm the Update Driver Warning dialog.
14. Driver installed

Yeah...
It's funny enough that you created this thread because I am having the exact same issue right now too.
I tried on my laptop running Windows 10 and then on my desktop running Ubuntu. Absolutely zero luck with this. Please let me know if you can figure out a solution. With Powershell I was able to see adb devices but other than that fastboot seems broken to me on Glass.

Hard reset maybe? While on hold power button for 15 seconds, then release. wait a few seconds after that and then hold power button for a few seconds to turn back on.
Also you might try Installing the rooted bootloader.
And take a look at these 2 pages: https://support.google.com/glass/answer/9649198?hl=en
https://dl.google.com/android/repository/platform-tools_r30.0.1-windows.zip

I appreciate your response!
On Windows 10, fastboot devices just seemingly doesn't work at all and doesn't populate the glass hardware at all for me.

OscarDelphi said:
I appreciate your response!
On Windows 10, fastboot devices just seemingly doesn't work at all and doesn't populate the glass hardware at all for me.
Click to expand...
Click to collapse
I see others have had problems on Windows 10 using fastboot. Seems to be related to having a correct driver for your device. If you can't find one (check your device manager to see if it is recognizing Glass properly) you might have to find a Windows 7 computer to do this on.

droidzer1 said:
I see others have had problems on Windows 10 using fastboot. Seems to be related to having a correct driver for your device. If you can't find one (check your device manager to see if it is recognizing Glass properly) you might have to find a Windows 7 computer to do this on.
Click to expand...
Click to collapse
I even tried on Ubuntu with no luck just for curiosity's sake.
Device manager is showing me Unknown USB Device is attached.

OscarDelphi said:
I even tried on Ubuntu with no luck just for curiosity's sake.
Device manager is showing me Unknown USB Device is attached.
Click to expand...
Click to collapse
It makes me so happy to be able to follow up this post with how I found a solution. I am going to give a story first because this was beyond frustrating. The solution for me was to forget finding a solution in Windows 10 and just use an installation of Ubuntu. Holy crap this made the steps a lot easier.
However, even using the Terminal in Ubuntu it hung up twice while flashing system.img and I thought Glass was dead. Fortunately, fastboot was just being finicky and refusing to work. The solution to that was to have the command already ran and then reboot back into fastboot because this allowed the system to almost instantaneously realize the device was in fastboot and it immediately the flashed the files.
I hope this might point some light if anyone else ever comes across the issue!

Install Ubuntu
The easy way to do it, is install Ubuntu and install adb and fasstboot from terminal with comand "apt-get install 'your Tool...'"
yubarajoli77 said:
I tried to flash my google glass EE2 via my laptop which is currently running windows 10. I have done the following steps:
1. Update the Google USB Driver from android studio sdk manager
2. Download the new image file and unzip it
3. Open windows powershell from inside unzip image folder.
4. Run adb devices (Show my google glass in list)
5. Then adb reboot-bootloader
6. Then turn off the device with physical button and restart with camera and power button until “Press volume key to select, and press the power key to accept.” screen shows up.
7. Then run fastboot devices (Here I stuck, No list of devices, no message nothing happens)
Note:- I updated the driver as well via these steps but still end with no success
1. Connect your Android device to your computer's USB port.
2. From Windows Explorer, open Computer Management.
3. In the Computer Management left pane, select Device Manager.
4. In the Device Manager right pane, locate and expand Portable Devices or Other Devices, depending on which one you see.
5. Right-click the name of the device you connected, and then select Update Driver Software.
6. In the Hardware Update wizard, select Browse my computer for driver software and click Next.
7. Click Let me pick from a list of available drivers on my computer
8. Click Next with Show all devices selected.
9. Click Have disk.
10. Click Browse and then locate the USB driver folder. For example, the Google USB Driver is located in android_sdk\extras\google\usb_driver\.
11. Select android_winsub.inf file and click Open.
12. Click Next to install the driver with Android ADB Interface selected.
13. Confirm the Update Driver Warning dialog.
14. Driver installed
Click to expand...
Click to collapse

QPST driver install...

Trying to get these drivers installed on windows 10 machine but no matter which driver i choose it always pops up "windows encountered an error while installing driver". im trying to get into qpst file explorer to see the policy_man folder for the carrier policy. im on havoc rom 11 and there is no engineer mode(*#801, *#800) or log kit since im not factory rom. ive tried disable driver signature verify under advanced restart on the pc....no luck same error. ive tried disable secure boot in bios on pc....same error.
ive tried these steps......
1. adb reboot ftm
2. Install (in your smartphone) USB Gadget Tool (https://f-droid.org/es/packages/net.tjado.usbgadget/) and check this modes: ( cser.dun.O , diag.diag, diag.diag.mdm , ffs.adb , gsi.dpl , gsi.rmnet , qdss.qdss , qdss.qdss.mdm )
3. adb shell su setprop sys.usb.config diag,diag_mdm,adb
4. Disconnect and connect your phone usb cable.
5. Go to Control Panel – Device Manager. You will see some unknown device. You should look at the so-called "Oneplus 8T", ignore the others.
Right click on the first "Oneplus 8T" –> Update Driver –> Browse my computer drivers -> Let me pick form a list of available drivers -> Click on I Have Disk -> Show all devices, browse then go to the Qualcomm Drivers that you download earlier. Then do the same to the other "Oneplus 8T". Choose 9018 for both unknown "Oneplus 8T"..
6. Add both ports in QPST Configuration. Only one of them is the one you are going to use. By clicking on EFS Explorer you will know which one it is by seeing X55 Driver in the description.
7. Change carrier_policy and carrier_policy.xml_Subscription01 files
8. adb reboot
stuck on step 5

Hmmm... You do have the regular drivers for the device installed as well, correct?
(ADB) works? Try this - (Let me know if you need 32 bit installer) No need to disable driver signing enforcement.
10.99 MB file on MEGA
mega.nz
64bit - If it needs a password it's GADGETSDOCTOR
If you're getting into the use of Qualcomm engineering tools check out the fine work of KL Joachim Schepke and the #u100 Crew to make QXDM5g and the accompanying Tools available, search QXDM5 , also includes driver autoinstaller.
Uninstall the old ones and reboot first, go actually delete the directory, Qcomm doesn't uninstall very cleanly.
Let me know how it goes,
-L4X$

L!V3_4_XC3SS said:
Hmmm... You do have the regular drivers for the device installed as well, correct?
(ADB) works? Try this - (Let me know if you need 32 bit installer) No need to disable driver signing enforcement.
10.99 MB file on MEGA
mega.nz
64bit - If it needs a password it's GADGETSDOCTOR
If you're getting into the use of Qualcomm engineering tools check out the fine work of KL Joachim Schepke and the #u100 Crew to make QXDM5g and the accompanying Tools available, search QXDM5 , also includes driver autoinstaller.
Uninstall the old ones and reboot first, go actually delete the directory, Qcomm doesn't uninstall very cleanly.
Let me know how it goes,
-L4X$
Click to expand...
Click to collapse
Hey thx for the reply....if you mean the oneplus drivers, then yes they are installed on pc and adb works(command prompt and all that).
i uninstalled the old ones and rebooted...downloaded that file and installed....trying now

L!V3_4_XC3SS said:
Hmmm... You do have the regular drivers for the device installed as well, correct?
(ADB) works? Try this - (Let me know if you need 32 bit installer) No need to disable driver signing enforcement.
10.99 MB file on MEGA
mega.nz
64bit - If it needs a password it's GADGETSDOCTOR
If you're getting into the use of Qualcomm engineering tools check out the fine work of KL Joachim Schepke and the #u100 Crew to make QXDM5g and the accompanying Tools available, search QXDM5 , also includes driver autoinstaller.
Uninstall the old ones and reboot first, go actually delete the directory, Qcomm doesn't uninstall very cleanly.
Let me know how it goes,
-L4X$
Click to expand...
Click to collapse
I have tried this and no luck, this is preventing me from using msm to convert my 8t and possibly unbrick if needed. No matter how I install these drivers this is what I get after reboot
"Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)"
msi laptop running windows 10 latest update

JayTheKid said:
I have tried this and no luck, this is preventing me from using msm to convert my 8t and possibly unbrick if needed. No matter how I install these drivers this is what I get after reboot
"Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)"
msi laptop running windows 10 latest update
Click to expand...
Click to collapse
i was able to get device manager to show the device(kb2005) and update/install the driver for that....however, it does not show another kb2005 device, just shows 2 'unknown device'. when i try the update/install driver for the 'unknowns', i get the windows has encountered an error message
with only the one driver installed(shows qualcomm android modem 9018 in device manager under modems tab), i still cant get qpst tools to work without both drivers. in qpst, it shows the correct driver installed as active phones and shows under ports tab....and theres no port to add with add new port

fosgate24360 said:
i was able to get device manager to show the device(kb2005) and update/install the driver for that....however, it does not show another kb2005 device, just shows 2 'unknown device'. when i try the update/install driver for the 'unknowns', i get the windows has encountered an error message
with only the one driver installed(shows qualcomm android modem 9018 in device manager under modems tab), i still cant get qpst tools to work without both drivers. in qpst, it shows the correct driver installed as active phones and shows under ports tab....and theres no port to add with add new port
Click to expand...
Click to collapse
Sorry I was traveling for a little bit - did you get this handled? Sounds to me like you need to make sure that your USB & or wireless debugging is active and not just charging, you can change it on your notifications to transfer files or something like that

L!V3_4_XC3SS said:
Sorry I was traveling for a little bit - did you get this handled? Sounds to me like you need to make sure that your USB & or wireless debugging is active and not just charging, you can change it on your notifications to transfer files or something like that
Click to expand...
Click to collapse
no problem....i was able to get it working thank you. i ended up switching over to android12 evolutionx rom. i had to do that same mod with carrier files and the phone does now pick up 5g signal and 5g icon in stat bar

fosgate24360 said:
Trying to get these drivers installed on windows 10 machine but no matter which driver i choose it always pops up "windows encountered an error while installing driver". im trying to get into qpst file explorer to see the policy_man folder for the carrier policy. im on havoc rom 11 and there is no engineer mode(*#801, *#800) or log kit since im not factory rom. ive tried disable driver signature verify under advanced restart on the pc....no luck same error. ive tried disable secure boot in bios on pc....same error.
ive tried these steps......
1. adb reboot ftm
2. Install (in your smartphone) USB Gadget Tool (https://f-droid.org/es/packages/net.tjado.usbgadget/) and check this modes: ( cser.dun.O , diag.diag, diag.diag.mdm , ffs.adb , gsi.dpl , gsi.rmnet , qdss.qdss , qdss.qdss.mdm )
3. adb shell su setprop sys.usb.config diag,diag_mdm,adb
4. Disconnect and connect your phone usb cable.
5. Go to Control Panel – Device Manager. You will see some unknown device. You should look at the so-called "Oneplus 8T", ignore the others.
Right click on the first "Oneplus 8T" –> Update Driver –> Browse my computer drivers -> Let me pick form a list of available drivers -> Click on I Have Disk -> Show all devices, browse then go to the Qualcomm Drivers that you download earlier. Then do the same to the other "Oneplus 8T". Choose 9018 for both unknown "Oneplus 8T"..
6. Add both ports in QPST Configuration. Only one of them is the one you are going to use. By clicking on EFS Explorer you will know which one it is by seeing X55 Driver in the description.
7. Change carrier_policy and carrier_policy.xml_Subscription01 files
8. adb reboot
stuck on step 5
Click to expand...
Click to collapse
What did you do specifically to get this working? I'm having trouble on Step 5 as well and I can't detect a device.

Xryphon said:
What did you do specifically to get this working? I'm having trouble on Step 5 as well and I can't detect a device.
Click to expand...
Click to collapse
Have you tried disabling Driver Signing Enforcement when booting into Windows and then installing the driver?

Xryphon said:
What did you do specifically to get this working? I'm having trouble on Step 5 as well and I can't detect a device.
Click to expand...
Click to collapse
#3 command should start like this:
adb shell
su
setprop....
Also disable Driver Signing Enforcement, as you'll have to install driver every time you want to use QPST, with it enabled.