Database Info

[Q] NS4g - Not detected by fastboot!

Google doesn't know, so maybe the experts here can help.
I'm trying to unlock the bootloader of my Nexus S 4G.
I installed drivers via PDAnet. USB Debugging is on. Windows detects the device, both when its on in normal mode, and in Fastboot mode. ADB detects the phone when on.
Fastboot won't detect it when in Fastboot mode, though!
ADB won't detect it in Fastboot, either. (But maybe that's normal.)
Why doesn't fastboot see it?
I'm running Win7 x64, if that helps.
Thanks in advance.

pennyfan87 said:
Google doesn't know, so maybe the experts here can help.
I'm trying to unlock the bootloader of my Nexus S 4G.
I installed drivers via PDAnet. USB Debugging is on. Windows detects the device, both when its on in normal mode, and in Fastboot mode. ADB detects the phone when on.
Fastboot won't detect it when in Fastboot mode, though!
ADB won't detect it in Fastboot, either. (But maybe that's normal.)
Why doesn't fastboot see it?
I'm running Win7 x64, if that helps.
Thanks in advance.
Click to expand...
Click to collapse
What happens when you type:
Fastboot devices
?
Sent from my Nexus S using XDA App

matt2053 said:
What happens when you type:
Fastboot devices
?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Nothing shows up. No errors. No devices.

Are you in bootloader mode when you're doing fastboot commands?

zephiK said:
Are you in bootloader mode when you're doing fastboot commands?
Click to expand...
Click to collapse
I'm in "fastboot mode", I think that's what its called.
I get there by holding Vol Up + Power when I turn it on.

pennyfan87 said:
I'm in "fastboot mode", I think that's what its called.
I get there by holding Vol Up + Power when I turn it on.
Click to expand...
Click to collapse
If you have the USB Driver from the SDK installed edit android_winusb.inf and add:
;Nexus S
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E20&REV_0100
Go into device manager and tell it to update the driver, hit pick from list, all and have disk. Pick the INF and let it install.

pennyfan87 said:
I'm in "fastboot mode", I think that's what its called.
I get there by holding Vol Up + Power when I turn it on.
Click to expand...
Click to collapse
Search is your friend...
http://forum.xda-developers.com/showthread.php?t=878786
Please read the whole post for instructions...

