Database Info

Computers blind to NS4G. Help?

Hey folks.
I have been trying to get my wife's NS4G back to stock to get the JB OTA. I have downloaded all drivers multiple times on multiple computers (windows). I have tried 3 or 4 different USB cables. I have downloaded pdanet. I have downloaded the JAVA SDK and updated everything about it.
My computers cannot connect to the NS4G.
USB debugging is on. When I try to turn on tether, it tells me USB is not plugged in.
I have been able to restore the stock ROM (2.3.7) via CWM, but now I no longer have a recovery. It is still rooted and unlocked. Rom Manager is installed and it will not download CWM Recovery.
I need some way to get a recovery onto it. CMW or stock.
Does ANYONE have any suggestions?
Thanks in advance for all suggestions and particularly to the one that will work.

SemperFratres said:
Hey folks.
I have been trying to get my wife's NS4G back to stock to get the JB OTA. I have downloaded all drivers multiple times on multiple computers (windows). I have tried 3 or 4 different USB cables. I have downloaded pdanet. I have downloaded the JAVA SDK and updated everything about it.
My computers cannot connect to the NS4G.
USB debugging is on. When I try to turn on tether, it tells me USB is not plugged in.
I have been able to restore the stock ROM (2.3.7) via CWM, but now I no longer have a recovery. It is still rooted and unlocked. Rom Manager is installed and it will not download CWM Recovery.
I need some way to get a recovery onto it. CMW or stock.
Does ANYONE have any suggestions?
Thanks in advance for all suggestions and particularly to the one that will work.
Click to expand...
Click to collapse
If you are running Windows 7 hold down the shift key and right click then select open command prompt here. type ADB devices and if your drivers are installed then you will see your serial number. Remember to be in fastboot when you install drivers. then use ADB to reboot bootloader. when in fastboot type "fastboot devices" and you should again see your serial number to know that your drivers are all installed correctly. You need to fastboot flash a new recovery image. Hope that helps

