Related
Hi all. Just got my shiny new HTC One dev edition this week. What I learned is I should have done more reading on here before I even turned on my device - for example I went and upgraded to OTA 4.4 before getting S-Off and Super CID - my bad... in any case absolutely loving the device with one exception and bad experience that I can hopefully help others recover from or avoid.
I unlocked by bootloader, got root, flashed custom recovery and flashed a KitKat based customer ROM - all the usual stuff. That was all good - here's where the fun starts. My exchange server requires device encryption as one of its policies and of course encryption with KitKat on the HTC One is flat out broken. The device refuses to boot after you've etered your dycryption password and it just hangs on boot screen forever. This is the case with KitKat whether you are on stock OTA or custom - did I mention KitKat encryption is broken on the One?
I tried everything:
1. Wiping in custom recovery doesn't work because it cannot decrypt
2. RUU fails
3. RUU.zip via fastboot fails
4. Tried flashing back to stock recovery and that factory reset also fails
I was contemplating what to do with my shiny new brick and remembered that the HTCDev unlock process does a wipe, so I relocked the bootloader (fastboot oem lock) and unlocked again using the Unlock_Code.bin file I got from HTC. This process was the only method that I found to work in this situation to remove encryption.
To summarize, if you have upgraded to KitKat (Stock or Custom ROM) and you go and encrypt your device, do the following to recover:
1. Relock the bootloader (if not unlocked - go to step 2)
2. Unlock the bootloader again using the Unlock_Code.bin from HTCDev
3. Select Yes during the process to erase all data on the device.
I hope this helps save someone the3 hours I spent on this.
Cheers.
I unlocked my bootloader, installed twrp and several roms to try them out, then decided to go back to stock. Currently have OOS 3.5.4 installed with stock recovery (that came with the toolkit). However, whenever I try to lock the booltloader again, the phone won't boot up. It will bootloop, or just stay off with the led glowing white. I tried to sideload the stock ROM from OnePlus, but it fails after about 45% completion. I tried both 3.5.3 and 3.5.4 and both fail after about 45%. The only way to get the phone to boot again is by unlocking the bootloader again, then it boots just fine. Tried unlocking with the toolkit as well as fastboot oem lock. Both give me the prompt on the phone, then wipe the phone and go into the bootloop.
Any suggestions on how to re-lock the bootloader? I want to be able to get the OTA update, which I think will fail with an unlocked bootloader. Note, I have also tried loading the Nougat update from settings - system update - local upgade (both full and update) and they also fail to load shortly after booting to recovery.
Thanks,
TR
Instead of using the toolkit, try just doing it manually.
fastboot oem lock IS the correct way to lock the bootloader.
If you're running into all those issues, try to reflash the stock rom from the official site. OR try this
NOTE: This WILL wipe everything on your phone so make a backup first!
First Unlock booloader1. On your phone go into Developer screen (Settings --> Developer Options)
If you don't have this go back to Settings --> About Device. Tap "Build number" 7-10 times to unlok developer options
2. In Developer Options turn on "USB Debugging" and "OEM Unlock"
3. Open ADB in command prompt and go to the directory where ADB is.
Type adb reboot bootloader
4. Once your device is in fastboot mode, type in fastboot devices to make sure your device is listed
5. Type in fastboot oem unlock to unlock your device bootloader
You can check to make sure it was properly unlocked by typing in fastboot oem device-info.
6. Reboot into your system
Files we need7. Download the following files:
TWRP - https://build.nethunter.com/test-builds/twrp/oneplus/twrp-3.0.2-0-oneplus3t.img
No-verity-opt-encrypt - https://build.nethunter.com/android-tools/no-verity-opt-encrypt/no-verity-opt-encrypt-5.0.zip
Magisk - http://tiny.cc/latestmagisk
Phh-Superuser - https://forum.xda-developers.com/attachment.php?attachmentid=3988488&d=1483407725
Latest Stable Nougat Rom - http://otafsc.h2os.com/patch/amazon...s3TOxygen_28_OTA_035_all_1612310259_2dc0c.zip
8. Copy all the files to your phone (keep the original on your pc just in case)
9. Load back up to fastboot mode
In ADB type adb reboot bootloader
10. Flash twrp img we downloaded above by typing
fastboot flash recovery twrp-3.0.2-0-oneplus3t.img
11. After this reboot into the system
Install all of our downloaded files through TWRP12. Now boot into recovery by issuing the following ADB command
adb reboot recovery (you should go into TWRP)
13. Once you're in twrp flash the "no-verity-opt-encrypt-5.0.zip" file OR you can format the data partition to f2fs to prevent the dm-verity error.
14. Now install the stock stable nougat rom we downloaded above
15. Do a factory system wipe / cache & dalvik
16. Install magisk through TWRP
17. Wipe cache/dalvik
18. Install phh SuperUser
19. Now reboot into the system normally.
NOTE: This *COULD* take a while since you did a clean install of nougat so just be patient and you should be good to go after this.
Thanks for the reply.
I did do fastboot oem lock, and it results in an unbootable system. fastboot oem unlock makes it bootable again. Not sure why. Also, whenever I do adb sideload <any_rom> it fails after about 45%. Not sure what's happening. Your instructions would get me to Nougat with TWRP and an unlocked bootloader, which may be what I end up doing, but I was trying to get back to fully stock, and locked again, so that OTA's will work properly. If nothing else works, I will go the route you suggest above.
Thanks again!
I just figured I'd try to get you to a working system/phone. After you get all that working you can probably lock your bootloader back to default. Now, I'm not 100% sure, but I believe that if you have a custom recovery you will need to restore that to stock as well before setting the bootloader back to locked.
TXRangerXDA said:
I unlocked my bootloader, installed twrp and several roms to try them out, then decided to go back to stock. Currently have OOS 3.5.4 installed with stock recovery (that came with the toolkit). However, whenever I try to lock the booltloader again, the phone won't boot up. It will bootloop, or just stay off with the led glowing white. I tried to sideload the stock ROM from OnePlus, but it fails after about 45% completion. I tried both 3.5.3 and 3.5.4 and both fail after about 45%. The only way to get the phone to boot again is by unlocking the bootloader again, then it boots just fine. Tried unlocking with the toolkit as well as fastboot oem lock. Both give me the prompt on the phone, then wipe the phone and go into the bootloop.
Any suggestions on how to re-lock the bootloader? I want to be able to get the OTA update, which I think will fail with an unlocked bootloader. Note, I have also tried loading the Nougat update from settings - system update - local upgade (both full and update) and they also fail to load shortly after booting to recovery.
Thanks,
TR
Click to expand...
Click to collapse
I also have the same problem, after the bootloader lock the phone does not start.
I tried with all the possible procedures, also even the rom flash in local and sideload it does not work, It comes to 45% and then fails.
we will highlight the problem, so everyone will know and maybe there is a solution
m0d hipp¥ said:
I just figured I'd try to get you to a working system/phone. After you get all that working you can probably lock your bootloader back to default. Now, I'm not 100% sure, but I believe that if you have a custom recovery you will need to restore that to stock as well before setting the bootloader back to locked.
Click to expand...
Click to collapse
But of course, you can't relock phone with a non standard recovery. Replace TWRP with the ROMs real recovery and relock will work again.
That's what I figured. Thanks for the confirmation.
Use the unbrick tutorial to go back to stock
This is what i did
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
pitrus- said:
But of course, you can't relock phone with a non standard recovery. Replace TWRP with the ROMs real recovery and relock will work again.
Click to expand...
Click to collapse
I'm sorry, even with the stock recovery but does not work, it was the first thing I did
You can a unbick tutorial. It worked for my OnePlus 3T. Just search up How to unbrick (whatever OnePlus device you have) on Google. Then follow all the instructions carefully. If you need help with it I could try to do a remote session with you. Edit: It will erase all data and you will boot with oos 3.5.3 ( I also had the same issue as you. But I couldn't install any zip with stock recovery or adb side load.
Haven't seen nothing on the fórum about this particular subject, locking the bootloader seems a problem in this phone
enokack said:
Haven't seen nothing on the fórum about this particular subject, locking the bootloader seems a problem in this phone
Click to expand...
Click to collapse
Only if you have modified the phone in some way or another (like rooting and installing twrp) before trying to re-lock.
If you keep it stock, you should be able to re-lock. Or else, just use the Qualcomm restore method to re-lock.
tried this
OK what i did was when the phone was starting and vibrating I push the power bottom and volume down bottom at the same time ,then i connected the phone to the PC,from the panel in the phone there are 3 categories to erase everything on the phone I did it all(1,2,3) and then I put the phone in ADB mode from the control panel in the phone,After that I flash via fastboot the original .zip from one plus for the version 4.0.3 (1.4 GB) ,when it finished I restarted and the phone started normal again,I hope this help someone alse,I was so desesperated:silly:.
I think the problem in re-locking it is the modified boot image. Locked bootloaders don't support those.
re-locking bootloader will getback the warranty ???
No solutions till now
enokack said:
Haven't seen nothing on the fórum about this particular subject, locking the bootloader seems a problem in this phone
Click to expand...
Click to collapse
Its three easy steps, no need to use any toolkit just follow the instructions. https://forums.oneplus.net/threads/...-3-3t-and-go-back-completely-to-stock.456232/
Abrar123 said:
re-locking bootloader will getback the warranty ???
Click to expand...
Click to collapse
Unlocking the bootloader does not void the warranty on this device:
https://oneplus.net/support/answer/will-rooting-or-unlocking-the-bootloader-void-my-warranty
Once I have root, is there a command to re-lock and later eventually unlock the bootloader again?
I remember this was possible with google nexus devices, there was a shell command (require root) that was able to change bootloader status
Hi Guys,
I haven't find so far (after reading hundreds of threats here and there) a clear solution to my problem.
To make it short :
Last EMUI update to 5.0.1 on my PRA-LX1C109B131 caused GPS instability.
I reported to Huawei France support but did not get any answer apart from launching a factory reset.
So I decided to install an alternative ROM.
I first unlocked the bootloader and taped OEM unlock from the developer's menu -> OEM Unlocked (FRP Unlock in Fastboot) and Bootloader was Unlocked
From instruction from a spanish forum I installed TWRP from Revolution Project (fastboot flash recovery TWRP_3.0.3-0_RevolutionRecoveryNougat_RC2.img).
From TWRP, I installed the ROM_MIDGARD_3V3.0_P8-P9LITE2017.zip backup.
This has fixed the GPS issue !
But I thought it could be nice to re-install a stock ROM and downgrade from C109B131 to C109B120.
I downloaded PRA-LX1C109B120-FullOTA-MF zip packages ("update.zip", "update_data_full_public.zip" et "PRA-L11_orange_all/update_full_PRA_orange_all.zip")
I unzipped the 2 first packages to get the UPDATE.APP file.
From the UPDATE.APP file I got BOOT.img, RECOVERY.img et SYSTEM.img and CUST.img
Then from fastboot :
fastboot flash boot BOOT.IMG -> success
fastboot flash recovery RECOVERY.IMG -> success
fastboot flash system SYSTEM.IMG -> success
fastboot flash cust CUSTOM.IMG -> success
fastboot reboot
From Huawey recovery, I did a wipe/cache and then a factory reset / wipe data.
Then installation starts ang get stuck at 99%
I left the phone for about 15/20 minutes.
In the end I re-installed the Midgard ROM and restored my data.
I'd like to know if I did something wrong or if I missed something.
Perhaps I need to flash recovery2 file.
I saw that some say I need to unlock again the bootlaoder although it is shown as unlock.
Please advise.
DamageINC_54590 said:
Hi Guys,
I haven't find so far (after reading hundreds of threats here and there) a clear solution to my problem.
To make it short :
Last EMUI update to 5.0.1 on my PRA-LX1C109B131 caused GPS instability.
I reported to Huawei France support but did not get any answer apart from launching a factory reset.
So I decided to install an alternative ROM.
I first unlocked the bootloader and taped OEM unlock from the developer's menu -> OEM Unlocked (FRP Unlock in Fastboot) and Bootloader was Unlocked
From instruction from a spanish forum I installed TWRP from Revolution Project (fastboot flash recovery TWRP_3.0.3-0_RevolutionRecoveryNougat_RC2.img).
From TWRP, I installed the ROM_MIDGARD_3V3.0_P8-P9LITE2017.zip backup.
This has fixed the GPS issue !
But I thought it could be nice to re-install a stock ROM and downgrade from C109B131 to C109B120.
I downloaded PRA-LX1C109B120-FullOTA-MF zip packages ("update.zip", "update_data_full_public.zip" et "PRA-L11_orange_all/update_full_PRA_orange_all.zip")
I unzipped the 2 first packages to get the UPDATE.APP file.
From the UPDATE.APP file I got BOOT.img, RECOVERY.img et SYSTEM.img and CUST.img
Then from fastboot :
fastboot flash boot BOOT.IMG -> success
fastboot flash recovery RECOVERY.IMG -> success
fastboot flash system SYSTEM.IMG -> success
fastboot flash cust CUSTOM.IMG -> success
fastboot reboot
From Huawey recovery, I did a wipe/cache and then a factory reset / wipe data.
Then installation starts ang get stuck at 99%
I left the phone for about 15/20 minutes.
In the end I re-installed the Midgard ROM and restored my data.
I'd like to know if I did something wrong or if I missed something.
Perhaps I need to flash recovery2 file.
I saw that some say I need to unlock again the bootlaoder although it is shown as unlock.
Please advise.
Click to expand...
Click to collapse
You can try find a full twrp backup and restore it following instructions in this forum, i dont know if the twrp b182 backup its valid for you, search about this and good luck!
Enviado desde mi PRA-LX1 mediante Tapatalk
Thanks for this but I'd like to know first why the factory reset remains at 99%
I know for sure the build build C109B120 I downloaded is fully compatible with my P8 lite 2017 so it should be no problem re-flashing it.
Since the last EMUI official update to version 5.0.1 a lot of users (at least on French, Italian and Spanish forum) reported some GPS issue (signal is lost after 15/20 minutes). Rebooting the device fix this.
No official fix yet from Huawei.
EDIT : another bug was also reported regarding wifi slow transfer rate when blutooth is activated.
I tested myslef and confirm that on my device if blutooth is activated wifi transfer rate drops down from 3/4 Mb per s. to less than 100kb / s.
DamageINC_54590 said:
Hi Guys,
I haven't find so far (after reading hundreds of threats here and there) a clear solution to my problem.
To make it short :
Last EMUI update to 5.0.1 on my PRA-LX1C109B131 caused GPS instability.
I reported to Huawei France support but did not get any answer apart from launching a factory reset.
So I decided to install an alternative ROM.
I first unlocked the bootloader and taped OEM unlock from the developer's menu -> OEM Unlocked (FRP Unlock in Fastboot) and Bootloader was Unlocked
From instruction from a spanish forum I installed TWRP from Revolution Project (fastboot flash recovery TWRP_3.0.3-0_RevolutionRecoveryNougat_RC2.img).
From TWRP, I installed the ROM_MIDGARD_3V3.0_P8-P9LITE2017.zip backup.
This has fixed the GPS issue !
But I thought it could be nice to re-install a stock ROM and downgrade from C109B131 to C109B120.
I downloaded PRA-LX1C109B120-FullOTA-MF zip packages ("update.zip", "update_data_full_public.zip" et "PRA-L11_orange_all/update_full_PRA_orange_all.zip")
I unzipped the 2 first packages to get the UPDATE.APP file.
From the UPDATE.APP file I got BOOT.img, RECOVERY.img et SYSTEM.img and CUST.img
Then from fastboot :
fastboot flash boot BOOT.IMG -> success
fastboot flash recovery RECOVERY.IMG -> success
fastboot flash system SYSTEM.IMG -> success
fastboot flash cust CUSTOM.IMG -> success
fastboot reboot
From Huawey recovery, I did a wipe/cache and then a factory reset / wipe data.
Then installation starts ang get stuck at 99%
I left the phone for about 15/20 minutes.
In the end I re-installed the Midgard ROM and restored my data.
I'd like to know if I did something wrong or if I missed something.
Perhaps I need to flash recovery2 file.
I saw that some say I need to unlock again the bootlaoder although it is shown as unlock.
Please advise.
Click to expand...
Click to collapse
I posted this procedure on a French forum and got feed-back. It works.
Perhaps i dont't wait enough time when the EMUI installation process reaches 99%.
I forced the shutdown of the device by pressing the power button after approximatively 20 minutes
I managed to brick my Honor 9 Lite while attempting to root it, and it seems that all recovery methods have failed. Is there any way to restore back to stock firmware, or should I just give up and put it through a shredder? Here's what happened:
1. Set up as a new device and successfully unlocked the bootloader
2. Installed unofficial TWRP build via fastboot
3. Attempted to install SuperSU, which failed at decompression stage
4. Flashed a "System-Mode" SuperSU, which appeared to succeed
5. When rebooting, the device hangs at the "Honor" boot logo and never successfully enters the home screen
There are a few things to note at this point:
- The TWRP build may have been faulty, as none of the user preferences would save properly
- Before attempting to root, I tried to make a TWRP backup multiple times, and every time it failed with error 255, probably because TWRP itself was faulty, hence I have no backup to restore to
Here's what I've tried to recover the system:
- Entered eRecovery, connected to Wi-Fi but it could not gather package info from their servers
- Downloaded the stock firmware package and saved it to the correct location on the micro SD card, attempting to install it via the "three-button" mode would begin the process but fail at 5%, with an "install failed" message
- Connected to HiSuite in fastboot mode, attempting to recover results in a "your device is not supported" message
- Visited the URLs displayed on the device in each of the recovery mode failure screens, they're all dead links (Huawei reorganising their website?)
- Used TWRP to wipe cache, Dalvik cache before repeating above steps
- Attempted a factory reset, still stuck at the boot animation
- Re-locked the boot loader and retried the above steps
- Flashed LineageOS via TWRP, it just stays at the Lineage boot animation for 10 minutes before automatically rebooting to eRecovery
- Copied the stock update.zip to the SD card and attempted to flash via TWRP, it just fails
- Extracted the parts from update.app and manually flashed each to the device via fastboot, still gets stuck on the boot animation
Is there anything else I should try before giving up and tossing it in the trash?
Edit:
I bought this thing yesterday, it lasted a grand total of less than 12 hours before bricking. There's no important data on it whatsoever, so I don't care if anything needs to be formatted.
My guess: if You can flash los than do it and flash stock recovery after that. Worked for me.
Info needed :
- Bootloader unlocked
- FRP unlock
- What's your Build ( example: LLD-L31C432B131 / LLD-L31 8.0.0.131/C432) )
If bootloader and FRP unlock and you can boot to bootloader : it's a little problem
You need your Build FULL-Update.
Extract with "UpdateExtractor" : ramdisk.img + recovery_ramdis.img + system.img
Extractor do automatic for all *.img the *.img.header / you have now 6 files
copy this 6 files in your "adb"-folder / boot to bootloader / go to your "adb"-folder
- fastboot flash ramdisk ramdisk.img
- fastboot flash recovery_ramdisk recovery_ramdis.img
- fastboot flash system system.img
reboot
if this work : your phone have now stock-ROM and boot as "new"-phone (format data, initial-settings ...)
if this not work (recovery stop at 5%) you have chance "2"
look this : https://forum.xda-developers.com/ho.../recovery-bkl-nocheck-recovery-flash-t3778085
reed the instruction
if you understand and can do this it's the same result : at the end your phone boot with stock-ROM
with this way i have my Honor 9 Lite reset to stock-ROM
JamesBott said:
Info needed :
- Bootloader unlocked
- FRP unlock
- What's your Build ( example: LLD-L31C432B131 / LLD-L31 8.0.0.131/C432) )
If bootloader and FRP unlock and you can boot to bootloader : it's a little problem
You need your Build FULL-Update.
Extract with "UpdateExtractor" : ramdisk.img + recovery_ramdis.img + system.img
Extractor do automatic for all *.img the *.img.header / you have now 6 files
copy this 6 files in your "adb"-folder / boot to bootloader / go to your "adb"-folder
- fastboot flash ramdisk ramdisk.img
- fastboot flash recovery_ramdisk recovery_ramdis.img
- fastboot flash system system.img
reboot
if this work : your phone have now stock-ROM and boot as "new"-phone (format data, initial-settings ...)
if this not work (recovery stop at 5%) you have chance "2"
look this : https://forum.xda-developers.com/ho.../recovery-bkl-nocheck-recovery-flash-t3778085
reed the instruction
if you understand and can do this it's the same result : at the end your phone boot with stock-ROM
with this way i have my Honor 9 Lite reset to stock-ROM
Click to expand...
Click to collapse
Thanks for your response, my device is both FRP and bootloader unlocked, build LLD-L31C432B127.
I have already tried manually flashing ramdisk, ramdisk recovery, and system, however it is still bootlooping.
I have also tried the HWOTA method, however there is no su. I am also not able to access adb, only fastboot. Previously adb would work at the boot animation, however now nothing appears when I type adb devices.
You have to be in TWRP to use adb, if I remember right.
I think, you ar the same problem as i for many week.
If you can - check following : download this TWRP https://forum.xda-developers.com/9-lite/development/recovery-twrp-3-2-1-0-t3789306
flash TWRP, boot to recovery "USB-Wire out phone, press and hold Vol-Up and Power, if phone restart less Power, on bootscreen less Vol-Up.
now start TWRP.
if you setting PIN for screen-unlock TWRP write on start "input code for decrypt" : you can now over-step
in TWRP go to reboot, boot system.
now 2 possibility : 1= system boot, 2= phone boot to TWRP
check this please and give answer, what phone doing
JamesBott said:
I think, you ar the same problem as i for many week.
If you can - check following : download this TWRP https://forum.xda-developers.com/9-lite/development/recovery-twrp-3-2-1-0-t3789306
flash TWRP, boot to recovery "USB-Wire out phone, press and hold Vol-Up and Power, if phone restart less Power, on bootscreen less Vol-Up.
now start TWRP.
if you setting PIN for screen-unlock TWRP write on start "input code for decrypt" : you can now over-step
in TWRP go to reboot, boot system.
now 2 possibility : 1= system boot, 2= phone boot to TWRP
check this please and give answer, what phone doing
Click to expand...
Click to collapse
Thank you so much!
While a direct boot from TWRP did not work, completely migrating the HWOTA files and then booting into the "no-check" recovery successfully forced an update, and the system was properly restored. The device is now up and running and I was able to root it. Sadly, TWRP still doesn't make backups properly, so I will have to be careful.
ok : now you have 99% stock-ROM
the last 1% is "encrypted data".
if your data is "encrypted" is a little security for you (is phone lost)
i hope you use the TWRP from Pretorian80
first now set PIN for screen-unlock (no fingerprint, no other)
check this : tap on power, phone go stand-by, tap on power, phone wake up and need PIN
next do : flash stock-recovery, boot to recovery and wipe data AND recovery do low-level format data
flash TWRP, boot to TWRP and this write "give me the PIN for decrypt"
if this - your data now encrypted
if this not - other way : boot to bootloader
fastboot flash stock-recovery
fastboot erase userdata
reboot phone, stock-recovery format data low-level
flash TWRP and check
now give answer what work and what NO
only stock-recovery can format data WITH encryption - i do not know another way
on a brand new phone with NO PIN setting the TWRP write "i use the standard code for decrypt"
is a PIN set the TWRP write "give me the PIN for decrypt"
the best on this "little" bootloop : you learning your phone understanding
I found this useful tool, just in case someone need to recover his device.
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
You only need to be able to access TWRP and have aN update.zip with a full OTA
I want to back to stock on my Xiaomi A2 (full factory state - bootloader locked, no TWRP etc.) to get ma warranty back.
My current status:
- bootloader and critical unlocked
- loaded V10.0.8.0.PDIMIXM ROM (Fastboot official) from https://forum.xda-developers.com/mi-a2/how-to/ota-v9-6-5-0-odimife-t3823445 (used edl mode)
- previously I installed TWRP, decryption disabler and magiks
My last way to install ROM was by edl mode - downloaded fastboot version and used MiFlash tool (clean all). Previously I tried to run flash_all.bat from fastboot ROM, but it stopped on lashing devcfg_a (FAILED (remote: Flashing is not allowed for Critical Partitions), but I have critical unlocked.
My question is: Should I use MiFlash with edl mode to back to full stock with "clean all and lock" mode? Is it safe? I am afraid of locking bootloader and missing something what should be done before (I read it can brick the phone).
Should I install recovery first (missing in fastboot package), enable encryption or do something more?
Just flash fastboot image and relock and it'll be fine
I've reinstalled stock rom just yesterday, i had the same error with Mi Flash, i've flashed all manually from ADB, if you're coming from an Android Q ROM flash back the persist partition (i've a full Pie Backup) first or your WiFi MAC will disappear, when you've installed all (if the phone boot with Android One and everything Is working) just lock the bootloader (i've just used Oem Lock, idk about critical partitions) and you're good to go
When I used Mi A2 Toolkit, there were 3 options when I was unlocking bootloader: "Unlock OEM", "Unlock Flashing" and "Unlock flashing critical". I am not sure if executed all of them, but I am sure they were at least 2 of them.
So do I have to lock in the opposite way "Lock flashing critical", "Lock flashing" and "Lock OEM" or just "Lock OEM"? I need to be sure.
Can something happen if I will try to lock in that way, but I didn't unlock if before?
There is a toggle in developer options, "OEM Unlocking," which needs to be toggled on to lock or unlock the bootloader with fastboot. I would leave the bootloader and critical both unlocked until you are ready to use the warranty. If you have a bad flash and then lock the bootloader or critical then you might have a hard time getting everything working again.