Database Users

having trouble with usb drivers

so i am new to android and i decided " hey why don't i try to root my nexus" so i tried and i cant get any father that checking if the computer can see my device which it cant for some reason. so i went online i figured out that i don't have the usb driver for android. so after that i tried to down load then and i even installed them and restarted my computer and it still wont work. so if any one can help me with my problem it would be greatly appreciated.

On Home Screen, press menu>settings>applications>development and make sure USB debugging is checked.

What OS you running?
Specs would help, where did you get your drivers? What other software have you tried?

i turned on the debugging and it still hasnt worked
i am running xp. i downloaded the android sdk from here
developer.android.com

i just want to put the modaco desire rom on my phone that my onl reason for wanting to root. i really like the sense ui

I am having a similar problem, so i might as well use this thread instead of creating a new one.
I have a dual boot computer, win7 and fedora, both have SDK. I unlocked my nexus one with windows, as i noticed the commands were considerably easier, or at least they don't work when i plug the linux ones into fedora.
Last night i was going to push the undervolt kernel so i plugged my n1 while in win7, It instantly came up complaining about drivers, which i had already installed and had previously worked, i went to re-install them, and windows says they are up to date, but still no luck recognising the device (Debugging mode is definately on)
So i switched to fedora, no driver pop ups obviously, but when i try to push the kernel through, it does not recognise the device.
In the bootloader it says "fastboot usb" while plugged in.
I can't pinpoint when it stopped working, but the last time i used fastboot was to put the RA recovery, since then i flashed CM 5.0.2, CM 5.0.3.1, the desire rom, and used a nandroid restore to get back to 5.0.3.1
Anyone got any ideas? Without fastboot i am pretty much restricted to flashing .zip files from the recovery.

yeah i cant even unlock mine its so frustrating

Me either. I'm coming from windows and flashed the heck out of that. The instructions seem super easy, but the darn thing wont recognize phone to root... and there is no real good instructions on the driver part. Yes USB debug is enabled... sucks cause I want that desire rom, if 10.1 is working that is...

temperbad said:
Me either. I'm coming from windows and flashed the heck out of that. The instructions seem super easy, but the darn thing wont recognize phone to root... and there is no real good instructions on the driver part. Yes USB debug is enabled... sucks cause I want that desire rom, if 10.1 is working that is...[/QUOTE
Yeah I know how you feel its so frustrating I tried all day yesterdAY too
Click to expand...
Click to collapse

drbrendin said:
temperbad said:
Me either. I'm coming from windows and flashed the heck out of that. The instructions seem super easy, but the darn thing wont recognize phone to root... and there is no real good instructions on the driver part. Yes USB debug is enabled... sucks cause I want that desire rom, if 10.1 is working that is...[/QUOTE
Yeah I know how you feel its so frustrating I tried all day yesterdAY too
Click to expand...
Click to collapse
I tried all day too like a gazillion times.... and wonder does everyone have driver issues? I tried with my XP computer and windows 7, no go, then I read posts people having the same issue, then they just post " nevermind got it" and didn't even write what they did to get it.......
Click to expand...
Click to collapse

not everyone is a dev

Ok, I have my Nexus One set up so I can use with via Windows 7 (desktop) or Ubuntu (Laptop).
The Linux part is a bit more involved, but since everyone is running Windows (unless I missed something), I will work there.
First of all, your phone needs to be in Dev mode (which was covered earlier).
With the phone UNPLUGGED from the PC, uninstall any previous SDK installs you have and be sure to remove the directory.
Then, install the SDK found here: SDK
Install this SDK and let it complete the install, which will include downloading for a bit. You need to do this since the SDK package above does NOT include the right drivers!!!
Once this has been completed, plug your phone into the computer via USB. Your computer will find a new device, however, it cannot locate the drivers for it. Browse and point the installer to:
DRIVE:\PATH_TO_android-sdk-windows\usb_driver
Don't go any further than this!!
Now, let it do it's thing and you should have a new device in the device manager called:
Android Phone
...|_Android Composite ADB Interface
Now, go to the command prompt and change to the following directory:
DRIVE:\PATH_TO_android-sdk-windows\tools
There, you will find adb.exe
Type:
adb devices
and you should see:
List of devices attached
HT019P801614 device
If not, something got screwed up and would need to dig further to help ya.

Ok ill give this a try once get home from school

