Has anyone tried this yet? There are tutorials that have popped up within the last 24 hours that say nothing about having to enable the OEM Unlock to root your phone.
Sorry, I'm a new member so I can't post the links I'm referring to
nothing to see here, thought I posted something that is in line with the thread, however, when you go to Chainfire's site it does have the following warning:
"UNLOCK BOOTLOADERS
If you have locked bootloaders, flashing one of these will probably brick your device - with the exception of Nexus devices, which will usually automatically "OEM unlock" and wipe your data !"
Related
Hello, I have several questions about Verified Boot. I've previously owned a rooted Nexus 5, but I never cared about keeping my bootloader unlocked state. Now I have a OnePlus 5, and while looking for info online I learnt about Verified Boot and how keeping my bootloader unlocked is a security risk.
Then I found that you can add your own certificate, which would be used if the OEM verification fails and allows you (AFAIK!) to flash any zip you sign with the bootloader locked. I also found a thread here where it explains how to do it.
So my questions are:
Does the procedure linked before allows flashing my own zips with a locked bootloader or am I missing something?
If it allows you to have the benefits of an unlocked bootloader while keeping the same security measures, why isn't its usage more widespread?
That's all. BTW hi to everyone! It's my first post here
a) There is no logical reason to bootloader lock a phone. You will gain nothing.
b) If you lock it there is a high probability you won't ever be able to bootloader unlock it again - no more mods - ever.
EDIT: Perhaps if you flash the "correct stock" meaning one like/identical to the one that you originally had on your phone when you unlocked it the first time, it will work...
Think about this, please, before you flash things!!!
Do you refer to lock and unlock the bootloader? I locked and unlocked it much times and I've never had problems (obviously considering the bootloader version).
gercdgcat said:
Do you refer to lock and unlock the bootloader? I locked and unlocked it much times and I've never had problems (obviously considering the bootloader version).
Click to expand...
Click to collapse
Thanks for replying - could you perhaps write a guide as to exactly how you unlock your bl after using fastboot lock?
I have seen a few folks who appear stuck at that point and I and they would be happy campers if they could get around that!!!
Thanks!
EDIT: I added a comment about "correct stock" to the first post... This may be key to the folks that are having trouble...
You might look at thread
https://forum.xda-developers.com/moto-z-play/help/please-help-urgently-t3814260
But I guess I would have to call anyone who successfully locks and unlocks again their bootloader as darn lucky. Some, (many?) can't.
In the end I still have to ask "why the heck are you locking your phone" - what could you possibly gain? It's totally unnecessary. it can be a very expensive little line of code.
I lock my phone all the time, multiple times per day even! It's really easy to unlock: I simply put my finger on the sensor and voila!
Maybe you mean the bootloader? That would be a helpful little detail to add to the title of your post.
pkadavid said:
I lock my phone all the time, multiple times per day even! It's really easy to unlock: I simply put my finger on the sensor and voila!
Maybe you mean the bootloader? That would be a helpful little detail to add to the title of your post.
Click to expand...
Click to collapse
LOL - right! Thanks!!!
bump
I've locked mine as I upgraded to a Pixel 2 XL and gave my Z Play to my father, so I don't really care if I can't unlock it again, but I'm sure that wouldn't be an issue anyway.
IncendiaryPyro said:
I've locked mine as I upgraded to a Pixel 2 XL and gave my Z Play to my father, so I don't really care if I can't unlock it again, but I'm sure that wouldn't be an issue anyway.
Click to expand...
Click to collapse
How's the 2xl?
hithere
KrisM22 said:
a) There is no logical reason to bootloader lock a phone. You will gain nothing.
b) If you lock it there is a high probability you won't ever be able to bootloader unlock it again - no more mods - ever.
EDIT: Perhaps if you flash the "correct stock" meaning one like/identical to the one that you originally had on your phone when you unlocked it the first time, it will work...
Think about this, please, before you flash things!!!
Click to expand...
Click to collapse
I prefer stock without modifications but sometimes when i have time to try news modifications or roms i used to unlocked the phone and after this relock again, the process that i use is very simple, i just unlock with the same code that Motorola gaves to unlock bootloader, i don't have sure but if you request unlock codes to many times can be a problem but i use the same code and works good.
Basically: relock as are specifcified in another topic in this device forum( using the last stock version that you used)
And after this unlock with code again
Obs.: Is not recommended to unlock/relock to many times.
Obs2.: I only did this three times and i don't know if has a limit
bumpsi
It is my opinion also that relocking is a bad idea. But if someone likes to do it, eg to get Google Pay working without Magisk, why do you want to warn him?
Relock only is possible in combination with flashing a complete correctly firmware. If something is wrong with the firmware you flash, relocking won't succeed. Your device won't be locked if it does not fully succeed or the firmware is not correctly signed. The unlock code is supposed to stay valid, you should be able to unlock your device as many times as you want using the same code.
a) is fine, but does not consider Android SafetyNet
b) is just wrong, and this already was written in a comment.
Please do not bump wrong warnings.
Hey all,
Sorry, I know that has been covered extensively on here, but I just want to clarify my understanding and make sure I'm not waiting pointlessly and hopefully avoid mucking this up in the future.
So, I've had my Galaxy S9+ long enough that OEM UNLOCK appeared in the developer options menu. I've rooted/flashed installed enough phones in the past that I stupidly didn't read up on any of the newer security features (such as RMM).
I OEM unlocked the phone, restarted, and everything looked fine. I've then rebooted into Odon (3.13.1, downloaded through Sam Mobile) and tried to install the tar file associated with my phone (twrp-3.2.3-0-star2lte).
Odin failed to install, with the error message, "only official released binaries are allowed to be flashed(recovery)" After a quick look around, this error message appears to be associated with a bootloader that is still locked:
If I look at the values at the top of the download menu, I see
RMM STATE: Prenormal
FRP LOCK: Off
OEM LOCK: Off
So, if my OEM lock is off, is it the RMM state preventing me from flashing the device? If so, is this a wait seven days without restarting the phone for RMM state to change to normal or am I missing something entirely?
What I've also read, is it is required to do the TWRP flash mid-OEM unlock (during the reboot of the factory reset), is this something I will still need to do?
Any direction appreciated. Sorry for posting on the same subject so many others have, I just can't quite find any information on it when the OEM is unlocked already.
ta.
jusx10i said:
Hey all,
Sorry, I know that has been covered extensively on here, but I just want to clarify my understanding and make sure I'm not waiting pointlessly and hopefully avoid mucking this up in the future.
So, I've had my Galaxy S9+ long enough that OEM UNLOCK appeared in the developer options menu. I've rooted/flashed installed enough phones in the past that I stupidly didn't read up on any of the newer security features (such as RMM).
I OEM unlocked the phone, restarted, and everything looked fine. I've then rebooted into Odon (3.13.1, downloaded through Sam Mobile) and tried to install the tar file associated with my phone (twrp-3.2.3-0-star2lte).
Odin failed to install, with the error message, "only official released binaries are allowed to be flashed(recovery)" After a quick look around, this error message appears to be associated with a bootloader that is still locked:
If I look at the values at the top of the download menu, I see
RMM STATE: Prenormal
FRP LOCK: Off
OEM LOCK: Off
So, if my OEM lock is off, is it the RMM state preventing me from flashing the device? If so, is this a wait seven days without restarting the phone for RMM state to change to normal or am I missing something entirely?
What I've also read, is it is required to do the TWRP flash mid-OEM unlock (during the reboot of the factory reset), is this something I will still need to do?
Any direction appreciated. Sorry for posting on the same subject so many others have, I just can't quite find any information on it when the OEM is unlocked already.
ta.
Click to expand...
Click to collapse
I'd love any info on this as well.
Unfortunately, I just had to wait the week.
I will say though when you come to install TWRP make sure you follow the instructions. I didn't, then I had to wait another week for the OEM Unlock to re-appear again!
Hi everyone !
Hope I'm not making any double post but I couldn't find any explanation for this very specific situation.
After thorough research it, it seems that most of samsung devices has a secret setting called "OEM unlock" that we have to use to do the first step of rooting the device. In some cases that setting is missing but can be displayed again by some "date settings" tricks or waiting 7 days. In some other cases which seems to be mine, the "OEM unlock" setting is simply removed by probably the carrier of the phone and can't be reinstated.
In that last case which seems to be mine, I can't find any precise information wether we can or we simply can't unlock bootloader by other way and therefore root the phone.
Could anyone enlighten me ?
Thank you very much in advance !
-sofiann- said:
Hi everyone !
Hope I'm not making any double post but I couldn't find any explanation for this very specific situation.
After thorough research it, it seems that most of samsung devices has a secret setting called "OEM unlock" that we have to use to do the first step of rooting the device. In some cases that setting is missing but can be displayed again by some "date settings" tricks or waiting 7 days. In some other cases which seems to be mine, the "OEM unlock" setting is simply removed by probably the carrier of the phone and can't be reinstated.
In that last case which seems to be mine, I can't find any precise information wether we can or we simply can't unlock bootloader by other way and therefore root the phone.
Could anyone enlighten me ?
Thank you very much in advance !
Click to expand...
Click to collapse
I assume you know that the OEM unlock toggle is in the developer settings? To enable developers settings, tap build number repeatedly until it says you are now a developer. You will need no fancy trick to show it as the lock that hides OEM unlock, only came out in oreo. I don't think carriers disable OEM unlock on Samsung's but I could be wrong. Lastly, if you get it figured out, go over here to the right thread and get it rooted. Good luck! https://forum.xda-developers.com/sa.../how-to-root-twpr-flash-a300fu-a300y-t3494362
SnowFuhrer said:
I assume you know that the OEM unlock toggle is in the developer settings? To enable developers settings, tap build number repeatedly until it says you are now a developer. You will need no fancy trick to show it as the lock that hides OEM unlock, only came out in oreo. I don't think carriers disable OEM unlock on Samsung's but I could be wrong. Lastly, if you get it figured out, go over here to the right thread and get it rooted. Good luck! https://forum.xda-developers.com/sa.../how-to-root-twpr-flash-a300fu-a300y-t3494362
Click to expand...
Click to collapse
Thank you for the answer.
You assume right. I enabled developers settings first, saw that I didn't have OEM unlock option visible, then started to look about this issue. It is quick to see that in many case, even for phone not on OREO (I'm with Marshmallow 6.0.1), this OEM unlock is missing. But based on internet available data, it seems that in most of the case there is a trick to make it visible again. It is a sort of samsung security against thief that hide this option for seven days.
The trick didn't work for me and by looking more I saw that some people seems to be facing the same situation as mine. Some suggest that it is disabled by carrier.
But I couldn't find a solution anywhere for that context.
My question remains.
Here is a more detailed explanation :
from https://www.howtogeek.com/239798/how-to-unlock-your-android-phones-bootloader-the-official-way/
""There are two kinds of phones in this world: Those that let you unlock your bootloader, and those that don’t.
Whether you’re allowed to unlock your bootloader depends on the manufacturer of your phone, the model you have, and even your carrier. Nexus phones are all unlockable by nature, and many phones from Motorola and HTC allow you to unlock your bootloader through a similar process as the Nexus.
Other phones, however–and some carriers–don’t allow you to unlock your bootloader the official way, which means you have to wait for developers to exploit a security vulnerability if you want to root and flash ROMs. If you have one of those phones, this guide will sadly not help you.
The best way to find out which category your phone falls into is to browse its section at XDA Developers. If you have an HTC or Motorola phone, you may be able too research its unlockability on HTC or Motorola’s website. If it doesn’t support unlocking, you’ll have to use an unofficial unlocking or rooting method, which you’ll usually find on the XDA Developers forums.""
-sofiann- said:
Thank you for the answer.
You assume right. I enabled developers settings first, saw that I didn't have OEM unlock option visible, then started to look about this issue. It is quick to see that in many case, even for phone not on OREO (I'm with Marshmallow 6.0.1), this OEM unlock is missing. But based on internet available data, it seems that in most of the case there is a trick to make it visible again. It is a sort of samsung security against thief that hide this option for seven days.
The trick didn't work for me and by looking more I saw that some people seems to be facing the same situation as mine. Some suggest that it is disabled by carrier.
But I couldn't find a solution anywhere for that context.
My question remains.
Here is a more detailed explanation :
from https://www.howtogeek.com/239798/how-to-unlock-your-android-phones-bootloader-the-official-way/
""There are two kinds of phones in this world: Those that let you unlock your bootloader, and those that don’t.
Whether you’re allowed to unlock your bootloader depends on the manufacturer of your phone, the model you have, and even your carrier. Nexus phones are all unlockable by nature, and many phones from Motorola and HTC allow you to unlock your bootloader through a similar process as the Nexus.
Other phones, however–and some carriers–don’t allow you to unlock your bootloader the official way, which means you have to wait for developers to exploit a security vulnerability if you want to root and flash ROMs. If you have one of those phones, this guide will sadly not help you.
The best way to find out which category your phone falls into is to browse its section at XDA Developers. If you have an HTC or Motorola phone, you may be able too research its unlockability on HTC or Motorola’s website. If it doesn’t support unlocking, you’ll have to use an unofficial unlocking or rooting method, which you’ll usually find on the XDA Developers forums.""
Click to expand...
Click to collapse
The trick didn't work for you because there is no security thing on marshmallow. What carrier are you on if you don't mind telling? Samsung's aren't bootloader unlocked like other phones.
-sofiann- said:
Hi everyone !
Hope I'm not making any double post but I couldn't find any explanation for this very specific situation.
After thorough research it, it seems that most of samsung devices has a secret setting called "OEM unlock" that we have to use to do the first step of rooting the device. In some cases that setting is missing but can be displayed again by some "date settings" tricks or waiting 7 days. In some other cases which seems to be mine, the "OEM unlock" setting is simply removed by probably the carrier of the phone and can't be reinstated.
In that last case which seems to be mine, I can't find any precise information wether we can or we simply can't unlock bootloader by other way and therefore root the phone.
Could anyone enlighten me ?
Thank you very much in advance !
Click to expand...
Click to collapse
The Galaxy A3 2015 (SM-A300FU) has no OEM unlock as A3 from 2015 don't even have FRP Lock, neither it has RMM state. That means there is no lock which prevents you to flash any custom binaries like TWRP recovery with Odin. You'll only lose access to knox apps/services (because of knox 0x1), rest remains the same.
SnowFuhrer said:
The trick didn't work for you because there is no security thing on marshmallow. What carrier are you on if you don't mind telling? Samsung's aren't bootloader unlocked like other phones.
Click to expand...
Click to collapse
Hi !
About my device, here are details :
Samsung A300FU
Android 6.0.1
BASEBAND VERSION : A300FUXXU1CPH3
Build number : MMB29M.A300FUXXS1CQD5
Carrier was French company called Bouygues.
About bootloader lock or not, I can see on various website that many samsung are bootloader locked but can be unlocked easily by this OEM unlock option. Sometimes it is missing. Two reasons for that : Security check that is removed after 7 days or apparently permanently removed by carrier or geographic area control.
If i'm in that last case, is there any other solution to unlock the boatloader ?Or the phone is just unrootable. It seems strange to me that some phone are just unrootable.
Thanks again !
-sofiann- said:
Hi !
About my device, here are details :
Samsung A300FU
Android 6.0.1
BASEBAND VERSION : A300FUXXU1CPH3
Build number : MMB29M.A300FUXXS1CQD5
Carrier was French company called Bouygues.
About bootloader lock or not, I can see on various website that many samsung are bootloader locked but can be unlocked easily by this OEM unlock option. Sometimes it is missing. Two reasons for that : Security check that is removed after 7 days or apparently permanently removed by carrier or geographic area control.
If i'm in that last case, is there any other solution to unlock the boatloader ?Or the phone is just unrootable. It seems strange to me that some phone are just unrootable.
Thanks again !
Click to expand...
Click to collapse
If you read @prototype74 's post it explains it quite well. I think your bootloader is already unlocked if I read right.
SnowFuhrer said:
If you read @prototype74 's post it explains it quite well. I think your bootloader is already unlocked if I read right.
Click to expand...
Click to collapse
Hi !
Thank you very much both of you for your help. Indeed there was no OEM unlock.
Many posts talking about OEM unlock existing on that A3 and the fact that I couldn't check if it was locked or not using the two methods advised (with adb or with a special code to dial up on the phone interface) led me to stop at that step to be sure before going on.
It is advises not to root a divise with a bootloader locked to avoid bricking it.
Anyway, trusting your input I did the whole process of rooting and putting a custom rom and it's all great !
Is there a reason why nobody is trying to unlock the bootloader? I mean we already have root on the AFTV 2 so it shouldn't be too hard to rewrite and re-flash the bootloader to unlock it or are there other issues i.e. a boot rom that checks the integrity of the Bootloader
...
lol, if it were that simple, it would have been done years ago.
There's people working on it in their spare time & if they figure it out, it'll be posted here.
MOD ACTION:
Thread closed at the request of the OP.