[Xiaomi Redmi Note 3 [Snapdragon] ROMs, Kernels, Re] ilfccd:
You did. However my permissions got revoked for some reason, so I can not officially unlock. I'm looking into a procedure for unofficial unlock, as I don't want to lose my data. In the mean time I'm waiting for Xiaomi to approve me again, but my patience is not my strongest suit.

---------- Post added at 09:51 PM ---------- Previous post was at 09:35 PM ----------

Possible solution for a re-locked bootloader after CM14-firmware flash I would like someone's opinion on this.

As all of you who have unofficially unlocked the bootloader know, the procedure is pretty straight forward and involves booting into edl mode and flashing from there with modified emmc_appsboot.mbn.

I was wondering could we do the same with the MiFlasher but with modified script so that we just replace the emmc_appsboot.mbn again with the moddified one and oem unlocking the bootloader again. That would probably allow the device to boot instead of going into boot loop.

I'm using kate, but the procedure for kenzo is the same. I extracted the fastboot rom 6.12.1 into c:\kate\kate_global_images_6.12.1_20161201.0000.00_6.0_global_mod

then I went into the images folder and deleted everything except (the emmc_appsboot.mbn is the modded one, obviously, not the original one that comes with the ROM)

emmc_appsboot.mbn
hyp.mbn
keymaster.mbn
NON-HLOS.bin
prog_emmc_firehose_8976_ddr.mbn
rpm.mbn
sbl1.mbn
tz.mbn

then I modded the bat file flash_all_except_data.bat to include just this:

fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *kate" || echo Missmatching image and device
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *kate" || exit /B 1
fastboot %* flash tz %~dp0images\tz.mbn || @echo "Flash tz error" && exit /B 1
fastboot %* flash sbl1 %~dp0images\sbl1.mbn || @echo "Flash sbl1 error" && exit /B 1
fastboot %* flash rpm %~dp0images\rpm.mbn || @echo "Flash rpm error" && exit /B 1
fastboot %* flash aboot %~dp0images\emmc_appsboot.mbn || @echo "Flash emmc_appsboot error" && exit /B 1
fastboot %* flash hyp %~dp0images\hyp.mbn || @echo "Flash hyp error" && exit /B 1
fastboot %* flash keymaster %~dp0images\keymaster.mbn || @echo "Flash keymaster error" && exit /B 1
fastboot %* flash cmnlib %~dp0images\cmnlib.mbn || @echo "Flash cmnlib error" && exit /B 1

fastboot %* flash modem %~dp0images\NON-HLOS.bin || @echo "Flash modem error" && exit /B 1

fastboot %* reboot
pause

in the MiFlasher I chose save user data, which would imply that the bat file flash_all_except_data.bat would be used for the "flashing process". Just to be on the safe side I'm gonna mod the .sh script, although it is supposed to be used on *NIX platforms.

I suppos that would flash the firmware files and the modded emmc_appsboot.mbn only. The only reason I'm not testing this directly is that I don't know what does prog_emmc_firehose_8976_ddr.mbn do. This is supposed to be a flash programmer of sorts, but will someone let me know what it is supposed to do. I also removed the fastboot erase DDR, as I'm not sure it is needed in this case.

Can someone advice on this, because as long as I don't know what the prog_emmc_firehose does I'm not gonna test this on my phone..