Database Users

GUIDE: Flash Xiaomi Mi 5S from Chinese ROM to Global Rom WITHOUT UNLOCKING

Many people like me did buy its Xiaomi Mi 5S from Chine wich official Chinese ROM. The problem of this ROM is that unless you are Chinese you dont really enjoy it. But now since the official Global ROM was released all was supposed to be saved and beautiful. Except you could not flash it using the built-in flashing (update) tool of the ROM it just would not recognize it as valid and thats that.
First and most recognized solution you would find is Unlock bootloader and flash it via fastboot (MiFlash windows app). In order to unlock a Xiaomi you have to Apply for unlock and give them specific reason to grant you your wish (pretty lame). Than after unlock it will work. It takes them less then 10 days (official Xiaomi), if not you should write on their forum. Not sure if anyone did not get it, but its still stupid.
There used to be option to do this using EDL mode (or Download mode), but there is no EDL in Mi 5s any more, so no luck here either.
So here is option number two that will always work without unlocking bootloader. It will even work with bricked phones. It is called Deep Flash. This option works only with Qualcom machines (f.e. Snapdragon) and what it does is, it connects your smartphone to your computer via one of COM ports using the Qualcom drivers. Dont ask me how exactly, I dont know, dont care. It just works The whole point of this method is the Deep Flash Cable, you need it and you either make it yourself (real easy) od buy one on Aliexpress (easier, but you have to wait long).
Here is video with the procedure of deep flashing: https://youtu.be/tdk0d2Zrm9w
Here is an OK website with the whole procedure including how to make Deep Flash cable: http://www.stupdroid.com/2016/10/make-xiaomi-deep-flash-cable-and.html
Here is link to the official FASTBOOT Global ROM: http://en.miui.com/thread-454687-1-1.html
Here is link to MiFlash tool: http://en.miui.com/thread-345974-1-1.html - I beleive the new version already has Qualcom drivers included.
If windows was making you trouble and your Qualcom driver will not install here is why: http://en.miui.com/thread-237673-1-1.html
I also attach pictures of my cable and a schematic of what you are actually doing. It is really a simple thing to do. It took me like 20 minutes. No special skills required, and I used only sharp knife, did not even have a razer. I used some random cable, not genuine Xiaomi cable as the guide says. I used non copper cables to connect B and G (I canibalized some other old USB cable).
IMPORTANT NOTE, keep with the flash procedure exactly as it says, or you will get errors ("cannot receive hello packet") when flashing like I did.
1. MiFlash is not running on your PC, Your phone is turned OFF, The two cables (B and G) are connected together, Your Device Manager is ON
2. You connect the Deep Flash cable to your PC use USB 2.0 port (USB 3.0+ are reported not to work)
3. You connect the Deep Flash cable to your Mi5S
4. Wait for 10 seconds. (just count to 13 or something) - apparently this may save you from the "hello packet" error
5. You disconnect the two cables (B and G) - in Device Manager you will see something like Qualcom HS-USB Diagnostic 9008 - keep cables disconnected
6. Only now you launch MiFlash by going to C:\XiaoMi\XiaoMiFlash and Right-clicking on XiaoMiFlash.exe and Run as Administrator
7. In MiFlash tool Press Refresh button - you will see your phone on one COM port
8. Browse to your Global Rom (f.e. capricorn_global_images_V8.0.3.0.MAGMIDI_20161222.0000.00_6.0_global) under this folder you will see folder named image
9. Press Refresh one more time
10. Press Flash and have a coffe (took mine 5 minutes)
11. After you see nice green success you turn off MiFlash
12. Disconnect the cable from phone
13. Boot the phone - dont panic first boot is very long
There ya go. You are now on Xiaomi Mi5S with Global ROM with still locked bootloader. This guide should work with Mi5S Plus, but I did it on my Mi5S only.
Special thanx to XN Logos and his post about unbricking. This one is literarly the same method. But I myself ran around that post 10 times when searching for solution to my problem and never knew this in fact is solution to my problem aswell :silly:
Thanx to awaaas for mentioning the disclaimer about USB 3.0 ports.
Thanx to cerietke for mentioning the 10 second pause in step 4.

