can't ROOT phone - device not installed - General Questions and Answers

can't ROOT phone - device not installed - General Questions and Answers

I followed this guide from LG optimus 3d fourm
Step 1: Download SuperOneClick here http://www.megaupload.com/?d=IKMS0QN3 then extract it.
Step 2: On the phone goto settings > Applications > Development > Turn USB Debugging on also turn on unknown sources.
Step 3: connect the phone to your pc make sure mass storage is turned off once connected wait for the drivers to install
Step 4: Run SuperOneClick as admin and click on Root, sometimes it can take a few minutes once it's done restart the phone now you should have superuser app on the phone.
Click to expand...
Click to collapse
MY ERROR
~~~~
when running superoneclick and hitting root.
the follow device does not have drivers installed:
android phone USB\VID_1004&PID_618E
Would you like to me forcefully install an Android ADB Interface driver for this device?
If I hit "no" it begins the root and the program freezes after step 2.
I haven't hit yes because I don't know if I this is a good thing.

Unplug your phone from your computer. Download a program called usbdeview. Open the program and it will allow you to see all of the drivers installed on your computer. Delete everything associated with your phone. Make sure USB Debugging is checked and plug your phone back into your computer. This will do a fresh install of all drivers and should also include the drivers for ADB. To check this, open up a CMD window in platform-tools in your SDK folder and type in "adb devices". A serial number for your phone should come up, and if it does, you are good to go.

Have you got lgs drivers installed on pc? I had same problem and had to reinstall driver.
Dave
Sent from my LG P920 using Tapatalk

lowandbehold said:
Unplug your phone from your computer. Download a program called usbdeview. Open the program and it will allow you to see all of the drivers installed on your computer. Delete everything associated with your phone. Make sure USB Debugging is checked and plug your phone back into your computer. This will do a fresh install of all drivers and should also include the drivers for ADB. To check this, open up a CMD window in platform-tools in your SDK folder and type in "adb devices". A serial number for your phone should come up, and if it does, you are good to go.
Click to expand...
Click to collapse
device driver was not successfully installed.
I uninstalled both the LG usbs in usbdeview.

umirin said:
device driver was not successfully installed.
I uninstalled both the LG usbs in usbdeview.
Click to expand...
Click to collapse
http://www.t-mobilephone.org/t-mobile-lg-optimus-3d-usb-driver-download.html/
Try this

lowandbehold said:
http://www.t-mobilephone.org/t-mobile-lg-optimus-3d-usb-driver-download.html/
Try this
Click to expand...
Click to collapse
thank you very much worked.

Related

Google Ion Developer's Edition

I need some help installing amon_ra's recovery. In adb it states I don't have permission to push files. If I try to run a fastboot it states I don't have permission. How can I get the above mentioned recovery on this phone ?

timal said:
I need some help installing amon_ra's recovery. In adb it states I don't have permission to push files. If I try to run a fastboot it states I don't have permission. How can I get the above mentioned recovery on this phone ?
Click to expand...
Click to collapse
You should ask this in the thread that already exists.
If you follow every step listed, that won't happen. Do not skip any steps.
Do not skip any steps
1. Boot the device in fastboot mode, hold down the back button while powering on.
2. Connect via USB.
3. "fastboot boot recovery-RAv1.1.1H.img"
It will reboot into the custom fastboot with a black background. Then you'll be set to do these commands:
adb shell mount -a
Ignore the the errors...
adb push recovery-RAv1.1.1H.img /system/recovery.img
adb push recovery-RAv1.1.1H.img /sdcard/recovery-RAv1.1.1H.img
adb shell flash_image recovery /sdcard/recovery-RAv1.1.1H.img
adb shell reboot

I would have tried all that except the adb drivers are not working with the magic on windows vista. Device manager only shows Android 1.0

timal said:
I would have tried all that except the adb drivers are not working with the magic on windows vista.
Click to expand...
Click to collapse
they work fine, you just need to properly install them.

k4r1m said:
they work fine, you just need to properly install them.
Click to expand...
Click to collapse
Device manager only shows Android 1.0 Which I installed from the most recent sdk. Adb only will show 'waiting for device' even when I try to boot the recovery before flashing.