nexus one root.
Ok assuming that you have the android sdk installed correctly, try rooting your phone via the superboot method. The first link below has a full detailed guide for rooting the nexus one and I believe has all of the device drivers for those who have not been able to get them running well. If you still have trouble getting the drivers working checkout the second link. Anyone who is relatively new to working with the sdk and is not familiar with working the commands check out the third link. Read the entire thread! it is very helpful.
1) http://theunlockr.com/2010/01/02/how-to-root-the-nexus-one/
2) http://forum.xda-developers.com/showthread.php?t=613217
3) http://forum.xda-developers.com/showthread.php?t=619153
If you have any questions PM me on xda. I'll try and help in anyway, it took my like two days to actually root my nexus, I wasnt familiar with using ADB and Fastboot to root.

One thing I know I was having problems with since I came from the G1 was that the new SDK has to actually be installed via an .exe now. I was used to it all being in a zip so I kept trying to load up what I thought were the right USB drivers, but they were actually the 1.6 drivers I already had. So make sure to run the .exe that comes with the SDK.

ok so while i was downloading the sdk a notification came up that said that it could not rename the directory. is this bad?

i am having an issue with installing the right driver as well. my computer keeps installing the nexus one as a "mass storage device". i have uninstalled and reinstalled a few times but no luck. i have the phone set to debug mode, using XP btw. any help would be appreciated.

[Q] Device Offline: Brand New Nexus 4, 4.2.2

So, got a replacement Nexus 4 today, and it's been updated to 4.2.2 and for some reason, it comes up as offline on ADB no matter what I do.
However, the funny thing is, my other Nexus 4, the one I was getting the replacement for, connects to ADB wonderfully. Shows up as a device, no problem. It's on 4.2.1.
Question 1: How can I manage to get the gosh darn thing to be recognized as online. I've tried two different cables, both of which connect with the 4.2.1 nexus but not the 4.2.2.
Question 2: Can I install a custom recovery without ADB?
EDIT: Consider this solved... it seems I had a bit much to drink... little did I know I don't need ADB... just fastboot.
Oh well All is well.

x3phyr said:
So, got a replacement Nexus 4 today, and it's been updated to 4.2.2 and for some reason, it comes up as offline on ADB no matter what I do.
However, the funny thing is, my other Nexus 4, the one I was getting the replacement for, connects to ADB wonderfully. Shows up as a device, no problem. It's on 4.2.1.
Question 1: How can I manage to get the gosh darn thing to be recognized as online. I've tried two different cables, both of which connect with the 4.2.1 nexus but not the 4.2.2.
Question 2: Can I install a custom recovery without ADB?
Click to expand...
Click to collapse
Is the device recognized by Windows? Checking under Computer>Properties>Device Manager does the phone show up correctly?

Use the search in the future please. Just update ADB. With 4.2.2 the phone will pop up to ask you if you want to authorize your computer to access the phone, this "feature" requires the updated ADB, no change to fastboot, so you'll be fine getting the recovery on there, but ffr with ADB.

Unlock and Root 4.2.2
h.nocturna said:
Is the device recognized by Windows? Checking under Computer>Properties>Device Manager does the phone show up correctly?
Click to expand...
Click to collapse
If you're trying to unlock and root your nexus, you can follow the steps on this forum http://forum.xda-developers.com/show....php?t=2147413 There's another way to unlock and root your device (via adb) since Wugfresh's NRT doesn't support 4.2.2. Just make sure you use the correct .img file for your specific device.
You can also update any old SDK files by opening the SDK Manager on your pc.

USSENTERNCC1701E said:
Use the search in the future please. Just update ADB. With 4.2.2 the phone will pop up to ask you if you want to authorize your computer to access the phone, this "feature" requires the updated ADB, no change to fastboot, so you'll be fine getting the recovery on there, but ffr with ADB.
Click to expand...
Click to collapse
I did use the search feature and I will have you know that the FIRST THING I DID was download and update the absolute most recent ADB so thank you, but the degrading "learn to search" comment was not applicable.
Anyhow, this whole conversation is fairly irrelevant since I got what I needed to do, done.
Thanks for the help everyone.

Mind telling me what you did, im stuck in the same situation

gsusx said:
Mind telling me what you did, im stuck in the same situation
Click to expand...
Click to collapse
same situation. whatd you end up doing?

