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.
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.
Ok, here goes my story.
Just a week ago from the date this was posted, I decided to update my recovery (TWRP) through ROM Installer. Surprisingly, I didn't see TWRP at all in the "Recoveries" section of the application. Stock, ClockworkMod Touch, regular Clockworkmod (no touch), and unofficial Clockworkmod were available - from what I can remember. I decided to use Clockworkmod (no touch) to install Paranoid Android. Coming from OmniROM, I factory reset and flashed the .zip.
Flashing ended in error with Status 7. A while before I had used ClockworkMod Touch to try another ROM and had no such issue. I ignored the error and restarted my tablet hoping that it would still boot fine. It rebooted, gave me the Google logo for about 5-10 seconds and automatically rebooted into recovery.
I saw a bypass for Status 7. Removing some lines from the updater-script was the solution. Having no access to my Nexus 7 storage, this bypass is unusable
I tried flashing a new recovery using flashboot fastboot. After verifying that I had my drivers installed (Universal ADB by Koush), I opened up adb in the command line (Windows) as an administrator. I could not see my device. I tried the drivers from Asus, multiple USB 2.0 ports, and a different USB cord, but same results. I tried on a different computer. Still no detection.
Systems used: Windows 8.1, Windows 7 (x64), Windows 7 (x86)
I tried using Wug's Toolkit and used Flash Stock + Unroot, since it didn't need USB Debugging enabled. Same results...
I also tried plugging in another Android phone (LG Optimus Dynamic II) to see if Windows would recognize it. Windows recognized it, installed drivers automatically, and was recognized in ADB immediately. This practically unknown phone (XDA doesn't have a section for it yet) could be recognized, but my world famous Nexus 7 2012 can't be seen.
I have absolutely no idea of what to do now...
Are you on the bootloader screen when trying to use fastboot?
PrizmaticSmoke said:
Are you on the bootloader screen when trying to use fastboot?
Click to expand...
Click to collapse
Yes. Every time I use fastboot, I am in the bootloader.
I'm not new to this at all, so say whatever you need to ^^
The main problem is my PC not recognizing my Nexus 7 through adb. Again, I have used multiple cables with no success.
The computer I am using for this runs Windows 7 x64. I have only tried using USB 2.0 ports to connect my tablet.
Thank you!
Might try deleting the drivers and starting over. I had some issues with adb drivers for both the N7 and the kindle fire on windows 7 as well, but eventually got both working by doing this several times.
I'm assuming you ticked the option for softbricked when trying the flash stock option? If not try again and check that option.
This thread http://forum.xda-developers.com/showthread.php?t=1907796 has a section on driver installation with good info and links too.
Hope that helps. Best of luck man, getting the adb drivers working properly seems to be finicky sometimes in my experience, and i'm no stranger to PC and software troubleshooting either.
PrizmaticSmoke said:
Might try deleting the drivers and starting over. I had some issues with adb drivers for both the N7 and the kindle fire on windows 7 as well, but eventually got both working by doing this several times.
I'm assuming you ticked the option for softbricked when trying the flash stock option? If not try again and check that option.
This thread http://forum.xda-developers.com/showthread.php?t=1907796 has a section on driver installation with good info and links too.
Hope that helps. Best of luck man, getting the adb drivers working properly seems to be finicky sometimes in my experience, and i'm no stranger to PC and software troubleshooting either.
Click to expand...
Click to collapse
Thank you so much for all of this! I'll need all the luck I can get...
By the way, I checked that softbrick option ^^!
howdy y'all,
so im trying to help out my buddy. he currently has no os installed as well, but can boot to bootloader and twrp recovery 2.5. no idea how he has that but I figure I could just mount some zip files and be on my way. Currently whenever we try to do anything in twrp(ie wipe/mount) it is just hung up on unable to mount /radio even when all I have checked is system. I can't use adb or fastboot as far as I'm aware of; I've tried to use the unified android toolkit from skipsoft but its no dice since I was never able to turn on debug mode to begin with? So yeah any help would be much appreciated
oh and I know its not my cable or usb ports since the tablet can still charge.
Also this is the 2012 N7
Hi,
You'll need to get adb and fastboot working, best approach is to wipe and flash factory images through fastboot but may also need to use adb for e2fsck
http://forum.xda-developers.com/showthread.php?t=2277112
See this on getting fastboot working, best of luck!
demkantor said:
Hi,
You'll need to get adb and fastboot working, best approach is to wipe and flash factory images through fastboot but may also need to use adb for e2fsck
http://forum.xda-developers.com/showthread.php?t=2277112
See this on getting fastboot working, best of luck!
Click to expand...
Click to collapse
I don't understand how I'm supposed to get fastboot working since I was never able to enable debug mode on the device in the past let alone now that it has nothing installed. And from what I can understand from the instructions I need the drivers to be installed after I plug in while under debug mode for the sdk to work.
I attempted to install the nexus 7 driver from here: http://support.asus.com/download.aspx?SLanguage=en&m=Nexus+7&os=32
However it looks like I already have the files on my computer from a previous attempt with Skipsoft's Android toolkit?
Because of this I'm unsure of how to move forward with this fastboot business.
fastboot doesn't need debugging on or an os installed, just a functional bootloader
You will probably need to manually update the drivers yo the proper ones
I see, how do I go about manually installing this driver then? I'm assuming I need to go through some sort of windows device tree? Or can I just extract a file somewhere?
You can download usbdview (just search Google for a free download) to see what driver is selected when you plug in your tab easily
Or you will need to go into device manager and select to manually update the drivers, don't allow windows to select but manually choose it
There are loads of instructional videos on YouTube for you if needed
I know this is a super late response, but I never managed to get around to trying to find out how to do a manual install. Just tried today using the Nexus Root Toolkit v.1.9.9. I still can't figure out how to manual install the driver because my issue is that windows doesn't recognize anything is plugged in, and all of these guides do state that I should have had usbdebugging checked. I can't seem to find a specific guide that correlates to setting fastboot up exclusively like you mentioned.
Also, using usbdeview like you said I could see that I have installed a google nexus adb interface, a google galaxy nexus adb interface, as well as the mtp usb driver.
Sorry for all the handholding, but this really is an issue that I've never have encountered and I can't seem to manage.
Hey again
There is a fastboot guide in the first post I linked you to
If you can't get fastboot to recognize device in bootloader mode it is possible the USB port is broken, but more likely an issue with drivers, cord or PC
So try a new USB cable, or a different PC
Try try again with drivers, uninstall and reinstall
Unfortunately this type of trouble shooting is hard to do without device in hand
When I plug in my phone to my PC the only thing that happens is it begins charging. Doesn't show signs of adb working, only thing that happens beside charging is my pc says it's an Unknown Device.
I tried all sorts of things, like USB Debugging on and off, MTP on and off, PTP on and off, I think even fastboot doesn't work. I tried to install all kinds of drivers (official, unofficial, uninstalling them afterwards if they didn't work ofc), I tried Wug's toolkit, nothing. I tried killing adb server then restarting it - nope. I even tried all of my USB ports, both 2.0 and 3.0. Also tried 3 different roms/kernels (L dev preview, Purity and Mahdi), didn't work aswell.
Things seem pretty hopeless at this point :/
Download wugfresh toolkit... look In the section of driver installation... They'll help you out
Sent from my Nexus 4 using XDA Free mobile app
driver installation...
As I said, I already tried the driver thing in Wug's Toolkit. Also my Windows allows unsigned drivers.
Bump :/
monitobeko said:
Bump :/
Click to expand...
Click to collapse
If it still says Unknown Device on your PC, its a driver issue. Personally I use the Google usb driver, that page also has instructions on how to install the driver. Try uninstalling whatever drivers you have installed right now, then install Google usb driver carefully following instructions. Fastboot needs bootloader mode, so make sure your phone is in that mode before trying a fastboot command. I use the Minimal adb installer to install adb/ fastboot tools.
venu123 said:
If it still says Unknown Device on your PC, its a driver issue. Personally I use the Google usb driver, that page also has instructions on how to install the driver. Try uninstalling whatever drivers you have installed right now, then install Google usb driver carefully following instructions. Fastboot needs bootloader mode, so make sure your phone is in that mode before trying a fastboot command. I use the Minimal adb installer to install adb/ fastboot tools.
Click to expand...
Click to collapse
Fastboot actually works, only ADB doesn't. I use the Android SDK to install adb/fastboot and I tried Google USB drivers and also Universal ADB. I tried the drivers from Wug's Nexus Toolkit and then LG drivers, same old story :/
Edit: I upgraded from Windows 8 to Windows 8.1 using clean install, still same problem.
monitobeko said:
Fastboot actually works, only ADB doesn't. I use the Android SDK to install adb/fastboot and I tried Google USB drivers and also Universal ADB. I tried the drivers from Wug's Nexus Toolkit and then LG drivers, same old story :/
Edit: I upgraded from Windows 8 to Windows 8.1 using clean install, still same problem.
Click to expand...
Click to collapse
Might be windows 8/8.1 giving you driver signature grief. Try the Universal adb drivers:
http://www.koushikdutta.com/post/universal-adb-driver