Database Users

Why no root yet ?

First off I am not criticizing the amazing XDA developers here, and all the people that help make root and ROM's happen.
This is aimed at Essential the company themselves
I was under the impression the Essential Phone was sort of like a Pixel, or Nexus, or OnePlus type of phone. Meaning running a near stock Android OS, an unlocked device, easily rooted. For example when a new OnePlus phone is released, root is out super fast. But the reason the Essential Phone has not been rooted yet is because of Essential holding back the factory images on us still. I guess I have to ask why would Essential do this ? I thought they touted this phone as a open platform, very similar in idea to the old Nexus line ?
The Essential Phone has been out 2 months now, and the important files for rooting still have not been officially released to the public yet ? What's up with Essential holding back so long ?

https://ibb.co/mgaVcb Mine ist rooted

Z-Fire821 said:
https://ibb.co/mgaVcb Mine ist rooted
Click to expand...
Click to collapse
Last I read was the boot image that was pulled didn't enable root with magisk and hadn't seen anything more from it. Did you have to do anything specifically?

Z-Fire821 said:
https://ibb.co/mgaVcb Mine ist rooted
Click to expand...
Click to collapse
Interedasting.
It'd be great if you could provide further proof/instructions.
Thanks a bunch.

There was a thread about someone working on LOS earlier this week but now I don't see it. Can't remember the user's name but he said that he had TWRP (no touchscreen though) working on the ROM, and posted some screenies of it booted and invited anyone who wanted to develop to his Discord. The same person was over on the /essential thread too on reddit too but now I don't see that thread either.
The Essential staff did an AMA over there yesterday too but noone asked about releasing the source code to my knowledge. I'm not sure what's going on. They'd sell more phones if people knew they are ROM friendly.
*Found the thread here:
https://forum.xda-developers.com/essential-phone/help/bootloader-root-t3695583

kchino said:
There was a thread about someone working on LOS earlier this week but now I don't see it. Can't remember the user's name but he said that he had TWRP (no touchscreen though) working on the ROM, and posted some screenies of it booted and invited anyone who wanted to develop to his Discord. The same person was over on the /essential thread too on reddit too but now I don't see that thread either. Maybe it was a Larp ¯\_(ツ)_/¯
The Essential staff did an AMA over there yesterday too but noone asked about releasing the source code to my knowledge. I'm not sure what's going on. They'd sell more phones if people knew they are ROM friendly.
Click to expand...
Click to collapse
Pretty sure the staff that did the AMA was just the design staff, not software staff. As soon as the files are released it will take about a day I bet for root. I remember seeing a thread on reddit that you are referring to as well. I think the people who can root it won't until the files are released. One **** up and they have a very expensive brick.

Thanks for the replies. So any idea as to when this source code image files will get released from Essential ? What's their holdup ?

Agreed, dicey proposition with no factory images.

We have devs working on it. Root has been achieved and there's a TWRP build but the touchscreen doesn't work you have to use a mouse to navigate. Also, there's no factory images yet to go back to stock in case of a problem. Once they iron out the issues I'm sure someone will release a guide.

Currently on the Nexus 6P, that's getting bad. I really want the Essential phone, but only if root comes out for sure, also ROM's would be great.
Otherwise I may just wait for the OnePlus 5T announcement, and if it's $500 go that route instead. At least the 5T will have good development

Z-Fire821 said:
https://ibb.co/mgaVcb Mine ist rooted
Click to expand...
Click to collapse
Man how did u root?? I really wanna root

I rooted with this Guide from the Discord Server from bmg1001: "In order to flash Magisk, you'll need the Magisk zip, TWRP, the stock boot image, and A USB OTG MOUSE (used to control TWRP for the moment). Boot into the stock recovery and perform a factory reset, then reboot into the bootloader. You need to flash TWRP via "fastboot flash boot twrp-mata.img". Once flashed, you need to boot into TWRP via the bootloader menu. When you boot into TWRP, move the Magisk zip and stock boot image into the phone's storage. Then, flash the boot image within TWRP, then flash Magisk."

Z-Fire821 said:
I rooted with this Guide from the Discord Server from bmg1001: "In order to flash Magisk, you'll need the Magisk zip, TWRP, the stock boot image, and A USB OTG MOUSE (used to control TWRP for the moment). Boot into the stock recovery and perform a factory reset, then reboot into the bootloader. You need to flash TWRP via "fastboot flash boot twrp-mata.img". Once flashed, you need to boot into TWRP via the bootloader menu. When you boot into TWRP, move the Magisk zip and stock boot image into the phone's storage. Then, flash the boot image within TWRP, then flash Magisk."
Click to expand...
Click to collapse
Can you provide the file for TWRP and boot img?

drocny87 said:
Can you provide the file for TWRP and boot img?
Click to expand...
Click to collapse
Just join the Discord Server and load it from there.

Z-Fire821 said:
I rooted with this Guide from the Discord Server from bmg1001: "In order to flash Magisk, you'll need the Magisk zip, TWRP, the stock boot image, and A USB OTG MOUSE (used to control TWRP for the moment). Boot into the stock recovery and perform a factory reset, then reboot into the bootloader. You need to flash TWRP via "fastboot flash boot twrp-mata.img". Once flashed, you need to boot into TWRP via the bootloader menu. When you boot into TWRP, move the Magisk zip and stock boot image into the phone's storage. Then, flash the boot image within TWRP, then flash Magisk."
Click to expand...
Click to collapse
Thanks
---------- Post added at 08:57 PM ---------- Previous post was at 08:53 PM ----------
Z-Fire821 said:
Just join the Discord Server and load it from there.
Click to expand...
Click to collapse
What's the link to it?