gsusx said:
Mind telling me what you did, im stuck in the same situation
Click to expand...
Click to collapse
whocanhebe said:
same situation. whatd you end up doing?
Click to expand...
Click to collapse
Download this and replace your old adb & fastboot
http://forum.xda-developers.com/showpost.php?p=37935821&postcount=26

Have you tried entering:
adb kill server
adb start-server
Read this:
http://stackoverflow.com/questions/8162581/why-does-adb-return-offline-after-the-device-string
It worked for me. I did it last night when I had the same issue.

hiya
might be havving a blonde day but even using this my device still shows in cmd as offline when i type "adb devices"
what am i doing so horribly wrong

gsusx said:
hiya
might be havving a blonde day but even using this my device still shows in cmd as offline when i type "adb devices"
what am i doing so horribly wrong
Click to expand...
Click to collapse
if you have updated adb try killing the server with adb kill-server

EZ
Hey
Guys had the same problem and it was really simple to solve.
When you start adb and type adb devices and your device comes offline.
Go to settings>developer options - unchecked USB debugging and check it again, right after your computer will recognize your phone and in the phone will appear a box with your computer's Mac address asking you to allow connection.

gsusx said:
hiya
might be havving a blonde day but even using this my device still shows in cmd as offline when i type "adb devices"
what am i doing so horribly wrong
Click to expand...
Click to collapse
Have you downloaded the updated version of adb from post #8? And make sure you use that rather than whichever you were using? That was all I needed to do to get my offline Nexus 4 online again...

It have something to do with usb debugging not being enabled on the new phone?
Sent from my Nexus 4 using Tapatalk 2

VoiD_Dweller said:
It have something to do with usb debugging not being enabled on the new phone?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
In that case, I don't think you get the "offline" status from adb - I think it wouldn't appear at all?

It appears that the Linux SDK isn't fully updated (as of today, newest build is 0219). My adb version is 1.0.29, and from a bit of research it seems that that version cannot ask your device for the OK it needs in 4.2.2. I hope I'm wrong though...
EDIT: When I had basically given up, I re-checked one last time, and there it was on my screen; the OK. Unfortunately, I have no idea what permitted this. Let the building start. Good luck to all of you!

jotss said:
Hey
Guys had the same problem and it was really simple to solve.
When you start adb and type adb devices and your device comes offline.
Go to settings>developer options - unchecked USB debugging and check it again, right after your computer will recognize your phone and in the phone will appear a box with your computer's Mac address asking you to allow connection.
Click to expand...
Click to collapse
^ This worked for me. Thanks a lot! :good:

[Q] Screen broken, how to access my pics ?

Hi,
I broke my Nexus 4 screen so I can't do anything, the touchscreen is completely down. But the display is working.
I have bought a new Nexus 4 and I want to get my photos from the broken device. The problem is that I can't unlock the phone (pattern), so I can't access to these. USB debugging is off and the device isn't rooted.
I hope someone have a solution for me. Does any virtual touchscreen exist ?

Ghuillaume said:
Hi,
I broke my Nexus 4 screen so I can't do anything, the touchscreen is completely down. But the display is working.
I have bought a new Nexus 4 and I want to get my photos from the broken device. The problem is that I can't unlock the phone (pattern), so I can't access to these. USB debugging is off and the device isn't rooted.
I hope someone have a solution for me. Does any virtual touchscreen exist ?
Click to expand...
Click to collapse
Don't know if there is a simpler option, but this might help you:
http://forum.xda-developers.com/showthread.php?t=2433307
Not sure if adb works with usb debugging disabled though...

That has to be the Worst case scenario. Another reason I use Google drive and keep pics synced via cloud
Sent from my Nexus 4 using xda app-developers app

It's really annoying, I just need to unlock my phone but I can't !
I'm not comfortable with the idea having my pics on Google's servers, but I will find something to backup data now..
Maybe the only way is to wait the nexus to be obsolete and find a screen for a low price

Oh wait !
USB debugging is ON ! I didn't see the bean icon because there are a lot of notifications.
But I can't use adb :
$ adb shell
error: device unauthorized. Please check the confirmation dialog on your device.
Click to expand...
Click to collapse

Ghuillaume said:
Oh wait !
USB debugging is ON ! I didn't see the bean icon because there are a lot of notifications.
But I can't use adb :
Click to expand...
Click to collapse
I'm assuming that because your phone isn't rooted you don't have a custom recovery or an unlocked bootloader. Is this correct?

