Database Info

Unable to re-lock nexus-s through fastboot

i'm in the process of re-locking my bootloader in order to send it to Samsung for repair (home button not working). when i run the command line "fastboot oem lock", it just keeps hanging at "waiting on device" and nothing happens. i have the correct drivers installed. when i run "adb devices", it shows up the device. however, when i run "fastboot devices", it does not show up anything. any help on relocking my bootloader would be appreciated. Thanks!

Probably shouldn't be answering this here buuuuut...
adb reboot bootloader
and THEN
fastboot oem lock.
See what happens. You have to be in boot loader mode. Please move your questions to the Q&A section sir.

i did enter that command in order to get into fastboot. after that , i ran the command "fastboot oem lock" but it gets stuck at "waiting on device"

Update your drivers

Yea at this point I'd say its a connectivity problem. Drivers and or cable, but since you are getting adb devices to recognize, its not your cable. You should really use ubuntu, you would save yourself a lot of time, because you don't really have to deal with drivers like windows.

'sudo fastboot oem lock'
You need to be super user.

sure you went into bootloader and not recovery? because adb is seen in recovery and doesnt work in bootloader!

[Q] CANNOT UNLOCK BOOTLOADER USING htcdev.com

i have registered on htcdev.com.
i followed the steps to the point where i had to execute the fastboot file to get an identifier token using a cmd command.
for some reason it say "waiting for device"
it has been like that for hours.
tried it about 3 times. I had a problem with rebooting into bootloader using VOLUME DOWN + POWER button so i ised abd and it worked
exact command i typed was "fastboot oem get_identifier_token"
PLEASE HELP ME

You don't have the right drivers for fastboot, it seems.
Find a guide and install them.

I always run ADB devices or fastboot devices first to check that I'm connected to the phone, before running any other commands.
Sent from my Nexus 7

Need help getting in to fastboot

Hi!
I unlocked my phone - but when i type in the command "adb reboot bootloader"
it goes in to fastboot for a second, and then I get "bootloader unlocked" warning and after that it boots in to android.
How can I stop at fastboot to flash a custom recovery ?
Cheers!
EDIT:
NVM fixed

I am sure it was the right way.
How did you get it fixed?

I turned it off completely and after that, it accepted the command and stayed in fastboot.

Good to know, thanks for the information.

Can't unlock bootloader

I bought a Oneplus One 64gb from china with cynamogen pre-flashed on it, I tried to unlock the bootloader following various guides on this site but I'm stuck.
I manage to put the device on fastboot mode (three chinese words followed by "fastboot...") and the computer recognize it through "fastboot devices", when I input "fastboot oem unlock" it says "done" but when I input "fastboot reboot" the one reboots normally without wiping anything
It makes no sense
I'm not english, sorry if you find some errors
edit i finally managed to root it, you can close the thread

Tmobile oneplus 8 - Unlock bootloader

I have my tmo oneplus 8 sim unlocked and checked "OEM Unlocked" and "USB debugging". When I executed the command " fastboot.exe oem get_unlock_code" in Fastboot mode, following https://support.oneplus.com/app/ans...-bootloader-for-oneplus-6t-(t-mobile-edition). On Windows, it keeps saying "Waiting for any device". Any steps I missed?

zrzhu said:
I have my tmo oneplus 8 sim unlocked and checked "OEM Unlocked" and "USB debugging". When I executed the command " fastboot.exe oem get_unlock_code" in Fastboot mode, following https://support.oneplus.com/app/answers/detail/a_id/588/~/how-to-unlock-bootloader-for-oneplus-6t-(t-mobile-edition). On Windows, it keeps saying "Waiting for any device". Any steps I missed?
Click to expand...
Click to collapse
Run the command while in bootloader.

crazynapkinman said:
Run the command while in bootloader.
Click to expand...
Click to collapse
yes. That's what I did.

zrzhu said:
yes. That's what I did.
Click to expand...
Click to collapse
No, you ran it in fastboot. Also the commands are wrong.
Fastboot oem get_unlock_code
Happy modding

Nathan.7118391 said:
No, you ran it in fastboot. Also the commands are wrong.
Fastboot oem get_unlock_code
Happy modding
Click to expand...
Click to collapse
Just did some research and finally figured it out. I have to disable Windows 10 driver signature.
I followed the instructions here: https://forums.oneplus.com/threads/op-x-in-fastboot-mode-unlock-oem-waiting-for-device.1010279/.
Just want to share. in case some one else has the same issues.

Nathan.7118391 said:
No, you ran it in fastboot. Also the commands are wrong.
Fastboot oem get_unlock_code
Happy modding
Click to expand...
Click to collapse
Bootloader And fastboot are the exact same thing

zrzhu said:
I have my tmo oneplus 8 sim unlocked and checked "OEM Unlocked" and "USB debugging". When I executed the command " fastboot.exe oem get_unlock_code" in Fastboot mode, following https://support.oneplus.com/app/answers/detail/a_id/588/~/how-to-unlock-bootloader-for-oneplus-6t-(t-mobile-edition). On Windows, it keeps saying "Waiting for any device". Any steps I missed?
Click to expand...
Click to collapse
I have same issue on the 7tpro, did you ever find a solution?

ogtigerman said:
I have same issue on the 7tpro, did you ever find a solution?
Click to expand...
Click to collapse
This seems to be a drivers problem. You should update them.

ogtigerman said:
I have same issue on the 7tpro, did you ever find a solution?
Click to expand...
Click to collapse
You to disable Windows 10 driver signature in order to have the drivers installed successfully. See my post above.