Database Info

[Q] Nexus S cannot unlock bootloader or flash with Odin

I've got a Nexus S that got screwed up from the 2.3.6 OTA. It can go into fastboot mode and recovery mode but it will not boot into Android. When you try to unlock the bootloader you get the unlock screen, can select yes but when you press power the device just hangs. If you go into download mode you get a screen about unlocking the bootloader. Odin detects the device, retrieves the pit, sends the image you want to flash to the phone and the phone says image verified. Then it just does nothing. Odin just sits there and there is no other feedback on the device. It looks like if the bootloader is locked you cannot flash with Odin either. Or at least if the device goes into the strange unlock bootloader screen instead of the true download mode screen Odin flashes fail. I have searched and searched and cannot find a resolution to this problem. Has anyone figured out why some devices hang when you try to unlock the bootloader and has anyone found a way to work around this problem. I am trying to help a guy out and don't want to give him back his phone telling him there is simply nothing I can do for him. He has a TMO device in Thailand. Samsung service here will only service phones sold in Thailand through authorized channels. Since it has a TMO model number they won't touch it.

push clockwork with fastboot

tylerwatt12 said:
push clockwork with fastboot
Click to expand...
Click to collapse
Can't. Clockwork recovery image is sent to the phone. Then it says failed because bootloader lockaed, use "fastboot oem unlock" to unlock the bootloader. And on the phone it says something like Flash FailedState LOCKEDbootloader.
Without being to unlock the bootloader no image can be flashed. I even tried a stock boot image just for a test and it was rejected in the same manner. With the bootloader being locked down it won't let me flash anything. I would need a stock signed rom with android-info.txt and android-product.txt files. I have yet to find one. I think that would flash the phone.
Odin is a no go also. The images are pushed to the phone, the phone verifies the images and then doesn't flash them due to the bootloader being locked. And in download mode I don't get the shovel guy I get a screen telling me to unlock the bootloader but I am connecting in the manner that Odin can see and talk to the phone. The phone just refuses to flash the images once they are downloaded to it.

same for my nexus s,how to solve it?thx

I'm also having the problems here.
However, I simply cant get fastboot to work. It is continually stuck on 'waiting for device' (since the 2.3.6 OTA update).
I tried to flash an old 2.3.4 stock ROM I had on my SDcard, but recovery wont let me. ClockworkMod also cant be flashed because of the fastboot problem.
Yes, I checked that my drivers are up to date, I've tried using fastboot from both windows 7 and Ubuntu 11.04.

splinter701 said:
I'm also having the problems here.
However, I simply cant get fastboot to work. It is continually stuck on 'waiting for device' (since the 2.3.6 OTA update).
I tried to flash an old 2.3.4 stock ROM I had on my SDcard, but recovery wont let me. ClockworkMod also cant be flashed because of the fastboot problem.
Yes, I checked that my drivers are up to date, I've tried using fastboot from both windows 7 and Ubuntu 11.04.
Click to expand...
Click to collapse
Do you mean getting stuck when you try to unlock the bootloader (fastboot oem unlock) or can you not even get into the bootloader at all.

I can get into the bootloader with "adb reboot-bootloader" or just holding the power and volumeup keys on. However, no fastboot commands work at all. My lock state = unlocked, but even though I have the superuser app installed, I dont have root access.
All the problems started when I foolishly applied the OTA update from 2.3.4 to 2.3.6.

maybe try on another pc?

splinter701 said:
I can get into the bootloader with "adb reboot-bootloader" or just holding the power and volumeup keys on. However, no fastboot commands work at all. My lock state = unlocked, but even though I have the superuser app installed, I dont have root access.
All the problems started when I foolishly applied the OTA update from 2.3.4 to 2.3.6.
Click to expand...
Click to collapse
Reinstall drivers?
Sent from my Nexus S 4G using xda premium

Had the same problem ... but there's a YouTube video where the guy shows how to root any nexus device... here's the link but view from the PC because within the video there's a link saying that this video is old and to click the box within the video screen
Also there should be a link that says Nexussrootnew ... click on it to download and extract it and move it to C drive... within the file Ull have the USB drivers superuser ... recovery. Once moved into C drive open Command Prompt and type:
>cd c:\Nexussrootnew "enter"
>Fastboot Device"s" < Forgot lol
>FastBoot OEM Unlock
Just Follow the step in the video and Ull be fine
"REMEMBER Watch Video Via PC"
http://m.youtube.com/#/watch?deskto...e.com/watch?v=xwe4sWH67dk&v=xwe4sWH67dk&gl=US
Sent from my Nexus S using xda premium

