Database Info

Help downgrading to 4.4.4 no sound

I have searched through several threads and attempted a few commands through fastboot with no success.
Since OTA update on my xt1032 to 5.1, I heard cracking sound in earpiece and now I do not hear anything when placing a phone call through earpiece although it seems to work fine on speaker phone or when headset is attached. Rebooting changes nothing. I am trying to downgrade as I've read that may help or even try CM12 to see if that does anything. (factory reset did nothing)
However, I found out through the Motorola website that I cannot unlock my boot loader (version 41.1A), so I don't know if I can install TWRP in any fashion or unlock my bootloader by some other means?
I tried ChainFire AUto-Root but it was unable to boot back into Red Android (1st 2 steps appeared successful in the fastboot dialog)
Can anyone help me or point me in the proper direction?

The issue is not Android 5.1 - but your current Android installation, or possibly a hardware fault.
Flash the latest Factory Firmware Image for your model.
Factory Firmware Images: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
Provide logs (copy and paste commands prompt screen) of what happens.

Provide logs (copy and paste commands prompt screen) of what happens.
Click to expand...
Click to collapse
ok initially, I got the "missing adbwinapi.dll" error message: copied adbwinapi.dll and adbwinusbapi.dll into the firmware folder (also copied the firmware into the minimal adb and fastboot folder, same result)
T:\xt1032>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
error: cannot load 'gpt.bin': No error
T:\xt1032>mfastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
error: cannot load 'motoboot.img': No error
I can't seem to find the option to attach the screenshots (add image seems to be for online images)

adambration said:
ok initially, I got the "missing adbwinapi.dll" error message: copied adbwinapi.dll and adbwinusbapi.dll into the firmware folder (also copied the firmware into the minimal adb and fastboot folder, same result)
T:\xt1032>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
error: cannot load 'gpt.bin': No error
T:\xt1032>mfastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
error: cannot load 'motoboot.img': No error
I can't seem to find the option to attach the screenshots (add image seems to be for online images)
Click to expand...
Click to collapse
I think the adb is corrupt (those .dll errors), reinstall adb and then try again!
And for the screenshots just attack them as attachments in advance settings or just upload the image somewhere and then paste that link it here!

it appears I downloaded lost101's flashable zips instead of the correct firmware image (downloading as I write)
sidenote: still no luck in attaching images to my posts

Hello again,
I downloaded the firmware for retail US 4.4.4 off your thread (not the flashable zip as I initially did) and re-installed adb/fastboot 1.4.3.
fastboot devices found my xt1032
TA9290L3HG fastboot
I proceeded then with each line with fastboot and mfastboot (the latter was copied into the firmware folder)
for the 1st few lines (partition gpt, motoboot, logo.bin, boot...), I kept getting:
writing 'recovery'...
(bootloader) Preflash validation failed
when I got to the sparsechunk portions:
T:\retail>fastboot flash system system.img_sparsechunk.1
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.031s
all the modem section went well till the very end, it rebooted and I was back in 5.1 where I started!
Should I be using android sdk instead of adb/fastboot?
another site states to skip the 1st 2 commands when downgrading:
* mfastboot flash partition gpt.bin *
* mfastboot flash motoboot motoboot.img *
I have screenshots, but stll don't see the attachment option

screenshot attempt
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Stop trying random stuff and do exactly as I describe.
Extract this zip to the Factory Firmware Image folder: https://www.androidfilehost.com/?fid=24052804347778493
Use only a 5.1 Firmware Image. Use commands described in tutorial - but change sparsechunk names to match what you actually have in the folder.
Report back exactly what happens - with screenshots if necessary.​

[Recovery] TWRP 3.2.2.0 for redmi 6 pro ( sakura )

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
IM NOT THE CREATOR OF THIS TWRP, FOUND IT SPMEWHERE AND WANTED TO SHARE IT​
installation:
1. Setup ADB/Fastboot
2. Download the twrp from here : download
3. Power off your device.
4. Hold volume down + power button to boot into the bootloader.
5. Connect your device to your PC with a USB cable.
6. Open the command prompt on your PC.
7. Type cmmand : fastboot flash recovery "filename of recovery.img"
done
If u have anti rollback enabled :
first method:
fastboot boot "recovery.img"
in that booted twrp recovery flash twrp .img again and it will work
2nd method:
fastboot flash antirbpass "recovery.img"
changelog:
What's new in 3.2.2-0:
* adb backup fixes
* OTA style update zips will now install automatically without prompting for decrypt
* minor tweaks to handling date/time on Qualcomm devices
* updates to some language translations
for further questions and discussion join telegram group here

