Hi
I have mi a2 rooted on 10.0.8.0 with magisk. I wanted to know how could update through OTA.
This is my first time rooting a device so I am a bit worried about bricking the device so please mention the procedure in detail.
As you obviously have unlocked phone, it is easier to flash via fastboot the latest stock 10.0.10.0 ROM image http://bigota.d.miui.com/V10.0.10.0...0.PDIMIXM_20190611.0000.00_9.0_9e6473956a.tgz
Guides are in corresponding section of this forum. Note to use "flash_all_except_data.bat" (and not other command files in ROM image) to have your data safe.
Then get patched boot image https://forum.xda-developers.com/showpost.php?p=79757523&postcount=28 , boot into it and restore root.
If you still decide to update by OTA, read appropriate Guide in corresponding section of this forum (uninstall Magisk restoring stock boot., etc.), but even if you have not changed /system and correctly restore boot, you can encounter bootloop after "successful" OTA, nobody yet knows why... and then you'll still return to flashing stock ROM via fastboot.
There is a guide on Mi A2 lite's forum just for this thing. It's been 3 months since I rooted my phone and I've been following the steps mentioned there and it works. It's a bit hit and miss but I've learned to work my way around the problems.
Hello everyone,
Today I had a notification telling me that there is a new version of both magisk manager and module. Therefore I first updated the manager successfully and proceeded to update the module through in-app flash. After the flash completed, app prompted me to reboot. However, the reboot process never finished and the phone got stuck while booting. Since then I only tried factory reset which only booted the phone to let me enter my sim card password but after that, it rebooted itself to boot loop again. Some info about the phone:
TWRP installed and still working,
Latest xiaomi.eu from that won't boot anymore,
Only viper4droid and youtube vanced modules were installed.
AdAway for obvious reasons.
and that's it. Now I am planning on flashing crdroid ROM to make the phone work again but the installation process requires me to do:
Flash MIUI11 eea with miflash : min V11.0.8.0.QFAEUXM note : if already on v11.08.0 there's no need to redo
Flash vbmeta.img with "fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification" note : if already done there's no need to redo
Flash TWRP in fastboot and boot into TWRP
Click to expand...
Click to collapse
is there a step that I should skip? It's been 6 months since I handled the initial process to be able to flash xiaomi.eu from therefore I don't remember how I exactly did that as I have only been OTA updating the from since then. I don't remember or know how to flash V11.0.8.0.QFAEUXM nor vbmeta.img nor TWRP. I don't even know if I "should" flash those. I am open to any different suggestions or help to let me achieve my goal of flashing crdroid to get out of this mess.
Thanks in advance!
Want to confirm before proceeding, I find this instruction.
How to Root Xiaomi Mi 11 Ultra and Unlock Bootloader
Want to root Xiaomi Mi 11 Ultra with Magisk? Here's how to root Mi 11 Ultra along with a guide to unlock bootloader.
www.ytechb.com
I've already unlocked the bootloader, want to make sure it is safe to do so (won't brick etc)
bump, anybody successfully rooted the phone?
linnil said:
Want to confirm before proceeding, I find this instruction.
How to Root Xiaomi Mi 11 Ultra and Unlock Bootloader
Want to root Xiaomi Mi 11 Ultra with Magisk? Here's how to root Mi 11 Ultra along with a guide to unlock bootloader.
www.ytechb.com
I've already unlocked the bootloader, want to make sure it is safe to do so (won't brick etc)
Click to expand...
Click to collapse
You need to patch to boot image a and boot image b
As descriped here. This worked on my MI11
https://www.getdroidtips.com/root-xiaomi-mi-11/
linnil said:
bump, anybody successfully rooted the phone?
Click to expand...
Click to collapse
Yes. I patched my boot.img with magisk, then flashed it using "fastboot flash boot_ab magisk_patched(boot.img file name).omg"
Caveat: I bricked my device like many others after unlocking the bootloader and flashing xiaomi.eu ROM. I had to have a authorized EDL account holder flash a factory ROM (in my case I had a China variant flashed with the Global ROM), after which I flashed xiaomi.eu latest stable ROM and then rooted it.
does google pay still work after root?
xreactx said:
Caveat: I bricked my device like many others after unlocking the bootloader and flashing xiaomi.eu ROM. I had to have a authorized EDL account holder flash a factory ROM (in my case I had a China variant flashed with the Global ROM), after which I flashed xiaomi.eu latest stable ROM and then rooted it.
Click to expand...
Click to collapse
I still don't get, how you all bricked your phones? I was able to unlock (granted, after 7 days) successfully and update CN with EU-ROM... There's thread for it in this forum.
[ROM][MIUI][star/mars] Xiaomi.eu ROM for Xiaomi MI 11 Pro / Ultra
How to install Xiaomi.eu ROM for Xiaomi MI 11 Pro / Ultra We will release fastboot ROM versions until TWRP for star/mars is released TWRP RELEASED Steps to install xiaomi.eu ROM for first time from China ROM (All your data and files on...
forum.xda-developers.com
SanHelios said:
I still don't get, how you all bricked your phones? I was able to unlock (granted, after 7 days) successfully and update CN with EU-ROM...
Click to expand...
Click to collapse
Seems it was an issue with setting the active slot in the installation script. Solution is described here and since then it looks as if no more bricks occur
s3axel said:
Seems it was an issue with setting the active slot in the installation script. Solution is described here and since then it looks as if no more bricks occur
Click to expand...
Click to collapse
Oh thanks, mate. I missed that one..
Now back to issue, does it work, rooting the device the way it is descibred on that page?
SanHelios said:
Oh thanks, mate. I missed that one..
Now back to issue, does it work, rooting the device the way it is descibred on that page?
Click to expand...
Click to collapse
My pleasure
And yes, I rooted my device this way although I took the "fastboot flash boot_ab" approach instead of the separate flashing of a and b.
For updating the ROM I took the boot image before installing, patched it with Magisk, copied it back to the images installation folder and let the update script do its magic - thus I got instant-root for the update...
s3axel said:
My pleasure
And yes, I rooted my device this way although I took the "fastboot flash boot_ab" approach instead of the separate flashing of a and b.
For updating the ROM I took the boot image before installing, patched it with Magisk, copied it back to the images installation folder and let the update script do its magic - thus I got instant-root for the update...
Click to expand...
Click to collapse
well, i just rooted it according to the site's instructions.. it booted up, BUT the Safety-Net-Check was negative... Did i miss something?
you n
SanHelios said:
well, i just rooted it according to the site's instructions.. it booted up, BUT the Safety-Net-Check was negative... Did i miss something?
Click to expand...
Click to collapse
you need to hide Magisk Manager and also Magisk hide Google Play, Play services and Google Services Framework
s3axel said:
My pleasure
And yes, I rooted my device this way although I took the "fastboot flash boot_ab" approach instead of the separate flashing of a and b.
For updating the ROM I took the boot image before installing, patched it with Magisk, copied it back to the images installation folder and let the update script do its magic - thus I got instant-root for the update...
Click to expand...
Click to collapse
I flashed it separately on the second attempt for 12.5.3. The first time I tried flashing the patched boot.img I was greeted with an error.
Hi! I have the latest xiaomi eu weekly installed (21.6.23) as well as unofficial twrp.
I would like to root the phone with magisk, but I don't understand a few things.
Magisk manager require patching the boot.img file from the zip firmware.
I can not just simply install magisk zip file in twrp to root mi11 ultra?
If not, I understand that I have to patch the boot.img- but do I have to do it every time I want to install update of the latest xiaomi.eu firmware?
The second question is about data.
Am I loosing the data by rooting the device by this method?
EDIT:
Ok, I managed. So those are the steps that I did:
I unpacked the boot.img from the xiaomi.eu firmware in my phone. Then I patched the file, and copy this file to the adb installation folder of my pc.
Later it's easy- usb debugging needs to be active in developer options, then connect your phone by the cable to your pc, accept usb debugging in your phone, start CMD in the adb folder in your pc and write the command:
fastboot flash boot_ab nameofthefilewhatmagiskgenerated.img
then
fastboot reboot
And done, root works. Data are untouched.
I did it easier, boot into twrp and flash magisk.zip done
Also I'm on official EEA firmware, with original stock recovery, so doesn't matter what rom you use. On xiaomi EU you don't even need adb because you already have twrp injected
Is there anything to worry about when you update the phone while having root access?
Is the following order right?
1) update Rom over twrp and delete dalvik&cache
2)flash magisk.zip again
3)boot into system
Right ?
I have the latest EU Rom 12.5.7...
Just take this bat with decrypted Star twrp 3.5.1
unzip and klick Install-Star.bat
fastboot boot star.img are the commands in there
xNAPx said:
I did it easier, boot into twrp and flash magisk.zip done
Click to expand...
Click to collapse
how did you get twrp on your mi 11??? I cannot find a working method. I have Global ver
ottjoshua said:
how did you get twrp on your mi 11??? I cannot find a working method. I have Global ver
Click to expand...
Click to collapse
Hello all. first post here as i only recently found this great site. So ive been wanting a rooted phoje for a long time now as i iswd to jailbreak my uphone back when i used apple and hadnt learned of Androida greatness. I got a pixel 5a and i love it! Its different and i just love it. Maybe more than my s21ultra even. Anyways I updated to android 12 beta and then tried to root my device. I've never done this before so i tried to learn as much as possible. Anyways I followed the magisk tutorials and unlocked my boot loader and downloaded the boot.IMG for Android 12 and patched the image then did the fastboot and adb stuff only to end up with my phone not working. Clearly I did something wrong. It originally said on the fastboot menu failed to load or verify boot image. And was stuck on that menu. Tried to recover reboot and it stayed the same. Somehow I got it to restart then it was in a bootloop going to google to the unlocked bootloader warning screen over and over. I got frustrated and left it. It died and put it on the charger and it was in rescue or recovery mode saying no command. I got it into recovery menu and tried to factory reset and now it boot to the white google screen. I wanna flash it back to android 11 that it came with so I can eventually try and root it again as that seems much more successful then Android 12. ANy help is very appreciated and I am a SUPER noob at this and don't know about any of it so please keep that in mind when replying. Thanks
You needed to disable verification and dm-verity when flashing the android 12 beta.. You're stuck at fastboot now because of this..
The solution is to use the Google flashing tool, and re-flash android 11 w/ wiping the data selected.. You can try without having wipe data selected, up to you.
P.S. while I recommend you stay on Android 11 if you want a less buggy rooted phone, follow guide #1 on this thread here if you wanna use android 12 beta w/ Magisk:
[Guide] Flash Magisk on Android 12
Trying to root the Pixel 5 running Android 12 by flashing a magisk-patched boot image results in the phone only booting to fastboot mode ("failed to load/verify boot images") Some users have reported that booting (instead of flashing) the patched...
forum.xda-developers.com
bobpiesz said:
You needed to disable verification and dm-verity when flashing the android 12 beta.. You're stuck at fastboot now because of this..
The solution is to use the Google flashing tool, and re-flash android 11 w/ wiping the data selected.. You can try without having wipe data selected, up to you.
P.S. while I recommend you stay on Android 11 if you want a less buggy rooted phone, follow guide #1 on this thread here if you wanna use android 12 beta w/ Magisk:
[Guide] Flash Magisk on Android 12
Trying to root the Pixel 5 running Android 12 by flashing a magisk-patched boot image results in the phone only booting to fastboot mode ("failed to load/verify boot images") Some users have reported that booting (instead of flashing) the patched...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks for the help I really appreciate it! I'm gonna give it an attempt right now.
I am facing the same type of problems for so long now.
Seems Magisk breaks booting when on the 12 S bootloaders :c even with disable-verity and disable verification in any step of the process
Disabling verity and verification is no longer required with Magisk 23016.
Follow my guide here, use the Factory Image method.
Hello to all,
I tried 1 year ago to root my POCO M3 Pro 5G but could not succeed to install TWRP unofficial for this model because of the problem of non-existent recovery partition (see https://forum.xda-developers.com/t/...oco-m3-pro-5g-redmi-note-10-5g.4474375/page-2) In short I bricked my device several times and then I had a boot with a weird screen that disappeared when I updated to MIUI 13.
Today I am on Android 12 MIUI global 13.0.3 and I would like to install magisk manager without the help of TWRP and I have the default recovery of MIUI with which I can not install anything.
I had also followed the procedure described https://forum.xda-developers.com/t/...urself-and-optionnal-debloat-privacy.4337693/ but without success impossible to flash on A or B : error messages : too many links, the partition does not exist (see screen shot in PJ), no emulator etc
The bootloader is still unlocked
I would like to root my phone and use Magisk manager modules such as Skvalex without damage or install root apk with spyware and trojan.
Do you have any solutions for me?
Thank you very much for your answers.
ROOT GAINED !!!!
THIS METHOD WORKS on both: POCO M3 Pro / Redmi Note 10 5G hey guys.. wonderful news.. been trying here and there and IT WORKS FINALLY i gained root of POCO m3 Pro 5G ! i'll write in steps how it works and post all files i've been using...
forum.xda-developers.com
Ok tx I'll try this method and let you know
install magisk via fastboot is the easiest way for rooting. and more safe than using custom recovery. follow the guides with more attention. bad twrp can damage bootloader. bad flash of stock can damege device
i think the twrp have broked your boot, and i suppose u have flashed a wrong stock rom.
before made other damage, if can enter into fastboot: be sure to download right firmware. and flash it without relock option. if u dont do this, the risk is a serious hard brick. for who is not able to do a simply procedure like rooting, an hard brick is impossible to repair . be carefull
I have rooted my phone with magisk without any recovery, you just have to modify boot.img and flash it using fastboot.
I followed this method- https://www.getdroidtips.com/root-poco-m3-pro-5g/
Good evening
Thanks for your 2 answers.
I finally succeeded in laboriously rooting and patching on A and B but the modops on https://www.getdroidtips.com/root-poco-m3-pro-5g/ are incomplete and/or inaccurate. For example it is necessary to specify that it is necessary to download not the recovery version of the ROM but the fastboot version which is not underlined in the text of the link and other details of this type which avoid wasting time other example to find in the repertory the file of the patch.img even not hidden difficult to find even with the way and invisible via the directory of windows.
I have the root and I have installed modules on Magisk manager finally after the first attempt 12 months ago.
Cheers