Hello everyone, been a while since I have been on this site.
I am in a dilemma which I hope you guys can help me with.
I have a samsung galaxy nexus, and I just wiped the phone. But there is no recovery, so I have no OS atm.I have tried the Android Toolkit, however, everytime I try using it I get problems. It says , " waiting for adb mode" . I downloaded SDK and have runned the adb.exe file, but a command prompt pops up, and a bunch of stuff pops up and scrolls down, and then it closes. It does nothing.
I have read that my drivers for ADB are not installed properly or whatever. So I tried uninstalling them from " device manager" and I tried reinstalling them. That didnt work. I tried uninstalling again and than downloaded a samsung galaxy nexus usb adb driver, which also did not work.
I just want to be able to place a ROM on my phone from the computer. If I can get that far, I can install it from recovery mode. But I cant even get it fully detected on my computer. Whenever I plug in the USB, it detects it, but drivers fail.
Also, in device manager, the universal serial bus controller, SM bus controller, and ethernet controller all have a yellow triangle over them. They always fail to install..
I have tried updating them from the device manager. But that has failed aswell..
Please someone help me. I am at a dead end and unsure what to do.
-Andrew
Try a different cable or different drivers. And please learn to use adb yourself and stop using toolkits.
Sent from my Galaxy Nexus using XDA Premium HD app
Can you enter in bootloader?
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
I can go into bootloader and recovery mode. I also tried a different computer and usb. It looks like its a bit better now because it actually says Galaxy nexus, instead of android device. However, I still cant go into ADB mode.
Everywhere I go, people say you need to enable debugging....but I dont have an OS. I am stuck in recovery or fast bootmode.
In the meanwhile, I tried installing zip file via sideload using Android Toolkit by skipsoft.( option 16) ....it looked like it was going to actually work...but it didnt. It says i dont have a recovery for TWRP or any of the other options.
You need to install fastboot drivers, and download 4.3 (or any you like) Google factory image for maguro. Flash that image, and install prefered custom recovery
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
I downloaded the fastboot usb drivers, however, I am not sure what to do with them.
Here's a pic of the files. I also download the adb files, and installed them, even though it said I had existing files.
andrewb71 said:
I downloaded the fastboot usb drivers, however, I am not sure what to do with them.
Here's a pic of the files. I also download the adb files, and installed them, even though it said I had existing files.
Click to expand...
Click to collapse
Enter bootloader on phone and connect it to PC. Phone probably wont be recognized. After that go to Device manager and find your phone ( as I remember it will say Android 1.0 or something similar), right click on it and press Update driver. In new dialog it will ask you whether you want to automaticly find drivers or manually. Press manually and select that usb_driver folder.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
Related
i got the samsung drivers, adb, fastboot,
but when i boot to bootloader (vol up+down +power) adb doesnt find any device. is that normal? fastboot oem unlock doesnt work, i presume b/c adb isnt recognizing my phone.
Some help please. Thanks
David 617 said:
i got the samsung drivers, adb, fastboot,
but when i boot to bootloader (vol up+down +power) adb doesnt find any device. is that normal? fastboot oem unlock doesnt work, i presume b/c adb isnt recognizing my phone.
Some help please. Thanks
Click to expand...
Click to collapse
ADB will not find the phone in bootloader mode. If you type fastboot devices, it should show your phone. Check device manager and see if you have an unrecognized device showing. If you do, try manually installing the drivers by clicking the update driver button under the unrecognized device's properties window.
try reinstalling the drivers...or you may need to use the google drivers in the sdk/adb package instead. Also when you plug the device into pc, go into device manager and see if shows up as android device. If it comes up unkown, then manually push the driver update.
^Ninja'd lol
fastboot devices comes up blank.
in device manager my phone comes up as other devices - android 1.0
i guess my driver is bad. where can i get a good one?
(i just installed the one from samsung.. same thing.)
what have you used
Make sure to download the software from sdk that is for the newest update of android. I think it is 4.0.3 there is like 5 things in that folder. You will need all of them, and after they download type "adb devices" in the command window and it should show the serial #.
Sent from my Galaxy Nexus using XDA App
Randroidran said:
Make sure to download the software from sdk that is for the newest update of android. I think it is 4.0.3 there is like 5 things in that folder. You will need all of them, and after they download type "adb devices" in the command window and it should show the serial #.
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
did that. i dont have any issues untill i am in the bootloader. adb works fine before i reboot.
I'm assuming your driver is not loaded properly. Download this driver and unzip it. Install it by using the update driver wizard in device manager. I used this same driver on my work laptop (windows 7) and have had zero issues.
thx ill try now
.
.
.
works!
thx a million
hey.
i followed the guide for rooting my galaxy nexus.
driver installation was alright, and then i switched to fastboot mode (green android) and then the device manager didn't recognize my gn (unknown device).
tried uninstalling and then reinstalling, tried "updating" it with various rar files i found on this forum and ofcourse i tries pdanet.
none of them worked. it was always unknown device.
then i had no choice and i removed the battery to boot it normal.
suggestions? thnaks
After installation, plug in your phone, look at your system tray for the USB icon, click it. It should show a status of installing more drivers. This can take awhile, and for a lot of people it seems to fail the last step, Android 1.0 drivers. Open control panel, system, device manager. Look for a yellow error icon. Click that, choose to install drivers manually and locally. Then select 'choose from list', find Samsung.
That should get you back on track
Sent from my Galaxy Nexus Bugless Beast 4.0.3 lte +franco#5
Were you able to unlock the bootloader? If you didn't do this, don't go installing any driver... be very careful. If you install the wrong driver in device manager, you'll screw it up. I installed the wrong driver on my main computer and I couldn't get the device manager to even recognize the phone :| I couldn't locate the right driver either because once I installed the driver, it renamed it. It was a huge pain and the only way I got this to work was by using a different PC with the correct drivers.
I have found this to be the best instructions for unlocking the bootloader. Most importantly, it includes directions on how to gain access to adb on your phone properly. Take your time and follow the instructions exactly...
Dutchy18 said:
hey.
i followed the guide for rooting my galaxy nexus.
driver installation was alright, and then i switched to fastboot mode (green android) and then the device manager didn't recognize my gn (unknown device).
tried uninstalling and then reinstalling, tried "updating" it with various rar files i found on this forum and ofcourse i tries pdanet.
none of them worked. it was always unknown device.
then i had no choice and i removed the battery to boot it normal.
suggestions? thnaks
Click to expand...
Click to collapse
I had the same issue, install pdanet and your phone will be recognized when in fastboot
Sent from my Galaxy Nexus using xda premium
i followed one of the main guides on this forum.
it says to install the pdanet drivers and then boot to fastmode via the volume buttons.
once i got into fastboot, the device was unrecognizable.
when i was still in normal boot, the device was recognized and it was all right. and yeah i turned usb debugging on.
how can i unlock the bootloader without installing drivers?
thanks
Dutchy18 said:
i followed one of the main guides on this forum.
it says to install the pdanet drivers and then boot to fastmode via the volume buttons.
once i got into fastboot, the device was unrecognizable.
when i was still in normal boot, the device was recognized and it was all right. and yeah i turned usb debugging on.
how can i unlock the bootloader without installing drivers?
thanks
Click to expand...
Click to collapse
silly question, but after booting to fastboot, you are using the fastboot.exe, and not adb? if you type "fastboot devices" does anything show up?
no, nothing shows up.
and thats clearly because the driver is not installed correctly.. i see a yellow sign in device manager.
what am i doing wrong? only thing i was different from the guide is that instead of typing adb reboot bootloader, i got into fastboot by pressing the volume buttons.
Dutchy18 said:
no, nothing shows up.
and thats clearly because the driver is not installed correctly.. i see a yellow sign in device manager.
what am i doing wrong? only thing i was different from the guide is that instead of typing adb reboot bootloader, i got into fastboot by pressing the volume buttons.
Click to expand...
Click to collapse
click open that yellow unrecognized device...manually choose drivers (don't do auto), and select from the list, you'll see samsung, choose the driver
that should install android 1.0...alot of people have gotten this error.
edit: another thing to keep in mind is, after installing the drivers, and fixing the device in device manager, it can still take a little bit to initialize. in your system tray there should be a usb icon, open that to see when the drivers are done
I am in the same boat. I tried for hours on 2 different Windows 7 laptops (both 64bit). I am trying to get Yakju from one of the derivitives (without unlocking the device).
Steps taken:
- Dloaded Samsung USB driver 1.4.6 & Installed: Did not recongnize in explorer or Odin (even Odin did not show a thing)
- Dladed PDA Net A302x64: Did not recognize in explorer or Odin.
Both times the GN is in Device/Printers and listed as having Android 1.0 driver. I try to manually update, but cannot seem to find driver in list (as it just has Android 1.0 driver listed). Any suggestions?
i didnt even see the "Android 1.0".. just "unknown device" all along..
i also tried on a different computer.. same issue.
about manually installing the driver.. i tried pointing him to a manual driver package i got from this forum.. it said its the same driver..
when im searching for "samsung" on the list, i dont see a relevant driver.
Well, i've saw someone else on here who was having driver issues, who also had installed both samsung & pda drivers...
uninstall both.
fresh install ONLY the naked drivers directly off samsungs website (http://www.samsung.com/us/support/downloads/verizon-wireless/SCH-I515MSAVZW -- if you're verizon, if not, you can search there). Do the install. Plug the phone in, it will start to install its usual crap. this is the long part. then, it will fail like you saw before. in device manager, you'll see the unrecognized device. Open, it will ask you to find drivers, choose "Browse", "Let Me Pick From a List", "Samsung", and then pick the driver with the date 11/25/2011
check to see if there are any other unrecognized devices in device manager, just to be sure you got em all. at this point, plugging in your phone should show the USB connected icon in the system tray. do you see this? If you click it does it say "Eject MTP"?
I'm having problems getting my phone recognized by Heimdall (both Windows and Mac) and Odin (Windows). Here's the situation.
I have a practically fresh install of Windows with no drivers installed. I downloaded Heimdall to try and restore my Epic that has the [Phone] ! [PC] screen. I booted it into recovery mode, ran zadig, used a non-Samsung cable, etc. Heimdall's detect button recognizes my phone. However, when I actually try and do anything, I get "Error: libusb error: -12". I've seen some posts from different forums that say this is correlated with NOT having the zadig drivers installed, so I reinstalled them and rebooted for good measure. I still have the same problem.
So, I assumed that Heimdall was a lost cause and moved on to Odin. I'm following the how to in the dev forum and I installed the drivers mentioned there (x64 as I'm on Win 7 64 bit), downloaded the TAR, and so on. I open up Odin, put my phone in download mode, plug it in... and Windows says that it's an unknown device and can't recognize it. I've uninstalled/reinstalled the drivers several times, swapped out USB cables, and I can't find or think of anything more to do.
Help!
Okay when you open device manager and find the "unknown device" update the driver with your epic 4g drivers this will fix it hopefully... if not try and unistalling it pulling your usb out and popping out the battery and leave it out and plug in the usb and go into dlmode and it should reset things.
Sent from my SPH-D700 using xda premium
I'm getting a screen that says "The best software for your device is already installed. Windows has determined the driver software for your device is already up to date." and the dialog still shows Unknown Device.
Biggoron said:
Okay when you open device manager and find the "unknown device" update the driver with your epic 4g drivers this will fix it hopefully... if not try and unistalling it pulling your usb out and popping out the battery and leave it out and plug in the usb and go into dlmode and it should reset things.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
http://db.tt/gh3MgHKl
Try installing these.. more device specific drivers let me know if these work... did you unistall it and try an advanced install?
Sent from my SPH-D700 using xda premium
That's just a download for driver detective..
Biggoron said:
http://db.tt/gh3MgHKl
Try installing these.. more device specific drivers let me know if these work... did you unistall it and try an advanced install?
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
Hmm that's weird sorry.... don't have a 64bit pc so I've never tried em.... I'm at a loss then... usually if you unistall it and go back into download mode it erases the previous setup and asks you for the reccommended install or advance install which is what you would want to advance install the correct drivers...
Sent from my SPH-D700 using xda premium
Well thanks for trying. I'm basically where I started, unfortunately: I put the phone in download mode, it tells me it's an Unknown Device, I can't update/advanced install the correct drivers, and Odin doesn't recognize my device.
Biggoron said:
Hmm that's weird sorry.... don't have a 64bit pc so I've never tried em.... I'm at a loss then... usually if you unistall it and go back into download mode it erases the previous setup and asks you for the reccommended install or advance install which is what you would want to advance install the correct drivers...
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
redct said:
Well thanks for trying. I'm basically where I started, unfortunately: I put the phone in download mode, it tells me it's an Unknown Device, I can't update/advanced install the correct drivers, and Odin doesn't recognize my device.
Click to expand...
Click to collapse
Just read someone fixed this by reinstalling Windows 7. Otherwise try Heimdall. It installs it's own drivers. Check out post 2 here:
http://forum.xda-developers.com/showthread.php?t=1052813
redct said:
I'm having problems getting my phone recognized by Heimdall (both Windows and Mac) and Odin (Windows). Here's the situation.
I have a practically fresh install of Windows with no drivers installed. I downloaded Heimdall to try and restore my Epic that has the [Phone] ! [PC] screen. I booted it into recovery mode, ran zadig, used a non-Samsung cable, etc. Heimdall's detect button recognizes my phone. However, when I actually try and do anything, I get "Error: libusb error: -12". I've seen some posts from different forums that say this is correlated with NOT having the zadig drivers installed, so I reinstalled them and rebooted for good measure. I still have the same problem.
So, I assumed that Heimdall was a lost cause and moved on to Odin. I'm following the how to in the dev forum and I installed the drivers mentioned there (x64 as I'm on Win 7 64 bit), downloaded the TAR, and so on. I open up Odin, put my phone in download mode, plug it in... and Windows says that it's an unknown device and can't recognize it. I've uninstalled/reinstalled the drivers several times, swapped out USB cables, and I can't find or think of anything more to do.
Help!
Click to expand...
Click to collapse
http://www.samsung.com/us/support/downloads/sprint/SPH-D700ZKASPR
this is a direct link to the drivers needed.
Well, I got it to work with Heimdall. It seems to have been a combination of the USB cable, USB port, and drivers that caused my problems. Here's how I got it to work for those who might have this problem in the future.
1. Uninstall literally everything related to Samsung, Heimdall, Odin, etc. This means uninstall any drivers, delete all instances of Odin, Heimdall, Kies, or any other software.
2. Reboot.
3. Download the latest version of Heimdall (1.3.1).
4. Remove the battery from your Epic and let it sit for about 15 minutes.
5. Get a fresh, non-Samsung (and possibly non Amazon, as that's another one that didn't work for me) USB cable. I opened a brand new Monoprice one that I had laying around.
6. Plug in the cable to a USB port directly on your computer.
7. Hold down power and 1 while plugging in the USB cable (this is with the battery still out).
8. Run zadig.exe, which comes with Heimdall. The computer should recognize it as a Samsung composite device or "Gadget serial". Install drivers.
9. Open Heimdall and flash. DON'T TOUCH ANYTHING UNTIL IT'S DONE!
Great. As long as u got it to work. Excellent.
Sent from my SPH-D700 using xda premium
Nice job redct. I get mine to flash by whispering to it "it'll be OK...it will make you better"....LOL
Sent from my SPH-D700 using XDA App
don't know if you are still around,..but THANK YOU THANK YOU!!!! After all my searching and seaching,. this post saved me. Uninstalled drivers, rebooted pc, and the rest is history. Before I used heimdall I reinstalled the drivers and unzipped odin,. and odin recognized the phone,.so getting phone back up was just a matter of adding 2 files to odin and waiting!
this site had ALL the files I needed as well
epiccm.blogspot.com ..I cant post the direct link yet but maybe search factory firmware with the site.
redct said:
6. Plug in the cable to a USB port directly on your computer.
Click to expand...
Click to collapse
I suspect this might of been your issue. Where you plugged into a hub or an extension cable?
kennyglass123 said:
Nice job redct. I get mine to flash by whispering to it "it'll be OK...it will make you better"....LOL
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
ROFLMBO
I've been trying since last night to root my Nexus, because I want to install Jelly Bean. When I used the Galaxy Nexus Toolkit to install my drivers it did fine for adb. When I go into device manager it shows up as Android Phone like its supposed to. However, when I boot into fastboot mode, my computer no longer recognizes my Nexus and when I got into device manager, nothing shows up for it...not even Android 1.0.
Can someone please give me some tips as how to fix this issue.
P.S. I also installed the Google SDK along with the Google USB drivers afterwards, hoping that would fix the issue...but no luck...and I tried PDAnet...still no luck
The issue I was having was due to the fact that I wasnt pressing Volume Up+Volume Down+Power, so I wasnt even in fastbook, but a screen similar to it
schwartzman93 said:
I've been trying since last night to root my Nexus, because I want to install Jelly Bean. When I used the Galaxy Nexus Toolkit to install my drivers it did fine for adb. When I go into device manager it shows up as Android Phone like its supposed to. However, when I boot into fastboot mode, my computer no longer recognizes my Nexus and when I got into device manager, nothing shows up for it...not even Android 1.0.
Can someone please give me some tips as how to fix this issue.
P.S. I also installed the Google SDK along with the Google USB drivers afterwards, hoping that would fix the issue...but no luck...and I tried PDAnet...still no luck
Click to expand...
Click to collapse
The driver needs to be installed TWICE: once when you are booted normally, and once when booted in fastboot. http://forum.xda-developers.com/showpost.php?p=28060885&postcount=3
efrant said:
The driver needs to be installed TWICE: once when you are booted normally, and once when booted in fastboot. http://forum.xda-developers.com/showpost.php?p=28060885&postcount=3
Click to expand...
Click to collapse
My problem is that when I plug in my phone...while its in fastboot its not recognized as an Android phone or Android 1.0...its recognized as a "SAMSUNG Mobile USB CDC Composite Device"
schwartzman93 said:
My problem is that when I plug in my phone...while its in fastboot its not recognized as an Android phone or Android 1.0...its recognized as a "SAMSUNG Mobile USB CDC Composite Device"
Click to expand...
Click to collapse
That's because you need to uninstall all the old drivers and install the ones I link to...
Sent from my Galaxy Nexus using Tapatalk 2
FastBoot Driver- Xperia Neo
efrant said:
That's because you need to uninstall all the old drivers and install the ones I link to...
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Hi,
I am using sony sricsson neo .587. I tried to connect my phone in fastboot mode. I connected in fastboot mode. I am not able to install drivers for that.
Steps I Followed
1. I updated google usb driver
2. Replaced "android_winusb.inf" file which is provided by Sony official
3. Connected phone in fastboot mode
4. It asked for drivers
5. I selected usb driver folder to install drivers
But It fails...
I am doing these all things on Windows 7 64 bit
Please help...
I'm totally lost, I have tried everything in the world to get my Nexus 7 2ed gen to get out of a self inflicted boot loop. It all started when I wanted to upgrade it from 4.4.4 to 5.0.2. It was rooted and I have TWRP recovery installed, I wiped the data and chose the wrong thing to do. I instead of a simple wipe, wiped the entire OS and everything.... So now i'm stuck with a rather nice paperweight.... I can boot into recovery (TWRP) and Fastboot. But regardless of what i do I cant get the damn thing to be seen on my computer via ADB or fastboot, so I can't install the stock OS onto it. I've tried re-installing the drivers for The tablet and ADB/fastboot, a countless number of times and nothing works. I've tried it on other computers, that doesn't work, and from how I see it It should.... Anyone out there know what I did to screw this up and how to fix it?
Get an OTG cable and load a ROM onto a flash drive. Then flash the ROM and your choice of gapps.
Sent from my LG-D850 using XDA Free mobile app
^That would be the easiest but still why would fastboot not work?
If adb can't see it in twrp or fastboot on the bootloader screen it's gotta be a driver or connection issue right?
You've probably done it but try different cables/make sure the usb ports are clean.
I'm guessing you flashed twrp with fastboot and know how to use fastboot. If not make sure you're in the fastboot directory before typing the commands in the command prompt.
Only thing left that you already tried is reinstalling everything. Uninstall any fastboot/adb/drivers anything related to android really.
Install the sdk. Install the google usb driver from the sdk manage in the sdk folder.
Boot the tablet to the bootloader screen and plug it in, driver should install automatically. Open a command prompt in the platform-tools folder in the sdk folder and type fastboot devices.
If that doesn't work I have no idea. Oh you could try reinstalling java.
Ok I went ahead and ordered an OTG cable. I also tried installing all the drivers and such another time, but this time when I plugged it in, while it was in bootloader mode, the driver didn't install? I tried several cords, could it be that the tablets port itself is the issue?