Thanks so much YourMainDude! I usually avoid videos for instructions on this kind of thing, but this one was actually good.
For anyone who comes across this thread again, the tools you need seem to be in the SDK but do not work. The tools that work are at the website of the above video-maker (I cant post links yet, but if you search google for 'nexussrootnew.zip' the first hit should be the website nexusshacks.com)
I'll be installing cyanogenmod I think, since I'd rather that I never again have an OTA update from google.

splinter701 said:
Thanks so much YourMainDude! I usually avoid videos for instructions on this kind of thing, but this one was actually good.
For anyone who comes across this thread again, the tools you need seem to be in the SDK but do not work. The tools that work are at the website of the above video-maker (I cant post links yet, but if you search google for 'nexussrootnew.zip' the first hit should be the website nexusshacks.com)
I'll be installing cyanogenmod I think, since I'd rather that I never again have an OTA update from google.
Click to expand...
Click to collapse
=] your most welcome sir
Sent from my Nexus S using xda premium

YourMainDude said:
Had the same problem ... but there's a YouTube video where the guy shows how to root any nexus device... here's the link but view from the PC because within the video there's a link saying that this video is old and to click the box within the video screen
Also there should be a link that says Nexussrootnew ... click on it to download and extract it and move it to C drive... within the file Ull have the USB drivers superuser ... recovery. Once moved into C drive open Command Prompt and type:
>cd c:\Nexussrootnew "enter"
>Fastboot Device"s" < Forgot lol
>FastBoot OEM Unlock
Just Follow the step in the video and Ull be fine
"REMEMBER Watch Video Via PC"
link
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
I tried this but it still requires bootloader to be unlocked so it didn't work. My problem is similar to OP's. My phone appears to offer the bootloader unlock option, but selecting 'yes' to unlock fails to actually unlock. So nothing else works to restore the ROM. Though the phone does accept commands from adb just fine.
Anyway, I'm just posting this in case anyone else has the the same issue w/ bootloader not unlocking.

[Q] ***HELP*** Bricked..Stuck in Boot Loop**

So here is what I did... Last night i successfully unlocked my bootloader on my AT&T HTC Onc X and established root. I was running the AT&T RUU_Evita_UL_Cingular_US-1.82.502. I then tried to update this morning to AT&T RUU_Evita_UL_Cingular_US-1.85.502(desktop installer type) it kept giving me errors and would not complete. Like an idiot i tried to flash CleanROM 2.0 -★| 1.85.502.3 | Tweaked! | Stable! | CWM Install! through CWM and it installed successfully but my WIFI would not work at all. So i decided to reload CleanROM DE 1.0 -★| which had worked fin in the past. At the end of the installer it said to do a factory reset and I did. After the reboot is where i noticed my problem. I am stuck on the boot animation screen. Not able to get into the phone at all now. I am able to get back to the bootloader menu.. boot into CWM but unable to reflash the room on the sdcard. It will not mount USB storage. None of the stock desktop installer will recognize my device is plugged in....... ANY SUGGETIONS...or am I screwed....

Is it in a boot loop or is it frozen on the HTC One screen? That happened to me last night but I was able to run the RUU installer. Did you make sure HTC Sync wasn't running, and that you killed adb by using adb kill-server before trying the RUU installer?
Apologies if you've done these things already, I'm just grasping at straws here.
If you can do adb reboot bootloader, you should be able to run the RUU installer from there, no?

it does not show the ONE X boot screen. Its shows i guess what is known as the Galaxy Nexus boot screen that just flashes the colorful boxes over and over the longest i let it go for was like 20 minutes. The RUU installer you talk about, is that the one that you run from ur desktop. If so how do i get it to recognize my device is even plugged in. I have tried it while it is on the boot animation screen and from the bootloader menu. At this point it just seems like I dont have a way to get my computer to detect my device is plugged in. Is there a way to do that from the Bootloader menu?