timal said:
Device manager only shows Android 1.0 Which I installed from the most recent sdk. Adb only will show 'waiting for device' even when I try to boot the recovery before flashing.
Click to expand...
Click to collapse
Switch to Linux ... nah just kidding... you obviously have a driver "issue", it happens to many people using Micro$oft Vi$ta...
Perform the following steps (do not skip any steps) on Vista :
1. Make sure your phone is not connected via usb
2. Download USBdeview and run it as admin (it's very important to run it as admin otherwise you will be unable to uninstall!).
3. Uninstall all drivers that mention Android in the device name or description.
4. Make sure that USB debugging is enabled in your phone (Settings - Applications - Development - USB debugging).
5. Connect your phone via usb.
6. Vista will now look for drivers, point it to the sdk drivers and make sure it uses those.
7. Check with "adb devices" to see if your phone listed.

Amon_RA said:
Switch to Linux ... nah just kidding... you obviously have a driver "issue", it happens to many people using Micro$oft Vi$ta...
Perform the following steps (do not skip any steps) on Vista :
1. Make sure your phone is not connected via usb
2. Download USBdeview and run it as admin (it's very important to run it as admin otherwise you will be unable to uninstall!).
3. Uninstall all drivers that mention Android in the device name or description.
4. Make sure that USB debugging is enabled in your phone (Settings - Applications - Development - USB debugging).
5. Connect your phone via usb.
6. Vista will now look for drivers, point it to the sdk drivers and make sure it uses those.
7. Check with "adb devices" to see if your phone listed.
Click to expand...
Click to collapse
Thank you I tried all the above. Long story short brick, no power dead . This hobbie is getting expensive.

[Q] Can i root 2.3.3 with gingerbreak ?

hello, can i root my official 2.3.3 optimus one with gingerbreak from this thread http://forum.xda-developers.com/showthread.php?t=1044765 ? i mean will it work? If not is where any simple ways to do what?

Can i root 2.3.3 with gingerbreak ?
Click to expand...
Click to collapse
no
How to root LG Optimus One P500 on gingerbread 2.3.3
1. Be sure that you have installed the original V20 GB ROM
2. if you have it installed and tried different methods to root on it do a factory reset before trying this one
3. Be absolutely sure that you have all the phone-drivers installed when working with the phone in USB debugging mode, if not install them (http://www.mediafire.com/file/t3gvrb6345yay99/LGUnitedMobileDriver_S497MA20_WHQL_ML_Ver_1.0.msi)
4. Download SuperOneClickv1.9.5-ShortFuse (http://forum.xda-developers.com/attachment.php?attachmentid=624175&d=1307984755), after download extract the files into a folder with the same name as the archive.
5. After you extracted the files, go to C:\Windows\System32 and copy the cmd.exe to the folder where you extracted the files, in my case C:\Users\myuser\Desktop\SuperOneClickv1.9.5-ShortFuse\ADB.
6. Enter the phone settings menu, to the Development and tick the USB debugging mode. Connect the USB cable to the phone, wait until it recognizes it
7. right click on cmd.exe from the ADB folder, Run as administrator, than write:
adb devices
adb shell
echo 1 > /data/local/lge_adb.conf (do not close the window)
8. Leave the settings to the SuperOneClick as they are when it opens, click on ROOT and wait, it will say Starting ADB server..., than it will do it's job and than it will appear Waiting for device... it will say ok --- if it freezes while running psneuter do the following:
a. Turn USB Debugging OFF wait until it will appear in the window again Starting ADB server..., after that,
b. Turn USB Debugging ON, and after this trick it will start rooting.

rockvoid said:
no
How to root LG Optimus One P500 on gingerbread 2.3.3
1. Be sure that you have installed the original V20 GB ROM
2. if you have it installed and tried different methods to root on it do a factory reset before trying this one
3. Be absolutely sure that you have all the phone-drivers installed when working with the phone in USB debugging mode, if not install them (http://www.mediafire.com/file/t3gvrb...ML_Ver_1.0.msi)
4. Download SuperOneClickv1.9.5-ShortFuse (http://forum.xda-developers.com/atta...5&d=1307984755), after download extract the files into a folder with the same name as the archive.
5. After you extracted the files, go to C:\Windows\System32 and copy the cmd.exe to the folder where you extracted the files, in my case C:\Users\myuser\Desktop\SuperOneClickv1.9.5-ShortFuse\ADB.
6. Enter the phone settings menu, to the Development and tick the USB debugging mode. Connect the USB cable to the phone, wait until it recognizes it
7. right click on cmd.exe from the ADB folder, Run as administrator, than write:
adb devices
adb shell
echo 1 > /data/local/lge_adb.conf (do not close the window)
8. Leave the settings to the SuperOneClick as they are when it opens, click on ROOT and wait, it will say Starting ADB server..., than it will do it's job and than it will appear Waiting for device... it will say ok --- if it freezes while running psneuter do the following:
a. Turn USB Debugging OFF wait until it will appear in the window again Starting ADB server..., after that,
b. Turn USB Debugging ON, and after this trick it will start rooting.
Click to expand...
Click to collapse
Thanks, what was very informative, much more informative than i have found superoneclick instructions with google. Thanks again

adb is included in superoneclick zip-file.
just extract zip-file and you have adb...

Teraman said:
hello, can i root my official 2.3.3 optimus one with gingerbreak from this thread http://forum.xda-developers.com/showthread.php?t=1044765 ? i mean will it work? If not is where any simple ways to do what?
Click to expand...
Click to collapse
http://www.lg-p500.ru/2011/06/root-android-233.html - got root on original rom with no problem. You can translate it on Google translate if russian language is not for you Sorry for English - rules forbid me to write here in Lithuanian

Teraman said:
whese links are broken
Click to expand...
Click to collapse
sorry... fixed it in my 1st post...
usb drivers: http://www.mediafire.com/file/t3gvrb6345yay99/LGUnitedMobileDriver_S497MA20_WHQL_ML_Ver_1.0.msi
superoneclick: http://forum.xda-developers.com/attachment.php?attachmentid=624175&d=1307984755

rooted successfully

rockvoid, milion thanks to you

tried same with my p500 v20c but it keeps getting stuck in the psneuter running thing. tried turning debugg off and on and rebooting device between tries but not getting anywhere i guess i'll have to wait for something else to come by unless theres any other way but i've looked everywhere and there isnt

have you done the following, without getting an error?
adb devices
adb shell
echo 1 > /data/local/lge_adb.conf (do not close the window)
Click to expand...
Click to collapse

I did but not that exact way i put em just with the spaces in between them. does it matter? me and dos don't really get along lol

enobano said:
I did but not that exact way i put em just with the spaces in between them. does it matter? me and dos don't really get along lol
Click to expand...
Click to collapse
you must type it exactly.... with "enter-key" after every line...
adb devices (enter-key)
adb shell (enter-key)
echo 1 > /data/local/lge_adb.conf (enter-key)

done in 10 seconds thanks a lot mate. crystal clear advice.

by the way is busybox obligatory after root or is it ok without? i see in most of those tutorials they say to install it.
thanks again man

Hi, I succesfuly rooted my P500 with these instructions, however after reboot it seems that rooting was lost. Did I miss something for making the rooting permamanent?
> Never mind it seems there was a glitch in an app getting root rights, it's working fine

enobano said:
by the way is busybox obligatory after root or is it ok without? i see in most of those tutorials they say to install it.
thanks again man
Click to expand...
Click to collapse
no it´s not obligatory.. it´s optional

still not rootin

Crashing
Hy, i think i rooted my phone ,because i followed the steps you posted and i didn't get any errors , but when i try to run different apps like titanium backup or rom manager super user crashes,not even the fix permissions in rom manager will fix it.any ideas ? oh and i was talikn on my phone and it reboted directly from the android loading screen..what do you think? root problem or phone glitch.thanx in advance

[Q] Phone not recognized by computer

Alright, here goes my first post. I have lingered in these forums for awhile, and have always found what I needed. This is the first time my searching on here, as well as google, has let me down.
To clarify, if I connect to my computer and have USB Mass Storage on, I can see it, move files to it and everything. My problem is, I am using my old phone (P500) to learn and practice ADB (I own a GNEX), and would like to install CWM via ADB, but I need to move files to the root of my sd.. but my phone won't show up if it's in debugging mode!
I have the drivers installed, and used a toolkit to root (worked fine, no errors). Am I missing something here or is there another issue?
Info:
Windows 7 64bit
Telus Mobility (Canada)
Model: LG-P500h
Android 2.3.3 (stock)
stock kernel

MissBizz said:
Alright, here goes my first post. I have lingered in these forums for awhile, and have always found what I needed. This is the first time my searching on here, as well as google, has let me down.
To clarify, if I connect to my computer and have USB Mass Storage on, I can see it, move files to it and everything. My problem is, I am using my old phone (P500) to learn and practice ADB (I own a GNEX), and would like to install CWM via ADB, but I need to move files to the root of my sd.. but my phone won't show up if it's in debugging mode!
I have the drivers installed, and used a toolkit to root (worked fine, no errors). Am I missing something here or is there another issue?
Info:
Windows 7 64bit
Telus Mobility (Canada)
Model: LG-P500h
Android 2.3.3 (stock)
stock kernel
Click to expand...
Click to collapse
Since the device is not getting detected with USB Debugging enabled it's safe to assume a bad driver installation. To verify tho, enable USB Debugging on the device and connect it to your PC. Go to Device Manager. Somewhere towards the top, assuming the drivers were installed will be a device "ADB Interface" with a subitem "Android Platform Sooner Single ADB Interface" or something similiar. If the "ADB Interface" item isn't there then the drivers weren't installed correctly. Uninstall them. Reboot computer. Rerun driver installation program. When it finished, reboot your PC. Power off the device. Connect it to your PC. Power on the device and let all drivers install. You should be good to go from here.
If you'd like a good known set of LGE USB drivers, download Android Flash Recovery, link is in my signature. Hope this helps.
EDIT:
Oh, and Welcome to XDA

Diagnosing USB Driver and ADB issues in Windows

Are you getting errors like "device not found" or "device offline" while trying to run ADB commands? Here's a quick way to troubleshoot your problem on Windows.
Steps
1. Ensure USB Debugging is enabled in Developer Options.
2. Verify current Google USB Driver is installed and that Device Manager is using that driver.
3. Update to latest version of ADB.
1. Ensure USB Debugging is enabled in Developer Options.
Enable Developer Options by going to Settings -> About Phone and tapping on "Build Number" multiple repeated times. You will be greeted with "You are a developer."
Now, under Settings -> Developer Options, ensure you check the box for "USB debugging."
2. Verify current Google USB Driver is installed and Device Manager is using that driver.
You may skip this step if Device Manager lists your phone as "Android Phone -> Android Composite ADB Interface." If it does not, this is likely your root cause.
Go to the Google USB Driver page and download the latest driver directly from Google. Extract the zip file to a folder you know and will remember in the future.
Open up Device Manger in Windows with your Nexus 5 connected. Whatever your Nexus 5 is currently detected as, right click on it and select Properties. Then, in the Driver tab, hit "Uninstall." If available, select "Delete the driver software for this device." and hit "OK." It will remove the old drivers.
Restart your computer.
After restarting, reconnect your Nexus 5. It should be recognized as an unknown device in the Device Manager. (If it isn't, try the previous driver deletion steps again.)
Right click on the unknown Nexus 5 device, choose Properties, and in the Driver tab again select "Update driver." Browse your computer manually by putting in the path to the new Google USB Drivers you unzipped to a folder of your choice in the beginning of this step. Choose next and your drivers should install! You'll know everything completed successfully when you see the phone listed under "Android Phone -> Android Composite ADB Interface" in Device Manager.
This is the most finicky process, so don't be afraid to reboot your computer a time or two and repeat these steps if they don't work on the first try.
3. Update to latest version of ADB.
This is a crucial step. The new version of ADB is required to work with the "USB debugging authorizations" setting.
Perhaps you know how to update ADB, in which case, just do it. However, here's a detailed manual approach to download JUST the adb suite from the SDK:
Go to the Google Android SDK website and choose "Use An Existing IDE" and click the "Download the SDK Tools for Windows." This will allow you to download only an 80 MB file rather than the whole 400 MB suite.
Install the SDK tools exe to a folder of your choosing.
Run SDK Manager and uncheck everything except for "Android SDK Platform-tools." This is the ADB and Fastboot bundle. Install that.
Navigate to your SDK Path as indicated at the top of your Android SDK Manager window. You will now see a freshly downloaded platform-tools folder containing ADB.exe, Fastboot.exe, and a host of other files. That folder is now your updated, portable ADB tools folder. You can move it anywhere you like as long as you run ADB from a command prompt window set to that directory.
After you've followed these procedures, running "ADB Devices" should trigger a prompt on your device to accept the RSA fingerprint of your computer. Accept it, and now all should be working as intended!
Questions? Ask below!

Crowd-sourced solutions.
Windows 8 Diagnosis
Yorus said:
The following worked for me, since all of the suggestions mentioned here didn't work for me:
If you use a Windows 8.1 enterprise N or KN edition, install the Microsoft Media Feature Pack :
http://support.microsoft.com/kb/2929699/en
Sounds too simple to be true but work instantly for me.
Hope it works you some of the people here looking for a solution
Click to expand...
Click to collapse
Setting up ADB and Fastboot commands to work from ANY path (credit to original author in quote).
Chromium_ said:
Setup, Preparation and Prerequisites
ADB and Fastboot Installation
Download the full Android SDK here (scroll to the bottom of the page>DOWNLOAD FOR OTHER PLATFORMS>SDK Tools Only) or get a slimmed version containing only the essential components here (Thanks @El Daddy)
Extract the zip and place the android-sdk-windows folder on the root of your hard drive. (the path should be like this: C:\android-sdk-windows)
**If you chose to download the slimmed sdk skip to step 5**
Only if you downloaded the full sdk: Go into the folder and run SDK Manager.exe. Install the following packages (there are a total of 4 packages):
- Tools > Android SDK Tools, Android SDK Platform-tools
- Extras > Android Support Library, Google USB Driver
Only if you downloaded the full sdk: Go back into the android-sdk-windows directory, and you should see a new folder named platform-tools. If not, repeat the step above.
Open a command prompt window and run "sysdm.cpl" (without the quotes) and a new window should popup. Go to the Advanced tab > Environmental Variables
Now focus your attention to the System variables box (the lower box). Scroll down and look for the Path variable > highlight it > click Edit > go all the way to the end of the Variable value text box, and paste the following entry:
Code:
;C:\android-sdk-windows\platform-tools
(OR WHATEVER PLATFORM-TOOLS DIRECTORY YOU PICKED)
Click OK then close all of the System Properties windows
You should now be able to use adb/fastboot commands no matter what location your command prompt is in. To confirm that it is indeed working, open a command prompt window and enter "adb version" (without the quotes). If it displays "Android Debug Bridge version x.x.xx" it is working. If it is gives an error saying that adb is not a recognized command, it has not been successful. Carefully repeat the steps above if this is the case.
Click to expand...
Click to collapse
The importance of being careful with your command choices.
MkVsTheWorld said:
"Be sure to use the CORRECT adb/fastboot commands, double-check the path on all commands, and double-check the existence of each file you are working with."
I hate to admit this, but I couldn't figure out why nothing was appearing in the device list when I did "adb devices", while the phone was in Fastboot. I did everything from A-Z and tore my hair out for 30 minutes until it hit me, my phone's in Fastboot. I've been messing with Android for 3+ years and made a newbie mistake lol.
Click to expand...
Click to collapse
Fixing MTP device not showing up after installing ADB drivers.
dbareis said:
I'm not sure what happened but on my WINDOWS 7 (64 bit) OS I had to modify "%WINDIR%\inf\wpdmtp.inf" as shown here: "http://forum.xda-developers.com/showpost.php?p=37930602&postcount=937". I then uninstall the device and drivers and performed a hardware scan to get it to work. I also added a "...PID_4EE2&MI_01" line but I am not positive that was required.
Hope that helps someone.
Click to expand...
Click to collapse
Whyzor said:
You should also mention what worked for me in post #16 (& confirmed by a few others in other threads). That is to toggle Settings - Storage - USB Connection type from Camera to Mass storage & also the debugging mode on & off.
Click to expand...
Click to collapse
Ashcunak said:
Op might wanna tack this onto the bottom of the main post as a last resort for folks to "start over" and be sure they have no old drivers installed.
http://www.nirsoft.net/utils/usb_devices_view.html
i had to use this program (right click run as admin if permissions are set) to remove EVERY single android related driver in order to get mine working.. turns out i had so many old ones in my system and some i couldn't remove from the device manager, the buttons wouldn't become click able..
Click to expand...
Click to collapse
CrazyIvan said:
I've tried everything and cannot get the authorization prompt to pop up on my Nexus5 so when I run adb devices the phone shows up as "unauthorized". Any suggestions? This is with updated sdk and USB drivers. Device manager shows phone as "Android Phone->Android Composite ADB Interface" and "Portable Device->Nexus 5". Tried toggling between MTP/PTP, USB Debugging on/off, stopping and starting the adb server (latest version 1.0.31).
Thanks in advance!
EDIT: Finally got the ba$tard! Run this for some adb debug logging:
adb kill-server
set ADB_TRACE=all
adb nodaemon server
Go and look back at the output from the start for any errors. In my case it couldn't mkdir in c:\users\administrator, which for me doesn't exist. I changed the Windows environment variable "ANDROID_SDK_HOME" to point to "C:\users\<my account dir>", closed the DOS window, re-ran the commands and I got prompted for the permission on my phone. Yee ha! Now I can fire up hello world with the SDK on my phone. Praise be to Google search for turning up this thread that told me about the debug logging.
Click to expand...
Click to collapse
SonicAngel said:
I just rooted my N5 (using the guide on this forum so I had no other drivers other than Google's SDK) and after unlocking my bootloader windows did not recognize my phone so I couldn't go further. Upon checking device manager I saw something called "AOSP on Hammerhead", a quick online search found a lot of very complicated answers (uninstall all drivers, restart, install adb drivers was one example).
Instead of all that I just right clicked "AOSP on Hammerhead", chose Update Driver, manually choose driver, went to "Android bootloader", chose the default driver from "Google inc" manually and that for some reason worked.
I figured this might help someone since the other solutions I found really were very long.
Click to expand...
Click to collapse
Questions? Ask below!

MaxRabbit said:
Reserved.
Questions? Ask below!
Click to expand...
Click to collapse
Hey man, thanks for the tutorial, I seem to still have trouble with this. Followed all the steps, even reset the device, to no avail. Anyone else having issues?

KTT16 said:
Hey man, thanks for the tutorial, I seem to still have trouble with this. Followed all the steps, even reset the device, to no avail. Anyone else having issues?
Click to expand...
Click to collapse
You're welcome! What shows up in your Device Manager now?

MaxRabbit said:
You're welcome! What shows up in your Device Manager now?
Click to expand...
Click to collapse
Hey thanks for the quick reply! I got it to work finally via: http://forum.xda-developers.com/showthread.php?t=2507905
Great tips and tutorial though..so stoked to have this phone!

KTT16 said:
Hey thanks for the quick reply! I got it to work finally via: http://forum.xda-developers.com/showthread.php?t=2507905
Great tips and tutorial though..so stoked to have this phone!
Click to expand...
Click to collapse
What step exactly did you take that fixed it?

MaxRabbit said:
What step exactly did you take that fixed it?
Click to expand...
Click to collapse
Open a command prompt window and run "sysdm.cpl" (without the quotes) and a new window should popup. Go to the Advanced tab > Environmental Variables
Now focus your attention to the System variables box (the lower box). Scroll down and look for the Path variable > highlight it > click Edit > go all the way to the end of the Variable value text box, and paste the following entry:
Code:
;C:\android-sdk-windows\platform-tools
Click OK then close all of the System Properties windows
You should now be able to use adb/fastboot commands no matter what location your command prompt is in. To confirm that it is indeed working, open a command prompt window and enter "adb version" (without the quotes). If it displays "Android Debug Bridge version x.x.xx" it is working. If it is gives an error saying that adb is not a recognized command, it has not been successful. Carefully repeat the steps above if this is the case.

KTT16 said:
Open a command prompt window and run "sysdm.cpl" (without the quotes) and a new window should popup. Go to the Advanced tab > Environmental Variables
Now focus your attention to the System variables box (the lower box). Scroll down and look for the Path variable > highlight it > click Edit > go all the way to the end of the Variable value text box, and paste the following entry:
Code:
;C:\android-sdk-windows\platform-tools
Click OK then close all of the System Properties windows
You should now be able to use adb/fastboot commands no matter what location your command prompt is in. To confirm that it is indeed working, open a command prompt window and enter "adb version" (without the quotes). If it displays "Android Debug Bridge version x.x.xx" it is working. If it is gives an error saying that adb is not a recognized command, it has not been successful. Carefully repeat the steps above if this is the case.
Click to expand...
Click to collapse
Ahh, your problem with my instructions then were that you weren't running ADB from inside the platform-tools folder

Definitely! I seriously got frustrated for a second and forgot how to read!
Sent from my Nexus 5 using XDA Premium 4 mobile app

Not showing up as removable storage
Hi, maybe you can help me.
Last night I unlocked my N5 using CF-Root, and flashed TWRP using Flashify. However, when I plug my N5 into my home computer it doesn't ever show up under 'My Computer' with other removable storage devices. It is present in the device manager under 'Android Phone -> Google Nexus ADB Interface'.
I've tried restrarting my computer, uninstalling the drivers and reinstalling them. Developer mode is enabled and if I switch from MTP to PTP then is shows up under removable storage, but I only have access to the DCIM folder. Switching back to MTP makes it disappear.
On my work computer it shows up correctly no problem.
My personal computer has had multiple installations of WugFresh Root toolkit and ADB/SDK files for my previous Galaxy Nexus and Nexus 7 but I uninstalled most of that before setting up the N5.
Thanks!

JonnyRock said:
Hi, maybe you can help me.
Last night I unlocked my N5 using CF-Root, and flashed TWRP using Flashify. However, when I plug my N5 into my home computer it doesn't ever show up under 'My Computer' with other removable storage devices. It is present in the device manager under 'Android Phone -> Google Nexus ADB Interface'.
I've tried restrarting my computer, uninstalling the drivers and reinstalling them. Developer mode is enabled and if I switch from MTP to PTP then is shows up under removable storage, but I only have access to the DCIM folder. Switching back to MTP makes it disappear.
On my work computer it shows up correctly no problem.
My personal computer has had multiple installations of WugFresh Root toolkit and ADB/SDK files for my previous Galaxy Nexus and Nexus 7 but I uninstalled most of that before setting up the N5.
Thanks!
Click to expand...
Click to collapse
same issue on my side...I canot use MTP only PTP...I also tryed new drivers from SDK but has not solved the problem
Alex

JonnyRock said:
Hi, maybe you can help me.
Last night I unlocked my N5 using CF-Root, and flashed TWRP using Flashify. However, when I plug my N5 into my home computer it doesn't ever show up under 'My Computer' with other removable storage devices. It is present in the device manager under 'Android Phone -> Google Nexus ADB Interface'.
I've tried restrarting my computer, uninstalling the drivers and reinstalling them. Developer mode is enabled and if I switch from MTP to PTP then is shows up under removable storage, but I only have access to the DCIM folder. Switching back to MTP makes it disappear.
On my work computer it shows up correctly no problem.
My personal computer has had multiple installations of WugFresh Root toolkit and ADB/SDK files for my previous Galaxy Nexus and Nexus 7 but I uninstalled most of that before setting up the N5.
Thanks!
Click to expand...
Click to collapse
This is a really strange problem :-/ what does it show up as when you are in device manager on your work computer?

MaxRabbit said:
This is a really strange problem :-/ what does it show up as when you are in device manager on your work computer?
Click to expand...
Click to collapse
It shows up as a 'Portable Device' -> 'Portable Media Player' (I was thinking it was a 'Device with Removable Storage').
I have full access to the internal file folders here at work.

Here's a suggestion for something to add to the OP.
"Be sure to use the CORRECT adb/fastboot commands, double-check the path on all commands, and double-check the existence of each file you are working with."
I hate to admit this, but I couldn't figure out why nothing was appearing in the device list when I did "adb devices", while the phone was in Fastboot. I did everything from A-Z and tore my hair out for 30 minutes until it hit me, my phone's in Fastboot. I've been messing with Android for 3+ years and made a newbie mistake lol.
Sent from my Nexus 5 using Tapatalk

JonnyRock said:
Hi, maybe you can help me.
Last night I unlocked my N5 using CF-Root, and flashed TWRP using Flashify. However, when I plug my N5 into my home computer it doesn't ever show up under 'My Computer' with other removable storage devices. It is present in the device manager under 'Android Phone -> Google Nexus ADB Interface'.
I've tried restrarting my computer, uninstalling the drivers and reinstalling them. Developer mode is enabled and if I switch from MTP to PTP then is shows up under removable storage, but I only have access to the DCIM folder. Switching back to MTP makes it disappear.
On my work computer it shows up correctly no problem.
My personal computer has had multiple installations of WugFresh Root toolkit and ADB/SDK files for my previous Galaxy Nexus and Nexus 7 but I uninstalled most of that before setting up the N5.
Thanks!
Click to expand...
Click to collapse
I have the same problem and done the same exact things u did. any help?

I'm having no luck with unlocking bootloader of my Nexus 5 today. I've unlocked previous Android devices fine, but this one for some reason it's not detecting it in USB drivers. It shows as Other devices -> Nexus 5 in device manager, but when I select update driver & navigate to the dir where Android SDK/extras/google/usb_driver
Windows was unable to install your Nexus 5
Windows could not find driver software for your device.
I updated the OTA that came right away earlier, maybe this caused the Windows USB drivers to not work match the updated OTA build? Is there a way to ensure that old windows driver is uninstalled? I can only select 'uninstall', but not the 'remove old driver files' some docs mention. Also when I connect my Nexus 4 it's fine, and enabling debugging mode prompts for to allow the security fingerprint of the PC. But this prompt doesn't appear on Nexus 5, not sure if it's supposed to happen AFTER the PC is able to communicate with the N5 or not, which is the step that I'm stuck on. Tried it on another Windows 7 system and same problem.
UPDATE: Well my Nexus 4 worked fine along with adb until a few minutes ago, after toggling the Debugging Mode on the phone, it's not recognized on Windows now either. So definitely think it's a Windows 7 or Google USB Driver issue. Any pointers on how to start over (without reinstalling Windows) would be appreciated.
UPDATE 2: For future reference, I got around my Windows driver issue by going into Nexus - Settings - Storage - USB computer connection, toggle to Camera (PTP) and Media device (MTP), that reinitialized windows to recognize it in Device Manager again. Stupid Windows.

aluxzen said:
same issue on my side...I canot use MTP only PTP...I also tryed new drivers from SDK but has not solved the problem
Alex
Click to expand...
Click to collapse
I'm not sure what happened but on my WINDOWS 7 (64 bit) OS I had to modify "%WINDIR%\inf\wpdmtp.inf" as shown here: "http://forum.xda-developers.com/showpost.php?p=37930602&postcount=937". I then uninstall the device and drivers and performed a hardware scan to get it to work. I also added a "...PID_4EE2&MI_01" line but I am not positive that was required.
Hope that helps someone.

Whyzor said:
UPDATE 2: For future reference, I got around my Windows driver issue by going into Nexus - Settings - Storage - USB computer connection, toggle to Camera (PTP) and Media device (MTP), that reinitialized windows to recognize it in Device Manager again. Stupid Windows.
Click to expand...
Click to collapse
That... Thankyou for that info.
I was able to get ADB to work but was not able to get the device to popup as a storage device. That fixed it. Thanks!

I'm not sure what happened but on my WINDOWS 7 (64 bit) OS I had to modify "%WINDIR%\inf\wpdmtp.inf" as shown here: "http://forum.xda-developers.com/show...&postcount=937".
Click to expand...
Click to collapse
Thanks, that link was really helpful! I struggled with the correct detection before (seems I had some old drivers for my last phone on that windows installation...)

Whyzor said:
I'm having no luck with unlocking bootloader of my Nexus 5 today. I've unlocked previous Android devices fine, but this one for some reason it's not detecting it in USB drivers. It shows as Other devices -> Nexus 5 in device manager, but when I select update driver & navigate to the dir where Android SDK/extras/google/usb_driver
Windows was unable to install your Nexus 5
Windows could not find driver software for your device.
I updated the OTA that came right away earlier, maybe this caused the Windows USB drivers to not work match the updated OTA build? Is there a way to ensure that old windows driver is uninstalled? I can only select 'uninstall', but not the 'remove old driver files' some docs mention. Also when I connect my Nexus 4 it's fine, and enabling debugging mode prompts for to allow the security fingerprint of the PC. But this prompt doesn't appear on Nexus 5, not sure if it's supposed to happen AFTER the PC is able to communicate with the N5 or not, which is the step that I'm stuck on. Tried it on another Windows 7 system and same problem.
UPDATE: Well my Nexus 4 worked fine along with adb until a few minutes ago, after toggling the Debugging Mode on the phone, it's not recognized on Windows now either. So definitely think it's a Windows 7 or Google USB Driver issue. Any pointers on how to start over (without reinstalling Windows) would be appreciated.
UPDATE 2: For future reference, I got around my Windows driver issue by going into Nexus - Settings - Storage - USB computer connection, toggle to Camera (PTP) and Media device (MTP), that reinitialized windows to recognize it in Device Manager again. Stupid Windows.
Click to expand...
Click to collapse
Thank you for sharing your solution.

Need Help with ADB

I have read many guides about setting up and using ADB, I am using an older computer with windows xp sp3. I just got my first nexus device which is a nexus 5, in device manager the phone shows up as " samsung android phone" and then "google nexus adb interface". I have tried uninstalling and then reinstalling the drivers using many different ones found on xda. I have the android sdk installed and adb seems to be working, at least when I type in "adb version" the version number comes up, but when I type "adb devices" nothing comes up as attached devices. This is really frustrating me, as I have have been trying to get this working for days now.i have already uninstalled every other android related driver using USBDeview. If anyone could please help me with this I would greatly appreciate it. I'm almost to the point go giving up! Could the problem be because I rooted the phone before getting all this setup? I ask this because when I try to update the driver in device manager it always shows driver type as clockwork mod no matter what driver I try to use

Did you enable ADB via Dev Options on the phone?

theesotericone said:
Did you enable ADB via Dev Options on the phone?
Click to expand...
Click to collapse
Do you mean USB debugging, yes I have that enabled

Go to device manager select your phone (samsung device or whatever it's showing!!) and right click and select "Update Driver Software".
On the next screen, select "Browse my computer for driver software" and set the path to : C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver"
I have used C:\Program Files (x86) because that's the place in which I have installed the SDK. Put a tick mark on "Include subfolders" and then hit Next...
Your device drivers will be installed again and adb will be working!
PS: Please make sure you have the latest android sdk and usb_driver downloaded from SDK manager!!

Database Info

welcome