Related
It is stuck on a screen with the battery. I can get to bootloader mode but cannot get into recovery. Bootloader is locked... Please help
Basically I had the bootloader unlocked and it was rooted. I unrooted the phone and then I locked the bootloader and I am here now. Just wanted to make it go back to stock.
Is it a carrier model or a play store
https://forum.xda-developers.com/pixel-xl/how-to/psa-read-ca-bootloader-t3494615
This.
chapelfreak said:
Is it a carrier model or a play store
Click to expand...
Click to collapse
Google store
ASimpleSock said:
https://forum.xda-developers.com/pixel-xl/how-to/psa-read-ca-bootloader-t3494615
This.
Click to expand...
Click to collapse
I see the thread but it doesnt seem like theres a fix in it
tryfont said:
I see the thread but it doesnt seem like theres a fix in it
Click to expand...
Click to collapse
There probably isn't, if you've altered system and relock and toggle OEM unlocking off in dev. options you get bricked.
tryfont said:
It is stuck on a screen with the battery. I can get to bootloader mode but cannot get into recovery. Bootloader is locked... Please help
Basically I had the bootloader unlocked and it was rooted. I unrooted the phone and then I locked the bootloader and I am here now. Just wanted to make it go back to stock.
Click to expand...
Click to collapse
Did you try:
fastboot flashing unlock
Since you only relocked, you unlikely toggled "OEM unlock"?!
If it fails, I think you are SOL. Maybe someone with a proper solution will chime in. Otherwise, you have to RMA your device...
Good luck...
5.1 said:
Did you try:
fastboot flashing unlock
Since you only relocked, you unlikely toggled "OEM unlock"?!
If it fails, I think you are SOL. Maybe someone with a proper solution will chime in. Otherwise, you have to RMA your device...
Good luck...
Click to expand...
Click to collapse
It just says waiting for device and hangs there... I don't think it recognizes the phone
EDIT: IT WORKED!!!!!
It wouldnt recognize it and I ran fastboot continue and it just hanged there but I went into the bootloader mode and for like a quarter of a second it recognized it and forced it to boot
tryfont said:
It just says waiting for device and hangs there... I don't think it recognizes the phone
Click to expand...
Click to collapse
Open device manager in windows. Plug your phone and see how is your phone recognized.?!
5.1 said:
Open device manager in windows. Plug your phone and see how is your phone recognized.?!
Click to expand...
Click to collapse
Im on mac but its good now I edited my comment above. Only question is how to I completely clean the OS so I can relock bootloader without running into the same problem
This is whats happening to me- https://goo.gl/photos/2kv9Xo3HM3Mqn8AQ9
tryfont said:
Im on mac but its good now I edited my comment above. Only question is how to I completely clean the OS so I can relock bootloader without running into the same problem
Click to expand...
Click to collapse
Hey... Go into recovery and perform a factory reset.
Reboot bootloader and flash stock firmware. You could flash both slots to be sure your device is completely clean.
I wrote a how-to for someone having another issue. You.can follow this:
https://forum.xda-developers.com/showpost.php?p=71849370&postcount=28
When you are finished with flashing, reboot to be sure your system boot properly and your phone works as it should...
From here you can reboot into bootloader and issue:
fastboot flashing lock
If It was me I'd leave it unlocked though... Or at least OEM unlock enabled and ADB debugging ON. Since Google tend to release messed up OTA, you can always unlock the bootloader if needed.
But if you wish you can also disable the OEM unlock.
Good luck...
5.1 said:
Hey... Go into recovery and perform a factory reset.
Reboot bootloader and flash stock firmware. You could flash both slots to be sure your device is completely clean.
I wrote a how-to for someone having another issue. You.can follow this:
https://forum.xda-developers.com/showpost.php?p=71849370&postcount=28
When you are finished with flashing, reboot to be sure your system boot properly and your phone works as it should...
From here you can reboot into bootloader and issue:
fastboot flashing lock
If It was me I'd leave it unlocked though... Or at least OEM unlock enabled and ADB debugging ON. Since Google tend to release messed up OTA, you can always unlock the bootloader if needed.
But if you wish you can also disable the OEM unlock.
Good luck...
Click to expand...
Click to collapse
I'm pretty inexperienced with this kind of stuff and so you might have to explain it a bit further than what that link says. I did fastboot reboot bootloader in terminal but it can't find my device. Also I couldnt get into recovery when it was bricked so I probably still can't
tryfont said:
I'm pretty inexperienced with this kind of stuff and so you might have to explain it a bit further than what that link says. I did fastboot reboot bootloader in terminal but it can't find my device
Click to expand...
Click to collapse
Hey...
You boot into bootloader when the Device is powered off
Just like in your video: with power + volume down
You can see infos regarding:
Bootloader
Radio
S/N
DRAM
Boot-slot=
Etc...
This is the bootloader :good:
From here, unzip the google image you have downloaded, open the folder and from here run the flash-all script. Let your device reboot. Power it down, boot into bootloader again with power + volume down. Change active slot as I described in the link I gave you previously. Run the same flash-all again... Done!
Just for safety, remove your Google account before you continue. You'll add it again later...
Good luck...
5.1 said:
Hey...
You boot into bootloader when the Device is powered off
Just like in your video: with power + volume down
You can see infos regarding:
Bootloader
Radio
S/N
DRAM
Boot-slot=
Etc...
This is the bootloader :good:
From here, unzip the google image you have downloaded, open the folder and from here run the flash-all script. Let your device reboot. Power it down, boot into bootloader again with power + volume down. Change active slot as I described in the link I gave you previously. Run the same flash-all again... Done!
Just for safety, remove your Google account before you continue. You'll add it again later...
Good luck...
Click to expand...
Click to collapse
Alright thank you so much its doing the flashing right now. I really appreciate you helping...I was worried I'd have to get a replacement through google. Have a great day lad
tryfont said:
Alright thank you so much its doing the flashing right now. I really appreciate you helping...I was worried I'd have to get a replacement through google. Have a great day lad
Click to expand...
Click to collapse
Hey... Flash both slots... Just to be sure both are clean and nothing problematic remains on your device before locking your bootloader!
It could brick installing an OTA or whatever. Better restart 100% clean. :good:
Cheers...
Just flash the flash-all, relock and call it a day. Then you'll be fully stock and locked. I would however recommend rebooting once before locking to make sure its all good.
tryfont said:
It is stuck on a screen with the battery. I can get to bootloader mode but cannot get into recovery. Bootloader is locked... Please help
Basically I had the bootloader unlocked and it was rooted. I unrooted the phone and then I locked the bootloader and I am here now. Just wanted to make it go back to stock.
Click to expand...
Click to collapse
Hey man I have the same problem you can try calling Google support they can send you a replacement if you still have a warranty
my warranty has expired so I'm on my own
Hi,
Like the title says, my Pixel XL is bootlooping.
The only thing that works is getting to bootloader, I can't even get to recovery without it booting again. The biggest problem is that it's OEM locked and obviously I can't unlock it via developer options.
Is there any way to unlock it without booting to the OS?
Don't Ask said:
Hi,
Like the title says, my Pixel XL is bootlooping.
The only thing that works is getting to bootloader, I can't even get to recovery without it booting again. The biggest problem is that it's OEM locked and obviously I can't unlock it via developer options.
Is there any way to unlock it without booting to the OS?
Click to expand...
Click to collapse
OEM unlock must be toggled before unlocking bootloader or CMD won't work, Can't you flash stock OTA in the recovery? https://developers.google.com/android/ota You can sideload the zip and should flash it to save your device once you get into the OS unlock your bootloader and avoid a situation like this again
liam_davenport said:
OEM unlock must be toggled before unlocking bootloader or CMD won't work, Can't you flash stock OTA in the recovery? https://developers.google.com/android/ota You can sideload the zip and should flash it to save your device once you get into the OS unlock your bootloader and avoid a situation like this again
Click to expand...
Click to collapse
Thanks, but like I said - I can't get into recovery mode and the phone is OEM locked.
Don't Ask said:
Thanks, but like I said - I can't get into recovery mode and the phone is OEM locked.
Click to expand...
Click to collapse
Sorry missread... My bad Contact Google sounds like an RMA job for this one
Hey, if you can get into the bootloader, there's a high chance you can use fastboot. Using a computer to install adb/fastboot and then using the command line to run
`fastboot reboot recovery` (without the ticks)
Worth a shot, but if you can't get into recovery, I'm afraid the recovery might be failing as well.
khoanguyen96 said:
Hey, if you can get into the bootloader, there's a high chance you can use fastboot. Using a computer to install adb/fastboot and then using the command line to run
`fastboot reboot recovery` (without the ticks)
Worth a shot, but if you can't get into recovery, I'm afraid the recovery might be failing as well.
Click to expand...
Click to collapse
I've tried that as well with no success, it simply starts boot looping again.
I read somewhere about EDL mode, does something that like actually work for the Pixel?
Don't Ask said:
I've tried that as well with no success, it simply starts boot looping again.
I read somewhere about EDL mode, does something that like actually work for the Pixel?
Click to expand...
Click to collapse
Hey, yeah I looked into EDL mode. No luck unfortunately, looks like it requires special files manufacturers only have access to. Is there any way you can do a RMA?
This is potentially a MUCH easier way to OEM Unlock the S9.
I bought my S9 and waited the 7 days,did the unlock and accidentally let it wipe and reboot, so I had to wait the 7 days again. I tried the date manipulation trick and it never worked. Flashing a new bootloader wouldn't work.
Then I saw that Fastboot had an OEM unlock command, so I tried that, but it said it failed.
But then today, the 7 days were up again, and oem unlock finally appeared in my dev options again, and behold, OEM Unlock was already true!
I'm going to try flashing twrp and rooting later today, but I thought someone who may not want to wait 7 days could try this and see if even though it "fails" the bootloader may unlock anyway!
Assuming you have Fastboot and the proper USB drivers etc. Also assuming the device is not modified from its factory state etc.
Steps to attempt:
1. Turn off the phone.
2. Hold vol up, bixby, and power (to go into Fastboot)
3. From a command prompt enter: fastboot oem unlock
4. It will say it failed.
5. Attempt flashing the recovery of your choice via: fastboot flash recovery <recovery file>
Let people know in the comments whether this works!
Did this method work for your....
LysolPionex said:
This is potentially a MUCH easier way to OEM Unlock the S9.
I bought my S9 and waited the 7 days,did the unlock and accidentally let it wipe and reboot, so I had to wait the 7 days again. I tried the date manipulation trick and it never worked. Flashing a new bootloader wouldn't work.
Then I saw that Fastboot had an OEM unlock command, so I tried that, but it said it failed.
But then today, the 7 days were up again, and oem unlock finally appeared in my dev options again, and behold, OEM Unlock was already true!
I'm going to try flashing twrp and rooting later today, but I thought someone who may not want to wait 7 days could try this and see if even though it "fails" the bootloader may unlock anyway!
Assuming you have Fastboot and the proper USB drivers etc. Also assuming the device is not modified from its factory state etc.
Steps to attempt:
1. Turn off the phone.
2. Hold vol up, bixby, and power (to go into Fastboot)
3. From a command prompt enter: fastboot oem unlock
4. It will say it failed.
5. Attempt flashing the recovery of your choice via: fastboot flash recovery <recovery file>
Let people know in the comments whether this works!
Click to expand...
Click to collapse
which variant you use?
angel8502 said:
which variant you use?
Click to expand...
Click to collapse
SM-960F/DS.
But I just got the "Only Official released binaries are allowed to be flashed" message, so I might get to try this method again myself, lol.
How exactly are you able to run fastboot commands when this is a samsung?? Odin is fastboot replacement and there is no way to make it recognize Fastboot. Please enlighten
beatbreakee said:
How exactly are you able to run fastboot commands when this is a samsung?? Odin is fastboot replacement and there is no way to make it recognize Fastboot. Please enlighten
Click to expand...
Click to collapse
Well, I just got the lock screen freeze and had to force a reboot, and when I did, I couldn't flash anything recovery or rom via Odin, so I tried using fastboot again to oem unlock, and it fastboot didn't even see it connected, so what you're saying makes sense.
Is it possible I used ADB instead? Does ADB have an oem unlock command as well? Or maybe the factory reset after the first toggle didn't set OEM lock like it normally does?
I'm not sure what I did, but OEM unlock was definitely toggled on once the option appeared. I'm going to play around with it a bit more.
On a side note, when I go into download mode, it still says OEM LOCK: off, but still won't let me flash unofficial bins. Would the RMM Prenormal have something to do with that?
LysolPionex said:
Well, I just got the lock screen freeze and had to force a reboot, and when I did, I couldn't flash anything recovery or rom via Odin, so I tried using fastboot again to oem unlock, and it fastboot didn't even see it connected, so what you're saying makes sense.
Is it possible I used ADB instead? Does ADB have an oem unlock command as well? Or maybe the factory reset after the first toggle didn't set OEM lock like it normally does?
I'm not sure what I did, but OEM unlock was definitely toggled on once the option appeared. I'm going to play around with it a bit more.
On a side note, when I go into download mode, it still says OEM LOCK: off, but still won't let me flash unofficial bins. Would the RMM Prenormal have something to do with that?
Click to expand...
Click to collapse
take a pic n post it of download mode
elliwigy said:
take a pic n post it of download mode
Click to expand...
Click to collapse
Just a close up, nothing else relevant in the screen.
LysolPionex said:
Just a close up, nothing else relevant in the screen.
Click to expand...
Click to collapse
most likely is the rmm state
elliwigy said:
most likely is the rmm state
Click to expand...
Click to collapse
That makes sense with what I found last night in another thread. I think I used an old version of the rmm Mesa bypass too, so we'll see what happens. In another 5 days...
This will not work. The large majority of Samsung devices (exceptions being the Galaxy Nexus and Nexus S) don't support Fastboot and there isn't any way to unlock the device using ADB.
The reason why your "OEM unlock" switch was already toggled was because, even after the data wipe, it doesn't reset. Your device stays OEM unlocked, but isn't RMM unlocked until the 7 day timer has passed -- so your bootloader stays locked until the RMM timer passes.
Fun fact: you can flash the "combination" firmware to your device and immediately enable OEM unlock, but you'll have to flash the normal firmware back and let the RMM lock timer pass still. You won't have to wipe your device that way.
tomiga said:
This will not work. The large majority of Samsung devices (exceptions being the Galaxy Nexus and Nexus S) don't support Fastboot and there isn't any way to unlock the device using ADB.
The reason why your "OEM unlock" switch was already toggled was because, even after the data wipe, it doesn't reset. Your device stays OEM unlocked, but isn't RMM unlocked until the 7 day timer has passed -- so your bootloader stays locked until the RMM timer passes.
Fun fact: you can flash the "combination" firmware to your device and immediately enable OEM unlock, but you'll have to flash the normal firmware back and let the RMM lock timer pass still. You won't have to wipe your device that way.
Click to expand...
Click to collapse
This is the first time I've seen a clear explanation off all of this. Thank you for that!
What do I need to flash a combination firmware? Anda what is this combination?
Ps: sorry my english I am Brasilian. He...he..
Regikitten said:
What do I need to flash a combination firmware? Anda what is this combination?
Ps: sorry my english I am Brasilian. He...he..
Click to expand...
Click to collapse
I'm not familiar with it, but I assume he's talking about this: https://forum.xda-developers.com/ga...ollection-combination-rom-samsung-s9-t3782737
There are a couple other threads about it in the S9 forum.
tomiga said:
This will not work. The large majority of Samsung devices (exceptions being the Galaxy Nexus and Nexus S) don't support Fastboot and there isn't any way to unlock the device using ADB.
The reason why your "OEM unlock" switch was already toggled was because, even after the data wipe, it doesn't reset. Your device stays OEM unlocked, but isn't RMM unlocked until the 7 day timer has passed -- so your bootloader stays locked until the RMM timer passes.
Fun fact: you can flash the "combination" firmware to your device and immediately enable OEM unlock, but you'll have to flash the normal firmware back and let the RMM lock timer pass still. You won't have to wipe your device that way.
Click to expand...
Click to collapse
So I kept the device on for 155 hours, and the oem option appeared again, so I booted into download mode: RMM prenormal (oem lock off still). When I started it back up, the oem option was gone again (still is). Does the 7 day period have to be without turning the device off?
LysolPionex said:
So I kept the device on for 155 hours, and the oem option appeared again, so I booted into download mode: RMM prenormal (oem lock off still). When I started it back up, the oem option was gone again (still is). Does the 7 day period have to be without turning the device off?
Click to expand...
Click to collapse
to my understanding yes lol.. theres many threads with specific instructions.. if u miss one lil step u start over waiting period and all
elliwigy said:
to my understanding yes lol.. theres many threads with specific instructions.. if u miss one lil step u start over waiting period and all
Click to expand...
Click to collapse
Lol, so I'm at 182 hours uptime, but the OEM option isn't in dev options...do I risk going to download mode to see RMM status?
tomiga said:
This will not work. The large majority of Samsung devices (exceptions being the Galaxy Nexus and Nexus S) don't support Fastboot and there isn't any way to unlock the device using ADB.
The reason why your "OEM unlock" switch was already toggled was because, even after the data wipe, it doesn't reset. Your device stays OEM unlocked, but isn't RMM unlocked until the 7 day timer has passed -- so your bootloader stays locked until the RMM timer passes.
Fun fact: you can flash the "combination" firmware to your device and immediately enable OEM unlock, but you'll have to flash the normal firmware back and let the RMM lock timer pass still. You won't have to wipe your device that way.
Click to expand...
Click to collapse
The above information was clear and helpful, but one query with respect to my case.
I have an Samsung S7 edge (SM-G935FD), i have flashed custom ROM successfully, but due to some reason I need to go back to my Stock ROM and I was able to do successfully.
The question is, seems still my OEM is unlocked even after stock ROM, will the OEM lock will happen automatically after 7 days, or is there any way to lock back manually.
Thanks in Advance
Samsung doesn´t have fastboot , it uses some kind of own mode only accessible via Odin. I prefer this way.
Also you have Prenormal state , this is some kind of security blocking by Knox, happened to me and had to wait 7 days.
---------- Post added at 08:45 AM ---------- Previous post was at 08:44 AM ----------
askader said:
The above information was clear and helpful, but one query with respect to my case.
I have an Samsung S7 edge (SM-G935FD), i have flashed custom ROM successfully, but due to some reason I need to go back to my Stock ROM and I was able to do successfully.
The question is, seems still my OEM is unlocked even after stock ROM, will the OEM lock will happen automatically after 7 days, or is there any way to lock back manually.
Thanks in Advance
Click to expand...
Click to collapse
Will appear within 5-7 days since you flashed stock ROM.
ZoiraP said:
Samsung doesn´t have fastboot , it uses some kind of own mode only accessible via Odin. I prefer this way.
Also you have Prenormal state , this is some kind of security blocking by Knox, happened to me and had to wait 7 days.
---------- Post added at 08:45 AM ---------- Previous post was at 08:44 AM ----------
Will appear within 5-7 days since you flashed stock ROM.
Click to expand...
Click to collapse
Did it solved after 7 days?
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
Hello,
I've recently switched to Android 13 B2 and after the restart required for 2.1, the phone immediately went into a bootloop.
Android Flasher requires the bootloader to be unlocked, which I can't do now as Oem unlocking was disabled in developer options. Pixel repair also doesn't work as it is not compatible with Android 13. (Your phone's current software version:TPBB.220414.015 is newer than what this repair tool has.)
Does anyone know how I can recover the phone? Thank you.
Hopefully you had USB debugging enabled could sideload an ota
fil3s said:
Hopefully you had USB debugging enabled could sideload an ota
Click to expand...
Click to collapse
I don't think he can. I'm almost positive that you need to have the bootloader unlocked to sideload any updates. If it's not unlocked then you are often close to SOL =(.
IonutP said:
Hello,
I've recently switched to Android 13 B2 and after the restart required for 2.1, the phone immediately went into a bootloop.
Android Flasher requires the bootloader to be unlocked, which I can't do now as Oem unlocking was disabled in developer options. Pixel repair also doesn't work as it is not compatible with Android 13. (Your phone's current software version:TPBB.220414.015 is newer than what this repair tool has.)
Does anyone know how I can recover the phone? Thank you.
Click to expand...
Click to collapse
1. have you have any chances that you still have warranty?
2. had you already went to recovery mode and wiped cache? if still not boot try wipe userdata?
edit: OP had solved the problem.
fil3s said:
Hopefully you had USB debugging enabled could sideload an ota
Click to expand...
Click to collapse
Thank you, much appreciated! I had this option enabled and was able to sideload the OTA from here https://forum.xda-developers.com/t/...e-with-a-new-predictive-back-gesture.4380119/.
Then I've enabled oem unlocking and flashed 12.1 with Android Flasher. Everything's back to normal now.