Are you running command prompt as Administrator?
pennyfan87 said:
Google doesn't know, so maybe the experts here can help.
I'm trying to unlock the bootloader of my Nexus S 4G.
I installed drivers via PDAnet. USB Debugging is on. Windows detects the device, both when its on in normal mode, and in Fastboot mode. ADB detects the phone when on.
Fastboot won't detect it when in Fastboot mode, though!
ADB won't detect it in Fastboot, either. (But maybe that's normal.)
Why doesn't fastboot see it?
I'm running Win7 x64, if that helps.
Thanks in advance.
Click to expand...
Click to collapse
Hi, I had the same problem, I fixed it by giving the command prompt root permissions (I'm using Linux). On Windows, make sure the command prompt is running AS THE ADMINISTRATOR

[Q] Fastboot and locking problems

hey so i need to send my nexus s in for repair and i have stock rom and recovery, but every time i try fastboot oem lock it just sits at "waiting for device"
ADB works fine.
I tried alternative drivers
What can i do to re lock my phone?

Are you in the bootloader? (Phone off -> Vol. Up + Power -> fastboot oem lock).
Also, does the command "fastboot devices" show your device?

The USB connector socket at the phone might not make a proper contact with the USB plug. Make sure they connect properly. You may try another cable, or have a look at your USB socket and compare it to another. Check out particularly the little horizontal part in the USB socket.
Make sure you're in bootloader/fastboot mode before attempting to connect in fastboot. Fastboot cannot detect your phone, make sure your udev related settings are appropriate. Check on a Linux PC: https://source.android.com/source/initializing.html Configuring USB Access section.
If after this your phone will not be recognized by fastboot, please post the output of the following command (as root), after seconds after connecting the phone in fastboot mode:
Code:
tail /var/log/messages

Harbb said:
Are you in the bootloader? (Phone off -> Vol. Up + Power -> fastboot oem lock).
Also, does the command "fastboot devices" show your device?
Click to expand...
Click to collapse
fastboot does not show my device. I go into bootloader using adb reboot bootloader because my stupid power button wont work, thats why i want to sent it in to get fixed.

If drivers are properly installed this might not be working because the power button is stuck in or something. Not sure what to try to sort it out if that's the case.

mikeydubbs said:
hey so i need to send my nexus s in for repair and i have stock rom and recovery, but every time i try fastboot oem lock it just sits at "waiting for device"
ADB works fine.
I tried alternative drivers
What can i do to re lock my phone?
Click to expand...
Click to collapse
1 - Boot your phone into fastboot mode.
2 - open cmd in your pc.
3 - write: cd \"name of the file where your fastboot is in your pc", and then press enter.
4 - write: fastboot oem lock
5 - press enter and it's done!

bjuderas said:
1 - Boot your phone into fastboot mode.
2 - open cmd in your pc.
3 - write: cd \"name of the file where your fastboot is in your pc", and then press enter.
4 - write: fastboot oem lock
5 - press enter and it's done!
Click to expand...
Click to collapse
if you read the first post it says that fastboot doesnt work

mikeydubbs said:
if you read the first post it says that fastboot doesnt work
Click to expand...
Click to collapse
Sorry, didn't read it right!
And I'm sorry, but I don't know the solution for your problem!

have you tried using a different usb port on your pc?
sent from my dark iced, skanky, t11 infused ns4g

p1gp3n said:
have you tried using a different usb port on your pc?
sent from my dark iced, skanky, t11 infused ns4g
Click to expand...
Click to collapse
yeah i have and i tried using my laptop, and ubuntu 11.10
this sucks so much

i sent my phone in for a broken power button as well. I couldn't even get into the bootloader to relock it so i sent it with an unlocked bootloader. they still fixed it.

shahravi94 said:
i sent my phone in for a broken power button as well. I couldn't even get into the bootloader to relock it so i sent it with an unlocked bootloader. they still fixed it.
Click to expand...
Click to collapse
so do you think as long as its not rooted they wont care?

yup! i flashed a stock image so it was unrooted and sent it in. they fixed it up for me

If you are using Linux you might need su permissions!
Try:
sudo fastboot oem lock

mikeydubbs said:
hey so i need to send my nexus s in for repair and i have stock rom and recovery, but every time i try fastboot oem lock it just sits at "waiting for device"
ADB works fine.
I tried alternative drivers
What can i do to re lock my phone?
Click to expand...
Click to collapse
Hi, I know this thread is old but I was having the same problem relocking my nexus 4 after installing stock Android 4.4.3 KitKat.
I'm using Nexus Root Toolkit, I don't know what tools you're using to lock your nexus S boblem ut this very easy to use it downloads the drivers and what ever you need to lock, unlock or flash stock and custom roms for any Nexus device.
So my problem was that I would launch OEM Lock on Nexus Root Toolkit and it would detect the device, reboot in Fastboot mode and it would proceed just fine but after saying "Launching TWRP.... something" it would reboot the phone and say to me "Waiting for device" untill it would time out.
I found out that when the program(NEXUS ROOT TOOLKIT) asked me to download a TWRP IMG files, I said no everytime because I didn't think I'd need it. So after trying 5 times, I allowed it to download it and i retryed to OEM Lock it and MAGIC!
Somewhere in the process of Locking the rom it is going to need the TWRP File so allowing the program to download it solved it for me.
I don't know if this will help you or if you still have the same phone, but if you do have use Nexus Root Toolkit and download all it asks and you'll be fine.
Good Luck.

"waiting for device" forever when "fastboot oem unlock:
mikeydubbs said:
hey so i need to send my nexus s in for repair and i have stock rom and recovery, but every time i try fastboot oem lock it just sits at "waiting for device"
ADB works fine.
I tried alternative drivers
What can i do to re lock my phone?
Click to expand...
Click to collapse
I have the same exact problem.
ADB works fine when the phone is up & running, so I am suspecting a driver compatibility problem when the phone is in "FASTBOOT MODE".
I tried to install the "Universal Naked Driver 0.73 (Compatible with Nexus 5, 4, 7, 10 and S)" but Windows 7 64-bit refuses to pick it up. I use the Device Manager method which shows (when the phone is in "FASTBOOT MODE"):
Code:
"Other Devices
> Android 1.0"
When the phone is up & running, Device Manager shows it as:
Code:
"Android USB Devices
> SAMSUNG Android Composite ADB Interface"
Any idea how to proceed from here?
-----
Update: After a day went by, I searched Google some more and found a thread that describes exactly my problem:
http://forum.xda-developers.com/nexus-s/help/nexus-s-root-windows-requests-android-1-t878579
Which led me to:
http://forum.xda-developers.com/nex...oader-nexus-s-t875580/post9861928#post9861928
Which led me to:
http://pdanet.co/a/
I am rushing to try this now...
-------
Success!
~> fastboot oem unlock
...
OKAY [ 18.734s]
finished. total time: 18.734s
Click to expand...
Click to collapse

nunojpg said:
If you are using Linux you might need su permissions!
Try:
sudo fastboot oem lock
Click to expand...
Click to collapse
It helped. Thanks!

mikeydubbs said:
hey so i need to send my nexus s in for repair and i have stock rom and recovery, but every time i try fastboot oem lock it just sits at "waiting for device"
ADB works fine.
I tried alternative drivers
What can i do to re lock my phone?
Click to expand...
Click to collapse
Well before trying to Relock the device see whether its connected or not. Type this command fastboot devices and hit enter see whether it shows some no. As in a reply if not that means the deivce isnt connected. If the device is connected type this command to relock your device fastboot oem lock and hit enter. Check on your device screen The Lock status will be changed to LOCKED.
If Helped Click Thanks
---------- Post added at 03:30 PM ---------- Previous post was at 03:27 PM ----------
mikeydubbs said:
hey so i need to send my nexus s in for repair and i have stock rom and recovery, but every time i try fastboot oem lock it just sits at "waiting for device"
ADB works fine.
I tried alternative drivers
What can i do to re lock my phone?
Click to expand...
Click to collapse
Well before trying to Relock the device see whether its connected or not. Type this command fastboot devices and hit enter see whether it shows some no. As in a reply if not that means the deivce isnt connected. If the device is connected type this command to relock your device fastboot oem lock and hit enter. Check on your device screen The Lock status will be changed to LOCKED.
If Helped Click Thanks

cant't access bootloader (tried everything)

hi all
I have strange problem
I can't access bootloader I tried these ways:
A- vol down + power = nothing just boot normally
B- in fast boot usb: fastboot reboot-bootloader = nothing still in fastboot
C- in extended power menu : restart - bootloader = fastboot
excuse my poor english
please any help

dude you are in bootloader ..when connected to pc ..it will go to fastboot usb (infact fastboot is part of bootloader)
1.you need to remove battery ,then reinsert it then do volume down + power ..or uncheck the fastboot in settings->power then volume down + power
2.obvious ..as long as connected to pc ..it will be in fastboot
3.when connected to pc ..it happens

This is not my first time to install radio
I didn't ask before reading and searching
Still waiting help

Fastboot is/is part of the bootloader. From fastboot you have the 'Bootloader' option, which will load the HBOOT and thus scan for a PG58IMG.* on your SDcard.
/thread.

The funny thing is when I push vol down it scrolls up
When I push power nothing happen
In other word when I highlite bootloader then push power to choose nothing happen

thunder2007 said:
The funny thing is when I push vol down it scrolls up
When I push power nothing happen
In other word when I highlite bootloader then push power to choose nothing happen
Click to expand...
Click to collapse
If you want to go to bootloader only then.. Do this.. Type adb reboot bootloader from phone connected normally then once the coand is done.. Immediately remove the usb cable.. That will take you to hboot only
Sent from my HTC Sensation 4G using xda premium

ganeshp said:
If you want to go to bootloader only then.. Do this.. Type adb reboot bootloader from phone connected normally then once the coand is done.. Immediately remove the usb cable.. That will take you to hboot only
Sent from my HTC Sensation 4G using xda premium
Click to expand...
Click to collapse
nothing same as before
by the way did anybody have this strange problem
I mean why the power not respoding while it does response if not in fastboot

ok I lost hope about bootloader
is the any way to install radio than the bootloader method
by fastboot for examble
this is Q&A section right. I mean not Q&Q
I am repeating my self here

http://forum.xda-developers.com/showthread.php?t=1202867
Extract the radio.img from your PG58IMG.zip and then:
Code:
fastboot flash radio radio.img

thanks this helped me
bout there is no answer to my Q. how could the power button not function in fastboot

thunder2007 said:
thanks this helped me
bout there is no answer to my Q. how could the power button not function in fastboot
Click to expand...
Click to collapse
Reflash the firmware that might help
And I still didn't understood your question.. I keep on saying fastboot is part of bootloader.. And you still say can't access bootloader..
Sent from my HTC Sensation 4G using xda premium

[Q] Fastboot not working

hi..
my problem is, when i connect my CHACHA with ma PC in FASTBOOT mode, and trying to flash boot and system by CMD Promt the commands are " fastboot flash boot boot.img" and " fastboot flash system system.img".. but CMD window reply me "waiting for device". And I cant flash anything.
how can i solve it?

Are you sure you connect it properly?
You must first boot the phone in bootloader. To do so, go to settings>power>fastboot and untick that option. After that power off your phone.
Unplug your usb cable from the phone if it is still plugged. Start your phone pressing volume down and power buttons simultaneosly for about 5 seconds. After that, you will see the bootloader screen. It wil make a search and could say "wrong image", something like that but this is nothing important. After that, select fastboot using volume rocker buttons and tap power button to select your option. Now the phone will be in fastboot. Now all you have to do is to plug your usb cable first to the pc and later phone. The reading on the screen will change from fastboot to usb fast boot. After seeing it is "usb fastboot" you are good to go.

Still cant connect the phone.. thnks.
Sent from my HTC ChaCha A810e using xda app-developers app

Djstar_htc said:
Still cant connect the phone.. thnks.
Sent from my HTC ChaCha A810e using xda app-developers app
Click to expand...
Click to collapse
Do you have the drivers installed on your pc? Try installing HTC Sync Manager and it should also install the necessary drivers for connection.

furkandeger said:
Do you have the drivers installed on your pc? Try installing HTC Sync Manager and it should also install the necessary drivers for connection.
Click to expand...
Click to collapse
oh!!!... I have already installed it. But i saw that " ANDROID 1.0" Device driver was missing. Now i have got it from "PdaNet".
Thanks Buddy..

[Q] bricked volume key, not able to reboot in recovery

Hello all,
i have a htc sensation 4G S-off.
i broked its display, and while repairing it broken the volume key cable. now volume key not working.
i installed PACman rom 1.2 and wifi was not working.
as directed in that thread of PACman i installed beta version sultan kernel.
now its not booting, just getting the HTC splash screen and then again going off.
i tried it to connect via PC but no success , neither adb, nor fastboot, recognzing it connected.

you can go to bootloader the traditional way atleast?
remove battery --reinsert it -> hold power + volume down ..until you get to bootloader
then connect to PC (if conncected properly thge phone says FASTBOOT USB)
then you can atleast use fastboot
in the mean time from the zip of the PAC MAN rom you've installed ..extract the boot.img and copy it to your fastboot/adb folder
then type this command
fastboot flash boot boot.img
then reboot using this command
fastboot reboot
and next time find the proper kernel and flash it (be careful this time )

ganeshp said:
you can go to bootloader the traditional way atleast?
remove battery --reinsert it -> hold power + volume down ..until you get to bootloader
then connect to PC (if conncected properly thge phone says FASTBOOT USB)
then you can atleast use fastboot
in the mean time from the zip of the PAC MAN rom you've installed ..extract the boot.img and copy it to your fastboot/adb folder
then type this command
fastboot flash boot boot.img
then reboot using this command
fastboot reboot
and next time find the proper kernel and flash it (be careful this time )
Click to expand...
Click to collapse
the volume key hardware is broken, so not able to enter bootloader or recovery.

pseudofarji said:
the volume key hardware is broken, so not able to enter bootloader or recovery.
Click to expand...
Click to collapse
ahh yes :/
what else ..hmm
try this
adb wait-for-device
if you got the command prompt back after the above command ...you got adb
then immediately try
adb reboot recovery

ganeshp said:
ahh yes :/
what else ..hmm
try this
adb wait-for-device
if you got the command prompt back after the above command ...you got adb
then immediately try
adb reboot recovery
Click to expand...
Click to collapse
i uninstalled the htc drivers and then reinstalled. and then used the adb reboot recovery command as you told previously.
now its been recognized by adb in recovery mode.
thanks now my problem is solved.

pseudofarji said:
Hello all,
i have a htc sensation 4G S-off.
i broked its display, and while repairing it broken the volume key cable. now volume key not working.
i installed PACman rom 1.2 and wifi was not working.
as directed in that thread of PACman i installed beta version sultan kernel.
now its not booting, just getting the HTC splash screen and then again going off.
i tried it to connect via PC but no success , neither adb, nor fastboot, recognzing it connected.
Click to expand...
Click to collapse
I know issue have been solved with help of ganeshp but to help other people there's a quite more simple way, htc sensation 4g tool, it also let u unlock bootloader in 4 clicks and flash new recovery but it also let u boot into bootloader and boot into recovery in one click: http://forum.xda-developers.com/showthread.php?t=1497404
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium

dany xe said:
I know issue have been solved with help of ganeshp but to help other people there's a quite more simple way, htc sensation 4g tool, it also let u unlock bootloader in 4 clicks and flash new recovery but it also let u boot into bootloader and boot into recovery in one click: http://forum.xda-developers.com/showthread.php?t=1497404
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
Click to expand...
Click to collapse
i tried 2-3 tools available for sensation before posting here, but none was able to detect the device.
i guess the issue in my case was only due to corrupt htc drivers and the broken volume key was just giving it a more confusion.
i also tried first repairing of the drivers but that doesnt helped me. then i tried uninstalling and reinstalling drivers and that solved out the issue.

pseudofarji said:
i tried 2-3 tools available for sensation before posting here, but none was able to detect the device.
i guess the issue in my case was only due to corrupt htc drivers and the broken volume key was just giving it a more confusion.
i also tried first repairing of the drivers but that doesnt helped me. then i tried uninstalling and reinstalling drivers and that solved out the issue.
Click to expand...
Click to collapse
This tool is new and u can install htc drivers from it
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium

Yeah I know about the tool
But inside it does the same way as I'm explaining
Btw the tool perfectly works when you can boot your phone fine and ofcourse it will cause troubles when you can't boot the phone fine
But that's not the case here .. This guy's case is pretty hard here.. He can't boot to bootloader manually and also he is stuck at splash screen (where there is 90% chance that adb won't work).. Luckily he fell in the 10% category
Sent from my Nexus 7 using xda premium

Will it work on HTC One C ?
ganeshp said:
ahh yes :/
what else ..hmm
try this
adb wait-for-device
if you got the command prompt back after the above command ...you got adb
then immediately try
adb reboot recovery
I think I have the same problem ... Don't weither the Volume down button is bricked or broken ... But I'll try this method ...
Click to expand...
Click to collapse