Hello. I received the OTA update, install it pressed and then I have not loaded tablet.
What should I do?
I Tried:
- wipe data/cache
- charge device
Unlock OEM is not allow (in setting). And I can't unlock bootloader
I dot no my friend but, ota today ? New ota ?
Or it this your first boot on new tablet?
Anyway good luck, wait for pro advice , maybe with PC/cable.
Nothing new Snegovik for your problem ?
xennos said:
Nothing new Snegovik for your problem ?
Click to expand...
Click to collapse
No, I have not solved the problem. The tablet is not loaded, and I can't flast it.
My advice: Allow OEM unlocking the bootloader in the Setting
sad...
I need to find an OTA update on flash recovery. But I can not find it ((
are you using the new unlock command.?
you may also want to update the sdk or whatever adb/fastboot package you use.
dkryder said:
are you using the new unlock command.?
you may also want to update the sdk or whatever adb/fastboot package you use.
Click to expand...
Click to collapse
What you mean?)
Who can get OTA link?
Please see:
http://www.droid-life.com/2014/06/05/download-nexus-ota-url-file/
I want a try flash a OTA from adb sideload)
SnegovikRZN said:
What you mean?)
Click to expand...
Click to collapse
you were saying that pixel c would not unlock and i was asking if you are using the new unlock command. the pixel c uses the nexus 6p unlock
command. not the old one.
it is no longer "fastboot oem unlock"
it is now for pixel c "fastboot flashing unlock"
you need to update your fastboot/adb package you use in case the one you are using does not recognize the new commands.
dkryder said:
you were saying that pixel c would not unlock and i was asking if you are using the new unlock command. the pixel c uses the nexus 6p unlock
command. not the old one.
it is no longer "fastboot oem unlock"
it is now for pixel c "fastboot flashing unlock"
you need to update your fastboot/adb package you use in case the one you are using does not recognize the new commands.
Click to expand...
Click to collapse
Unfortunately this does not work (
Maybe you need to install ADB USB driver manually.
Once fastboot is working .. fastboot flashing unlock
generally that message is shown when the allow oem unlock switch in developer options is not set on.
dkryder said:
generally that message is shown when the allow oem unlock switch in developer options is not set on.
Click to expand...
Click to collapse
yes...
but I can not set it in Setting, because my device is not bott
well, if you still have the device then one possibility is to post your issue to this group,
https://groups.google.com/a/chromium.org/forum/#!forum/chromium-os-discuss
to see if there is a flag in the vbnv that can be set with fwtool. [similar to fastboot issue] to get it to boot.
Pixel C bootloop[
SnegovikRZN said:
yes...
but I can not set it in Setting, because my device is not bott
Click to expand...
Click to collapse
Even i am facing the same problem with my Pixel C device. is there any way to unlock the boatloader ? if it is not set in Settings. or only option left is replacement from google?
vtirugudu said:
Even i am facing the same problem with my Pixel C device. is there any way to unlock the boatloader ? if it is not set in Settings. or only option left is replacement from google?
Click to expand...
Click to collapse
Yes you can unlock same as you would a Nexus device.
bill3508 said:
Yes you can unlock same as you would a Nexus device.
Click to expand...
Click to collapse
How to unlock the device?
HI there,
I get same problem, not possible to active Debug & Dev on android setting, because the tablet dosnt load to android !
I tried with Nexus Root Toolkit no success also
Related
I recently used the newfound method of unlocking the Verizon Pixel/XL 1 to unlock my Pixel XL. The issue now though is that I can't flash anything, or do anything in fastboot. Windows doesn't see my device when I use adb reboot bootloader, and the console entry on the bootloader screen says DISABLED. Google is unhelpful as I seem to be the only person here with this problem. Any ideas?
For what it's worth, I used fastboot oem unlock instead of fastboot flashing unlock.
RenaldiDroidXDA said:
I recently used the newfound method of unlocking the Verizon Pixel/XL 1 to unlock my Pixel XL. The issue now though is that I can't flash anything, or do anything in fastboot. Windows doesn't see my device when I use adb reboot bootloader, and the console entry on the bootloader screen says DISABLED. Google is unhelpful as I seem to be the only person here with this problem. Any ideas?
For what it's worth, I used fastboot oem unlock instead of fastboot flashing unlock.
Click to expand...
Click to collapse
I think your problem is you used 'fastboot oem unlock' instead of 'fastboot flashing unlock.'
Well, now I see the problem.
Now I need to know how to fix it .-.
RenaldiDroidXDA said:
Well, now I see the problem.
Now I need to know how to fix it .-.
Click to expand...
Click to collapse
did you enable usb debugging in developer options?
lucky_strike33 said:
did you enable usb debugging in developer options?
Click to expand...
Click to collapse
Yes, I did. adb works quite well enough, but fastboot detects nothing.
The title pretty much describe the whole issue: I get a persistent notification that there's an OTA update to install, but touching the notification does nothing.
There seem to be no way of manually installing it either, because there is no update option listed in the configuration.
Can't unlock the bootloader either, because there is no OEM unlock listed in the dev tools.
I've never seen anything like this. Spent days researching, but found nothing. So here I'm hoping someone might have a clue about how to enable updates and OEM unlock in a situation like this.
Any help is appreciated.
This phone is a Xiaomi Mi A2 Lite model M1805D1SG, running Android 8.1 (OPM 1.171019.019.V9.6.6.0ODLMIFF)
you system is clean or modified (magisk etc)?
eremitein said:
you system is clean or modified (magisk etc)?
Click to expand...
Click to collapse
How should he modify or root it with a locked bootloader?
nquil said:
Can't unlock the bootloader either, because there is no OEM unlock listed in the dev tools.
Click to expand...
Click to collapse
for unlocking the bootloader you have to use ADB tools. you can't just unlock it in developer setting.
for your problem i would recommend you too check the forums on how to unlock the bootloader with adb and then grab the latest official A2 lite rom (10.0.40. or something i guess) and flash it with the MiFlashTool.
this procedure will upgrade your device without any loss of data.
I'm telling you this because that's how i update my device (which is rooted and kernel modified) with no problems.
thorin0815 said:
How should he modify or root it with a locked bootloader?
Click to expand...
Click to collapse
maybe early somebody did this with his phone:laugh:
so need to more checking
eremitein said:
you system is clean or modified (magisk etc)?
Click to expand...
Click to collapse
It is clean.Brand new device, unable to do anything, as it is OEM locked.
merlin.berlin said:
for unlocking the bootloader you have to use ADB tools. you can't just unlock it in developer setting.
for your problem i would recommend you too check the forums on how to unlock the bootloader with adb and then grab the latest official A2 lite rom (10.0.40. or something i guess) and flash it with the MiFlashTool.
this procedure will upgrade your device without any loss of data.
I'm telling you this because that's how i update my device (which is rooted and kernel modified) with no problems.
Click to expand...
Click to collapse
True. We usually need to run 'fastboot oem unlock' to actually unlock the bootloader. Problem is, the command needs one to enable OEM unlocking in the developer options beforehand, otherwise it fails. And I dont have any means to enable OEM unlocking in the dev options, because it is not listed at all!
And without that I'm unable of doing any flashing.
The only report I found regarding a missing an OEM unlock option in the dev tools concern Samsung S9. Apparently one needs to wait 7 days for it to appear. But such a thing is unheard of concerning a Xiaomi phone.
eremitein said:
maybe early somebody did this with his phone:laugh:
so need to more checking
Click to expand...
Click to collapse
I have been researching this for days, couldn't find anything... Didn't find a single report about OEM unlock not showing up in Developer options for Xiaomi Mi A2 Lite, at all.
nquil said:
True. We usually need to run 'fastboot oem unlock' to actually unlock the bootloader. Problem is, the command needs one to enable OEM unlocking in the developer options beforehand, otherwise it fails. And I dont have any means to enable OEM unlocking in the dev options, because it is not listed at all!
And without that I'm unable of doing any flashing.
The only report I found regarding a missing an OEM unlock option in the dev tools concern Samsung S9. Apparently one needs to wait 7 days for it to appear. But such a thing is unheard of concerning a Xiaomi phone.
Click to expand...
Click to collapse
Could you post a screenshot of your System menu under settings?
nquil said:
I have been researching this for days, couldn't find anything... Didn't find a single report about OEM unlock not showing up in Developer options for Xiaomi Mi A2 Lite, at all.
Click to expand...
Click to collapse
show screenshots from dev settings with blanked OEM unlock and from about phone information (build, kernel etc)
capajga said:
Could you post a screenshot of your System menu under settings?
Click to expand...
Click to collapse
Sure. Let's see if it works this time around
Here are the screenshots. (Attached)
nquil said:
Here are the screenshots. (Attached)
Click to expand...
Click to collapse
Could it be that the OEM unlock option is under Development tools?
capajga said:
Could you post a screenshot of your System menu under settings?
Click to expand...
Click to collapse
Sure, here goes (i hope!) --> https://imgur.com/gallery/c77LPsS
capajga said:
Could it be that the OEM unlock option is under Development tools?
Click to expand...
Click to collapse
Nope. See screenshots.---> https://imgur.com/a/b0SXeV0
I wonder if there's a way to enable it through command line, in a local shell (inside android)
nquil said:
Nope. See screenshots.---> https://imgur.com/a/b0SXeV0
Click to expand...
Click to collapse
Strange
I'm on 9.6.11.0 version and it's there. You're on 9.6.6.0 version. Maybe there's someone who had experience with 9.6.6.0 and OEM unlocking but if not there's always the option to do an OTA update to a newer firmware version.
Just don't update to a 10.x.x.x version (Pie) if you want to keep Oreo
capajga said:
Strange
I'm on 9.6.11.0 version and it's there. You're on 9.6.6.0 version. Maybe there's someone who had experience with 9.6.6.0 and OEM unlocking but if not there's always the option to do an OTA update to a newer firmware version.
Just don't update to a 10.x.x.x version (Pie) if you want to keep Oreo
Click to expand...
Click to collapse
Can't do an OTA update either. Check closely: along with OEM unlock, there is no system update option.
eremitein said:
show screenshots from dev settings with blanked OEM unlock and from about phone information (build, kernel etc)
Click to expand...
Click to collapse
I have posted them in posts previous to this one. Please take a look.
nquil said:
Can't do an OTA update either. Check closely: along with OEM unlock, there is no system update option.
Click to expand...
Click to collapse
Yeah, saw it the second time i looked
It sais security update from December 2018 but the build is 9.6.6.0
My screenshots:
I got replacement pixel 2 xl on android 10 security patch October 6/2019 I tried everything from fastboot I get error saying locked I don't know what carrier I checked imei and meid all good its networked unlocked I even went into safe mode and removed guest rebooted nothing …...I hate android 10 my signal sucks compared to android 9
oem unlock bootloader is grayed out
fryedmonk911 said:
I got replacement pixel 2 xl on android 10 security patch October 6/2019 I tried everything from fastboot I get error saying locked I don't know what carrier I checked imei and meid all good its networked unlocked I even went into safe mode and removed guest rebooted nothing …...I hate android 10 my signal sucks compared to android 9
oem unlock bootloader is grayed out
Click to expand...
Click to collapse
Sounds like you got a Verizon variant device instead of a google one. If you can't toggle OEM unlocking from the get go, you really can't unlock the bootloader. Sorry man
Badger50 said:
Sounds like you got a Verizon variant device instead of a google one. If you can't toggle OEM unlocking from the get go, you really can't unlock the bootloader. Sorry man
Click to expand...
Click to collapse
I'm Canadian and I got three pixel 2 refurbs before giving up. There's a huge support thread about how all refurb bootloaders cannot be unlocked. Not sure why. I had a slot unbootable error, this was on my non xl variant.
crixley said:
I'm Canadian and I got three pixel 2 refurbs before giving up. There's a huge support thread about how all refurb bootloaders cannot be unlocked. Not sure why. I had a slot unbootable error, this was on my non xl variant.
Click to expand...
Click to collapse
thank you all for responding , I did contact google yesterday and was told all pixel devices that come from google are fully unlock they told me to call Verizon up I did last night and it is one of there phones I am sending it back to the seller and explaining to him what I want .were I live we have a hybrid tower and for some reason android 10 sucks compard to 9
Mine have oem unlock option but can't unlock the bootloader. tried all the commands but won't let me unlock the bootloader. any help will be greatly appreciated. running android 10
sinkoo1979 said:
Mine have oem unlock option but can't unlock the bootloader. tried all the commands but won't let me unlock the bootloader. any help will be greatly appreciated. running android 10
Click to expand...
Click to collapse
Are platform-tools up to date?
Are you using a USB a to USB C cable?
Does your phone get recognized when you type in fastboot devices?
Are you using power shell?
Is USB debugging turned on?
Badger50 said:
Are platform-tools up to date?
Are you using a USB a to USB C cable?
Does your phone get recognized when you type in fastboot devices?
Are you using power shell?
Is USB debugging turned on?
Click to expand...
Click to collapse
didn't check
yes
yes
yes
yes
sinkoo1979 said:
didn't check
yes
yes
yes
yes
Click to expand...
Click to collapse
Check your platform-tools, and don't use power shell commands. Open your command prompt directly on your platform-tools folder.
Badger50 said:
Check your platform-tools, and don't use power shell commands. Open your command prompt directly on your platform-tools folder.
Click to expand...
Click to collapse
will try. Thank you
Update: unlocked bootloader with minimal adb and fastboot.
sinkoo1979 said:
will try. Thank you
Update: unlocked bootloader with minimal adb and fastboot.
Click to expand...
Click to collapse
Congrats :good: However, I would recommend getting rid of minimal adb and just use platform-tools going forward. Minimal adb can cause problems when it comes to fastbooting factory images :good:
fryedmonk911 said:
thank you all for responding , I did contact google yesterday and was told all pixel devices that come from google are fully unlock they told me to call Verizon up I did last night and it is one of there phones I am sending it back to the seller and explaining to him what I want .were I live we have a hybrid tower and for some reason android 10 sucks compard to 9
Click to expand...
Click to collapse
I'm guessing when Google told you that all phones coming from Google were fully unlocked they were talking about being carrier unlocked instead of having the capability of unlocking the bootloader.
When buying a LG phone (e.g. Pixel 2 XL) it's good to have the seller run an IMEI check and post the screenshot for you from this site... https://www.imeipro.info/check_lg.html
Under they buyer name you can tell if you are getting a Google or Verizon variant.
Badger50 said:
Congrats :good: However, I would recommend getting rid of minimal adb and just use platform-tools going forward. Minimal adb can cause problems when it comes to fastbooting factory images :good:
Click to expand...
Click to collapse
Since all Minimal ADB and Fastboot does is bundle up the platform tools and add a Windows executable stub to them, removing it isn't a bad idea. An alternative - that I took - would be to update the platform tools in the Minimal ADB folder with the latest from Google.
Hello guys,
As always, I am here with a new share. I am sharing with you the deep testing app for Android 10 RM5 pro. I got to fastboot with this app. Next to unlock....[Update: UNLOCKED & Rooted]
Go on try it out.
The sweet guy who shared this video and app.
https://www.youtube.com/watch?v=LFuuZSh6C-I
The apk link here:
https://www.youtube.com/redirect?re...vPDNolgt_uV4AaABAg&q=http://shorturl.at/acuT5
Note: I had already selected OEM unlock in my RM5P since long, so I just installed this apk and opened and selected
QUERY VERIFICATION STATUS (right top corner). It showed Review Successful. Select START IN-DEPTH TEST.
You go straight to fastboot..
Enjoy LOCKDOWN safe in your home.
Thank you for reading.
Do you know if work for european devices?
loqi said:
Do you know if work for european devices?
Click to expand...
Click to collapse
Officially no, but for me and several others it still worked, even with an EU phone.
I had to upgrade to Android 10 and then follow the steps described here:
https://c.realme.com/in/post-details/1244566811094024192?language=en-US
Btw., it's better to stick to the official post from realme I linked above, apps and links on youtube could be malicious.
I am using RM5P Indian version. The youtube link is safe. I didn't find any issues.
More than that, this apk was already listed in xda by faisalxp. I realized that late.
https://forum.xda-developers.com/realme-5-pro/how-to/stock-firmware-boot-recovery-vbmeta-t4006615.
Go to this link to download safely.
loqi said:
Do you know if work for european devices?
Click to expand...
Click to collapse
AFAIK, installing this apk and getting into fastboot wont do any harm to your mobile.
Unlocking BL will erase all your data.
gracias !!
Can i unlock BL version RMX1971_11_c.02 with this apk
Juni_MJ said:
Can i unlock BL version RMX1971_11_c.02 with this apk
Click to expand...
Click to collapse
Yes, that's exactly what I was on before unlocking and rooting (INDIAN version).
Install adb and fastboot drivers in PC.
Good practice is to put all the necessary files in the C:/adb folder for installing twrp recovery.
Backup your data/pictures/notes etc first to pc.
Enable OEM unlock in Developer options. Enable USB debugging.
Install deep test apk and follow the instructions and get into FASTBOOT.
In fastboot type: fastboot flashing unlock and enter, and then unlock.
Needed Files:
twrp - link: https://files.orangefox.tech/OrangeFox-Beta/rmx1971/OrangeFox-R10.1_1-Beta-RMX1971.zip
vbmeta - link: https://drive.google.com/file/d/17hHXy4tJVxoXAIdTuVV--gq6qI_fsmaQ
But my realme 5 pro have (Indonesian version) this is work to ?
Juni_MJ said:
But my realme 5 pro have (Indonesian version) this is work to ?
Click to expand...
Click to collapse
I only suggest you to install fastboot on your phone. No harm in it.
But before unlocking, please confirm with your similar phone user because this is not the time to experiment.
thanks.
Juni_MJ said:
But my realme 5 pro have (Indonesian version) this is work to ?
Click to expand...
Click to collapse
On a positive note according to faisalxp (quoting from his thread)
"" Realme 5 Pro - All Global Region ID, IN, EU, RU, etc it's same EXCEPT Realme Q ""
So, i suggest you please ask in this thread about your phone version support.
https://forum.xda-developers.com/realme-5-pro/how-to/stock-firmware-boot-recovery-vbmeta-t4006615
jijojamie said:
I only suggest you to install fastboot on your phone. No harm in it.
But before unlocking, please confirm with your similar phone user because this is not the time to experiment.
thanks.
Click to expand...
Click to collapse
Oke thanks i hope
this work on my phone ???
jijojamie said:
On a positive note according to faisalxp (quoting from his thread)
"" Realme 5 Pro - All Global Region ID, IN, EU, RU, etc it's same EXCEPT Realme Q ""
So, i suggest you please ask in this thread about your phone version support.
https://forum.xda-developers.com/realme-5-pro/how-to/stock-firmware-boot-recovery-vbmeta-t4006615
Click to expand...
Click to collapse
i have problem command write failed with this but in depth test work
Juni_MJ said:
i have problem command write failed with this but in depth test work
Click to expand...
Click to collapse
Not sure why.
Which command you typed in fastboot?
fastboot flashing unlock - if this command gave you this error. Try the regular one
fastboot oem unlock.
jijojamie said:
Not sure why.
Which command you typed in fastboot?
fastboot flashing unlock - if this command gave you this error. Try the regular one
fastboot oem unlock.
Click to expand...
Click to collapse
Okee thanks
Guys i am getting serious issue... Yesterday i have downgrade system successful but my phone do not goes to fastboot moode its reboots to system
prashant.palange said:
Guys i am getting serious issue... Yesterday i have downgrade system successful but my phone do not goes to fastboot moode its reboots to system
Click to expand...
Click to collapse
What's the status now? Fixed?
Can we relock the bootloader with this? I unlocked my bootloader on ColorOS 6 and then updated my phone to Realme UI via OTA, now I want to lock the bootloader but idk how.
RockV said:
Can we relock the bootloader with this? I unlocked my bootloader on ColorOS 6 and then updated my phone to Realme UI via OTA, now I want to lock the bootloader but idk how.
Click to expand...
Click to collapse
Yes, you can use the app prompt "Apply to exit in-depth test". It will reboot to Fastboot where you need to type the command to lock.
Fastboot help - will give you all the commands available.
Commands available:
locking/unlocking:
Fastboot flashing lock|unlock Lock/unlock partitions for flashing
I suggest you research a bit more. Phone might get bricked. Do it at your own risk.
You should not be on TWRP, go back to official recovery.
If you have rooted, UNROOT first and do the rest.
jijojamie said:
Yes, you can use the app prompt "Apply to exit in-depth test". It will reboot to Fastboot where you need to type the command to lock.
Fastboot help - will give you all the commands available.
Commands available:
locking/unlocking:
Fastboot flashing lock|unlock Lock/unlock partitions for flashing
I suggest you research a bit more. Phone might get bricked. Do it at your own risk.
You should not be on TWRP, go back to official recovery.
If you have rooted, UNROOT first and do the rest.
Click to expand...
Click to collapse
Actually when i press that button it shows this "You can only apply to exit in-depth test after carrying out bootloader lock operation in fastboot mode".
so I went into fastboot mode and used the command fastboot flashing lock it wiped my data and rebooted to welcome screen (language region setup)
Should I now use the app to "Apply to exit in-depth test"? or don't use the app?
Hello, i unlocked the bootloader of my motorola one action. And i installed lineage 18.1 official, but i want to lock the bootloader again. i tried locking the bootloader using this help thread https://forum.xda-developers.com/t/...-2019-ask-any-question-noob-friendly.4010875/ but it din't work. Can somewone help me?
raphaelgamer981 said:
Hello, i unlocked the bootloader of my motorola one action. And i installed lineage 18.1 official, but i want to lock the bootloader again. i tried locking the bootloader using this help thread https://forum.xda-developers.com/t/...-2019-ask-any-question-noob-friendly.4010875/ but it din't work. Can somewone help me?
Click to expand...
Click to collapse
NEVER lock a phone with custom firmware installed. This usually leads to bootloops.
georg3_ said:
NEVER lock a phone with custom firmware installed. This usually leads to bootloops.
Click to expand...
Click to collapse
No, I Didn't try to lock the bootloader with a custom firmware.
raphaelgamer981 said:
No, I Didn't try to lock the bootloader with a custom firmware.
Click to expand...
Click to collapse
What are the steps you took before relocking the bootloader?
In my experience, relocking the bootloader should be the last thing you do, after you've got a working/bootable stock ROM.
arsradu said:
What are the steps you took before relocking the bootloader? In my experience, relocking the bootloader should be the last thing you do, after you've got a working/bootable stock ROM.
Click to expand...
Click to collapse
So, after i installed the latest stock rom, the device worked normally, but after waiting a while for the oem lock option appear in development options, it din´t show up. so i just gave up and installed lineage 19.1 but if i can i want to lock the bootloader again.
Raphael, I think you might have quoted my post twice, but didn't add an actual answer. Or maybe I'm super blind and I can't see it.
arsradu said:
Raphael, I think you might have quoted my post twice, but didn't add an actual answer. Or maybe I'm super blind and I can't see it.
Click to expand...
Click to collapse
ohh sorry, i tried replying to your post in my ipad 3 and it din´t show up any caracters.
raphaelgamer981 said:
So, after i installed the latest stock rom, the device worked normally, but after waiting a while for the oem lock option appear in development options, it din´t show up. so i just gave up and installed lineage 19.1 but if i can i want to lock the bootloader again.
Click to expand...
Click to collapse
So, the OEM lock/unlock thing comes with a pretty big caveat, and you need to be aware of it: loss of data.
Every time you lock or unlock your bootloader, a wipe data is triggered.
Now, for as far as I know, to lock the bootloader, you need two things:
1. Stock ROM. Don't do this on a custom ROM!
2. following command, in Terminal/Cmd Prompt
fastboot oem lock
Of course, you need to be in fastboot mode, so if you're not, and if you're booted and connected via USB (USB debugging needs to be ON and RSA fingerprinting accepted), do:
adb devices
It should display your device here. This is just to make sure ADB is working properly.
adb reboot bootloader
At this point, the phone should reboot into bootloader, so now you can do the lock command
fastboot oem lock
Data should be erased and, in case it doesn't automatically boot up, you can reboot the phone.
Don't worry about the OEM unlocking option in Developer Options. You just make sure the stock ROM is functional before attempting to relock the bootloader.
arsradu said:
So, the OEM lock/unlock thing comes with a pretty big caveat, and you need to be aware of it: loss of data.
Every time you lock or unlock your bootloader, a wipe data is triggered.
Now, for as far as I know, to lock the bootloader, you need two things:
1. Stock ROM. Don't do this on a custom ROM!
2. following command, in Terminal/Cmd Prompt
fastboot oem lock
Of course, you need to be in fastboot mode, so if you're not, and if you're booted and connected via USB (USB debugging needs to be ON and RSA fingerprinting accepted), do:
adb devices
It should display your device here. This is just to make sure ADB is working properly.
adb reboot bootloader
At this point, the phone should reboot into bootloader, so now you can do the lock command
fastboot oem lock
Data should be erased and, in case it doesn't automatically boot up, you can reboot the phone.
Don't worry about the OEM unlocking option in Developer Options. You just make sure the stock ROM is functional before attempting to relock the bootloader.
Click to expand...
Click to collapse
I tried that, and it din´t work, this method is the same that was in a help thread in xda forum of my device, this command works fine in my nexus 6, but on my moto one action it does not, i unlocked my bootloader via the normal method using motorola´s website, not using another method.
raphaelgamer981 said:
I tried that, and it din´t work, this method is the same that was in a help thread in xda forum of my device, this command works fine in my nexus 6, but on my moto one action it does not, i unlocked my bootloader via the normal method using motorola´s website, not using another method.
Click to expand...
Click to collapse
raphaelgamer981 said:
I tried that, and it din´t work, this method is the same that was in a help thread in xda forum of my device, this command works fine in my nexus 6, but on my moto one action it does not, i unlocked my bootloader via the normal method using motorola´s website, not using another method.
Click to expand...
Click to collapse
But why do you say it didn't work? Do you get an error at any point during the process?
arsradu said:
But why do you say it didn't work? Do you get an error at any point during the process?
Click to expand...
Click to collapse
no, i run the command and it asks for changing the oem lock setting in developer options, i reboot the phone and run through the setup process. Then when i enable developer options and check the oem lock option, it is greyed out.
Is it greyed out in the on or off position? Can you attach a screenshot? I don't remember the operations sequence... But I think the option was automatically switched back to the original position (off) when you lock the bootloader. I could be wrong though. So...when you run the "fastboot oem lock" command, it asks you to....what?
Set the option to on or off? Some screenshots from both the PC, with the message, and the developer options might help to clarify this.
arsradu said:
Is it greyed out in the on or off position? Can you attach a screenshot? I don't remember the operations sequence... But I think the option was automatically switched back to the original position (off) when you lock the bootloader. I could be wrong though. So...when you run the "fastboot oem lock" command, it asks you to....what?
Set the option to on or off? Some screenshots from both the PC, with the message, and the developer options might help to clarify this.
Click to expand...
Click to collapse
it is greyed in the on position, i can´t add a screenshot because i am in lineage 19.1 with root and the option shows up,when i run the command in cmd, it says to me to check the oem lock option in developer options
raphaelgamer981 said:
it is greyed in the on position, i can´t add a screenshot because i am in lineage 19.1 with root and the option shows up,when i run the command in cmd, it says to me to check the oem lock option in developer options
Click to expand...
Click to collapse
A screenshot would be really useful. But don't worry about it. When you're back to stock rom and ready to lock your bootloader, we can resume this then. I think either we're missing something, or it's everything ok, and you just need to switch that option off. Though, I remember I didn't have to do it manually. But I could be wrong though.
So, don't worry. Enjoy LineageOS and we can resume this when you're back to stock ROM and ready to lock.
arsradu said:
A screenshot would be really useful. But don't worry about it. When you're back to stock rom and ready to lock your bootloader, we can resume this then. I think either we're missing something, or it's everything ok, and you just need to switch that option off. Though, I remember I didn't have to do it manually. But I could be wrong though.
So, don't worry. Enjoy LineageOS and we can resume this when you're back to stock ROM and ready to lock.
Click to expand...
Click to collapse
ok thanks for your help!
arsradu said:
A screenshot would be really useful. But don't worry about it. When you're back to stock rom and ready to lock your bootloader, we can resume this then. I think either we're missing something, or it's everything ok, and you just need to switch that option off. Though, I remember I didn't have to do it manually. But I could be wrong though.
So, don't worry. Enjoy LineageOS and we can resume this when you're back to stock ROM and ready to lock.
Click to expand...
Click to collapse
hello, so i want to lock the bootloader again, how do i install the stock rom back?
arsradu said:
A screenshot would be really useful. But don't worry about it. When you're back to stock rom and ready to lock your bootloader, we can resume this then. I think either we're missing something, or it's everything ok, and you just need to switch that option off. Though, I remember I didn't have to do it manually. But I could be wrong though.
So, don't worry. Enjoy LineageOS and we can resume this when you're back to stock ROM and ready to lock.
Click to expand...
Click to collapse
so after running the fastboot oem lock command, it asked this in the cmd
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem lock
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.080s]
finished. total time: 0.080s
when i rebooted the phone, it showed the screen saying that the bootloader was unlocked. also i had to re run the command because it was going to erase my phone but that din´t happend, after going to developer options the option was still greyed out.
The last 3 days i've tried some roms from here.first i've unlocked the bootloader in developer menu,then from fastboot with the unlock key provided by motorola website,i've tried different rom,didnt like that i cannot use bank apps.so i went for locking.full reset,adb enable,reboot bootloader,full flash stock rom (last one from Motorola),reboot to check,adb enable, reboot bootloader,run command " fastboot oem lock " once ,it asked for confirmation due to data loss,then run command " fastboot oem lock " once more,then reboot to os.everything went ok,device dont show that was unlocked