Database Users

Stuck installing TWRP w/ Kindle Fire Utility 0.9.1

Here's what I'm seeing...I've restarted the Kindle 4 times now and nothing is happening.
Any ideas?
Here's a link the pic : img18.imageshack.us/img18/6505/image1cb[dot]png

What are you seeing on your Kindle now? Are you in fastboot (Yellow Triangle with fire)?

I don't have FireFireFire installed. Basically I ran the Kindle Fire Utility and did a Permanent Root (after I unrooted using BurritoRoot)...and then ran latest install of TWRP....and everytime it gets to the actually instal part...I see that screen....
and when I restart my kindle (like it says to do in Kindle Fire Utility) it just restarts normally and then goes to USB connected screen.

Steps:
1. Download this .img for twrp.
2. Place it in the adb folder. (where ever you have to cd to)
3. Do the following commands:
adb shell
su
idme bootmode 4002
reboot
4. Download fastboot and place it in the adb folder and do:
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
5. Enjoy your newly added recovery.

I'm now stuck in fastboot (yellow triangle with fire)
I tried to just press the power butter to load into recover but it didn't work.
I tried adb reboot, but it says no device is found...
Any ideas?
Edit: I saw a post that I need to re-install the drivers?
Which one:
Image: img809.imageshack.us/img809/7474/image3si[dot]png

did you do
idme bootmode 4000
to get it to boot normal?

adb commands arent working....do i need to reinstall the drivers? if so which one...it gives me three choices...
ADB interface
Bootloader Interface
Composite ADB Interface...
I'm assuming once I get adb commands working again...then I can use idme bootmode 4000 to get into regular boot mode again.
Edit: I tried chaning to Normal boot with Kinde Fire Utility...didn't work...
Really wondering if I should reinstall the drivers and try agian...but the KFU doesn't really seem to be playing nice with my device.

Not to say KFU is bad but I never used it. If you started with the directions that came with twrp we might not need so many topic about twrp help.

I just ran into the same problem!
ADB and fastboot commands don't work for me too, and I also tired to reinstall the drivers and still didn't work..
edit: try using KFU on another computer, and then changing to normal boot!
that seemed to work for me!

try to uninstall old/faulty drivers:
disconnect kf and use:
http://support.microsoft.com/kb/315539/en-us
connect KF and select the last installed driver (which you installed by running "install_drivers.bat") manually (check the date/time on selection)

Yeah, the KFU has just been a headache for me.. I finally got it working though, i have to use burrito root everytime I want to do anything after a reboot in KFU, but it works perfectly fine after that. Make sure you have good drivers installed under android phone also! Don't use the install_drivers.bat from KFU, just caused me more headaches...

i used the drivers from kfu - but after a cleanup - that seems to be the point
the difference is they are te only ones with entries for device 18D1 you'll nedd in fastboot mode or you can add the entries to your drivers under "kindle" or "kindle fire" or what it is called in your android_winusb.inf:
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0100
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0100&MI_01

Well I was assuming they used a root method that already had them set up their own driver files etc. already.

no they don't - they try to provide drivers that are working in every bootmode - i've made corrections in the driver installer script for non english os which vashipooh implemented off ver. .9 - i have also device 18D1 in my adb_usb.ini - if it helps ? - but there's no downside

Maybe I'm just too tired (its 4:30 AM here) But I don't understand what you said... And the current version of KFU has a bad install_drivers.bat, it replaces the mass USB storage driver and it made my ADB stop working...

i think it don't replace the mass storage driver, it just reinstalls it - that's not they'r fault - it's the tool they are using from microsoft (devcon) to update existing drivers - devcon seems to be working this way - good or not ? - who know's ?

Wait, are you talking about the most current 9.1 or 9.0? Because 9.0 works fine, the new 9.1 kills USB storage, and for me ADB which kind of destroys the point.

9.0 - will download 9.1 and take a look - perhaps i can help to sort the problems out and contact vashi to correct the issue - thanks for the hint !!!

