Is TWRP out for Redmi Note 9? - Redmi Note 9S / Note 9 Pro (Indian Model) Question

Okay, I have been looking everywhere... Is Official TWRP out for Note 9 yet? I dont want to install unofficial ROM, and compiling my own version is too much time. If its out, can someone throw me with a link? If not, what do you think, when will they upload it?
Thanks for you answers.

https://twrp.me/Devices/

zerodeaths000 said:
Okay, I have been looking everywhere... Is Official TWRP out for Note 9 yet? I dont want to install unofficial ROM, and compiling my own version is too much time. If its out, can someone throw me with a link? If not, what do you think, when will they upload it?
Thanks for you answers.
Click to expand...
Click to collapse
No, no official TWRP out there, yet. I don't know for the RN9 (merlin), but for the RN9s/Pro India (curtana) there are LR TWRP, LOS recovery and PBRP out. For the RN9Pro global (joyeuse) and RN9ProMAX(excalibur) only PBRP.
Don't flash a recovery for curtana on a joyeuse or an excalibur! It could hardbrick the phone and only a service centre or a MI account with special rights to flash in EDL mode (which Xiaomi doesn't give out anymore) would be able to fix that!
There are already many ROMs for the curtana out there, but for the others only a few.
For the RN9(merlin) is a sperate forum here on XDA.

Tried all sorts, none worked.
Until I found this.
https://www.cyanogenmods.org/twrp-recovery-redmi-note-9-pro/
Offered there for Redmi Note 9 Pro / 9s [curtana]
But also works on my Redmi Note 9 Pro Joyeuse.
Backup was created without an error message.
Restoring data also worked correctly.
All other versions had a problem with this and issued an error and the data was of course destroyed.
The misc.bin is important for the installation, which was not included in all other versions
Ps:
Point 8 does not work there,
fastboot oem reboot-recovery
fastboot does not know this command.
Then just by
fastboot reboot
reboot and quickly via buttons
Power + volume up
boot into recovery mode

Thanks!
tinaeire said:
No, no official TWRP out there, yet. I don't know for the RN9 (merlin), but for the RN9s/Pro India (curtana) there are LR TWRP, LOS recovery and PBRP out. For the RN9Pro global (joyeuse) and RN9ProMAX(excalibur) only PBRP.
Don't flash a recovery for curtana on a joyeuse or an excalibur! It could hardbrick the phone and only a service centre or a MI account with special rights to flash in EDL mode (which Xiaomi doesn't give out anymore) would be able to fix that!
There are already many ROMs for the curtana out there, but for the others only a few.
For the RN9(merlin) is a sperate forum here on XDA.
Click to expand...
Click to collapse
Thanks for reminding, I didn't even know I had a joyeuse device, with QJZEUXM rom. I wanted to flash curtana... You saved me

nostra_DE said:
Tried all sorts, none worked.
Until I found this.
https://www.cyanogenmods.org/twrp-recovery-redmi-note-9-pro/
Offered there for Redmi Note 9 Pro / 9s [curtana]
But also works on my Redmi Note 9 Pro Joyeuse.
Backup was created without an error message.
Restoring data also worked correctly.
All other versions had a problem with this and issued an error and the data was of course destroyed.
The misc.bin is important for the installation, which was not included in all other versions
Ps:
Point 8 does not work there,
fastboot oem reboot-recovery
fastboot does not know this command.
Then just by
fastboot reboot
reboot and quickly via buttons
Power + volume up
boot into recovery mode
Click to expand...
Click to collapse
What ROM does your device use?

@zerodeaths000
Redmi Note 9 Pro – EEA Stable ROM
V11.0.4.0.QJZEUXM
https://mirom.ezbox.idv.tw/en/phone/joyeuse/
If you actually have the ROM QJZEUXM, then your phone is a Redmi Note 9 Pro
Without Pro, it had to have the following ROM QJOEUXM
https://mirom.ezbox.idv.tw/en/phone/merlin/
So never overlook the Pro, Pro and not Pro differ.

nostra_DE said:
@zerodeaths000
Redmi Note 9 Pro – EEA Stable ROM
V11.0.4.0.QJZEUXM
https://mirom.ezbox.idv.tw/en/phone/joyeuse/
If you actually have the ROM QJZEUXM, then your phone is a Redmi Note 9 Pro
Without Pro, it had to have the following ROM QJOEUXM
https://mirom.ezbox.idv.tw/en/phone/merlin/
So never overlook the Pro, Pro and not Pro differ.
Click to expand...
Click to collapse
I have a PRO, bought in Hungary, and even looked up that I had that ROM in the settings! Thanks for your reply!
Also, one more question. That ROM that you have provided, In case anything goes wrong, how can I flash it back?(MIUI 11.0.4.0)

The best way is by fastboot, see my post # 6 here
https://forum.xda-developers.com/re...9-pro-dead-t4141055/post83194647#post83194647
https://mirom.ezbox.idv.tw/en/phone/joyeuse/
Fastboot
joyeuse_eea_global_images_V11.0.4.0.QJZEUXM_20200715.0000.00_10.0_eea_dcfb9c0b60.tgz
https://bigota.d.miui.com/V11.0.4.0...EUXM_20200715.0000.00_10.0_eea_dcfb9c0b60.tgz