ROOT
Guys, if you truly, truly want to root your device, follow these steps. Just remember, I am not responsible if you end up bricking your device (and neither are the main developers currently working on TWRP and Lineage). YOU ARE RESPONSIBLE FOR WHAT YOU DO ON YOUR OWN DEVICE! (also this probably voids warranty btw)
THESE INSTRUCTIONS ARE FOR NMJ20D.
Now, one more thing. Remember, this TWRP build is very much in alpha stages and there are some major bugs with it, including no touch support and no crypto. Also, when I rooted, I had to use my USB OTG Mouse in order to maneuver around TWRP, but with this method, hopefully anyone can do it, without the mouse. The boot.img I will provide is the NMJ20D boot.img with the patches that Magisk puts in when you install it, so it's not exactly stock. Also, you might need to factory reset your device via the stock recovery (and make sure not to boot it back up until after you flash Magisk) just in case, since TWRP is buggy with crypto atm.
You can find a dump of NMJ20D here, in case you need to fix a bootloop (due to a bad Substratum theme, etc...) -- (you'll likely need only boot_a.img and system_a.img (within the system_a.zip).
If you wish to return to stock in order to accept OTAs, feel free to flash the unofficial factory images here and, should OTAs still fail, you may be required to wipe your data, which can be done via "fastboot -w". (Side Note: I believe the script included within the unofficial factory images also flashes the firmware to both partitions, so if your fingerprint sensor is seemingly absent or not working, this might actually fix it, as it has for some custom ROMs on the Essential.
Anyways, lets get started!
Make sure to download Magisk v14.3 and the alpha build of TWRP. Also, make sure to grab my boot.img with the Magisk stuff in it. And of course, your bootloader must be unlocked.
1. Reboot your Essential into fastboot mode. Once in fastboot mode, flash TWRP via
Code:
fastboot flash boot twrp-mata.img
2. Then, from within the fastboot menu, go to "recovery mode" and select it. After TWRP has booted up, type
Code:
adb shell twrp sideload
and then
Code:
adb sideload magisk.zip
3. Once Magisk finishes installing completely, reboot back to fastboot. Now that you're back in fastboot, flash the boot.img I provided via the good ol' command
Code:
fastboot flash boot boot_a.img
4. Now reboot! You should now have root and stuff via Magisk!

Appreciate the root guide, guess I can pick one of these up now to play around with. Awesome!!

[
Anyways, lets get started!
Make sure to download Magisk v14.3 and the alpha build of TWRP. Also, make sure to grab my boot.img with the Magisk stuff in it. And of course,
2. Then, from within the fastboot menu, go to "recovery mode" and select it. After TWRP has booted up, type and then
3. Once Magisk finishes installing completely, reboot back to fastboot. Now that you're back in fastboot, flash the boot.img I provided via the good ol' command
4. Now reboot! You should now have root and stuff via Magisk![/QUOTE]
I followed the whole guide, got to the side loading, and I couldn't get magisk to side load..

shooterlgk said:
[
Anyways, lets get started!
Make sure to download Magisk v14.3 and the alpha build of TWRP. Also, make sure to grab my boot.img with the Magisk stuff in it. And of course,
2. Then, from within the fastboot menu, go to "recovery mode" and select it. After TWRP has booted up, type and then
3. Once Magisk finishes installing completely, reboot back to fastboot. Now that you're back in fastboot, flash the boot.img I provided via the good ol' command
4. Now reboot! You should now have root and stuff via Magisk!
Click to expand...
Click to collapse
I followed the whole guide, got to the side loading, and I couldn't get magisk to side load..[/QUOTE]
What happens when you attempt to sideload Magisk? Does the adb sideload prompt on TWRP pop-up correctly after running "adb shell twrp sideload"?

bmg1001 said:
I followed the whole guide, got to the side loading, and I couldn't get magisk to side load..
Click to expand...
Click to collapse
What happens when you attempt to sideload Magisk? Does the adb sideload prompt on TWRP pop-up correctly after running "adb shell twrp sideload"?[/QUOTE]
I should of took a picture cuz I can't remember but it does give me an error tho ..I'm gonna retry when I get home from work but I literally sat there for almost 3 hours attempting to root to no success

Spent 6+ Hours Trying To Get Rooted Android 10

I tried rooting my OP6T on Android 10, and was up half the night. Recovered from a hard brick twice, using the Qualcomm serial flash tool thing. I was trying to flash Majisk, and read that it had to be done via a custom recovery like TWRP. All the guides said that it to boot TWRP, then basically flash TWRP using itself so that it says. Fastboot kept saying "Remote Unknown Command" when using "fastboot boot" like all the guides said. Then someone told me to run "fastboot flash boot twrp.img". This caused the first hard brick. I guess because I wrote the recovery over the boot partition. I then found a post somewhere where someone said that Oneplus Devs removed the boot command from Fastboot for some reason. No idea why!! But no one else in the OP6T TWRP thread reported issues. Maybe they were all installing TWRP on an Android 9.x build that diden't have this issue? Eventually after recovering and flashing several layers on OTA updates through the local upgrade option, I was back on A10 OB2. But I still wanted root and hadn't got TWRP working yet. Then I found a random post buried in a random thread somewhere saying that custom recoveries on A10 are useless at this point period because TWRP can't flash the system partition, as it's read only. Not sure if this only applies to OP devices?
I am now back to where I started. I would still like twrp for backups, but since it's not cooperating, I try the alternative option for Masisk, involving the patched boot.img file. I download the patched the patched boot file in this thread. Flashed it with "fastboot flash boot boot.img", and got my 2nd hard brick. It would get stuck at the bootloader warning screen and no fastboot.
Now i've lost my data, 6+ hour of time, and no closer than I was before.
I am going to take a break now, cause I need an operational phone this week. Word of advice: If you're not a developer that knows exactly what they are doing, don't even attempt to get root on an Android 10 build!

You can install Magisk,manager,extract the boot img from the OOS zip file using payload_dumper,copy that boot img. to your phone,patch the image with magisk,copy to your PC then fastboot the patched image to your phone .And yes,you cannot have twrp yet.

I'm on the open beta 2 of Android 10 and I have root and TWRP. It's possible.

It's not that hard, you don't even need twrp to install magisk. in android 10.
download open beta 2 Android 10. Extract payload.bin from it. Use payload_dumper to extract boot
install magisk apk, and patch boot.
go to fastboot use the
"Fastboot flash boot_a patched_boot.img "
and you are done.

Sh4d0wk1ng said:
It's not that hard, you don't even need twrp to install magisk. in android 10.
download open beta 2 Android 10. Extract payload.bin from it. Use payload_dumper to extract boot
install magisk apk, and patch boot.
go to fastboot use the
"Fastboot flash boot_a patched_boot.img "
and you are done.
Click to expand...
Click to collapse
I think I see what I did! I need to use "fastboot flash boot_a" (or b), and not just "fastboot flash boot". Not sure how you know whether to use a or b without a custom recovery though? Because AFAIK, the fastboot command for that is broken.
Not sure what payload dumper is, but I should be able to use the the same patched boot image that everyone else used since it's for that same ROM, now that I known exactly where to flash it to (besides A or B).
When I flashed to "boot" before, I must have overwritten some kind of low-level pre-bootloader, lol.
Thank you
Bhamilton0347 said:
I'm on the open beta 2 of Android 10 and I have root and TWRP. It's possible.
Click to expand...
Click to collapse
How did you achieve this? Do you have to start with A9 with TWRP, and then somehow upgrade to A10 without overwriting it with stock recovery?
I found this guide, but step 2 does not make sense to me. How could you flash TWRP inside of the Masisk Manager app?
I imagine you still can't flash system with TWRP, but everything else works?
Thank you
roman gabriel said:
You can install Magisk,manager,extract the boot img from the OOS zip file using payload_dumper,copy that boot img. to your phone,patch the image with magisk,copy to your PC then fastboot the patched image to your phone .And yes,you cannot have twrp yet.
Click to expand...
Click to collapse
I think the issue was that I flashed to the wrong place. See above. Thank you.

I'm feeling extremely lazy rn and I don't feel like explaining all of the trouble I went through to get it working, but you should be able to just fastboot flash these images to their respective partitions and you should have both TWRP and Magisk. It's got Magisk 20.1, the modified one so that EdXposed will work. But they're functionally the same.
https://drive.google.com/file/d/149TqVLqKr7Rc8xygMDoUyY_SLoATQrRq/view?usp=drivesdk
Let me know if it works.
Note: this is the boot.img for the second open beta of Android 10 for the OnePlus 6T. This may also work on the stable and first beta release as well as even on the 6, but I do not know. Also, your SIM card may not be showing up, but this problem disappeared for me a minute or two after boot.

Bhamilton0347 said:
I'm feeling extremely lazy rn and I don't feel like explaining all of the trouble I went through to get it working, but you should be able to just fastboot flash these images to their respective partitions and you should have both TWRP and Magisk. It's got Magisk 20.1, the modified one so that EdXposed will work. But they're functionally the same.
https://drive.google.com/file/d/149TqVLqKr7Rc8xygMDoUyY_SLoATQrRq/view?usp=drivesdk
Let me know if it works.
Note: this is the boot.img for the second open beta of Android 10 for the OnePlus 6T. This may also work on the stable and first beta release as well as even on the 6, but I do not know. Also, your SIM card may not be showing up, but this problem disappeared for me a minute or two after boot.
Click to expand...
Click to collapse
Thank you. I can't risk it right now. But i'll try sometime. Anyone wanna be the guinea pig?
If it works well, it should be very useful to the community.
I am brand new to Majisk by the way. It's been a couple years since I was rooted.

flyoffacliff said:
Thank you. I can't risk it right now. But i'll try sometime. Anyone wanna be the guinea pig?
If it works well, it should be very useful to the community.
I am brand new to Majisk by the way. It's been a couple years since I was rooted.
Click to expand...
Click to collapse
It's 100% safe and I can guarantee it'll boot as long as you're on an international OP6T on the Android 10 open beta 2. I reuploaded and included the stock boot.img as well so just in case you do have any problems, you can just fastboot flash it and you'll be able to boot right up (no hard brick or anything)

Bhamilton0347 said:
It's 100% safe and I can guarantee it'll boot as long as you're on an international OP6T on the Android 10 open beta 2. I reuploaded and included the stock boot.img as well so just in case you do have any problems, you can just fastboot flash it and you'll be able to boot right up (no hard brick or anything)
Click to expand...
Click to collapse
Great. Thank you. I might wait for the next stable build though. It just came out on H2OS, so shouldn't be too long now.

Man it just worked smooth for me. I was already on OB2 and I followed this below link. Half way down, I realised it was for OP6 and not 6T. However I had proper twrp and I just followed the procedure.
https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213
EDIT: I faced problems with wifi connectivity. So I had rebooted to TWRP and reflashed OB2, TWRP and Magisk again to get it working. An issue with
"fastboot flash boot" command I guess.

flyoffacliff said:
I think I see what I did! I need to use "fastboot flash boot_a" (or b), and not just "fastboot flash boot". Not sure how you know whether to use a or b without a custom recovery though? Because AFAIK, the fastboot command for that is broken.
Not sure what payload dumper is, but I should be able to use the the same patched boot image that everyone else used since it's for that same ROM, now that I known exactly where to flash it to (besides A or B).
When I flashed to "boot" before, I must have overwritten some kind of low-level pre-bootloader, lol.
Thank you
I wasn't sure either but I know that the boot on the oneplus 6t android 10 it has two partitions. I just flashed it on boot_a and it works. I could attempt to install twrp on the other partition but I don't really needed it. good luck and let us know how it went.
Click to expand...
Click to collapse

I had a bit more luck with the adventure this time! Successfully flashed TWRP and Magisk, but then Emojis were completely broken at the OS level. Apparently this is caused by a partition issue, but not sure how this happened. I tried a script to fix it that someone posted and it did not work. So I took this as an opportunity to flash the latest ROM to fix it.
I went into TWRP, ran the full update ZIP, then the TWRP installer, then the Magisk installer (all without rebooting). Apparently it does not switch slots automatically when you run it from recovery instead of the "local update" option? TWRP was fine after the update, but Masisk was not, despite me flashing the ZIP. No idea why! But I switched back to the other slot that was still rooted, used Magisk Manager to flash it to inactive slot, and switched slot back to one with new OS. Success! Funny how different methods work/fail with different people. Thanks for the help everyone. I just noticed 10.3.1 is no longer posted on the OnePlus website download page, hope it didn't get pulled again!
EDIT: Does each slot just have its own system and cache partition? Everything else is like data and modem is combined, right?

https://forum.xda-developers.com/oneplus-6t/how-to/root-oneplus-6t-loosing-data-android-10-t4041865
follow this guide.. work 100%. Tested.

Stuck in fastboot after flashing TWRP (Mi 9T)

First of all why did this happen, presumably I wasn't doing anything wrong or uninformed. I just unlocked the bootloader successfully, afterward as many threads claimed I flashed twrp-3.3.1-2-davinci-fix, and now it simply wont boot neither to system nor twrp. Why did this happen?
Does anyone know how to fix this? Thank you!
Mi 9T (M1903F10G)

Did you try to power off and then turn back on holding power and volume up? I had this issue yesterday but doing the vol up and power got me to twrp then did format and it booted up

cmlucht said:
Did you try to power off and then turn back on holding power and volume up? I had this issue yesterday but doing the vol up and power got me to TWRP then did format and it booted up
Click to expand...
Click to collapse
Thank you for your reply. You can't even power off, it will simply bootloop forever into fastboot. Nonetheless I managed to fix it by flashing fastboot ROM using MIFlash, but man, didn't expect root solutions to be this complicated, unstable, and outdated for our beloved Mi 9T. I simply want to achieve root in the stock rom, and wasted 7 hours yesterday and still got nowhere. I come from a classic LG G2, when things were much simple and straight forward back then. You can stop reading here, but now I had to:
Wait 1 week for bootloader unlock.
Flash TWRP, which soft bricked my phone right away. Why on earth, a recovery image provided in many reliable tutorials from multiple sources cause soft-brick in the second step is beyond my comprehension. I am still genuinely curious why did this happen, and why such a broken image is still circulating here?
Then I had to inform myself all about Anti Rollback, in order to prevent it happening, and concluded that MiFlash is safe, so I got MiFlash and a fastboot rom.
Apparently Mi Flash is terribly buggy and kept showing .net error exceptions because a "LOG" folder was missing in root folder, so let's waste one hour scratching our heads what the hell is happening because the developer missed a simple MkDir line during development.
After creating LOG folder, and installing drivers, couldn't flash any fastboot ROM because my 9T antiroll back number is 1 while fastboot rom ARB index was 0.
Then it appears that this error has actually nothing to do with ARB, but it is because I had to a) start MiFlash from C:\, b) remove name spaces in target address and c) shorten fastboot ROM folder name. So I had to get all these 3 variables right in order to resurrect my phone. MiFlash terrible programming didn't stop at step 4) but it extends into showing entirely confusing ARB errors that have nothing to with the real problem, rather petty programming bugs such as folder naming.
Finally managed to boot up 9T, and we're back at square one.
Afterward successfully flashed mauronofrio TWRP including vbmeta and got recovery working.
I decided to try out few custom ROMs since all my data were erased anyway, but it appears my system was encrypted and TWRP showed encrypted alphanumeric characters, so I had to format data in order to flash files.
Now every-time I flash stock ROM .zip I lose TWRP, and every-time I reflash mauronofrio TWRP I end up in recovery bootloop, and so I can't manage to have both at same time in order to move with the Magisk flash.
10 steps and 7 hours later and still got nowhere, just risked bricking my phone.
Now we have to deal with
a) bootloader wait,
b) twrp encryption mess,
c) anti roll back risk,
d) buggy MiFlash
e) safety net measures
f) no custom ROMs that are pre-rooted and simple
g) dependency of stock ROM files - meaning you can't wipe everything including system and just flash custom ROM .zips, like I used to do with 5 android phones before this one. Now you are somehow dependent on original ROM files which probably means you will have to base install stock MI before you flash anything Xiaomi.EU, Evolution X, PixelExperience etc.​ When did things get so complicated? It seems every year new limitations are introduced and the sheer combination to get them all right give headaches.
Anyway, all I want is to install latest stock ROM from TWRP and keep TWRP so I can also flash Magisk. In other words, how to simply have a rooted stock?