ken3669 said:
If you are running Windows 7 hold down the shift key and right click then select open command prompt here. type ADB devices and if your drivers are installed then you will see your serial number. Remember to be in fastboot when you install drivers. then use ADB to reboot bootloader. when in fastboot type "fastboot devices" and you should again see your serial number to know that your drivers are all installed correctly. You need to fastboot flash a new recovery image. Hope that helps
Click to expand...
Click to collapse
Drivers are installed, as I can see my S3 fine as well as adb getting my serial number. The computer, nor adb, can see my NS4G. I have tried a desktop as well as 2 laptops.
Will be trying Vaelek's idea of wireless adb this evening.
Thanks for the suggestion.
Sent from my SPH-L710 (that's a Galaxy S3 to you) via tapatalk.

SemperFratres said:
Drivers are installed, as I can see my S3 fine as well as adb getting my serial number. The computer, nor adb, can see my NS4G. I have tried a desktop as well as 2 laptops.
Will be trying Vaelek's idea of wireless adb this evening.
Thanks for the suggestion.
Sent from my SPH-L710 (that's a Galaxy S3 to you) via tapatalk.
Click to expand...
Click to collapse
Drivers are NOT installed properly then. Drivers are installed on a per device basis. If your phone doesn't get recognized, then they are not installed.
Chances are your device ID isn't found in the .inf file of the drivers. I know back when I rooted my phone over a year ago I had to manually change the inf file and add my device.
If you start your phone in fastboot mode and plug it in, when you go in device manager you should see an unrecognized device with a yellow question mark. Right click it, then Properties, then Details tab. Give me the information in the Device Instance Path.

Will check this out and post info when I get home tonight. Thanks for the input.
Sent from my SPH-L710 (that's a Galaxy S3 to you) via tapatalk.

polobunny said:
Drivers are NOT installed properly then. Drivers are installed on a per device basis. If your phone doesn't get recognized, then they are not installed.
Chances are your device ID isn't found in the .inf file of the drivers. I know back when I rooted my phone over a year ago I had to manually change the inf file and add my device.
If you start your phone in fastboot mode and plug it in, when you go in device manager you should see an unrecognized device with a yellow question mark. Right click it, then Properties, then Details tab. Give me the information in the Device Instance Path.
Click to expand...
Click to collapse
Started phone in fastboot mode. Plugged it in and watched Device Manager. Closed device manager and re-opened it for a good refresh. I get nothing new. No unrecognized device and no Android Device like when I plug in my S3. ADB Wireless wont connect.
OK... I just cleared my sd card and was able to install CWM. One hurdle cleared...
I still need to get stock ROM and recovery. Is there anyway to do this WITHOUT being able to connect via adb?
Thanks again for any input.

[SOLVED] Nexus 5 shows up in adb but not fastboot.

Okay so I did read up on another post about the same issue but it didn't really explain what fixed it. I only have a windows xp or vista or something computer. Its a 32 bit. I have installed and uninstalled drivers from SDK manager, manually installed Google drivers, universal drivers. All of it. I originally tried rooting using cf auto. Than tried to do it manually. That is when I realized it was a fastboot issue. I'm in fastboot mode during my attempts. Should it say fastboot USB when plugged in?
Sent from my Nexus 5 using xda app-developers app

whozilla said:
Okay so I did read up on another post about the same issue but it didn't really explain what fixed it. I only have a windows xp or vista or something computer. Its a 32 bit. I have installed and uninstalled drivers from SDK manager, manually installed Google drivers, universal drivers. All of it. I originally tried rooting using cf auto. Than trues to do it manually. That is when I realized it was a fastboot issue. I'm in fastboot mode during my attempts. Should it say fastboot USB when plugged in?
Click to expand...
Click to collapse
Have you endabled USB debugging under Developer options in your Settings?

Yep. More details
I have uninstalled and re installed all drivers from
lgs driver .exe
From the universal. Driver.
And google drivers
via sdk manager.exe.
I did that after i re set up android SDK in the c drive,s root. and ran the commands from directly in the platforms folder. Still my device is only seen under adb devices. Not fastboot devices. I just type in fastboot in the promt and it shows all the commands listed so I assume it has been set up.
Now it seems SDK manager won't open. A promt pops up and closes with no program open thereafter. I wanted to retry googles drivers because I uninstalled and re set up android SDK. I wanted to re download the packages and start fresh.
Sent from my Nexus 5 using xda app-developers app

whozilla said:
Yep. More details
I have uninstalled and re installed all drivers from
lgs driver .exe
From the universal. Driver.
And google drivers
via sdk manager.exe.
I did that after i re set up android SDK in the c drive,s root. and ran the commands from directly in the platforms folder. Still my device is only seen under adb devices. Not fastboot devices. I just type in fastboot in the promt and it shows all the commands listed so I assume it has been set up.
Now it seems SDK manager won't open. A promt pops up and closes with no program open thereafter. I wanted to retry googles drivers because I uninstalled and re set up android SDK. I wanted to re download the packages and start fresh.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Google tool adb fastboot drivers xda. That should get them working

Nice. gonna try as soon as I get home from work. I'll report back with result :thumbup:
Sent from my Nexus 5 using xda app-developers app

You're still thinking of HTC phones...
When in fastboot it will no change on the phone itself, you check by running 'fastboot devices' in the command prompt. If you see your serial number, it's fine. If you don't, go into Device Manager and manually update the driver
If you run 'adb devices' when connected in fastboot nothing will happen as adb is ONLY FOR WHEN ANDROID IS RUNNING (how many more times does this need to be said??).

whozilla said:
Nice. gonna try as soon as I get home from work. I'll report back with result :thumbup:
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
I'm sorry eddy. It seems you misread my posts. Im not having an issue understanding the difference between adb and fastboot. Allow me to clarify. While phone is on. With USB debugging enabled. I type
adb devices
in the command prompt under platform tools.. My device shows up and I have authorized it
When my phone is in the bootloader in fastboot mode. I type
fastboot devices
Nothing. That is my issue. Feel free to scroll back up and read the details. Any help is good help :beer:
Sent from my Nexus 5 using xda app-developers app

EddyOS said:
You're still thinking of HTC phones...
When in fastboot it will no change on the phone itself, you check by running 'fastboot devices' in the command prompt. If you see your serial number, it's fine. If you don't, go into Device Manager and manually update the driver
If you run 'adb devices' when connected in fastboot nothing will happen as adb is ONLY FOR WHEN ANDROID IS RUNNING (how many more times does this need to be said??).
Click to expand...
Click to collapse
I quoted myself by mistake haha. PS
I have manually updated drivers. After uninstalling them to be clear. That's what I meant when I said I tried the universal drivers. For the record. All attempts I have made to get fastboot to recognize my device have been done using forums with detailed instructions.
Sent from my Nexus 5 using xda app-developers app

Sounds like Windows isn't wanting to use the driver. Manually update the driver and point it to the *.inf file in the SDK. It should then work fine

Solved. Such a small detail. Eddy you were right. Before I could see your post I realized. Vuala! I needed to update the drivers manually with the phone plugged in in fastboot mode!. That was my mistake. Cf root did the rest.
In device manager you will see a yellow triangle under other devices when the nexus is plugged in on fastboot mode. I installed drivers from the .exe found in this thread.tool adb fastboot drivers. I let the computer search on its own for updates. Done. Rooted
Sent from my Nexus 5 using xda app-developers app

jd1639 said:
Google tool adb fastboot drivers xda. That should get them working
Click to expand...
Click to collapse
Thank you sir. You lead me in the right path
Sent from my Nexus 5 using xda app-developers app

[Q] Bricked my Nexus 5 using cwm. Help!!!!

Long story short, installed clockwork mod recovery in attempt to install a cyanogen nightly. I stupidly formatted everything including data and SYSTEM! Now I can only boot to recovery. When I plug the nexus into any PC it's not picked up as an unidentified piece of hardware on windows so I can't push another rom or adb sideline commands result in "waiting for device". Any suggestions? Should I attempt to RMA?

Reinstall drivers. Boot into the bootloader and flash the factory image.

El Daddy said:
Reinstall drivers. Boot into the bootloader and flash the factory image.
Click to expand...
Click to collapse
Thank you!! I never used the USB cable that actually came with the NEXUS until just now, the PC finally detected the phone as i was in the Bootloader and start automatically Download and Writing, rebooting itself and looks like it's booting up. Thanks again. Very quick response.

I accidentally formatted system as well, slip of the finger. I am unable to get my computer to recognize my device, "fastboot devices" lists nothing. Have tried flashing factory software, but it just says "waiting for device". Any suggestions???

Check USB drivers. Might not be working
Sent from my Nexus 5 using Tapatalk

wltnkyl said:
I accidentally formatted system as well, slip of the finger. I am unable to get my computer to recognize my device, "fastboot devices" lists nothing. Have tried flashing factory software, but it just says "waiting for device". Any suggestions???
Click to expand...
Click to collapse
If you are on windows 8 or 8.1 you have turn of driver signiture enforecment. http://sixcolumns.com/how-to-disable-and-bypass-driver-signature-enforcement-in-windows-8/
To make adb works when you are in recovery you need the naked usb drivers. Turn on sideload in the recovery and on a cmd type this: adb sideload path_to_your_rom_file.zip end hit enter.

bitdomo said:
If you are on windows 8 or 8.1 you have turn of driver signiture enforecment. http://sixcolumns.com/how-to-disable-and-bypass-driver-signature-enforcement-in-windows-8/
To make adb works when you are in recovery you need the naked usb drivers. Turn on sideload in the recovery and on a cmd type this: adb sideload path_to_your_rom_file.zip end hit enter.
Click to expand...
Click to collapse
Thank you so much!! Unfortunately I am only able to hit the THANKS button once. I thought for sure that it was done for!
I have bricked my phone before, but have always been able to find a workaround. This time, not so much.
Again, Thank You!!

wltnkyl said:
Thank you so much!! Unfortunately I am only able to hit the THANKS button once. I thought for sure that it was done for!
I have bricked my phone before, but have always been able to find a workaround. This time, not so much.
Again, Thank You!!
Click to expand...
Click to collapse
you can also try unlock bootloader, flash factory images. and bumm your phone works again.
install fastboot and etc... http://forum.xda-developers.com/showthread.php?t=2588979
guide to return stock http://forum.xda-developers.com/showthread.php?t=2513701
Oh and send me an e-mail: [email protected] then I will instruct you to downlaod teamviewer, so I could resolve your driver problems

You should give wag tool a try it completely brings you back to stock
Sent from my Nexus 5 using XDA Premium 4 mobile app

[Q] Softbricked after 4.3.3

Hey guys, semi-noob here. Here is the situation:
1) encrypted device yesterday (Nexus 5 w/ stock android 4.4.2 and CWM Recovery)
2) 4.4.3 came out, downloaded and installed (yee! new dialer)
3) restarted after install (so excited! :fingers-crossed
4) enter the bootloop
5) try to do fastboot -> recovery mode
6) nope. recovery mode = bootloop
What do, XDA? I searched the forums, and nothing seems to address this. The N5 isn't even showing up on the devices list for my comp (W7 w/ ADB installed and ran before). I can't talk to it through my computer.

