Database Develop

LOCK Oneplus 5 Bootloader (GUIDE)

Hi guys, if you are like me trying to lock the bootloader to get Android Pay, or Netflix back up and running without much fuss, I found a way to lock the bootloader.
WARNING: This will do a factory reset to your device, so do backups...
Requires:
- Official OOS flashed (Download here the full zip file for the latest OOS, you can flash through TWRP or stock Recovery)
- Latest Fastboot drivers and SDK file
- Basic knowledge of Fastboot commands
Guide:
- Boot the device into Bootloader mode (power the device with Volume up + Power Button)
- Connect to the PC
- Run the command "fastboot flashing lock"
- On the device, using the volume keys select "Yes" to lock the bootoader
And that's it, the 1st boot will take longer, but just wait.
Hope this helps =)

@hugoprh
It should be
Code:
fastboot oem lock
instead of
Code:
fastboot flashing lock
as OnePlus still uses the older LK. Only Nexus 6P & Pixel/Pixel XL have updated LK that includes these changes.
You should also mention that this procedures factory resets the device i.e. the internal memory is wiped.

Titokhan said:
@hugoprh
It should be
Code:
fastboot oem lock
instead of
Code:
fastboot flashing lock
as OnePlus still uses the older LK. Only Nexus 6P & Pixel/Pixel XL have updated LK that includes these changes.
You should also mention that this procedures factory resets the device i.e. the internal memory is wiped.
Click to expand...
Click to collapse
Hi, thanks for your feedback, but I did try "fastboot oem lock", as other XDA Oneplus 5 users have tried as well, without success, so I tried the Nexus 6p way "fastboot flashing lock" and it worked and this is the reason I decided to make this guide and I did write a "WARNING" about this procedure doing a factory reset, it's written in bold and underlined, please read carefully.

hugoprh said:
Hi, thanks for your feedback, but I did try "fastboot oem lock", as other XDA Oneplus 5 users have tried as well, without success, so I tried the Nexus 6p way "fastboot flashing lock" and it worked and this is the reason I decided to make this guide and I did write a "WARNING" about this procedure doing a factory reset, it's written in bold and underlined, please read carefully.
Click to expand...
Click to collapse
Let me explore the firmware - it would a curious case of hybridization then.
Regarding the warning: Yah, my bad... missed it somehow.

Trying to relock my bootloader, everytime I get to the fastboot screen I scroll through to "START" and select it using the power button the phone shuts off and reboots. Having a hard time getting into fastboot. any suggestions?

rgreene1971 said:
Trying to relock my bootloader, everytime I get to the fastboot screen I scroll through to "START" and select it using the power button the phone shuts off and reboots. Having a hard time getting into fastboot. any suggestions?
Click to expand...
Click to collapse
I was able to figure out my fastboot issues and able to flash twrp and revert back to a stock image, however when I try to lock the boot loader i get the error "FAILED (remote: flashing lock is not allowed).
Any ideas on the direction I need to go?

rgreene1971 said:
I was able to figure out my fastboot issues and able to flash twrp and revert back to a stock image, however when I try to lock the boot loader i get the error "FAILED (remote: flashing lock is not allowed).
Any ideas on the direction I need to go?
Click to expand...
Click to collapse
+1

rgreene1971 said:
I was able to figure out my fastboot issues and able to flash twrp and revert back to a stock image, however when I try to lock the boot loader i get the error "FAILED (remote: flashing lock is not allowed).
Any ideas on the direction I need to go?
Click to expand...
Click to collapse
You need to turn on OEM Unlocking in Developer Settings. If for any reason OEM Unlocking is freezed, flash Magisk and then turn on OEM Unlocking. Flash the stock recovery and the lock bootloader command. It should work flawless!
Don't forget the backup!

Why lock? Why not just use Magisk? That works fine with Android Pay.

You don't need to lock your bootloader to use Netflix

nagorimayank said:
You need to turn on OEM Unlocking in Developer Settings. If for any reason OEM Unlocking is freezed, flash Magisk and then turn on OEM Unlocking. Flash the stock recovery and the lock bootloader command. It should work flawless!
Don't forget the backup!
Click to expand...
Click to collapse
I am getting the same error saying that Flashing Lock is not allowed.I did what you said to do but the i can't turn on the OEM Unlocking in Developer Settings since it is greyed out.
What should i do?