i know with my HTC desire i run adb, when the device is turned off and connected to PC .
i think you can try it with your N4 , there are tools to do it google it .
good luck

You can try some combination of Airdroid (older version) and adb/shell command. So you'll need your device connected and older version of Airdroid - not two, because it asks for user action to accept the connection, and the older one just gives random generated password for the user to input in their browsers.
Now, you'll need to push the apk on your phone, and then just start it from your adb shell with the following command:
am start -a android.intent.action.MAIN -n com.sand.airdroid/.Splash - this should work on the old version
am start -a android.intent.action.MAIN -n com.sand.airdroid/.SplashActivity_ this works on last airdroid
At least you can try with other app that doesn't need user interaction on their display to get into the phone memory from their browsers. You can just install them from play store.
The first time that I'm writing here in Nexus forum though I am here with my 2 old DHD for about 2 years and I hope my answer could be helpful. And now I am here because of my soon to come Nexus 4

You could try to unlock, flash CWM then "adb pull" the files from there. No need for the digitizer to get it done. Fully charge the battery before starting.

You don't need root access, just adb debugging.
For everything off your phone: adb pull /sdcard/
Done.
EDIT: If you just want your pics from your camera the command would be adb pull /sdcard/DCIM/Camera/

lopezk38 said:
I'm assuming that because your phone isn't rooted you don't have a custom recovery or an unlocked bootloader. Is this correct?
Click to expand...
Click to collapse
You don't need root to use adb.
You only need to for adb to access anything beyond the sdcard.
When you first use adb there is a pop up on the device that asks if you want to allow the pc access.
He can't use the touchscreen to confirm its ok. This is the reason after I flash a Rom hook up to my pc ASAP and have it remember my computer to allow me access if this were to happen to me.
illru said:
You could try to unlock, flash CWM then "adb pull" the files from there. No need for the digitizer to get it done. Fully charge the battery before starting.
Click to expand...
Click to collapse
HUGE reason why this won't work:
unlocking the bootloader wipes the entire device.
Which... is pointless if you're trying to recover data.

studacris said:
HUGE reason why this won't work:
unlocking the bootloader wipes the entire device.
Which... is pointless if you're trying to recover data.
Click to expand...
Click to collapse
If you flash the custom recovery immediately after unlocking (without rebooting into android in between) your data should not get wiped.

Well then... I sit here humbly corrected.

studacris said:
Well then... I sit here humbly corrected.
Click to expand...
Click to collapse
Dont worry, its not really an officially documented thing...more of just a bug with the bootloader.

Also if flashing your phone makes you nervous you could try to pull from in stock recovery but I don't know if it will work. Never played with stock recovery, it dose not last on my phone for very long.

illru said:
Also if flashing your phone makes you nervous you could try to pull from in stock recovery but I don't know if it will work. Never played with stock recovery, it dose not last on my phone for very long.
Click to expand...
Click to collapse
I dont think adb works in stock recovery. Only custom ones afaik.

[Q] Ach! Doh! I did it. I bricked my N7 while going 4.4 to 4.3

I know. You guys have heard it all before...but
I was using WugFresh to re-flash back to 4.3 from 4.4 and the recovery was taking so long. After an hour of running, I was moving the device to a coffee table when the cable fell out.
Hay, why isn't a message include in WugFresh like the backup process as to approximately how long this process takes? That brings up another issue in general with these old N7s is that these micro-USB female connectors get loose after so many years of use, makes connecting and charging difficult.
But I digress.
I have read often in the XDA forums about a factory reset ‘from bricked feature’ in WugFresh, but I can not find that feature anywhere where ‘bricked’. anything is. If it is there, where is it?
Anyway, how can I recover the bootloader and everything without having to learn doing everything via a cmd line or .bat process?
These are the facts:
Nexus 7 2012, 8g, re-flashing back to 4.3 from 4.4, using Nexus Root Kit
v1.8.2, Flash Stock + Unroot (I had read in XDA Forum somewhere where it was suggested to go back to a factory vs to use this option).
The N7 is currently has one of 4 states available: Bootloader screen (with below stated status), Google initial screen (with "Start" Showing and "Booting failed" in the upper right corner), or it can Power off. Recovery Mode is an option, but does nothing but cycles to the Google initial screen.
In Fastboot mode the status says this:
FASTBOOT MODE
Product name - grouper (it got that far)
Variant - grouper
HU version - E3
LOCK STATE - UNLOCKED
Bootloader Version - N/A
Serial Number - 015d2109ab281807
SIGNING - not defined yet
Of course I can't get an MTP connection to Microsoft XP, but an "Unknown
device" error shows up under USB when I connect the cable. No drivers from WMSDK kit or any from WugFresh worked.
Oh, and by the way, the WugFresh backup didn't work for me. It saved next to nothing, but I have another type of backup that works, so no worry.
GOT ANY SUGGESTIONS?