Your mistake is to not use Official TWRP instead of an old TWRP version...

Micdu70 said:
Your mistake is to not use Official TWRP instead of an old TWRP version...
Click to expand...
Click to collapse
Thanks for your reply! Yes, that must have been it. Those outdated tutorials should be removed.
Now I flashed miui_DAVINCIEEAGlobal_V11.0.4.0.QFJEUXM through latest TWRP, but it removed TWRP. When I reflash latest TWRP then it ends up in bootloop.
EDIT: Ended up reflashing all over again using MiFlash. Now the only problem remaining is which version of Magisk is compatible with miui_DAVINCIEEAGlobal_V11.0.4.0.QFJEUXM?

What are you flashing with? I am now using xiaomitools v2 and it installed twrp and magisk with no problems.
I flashed the EU custom stable, I was global but I wanted to compare the 2 and I like the EU better.
I came from a non rootable lg g7.
I have not flashed custom ROMs since my old Galaxy note days.

cmlucht said:
What are you flashing with? I am now using xiaomitools v2 and it installed twrp and magisk with no problems.
I flashed the EU custom stable, I was global but I wanted to compare the 2 and I like the EU better.
I came from a non rootable lg g7.
I have not flashed custom ROMs since my old Galaxy note days.
Click to expand...
Click to collapse
Never heard of XiaomiTools v2, it seems like a great alternative. I used buggy MiFlash to flash fastboot ROM, flashed TWRP, then got a bootloop, formatted data from TWRP and flashed Magisk. It seems everything is working fine now, but in the future I'll make sure to check XiaomiTools v2.
I never used stock ROMs in any of my past phones, first thing I did when I bought a new phone is unlock bootloader and install Lineage or Cyanogenmod back in the days. But somehow I like MIUI so all I needed was root.
It is hard to believe that there are actually phones that have no root at all.