haloux said:
Hey guys, semi-noob here. Here is the situation:
1) encrypted device yesterday (Nexus 5 w/ stock android 4.4.2 and CWM Recovery)
2) 4.4.3 came out, downloaded and installed (yee! new dialer)
3) restarted after install (so excited! :fingers-crossed
4) enter the bootloop
5) try to do fastboot -> recovery mode
6) nope. recovery mode = bootloop
What do, XDA? I searched the forums, and nothing seems to address this. The N5 isn't even showing up on the devices list for my comp (W7 w/ ADB installed and ran before). I can't talk to it through my computer.
Click to expand...
Click to collapse
Hi.
Boot into bootloader
open cmd
Type fastboot devices
See if your device gets detected or not.
If yes..you can flash stock factory IMG.
If not make sure u have installed the drivers and adb set up is there.
Sent from my Nexus 5 using XDA Free mobile app

Vivek_Neel said:
Hi.
Boot into bootloader
open cmd
Type fastboot devices
See if your device gets detected or not.
If yes..you can flash stock factory IMG.
If not make sure u have installed the drivers and adb set up is there.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Hi,
Thanks for the quick response.
Win7 doesn't even detect the N5. Device manager doesn't even show that it exists (as android device or anything else). I've unplugged and replugged, no sound, multiple different ports.