taterdog2 said:
it does not show the ONE X boot screen. Its shows i guess what is known as the Galaxy Nexus boot screen that just flashes the colorful boxes over and over the longest i let it go for was like 20 minutes. The RUU installer you talk about, is that the one that you run from ur desktop. If so how do i get it to recognize my device is even plugged in. I have tried it while it is on the boot animation screen and from the bootloader menu. At this point it just seems like I dont have a way to get my computer to detect my device is plugged in. Is there a way to do that from the Bootloader menu?
Click to expand...
Click to collapse
If you have adb on your computer (from the Android SDK) and the drivers installed, you should be able to access the device from fastboot (bootloader). RUU will work if you can get your device into fastboot. I'm doing it right now (I wanted to try it before telling you).
Just remember, if you were on an unlocked 1.82 when you borked it, you need to be locked again before you can use RUU. Just use fastboot oem lock from the command prompt.

If you can get to the bootloader screen you are not bricked. Why can't you run the RUU like normal from there? Just re-lock your bootloader first.
Poster above beat me to it while I was taking forever to post.

1. Hold down your Volume Down Button and your power button
2. Wait for the device to turn off and keep holding the combination until you boot into the bootloader (It might take a couple tries, don't give up)
3. Plug your device into your computer via the OEM USB Cable
4. Use the Volume Up/Down keys and the Power button to select the Fastboot Option
5. Wait till the device is recognized (The text on screen where it said Fastboot should become Fastboot USB)
6. Go to the folder where you have fastboot installed and type:
fastboot oem lock
7. Go back to the bootloader and into fastboot when its done with relocking. Make sure the text on the top of the screen says "Relocked" or "Locked" (under the Tampered flag)
8. Run the RUU while in fastboot mode. Use version 1.85.

I sorry for being a NOOB... step 6. Go to the folder where you have fastboot installed and type:
fastboot oem lock...
when you refer to "having fastboot installed" I am taking it that you are not refering to the RUU installer... where do I get this FASTBOOT file from to install?

I think I figured it out... will let yall know in a few minutes

I looks to be that the 1.85 RUU is flashing properly... do I use the same method that I originally used to unlock the bootloader again?

taterdog2 said:
I looks to be that the 1.85 RUU is flashing properly... do I use the same method that I originally used to unlock the bootloader again?
Click to expand...
Click to collapse
Yes. You may need another unlock code. I did, but other people didn't. They just tried several times until it worked.

jmattp said:
Yes. You may need another unlock code. I did, but other people didn't. They just tried several times until it worked.
Click to expand...
Click to collapse
how u get unlock code again....i believe htcdev asking token right...? how do i get token back...? last time i try before one click came up device not found....kinda mess up my adb...? any link to re DL adb or android sdk platform tool again...thanks in ADV

ted77usa said:
how u get unlock code again....i believe htcdev asking token right...? how do i get token back...? last time i try before one click came up device not found....kinda mess up my adb...? any link to re DL adb or android sdk platform tool again...thanks in ADV
Click to expand...
Click to collapse
If you got device not found, you might not have USB Debugging enabled.
I don't think it's possible for something to "mess up" adb. For the Android SDK, just Google it.
When you run the one click CID tool again, just go through it all the exact way you did the first time.
I just spend about four hours on here answering questions and uploading mods. I'm going to take a shower and enjoy the rest of my Saturday. Good luck.

jmattp said:
If you got device not found, you might not have USB Debugging enabled.
I don't think it's possible for something to "mess up" adb. For the Android SDK, just Google it.
When you run the one click CID tool again, just go through it all the exact way you did the first time.
I just spend about four hours on here answering questions and uploading mods. I'm going to take a shower and enjoy the rest of my Saturday. Good luck.
Click to expand...
Click to collapse
so one click unlock bootloader tool work on 1.85 base from designgears that post by Kpenn.....? did u trying using that also...? ENJOY YOUR SAT....HAVE A NICE LONG WEEKEND....HAPPY MEMORIAL DAY...

ted77usa said:
so one click unlock bootloader tool work on 1.85 base from designgears that post by Kpenn.....? did u trying using that also...? ENJOY YOUR SAT....HAVE A NICE LONG WEEKEND....HAPPY MEMORIAL DAY...
Click to expand...
Click to collapse
I think as long as you're relocked, not factory locked (meaning, you unlocked 1.82 and then locked it again) you should be able to use the one click tool again. That's how I did it.

jmattp said:
I think as long as you're relocked, not factory locked (meaning, you unlocked 1.82 and then locked it again) you should be able to use the one click tool again. That's how I did it.
Click to expand...
Click to collapse
assuming it work how u get CWM recovery....are u using one click tool also...? and how u re-root....? are u flashing paulobrien superSU script from recovery?

ted77usa said:
assuming it work how u get CWM recovery....are u using one click tool also...? and how u re-root....? are u flashing paulobrien superSU script from recovery?
Click to expand...
Click to collapse
Once you unlock your bootloader on 1.85 you will not need root to flash CWM Recovery

[Q] Correct unroot and bootloader lock procedure?

Hi, my powerbutton on my sns got stuck in the "on" position. So i need to unroot the phone and lock the bootloader in order to send it to warranty repair. I would do it this way
1) reboot to bootloader
2) flash stock images via fastboot
3) issue fastboot oem lock command
4) done?
Im not really sure so im asking first.
Thanks

