Related
Again and again, many user are asking how to get access
to the SD card under android 2.3.1 Gingerbread or CM 7.0.
So I prepared, the solutions that I found here and have tested
under Windows XP x32 and Windows Vista x32.
Both methods are working for me on these systems!
Method 1:
1. Right click on My Computer, go to Properties.
2. Go to Device Manager
3. Find your My HTC (should be the second one Android USB Device), right click on it and select Update Driver Software
4. Then select Browse My Computer for Software
5. Then choose Let Me Pick which driver to install on the bottom.
6. Then choose USB Mass Storage Device
After this unplugging the phone. I have change the MTP to ADB Testing Interface or Android ADB Interface and things seem to be mounting everytime.
Rebooted phone and PC, both worked again so I think this may be a working solution.
Now go to MTP
1. Right click on My Computer, go to Properties.
2. Go to Device Manager
3. Find your MTP (should be under Unknown Devices), right click on it and select Update Driver Software
4. Then select Browse My Computer for Software
5. Then choose Let Me Pick which driver to install on the bottom.
6. Then choose Google Inc. and the Driver is ADB Testing Interface
or Android ADB Interface
Method 2:
Download USBDreview and delete all android drivers (including adb)
Download PDAnet and install (it will install all necessary android drivers)
Job done.
Any way to sort this in Win 7 x64?
Drive shows up but says INSERT DISC :s
New to this Android stuff and and getting nowhere fast!
TIA
If the cm kernel is being built correctly it shouldn't be showing as an mtp device at all, this only happens with stock kernels, a good example is the pershoot oc kernel I built and posted as opposed to flippy's, I think he is just using the msm7x30 source and either not using the correct drivers, or it is not being configured correctly.
I haven't seen a proper cm kernel that behaves that way.
Here's how to fix the USB problem in two easy steps:
1) Install Linux.
2) Learn bash.
Sent from a Western Union telegram.
I know there is a guide already here a long time ago, but Its step is kind of complicated. So, I figure it out another way, no need to set up a HTTP server to trick LG's update software.
I have tested it on V20f, everything works perfect. But remember, whatever you do, you do at your own risk and responsibility for your actions rests solely on you.
Unbricking part:
1. Install LG's cell phone driver, of cause.
2. Install B2CAppSetup.exe from kdz-flash.rar （download）
3. Open test-version-upTest_EX folder, Run Windows Enabler.exe as Administrator‘s authorization and turn it on by single click the icon of windows's tray.
4. Switch the phone to Download mode:
Turn off the phone, if you have not turned off.
Disconnect the USB cable from the phone if connected.
Hold down Volume Up and connect the USB cable to the phone.
Hold Volume Up until the screen: Download mode.
5. Open the folder test-version-upTest_EX and run the program UpTestEX_original.exe
6. Click on the folder icon in the row "Select kdz file" and select the file V20F_00.kdz
7. Click on "CSE web upgrade test".
8. In the window that appears, click on "Upgrade Start".
9. In the next window that appears, you will be prompted to select country and language, which will use the program.
10. The program will begin to flash update file V20F_00.kdz on your phone.
Rooting your P93x:
1.Copy LG_SystemBackupTest.apk from ROOT.rar to your phone's sdcard and intall it, run it.(download)
2.Enable USB debug mode, and connect your phone with computer by usb cable, then run root_P930.bat in your computer, then, let your PC do the rest. then you can get a rooted V20f firmware. alse, this method can root V20e, And maybe other's version firmware can be rooted by it too.
is this works in SU640 korean version?
jeonaztigz said:
is this works in SU640 korean version?
Click to expand...
Click to collapse
Use the guide I link to; it flashes a SU640 KDZ instead of the P93x.
http://forum.xda-developers.com/showthread.php?t=1784709
your files have errors & can not be extracted - can u post different file links that work
kdz-flash have virus
brianlili said:
I know there is a guide already here a long time ago, but Its step is kind of complicated. So, I figure it out another way, no need to set up a HTTP server to trick LG's update software.
I have tested it on V20f, everything works perfect. But remember, whatever you do, you do at your own risk and responsibility for your actions rests solely on you.
Unbricking part:
1. Install LG's cell phone driver, of cause.
2. Install B2CAppSetup.exe from kdz-flash.rar （download）
3. Open test-version-upTest_EX folder, Run Windows Enabler.exe as Administrator‘s authorization and turn it on by single click the icon of windows's tray.
4. Switch the phone to Download mode:
Turn off the phone, if you have not turned off.
Disconnect the USB cable from the phone if connected.
Hold down Volume Up and connect the USB cable to the phone.
Hold Volume Up until the screen: Download mode.
5. Open the folder test-version-upTest_EX and run the program UpTestEX_original.exe
6. Click on the folder icon in the row "Select kdz file" and select the file V20F_00.kdz
7. Click on "CSE web upgrade test".
8. In the window that appears, click on "Upgrade Start".
9. In the next window that appears, you will be prompted to select country and language, which will use the program.
10. The program will begin to flash update file V20F_00.kdz on your phone.
Rooting your P93x:
1.Copy LG_SystemBackupTest.apk from ROOT.rar to your phone's sdcard and intall it, run it.(download)
2.Enable USB debug mode, and connect your phone with computer by usb cable, then run root_P930.bat in your computer, then, let your PC do the rest. then you can get a rooted V20f firmware. alse, this method can root V20e, And maybe other's version firmware can be rooted by it too.
Click to expand...
Click to collapse
The file kdz-flash have virus, can you update that? tvm.
If you take the ZVE update, IORoot no longer works. You must use Stump Root method
According to @autoprime, you must use the Stump Root method in order to root the ZVE update
http://forum.xda-developers.com/sprint-g2/general/ls980-zve-ota-zip-update-zvc-zve-t2912488
Stump root can be found here
http://forum.xda-developers.com/lg-g3/orig-development/root-stump-root-lg-g3-sprint-verizon-t2850906
It has been confirmed by many that the IO root now works on the LS980 though it is not listed in the main IO root thread. Below is a link with all the specific instructions for how to use this root tool.
http://forum.xda-developers.com/showthread.php?t=2448887
Basic Instructions for rooting on firmware ZVA
1. Ensure you have the proper USB drivers installed, and your phone is in the proper mode (For Verizon, use Ethernet mode on the PC settings menu).
NOTE: If you do not have the USB drivers installed, you can get them from here: http://www.lg.com/us/support-mobile/lg-LGD801BK under MANUALS & DOWNLOAD -> Software Update -> USB Drivers (Yes the Tmobile drivers work since the Sprint page doesn't post USB drivers)
2. Enable Developer Mode (Press "Build Number" 7 times) on your phone and enable USB Debugging
3. Extract ioroot zip file somewhere on your PC
4. Plug your phone into your PC. Ensure that the USB connection is set to "Charge Only".
5. On PC, open up command prompt and type adb devices command and accept the ADB RSA command on the phone. It should say "LG-LS980-XXXXXXXXXXX device" If you saw the following it confirms that the device is detected in ADB.
6. Put your phone in Airplane mode.
7. Run root.bat
8. The script will ask you that the USB Connection Mode needs to be toggled. Toggle USB mode from Charge Only to MTP and then back to Charge Only.
9. You will then be asked if you would like to have a superuser package installed, which you can accept or decline
10. Download Root Checker from Play Store: https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck to verify successful root.
Basic Instructions for rooting on firmware ZVC with IO Root v25
1. Ensure you have the proper USB drivers installed, and your phone is in the proper mode (For Verizon, use Ethernet mode on the PC settings menu).
NOTE: If you do not have the USB drivers installed, you can get them from here: http://www.lg.com/us/support-mobile/lg-LGD801BK under MANUALS & DOWNLOAD -> Software Update -> USB Drivers (Yes the Tmobile drivers work since the Sprint page doesn't post USB drivers)
2. Enable Developer Mode (Press "Build Number" 7 times) on your phone and enable USB Debugging
3. Extract ioroot zip file somewhere on your PC
4. Plug your phone into your PC. Ensure that the USB connection is set to "Charge Only".
5. On PC, open up command prompt and type adb devices command and accept the ADB RSA command on the phone. It should say "LG-LS980-XXXXXXXXXXX device" If you saw the following it confirms that the device is detected in ADB.
6. Run root.bat
7. When phone boots into recovery, select 'apply update from ADB' with power button.
8. Reboot phone into system.
10. Download Root Checker from Play Store: https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck to verify successful root.
Download the latest version of IO Root (6/17/14 build) from @autoprime's post below:
http://forum.xda-developers.com/showpost.php?p=48709232&postcount=869
YOU MUST USE IOROOT v25 or later if you are on the ZVC (Android 4.4.2) firmware update.
Here is a tutorial video explaining how to install IO Root:
http://www.youtube.com/watch?v=Y45SXPRb31o
I am not the creator of this root method i am simply compiling the information for sprint users since it is scattered in many different places.
Credits go to @autoprime and thank him for maintaining and updating the IO Root method as new updates come up and @thecubed for creating the IO Root method.
Univsoldur said:
It has been confirmed by many that the IO root now has an area for the LS980 though it is not listed in the main IO root thread. below is a link with all the specific instruction for how to use this root tool.
http://forum.xda-developers.com/showthread.php?t=2448887
This is a link to the area for the file that you will use in conjunction with the instructions from that thread. The link that they provide does not link to IO root version 11.
http://downloads.codefi.re/shelnutt2/g2/spr
According to ericdabbs this file works with the IO root method.
http://forum.xda-developers.com/showpost.php?p=47339494&postcount=3
I am not the creator of this root method i am simply compiling the information for sprint users since it is scattered in many different places.
Click to expand...
Click to collapse
anyone try this yet? is there any reason to do this over the other root method?
I did i just prefer methods developed by xda members specifically for our phones.
Sent from my LG-LS980 using Tapatalk
I'm worried that Sprint will issue an update soon, as carriers often do quickly after the launch of a new product, and we won't be able to get it with a rooted phone. Not sure whether to root or not, and if so how long to wait.
TheSapient said:
I'm worried that Sprint will issue an update soon, as carriers often do quickly after the launch of a new product, and we won't be able to get it with a rooted phone. Not sure whether to root or not, and if so how long to wait.
Click to expand...
Click to collapse
You can always unroot if the an update won't take. The only time this has been an issue for me is when I'm running something other than the stock ROM. The downside about OTA's is they break root most of the time, so you'll have to root your device again.
I used this method to root. The only problem I had was where it said to disable USB debugging and reconnect the phone. After I did that it wouldn't connect and complete the superuser install. I tried all the USB connections types; charge only, mtp, & ptp, but the adb interface wouldn't show up in device manager. I finally just re-enabled USB debugging and the install process continued without any problem. Everything seems OK, superuser is installed, I was able to install TWRP and I'm doing a Titanium backup right now.
Does anyone think there will be a mod released later on to "untrip" the built in root checker? I'm holding off on rooting based only on that.
rich_e said:
I used this method to root. The only problem I had was where it said to disable USB debugging and reconnect the phone. After I did that it wouldn't connect and complete the superuser install. I tried all the USB connections types; charge only, mtp, & ptp, but the adb interface wouldn't show up in device manager. I finally just re-enabled USB debugging and the install process continued without any problem. Everything seems OK, superuser is installed, I was able to install TWRP and I'm doing a Titanium backup right now.
Click to expand...
Click to collapse
I'll give you an explanation why it didn't work for you initially and how your accidental discovery was what fixed it.
The instructions in the root.bat file said to do after it pushed the initial files into the phone was
1. Unplug the phone off USB from PC
2. Disable USB debugging option
3. Re-enable USB debugging option
4. Connect phone to USB from PC.
What you did initially was steps 1, 2 and 4 and skipped 3 and expected the root.bat script to continue. Obviously the root.bat file can't detect the phone once you reconnected it to USB because you don't have USB debugging on which is needed for detection. What you did eventually was the smart thing and re-enable the USB debugging that finished the install process.
This is the excerpt from the root.bat file that clearly explains to disable USB debugging and immediately re-enable USB debugging after the root.bat file pushes the initial root files.
echo *******************************************************
echo Now, please unplug usb, go to developer options and
echo disable USB debugging and re-enable it.
echo Once you've done that, re-plug your usb...
echo *******************************************************
This root works 100%. I compared the iorootv10 and iorootv11 root.bat files and it clearly did not have a Sprint option for the root.bat file to detect in iorootv10. Also this was released by a recognized developer/contributer shelnutt2. I hope thecubed edits his XDA thread to upload iorootv11 so that we can reference that XDA thread instead.
Mine stays stuck on "looking for device" ... Any tips?
o0adam0o said:
Mine stays stuck on "looking for device" ... Any tips?
Click to expand...
Click to collapse
Did you ensure you have enabled USB debugging and installed the USB drivers? Also if you have adb, try opening a command prompt in the same folder as adb and type "adb devices". You should see a response of your device listed and "device". If you see a response of a device listed and "offline" that means your phone is not communicating with your PC which is why the root.bat file is giving you an error.
Check out this tutorial video for the ioroot and it should make it more clear. Keep in mind that the video was made when iorootv10 was released but the steps to do the root are the same.
http://www.youtube.com/watch?v=Y45SXPRb31o
Make sure you are downloading the iorootv11 files here that includes the Sprint version: http://downloads.codefi.re/shelnutt2/g2/spr
Here is the link to the USB Drivers in case you need it. It is from the ATT and Tmobile version from the LG website but it works fine. Scroll down the page to Software Update tab and download USB driver.
http://www.lg.com/us/support-mobile/lg-D801
o0adam0o said:
Mine stays stuck on "looking for device" ... Any tips?
Click to expand...
Click to collapse
If you haven't installed the drivers use these.
LG United Mobile Drivers
http://d-h.st/EW4
Edit: was already answered in the post ahead of mine. This file is a direct download.
ericdabbs said:
..
Click to expand...
Click to collapse
removed for less confusion
Univsoldur said:
Could you put together something that references the correct places for sprint users to install recovery. I haven't flashed it yet though I think this is correct. I thought since you had already you would prolly know best and could explain it to people easier than me.
http://www.teamw.in/project/twrp2/197
Click to expand...
Click to collapse
Actually I haven't installed TWRP on my G2 yet.
However I intend to follow WACOMalt's method located here:
http://forum.xda-developers.com/showthread.php?t=2449670
You need to download the Sprint TWRP Recovery file here: http://techerrata.com/browse/twrp2/g2spr
WACOMalt also posted a tutorial video on how to flash recovery using his method shown here:
http://www.youtube.com/watch?v=OZSjL6FCyxA
ericdabbs said:
..
Click to expand...
Click to collapse
removed for less confusion
Univsoldur said:
yea i know thats the correct recovery image but i dont have adb set up on this PC and was wondering if i could do it using terminal emulator. Either way I wont clutter this thread up with recovery because I know people will get confused so I will create a new thread.
Click to expand...
Click to collapse
Please create a new thread so that I can have you post the adb/fastboot files for download. Its very important to have adb and fastboot files installed on your PC if you intend to do Android hacking.
ericdabbs said:
Please create a new thread so that I can have you post the adb/fastboot files for download. Its very important to have adb and fastboot files installed on your PC if you intend to do Android hacking.
Click to expand...
Click to collapse
its up im gonna remove these previous posts
Univsoldur said:
its up im gonna remove these previous posts
Click to expand...
Click to collapse
Can you update the OP for this thread to include reference to the ioroot tutorial video.
http://www.youtube.com/watch?v=Y45SXPRb31o
Also can you remove the reference to me confirming the root works in the OP. I don't think its necessary to have that since we know ioroot is a trusted root method.
Anyoneknow how to disable system updates.
Sent from my LG-LS980 using Tapatalk
Univsoldur said:
Anyoneknow how to disable system updates.
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
I am not sure. That would be very handy in case Sprint wants to push out an OTA. We know that eventually Sprint is going to get an OTA in early 2014 to enable triband LTE or Sprint Spark.
At this point, I am more interested in leroybrute's message that wifi tether works on the Sprint version.
Used this and flashify to install twrp took less than 5 minutes bring on the ROMS
Sent from my LG-LS980 using XDA Premium 4 mobile app
Have You enabled USB Debuging?
(In Android 4.2.2 or later)
Don't see the option To have USB debugging enabled;
Go to -
Settings, More,
Scroll to the bottom,
About on your device
and click on
Build number at the bottom 7 times
until it says You are now a developer (may go by fast and you don't actually see it).
Now here is where the problem may start.
When you have enabled usb debugging, then unplug/replug the usb cable and still your device is not listed in ADB?
OK so you have set your device into USB mode ( hit the Build number in About device 7 times if necc.)
Windows popped up a little notice and said your device Samsung xyz is ready to use.
Your device shows up in list of items to explore and you can see your files in windows explorer.
Great. Now why doesn't it show up in adb? You try different adb installs and still no device.
What could be wrong?
What to do?
If the device is seen in Windows explorer but is not recognized in adb,
you may need to reconfigure the inf file in windows/ inf folder (usb.inf)
Do this after you make a backup of you usb.inf file first!
Use notepad and make sure the box to use this always is not checked.
I just copied the file to another location to edit it. Then rename the original file to usb1.inf.
Then I copied the edited file back to the windows inf folder.
In Windows 7 (The listed information is listed in devices, driver, driver ID.)
To get the needed information to edit your usb.inf file -
Go to Computer, System Properties (at the top) Device manager.
Here under Portable Devices you should see your device listed. Note the exact name.
Double click or right click and then properties, under driver details change the radio bar to Harware ID from Device description. The information should look like this;
USB\VID_04E8&PID_6860.
USB\VID_04E8&PID_6860&REV_0400.
Now you will need to use that information in the area of your usb.inf file after this item;
;Non-Localizable
Samsung.Mfg="Samsung"
USB\VID_0419&PID_8001.DeviceDesc="Samsung USB Hub"
USB\VID_055D&PID_8001.DeviceDesc="Samsung E.M. USB Hub"
so that after it will look like this (after the previously noted area)
;Non-Localizable
Samsung.Mfg="Samsung"
USB\VID_04E8&PID_6860.DeviceDesc="Samsung USB Hub"
USB\VID_04E8&PID_6860&REV_0400.DeviceDesc="Samsung E.M. USB Hub"
I have tested this on a Samsung S3 SPH-L710 and was able to get the phone to be recognized by adb.
Then I was able to install recovery and root thanks to the work of Chainfire via
Sprint variant – [SPH-L710] CF-Auto-Root v1.0
After upgrading to Android Q suddenly my pc can't recognize my pixel as a android device also i can't connect any wired things such as dongle jack or USB Transfer (USB charging options disappeared).
Planning to downgrade to Pie but the problem is my device can't be detected on my pc. Any solutions? Thanks
If you're using a Microsoft Windows machine, I would suggest uninstalling any "Android" drivers from the Device Manager. Then restart the PC, then turn off "USB debugging" and back on for the Pixel, and even "Revoke authorizations" in hopes that it will re-alert & request another authorization and, therefore, verify it being connected and detected on the PC....
After all that -- or if you can only enter in Bootloader Mode -- type the command "fastboot devices" and say here what it outputs. If anything, while in Bootloader Mode, do what I previously said, but look for anything "Android" and "Bootloader" and uninstall those device drivers...
Good luck and hope this helps!
simplepinoi177 said:
If you're using a Microsoft Windows machine, I would suggest uninstalling any "Android" drivers from the Device Manager. Then restart the PC, then turn off "USB debugging" and back on for the Pixel, and even "Revoke authorizations" in hopes that it will re-alert & request another authorization and, therefore, verify it being connected and detected on the PC....
After all that -- or if you can only enter in Bootloader Mode -- type the command "fastboot devices" and say here what it outputs. If anything, while in Bootloader Mode, do what I previously said, but look for anything "Android" and "Bootloader" and uninstall those device drivers...
Good luck and hope this helps!
Click to expand...
Click to collapse
Thanks for replying, i already tried to uninstall android driver, but when i try to reconnect, my pc recognize my device as "unknown device"
blancheSX said:
Thanks for replying, i already tried to uninstall android driver, but when i try to reconnect, my pc recognize my device as "unknown device"
Click to expand...
Click to collapse
what about the other things I suggested?
Or, so it can be clearer, are you in the System/OS when plugging/reconnecting or in Bootloader Mode?
I ran across the same issue..I followed this video to get rid of the old USB drivers and updated to the new Android driver.. Now my window 10 recognize my pixel 2xl storage completely.
https://youtu.be/Zc_dhxc8iJU
I have this issue before, and after all i got my phone detected. But when i flash it, it say unbootable slot in fastboot screen. After couple onf time, it cant be flashed again and die.... My phone cant turn on in fastboot mode again, it bricked
I had to use the USB dongle to connect a flashdrive to my phone, wait for it to recognize the drive, then unplug the drive and dongle... Then connect phone to PC... Profit!
If anyone is still having the issue of PC not recognizing device in fastboot, please be sure you have UNinstalled the older version(s) of SDK Tools from yhour PC and make sure to INSTALL the latest versions.
You can find the latest version linked in the 9x guide in my signature.
Also, make sure you have both older and newer USB cables handy. The Pixel has a nasty reputation for being finicky with USB cables, try diff cables and different USB ports on your PC.
There is also a basic troubleshooting guide in the same link in my sig.
Best regards!
simplepinoi177 said:
what about the other things I suggested?
Or, so it can be clearer, are you in the System/OS when plugging/reconnecting or in Bootloader Mode?
Click to expand...
Click to collapse
i did in 2 conditions, first one is my device turned On (adb is not detected) also 2nd one is my device in bootloader mode (fastboot devices is not detected too)
been trying to update my driver but i always got (error code : 10, device cannot started) i dunno what to do right now
dallas90733 said:
I ran across the same issue..I followed this video to get rid of the old USB drivers and updated to the new Android driver.. Now my window 10 recognize my pixel 2xl storage completely.
https://youtu.be/Zc_dhxc8iJU
Click to expand...
Click to collapse
i tried those tuturial and ended in error code : 10, device cannot started.
SageWilliams said:
I had to use the USB dongle to connect a flashdrive to my phone, wait for it to recognize the drive, then unplug the drive and dongle... Then connect phone to PC... Profit!
Click to expand...
Click to collapse
whenever i try to connect a flashdrive with my dongle, there is no option or something, it's just usb charging option appeared.
blancheSX said:
i did in 2 conditions, first one is my device turned On (adb is not detected) also 2nd one is my device in bootloader mode (fastboot devices is not detected too)
been trying to update my driver but i always got (error code : 10, device cannot started) i dunno what to do right now
Click to expand...
Click to collapse
blancheSX said:
whenever i try to connect a flashdrive with my dongle, there is no option or something, it's just usb charging option appeared.
Click to expand...
Click to collapse
So…without you being too definitive…it seems that you’re able to get into your OS…
What I’d like you to do is uninstall and remove Google usb drivers on your computer. Then, download it again HERE: https://dl-ssl.google.com/android/repository/latest_usb_driver_windows.zip . And, in case things don’t work out this time around, if you can please save the (.zip) file on your Desktop or root folder (usually the C: drive). I might have you direct the device detected to the files in this .zip directly.
Then, after installing the USB drivers, I’d like you to uninstall and remove any/all things that are named “platform-tools” (so there will only be ONE "platform-tools" after you re-download it in this step) on the whole device. After, I’d like you to download the latest Windows version HERE: https://developer.android.com/studio/releases/platform-tools . Again, to simplify things, if you can extract it either in your Desktop or root folder (C: drive).
Again, like I mentioned before, I would like for your device to request authorization for your computer again, so if you can please go to the Developers option, and select “Revoke USB debugging authorizations” as well as double-checking you have "USB debugging" enabled…
Only THEN, once these two things are extracted and installed (as is the case in the first step) and you revoked the authorizations, can you plug in your device and USB cord. Watch your phone/device, as it will ask for authorization to connect to your computer, and you’ll have to make sure the box is checked that says “don’t ask this every time” or “remember this device” – I can’t recall off-hand – and then make sure to “Allow” it. By doing this, you can be sure that your computer and device are talking correctly.
*One suggestion that isn’t mandatory is that you select where it says “USB charging” and change it to “MTP” or “file-sharing” (sorry, again, I can’t recall specifically off the top of my head…)
If all things are working well, if you can open up a command prompt (a.k.a. “cmd”, and also make sure you are running it “As an administrator”) and direct it to the platform-tools directory (hopefully you followed my suggestion and kept it simple so it will either be at the root “C:\” or on your Desktop “C:\Users\[username]\Desktop” so it won't be too difficult directing it there...), and run the commands
Code:
adb devices
and
Code:
fastboot --version
.
Hopefully, if you do all of these things, it might get things reset and working from a stable established set up.
If it somewhat works, but the device in your "Device Manager" is showing up something "funky", then it'll take a rather nuanced Windows troubleshooting technique to resolve where I would have you correct the wrong entry/driver in the "Device Manager" and have it specifically point to one of the contents of the .zip files; shown prior.... We'll tackle that if need be and if all this initial beginning troubleshooting doesn't pan out...
Let me/us know how it works out, good luck, and hope this all ends up being helpful…
simplepinoi177 said:
So…without you being too definitive…it seems that you’re able to get into your OS…
What I’d like you to do is uninstall and remove Google usb drivers on your computer. Then, download it again HERE: https://dl-ssl.google.com/android/repository/latest_usb_driver_windows.zip . And, in case things don’t work out this time around, if you can please save the (.zip) file on your Desktop or root folder (usually the C: drive). I might have you direct the device detected to the files in this .zip directly.
Then, after installing the USB drivers, I’d like you to uninstall and remove any/all things that are named “platform-tools” (so there will only be ONE "platform-tools" after you re-download it in this step) on the whole device. After, I’d like you to download the latest Windows version HERE: https://developer.android.com/studio/releases/platform-tools . Again, to simplify things, if you can extract it either in your Desktop or root folder (C: drive).
Again, like I mentioned before, I would like for your device to request authorization for your computer again, so if you can please go to the Developers option, and select “Revoke USB debugging authorizations” as well as double-checking you have "USB debugging" enabled…
Click to expand...
Click to collapse
thanks for ur explanation, and i'm sure i already did this 100% as you mentioned before. looking for solution and i found this at pixel community thread : https://support.google.com/pixelphone/thread/14477635?hl=en
and btw when i try to disable and back to enable (again) USB debugging, there's no pop up or something like that, just nothing appear. so i just realized why i got error code : 10 is just because my phone still not detected by PC also i tried in other computer (with windows 8.1 installed) my device is got detected but as "device descriptor request failed" not as an android device. Hopefully next update google will fix this "bug". Once again thank you very much
blancheSX said:
thanks for ur explanation, and i'm sure i already did this 100% as you mentioned before. looking for solution and i found this at pixel community thread : https://support.google.com/pixelphone/thread/14477635?hl=en
and btw when i try to disable and back to enable (again) USB debugging, there's no pop up or something like that, just nothing appear. so i just realized why i got error code : 10 is just because my phone still not detected by PC also i tried in other computer (with windows 8.1 installed) my device is got detected but as "device descriptor request failed" not as an android device. Hopefully next update google will fix this "bug". Once again thank you very much
Click to expand...
Click to collapse
Yeah...I figured as much...I was just making sure to lay down the "ground work" before proceeding...
If you're still willing....what I had planned next was to walk you through manually updating/"editing" the driver (on the PC) to directly look at the Google usb drivers specifically to try and get around the whole "device descriptor" and other (detection) error codes.......
Might want to try uninstall the SDK toolkit, reboot PC, then install the latest SDK toolskit.
Also having both USB 2.0 and 3.0 cables saved me more than once, and is a known thing on the 2XL.