yashsingh1/xdaforums huggingface dataset:
[Xiaomi Mi A2 Lite Guides, News, & Discussion] a1291762:
If you didn't flash boot, the OTA would have failed, so that part is clear.

I flash vanilla boot and boot patched boot so that Magisk is active.

Since you were applying the OTA without Magisk active, you had no ability to extract the new vanilla boot or install Magisk to the new boot. That's not a problem per-se... You just have to run more steps after reboot (see grufty47's instructions).

When you rebooted... Did you click the OTA reboot button or something in Magisk manager?

If the system rebooted without changing to the other slot, I can see that causing a problem. The current slot had 10.0.14.0 but the data partition will have post-install stuff for 10.0.15.0. I wouldn't necessarily expect that to break the boot, depending on what that post-install stuff did.

If it did correctly boot to the other slot, there's nothing here to indicate why it should have had an issue. It was a standard OTA after all, with vanilla everything.

I don't know. There don't seem to be guides written up by anyone which suggests nobody else knows either. I found some encryption-looking things on partitions and even partitions that looked like encryption stuff. There are generic guides to how encryption works on newer devices but there's missing details.

You can use the encryption disabler hack to prevent /data being encrypted in the first place. That's commonly done with custom ROMs.
[Xiaomi Mi A2 Lite Guides, News, & Discussion] sebadamus:
Yup! I did the OTA since I bought the phone with version 10.0.9 I think... and have followed the steps right. But this time happend this with the "password asking" maybe I was not precise as I should.

I click OTA reboot, as I couldnt do anything else with Magisk manager (because I boot with vanilla boot image and also had flashed vanilla boot image 10.0.4.0, almost sure...)

Yes, you right... clicking OTA reboot like a normal update, then it shoud change slot automatically. I remember this, as soon as it rebooted and restart where the android colored line in middle screen shows "its doing something" I wait about 10 minutes and nothing happened (this also happened me once before after an update... and I just hold power button to restart and it passed the "doing nothing screen" and booted ok and updated). But this time, after doing the same it came up with the android password asking.

May be I had to wait more than 10 minutes after OTA reboot? damn I could not see what was it doing really in the boot process (cant adb logcat there)

Will get that encryption disabler next custom rom I get! but for now will stay stock and magisked, hope Android 10 get out soon.

Thanks for you clear explanations and time with answers :highfive:
[Xiaomi Mi A2 Lite Guides, News, & Discussion] a1291762:
I finally got around to testing this when I did the 10.0.16.0 OTA.

I can have both Magisk 20.1 and TWRP 3.3.1 installed and working at the same time.
[Xiaomi Mi A2 Lite Guides, News, & Discussion] grufty47:
When you're in TWRP, you can still get access to the by-name labels (so you don't have to guess at partition numbers). They're just in a slightly different path: /dev/block/platform/soc/7824900.sdhci/by-name[/QUOTE]

Yes, you can! The boot images are also saved in </dev/block/platform/soc/7824900.sdhci/by-name/boot_a> or </dev/block/platform/soc/7824900.sdhci/by-name/boot_b> respectively.

I just did the upgrade to 10.0.16.0 using the procedure in post #69 with comparing the check sums of the boot file in both locations, yes, they are the same.

There are just 2 issues left:

1.) What to do if you experience the password horror (if anything goes wrong). I know nothing else but factory reset or full flash and relying on your back-up.

2.) How to get into the system if no reliable TWRP is available (e.g. shortly after the launch of a new device)? That is to say how do you get administrator rights on your android via a terminal emulator?

feel free to build your own magisk_patched with the files attached:

https://drive.google.com/open?id=1LIW00dU7OpDjRmRGlntSqVUTcGNG-0I_

regards grufty47
[Xiaomi Mi A2 Lite Guides, News, & Discussion] a1291762:
The password thing is concerning. To me it looks like the encryption keys are corrupted but I'm not sure of the cause.