blackmatrix64 said:
Thank you for your reply. You can't even power off, it will simply bootloop forever into fastboot. Nonetheless I managed to fix it by flashing fastboot ROM using MIFlash, but man, didn't expect root solutions to be this complicated, unstable, and outdated for our beloved Mi 9T. I simply want to achieve root in the stock rom, and wasted 7 hours yesterday and still got nowhere. I come from a classic LG G2, when things were much simple and straight forward back then. You can stop reading here, but now I had to:
Wait 1 week for bootloader unlock.
Flash TWRP, which soft bricked my phone right away. Why on earth, a recovery image provided in many reliable tutorials from multiple sources cause soft-brick in the second step is beyond my comprehension. I am still genuinely curious why did this happen, and why such a broken image is still circulating here?
Then I had to inform myself all about Anti Rollback, in order to prevent it happening, and concluded that MiFlash is safe, so I got MiFlash and a fastboot rom.
Apparently Mi Flash is terribly buggy and kept showing .net error exceptions because a "LOG" folder was missing in root folder, so let's waste one hour scratching our heads what the hell is happening because the developer missed a simple MkDir line during development.
After creating LOG folder, and installing drivers, couldn't flash any fastboot ROM because my 9T antiroll back number is 1 while fastboot rom ARB index was 0.
Then it appears that this error has actually nothing to do with ARB, but it is because I had to a) start MiFlash from C:\, b) remove name spaces in target address and c) shorten fastboot ROM folder name. So I had to get all these 3 variables right in order to resurrect my phone. MiFlash terrible programming didn't stop at step 4) but it extends into showing entirely confusing ARB errors that have nothing to with the real problem, rather petty programming bugs such as folder naming.
Finally managed to boot up 9T, and we're back at square one.
Afterward successfully flashed mauronofrio TWRP including vbmeta and got recovery working.
I decided to try out few custom ROMs since all my data were erased anyway, but it appears my system was encrypted and TWRP showed encrypted alphanumeric characters, so I had to format data in order to flash files.
Now every-time I flash stock ROM .zip I lose TWRP, and every-time I reflash mauronofrio TWRP I end up in recovery bootloop, and so I can't manage to have both at same time in order to move with the Magisk flash.
10 steps and 7 hours later and still got nowhere, just risked bricking my phone.
Now we have to deal with
a) bootloader wait,
b) twrp encryption mess,
c) anti roll back risk,
d) buggy MiFlash
e) safety net measures
f) no custom ROMs that are pre-rooted and simple
g) dependency of stock ROM files - meaning you can't wipe everything including system and just flash custom ROM .zips, like I used to do with 5 android phones before this one. Now you are somehow dependent on original ROM files which probably means you will have to base install stock MI before you flash anything Xiaomi.EU, Evolution X, PixelExperience etc.​ When did things get so complicated? It seems every year new limitations are introduced and the sheer combination to get them all right give headaches.
Anyway, all I want is to install latest stock ROM from TWRP and keep TWRP so I can also flash Magisk. In other words, how to simply have a rooted stock?
Click to expand...
Click to collapse
Hey, I'm facing the same issue you faced here. Waited 7 days to unlock bootloader, after unlocking it, flashed a twrp i found on one of the youtube tutorials. Immediate bootloop. Im fairly new to all of this, and dont understand what certain words even mean tbh. Do you mind guiding me in fixing my phone? Any help would be really appreciated. Thank you.

