Related
Hey guys,
So I'm attempting to root the nexus. I was following the instructions and put it into bootloader mode. I accidentally hit the power button while it said start at the top of the screen and it restarted. Now every time I power off and try to enter bootloarder mode it wont display the android guy. How can I bring that back up?
thanks,
Mike
try adb reboot-bootloader?
opticaldh said:
try adb reboot-bootloader?
Click to expand...
Click to collapse
my phone also isnt getting recognized by my computer now as well
hkdflip2 said:
my phone also isnt getting recognized by my computer now as well
Click to expand...
Click to collapse
try adb devices. If nothing shows up, then I think you should reinstall your driver. I used the Nexus Root Toolkit to install the driver.
After you uninstall the driver and plug in your device again, if Windows keeps installing autimatically the driver, then you should disable the Automatic Driver Update (or something named like that). I used to stuck with this Driver Update for 2 days. After I disable it, uninstall driver, then install again through Device Manager. Everything is OK now.
Cross check if USB debugging is enabled before connecting via adb. I have never used that Start option so don't know what it does apart from booting your phone.
---------- Post added at 04:23 AM ---------- Previous post was at 04:19 AM ----------
I reproduced the actions that got you the bug (selected Start from boot loader screen). But my boot loader still shows up.
Try adb bootloader
sent from my nexus 4; cat on lap, beer in hand
So i figured out most of it, im following the instructions from http://www.youtube.com/watch?v=g88PPZyvfDI however i get to the part about 11 1/2 minutes in where my phone should be rebooting once i put usb debugging on however i put it on and my phone doesn't restart and the nexus toolkit just says waiting for usb debugging to be enabled. Any suggestions
Problem: USB driver failure for Nexus 4. The android composite USB driver loads. Portable device driver (MTP) does not.
I have the latest v7 Google USB drivers in the extras 4.2.2 SDK folder, and pointing the driver install to this folder has worked in the past. Now, I never get the portable device MTP to install. I have both windows 7 and windows 8 machines that used to recognize the phone. I suspect my phone USB firmware is corrupted ( or something else software related?), but don't know how to find or make a zip file I can flash via custom recovery to test my theory.
I've tried multiple USB cables, all which have worked in the past. Simultaneously, I can only charge at USB rate. This all started occurring a week ago.
Any recommendations?
LG-E960
A different Nexus 4 connects fine, mine has no response to USB. It will charge off the PC, but no adb device found, no fastboot device found, no portable device MTP. I think something is wrong with my USB firmware on the phone.
LG-E960
Are you sure usb fast charge is not on?
User failure in this case, install these drivers from here http://forum.xda-developers.com/showthread.php?t=1998650. Delete all excisting usb drivers and then reconnect to usb and prevent/stop windows from installing drivers. Open device manager in windows and select the N4 and install the 0.72 drivers and you`re done.
gee2012 said:
User failure in this case, install these drivers from here http://forum.xda-developers.com/showthread.php?t=1998650. Delete all excisting usb drivers and then reconnect to usb and prevent/stop windows from installing drivers. Open device manager in windows and select the N4 and install the 0.72 drivers and you`re done.
Click to expand...
Click to collapse
I'm having the same problem, ADB, MTP none of it works, I've tried every method including yours. Worst part of it is that nothing happens in the device manager when i plug in Nexus 4 so i can't update drivers manually too. It used to work great with both MTP, ADB etc. Stopped working all of a sudden...Help please anyone. The phone is pretty much useless without MTP or ADB for me.
I too,, have tried to clear all old drivers and use the universal driver, but nothing works. I went through the tedious windows 8 advanced startup to allow unsigned drivers.
LG-E960
This sucks. I still cant resolve this, and 4.3 is coming. Maybe I'll try Ubuntu.
Sent from my Nexus 4 using Tapatalk 4 Beta
Still sucks
LG-E960, Tapatalk b4
Problem with Nexus 4
Any updates about this?
I'm going through the same thing with my Nexus 4.
No response to USB, except charging.
No ADB, No Fastboot, No MTP nothing at all, it's as if the system detects only a device that uses power from the USB port and nothing else.
---------- Post added at 03:31 PM ---------- Previous post was at 03:27 PM ----------
muzicfreako said:
I'm having the same problem, ADB, MTP none of it works, I've tried every method including yours. Worst part of it is that nothing happens in the device manager when i plug in Nexus 4 so i can't update drivers manually too. It used to work great with both MTP, ADB etc. Stopped working all of a sudden...Help please anyone. The phone is pretty much useless without MTP or ADB for me.
Click to expand...
Click to collapse
Any updates about this?
I'm going through the same thing with my Nexus 4.
Adeelx said:
Any updates about this?
I'm going through the same thing with my Nexus 4.
No response to USB, except charging.
No ADB, No Fastboot, No MTP nothing at all, it's as if the system detects only a device that uses power from the USB port and nothing else.
---------- Post added at 03:31 PM ---------- Previous post was at 03:27 PM ----------
Any updates about this?
I'm going through the same thing with my Nexus 4.
Click to expand...
Click to collapse
It was a hardware problem at my end. My nexus 4 wasn't detected at all in any computers.
muzicfreako said:
It was a hardware problem at my end. My nexus 4 wasn't detected at all in any computers.
Click to expand...
Click to collapse
I still have the same problem as you.
LG-E960
Resolved
muzicfreako said:
It was a hardware problem at my end. My nexus 4 wasn't detected at all in any computers.
Click to expand...
Click to collapse
It was the same with my phone. Wasn't detected on other computers too.
Here's what led to the problem resolution (kinda):
1. Formatted /system, /data, /cache, and flashed CM 10.1.2: http://get.cm/get/jenkins/34261/cm-10.1.2-mako.zip
2. Restarted the phone, then I came upon this forum post which mentioned that Trickster MOD Kernel Settings should be used to test for fast charge.
3. To install Trickster Mod I had to have Play Store (and thus the GApps package), so I rebooted into recovery.
4. After flashing the GApps package and rebooting the phone got detected and I was back in business.
5. Immediately flashed the factory image JDQ39 (it was the one I had available at the time.
6. Received the 4.3 OTA update about an hour ago and the phone is again back to not functioning on USB.
(Worth mentioning here that before this fiasco started, I was on CM 10.1.2, linked above.)
-- Update --
Rebooted a few times, phone appears on USB now and is there consistently, I'm beginning to think this is a hardware issue but I cannot apply for a warranty claim until the problem is consistent enough.
I've been having the same problem the last few weeks. I am on v4.3 stock. The phone is not being detected in any computer i've tried. I've used several USB cords and none of them work. The phone can be charged, but only in USB mode, so charging is slow, even when using AC charger.
I think this problem was triggered by charging on a cheap car charger. The Nexus 7 also can get into this state from what i've been reading.
I haven't come across a fix yet, so I think I'm going to RMA it before the warranty runs out.. its to bad though, I think this is a software problem related to 4.3. I used a lot of cheap chargers without this problem coming up before upgrading to 4.3.
Just go to storage settings and just try uncheck and re check the option of USB connection . It worked !! for me
Sent from my Nexus 4 using XDA Premium 4 mobile app
krishnan.sri92 said:
Just go to storage settings and just try uncheck and re check the option of USB connection . It worked !! for me
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Tried that. I also replaced the USB flexible circuit card ($25 amazon) and nothing changed. I'm glad their are people like xDA member, enfrant, that provides zip files for updating the phone, else I'd be stuck with a non- updateable nexus 4, which would be a nightmare for a flash junkie.
LG-E960
Very basic step but I've seen it being missed before:
- Go to Settings
- Storage
- Menu > USB computer Connection
- Check Media Device(MTP)
If this was not checked, checking it will make your computer download the necessary drivers if not present already.
MTP not detected Nexus4
jigarbond said:
Very basic step but I've seen it being missed before:
- Go to Settings
- Storage
- Menu > USB computer Connection
- Check Media Device(MTP)
If this was not checked, checking it will make your computer download the necessary drivers if not present already.
Click to expand...
Click to collapse
Hi There, i faced same problem. No matter what i did, still my XP could not detect my Nexus 4 storage. ( I must have deleted all drivers..samsung..nexus..android..from my device Manager when trying to install Nexus driver with WUGs Nexus Toolkits.) .BEST solution.."Restore System " to the date when everything was running fine.....walla.........problem solved:good::good::good:
krishnan.sri92 said:
Just go to storage settings and just try uncheck and re check the option of USB connection . It worked !! for me
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank you very much - it worked for me as well!
My laptop won't recognize my nexus 7. It's running Windows 7. I looked up possible solutions on Google and none really worked. Help?
Sent from my Nexus 7 using Tapatalk HD
Which ones did you try?
danvee said:
Which ones did you try?
Click to expand...
Click to collapse
I tried using a different cord, plugging the cord into different USB ports, rebooting the device as well as reinstalling the drivers.
Then you haven't tried everything yet
A different computer? (will verify if it's the computer)
Uninstalling all USB drivers then reinstalling them?
Watching what happens in Device Manager when you plug in?
Switching debugging mode on or off on N7?
danvee said:
Then you haven't tried everything yet
A different computer? (will verify if it's the computer)
Uninstalling all USB drivers then reinstalling them?
Watching what happens in Device Manager when you plug in?
Switching debugging mode on or off on N7?
Click to expand...
Click to collapse
One of those options, I held off on since I was confused on how to exactly do it.
I can't really use a different computer because I'm trying to move around 15 GB of music located on the laptop I'm trying to get to recognize the Nexus 7 ..and the other computer is damaged lol.
The second option is what I was confused on. How would I go about doing this?
I'll try the third and fourth now.
I switched to USB debugging and it installed some drivers again. "Google Nexus 7 ADB Interface Installed" It said this when before I turned on USB Debugging. Still doesn't show up as a drive if it's supposed to.
You need the other computer long enough to verify if the N7 is Ok.
You're not going to be transferring stuff.
Just a diagnostic step. Any computer running XP-8 will do.
I'd do that before playing with the drivers. You've got to have access to another computer somewhere for 3-4 minutes.
USB Driver Uninstall :
http://www.faqforge.com/windows/uninstall-usb-drivers-on-windows-7/
http://www.sevenforums.com/tutorials/165554-usb-driver-general-fix-problems.html
http://www.petri.co.il/removing-old-drivers-from-vista-and-windows7.htm
Google will turn up others, but these should get you there.
---------- Post added at 05:05 PM ---------- Previous post was at 05:01 PM ----------
It should show up as an MTP device.... http://android-ios-video-tips.com/how-to-transfer-files-to-your-google-nexus-10-nexus-7-from-pc/
I tried uninstalling drivers through device manager before and installing them by connecting the tablet back into the computer and still nothing.
Should the Nexus 7 ADB thing be showing up under SAMSUNG Android Phone? (edit)
*Edit again*
I got it to work by checking "Delete Driver Software" when uninstalling the drivers from Device Manager. It's not showing up under SAMSUNG Android Phone anymore but I think that's because I havent connected my s4 yet. Thanks for the help!
Not unusual.
Another interesting link.... http://forum.xda-developers.com/showthread.php?t=2213688
---------- Post added at 05:18 PM ---------- Previous post was at 05:17 PM ----------
Idkwts said:
I tried uninstalling drivers through device manager before and installing them by connecting the tablet back into the computer and still nothing.
Should the Nexus 7 ADB thing be showing up under SAMSUNG Android Phone? (edit)
*Edit again*
I got it to work by checking "Delete Driver Software" when uninstalling the drivers from Device Manager. It's not showing up under SAMSUNG Android Phone anymore but I think that's because I havent connected my s4 yet. Thanks for the help!
Click to expand...
Click to collapse
I was just going to add that sometimes 'delete' is preferable to uninstalling.
---------- Post added at 05:19 PM ---------- Previous post was at 05:18 PM ----------
Glad it all worked out. :thumbup:
Idkwts said:
I tried uninstalling drivers through device manager before and installing them by connecting the tablet back into the computer and still nothing.
Should the Nexus 7 ADB thing be showing up under SAMSUNG Android Phone? (edit)
*Edit again*
I got it to work by checking "Delete Driver Software" when uninstalling the drivers from Device Manager. It's not showing up under SAMSUNG Android Phone anymore but I think that's because I havent connected my s4 yet. Thanks for the help!
Click to expand...
Click to collapse
Have you tried looking under my computer and seeing if it shows up there? On my friends laptop it doesn't show on bottom but shows up under my computer.....idk this would help but danvee listed everything I could think
Idkwts said:
I tried uninstalling drivers through device manager before and installing them by connecting the tablet back into the computer and still nothing.
Should the Nexus 7 ADB thing be showing up under SAMSUNG Android Phone? (edit)
*Edit again*
I got it to work by checking "Delete Driver Software" when uninstalling the drivers from Device Manager. It's not showing up under SAMSUNG Android Phone anymore but I think that's because I havent connected my s4 yet. Thanks for the help!
Click to expand...
Click to collapse
I had a similar problem.
My Nexus 2013 LTE model was connecting perfectly but using the same port the 16 GB version was not able to show up.
Checked the device manager and it did appear under Samsung Android device. Deleted the drivers and got them to install again after connecting.
Now the Nexus 7 appears under portable device and works perfectly.
Thanks for the idea
I have the same problem
idkwts said:
my laptop won't recognize my nexus 7. It's running windows 7. I looked up possible solutions on google and none really worked. Help?
Sent from my nexus 7 using tapatalk hd
Click to expand...
Click to collapse
can someone help me, i have try everything in different laptops different usb, but nothing seems to work, please someone help me
Hi,
I tried a lot of other rooting applications and have had no luck with any of them. Then I found Wug's Nexus Root Toolkit. It works for my Nexus 4 (Jelly Bean 4.3) - until I came to the "Full Driver Configuration Guide" - where it gives a message: "ADB device was not found".
I have tried it over several times to no avail. Can anyone offer any clues as to what may be causing this?
btw, I am running the Wug's Nexus Root Toolkit v1.7.2 on Windows 8.
Thank you,
David
I was just having the same problem, and I realized after a while that I was making the STUPID mistake of not noticing that my phone was asking me to confirm USB debugging when the toolkit started searching for ADB devices. If you're as big of a dummy as I am (or just having an off day), this may be your problem
aaronwebstey said:
I was just having the same problem, and I realized after a while that I was making the STUPID mistake of not noticing that my phone was asking me to confirm USB debugging when the toolkit started searching for ADB devices. If you're as big of a dummy as I am (or just having an off day), this may be your problem
Click to expand...
Click to collapse
I am having the same problem. Where/how does the phone ask you to confirm USB debugging? It asks me when I turn it on, but not again later.
I have tried 3 or 4 different drivers, but, although the device is recognised by Windows 8, it is not recognised by Root Toolkit.
.... toolkits are the the devil...
They promote not learning what you're doing or what's actually happening in your devices so... there's posts like this.
please read this thread before touching your device
studacris said:
.... toolkits are the the devil...
They promote not learning what you're doing or what's actually happening in your devices so... there's posts like this.
please read this thread before touching your device
Click to expand...
Click to collapse
I'm not quite sure how this was supposed to help. My problem is that the ADB drivers do not seem to work on my computer. I have just tried installing the Android SDK (which comes with its own ADB drivers), having first uninstalled all the existing drivers. It did not help.
Not entirely sure where to go from here.
PDAnet's drivers may work. Simply install PDAnet (after uninstalling any previous attempted driver installations) to get the drivers.
studacris said:
PDAnet's drivers may work. Simply install PDAnet (after uninstalling any previous attempted driver installations) to get the drivers.
Click to expand...
Click to collapse
I had installed PDANet from within Root Toolkit, and it didn't work. Just now, I uninstalled everything again, and installed PDANet from their web site. Still get no ADB device in Root Toolkit. [NB I didn't have PDANet on the phone, but it seems to be there now]
I tried running adb from the android SDK, and it says "error: device not found".
However, I noted there was an adb prompt on the phone when I first plugged it in, this time (which I told to always accept).
[Later]
Wierd - it is now a bit further on. This is what I did:
Started PDANet on the phone, and enabled USB tethering.
Started PDANet on the computer, and it connected to the phone. At this point the USB debugging permission thing came up again, and I accepted it (also ticking the box to always accept).
Unticked USB tethering on the phone again.
Stopped PDANet on the computer (right click on icon, exit).
Tried the Root Toolkit again (pressed Root button), it connected to the device, and put it into fastboot mode.
The boot loader appeared on the phone, and the computer said "Checking Fastboot Status".
It seemed to stay like that for ever.
Killed the root toolkit. and tried again.
Left the computer for a while, and when I came back, it had completed.
So, it seems to be working now.
And when you try using fastboot directly instead of the toolkit....... what happens?
changing MTP to camera in USB connection mode did it for me...with MTP it showed correctly in device manager but the toolkit didn't recognise it
Gesendet von meinem Nexus 4 mit Tapatalk 4
studacris said:
And when you try using fastboot directly instead of the toolkit....... what happens?
Click to expand...
Click to collapse
I type "fastboot reboot" at the command prompt.
It replies "< waiting for device >"
I wait a few minutes.
Then I press ^C and the command prompt returns.
P.S. Changing the USB connection to camera doesn't make any difference to the above.
Best idea i didnt notice too
aaronwebstey said:
I was just having the same problem, and I realized after a while that I was making the STUPID mistake of not noticing that my phone was asking me to confirm USB debugging when the toolkit started searching for ADB devices. If you're as big of a dummy as I am (or just having an off day), this may be your problem
Click to expand...
Click to collapse
Thanx !!!!!!!
cmajetic said:
changing MTP to camera in USB connection mode did it for me...with MTP it showed correctly in device manager but the toolkit didn't recognise it
Gesendet von meinem Nexus 4 mit Tapatalk 4
Click to expand...
Click to collapse
Thank you so much! This solved it for me :good:
nikkilocke said:
I type "fastboot reboot" at the command prompt.
It replies "< waiting for device >"
I wait a few minutes.
Then I press ^C and the command prompt returns.
P.S. Changing the USB connection to camera doesn't make any difference to the above.
Click to expand...
Click to collapse
I got stuck the same way.
The way to got around was to change connection to camera -> the PC is intalling some drivers,
then turn off the USB debugging -> the PC is again installing some drivers,
then turn on the USB debugging -> "bingo" adb mode recognized by the toolkit
Now I can install and enjoy Kikat 4.4.1 :good:
cmajetic said:
changing MTP to camera in USB connection mode did it for me...with MTP it showed correctly in device manager but the toolkit didn't recognise it
Click to expand...
Click to collapse
I found the same solution, changing over from MTP to CAMERA suddenly had the toolkit recognise the phone and could boot it to unlock then root it... Previously, I had installed PDA drivers...
I am astonished how PATHETIC nexus phones/tablets are at simply connecting to a PC. I am baffled at the attempt by google to make their devices as UN-plug & play friendly as possible... bizarre! I have a N10, N7 and have had two N5's and all have the same PITA random disability....
grrr...
Mark.
So the Nexus toolkit is able to see the Nexus 7 as a media device but not Windows ?
marcelin99 said:
I got stuck the same way.
The way to got around was to change connection to camera -> the PC is intalling some drivers,
then turn off the USB debugging -> the PC is again installing some drivers,
then turn on the USB debugging -> "bingo" adb mode recognized by the toolkit
Now I can install and enjoy Kikat 4.4.1 :good:
Click to expand...
Click to collapse
So the Nexus 7 toolkit is able to see the Nexus 7 as media device with this method, but not Windows ? That's strange because Windows is supposed to see your files within the Nexus via Mtp mode. Is it that google removed the ability for Windows to be able to see Nexus 7 files in Android kit kat 4.4.2. What should I do then if I simply want to view files inside Nexus as a non root user ? B.T.W I'm currently on stock kitkat 4.4.2 build KOT49H. Therefore, I'd gladly appreciate it if anyone out there would answer this question and thanks in advance. Feel free to PM me on this so we can "talk" about this. : )
cmajetic said:
changing MTP to camera in USB connection mode did it for me...with MTP it showed correctly in device manager but the toolkit didn't recognise it
Gesendet von meinem Nexus 4 mit Tapatalk 4
Click to expand...
Click to collapse
Success.
Well, mtp connection works perfectly fine in my Windows 7 machine. But on my xp machine I could never get it to work no matter what driver combination I used.
I can see the reason they changed to mtp but I found mass storage to be much more user friendly.
Sent from my Nexus 4 using XDA Free mobile app
as others, I was using WUG kit to get back to stock. I was stuck without USB degugging options. Installing PDAnet did the trick, installing drivers so that I was able to get WUG working. I am now stock. All traces on my tinkering are gone. Later this week I will upgrade to a Galaxy Mega and trade in my Galaxy Nexus that I have loved for 3 plus years.
Stuck on fastboot screen
GranPaSmurf said:
as others, I was using WUG kit to get back to stock. I was stuck without USB degugging options. Installing PDAnet did the trick, installing drivers so that I was able to get WUG working. I am now stock. All traces on my tinkering are gone. Later this week I will upgrade to a Galaxy Mega and trade in my Galaxy Nexus that I have loved for 3 plus years.
Click to expand...
Click to collapse
Hi
Happy New Year to all! unfortunately I am left with the unusable nexus 7 that happened last night.
I was going crazy with the lags with lollipop and was waiting for the 5.0.5 update OTA but the delay was making me go crazy so I decided to take the risk of manually flashing the image using ADB and SDK.
Like many others pointed, I knew how to enable my computer to see my device by switching from MTP to PTP mode from my earlier rooting experience with Samsung, HTC and others. So that was not an issue for me.
I was following a tutorial from androidcentral and half way through I went to check a tutorial on youtube which I think caused the disaster. After I executed the adb devices no devices were detected and like I said I went and changed the MTP mode to off and bingo now my device was detected.
I executed device unlock and currently my device is in unlocked bootloaded state which is displayed in the fastboot screen where I am stuck now. Following the youtube instead of flashing each separately bootloader first and then the factory image I jumped to 'flash-all.bat' command...I saw something say on my command prompt on pc that completed in so many seconds or minutes which led me to get anxious and since no rebooting happened on the device I went and manually tried to press the power button.
From that time I am stuck on the fastboot screen. I can cycle through 'power off', restart booloader, recovery mode and start. But when I select 'restart bootloader' it comes to 'start' in the same mode and when I select that I can see a tiny 'Booting failed' in white letters in tiny fonts on the top left side of the 'Start'. I cannot go past this state.
Since I know the last time I had enabled 'usb debugging' and MTP off before everything went wrong I am presuming those states are still intact. I can see status on 'reboot bootloader' screen that my bootloader is unlocked.
Now, when I try to go through the process again my device is seen in device manager but when I send 'adb devices' command it cannot detect any devices. If my device is usable I can atleast go into settings to see if my MTP state and usb debugging status. Now I don't have that option. I even tried the Nexus Root Toolkit - everything is fine but until it tests the driver to finally say 'ADB device not found'.
After browsing so many posts I spotted there were some posts that said there is some discrepancy between the device id as listed by the driver to what actually is usb.inf, which all is too technical and overboard for me. And finally left me thinking that it is some issue of Windows PC as someone pointed that the ADB device was detected on a MAC. So I am now thinking to give it a shot in a mac machine as a final attempt to recover my device.
Anyone please suggest a solution, apologies if this is covered by someone elsewhere in the forum if so please point me there. I will make sure that from next time I will never do a manual flash of factory image.
please help!
It sounds like you are on top of it, but haven't hit the right combination yet. Thanks for the quote and I am sorry I am unable to offer any help. As mentioned in my post, I have switched to the Galaxy Mega and was pleasantly surprised by the OTA upgrade to 4.4. Now I am trying to figure out how to root it.
Hey,
today I tried to flash stock android 4.4.2 via WugFresh Nexus Root Toolkit. The rom was installed without a problem. But when I tried to root my nexus 4 with the toolkit, I've checked USB-debugging and plugged it to my PC (windows 8.1) but there was no question for the RSA fingerprint on my device, then I startet ADB to see if it can identify my N4 but, nope. So I used the toolkit to reinstall the N4 driver. But the problem was stilll there. Then I tried another reinstall of the driver. But then I had another problem: I could only connect my device for charging, in the device manager from windows was nothing to see that my nexus was connected. After a long time of charging, windows opened a ballon with the message: unknown device and in the device manager was an unknown device listed in USB-controller with the error code 43.
I've tried different things:
-plugged in another PC (windows 7, windows 8.1, Xubuntu)
-used different USB-Ports
-different USB-cable
If anyone has an idea, how I'm able to connect my Nexus to my PC again please tell me.
Ask if you need another information.
Cewar said:
Hey,
today I tried to flash stock android 4.4.2 via WugFresh Nexus Root Toolkit. The rom was installed without a problem. But when I tried to root my nexus 4 with the toolkit, I've checked USB-debugging and plugged it to my PC (windows 8.1) but there was no question for the RSA fingerprint on my device, then I startet ADB to see if it can identify my N4 but, nope. So I used the toolkit to reinstall the N4 driver. But the problem was stilll there. Then I tried another reinstall of the driver. But then I had another problem: I could only connect my device for charging, in the device manager from windows was nothing to see that my nexus was connected. After a long time of charging, windows opened a ballon with the message: unknown device and in the device manager was an unknown device listed in USB-controller with the error code 43.
I've tried different things:
-plugged in another PC (windows 7, windows 8.1, Xubuntu)
-used different USB-Ports
-different USB-cable
If anyone has an idea, how I'm able to connect my Nexus to my PC again please tell me.
Ask if you need another information.
Click to expand...
Click to collapse
http://answers.microsoft.com/en-us/...cognised/6a2a5531-8b80-4798-9aa6-ee2dcb705c7f
Sent from my Nexus 7 (2013)
---------- Post added at 05:29 AM ---------- Previous post was at 05:28 AM ----------
http://forum.xda-developers.com/showthread.php?t=1766475
Sent from my Nexus 7 (2013)
---------- Post added at 05:29 AM ---------- Previous post was at 05:29 AM ----------
http://forum.xda-developers.com/showthread.php?t=2588979
Sent from my Nexus 7 (2013)
thank you for your reply
but it didn't solve my problem, but I've forgotten to write that even if my nexus is identified as unknown device, there is no message on the nexus that it is connected to the pc. (sorry that I forgot about it)
In my opinion there is something wrong with my N4.