This phone doesn't need TWRP to get root. You can use Magisk manager to patch a vanilla boot obtained from fastboot image. That's what I did at the start because the posted Magisk patched images were all old.
[Xiaomi Mi A2 Lite Guides, News, & Discussion] grufty47:
This phone doesn't need TWRP to get root. You can use Magisk manager to patch a vanilla boot obtained from fastboot image. That's what I did at the start because the posted Magisk patched images were all old.[/QUOTE]

You are saying that the boot file doesn't change anyhow with the security patches, hence we can take the boot file from the official fastboot ROM (currently 10.0.13.0) to create the magisk_patched.img to install Magisk after an OTA? Ok, sounds logically!(As far as I remember I had observed different sizes of the various boot/patched_boot images, maybe I was wrong).

Ok, forget about the need for TWRP to retrieve the boot file for installing Magisk!

Thanks

grufty47
[Xiaomi Mi A2 Lite Guides, News, & Discussion] a1291762:
No.

Booting a 10.0.13.0 boot with a newer system is likely to bootloop or corrupt your encryption keys.

If you're running > 10.0.13.0 then you can't get a fastboot image (since they have yet to be released) but you may still be able to use one of those "full OTA" packages to get a vanilla boot image.
[Xiaomi Mi A2 Lite Guides, News, & Discussion] grufty47:
??? I am now on PKQ1.180917.001.V10.0.16.0.PDLMIXM. My view is that the newest official ROM is 10.0.13.0 PDLMIXM (re MIUI web page on http://c.mi.com//miuidownload/detail?device=1700354).

Which "full OTA" did you use to get a vanilla boot image, Which version 10.x.x.x refers to "vanilla"?

grufty47
[Xiaomi Mi A2 Lite Guides, News, & Discussion] a1291762:
When I first got the phone, I got the image from a fastboot ROM. Can't remember exactly, probably Oreo though.

Now I back it up while doing the OTA. Handy when there is no fastboot image released.

Magisk OTA process existed for a long time if you don't want to backup but still want to OTA...
[Xiaomi Mi A2 Lite Guides, News, & Discussion] a1291762:
The "full OTA" I mentioned is those .zip that get posted. It's what your phone downloads for OTA if you're on an ancient version. I think that unlike a regular OTA they have complete partitions, at least for boot...

Anyway, I've never directly used one.

This page seems to have a collection.

https://mirom.ezbox.idv.tw/en/phone/daisy/roms-global-stable/
[Xiaomi Mi A2 Lite Guides, News, & Discussion] barumbads:
thank you for sharing your information. really helpful ?
[Xiaomi Mi A2 Lite Guides, News, & Discussion] grufty47:
I am still a bit puzzled, I think the "OTA" includes just those parts of the official fastboot rom that are changed by the security updates, there are no "full" or "regular" OTA's. Maybe each OTA has a boot partition included, unfortunately there are no copies of the last OTA's to be found in /data/ota or /data/ota_package. Currently the newest official fastboot rom is V 10.0.13.0, as posted on the miui web site. Any other fastboot roms posted on the web (as above) are created by the uploader from individually composed images.

If there is effictively a risk to use the the boot from the official fastboot rom (i did not use it for the latest updates) and no backed up initial boot image is available I'd suggest another proposal to retrieve the boot image from the OTA: Download the OTA but don't install it. Since Magisk root is still active we could search for the OTA ( in /data/ota or /data/ota_package?) save it to the extsdcard and retrieve the latest boot image from the OTA. Afterwards Magisk can be uninstalled and the installation process for the OTA can be continued. What do you think?

grufty47

PS: checking the V.13 ROM on

http://c.mi.com/oc/miuidownload/detail?device=1700354

shows a "last changed date" of 12/31/2008 for the boot, system, system_other and vendor partition. All the other partitions have been compiled on 08/13/2019, hence the boot file is always the same???
[Xiaomi Mi A2 Lite Guides, News, & Discussion] a1291762:
There are 2 kinds of OTAs.

https://www.the***********.com/how-to-extract-android-payload-bin-file/

Your process sounds overly complex and is likely to be foiled by the phone downloading a partial OTA rather than a full OTA. If you've got a root shell just use dd? Uninstalling Magisk from Magisk manager only works if you don't have TWRP. I guess you could dd the vanilla boot to a running system though (I guess that's what Magisk manager does under the hood).

Timestamps in archives can't really be trusted. Maybe those files have changed, maybe not. Do a checksum comparison to the previous release if you want to be sure.
[Xiaomi Mi A2 Lite Guides, News, & Discussion] a1291762:
For [MENTION=9349520]grufty47[/MENTION]...

1) download miui_DAISYGlobal_V10.0.16.0.PDLMIXM_71b77f7c2b_9.0.zip (OTA link from before)

2) download payload_dumper.zip (previous link)