mullafabz said:
I am getting the same error saying that Flashing Lock is not allowed.I did what you said to do but the i can't turn on the OEM Unlocking in Developer Settings since it is greyed out.
What should i do?
Click to expand...
Click to collapse
What I did was install custom ROM, the option isn't greyed out. Then try again. But make sure you install stock ROM and recovery before bootloader lock.

beache said:
What I did was install custom ROM, the option isn't greyed out. Then try again. But make sure you install stock ROM and recovery before bootloader lock.
Click to expand...
Click to collapse
I managed to lock back the bootloader but now am stuck in an bootloop.

mullafabz said:
I managed to lock back the bootloader but now am stuck in an bootloop.
Click to expand...
Click to collapse
You have to format data in recovery

mi8 Locked Bootloader with TWRP installed. help to flash the official rom

Guys, my mi8 was unlocked while buying this. It was on miui9. I updated to miui10 via updater app. Today i've installed TWRP & rooted it. and formatted the data>flash disable dm verity to stop the encryption. Everything was ok but when i went to the settings i see the device is again locked. So i tried to unlock it but Mitool says "device already unlocked, no need to repeat unlock" and not letting me to unlock. Again i see the device is still encrypted. What can i do now to get everything okay? Because now i have a device with locked bootloader and TWRP installed. please help me

sajib1403 said:
Guys, my mi8 was unlocked while buying this. It was on miui9. I updated to miui10 via updater app. Today i've installed TWRP & rooted it. and formatted the data>flash disable dm verity to stop the encryption. Everything was ok but when i went to the settings i see the device is again locked. So i tried to unlock it but Mitool says "device already unlocked, no need to repeat unlock" and not letting me to unlock. Again i see the device is still encrypted. What can i do now to get everything okay? Because now i have a device with locked bootloader and TWRP installed. please help me
Click to expand...
Click to collapse
Boot into fastboot mode, connect to your computer, then use command fastboot oem device-info on your computer.
Device unlocked: (does it show locked or unlocked here)

New Xiaomi A2 global bricked???

I was trying to install Camera2 on it. Unlocked it with developer options ->Unlock OEM
After try some things I reset factory the cellphone and decide to forget camera2 things...
So I went to developer options and LOCKED OEM.
After that I reboot in fastboot mode and did fastboot oem lock
Now the cellphone is locked in a bootloop saying that my deveice loaded a differente operational system and a screen to visit miui.com/unlock.
The unlock aplication doesn't work. Says that I can't unlock the device.
So that means I lost my crazy brand new phone? THere's any solution? The Test Point solution will work? Is that the only solution???
Thiank you for any response.

foxdanger said:
I was trying to install Camera2 on it. Unlocked it with developer options ->Unlock OEM
After try some things I reset factory the cellphone and decide to forget camera2 things...
So I went to developer options and LOCKED OEM.
After that I reboot in fastboot mode and did fastboot oem lock
Now the cellphone is locked in a bootloop saying that my deveice loaded a differente operational system and a screen to visit miui.com/unlock.
The unlock aplication doesn't work. Says that I can't unlock the device.
So that means I lost my crazy brand new phone? THere's any solution? The Test Point solution will work? Is that the only solution???
Thiank you for any response.
Click to expand...
Click to collapse
"So I went to developer option and LOCKED OEM" can you be a little more clear. Because unlocking the bootloader locks the OEM unlock option in the developer settings.
Possible cause of your bootloop is the change in your build.prop file.
I did a similar mistake as well. My phone was stuck in a bootloop. My mistake was that I installed Magisk and forgot to uninstall it through the Magisk manager before locking the bootloader and so the system were not in their stock state.
What I did was, I just booted my phone into fastboot.
Unlocked the bootloader again by using "fastboot OEM unlock". Went into fastboot again. Checked the current active slot by "fastboot getvar current-slot" and flashed the stock boot image from the stock pie rom found on Mi website.

Njaiker said:
"So I went to developer option and LOCKED OEM" can you be a little more clear. Because unlocking the bootloader locks the OEM unlock option in the developer settings.
Possible cause of your bootloop is the change in your build.prop file.
I did a similar mistake as well. My phone was stuck in a bootloop. My mistake was that I installed Magisk and forgot to uninstall it through the Magisk manager before locking the bootloader and so the system were not in their stock state.
What I did was, I just booted my phone into fastboot.
Unlocked the bootloader again by using "fastboot OEM unlock". Went into fastboot again. Checked the current active slot by "fastboot getvar current-slot" and flashed the stock boot image from the stock pie rom found on Mi website.
Click to expand...
Click to collapse
What I did was with the phone working I entered on configuration, developer, and turned of the oem lock option.
Than I reboot in fastboot and did fastboot oem lock.
This made the cellphone unbootable. Bootloop saying that I'm trying to start a different operational system.
And I can't make fastboot unlock because I turned off the option in the system, so I can't send fastboot commands like oem edl, unlock, unlock-critical and etc...
I can't do nothing :/