Great guide! Unfortunately I have unlocked my device to change to global rom. Hopefully it will benefit other. UP!

I tried following these instructions but have ran into one problem which I managed to solve. In case MiFlash shows an error "cannot receive hello packet" you have to make sure adb driver is installed. More about this is written in this topic: en.miui.com/thread-299790-1-1.html
You can make a backup with built in MIUI app, then copy it to your pc and restore after flashing.
Now I can enjoy a ROM without crappy chinese apps and all notifications are working from the beginning.

Are there any advantages of deep flash method over standard with unlocked bootloader?

Rejerf said:
Are there any advantages of deep flash method over standard with unlocked bootloader?
Click to expand...
Click to collapse
Well you do not have to unlock the bootloader for once. But other than that, no, there are none. But with Xiaomi you have to be approved for unlock case by case and it takes them approx 3 days. But it is just flashing. ROM is the same.

i try this prozedre with help by simply silver paper. what should i say, this also works. xdddd
neverless, i still wait for the "deep flash" cable from aliexpress.
best regards

I tried everything, with the lots of guides, I made my own deep flash cable, I succeeded in putting my mi 5s Plus into deep flash mode but did not succeeded in flashing the Rom.
Every time there is the error message from the Mi flasher cannot receive hello packet etc. Then I applied for unlock boot loader officially. I got SMS with the unlocking permission in 15 minutes. After unlocking boot loader, I put my phone into fast boot mode and flashed fast boot Rom and everything is fine. No error ..nothing. So, I do not want to disappoint anybody, but this method did not worked for me.

Just want to add a note, this method would not work if you use USB 3.0+ port (or USB 2.0 behind USB 3.0 hub) such as on a intel's skylake/kabylake-based machine.
Maybe that's your problem @richie16171?

richie16171 said:
I tried everything, with the lots of guides, I made my own deep flash cable, I succeeded in putting my mi 5s Plus into deep flash mode but did not succeeded in flashing the Rom.
Every time there is the error message from the Mi flasher cannot receive hello packet etc. Then I applied for unlock boot loader officially. I got SMS with the unlocking permission in 15 minutes. After unlocking boot loader, I put my phone into fast boot mode and flashed fast boot Rom and everything is fine. No error ..nothing. So, I do not want to disappoint anybody, but this method did not worked for me.
Click to expand...
Click to collapse
Good point from awaas I did not know that. Try that too.
But I was getting the same error as you. What you need to do is follow my instructions religiously. It made difference to me when I skipped some point or did something parallel. Do exactly as my guide says. Disconnect and turn everything off and start from point one exactly like the guide says.
I remember it was different when I had flashing tool open before and after some point. So go exactly as the guide and you should be fine

awaaas said:
Just want to add a note, this method would not work if you use USB 3.0+ port (or USB 2.0 behind USB 3.0 hub) such as on a intel's skylake/kabylake-based machine.
Maybe that's your problem @richie16171?
Click to expand...
Click to collapse
Nope ..it was USB 2.0 and I am using laptop. I tried all the ports in the computer. Tried with another computer and not once 7 times.
---------- Post added at 02:24 PM ---------- Previous post was at 02:07 PM ----------
Seehank said:
Good point from awaas I did not know that. Try that too.
But I was getting the same error as you. What you need to do is follow my instructions religiously. It made difference to me when I skipped some point or did something parallel. Do exactly as my guide says. Disconnect and turn everything off and start from point one exactly like the guide says.
I remember it was different when I had flashing tool open before and after some point. So go exactly as the guide and you should be fine
Click to expand...
Click to collapse
I did exactly what you said 100%. As I said not once.., with driver signature off and on. I did not had any driver problem. It was showing me the port com16.
I think that is not the right port for flashing.

