Which ROM relocks bootloader - Xiaomi Redmi Note 3 Guides, News, & Discussion

Hello,
I'm not the only facing this issue. One of the ROMs I've installed relocked my bootloader. I suspect it was Mokee, but I'm not sure. Let's make a list. Share your knowledge and/or experience.
Later edit:
In the meantime I've discovered that:
- AICP (aicp_kenzo_mm-11.0-NIGHTLY-20160819) does not relock the bootloader.
- Beanstalk does not relock the bootloader. (thanks @shinu#333)
- FireHound (FireHound-BurntAss-2.0-20160904-kenzo) does not relock the bootloader.
- HexagonROM does not relock the bootloader. (thanks @shinu#333)
- Mokee, as of MK60.1-kenzo-201608191009-NIGHTLY relocks bootloader.
- NX ROM 1.4 does not relock the bootloader. (thanks @R8LMS)
- Official CM13 (cm-13.0-20160820-SNAPSHOT-ZNH5YAO0J4-kenzo) does not relock the bootloader.
- RessurectionRemix (ResurrectionRemix-M-v5.7.3-20160820) does not relock the bootloader.
- XenonHD does not relock the bootloader. (thanks @shinu#333)
- XOSP does not relock the bootloader. (thanks @superboy123)
- ZephyrOs (ZEPHYR-OS-6.0.1-20160813-kenzo) does not relock the bootloader.

i guess any aosp and cm based rom relock the bootloader

ruhul5 said:
i guess any aosp and cm based rom relock the bootloader
Click to expand...
Click to collapse
you are absolutely wrong..
As I know, only cm13 by santhos relocks bootloader.

patelumangv said:
you are absolutely wrong..
As I know, only cm13 by santhos relocks bootloader.
Click to expand...
Click to collapse
may be ia m wrong but i faced bootloader relocked in hexagon rom also

paul_damian said:
Hello,
I'm not the only facing this issue. One of the ROMs I've installed relocked my bootloader. I suspect it was Mokee, but I'm not sure. Let's make a list. Share your knowledge and/or experience.
In the meantime I've discovered that Mokee, as of MK60.1-kenzo-201608191009-NIGHTLY relocks bootloader.
Click to expand...
Click to collapse
Every ROM based on Android M bootloader will relock the bootloader (e.g. Unofficial CM by Santosh sir and the ROM based on unofficial CM).
The ROM based on Android lollipop bootloader will not relock the bootloader.

I don't know if it is so. Just tested CM13 20160820-SNAPSHOT, and my bootloader is still unlocked.

Only rom based on Santosh's sources relocks bootloader.Like his cm13,mokee ecc...

Tell which one you have tested yourself and got a locked bootloader and I will update my first post.

I am trying to do the same thing man.i also have a post about this but nothing much happening so ill just say what roms i have tested and not lock boot loader
XenonHD
HexagonROM
Beanstalk
Cm13 nightly official.
These all dont lock it and tested by me

Thanks, I update my first post with your experience

Does Xosp relock bootloader ?

XOSP wont lock bootloader.

Every rom that change firmware will relock bootloader, if you flash cm13 over miui relock
If you flash miui based on mm relock.
If you flash miui over cm13 probably relock.
But it's not a full relock since twrp will still be there (exept for fastboot / edl flashed roms), and let you flash any rom without locking the phone

NX ROM 1.4 (AOSP) will not relock the bootloader.
It's almost perfect. Just a few bugs to be squashed, but I could imagine using this as a daily driver for a looooong time, or until 7.0 development is really stable.

Thanks for the info, OP updated.

Related

[Q] Nexus 4 unlocking bootloader

Hello, i have new Nexus 4 and i have some questions about unlocking bootloader (please, do not send me FAQ themes, they are useless):
1. is warranty restored by relocking bootloader? (On my old xperia no because of removed DRM keys)
2. can i use AOSP based roms with stock kernel without unlocking bootloader?
3. unlocked bootloader is disabling security features like secure boot or SElinux?
MichalkoOo said:
Hello, i have new Nexus 4 and i have some questions about unlocking bootloader (please, do not send me FAQ themes, they are useless):
1. is warranty restored by relocking bootloader? (On my old xperia no because of removed DRM keys)
2. can i use AOSP based roms with stock kernel without unlocking bootloader?
3. unlocked bootloader is disabling security features like secure boot or SElinux?
Click to expand...
Click to collapse
1. Yes, u own a nexus nothing to worry about as long as u return to stock img and relocked bootloader ive warranty several nexus devices the years (they usually just give u new one )
2. No, they will casue major screen tearing or wont boot,if u want 100% guaranteed stock kernel (aosp version) u can pull boot. Img from RASBEANJELLY rom by rascarlo , he is always up to date with aosp and uses stock kernels in his roms (legit dev)
3. Theres always a security risk when unlocking or rooting i don't no exact answer to that question
Thank you, is 1.8GHz safe? Or what is max safe OC with what voltage?

Flash BETA( Developer) ROM [SD] without unlocking BL

Latest beta MIUI block flashing over stable for unknown reason. No need to unlock BL. just flash this version of beta ROM http://bigota.d.miui.com/7.2.16/miui_HMNote4XGlobal_7.2.16_e6eed016d8_6.0.zip
Then flash latest to get latest ROM.
**I am not responsible for damage of your phone. Do at your own risk.
PS: tested on stable 8.1.x. So if you can not flash over your latest stable version make sure you downgrade to 8.1.x

Official MIUI9 via Recovery?

Hey guys ! Maybe Us, the (proudly) Redmi 3S owners get soon the MIUI9 updated, but I have a question... Could us that we have Unlocked bootloader / Custom Recovery /Root just to flash .Zip packet like any official Rom? Or We must to flash it via Mi Flasher or OTA update? Because I prefer stay on MM MIUI8 With Unlocked Bootloader, Root and Custom Recovery...
kukuteku said:
Hey guys ! Maybe Us, the (proudly) Redmi 3S owners get soon the MIUI9 updated, but I have a question... Could us that we have Unlocked bootloader / Custom Recovery /Root just to flash .Zip packet like any official Rom? Or We must to flash it via Mi Flasher or OTA update? Because I prefer stay on MM MIUI8 With Unlocked Bootloader, Root and Custom Recovery...
Click to expand...
Click to collapse
We can flash MIUI 9 update from both the TWRP and the stock recovery (if you're on it), so there's nothing to worry about. Even I have an unlocked bootloader and have flashed custom ROMs as well as MIUI using TWRP without any problems.
psychopac said:
We can flash MIUI 9 update from both the TWRP and the stock recovery (if you're on it), so there's nothing to worry about. Even I have an unlocked bootloader and have flashed custom ROMs as well as MIUI using TWRP without any problems.
Click to expand...
Click to collapse
I have TWRP too, and also I flashed MIUI. I thought that MIUI9 could bring "New core" etc, We must to Flash it via stock/MI flash.... So I dont fear any more , waiting for MIUI9 for Redmi 3S :fingers-crossed:
Thank You!

Bootloader

how to install mm bootloader or lp bootloader on j500m via twrp?
obs: I want to install rom miui 9 multipro or pro global.
Who can help me already thank you?
killernightdark said:
how to install mm bootloader or lp bootloader on j500m via twrp?
obs: I want to install rom miui 9 multipro or pro global.
Who can help me already thank you?
Click to expand...
Click to collapse
You can't you must do it from a computer using odin. Follow the steps on this page https://forum.xda-developers.com/ga...5-1-1-bootloader-modem-j500xx-t3566801/page14
garylawwd said:
You can't you must do it from a computer using odin. Follow the steps on this page https://forum.xda-developers.com/ga...5-1-1-bootloader-modem-j500xx-t3566801/page14
Click to expand...
Click to collapse
but I'm using the 15.1 lineage so I'm wondering how to install the lp or mm bootloader You need them to install one of these two rom miui9
killernightdark said:
but I'm using the 15.1 lineage so I'm wondering how to install the lp or mm bootloader You need them to install one of these two rom miui9
Click to expand...
Click to collapse
If your using los15.1 then you already have mm bootloader and modem as it doesn't work with lp.
There are only 2 bootloaders for j5 2015 lp and mm. Even if the ROM is nougat or Oreo you will still have either lp or mm bootloader.
If you want to change bootloader the only way is from my last post.
You can only change it using Odin on the computer.
But right now you definitely have mm bootloader installed

Want some guidence and having some questions about custom rom.

I have moto g4 plus (2016) and want to install custom rom but I have some questions and without knowing about them i can't take the risk.so please answer sir.
1) There is 2 Twrp custom recovery one is 32 bit and second is 64 bit, so which is best ?
2) if I use 32 bit and flash 64 bit rom ,can it possible?
3) if No then if am use 64 bit Twrp and flash 32 bit rom accidentally ,can it will brick my device??
4) i am currently on stock rom android 7.0 , today most custom rom is based on 9.0 ,if I flash pie custom rom and after months i want revert back to stock or Oreo rom ,can i will do it? Because in some custom rom there is note that after flashing this rom you can not revert back lower version of rom.
5) where is rom take space if I flash it, means in ram ,internal storage???
Thanks in advance.i know this question is help for other noob:good:
keval3492 said:
I have moto g4 plus (2016) and want to install custom rom but I have some questions and without knowing about them i can't take the risk.so please answer sir.
1) There is 2 Twrp custom recovery one is 32 bit and second is 64 bit, so which is best ?
2) if I use 32 bit and flash 64 bit rom ,can it possible?
3) if No then if am use 64 bit Twrp and flash 32 bit rom accidentally ,can it will brick my device??
4) i am currently on stock rom android 7.0 , today most custom rom is based on 9.0 ,if I flash pie custom rom and after months i want revert back to stock or Oreo rom ,can i will do it? Because in some custom rom there is note that after flashing this rom you can not revert back lower version of rom.
5) where is rom take space if I flash it, means in ram ,internal storage???
Thanks in advance.i know this question is help for other noob:good:
Click to expand...
Click to collapse
64bit recoveries can handle 32bit roms too. Use a 64bit recovery and everything is fine.
You cannot downgrade your bootloader from stock Oreo to stock nougat(your current Rom). Custom roms won't flash bootloaders,only stock roms.
Your whole flash storage of your device is divided into several partitions like system, data, boot, recovery, internal storage. That's why you have to deal with less memory in your internal storage(10 out of 16 for example).
You cannot(yeah, but don't do it) modify the partition size cause it's used to met some requirements.
The rom will be flashed into system/data partition, not internal storage but also uses ram of course
Thanks man , but can you elaborate my question on if I flash today custom rom on pie base and that is rumor on moto g4 plus that oreo update will launch soon and I also wait for it.so can i get that update if I am on pie custom rom.sorry for your answer ,i not understand that .
keval3492 said:
Thanks man , but can you elaborate my question on if I flash today custom rom on pie base and that is rumor on moto g4 plus that oreo update will launch soon and I also wait for it.so can i get that update if I am on pie custom rom.sorry for your answer ,i not understand that .
Click to expand...
Click to collapse
Yes you can get official Oreo update if you are on Pie custom rom. You just need to go back to stock rom or flash the stock Oreo rom manually like the soak test.
Can you give me Twrp 64 bit link and also which custom rom do you prefer on gaming performance , battery performance and customisable wise? Thanks a lot...
keval3492 said:
Can you give me Twrp 64 bit link and also which custom rom do you prefer on gaming performance , battery performance and customisable wise? Thanks a lot...
Click to expand...
Click to collapse
Here's a link for the 64 bit TWRP https://forum.xda-developers.com/mo...recovery-twrp-3-2-1-unofficial-touch-t3722206 for flashing both 32 bit and 64 bit custom ROMs and TWRP flashables.
Of course, unlocking your bootloader and flashing a custom ROM via TWRP will unavoidably erase your device, so back up as necessary. Be also aware that flashing a custom ROM may necessitate flashing magisk as well, to get your device Google certified again.
As for a particular ROM, your best bet is to have a look at each custom ROM's page and particularly the first page and the last few pages. Both of those should give you information on how suitable the ROM is from other user's reports for your usage and also give you an idea how often the ROM is updated.
It is necessary for flashing magisk? Because magisk root my mobile and I don't want to do it right now.
keval3492 said:
It is necessary for flashing magisk? Because magisk root my mobile and I don't want to do it right now.
Click to expand...
Click to collapse
For some apps, like banking apps for example, these apps may not function properly if they detect an unlocked bootloader, or if your device does not pass Google Play Store certification. If you're wanting to flash a custom ROM or a TWRP flashable, then you may have to consider flashing magisk for magisk hide. Magisk hide helps to hide your unlocked bootloader status and thus may get your device certified to use these apps. Up to you - depends on if you use apps that won't work if they detect your device has an unlocked bootloader.
Thanks sir for get me guide .What is athens when I open xda moto g4 plus and what is kernel and how it is important ??
keval3492 said:
Thanks sir for get me guide .What is athens when I open xda moto g4 plus and what is kernel and how it is important ??
Click to expand...
Click to collapse
I'm guessing by Athens you mean athene? If so, athene is the device codename for the Moto G4/plus (2016). Custom ROMs and software designed for athene should work on our services, though please check the release dates of such software. That also means software built for another device codename may not work.
A kernel is part of the software communicating between the hardware and the software. Custom ROMs will come with one usually. If you choose to flash another kernel, ensure you flash the correct type of kernel - there are kernels for stock 7.0/6.0 (Motorola), 7.1 (custom) and kernels for custom 8.1/9.0 ROMs. These may not be cross compatible and as such if you flash the incorrect kernel to your device your device may fail to boot (buy then that's what TWRP backups are for). Due to the lack of source code for stock 8.1, I've not seen custom kernels built for the stock Motorola 8.1 stock ROM yet.
Thank you sir for guide me about athene and kernel ,so i choose custom rom only made for athene and kernel is also built in with custom rom.
I am on stock oreo on moto g4 plus ,it is same process in oreo for unlock bootloader??
keval3492 said:
I am on stock oreo on moto g4 plus ,it is same process in oreo for unlock bootloader??
Click to expand...
Click to collapse
Please search within the correct rom thread https://forum.xda-developers.com/mo...4-oreo-soak-test-update-t3871136/post78966322
I did not get proper answer from link you send ,please help for this..
keval3492 said:
I did not get proper answer from link you send ,please help for this..
Click to expand...
Click to collapse
Should be the same process to unlock your bootloader, provided your motherboard is the same and you've still got your IMEI and software channel.
Can you elaborate what you said about motherboard and IMEI ,i am getting that method is same as nought but after that line i don't understand.
keval3492 said:
Can you elaborate what you said about motherboard and IMEI ,i am getting that method is same as nought but after that line i don't understand.
Click to expand...
Click to collapse
When you unlock your bootloader, you need the unlock key. The unlock key is likely generated from and linked to your motherboard; if your motherboard had been changed, then you'd have to get a new unlock key.
If your IMEI is still present in your device and working, the unlock key should work. Some users with existing IMEI issues may not be able to unlock their bootloaders.
Basically, if your device is the same when you requested the unlock key, and everything is working okay, then unlocking should be the same as Nougat without any further steps. Back up, boot to fastboot and connect your device to your computer, then enter the unlock key command - with your key - on your computer in the minimal ADB terminal.
I changed my motherboard once and after that I unlock my bootloader also ,but I brick my device by installing 64 bit rom on 32 bit twrp version and after that I lock my bootloader and start as a fresh device till now.
Same key is still working for me as I want unlock my bootloader??
keval3492 said:
I changed my motherboard once and after that I unlock my bootloader also ,but I brick my device by installing 64 bit rom on 32 bit twrp version and after that I lock my bootloader and start as a fresh device till now.
Same key is still working for me as I want unlock my bootloader??
Click to expand...
Click to collapse
Should be - use the same key as you used to unlock your bootloader before (after you had your motherboard changed). Be aware you will not be able to re-lock your bootloader if you unlock your bootloader at the moment. We do not have the Oreo firmware to lock stock Oreo devices or devices previously updated to stock Oreo firmware.
Oreo firmware means coding in CMD ??

Categories

Resources