nofx161 said:
IM NOT THE CREATOR OF THIS TWRP, FOUND IT SPMEWHERE AND WANTED TO SHARE IT​
installation:
1. Setup ADB/Fastboot
2. Download the twrp from here : download
3. Power off your device.
4. Hold volume down + power button to boot into the bootloader.
5. Connect your device to your PC with a USB cable.
6. Open the command prompt on your PC.
7. Type cmmand : fastboot flash recovery "filename of recovery.img"
done
changelog:
What's new in 3.2.2-0:
* adb backup fixes
* OTA style update zips will now install automatically without prompting for decrypt
* minor tweaks to handling date/time on Qualcomm devices
* updates to some language translations
for further questions and discussion join telegram group here
Click to expand...
Click to collapse
C : \ adb> fastboot flash recovery sakura . img
sending 'recovery' (47604 KB)...
OKAY [ 1.562s]
writing 'recovery'...
FAILED (remote: rollback version downgrade)
finished. total time: 1.578s

evl01 said:
C : \ adb> fastboot flash recovery sakura . img
sending 'recovery' (47604 KB)...
OKAY [ 1.562s]
writing 'recovery'...
FAILED (remote: rollback version downgrade)
finished. total time: 1.578s
Click to expand...
Click to collapse
fastboot boot "recovery.img"
in that booted twrp recovery flash twrp .img again and it will work
u can aso try : fastboot flash antirbpass "recovery.img"

nofx161 said:
fastboot boot "recovery.img"
in that booted twrp recovery flash twrp .img again and it will work
u can aso try : fastboot flash antirbpass "recovery.img"
Click to expand...
Click to collapse
Now is asking for a password to decrypt. What should I put there?
---------- Post added at 10:53 PM ---------- Previous post was at 10:48 PM ----------
evl01 said:
Now is asking for a password to decrypt. What should I put there?
Click to expand...
Click to collapse
When I put cancel, I can enter to recovery but I can't use any storage. It's 0mb

If you factory reset through twrp and reboot recovery it should be OK. But keep in mind to do a backup of your stuff first.

Hello,
TWRP is released under GPLv3+. It means that if you submit a build of TWRP, you need to distribute its source code and instructions to build it.
Where did you find this build if you "found it somewhere and wanted to share it"? You are basically violating the license by just "sharing" it.
Read the pinned post for more information (applies to GPLv2 like GPLv3).

nofx161 said:
fastboot boot "recovery.img"
in that booted twrp recovery flash twrp .img again and it will work
u can aso try : fastboot flash antirbpass "recovery.img"
Click to expand...
Click to collapse
Thanks for the information, I lost connection with terminal after booting into TWRP, and didn't know what to do next as TWRP was o MB .
And terminal showed "FInished" with no error in your second command, but twrp was still not installed after holding down power + volumn down. :/
Is there anything i did wrong? Please reply Mr.Sakura

How to check if anti rollback is enabled?

Fastboot getvar anti

It just says anti: and no number. What does this means?

Mine shows the same so I think there is no anti rollback on our 2 devices.

mine also says "anti"..no number

Please be careful while flashing recovery that are found "somewhere".

Well, after flashing latest miuipro still anti with no count

Please delete this thread! False information!

any solution it is show 0mb internal

Do a factory reset in twrp or flash disable encryption.zip

forum.xda-developers.com/redmi-6-pro/development/recovery-twrp-v3-2-x-redmi-6-prosakura-t3851959
Check my post in above link

Doubt
coolek33 said:
If you factory reset through twrp and reboot recovery it should be OK. But keep in mind to do a backup of your stuff first.
Click to expand...
Click to collapse
How will i access the internal storage later if i format it totally ???

You will access it but it will be empty. So U can use sd card/usb otg for flashing

[Guide] TA-1050 LineageOS 18.1 Install