richie16171 said:
Nope ..it was USB 2.0 and I am using laptop. I tried all the ports in the computer. Tried with another computer and not once 7 times.
---------- Post added at 02:24 PM ---------- Previous post was at 02:07 PM ----------
I did exactly what you said 100%. As I said not once.., with driver signature off and on. I did not had any driver problem. It was showing me the port com16.
I think that is not the right port for flashing.
Click to expand...
Click to collapse
Well man, than this is the end of me :-/ I know I was getting this error when I had MiFlash turned on before I connected my phone to the PC . That gave me same error. But when it was off before and after deep flashmode a opened it up as admin (from the directory, not Start) it worked for me just fine.

Does anyone know if this works in 8.2? When I plug cable in it starts charging..

Agirretxd said:
Does anyone know if this works in 8.2? When I plug cable in it starts charging..
Click to expand...
Click to collapse
The 8,2 hasa big problem with battery drain. Mine 5s has poor battery life now. Just wait a bit.

Is there any work being done on official Lineage OS for the Mi5S?

richie16171 said:
I tried everything, with the lots of guides, I made my own deep flash cable, I succeeded in putting my mi 5s Plus into deep flash mode but did not succeeded in flashing the Rom.
Every time there is the error message from the Mi flasher cannot receive hello packet etc. Then I applied for unlock boot loader officially. I got SMS with the unlocking permission in 15 minutes. After unlocking boot loader, I put my phone into fast boot mode and flashed fast boot Rom and everything is fine. No error ..nothing. So, I do not want to disappoint anybody, but this method did not worked for me.
Click to expand...
Click to collapse
Hey,
I just tried to reflash mine and just like you said I was getting all the errors. No way to fix it But then I uninstalled (also deleted every single file) the MiFlash tool and after installing it again it worked Sooo probably there is some log file or some setting or I dont know what that is doing trouble.

@ Seehank., Thank you so much, Maybe that is the problem... otherwise so many people succeeded doing this, Only I failed.
Now no point. I already unlocked boot loader and flashed the firmware. And that also I flashed in fast boot mode.
Now I have one more Mi note3 pro. And it is the used phone. Someone already unlocked boot loader. That is why or for some reason I was not getting OTA update. Hence the boot loader is unlocked, and I tried to flash with the fast boot mode.. No.. I am getting error. In flash tool it is not showing Com Port..instead some serial number. So I flashed that in EDL mode and success. After that now I am getting OTA update.

Hope this may help others with the hello packet issue.
I was following your guide, but I was going through pretty quickly, which turned out to be relevant. I did some searching on the issue and discovered a post on en.miui.com that suggested a solution (post 32 in the "[Help]-cannot receive hello packet,MiFlash is trying to reset status" topic; as a new user I cannot post outside links). Apparently you'd need to wait at least 10 seconds between step 3 and 4. As I also did a full reboot of the phone without the cable attached that may have also been the solution. I did not further test as I got it working.

Hi guys, have locked phone on purchase, thought I might revive it with above methode but...no way I coulkd install quallcomn drivers, tried (i think) everything, phone gets into charging mode, nothing happens in Device manager...

cerietke said:
Apparently you'd need to wait at least 10 seconds between step 3 and 4.
Click to expand...
Click to collapse
I will add this to the guide. It can not harm anyone So between my guide and steps 3 and 4 wait 10+ seconds.

Hi mate, i followed your guide, everything works till the very last point, when i boot my phone (after the success message in the MiFlash), 2 strange things happen:
1) first time i press "power" button it wont start, i press a second time and it starts
2) the MI logo starts blink every x minutes, but actually is not going forward (still stuck on MI logo after more than 10 mins waiting)
can you help me somehow? Thanks

Please Help! I flashed my phone to Lineage OS and tried to relock the bootloader.

Please Help! I flashed my phone to Lineage OS and everything was working great except android pay. I read online to re lock the bootloader for android pay to work. I did and the phone suddenly died on me. If I try to switch on it wont switch on. It just shows ZTE logo and dies and the red notification light flashes once immediately. If I try to charge, the red notification light wont come up. Its all black. Please help if anybody knows any solution! Thank you!

It's because LOS needs unlocked bootloader. What you're experiencing is it booting into EDL. If you connect it to your computer you should near that chime that something is connected. You'll need to flash the b20 bootloader to unlock it again. Once you do that flash the nougat bootstacks and you'll be back in business.