blackmatrix64 said:
Never heard of XiaomiTools v2, it seems like a great alternative. I used buggy MiFlash to flash fastboot ROM, flashed TWRP, then got a bootloop, formatted data from TWRP and flashed Magisk. It seems everything is working fine now, but in the future I'll make sure to check XiaomiTools v2.
I never used stock ROMs in any of my past phones, first thing I did when I bought a new phone is unlock bootloader and install Lineage or Cyanogenmod back in the days. But somehow I like MIUI so all I needed was root.
It is hard to believe that there are actually phones that have no root at all.
Click to expand...
Click to collapse
i miss the Cyanogenmod days

I keep loosing root after reboot, Pls help.

Hey guys,
first time posting here so i dont kow how to style the text, so sorry about that.
last time i rooted a phone was on my sony xperia sp , where all i had to do was to go to towelroot .com and click to root.
I tryed to root my OP6T yesterday, after some setbacks i managed to sucessfully do it.
I did it like this:
1. Downloaded full ROM of OOS 10.3.2,
2. copied the payload to a program called payload dumper that extracted the boot image.
3. Copied the boot image to the phone
4. opened Magisk manager and selected install from source where i chose the boot.img
5. it created a copy called magisk_patched.img
6. booted in fastboot
7. on my pc used the command prompt to "fastboot boot magisk_patched.img"
booted normally and i had root.
but then problem appeared
#Problem 1
everytime i rebooted my phone i would loose root and it would say Magisk not installed. To get it back i would need to perform step 7 again and it was not ideal to do that everytime i turned off my phone.
#Problem 2
While tryng to solve problem 1 i read that i needed to open magisk manager and "Install to Inactive Slot (After OTA)."
After doing that it rebooted but now it wont boot at all, even if i try to "fastboot boot magisk_patched.img" the cmd gives me error:
fastboot boot magisk_patched.img
downloading 'boot.img'...
OKAY [ 0.838s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.845s
now my phone is just sitting there i dont want to reset it again. it would be the 4th time that i need to set up my phone in 2 days, so im trying to see if there are alternatives.
If reset is really the only way, i read that with root you can make a full backup of your phone and then restore it. How to do that? can i do it in the situation im in?
How can i root my OP6T running OOS10.3.2, and keep it? Whats the right method bc the one i followed seemed flawed.
I also tried one that had TWRP but maybe i did something wrong bc it didnt work., also there is no official one working for 10.3.2.

What is happening is normal with those instructions (they aren't right).
All you need to do is install TWRP. Do not use the official one, it is out of date. Use TWRP from this thread Link here. The TWRP from that thread is from the official maintainer. It works fine with OOS 10.
- You need to get the phone in fully working order again. Which may mean you need to use the fastboot ROM, as you've probably "goofed" something up at this point. (no offense meant). Make sure your phone boots and such after this.
- For OOS 10 with the phone in fastboot, fastboot boot recoveryimgfilename.img (<-- For OOS 10 you will need TWRP 3.3.1-32 Q Unofficial by mauronofrio from the thread I linked to above) This will boot to TWRP.
- Now run TWRP 3.3.1-32 Unofficial Installer by mauronofrio this will install TWRP. The installer is the same for Android 9 and 10, doesn't matter.
- Once the installer runs, click back, choose reboot to recovery. If you boot to the system, you have to start over. Reboot to recovery!
- Install Magisk 20.3 <-- The current version. The official download page. After that you can reboot to the system. You should now have a rooted, phone with Magisk, and TWRP installed.
Any questions ask.

OhioYJ said:
What is happening is normal with those instructions (they aren't right).
All you need to do is install TWRP. Do not use the official one, it is out of date. Use TWRP from this thread Link here. The TWRP from that thread is from the official maintainer. It works fine with OOS 10.
- You need to get the phone in fully working order again. Which may mean you need to use the fastboot ROM, as you've probably "goofed" something up at this point. (no offense meant). Make sure your phone boots and such after this.
- For OOS 10 with the phone in fastboot, fastboot boot recoveryimgfilename.img (<-- For OOS 10 you will need TWRP 3.3.1-32 Q Unofficial by mauronofrio from the thread I linked to above) This will boot to TWRP.
- Now run TWRP 3.3.1-32 Unofficial Installer by mauronofrio this will install TWRP. The installer is the same for Android 9 and 10, doesn't matter.
- Once the installer runs, click back, choose reboot to recovery. If you boot to the system, you have to start over. Reboot to recovery!
- Install Magisk 20.3 <-- The current version. The official download page. After that you can reboot to the system. You should now have a rooted, phone with Magisk, and TWRP installed.
Any questions ask.
Click to expand...
Click to collapse
So getting it straight, i need to first reset my phone and then do the steps you described.
Can i backup the data first with TWRP to restore it later and avoid setting up everything again?

Davide1713 said:
So getting it straight, i need to first reset my phone and then do the steps you described.
Can i backup the data first with TWRP to restore it later and avoid setting up everything again?
Click to expand...
Click to collapse
Supposedly. I've never used that function of TWRP. Some people have luck with, some people restore things that shouldn't be restored and end up having to wipe the phone again. Personally I just use TitaniumBackup like I always have. I would search for information on that in the TWRP thread if you want to try method. I don't know enough on that to provide solid information.

OhioYJ said:
Supposedly. I've never used that function of TWRP. Some people have luck with, some people restore things that shouldn't be restored and end up having to wipe the phone again. Personally I just use TitaniumBackup like I always have. I would search for information on that in the TWRP thread if you want to try method. I don't know enough on that to provide solid information.
Click to expand...
Click to collapse
Hey man,
Thank you so much. It worked and i stay rooted even after reboot.
May i ask how you use the Titanium Backup, i think back in the days all i used it for was uninstalling system apps. Or if you know some nice guides. If you know other good things to checkout now that i have root i would appreciate it, i have been far away from rooting for too long.
Once again thank you so much

Davide1713 said:
Hey man,
Thank you so much. It worked and i stay rooted even after reboot.
May i ask how you use the Titanium Backup, i think back in the days all i used it for was uninstalling system apps. Or if you know some nice guides. If you know other good things to checkout now that i have root i would appreciate it, i have been far away from rooting for too long.
Click to expand...
Click to collapse
I use it to back up app and app data primarily. It allows me to restore data to apps after a clean install. Since I have the Pro version it's just a batch action (one click essentially). There is also a way to create a flashable .zip you can use in TWRP, although I haven't tried that method, as I'm typically not restoring apps, just data. I also use it remove apps from time to time.

OhioYJ said:
I use it to back up app and app data primarily. It allows me to restore data to apps after a clean install. Since I have the Pro version it's just a batch action (one click essentially). There is also a way to create a flashable .zip you can use in TWRP, although I haven't tried that method, as I'm typically not restoring apps, just data. I also use it remove apps from time to time.
Click to expand...
Click to collapse
Hey man, im sorry i am once again in need.
Idk why but at first i can reboot the system normally without issues. but after a while once i set up everything it just doesnt boot anymore. Am i missing something? do i have to do anything with magisk? download a module or something?
Could it be that google security update is the fault?

Davide1713 said:
Hey man, im sorry i am once again in need.
Idk why but at first i can reboot the system normally without issues. but after a while once i set up everything it just doesnt boot anymore. Am i missing something? do i have to do anything with magisk? download a module or something?
Could it be that google security update is the fault?
Click to expand...
Click to collapse
When you installed everything originally did you fix everything with a clean install? Both slots are the same version of Android? (Like you don't have something weird going on like Android 9 on one and Android 10 on another?)
You definitely have something abnormal going on. There shouldn't be anything in Magisk that you have to do, at least not to prevent crashing. I normally hide it, but that has to do with keeping apps from detecting root.

OhioYJ said:
When you installed everything originally did you fix everything with a clean install? Both slots are the same version of Android? (Like you don't have something weird going on like Android 9 on one and Android 10 on another?)
You definitely have something abnormal going on. There shouldn't be anything in Magisk that you have to do, at least not to prevent crashing. I normally hide it, but that has to do with keeping apps from detecting root.
Click to expand...
Click to collapse
I got it to boot by uninstalling magisk,
I am 100% sure i dont have two different version of android in different slots, bc yesterday i was in big trouble and nothing was working and i flashed on both slots the same version of android 10(dont remember exactly wich one as i tried a couple, but they were the same).
Today when i couldnt boot anymore i went into stock recovery, factory reset -> when it booted i placed the stockOS.zip file in the phone and applied update from local file -> after that i factory reset again from the system settings, so i think the phone should have installed it properly.
Only after that i did what you told me and installed TWRP and Magisk. and as i said it worked and i could restart my device etc..
After a while when i restarted i couldnt boot anymore and went to bootloader. Removing Magisk fixed it,apperantly on install magisk creates a copy of the boot.img that it restores on uninstall, and i booted to system.
Now i can use my phone but dont have root.
Im very thankful for you being there and helping me out trough this, i cant thank you enough

GuestD2272 said:
I got it to boot by uninstalling magisk,
I am 100% sure i dont have two different version of android in different slots, bc yesterday i was in big trouble and nothing was working and i flashed on both slots the same version of android 10(dont remember exactly wich one as i tried a couple, but they were the same).
Today when i couldnt boot anymore i went into stock recovery, factory reset -> when it booted i placed the stockOS.zip file in the phone and applied update from local file -> after that i factory reset again from the system settings, so i think the phone should have installed it properly.
Only after that i did what you told me and installed TWRP and Magisk. and as i said it worked and i could restart my device etc..
After a while when i restarted i couldnt boot anymore and went to bootloader. Removing Magisk fixed it,apperantly on install magisk creates a copy of the boot.img that it restores on uninstall, and i booted to system.
Now i can use my phone but dont have root.
Im very thankful for you being there and helping me out trough this, i cant thank you enough
Click to expand...
Click to collapse
Not sure if you're still having this issue but I'll post the solution just in case anyone gets stumped, does a google search, and comes across this post. You were using the wrong command.
"fastboot boot" just lets you boot with the img so you can verify that root works.
"fastboot FLASH boot" will flash it and root will stick after reboot.
No need to jump through hoops with TWRP and such.

Redmi 7A - Upgrade to Magisk v22 -- issues

Was running older version of Magisk+Manager all 100% fine, trying to update to the new Magisk v22 apk.
reading guide here: https://topjohnwu.github.io/Magisk/install.html
it seems the device does NOT have a randisk (says NO), which means, one takes the *recovery* path (in the steps)
I have the TWRP recovery image used, and patched it using the Magisk that was on the phone, selected 'recovery method', selected the file, and it wrote:
/sdcard/Download/magisk_patched_f7KJH.img
Click to expand...
Click to collapse
so, pulled the file to PC:
adb pull /sdcard/Download/magisk_patched_f7KJH.img
Click to expand...
Click to collapse
then rebooted into FASTBOOT mode, and flashed that recovery image using:
fastboot flash recovery magisk_patched_f7KJH.img
Sending 'recovery' (65536 KB) OKAY [ 2.079s]
Writing 'recovery' OKAY [ 5.316s]
Finished. Total time: 7.408s
Click to expand...
Click to collapse
However, phone boots showing magisk is not installed, well, there is an icon Magisk, but it says v22 needs to be installed, but using that install button does not work, it appears to succeed, but doesn't do anything
Read on that page above , that one can RENAME the magisk v22 .apk to .zip, and FLASH the ZIP file from TWRP!!!
So, did that , renamed Magisk-22.0(22000).apk to .zip, when when booted into TWRP to flash this zip it says:
Checking for Digest file...
Zip file is corrupt!
Error installing zip file '/external_sd/Download/Magisk-22.0(22000).zip
Click to expand...
Click to collapse
So, it's a bit confusing.. Does anyone have steps for Redmi 7a? which does not appear to have ramdisk...
I thought it would imply be to patch the TWRP image file to using Magisk, then flashing the recovery image on to the recovery partition..
Corrections welcomed.
Stormy.
EDIT: ROM MIUI Global 10.2.5 | Stable 10.2.5.0 (PCMMIXM)

The error flashing comes from:
Installation
The Magic Mask for Android
topjohnwu.github.io
Download the Magisk APK
Rename the .apk file extension to .zip, for example: Magisk-v22.0.apk → Magisk-v22.0.zip. If you have trouble renaming the file extension (like on Windows), use a file manager on Android or the one included in TWRP to rename the file.
Flash the zip just like any other ordinary flashable zip.
Click to expand...
Click to collapse
Rename was easy, but flashing the zip from TWRP claimed it is corrupted. also read the "Magisk in recovery", however, trying this gets me to recovery mode (TWRP):
(Recovery Key Combo) → (Splash screen) → (Release all buttons) → (System with Magisk)
Click to expand...
Click to collapse
A bit confusing on how the new magisk works, the over-use of the term 'magisk' causes it to be incredibly hard to understand what is new/old/what/where/how things are laied out. Anythanks, thanks for any tips.
Stormy.

stormy1777 said:
Was running older version of Magisk+Manager all 100% fine, trying to update to the new Magisk v22 apk.
reading guide here: https://topjohnwu.github.io/Magisk/install.html
it seems the device does NOT have a randisk (says NO), which means, one takes the *recovery* path (in the steps)
I have the TWRP recovery image used, and patched it using the Magisk that was on the phone, selected 'recovery method', selected the file, and it wrote:
so, pulled the file to PC:
then rebooted into FASTBOOT mode, and flashed that recovery image using:
However, phone boots showing magisk is not installed, well, there is an icon Magisk, but it says v22 needs to be installed, but using that install button does not work, it appears to succeed, but doesn't do anything
Read on that page above , that one can RENAME the magisk v22 .apk to .zip, and FLASH the ZIP file from TWRP!!!
So, did that , renamed Magisk-22.0(22000).apk to .zip, when when booted into TWRP to flash this zip it says:
So, it's a bit confusing.. Does anyone have steps for Redmi 7a? which does not appear to have ramdisk...
I thought it would imply be to patch the TWRP image file to using Magisk, then flashing the recovery image on to the recovery partition..
Corrections welcomed.
Stormy.
EDIT: ROM MIUI Global 10.2.5 | Stable 10.2.5.0 (PCMMIXM)
Click to expand...
Click to collapse
You need to patch the file: boot.img

VD171 said:
You need to patch the file: boot.img
Click to expand...
Click to collapse
Why do you write that? Reading here:
Installation
The Magic Mask for Android
topjohnwu.github.io
says:
Patching Images​If your device has boot ramdisk, you need a copy of the boot.img
If your device does NOT have boot ramdisk, you need a copy of the recovery.img
Click to expand...
Click to collapse
The Redmi 7A says RAMDISK *NO* on the Magisk app, which reads to me as I have to patch the recovery.img, in my case recovery is TWRP, so that is the image I gave it.
Has anyone managed to get Magisk v22 on Redmi 7a? any steps? if not, may have to revert back to the prior set up which worked, until this is sorted out.
Thanks for any specific tips to devices withOUT ramdisk=yes, like Redmi 7A.
Stormy.

Yes, I read.
You can't patch TWRP using magisk.
If you want to apply magisk patched to the recovery, then patch the boot.img and then flash it to recovery.
You can ignore the info about ramdisk, just patch the stock boot.img and then flash it to the boot partition.
Good luck

Thanks, quick update from a "naive-end user" Before your second reply, re-read and noticed using the TWRP recovery image, and not the STOCK/ROM, so, pulled stock recovery.img, patched it, flashed to recovery partition.. all OK..
Now, on normal boot, no Magisk or root; on boot through recovery it goes into stock recovery, even leaving the up-vol key immediately when logo disappears does not do it, it simply boots normally without root/magisk installed
This is how easy one can take a perfectly working env to no root, no TWRP
Now, taking your advise and patch using magisk 22 the stock boot.img, here goes:
cksum:
Code:
4261103684 33554432 boot-stock1025.img
(after patching w/Magisk v22):
Code:
245310758 33554432 magisk_patched_U6lEU.img
flash in fastboot:
Code:
c:> fastboot flash boot magisk_patched_U6lEU.img
target reported max download size of 535822336 bytes
sending 'boot' (32768 KB)...
OKAY [ 1.034s]
writing 'boot'...
OKAY [ 0.886s]
finished. total time: 1.924s
it boots OK, but, magisk v22 says "no magisk installed"
I now recall that no matter which version of Magisk, the self-patching , i.e. on the actual device, NEVER WORKED, I've reported that many times in the past on this forum, but no clear answer. The only way I could root in the first place was to download an already patched boot.img that I use till yesterday.. that was posted on the forum here.
So, does anyone have a dump of boot.img patched to magisk v22 for Redmi 7A?
Or, alternatively, knows why patching of boot.img using v22 does not work?
Thanks.
Stormy.

Searching online, seems others w/Xiamoi devices having similar issues/confusions, this thread claims to RESOLVE:
Invalid - Magisk v22.0 issue [RESOLVED]
hi every one could anyone explain how we could update the latest magisk 22 because the magisk manager is no longer available....i turned the apk to zip file and it didnt want to be installed at all it gives you an error message THE DEVICE IS NOT BOOTING TO SYSTEM IT DIRECTS TO FASTBOOT....any...
xiaomi.eu
but does not say exactly HOW.. I've patched the Magisk uninstaller
https://github.com/topjohnwu/Magisk/releases/download/v21.4/Magisk-uninstaller-20210117.zip
so, no magisk at all, but when renaming magisk 22.img to magisk22.zip and trying to flash in TWRP, it says zip file is corrupted in red and flashing stops.

One more tip found these errors in the magisk patching log!!
Code:
Output file is written to
/storage/emulated/0/Download/magisk_patched_35S0f.img
****************************
cp: can't preserve ownership of 'busybox': Operation not permitted
cp: can't preserve ownership of 'magisk32': Operation not permitted
cp: can't preserve ownership of 'magisk64': Operation not permitted
cp: can't preserve ownership of 'magiskboot': Operation not permitted
cp: can't preserve ownership of 'magiskinit': Operation not permitted
- All done!
don't know how to resolve, found on:
Bootloop on Xiaomi Redmi 9 · Issue #3985 · topjohnwu/Magisk
Hi there, I'm trying to root my Redmi 9, alas it doesn't seem to be working. MIUI version: 12.0.1.0 (QJCEUXM) Android Version 10 QP1A.190711.020 I have unlocked the bootloader (open padlock icon on...
github.com
mention to flash *vbmeta*, so did that as well as patched v22 boot.img, and still it no root, magisk says it is not installed.

After full day downtime, and 50+ attempts most before posting, decided to revert back to Magisk v21.4/manager 8.0.7, installed riru/riru-edxposed within 5 minutes, phone is rooted all is fine. will re-try once someone announces success on Redmi 7A or someone provides a working pre-patched boot.img debug is also possible, more time for that path in 2 weeks.
Thanks Stormy.

@stormy1777
For the Redmi 7A you must have a patched boot.img to install Magisk with TWRP.
The problem is, the boot.img is a 32 bit img with a fake Ramdisk for a 64 bit processor.
Please look here: Install Magisk 22

MOFI69 said:
@stormy1777
For the Redmi 7A you must have a patched boot.img to install Magisk with TWRP.
The problem is, the boot.img is a 32 bit img with a fake Ramdisk for a 64 bit processor.
Please look here: Install Magisk 22
Click to expand...
Click to collapse
Incredible! If i read this right, you seem to say that Magisk can NOT patch the boot.img on the Redmi 7A due to the 32/64 bit issue relating to ramdisk?
I felt that all along, just couldn't prove it, used a pre-existing patched boot.img from day1, and never managed to patch directly on the phone Was that reported to Magisk team? or they can't fix it from a technical perspective?
will find the time (in few days) to play with this patching, if it works will post patched MIUI Global 10.2.5 | Stable 10.2.5.0 (PCMMIXM) image
Thanks.

Completely correct, Xiaomi installed a 32-bit operating system because the smartphone only has 2 GB of RAM. Not enough to work properly with a 64 bit operating system. Topjohnwu published the information on its Github page and criticized Xiaomi very much for this behavior. The original boot.img contains a ramdisk, but only as a placeholder, so when repackaging it is added with 0 MB to the boot.img. Therefore the image is smaller (approx. 15 MB) than the original.
Why don't you update to 12.xx.xx right away?

MOFI69 said:
Completely correct, Xiaomi installed a 32-bit operating system because the smartphone only has 2 GB of RAM. Not enough to work properly with a 64 bit operating system. Topjohnwu published the information on its Github page and criticized Xiaomi very much for this behavior. The original boot.img contains a ramdisk, but only as a placeholder, so when repackaging it is added with 0 MB to the boot.img. Therefore the image is smaller (approx. 15 MB) than the original.
Why don't you update to 12.xx.xx right away?
Click to expand...
Click to collapse
Dear Mofi69 in a small town by Berlin
Thank you SOOO much for such nice explanations, goes a long way to "trickle" down information to lowly people
Not moving to ROM 12, due to lack of time to "play with this", have several phones, and it would mean more time spent on it, for no "visible" significant benefit. I don't work for CIA or have anything secret, phone is not used in public places, mostly home, and wifi, so, security is not really an issue as they make it.. switching ROM sounds too many moving-parts and there are TONS of old apps that are already working, many not from app store we live with it fine. on a new phone, we'll upgrade, I'm certain ...
in next few days will try the magisk patching again (I was selecting "recovery" due to the ramdisk=no confusion), MAYBE they fixed it, and will produce a valid image, I can't think that the magisk binary would not have full control of their output, so as to make it exactly the right size/layout.. if it fails, will try the python patcher. Thanks so much for this info!!
Stormy.

stormy1777 said:
Dear Mofi69 in a small town by Berlin
Click to expand...
Click to collapse
Oh, oh, what kind of garbage did I write there, it comes from when you are not careful in English class ...
Only for you...
there is now the "OLD" boot.img, ready pached with the oss-patcher. Please install Magisk via TWRP (magisk.zip), boot.img from
miui_PINEGlobal_V10.2.5.0.PCMMIXM_7380681456_9.0
Important: I cannot test it! Please let me know if it works.
Best regards
Michael

Thanks friend for the help!!! Spent few more hours, eventually managed to get it, but not sure HOW
Starting point, Magisk 21.4/Manager 8.0.4 (not hidden), rooted, boot into TWRP, and flash:
1) patched boot.img from you
2) flash Magiskv22.zip confirmed md5sum:
Code:
e14132835b4cc0878639fcf645db479c Magisk-v22.0.zip
noticed that this flashing of zip appears to overwrite the boot.img, ignored it for the time being.
booted OK, said Magisk 22 is installed on the TOP part of the app, BUT, on the bottom, it showed Latest v22, and installed 8.0.4, and said, your device needs more updates, it will now download v22 and install, click ok,
rebooting in 5 seconds, and it comes back to the same spot, again, your machine needs more updates , click OK, again, download, rebooting in 5 seconds, and no change. Clicking CANCEL allows pressing the UPDATE button.. that doesn't help either.
Went to TWRP again, flashed your boot-patched.img , it then appear to not have any Magisk installed at all
so, installed v22 APK from the running phone, it then showed app/manager v22, but no magisk installed, so recalling that flashing the ZIP made it appear that magisk v22 IS installed, so flashed the ZIP in TWRP and it booted ok, and appears to have v22 installed on both parts of the app.
I'm thinking the steps should be:
1) Install Magisk v22 APK from phone
2) reboot into TWRP and flash the patched boot.img
3) if does not work, flash magisk v22 from twrp..
Sorry for "reinventing" what is known to all just couldn't find a "guide" with correct order for Redmi 7a...
Stormy.
PS: @MOFI69 , after an hour or so, got a pop up with long hex value and it said to send 1 BTC there to continue using the phone, I did that, then same message appeared on Android TV, did that, now on the Android Dog Collar do you think it has anything to do w/that boot.img u patched
Just kidding friend, have fun!!

Since the phone was already rooted (with a manipulated boot.img unknown to me) it can lead to strange malfunctions.
The best and easiest way is to uninstall Magsik (from the manager); REBOOT TO TWRP; INSTALL THE ORIGINAL boot.img and immediately afterwards my leased and immediately magisk V22, no reboot in between.
Then reboot into the system and install the magisk V22.apk, sometimes it is already there as a "shadow", then just start, it installs itself.

ok, may try that, only thing is that uninstalling magisk mgr, will lose all the "settings", like which app is granted root, and modules installed?
the way i did seems to work (i don't know exactly the steps yet), but it kept all settings/permissions, of all rooted apps...
Strange is that flashing magisk v22 appear to patch the boot.img, so question is why your boot.img is needed if it gets flashed later... not doubting it is, just asking.. ok, will try another phone and see...
S

Yes, the settings of Magisk have to be recreated again, as with a first-time installation. All possibly installed modules must be removed beforehand!
The boot.img is always pached by magisk, which is not possible without a boot.img edited with oss-patcher. The 32 bit ramdisk is missing (the operating system is recognized as this by magisk), so it cannot be installed. The patch only adds an interface so that magisk can install "redirection" for root access.
I think the boot.img you have used so far already contains a permanently installed magisk version, is often done this way on other chinese telephones, it works, but an update of magisk is mostly not possible, hence your problems.
In "my" boot.img there is no magisk preinstalled and updates are possible at any time. Unfortunately, I can't tell you whether your type of installation will work in the long term, you'll notice that with the next update ;-)

Thanks for the GREAT explanation!! yes, current boot.img I could not apply magisk updates smoothly, had to always flash from recovery, and that worked fine.
Manage to update without having to reinstall all modules, all remained, vanced, etc. so far leaving it.. I used to have 5 days to play with such things, now, 5 hours is hard to get, naively I expected it to be 5-min
Also managed to root a totally brand new phone using your boot.img + magisk v22, here one must add vbmeta.img as well as Permissiver_v4.zip, not entirely clear on right order, eventually it worked
Thanks much to @MOFI69
Stormy.

Super that makes me happy!
Then have fun with your Redmi
Best wishes