Looks like it will be fine follow the sticky for reflashing a factory image.
http://forum.xda-developers.com/showthread.php?t=1907796
[GUIDE] Flashing a Factory Image with fastboot / return to stock
Don't use toolkits for flashing devices just learn the adb commands its much safer. The reason there is no time for completing a flash if it varies with devices.
FYI the wugfresh option you are looking for is return to stock/unroot with soft bricked checked
Programming is a race between engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.

Captain Sweatpants said:
Looks like it will be fine follow the sticky for reflashing a factory image.
http://forum.xda-developers.com/showthread.php?t=1907796
[GUIDE] Flashing a Factory Image with fastboot / return to stock
Don't use toolkits for flashing devices just learn the adb commands its much safer. The reason there is no time for completing a flash if it varies with devices.
FYI the wugfresh option you are looking for is return to stock/unroot with soft bricked checked
Programming is a race between engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.
Click to expand...
Click to collapse
{Q} Thanks Captain, I have been following the Guide instruction, but I have some other questions before I proceed.
In your Quote above you said “follow the sticky for reflashing”, I don’t know what you mean by a “sticky” and I have looked though a lot of the pages after the "[GUIDE] Flashing a Factory Image with fastboot / return to stock" and I can not find “reflashing” mentioned yet. Did you mean to go directly to the "Flashing the Factory Image" section in the Guide and follow that?
Since I didn't know that answer, I went a head and read the whole Guide and other questions popped up: If I have to download Java SE JDK will the Version 6 I already have work? The Oracle website you directed me to won’t let me download Version 8; however, Android SDK did accept Version 6 to install.
I did re-download all the drivers as instructed and put the JWR66V bootloader into the place of the JWR66Y one and then inserted bootloader-grouper-4.23.img, image-nakasi-jwr66y.zip, flash-all.sh, and flash-base.sh all into <my sdk directory>\platform-tools as the Guide says.
Now that I think I have it all ready to go, will I still have to run the Adb cmds to install Drivers?

I don’t know what you mean by a “sticky"
Click to expand...
Click to collapse
A sticky is a thread that a mod has "stickied" meaning that it won't move down the forum but stays at the top.
I can not find “reflashing” mentioned yet. Did you mean to go directly to the "Flashing the Factory Image" section in the Guide and follow that?
Click to expand...
Click to collapse
Yes that's what I meant.
Just follow the whole guide and take it slow if you have been relying on toolkits like wugfresh this will be a not of a learning curve
Now that I think I have it all ready to go, will I still have to run the Adb cmds to install Drivers?
Click to expand...
Click to collapse
Yes you still have to install drivers you shouldn't need adb to do that just make sure windows has the correct adb and fastboot drivers installed. If you have been using wugfresh NRT the drivers should be OK.
As your device is soft bricked where the guide says use the command adb reboot bootloader you will need to manually enter the bootloader by pressing power & vol +
Sent from my C5303 using xda app-developers app