No problem, haha I knew there was something missing in that conversation, hope you guys can figure it out!

tec2030 said:
adb commands arent working....do i need to reinstall the drivers? if so which one...it gives me three choices...
ADB interface
Bootloader Interface
Composite ADB Interface...
I'm assuming once I get adb commands working again...then I can use idme bootmode 4000 to get into regular boot mode again.
Edit: I tried chaning to Normal boot with Kinde Fire Utility...didn't work...
Really wondering if I should reinstall the drivers and try agian...but the KFU doesn't really seem to be playing nice with my device.
Click to expand...
Click to collapse
Here is how to manually install the drivers step by step.. If you think you may have a problem with the drivers that you have on your computer it would be smart to get download another .android folder and put it on the root of your c:drive just to be sure that nothing is wrong with it before you attempt this
- Go to start Menu and right click on computer, Click manage
- In computer Management hit device manager
- I am guessing that you see your kindle connected in there with a yellow ! by it
- Right click on kindle and update driver software
- Click Browse my computer for driver software
- Click let me pick from the list of device drivers on my comp
- Click Next
- Click Have Disk
- Click Browse
- Navigate to your user folder in that window/ or wherever your .android folder is
- Double click on .android folder
- Double click on Driver Folder
- Now Click open
- Now click ok
- Click Next
- ClickInstall driver software anyway
Hope that helps..!

[Q] Windows ADB USB drivers?

After enabling USB debugging on my Nexus 7, I still can't get "adb devices" to list my Nexus 7. I also tried switching its USB connection type from "media" to "camera", to no effect. I have Windows 7; I see a "Nexus" device under Other Devices in my device manager, but when I try to install the Google USB drivers from the Android SDK, Windows refuses to take it.
This is going to make development difficult Anyone know where I can find working USB drivers for Windows 7?

beandog said:
After enabling USB debugging on my Nexus 7, I still can't get "adb devices" to list my Nexus 7. I also tried switching its USB connection type from "media" to "camera", to no effect. I have Windows 7; I see a "Nexus" device under Other Devices in my device manager, but when I try to install the Google USB drivers from the Android SDK, Windows refuses to take it.
This is going to make development difficult Anyone know where I can find working USB drivers for Windows 7?
Click to expand...
Click to collapse
If you have updated the drivers from the SDK, then your problem is probably coming from the cable.
PS: Try not to use an extension cable

When I have had this problem in the past I have found that installing PDA net solves it.
Sent from my Galaxy Nexus using Tapatalk 2

download a sync software,for example,chinese use 360 mobile assistant,it will help you to connected with PC
Sent from my SHW-M190S using xda premium

i got the problem too,just install 360 mobile assistant ,it worked.but i dont know ,any mobile assistant
used in your city？
Sent from my SHW-M190S using xda premium

You may try to use device manager to solve the issue.:
Firstly please connect your Nexus 7 to you computer using the USB cable
included in the box.
Then on the tablet,
choose "Settings" -> "Storage" -> open the menu -> choose "USB computer connection" -> choose "MTP" or "PTP".
On your computer,
1. Control Panel -> Hardare and Sound -> View devices and printers
2. Click on Nexus.
3. Click on "Hardware" tab
4. Click on "Properties"
5. Click on "Change settings"
6. Click on "Driver" tab
7. Click on "Update drivers".
I'd suggest that you repeat these steps for both "MTP" and "PTP" connection types mentioned above.
Then on your computer, run "adb devices", the Nexus 7 would be listed in the
output of the adb command.
Enjoy.

Works with PTP mode - MTP mode doesn't
just for future reference...
By default it uses the MTP mode for USB. ADB is not working in this mode, even after i follow all the steps in above post.
Change it to use PTP (Camera mode), and ADB works !! go figure.