I don't know how the option was working, but was... I know it should be locked, but this time wasn't. Was after I factory reset the cellphone

Your fault that you locked bootloader on a modified system. Do a research next time

RMM state: prenormal after OEM unlock on Android 9.0

Hello!
Got a strange situation: set up new Note9, updated it to Pie, connected to Wi-Fi and did OEM unlock instantly rebooting to Odin mode to flash TWRP, but instead of this I got RMM state: prenormal message (should be RMM state: checking in Pie) and KG state : checking. Booted back in OS, set it up and see OEM unlock active in Development options. Unlocked lots of samsung devices - but they are all always got me RMM checking and let flash TWRP instantly in PIE. Is this some new security feature or its because I updated to PIE from Oreo and still have to wait 7 days for unlock?

+1 waitting

Narkozzz said:
Hello!
Got a strange situation: set up new Note9, updated it to Pie, connected to Wi-Fi and did OEM unlock instantly rebooting to Odin mode to flash TWRP, but instead of this I got RMM state: prenormal message (should be RMM state: checking in Pie) and KG state : checking. Booted back in OS, set it up and see OEM unlock active in Development options. Unlocked lots of samsung devices - but they are all always got me RMM checking and let flash TWRP instantly in PIE. Is this some new security feature or its because I updated to PIE from Oreo and still have to wait 7 days for unlock?
Click to expand...
Click to collapse
the waiting periode is not the issue. if oem unlock is there then no wait was needed.
the real problem was not reading the guides section attentively. check for dr.ketans guide and follow it through.
you should be using method 1 in the guide.
and again follow it from a to z.
now flash back stock firmware and start the procedure again.

bober10113 said:
the waiting periode is not the issue. if oem unlock is there then no wait was needed.
the real problem was not reading the guides section attentively. check for dr.ketans guide and follow it through.
you should be using method 1 in the guide.
and again follow it from a to z.
now flash back stock firmware and start the procedure again.
Click to expand...
Click to collapse
The problem is RMM prenormal state even after clean flash of stock rom and oem unlock enabled. I cant flash anything non-signed. With all respect to dr.ketan I have mine experience that never failed before - RMM checking always appear after unlock on Pie. So I asking people who could have same issue - will it change from prenormal to checking in 7 days or I better flash Oreo and wait 168 hours?

Narkozzz said:
The problem is RMM prenormal state even after clean flash of stock rom and oem unlock enabled. I cant flash anything non-signed. With all respect to dr.ketan I have mine experience that never failed before - RMM checking always appear after unlock on Pie. So I asking people who could have same issue - will it change from prenormal to checking in 7 days or I better flash Oreo and wait 168 hours?
Click to expand...
Click to collapse
fine dont read and follow the guide to flash his root oem fix root v5
sheesh
here are some more details since you are new to note 9.
here an other zip that does partially what ketans does:
https://1drv.ms/u/s!AhXVLDDj8g3AgrxVEeICKZil9BIAUA?e=kpfiM9
it has no kernel nor magisk.
ketan has a kernel and magisk AND rmm state fix that should make device be able to boot while on custom recovery as the kernel needs to be patched in order to boot.

bober10113 said:
the waiting periode is not the issue. if oem unlock is there then no wait was needed.
the real problem was not reading the guides section attentively. check for dr.ketans guide and follow it through.
you should be using method 1 in the guide.
and again follow it from a to z.
now flash back stock firmware and start the procedure again.
Click to expand...
Click to collapse
bober10113 said:
fine dont read and follow the guide to flash his root oem fix root v5
sheesh
here are some more details since you are new to note 9.
here an other zip that does partially what ketans does:
https://1drv.ms/u/s!AhXVLDDj8g3AgrxVEeICKZil9BIAUA?e=kpfiM9
it has no kernel nor magisk.
ketan has a kernel and magisk AND rmm state fix that should make device be able to boot while on custom recovery as the kernel needs to be patched in order to boot.
Click to expand...
Click to collapse
Thank you for trying to help me, friend. But you misses the core thing - to flash anything mentioned in dr.ketan's guide I have to flash TWRP first. But I cant flash TWRP since I have RMM state prenormal mode alongside with unlocked bootloader. Even after reflash of stock rom. So the only question in my situation is: will RMM state change after 168 hours wait on Pie, or I need to flash Oreo rom first and wait. I am not new neither to Note9 unlocking, not to Samsung devices and have all needed tools to fix OEM and RMM issue AFTER I will get a chance to flash TWRP.

