If you're already on MM bootloader, I don't think you need to. I've already flashed some ROMs that needs MM bootloader and haven't faced any problems.TheStrix posted this warning on his LOS thread: https://forum.xda-developers.com/showpost.php?p=72211918&postcount=6004
I was just wondering, are people that followed this guide to flash LOS with locked bootloader good to go, or do we need to revert back to stock MIUI and unlock officially?
Don't know what bootloader I am on. If following this guide (or relocking my bootloader) didn't change version, I guess I am still on LP. Flashed latest AOSIP without problem though, not sure if mm is needed for that rom.If you're already on MM bootloader, I don't think you need to. I've already flashed some ROMs that needs MM bootloader and haven't faced any problems.
If you go through what strix explained there, I wonder then if we are still on 6.11.3 fw, which I don't know is LP based or MM basedIf you're already on MM bootloader, I don't think you need to. I've already flashed some ROMs that needs MM bootloader and haven't faced any problems.
I am on Kate. As Kate ships MM out of the box, it should be on MM bootloader(?).Don't know what bootloader I am on. If following this guide (or relocking my bootloader) didn't change version, I guess I am still on LP. Flashed latest AOSIP without problem though, not sure if mm is needed for that rom.
Update: Replacing LP bootloader with the MM one won't work. TWRP would still not boot.Will the new roms that require MM bootloader, like the new Lineage, break this method? Do we need to do anything differently? Maybe also replace "emmc_appsboot.mbn" with the MM one circulating in Lineage 14 thread instead of only replacing "recovery.img"?
We are on LP "bootloader" not firmware. If you've flashed any subsequent FW then obviously you're on that FW(7.5.4, etc.)If you go through what strix explained there, I wonder then if we are still on 6.11.3 fw, which I don't know is LP based or MM based
And the thing is if something goes terribly wrong since on a locked bootloader, cannot use fastboot command to repair the damage ?
Thank you for testing this, at least now we know we need to get back on latest miui global dev. I'm going for official unlock.I am on Kate. As Kate ships MM out of the box, it should be on MM bootloader(?).
I did the experimental steps to install twrp, but after flashing the 7.3.2 firmware of TheStrix provided on the DU rom thread, I bricked my phone. So maybe doing the steps here will change your bootloader to LP? I've downloaded the latest firmware provided by TheStrix on his Lineage OS thread and will try flashing that, will report back. Let's hope I don't break my phone.
Edit: Yup I broke my phone:silly::laugh: That confirms it that doing this guide will revert you to LP bootloader.
Well good thing I know how to fix it. Will try what this guy said:
Update: Replacing LP bootloader with the MM one won't work. TWRP would still not boot.
Anyone who followed this guide is on LP bootloader. Be careful flashing newer ROMs.
:good: Good luck with that. I received my unlock permission even before I got my phone, 1 month later still haven't officially unlockedThank you for testing this, at least now we know we need to get back on latest miui global dev. I'm going for official unlock.
My unlock permission didn't work anymore, had to re-apply. Latest dev miui is running very smooth, so I don't mind the wait.:good: Good luck with that. I received my unlock permission even before I got my phone, 1 month later still haven't officially unlocked. I don't feel like downloading 1 Gb+ of ROM. Maybe later if problems crop up.
Save yourself the (future) trouble and flash latest global dev rom, unlock your device officially, flash twrp.Thanks for the excellent guide!. I successfully installed LOS on my kenzo.
Still i have tried several times to make it work:
- I followed the steps strictly, step by step, but when i flashed minui dev rom and try to reboot into twrp, i just found twrp is not flushed at all: i just get the standard official recovery blank screen. I tried several times and all ended with no much.
- Then i downgraded MiFlashTool to 20160401 and used minui dev rom 2016060929, and repeated the steps - still with no luck.
I even tried to manually edit the flash_all.bat in the extracted dir of miui dev rom manually, to only leave the line that flashes the recovery, but somehow the MiFlashTool still flashes everything.
And before i was ready to give up, i tried for the last time - and it works - it booted into TWRP after flashing the miui dev rom!
I don't know what happened exactly, but for sure something has changed since the guide was written.
That's the weird part. They kept saying you need MM bootloader. Yet flashing the MM bootloader will break TWRP which makes me believe that only LP bootloader can be fooled that your stock recovery is TWRP. So anyone doing this guide should be on LP bootloader yet I faced no problems flashing the newest ROMs others have claimed to cause bootloops. I am on Kate though, maybe the file provided on Kate is a modified MM bootloader?Sadly i don't have much time for troubleshooting at the moment.
Only thing i can say is that i never faced any bootloops (lucky me?)
Still using ZCX TWRP version 0719
Flashing RR version on weekly base (atm RR-N-v5.8.3-20170507-kenzo-Nightly)
Using this with francokernel and i think atm 7.5.4 firmware.
I never used the experimental method. Used original method from 6.11.3. Maybe only Kenzo has LP bootloader. I'm on Kate as well and never had problems.That's the weird part. They kept saying you need MM bootloader. Yet flashing the MM bootloader will break TWRP which makes me believe that only LP bootloader can be fooled that your stock recovery is TWRP. So anyone doing this guide should be on LP bootloader yet I faced no problems flashing the newest ROMs others have claimed to cause bootloops. I am on Kate though, maybe the file provided on Kate is a modified MM bootloader?
build 20170426: change kernel if your unsatisfiedWhat is wrong with the developers lately, the paste 3 updates for redmi note 3pro have been so bad...
20170426-drained the battery to fast and heated up the device
20170503- didn't have the option for fingerprint at all....
now the last one 20170510 from yesterday i can not install...
Get your s*** together and do something good, stop using drugs)))))))))))))))))