3) install termux (play store or fdroid)

4) termux-setup-storage

5) pkg install python

6) cd /sdcard/Download

7) unzip miui*.zip

8) unzip payload_dumper.zip

9) cd payload_dumper

10) pip install -r requirements.txt

11) python payload_dumper.py ../payload.bin

Vanilla 10.0.16.0 boot.img in output/ without root or PC. Its 27Mb.
[Xiaomi Mi A2 Lite Guides, News, & Discussion] grufty47:
Sorry for always picking on retrieving the correct boot image to be used for Magisk patching. Perhaps I should discuss this under BlubuXP's thread <Installing Magisk... >, because I don't keep TWRP installed just boot it in case of need. Using my procedure described previously (removing Magisk, doing OTA, retrieving boot images with TWRP) I have updated to 10.0.16.0 without problems. Now I am just wondering about retrieving the boot image without TWRP only using the official global rom and adb/fastboot or Linux tools.

I don't have problems with different compression formats. I use the payload_dumper-win64 tool to extract images in payload.bin format. My termux doesn't offer a root shell for android smartphones hence no chance unless rooted otherwise.

Studying the Miui/Xiaomi web sites I understand that for the MI A2 lite there is no basic stock rom available at all, there are just the recovery ROMs, the latest being the V 10.0.13.0. Incremental OTA's could not be found on the web. After the release of a new OTA new recovery ROMs including the latest security fixes or any other updates are (unofficially???) published in the web.

And yes, it is true, timestamps cannot be trusted. However, examinig the hashfiles of boot images I found discrepancies for the same load depending on the source (miui, bigotta, etc). Ok, let's wait and see, Perhaps at the next update I try saving the OTA after download with Magisk still active, then uninstalling Magisk and installing the OTA. Hopefully the update includes the boot image else I can use dd or TWRP to retrieve the boot images (for patching with Magisk again)

grufty47
[Xiaomi Mi A2 Lite Guides, News, & Discussion] a1291762:
The site I found recently posts links to both fastboot (what I've known as stock roms) and recovery (what I'd call full OTA). The links are all to bigota.d.miui.com.

https://mirom.ezbox.idv.tw/en/phone/daisy/roms-global-stable/

Most people have no need to download an incremental OTA because it's only useful to get from one specific version to another. An incremental OTA isn't going to help you get a vanilla boot image, since it only has the differences.
[Xiaomi Mi A2 Lite Guides, News, & Discussion] grufty47:
Totally agreed.

Official Global Stable Full ROM to be used with fastboot or Miui Flash is posted on:

https://c.mi.com/oc/miuidownload/detail?device=1700354

An updated but uncomplete version of the Global Stable ROM, called Recovery ROM, including at least all the partitions with modifications by security fixes and other (stability?) updates is shipped as payload.bin and posted on:

https://mirom.ezbox.idv.tw/en/phone/daisy/

At the same website above the incrementel OTA files with those security fixes and other (stability?) updates are posted.