Narkozzz said:
Thank you for trying to help me, friend. But you misses the core thing - to flash anything mentioned in dr.ketan's guide I have to flash TWRP first. But I cant flash TWRP since I have RMM state prenormal mode alongside with unlocked bootloader. Even after reflash of stock rom. So the only question in my situation is: will RMM state change after 168 hours wait on Pie, or I need to flash Oreo rom first and wait. I am not new neither to Note9 unlocking, not to Samsung devices and have all needed tools to fix OEM and RMM issue AFTER I will get a chance to flash TWRP.
Click to expand...
Click to collapse
flash stock. boot to home screen make it check for updates in the software menu once. check dev tool if OEM unlock is there. if it is a unlocked flash twrp. and boot directly to recovery after odin finishes. in recovery format data in wipe menu and type yes. go to reboot menu and choose reboot to recovery. flash ketans oem root fix v5 in aroma setup choose to flash kernel and magisk.
ive had your issue before. its not complicated. just do what i said if your oem unlock is there and unlocked. if its vanished and want it to appear then there are guides to make it appear instead of waiting.
also do you want oreo or pie? ketan has both. just read..

You are not listening: I flashed stock; I connected to WiFi; I do see OEM unlock enabled in Development Options; Still I have RMM state prenormal in Odin mode and cant flash TWRP.

Narkozzz said:
You are not listening: I flashed stock; I connected to WiFi; I do see OEM unlock enabled in Development Options; Still I have RMM state prenormal in Odin mode and cant flash TWRP.
Click to expand...
Click to collapse
well if you dont try as i said of course youll never know.
again, i had your issue and alot of people as well. please use xda search feature and read. if not then dont post for help if you dont want help.

Narkozzz said:
You are not listening: I flashed stock; I connected to WiFi; I do see OEM unlock enabled in Development Options; Still I have RMM state prenormal in Odin mode and cant flash TWRP.
Click to expand...
Click to collapse
I also have the problem, but with the S10.
OEM activation active, even reactivated in download mode, so OEM activation is gray. Even the trick with the 8 days did not help - it remains prenormal.

bober10113 said:
the waiting periode is not the issue. if oem unlock is there then no wait was needed.
you should be using method 1 in the guide.
Click to expand...
Click to collapse
Hello, do you have a link for the manual?
Have been looking for a long time and geffen nothing.
Maybe I will continue with the instructions to get the "prenormal" away

bininga59 said:
Hello, do you have a link for the manual?
Have been looking for a long time and geffen nothing.
Maybe I will continue with the instructions to get the "prenormal" away
Click to expand...
Click to collapse
https://forum.xda-developers.com/galaxy-note-9/how-to/root-note-9-n960f-fd-experimental-t3832143

I am in the same situation, the rmm state prenormal still continues
even when I have the OEM unlocked, in fact I tried to do it through the chimera
program, but for having the June android security patch (CSF2)
the chimera friends commented to me that for that reason I could not do the
unlocking of rmm through their program, they told me that they worked on a
solution for it, but they did not give me an estimate of time, I guess we will
have to wait for a solution from them, since searching and reading most of the post,
none worked for me, I'm stuck in not being able to flash TRWP, so I can't really do anything.
I hope someone finds a solution or that through the chimera program, we can correct that problem.

I'm facing same problem on sm-a730f, the rmm state prenormal still active
even when I have the OEM unlocked

Same problem here, i'm using a brazilian Samsung galaxy Note 9 N9600 retail version

Same situation here i have galaxy s9 exynos

RMM state prenormal fix for non-US phones
@bober10113 et al, specially non-US folks
I guess these guys are suffering the same as me, it is exactly like what @Narkozzz said. RMM state prenormal (even with OEM already unlocked!!!) won't allow for flashing one single thing other than official binaries e.g. TWRP without which we can do nothing (the fixes are only prevention, not remedying).
Skimming through Samsung international forums abroad and other websites I saw the solution consists in installing the SIM card, flashing stock with Odin again, and then keeping the cellphone, the simcard and the mobile data turned on constantly. Eventually after 7 days, on in some cases more than a month, that state will reset back and we will then be able to flash TWRP and the RMM bypass, plus noverity etc. etc.
Ketan also mentioned that in the comments in his topic, although he did not mention specifically about keeping the simcard together with mobile data enabled during all the time
I'm about to flash mine now and wait with everything enabled, following that solution.
Will report back in here after a while
Cheers!