nolimit78 said:
It's because LOS needs unlocked bootloader. What you're experiencing is it booting into EDL. If you connect it to your computer you should near that chime that something is connected. You'll need to flash the b20 bootloader to unlock it again. Once you do that flash the nougat bootstacks and you'll be back in business.
Click to expand...
Click to collapse
Thanks a lot for the reply. computer doesn't do any chime when I connect it. I dont see any drivers related to that also. I dont know what to do.

ar4m7 said:
Thanks a lot for the reply. computer doesn't do any chime when I connect it. I dont see any drivers related to that also. I dont know what to do.
Click to expand...
Click to collapse
With the phone connected to the pc, post a screen shot of the device manager screen.

A2017G bricked with Lineage OS and Twrp

Hullo,
I succesfully installed Lineage with no problems in the OS, but was unable to access TWRP as it asked for a decryption pattern that didn't seem to match the pattern I set on my phone. I then tried a password in the OS but this also didn't work in TWRP.
After checking the thread again, I found Unjustified had recommended the TWRP found in his bootloader, which I then downloaded and proceeded to install via fastboot. The installation appeared to go smoothly but after that I was unable to turn on my phone.
After pressing the power button I am presented with either the battery icon or the ZTE logo, which disspears after a few seconds followed by three flashing red lights. The last flashing light seems to be cut off part way.
I thought this might be a dead battery but even after charging for an extended period of time the result is the same.
Any help would be very much appreciated!

mvortex3710 said:
Hullo,
I succesfully installed Lineage with no problems in the OS, but was unable to access TWRP as it asked for a decryption pattern that didn't seem to match the pattern I set on my phone. I then tried a password in the OS but this also didn't work in TWRP.
After checking the thread again, I found Unjustified had recommended the TWRP found in his bootloader, which I then downloaded and proceeded to install via fastboot. The installation appeared to go smoothly but after that I was unable to turn on my phone.
After pressing the power button I am presented with either the battery icon or the Axon logo, which disspears after a few seconds followed by three flashing red lights. The last flashing light seems to be cut off part way.
I thought this might be a dead battery but even after charging for an extended period of time the result is the same.
Any help would be very much appreciated!
Click to expand...
Click to collapse
Your phone doesn't seem to be bricked at all.
That was a known issue many G users encountered...
Just boot into TWRP by pressing Power and volume + or choosing it from the bootloader warning screen and reflash the universal B15 N bootloader.
Reboot your phone and from now on it should boot every N rom just fine :fingers-crossed:
Good luck,
Martin

mischa_martin said:
Your phone doesn't seem to be bricked at all.
That was a known issue many G users encountered...
Just boot into TWRP by pressing Power and volume + or choosing it from the bootloader warning screen and reflash the universal B15 N bootloader.
Reboot your phone and from now on it should boot every N rom just fine :fingers-crossed:
Good luck,
Martin
Click to expand...
Click to collapse
I'm glad to hear it is quite common, but I should mention that the three lights persist when I try to load TWRP... I can only get as far as the ZTE logo.
The bootloader warning also hasn't shown since I attempted to flash TWRP as the phone appears to cut off after showing ZTE.
I will try an overnight charge in case the battery is completely empty and somehow slow charging. But any other suggestions are most welcome.
Kind regards,
James

mvortex3710 said:
I'm glad to hear it is quite common, but I should mention that the three lights persist when I try to load TWRP... I can only get as far as the ZTE logo.
The bootloader warning also hasn't shown since I attempted to flash TWRP as the phone appears to cut off after showing ZTE.
I will try an overnight charge in case the battery is completely empty and somehow slow charging. But any other suggestions are most welcome.
Kind regards,
James
Click to expand...
Click to collapse
You should try some button combinations like
Power + volume down
Power + volume down + volume up
And see how the device reacts
It helps connecting the device to a PC to look up in device manager to determine the mode its booted in

mischa_martin said:
You should try some button combinations like
Power + volume down
Power + volume down + volume up
And see how the device reacts
It helps connecting the device to a PC to look up in device manager to determine the mode its booted in
Click to expand...
Click to collapse
Thanks for the continued help.
I was just trying to connect it to the PC and appear to have made some headway, it started off showing up as qusb_bulk, but after repeatedly deleting that driver I returned to Qualcomm HS-USB QDLoader 9008 (COM6).
As I understand axon7root *should be able to write to the device at this point.
Does this device name give any indication as to the problem?
I wonder if miflash could be used on a G model to unbrick it. I'm happy to restart from stock files.

mvortex3710 said:
Thanks for the continued help.
I was just trying to connect it to the PC and appear to have made some headway, it started off showing up as qusb_bulk, but after repeatedly deleting that driver I returned to Qualcomm HS-USB QDLoader 9008 (COM6).
As I understand axon7root *should be able to write to the device at this point.
Does this device name give any indication as to the problem?
I wonder if miflash could be used on a G model to unbrick it. I'm happy to restart from stock files.
Click to expand...
Click to collapse
As you are in EDL now you have some options.
First I would try to flash a recovery and boot image that is proven to be working fine e.g official twrp https://forum.xda-developers.com/axon-7/development/recovery-official-twrp-zte-axon-7-t3515715 or some A2017G stock boot.img
If that doesn't help you could get in contact with @jcadduono to be a tester for that miflash method. (As your device is already pretty badly bricked)
I don't exactly know how EDL flashing works if it depends on a exact GPT table or not.
But I can say that I flashed every single part of the A2017U bootloader except for NON-HLOS (modem) on my A2017G for each B29 and B15 and it worked just fine. So maybe we just have to exchange the modem file in the EDL package :silly:
If you don't want to take that risk you also could try sending it back to ZTE and hope they don't check the bootloader :fingers-crossed:
(Just a thought: Maybe if the EDL package won't work on your device it will be so heavily damaged ZTE can't check for bootloader unlock and accept it as a warranty case, but don't take that too seriously )
Regards,
Martin

mvortex3710 said:
Thanks for the continued help.
I was just trying to connect it to the PC and appear to have made some headway, it started off showing up as qusb_bulk, but after repeatedly deleting that driver I returned to Qualcomm HS-USB QDLoader 9008 (COM6).
As I understand axon7root *should be able to write to the device at this point.
Does this device name give any indication as to the problem?
I wonder if miflash could be used on a G model to unbrick it. I'm happy to restart from stock files.
Click to expand...
Click to collapse
If you are not afraid then try to use my package for A2017G with MiFlash: https://mega.nz/#!88BjXKhA!TnVSobBw5PkmShSqZ-Ni8MCCbnhJP2SWRNvvXqYHSjc

I really appreciate all this advice!
Looks like the MiFlash is promising. I was able to load the phone into MiFlash from the [EDL] thread. I have just tried the A2017G package provided by djkuz and will report back with any updates.
Just got to the mifavor screen, charging the battery from empty, although quickcharge appears to be functional again.
The charging battery logo is different from before so appears that this bootstack has done the trick.
The flashing red light has gone now, appears to be loading Lineage as before! I'm so grateful for all this help
However, now the unlock pattern is coming up as 'wrong pattern'. Is there anything that can be done? My settings appear to be saved as before (wallpaper and quick settings are the same).
I will attempt to reinstall twrp recovery and fix the lockscreen over adb. Thanks very much for the help. The brick has gone!!

Cannot unlock bootloader, phone not recognized in fastboot (RN7)

I've been trying for almost two weeks to unlock the bootloader on my Redmi Note 7 (Model M1901F7H) because I want to flash the official Global ROM (it has a carrier modified ROM) But Mi unlock REFUSES to recognize the phone when it's connected in fastboot mode.
I've searched the web for a solution and tried a dozen things, including following every single step on this thread: https://forum.xda-developers.com/redmi-note-7/how-to/one-redmi-note-7-unlock-bootloader-t3890751
But I haven't been able to solve the Issue. The device is recognized by all the computers I've been using while plugged in file transfer mode, but none of them recognize the device while it's in fastboot.
Some of the things I've already done include:
Trying 3 different PCs (both AMD and intel)
Disabled signature driver enforcement
Trying USB 2.0 ports
Installing old versions of Mi Unlock
Installing Xiaomi Usb Drivers
Installing 15 seconds ADB drivers
Intalling Mi unlock directly to C://
Enabled OEM unlocking and USB debugging on the device
Linked my Mi Account to the device
Restarting the device and computer multiple times
Re installing drivers over and over again
I know this is the first and supposedly easiest step of the whole process, but I'm stuck and close to giving up (but I really don´t want to).
Can anybody please help me out?

Same here

connect it through a USB hub, it worked for me

Cicciocap94 said:
connect it through a USB hub, it worked for me
Click to expand...
Click to collapse
A usb 2.0 hub did the trick for me, using a usb 3.0 only laptop. It did not work with my usual usb3 hub.

N7Witcher said:
I've been trying for almost two weeks to unlock the bootloader on my Redmi Note 7 (Model M1901F7H) because I want to flash the official Global ROM (it has a carrier modified ROM) But Mi unlock REFUSES to recognize the phone when it's connected in fastboot mode.
I've searched the web for a solution and tried a dozen things, including following every single step on this thread: https://forum.xda-developers.com/redmi-note-7/how-to/one-redmi-note-7-unlock-bootloader-t3890751
But I haven't been able to solve the Issue. The device is recognized by all the computers I've been using while plugged in file transfer mode, but none of them recognize the device while it's in fastboot.
Some of the things I've already done include:
Trying 3 different PCs (both AMD and intel)
Disabled signature driver enforcement
Trying USB 2.0 ports
Installing old versions of Mi Unlock
Installing Xiaomi Usb Drivers
Installing 15 seconds ADB drivers
Intalling Mi unlock directly to C://
Enabled OEM unlocking and USB debugging on the device
Linked my Mi Account to the device
Restarting the device and computer multiple times
Re installing drivers over and over again
I know this is the first and supposedly easiest step of the whole process, but I'm stuck and close to giving up (but I really don´t want to).
Can anybody please help me out?
Click to expand...
Click to collapse
Hello,
sorry to hear that I'll try to help you but I'll need a screenshot shot of your device manager page (assuming you are using a windows PC). Make sure that you connect your phone in fastboot mode before taking the screenshot.

Maybe it's helpfull to install a VPN, in my case flexvpn from playstore, before starting unlock- process...

I solve with an old PC...but I wait for 270h to unlock...

thank you all for your comments, I don't know exactly what happened but Mi unlock recognized the device and asked me to wait for 33 hours to finish the unlocking process.

arunbiju969 said:
Hello,
sorry to hear that I'll try to help you but I'll need a screenshot shot of your device manager page (assuming you are using a windows PC). Make sure that you connect your phone in fastboot mode before taking the screenshot.
Click to expand...
Click to collapse
I don't know how but today Mi unlock recognized the device and asked me to wait 33 hours before unlocking.
This is my first time flashing a device and I'm feeling a bit nervous, if it's not much to ask, could you help me out with some questions? I would be very, very grateful
Can I wait 48 hours before attempting to unlock the bootloader again just to be sure? or it has to be exactly 33 hours?
I plan to flash the global RN7 rom found on en.miui.com/a-234.html to my device (Model M1901F7H), is this the correct one?
How can I lock the bootloader again after flashing this rom? I don't want to keep it unlocked
Do I need a custom recovery? I'd like to keep the stock one if possible
Is there a way to backup my current ROM? In case I need to issue a warranty claim

N7Witcher said:
I don't know how but today Mi unlock recognized the device and asked me to wait 33 hours before unlocking.
This is my first time flashing a device and I'm feeling a bit nervous, if it's not much to ask, could you help me out with some questions? I would be very, very grateful
Can I wait 48 hours before attempting to unlock the bootloader again just to be sure? or it has to be exactly 33 hours?
I plan to flash the global RN7 rom found on en.miui.com/a-234.html to my device (Model M1901F7H), is this the correct one?
How can I lock the bootloader again after flashing this rom? I don't want to keep it unlocked
Do I need a custom recovery? I'd like to keep the stock one if possible
Is there a way to backup my current ROM? In case I need to issue a warranty claim
Click to expand...
Click to collapse
These stuffs seems quite tough and tense at first but its quite easy and safe if you understand what you are doing...and yes I'll answer them one by one
1)The wait period shown by the unlocker is the minimum time you would have to wait to unlock your bootloader so any time after that wait period is fine(But is a chance that even after the wait period the unlocker would give you some error if that happens PM me or quote me)
2)The device code name for Redmi note 7 is lavender so just flash the rom made for lavender I'll give the link to download the stable rom https://sourceforge.net/projects/xi...files/xiaomi.eu/MIUI-STABLE-RELEASES/MIUIv10/
From the above link download the latest version for HMnote7 ,in my opinion European is better than the original one but best rom so far is mokee.
3)You can lock your bootloader using fastboot commands or by flashing the device with miui using Flash tools...but that is not necessary open bootloader is better
4)Yes you need a custom recovery and after flashing the rom from your link the custom recovery will be replaced by the one given in the rom(Don't flash that one! Use the one i gave you if you still want miui but if you like stock then go for mokee)
5)No need to backup it is available online and it can be flashed using flash tools also doing these things and keeping the bootloader unlocked won't void your warranty so there is nothing to loose warranty will be give as per your purchase invoice date! Also if you backup that rom using a custom recovery then it can be use as failsafe if you get into a bootloop or something..but that rom is not mandatory any roms bqckup would do just fine
If you still have doubts I'll be happy to clarify ?

arunbiju969 said:
These stuffs seems quite tough and tense at first but its quite easy and safe if you understand what you are doing...and yes I'll answer them one by one
1)The wait period shown by the unlocker is the minimum time you would have to wait to unlock your bootloader so any time after that wait period is fine(But is a chance that even after the wait period the unlocker would give you some error if that happens PM me or quote me)
2)The device code name for Redmi note 7 is lavender so just flash the rom made for lavender I'll give the link to download the stable rom https://sourceforge.net/projects/xi...files/xiaomi.eu/MIUI-STABLE-RELEASES/MIUIv10/
From the above link download the latest version for HMnote7 ,in my opinion European is better than the original one but best rom so far is mokee.
3)You can lock your bootloader using fastboot commands or by flashing the device with miui using Flash tools...but that is not necessary open bootloader is better
4)Yes you need a custom recovery and after flashing the rom from your link the custom recovery will be replaced by the one given in the rom(Don't flash that one! Use the one i gave you if you still want miui but if you like stock then go for mokee)
5)No need to backup it is available online and it can be flashed using flash tools also doing these things and keeping the bootloader unlocked won't void your warranty so there is nothing to loose warranty will be give as per your purchase invoice date! Also if you backup that rom using a custom recovery then it can be use as failsafe if you get into a bootloop or something..but that rom is not mandatory any roms bqckup would do just fine
If you still have doubts I'll be happy to clarify ?
Click to expand...
Click to collapse
Thank you very much for taking the time to answer all of my questions! You've been very helpful.
I've been thinking about what you wrote but I think I wanna install the official global ROM via Mi Flash. If I select the "clear all and lock" do I risk bricking my device? That's my main concern.
I didn't mention it earlier, but the only reason I want to unlock the Bootloader is so I can flash the official global Rom, (my carrier takes ages to update the rom they install, and it's also full of bloatware) this is my main phone (less than a month old), and while I understand that keeping the bootloader open and using custom ROMS could enhance my user experience, for the time being I want to keep things simple and safe. Maybe in the near future I'll start tinkering with custom rom and recoveries.

Thank you everyone for your suggestions! I don't know exactly what did the trick, but I was able to unlock the bootloader and flash a global ROM. I've encountered some issues with it but that's another topic.
Once again, thank you all!

N7Witcher said:
I've been trying for almost two weeks to unlock the bootloader on my Redmi Note 7 (Model M1901F7H) because I want to flash the official Global ROM (it has a carrier modified ROM) But Mi unlock REFUSES to recognize the phone when it's connected in fastboot mode.
I've searched the web for a solution and tried a dozen things, including following every single step on this thread: https://forum.xda-developers.com/redmi-note-7/how-to/one-redmi-note-7-unlock-bootloader-t3890751
But I haven't been able to solve the Issue. The device is recognized by all the computers I've been using while plugged in file transfer mode, but none of them recognize the device while it's in fastboot.
Some of the things I've already done include:
Trying 3 different PCs (both AMD and intel)
Disabled signature driver enforcement
Trying USB 2.0 ports
Installing old versions of Mi Unlock
Installing Xiaomi Usb Drivers
Installing 15 seconds ADB drivers
Intalling Mi unlock directly to C://
Enabled OEM unlocking and USB debugging on the device
Linked my Mi Account to the device
Restarting the device and computer multiple times
Re installing drivers over and over again
I know this is the first and supposedly easiest step of the whole process, but I'm stuck and close to giving up (but I really don´t want to).
Can anybody please help me out?
Click to expand...
Click to collapse
I have finally understood the problem. What you need to do is not install the ADB Drivers separately, but you need to check for the unknown Android device that is shown under the USB devices when you connect the device (via USB port).
You have to update that driver with the ADB Drivers.
That will only solve the problem of the fastboot detection

