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] adb offline nexus 7 4.2.2

Im trying to root my nexus 7 what exactly am i supposed to do to achieve that?
i got this error adb offline and it's screwing with the rooting process
i upgraded to 4.2.2 yesterday help me achieve rootness
also am i suppose to unlock my nexus before rooting it.:victory:

Hello there, have you unlocked your bootloader?
Also have you installed the correct drivers?
And is USB debugging mode enabled on your nexus?

how to do that?
compty said:
Hello there, have you unlocked your bootloader?
Also have you installed the correct drivers?
And is USB debugging mode enabled on your nexus?
Click to expand...
Click to collapse
how to unlock bootloader 4.2.2?
yes usb debugging is enabled

I assume you are using Google Nexus 7 Toolkit?
If so there should be an option which says unlock bootloader.

google toolkit error trying to unlock
compty said:
I assume you are using Google Nexus 7 Toolkit?
If so there should be an option which says unlock bootloader.
Click to expand...
Click to collapse
Oh yeah sorry about that however when I try to unlock the error adb devices offline comes also it can't find adb anywhere even when my nexus is on normally

Same problem
leo9252 said:
Oh yeah sorry about that however when I try to unlock the error adb devices offline comes also it can't find adb anywhere even when my nexus is on normally
Click to expand...
Click to collapse
I feel your pain as I too am having the same problem. I am posting on here so I can easily follow your post. I will tell you also that I think it has something to do with 4.2.2 but not positive at this point. I have rooted a Nexus One, HTC Dream, SGH679, so I do have some experience with this. I have changed ports, cables, started and stopped the service, rebooted the tablet, toggled the debugging just keep getting the offline. When I plug my phone in and use it, it sees it and it works fine, then when I plug the tablet back in it go back to offline. I even removed all the drivers on the computer just so it would get confused with the phone driver and still no luck. I think the driver is fine tho because it says it is in device manager, and I can transfer files back and forth from my tablet to my computer. Don't loose heart tho I think the answer is out there and I will keep working on it, and checking back to see if anyone else has had success.

Have you tried updating the data files in NexusRootToolkit?
http://forum.xda-developers.com/showthread.php?p=37955981#post37955981

further problems
sicameron32 said:
I feel your pain as I too am having the same problem. I am posting on here so I can easily follow your post. I will tell you also that I think it has something to do with 4.2.2 but not positive at this point. I have rooted a Nexus One, HTC Dream, SGH679, so I do have some experience with this. I have changed ports, cables, started and stopped the service, rebooted the tablet, toggled the debugging just keep getting the offline. When I plug my phone in and use it, it sees it and it works fine, then when I plug the tablet back in it go back to offline. I even removed all the drivers on the computer just so it would get confused with the phone driver and still no luck. I think the driver is fine tho because it says it is in device manager, and I can transfer files back and forth from my tablet to my computer. Don't loose heart tho I think the answer is out there and I will keep working on it, and checking back to see if anyone else has had success.
Click to expand...
Click to collapse
So I was going to do it the old fasion way by following this guide
http://forum.xda-developers.com/showthread.php?t=2150661
I didn't quite get step four because the nexus 7 doesn't have an SDcard, but I copied the zip to the root of the device.
When I did step 7 the device did not go to Fastboot, it didn't go anywhere other than a black screen. I think I have a faulty unit, or the holding of the volume buttons with the power is really not the way to get to fastboot, either way I am looking at a brick right now. Any thoughts will be welcome. I messed around with it for 10 min now and got the device to re-boot. Not sure if I should try the fast boot option again.

Are you on Windows 8 by any chance?
Because I couldn't get it to work on Windows 8 and had to use Windows 7.

You must update adb command from here:
http://forum.xda-developers.com/showthread.php?t=1766475&page=251
JB 4.2.2 is asking for debugging PC white list, please enable and allow it when prompt. Check here.
http://www.androidpolice.com/tags/android-4-2-2-adb-device-offline/
I got exactly the same problem and now it works for me.

