Please help ... been trying to root my wife's Nexus S 4G.
I updated SDK which has the drivers for the NS4G, the Samsung website does not seem to have drivers. The Google USB Drivers on the SDK are updated to Rev.7.
I've been trying to use Shabby's One Click Root several times, v. 6, 6.5 and 7. During 1CR the phone gets into Fastboot mode, the Batchwindow on my computer showing <Waiting for device>, but gets stuck there. The options to Unlock the Bootloader never pops up! Instead my computer starts a window that is telling me that I need to install Android Drivers 1.0.
What to do?? Thanks
HackGerm said:
Please help ... been trying to root my wife's Nexus S 4G.
I updated SDK which has the drivers for the NS4G, the Samsung website does not seem to have drivers. The Google USB Drivers on the SDK are updated to Rev.7.
I've been trying to use Shabby's One Click Root several times, v. 6, 6.5 and 7. During 1CR the phone gets into Fastboot mode, the Batchwindow on my computer showing <Waiting for device>, but gets stuck there. The options to Unlock the Bootloader never pops up! Instead my computer starts a window that is telling me that I need to install Android Drivers 1.0.
What to do?? Thanks
Click to expand...
Click to collapse
Wrong section .....
Go to shabby's thread or Q&A section.
Vs Nexus S4G using tapatalk2
Related
Hi,
I have an O2 retail Galaxy Nexus. Before I began to use the phone I thought I would root it now.
I've read through the instructions and tips but unfortunately my PC can't find the drivers...
I could still access the phone so I opened the .bat for Windows Superboot.
CMD read < Waiting for Device> so I closed the cmd after waiting.
The phone now seems to be stuck on Fastboot Mode. Holding buttons or using the screen do not do anything.
This is my first Android device.
Is there a way for me to get back to normal phone mode until I sort the drivers?
I would be tempted to remove the battery if this were any other circumstance.
Will the older threads about Fastboot being stuck also work?
Thanks in advance.
I hit this myself and yanked out the battery to overcome it. Sorry if that's not what you want to hear, but I do now have a rooted device.
In response to fastboot freezing at <waiting for device> you need to install the fastboot drivers (these are not included in the root zip). Google around to find the best way to install them, I ended up installing pdanet onto my PC - as this has them included - and then removed the application after the drivers were installed.
Thanks for the reassurance, el3ctrik. Battery pull allowed it to boot normally.
Think I'll wait til the morning before trying again... Read some more articles, and try the pdanet method.
Ta!
I remember struggling with the drivers when I rooted my NS - I also ended up installing PDA net to sort out the issue.
Sent from my Nexus S using XDA App
I'm looking at buying a GNex for next to nothing, but the seller says it's stuck in fastboot. Came across this thread after a search, is this a fixable issue?
You need to install two drivers. Actually, it is the same driver, it just needs to be installed twice - once when your device is booted normally, and once when it is booted in fastboot mode.
I personally would use the Universal Naked Drivers by 1wayjonny that bk201doesntexist mentioned, NOT the PDA drivers or Samsumg drivers or any other ones. 1wayjonny's drivers do not install any other software on your PC - they are just the drivers, unlike the PDA drivers.
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"?
[FIXED]
For some reason Toolkit didnt work for me and i used this method to unlock bootloaders and root it.
http://forum.xda-developers.com/showthread.php?t=1362957
Also installed CWM recovery
------------------------------------------------------------------------
I installed my drivers and 1st time when I connected my phone in adb toolkit recognised it and showed his id. Next time when I connected it in adb it didnt recognise it in toolkit but windows recognise my phone and i can access it.
I've rebooted my pc every time and reinstalled couple of drivers:
-Naked samsung drivers
-Pda drivers
-Samsung_USB_Driver_for_Moblie_Phones_v1_4_6_0
Nothing worked.
1st time I used Samsung_USB_Driver_for_Moblie_Phones_v1_4_6_0 and i tried again and nothing.
I am on Windows 7 64bit version.
If anyone knows how to solve this please share the idea.
sukyman said:
I installed my drivers and 1st time when I connected my phone in adb toolkit recognised it and showed his id. Next time when I connected it in adb it didnt recognise it in toolkit but windows recognise my phone and i can access it.
I've rebooted my pc every time and reinstalled couple of drivers:
-Naked samsung drivers
-Pda drivers
-Samsung_USB_Driver_for_Moblie_Phones_v1_4_6_0
Nothing worked.
1st time I used Samsung_USB_Driver_for_Moblie_Phones_v1_4_6_0 and i tried again and nothing.
I am on Windows 7 64bit version.
If anyone knows how to solve this please share the idea.
Click to expand...
Click to collapse
I was facing lot of driver issues when connecting my GNex for the first time to the laptop on WinXP. Installing the drivers through the GNex Toolkit also did not work for me.
Finally what worked for me was, installing the latest version of Android SDK with the additional package of Google USB drivers, and then manually selecting the drivers after connecting my phone instead of asking Windows to look for drivers automatically.
I had trouble when first connecting my GNex too. However, these drivers worked for me (plus work with many many other android devices):
http://forum.xda-developers.com/showthread.php?t=1379875
If you have several android devices you'll find that you don't have to install multiple drivers for adb, fastboot, etc. for each of the devices.
Taken from post#3 of the ToolKit thread:
Note 1: If the driver doesnt install automatically then double click on the Android 1.0 item, then click on the driver tab and select 'update driver'. Select 'browse my computer' and then 'Let me pick from a list'. If no items appear in the list then untick 'Show compatible hardware' and find the Android adb driver or Samsung adb driver.
Try that as they may be on your pc and just not installing.
Mark.
Got them working now but i have problem when rooting, using GNex toolkit 5.6
It boots into android, i set usb debugging but when the phone is suppose to boot back to fastboot it gives error device not connected.
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 followed the instruction for this link. (http://forum.xda-developers.com/showthread.php?t=1347321) Everything was going well. Now I can't get out of mini pooploader. I searched around and was suggested from other peoples issues that I need to install the drivers. I manually installed the drivers, supplied in the link and Windows 7 states that the drivers I have are up to date. DO I need to go to HTC and find there drivers (Which are windows based or find android drivers)
I recently upgraded my XOOM to KIT KAT and am happy with it. I had fast boot and ADB installed for that project. Is that what the problem is? I have co-mingled the downloads for the NAND install with the KIT KAT ADT Bundle?
I have no problem running ADB and seeing SDK recognize the commands. When I try Fastboot commands I get waiting for device messages. Can someone please point me in the right direction. I know this is an old thread and Im hoping someone will be having so much fun this holiday weekend that they'll hop online and help. I hope this use the phone in conjunction with the updated Xoom.
Oh yeah, Thanks to all the VETS out there
Silent Assasin said:
I followed the instruction for this link. (http://forum.xda-developers.com/showthread.php?t=1347321) Everything was going well. Now I can't get out of mini pooploader. I searched around and was suggested from other peoples issues that I need to install the drivers. I manually installed the drivers, supplied in the link and Windows 7 states that the drivers I have are up to date. DO I need to go to HTC and find there drivers (Which are windows based or find android drivers)
I recently upgraded my XOOM to KIT KAT and am happy with it. I had fast boot and ADB installed for that project. Is that what the problem is? I have co-mingled the downloads for the NAND install with the KIT KAT ADT Bundle?
I have no problem running ADB and seeing SDK recognize the commands. When I try Fastboot commands I get waiting for device messages. Can someone please point me in the right direction. I know this is an old thread and Im hoping someone will be having so much fun this holiday weekend that they'll hop online and help. I hope this use the phone in conjunction with the updated Xoom.
Oh yeah, Thanks to all the VETS out there
Click to expand...
Click to collapse
Try this guide. Lot newer.
http://forum.xda-developers.com/showthread.php?t=2049567
wizardknight said:
Try this guide. Lot newer.
http://forum.xda-developers.com/showthread.php?t=2049567
Click to expand...
Click to collapse
Thanks for replying. That's the guide I was using. I can't get into fastboot. ADB commands work. I tried to manually install the drivers (On the computer). Windows 7 says my drivers are up to date. I can't move forward out of mini pooploader (funny name by the way). Any ideas would be appreciated...
I meant to say that I found that thread after being stuck in mini poop mode.
9. Turn the phone back on. You should see a blue miniPooploader screen with a lot of white text scrolling for a moment. When it gets done, pull the battery to shut it off. Then replace the battery (it should still be off)
10. Connect the usb cable between the phone and the PC, and turn the phone on. The PC should see the device, and may or may not assign drivers to it.
Click to expand...
Click to collapse
have you done this part? when you do the 10th one, your phone should get a black screen and a driver should be automatically installed by windows 7. for me - the driver was HTC Bootloader. after this, i installed the fastboot driver. more specific - the driver in the ADB_fastboot folder. after that - it went smooth.
plrusek said:
have you done this part? when you do the 10th one, your phone should get a black screen and a driver should be automatically installed by windows 7. for me - the driver was HTC Bootloader. after this, i installed the fastboot driver. more specific - the driver in the ADB_fastboot folder. after that - it went smooth.
Click to expand...
Click to collapse
I followed your advice. I let mini pooploader run the blue screen with white letters. Once finished, I removed the battery, placed the battery back in and then plugged usb into computer. I then powered the phone up with the same results. I performed this task 11 times with the same results. No black screen and no win 7 driver install. The computer says unknown device. I have tried to install drivers and computers states the drivers are up to date. I have tried different USB ports. I have attempted to install HTC drivers someone posed in this forum as well as the drivers that come with SDK with negative results. I have tried to uninstall the drivers in hopes that windows would install upon recognizing device with no luck.
Any ideas? I really need to get this working. i have not had a phone for a week now