Nokia 6.1 - TA-1050 LineageOS 18.1 install
Note: These use A/B slots.
Thanks to @Raghu varma
Prerequsites:
- Official LineageOS 18.1 https://wiki.lineageos.org/devices/PL2/
- Unofficial TWRP (for) Android 11: https://forum.xda-developers.com/t/...in-recovery-project-nokia-6-1-plate2.4122949/
With TWRP, it must match the Android version being installed.
- Gapps For Android 11 ARM64: https://wiki.lineageos.org/gapps
Install ADB/Fastboot on Windows.
- Unlocked bootloader
- Know how to place phone into download mode (hold power and vol down)
Note: TWRP is NOT installed. We directly boot the TWRP image FILE each time TWRP is needed with the following commands:
From ADB in windows:
1. fastboot flash recovery twrp-3.4.0-0-PL2_sprout-11.0-20200909.img (ERRORS OUT - this is OK)
2. fastboot boot twrp-3.4.0-0-PL2_sprout-11.0-20200909.img
Installation procedure for the roms which doesn't comes with gapps
==============
1. Boot in to twrp (phone in download mode)
2. Click on wipe
3. Select format data
4. Type yes
5. Reboot to bootloader
6. Boot in to twrp
7. Select wipe
8. Select advance wipe
9. Select all except sdcard
10. Swipe to wipe
11. Copy rom.zip
12. Flash ROM.zip
11/12 - ADB Sideload LineageOS ROM:
a. In TWRP - Enable ADB Sideload
b. From PC: adb sideload lineage-18.1-20220208-nightly-PL2-signed.zip (Note: NO ERRORS ignore forums)
13. CHANGE SLOT (instructions continue below)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
a. In TWRP Change SLOT: Menu back to Reboot Options) Example: Refer Image, e.g. Current SLOT is A, change to B)
b. Reboot to TWRP again
c. Via ADB (per steps 11/12) flash GAPPS
- adb sideload MindTheGapps-11.0.0-arm64-20210920_084011.zip
14. Select wipe
15. Select advance wipe
16. Select all except system vendor SD card and swipe to wipe
17. Reboot system

I am longer trying to get LOS to my Nokia 6.1 and this procedure is the one I got most success so far.
I installed LOS on different mobiles and tablets before but this Nokia 6.1 PL2 TA-1043 seems to be different and difficult.
The Device is unlocked and adb and fastboot are working:
Code:
fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true <<-----
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
OKAY [ 0.001s]
Finished. Total time: 0.001s
I did a stockrom installation from https://nokia-sdm660.github.io/ and bootet both slots until the installation/configuration process started.
Then I started with above procedure.
Poweroff, booted Bootloader
add 1: additional: swipe to allow modifications
Followed till 10
11: I assumed copy from download directory to where adb finds it
12 worked fine
13: change slot -> OK
From there I cannot boot TWRP anylonger. Flasshing MindTheGapps at Point 12 results in unbootable Phone,
it gets into reboot loop.
Questions:
1. Is the slot change needed to install MindTheGapps?
2. If yes (I assume it is needed), any idea what I am doing wrong?
I am running on Linux, doing UNIX'ish OS since 1995 and I am very unused to Windows.
Info:
I accidently bootet TWRP-3.6 once and there no sideload started at all.

chi70 said:
I am longer trying to get LOS to my Nokia 6.1 and this procedure is the one I got most success so far.
I installed LOS on different mobiles and tablets before but this Nokia 6.1 PL2 TA-1043 seems to be different and difficult.
The Device is unlocked and adb and fastboot are working:
Code:
fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true <<-----
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
OKAY [ 0.001s]
Finished. Total time: 0.001s
I did a stockrom installation from https://nokia-sdm660.github.io/ and bootet both slots until the installation/configuration process started.
Then I started with above procedure.
Poweroff, booted Bootloader
add 1: additional: swipe to allow modifications
Followed till 10
11: I assumed copy from download directory to where adb finds it
12 worked fine
13: change slot -> OK
From there I cannot boot TWRP anylonger. Flasshing MindTheGapps at Point 12 results in unbootable Phone,
it gets into reboot loop.
Questions:
1. Is the slot change needed to install MindTheGapps?
2. If yes (I assume it is needed), any idea what I am doing wrong?
I am running on Linux, doing UNIX'ish OS since 1995 and I am very unused to Windows.
Info:
I accidently bootet TWRP-3.6 once and there no sideload started at all.
Click to expand...
Click to collapse
Hi,
Do not install TWRP.
Note: TWRP is NOT installed. We directly boot the TWRP image FILE each time TWRP is needed with the following commands:
From ADB in windows:
1. fastboot flash recovery twrp-3.4.0-0-PL2_sprout-11.0-20200909.img (ERRORS OUT - this is OK)
2. fastboot boot twrp-3.4.0-0-PL2_sprout-11.0-20200909.img
Instructions revised for clarity based on your feedback - Thanks.
I spend hours trying to get LineageOS on my TA-1050. With these steps, I can do it quickly every time.
Dont give up, you will get there!

I did not install TWRP but now I was able to install LOS 18.1!
I missed the
Code:
fastboot flash recovery twrp
before the
Code:
fastboot boot twrp
in 13.b.The ones before switching slot worked without.
Anyway, now the setup is running.
Thanks to all for the procedure, LinegaeOS, TWPR...
Christian

