I'm currently running Android 11 based Wave OS on my Redmi Note 9 Pro (Curtana). I have OrangeFox recovery installed. I want to flash latest stock ROM which is also based on Android 11.
So, can anyone help me with the correct procedure for the flashing of Stock MIUI 12 based on Android 11 on my Curtana with OF recovery installed?
Azamsm said:
I'm currently running Android 11 based Wave OS on my Redmi Note 9 Pro (Curtana). I have OrangeFox recovery installed. I want to flash latest stock ROM which is also based on Android 11.
So, can anyone help me with the correct procedure for the flashing of Stock MIUI 12 based on Android 11 on my Curtana with OF recovery installed?
Click to expand...
Click to collapse
You can flash this directly from ofox. It's the current updated Android R stock firmware which is stable. Just format your data, flash the recovery rom (not the fastboot rom) and reboot.
But I highly recommend you to try EU rom from xiaomi.eu website.
MPK99 said:
You can flash this directly from ofox. It's the current updated Android R stock firmware which is stable. Just format your data, flash the recovery rom (not the fastboot rom) and reboot.
But I highly recommend you to try EU rom from xiaomi.eu website.
Click to expand...
Click to collapse
So, I can flash this one by the same method?
Azamsm said:
So, I can flash this one by the same method?
Click to expand...
Click to collapse
Ys. It's the eu one that I mentioned.
But note that eu roms are always little behind the latest versions.
Right now, eu rom is 12.0.1 & stock is 12.0.4.
But don't worry, differences are very minor. Go with EU.
MPK99 said:
Ys. It's the eu one that I mentioned.
But note that eu roms are always little behind the latest versions.
Right now, eu rom is 12.0.1 & stock is 12.0.4.
But don't worry, differences are very minor. Go with EU.
Click to expand...
Click to collapse
Hi @MPK99
I successfully flashed eu rom 12.0.1. Thanks for the guidance.
Can you also help me gaining root. I flashed Magisk 22.0 zip via OFox, it's successfully installed, root checker shows phone is rooted and even able to grant apps root access but it actually doesn't seem to be working. I can't modify system files and root apps don't do what they are supposed to do. Please help.
Thanks in advance!
Azamsm said:
Hi @MPK99
I successfully flashed eu rom 12.0.1. Thanks for the guidance.
Can you also help me gaining root. I flashed Magisk 22.0 zip via OFox, it's successfully installed, root checker shows phone is rooted and even able to grant apps root access but it actually doesn't seem to be working. I can't modify system files and root apps don't do what they are supposed to do. Please help.
Thanks in advance!
Click to expand...
Click to collapse
What method you used to root? Boot Patch or Recovery flash? Also check & tell whether device is encrypted or not.
MPK99 said:
What method you used to root? Boot Patch or Recovery flash? Also check & tell whether device is encrypted or not.
Click to expand...
Click to collapse
Recovery flash and device in not encrypted.
Can I have your telegram?
Azamsm said:
Recovery flash and device in not encrypted
Click to expand...
Click to collapse
Get latest Magisk (magisk-v22.0.zip), flash it as a module under Magisk app itself. Reboot.
MPK99 said:
Get latest Magisk (magisk-v22.0.zip), flash it as a module under Magisk app itself. Reboot.
Click to expand...
Click to collapse
Didn't work. Thanks for the help btw.
Azamsm said:
Didn't work. Thanks for the help btw.
Click to expand...
Click to collapse
There's no root problems btw. Try to enable root permissions for the explorer manually under magisk. Also check whether you allowed root under your explorer settings.
MPK99 said:
There's no root problems btw. Try to enable root permissions for the explorer manually under magisk. Also check whether you allowed root under your explorer settings.
Click to expand...
Click to collapse
I checked and it's enabled. But it's not working anyhow. Stock MIUI doesn't get rooted too. There's this wave OS rom which I could successfully root so far. But it had heating issue while charging. Maybe I should forget about rooting for a whilr
Azamsm said:
I checked and it's enabled. But it's not working anyhow. Stock MIUI doesn't get rooted too. There's this wave OS rom which I could successfully root so far. But it had heating issue while charging. Maybe I should forget about rooting for a whilr
Click to expand...
Click to collapse
Is root not working for just solid explorer or other root apps too? If root works on other apps, try Mixplorer instead of Solid.
MPK99 said:
Is root not working for just solid explorer or other root apps too? If root works on other apps, try Mixplorer instead of Solid.
Click to expand...
Click to collapse
Not working on any app.
While I retried flashing Magisk through OFox, I saw these lines
Code:
-System as root, keep dm/avb verity
- Encrypted data, keep force encryption
Is this the encryption you were talking about
Azamsm said:
While I retried flashing Magisk through OFox, I saw these lines
Code:
-System as root, keep dm/avb verity
- Encrypted data, keep force encryption
Is this the encryption you were talking about
Click to expand...
Click to collapse
Maybe. Because, Encryption & rooting together doesn't go well.
On Encryption, you have to follow boot patch method. Recovery flashing won't work.
Extract boot.img from your stock firmware (or EU rom firmware), patch that file from magisk patch method. You'll get patched_boot.img. Flash that as boot under recovery.
MPK99 said:
Maybe. Because, Encryption & rooting together doesn't go well.
On Encryption, you have to follow boot patch method. Recovery flashing won't work.
Extract boot.img from your stock firmware (or EU rom firmware), patch that file from magisk patch method. You'll get patched_boot.img. Flash that as boot under recovery.
Click to expand...
Click to collapse
Tried this method too, still can't delete that miui_mod_icons folder. Root isn't working yet.
Azamsm said:
Tried this method too, still can't delete that miui_mod_icons folder. Root isn't working yet.
Click to expand...
Click to collapse
Well, you have some specific reason to root. To remove some system apps right. You can do that on recovery too. Leave rooting, caz it's encrypted.
MPK99 said:
Well, you have some specific reason to root. To remove some system apps right. You can do that on recovery too. Leave rooting, caz it's encrypted.
Click to expand...
Click to collapse
Hey dude, first of all, I'm thankful to you for keeping calm and helping me
But actually both TWRP and OFox recoveries show nothing inside /system except for 4 folders which has nothing inside them. So I can't even see the files I want to delete.
Maybe it's because of the dynamic system partition or super partitions in android 11, idk I'm just super disappointed
Hey, @MPK99
One thing I noticed that system can be mounted read-only in OFox. If I want to mount it read-write, it just won't.
Related
This thread was originally for Pixel-specific rooting instructions, but by now the SuperSU ZIP and TWRP are fully supported:
- Fastboot boot TWRP
- Install latest SuperSU ZIP (v2.79-SR3 at the time of writing)
Note that at this time I recommend against fastboot flashing TWRP. With the Pixel's new partition layout, the recovery files are inside the boot partition, and so is SuperSU. If you flash both, SuperSU's internal boot image backup will not be of the original boot image, but of TWRP. This means that neither the 'full unroot' option in SuperSU, nor incremental OTA update through FlashFire, will work as expected.
OR
- Use CF-Auto-Root for Pixel (not released at the time of writing, but should be released soon)
Nice work!
Hell Yeah!!! Thanks @Chainfire, your time as well as others that have made this and the bootloader unlock happen is appreciated very much.
Sent from my Pixel XL using Tapatalk
can we flash another kernel such as elementalX on top of this?
diabl0w said:
can we flash another kernel such as elementalX on top of this?
Click to expand...
Click to collapse
How does this relate?
Ker~Man said:
How does this relate?
Click to expand...
Click to collapse
because I attempted to not really thinking about that its systemless and wasnt sure if root would persist. after attempting to flash boot elementalX's kernel my device just powered off so i immediately reflashed root and all is okay now
diabl0w said:
can we flash another kernel such as elementalX on top of this?
Click to expand...
Click to collapse
Lol if you read chainfires instructions you would have e your answer,but it short no, not until they add it
I did read the readme.. so not sure what your getting at
cwalker0906 said:
Lol if you read chainfires instructions you would have e your answer,but it short no, not until they add it
Click to expand...
Click to collapse
chainfire said:
- If you want to use a custom kernel, simply 'fastboot boot' the root image again after flashing the custom kernel. This has been tested with a few custom kernels and found to work well so far.
Click to expand...
Click to collapse
It was a valid question since this flashing method is different than what we are used to due to the difference in partitions and the file system.
lexcyn said:
It was a valid question since this flashing method is different than what we are used to due to the difference in partitions and the file system.
Click to expand...
Click to collapse
okay thanks, so i guess the answer is actually yes
Thanks @Chainfire - booted and working well!
thanks..emoji..root explorer.. viper.. naptime.. titanium.. yes..
if new kernel must boot boot to root again..
Seems I cannot remount /system_root as rw (to copy Emoji font over).
marlin://system_root/system/fonts # mount -o remount,rw /system_root
mount: '/dev/block/bootdevice/by-name/system_a'->'/system_root': Device or resource busy
Edit: Nevermind, used Solid Explorer and granted it SuperUser and seemed to work. Strange.
Does anyone have the stock boot.img for the pixel xl? I don't have the data to download the full factory image.
Life is good!
Thanks to all involved, especially Chainfire.
You Rock!
Worked like a charm. Thanks @Chainfire!
Can't thank you enough. Works perfectly.
can someonone please post the exact steps they are using?
I just unlocked my bootloader. then tried flashing the root-boot img file, it did the reboots, but when i complete android setup, theres no SuperSU and if i install the .apk, it still does not detect root...
just reflashed stock boot.img, locked and unlocked bootloader. waiting for instrustion.
thanks!
spunks3 said:
can someonone please post the exact steps they are using?
I just unlocked my bootloader. then tried flashing the root-boot img file, it did the reboots, but when i complete android setup, theres no SuperSU and if i install the .apk, it still does not detect root...
just reflashed stock boot.img, locked and unlocked bootloader. waiting for instrustion.
thanks!
Click to expand...
Click to collapse
fastboot boot boot-to-root.img
lexcyn said:
fastboot boot boot-to-root.img
Click to expand...
Click to collapse
what about superSU?
I have global Honor 9, updated to 8.0.0.379(C432), unlocked and rooted.
I read that Huawei rolled out an update which broke Magisk, does anyone know if the latest update is safe?
How can I tell if an update is safe to use?
I'm using it with the new 9.0.1 rom and it works just fine, the only problem is that it cannot exist on the phone at the same time with a TWRP recovery
mtvento said:
I'm using it with the new 9.0.1 rom and it works just fine, the only problem is that it cannot exist on the phone at the same time with a TWRP recovery
Click to expand...
Click to collapse
as opposed to version 8.0.0.379?
I currently have magisk and TWRP with no problem, is this problem you describe is new to the latest version?
Do you have a different custom ROM?
I have the latest official ROM, and yes it is a new problem with EMUI9, the boot.img partition doesn't exist any more and magisk has to be installed on the recovery_ramdisk.img
mtvento said:
I have the latest official ROM, and yes it is a new problem with EMUI9, the boot.img partition doesn't exist any more and magisk has to be installed on the recovery_ramdisk.img
Click to expand...
Click to collapse
So on EMUI9 there's no option of Root+Custom recovery?
So the options are either root or custom recovery?
Did I understand correctly?
Thank you
Yes, correct until new findings lead to better solution, and keep in mind that you have to boot to recovery each time to keep root working...
mtvento said:
Yes, correct until new findings lead to better solution, and keep in mind that you have to boot to recovery each time to keep root working...
Click to expand...
Click to collapse
That sucks big time.
What do you mean by "have to boot to recovery each time"? every time I restart the phone or turn it off and back on I must go through recovery?
I think I'll avoid EMUI9 and stick with EMUI8.
For some reason there are not much custom ROMs or honor 9
That is the last time I buy a non root friendly phone like Huawei/Xiaomi
Once you have magisk set up you can just get it to flash the boot image from within the manager you can boot as normal then
buchman said:
Once you have magisk set up you can just get it to flash the boot image from within the manager you can boot as normal then
Click to expand...
Click to collapse
I don't really know what that means.
Is it a one time thing?
how is it done exactly?
Clonimus said:
I don't really know what that means.
Is it a one time thing?
how is it done exactly?
Click to expand...
Click to collapse
From within magisk manager click on install magisk and the select the direct install method. It patches the right bit then and you can boot without going through recovery
buchman said:
From within magisk manager click on install magisk and the select the direct install method. It patches the right bit then and you can boot without going through recovery
Click to expand...
Click to collapse
When I do that it gives me 2 options, one is download a zip file (and then I need to install using TWRP, right?)
The other option is patch a boot image, and it lets me look for one. Is this option to patch a downloaded boot image and then I need to flash it? what do I do with this option?
Last updated May 2020
Keeping it short. This is a simple way to root your device. You will need a computer and a data cable for this.
Objectives :
Have root using Magisk
Be able to install OTA from the settings without bootloops
Avoid boot loop
Very important :
This will work with ANY Xiaomi phone, and should work with ANY ANDROID phone as well. The difference between phones would be in where you can get your boot image from.
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.
Steps:
Download the ROM full zip file. This could be the ROM ALREADY installed on your phone or you are updating your phone to it. Here is a video of one way to get your ROM file.
https://youtu.be/KsxHial1v1U
Open the file and extract "boot.img" on your phone or Computer.
Move the boot.img file to your phone
Download and install the latest Magisk official manager app from here: https://github.com/topjohnwu/Magisk/releases/download/manager-v7.4.0/MagiskManager-v7.4.0.apk
Open Magisk manager and click install then "select and patch a file" like in this video
https://youtu.be/USHcCMYlexM
Copy the Patched image from the download folder to your computer adb/fastboot folder
Reboot your phone into fastboot (press and hold power and vol down) and connect it to the computer
Flash that patches image file using fastboot
fastboot flash boot magisk_patched.img
Click to expand...
Click to collapse
fastboot reboot
Click to expand...
Click to collapse
Open Magisk manager and complete the installation if needed. The app will prompt you for action.
Enjoy
Update May 2020
Hello again,
Sorry for being away for so long. Here are some of the things I have noticed people are confused with and need to make them clear:
This method works for ANY Android phone. As long as you have the Correct boot.img and can unlock the bootloader
MAKE SURE 100% you have the correct boot.img file for your CURRENT ROM
MAKE 100% SURE, the boot.img file you get from the FULL ROM zip file, not an OTA update zip file
Make sure you check the date and time of the "magisk_patched.img" file to make sure that is the one you made
Make sure you use the LATEST magisk manager
Make sure you open magisk after flashing the magisk_patched.img as boot image. Magisk manager will tell you if there is another step needed, just click yes and it will be done in seconds
Make sure to enable "Hide Magisk" to allow you to have your BANK apps working as well as security checks
If any app you use gives you an error "YOU ARE Rooted bla bla bla" Use magisk manager to hide the root for this specific app (in the settings)
That's all I can remember, good luck
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Kiwironic said:
Keeping it short. This is a simple way to root your device. You will need a computer and a data cable for this.
Steps:
Download the ROM full zip file. This could be the ROM ALREADY installed on your phone or you are updating your phone to it. Here is a video of one way to get your ROM file.
Open the file and extract "boot.img" on your phone or Computer.
Move the boot.img file to your phone
Download and install the latest Magisk official manager app from here: https://github.com/topjohnwu/Magisk/releases/download/manager-v7.4.0/MagiskManager-v7.4.0.apk
Open Magisk manager and click install then "select and patch a file" like in this video
Copy the Patched image from the download folder to your computer adb/fastboot folder
Reboot your phone into fastboot (press and hold power and vol down) and connect it to the computer
Flash that patches image file using fastboot
Open Magisk manager and complete the installation if needed. The app will prompt you for action.
Enjoy
Click to expand...
Click to collapse
After fastboot flash, reboot, open magisk manager, tap INSTALL beside "magisk is up to date". Then select direct install; reboot.
Works on MIUI 11.0.2; davinciin. ??
I know that when I unlock the bootloader,the phone is going to reset...but,is it going to happen immediately or after that 168 hours of waiting?
Sent from my Xiaomi Mi 9T using XDA Labs
welder73 said:
I know that when I unlock the bootloader,the phone is going to reset...but,is it going to happen immediately or after that 168 hours of waiting?
Sent from my Xiaomi Mi 9T using XDA Labs
Click to expand...
Click to collapse
People report different amounts of wait time, depends on the mi account I think
welder73 said:
I know that when I unlock the bootloader,the phone is going to reset...but,is it going to happen immediately or after that 168 hours of waiting?
Sent from my Xiaomi Mi 9T using XDA Labs
Click to expand...
Click to collapse
Phone is reset when the bootloader is unlocked, not before/during the waiting time.
Can do with locked bootloader?
Micdu70 said:
Phone is reset when the bootloader is unlocked, not before/during the waiting time.
Click to expand...
Click to collapse
Thank you man :good:
Sent from my Xiaomi Mi 9T using XDA Labs
Cabeção-Flu said:
Can do with locked bootloader?
Click to expand...
Click to collapse
No, bootloader has to be unlocked.
@Kiwironic followed your guide and worked very well, although I had to wipe data through the stock recovery to get the phone to boot, I believe that's just how newer Xiaomi phones work. I do have one question though, now that I'm rooted with stock recovery, would I be able to install OTA updates? I'm assuming I would of course lose root and have to redo the process from scratch if that's the case.
Lazer Bear said:
@Kiwironic followed your guide and worked very well, although I had to wipe data through the stock recovery to get the phone to boot, I believe that's just how newer Xiaomi phones work. I do have one question though, now that I'm rooted with stock recovery, would I be able to install OTA updates? I'm assuming I would of course lose root and have to redo the process from scratch if that's the case.
Click to expand...
Click to collapse
I had root on MIUI10 and updated the ROM to MIUI11 then did my root again the way mentioned and did NOT have to wipe. You can get OTA anyway, it will try the update first, it will fail, then it download and install a full ROM zip automatically. You have to wait for it to do that twice, that's all. The first boot after the update takes some time.
@Kiwironic First, thank you so your simple guide!
Can this cause bootloop on my device? If yes, can I simply flash the original boot.img to boot without any data loss?
Also another question: my device is rootless and bootloader unlocked, so my Google Pay doesn't work. When installing Magisk it goes back to work immediately or I have to do something to work?
kryzeK said:
@Kiwironic First, thank you so your simple guide!
Can this cause bootloop on my device? If yes, can I simply flash the original boot.img to boot without any data loss?
Also another question: my device is rootless and bootloader unlocked, so my Google Pay doesn't work. When installing Magisk it goes back to work immediately or I have to do something to work?
Click to expand...
Click to collapse
If you flash the full rom, chances of bootloop is minimal. And should have stock experience except for being unlocked.
I got bootloop, using indian global V11.0.2.0.
After flashing patched boot, it gets bootloop recovery, only way is to wipe all data and reboot
After booting up and opeing magisk it shows a recommendation to install some ZIP
Accepting the recommendation results in bootloop,
Rejecting the recommendation and trying to Install > Direct Install results in bootloop as well
Posted a thread with this issue here
stone_henge said:
I got bootloop, using indian global V11.0.2.0.
After flashing patched boot, it gets bootloop recovery, only way is to wipe all data and reboot
After booting up and opeing magisk it shows a recommendation to install some ZIP
Accepting the recommendation results in bootloop,
Rejecting the recommendation and trying to Install > Direct Install results in bootloop as well
Posted a thread with this issue here
Click to expand...
Click to collapse
This
I got the exact same issue, every time it asked me to install additional zip files it went into recovery immediately after booting up.
Anyone know why this happened?
oblyvision said:
This
I got the exact same issue, every time it asked me to install additional zip files it went into recovery immediately after booting up.
Anyone know why this happened?
Click to expand...
Click to collapse
Do you have stock recovery or TWRP? Which version of Magisk are you using?
I have patched my boot stock image, installed full ROM, then flashed the patched boot image. Magisk did not show any recommendation installation.
There are a few guides online on how to deal with Magisk Bootloop without the need to wipe data.
Kiwironic said:
Do you have stock recovery or TWRP? Which version of Magisk are you using?
I have patched my boot stock image, installed full ROM, then flashed the patched boot image. Magisk did not show any recommendation installation.
There are a few guides online on how to deal with Magisk Bootloop without the need to wipe data.
Click to expand...
Click to collapse
TWRP 3.3.1-8, magisk 20.1
Patching boot image with magisk wasn't a problem. The Superuser itself works normally, module doesn't. The magisk manager suggested to download additional files for the magisk to be working properly.
I'm on MIUI 11.0.1 Global
Was TWRP the cause in the fist place?
oblyvision said:
TWRP 3.3.1-8, magisk 20.1
Patching boot image with magisk wasn't a problem. The Superuser itself works normally, module doesn't. The magisk manager suggested to download additional files for the magisk to be working properly.
I'm on MIUI 11.0.1 Global
Was TWRP the cause in the fist place?
Click to expand...
Click to collapse
On first installation MM asks to download what it needs e.g. to verify SafetyNet. Allow and there is no problem about. TWRP is generally not needed to install Magisk. Things are documented in Magisk guides
https://topjohnwu.github.io/Magisk/
https://www.didgeridoohan.com/magisk/HomePage
oblyvision said:
TWRP 3.3.1-8, magisk 20.1
Patching boot image with magisk wasn't a problem. The Superuser itself works normally, module doesn't. The magisk manager suggested to download additional files for the magisk to be working properly.
I'm on MIUI 11.0.1 Global
Was TWRP the cause in the fist place?
Click to expand...
Click to collapse
Yes, as the title suggests "without TWRP". The reason is, you cannot install OTA and magisk easily without using the stock recovery. Any attempt to update OTA or use any recovery script on the phone will result in a boot loop.
The solution to get out of the boot loop is simple. Actually a couple of solutions.
One, flash your stock recovery, or
Two, flash a full ROM that includes the stock recovery.
No need to wipe data
That's the only reason I made this post and the other about OTA on root. I don't like to use TWRP because I want OTA install without boot loop. At the same time I want root. Hence the solutions I provided
Kiwironic said:
Yes, as the title suggests "without TWRP". The reason is, you cannot install OTA and magisk easily without using the stock recovery. Any attempt to update OTA or use any recovery script on the phone will result in a boot loop.
The solution to get out of the boot loop is simple. Actually a couple of solutions.
One, flash your stock recovery, or
Two, flash a full ROM that includes the stock recovery.
No need to wipe data
That's the only reason I made this post and the other about OTA on root. I don't like to use TWRP because I want OTA install without boot loop. At the same time I want root. Hence the solutions I provided
Click to expand...
Click to collapse
I've tried flashing magisk via recovery and didn't work, the same bootloop. Here's the thread: https://forum.xda-developers.com/mi-9t/how-to/guide-miui-11-v11-0-1-0-pfjmixm-rooted-t3997299
I thought this might be a working alternative.
Gotta try installing magisk with stock recovery then, and if it still didn't work, well, more research for me..
oblyvision said:
I've tried flashing magisk via recovery and didn't work, the same bootloop. Here's the thread: https://forum.xda-developers.com/mi-9t/how-to/guide-miui-11-v11-0-1-0-pfjmixm-rooted-t3997299
I thought this might be a working alternative.
Gotta try installing magisk with stock recovery then, and if it still didn't work, well, more research for me..
Click to expand...
Click to collapse
You have to understand the requirements :
- stock recovery
- install magisk manager app
- patch the boot image for your stock ROM (same version on your phone)
- flash that Patched boot image.
- reboot
- done, that's magisk installed
Hi using latest updated stock rom with root..
Magisk
New August update doesn’t install..
Before i used to install updates in root..
Now cant..
Help..
Do you have twrp installed and if so did you flash any mods to the system?
If no mods were installed just flash the stock boot.img for your firmware version using fastboot and reboot and apply the update
garylawwd said:
Do you have twrp installed and if so did you flash any mods to the system?
If no mods were installed just flash the stock boot.img for your firmware version using fastboot and reboot and apply the update
Click to expand...
Click to collapse
I have only magisk.. I got no mods.. Only by magisk i installed everything... How to get stock boot img? U mean unroot?
I have twrp sharp installed.on slot...
Sami Devo said:
I have only magisk.. I got no mods.. Only by magisk i installed everything... How to get stock boot img? U mean unroot?
I have twrp sharp installed.on slot...
Click to expand...
Click to collapse
Custom recovery that's why you cant install. Ota updates don't usually work with a custom recovery installed. You will have to flash stock boot.img there is a whole thread about this and all versions of the stock boot.img here https://forum.xda-developers.com/mi-a3/how-to/guide-how-to-root-mi-a3-magisk-t3958509/page43
You were even the last person to comment on that thread
My build..
garylawwd said:
Custom recovery that's why you cant install. Ota updates don't usually work with a custom recovery installed. You will have to flash stock boot.img there is a whole thread about this and all versions of the stock boot.img here https://forum.xda-developers.com/mi-a3/how-to/guide-how-to-root-mi-a3-magisk-t3958509/page43
You were even the last person to comment on that thread
Click to expand...
Click to collapse
But i had custom recovery and it installed before..the boot.img have to match with current build? For fastboot flash?? And which slot i have to flash the boot?
This might help (as long as you really read it and follow instructions): https://forum.xda-developers.com/mi-a3/how-to/guide-failed-ota-update-installation-t4041291
_mysiak_ said:
This might help (as long as you really read it and follow instructions): https://forum.xda-developers.com/mi-a3/how-to/guide-failed-ota-update-installation-t4041291
Click to expand...
Click to collapse
This link u give is for flash fastboot rom
Should i uninstall magisk and try?
Sami Devo said:
This link u give is for flash fastboot rom
Click to expand...
Click to collapse
Maybe try to read it at least one more time..
same but different problem.
I'm having somewhat similar problem here, but the thing is, I'm using stock mi a3, without any custom bootloader, twrp, rom, etc.
currently in version 11.0.17.0.QFQMIXM
trying to install the august security update that was supposed to be version 11.0.20.0
updater showed the august update as 464mb, which is weird as its supposed to be 34mb or so.
any help from the experts here are kindly appreciated.
I have no custom recovery, or magisk but have same problem
So I solved the problem as I love root .. I had to loose recovery sharp... Now I have no recovery . I flashed stock ROM of Build 19 and installed the latest OTA . After then I extracted the boot image of stock ROM then I patch stock boot image of latest build.i got now root with magisk with no recovery . I hope I can install future OTA with the method..
If u can't install u must have to flash fastboot..
I have tried restoring stock boot.img of build 19.. but doesn't installed.. although I removed custom recovery but still couldn't install OTA..
Sami Devo said:
So I solved the problem as I love root .. I had to loose recovery sharp... Now I have no recovery . I flashed stock ROM offer BL 19 and installed the latest OTA . After then I extracted the boot image of stock ROM then I patch stock boot image of latest build.i got now root with magisk with no recovery . I hope I can install future OTA with the method..
If u can't install u must have to flash fastboot..
I have tried restoring boot.img of build 19.. but doesn't installed.. although I removed custom recovery but still couldn't install OTA..
Click to expand...
Click to collapse
thanks for the great advice. anyone willing to do the needful, might as well do as suggested. but i kind of trying to keep things stock as much as i can, dont have the time to fiddle around as much. this phone is buggy enough as it is
decided to backup everything and reset for now. might root if resetting didnt fix the issue. cheers mate! :good:
weeeeeeeb said:
thanks for the great advice. anyone willing to do the needful, might as well do as suggested. but i kind of trying to keep things stock as much as i can, dont have the time to fiddle around as much. this phone is buggy enough as it is
decided to backup everything and reset for now. might root if resetting didnt fix the issue. cheers mate! :good:
Click to expand...
Click to collapse
???Yah.. i have some apps which i must use! Such as greenify , titanium backup.. those r core of root..
Am looking forward to meet another update challenge. Am ready.
weeeeeeeb said:
I'm having somewhat similar problem here, but the thing is, I'm using stock mi a3, without any custom bootloader, twrp, rom, etc.
currently in version 11.0.17.0.QFQMIXM
trying to install the august security update that was supposed to be version 11.0.20.0
updater showed the august update as 464mb, which is weird as its supposed to be 34mb or so.
any help from the experts here are kindly appreciated.
Click to expand...
Click to collapse
No its not weird. Becoz july update n also August both have to installed by u...thats y its not only 35mb.ur build is too old. It ought to be a big update
Tyrese117 said:
I have no custom recovery, or magisk but have same problem
Click to expand...
Click to collapse
Then u need to flash fastboot rom
Sami Devo said:
Then u need to flash fastboot rom
Click to expand...
Click to collapse
I have installed July patch without any problem
I have solved this problem
Download recovery rom and flash from stock recovery: APPLY UPDATE FROM SD CARD
Tyrese117 said:
I have solved this problem
Download recovery rom and flash from stock recovery: APPLY UPDATE FROM SD CARD
Click to expand...
Click to collapse
this is very hard work.. i cant do that in every month and retaining root again!
Hello, I am trying to root my a21s problem is whenever I try installing a custom rom I get stuck in a bootloop I have tried 2 custom roms flashed with odin Unofficial twrp and a Magisk patched ap.tar file Both times have put me in a boot loop is there a way to get past this is it possible to root the a21s as of now what other methods could i use
1atom1 said:
Hello, I am trying to root my a21s problem is whenever I try installing a custom rom I get stuck in a bootloop I have tried 2 custom roms flashed with odin Unofficial twrp and a Magisk patched ap.tar file Both times have put me in a boot loop is there a way to get past this is it possible to root the a21s as of now what other methods could i use
Click to expand...
Click to collapse
Stock rom can't be roooted yet. If you need root, install pre-rooted AOSP from Wer99
thatha said:
Stock rom can't be roooted yet. If you need root, install pre-rooted AOSP from Wer99
Click to expand...
Click to collapse
Oh ok his steps where very complicated but I'll try I wish I could use Odin but I can't do think there will be a way to root the stock rom?
1atom1 said:
Oh ok his steps where very complicated but I'll try I wish I could use Odin but I can't do think there will be a way to root the stock rom?
Click to expand...
Click to collapse
As I said, no way to root stock rom now.
If you need root, install AOSP GSI via odin (AP slot). It's very easy and simple. Remember to unlock bootloader first. After installing, it will reboot to recovery, just wipe data and cache, then reboot. Link below:
AP_AOSP_Android_10_A21s
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
thatha said:
As I said, no way to root stock rom now.
If you need root, install AOSP GSI via odin (AP slot). It's very easy and simple. Remember to unlock bootloader first. After installing, it will reboot to recovery, just wipe data and cache, then reboot. Link below:
AP_AOSP_Android_10_A21s
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Click to expand...
Click to collapse
thanks I am currently downloading it to see if it works
thatha said:
As I said, no way to root stock rom now.
If you need root, install AOSP GSI via odin (AP slot). It's very easy and simple. Remember to unlock bootloader first. After installing, it will reboot to recovery, just wipe data and cache, then reboot. Link below:
AP_AOSP_Android_10_A21s
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Click to expand...
Click to collapse
Thanks it worked but I still would like a magisk root magisk is way better it's open source and it has modules and all that I know it's impossible right now do you think I will become a possibility? SuperSu is very untrusted right now and magisk may have just patched the problem read the magisk changelog for v20.4
1atom1 said:
thanks I am currently downloading it to see if it works
Click to expand...
Click to collapse
1atom1 said:
thanks I am currently downloading it to see if it works
Click to expand...
Click to collapse
Also I did a reboot from recovery and it destroyed the OS it bootlooped me over and over kinda messy hoping the android 11 version will work better.