cahir_cz said:
Hi, my powerbutton on my sns got stuck in the "on" position. So i need to unroot the phone and lock the bootloader in order to send it to warranty repair. I would do it this way
1) reboot to bootloader
2) flash stock images via fastboot
3) issue fastboot oem lock command
4) done?
Im not really sure so im asking first.
Thanks
Click to expand...
Click to collapse
Seems about right

kwibis said:
Seems about right
Click to expand...
Click to collapse
Thanks for confirming. However when i reboot my phone into bootloader my computer cant detect it, thus making fastboot flashing impossible. Any idea what to do?

You need to make sure you have fastboot drivers installed on your computer. Search o the forum, loads of info, I cannot search now as I'm on the phone. Good luck :thumbup:
Sent from my Nexus S

cahir_cz said:
Thanks for confirming. However when i reboot my phone into bootloader my computer cant detect it, thus making fastboot flashing impossible. Any idea what to do?
Click to expand...
Click to collapse
some pics step by sptep to help!!!! (at the 6 step it appear "asus android device" but dont care about that, just search for the words "android devices", nexus devices are universal they work with all drivers)
download drivers (unzip first): http://www.4shared.com/rar/Udv-0weq/usb_driver.html

You're going to have a problem if the power button is not working.
Not going to be able to issue any commands if you can't move the cursor up and down with the volume keys in fastboot. Basically get where it says fastboot USB int...

Problem after unlocking bootloader - Bricked?

Hey guys, how are you?
Well, I wished to root my Moto G, so I (tryed?) to unlock the bootloader. Alright, done it, but then I ran into some trouble...
After the booting up, everything started forceclosing and since then, when I try to boot it, I get a black screen after the Motorola logo.
Now, I am really really worried about my phone. I got it a month ago. I'm so afraid I really f****d up my phone right now that my hands are shaking.
I'm new to Android, so sorry if the solution is pretty obvious. And if it's not, could explain it very carefully to me? I don't know what to do.
My best wishes to you, guys.

I'm assuming you used superboot if so that would happen.
The logo sort of blured out right just press volume down and power and it would work
Or did this happen when you were just trying to unlock bootloader?

TomGlass1 said:
I'm assuming you used superboot if so that would happen.
The logo sort of blured out right just press volume down and power and it would work
Or did this happen when you were just trying to unlock bootloader?
Click to expand...
Click to collapse
Yeah, that happenned when I was trying to unlcok bootloader.
And well, my computer now doesn't even recognizes my phone.
EDIT: It appears as "Fastboot falcon S" in the Device Manager. Tried installing some drivers I found in the Internet, but it didn't work.

Explain exactly what happened please. Was the unlock successful and did you just bootup normally after or did u do anything else in fastboot mode? Why are you trying to install fastboot drivers again, as you already wouldve had them to unlock the bootloader. Did you try installing recovery or some root img from fastboot? You said its forceclosing, but it isnt starting at all now?
Some things you can do right now (if your bootloader is unlocked) is to flash a recovery (twrp,cwm) through fastboot and if you think most system files (or settings) are beyond repair, flash your firmware version though fastboot. Will point you to the guides for them, but post more info if you want help.

hemanthmahesh said:
Explain exactly what happened please. Was the unlock successful and did you just bootup normally after or did u do anything else in fastboot mode? Why are you trying to install fastboot drivers again, as you already wouldve had them to unlock the bootloader. Did you try installing recovery or some root img from fastboot? You said its forceclosing, but it isnt starting at all now?
Some things you can do right now (if your bootloader is unlocked) is to flash a recovery (twrp,cwm) through fastboot and if you think most system files (or settings) are beyond repair, flash your firmware version though fastboot. Will point you to the guides for them, but post more info if you want help.
Click to expand...
Click to collapse
Alright, just after I unlocked, when I was booting, I got a message saying that "xxxx has stopped working/failed to initialize/something like that". And then, when I rebooted, I got the usual message of the "bootlocker has been unlocked". After that, the Motorola logo started animating, but then I just got a black screen. I can't turn it off and the battery just got depleted (I'm charging right now).
When I try to connect it in my computer, the PC recognizes it as "MTP Device" or "Fastboot falcon S" when fastbooted. I can't install any drivers and the Motorola Device Manager doesn't recognizes it either.
Well, if there is some missing information, just ask me. I tried to describe my problem the best I could. Anyway, sorry for my bad English and thanks in advance for any effort trying to discover what's wrong.