everyone i got it working! adb offline fixed
It took me a while but I finally fixed it! Here's what I did I went crazy and searched all over the web with the keywords adb offline nexus 7 4.2.2 I then found a website that related to my issue it said to update SDK manager so I downloaded the manager then found android 4.2 next downloaded all that was under the 4.2 package and next downloaded the extra packages next thing I knew I plugged in my nexus and on it on the screen it told to choose yes or no on USB debugging and that's all you have to do to fix the problem of the adb offline bullstuff. I hope you guys will be able to understand what I'm writing to you. I also use windows 7 for this.

leo9252 said:
It took me a while but I finally fixed it! Here's what I did I went crazy and searched all over the web with the keywords adb offline nexus 7 4.2.2 I then found a website that related to my issue it said to update SDK manager so I downloaded the manager then found android 4.2 next downloaded all that was under the 4.2 package and next downloaded the extra packages next thing I knew I plugged in my nexus and on it on the screen it told to choose yes or no on USB debugging and that's all you have to do to fix the problem of the adb offline bullstuff. I hope you guys will be able to understand what I'm writing to you. I also use windows 7 for this.
Click to expand...
Click to collapse
It won't let me download and install anything from the 4.2 list...did you do anything else?

myleb said:
You must update adb command from here:
http://forum.xda-developers.com/showthread.php?t=1766475&page=251
JB 4.2.2 is asking for debugging PC white list, please enable and allow it when prompt. Check here.
http://www.androidpolice.com/tags/android-4-2-2-adb-device-offline/
I got exactly the same problem and now it works for me.
Click to expand...
Click to collapse
FWIW, here is my experience:
PC: Win7 Pro x64 SP1 - SDK platform-tools 16.0.1 - SDK Tools 21.1 - ADB v 1.0.31
N7: JDQ39 Stock *
( *OK, i diddled default.prop in my boot image to set "ro.secure =0". I don't know if that could make a difference or not )
The Nexus 7 asks for confirmation of inbound adb sessions for every new adb server invocation on the client PC.
When it does ask for credentials, you have to get to the on-screen display pretty quickly - a couple of seconds at most. If you don't the device will be reported as "offline" by the first invocation of
adb devices
If you accept the connection, the next time you run "adb devices", the status is back to normal (reports "device" instead of "offline").
You can test this out yourself - just iterate in a loop these three commands:
adb devices
adb devices
adb kill-server
Nothing that can't be understood by someone who knows what is going on; but I suppose that all the toolkits are running adb underneath the hood, so it is certainly possible to get tripped up when using a toolkit if you aren't Jhonny-on-the-Spot when that dialog pops up on the tablet.
Also, for the adventuresome:
I note that the new stock JDQ39 (4.2.2) ramdisk has a new line in the default.prop that was not in JOP40D (4.2.1) :
Code:
ro.adb.secure=1
I suppose that could be toggled off if you have a favorite kernel/ramdisk setup and you don't want to be bothered by this stuff. But it does mean unpacking/repacking your boot images.
cheers

I'm having the same problem. Never recognizes an ADB device. When it does it shows my serial number followed by "offline."
Any ideas? I'm ready to return this thing.
---------- Post added at 08:28 PM ---------- Previous post was at 08:16 PM ----------
Out of curiousity what driver are you using and how are you installing it?
Also where is your device coming up in the device manager?
I've tried so many things that I think I'm getting off track. Sadly my motorola phones were much easier to root.

how come you cant?
LucentBirch said:
It won't let me download and install anything from the 4.2 list...did you do anything else?
Click to expand...
Click to collapse
How come you can't download and install from the SDK manager?
That's how my problem got fixed.

Worked
jibdev said:
Have you tried updating the data files in NexusRootToolkit?
http://forum.xda-developers.com/showthread.php?p=37955981#post37955981
Click to expand...
Click to collapse
Thank you.... this worked first time go! So happy!
Thanks to all involved.... This is by far the most useful forum for phones.

you're welcome
sicameron32 said:
Thank you.... this worked first time go! So happy!
Thanks to all involved.... This is by far the most useful forum for phones.
Click to expand...
Click to collapse
I knew someone would find this useful.
:laugh::good:

leo9252 said:
I knew someone would find this useful.
:laugh::good:
Click to expand...
Click to collapse
The sad thing is I have no idea what finally got it to work. Maybe just an extra reboot I had forgotten at some point. I do know however that I had to add a few extra lines (hardware ID) to the .inf file in the usb driver. Not sure which did the trick. I also used a combo of the toolkit to unlock and the manual method to root. Also I am unable to boot my device into the bootloader/fastboot via windows and rather have to manually (physically) shut down the device and enter the bootloader via the physical buttons. Probably an issue with the windows drivers again, but at least I have full functionality once in fastboot.
Only thing is now I can't get access to the storage via windows. And there's no way in hell I want to change the ADB drivers without knowing which finally worked for me. I'm thinking though that this is an entirely different device in device manager (I'm obviously not that knowledgeable).
Also I'm kinda annoyed by the unlocked padlock symbol on startup. I suppose that should be a welcome sign of achievement after spending all day trying to unlock/root, especially for such an unlearned person as myself.