The boot partition should not be normally affected by OTA, therefore the correct boot file to be used for rooting by patching with Magisk should be included in the latest recovery ROM.

By the way, unlike any other recovery ROM I cannot unpack the payload.bin coded latest OTA (15 to 16) on win10. Did you succeed so? I'll try now with payload_dumper.zip for Linux (to be used with termux) and your commands. Keep fingers crossed.

Kind regards

jochen47
[Xiaomi Mi A2 Lite Guides, News, & Discussion] a1291762:
payload_dumper is the first thing I found for unpacking payload.bin. It's python so it should work on any OS. I have a Mac at home but I ran it on my phone so I could verify the instructions without having to go sit in front of it ;)

I did not attempt to use the unpacked boot.img in any way...
[Xiaomi Mi A2 Lite Guides, News, & Discussion] grufty47:
Thanks, this works perfectly! The unpacking of the V.15 to V.16 OTA with the above command suite confirms that the OTA update contains just the code modifications of/within the updated partitions, e.g. no full functional partitions. Whereas the Recovery ROM consists of the complete updated partitions, however, the Recovery ROM does not comprise all the partitions/folders required for the official Global Stable ROM.

Therefore, the boot file for Magisk patching must be taken from the Recovery ROM or extracted from the device immediately after OTA. Thanks for contributing to this clarification!

grufty47

PS: Another proposal to resolve the problem of retrieving the correct boot file to patch has been posted in the faq section of:

https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/

"On an A/B device you dont need to care about losing root. After the update just reboot to new system, set the old partition active, reboot, get root on your old system and extract the new boot.img, patch it with magisk manager. Reboot and set updated partiton as active again flash patched boot.img and you are done."

Be careful! I changed the active slot b on V10.0.16.0 to slot a, rebooted ... and ended up in a mess! Password error (PE), returning to slot b gave PE again. I only use the SIM PIN. Booting and flashing boot_a|b, patched_boot_b and system _a|b did not help. Factory reset with TWRP was the only way out.
[Xiaomi Mi A2 Lite Guides, News, & Discussion] a1291762:
I didn't get offered the OTA before it got pulled. Is it worth tracking down a link (I have the apparently safe goodix panel)? It sounds a bit rough even on the good systems...
[Xiaomi Mi A2 Lite Guides, News, & Discussion] grufty47:
Sorry, I'd better been more precise. I am living in Germany, a couple oft days ago I manually checked for updates and was then offered to download the Android 10 release. OK, Magisk uninstalled, Android 10 downloaded, installed and up to now everything is fine. Apps including banking apps are working, however, I don't dare to install Magisk as of now. Let's wait and see...

grufty47

Today, 13th June 2020, I successfully updated manually from V11.0.2.0.QDLMIXM to V11.0.5.0QDLMIXM using Muhammad Asif Quasim's ver straightforward way at:

https://xdaforums.com/mi-a2-lite/how-to/how-to-manual-update-v11-0-4-0-users-t4082815

The only problem was to get into the recovery, very tricky, it appears you have to observe some strange timing aspects.

Anyhow, I was fine with V11.0.2.0.QDLMIXM (perhaps of goodix touch panel?) but I could not implement any OTA-Update.

Waiting for the next security-update to run smoothly before loading Magisk or booting TWRP...

Cheers grufty47
[Xiaomi Mi A2 Lite Guides, News, & Discussion] a1291762:
I was offered 11.0.4.0 (again) and this time it didn't disappear half-way through installation...

Even though the payload is a "full" one, I still had to revert my partitions (or maybe just boot?) to stock because the post-install hadh validation failed.

I got stuck on the boot animation with Magisk but the system booted fine without Magisk.

I booted TWRP and used /sdcard/mm (MagiskManager module for managing Magisk modules from TWRP) to disable my modules and then enabled them until I isolated the culprit.

It's one/both of these:

Riru - Core v19.5

Riru - EdXposed v0.4.5.1_beta(4463) (SandHook)