Motorola Device Manager isn't helpful in this state as it doesn't handle things in fastboot. You already have all the required drivers (fastboot falcon S is the right driver afaik, falcon being motog codename) for flashing your stock firmware.
1. First, you can try the "Factory" option in bootloader (the third one, use volume down to move selector, volume up to select), though this might not really work for major issues.
2. When in fastboot mode, use "fastboot getvar all" to get the firmware details if you already didn't know about it.
3. Otherwise if yours is a standard gsm (non dualsim/non cdma), just download Blur_Version.174.44.9.falcon_umts.Retail.en.GB (UK stock for gsm, 4.4.2)
Download the mfastboot files to use rather than fastboot for flashing. You might need to modify your commands a bit for various firmwares.
http://forum.xda-developers.com/showthread.php?p=47820707 (refer this thread for flashing your stock firmware)
All the firmwares are in either of the links below (all around 400mb):
http://sbf.droid-developers.org/phone.php?device=14
(or)
http://www.filefactory.com/folder/c6cdedc45a775d27
I still don't get why many ppl are getting these errors after unlocking, very bad unlock method of moto if so ( I didnt get any such issues though).

When I use the "fastboot getvar all" command, it says "waiting for device". The phone is already connected, but the Moto G doesn't recognizes it's connected either.
I'm getting more and more afraid I really hardbricked it.

http://www.mymotocast.com/download/MDM?platform=windows
Tried installing these drivers? Your fastboot doesn't seem to be setup properly. How did you unlock without a working fastboot driver? You are trying that command in bootloader mode right?

Already installed it from the start. The message I got is always this:
"There aren't any updates for your device at the moment
Current Version: N/A"
My fastboot: Doesn't matter the operation I do, I always get this <waiting for device> and the phone is already connected into the computer. And the phone doesn't recognizes it is connected too.
And greeeeat news: my phone now doesn't charges either. I get stuck on a screen with a battery logo and 0%, when connected to the charger. Still, I still can access the fastboot mode. Well, am I lucky or not?

I'm pretty confused with this. How exactly did you unlock without a working fastboot (no waiting for device issue)? Did you change your pc drivers after unlock or trying this from a different pc? When you say "phone doesn't recognizes it is connected" you mean it says "Connect USB data cable" below "Device is UNLOCKED"? If so, maybe try another usb port cause it should normally say "Transfer Mode: USB Connected" regardless of proper drivers.
Your phone will chrarge no matter what though, no worry about that. It needs to say "Battery OK (Charging)" when connected to PC
No, as long as you have working your device isn't technically bricked in any sense. Don't worry, get that fastboot working again and anything can be fixed.
Also you didnt say whether or not you tried that "Factory" option in bootloader!

hemanthmahesh said:
I'm pretty confused with this. How exactly did you unlock without a working fastboot (no waiting for device issue)? Did you change your pc drivers after unlock or trying this from a different pc? When you say "phone doesn't recognizes it is connected" you mean it says "Connect USB data cable" below "Device is UNLOCKED"? If so, maybe try another usb port cause it should normally say "Transfer Mode: USB Connected" regardless of proper drivers.
Your phone will chrarge no matter what though, no worry about that. It needs to say "Battery OK (Charging)" when connected to PC
No, as long as you have working your device isn't technically bricked in any sense. Don't worry, get that fastboot working again and anything can be fixed.
Also you didnt say whether or not you tried that "Factory" option in bootloader!
Click to expand...
Click to collapse
OMG. I tried that "Factory" option before but it didn't work. Now I tried a second time and it worked. Thanks a lot! Really :laugh:
Anyway, now my phone is back again and rooted. Thanks for the help, guys!