Lenovo M7 3rd Gen (TB-7306F) Unlock Bootloader and Root (MT8166)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Lenovo M7 3rd Gen (TB-7306F) Unlock Bootloader and Root Android 11​
Code:
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
Requirements​
PC​
MTK drivers , Adb and Fastboot drivers Installed​
Magisk APP​
Drivers and Softwares​
MTK Drivers​
ADB and FastBoot Drivers​
SDK (in attaeched files)​
Vbmeta files (in attaeched files)​
Magisk App​
Method​
1. Install the all things in given above
Extract SDK.zip and open that folder
2. Type cmd in address bar
3. go to about device . tap 7 times on build number and go to developer options and enable oem unlock
4. Reboot to Fastboot Mode
adb reboot bootloader or using recovery
5.Connect the tablet to Pc using data cable.
5.Type in CMD,
fastboot flashing unlock (automatically wipe data)
press vol.up key
fastboot reboot
______________________________________________________________________________________________________________________
Root​______________________________________________________________________________________________________________________
1.Make a patched boot.img or download the patched boot.img (Attached files)
2.Flash all empty Vbmeta Files according to the Partition (Vbmeta.zip) Type these in CMD
Code:
adb reboot fastboot
fastboot flash vbmeta_system_a {path to vbmeta_vbmeta_system_a.bin}
fastboot flash vbmeta_system_b {path to vbmeta_system_b.bin}
fastboot flash vbmeta_a {path to vbmeta_a.bin}
fastboot flash vbmeta_b {path to vbmeta_b.bin}
fastboot flash boot_a {path to boot_a.img}
fastboot flash boot_b {path to boot_b.img}
fastboot reboot
Example
3.Reboot to device to recovery mode by Pressing Vol. UP + Vol. Down + Power.
4.Wipe Data and Reboot. if you didnt wipe data you will get Bootloop.
Note
if you flash full stock rom through lenovo rescue and smart assitant, it will automatically lock the boot loader
you need to unlock the bootloader using above steps
______________________________________________________________________________________________________________________
Remove the Warning​
___________________________________________________________
1.Download the Waring_Remove.zip extract it
2.Type these in CMD
Code:
adb reboot bootloader
fastboot flash lk_a {path to lk_a.bin}
fastboot flash lk_b{path to lk_a.bin}
fastboot reboot
Fastboot mode vs Bootloader mode
Fastboot mode
Bootloader mode

Outstanding work, thank you. I have been hassling with this tablet for a month and just today I figured out how to unlock the bootloader. This is great work sir, thanks

If I didn't enjoy wrecking tech toys, I'd quit. Twice now I had to rescue the tablet because after flashing patched boot_a and b it loops even wipe a wipe.
It just finished restoring and it relockes the bootloader in the process.
Lenovo rescue tool works great
I think I will take a day off from this uninspiring tablet

toddy127 said:
If I didn't enjoy wrecking tech toys, I'd quit. Twice now I had to rescue the tablet because after flashing patched boot_a and b it loops even wipe a wipe.
It just finished restoring and it relockes the bootloader in the process.
Lenovo rescue tool works great
I think I will take a day off from this uninspiring tablet
Click to expand...
Click to collapse
Did you flashed the vbmeta?

I will admit I got a little confused with the process and forgot to flash the meta.

Thanks again. I am unlocked and rooted finally. I used the Linux on a stick and Windows. It was very easy thanks to you and the other developers work.
I left the bootloader warning on the tablet lol

Man, you are a life saver! Spent hours looking for a write up on this tablet. I actually ended up stuck in a bootloop after flashing vbmeta and then writing fastboot reboot according to the image above. (Im sort of a noob when it comes to this stuff.) After a while of tinkering was able to fix it simply by holding the vol + and vol - and plugging in usb from PC. Got it to load into fastboot and was able to wipe. But for real much appreciate the time and effort put into this write up especially for a niche tablet like this one. + Respect

smiley9000 said:
fastboot flash vbmeta_system_a {path to vbmeta_vbmeta_system_a.bin}
Click to expand...
Click to collapse
this command fails for me :/
>
Downloads/vbmeta/vbmeta_
❯ fastboot flash vbmeta_system_a vbmeta_system_a.bin
Sending 'vbmeta_system_a' (8192 KB) OKAY [ 0.343s]
Writing 'vbmeta_system_a' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
any ideas?

Rooting on MIUI 13.0.3.0