I only have a single EdXposed module (since everything else stopped working). The module suppresses the "Install Google Play Games" prompt so many games insist on showing me. I can certainly live without that, in the event that Riru/EdXposed isn't updated to work with Android 10.
[Xiaomi Mi A2 Lite Guides, News, & Discussion] a1291762:
I previously hid (using terminal debloater) Quickstep so that I got the old multitasking experience. In Android 10, the system launcher is called AndroidOneLauncher and disabling it does not restore the old multitasking experience :(
[Xiaomi Mi A2 Lite Guides, News, & Discussion] Antho02:
hi,

well i have different problem here

used xiaomi flash to update from 10.0.20.0 to 11.0.4.0 --> works ok

then i boot twrp and install --> works ok

then i boot magisk patched --> i never arrived to pin code, bootloop and suddenly blackscreen , then twrp

and now the phone always goes to twrp, only way to run the phone "normally" is fastboot boo.img :(
[Xiaomi Mi A2 Lite Guides, News, & Discussion] a1291762:
Apparently the lesson here is to check for updates before upgrading, since both of these had updated packages (Magisk Manager only checks for updates manually, it doesn't notify you that a module can be updated).
[Xiaomi Mi A2 Lite Guides, News, & Discussion] a1291762:
So... you can boot a vanilla_boot.img but not a patched_boot.img?

That seems to indicate a Magisk Module is causing a problem.

From TWRP, you can use mm (Magisk Manager for recovery) to disable Magisk modules. If you don't have that, there's probably a way to do it manually (I think you just put an empty file called 'disabled' into directories under /data/adb/modules/*).

Did you make the patched boot yourself? If not, can you try that (point Magisk Manager at your vanilla_boot.img and let it make a patched_boot.img for you).
[Xiaomi Mi A2 Lite Guides, News, & Discussion] Antho02:
hi. the biggest problem is that my phone allways booted on twrp when i turned it on, only way to boot to android was using fastboot command on computer....

btw after several tries i advanced a bit, to "repair" it a had to fastboot flash boot_a/boot_b (untouched) boot.img , and then force a retry in stock recovery

i tried twrp+magisk again, with one patched from xda and one patched by myself but always same results

i missed time so passed twrp and try only magisk without outdated edxposed and it works well

so today ill same configuration but 1st install twrp.... crossed fingers
[Xiaomi Mi A2 Lite Guides, News, & Discussion] a1291762:
fastboot flash boot_? vanilla_boot.img should "fix" that.

May I suggest following the guide's process?

I always had trouble in the past booting after installing TWRP, so I have not done that for a very long time. Instead, I install TWRP, fastboot boot from patched_boot.img and then install Magisk (direct) which leaves a TWRP+Magisk boot.
[Xiaomi Mi A2 Lite Guides, News, & Discussion] Antho02:
yes they are both what i did, sorry for my bad english if it wasnt clear

btw today i had time for twrp so i did it again and all goes correctly now so i guess outdated edxposed was also my problem as you encountered
[Xiaomi Mi A2 Lite Guides, News, & Discussion] a1291762:
Nice. There's a new riru/EdXposed that works. Just install and it works :)
[Xiaomi Mi A2 Lite Guides, News, & Discussion] rezasirish99:
how to root and install twrp?

my phone is android 10.
[Xiaomi Mi A2 Lite Guides, News, & Discussion] gusbalaa:
Is possible to add numbering step on the first page?

I think some noob user (Like Me) need that simple thing to avoid missing step. ASAP

Thank you
[Xiaomi Mi A2 Lite Guides, News, & Discussion] Kaimilo:
flashed vanilla boot and i am in a bootloop

So i had to perform a factory reset as i was in a rush and i wont have a pc near until end of the day

For that reason i will try to show my steps to show if i did something bad, i had just installed a custom kernel

Mybe the error is because i didnt do anything related with the patched image? i am trying to understand
[Xiaomi Mi A2 Lite Guides, News, & Discussion] Aadil Gillani:
Sorry to bother you sir but I wanted to ask that what is the difference between these 2 procedure doing this all the steps that you have mentioned

and

flashing the tgz file using MI flash using save data then booting and installing deestroy twrp and then booting and installing magisk

I mean is there any step here that I do wrong or just it is a long process so people don't like to do this and prefer to do the complicated steps
[Xiaomi Mi A2 Lite Guides, News, & Discussion] a1291762:
When you do that... how do you get the patched boot.img for the new version?

If there is no tgz, what do you do then?

Installing a fastboot image does not seem easier to me, but if it works for you, don't let me stop you.

I wrote this guide mostly so I'd remember what to do each month. I don't want to wait for a tgz to be available, or rely on someone else to make a patched boot image. Probably there are other ways to do things but I'm a cli junkie so this is easy for me.
[Xiaomi Mi A2 Lite Guides, News, & Discussion] Aadil Gillani:
Tbh this time Tgz file was available several hours before OTA

After flashing tgz file I boot twrp img and install twrp zip via twrp then flash Magisk zip from twrp
[Xiaomi Mi A2 Lite Guides, News, & Discussion] a1291762:
Nice. That'll work fine. Except for those odd releases where there's no .tgz :)

I guess my steps require much less downloading. Only a few years ago, downloading >1Gb was a big deal for me. I'm still not used to it :)
[Xiaomi Mi A2 Lite Guides, News, & Discussion] Aadil Gillani:
For that case I am going to skip the update of that particular release or use your method

Also I think you are right as downloading a large file might be the main issue for other people by my procedure

Also sir could you run diff command to check what were the changes in this release
[Xiaomi Mi A2 Lite Guides, News, & Discussion] a1291762:
In the other thread :)
[Xiaomi Mi A2 Lite Guides, News, & Discussion] a1291762:
Interesting... when installing the November update today, I accidentally typed the wrong thing and fastboot gave me a rather odd error.

Writing 'system_v' FAILED (remote: 'partition table doesn't exist')

The partition table tells the phone which partitions exist. I would have expected an error like "partition doesn't exist" instead.

I'm sure I've seen other people getting this error from fastboot. I guess this error indicates the named partition doesn't exist, rather than "there is no partition table", which is a much more serious problem.
[Moto G5 Questions & Answers] girishjangir7:
I just want to know that when we will get treble rom for cedric coz i want to try q gsi

So jsut want to know if anyone working on it and when will we get???
[Lenovo ZUK Z2 (Plus) ROMs, Kernels, Recoveries, & ] PdyLZY:
bug:

There is a problem with the audio, you need to use the mask to install v4 sound solution

- Backup your personal data (Important)

- Download the Zip

- Boot to recovery (/vendor according to port)

- Restart recovery

- Wipe the System, Cache, Data and ART/Dalvik cache.

- Flash the ROM

- Flash Pie ARM64 Gapps

- Flash the root solution of your choice

- Reboot your device.

ROM OS Version: 9.0 Pie

ROM Kernel: 3.18.X

The kernel comes from:Nameless

Kernel source code：https://github.com/xzr467706992/android_kernel_zuk_msm8996

ROM Firmware Required: ZUI 2.5

Based On: AOSP

Since my region is China, the screenshot is Chinese.

Screenshot:
[Lenovo ZUK Z2 (Plus) ROMs, Kernels, Recoveries, & ] PdyLZY:
ROM:

https://mega.nz/#!4MVBWaLY!aXe_NB9l-neJ5UroFemBLMeCWT3PbXmFctbIsZNhVQc

vendor:

https://mega.nz/#!AANWVQyB!xJudIQsDU1pjg6isu6nBvmgYq6TC7ZkY2dEReXhFogg
[Lenovo ZUK Z2 (Plus) ROMs, Kernels, Recoveries, & ] PdyLZY:
Welcome to it