driving me crazy too.
First, windows did not recognize the thing in AdB mode. I managed to get around that with PDA net. But in cmd mode running "fastboot oem unlock" it just sits there saying "waiting for device". Also switched to both usb modes under "storage" as well as tried all usb ports on my pc (running Win 7 64bit). Using original cable.
Any other clues on what to do next?

bytecollektr said:
driving me crazy too.
First, windows did not recognize the thing in AdB mode. I managed to get around that with PDA net. But in cmd mode running "fastboot oem unlock" it just sits there saying "waiting for device". Also switched to both usb modes under "storage" as well as tried all usb ports on my pc (running Win 7 64bit). Using original cable.
Any other clues on what to do next?
Click to expand...
Click to collapse
ADB and fastboot may have two different drivers, this is the case with most other devices.
Anywho here's a link to the all inclusive driver bundle. Drivers was one of the reasons I only use a linux distro these days.

Unlawful said:
ADB and fastboot have two different drivers.
Anywho here's a link to the all inclusive driver bundle. Drivers was one of the reasons I only use a linux distro these days.
Click to expand...
Click to collapse
Still nothing. Deleted the drivers, and it obviously installed the new ones, since the name under the "device manager" changed. I go to the Android sdk and it still says waiting for device. Is there different versions of fastboot? Maybe its the wrong command? (fastboot oem unlock)

reddweb said:
just for future reference...
By default it uses the MTP mode for USB. ADB is not working in this mode, even after i follow all the steps in above post.
Change it to use PTP (Camera mode), and ADB works !! go figure.
Click to expand...
Click to collapse
This is how i got my ADB drivers to actuallly work right!! listen to this guy.

Nexcellent said:
This is how i got my ADB drivers to actuallly work right!! listen to this guy.
Click to expand...
Click to collapse
I have it in that mode, and it does not do anything, even with the new drivers.

bytecollektr said:
I have it in that mode, and it does not do anything, even with the new drivers.
Click to expand...
Click to collapse
Oh and fastboot is not available during normal operations and it has to be booted into the bootloader to use fastboot. Try using adb reboot bootloader and then when it restarts fastboot oem unlock.

I'm in the exact same situation
I'm having the same problem. I'm not exactly sure how to use the Naked Drivers pack. Can someone advise?

Easy as ADB...
Use the step by step instructions in the Nexus Root Toolkit found here;
http://forum.xda-developers.com/showthread.php?t=1766475
Hope that helps,
-CC

Set it to ptp mode, install updated sdk, and you will find proper adb driver in extras/google/usb-driver directory. After those steps adb started to work in my case' no need for third party downloads.
Sent from my Nexus 7 using xda app-developers app

I've been having the same issues with all of the new android devices I've tried to use adb on my computer for. I as able to make them work by manually installing the drivers in device manager. When you choose browse for drivers manually you can look through pre installed drivers and select adb interface and manually choose the drivers for adb and fast boot. Only issue I have is that it won't give adb root access and says rot is not available in production builds. Not sue if that's related or not.
Sent from my Nexus 7 using xda app-developers app

Windows 7 - Nexus 7 ADB Recognition
For me, like others, choosing either MTP or PTP from the Nexus 7's USB computer connection options didn't solve the issue. Updated to the latest version of the Android SDK Tools within Eclipse [version 20.0.1], and even uninstalled and re-installed the Google USB Driver [Revision 6] within the Android SDK manager, but no luck.
What ended up clearing the issue for me was to go to Computer Management, find the Nexus device with the question mark next to it, update the driver by browsing a location on the computer, browse to the location on your computer where you saved the Android SDK [the one with the following directories: add-ons, docs, extras, platforms, platform-tools, etc], and choose that very folder containing those folders I mentioned. It should search for a while then ask you whether or not to install some Asus/Google driver.
After installing that driver, my N7 was recognized by the "adb devices" command.
NOTE: Turns out when I updated the driver, my N7 was in PTP mode, and when I switched it to MTP mode, it was no longer recognized under adb devices. adb kill-server then adb start-server should get it recognized again when you switch between MTP and PTP.
Hope this works for all of you out there, like me, who really didn't want to take the 3rd party software route to overcome this problem.
Cheers.