Thaiane said:
Already installed it from the start. The message I got is always this:
"There aren't any updates for your device at the moment
Current Version: N/A"
My fastboot: Doesn't matter the operation I do, I always get this <waiting for device> and the phone is already connected into the computer. And the phone doesn't recognizes it is connected too.
And greeeeat news: my phone now doesn't charges either. I get stuck on a screen with a battery logo and 0%, when connected to the charger. Still, I still can access the fastboot mode. Well, am I lucky or not?
Click to expand...
Click to collapse
Guys the problem occurs due to corruption of /data folder. Even I had the same issue.
What you can do is
1. Connect your phone to PC in fastboot mode.
2. In fastboot, enter the command "adb erase userdata" and "adb erase cache" without quotes and reboot you phone. It will work for most of the devices, if it doesn't I have some other workaround too.

help
forgotter said:
Guys the problem occurs due to corruption of /data folder. Even I had the same issue.
What you can do is
1. Connect your phone to PC in fastboot mode.
2. In fastboot, enter the command "adb erase userdata" and "adb erase cache" without quotes and reboot you phone. It will work for most of the devices, if it doesn't I have some other workaround too.
Click to expand...
Click to collapse
I have the same problem. my phone stuck in blank screen after Unlock Bootloader. and then I try to do "adb erase userdata" and "adb erase cache". but my phone has no chenge, still stuck in.
I attach log when enter command adb above.
I'm sorry before. I can't spech English well

jidurrr said:
I have the same problem. my phone stuck in blank screen after Unlock Bootloader. and then I try to do "adb erase userdata" and "adb erase cache". but my phone has no chenge, still stuck in.
I attach log when enter command adb above.
I'm sorry before. I can't spech English well
Click to expand...
Click to collapse
The log you have posted contains only the help commands of adb and not the actual commands you gave.
Give a try to factory reset from fastboot mode on your phone. And do you a custom recovery installed in your phone?

forgotter said:
The log you have posted contains only the help commands of adb and not the actual commands you gave.
Give a try to factory reset from fastboot mode on your phone. And do you a custom recovery installed in your phone?
Click to expand...
Click to collapse
I've tried factory reset for several times, but no change as well.
yes, I get a CWM in my phone. and then, what have I do?

jidurrr said:
I've tried factory reset for several times, but no change as well.
yes, I get a CWM in my phone. and then, what have I do?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2704207
Go to the above forum.
Sorry for late reply was busy with studies.

I had flash stock firmware
through PC

Question OEM Unlock greyed out and device not found in fastboot

I'm trying to unlock bootloader, but OEM Unlock option is greyed out.
Device can enter fastboot but doesn't respond to any commands. For example "fastboot devices" do nothing. Using same computer, fastboot commands work fine with another device.
Any solutions? thanks

Windoors said:
I'm trying to unlock bootloader, but OEM Unlock option is greyed out.
Device can enter fastboot but doesn't respond to any commands. For example "fastboot devices" do nothing. Using same computer, fastboot commands work fine with another device.
Any solutions? thanks
Click to expand...
Click to collapse
Try removing the sim card, or putting another carriers card in there. I seem to remember this popping up before

Beetle84 said:
Try removing the sim card, or putting another carriers card in there. I seem to remember this popping up before
Click to expand...
Click to collapse
i've tried that and factory reset too. I guess I need to wait for few days, its only been a day.
But I'm concerned about the fastboot commands. Are those also supposed to not work until "OEM unlock" isn't grey anymore? If that's the case then good, at least it will work after few days. but if it never works then maybe bootloader can never be unlocked?

Windoors said:
i've tried that and factory reset too. I guess I need to wait for few days, its only been a day.
But I'm concerned about the fastboot commands. Are those also supposed to not work until "OEM unlock" isn't grey anymore? If that's the case then good, at least it will work after few days. but if it never works then maybe bootloader can never be unlocked?
Click to expand...
Click to collapse
Help with unlock OEM no work
Is off and dont put on, say Conect to Internet or call you carrier. Any help please... thanx
forum.xda-developers.com
Have a read of this thread

Windoors said:
i've tried that and factory reset too. I guess I need to wait for few days, its only been a day.
But I'm concerned about the fastboot commands. Are those also supposed to not work until "OEM unlock" isn't grey anymore? If that's the case then good, at least it will work after few days. but if it never works then maybe bootloader can never be unlocked?
Click to expand...
Click to collapse
Also try installing tinyfastboot from the lineage or evo rom threads. Select the recommended moto drivers, fastboot should be fine afterwards.

Fastboot working after installing drivers from: https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/88481/