Related
Hi,
I have been messing with this for a few weeks now.
I have a magic 32B, spl 0004
I don't know how but i got cyanogenmod 4.2.5 on my phone.
But then i tried to use the update app and it fails.
It seems that there are 2 problems.
1. my recovery is still the stock one
2. i just cant seem to get a good connection with my computer.
Every time i try something its waiting for device.
Or with adb devices its an empty list.
i used a windows vista machine and a windows 7 machine
Is there someone who is willing to help me get this done?
I checked threads about, usb drivers, installing adb, installing recovery.img, installing cyanogen.
But there is always a step that just doesn't go according to the manuals.
i was about to give up, but i just really want this to work.
As you have already stated you have a stock recovery.img on the phone, to get the cyanogenmod updater program to work you need a custom one, the instructions to install this can be found on cyanogenmod.com in the downloads section.
If you are having problems getting the phone to connect to the pc make sure the drivers have installed correctly, you can download them at the link bellow incase you cant find them, by default they dont download with the sdk anymore, dont know why :-|
http://rapidshare.com/files/315790307/usb_driver.rar.html
justbenjp said:
As you have already stated you have a stock recovery.img on the phone, to get the cyanogenmod updater program to work you need a custom one, the instructions to install this can be found on cyanogenmod.com in the downloads section.
If you are having problems getting the phone to connect to the pc make sure the drivers have installed correctly, you can download them at the link bellow incase you cant find them, by default they dont download with the sdk anymore, dont know why :-|
http://rapidshare.com/files/315790307/usb_driver.rar.html
Click to expand...
Click to collapse
I have tried to install a custom recovery, but when i follow the steps i cant seem to connect to my phone via CMD.
When i check the drivers.. i'm not sure its 100% correct.
I have installed the once before.
and now he doesn't ask me for the drivers anymore.
but neither do i see it in the devicemanager, the way its being described in the manuals.
just something else involving android, but not ADB
i have tried to follow the manual, and threats about how to get the driver right..
but with this, i also have had problems with the steps..
On your phone go into settings....applications....Development and make sure
you have USB debugging enabled
justbenjp said:
On your phone go into settings....applications....Development and make sure
you have USB debugging enabled
Click to expand...
Click to collapse
I have done this..
I will try again on a vista machine which i havent used for this yet
anheuer said:
I have done this..
I will try again on a vista machine which i havent used for this yet
Click to expand...
Click to collapse
Great.. it would not install the SDK..
So back on my windows 7 machine..
still getting device not found in CMD - adb devices
connected with usb debugging on..
cant see anything in device manager, but the system also doesnt ask for drivers...
I went into fastboot and then it asked me for drivers..
Now i do have
Android phone - Android Bootloader interface
but in any other situation, it does not show anything or ask anything.
I just keep getting device not found...
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.
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.
Does anyone know whether the GPE can be rooted yet? I got mine yesterday and would like to transfer my app data from the LGE to the GPE if possible. I'd also like to use some root only apps like Xposed so that I can force Immersive Mode for more apps (mostly games and book/magazine readers).
UPDATE: I thought I'd post instructions on how to do it here. Basically just follow the Nexus 5 guide posted here:
http://www.droid-life.com/2013/11/04...t-the-nexus-5/
but in step 6 (flashing an alternative recovery), use this TWRP recovery image:
http://forum.xda-developers.com/showthread.php?t=2565431
Hopefully that helps others who are wanting to root their G Pad GPEs!
SCWells72 said:
Does anyone know whether the GPE can be rooted yet? I got mine yesterday and would like to transfer my app data from the LGE to the GPE if possible. I'd also like to use some root only apps like Xposed so that I can force Immersive Mode for more apps (mostly games and book/magazine readers).
Click to expand...
Click to collapse
yes it can be, the bootloader unlock is the same as it's always been for nexus devices, there is a custom recovery for it already.
1. download recovery and superSU zip
2. unlock bootloader
3. flash the recovery
4. boot into recovery
5. flash the superSU.zip
6. profit
thoughtlesskyle said:
yes it can be, the bootloader unlock is the same as it's always been for nexus devices, there is a custom recovery for it already.
1. download recovery and superSU zip
2. unlock bootloader
3. flash the recovery
4. boot into recovery
5. flash the superSU.zip
6. profit
Click to expand...
Click to collapse
Thanks! I've never had a Nexus or GPE device before, so I'm more accustomed to the various non-standard ways to root devices and assumed the G Pad GPE might need something similar.
I assume this is the recovery you're referencing?
http://forum.xda-developers.com/showthread.php?p=48479203
I tried to use the minimal adb included with dalingrin's simple root for the LGE but it says "error: device not found". Can you provide a pointer to the correct drivers for adb so I can perform steps 2-3?
Thanks again!
SCWells72 said:
Thanks! I've never had a Nexus or GPE device before, so I'm more accustomed to the various non-standard ways to root devices and assumed the G Pad GPE might need something similar.
I assume this is the recovery you're referencing?
http://forum.xda-developers.com/showthread.php?p=48479203
I tried to use the minimal adb included with dalingrin's simple root for the LGE but it says "error: device not found". Can you provide a pointer to the correct drivers for adb so I can perform steps 2-3?
Thanks again!
Click to expand...
Click to collapse
i just downloaded the sdk ages ago and have been using that, you'll also need the fastboot drivers instead of just ADB
in fact if you watch a tutorial about how to root a nexus 5 it will be closer than any of the stuff posted right now
Sorry for being a bit dense here, but I'm still spinning my wheels a bit on this. I downloaded the latest ADK and had it install the Google USB Driver. I have USB Debugging enabled on the GPE tablet. Unfortunately neither "adb shell" nor "fastboot devices" recognize the device. Any tips on what important step I'm missing that will allow me to get past this first hurdle?
UPDATE (FIXED): Never mind. I had to update the device with the driver first as per this link: http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver
SCWells72 said:
Sorry for being a bit dense here, but I'm still spinning my wheels a bit on this. I downloaded the latest ADK and had it install the Google USB Driver. I have USB Debugging enabled on the GPE tablet. Unfortunately neither "adb shell" nor "fastboot devices" recognize the device. Any tips on what important step I'm missing that will allow me to get past this first hurdle?
UPDATE (FIXED): Never mind. I had to update the device with the driver first as per this link: http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver
Click to expand...
Click to collapse
I can seem to find the drivers for our tablet! I can't find the link to download them. Where did you find them?
Thanks!
joaquinla1 said:
I can seem to find the drivers for our tablet! I can't find the link to download them. Where did you find them?
Thanks!
Click to expand...
Click to collapse
Just install the Android Development Kit and then have it install the USB driver. Don't forget to use Windows Device Manager (if using Windows) to update the driver for the G Pad while it's plugged in.
SCWells72 said:
Just install the Android Development Kit and then have it install the USB driver. Don't forget to use Windows Device Manager (if using Windows) to update the driver for the G Pad while it's plugged in.
Click to expand...
Click to collapse
Thanks!
I tried using the WDM before, but it can't find the drivers online. Should i just install the google drivers from the adk?
Update: I installed the google usb drivers with the ADK and still no luck!
joaquinla1 said:
Thanks!
I tried using the WDM before, but it can't find the drivers online. Should i just install the google drivers from the adk?
Update: I installed the google usb drivers with the ADK and still no luck!
Click to expand...
Click to collapse
Yes, install "Google USB Driver" from the ADK, then open WDM and find your tablet which should say something like "Unknown Device" (can't remember the exact term), right-click and say "Update Driver...", and navigate to the driver that the ADK downloaded for you. Once that's updated, you'll be able to use adb and fastboot.
The links I've posted don't seem to be working properly, but if you Google "root nexus 5", go to the result on Droid Life called "How to: Root the Nexus 5" and follow the linked instructions on how to unlock the boot loader, then the instructions on that page on how to root the device. Like I said, the only difference is that you'll use the TWRP image for the G Tab GPE from this forum instead of the one referenced there.
Howdy,
My question is, does Odin not work with Windows 8.1 in general? If you have managed to get Odin to register that a device has been connected was there any special way you managed to get around this?
Some background:
I mentioned this issue in the noob friendly section but it seems I am the only one having the issue there. So I'm asking around here if anyone has had this issue under Windows 8.1. All I wish to do is flash the unbranded firmware to remove carrier bloat-ware.
I've downloaded Odin 9.07/9/10 and have the same result, that the device just does not appear.
System is running Win8.1 and has driver signature disabled.
Kies is installed and picks up the device without error
Phone has USB debugging on and appears under 'Device Manager' when in Download mode.
I've had a look around and found nothing with this issue, watched folks do it in various videos too but they were using Win7.
Thanks for reading!
Ste_JDM said:
Howdy,
My question is, does Odin not work with Windows 8.1 in general? If you have managed to get Odin to register that a device has been connected was there any special way you managed to get around this?
Some background:
I mentioned this issue in the noob friendly section but it seems I am the only one having the issue there. So I'm asking around here if anyone has had this issue under Windows 8.1. All I wish to do is flash the unbranded firmware to remove carrier bloat-ware.
I've downloaded Odin 9.07/9/10 and have the same result, that the device just does not appear.
System is running Win8.1 and has driver signature disabled.
Kies is installed and picks up the device without error
Phone has USB debugging on and appears under 'Device Manager' when in Download mode.
I've had a look around and found nothing with this issue, watched folks do it in various videos too but they were using Win7.
Thanks for reading!
Click to expand...
Click to collapse
My guess is that you need to install Samsung's USB drivers for your device. Have a look at the instructions at this, and this page. I suspect that you haven't installed SAMSUNG's Android ADB Interface Driver (look at OP of the second thread), which is used by Odin if I'm not mistaken to talk to your phone and push the images you want via ADB.
Install the Samsung usb drivers!
Odin works fine on my windows 8.1 computer.
ernani said:
My guess is that you need to install Samsung's USB drivers for your device. Have a look at the instructions at this, and this page. I suspect that you haven't installed SAMSUNG's Android ADB Interface Driver (look at OP of the second thread), which is used by Odin if I'm not mistaken to talk to your phone and push the images you want via ADB.
Click to expand...
Click to collapse
That was it. Thanks so much! I removed Kies, rebooted, installed the driver from samsung and rebooted again, after that Odin worked like a charm.