nostra_DE said:
The best way is by fastboot, see my post # 6 here
https://forum.xda-developers.com/re...9-pro-dead-t4141055/post83194647#post83194647
https://mirom.ezbox.idv.tw/en/phone/joyeuse/
Fastboot
joyeuse_eea_global_images_V11.0.4.0.QJZEUXM_20200715.0000.00_10.0_eea_dcfb9c0b60.tgz
https://bigota.d.miui.com/V11.0.4.0...EUXM_20200715.0000.00_10.0_eea_dcfb9c0b60.tgz
Click to expand...
Click to collapse
Unfortunately, I cant get MiFlash tool to work(Doesn't install the drivers after a long waiting), so I'm going to have to do it in fastboot(command line). Also, I got the .zip version, but if required, I can get the tar file.

Please refresh the forum link I gave here again.
I accidentally wrote Power + Up for the fastboot mode instead of Power + down
Just seen and corrected.
---------------------------------
The * .zip are only for recovery or OTA flash.
For fastboot with flashtool you absolutely need the content from * .tgz
Winrar completely unpacks folders and files that you need for fastboot.
7-zip, however, still displays a * .tar archive, which could then be flashed with the fastboot command line. Not tried myself.
Ps: driver problem maybe an administrator problem?
Start setup as administrator.
Or a snake oil problem (third-party Antivir)?

nostra_DE said:
Please refresh the forum link I gave here again.
I accidentally wrote Power + Up for the fastboot mode instead of Power + down
Just seen and corrected.
---------------------------------
The * .zip are only for recovery or OTA flash.
For fastboot you absolutely need the content from * .tgz
Winrar completely unpacks folders and files that you need for fastboot.
7-zip, however, still displays a * .tar archive, which could then be flashed with the fastboot command line. Not tried myself.
Ps: driver problem maybe an administrator problem?
Start setup as administrator.
Or a snake oil problem (third-party Antivir)?
Click to expand...
Click to collapse
Got it. I can fix the driver issue for sure. I will try this method, with the cyanogenmod link you gave. I will notify you when its done, because I have 3 more days until I can unlock the bootloader. Hope I won't have to flash the firmware again, and that nothing goes wrong.
One more thing though
"The folder with the extracted files must be on the root of a partition, otherwise there are error messages"
Does this mean that the files found in the tar file have to be extracted directly to C:\ or any other partition?

Partition doesn't matter, it doesn't have to be C :
I get an error message in the not root, probably because the path name was too long.
Didn't investigate further, but copied it straight into the root.
Looks like.
Before that, the folder was on the desktop, which of course made the path name very long.
Maybe the long folder name would have been enough
joyeuse_eea_global_images_V11.0.4.0.QJZEUXM_20200715.0000.00_10.0_eea
shorten by renaming.

Related

Bootloop Redmi 5 Plus global

Hi guys,
I've purchased a Redmi 5 Plus (MEG7) as my new backup phone (2nd hand). The Mi account of the previous owner is still bound to the device, but the phone did shut down on the way (ran out of juice) and never came back. In other words it is stuck in a bootloop at the android screen.
What I already did:
Used Xiaomi ADB to sideload both global stable and global developer roms (not to mention most of the past global developer roms and some china stable/developer roms), no love.
Unlocking the bootloader didn't work either, since I can't add my account to the phone.
The test point method was able to deliver a clear flash (tried China stable, China developer, Global stable and Global developer roms and most of the past relevant roms, you get the idea) with and without persist.img edit.
Tweaking fastboot ROMs with TWRP as recovery.img, still nothing.
I'm open to any new bright ideas besides going to a Mi Center or any other "Let the store fix it" suggestion.
Thanks
exigon said:
... I'm open to any new bright ideas besides going to a Mi Center or any other "Let the store fix it" suggestion ...
Click to expand...
Click to collapse
Have you tried installing a custom ROM - eg AOSP/LOS based?
I'd like to
DarthJabba9 said:
Have you tried installing a custom ROM - eg AOSP/LOS based?
Click to expand...
Click to collapse
That's what I'd like to do in the end, but since I have a locked bootloader, xiaomi's gorgeous beast of a recovery and no way to bind my account without entering the system, it's pretty much a stalemate.
If there was another fastboot rom besides MIUI, I'd love to try it.
https://forum.xda-developers.com/re...fastboot-rom9008-edlh2osbeta19-vince-t3890747 this resulted in a MiFlash error message.
exigon said:
That's what I'd like to do in the end, but since I have a locked bootloader, xiaomi's gorgeous beast of a recovery and no way to bind my account without entering the system, it's pretty much a stalemate.
Click to expand...
Click to collapse
Did you try to flash a stock Xiaomi fastboot ROM with the mi flash tool?
yes
DarthJabba9 said:
Did you try to flash a stock Xiaomi fastboot ROM with the mi flash tool?
Click to expand...
Click to collapse
Flashing the fastboot stock stable global and fastboot stock developer roms was the first thing I did, with a bootloop as the result.
exigon said:
Flashing the fastboot stock stable global and fastboot stock developer roms was the first thing I did, with a bootloop as the result.
Click to expand...
Click to collapse
Hmm ... if flashing with the mi flash tool gives you a bootloop, then I think something is seriously amiss. Unfortunately, I am out of ideas.
exigon said:
Hi guys,
I've purchased a Redmi 5 Plus (MEG7) as my new backup phone (2nd hand). The Mi account of the previous owner is still bound to the device, but the phone did shut down on the way (ran out of juice) and never came back. In other words it is stuck in a bootloop at the android screen.
What I already did:
Used Xiaomi ADB to sideload both global stable and global developer roms (not to mention most of the past global developer roms and some china stable/developer roms), no love.
Unlocking the bootloader didn't work either, since I can't add my account to the phone.
The test point method was able to deliver a clear flash (tried China stable, China developer, Global stable and Global developer roms and most of the past relevant roms, you get the idea) with and without persist.img edit.
Tweaking fastboot ROMs with TWRP as recovery.img, still nothing.
I'm open to any new bright ideas besides going to a Mi Center or any other "Let the store fix it" suggestion.
Thanks
Click to expand...
Click to collapse
You have a serious problem here cause if you flash succesfully any miui rom then Xiaomi will ask for the password to the last account binded.
I guess that the one method to bypass this is using some box/dongle in a service center by formatting eMMc, if you are now the new owner this action will be fine.
There´s only one thing that forgot to do trying to install a custom rom when my R5+ was locked yet. A short history first: some older Xiaomi devices as one that I had as a second device; Mi Max(2016) accepted to replace TWRP instead of stock recovery and flashing it through MiFlash tool without any problem but newer devices will refuse to boot.
I don´t know if this work, maybe bootloader redirects to fastboot mode instead of try to boot but anyway; Rename TWRP.img as boot.img (not recovery.img) and replace for the boot.img in the fasboot rom folder, after of flash try to reboot normally.

Need to un-Bricking after de-bloating of rooted Redmi Note9S with EU ROM

After unlocking, I installed EU rom via adb, the installed unofficial TWRP 3.4.1b -0506 and rooted.
I used the phone without any probems for some days .
I then decided to get rid of MI software. After uninstalling a lot of software using App Uninstaller by Jumobile.
Also after that the phone worked well for an hour or two, but after a reboot the phone always goes into Fastboot.
I still can go into TWRP. When I try to install Curtana Global from external SD card, TWRP returns "Install zip Successful" but with an error message
"Failed to mount "/vendor" (Read-only file system)
I am very grateful for any help to unbrick my phone
Bruno
brufi said:
After unlocking, I installed EU rom via adb, the installed unofficial TWRP 3.4.1b -0506 and rooted.
I used the phone without any probems for some days .
I then decided to get rid of MI software. After uninstalling a lot of software using App Uninstaller by Jumobile.
Also after that the phone worked well for an hour or two, but after a reboot the phone always goes into Fastboot.
I still can go into TWRP. When I try to install Curtana Global from external SD card, TWRP returns "Install zip Successful" but with an error message
"Failed to mount "/vendor" (Read-only file system)
I am very grateful for any help to unbrick my phone
Bruno
Click to expand...
Click to collapse
Hello
Why not to flash a fastboot rom via Miflash? Phone will be from clean basis.
Test the new Miflashpro if you have time.
Good luck.
Note 9S not yet listed in Miflashpro; fastboot rom not found
thanks Lolo93939 for the input.
I found miflashpro under a com domain with the same name and installed the most recent version 4.3.1220.29. Selection of device does not include Redmi Not 9 S or Pro, accordingly moflashpro can not be used as of today for note 9S.
I then downloaded XIAOMIFlashTool from the com domain of the same name: miflash20191206.zip and installed
Downloaded latest fastboot rom from mifirm net / model / curtana.ttt which is V11.0.7.0.QJWMIXM.
unziped the rom 2 times until I had a folder with subfolder "Images" and shortened the folder name to V11.0.7.0.QJWMIXM and copied it under new folder c:XIAOMI
Executed XiaoMIFlash.exe, selected V11.0.7.0.QJWMIXM folder, selected "clean all" at bottom (to make sure the device is not locked again), then connected phone in Fastboot screen, refreshed in XiaoMiFlash and flashed.
Flash ended with error but phone seems to be up and running again.
brufi said:
Lolo93939, i would love too. I have searched for 3 hours now and did not find a functioning Miflash. I tried the 2 latest versions from xiaomiflash com but both give out an error "could not find flash script."
I find Stable roms for curtana but all links to fastboot roms end in 404 pages.
Could you point me to source of Miflash and a fastboot rom?
Thanks a lot!
Click to expand...
Click to collapse
It doesn't find your computer path for stating flashing.
Did you unzip the tgz and the tar file?
Place the unzipped result close to your computer C: directory and clean as much as possible the name.
That MUST work...
https://mirom.ezbox.idv.tw/en/phone/curtana/
Thank you! I did as suggested.
all worked well, but got
error: not catch checkpoint (\$fastoot -s . *lock).flash is not done
still the phone is up and running again, so things seem to be good.
:good:
brufi said:
Thank you! I did as suggested.
all worked well, but got
error: not catch checkpoint (\$fastoot -s . *lock).flash is not done
still the phone is up and running again, so things seem to be good.
:good:
Click to expand...
Click to collapse
Yeah, had the "catch checkpoint" error, too.
Don't mind, phone is running without problems after that, also when you got this error.
Biggest difference I've noticed is that I had to restart the device manually after flashing (normally without this error, it would reboot automatically) ?
By the way, have you edited your posts a few times?
That makes it hard for other users to understand the whole problem and on that way maybe your posts can't help other users with same problem, so please don't edit/change whole postings ?

Question Xiaomi Redmi Note 10: how to root

Does anyone have a guide on how to root a Xiaomi Redmi Note 10? I’m a novice Android user so any help will be appreciated. Thanks
You will need a Windows PC with Fastboot and Mi unlock tool installed. Here is what you could do without a TWRP to root through Magisk:
Apply for the Unlock process. This will take 167 hours and will factory reset your device. Backup your data before you do this. After the waiting period unlock your Bootloader.
Download your matching or newer Fastboot firmware from here. I assumed you have note 10 non 5G (mojito) based on that screenshot, if not, then that website has it for different varieties as well.
The Fastboot firmware is in .tgz format. Keep a copy for future screw ups just in case (will rescue you). Extract that archived folder and find boot.img inside.
Copy that .img to your phone, and download magisk manager 21.0 or newer and install it.
When opening the Manager on your phone for the first time, it'll prompt you to install itself, choose select and patch file and select the boot.img you copied to your phone earlier.
After it does that successfully, you will find a file called magisk_patched.img on the root of internal storage. Copy that patched .img back to your PC.
Reboot your phone to fastboot mode and connect to PC, flash that patched boot.img using:
Code:
fastboot flash boot magisk_patched.img
If flashed successfully, reboot your device and update/further install magisk.
Done, Your device is rooted !!!
P.S. Don't forget to mark this answer as solved by clicking the check mark beside it if it solved your question so anyone can see this in the future.
Slim K said:
You will need a Windows PC with Fastboot and Mi unlock tool installed. Here is what you could do without a TWRP to root through Magisk:
Apply for the Unlock process. This will take 167 hours and will factory reset your device. Backup your data before you do this. After the waiting period unlock your Bootloader.
Download your matching or newer Fastboot firmware from here. I assumed you have note 10 non 5G (mojito) based on that screenshot, if not, then that website has it for different varieties as well.
The Fastboot firmware is in .tgz format. Keep a copy for future screw ups just in case (will rescue you). Extract that archived folder and find boot.img inside.
Copy that .img to your phone, and download magisk manager 21.0 or newer and install it.
When opening the Manager on your phone for the first time, it'll prompt you to install itself, choose select and patch file and select the boot.img you copied to your phone earlier.
After it does that successfully, you will find a file called magisk_patched.img on the root of internal storage. Copy that patched .img back to your PC.
Reboot your phone to fastboot mode and connect to PC, flash that patched boot.img using:
Code:
fastboot flash boot magisk_patched.img
If flashed successfully, reboot your device and update/further install magisk.
Done, Your device is rooted !!!
P.S. Don't forget to mark this answer as solved by clicking the check mark beside it if it solved your question so anyone can see this in the future.
Click to expand...
Click to collapse
Thanks mate. Will wait for the phone to be unlocked then will try these steps.
hello, I followed the whole procedure and the phone only reboots in bootloop or after several reboots it brings me back to Fastboot
Slim K said:
You will need a Windows PC with Fastboot and Mi unlock tool installed. Here is what you could do without a TWRP to root through Magisk:
Apply for the Unlock process. This will take 167 hours and will factory reset your device. Backup your data before you do this. After the waiting period unlock your Bootloader.
Download your matching or newer Fastboot firmware from here. I assumed you have note 10 non 5G (mojito) based on that screenshot, if not, then that website has it for different varieties as well.
The Fastboot firmware is in .tgz format. Keep a copy for future screw ups just in case (will rescue you). Extract that archived folder and find boot.img inside.
Copy that .img to your phone, and download magisk manager 21.0 or newer and install it.
When opening the Manager on your phone for the first time, it'll prompt you to install itself, choose select and patch file and select the boot.img you copied to your phone earlier.
After it does that successfully, you will find a file called magisk_patched.img on the root of internal storage. Copy that patched .img back to your PC.
Reboot your phone to fastboot mode and connect to PC, flash that patched boot.img using:
Code:
fastboot flash boot magisk_patched.img
If flashed successfully, reboot your device and update/further install magisk.
Done, Your device is rooted !!!
P.S. Don't forget to mark this answer as solved by clicking the check mark beside it if it solved your question so anyone can see this in the future.
Click to expand...
Click to collapse
what about vbmeta?
0purple said:
what about vbmeta?
Click to expand...
Click to collapse
I do not understand the question
0purple said:
what about vbmeta?
Click to expand...
Click to collapse
Not really necessary for Xiaomi devices (apart from the Mi series) as far as I know, but maybe they changed that with the upgrade to android 11?
titifayls said:
I do not understand the question
Click to expand...
Click to collapse
He meant disabling AVB 2.0 by flashing the vbmeta.img from the downloaded fastboot firmware by using:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
I personally have encountered many problems using Magisk 22.0 stable version, if you're using that, then either update to the canary version (you can switch the update channel in the manager settings) or use the older version 21.4.
If all of the above fails, just reflash the stock boot.img and your phone will boot normally.
Slim K said:
Not really necessary for Xiaomi devices (apart from the Mi series) as far as I know, but maybe they changed that with the upgrade to android 11?
He meant disabling AVB 2.0 by flashing the vbmeta.img from the downloaded fastboot firmware by using:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
I personally have encountered many problems using Magisk 22.0 stable version, if you're using that, then either update to the canary version (you can switch the update channel in the manager settings) or use the older version 21.4.
If all of the above fails, just reflash the stock boot.img and your phone will boot normally.
Click to expand...
Click to collapse
precisely I did not take magisk v22 but v21, moreover I have exactly the same version as the first poster is 12.0.1 RKGEUXM.
To root I took the boot.img from version 12.0.2, was it an error?
I tried to reflash the original boot.img file from v12.0.2 but still in bootloop
I can not find anywhere where to take my original version yet up to date v12.0.1
@titifayls The original poster had version
V12.0.1.0.RKGMIXM (Global) while you claim to have downloaded
V12.0.2.0.RKGEUXM (European) which are not interchangeable. If you want to use either global or eu. Then you would need to flash the full firmware, you can't flash the boot.img from EU to ROM of global. It won't boot.
If you don't really remember which version came with your device, then reply to me again and I can give you further instructions. Tell me which OS are you using to access fastboot and if you want to preserve your data.
Slim K said:
@titifayls The original poster had version
V12.0.1.0.RKGMIXM (Global) while you claim to have downloaded
V12.0.2.0.RKGEUXM (European) which are not interchangeable. If you want to use either global or eu. Then you would need to flash the full firmware, you can't flash the boot.img from EU to ROM of global. It won't boot.
If you don't really remember which version came with your device, then reply to me again and I can give you further instructions. Tell me which OS are you using to access fastboot and if you want to preserve your data.
Click to expand...
Click to collapse
ha , sorry indeed I may have made a mistake, now I don't remember my exact version, it seemed to me that it was EU but in 12.0.1
I use ABD in fastboot and yes I would like to keep all my data that I did not save before wanting to root: /
I bought the phone on aliexpress, I am French, can I look on the box if I have any info on the version?
titifayls said:
ha , sorry indeed I may have made a mistake, now I don't remember my exact version, it seemed to me that it was EU but in 12.0.1
I use ABD in fastboot and yes I would like to keep all my data that I did not save before wanting to root: /
I bought the phone on aliexpress, I am French, can I look on the box if I have any info on the version?
Click to expand...
Click to collapse
I asked if you're using windows or linux to connect to your phone. About losing data, maybe a clean flash could be required, but trying first won't hurt.
Here is how you do it: (you can use the downloaded fastboot firmware, because your device is unlocked, so region differences won't matter that much when flashing full firmware):
Inside that .tgz archive (that you unarchived) you'll find a script called flash_all_except_data_storage.bat for windows or flash_all_except_data_storage.sh for linux. (Do not use the flash_all_lock.bat/.sh script or risk a hard brick, so read carefully this time!!!!)
Connect your device in fastboot mode and open a CMD/Terminal where those scripts and the rest of the firmware files are. Use fastboot devices to make sure device is recognized.
If it is, then type in fastboot followed by dragging and dropping the flash_all_except _data_storage.bat to your CMD/terminal and press Enter. The process should begin automatically. If you get an error, make sure to have typed a space after the fastboot command and before the dropped script.
If it takes a long time during flash of super, don't panic!! Super.img is a very big file
Done!
If it still bootloops after that, then use the flash_all.bat script (will factory reset your phone and delete data)
It doesn't matter, it gives me the list of commands but doesn't launch anything
Wouldn't it be better to put fastboot flash?
don't bother, I'll take miflash, it'll be easier
I delivered an eea_global_images_V12.0.2.0.RKGEUXM rom with miflash by putting flash_all_except_data_storage.
I recovered everything at startup, my applications everything, so I redid the manipulation for the root and now everything works, perfect
thank you
I did the above process successfully.
Also if new update comes out, the process must be done again (not including the unlocking part of course).
The ROMs are posted here
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Slim K said:
Not really necessary for Xiaomi devices (apart from the Mi series) as far as I know, but maybe they changed that with the upgrade to android 11?
He meant disabling AVB 2.0 by flashing the vbmeta.img from the downloaded fastboot firmware by using:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
I personally have encountered many problems using Magisk 22.0 stable version, if you're using that, then either update to the canary version (you can switch the update channel in the manager settings) or use the older version 21.4.
If all of the above fails, just reflash the stock boot.img and your phone will boot normally.
Click to expand...
Click to collapse
so if i use latest magisk v22.1 , do i have to disable something like vbmeta.img or not ? or it is onli Mi Series that need to disable vbmeta.img ?
how to see how many hours left to unlock the phone ? i kinda forgot about it, it is my 1st MIUI device beside Xiaomi Mi A1
pihpih95 said:
so if i use latest magisk v22.1 , do i have to disable something like vbmeta.img or not ? or it is onli Mi Series that need to disable vbmeta.img ?
Click to expand...
Click to collapse
Only MI series need that. You should not have to do that. Also yes, I meant to say that 22.0 stable magisk can make the patched boot.img unbootable. Using the 22.1 canary is the way to go.
pihpih95 said:
how to see how many hours left to unlock the phone ? i kinda forgot about it, it is my 1st MIUI device beside Xiaomi Mi A1
Click to expand...
Click to collapse
You would need to connect your phone in fastboot mode and use MI unlock tool again. It'll tell you how many hours left. Usually, you just need to wait exactly one week or 168 hours.
Slim K said:
Only MI series need that. You should not have to do that. Also yes, I meant to say that 22.0 stable magisk can make the patched boot.img unbootable. Using the 22.1 canary is the way to go.
You would need to connect your phone in fastboot mode and use MI unlock tool again. It'll tell you how many hours left. Usually, you just need to wait exactly one week or 168 hours.
Click to expand...
Click to collapse
about mi unlock tool , what version that show how many hours left ? i use latest version and it show nothing on the tool , if i remember correctly the oldest version show the time remaining to unlock , sorry if i mistaken something here >.<
pihpih95 said:
about mi unlock tool , what version that show how many hours left ? i use latest version and it show nothing on the tool , if i remember correctly the oldest version show the time remaining to unlock , sorry if i mistaken something here >.<
Click to expand...
Click to collapse
I used the latest as well. Most of the time, it errors out and I can't see the time left, but sometimes it works. Don't forget, you're giving them your imei for the freedom of your phone. Those imei's must be stored on Chinese servers and the tool must query those servers to get any info, depending on your country it may not work at all.
My experience with using an older tool has been very bad, the time was extended to 2 weeks instead of one on an another Xiaomi device. Avoid doing that and wait the requested time first.
After following the instruction my phone keeps rebooting.
I tried the flash_all.bat without success. What could I do?

Redmi note 5 - TWRP(vince)

Hi, I have Redmi Note 5 and I tried to install TWRP recovery(twrp-3.5.2_9-0-vince.img). But every time in the TWRP it is telling that "Internal Memory" is showing as 0 MB and I am unable to change it. It would be pleasure if you know a method to overcome this issue. Thank you.
Baranetharan said:
Hi, I have Redmi Note 5 and I tried to install TWRP recovery(twrp-3.5.2_9-0-vince.img). But every time in the TWRP it is telling that "Internal Memory" is showing as 0 MB and I am unable to change it. It would be pleasure if you know a method to overcome this issue. Thank you.
Click to expand...
Click to collapse
I think you have to format your data partition, but then you will lose all. Backup first all photos and other things. And why not orange fox?
joke19 said:
I think you have to format your data partition, but then you will lose all. Backup first all photos and other things. And why not orange fox?
Click to expand...
Click to collapse
Redmi Note 5 - Whyred or Vince?
Hello, just come over to ask, want to buy my wife and me new phones and found the xiaomi redmi note 5 (global version). Specs are good enought for us, so want to buy it and want (of course) flash lineageOS but now i am confused with...
forum.xda-developers.com
Thank you so much for the help.
joke19 said:
Redmi Note 5 - Whyred or Vince?
Hello, just come over to ask, want to buy my wife and me new phones and found the xiaomi redmi note 5 (global version). Specs are good enought for us, so want to buy it and want (of course) flash lineageOS but now i am confused with...
forum.xda-developers.com
Click to expand...
Click to collapse
OrangeFOx recovery is also asking for a PIN, that why I am thinking.
Ok, I will prepare to format my device the help.
Thank you so much for the help.
Help request.
Situation:
- Redmi 4X (Global, santoni), bootloader unlocked,
- flash recovery TWRP, v. 3.6.0_9-0 performed by ADB and using "Temporary" same
versions of TWRP,
- flash recovery TWRP, v. 3.5.1_9-0 performed by ADB and using "Temporary" same
versions of TWRP,
- Backup partition recovery is used to check if the flash has actually taken place.
Always with a positive result (each version is checked with "sh2")!
- Reboot into recovery or shutdown and put into recovery mode, always with a positive
result - TWRP recovery works!
- Once the OS has been booted at least once, the contents of the partition recovery will
take effect immediately returns to stock recovery - ALWAYS!
- an attempt was made with flash stock recovery - the result was adequate,
- all these experiments took place even after using SW MiFlash20210226 with parameter
Save user data. Results without change - always returned stock recovery.
Thank you for your help (please excuse your English level - thank you)
nemohouci said:
Help request.
Situation:
- Redmi 4X (Global, santoni), bootloader unlocked,
- flash recovery TWRP, v. 3.6.0_9-0 performed by ADB and using "Temporary" same
versions of TWRP,
- flash recovery TWRP, v. 3.5.1_9-0 performed by ADB and using "Temporary" same
versions of TWRP,
- Backup partition recovery is used to check if the flash has actually taken place.
Always with a positive result (each version is checked with "sh2")!
- Reboot into recovery or shutdown and put into recovery mode, always with a positive
result - TWRP recovery works!
- Once the OS has been booted at least once, the contents of the partition recovery will
take effect immediately returns to stock recovery - ALWAYS!
- an attempt was made with flash stock recovery - the result was adequate,
- all these experiments took place even after using SW MiFlash20210226 with parameter
Save user data. Results without change - always returned stock recovery.
Thank you for your help (please excuse your English level - thank you)
Click to expand...
Click to collapse
I recommend this recovery.
Xiaomi Redmi 4X (santoni) build releases | OrangeFox Recovery Downloads
Orangefox recovery for Xiaomi Redmi 4X (santoni)
orangefox.download
You use mi flash tool as last? Then the customer recovery will be replaced. Mi flash tool, development settings, OEM unlock and flash your recovery over fastboot. Here is a good guide, but don't use the recovery from this site.
[All-in-One] Redmi Note 7 (lavender): Unlock Bootloader, Flash TWRP, Root, Flash ROM
Dear Redmi Note 7 user, I'm not responsible if anything happens to your device. If you execute these AiO procedures properly then you shouldn't face any problems. Before you proceed please back up all your important data and make sure that...
forum.xda-developers.com
Begin by point c

[SOLVED] Tried restoring a original firmware to my Redmi note 9s but I'm unable to.

Hello, I'm having trouble restoring my Redmi note 9s to the stock firmware, basically I installed a custom rom but I want to revert back to stock since it has annoying problems and I'm fed up dealing with them.
I tried downloading a stock firmware and installing it with official Xiaomi tools but I just can't install them for my life, even got a bootloop, thought bricked the phone and that scared me lol. (it failed to install the stock firmware halfway)
My problem relies on the official tool not working and the drivers not working, the tool detected my phone after troubleshooting for like 4 hours searching a driver and trying all the Xiaomi flash tool versions I found, but it just won't install the official firmware, always giving some error.
If anyone here is kind enough to maybe direct me to a guide that works or just tell me what worked for them that would be appreciated, I just want to finally install Global firmware on my phone.
Thanks!
Check here that everything is correct.
Post the Miflash log, miflash log file.
MIFLASH[GUIDE]⚙ USE XIAOMI FLASH TOOL
FOR ALL XIAOMI BOOTLOADER MUST BE UNLOCKED https://new.c.mi.com/global/post/101245 https://en.miui.com/unlock/index.html ----------------------------------------------------------------------------------------------------------- All your data...
forum.xda-developers.com
If it's showing timeout error you may try miflash 2018 version. If it bootloop after flashing try miui 14 stock rom.
NOSS8 said:
Check here that everything is correct.
Post the Miflash log, miflash log file.
MIFLASH[GUIDE]⚙ USE XIAOMI FLASH TOOL
FOR ALL XIAOMI BOOTLOADER MUST BE UNLOCKED https://new.c.mi.com/global/post/101245 https://en.miui.com/unlock/index.html ----------------------------------------------------------------------------------------------------------- All your data...
forum.xda-developers.com
Click to expand...
Click to collapse
Okay, just so you know, I installed a miui custom rom from here and have been running that since, so I will need to back up my phone, install miflash and try to finally get back into the stock rom.
When I'm done with that I'll try installing the stock firmware and post it to you
Muhammad Juman said:
If it's showing timeout error you may try miflash 2018 version. If it bootloop after flashing try miui 14 stock rom.
Click to expand...
Click to collapse
The last time I tried it was the miui 13 but it was not a timeout error, it was weird, I think it detected my phone and all that but when it started installing, it gave out an error when it was maybe half way and hung, luckily I have a custom recovery so I realized I didn't brick it and just installed a custom miui 13 rom from here
Btw I'm not sure if there's miui 14 for the redmi 9s (thats a official stock firmware), all the sites I get to are sketchy lmao
dekannomad said:
dekannomad said:
The last time I tried it was the miui 13 but it was not a timeout error, it was weird, I think it detected my phone and all that but when it started installing, it gave out an error when it was maybe half way and hung, luckily I have a custom recovery so I realized I didn't brick it and just installed a custom miui 13 rom from here
Btw I'm not sure if there's miui 14 for the redmi 9s (thats a official stock firmware), all the sites I get to are sketchy lmao
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Try batch flashing via fastboot. Paste adb and fastboot.exe in image folder then click on flash_all.bat
MIUI 14 is out for global I'm using it. I also faced bootloop while flashing from cusrom to stock. Then i flashed all miui 11 versions it was still bootloop then flashed MIUI 14 it booted. Currently I'm on MIUI 14 SJWMIXM
Muhammad Juman said:
Try batch flashing via fastboot. Paste adb and fastboot.exe in image folder then click on flash_all.bat
MIUI 14 is out for global I'm using it. I also faced bootloop while flashing from cusrom to stock. Then i flashed all miui 11 versions it was still bootloop then flashed MIUI 14 it booted. Currently I'm on MIUI 14 SJWMIXM
Click to expand...
Click to collapse
Could you explain more how to batch flash or link a guide please? I know how to follow guides and all that but I don't know what batch flashing is
dekannomad said:
Could you explain more how to batch flash or link a guide please? I know how to follow guides and all that but I don't know what batch flashing is
Click to expand...
Click to collapse
Here is guide
NOSS8 said:
Check here that everything is correct.
Post the Miflash log, miflash log file.
MIFLASH[GUIDE]⚙ USE XIAOMI FLASH TOOL
FOR ALL XIAOMI BOOTLOADER MUST BE UNLOCKED https://new.c.mi.com/global/post/101245 https://en.miui.com/unlock/index.html ----------------------------------------------------------------------------------------------------------- All your data...
forum.xda-developers.com
Click to expand...
Click to collapse
So I was following what the guide said and when I click drivers it just crashes and leaves this log, I read it but it doesn't seem that helpful lol
dekannomad said:
So I was following what the guide said and when I click drivers it just crashes and leaves this log, I read it but it doesn't seem that helpful lol
Click to expand...
Click to collapse
Try that:
MIFLASH[GUIDE]⚙ USE XIAOMI FLASH TOOL
FOR ALL XIAOMI BOOTLOADER MUST BE UNLOCKED https://new.c.mi.com/global/post/101245 https://en.miui.com/unlock/index.html ----------------------------------------------------------------------------------------------------------- All your data...
forum.xda-developers.com
NOSS8 said:
Try that:
MIFLASH[GUIDE]⚙ USE XIAOMI FLASH TOOL
FOR ALL XIAOMI BOOTLOADER MUST BE UNLOCKED https://new.c.mi.com/global/post/101245 https://en.miui.com/unlock/index.html ----------------------------------------------------------------------------------------------------------- All your data...
forum.xda-developers.com
Click to expand...
Click to collapse
So I did that but it opened a cmd and closed really fast, I don't think it did anything at all to be honest, Im going to reboot see what happened
dekannomad said:
So I did that but it opened a cmd and closed really fast, I don't think it did anything at all to be honest, Im going to reboot see what happened
Click to expand...
Click to collapse
What OS are you using?
NOSS8 said:
Try that:
MIFLASH[GUIDE]⚙ USE XIAOMI FLASH TOOL
FOR ALL XIAOMI BOOTLOADER MUST BE UNLOCKED https://new.c.mi.com/global/post/101245 https://en.miui.com/unlock/index.html ----------------------------------------------------------------------------------------------------------- All your data...
forum.xda-developers.com
Click to expand...
Click to collapse
Damn it says the system has been destroyed, so now Im back to the situation I was in, I only have my custom recovery and fastboot
NOSS8 said:
What OS are you using?
Click to expand...
Click to collapse
Win 10, a few updates missing but basically up to date.
If my pc is the problem I have a laptop, which I never connect my phone to, that I can try on. It's on win 10 too but I haven't updated in a while since I don't use it often
Device manager/view/show hidden devices.
Do you have this?
NOSS8 said:
Device manager/view/show hidden devices.
Do you have this?
View attachment 5901529View attachment 5901531
Click to expand...
Click to collapse
This is what I have, I'm even using the original cable that my phone came with, which is brand new since I don't use it to charge it in everyday use.
One is unplugged, one is with it in fastboot mode
On this image, you have selected show hidden devices?
NOSS8 said:
On this image, you have selected show hidden devices?
Click to expand...
Click to collapse
Yes
Download and install ADB driver
Xiaomi Redmi Note 9S USB Driver for Windows
Download the latest Xiaomi Redmi Note 9S Driver for Windows Computer. You can use the latest Xiaomi Driver to connect the Xiaomi Device to the Computer.
xiaomidriver.com
NOSS8 said:
Download and install ADB driver
Xiaomi Redmi Note 9S USB Driver for Windows
Download the latest Xiaomi Redmi Note 9S Driver for Windows Computer. You can use the latest Xiaomi Driver to connect the Xiaomi Device to the Computer.
xiaomidriver.com
Click to expand...
Click to collapse
Okay I did that, I'm going to restart my pc. I should have known I was missing something. Should I try to install the firmware again?

Categories

Resources