hi guys. i was unlocking the bootloader of moto x style (Dual sim) XT-1572 model. i done everything properly until i got the below error
(Bootloader) fastboot oem unlock currently disabled !
Failed
Finished
(image attached). what i did wrong ????? need help....
predator83 said:
hi guys. i was unlocking the bootloader of moto x style (Dual sim) XT-1572 model. i done everything properly until i got the below error
(Bootloader) fastboot oem unlock currently disabled !
Failed
Finished
(image attached). what i did wrong ????? need help....
Click to expand...
Click to collapse
Go to settings
Developers option (if u dont find it go to about phone and tap 5-6 times on build no )
Then u will see the developers option in the settings
Enable oem unlocking and also enable android debugging
This is the main reason behind it oem unlocking is disabled
Sagar_1401 said:
Go to settings
Developers option (if u dont find it go to about phone and tap 5-6 times on build no )
Then u will see the developers option in the settings
Enable oem unlocking and also enable android debugging
This is the main reason behind it oem unlocking is disabled
Click to expand...
Click to collapse
done it before booting to fastboot mode.
predator83 said:
done it before booting to fastboot mode.
Click to expand...
Click to collapse
Did u activate oem unlocking also??
In the bootloader, what are the two lines under the green "Battery OK" line? Should be something like...
Device is LOCKED. Status Code: 0
Software status: Official
Also please attach output of 'fastboot getvar all'
its mentioned under battery ok line.
Device is Engineering
Software Status: Official
predator83 said:
its mentioned under battery ok line.
Device is Engineering
Software Status: Official
Click to expand...
Click to collapse
You can't unlock an Engineering status bootloader. Your device was repaired and shipped out incomplete, not the first one we have seen... You need to contact Moto support, there is a thread in the official forums about this bootloader state, it's kind of a partial unlock but it's uses for factory flashing in a different way than we do it.
I was searching for a method to unlock the bootloader after updating to nougat but i couldn't find any.
Any android version the bootloader unlock method is same. check the forum for newbie thread to unlock your bootloader.
Ramith96 said:
I was searching for a method to unlock the bootloader after updating to nougat but i couldn't find any.
Click to expand...
Click to collapse
You can get your unlock code from the Motorola website: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
As the website mentions, this will void the rest of your warranty once your device is unlocked, though there are reports on XDA of people getting their devices serviced even after a bootloader unlock. Your experience may vary.
Also, I'd recommend toggling OEM unlock on - you can get to this by going into Settings > About Phone, and tapping 7 times on the build number section. Go back to the main Settings menu and you should see Developer Options has appeared. Go into the Developer Options and scroll to OEM unlocking, and toggle it on before you boot to unlock your bootloader.
So the method would be:
1 - Toggle OEM unlock in the Developers Options
2 - Follow the Motorola website instructions to unlock your bootloader
3 - Wait whilst it wipes your data
4 - Boot and enjoy your unlocked phone
Good luck!
Waiting for device
In command window it shows as 'waiting for device'. Could you help me?
mansoor643 said:
In command window it shows as 'waiting for device'. Could you help me?
Click to expand...
Click to collapse
You need to check your driver to recognize the device. With the command "fastboot devices" there you should see your devices serial number. If not = driver, cable, firewall problem or your device is not in fastboot mode
Hello! i updated my nokia 5 from oreo to 9 pie and oem unlocking setting greyed out now.There is any experied time or something or its ll stuck now?
darklord1988 said:
Hello! i updated my nokia 5 from oreo to 9 pie and oem unlocking setting greyed out now.There is any experied time or something or its ll stuck now?
Click to expand...
Click to collapse
Turn developer options ON and OF couple of times and OEM unlocking will be available again
lakija said:
Turn developer options ON and OF couple of times and OEM unlocking will be available again
Click to expand...
Click to collapse
Oem unlock is on as i see but its still going grey and cant be change
Downgraded to nougat there was oem unlock enabled but when i tried adb unlock command in adb that said oem unlock isnt allowed....
Need Help my oneplus 6t stuck at fastboot loop . I tried flashing it . But it the end It leads me to unable to complete unit is in boot loader lock state. I tried unlocking the boot loader by doing the commands . but it say
FAILED (remote: Flashing Unlock is not allowed
finished. total time: 0.004s
Also I cant flash any OTA Roms. It will say unable to complete device is in lock state. My concern is . Is there a way to unlock the bootloader at this state of my phone or its completely garbage now. Sigh..
Did you make sure you enabled OEM unlocking under Developer options?
Is this a TMobile 6T or the international 6T?
You can always use the MSM tool to return it to stock / working form.
OhioYJ said:
Did you make sure you enabled OEM unlocking under Developer options?
Is this a TMobile 6T or the international 6T?
You can always use the MSM tool to return it to stock / working form.
Click to expand...
Click to collapse
Hello sir thanks for responding to my concern. Actually this is not mine I just borrowed it. In the middle of browsing it just suddenly happen to stuck or hang up. Then when I tried to force restart its now showing the bootloader menu. So I dont know if the oem unlock was enabled. Sorry for my bad English
Hi,
I have oneplus 6T which has suddenly started giving qualcomm crash dump error after normal reboot. I have tried msm tool to flash. Tool shows success but when it boots the mobile at end , same crash dump appears again. have also tried multiple version of msm. Also visited service center but they are suggesting motherboard replacement.
Now i want to try manual flashing. Phone is in bootlocked state. also OEM is not unblocked. Is it possible tounlock OEM when my phone is not booting. also is it possible to change boothlocked state to unlock?
I can go to fastboot by pressing vol UP + DOWN and power button but on selecting recovery option it still goes to same crash dump state.
Please suggest what options do i have?is there any way to recover?
Thanks
If your device is a global model 6t then put it in fastboot mode manually then try "fastboot oem unlock* and see what happens.. Unlocking the bootloader won't fix a hardware issue but it won't hurt anything either. ?
Have you ever unlocked your bootloader and then locked it afterwards? If so I wouldn't recommend it again. I've seen a few people screw up their devices that way on here. I've never since Nexus S days when I began modding my phone's locked a bootloader. I always unlock and leave them unlocked.
**I'd either sell it as is online or get motherboard replaced then unlock bootloader and install whatever you'd I like but don't lock the bootloader after you unlock it. That's just my opinion. I've been on XDA a long time and had many devices over the years and I remember reading about people on 5 or 6 phone's I've had in my past screwing up their phones that way..
Edit added: ?
Thanks for responding
yes device is global model of 6T.
I have not unlocked /locked bootloader in past.
"fastboot oem unlock" gives error as "FAILED (remote: Flashing unlock is not allowed)"
flash713 said:
If your device is a global model 6t then put it in fastboot mode manually then try "fastboot oem unlock* and see what happens.. Unlocking the bootloader won't fix a hardware issue but it won't hurt anything either. ?
Have you ever unlocked your bootloader and then locked it afterwards? If so I wouldn't recommend it again. I've seen a few people screw up their devices that way on here. I've never since Nexus S days when I began modding my phone's locked a bootloader. I always unlock and leave them unlocked.
**I'd either sell it as is online or get motherboard replaced then unlock bootloader and install whatever you'd I like but don't lock the bootloader after you unlock it. That's just my opinion. I've been on XDA a long time and had many devices over the years and I remember reading about people on 5 or 6 phone's I've had in my past screwing up their phones that way..
Edit added:
Click to expand...
Click to collapse
Did you tried different older versions of MSM Tool?
Dafelleant said:
Did you tried different older versions of MSM Tool?
Click to expand...
Click to collapse
Hi,
yes tried couple of older versions too (listed below).
ANDROID+10+OOS+10.3.5+fajita_41_J.47_200717.zip
ANDROID+10+OOS+10.3.2+fajita_41_J.44_200222.zip
6T_MsmDownloadTool_v4.0.59_OOS_v9.0.13.rar
Every time on completion of msm flashing in all the above versions, I still get qualcomm crash dump error.
My question is: Is it necessary for bootloader to be in unlocked state for msm tool to work? if no, is there any other command to unlock the bootloader on a bricked phone as "fastboot oem unlock" and "fastboot flashing unlock" fails with the message "not allowed".
thanks again for responding to the post.
ms2020 said:
Hi,
yes tried couple of older versions too (listed below).
ANDROID+10+OOS+10.3.5+fajita_41_J.47_200717.zip
ANDROID+10+OOS+10.3.2+fajita_41_J.44_200222.zip
6T_MsmDownloadTool_v4.0.59_OOS_v9.0.13.rar
Every time on completion of msm flashing in all the above versions, I still get qualcomm crash dump error.
My question is: Is it necessary for bootloader to be in unlocked state for msm tool to work? if no, is there any other command to unlock the bootloader on a bricked phone as "fastboot oem unlock" and "fastboot flashing unlock" fails with the message "not allowed".
thanks again for responding to the post.
Click to expand...
Click to collapse
As far as I know no. Because in order to unlock your bootloader you must have access to the screen so that after you send the unlock command you can use your volume buttons to confirm and power button to select yes and then it does its thing...
flash713 said:
As far as I know no. Because in order to unlock your bootloader you must have access to the screen so that after you send the unlock command you can use your volume buttons to confirm and power button to select yes and then it does its thing...
Click to expand...
Click to collapse
Hi,
The only screen i have access to is "fastboot mode " which has options like start, power off, restart bootloader, recovery mode.
When i choose recovery it goes back to same qualcomm crashdump.
i have tried sending "fastboot oem unlock" from pc while i am in fastboot mode. but gives error as
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.005s
Thanks
Deleted.
None of what I had typed will work because your bootloader is blocked correct?
---------- Post added at 03:31 PM ---------- Previous post was at 03:13 PM ----------
ms2020 said:
Hi,
The only screen i have access to is "fastboot mode " which has options like start, power off, restart bootloader, recovery mode.
When i choose recovery it goes back to same qualcomm crashdump.
i have tried sending "fastboot oem unlock" from pc while i am in fastboot mode. but gives error as
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.005s
Thanks
Click to expand...
Click to collapse
I think the only thing that may work would be a programmer box (ex: Octopus, Mudusa..) and I'm not even sure if it would or not. I was just about to buy two before this stupid Corona bs hit and made me broker than broke. If you had one of these programmer boxes I'm talking about you may be able to fix it but I'm not 100% sure of it and they cost anywhere from $75-300 depending on which one you're looking at. They make many different programmer boxes and they all are compatible with and do slightly different things.. Sorry I couldn't be of any real help man. I hope you can get this fixed.
I'm quite sure the reason you're being denied when trying to send the bootloader unlock command is because your switch in developer options on your device isn't switched to enable bootloader unlock.
yes you are right ... got same error
fastboot boot twrp-3.4.0-2-fajita.img
downloading 'boot.img'...
OKAY [ 0.678s]
booting...
FAILED (remote: boot is not allowed in Lock State)
finished. total time: 0.697s
thanks for your reverts .
flash713 said:
Deleted.
None of what I had typed will work because your bootloader is blocked correct?
---------- Post added at 03:31 PM ---------- Previous post was at 03:13 PM ----------
I think the only thing that may work would be a programmer box (ex: Octopus, Mudusa..) and I'm not even sure if it would or not. I was just about to buy two before this stupid Corona bs hit and made me broker than broke. If you had one of these programmer boxes I'm talking about you may be able to fix it but I'm not 100% sure of it and they cost anywhere from $75-300 depending on which one you're looking at. They make many different programmer boxes and they all are compatible with and do slightly different things.. Sorry I couldn't be of any real help man. I hope you can get this fixed.
I'm quite sure the reason you're being denied when trying to send the bootloader unlock command is because your switch in developer options on your device isn't switched to enable bootloader unlock.
Click to expand...
Click to collapse
ms2020 said:
yes you are right ... got same error
fastboot boot twrp-3.4.0-2-fajita.img
downloading 'boot.img'...
OKAY [ 0.678s]
booting...
FAILED (remote: boot is not allowed in Lock State)
finished. total time: 0.697s
thanks for your reverts .
Click to expand...
Click to collapse
Have you tried formatting data and then reboot system? I know that sounds kinda dumb but if I were you I would definitely try that. It might boot up to system. To do this you can plug up to your computer and open command window and manually set phone in fastboot mode where you see the "START" screen. Then from PC terminal do: sudo fastboot -w (hit enter) and then once it wipes , push power button on your device which should still be at the screen that reads START. Your device should then reboot. I'd give that a try for sure if I were in same situation.
What did the service center quote you price wise on motherboard replacement?
The process looks doable I think..
https://www.ifixit.com/Guide/OnePlus+6T+Motherboard+Replacement/129570
I'm assuming motherboard is the mainboard. If so OnePlus has the 6t main board costing more than I paid for my mint 8gb 128gb OnePlus 6t.
https://www.oneplus.com/support/repair-pricing/details?code=9
If you end up trying everything and just can't get it fixed ...
If the cost to repair is two hundred plus dollars I would sell it online as is and add some money to it when you can and grab another used device from swappa.com . I paid $200 for my 6t near mint condition on swappa about 5-6 months ago.
Hmm, unlocking the BL is a mute point if you didn't open the developer options and check usb debugging and oem unlocking... So as the phone is borked at moment, I like the idea of reformatting but I wouldn't reboot after the format.. but have MSM ready to go and use the edl tab in twrp to start the msm...flash away..
tried the format with -w,
erase-successful-but-not-automatically-formatting-cant-determine-partition-type........
looks like locked bootloader will not let me do anything
flash713 said:
Have you tried formatting data and then reboot system? I know that sounds kinda dumb but if I were you I would definitely try that. It might boot up to system. To do this you can plug up to your computer and open command window and manually set phone in fastboot mode where you see the "START" screen. Then from PC terminal do: sudo fastboot -w (hit enter) and then once it wipes , push power button on your device which should still be at the screen that reads START. Your device should then reboot. I'd give that a try for sure if I were in same situation.
What did the service center quote you price wise on motherboard replacement?
The process looks doable I think..
https://www.ifixit.com/Guide/OnePlus+6T+Motherboard+Replacement/129570
I'm assuming motherboard is the mainboard. If so OnePlus has the 6t main board costing more than I paid for my mint 8gb 128gb OnePlus 6t.
https://www.oneplus.com/support/repair-pricing/details?code=9
If you end up trying everything and just can't get it fixed ...
If the cost to repair is two hundred plus dollars I would sell it online as is and add some money to it when you can and grab another used device from swappa.com . I paid $200 for my 6t near mint condition on swappa about 5-6 months ago.
Click to expand...
Click to collapse
hi,
even though format didnt work tried with msm too after the command to format but same result.
formating throws error as
erase-successful-but-not-automatically-formatting-cant-determine-partition-type........
looks like locked bootloader will not let me do anything
lilbrat said:
Hmm, unlocking the BL is a mute point if you didn't open the developer options and check usb debugging and oem unlocking... So as the phone is borked at moment, I like the idea of reformatting but I wouldn't reboot after the format.. but have MSM ready to go and use the edl tab in twrp to start the msm...flash away..
Click to expand...
Click to collapse
ms2020 said:
hi,
even though format didnt work tried with msm too after the command to format but same result.
formating throws error as
erase-successful-but-not-automatically-formatting-cant-determine-partition-type........
looks like locked bootloader will not let me do anything
Click to expand...
Click to collapse
Well that's not good.. as flashing with msm wouldn't matter whether the bootloader is lock or not ... As it automatically relocks it anyways... Has me stumped..
Are you sure you didn't flash anything that wasn't specifically made for your model device? I mean after you started to fix the crashdump issue?
Want to hear something crazy.. Two days ago when we were first commenting about this crashdump deal, about an hour after we stopped chatting I took a shower, got out and went to grab my OnePlus 6t off the Dash ac charger and yep, you guessed it!!! Crashdump mode!!!! ?????
I swear man! And I wasn't messing with my device when it occurred either. I was not able to get out of it by manually holding power+ volume -&+ until I saw fastboot mode and then selecting start using power button like the three other times I've experienced this. So I went ahead and booted twrp, and did a clean install of OOS and formatted data and that worked. Is this **** contagious?! ? Tripped me out! Haha!!
I'd give the data format command: fastboot -w then run msm tool like the other user said to do. See if that works.
that sounds creepy.. you getting is 'crashdump':laugh:
i guess what is different in my case is i did not unlock oem. And so none of the commands are working. Phone was working fine and one morning fingerprint scanner did not reco. my finger so i thought of rebooting instead of other method to open and i get this error. i know there was no physical mishandling on my part so its difficult to believe that its a hardware failure and needs main board replacement as service center suggests. i have tried only msm tools (stated here in previous msgs) after service center gave a huge bill (230+)for repair.
and other commands as you stated but none of them have worked anyways so not sure if i did something wrong while self repair.
guess will do one more round format plus msm...
ms2020 said:
that sounds creepy.. you getting is 'crashdump':laugh:
i guess what is different in my case is i did not unlock oem. And so none of the commands are working. Phone was working fine and one morning fingerprint scanner did not reco. my finger so i thought of rebooting instead of other method to open and i get this error. i know there was no physical mishandling on my part so its difficult to believe that its a hardware failure and needs main board replacement as service center suggests. i have tried only msm tools (stated here in previous msgs) after service center gave a huge bill (230+)for repair.
and other commands as you stated but none of them have worked anyways so not sure if i did something wrong while self repair.
guess will do one more round format plus msm...
Click to expand...
Click to collapse
Far as I know fastboot and adb commands should still work but not commands like booting custom recovery...etc .. Also developer options and usb debugging needs to be set to "on" as well in settings. It sure seems like they would have made some alternate way to access these settings but if they did I've never heard of it. Tell you the truth I've never even used fastboot and adb on anything other than a device that is bootloader unlocked except to unlock the bootloader usually a a day or two after I get my device.. I really have no clue what works and doesn't with BL locked.
What mind boggles me is all over our OP6/6t forums you see people talking about this crashdump issue. And although I've been there 5 or 6 times on my 6t I've always been able to get out of it by holding down power + volume +&- until I see the fastboot screen then releasing. And I guess many people cannot do that. I wonder why? Maybe there are two different crashdumps...? Sure seems that way to me. I've always been able to hold my buttons down and get out of it by rebooting from fastboot mode. Many report they cannot do that. ?
(I wasn't even gonna mention crashdump. My luck my phone will go to it and I won't be able to get out of it like I've been able to before.) ?
Edit added:
sudo fastboot oem device-info
Use that command to show whether device is bootloader unlocked or not. See what it says if you type that in?
Maybe see what this shows afterwards as well:
sudo fastboot gatvar all
I believe your developer options and usb debugging was probably not flipped on as well, in settings?
bro fixed aleady? i got fix for you.
i have tried the commnads you have stated earlier.. still giving output here.
fastboot oem device-info
output below
...
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) enable_dm_verity: true
(bootloader) have_console: false
(bootloader) selinux_type: SELINUX_TYPE_INVALID
(bootloader) boot_mode: NORMAL_MODE
(bootloader) kmemleak_detect: false
(bootloader) force_training: 0
(bootloader) mount_tempfs: 0
(bootloader) op_abl_version: 0x31
(bootloader) cal_rebootcount: 0x31
OKAY [ 0.027s]
finished. total time: 0.028s
so it's locked
fastboot gatvar all gives the list of options that you can use with fastboot
most of the commands dont work and gives below error
FAILED (remote: Erase is not allowed in Lock State)
yes developer options and usb debugging was probably not flipped either
flash713 said:
Far as I know fastboot and adb commands should still work but not commands like booting custom recovery...etc .. Also developer options and usb debugging needs to be set to "on" as well in settings. It sure seems like they would have made some alternate way to access these settings but if they did I've never heard of it. Tell you the truth I've never even used fastboot and adb on anything other than a device that is bootloader unlocked except to unlock the bootloader usually a a day or two after I get my device.. I really have no clue what works and doesn't with BL locked.
What mind boggles me is all over our OP6/6t forums you see people talking about this crashdump issue. And although I've been there 5 or 6 times on my 6t I've always been able to get out of it by holding down power + volume +&- until I see the fastboot screen then releasing. And I guess many people cannot do that. I wonder why? Maybe there are two different crashdumps...? Sure seems that way to me. I've always been able to hold my buttons down and get out of it by rebooting from fastboot mode. Many report they cannot do that. ?
(I wasn't even gonna mention crashdump. My luck my phone will go to it and I won't be able to get out of it like I've been able to before.)
Edit added:
sudo fastboot oem device-info
Use that command to show whether device is bootloader unlocked or not. See what it says if you type that in?
Maybe see what this shows afterwards as well:
sudo fastboot gatvar all
I believe your developer options and usb debugging was probably not flipped on as well, in settings?
Click to expand...
Click to collapse
not yet..
gazitonmoy said:
bro fixed aleady? i got fix for you.
Click to expand...
Click to collapse