Updating rooted MI A2 by OTA - Xiaomi Mi A2 / 6X Questions & Answers

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.

Related

OTA update problems

So 7-8 weeks ago i played around a little with my mi a2 trying to flash some roms. I was completely new Xiaomi's slot a/b system. I oem unlocked. I accidentally wrote over twrp on both slots and had some problem. I downloaded some image files (i think boot and system) for the V9.6.15.0.ODIMIFE and flashed them. Now run my mi a2 on that version. *Fastforward to now* Now the problem is that I can't install the OTA updates (google drive images). Is it possible to getting the OTA updates again and how would I do that if it works?
Screenshots of error messages
https://drive.google.com/drive/folders/1ITVTRPX2g3iiIqoC9VOsXoNPAG-fMfkZ?usp=sharing
Let me know if you need more information to identify the problem
Help would be appreciated
EDIT: Currently i have twrp/rom on slots a/b
What you need to do is download a dump and flash all original files back to your phone, including boot_a, boot_b, system_a, system_b, and so forth.
You don't need to relock the bootloader.
Tipically the dumps have a "flash all except user data" script that does it for you.
This will remove Magisk/TWRP/whatever you've installed

Rooting Xiaomi Mi 9 and possible issues when OTA update is available.

Hello everyone,
I'm thinking about buying an Xiaomi Mi 9 and I have some questions:
1) How simple is rooting it?
I read this guide and I would know if I need to download the Full ROM, or can I simply install Magisk. Indeed I don't understand the steps about going in Magisk Manager Settings (I never done it).
Can't I simply download Magisk Manager and install it as usual (adb sideload in recovery mode), after unlock the bootloader?
In an other guide I've read that LazyFlasher is required! Is it?
2) If I succed in rooting the Mi 9 with Magisk, when some OTA update is available, may I have some problems when I update it?
I mean... with my old Samsung Galaxy S5 (with LineageOS and rooted with Magisk) when I have an OTA update I simply download it, starting the install the phone starts in recovery... it flash the update, and after the first boot (not rooted anymore) I go in recovery again and I install Magisk for restore the root. Can I do the same thing with the Mi 9?
If someone have a tested guide or some advice about rooting I appreciate it.
Thanks everyone.
I think it's simpler to root with TWRP. I never really got the hang of the method where you use Magisk Manager to flash the stock boot image so you can perform a normal OTA. I tried on a couple phones but never got it to work right. Maybe you will have a better result.

G970F questions for navigating flashing without bricking

Hello,
I purchased a G970F for the second time because I hard-bricked the first one due to not exercising as much caution, and since then, I've learned about the added difficulty the S10 generation has compared to the only other Samsungs I've had the displeasure of working with (S5, S4). I've read a number of guides since then, but I'm not entirely sure which still apply and which do not, since a lot of them are from 2019 / early 2020, and I've somehow managed to only soft-brick it once before bringing it back to current condition.
So, where I stand with my G970F:
Bootloader unlocked, downloaded the latest firmware via Frija (Android 11), patched the AP file, flashed the patched AP, along with BL, CP, CSC via Odin, booted with Magisk, then installed TWRP with SU privileges by downloading TWRP on the Play Store, going through the steps, yadda yadda. I've followed the two official guides (Official installation steps for Magisk by John Wu, and TWRP installation guide for Samsung Galaxy S10e (Exynos), also on the official page.
This is where I get stuck. I've come across some older guides on XDA that mention flashing multi-disabler, as well as mention of disabling FBE immediately after installing TWRP, on the TWRP 3.4.0 for Galaxy s10 Exynos thread on XDA. I don't know if these still apply (they're from 2019), because when I tried disabling FBE and booting to TWRP, it still shows the directories as encrypted hash, and when I tried flashing the multi-disabler on TWRP and rebooting, it gets stuck on Samsung splash (soft bricked), so I had to reboot to TWRP, reboot to download mode via ADB, then reflash the firmware with patched OS to start over. Multi-disabler soft-bricked my device, so I'm guessing it's not compatible with devices with Android 11?
The end goal for me here is to flash a custom rom safely, but I'm concerned about a few things:
The first time I hard-bricked my first G970F, it was during a root attempt, and the last thing I did was wipe data on TWRP, flash a zip, and reboot - and this essentially made it impossible to get into either Download mode or Recovery, it would just vibrate on black screen, stuck in a forever boot loop with no means to turn it off. I had to open the device to manually disconnect the battery.
I'm being extra cautious not to repeat the above scenario, so here is where my concern is: I've read that S10 series only have an A partition which leads to Magisk having to reside in a parasite-like existence with recovery, and the other landmine is that there is a 'VaultKeeper' that locks up the bootloader if an unauthorized OS is detected or some sort? I'm thinking that maybe either of these was responsible for my first G970F being stuck in an unbootable state, so I want to navigate carefully here.
I want to flash one of the unofficial roms linked on XDA by @expressluke , and I have Magisk patched AP + stock firmware + TWRP, only steps I have taken were from the two official guides (not XDA threads) for TWRP and Magisk, which never mentioned 'multi-disabler' nor disabling FBE. From my current state, how do I go about flashing the custom rom without potentially damaging recovery / partitions / triggering some Samsung trap like VaultKeeper? I'm a bit keen to do this, since it looks like having Magisk + stock firmware for some reason only recognizes my storage as 32GB instead of 128GB.

Question HELP | How to go back to official recovery?

I bought a used MI 11 Ultra running Xiaomi EU MIUI 13 Stable. The phone had the stock Xiaomi recovery on it, and I tried to flash TWRP onto it.
After having flashed multiple phones with TWRP and custom ROMs before I have run out of patience with this one. TWRP refuses to work. I can flash it and boot onto it the first time, then boot into MIUI. However, any time after that TWRP is useless and unresponsive. Now I have no usable recovery. I am not flashing anything from it, I'm just trying to make it work.
I am aware of the fact that MIUI 13/ Android 12 does not support flashing by TWRP YET, but this is something I wanted to take care of now before I setup the phone for the first time so that when TWRP adds support for Android 12 then I would have it already installed.
At this point I just want to flash the official/stock recovery on the phone, but I can't find a single thread on that.
I'm also worried about the fact that the phone may ask for the password for the MI account that was used to unlock the bootloader.
What should I do?
Any help would be appreciated.
I may be wrong - but the first thing I'd try is to find a stock package, explore it's assets, find the recovery image and flash it with fastboot.
fastboot flash recovery recovery.img
It may or may not work, but I'd try it, before I try going "full-stock" by flashing a complete image.

Question attempt to root on POCO M3 Pro 5G without TWRP

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

Categories

Resources