did you clear this issue?
leo9252 said:
Im trying to root my nexus 7 what exactly am i supposed to do to achieve that?
i got this error adb offline and it's screwing with the rooting process
i upgraded to 4.2.2 yesterday help me achieve rootness
also am i suppose to unlock my nexus before rooting it.:victory:
Click to expand...
Click to collapse
if not, pls gimme a mesg.
cause I'm a noob, I cannot use link here. :crying:
This issue is included in 4.2.2, and ADB is disabled by default for security.
I tested on my Nexus 4, 4.2.2 running. :fingers-crossed:

Okey. So to summarise: there is this new security feature in android 4.2. that makes the device show a popup if you want to allow the connected computer to use the adb = debugging bridge. But for this to work, you need to have the newest adb binary, which needs to print 1.0.31 when you run "adb version"
(found that info here --> http://www.androidpolice.com/2013/0...s-from-stealing-your-data-in-some-situations/ )
Under linux when you try to do it the old-school google-recommended way and download the huge "adt-bundle-linux-x86_64-20130219" and use the "android" tool to find new updates to the platform tools, it will tell you you already got the latest version which is rev 16.0.2 which contains an adb binary which will print version 1.0.26 which will not work with this new android 4.2.2 security feature.
So after searching for a linux adb 1.0.31 binary, I found it here:
https://github.com/mozilla/r2d2b2g/commit/2eefcc05366173ca51635da8f542fd8473ba0fea -->
https://ftp.mozilla.org/pub/mozilla.org/labs/r2d2b2g/adb-1.0.31-linux.zip
with that binary I finally can use adb on my nexus 7 again.

Need help... cannot figure rooting out

Hi all,
Long story short, I accidentally bought a Kindle Fire HD 7. I was hoping to root it but I've had nothing but difficulty. Can anyone help me with the things below? ** Please don't reply if you can't - the disorder and unmoderation of this forum is part of the confusion problem **
- The apps that are given on this site mostly don't work for 7.2.3. Is this an issue with the version?
- I kept getting permission denied errors. Nothing that pushes over, pushes successfully - yet it says it does
- When I finally got something "rooted", my status bar and home bar (at the bottom) are all gone. I can pretty much do nothing with it
- I can't figure out how to restore. I can get into FastBoot mode fairly easily, but when I try to do anything I get "waiting on device" errors. Any ideas?
- I'm a Mac guy, but running Windows 7 to do this. I've tried various versions of drivers posted on the board, but W7 is just a PITA to work with. When it goes into Fastboot, it comes up as an "unrecognized device" in Device Manager. Would this be part of the problem? I've tried to associate drivers with the unknown device, but it keeps saying the driver it has is the best (even though I've removed it).
And while I admit, an emotional rant after spending way too long having to do the above..:
- This forum is a complete mess.. can people with KF HD 8.9's get out of the forum and quit replying or giving advice on the wrong device? Mods, please shut down or move KFHD 8.9 posts. For people trying to find out info, it's seriously a mess.

