Related
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
I need to restore to stock firmware to get Lollipop, but adb won't recognise my phone in cmd, thus I can't follow this guide: http://forum.xda-developers.com/showthread.php?t=2542219 . I installed the Motorola Drivers from here: http://forum.xda-developers.com/showthread.php?t=2550635 , and I have the Motorola Device Manager installed. MotoTool picks up my device and is able to boot it into fastboot and install CWM or TWRP, but when I try to flash stock recovery using MotoTool it either gives me a 'no command' screen or doesn't work at all. Anyone having the same problem/know how to fix this? I'm on the Moto G 2013 XT1032 British retail.
EDIT: I fixed it! I replaced Moto Tool's stock recovery with the one that was included in here: http://forum.xda-developers.com/show...3#post54872143 then used Moto Tool to flash it, as that recognised my phone. I could then download the OTA as normal and installed it like a regular update. Enjoying Lollipop!
If the phone is in fastboot mode, try using fastboot commands on your computer. At the command prompt, type fastboot devices to see of your phone's serial # appears.
Do you have USB debugging enabled in settings?
Are you opening cmd in the directory where fastboot and adb were installed?
Are you sure you installed adb and fastboot correctly?
audit13 said:
If the phone is in fastboot mode, try using fastboot commands on your computer. At the command prompt, type fastboot devices to see of your phone's serial # appears.
Click to expand...
Click to collapse
SammyP6 said:
Do you have USB debugging enabled in settings?
Are you opening cmd in the directory where fastboot and adb were installed?
Are you sure you installed adb and fastboot correctly?
Click to expand...
Click to collapse
Yes to both of these, I was in fastboot and 'adb devices' came back with nothing even though I was in the directory where adb and fastboot were installed and the phone had USB debugging enabled. I fixed it a different way though, I replaced Moto Tool's stock recovery with the one that was included in here: http://forum.xda-developers.com/showthread.php?p=54872143#post54872143 then used Moto Tool to flash it as that recognised my phone. I could then download the OTA as normal and installed it like a regular update.
Adb commands won't work when the phone is in fastboot mode from what I have seen.
audit13 said:
Adb commands won't work when the phone is in fastboot mode from what I have seen.
Click to expand...
Click to collapse
They didn't work at all, no matter what mode I was in. All sorted now though.
Fithboy said:
They didn't work at all, no matter what mode I was in. All sorted now though.
Click to expand...
Click to collapse
It's great you that got the issue sorted out.
Post your solution in case it may help other users down the road. Thanks.
Hey guys, I really need some help here, I'm not good at any of this stuff - my OPO just randomly got stuck on a boot loop, I have never played with the USB debugging or any of that or tried to flash anything else, I was using just stock cyanogen.
I've been reading around and I've downloaded all the drivers but still can't detect the device when I do the Shift + Right Click --> Run CMD "fastboot devices" or "adb devices".
I never enabled options such as the USB debugging or anything else, can someone please help me out? I'm really clueless to all of this stuff.
You must first put your phone in fastboot mode.
To put your phone in fastboot mode, turn it off, and then hold power+volume down until you get a screen with only the cyanogenmod logo. If you get to this screen, you're in fastboot mode. If you have installed the proper drivers in your computer, you should be able to connect to the phone from your computer. Connect your usb cable to the phone and the computer, open a dos box and type "fastboot devices". If you get a series of letters and numbers then you're OK.
jchen221 said:
Hey guys, I really need some help here, I'm not good at any of this stuff - my OPO just randomly got stuck on a boot loop, I have never played with the USB debugging or any of that or tried to flash anything else, I was using just stock cyanogen.
I've been reading around and I've downloaded all the drivers but still can't detect the device when I do the Shift + Right Click --> Run CMD "fastboot devices" or "adb devices".
I never enabled options such as the USB debugging or anything else, can someone please help me out? I'm really clueless to all of this stuff.
Click to expand...
Click to collapse
joanquro said:
You must first put your phone in fastboot mode.
To put your phone in fastboot mode, turn it off, and then hold power+volume down until you get a screen with only the cyanogenmod logo. If you get to this screen, you're in fastboot mode. If you have installed the proper drivers in your computer, you should be able to connect to the phone from your computer. Connect your usb cable to the phone and the computer, open a dos box and type "fastboot devices". If you get a series of letters and numbers then you're OK.
Click to expand...
Click to collapse
This, except that's the wrong button combo (power + volume down is for recovery). Use power + volume up to get to fastboot mode and then try the "fastboot devices" command.
Heisenberg said:
This, except that's the wrong button combo (power + volume down is for recovery). Use power + volume up to get to fastboot mode and then try the "fastboot devices" command.
Click to expand...
Click to collapse
I'm sorry for this mistake.
joanquro said:
You must first put your phone in fastboot mode.
To put your phone in fastboot mode, turn it off, and then hold power+volume down until you get a screen with only the cyanogenmod logo. If you get to this screen, you're in fastboot mode. If you have installed the proper drivers in your computer, you should be able to connect to the phone from your computer. Connect your usb cable to the phone and the computer, open a dos box and type "fastboot devices". If you get a series of letters and numbers then you're OK.
Click to expand...
Click to collapse
Thanks for your advice. This is the big problem I'm having, I've downloaded the SDK slim, and the driver manager and the 15 second installer things and installed all of them but still can't manage to detect my phone on fastboot.
jchen221 said:
Thanks for your advice. This is the big problem I'm having, I've downloaded the SDK slim, and the driver manager and the 15 second installer things and installed all of them but still can't manage to detect my phone on fastboot.
Click to expand...
Click to collapse
What command are you using while in fastboot mode?
Heisenberg said:
What command are you using while in fastboot mode?
Click to expand...
Click to collapse
I'm using both
fastboot devices
adb devices
Fastboot devices comes back with nothing in the CMD box, ADB devices gives a message that says 'Devices:' but there are none listed.
jchen221 said:
I'm using both
fastboot devices
adb devices
Fastboot devices comes back with nothing in the CMD box, ADB devices gives a message that says 'Devices:' but there are none listed.
Click to expand...
Click to collapse
There's no point in using adb commands in fastboot because only fastboot commands work. What drivers do you have installed?
XDA Moderator
Transmitted via Bacon
Heisenberg said:
There's no point in using adb commands in fastboot because only fastboot commands work. What drivers do you have installed?
XDA Moderator
Transmitted via Bacon
Click to expand...
Click to collapse
I've looked around for all sorts of drivers, I have the universal ADB, android SDK slim or something, is there a specific one I need?
jchen221 said:
I've looked around for all sorts of drivers, I have the universal ADB, android SDK slim or something, is there a specific one I need?
Click to expand...
Click to collapse
Uninstall whatever drivers you have installed, reboot your PC, install these drivers, reboot your PC, connect your phone, test fastboot (fastboot devices).
Heisenberg said:
Uninstall whatever drivers you have installed, reboot your PC, install , reboot your PC, connect your phone, test fastboot (fastboot devices).
Click to expand...
Click to collapse
I tried that, but again no response in CMD when I type fastboot devices.
Although I just tried and am able to boot into recovery mode, would I be able to do some sort of factory reset there? I've already tried to wipe user data but I'm still getting a bootloop there.
jchen221 said:
I tried that, but again no response in CMD when I type fastboot devices.
Although I just tried and am able to boot into recovery mode, would I be able to do some sort of factory reset there? I've already tried to wipe user data but I'm still getting a bootloop there.
Click to expand...
Click to collapse
I can't remember what capabilities the stock recovery has, but if it's there it's worth trying.
jchen221 said:
I tried that, but again no response in CMD when I type fastboot devices.
Although I just tried and am able to boot into recovery mode, would I be able to do some sort of factory reset there? I've already tried to wipe user data but I'm still getting a bootloop there.
Click to expand...
Click to collapse
Heisenberg said:
I can't remember what capabilities the stock recovery has, but if it's there it's worth trying.
Click to expand...
Click to collapse
I managed to get it to work after resetting a bunch of the options, thanks so much for your help with this (even if I didn't get it to fastboot mode)
I have the same problem.
jchen221 said:
I managed to get it to work after resetting a bunch of the options, thanks so much for your help with this (even if I didn't get it to fastboot mode)
Click to expand...
Click to collapse
Hey bro, I have the same problem. Can you please explain me how did you resolve it? This would be of great help. Thanks.
pavanakshay said:
Hey bro, I have the same problem. Can you please explain me how did you resolve it? This would be of great help. Thanks.
Click to expand...
Click to collapse
for me too bro same problem please help me
---------- Post added at 08:28 AM ---------- Previous post was at 08:25 AM ----------
Heisenberg said:
Uninstall whatever drivers you have installed, reboot your PC, install these drivers, reboot your PC, connect your phone, test fastboot (fastboot devices).
Click to expand...
Click to collapse
i too having the same problem bro the driver link is not working please send me the link thankyou in advance
i am also facing the same problem that phone loops into fast boot mode whenever turned on i do totally every kind of drivers softwares and etc like tenorshare but all in vain i guess at last that phone must be enabled usb debuging in order to be detected as a active adb device,i pratically do this stuff by using another phone with enabled debuging and it was an active device andd can be processed further but when i disabled the usb debugging of same phone it was not working with adb interface i hope you understand,,,,but a miracle happenend i removed the battery for about a week and suddenly i pluged and try to turn it on hola it starts from roms boot logo
HELP!!!!! Stuck on bootloop and fastboot not working
i was flashing twrp on infinix s4 withfast boot. after flashing the device is stuck on bootloop. the recovery is not accessible (i press the key combo nothing happens) and fastboot combination is also not working. i tried connecting it with adb cmd and ran the command "adb reboot bootloader" but no device is detected.
ps: the link for drivers is broken
I was working on rooting my device, and had a working root successfully with Magisk. But then I wanted to remove it and relock my bootloader, that's when the trouble started.
I am able to boot the phone and it is working. I can boot to recovery (stock OEM not TWRP), can boot to bootloader, and can boot and use the Oxygen OS. But I cannot get fastboot to run to lock the bootloader. ADB devices comes up empty. These are the steps that I've tried:
-using it on my chromebook that was working with ADB before the unrooting mess
-installed fastboot and adb along with Oneplus USB drivers on a fresh Windows 8 copy
-2 different red OEM oneplus cables
My goal is to return completely to stock and a locked bootloader. Any help would be appreciated, it really seems to be a phone issue and not a driver issue. Thanks everyone!
Use the unbrick tool. That autolocks bootloader when it flashes stock.
NateDev said:
Use the unbrick tool. That autolocks bootloader when it flashes stock.
Click to expand...
Click to collapse
I looked into the tool, but I thought from what I read I had to be in fastboot mode to start. I can't get fastboot or adb to connect. Do you know if it will work without fastboot?
bam099 said:
I looked into the tool, but I thought from what I read I had to be in fastboot mode to start. I can't get fastboot or adb to connect. Do you know if it will work without fastboot?
Click to expand...
Click to collapse
Are you sure you have USB debugging checked in developer options?
Absolutely. Just checked again. I would normally say it was a driver issue, but it was working fine until I flashed a boot.img and also I used a windows pc and a Chromebook and chrome os pretty much comes ready to talk to android phones or of the box. I was wondering if adb could have been messed up during the flashing of boot images.
bam099 said:
I looked into the tool, but I thought from what I read I had to be in fastboot mode to start. I can't get fastboot or adb to connect. Do you know if it will work without fastboot?
Click to expand...
Click to collapse
No fastboot needed, it's done with the phone off.
NateDev said:
No fastboot needed, it's done with the phone off.
Click to expand...
Click to collapse
Even better! I will definitely try the tool and report back.
NateDev said:
No fastboot needed, it's done with the phone off.
Click to expand...
Click to collapse
This was correct and it worked. Phone is restored back to stock with a locked bootloader and everything is working as it should.
So I'm trying to re-lock my bootloader,
I already looked up how to lock the bootloader and you can do that by booting in to fastboot and locking the bootloader from there. My OP6 was rooted but I removed all root related applications, I even reinstalled android.
I tought it would be as simple as unlocking the bootloader, but whatever I try I can't get my device to show up in the command promt when using the "adb devices" command while in fastboot. I tried reinstalling the ADB, fastboot and OP drivers a couple times but it doesn't help. I tried everything possible but I can't lock the bootloader.
Could somebody please help me with this?
ian_99 said:
So I'm trying to re-lock my bootloader,
I already looked up how to lock the bootloader and you can do that by booting in to bootloader and locking the bootloader from there. My OP6 was rooted but I removed all root related applications, I even wiped android.
I tought it would be as simple as unlocking the bootloader, but whatever I try I can't get my device to show up in the command promt when using the "adb devices" command. I tried reinstalling the ADB, fastboot and OP drivers a couple times but it doesn't help. I tried everything possible but I can't lock the bootloader.
Could somebody please help me with this?
Click to expand...
Click to collapse
You have to be in fastboot mode ( power off phone, hold power and volume up til you see fastboot on screen) on your phone to do want to want, if you cant do it that way,you can try this tool, https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892 , it will return your phone to stock factory fresh. It will be back on 5.1.5 software. Good luck
in fastboot mode just type without quote"fastboot oem lock"
MrSteelX said:
in fastboot mode just type without quote"fastboot oem lock"
Click to expand...
Click to collapse
I can boot into fastboot mode (I said bootloader instead of fastboot, my bad), but the command promt does NOT show any devices, so I can't use this command. All drivers are correctly installed.
Did you enable USB debug?
whizeguy said:
Did you enable USB debug?
Click to expand...
Click to collapse
Yes I did
And I tried updating to android P but now I can't even access fastboot!
[UPDATE:]
I can finally boot into fastboot again, the only way to do this was to first boot into recovery and restart to fastboot from there.
And my device is still not detected by adb in fastboot
u do fastboot devices not adb devices
I just tried doing this in a Windows 7 virtual machine, but it gives the exact same results, I really don't know what is cousing this
Then take tool all in one
Well.... Use msm download tool then.. Since you can go to fastboot, it will reset everything and lock the BL.
whizeguy said:
Well.... Use msm download tool then.. Since you can go to fastboot, it will reset everything and lock the BL.
Click to expand...
Click to collapse
What a coincidence, I am watching a video on how you can fix a bricked OP6, wich does exaclty what you said.
Thanks!
ian_99 said:
I tought it would be as simple as unlocking the bootloader, but whatever I try I can't get my device to show up in the command promt when using the "adb devices" command while in fastboot.
Click to expand...
Click to collapse
You should do "fastboot devices" in fastboot mode!
I see thay you're doing "adb devices" instead which is wrong.
rhai said:
You should do "fastboot devices" in fastboot mode!
I see thay you're doing "adb devices" instead which is wrong.
Click to expand...
Click to collapse
Oh god that actually worked, how could I have forgotten I had to use the "fastboot" command.
I can't thank you enough :victory:
ian_99 said:
Oh god that actually worked, how could I have forgotten I had to use the "fastboot" command.
I can't thank you enough :victory:
Click to expand...
Click to collapse
No worries. Cheers!