ADB driver
Try to root toolkit from Wugfresh
http://forum.xda-developers.com/showthread.php?t=1766475
There is a very complete and usable guide to install ADB driver for most version of windows (XP->win 7).
You don't have to unlock or root; just use the interactive guide for driver install.
Good luck
bytecollektr said:
Still nothing. Deleted the drivers, and it obviously installed the new ones, since the name under the "device manager" changed. I go to the Android sdk and it still says waiting for device. Is there different versions of fastboot? Maybe its the wrong command? (fastboot oem unlock)
Click to expand...
Click to collapse

rootblock said:
For me, like others, choosing either MTP or PTP from the Nexus 7's USB computer connection options didn't solve the issue. Updated to the latest version of the Android SDK Tools within Eclipse [version 20.0.1], and even uninstalled and re-installed the Google USB Driver [Revision 6] within the Android SDK manager, but no luck.
What ended up clearing the issue for me was to go to Computer Management, find the Nexus device with the question mark next to it, update the driver by browsing a location on the computer, browse to the location on your computer where you saved the Android SDK [the one with the following directories: add-ons, docs, extras, platforms, platform-tools, etc], and choose that very folder containing those folders I mentioned. It should search for a while then ask you whether or not to install some Asus/Google driver.
After installing that driver, my N7 was recognized by the "adb devices" command.
NOTE: Turns out when I updated the driver, my N7 was in PTP mode, and when I switched it to MTP mode, it was no longer recognized under adb devices. adb kill-server then adb start-server should get it recognized again when you switch between MTP and PTP.
Hope this works for all of you out there, like me, who really didn't want to take the 3rd party software route to overcome this problem.
Cheers.
Click to expand...
Click to collapse
i'm having the issue with the mtp not being recognized in adb. can you be more specific in the adb kill-server and adb start-server.

Getting ADB to work on Windows 8? (Manual upgrade to Android 4.2)