lordmuggins said:
Hi all,
Long story short, I accidentally bought a Kindle Fire HD 7. I was hoping to root it but I've had nothing but difficulty. Can anyone help me with the things below? ** Please don't reply if you can't - the disorder and unmoderation of this forum is part of the confusion problem **
- The apps that are given on this site mostly don't work for 7.2.3. Is this an issue with the version?
- I kept getting permission denied errors. Nothing that pushes over, pushes successfully - yet it says it does
- When I finally got something "rooted", my status bar and home bar (at the bottom) are all gone. I can pretty much do nothing with it
- I can't figure out how to restore. I can get into FastBoot mode fairly easily, but when I try to do anything I get "waiting on device" errors. Any ideas?
- I'm a Mac guy, but running Windows 7 to do this. I've tried various versions of drivers posted on the board, but W7 is just a PITA to work with. When it goes into Fastboot, it comes up as an "unrecognized device" in Device Manager. Would this be part of the problem? I've tried to associate drivers with the unknown device, but it keeps saying the driver it has is the best (even though I've removed it).
And while I admit, an emotional rant after spending way too long having to do the above..:
- This forum is a complete mess.. can people with KF HD 8.9's get out of the forum and quit replying or giving advice on the wrong device? Mods, please shut down or move KFHD 8.9 posts. For people trying to find out info, it's seriously a mess.
Click to expand...
Click to collapse
Ok what is the state of your KFHD? 7"? I would try to use this toolhttp://forum.xda-developers.com/showthread.php?t=1951254 to restore your kindle and getting back to a working state. If you have any questions post them in here or that forum and I will try to guide you through anything. You should not try to use an automated root tool if it isn't for your specified version(7" 7.2.3) and using a automated tool, I think personally, is just not good in general. What does the device manager specifically say when you are in fastboot? It shoulde look like this:

Thanks for getting back to me. I have indeed also tried that, but I encounter the Fastboot problem mentioned above. I can get it into FB mode fine, but when I go to do anything, it gets stuck at "waiting for device". I'm wondering what I'm doing wrong?
I'm using Windows 7 (gah)... just for the purpose of this. Believe me, it reminds me why I've left Windows looonngg ago
PS All automated tools were specific to my model and version #.. i wouldn't do otherwise.

And I forgot to say, it shows the yellow triangle warning signs.
I have however installed all the right drivers that I got on various places on the forums. Any ideas why it's doing that? (USB debugging/ADB is enabled of course)

lordmuggins said:
And I forgot to say, it shows the yellow triangle warning signs.
I have however installed all the right drivers that I got on various places on the forums. Any ideas why it's doing that? (USB debugging/ADB is enabled of course)
Click to expand...
Click to collapse
Try to reinstall the appropriate drivers.. first uninstall the ones you have now then reinstall.. if you have the yellow triangle in device manager the drivers are not installed correctly

I've tried that.. not sure what I need to do now. (I hate Windows)
The drivers appear fine when not in Fastboot (ie regular ADB) just not when in Fastboot

lordmuggins said:
I've tried that.. not sure what I need to do now. (I hate Windows)
The drivers appear fine when not in Fastboot (ie regular ADB) just not when in Fastboot
Click to expand...
Click to collapse
You do know that ADB and Fastboot are different.. Correct? They are two different cmd lines to execite comds to your kindle..does your kindle boot? What is its state? what are you seeing or does it even run at all>

I thought I made this clear in other posts, sorry
My Kindle boots fine normally, but in my attempts to root it, it's screwed something up (my menubar doesn't appear). I wished to restore it using the tool above.
I can get it into Fastboot, but I can't actually perform any actions due to it saying "waiting for device". Most ADB functionality works fine, i.e. to push apps. But I also can't get it rooted.
My issue is that when it is in Fastboot...not when it's not. That is what I'm trying to figure out.

lordmuggins said:
I thought I made this clear in other posts, sorry
My Kindle boots fine normally, but in my attempts to root it, it's screwed something up (my menubar doesn't appear). I wished to restore it using the tool above.
I can get it into Fastboot, but I can't actually perform any actions due to it saying "waiting for device". Most ADB functionality works fine, i.e. to push apps. But I also can't get it rooted.
My issue is that when it is in Fastboot...not when it's not. That is what I'm trying to figure out.
Click to expand...
Click to collapse
Have you tried Kindle Fire First Aide tool and the restore option of you version?

Yes, I have.
And my issue remains - when in Fastboot mode, it also gets stuck on "waiting for device".
When normal boot, ADB functions are fine. It communicates.. things happen
When in fastboot (I have a WordArt looking 'fastboot' logo on the screen) then nothing appears to communicate, and my Device Manager claims it has an "Unknown Device" that it wont let me manually install drivers for.
Windows 7 is x64 if that makes a difference

