Mac OS X Fastboot Mode <Waiting for Device> - Samsung Galaxy Nexus

Hi, I am trying to Re-Lock my Galaxy Nexus GSM version, I've downloaded the SDK files (adb-mac and fastboot-mac) and all the image files and I am trying to execute the following commands:
adb reboot bootloader
fastboot flash bootloader bootloader-toro-primekk15.img
fastboot reboot-bootloader
fastboot flash radio radio-toro-i515.ek02.img
fastboot reboot-bootloader
fastboot flash radio-cdma radio-cdma-toro-i515.ek05.img
fastboot reboot-bootloader
fastboot -w update image-mysid-icl53f.zip
fastboot reboot-bootloader
fastboot oem lock
With the phone in normal mode I connect the USB cable to the computer, start Terminal windows and run the first command, "./adb-mac reboot bootloader" and the phone will boot into the "Fastboot Mode", then I try to execute "./fastboot-mac devices" to make sure the phone is connected and properly detected and I get nothing.
If I try to execute "./fastboot-mac flash bootloader bootloader-toro-primekk15.img" I get the message <waiting for device> and it will stay there forever.
Do you know what might be the problem ?, is there other method to do this ?, go back to Stock ROM and Re-Lock the device ?, thanks

You must also install the Samsung usb drivers. I have no idea how to do this in mac. A simple search will help you tho.

Related

[Q] fastboot stuck

i have just flashed a new recovery, and everything is just fine until i typed this:
fastboot reboot
and it does not reboot fastboot,stucks on first screen but!
pull out battery and entering by hardware key works, all fastboot, bootloader, my ROM, the new recovery.
so that confuses me, i can enter manually, but by adb i cant?
ADB works at the Bootloader and Recovery.
Fastboot works at the Fastboot mode.
Fastboot != ADB
Different commands, different purpose.
If you need reboot to fastboot command is:
"fastboot reboot-bootloader"
"fastboot reboot" just reboots your phone.

can't unroot/relock GNex - please help

I walked through the following steps to put the stock OS back on my device...
adb reboot bootloader
fastboot flash bootloader bootloader-toro-primekk15.img
fastboot reboot-bootloader
fastboot flash radio radio-toro-i515.ek02.img
fastboot reboot-bootloader
fastboot flash radio-cdma radio-cdma-toro-i515.ek05.img (Note: This one takes a couple minutes. Be patient)
fastboot reboot-bootloader
fastboot -w update image-mysid-icl53f.zip
I now have the stock OS loaded and can boot alright, unlocked. When I get back into the OS I turn debugging on and then head back to adb. I can browse to my device through the USB but get the following error when attaching to my device.
c:\android\android-sdk\platform-tools\adb shell
[email protected]:/ $ adb reboot bootloader
adb reboot bootloader
error: device not found
1|[email protected]:/ $
Further, if I run "fastboot devices" from my command prompt I get no devices returned.
What am I missing?? I need to get this device relocked to send back in for warranty quickly. I'm trying to get the device locked back up. Any help you can provide is appreciated!
Edit: Resolved now
nevermind... whew... figured it out.
Mark threads as solved and update first post with whats happening, so one doesnt waste time like i did.
No need to double post for that.

Fastboot/Command Line failing

Been an incredibly bad week for me as far as technology is concerned. Everything around me seems to be breaking apart form my new One X. That is of course.. until now..
I'm trying to flash TripNDroid's CM10 Rom to my phone by following my self written instructions that have worked like a charm for me so far.
Enter Fastboot on phone. Open the command line window in the relevant place in windows and check it's connected using 'fastboot devices' command. Then:
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
fastboot erase recovery
fastboot flash recovery-clockwork-touch-5.8.4.0-endeavoru.img
fastboot flash boot boot.img
Enter recovery and flash the ROM.
However, I'm getting mixed responses in the command line. Very occasionally I will type a command in and it will accept it. and say 'Done' but 90% of the time it will say 'FAILED (remote: 0000004)' or occasionally 'remote: not allowed'
I have checked that the usb is connected (it is the original cable) and used the fastboot devices command to confirm this. I have tried rebooting the bootloader and redownloading fastboot and the files to be flashed. Completely stuck D:

adb reboot-bootloader not putting me in fastboot mode

Anybody know why when I use adb reboot-bootloader doesn't put me into fastboot mode? All it does is a normal reboot.
have you tried the command in terminal emultator (Download)?:
Code:
su
Code:
reboot bootloader
Otherwise order/build a fastboot/factory cable

fastboot unresponsive

I haven't touched my LG G7 in a while, so I decided to flash original boot_a/b to be able to OTA update. But when I boot into bootloader, fastboot can't do anything, command simply hangs until I interrupt it.
It is not just that the:
Code:
fastboot flash boot_a boot_v10p.img
fails, but not even:
Code:
fastboot flashing get_unlock_ability
works.
Fastboot recognize the device properly:
Code:
# fastboot devices
LMG710EMabd8a3d8 fastboot
Any thoughts?

Categories

Resources