Hi guys,
I currently have a problem with my ADB which doesn't seem to work with Windows 8. I set up everything as I did on Windows 7 before (including Environment Variables), but the ADB doesn't detect my Nexus 7 (List of devices attached is empty)
I think it might be a driver issue (see the screenshot attached). I also tried it with my HTC One X and it doesn't detect it either.
Does anyone have any idea how to get it to work? My devices are both unrooted and locked.
I wanted to install the upgrade to Android 4.2 for the N7.
Hopefully somebody can help me.
Thanks in advance!
EDIT:
I btw also tried the Nexus 7 Toolkit from here and I also installed the Google Drivers through Android SDK.
When trying to install the drivers through Nexus 7 Toolkit the following error occurs:
Installing Windows 7 Drivers Please wait
Operation Started
android_winusb.inf
The resource loader cache doesn't have loaded MUI entry.
1
0
An Error Occured. Returning to Main Menu.
---------------------------------------------------------------------------------
If you got the message [the resource loader cache doesn't have loaded mui entry]
during the installation procedure dont worry as the drivers have been installed.
Click to expand...
Click to collapse

PCServe said:
Hi guys,
I currently have a problem with my ADB which doesn't seem to work with Windows 8. I set up everything as I did on Windows 7 before (including Environment Variables), but the ADB doesn't detect my Nexus 7 (List of devices attached is empty)
I think it might be a driver issue (see the screenshot attached). I also tried it with my HTC One X and it doesn't detect it either.
Does anyone have any idea how to get it to work? My devices are both unrooted and locked.
I wanted to install the upgrade to Android 4.2 for the N7.
Hopefully somebody can help me.
Thanks in advance!
EDIT:
I btw also tried the Nexus 7 Toolkit from here and I also installed the Google Drivers through Android SDK.
When trying to install the drivers through Nexus 7 Toolkit the following error occurs:
Click to expand...
Click to collapse
Do you have Android SDK installed?, if so try the following, you're using Windows 8, right?
On the 'old' Windows Desktop, right-click on the bottom left corner
> Select 'Command Prompt (Admin)'
> type ' devmgmt.msc '
> Right click on the driver with warning sign and select update driver > select BROWSE and go to the extras\google\usb_driver\ folder of your SDK and then update the driver. Did that resolve the issue?

It works for the Nexus 7 when it's running, not in fastboot though

PCServe said:
It works for the Nexus 7 when it's running, not in fastboot though
Click to expand...
Click to collapse
Have you rebooted the PC since installing the drivers?, if not give that a go and try again, they may need a reboot to complete the installation.

Yes, I tried to restart the computer as well as the tablet several times. When the system is running on the N7, the drivers are detected and everything works fine, even ADB. But in fastboot it shows the warning sign in Device Manager and when I try installing the drivers either from the SDK Google Drivers or the Nexus 7 Toolkit drivers it says
Windows was unable to install your Nexus
Windows could not find driver software for your device.
If you know the manufacturer of your device, you can visit its website and check the support section for driver software.
Click to expand...
Click to collapse
I also tried the drivers from ASUS with the same result.

PCServe said:
Yes, I tried to restart the computer as well as the tablet several times. When the system is running on the N7, the drivers are detected and everything works fine, even ADB. But in fastboot it shows the warning sign in Device Manager and when I try installing the drivers either from the SDK Google Drivers or the Nexus 7 Toolkit drivers it says
I also tried the drivers from ASUS with the same result.
Click to expand...
Click to collapse
Did you try browsing to the driver location instead of letting Windows find the driver?
This driver has helped others
http://forum.xda-developers.com/showthread.php?t=1766220

PCServe said:
Yes, I tried to restart the computer as well as the tablet several times. When the system is running on the N7, the drivers are detected and everything works fine, even ADB. But in fastboot it shows the warning sign in Device Manager and when I try installing the drivers either from the SDK Google Drivers or the Nexus 7 Toolkit drivers it says
I also tried the drivers from ASUS with the same result.
Click to expand...
Click to collapse
turn off driver signing and then do it.Mine works fine in Windows 8..check this for reference:-
http://forums.mydigitallife.info/th...ble-driver-signature-enforcement-in-Windows-8

Thanks, using unsigned drivers worked perfectly
Device Manager says I have a Galaxy Nexus though, but patching the update worked anyway!
Thanks alot!

PCServe said:
Thanks, using unsigned drivers worked perfectly
Device Manager says I have a Galaxy Nexus though, but patching the update worked anyway!
Thanks alot!
Click to expand...
Click to collapse
Glad to be of help

Need adb side load " device not found" fix

I'm trying to update my phone using adb side load and it keeps saying device not found. Adb works until I get into recovery. I'm also running windows 8. Any ideas?
Sent from my Nexus 4 using xda app-developers app

handman29 said:
I'm trying to update my phone using adb side load and it keeps saying device not found. Adb works until I get into recovery. I'm also running windows 8. Any ideas?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Go into device manager and install the ADB driver for the now unknown device.

I have the exact same problem, i used the driver that SDK manager downloaded.
In device manager its called "Android Composite ADB Interface"
but when i reboot Nexus 4 into recovery mode, windows does not recognize the device..

Update adb.exe to the latest version (from sdk) , connect and allow to use PC with ADB in android for the first time, then it should work in recovery also
Adam

I did that, still doesn't work
Sent from my Nexus 4 using xda app-developers app

handman29 said:
I did that, still doesn't work
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Install the naked drivers (found here on xda). And if sideload isn't recognized, your SDK is not up to date.

OK maybe my drivers..do you know if they work on windows 8
Sent from my Nexus 4 using xda app-developers app

Side load is recognized but adb can locate my device in recovery
Sent from my Nexus 4 using xda app-developers app

handman29 said:
Side load is recognized but adb can locate my device in recovery
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Did you select the adb option in recovery? If you did, then your drivers are not installed.

same problem here, i just downloaded SDK now, and the first thing i did was to use SDK manager to update the USB driver..
it does work when Nexus is booted in normal mode, but not in recovery.
i guess this is a windows 8 driver issue.
tried to install the driver from this thread:
http://forum.xda-developers.com/showthread.php?t=2019273
but it will not even install in windows 8

So there are different drivers for fast boot and recovery?
Sent from my Nexus 4 using xda app-developers app

I did a driver test from all in one tool kit and all the drivers work just not in adb recovery
Sent from my Nexus 4 using xda app-developers app

I had the same problem, on Windows 8, but while your device is in recovery, go to Device Manager, and choose 'Let me pick from a list of device drivers...', there you will see something like 'Android ADB device'. Install that, and voila! your device will now be recognized in recovery mode.
Sideloaded 4.2.2 on my N4 last night.

ravneetg said:
I had the same problem, on Windows 8, but while your device is in recovery, go to Device Manager, and choose 'Let me pick from a list of device drivers...', there you will see something like 'Android ADB device'. Install that, and voila! your device will now be recognized in recovery mode.
Sideloaded 4.2.2 on my N4 last night.
Click to expand...
Click to collapse
On my computer, the device is not even listed in device manager while in recovery mode, so there is no device to update..
wierd.

same issue here; I tried to do it in linux (linux doesn't need any driver), using the latest adb (I downloaded the sdk this morning) but still nothing: Error device not found

I was having the exact same problem and the below steps, posted by a member in reply to my problem, solved my problem-
I downloaded the nexus 4 drivers from this link- http://forum.xda-developers.com/showthread.php?t=1992345
mashedbymachines said:
Had the same problem.
Right click the "nexus 4" with the yellow exclamation mark.
Go to the details tab
Choose "hardware id"
you will see something like
USB\VID_18D1&PID_D001
USB\VID_18D1&PID_D001&REV_0228
Open your folder with the usb_driver
edit the android_winusb.inf
depending on if you use 32/64 bit, navigate to
for 32 bit
[Google.NTx86]
xxxxxx
;Google Nexus (generic)
xxxx
for 64 bit
[Google.NTamd64]
xxxxx
;Google Nexus (generic)
xxxx
Add these two lines
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_D001
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001&REV_0228
Be sure that the text after "USB_Install" matches what you had on your hardware id tab in device manager.
Now try to install these drivers and voila, it should install and work under recovery!
Click to expand...
Click to collapse

if you are still having issues, definitely try the naked drivers. I couldn't get other drivers including the SDK ones to detect my phone that is in recovery/sideload mode. The naked ones worked right off the bat.

whatsandroid said:
On my computer, the device is not even listed in device manager while in recovery mode, so there is no device to update..
wierd.
Click to expand...
Click to collapse
Adb won't be recognized in stock recovery until you choose the sideload option.
Adb access recovery wide is a custom ROM feature.
Sent from my Nexus 4 using xda premium

El Daddy said:
Adb won't be recognized in stock recovery until you choose the sideload option.
Adb access recovery wide is a custom ROM feature.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
OK, did not know that.
but still getting the same error message as the OP when i try to sideload.
and adb devices is not showing any devices, should adb devices work on a device with stock while in recovery?
also tried that "naked" usb driver that someone posted

whatsandroid said:
OK, did not know that.
but still getting the same error message as the OP when i try to sideload.
and adb devices is not showing any devices, should adb devices work on a device with stock while in recovery?
also tried that "naked" usb driver that someone posted
Click to expand...
Click to collapse
Did you try the method which I posted? I was having the same exact problem.
ADB devices should work while in recovery.

[Q] ADB not showing device

Hi, my problem is this: my phone is recognized as an ADB device but I cannot see it under adb devices.
Currently running PA RC2 3.99
Fastboot and Recovery do recognize it but ADB does not.
I have the drivers from here installed them as described in the instructions with uninstalling + deleting the old ones and rebooting.
I also have the most updated version of ADB from Android SDK.
One weird thing is that if i uninstall + delete the current drivers and try to install the ones i got from the SDK and not from the thread I mentioned then it does not install them. So maybe that is where my problem...
Any advice??
Thanks in advance.

akrabi said:
Hi, my problem is this: my phone is recognized as an ADB device but I cannot see it under adb devices.
Currently running PA RC2 3.99
Fastboot and Recovery do recognize it but ADB does not.
I have the drivers from here installed them as described in the instructions with uninstalling + deleting the old ones and rebooting.
I also have the most updated version of ADB from Android SDK.
One weird thing is that if i uninstall + delete the current drivers and try to install the ones i got from the SDK and not from the thread I mentioned then it does not install them. So maybe that is where my problem...
Any advice??
Thanks in advance.
Click to expand...
Click to collapse
Did you enable usb debugging?

Also check that you have an option selected under Settings>Storage>USB Computer connection, not having either MTP or PTP selected there will also bork adb.

If you still can't get it to work, try Koush's universal drivers: Link

still not working...
1. Yes, usb debugging is on.......
2. Already tried toggling MTP/PTP/None - When on MTP driver installs successfully but I cannot see the device under adb devices. on the other two options (PTP/None) I am unable to install the driver (tried both the ones on XDA and the ones from MDK)
3. Tried Koush's universal driver - on PTP/None still not able to install drivers. On MTP didn't do much except for changing device name from Android ADB Device to Google Nexus ADB Interface
Thanks for all the quick replies,
Any other suggestions???

akrabi said:
1. Yes, usb debugging is on.......
2. Already tried toggling MTP/PTP/None - When on MTP driver installs successfully but I cannot see the device under adb devices. on the other two options (PTP/None) I am unable to install the driver (tried both the ones on XDA and the ones from MDK)
3. Tried Koush's universal driver - on PTP/None still not able to install drivers. On MTP didn't do much except for changing device name from Android ADB Device to Google Nexus ADB Interface
Thanks for all the quick replies,
Any other suggestions???
Click to expand...
Click to collapse
what does it say when you issue the "adb devices" command? Please write it out here so we can help you. Does it say "device offline"? If yes, then your device is not registered by digital fingerprint by Android SDK.

taodan said:
what does it say when you issue the "adb devices" command? Please write it out here so we can help you. Does it say "device offline"? If yes, then your device is not registered by digital fingerprint by Android SDK.
Click to expand...
Click to collapse
Ok, so I'm with my Nexus connected as an MTP device, with the driver from XDA installed (see attached image), USB Debugging enabled:
Code:
C:\>adb kill-server
C:\>adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\>adb devices
List of devices attached
C:\>

Any advice???
Anyone has any advice??
I really have not idea what to do. Tried everything...
Thanks

Works on a different computer
I've connected the phone to my borther's PC and installed the drivers from the SDK. It worked without any problem.
I really can't figure out why it's not working on my laptop.

[Solved]
OK...
So as I said before I tried connecting when PTP is checked and when neither PTP nor MTP are checked and on both couldn't install the drivers properly (neither from xda nor from sdk).
What worked for me:
1. Uncheck both PTP & MTP
2. Device Manager -> Nexus 4 -> Update Driver Software -> Browse my computer for driver software
3. Now instead of browsing to the location I went to "Let me pick from a list..."
4. It should show a list of devices/manufacturers. Clicked "Show All Devices"
5. On the bottom right click "Have a disk"
6. Point to the android_winusb.inf file from Android SDK
7. Choose Android ADB Interface from the list
8. Let driver install
Click to expand...
Click to collapse
Hoped it will help someone.
Thanks to everyone that tried to help. :good: