How to flash it..I m on pixel experience ROM ..shall I flash it over this rom ..will it give me a bootloop..will I have to flash it always when flashing a ROM?
I m a noob plz help me
I m a noob plz help me
[FIRMWARE][MIUI STABLE][land] For Custom ROMs
- Thread starter dasshubham762
- Start date
Just go to recovery & flash it. If you do it correctly then you won't have to face bootloop.
There's a option in TWRP to mount system. You just have to know English to find it.
Help Me Please!
I lost my MIUI before, how do i install my MIUI back? Can you help me pleaseYou can get latest stable firmware images for land from here. If you are facing Unknown Baseband issue or something like that, then you should flash the latest firmware. If you need any further help, just comment down below.
NOTE: READ THIS CAREFULLY BEFORE PROCEEDING
Baseband Version (Latest):- ***NNS_PACK-1.87716.2.103688.2-V048
DOWNLOADSGLOBAL STABLE
V9.2.2.0 (2018-02-xx)
CHINA STABLE
FLASHING PROCEDURE1. Reboot to Recovery.
2. Select Install and select the firmware zip file which you've downloaded.
3. Swipe to start flashing and wait untill flashing finishes.
4. Reboot and Enjoy.
Thanks to @impulsar for suggesting.
Don't forget to hit Thanks button if you liked it.
XDA:DevDB Information
MIUI Global/China Stable Firmware, Tool/Utility for the Xiaomi Redmi 3S
Contributors
dasshubham762, impulsar, Xiaomi
Version Information
Status: Stable
Created 2017-10-01
Last Updated 2018-02-02
Thanks for OP, but I have found that flashing V9.2.1.0 China Version will make Redmi3s unsupport Standby Mode, thus making background tasks easiler to be killed by system.
Tested on Android 7.1 and 8.1.
Tested on Android 7.1 and 8.1.
I don't think firmware has anything to do with that sort of thing.
Sent from my Xiaomi Redmi 3S using XDA Labs
Please do explain the relation between baseband update and OS multitasking
Should i install firmware or rom first? if i format all partitions in twrp should i install firmware again? everytime that i am going to install a new rom i need install firmware? or just once and i can install every rom i want?
WARNING FOR PEOPLE WITH EDL-UNLOCKED BOOTLOADER !!!!!
If you have an unoficially unlocked device which was unlocked by flashing bootloader over EDL (by flashing unofficial appsboot which allows "fastboot oem unlock-go") be VERY CAREFUL! This package also updates bootloader and by applying it, the bootloader will be locked again. Additionally this new bootloader version won't allow "fastboot oem edl" to enter EDL mode and the only way to enter it would probably be those two test points on the motherboard.
This locked bootloader then won't load your custom rom and won't allow you to do "fastboot boot" command to enter (TWRP) recovery.
I was stupid enough to run official Mi unlock tool and it unlocked this new bootloader, but wiped something (either /data or some secure hw storage storing encryption keys). In the end, my original custom ROM boots but I can't mount my encrypted data partition (the same using TWRP - it behaves like if I entered a wrong password). :'( I have almost everything backed up but a few things were lost by this..
Looking at the "META-INF/com/google/android/updater-script" in this .zip, removing appsboot lines would skip the update of the bootloader and prevent this problem. Lesson learned - I will always inspect these scripts before flashing any zip over a running system.
If you have an unoficially unlocked device which was unlocked by flashing bootloader over EDL (by flashing unofficial appsboot which allows "fastboot oem unlock-go") be VERY CAREFUL! This package also updates bootloader and by applying it, the bootloader will be locked again. Additionally this new bootloader version won't allow "fastboot oem edl" to enter EDL mode and the only way to enter it would probably be those two test points on the motherboard.
This locked bootloader then won't load your custom rom and won't allow you to do "fastboot boot" command to enter (TWRP) recovery.
I was stupid enough to run official Mi unlock tool and it unlocked this new bootloader, but wiped something (either /data or some secure hw storage storing encryption keys). In the end, my original custom ROM boots but I can't mount my encrypted data partition (the same using TWRP - it behaves like if I entered a wrong password). :'( I have almost everything backed up but a few things were lost by this..
Looking at the "META-INF/com/google/android/updater-script" in this .zip, removing appsboot lines would skip the update of the bootloader and prevent this problem. Lesson learned - I will always inspect these scripts before flashing any zip over a running system.
Last edited:
Yes this is true.But we still have ways to enter EDL I.e. testpoint on the motherboard,etc.Also, any official firmware recovery will update aboot and lock the device down. So the warnings are already mentioned in all threads of unofficial bootloader versions.
My baseband version is ...v40. Which version is this ?
Now using viper nought ROM..I have low signal and network signal problem...which one I have to flash???
Now using viper nought ROM..I have low signal and network signal problem...which one I have to flash???
Current global v51
---------- Post added at 06:07 PM ---------- Previous post was at 06:06 PM ----------
Nope, still MM