Keeping it short:
This is the official STABLE global MIUI 11 Rom for Mi 9T
Official download links:
For rooted devices - Recovery full zip (2.3GB)
For stock unrooted devices - OTA upgrade zip (779MB)
Magisk Root without TWRP:
Objectives :
Have root using Magisk
Be able to install OTA from the settings without bootloops
Avoid boot loop
Very important :
Your phone has to have an unlocked bootloader
Your phone has to have stock recovery. TWRP WILL cause bootloop for root and/or OTA updates from system.
I like to have root with magisk and don't want to install TWRP because I want to be able to install OTA from system without boot loops. This guide will help you achieve this with ease.
Download the rooted boot image for your correct ROM version from here: https://mega.nz/#F!1kwETAwD!O5iPgAaocQ8WxfUK2V7RVA
Restart your phone in fastboot mode (hold vol-down and power buttons for a few seconds)
Flash the rooted boot image using fastboot. (fastboot flash boot Magisk_9T_Global_V11.0.1.0.PFJMIXM.img)* **
Reboot device (fastboot.exe reboot)
(install then) Open Magisk manager
Follow instruction shown in the magisk manager for adding necessary files (you might not need this)
*Download the latest Minimal ADB /fastboot and USB drivers for your device if you are having a problem with this.
** Using some data cables will result in your fastboot not seeing your device (showing < waiting for any device >). If you have this problem change your USB cable with another or use the one that comes with the device
I have attached the following root files:
V10.3.11.0.PFJMIXM (MIUI10) global stable room - Global 9T stock boot image
V11.0.1.0.PFJMIXM (MIUI11) global stable room - Global 9T stock boot image
V11.0.1.0.PFJMIXM (MIUI11) global stable room - Global 9T Magisk rooted boot image
Things to consider doing after the update:
Remove ads using this guide: https://miblog.co/miui-remove-system-ads/
Enable Android style notification (instead of the default MiUI one) from the notification settings
Disable option: “Settings / Additional settings / Privacy / Location / Scanning / WLAN scanning” to improve battery life
Use this guide to install Xiaomi Mi 9 Google Camera (GCam) (no root needed): https://miblog.co/xiaomi-mi9-google-camera/
Disable autostart for all apps excluding the ones you want to autostart to fix the battery drainage issue
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hey, quick question. I'm trying to install the new MIUI11 stock global ROM for my Mi 9T. The thing is, the phone's updater takes forever to download and the download itself even gets cancelled out of nowhere (my internet is pretty slow) Can I just download the 779MB OTA Upgrade zip you provided and move it to my phone and proceed selecting it from the updater app? Is it the same file you get as downloading it from the app? I'm on global, PFJMIXM version 10.3.11.0
Thanks!
Danielxgl said:
Hey, quick question. I'm trying to install the new MIUI11 stock global ROM for my Mi 9T. The thing is, the phone's updater takes forever to download and the download itself even gets cancelled out of nowhere (my internet is pretty slow) Can I just download the 779MB OTA Upgrade zip you provided and move it to my phone and proceed selecting it from the updater app? Is it the same file you get as downloading it from the app? I'm on global, PFJMIXM version 10.3.11.0
Thanks!
Click to expand...
Click to collapse
I'm not sure how the update app does the file check. Can you try it and report?
I know that if you're rooted, the OTA will fail to install and the update app automatically starts downloading the full ROM, which is pretty cool.
Kiwironic said:
I'm not sure how the update app does the file check. Can you try it and report?
I know that if you're rooted, the OTA will fail to install and the update app automatically starts downloading the full ROM, which is pretty cool.
Click to expand...
Click to collapse
Wish I could try it, but my update app miraculously decided not to fail this time, and I was able to update the phone normally. Maybe someone else could try it?
What im i do wrong if i get twrp while trying to boot miui? Installed Patched boot installed firmware cannot boot
Still Android 9, no?
SeriousX said:
What im i do wrong if i get twrp while trying to boot miui? Installed Patched boot installed firmware cannot boot
Click to expand...
Click to collapse
Flash the stock or rooted boot image and recovery for your device. It should work normally. That's my main reason to root without TWRP
robi10101298 said:
Still Android 9, no?
Click to expand...
Click to collapse
Yes
Kiwironic said:
Keeping it short:
This is the official STABLE global MIUI 11 Rom for Mi 9T
Official download links:
For rooted devices - Recovery full zip (2.3GB)
For stock unrooted devices - OTA upgrade zip (779MB)
Magisk Root without TWRP:
Download the rooted boot image for your correct ROM version from here: https://mega.nz/#F!1kwETAwD!O5iPgAaocQ8WxfUK2V7RVA
Restart your phone in fastboot mode (hold vol-down and power buttons for a few seconds)
Flash the rooted boot image using fastboot. (fastboot flash boot Magisk_9T_Global_V11.0.1.0.PFJMIXM.img)* **
Reboot device (fastboot.exe reboot)
(install then) Open Magisk manager
Follow instruction shown in the magisk manager for adding necessary files (you might not need this)
*Download the latest Minimal ADB /fastboot and USB drivers for your device if you are having a problem with this.
** Using some data cables will result in your fastboot not seeing your device (showing < waiting for any device >). If you have this problem change your USB cable with another or use the one that comes with the device
I have attached the following root files:
V10.3.11.0.PFJMIXM (MIUI10) global stable room - Global 9T stock boot image
V11.0.1.0.PFJMIXM (MIUI11) global stable room - Global 9T stock boot image
V11.0.1.0.PFJMIXM (MIUI11) global stable room - Global 9T Magisk rooted boot image
Things to consider doing after the update:
Remove ads using this guide: https://miblog.co/miui-remove-system-ads/
Enable Android style notification (instead of the default MiUI one) from the notification settings
Disable option: “Settings / Additional settings / Privacy / Location / Scanning / WLAN scanning” to improve battery life
Use this guide to install Xiaomi Mi 9 Google Camera (GCam) (no root needed): https://miblog.co/xiaomi-mi9-google-camera/
Disable autostart for all apps excluding the ones you want to autostart to fix the battery drainage issue
Click to expand...
Click to collapse
If I don't want root anymore I can install this via Twrp: Recovery full zip (2.3GB)rooted devices + V11.0.1.0.PFJMIXM (MIUI11) global stable room - Global 9T stock boot image
Is this right?
Drakar88 said:
If I don't want root anymore I can install this via Twrp: Recovery full zip (2.3GB)rooted devices + V11.0.1.0.PFJMIXM (MIUI11) global stable room - Global 9T stock boot image
Is this right?
Click to expand...
Click to collapse
Yes the full rom. But no need to flash boot, flashing the full image will automatically rewrite the boot image to a stock unrooted one.
Anybody who needed a root boot image, can send me the version of their ROM or send me the boot image from their phone and I'll root it for you using magisk. You can do that yourself as well by downloading the full ROM zip file, take the boot file and use magisk to create a root boot image. Can provide more details if you don't know how to do it.
Kiwironic said:
Anybody who needed a root boot image, can send me the version of their ROM or send me the boot image from their phone and I'll root it for you using magisk. You can do that yourself as well by downloading the full ROM zip file, take the boot file and use magisk to create a root boot image. Can provide more details if you don't know how to do it.
Click to expand...
Click to collapse
Do provide more details. I'm on stock miui (davinciin), with unlocked bl and would like to root tf outta this
geeknoob said:
Do provide more details. I'm on stock miui (davinciin), with unlocked bl and would like to root tf outta this
Click to expand...
Click to collapse
I wrote a guide and made some videos here :
https://forum.xda-developers.com/showpost.php?p=80835573&postcount=1
Updated the post because people using the guide while having TWRP will have bootloop . Please read the instructing carefully. You need a stock recovery for this root to work and for OTA to install from settings
Thanks for this guide, I couldn't get official TWRP to stick so that I could flash Magisk. I used your guide and now I have root. Many thanks
i need to ask.
when miui release a new update i usually update and after that i had to re flash the "recovery-TWRP-3.3.1-0916-REDMI_K20-CN-wzsx150" then again flash the magisk.
but this time i try to install it boot the recovery but when i go to the internal memory it appear a lot of weird folders and it won't allow me to paste the magisk to install it.
"+KPcZ3jsjybn9M850BgrhB"
3zitjokdIMQE++oQFL8PxA
9AmJcdRgO71ehKtIhWg3oB
9Y0e9H1NkAr4FMzOz9X,UD
882G73cfQNPbaXm2zAzXiD
---------- Post added at 11:34 AM ---------- Previous post was at 11:24 AM ----------
Jctatis said:
i need to ask.
when miui release a new update i usually update and after that i had to re flash the "recovery-TWRP-3.3.1-0916-REDMI_K20-CN-wzsx150" then again flash the magisk.
but this time i try to install it boot the recovery but when i go to the internal memory it appear a lot of weird folders and it won't allow me to paste the magisk to install it.
"+KPcZ3jsjybn9M850BgrhB"
3zitjokdIMQE++oQFL8PxA
9AmJcdRgO71ehKtIhWg3oB
9Y0e9H1NkAr4FMzOz9X,UD
882G73cfQNPbaXm2zAzXiD
Click to expand...
Click to collapse
NVM already fixed installed the twrp-3.3.1-0-davinci.img and flashed the magisk v.20
Kiwironic said:
Anybody who needed a root boot image, can send me the version of their ROM or send me the boot image from their phone and I'll root it for you using magisk. You can do that yourself as well by downloading the full ROM zip file, take the boot file and use magisk to create a root boot image. Can provide more details if you don't know how to do it.
Click to expand...
Click to collapse
Thanks for this! Would you be able to make a patched boot.img for V11.0.5.0.QFJMIXM? Please? Mi net is too bad to download the whole rom
galelouch993 said:
Thanks for this! Would you be able to make a patched boot.img for V11.0.5.0.QFJMIXM? Please? Mi net is too bad to download the whole rom
Click to expand...
Click to collapse
Just downloaded the whole ROM with no problem from:
https://mirom.ezbox.idv.tw/en/phone/davinci/
Anyway, try with the following - patched from my Magisk Canary:
https://mega.nz/file/09M13QhI#4AXcEYviHw_1xyhCoDYZh_J41Iu58ulozuRJbhQZP6w
You can test just by temporarily booting to the patched image (if it boots ok, then you would really flash it):
fastboot boot boot-Magisk_Canary_20405-davinci_v11.0.5.0_QFJIMXM_aaab5b40c7_10.0.img
Download and install the corresponding Canary Magisk Manager e.g. app-release.apk, from:
https://github.com/topjohnwu/magisk_files/find/canary?q=
If you have a bootloop it could be due to the previously installed Magisk modules - you would need to disable them in TWRP:
/data/adb/modules
and to every subfolder add an empty file named "disable" (or delete the whole modules folder)
zgfg said:
Just downloaded the whole ROM with no problem from:
https://mirom.ezbox.idv.tw/en/phone/davinci/
Anyway, try with the following - patched from my Magisk Canary:
https://mega.nz/file/09M13QhI#4AXcEYviHw_1xyhCoDYZh_J41Iu58ulozuRJbhQZP6w
You can test just by temporarily booting to the patched image (if it boots ok, then you would really flash it):
fastboot boot boot-Magisk_Canary_20405-davinci_v11.0.5.0_QFJIMXM_aaab5b40c7_10.0.img
Download and install the corresponding Canary Magisk Manager e.g. app-release.apk, from:
https://github.com/topjohnwu/magisk_files/find/canary?q=
If you have a bootloop it could be due to the previously installed Magisk modules - you would need to disable them in TWRP:
/data/adb/modules
and to every subfolder add an empty file named "disable" (or delete the whole modules folder)
Click to expand...
Click to collapse
Ty very much for replying with a complete guide and files needed. I managed to get a boot.img for my version and patched it successfully with stable magisk manager. I'm very grateful for your efforts tho.
Btw, any special reason for using canary builds in your steps?
9
galelouch993 said:
Ty very much for replying with a complete guide and files needed. I managed to get a boot.img for my version and patched it successfully with stable magisk manager. I'm very grateful for your efforts tho.
Btw, any special reason for using canary builds in your steps?
Click to expand...
Click to collapse
Canary has some early fixes and features, but also some new bugs
E.g., for a long time, Canary has a new UI. It was buggy and with issues but now is already good and stable andI I like its new features
But just realized that V4A cannot install driver with yesterday's Magisk Canary 20401 so I returned back to Canary 20405
Edit:
Btw, you can try Magisk Manager Canary - install from the link in my previous post.
It should work with your stable Magisk
By using Stable Channel, you can always return to stable Manager version
Related
I am on OOS 2.2.3 on my Oneplus X. Rooted with Twrp recovery. Was not able to flash the new and official OOS 3.1.3 zip file through TWRP, so flashed Blue_spark TWRP in recovery mode (read somewhere that it could have enabled me to flash OOS 3.1.3). Now the phone boots into OOS 2.2.3 normally, but I cant boot into recovery or bootloader and it gets stuck at the logo screen in both these modes.
Could someone please help me out with this?
Shalabh21 said:
I am on OOS 2.2.3 on my Oneplus X. Rooted with Twrp recovery. Was not able to flash the new and official OOS 3.1.3 zip file through TWRP, so flashed Blue_spark TWRP in recovery mode (read somewhere that it could have enabled me to flash OOS 3.1.3). Now the phone boots into OOS 2.2.3 normally, but I cant boot into recovery or bootloader and it gets stuck at the logo screen in both these modes.
Could someone please help me out with this?
Click to expand...
Click to collapse
As a result of this, I am not even able to do a manual factory reset from the setting menu in OOS 2.2.3, because when i try to initiate this the phone again gets stuck at the logo screen of recovery mode.
Shalabh21 said:
I am on OOS 2.2.3 on my Oneplus X. Rooted with Twrp recovery. Was not able to flash the new and official OOS 3.1.3 zip file through TWRP, so flashed Blue_spark TWRP in recovery mode (read somewhere that it could have enabled me to flash OOS 3.1.3). Now the phone boots into OOS 2.2.3 normally, but I cant boot into recovery or bootloader and it gets stuck at the logo screen in both these modes.
Could someone please help me out with this?
Click to expand...
Click to collapse
blu.spark TWRP v41 uses the updated Marshmallow bootloader from OOS3.1.3, and you are on the Lollipop bootloader.
Lollipop Bootloader recovery won't boot on Marshmallow bootloader and Marshmallow bootloader recovery won't boot on Lollipop bootloader.
If you wanna flash the 3.1.3 zip, then use these instructions.
Download Oxygen OS 3.1.3 full ROM
Download MM based unofficial TWRP
Downloaded Modded SuperSU if you want root
You will require a PC with WinRAR & Notepad++, because as we are running custom ROMs the zip will give an error 7 saying that The package is for OnePlus, this is an onyx, we need to remove that.
Don't worry, its super easy.
- Download the OOS3 zip, copy it to your PCs desktop
- Open it with winRAR, dont extract it, just open it
- There will be a META-INF folder, open it
- Then open com, then google, then android, there will be 2 files here, updater-binary & updater script
- Double click on updater-script
- It will ask which app to use to open the file, then select to open with Notepad++ (designate it from its installed directory if it isn't visible in the initial list)
- The file will look like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- Delete the entire first line that starts with getprop
- Now it should look like this
- Now press Ctrl+S to save the file and close the window
- WinRAR will ask weather to update changes in the archive, say yes to that
- Let it finish its job
- Done !
Moving on to the flashing now...
Assuming you on OOS2.2.3, goto settings, enable Advanced Reboot.
Then reboot to bootloader, this is fastboot mode.
Flash this recovery.
Done, now...
- Copy the modded OOS3 zip into your Device
- Boot into TWRP recovery
- Wipe system, data, cache & dalvik/art cache
- Flash the modified OOS3 zip
- Let it complete
- After it completes, press the wipe cache/dalvik button below
- Now reboot to system
- Complete the initial setup
- Goto settings, unlock developer options by tapping 7 times on build number in about phone
- Enable advanced reboot
- Then reboot to bootloader
- Flash the MM based unofficial TWRP via fastboot
- Remember to boot into this newly flash TWRP before booting into system so that it doesn't overwite it
- Done
Now you are on OOS 3.1.3, and have a working TWRP, you can proceed to flash SuperSU etc to gain root
Joshwin Aranha said:
blu.spark TWRP v41 uses the updated Marshmallow bootloader from OOS3.1.3, and you are on the Lollipop bootloader.
Lollipop Bootloader recovery won't boot on Marshmallow bootloader and Marshmallow bootloader recovery won't boot on Lollipop bootloader.
If you wanna flash the 3.1.3 zip, then use these instructions.
Download Oxygen OS 3.1.3 full ROM
Download MM based unofficial TWRP
Downloaded Modded SuperSU if you want root
You will require a PC with WinRAR & Notepad++, because as we are running custom ROMs the zip will give an error 7 saying that The package is for OnePlus, this is an onyx, we need to remove that.
Don't worry, its super easy.
- Download the OOS3 zip, copy it to your PCs desktop
- Open it with winRAR, dont extract it, just open it
- There will be a META-INF folder, open it
- Then open com, then google, then android, there will be 2 files here, updater-binary & updater script
- Double click on updater-script
- It will ask which app to use to open the file, then select to open with Notepad++ (designate it from its installed directory if it isn't visible in the initial list)
- The file will look like this
- Delete the entire first line that starts with getprop
- Now it should look like this
- Now press Ctrl+S to save the file and close the window
- WinRAR will ask weather to update changes in the archive, say yes to that
- Let it finish its job
- Done !
Moving on to the flashing now...
Assuming you on OOS2.2.3, goto settings, enable Advanced Reboot.
Then reboot to bootloader, this is fastboot mode.
Flash this recovery.
Done, now...
- Copy the modded OOS3 zip into your Device
- Boot into TWRP recovery
- Wipe system, data, cache & dalvik/art cache
- Flash the modified OOS3 zip
- Let it complete
- After it completes, press the wipe cache/dalvik button below
- Now reboot to system
- Complete the initial setup
- Goto settings, unlock developer options by tapping 7 times on build number in about phone
- Enable advanced reboot
- Then reboot to bootloader
- Flash the MM based unofficial TWRP via fastboot
- Remember to boot into this newly flash TWRP before booting into system so that it doesn't overwite it
- Done
Now you are on OOS 3.1.3, and have a working TWRP, you can proceed to flash SuperSU etc to gain root
Click to expand...
Click to collapse
Thank you very much Joshwin Aranha. This worked like a charm.
However I modified the last step and flashed OOS recovery instead. Want to use the phone without root for a while, because the main reason I rooted it in the first place was to install Greenify and save battery (battery used to drain heavily in OOS 2.2.2 and all prior versions), but unfortunately it did not have a great impact on battery life. So going back to stock version for now.
Shalabh21 said:
Thank you very much Joshwin Aranha. This worked like a charm.
However I modified the last step and flashed OOS recovery instead. Want to use the phone without root for a while, because the main reason I rooted it in the first place was to install Greenify and save battery (battery used to drain heavily in OOS 2.2.2 and all prior versions), but unfortunately it did not have a great impact on battery life. So going back to stock version for now.
Click to expand...
Click to collapse
Whatever rocks your boat buddy, glad you sorted that out.
OPX stuck at oneplus logo after following the procedure
@Joshwin Aranha
Hi, I followed the exact same procedure you mentioned, and the process goes smoothly. But when i reboot the phone is stuck at oneplus logo (when i check through my PC for the status it says it is in fastboot mode).
I can easily flash OOS 2.2.3 and move to lollipop , but the problem occurs in OOS 3.1.3 MM
P.S. - i am not rooted.
hbansal24x7 said:
@Joshwin Aranha
Hi, I followed the exact same procedure you mentioned, and the process goes smoothly. But when i reboot the phone is stuck at oneplus logo (when i check through my PC for the status it says it is in fastboot mode).
I can easily flash OOS 2.2.3 and move to lollipop , but the problem occurs in OOS 3.1.3 MM
P.S. - i am not rooted.
Click to expand...
Click to collapse
Which recovery did you use to flash OOS3 ? And did you properly wipe everything ? Try re-flashing.
Joshwin Aranha said:
Which recovery did you use to flash OOS3 ? And did you properly wipe everything ? Try re-flashing.
Click to expand...
Click to collapse
I have used official TWRP that you mentioned in the procedure. I can easily flash CM13 and get my phone running. The problem is only coming in flashing OOS 3.1.3 after OOS 2.2.3.
And yes i have tried it multiple times. With factory reset, user data erase . Everything.
One quirk which i faced 1 time was that while flashing OOS 3 via official twrp 3.0.2.0 , during system verification stage i got an error "system partition has unexpected contents". I cleaned dalvik/cache/data and the error went away but the problem still persists
hbansal24x7 said:
I have used official TWRP that you mentioned in the procedure. I can easily flash CM13 and get my phone running. The problem is only coming in flashing OOS 3.1.3 after OOS 2.2.3.
And yes i have tried it multiple times. With factory reset, user data erase . Everything.
One quirk which i faced 1 time was that while flashing OOS 3 via official twrp 3.0.2.0 , during system verification stage i got an error "system partition has unexpected contents". I cleaned dalvik/cache/data and the error went away but the problem still persists
Click to expand...
Click to collapse
Does the OOS3 zip give any errors ? Or flashes properly ? This seems like a peculiar issue nonetheless..
Joshwin Aranha said:
Does the OOS3 zip give any errors ? Or flashes properly ? This seems like a peculiar issue nonetheless..
Click to expand...
Click to collapse
It does flash properly when i try to flash from OOS 2.2.3->3.1.3 . What i have observed is that as soon as the phone starts it gets stuck on oneplus logo without "android" written below. When i plug it into my system and check the device, it responds to "fastboot devices". I guess there is some issue with the bootloader or something
hbansal24x7 said:
It does flash properly when i try to flash from OOS 2.2.3->3.1.3 . What i have observed is that as soon as the phone starts it gets stuck on oneplus logo without "android" written below. When i plug it into my system and check the device, it responds to "fastboot devices". I guess there is some issue with the bootloader or something
Click to expand...
Click to collapse
Very the md5 of the OOS3 zip to check for a corrupted download.
Original md5 is 162f12d4dfef0142a184e761da868c5f
Joshwin Aranha said:
Very the md5 of the OOS3 zip to check for a corrupted download.
Original md5 is 162f12d4dfef0142a184e761da868c5f
Click to expand...
Click to collapse
MD5 is the same for UNCHANGED zip. i guess md5 will differ on a modified zip due to the changes you mentioned in the process.
How to Install TWRP:
Note: that version is UNOFFICIAL TWRP-3.3.0-0524
.Pre-Requirements
ADB means Android Debug Bridge, and it is software that you should always do have installed on your PC.
Pre-Requisite 1
Make sure that you have the drivers for your phone installed on your PC.
If not, you can download and install them from here https://devsjournal.com/usb-drivers-...d-devices.html
Pre-Requisite 2
You must also install: Minimal ADB & Fastboot, you can download the software
from here https://devsjournal.com/download-min...boot-tool.html
Pre-Requisite 3
Your device needs this with unlocked bootloader
if it is not unlocked do the tutorial to unlock HERE
Pre-Requisite 4
Make sure you have enabled 'USB Debugging' and OEM Unlocking on your device
Settings -> Advanced settings -> Developer Options
PAY ATTENTION: If you do not see the Developer Options menu you need to do this:
Settings -> Device Info -> tap 6 or 7 times on the 'ZUI version' entry
A pop-up should appear, telling you 'now you are a developer'
------------------------------------------------
1) Download TWRP: recovery-TWRP-3.3.0-0524-LENOVO_Z5PRO_GT-CN-wzsx150.img
2) After getting the TWRP file put it in the same ADB folder
3) Now start the phone in bootlader by doing this:
Connect the phone to the PC
Start the Minimal ADB & Fastboot program from the PC
On the PC screen, type:
adb reboot bootloader
(A request may appear on the phone screen with permission of USB debugging, accept it)
The phone will now restart in Bootloader mode.
4) Now that you are in bootloader mode, from the PC, from the screen
Minimal ADB and Fastboot type:
fastboot flash recovery recovery-TWRP-3.3.0-0524-LENOVO_Z5PRO_GT-CN-wzsx150.img
Sending 'recovery' (98304 KB) OKAY [ 5.970s]
Writing 'recovery' OKAY [ 0.539s]
Done !
---------
.How to Install Root Magisk:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Done !
Credits:
Maker: wzsx150
Developer Team: LR.Team
Is there any issues related to this recovery?
firemax13 said:
Is there any issues related to this recovery?
Click to expand...
Click to collapse
I had no problem with this recovery
My device was unlocked by vendor. I'm unable to boot into twrp to root my device. The flashing is successful but it will only boot in a simple recovery where I can only install an "update.zip".
Have tried this https://forum.xda-developers.com/z5...-guide-lenovo-z5-pro-gt-t3915945#post81055547 but the problem remains.
Hope anyone can help. I need to root my device. Thanks
BlueIce84 said:
My device was unlocked by vendor. I'm unable to boot into twrp to root my device. The flashing is successful but it will only boot in a simple recovery where I can only install an "update.zip".
Have tried this https://forum.xda-developers.com/z5...-guide-lenovo-z5-pro-gt-t3915945#post81055547 but the problem remains.
Hope anyone can help. I need to root my device. Thanks
Click to expand...
Click to collapse
Have the same scenario as you but I haven't done the tutorial yet as I read your post and I got concerned. Have you fix you issue? Is it safe to do this tutorial?
No solution so far. No twrp and no root
Now I have flashed the original rom with ZUI 10. Works well and updated to ZUI 11.
luigi0824 said:
Have the same scenario as you but I haven't done the tutorial yet as I read your post and I got concerned. Have you fix you issue? Is it safe to do this tutorial?
Click to expand...
Click to collapse
I've read somewhere that you need to flash vbmeta.img if verified boot is enabled, however I couldn't find the correct img to flash anywhere. Maybe if we ask someone that has the phone already rooted.
Can anyone post wzsx150's newest TWRP 3.3.1 from October 4? It's in this thread but the download link is for registered users only. I can't sign up for a Club Lenovo account.
BlueIce84 said:
No solution so far. No twrp and no root
Now I have flashed the original rom with ZUI 10. Works well and updated to ZUI 11.
Click to expand...
Click to collapse
What method would you follow to install the stock rom, like you, it comes with the bootloader unlocked by the seller and I don't know how to flash stock rom
Use this guide:
https://forum.xda-developers.com/z5-pro-gt/how-to/guide-unbrick-guide-lenovo-z5-pro-gt-t3915945
carlshark said:
Can anyone post wzsx150's newest TWRP 3.3.1 from October 4? It's in this thread but the download link is for registered users only. I can't sign up for a Club Lenovo account.
Click to expand...
Click to collapse
I gave up on clublenovo. They require SMS authentication to post so even when you log in you can't post and download. TWRP 3.3.1 is also available from 4PDA. That's what I used.
I was able to flash the TWRP 3.3.1 but i cant root nor i cant flash anything as the folders inside the sdcard directory is showing in weird names
luigi0824 said:
I was able to flash the TWRP 3.3.1 but i cant root nor i cant flash anything as the folders inside the sdcard directory is showing in weird names
Click to expand...
Click to collapse
You need to decrypt the internal storage.
normally this is done by entering to ping code to unlock the phone in TWRP on start up.
thorvall said:
You need to decrypt the internal storage.
normally this is done by entering to ping code to unlock the phone in TWRP on start up.
Click to expand...
Click to collapse
Will I lose any data if I decrypt my phone? And where do I find that pin code?
luigi0824 said:
Will I lose any data if I decrypt my phone? And where do I find that pin code?
Click to expand...
Click to collapse
Its the pin code you use to open the phone.
And enabling does not remove data, but it does give twrp read/write permission
Is it possible to implement support for OTA updates through TWRP?
BlueIce84 said:
My device was unlocked by vendor. I'm unable to boot into twrp to root my device. The flashing is successful but it will only boot in a simple recovery where I can only install an "update.zip".
Have tried this https://forum.xda-developers.com/z5...-guide-lenovo-z5-pro-gt-t3915945#post81055547 but the problem remains.
Hope anyone can help. I need to root my device. Thanks
Click to expand...
Click to collapse
i had the same issue and discover a solution
1) you have to manually go to your phone after you finish the flash below. DO NOT cmd fastboot reboot as it will flash stock
recovery
a) fastboot flash recovery twrp.img ( i rename the tweak recovery file to twrp.img)
b) http://4pda.ru/forum/index.php?showtopic=973179&st=0
(tweak recovery version 3.31)
2) after flash quickly go to your phone fastboot mode ( reminder again: do not tyoe fastboot reboot after flash successful appear in cmd)
3) manually select recovery , select english then select reboot and TWRP will appear
issues
1) i cannot manually tweak recovery via phone ( power +volume down ) as stock recovery will appear again.
A) so you need to go your PC to redo flash recovery again
B) i did a back up and redo PC flassh recovery again and mine files are stored successful
c) there is no install root in TWRP
D) about backup...
.best to back up via OTA-USB. pixel GCI crash ( QUALCOMM CRASH DUMP MODE ) my phone and my restore
file was missing as TWRP rename the restore file. spent one hour it so decide to do stock rom
current
a) I have not flash any rom yet and my original ANTUTU benchmark hovers around 300000 to 350000 based on vendor custom global rom
b) my phone model is 8gb 128gb android version 9 and lenovo version 11.0.084
c) updatess and NFC not supported
d) i opt not too root
e) bootloader still unlock
REQUEST...
would appreciate a ROM recommendation
a) have anyone flash a rom (not china stock rom) wirh an antutu beachmark abve 400000 ?
from a novice... after 2 weeks i can finally flash tweak recovery from the phonE.
about flashing stock rom..
i opt for stock rom and my antutu hovers around 409000 to 418000. from LENOVO app centre you can install play store
butterx2341 said:
i had the same issue and discover a solution
1) you have to manually go to your phone after you finish the flash below. DO NOT cmd fastboot reboot as it will flash stock
recovery
a) fastboot flash recovery twrp.img ( i rename the tweak recovery file to twrp.img)
b) http://4pda.ru/forum/index.php?showtopic=973179&st=0
(tweak recovery version 3.31)
2) after flash quickly go to your phone fastboot mode ( reminder again: do not tyoe fastboot reboot after flash successful appear in cmd)
3) manually select recovery , select english then select reboot and TWRP will appear
issues
1) i cannot manually tweak recovery via phone ( power +volume down ) as stock recovery will appear again.
A) so you need to go your PC to redo flash recovery again
B) i did a back up and redo PC flassh recovery again and mine files are stored successful
c) there is no install root in TWRP
D) about backup...
.best to back up via OTA-USB. pixel GCI crash ( QUALCOMM CRASH DUMP MODE ) my phone and my restore
file was missing as TWRP rename the restore file. spent one hour it so decide to do stock rom
current
a) I have not flash any rom yet and my original ANTUTU benchmark hovers around 300000 to 350000 based on vendor custom global rom
b) my phone model is 8gb 128gb android version 9 and lenovo version 11.0.084
c) updatess and NFC not supported
d) i opt not too root
e) bootloader still unlock
REQUEST...
would appreciate a ROM recommendation
a) have anyone flash a rom (not china stock rom) wirh an antutu beachmark abve 400000 ?
from a novice... after 2 weeks i can finally flash tweak recovery from the phonE.
about flashing stock rom..
i opt for stock rom and my antutu hovers around 409000 to 418000. from LENOVO app centre you can install play store
Click to expand...
Click to collapse
If you boot your ZUI system, your twrp will be overwritten by a stock recovery.
However if you flash magisk, your twrp won't be overwritten anymore. If you want to preserve your twrp after rebooting on ZUI, you need to flash magisk.
whatever I do.. the twrp wont be installed (let alone the root/magisk). ADB does say the twrp is flashed... but it will always boot to or the bootloader.. or the system (not the lenovo recovery or twrp recovery). Quiet frustrating... what can I do? Want this boy rooted!
Edit: done. The twrp linked in the tutorial is not correct use this one: https://drive.google.com/file/d/13mt0RLmT83BHSUBpH-J7EhaeZQ-MPYUu/view
That worked!
I want to unlock my bootloader but the site where you request the image file for unlocking it wont accept my IMEI1.. any idea guys?
Disclaimer: I did not found this exploit, but there are some things I want to share about the exploit with some additions of my own. You can also say that this guide is newbie friendly version of this original guide here. without any further ado lets start with the guide. I recommend reading original guide first. :
First, I (or anyone at xda ) is not responsible for your bricked device. Make sure you have read every line of this guide (POST #1 and #2) before performing any of the steps. Because it is very risky and might cause permanent damage if steps were performed incorrectly.
And also make sure you have downloaded everything before like custom ROM, twrp, etc and placed them on external sdcard or otg before performing any steps because there is no going back.
Second, do not quote whole post or I will ignore.
What this guide covers?
It covers
Post #1
1. flashing custom recovery (by bypassing bootloader lock)
Post #2
2. flashing custom rom, flashing MIUI based rom
3. Rooting/flashing custom kernel
4. flashing GSI
Requirements to bypass bootloader lock:
NOTE: Flash nougat fastboot ROM through edl if you plan on using custom ROMs to avoid hassle like network/sim card etc but if you want to use xiaomi EU or miui then stay on Oreo miui.
1. Windows 10 PC (other windows versions might also work)
2. Portable MI Flash tool. Link (updated). Extract it somewhere on your PC, you should see QSaharaServer.exe and fhloader.exe after extract.
3. Firmware files (more on that on Post #2). Download and place them inside your external sdcard.
4. Basic knowledge of using Windows and knwo how to enter EDL mode.
Steps:
1. On your PC open directory where you extracted Portable MI Flash, and create a folder named 'tmp' inside folder containing QSaharaServer.exe
2. Download bypass.7z (Download links on Post #2) and extract all of its contents to tmp folder you created above. DO NOT CREATE ANY FOLDERS INSIDE tmp
3. Go to tmp folder then if you are using MIUI oreo then delete 'PBRP_recovery_official_nougat.img' and rename 'OrangeFox_oreo_unoffical_port_by_saurabh6377.img' to 'recovery.img' and do opposite if you are using MIUI Nougat. I recommend you to save both recoveries to external sdcard of your device for future use.
4. Connect your device in EDL mode (Your device must be POWERED OFF before connecting). Go outside tmp folder.
5. Open command prompt or power shell in the folder containing QSaharaServer.exe and run the following commands one by one
Code:
QSaharaServer.exe -p \\.\COM8 -s 13:prog_emmc_firehose_8917_ddr.mbn -b tmp\
to initialize firehose (Replace COM8 with COM Port of your device, find using device manager)
Code:
fh_loader.exe --search_path=tmp --port=\\.\COM8 --sendxml=twrp.xml
to flash custom recovery.
6. If the above command returns DONE then reboot to recovery. You should see MI logo and then hopefully custom recovery will boot.
Congratulations Now you have bypassed bootloader lock successfully on Redmi 5A.
If the commands does not return done, then Paste the ouput commands here, I will come for help.
Press thanks if this guide helped you.
This post covers the following.
1. Flashing custom ROM.
2. Flashing Stock MIUI ROM or Xiaomi EU Rom
3. Flashing custom kernel and rooting
4. Flashing GSI
5. Downloads
Requirements:
1. Appender. Download latest version for both normal and recovery versions and save to sdcard. Optionally read the post to get better idea on how and when to flash Appender.
2. Recovery for nougat fw. You can also PBRP Recovery in bypass.7z. You can also download recoveries from below.
3. Firmware files:
Redmi 5A have two firmwares available as of now, nougat fw and oreo fw.
Currently custom ROMs only work with nougat fw, so you need to flash nougat fw before flashing any custom ROMs. You can download global nougat fw from here
MIUI and Xiaomi EU already contains firmware files so no extra firmware need to be downloaded in most cases (more on that below)
Steps to flash custom ROMs:
1. Flash the downloaded nougat firmware using current recovery (Only required once)
2. If you are coming from oreo fw then flash recovery image (for nougat fw) using current recovery. You can also download recoveries I have uploaded, links at end of this post.
3. Flash Appender-rec.zip then reboot to recovery.
4. Flash the ROM then flash Appender.zip
5. Reboot. And hopefully the ROM will boot.
Steps for MIUI or Xiaomi EU ROM:
1. Flash the ROM
2. If you want to flash stock MIUI and dont want reocvery to be overwritten by stock then flash Magisk. For Xiaomi EU magisk is NOT required.
3. Flash Appender.zip
4. If you are coming from nougat fw and have recovery based on nougat fw installed then flash my Orangefox Recovery (link below) and then flash Appender-rec.zip after performing above steps.
5. Reboot
NOTE: Xiaomi may patch the bug anytime, so latest stock MIUI or Xiaomi EU ROMs might not work with this exploit. However, this bug isn't patched yet in any of the MIUI ROMs as of now, the latest version I have tested is MIUI china nightly v9.9.26. So, it is better to download the oreo firmware file (link below) and flash it EVERY time after flashing MIUI or Xiaomi EU ROMs.
Flashing custom Kernel and Rooting:
Flash the kernel or magisk and the flash Appender.zip
Flashing GSI
No extra steps are needed. Follow procedure to install custom ROM and after that flash GSI in system partition.
Downloads:
1. bypass.7z
2. Orangefox Recovery Oreo fw
3. Pitch Black Recovery Nougat fw
4. Appender
5. Oreo firmware file (Will upload soon)
6. Nougat fastboot ROM link http://bigota.d.miui.com/V10.1.1.0....FI_20181029.0000.00_7.1_global_f444c158ed.tgz
Reserved 2
@saurabh6377 Thanks a ton for this. Hopefully I might be able to try this next week when I get home. Just wanted to ask though if it was absolutely necessary to flash a nougat version of MIUI for using custom rom. And if there is no other choice which version should I flash? Also do I need any special account or sthng for flashing fastboot rom or should i just follow some tutorial on youtube?
adityam0338 said:
@saurabh6377 Thanks a ton for this. Hopefully I might be able to try this next week when I get home. Just wanted to ask though if it was absolutely necessary to flash a nougat version of MIUI for using custom rom. And if there is no other choice which version should I flash?
Click to expand...
Click to collapse
Yes, nougat miui is necessary for custom ROMs (except xiaomi eu) latest global stable (nougat version) is recommended. You can use any nougat version though.
I added link to nougat fastboot rom in post 2.
adityam0338 said:
do I need any special account or sthng for flashing fastboot rom or should i just follow some tutorial on youtube?
Click to expand...
Click to collapse
Lastly flashing through edl does not require any account on redmi 5A as far as I know.
@saurabh6377 It is not necessary to set up the device after flashing nougat version, right? I mean could i just flash the nougat version and then without starting the device follow this thread as it would be easier to get the device in edl mode then.
adityam0338 said:
@saurabh6377 It is not necessary to set up the device after flashing nougat version, right? I mean could i just flash the nougat version and then without starting the device follow this thread as it would be easier to get the device in edl mode then.
Click to expand...
Click to collapse
No need to setup, some users reported that edl does not work after flashing fastboot rom so, you may need to fully power off after flashing ROM from edl. So reboot then shut down then follow the guide. You can also just remove the battery socket then reconnect to fully power off, and then enter edl mode.
@saurabh6377 the link for portable mi flash tool doesn't work anymore. "404 not found"
@saurabh6377 Now I'm getting a different error. I'll attach a snapshot of the error. Hope u can help quick.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
https://drive.google.com/file/d/1wpTgmHDifrV
sCKiY2uys2ZrM9h9GiOrQ/view?usp=drivesdk
@saurabh6377
12:35:54: ERROR: function: sahara_rx_data:237 Unable to read packet header. Only read 0 bytes.
12:35:54: ERROR: function: sahara_main:924 Sahara protocol error
12:35:54: ERROR: function: main:303 Uploading Image using Sahara protocol failed
This is the error that I'm getting.
Can anyone confirm if we can flash pie based ROM after installing twrp this way or not? I'm currently on DotOS based on N.
Ripper1412 said:
Can anyone confirm if we can flash pie based ROM after installing twrp this way or not? I'm currently on DotOS based on N.
Click to expand...
Click to collapse
Yes you can. I read someone say he booted LOS 16 after flashing TWRP by this method. But if you are on dot os, it means ur Boot loader is unlocked. It would be better to flash TWRP by normal method in your case.
Ripper1412 said:
Can anyone confirm if we can flash pie based ROM after installing twrp this way or not? I'm currently on DotOS based on N.
Click to expand...
Click to collapse
Well yeah it works. I am using lineage os 16 based on pie at the moment after flashing by this method.
Edl mode
Can i enter EDL mode without test point method?
I have an unlocked bootloader of Redmi 5a global miui 11 Oreo ..can u tell me from where and what should I do to downgrade the firmware
sha0307 said:
I have an unlocked bootloader of Redmi 5a global miui 11 Oreo ..can u tell me from where and what should I do to downgrade the firmware
Click to expand...
Click to collapse
https://forum.xda-developers.com/xiaomi-redmi-5a/how-to/rollback-downgrade-to-miui-nougat-t3938904
Deleted
Ripper1412 said:
Can anyone confirm if we can flash pie based ROM after installing twrp this way or not? I'm currently on DotOS based on N.
Click to expand...
Click to collapse
You can even flash android q based rom as i am using pixel experience rom based on android 10 on naugat firmware.
Can someone help me how to flash a android 10 gsi in Redmi 5a Riva .cause I get bootloop or stuck at bootlogo whenever I try to install gsi ..can anyone help me plss
I have entered both the commands and it was written there "DONE" in powershell. But after that i have booted in recovery but it booted in MI recovery not in custom recovery. I followed all the steps correctly.
I am not responsible for your actions, but I will try to help.
I'm going to assume you have unlocked bootloader and ADB/Fastboot tools installed.
1. Download latest Magisk and make 2 copies of it. Install one of them on your phone. Change the extension of 2nd from .apk to .zip, then move it to your phone`s storage
2. Download Pitch Black recovery for Redmi 9C
3. Move recovery.img to both your ADB folder (can be found at C:\adb) and phone`s storage
5. Download DM-VERITY, FORCED ENCRYPTION
6. Rename it to enfec.zip and place in phone`s storage
4. Download attached vbmeta.img and place it in your ADB folder
5. Go into fastboot mode
5. On your PC, open cmd-here.exe in adb folder
6. fastboot flash recovery recovery.img
7. fastboot flash vbmeta vbmeta.img
8. fastboot reboot recovery
9. Sometimes recoveries don't work with touchscreen. In this case, flash other region's ROM. To do this, find and download fastboot version of ROM. Unzip it, run flash_all.bat while being in a fastboot mode (this will erase all data). WARNING: DO NOT RUN flash_all_and_lock.bat. THIS WILL LOCK THE BOOTLOADER AND YOU WILL HAVE TO WAIT ANOTHER WEEK!
Next retry again the whole tutorial. You can also use USB-OTG mouse.
10. Navigate to 'Install' section. Check every option except 'Reboot after installation is complete', 'Zip signature verification' and 'Advanced remove of Forced Encryption'. Select recovery image that you previously moved to your storage and install it 'as Recovery'.
11. In recovery, move to 'backup' and make a backup to your SD card (optional, but highly recommended). Usually, it doesn`t work out of the box. Try searching for guides.
12. In the same section install enfec.zip and then Magisk.zip. If you get errors like 'Failed to mount /nv_data', ignore them.
13. Reboot to system, copy external_sd/PBRB/tools -> storage/0/emulated/PBRB/
Done!
How to pass SafetyNet (tested on 05.05.21 dd/mm):
Simply enable MagiskHide. This will only work if you haven`t modified the /system with modules that don`t hide themselves.
If you did heavy modifications, install UniversalSafetyNetFix (USNF) (repo) or install both MagiskHide Props Config (can be found in Magisk`s modules) and USNF. Instructions to installation of Props Config can be found in the README or on the web. Experiment with it, this is device specific.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It seems like you are using redmi 9C NFC
I am using redmi 9C Global
Did you tested this recovery on your phone?
I downloaded a recovery from GitHub for redmi 9c flashed it after flashing I flashed vbmeta too but can't boot into recovery
I am currently on global EU ROM 12.0.3 which I flashed yesterday
Before that I was on miui global 12.0.10
I tried to root it with magisk and after flashing magisk patched boot.img flashed vbmeta too
But can't get root access
Before I was on miui global 12.0.8
I rooted with magisk and got root access
In order to get root access I downgraded back to miui 12.0.8 but can't get root access
What should I do now?
It seems like you are using redmi 9C NFC
Click to expand...
Click to collapse
True
I am using redmi 9C Global
Click to expand...
Click to collapse
That doesn`t really matter
Did you tested this recovery on your phone?
Click to expand...
Click to collapse
Yes
I downloaded a recovery from GitHub for redmi 9c
Click to expand...
Click to collapse
Which recovery have you flashed? I provided link to SouceForge, not GitHub
I downloaded a recovery [...] flashed it after flashing I flashed vbmeta too but can't boot into recovery
Click to expand...
Click to collapse
Try fastboot reboot recovery.img
If that doesn`t work, try updating your ADB/Fastboot tools. Just download needed files from any site and place them in your ADB folder.
Also, since this recovery is unofficial port, it is a bit different from original. To boot into recovery, you don`t have to hold power+volume_up untill you see recovery menu. Instead, hold it untill screen goes black.
I tried to root it with magisk and after flashing magisk patched boot.img flashed vbmeta too
But can't get root access
Click to expand...
Click to collapse
From my guide:
No users report bootloops, but in some cases root isn't granted. In this case follow next steps.
Click to expand...
Click to collapse
Before I was on miui global 12.0.8
I rooted with magisk and got root access
In order to get root access I downgraded back to miui 12.0.8 but can't get root access
Click to expand...
Click to collapse
I don`t really get what you say, but there is no need to downgrade/upgrade. If I were you, I would flash latest MIUI, though
What should I do now?
Click to expand...
Click to collapse
Try flashing latest eu MIUI (I can help with that, if you want) and then follow method B) step by step, without making any changes and reading everything that I wrote
Hope this helps!
Can't make a backup as your tutorial because i got an error, and what i need to backup just the 'one' selected from the recobery ? can i skip this step and just install the enfec.zip and then Magisk.zip ?
I am stuck from the step 8 and 9 because i got that error and i have no idea what select from the list of the backup...
Backup is an optional step. I get an error too and I have no idea why.
Seems like it worked very well. but the safetynet failed, should download Magisk v21.4 zip because the newest one failed at the moment to flash it, and if you get an error at the end of flashing the DM-VERITY, FORCED ENCRYPTION it's ok still working anyway. thanks for sharing the post
@0purple
Btw personally skip the step 8 and 9, if you failed to get into recovery with the bottons just try again the step 5,6,7
Knox6 said:
but the safetynet failed, should download Magisk v21.4 zip because the newest one failed at the moment to flash it,
Click to expand...
Click to collapse
Updated the post, try it
I have the European version 12.06 of the redmi 9c. I tried to boot into recovery, but the touch doesn't work in any way, so I can't do anything... help me
i just enabled magisk hide option in magisk manager setting it fixed it
MHaseebpk said:
View attachment 5278627View attachment 5278627i just enabled magisk hide option in magisk manager setting it fixed it
Click to expand...
Click to collapse
does the root work for you? I have the EUropera version 12.0.6 and it doesn't work
sephirot91 said:
does the root work for you? I have the EUropera version 12.0.6 and it doesn't work
Click to expand...
Click to collapse
Yes
MHaseebpk said:
Yes
Click to expand...
Click to collapse
See this
MHaseebpk said:
See this View attachment 5278773
Click to expand...
Click to collapse
how did you do it? I followed the guide perfectly and it doesn't work. On the other hand, with the second method, the pitch recovery touch does not respond to commands
sephirot91 said:
how did you do it? I followed the guide perfectly and it doesn't work. On the other hand, with the second method, the pitch recovery touch does not respond to commands
Click to expand...
Click to collapse
I just followed seconds method and I am on global rom
You should flash global rom and should try again
MHaseebpk said:
I just followed seconds method and I am on global rom
You should flash global rom and should try again
Click to expand...
Click to collapse
Ok thanks, I could try. Do you have a guide to flash the global version? thank you very much
https://c.mi.com/oc/miuidownload/detail?guide=2
is it okay? for flashing rom global
sephirot91 said:
Ok thanks, I could try. Do you have a guide to flash the global version? thank you very much
Click to expand...
Click to collapse
First you need to download angelica global latest (12.0.10) fastboot rom from Here
Download miflash pro english from Here
Extract mi flash pro zip file install mi flash pro and extract angelica global image too in your PC
Now power off you phone
Hold volume down and power button simultaneously for 5 seconds
Your phone will boot into fastboot mode
Now open miflash pro login with your mi account connect your phone
When you will connect your phone your phone will be automatically detected
And miflash pro will recommend you to flash in recovery click on it
Next select package (fastboot rom) which you downloaded and extracted before and select script flash all.bat
Wait for 5 to 6 minutes
Your phone will be flashed
After that setup your phone
Boot again into fastboot mode
Setup adb in your PC
Install mediatek USB vcom drivers
And next follow second method
MHaseebpk said:
First you need to download angelica global latest (12.0.10) fastboot rom from Here
Download miflash pro english from Here
Extract mi flash pro zip file install mi flash pro and extract angelica global image too in your PC
Now power off you phone
Hold volume down and power button simultaneously for 5 seconds
Your phone will boot into fastboot mode
Now open miflash pro login with your mi account connect your phone
When you will connect your phone your phone will be automatically detected
And miflash pro will recommend you to flash in recovery click on it
Next select package (fastboot rom) which you downloaded and extracted before and select script flash all.bat
Wait for 5 to 6 minutes
Your phone will be flashed
After that setup your phone
Boot again into fastboot mode
Setup adb in your PC
Install mediatek USB vcom drivers
And next follow second method
Click to expand...
Click to collapse
I don't lose the unlocked bootloader, right?
sephirot91 said:
I don't lose the unlocked bootloader, right?
Click to expand...
Click to collapse
Yes select flash all.bat your bootloader will remain unlock and your phone will be flashed
Don't select flash all and lock script otherwise bootloader of your phone will be locked and you will have to wait for 7 days to unlock bootloader
Hi,
I tried to update my P6 using the magisk OTA update method:
-Unistall / Restore image
-Install OTA, no reboot
-Install magisk on inactive slot
-Reboot
My phone was on the SQ3A.220705.001.B2 update, few months old.
When I rebooted, I was prompted with the "device corrupted" message. I pressed the power key to continue, and was stuck at the Google logo boot loop.
I forced turned off the phone (hold power + vol up a few sec), and the phone rebooted, no corruption message to my surprise, and booted correctly. However, my system did not update (still on SQ3A.220705.001.B2).
I'm a rookie on device rooting, but my understanding is that my inactive slot (partition b) as the update installed but is corrupted and goes in boot loop, while partition a is not updated but not corrupted either.
The thing is, I only did "install on inactive slot", so magisk was uninstalled on partition a, and rebooting made me lost root on that partition.
Is there any way to de-corrupt partition b without losing data ? Because without root on partition a, it seems like I'll need to reinstall it, meaning a factory reset...
I've searched a bit on here, saw that it was probably an avb bug (but rookie me doesn't know what avb is), and that OTA update using magisk inactive partition was not recommended for P6 and P7.
Any help would be greatly appreciated, thanks !
SleinBuyt said:
Is there any way to de-corrupt partition b without losing data ? Because without root on partition a, it seems like I'll need to reinstall it, meaning a factory reset...
I've searched a bit on here, saw that it was probably an avb bug (but rookie me doesn't know what avb is), and that OTA update using magisk inactive partition was not recommended for P6 and P7.
Any help would be greatly appreciated, thanks !
Click to expand...
Click to collapse
Be certain you're running the latest version of ADB. Google provides a link to the package you can download and extract. Then download a factory image from Google, extract the files from the zip to the same folder ADB was wxtracted to, and edit "flash-all.bat" in a text editor. You're looking for a snippet of text, "-w". Delete that text and save the file. From there, connect the unit to your PC and flash the ROM.
This will restore both partitions to working condition without removing data, but you will lose root in the process and will need to root again.
Strephon Alkhalikoi said:
Be certain you're running the latest version of ADB. Google provides a link to the package you can download and extract. Then download a factory image from Google, extract the files from the zip to the same folder ADB was wxtracted to, and edit "flash-all.bat" in a text editor. You're looking for a snippet of text, "-w". Delete that text and save the file. From there, connect the unit to your PC and flash the ROM.
This will restore both partitions to working condition without removing data, but you will lose root in the process and will need to root again.
Click to expand...
Click to collapse
Strephon Alkhalikoi said:
Be certain you're running the latest version of ADB. Google provides a link to the package you can download and extract. Then download a factory image from Google, extract the files from the zip to the same folder ADB was wxtracted to, and edit "flash-all.bat" in a text editor. You're looking for a snippet of text, "-w". Delete that text and save the file. From there, connect the unit to your PC and flash the ROM.
This will restore both partitions to working condition without removing data, but you will lose root in the process and will need to root again.
Click to expand...
Click to collapse
Ok I'll find out how to flash ROM using adb beacause I don't remember, and I'll do what you said.
After that, I should be able to force boot to partition b (the updated one) using adb, right? And will I be able to root without losing data ?
SleinBuyt said:
Ok I'll find out how to flash ROM using adb beacause I don't remember, and I'll do what you said.
After that, I should be able to force boot to partition b (the updated one) using adb, right? And will I be able to root without losing data ?
Click to expand...
Click to collapse
Ok so I've searched a bit, since my bootloader is unlocked I'll be able to root without losing data. The only question that remains :
You told me to download a factory image and to flash it with adb. Can I download the lasted version, for example the one that I failed to update to? If so, after flashing, will my de va ice be updated to the lasted version ?
Because that means that it's a way to update my phone, if I don't want to get the corruption error :
-download lasted update
-flash using adb, with the edited .bat
-Reboot and re-flash magisk
-done
SleinBuyt said:
Ok so I've searched a bit, since my bootloader is unlocked I'll be able to root without losing data. The only question that remains :
You told me to download a factory image and to flash it with adb. Can I download the lasted version, for example the one that I failed to update to? If so, after flashing, will my de va ice be updated to the lasted version ?
Because that means that it's a way to update my phone, if I don't want to get the corruption error :
-download lasted update
-flash using adb, with the edited .bat
-Reboot and re-flash magisk
-done
Click to expand...
Click to collapse
I think that the easiest way is with Pixel Flasher, it makes everything automatically with data preserve.
SleinBuyt said:
Ok so I've searched a bit, since my bootloader is unlocked I'll be able to root without losing data. The only question that remains :
You told me to download a factory image and to flash it with adb. Can I download the lasted version, for example the one that I failed to update to? If so, after flashing, will my de va ice be updated to the lasted version ?
Because that means that it's a way to update my phone, if I don't want to get the corruption error :
-download lasted update
-flash using adb, with the edited .bat
-Reboot and re-flash magisk
-done
Click to expand...
Click to collapse
m_pastuszek said:
I think that the easiest way is with Pixel Flasher, it makes everything automatically with data preserve.
Click to expand...
Click to collapse
@SleinBuyt : Yes
@m_pastuszek : While he could do that he should learn how to do it without a tool first. That way he can understand what is going on when the tool is working.
Strephon Alkhalikoi said:
@SleinBuyt : Yes
@m_pastuszek : While he could do that he should learn how to do it without a tool first. That way he can understand what is going on when the tool is working.
Click to expand...
Click to collapse
I agree on this side, but actually editing script that makes something similar comes down to the same thing
That was the same case for me.
After latest OTA update, no matter how many time I tried to flash full factory image via fastboot, stil showing device corrupted.
A couple of things everyone having this issue should be aware of.
Currently, "Flash to Inactive Slot" breaks verification/dm-verity on the Pixel 6/7, and I believe that's responsible for the "Device corrupted" error. The Magisk devs are aware but don't have a fix yet. I haven't been able to test because there have been no OTAs since I disabled those myself (which PixelFlasher can do for you), but I believe disabling them should prevent that problem during OTAs, but be advised I think doing so requires wiping /data when you do it.
Also, if you're still getting "device corrupted" even after reflashing stock, first watch for any errors during flashing in PixelFlasher (I may have a fix for anyone that has USB issues on Windows devices, but it involves the registry so it makes some people nervous), but if it isn't working then try Google's Android Flash Tool by finding your device and desired firmware here and clicking Flash. You'll need to be using Chrome. That's never failed for me. Once you have it up and running again *then* use PixelFlasher to patch and flash the boot image.
ALSO, for anyone on T1B1/QPR2: Magisk currently is not working at all with these versions. It'll boot, but you'll have no root. No one knows why yet as far as I'm aware. You'll have to stick to earlier/non beta builds until there's an answer for that if you want root.
Jaitsu said:
ALSO, for anyone on T1B1/QPR2: Magisk currently is not working at all with these versions. It'll boot, but you'll have no root. No one knows why yet as far as I'm aware. You'll have to stick to earlier/non beta builds until there's an answer for that if you want root.
Click to expand...
Click to collapse
To root the Pixel 6 on QPR2 Beta 1 you can patch the Pixel 7 boot image and then flash that on the Pixel 6.
Compression method of ramdisk in Pixel 6 boot image is incorrect · Issue #6441 · topjohnwu/Magisk
After switching to the beta version can't patch boot img and succesfully get root, with the stable version works. Device: Pixel 6a Android version: Android 13 QPR2 Beta 1 (T2B1.221118.006) Magisk v...
github.com
UPDATE : I did it, I used ADB for the sake of trying it, next time I'll look into PixelFlasher I guess. The message is gone.
Exact step followed :
-I first trained to use adb by flashing magisk, but ended up patching the wrong boot.img (the one from the A13 update, while being on A12), which sent me in a bootloop.
-I then flashed the A13 ROM, with the modified flash-all file
-Rebooted bootloader, flashed magisk
-Rebooted device.
Took me 2h lol, each step was learning something.
Thanks everyone!
SleinBuyt said:
UPDATE : I did it, I used ADB for the sake of trying it, next time I'll look into PixelFlasher I guess. The message is gone.
Exact step followed :
-I first trained to use adb by flashing magisk, but ended up patching the wrong boot.img (the one from the A13 update, while being on A12), which sent me in a bootloop.
-I then flashed the A13 ROM, with the modified flash-all file
-Rebooted bootloader, flashed magisk
-Rebooted device.
Took me 2h lol, each step was learning something.
Thanks everyone!
Click to expand...
Click to collapse
Just make sure you have the A13 bootloader on both slots if you haven't already, since it sounds like you just updated from A12 to A13?
🛑❗⚠️ WARNING! Read this before your initial upgrade to Android 13!⚠️❗🛑
***Note: THIS IS NOT A ROOT GUIDE. For updating and root instructions, check out my guide here.*** From the Pixel Images page: This applies to ALL Tensor devices, regardless of whether or not you're rooted! What this means: Once Android 13...
forum.xda-developers.com
Lughnasadh said:
Just make sure you have the A13 bootloader on both slots if you haven't already, since it sounds like you just updated from A12 to A13?
🛑❗⚠️ WARNING! Read this before your initial upgrade to Android 13!⚠️❗🛑
***Note: THIS IS NOT A ROOT GUIDE. For updating and root instructions, check out my guide here.*** From the Pixel Images page: This applies to ALL Tensor devices, regardless of whether or not you're rooted! What this means: Once Android 13...
forum.xda-developers.com
Click to expand...
Click to collapse
I mean, the objective was to update my device and keep root, wich is now done. Why do I need the A13 bootloader on both slots, and if it's important how should I do it ?
SleinBuyt said:
I mean, the objective was to update my device and keep root, wich is now done. Why do I need the A13 bootloader on both slots, and if it's important how should I do it ?
Click to expand...
Click to collapse
It's important if you don't want to brick your device. Did you read the link I gave you?
Lughnasadh said:
It's important if you don't want to brick your device. Did you read the link I gave you?
Click to expand...
Click to collapse
Sorry I didn't see, I've read now.
So If ok reboot to fastboot, plug in, and with adb :
fastboot flash bootloader --slot=all flash-all.img
I should be good ?
SleinBuyt said:
Sorry I didn't see, I've read now.
So If ok reboot to fastboot, plug in, and with adb :
fastboot flash bootloader --slot=all flash-all.img
I should be good ?
Click to expand...
Click to collapse
fastboot flash bootloader --slot=all <A13 bootloader image>
My situation is a bit bizarre. I'm on beta and recently got an update notification that was 190mb. I went to magisk to restore images and magisk says stock backup does not exist. From there and went ahead and use my PC to flash my stock boot image and rebooted. Once an Android it's still says the same thing but when I go back to the update it says installation problem Even though I am on stock. That's where I'm at right now. Haven't messed with it since just rolled with no root and stock boot image.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Lughnasadh said:
fastboot flash bootloader --slot=all <A13 bootloader image>
Click to expand...
Click to collapse
And it's done ! Thanks for potentially saving my phone later !