Now its Driver installation issues
Captain Sweatpants said:
A sticky is a thread that a mod has "stickied" meaning that it won't move down the forum but stays at the top. Yes that's what I meant.
Just follow the whole guide and take it slow if you have been relying on toolkits like wugfresh this will be a not of a learning curve
Yes you still have to install drivers you shouldn't need adb to do that just make sure windows has the correct adb and fastboot drivers installed. If you have been using wugfresh NRT the drivers should be OK.
As your device is soft bricked where the guide says use the command adb reboot bootloader you will need to manually enter the bootloader by pressing power & vol +
Sent from my C5303 using xda app-developers app
Click to expand...
Click to collapse
{Q} Installing the driver now seems to be the issue. I tried a couple of things:
1. I know this was not exactly appropriate, but I went into Device Manager, located the USB “Unknown Device”, tried to update
the Driver after selecting it, directed the screens to both the ‘supposed’ drivers in WugFresh and Adb subdir’s. None took.
2. Then I forced a new device though the Control Panel’s, Add New Hardware, navigated to “Add a new hardware device” and
selected “Google Nexus 7 ADB interface”, and it created the new device. The Device Manager showed and error on the
device, so I refreshed it with the Adb driver, with no different results.
3. I then added the device driver “Google Nexus Bootloader Interface” via Add New Hardware
4. I rebooted the computer. After it came back up…
5. I looked at the Device Manager with no change in the status of any of the Android or the Unknown USB Device.
6. I insured the N7 was in bootloader mode by rebooting with volume keys/on key.
7. I went ahead and ran “adb drivers” cmd after entering the “cd’ cmd. I got the following:
Bear with me as I have no screen printing capability at this time.
>Command Prompt screen:
>C:\<adb dir>\platform-tools> adb devices
>List of devices attached
>C:\<adb dir>>\platform-tools>
And as you can see, NO listing showed.
So what’s next? I have another XP computer I can try this on, but I will have to get all the Abd stuff over to it 1st. While you answer I will try that.

Your Nexus in fastboot mode is not an adb device so it won't show up. Change your command to fastboot devices and it should work.
If you are still having driver issues download USB deveiw and remove anything that looks like a Nexus bootloader interface or adb device
Programming is a race between engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.

Captain Sweatpants said:
Your Nexus in fastboot mode is not an adb device so it won't show up. Change your command to fastboot devices and it should work.
If you are still having driver issues download USB deveiw and remove anything that looks like a Nexus bootloader interface or adb device.
Click to expand...
Click to collapse
OK, I have tried what you said with no results. If you would be willing to work with my computer directly, I have a method of allowing you to see what I see. The 2nd computer I have the N7 on right now have very little personal stuff on it, and I would be willing to let you access it. I have set up a temporary e-mail address [email protected] you can send an e-mail to with your e-mail address, and we can correspond directly, thus I can give you the access you need. I know you are else where in the world, so I would be willing to leave my computer up for you to see it all when you like. What do you think?
Tell me the final score of Zebre and your teem, what date it occurred, and what the sport is so I know it is you. Send the answer to the e-mail above, so I know it is you. I’ll only give you a short time to respond.

nickynooner said:
OK, I have tried what you said with no results. If you would be willing to work with my computer directly, I have a method of allowing you to see what I see. The 2nd computer I have the N7 on right now have very little personal stuff on it, and I would be willing to let you access it. I have set up a temporary e-mail address [email protected] you can send an e-mail to with your e-mail address, and we can correspond directly, thus I can give you the access you need. I know you are else where in the world, so I would be willing to leave my computer up for you to see it all when you like. What do you think?
Tell me the final score of Zebre and your teem, what date it occurred, and what the sport is so I know it is you. Send the answer to the e-mail above, so I know it is you. I’ll only give you a short time to respond.
Click to expand...
Click to collapse
It wouldn't work as I would need to be able to press buttons on the nexus.
If none of this is working then try wugfresh NRT again make sure you have the most up-to-date version from www.wugfresh.com its 1.8.2
The option you are looking for is unroot/back to stock there is an option for soft bricked make sure that is ticked
Sent from my Nexus 7
Hit thanks if I've helped

The Fat Lady Just Sang an Unhappy Song!
Hi Captain,
Thank you for all of your help and patience with me. I have read a lot more about the status of my device through looking at the XDA forum about other devices that have the kind of issue I do, and I have concluded mine is HARDbricked. I went ahead and ordered another motherboard off of eBay. My device was an 8G and I got a 32G replacement, making sure it was for my age of my N7. XDA forum and other websites say the boards are interchangeable. I was thinking about buying a new device anyway and this way I can upgrade and still have the same familiar device with no learning curve of a new one.

[Q][Answered] Have I screwed up? (Fastboot not seeing the Tablet)

Okay, I bought a Nexus 10 off someone, and they had already rooted the device. Bootloader is unlocked and whatnot. That's where my problems start. I can not for the life of me get fastboot or adb to see this thing.
Here's my info:
Google Nexus 10 (Samsung)
ClockworkMod Recovery 6.0.4.3
Bootloader Version: MANTALJ12a
Windows 8.1 Pro x64
Full Android SDK
Samsung drivers installed (I rooted my Galaxy Nexus without issue).
USB has a direct connection
Before I decided to format and try to install a stock .zip, I could access the tablet as a media (That's how I got the .zip on the device).
Steps to how I got here:
Flashed Cyanogenmod 10.2 or whatever. Didn't want JB, wanted Lollipop.
Pushed the (what I thought was correct) .zip to /sdcard
Booted into recovery
Formatted /system, /cache, /data, /factory
Reflashed the .zip
Failed. Miserably.
I named the .zip as something simple and just overwrote it. I wouldn't have this issue if it wasn't for that. I know I did a bad there.
But still, nothing I can do will get fastboot/adb to see the device. It makes the sounds that it's connected when I plug it in. I'm using an elevated prompt as well, but it will not pull the device. How do I get myself out of this hole? If I could push a new .zip to somewhere on /sdcard I could at least use the recovery to reflash.

Wrong device ? [emoji14]

Khaon said:
Wrong device ? [emoji14]
Click to expand...
Click to collapse
No, I was going to put it in the general help thread, may be better here since this may not be a simple question (Please prove me wrong).

Some additional things I've tried:
The NExus Root Toolkit. Removing all drivers etc. Still getting to fastboot by PWR+ VOL+ + VOL-.
Still nothing. Should I go to my wife's computer and try it there? I might do that anyways.

gothmog1065 said:
Some additional things I've tried:
The NExus Root Toolkit. Removing all drivers etc. Still getting to fastboot by PWR+ VOL+ + VOL-.
Still nothing. Should I go to my wife's computer and try it there? I might do that anyways.
Click to expand...
Click to collapse
You don't have access to have os then? How did you push your zip if you don't have access to adb?
I have seen people who couldn't get adb and fastboot working on their windows and switching to another computer solved the issues.
Ok, make sure to make a full clean of your drivers. Wug toolkit explain how to. Then install proper samsung driver and this
If it is not a hardware's problem, you should have access to fastboot & adb. You might try on another computer if possible. A clean one would be the best (i.e. never used any droid devices, etc.).
Another workaround would be to use and otg cable and an usb drive with any zip of your liking.
Another one, I had an issue long time ago, similar, I had to flash through odin in downloading mode to fix my problems.
BUT did you really deleted /factory partition? It contains various proprietary files needed for the device to work. Well concerns more devices with imei and stuff to allow 3g connection and co. Might have no incidence tho on your device's behavior.

Khaon said:
You don't have access to have os then? How did you push your zip if you don't have access to adb?
Click to expand...
Click to collapse
Sorry if I wasn't clear on this, I have 100% access to my computer. I have the Android SDK installed, and adb/fastboot commands working in command prompt. They're just not seeing the tablet.
Ok, make sure to make a full clean of your drivers. Wug toolkit explain how to. Then install proper samsung driver and this
Click to expand...
Click to collapse
Yeah, that's one of the steps I did. Followed the Wug toolkit and removed everything. Still not seeing the tablet.
If it is not a hardware's problem, you should have access to fastboot & adb. You might try on another computer if possible. A clean one would be the best (i.e. never used any droid devices, etc.).
Click to expand...
Click to collapse
Yeah, seems to be doing the same on my wife's computer (Win 7 HP, never had my phone/tablet hooked to it). I get adb/fastboot loaded and working in the command prompt, and it registers when I plug in, but neither command will "see" the tablet.
Another workaround would be to use and otg cable and an usb drive with any zip of your liking.
Another one, I had an issue long time ago, similar, I had to flash through odin in downloading mode to fix my problems.
BUT did you really deleted /factory partition? It contains various proprietary files needed for the device to work. Well concerns more devices with imei and stuff to allow 3g connection and co. Might have no incidence tho on your device's behavior.
Click to expand...
Click to collapse
It's a Wifi tablet, no cellular data and IMEI etc.
edit: As a side note, I've been thinking about reformatting my computer, though it'll be a huge pain to get it back to here as I've got to go from 7 - 8.0 - 8.1 on the upgrade paths to get it back here again.

gothmog1065 said:
Sorry if I wasn't clear on this, I have 100% access to my computer. I have the Android SDK installed, and adb/fastboot commands working in command prompt. They're just not seeing the tablet.
Click to expand...
Click to collapse
From my own experience, having similar issue with the windows drivers for adb, but eventually I fixed it. I really doubt you are screwed.
adb version output ? 1.0.32 is latest.
Yeah, that's one of the steps I did. Followed the Wug toolkit and removed everything. Still not seeing the tablet.
Click to expand...
Click to collapse
Installed universal adb drivers? Nothing shows up in the device manager?
Yeah, seems to be doing the same on my wife's computer (Win 7 HP, never had my phone/tablet hooked to it). I get adb/fastboot loaded and working in the command prompt, and it registers when I plug in, but neither command will "see" the tablet.
Click to expand...
Click to collapse
You might try odin.
Usb mtp doesn’t work from recovery?

Khaon said:
From my own experience, having similar issue with the windows drivers for adb, but eventually I fixed it. I really doubt you are screwed.
adb version output ? 1.0.32 is latest.
Installed universal adb drivers? Nothing shows up in the device manager?
?
Click to expand...
Click to collapse
Android Debug Bridge version 1.0.32, yep latest.
I just feel like I'm missing something, maybe something stupid. HOWEVER, I'm now getting my nexus 10 to show up in device manager with a ? on it. Already tried the direct Samsung drivers, the universal drivers in the Wug toolkit.

gothmog1065 said:
Android Debug Bridge version 1.0.32, yep latest.
I just feel like I'm missing something, maybe something stupid. HOWEVER, I'm now getting my nexus 10 to show up in device manager with a ? on it. Already tried the direct Samsung drivers, the universal drivers in the Wug toolkit.
Click to expand...
Click to collapse
Did you deleted all samsung vendor, etc from the usb program, you know what i am talking about?
You can force to install drivers from device maanger, don't remember how, when installing manually, you must do some step , install from floppy or file, get inf files or so, you will get a prompt telling you it might be harmfull and it will force installation. Might be the solution?
The culprit is definitely software-sided.
Does the mount internal storage (mtp) work?

Would this be easier in Linux? I could pop open my Ubuntu VM and do this if it'd be easier?
Beyond that, are you telling me to try and install the drivers from the driver files created by the Samsung vendor .exe?
I have tried to 'mount USB storage' from recovery, but it doesn't seem to do anything. /system /cache /data /factory are all mounted ATM and nothing is showing.

You've already got more advanced advice than I can offer but when I tried to update to 5.0.1 from 4.4.4, I couldn't get my windows computer to see my device. I was trying the adb fastboot but it I couldn't get it to work.
Wug's toolkit got it all straightened out (http://forum.xda-developers.com/showthread.php?t=2015467)[*]. There was an option on his interface that asked whether the device was working properly or not (a!most missed it as a choice). Checked that box and it went through much of the process I had done (installing adb, updating drivers etc). Long story short, it worked.

Where did you see this option? The only thing I see is the Soft Brick/Bootloop option where it will install the factory again. Was it that or somewhere else?
I swear to the Android droid that I tried that before. That seems to be doing what needs to be done, holy crap thanks!
e: I would like to know, however, why fastboot/adp wouldn't work but this would without doing any of the other stuff?

gothmog1065 said:
Where did you see this option? The only thing I see is the Soft Brick/Bootloop option where it will install the factory again. Was it that or somewhere else?
I swear to the Android droid that I tried that before. That seems to be doing what needs to be done, holy crap thanks!
e: I would like to know, however, why fastboot/adp wouldn't work but this would without doing any of the other stuff?
Click to expand...
Click to collapse
You're right. I confused the heading but choosing that option got my computer and my Nexus "talking." After installing the factory image I think you can then push a cusom ROM to you Nexus (http://forums.androidcentral.com/go...acks/264619-wugs-nexus-toolkit-questions.html).

gothmog1065 said:
Where did you see this option? The only thing I see is the Soft Brick/Bootloop option where it will install the factory again. Was it that or somewhere else?
I swear to the Android droid that I tried that before. That seems to be doing what needs to be done, holy crap thanks!
e: I would like to know, however, why fastboot/adp wouldn't work but this would without doing any of the other stuff?
Click to expand...
Click to collapse
Problem solved ? I always had less issues with fastboot and adb on Linux you can install a ppa that install for you adb and fastboot
Hovewer if you are using 2.8.2.0 you will need 1.0.32 and the ppa includes 1.0.31 so only adb sideload fails.
Sent from my nexus 10