Anirban Kopty said:
I have finally understood the problem. What you need to do is not install the ADB Drivers separately, but you need to check for the unknown Android device that is shown under the USB devices when you connect the device (via USB port).
You have to update that driver with the ADB Drivers.
That will only solve the problem of the fastboot detection
Click to expand...
Click to collapse
Can you give detailed instructions on how to "update that driver with the ADB Drivers"? After installing the 15 secs ADB drivers and Xiaomi drivers, my Note 7 is still being recognized as an "Android" device with the yellow caution sign.

Corvus os and Evolution x stops booting midway unless phone is plugged in to a power source.

Hello, recently I came across this strange issue on my Redmi note 7 ( Lavender ) where certain custom roms will just literally stop their boot process midway and the device shuts down inspite of having a fully charged battery. The roms will only boot up normally when my device is connected to a wall adapter or via the usb cable plugged in to my computer. Lineage os v18.1 was the only custom rom as of now which booted normally. Can anybody tell me why is this issue happening and if there is any fix for this strange issue ?
Thanks
Edit
Lineage os v18.1 shuts down all of a sudden without any warning. Even stock MIUI won't boot unless I connect a power source to the device. Also I tried all the known ways of decrypting after flashing Orange fox recovery but no matter what I do, the encryption stays there and I have to format 'data' once or twice to boot up. Lazy flasher dm-verity-opt-encrypt doesn't work. I flashed the latest one from here . Magisk works but doesn't disable force encryption. OTA and dm-verity options from Orange fox recovery doesn't work. This issue is really big. I searched google for possible fixes but none of them were properly related to the issues i am having and not all of the options are specific to my device. Any help will be appreciated !!
Thanks

[email protected] said:
Hello, recently I came across this strange issue on my Redmi note 7 ( Lavender ) where certain custom roms will just literally stop their boot process midway and the device shuts down inspite of having a fully charged battery. The roms will only boot up normally when my device is connected to a wall adapter or via the usb cable plugged in to my computer. Lineage os v18.1 was the only custom rom as of now which booted normally. Can anybody tell me why is this issue happening and if there is any fix for this strange issue ?
Thanks
Edit
Lineage os v18.1 shuts down all of a sudden without any warning. Even stock MIUI won't boot unless I connect a power source to the device. Also I tried all the known ways of decrypting after flashing Orange fox recovery but no matter what I do, the encryption stays there and I have to format 'data' once or twice to boot up. Lazy flasher dm-verity-opt-encrypt doesn't work. I flashed the latest one from here . Magisk works but doesn't disable force encryption. OTA and dm-verity options from Orange fox recovery doesn't work. This issue is really big. I searched google for possible fixes but none of them were properly related to the issues i am having and not all of the options are specific to my device. Any help will be appreciated !!
Thanks
Click to expand...
Click to collapse
That means your battery is done for, even if your battery show good health there's limit on how much Amp. your battery can produce while booting which is insufficient, so better replace battery