Related
I have a Google Nexus 4, bought direct from Google, I rooted it and it was working well for a while. Then the battery started draining super fast. A friend recommended resetting, so I did and it seemed to fix it for a while. Then the battery issue came up again, so I reset again, expecting the same outcome....however, I wiped the phone completely. It turns on and displays Google, and that's it.. My computer does not recognize the phone when I plug it in, and I cannot get the USB Debugging to even be an option. Every resolution I have found for this situation needs me to enable the USB Debugging mode. Is there any other way to get all the OS files back on this phone or is it bricked?
When I plug it into the PC it tells me to look up drivers, and this is how it sees my phone: Unidentified Device USB\VID_0CF3&PID_3000&REV_0200.
It isn't recognized as a phone at all. It tells me to download Atheros Drivers.
I have searched for days trying to find the solution to this. Any help would be so very appreciated by this noob
Did you try to manually delete drivers from the device manager? Ticking the option that permanently delete the driver from PC.
And after doing this...trying Windows Update for driver installation?
PS: also try to manually flash with Fastboot all the latest Factory Image from Google....
Sent from my Nexus 4 using Tapatalk 4 Beta
thesebastian said:
Did you try to manually delete drivers from the device manager? Ticking the option that permanently delete the driver from PC.
And after doing this...trying Windows Update for driver installation?
PS: also try to manually flash with Fastboot all the latest Factory Image from Google....
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yes, I've done that, there are currently no drivers on my PC. When the phone is plugged into the PC, it tells me to find drivers because it is an unrecognized device.
MrsWhitey said:
I have a Google Nexus 4, bought direct from Google, I rooted it and it was working well for a while. Then the battery started draining super fast. A friend recommended resetting, so I did and it seemed to fix it for a while. Then the battery issue came up again, so I reset again, expecting the same outcome....however, I wiped the phone completely. It turns on and displays Google, and that's it.. My computer does not recognize the phone when I plug it in, and I cannot get the USB Debugging to even be an option. Every resolution I have found for this situation needs me to enable the USB Debugging mode. Is there any other way to get all the OS files back on this phone or is it bricked?
I have searched for days trying to find the solution to this. Any help would be so very appreciated by this noob
Click to expand...
Click to collapse
Hold volume up/down and power until it reboots into boot loader mode. Download the factory images from the Google website (search nexus stock images on Google) and plug your phone into the computer and use fastboot to flash the OS back.
Rember, as long as you can get the phone to turn on you can fix whatever other issue your having providing its software related.
To fastboot flash,
You need the android SDK, use Google to figure out how to install it but its not hard.
Run the flash-all bat found in the archive file you downloaded, or manullay flash each partition like this.
fastboot flash [partition] [.IMG name]
Sent from my Nexus 4 @1.944 GHz on Stock 4.2.2
IRX120 said:
Hold volume up/down and power until it reboots into boot loader mode. Download the factory images from the Google website (search nexus stock images on Google) and plug your phone into the computer and use fastboot to flash the OS back.
Rember, as long as you can get the phone to turn on you can fix whatever other issue your having providing its software related.
To fastboot flash,
You need the android SDK, use Google to figure out how to install it but its not hard.
Run the flash-all bat found in the archive file you downloaded, or manullay flash each partition like this.
fastboot flash [partition] [.IMG name]
Sent from my Nexus 4 @1.944 GHz on Stock 4.2.2
Click to expand...
Click to collapse
I am having trouble getting the phone to accept anything from the PC...
MrsWhitey said:
I am having trouble getting the phone to accept anything from the PC...
Click to expand...
Click to collapse
Download the toolkit and install the drivers
Sent from my Nexus 4 @1.944 GHz on Stock 4.2.2
yea download Google Nexus 4 ToolKit install drivers then you can factory restore using the toolkit to restore
i think i chose option 9 and it downloaded the need restore image
Tried it all
I have tried all those ideas and all have failed. I can never get the computer to see my device. All it says is unknown device. When I click update drivers and direct it to the sdk driver I download it still gives me no connection through fastboot or adb. I have tried selecting various general Android drivers through the update drivers screen, Found some from Google Inc. that specify Nexus 4 bootloader interface and adb interface. Nothing is working. I think I need to have a working Nexus 4 to install to correct drivers first and then I might be able to piggy back off those and use my phone to flash through fastboot or push adb. I have worked with both command lines with reasonable success before rooting samsung tablets and phones and htc's. I am familiar with the process and have read numerous ideas none of which seem to work in this case. Made it all the way to Google search page 12. Anyone know a way to force install the Nexus 4 drivers without having a working phone present? I am thinking I just need to go buy a new one and return it after I plug it in to install drivers. Don't want to have to pay the re-stock fee though. Any other ideas are very welcome.
And I have tried to use the toolkit as well and it does nothing either. I have the stock rom ready to go just need a way to get it onto the phone.
I took the OTA to 4.3 on my Nexus 7. It was previously unlocked and rooted, but had no kernels, etc changed. After the update ran, I lost root as expected, however, in trying to get it back, I've discovered I'm having a couple of other issues.
First, the device is no longer working properly via USB on my PCs. On both my Win 7 and Win 8 PCs, the device won't properly connect to where I can browse files or anything else. On the Win 8 computer, I see a Nexus 7 device in Device manager, but drivers won't install. I downloaded the drivers from the Asus site, but trying to manually install them doesn't work on the Win 7 machine, and on the Win 8 machine, they install but don't seem to be working with the Nexus 7 as it still shows a problem in Device Manager.
The tablet also will not boot into recovery mode. I can power it up into fastboot mode, but if I select "Recovery Mode" and hit the power button, I just got the Android with the red triangle for a few minutes before it boots back into the OS. After doing some searching, I saw where you might need to have it plugged into a PC to get it to go into recovery, but that doesn't work, either (might be tied to the USB problem).
Ideas?
Did you turn on developer options, and USB debugging? Have you tried USB connection type PTP instead of MTP?
If you have the stock recovery, the red triangle and Android are normal. You can bring up a blue options menu by pressing the power and volume up buttons from the red triangle Android.
Sent from my rooted Nexus 7 @ 49.4 mpg
exglynco said:
Did you turn on developer options, and USB debugging?
Sent from my rooted Nexus 7 @ 49.4 mpg
Click to expand...
Click to collapse
Yes.
Try another driver source. Wugfresh's installation is a lot tougher than Skipsoft's, but try the other guy 's system.
Sent from my rooted Nexus 7 @ 49.4 mpg
exglynco said:
Try another driver source. Wugfresh's installation is a lot tougher than Skipsoft's, but try the other guy 's system.
Sent from my rooted Nexus 7 @ 49.4 mpg
Click to expand...
Click to collapse
I was using the stock drivers off the Asus page. I'll look around for the two you mention. I assume they're posted on here somewhere.
And about the recovery just try flashing another recovery from fastboot
Code:
fastboot flash recovery recovery.img
Sent from my Nexus 7
Red Devil said:
And about the recovery just try flashing another recovery from fastboot
Code:
fastboot flash recovery recovery.img
Sent from my Nexus 7
Click to expand...
Click to collapse
Without USB access? That's my dilemma.
OK, I'm getting closer. I got TWRP installed and rerooted it. I had to do the "Revoke USB debugging authorizations" on the Dev Options screen. Then it would work via ADB.
Still not browsing files yet on my desktop, but at least I know I'm talking to it. So now I'll play with the driver installation a bit.
EDIT: Well, drivers reinstalled for about the 4th time, and it's still not allowing me to browse files from my desktop. Galaxy S4 works fine as soon as I plug it in, even if I also uninstall it's drivers. Ideas? I obviously have it working over USB because I can give it commands and reboot it via the PC.
OK, try this one. Plug in your tablet to pc, go to hardware manager, find your Android Device then choose Uninstall (choose Remove all drivers for this device), unplug and plug in your tablet again. Your Windows should discover few new devices (mine has discovered three) and download drivers for them then you should see Android ADB Interface in Android Devices and Nexus 7 in Mobile Devices.
--edit--
I've solved my issue
http://forum.xda-developers.com/showthread.php?p=44322739#post44322739
Already been done that road multiple times.
have the same problem except one thing: no one 3 computers don`t detect my nexus. have no reaction in device manager, on connection nexus as mtp/debug/fastboot. Only usb-otg works.
xxut said:
have the same problem except one thing: no one 3 computers don`t detect my nexus. have no reaction in device manager, on connection nexus as mtp/debug/fastboot. Only usb-otg works.
Click to expand...
Click to collapse
After you plug your nexus in have you unlocked the screen to see if it is asking you to authorize the tablet?
What other steps have you taken? Have you installed proper drivers? Have you manually chosen to update drivers with the sdk drivers if in device manager is showing the nexus? Have you tried the drivers from Asus?
Sent from my Nexus 7 using Tapatalk 4 Beta
SlowCobra96 said:
After you plug your nexus in have you unlocked the screen to see if it is asking you to authorize the tablet?
What other steps have you taken? Have you installed proper drivers? Have you manually chosen to update drivers with the sdk drivers if in device manager is showing the nexus? Have you tried the drivers from Asus?
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I personally did all of those things. After having the Nexus "forget" all the other PC authorizations on the dev screen, I finally got it to accept ADB commands, just not to properly install drivers that would allow me to browse files like it had done on 4.2.
SlowCobra96 said:
After you plug your nexus in have you unlocked the screen to see if it is asking you to authorize the tablet?
What other steps have you taken? Have you installed proper drivers? Have you manually chosen to update drivers with the sdk drivers if in device manager is showing the nexus? Have you tried the drivers from Asus?
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Nexus doesn`t appears in device manager. At all. It starts to charage, but no reaction in device manager, no any reaction(except charging) at nexus. On computer it looks like i didn`t connect anything. I`ve trying to intall drivers as legasy hardware, but nothing changes. Sorry for my english.
xxut said:
Nexus doesn`t appears in device manager. At all. It starts to charage, but no reaction in device manager, no any reaction(except charging) at nexus. On computer it looks like i didn`t connect anything. I`ve trying to intall drivers as legasy hardware, but nothing changes. Sorry for my english.
Click to expand...
Click to collapse
Try turning off usb debugging. My tablet cannot connect to pc but with usb debugging off it at least recognises tablet as a media device and this enables me to view its files
.but still the problem of not being able to root
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 guys any help or suggestions will be greatly appreciated on this matter. I will try to be as detailed as possible but I'm trying to fix this phone for a friend and he isn't very phone savvy. From what I understand, he was previously on CM10 and tried updating to CM11 using the cmupdater. For some reason it failed and he was stuck in TWRP. When he tried to reboot it kept kicking him back to recovery. He took his phone to a phone repair shop who then wiped his device. At this point he gave me the phone to try to fix.
First of all I have working fastboot and adb drivers for my Nexus 5 so I don't think this is a driver issue but I'm no expert on the Nexus 4 so I could be wrong. I'm also running Windows 8.1 if this is any relevance.
I can still access the devices bootloader (ver MAKOZ20i)
I can still access TWRP (ver 2.6.0.0)
When plugging the device into my USB 2.0 ports, nothing shows up in my device manager in bootloader, TWRP, or TWRP ADB sideload.
When plugging the device into my USB 3.0 ports, I see 'Unknown USB Device (Device Descriptor Request Failed)' and the Device Instance Path is 'USB\VID_0000&PID_0002\7&20F39B9B&0&2' in bootloader, TWRP, or TWRP ADB sideload.
I've never heard of a device not being seen at all in by USB 2.0 ports but showing using USB 3.0 ports so I attempted to give extra juice to the phone using a powered USB OTG cable. Still nothing shows up.
I've tried running 'fastboot device' and 'adb devices' with no luck.
I think I've covered all the bases... can anyone think of anything that could help me re-install a new rom or factory reset or his he out of luck?
I think it may be a Win8 problem. You have access to another machine with Win7 or WinXP?
Install "universal driver.exe" in win7, than connect phone while power off, I think it'll install driver...than push any custom ROM to phone via adb or just flash any official IMG..
Well I can tell you WHY it didn't work. That version of TWRP is not able to install 4.4 (CM11). if you manage to successfully push via adb and get it started again, make sure to flash the newest version of TWRP before trying that again.
Thanks for the reply guys. I kind of guessed that the version of TWRP was not compatible as I installed CM11 on my old Nook Tablet and had to update my recovery before installing it. Unfortunately the guys who wiped the phone prevented me from installing an old version of CM10 that my friend probably had from the cmupdater.
As for Windows 8 being the issue.. I attempted to try to use my laptop which runs Windows 7 but was unable to get anything to happen. Since the laptop only had USB 2.0 ports, plugging in the device to any of the ports did the exact same thing as what it did on my desktop (Windows doesn't even recognize anything is connected). I still get the charge animation on the phone but yea... nothing in device manager. I'm thinking of running Linux from a live installation to see if anything different happens, unfortunately its been ages since I've touched Linux so this is kind of a last ditch effort here.
Any other thoughts?
mrlazyone said:
Thanks for the reply guys. I kind of guessed that the version of TWRP was not compatible as I installed CM11 on my old Nook Tablet and had to update my recovery before installing it. Unfortunately the guys who wiped the phone prevented me from installing an old version of CM10 that my friend probably had from the cmupdater.
As for Windows 8 being the issue.. I attempted to try to use my laptop which runs Windows 7 but was unable to get anything to happen. Since the laptop only had USB 2.0 ports, plugging in the device to any of the ports did the exact same thing as what it did on my desktop (Windows doesn't even recognize anything is connected). I still get the charge animation on the phone but yea... nothing in device manager. I'm thinking of running Linux from a live installation to see if anything different happens, unfortunately its been ages since I've touched Linux so this is kind of a last ditch effort here.
Any other thoughts?
Click to expand...
Click to collapse
One more, when you plug into usb 3.0 you can see unknown device Right ??
If yes, download driver files from here Here.
It's a zip contains .inf files, Now click on unknown device and select update drivers then give the path to these drivers manually.
Hope this will help you out.
I'm pretty convinced at this point that the phone can't be fixed by me. Running it through Ubuntu I can't see the device at all (USB 2 & 3) when running the lsusb command but it sees my nexus 5 just fine. I even tried modifying drivers to match vendor id product id and class id as reported by windows. Thanks for the suggestions. Does anyone know of a reputable service to get this phone repaired? How much does a JTAG repair usually cost?
Sent from my Nexus 5 using XDA Premium 4 mobile app
mrlazyone said:
I'm pretty convinced at this point that the phone can't be fixed by me. Running it through Ubuntu I can't see the device at all (USB 2 & 3) when running the lsusb command but it sees my nexus 5 just fine. I even tried modifying drivers to match vendor id product id and class id as reported by windows. Thanks for the suggestions. Does anyone know of a reputable service to get this phone repaired? How much does a JTAG repair usually cost?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The following method may still help
http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060
DrFredPhD said:
The following method may still help
http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060
Click to expand...
Click to collapse
Awesome! Didn't realize this was an option. It didn't work using the USB 3.0 ports but the USB 2.0 actually worked for this method. Thank you!
Help!! I wiped out my os on my Nexus trying to load a ROM. I can't figure out what to do. If I boot the phone it stays on a screen that says google. Everything I have found so far says to check USB debugging but I can't get to that because the phone doesn't fully boot. Also my computer is not showing my phone in windows explorer but does show a nexus device in devices and printer & device manager. As far as I can figure I have to somehow get the computer to communicate w/the phone and then load an operating system but can't seem to figure out how to do this. I can get to TWRP but find nothing there to help. What ca I do?
You need to use adb to push or side load a rom to your device while you're booted into recovery
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
You need to use adb to push or side load a rom to your device while you're booted into recovery
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks. Thats what I am thinking but my device won't show in windows explorer, so I don't see away to communicate w/it. I have tried installing the device drivers but all I have now is it showing up in Device Manager as Google Nexus BootLoader Interface.Right now I am working with ADB and Fastboot and I think I have it working but I am still stuck on the drivers and the device showing up.
lol...
download WugFresh toolkit, download factory image from google, download universal ADB drivers.
enter bootloader, you should see an android with chest open, stay in bootloader and connect your phone to PC, flash ROM through Nexus 4 Tool kit.
you dont need usb debugging in bootloader
ahunter said:
Thanks. Thats what I am thinking but my device won't show in windows explorer, so I don't see away to communicate w/it. I have tried installing the device drivers but all I have now is it showing up in Device Manager as Google Nexus BootLoader Interface.Right now I am working with ADB and Fastboot and I think I have it working but I am still stuck on the drivers and the device showing up.
Click to expand...
Click to collapse
Google 15 second adb install xda. Has adb and the usb drivers. Try that. Factory image is going to wipe your device. By dirty flashing the rom you're on you'll save your data.
Sent from my Nexus 5 using XDA Free mobile app
---------- Post added at 05:09 PM ---------- Previous post was at 05:04 PM ----------
jd1639 said:
Google 15 second adb install xda. Has adb and the usb drivers. Try that. Factory image is going to wipe your device. By dirty flashing the rom you're on you'll save your data.
Edit, if those usb drivers don't work Google universal naked drivers xda
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Sent from my Nexus 5 using XDA Free mobile app
Mashed_Potatoes said:
lol...
download WugFresh toolkit, download factory image from google, download universal ADB drivers.
enter bootloader, you should see an android with chest open, stay in bootloader and connect your phone to PC, flash ROM through Nexus 4 Tool kit.
you dont need usb debugging in bootloader
Click to expand...
Click to collapse
Thanks Mashed_Potatoes. I tried Wug & Skipsoft toolkits but did not do it in bootloader mode. Hope I remember that for the next time! Still having trouble with the drivers and computer seeing the phone. In device manager should it be android device--Google Nexus ADB Interface? I just don't remember that and the phone doesn't show up in explorer, but it's listed under devices and printers. I hope I can get it. Wug toolkit gave me an error trying to install drivers. Thanks for the help
I didn't understand you, you managed to flash the ROM but not in bootloader? It won'tsay Google Nexus ADB Interface, i don't remember precisely i've done it a long time ago!
https://www.youtube.com/watch?v=a7GLJIlZzmk
try this
Mashed_Potatoes said:
I didn't understand you, you managed to flash the ROM but not in bootloader? It won'tsay Google Nexus ADB Interface, i don't remember precisely i've done it a long time ago!
https://www.youtube.com/watch?v=a7GLJIlZzmk
try this
Click to expand...
Click to collapse
I managed to re-install 4.4.4 with wug toolkit in bootloader. I got my OS back but have not been able to get the drivers sorted out (yet) so the Nexus isn't communicating w/the computer fully but I can still flash roms and install apk's w/wug also.
Try a factory reset and reinstall the drivers in PC