Whatever you do don't use a toolkit try and fix it.If something else happens trying to diagnosis it would be very hard.Manual installation and fixing is the Best. Plus you learn how to get out of jams.

habitformer said:
Whatever you do don't use a toolkit try and fix it.If something else happens trying to diagnosis it would be very hard.Manual installation and fixing is the Best. Plus you learn how to get out of jams.
Click to expand...
Click to collapse
Will do (or won't do?). Thank you for the advice. Any tips on how to get my system to recognize the device?

So here are a list of things I've tried so far.
Verified that ADB works and is capable of recognizing an android device
Booted into fastboot and attached to 2 different computers (with no response or indication of the device on both)
Verified that ADB and all SDK software was up to date
Restarted computer to verify USB controller status
Refreshed device manager list before and after plugging in N5.
I'm at a loss. ADB was used in the past, the drivers are up to date. It's as though the N5 isn't even sending a signal to my computer that it's alive. I'm losing hope here guys. Please, someone help.

haloux said:
So here are a list of things I've tried so far.
Verified that ADB works and is capable of recognizing an android device
Booted into fastboot and attached to 2 different computers (with no response or indication of the device on both)
Verified that ADB and all SDK software was up to date
Restarted computer to verify USB controller status
Refreshed device manager list before and after plugging in N5.
I'm at a loss. ADB was used in the past, the drivers are up to date. It's as though the N5 isn't even sending a signal to my computer that it's alive. I'm losing hope here guys. Please, someone help.
Click to expand...
Click to collapse
I swear I went through this 2 days ago @scarmon25 will tell,we had a late night hangouts session.
I used a one of my many nexus cables and it finally linked up.Not to sound like a jerk but you've got USB debugging on right?
I reread your OP.If.you can get into recovery just restore a back up!!! Than all should be good.

haloux said:
So here are a list of things I've tried so far.
Verified that ADB works and is capable of recognizing an android device
Booted into fastboot and attached to 2 different computers (with no response or indication of the device on both)
I'm at a loss. ADB was used in the past, the drivers are up to date. It's as though the N5 isn't even sending a signal to my computer that it's alive. I'm losing hope here guys. Please, someone help.
Click to expand...
Click to collapse
One thing you haven't stated. Do you have the fastboot drivers installed? They're different from adb. Since you're not seeing the device after "fastboot devices", I would check and make sure.

habitformer said:
I swear I went through this 2 days ago @scarmon25 will tell,we had a late night hangouts session.
I used a one of my many nexus cables and it finally linked up.Not to sound like a jerk but you've got USB debugging on right?
I reread your OP.If.you can get into recovery just restore a back up!!! Than all should be good.
Click to expand...
Click to collapse
Yea, USB debugging was on. The recovery mode just yields the dead android.
adrman said:
One thing you haven't stated. Do you have the fastboot drivers installed? They're different from adb. Since you're not seeing the device after "fastboot devices", I would check and make sure.
Click to expand...
Click to collapse
How would I verify that? I assumed that fastboot drivers were installed bc I used them in the past.
Code:
fastboot devices
(yields)
No devices found.

I would do a search here for "windows fastboot drivers". I can't be of much help to you as I haven't used windows for several years now. Also, if you have a working Android device, see if it shows up when connected in bootloader mode as a test.
Sent from my Nexus 5 using Tapatalk

Small breakthrough:
Used a diff cable like someone suggested and my device appeared. Updated device driver and fastboot driver. ADB devices still yields no device attached though.

haloux said:
Small breakthrough:
Used a diff cable like someone suggested and my device appeared. Updated device driver and fastboot driver. ADB devices still yields no device attached though.
Click to expand...
Click to collapse
if you are in fastboot mode (or bootloader) you should use the fastboot command and not the adb.
type: fastboot devices
any signs of life?
Tapatalk-kal küldve az én Nexus 5-el

bitdomo said:
if you are in fastboot mode (or bootloader) you should use the fastboot command and not the adb.
type: fastboot devices
any signs of life?
Tapatalk-kal küldve az én Nexus 5-el
Click to expand...
Click to collapse
Wow. It worked! The device showed up! Thank you guys.

haloux said:
Wow. It worked! The device showed up! Thank you guys.
Click to expand...
Click to collapse
Not sound like a turd but I mentioned using a nexus USB cable in post #7 after mentioning my issue.

[Q] Pull data with a smashed screen

Just after updating to lollipop I completly smashed my screen. It doesn't show any usefull information and touch is not working.
Since I'm not in the mood to buy a new screen because I already bought a Note 4, I wanted to pull the data from the phone. It's pin protected but fastboot is still working, adb however is not.
After reading up a bit I found that going into cwm recovery I would still be able to acces adb.
So I with fastboot I booted cwm recovery (fastboot boot recovery.img) only to find that adb still won't find my devices.
Is there any way left to pull the data from my phone? I also have acces to a external keyboard/mouse with a otg cable but that won't seem to work either.

Boot into recovery and with your device plugged into your pc go to device manager. Do you see your device there?
Sent from my Nexus 9 using XDA Free mobile app

In recovery it doesn't show up.
On a normal boot it does, only no files are showing because of the pin lock.

Wiisper said:
In recovery it doesn't show up.
On a normal boot it does, only no files are showing because of the pin lock.
Click to expand...
Click to collapse
Google 15 second adb install xda. It has drivers as well as sets up adb and fastboot on your pc which you'll need if you can get your device detected
Edit, also download the twrp image from here and boot into it fastboot boot twrp.img (use the full name of the twrp image file) cwm sucks. http://techerrata.com/browse/twrp2/hammerhead
Sent from my Nexus 9 using XDA Free mobile app

I think I got it working, I already had adb working but it wouldn't find the correct drivers for the nexus 5.
I tried to update the drivers from google but windows said that it didn't find any correct drivers for the devices so I had to get "naked drivers" from somewhere.
After that it showed up as galaxy nexus adb interface in the device managers and adb was able to find it.
It's now pulling all the data.
Thanks you for your help!
I will report back when it's done pulling.

Wiisper said:
I think I got it working, I already had adb working but it wouldn't find the correct drivers for the nexus 5.
I tried to update the drivers from google but windows said that it didn't find any correct drivers for the devices so I had to get "naked drivers" from somewhere.
After that it showed up as galaxy nexus adb interface in the device managers and adb was able to find it.
It's now pulling all the data.
Thanks you for your help!
I will report back when it's done pulling.
Click to expand...
Click to collapse
Np, glad it seems to be working
Sent from my Nexus 9 using XDA Free mobile app

Okay got all the files from the phone!
Thanks for helping.