lordmuggins said:
Yes, I have.
And my issue remains - when in Fastboot mode, it also gets stuck on "waiting for device".
When normal boot, ADB functions are fine. It communicates.. things happen
When in fastboot (I have a WordArt looking 'fastboot' logo on the screen) then nothing appears to communicate, and my Device Manager claims it has an "Unknown Device" that it wont let me manually install drivers for.
Windows 7 is x64 if that makes a difference
Click to expand...
Click to collapse
Try a factory reset on the device and if that doesn't work go to Chris's thread, KFFirstAide and post your problems that you having with the software. He will help you figure out if something is wrong with your device or its the software. I would think its user related, in the nicest way possible. A lot of times we get are selves all worked up over this stuff and forget to specific steps, I am guilty as well. Maybe take a step back for a few hours and then give it another shot.. Sorry I couldnt help more but I currently don't have my KFHD bc I just got a new one shipped to me and still waiting for it to arrive.. If i had my device in front of me I would probably be able to find you a solution.. Its been three weeks since I have seen a Kindle and my memory is vanishing

How do you propose I do a factory reset?

lordmuggins said:
How do you propose I do a factory reset?
Click to expand...
Click to collapse
right.. menubar is gone.. how the F did that happen.. I don't get all these people having so much problem with rooting their devices and $hit disappearing.. Can you download soft keys? I don't remember if you need to be rooted or not too..

If I knew the answer to that question, I wouldn't be here. I do not see how I can download soft keys.. unless they're in the Amazon store?

lordmuggins said:
If I knew the answer to that question, I wouldn't be here. I do not see how I can download soft keys.. unless they're in the Amazon store?
Click to expand...
Click to collapse
Hey man just trying to help you.. I'm not the one with the problem, although I am making my problem bc I am trying to help. Go over to either thread KFFirstAide or KFHD system.img resotre tool and post your problem.. good luck

So I got it restored; I had to execute the app open in adb to get into Settings. Still can't figure out how to get the Win 7 to recognize it in Fastboot mode.. I just get "waiting for device"

lordmuggins said:
So I got it restored; I had to execute the app open in adb to get into Settings. Still can't figure out how to get the Win 7 to recognize it in Fastboot mode.. I just get "waiting for device"
Click to expand...
Click to collapse
Do you mean you get that when you select the option to reboot into fastboot mode, or that you are already on the fastboot screen but nothing is happening?
I had the exact same issue with missing status bar and softkeys, cazy annoying. So hopefully I can remember exactly what I did, depending on your answer to my question though

In regular mode, I had missing status bar and softkeys. I restored factory settings (by using adb to get into the settings screen). They are now back.
Now, I have it rooted (well, I have Superuser loaded at least and it appears to be working)... but that is all. It still feels half-done to me.
With the FirstAide tool I'm getting into Fastboot and then I was going to use it to restore it using the Restore Tool here: http://forum.xda-developers.com/showthread.php?t=1951254
But it doesn't work.. I can load into the Fastboot screen (wordart logo) but it doesn't connect to the device... I just get "waiting for device" and that's where it stops. The WIndows 7 PC I'm using just says that an unknown device has connected and leaves it there.
Ideally, I wish to load Google Play etc, but I can't do that using the First Aide tool. It throws a lot of permission denied errors at me.. reboots several times, says it has been successful but none of the apps are there.
Ideas? I feel like I'm getting closer... perhaps..!

Have you tried running a app that needs root and seeing if the "grant permission" window pops up when you run it. There is a root checker app that you could install from the Noobs Guide to rooting, which should do the trick. SUChecker.apk http://forum.xda-developers.com/showthread.php?t=2069117
If you have managed to get the UI bars back, how come you want to use the restore tool to reset the whole kindle?
If you root is working fine, and you want to install google play then follow the Alternative Manual Install from here http://forum.xda-developers.com/showthread.php?t=2069329 instead of using the first aide tool, which seems to be giving a few issues at the moment.
Another random solution is make sure you are using a usb2 port instead of a usb3 port(if you have 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