active usb debugging and active oem, the same happens in note 9, waiting for your experience

For what it's worth, I'm going to share what I've done; since it seems like I've somehow just stumbled through the same issue on my note 9, without having to wait any substantial amount of time. Hopefully it's of some use to someone.
I originally had N960FXXU3CSF9 (rooted with TWRP installed) on my Exynos Note 9; flashed stock N960FXXS3CSG5 using Odin, got about half way through the new device setting up process then black screen with "Only official released binaries are allowed to be flashed" message.
Me rambling about my fails
After the initial 30 minutes of panic and swearing, got the phone to download mode (Volume Down + Bixby, plug in USB from PC), then various combinations of trying to flash the same stock N960FXXS3CSG5 rom, TWRP, trying to install no-verity-opt-encrypt and Magisk-v18.0. The only change I noticed was RMM state sometimes seems to be stuck on "checking" instead of "Prenormal" while in download mode sometimes; either way, all ends with the same "Only official released binaries are allowed to be flashed" brick.
Last ditch attempt that worked for me:
(from RMM msg brick)
- Volume Down + Bixby, plug in USB from PC to Download mode
- Flashed the old N960FXXU3CSF9 stock rom with Odin;
- Turned phone off after 1st reboot after ^;
- Volume Down + Bixby, plug in USB from PC to Download mode
- Flashed twrp-3.2.3-0-crownlte_UNOFFICIAL.tar.md5
- Held down Volume Up + Bixby + Power before reboot from ^, to boot straight to TWRP recovery
- Transferred N960F_DS_N_PIE_Root_for_OEM_issue_devices_V5.zip & Magisk-v18.0.zip from PC to external SD card
- From TWRP, Wipe - Format Data - "yes"; after format is done, press back to first TWRP page
- Install N960F_DS_N_PIE_Root_for_OEM_issue_devices_V5.zip
- Install Magisk-v18.0.zip
- Wipe Dalvik Cache
- Reboot to System
More rambling
it then took a few minutes with boot img before "optimizing apps" (I assume this is code for Samsung black magic and murdering imaginary orphans?) then eventually I got to enter my details through the new device set up process... for the 10th time today. So far it's been about 6hrs since I've put all my apps back, in developer options OEM unlocking is off, but
I have root access back, and everything seems to be fine.
Sorry that I kept jumping between tenses and waffled on a bit there; it's been a long 20 hrs of reading forums, articles, hand cramps death gripping phone buttons and bashing head against desks. Hope this is useful to someone, I'm off to find 2 tin cans and some string.

Need help for n9... Prenormal

How To Guide PSA: Fix for "Device Corrupted" when trying to relock bootloader.

plempereur said:
A few notes on my experience with this tablet : I got it with the global rom and I wished to flash the stock rom and re-lock the tablet after to restore it in the original factory state :
- Flashed the CN rom using this guide, it went fine. I used "adb oem edl" to enter EDL mode as the mehod with the buttons did not work for me
- Re locked using "fastboot flashing lock" from the bootloader menu (vol+up), not the fastboot menu. (this driver was needed to "see" the tablet with fastboot)
- The tablet was bricked (refused to boot after re-locking / some error messsage like "system corrupted / unable to boot" then after this it just kept going to the bootloader when turning on)
- Unlocked the bootloader using "fastboot oem unlock-go"
- Managed to flash again from EDL, to enter EDL again (took me a bit of time to figure this) I had to use "fastboot oem reboot-edl" from the bootloader
- Starting over I did all the OTA updates up to ZUI14 "14.0.255 ST" (I received the updates even if the tablet bootloader is unlocked), then did a "Factory data reset" from the settings menu.
- After this I attempted to lock again and... it worked. Not 100% sure if it's due to the Z14 OTA, the factory reset or both (I suspect the OTA).
(I am keeping the "OEM unlocking" (allows the unlocking of the bootloader) option enabled in the developper options just in case I need to re-flash for some reason in the future)
Hope this can help others,
Cheers
Click to expand...
Click to collapse
Reposting this guide from @plempereur as it deserves prominent attention.

OMGrant said:
Reposting this guide from @plempereur as it deserves prominent attention.
Click to expand...
Click to collapse
I used this guide mentioned in that post, but this post helped me solve some issues I had. We need a sticky with links to all the posts in that one long thread because there's so much information in there and its buried.