I have read around but am struggling to fully understand the significance of the OEM unlock option in developer settings and how/if it relates to FRP.
I have read this article which only goes some way to filling the gaps in my understanding. So I have a few questions and would be grateful for any answers.
1/ OEM unlock.
My understanding is that this should be enabled when the goal is to flash a custom binary (e.g. TWRP) to root the phone. Without this enabled attempting to flash a custom binary via odin will fail. Is this correct?
2/ Flashing stock FW to recover device
In the article linked to above it suggests that if you have an OTA update fail, without having OEM unlock enabled you are stuffed if you wish to recover your device by flashing stock factory fw via odin. Having followed this thread with interest regarding the flashing of stock fw it does not state that you need OEM unlock enabled (no custom binaries are being flashed). So if you are unlucky enough to have an OTA fail do you need OEM unlocked in order to flash a stock fw via odin to recover the device? Surely not???
3/ Relationship between OEM unlock and FRP
FRP requires you to enter your google password to unlock a device after a factory reset. I get this. And you can avoid this by removing your google account from the phone before executing the factory reset. So what is the relationship between OEM unlock and FRP? Is it that if you have OEM unlock enabled you can flash a custom binary (recovery and/or ROM) to then get around the FRP? I'm guessing though. I just don't understand the point. If it's my device I know my google account details so how does having OEM unlock enabled help after a factory reset.
My questions stem from the article I have linked to above which for me raises more questions than it answers. I found myself enabling OEM unlock last night "just in case" but I'm not fully sure what options I've given myself by doing this because as it stands I don't intend to root the phone.
What will happen if I relock bootloader .. because I hate the pop up "your device has been unlocked .." while it boots.. does after relocking bootloader stops twrp to work ?
dhenewar said:
What will happen if I relock bootloader .. because I hate the pop up "your device has been unlocked .." while it boots.. does after relocking bootloader stops twrp to work ?
Click to expand...
Click to collapse
If you relock your bootloader with TWRP or anything else non stock, you'll likely boot loop until you unlock again. It's likely you'll trip the verification checks -performed by a locked bootloader - with TWRP, which means you need to be fully stock for a successful locked bootloader. If you've not enabled OEM unlocking in developers options if you locked, then you'll have major issues as you can't then unlock.
If you want to, you can flash a custom logo.bin (plenty of links in the Mods section) which will hide the warning, won't shorten the delay but it'll be nicer to look at.
echo92 said:
If you relock your bootloader with TWRP or anything else non stock, you'll likely boot loop until you unlock again. It's likely you'll trip the verification checks -performed by a locked bootloader - with TWRP, which means you need to be fully stock for a successful locked bootloader. If you've not enabled OEM unlocking in developers options if you locked, then you'll have major issues as you can't then unlock.
If you want to, you can flash a custom logo.bin (plenty of links in the Mods section) which will hide the warning, won't shorten the delay but it'll be nicer to look at.
Click to expand...
Click to collapse
Ok bro thanks for the info ..will SuperSu be as same as twrp causing bootloop?... luckily I have got stock recovery n firmware .. as u said "If you've not enabled OEM unlocking in developers options if you locked, then you'll have major issues " .. I am having the problem in other device(Samsung Galaxy grand prime G531H .. Cuz of my careless n rush.i forgot to enable oem n then flashed custom rom in Odin .. then it got bricked.. searched alot in internet for solution..also .. i have created post here.. still no solution .. and Now my device is just waste ..gave up on it ... RIP :angel: ..
dhenewar said:
Ok bro thanks for the info ..will SuperSu be as same as twrp causing bootloop?... luckily I have got stock recovery n firmware .. as u said "If you've not enabled OEM unlocking in developers options if you locked, then you'll have major issues " .. I am having the problem in other device(Samsung Galaxy grand prime G531H .. Cuz of my careless n rush.i forgot to enable oem n then flashed custom rom in Odin .. then it got bricked.. searched alot in internet for solution..also .. i have created post here.. still no solution .. and Now my device is just waste ..gave up on it ... RIP :angel: ..
Click to expand...
Click to collapse
I think so, a locked bootloader, as I understand it, checks the integrity of your recovery, kernel and system, and if it detects a break in the chain of trust (e.g. if there's a custom modification that changes the signature expected), then as a security measure the device just won't boot/bootloop. SuperSU or any root, custom kernel, or TWRP or even if you've allowed TWRP to make modifications may result in bootloops thus.
Therefore, if you wish to re-lock your device, you'll want to re-flash the stock firmware and then lock. You can only lock your device with the same firmware or newer than the version your device was updated to (including OTA updates). The latest version we have is the June fastboot ROM: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 Of course, flashing this will wipe TWRP, root and possibly your data from your device, so back up and keep the backups off your device. Alternatively, you may just wish to flash the custom logo.bin as mentioned previously, which would hide the bootloader warning.
About your Galaxy Grand Prime, ouch - that's a horrible situation to be in; unless there's a potential bootloader exploit, you're caught in the nasty situation where you can't unlock your bootloader (because of the OEM unlock) and because the security's been tripped, won't allow you to boot to get to the OEM unlock Are there any Samsung service centres or repair shops that could help you recover? You could have a look around the Galaxy Grand Prime forum, see if there's anything that could help: https://forum.xda-developers.com/grand-prime
echo92 said:
I think so, a locked bootloader, as I understand it, checks the integrity of your recovery, kernel and system, and if it detects a break in the chain of trust (e.g. if there's a custom modification that changes the signature expected), then as a security measure the device just won't boot/bootloop. SuperSU or any root, custom kernel, or TWRP or even if you've allowed TWRP to make modifications may result in bootloops thus.
Therefore, if you wish to re-lock your device, you'll want to re-flash the stock firmware and then lock. You can only lock your device with the same firmware or newer than the version your device was updated to (including OTA updates). The latest version we have is the June fastboot ROM: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 Of course, flashing this will wipe TWRP, root and possibly your data from your device, so back up and keep the backups off your device. Alternatively, you may just wish to flash the custom logo.bin as mentioned previously, which would hide the bootloader warning.
About your Galaxy Grand Prime, ouch - that's a horrible situation to be in; unless there's a potential bootloader exploit, you're caught in the nasty situation where you can't unlock your bootloader (because of the OEM unlock) and because the security's been tripped, won't allow you to boot to get to the OEM unlock Are there any Samsung service centres or repair shops that could help you recover? You could have a look around the Galaxy Grand Prime forum, see if there's anything that could help: https://forum.xda-developers.com/grand-prime
Click to expand...
Click to collapse
Thanx bro I will try it out .. yep bro I got it in service center n they told me .. No way of fixing it .. Aahh n that's it ? .well there was option change of hardware price was half of the phone cost ..better to buy new one ?
since i have unlocked bootloader by official tool i can not root it and i cannot install any recovery
please help me so i can relock bootloader of my phone
i have tried maximum methods to relock bootloader of my phone but i am unsuccesful
can someone please help me so i can relock bootloader of my phone
uhm i unlocked my bootloader via official tool, and i already installed twrp and magisk
What is the process that you apply because I am facing issue.whenever I tried to install twrp recovery it says something about target report size does not reach and partition error
twrp not installing
now i am facing issue with this
unknown partition 'recoveryC:\Users\sankalp\Desktop\asus max pro m2\unlock\twrp-3.3.1-0-X01BD.img'
error: cannot determine image filename for
https://forum.xda-developers.com/max-pro-m2/development/recovery-twrp-3-2-3-x-t3885935/page10
Unlock 1st
After relock etc
Use original recovery wipe data case
Than boot to bootloder
Boot to twrp recovery
Wipe data
Install twrp
Flash rom?
https://forum.xda-developers.com/max-pro-m2/development/recovery-twrp-3-2-3-x-t3885935/page10
Unlock 1st
Flash orio file .. stock orio not pie
Hi everybody
I redid an installation of my xiaomi mi9t under miui 11.0.3 to start again on good bases because I had done a lot of trying to try to succeed in rooting it
So I relocked the bootloader and I followed the tutorial from A to Z to root the tel.
So these are the manipulations I did:
Unlock the bootloader with the miui tool
Fastboot flash recovery twrp.img
Fastboot boot twrp.img
Installation of the magisk zip.
Restart.
And then I restore my data with micloud and when I go to developer option it says that my bootloader and locked and OEM unlocking is no longer grayed out I can deactivate it when before it was not possible.
I don't know if it's the fact that I restored via micloud or that I used the xiaomi native security and cleaner app.
However my phone is well rooted and unlock bootloader because it is marked unlocked at startup and for rooting all the apps that request root rights have it.
Thank you for your answers.
Hi so I decide to root my phone today
I install magisk I patched the AP files
I load the 4 files to Odin click start, it stop at user data I got a red note says Custom binary Vbmeta blocked by oem lock
My OEM is unlocked any idea how fix it
My phone galaxy s10+ SM-G975F
I'm using the latest firmware
I attach a photo
i fix the problem bootloader was locked
What is this vbmeta package for? For flashing roms I always used the rom, magisk (if wanted root privileges), gapps (if wanted google apps package) and thats all. Why are people flashing other stuff as if it's now a essential rule? Sorry for my ignorance.