Hi there! So I've been trying to root F2 Pro using official magisk guide, I've patched boot.img (V13.0.3.0.SJKMIXM version, which is the same one I'm running) using Magisk 25.2 and 25.1 using fastboot and fastbootd, flashing or only booting into it, but whatever I do, magisk always displays N/A. Is there any method to root this version? Thanks in advance!

ashirviskas said:
Hi there! So I've been trying to root F2 Pro using official magisk guide, I've patched boot.img (V13.0.3.0.SJKMIXM version, which is the same one I'm running) using Magisk 25.2 and 25.1 using fastboot and fastbootd, flashing or only booting into it, but whatever I do, magisk always displays N/A. Is there any method to root this version? Thanks in advance!
Click to expand...
Click to collapse
Did you try with Magisk manager?

That is exactly what I was doing,.I've just tried magisk canary builds, but the exact same result - Installed: N/A

ashirviskas said:
That is exactly what I was doing,.I've just tried magisk canary builds, but the exact same result - Installed: N/A
Click to expand...
Click to collapse
The bootloader is unlocked?
Did you extract the boot.img from this fastboot rom?
POCO F2 Pro GlobalStableFastbootV13.0.3.0.SJKMIXM12.05.4 GB2022-06-20

NOSS8 said:
The bootloader is unlocked?
Did you extract the boot.img from this fastboot rom?
POCO F2 Pro GlobalStableFastbootV13.0.3.0.SJKMIXM12.05.4 GB2022-06-20
Click to expand...
Click to collapse
The bootloader is unlocked, I can successfully flash patched `boot.img` images (even my banking app stops working and after flashing original `boot.img` it starts working again, so I know that flashing is working), it's just that the magisk app still shows that nothing is installed.
Yes, this is the exact same image I've used.

ashirviskas said:
The bootloader is unlocked, I can successfully flash patched `boot.img` images (even my banking app stops working and after flashing original `boot.img` it starts working again, so I know that flashing is working), it's just that the magisk app still shows that nothing is installed.
Yes, this is the exact same image I've used.
Click to expand...
Click to collapse
I had this phone but I don't remember if it has RAMDISK?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

NOSS8 said:
I had this phone but I don't remember if it has RAMDISK?
Click to expand...
Click to collapse
It does.

And no vbmeta

ashirviskas said:
It does.
Click to expand...
Click to collapse
Surely you did everything correctly but just in case, check.(Possibly post a screenshot of the CMD with the result)
Copy the boot/recovery image to your device
Press the Install button on the Magisk card
If you are patching a recovery image, make sure “Recovery Mode” is checked in options.
In most cases, it should already be automatically checked.
Choose “Select and Patch a File” in the method, and select the stock boot/recovery image
The Magisk app will patch the image to [Internal Storage]/Download/magisk_patched_[random_strings].img.
Copy the patched image to your PC with ADB:
adb pull /sdcard/Download/magisk_patched_[random_strings].img
Flash the patched boot/recovery image to your device.
For most devices, reboot into fastboot mode and flash with the command:
fastboot flash boot /path/to/magisk_patched.img or
fastboot flash recovery /path/to/magisk_patched.img if flashing a recovery image
Reboot and voila!
Or use the twrp to flash the modified boot.img

Though I do see it when I run `adb shell ls -l /dev/block/by-name` I will try repatching and reflashing, maybe this is what has been missing.

Here's my latest attempt with vbmeta.img included:
sudo fastboot flash boot magisk_patched-25200_VvhFg.img
[sudo] password for mati:
Sending 'boot' (131072 KB) OKAY [ 3.275s]
Writing 'boot' OKAY [ 2.315s]
Finished. Total time: 5.600s
sudo fastboot flash vbmeta --disable-verity --disable-verification lmi_global_images_V13.0.3.0.SJKMIXM_20220620.0000.00_12.0_global/images
/vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (4 KB) OKAY [ 0.008s]
Writing 'vbmeta' OKAY [ 0.001s]
Finished. Total time: 0.024s
sudo fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.201s
Opening magisk app it still says `Installed: N/A`

Ok, I've just gotten it to work.. I had older, "hidden" magisk manager app on my phone. Removing it fixed everything, thank you for your time and effort.

ashirviskas said:
Ok, I've just gotten it to work.. I had older, "hidden" magisk manager app on my phone. Removing it fixed everything, thank you for your time and effort.
Click to expand...
Click to collapse
Better than stock(more options, call recorder)and play store certified without root.
https://xiaomi.eu/community/threads/miui-13-stable-release.64441/