Develop Bugs

How do I update the ROM OTA with rooted device?

Hi guys,
I'm on an outdated version of the global beta ROM and have received an OTA notification.
Unfortunately I can't run this as I'm rooted.
Please could you tell me the easiest way of updating the ROM without wiping everything and maintaining root?
Many thanks,
Andy

After flashing Rom root will be gone and if you need root just flash supersu.zip using twrp and you will get root back. That's all

sarthakwarlock said:
After flashing Rom root will be gone and if you need root just flash supersu.zip using twrp and you will get root back. That's all
Click to expand...
Click to collapse
thank you, unfortunately when I get into TWRP it asks for a password. Without a password I can't browse to the downloaded zip.
any idea?

andypa1 said:
thank you, unfortunately when I get into TWRP it asks for a password. Without a password I can't browse to the downloaded zip.
any idea?
Click to expand...
Click to collapse
Reflash Twrp from fastboot.

I've just found in a thread elsewhere:
"It's because of the dm-verity protection included in the MIUI firmwares.
To disable it, you have to:
- Format all encrypted partitions on fastboot (fastboot format system; fastboot format userdata;...)
- Boot on TWRP and flash a MIUI recovery image
- Download this patched boot file
- On fastboot flash the patched boot.img (fastboot flash boot boot-patched.img)
To manually remove the protection from a kernel you have to:
- Extract boot.img from a rom/device
- Unpack it, with this tool for example -> mkbootimg_tools
- Search the fstab file (fstab.qcom for example) and remove the "verify" mention and replace all "forceencrypt" mentions by "encryptable"
- Repack it and flash it"
I don't really understand this, or understand / remember how I managed to flash the global beta rom in the first place?!

in need of assistance on android 9.0 kernel & rooting issue

I flashed twrp recovery then i did not reboot i flashed a kernel witch is 9.0 compatiable then flashed magisk now I am stuck on a white screen with the Google G with a loading bar any help would be great

WoZzYDoesitbest said:
I flashed twrp recovery then i did not reboot i flashed a kernel witch is 9.0 compatiable then flashed magisk now I am stuck on a white screen with the Google G with a loading bar any help would be great
Click to expand...
Click to collapse
Just extract and fastboot flash the original boot.img from the factory image. You'll have to open the nested zipfile in the image file to get to it. Once you flash it, you should be back where you started and able to boot system. Retrace your steps and found out what you did wrong. Which kernel? As a side note, you should first fastboot boot the TWRP.img file and then while you are in TWRP, you flash the TWRP zip file. You can also use TWRP (boot) to queue up TWRP, Kernel, and Magisk and they will all flash in that sequence saving some time. There are also sticky guides on how to do this.

v12xke said:
Just extract and fastboot flash the original boot.img from the factory image. You'll have to open the nested zipfile in the image file to get to it. Once you flash it, you should be back where you started and able to boot system. Retrace your steps and found out what you did wrong. Which kernel? As a side note, you should first fastboot boot the TWRP.img file and then while you are in TWRP, you flash the TWRP zip file. You can also use TWRP (boot) to queue up TWRP, Kernel, and Magisk and they will all flash in that sequence saving some time. There are also sticky guides on how to do this.
Click to expand...
Click to collapse
Yeah appreciate it i figured it out last night this phone drives me nuts

BootLoop after installing (abd/fastboot) Boot.img. Need help!

HI there, so after patching the Boot.img with Magiskv23, it seems as if flashing it with ABD/Fastboot causes the bootloop. I had to flash to flash the stock boot.img back. Any advices? As I research this seems to be an issue with the fix being "I made some investigation and checked that replacing the file in the Magisk-v21.4.zip/arm/magiskboot with the magiskboot from v21.0 and flashing that one fixes the problem." But I have no idea how it'd work.
My device used to work with Magiskv21 until I updated my device and it has to be rooted again. So I got the stock boot.img file, patched it adb/fastboot flash it into the device (same method as before) and it causes bootloop.
If you experience a bootloop, attach a dmesg (kernel logs) when the device refuse to boot. This may very likely require a custom kernel on some devices as last_kmsg or pstore ramoops are usually not enabled by default.
HOW do I do this?
In addition, please also upload the result of cat /proc/mounts when your device is working correctly WITHOUT ROOT.
I can't go back to unrooting it, as I still want to keep my data on the device. Is there any way I could attach this without unrooting it?
If you experience issues during installation,
boot.zip
in recovery, upload the recovery logs, or in Magisk, upload the install logs. Please also upload the boot.img or recovery.img that you are using for patching.
Will include both stock boot.img, and stable and v23001 patched files.
I'll upload the boot.img file I use and the patched_boot.img file.
I can't upload with github so here https://drive.google.com/drive/folders/1YkekFaXmtOg6d5sMiecf3OnT7oqCEf4S?usp=sharing
Uploading boot.zip…
Device: Xiaomi 10T Pro (apollo) with MIUI Global Stable 12.5.1.0 (RJDMIXM)
Android version: 11 RKQ1.200826.002
Magisk version name: 23001
Magisk v23001 (I chose canary because that's what's needed to submit this report but I tried stable and the issue is the same as well)
Magisk version code: f822ca5(23001)

chinjangs said:
HI there, so after patching the Boot.img with Magiskv23, it seems as if flashing it with ABD/Fastboot causes the bootloop. I had to flash to flash the stock boot.img back. Any advices? As I research this seems to be an issue with the fix being "I made some investigation and checked that replacing the file in the Magisk-v21.4.zip/arm/magiskboot with the magiskboot from v21.0 and flashing that one fixes the problem." But I have no idea how it'd work.
My device used to work with Magiskv21 until I updated my device and it has to be rooted again. So I got the stock boot.img file, patched it adb/fastboot flash it into the device (same method as before) and it causes bootloop.
If you experience a bootloop, attach a dmesg (kernel logs) when the device refuse to boot. This may very likely require a custom kernel on some devices as last_kmsg or pstore ramoops are usually not enabled by default.
HOW do I do this?
In addition, please also upload the result of cat /proc/mounts when your device is working correctly WITHOUT ROOT.
I can't go back to unrooting it, as I still want to keep my data on the device. Is there any way I could attach this without unrooting it?
If you experience issues during installation,
boot.zip
in recovery, upload the recovery logs, or in Magisk, upload the install logs. Please also upload the boot.img or recovery.img that you are using for patching.
Will include both stock boot.img, and stable and v23001 patched files.
I'll upload the boot.img file I use and the patched_boot.img file.
I can't upload with github so here https://drive.google.com/drive/folders/1YkekFaXmtOg6d5sMiecf3OnT7oqCEf4S?usp=sharing
Uploading boot.zip…
Device: Xiaomi 10T Pro (apollo) with MIUI Global Stable 12.5.1.0 (RJDMIXM)
Android version: 11 RKQ1.200826.002
Magisk version name: 23001
Magisk v23001 (I chose canary because that's what's needed to submit this report but I tried stable and the issue is the same as well)
Magisk version code: f822ca5(23001)
Click to expand...
Click to collapse
when you were setting up the patched file you made sure you didnt choose rrecovery method in the magisk app
also rather flash it through twrp there are probably scripts that twrp has to run during the installation
if you dont have twrp you can flash it to recovery if you can access your fastboot/bootloader
reboot to recovery after then flash the patched boot.img to boot in twrp
(i dont know if you should clear cache or data or not just look for the guide )
reboot

flairepathos.info said:
when you were setting up the patched file you made sure you didnt choose rrecovery method in the magisk app
also rather flash it through twrp there are probably scripts that twrp has to run during the installation
if you dont have twrp you can flash it to recovery if you can access your fastboot/bootloader
reboot to recovery after then flash the patched boot.img to boot in twrp
(i dont know if you should clear cache or data or not just look for the guide )
reboot
Click to expand...
Click to collapse
I'm not sure how to use twrp, but I've rooted this device already just have issues with installing magisk patching boot.img after updating from magisk v20=>v23.
After that using boot.img that has been patched by magisk just causes bootloops.
Thanks for you comment though <3

chinjangs said:
I'm not sure how to use twrp, but I've rooted this device already just have issues with installing magisk patching boot.img after updating from magisk v20=>v23.
After that using boot.img that has been patched by magisk just causes bootloops.
Thanks for you comment though <3
Click to expand...
Click to collapse
Yes the stock boot image is locked bootloader so you will boot loop, flash magiskpatched boot image again to stop bootloop , even if its the old patched one

flairepathos.info said:
Yes the stock boot image is locked bootloader so you will boot loop, flash magiskpatched boot image again to stop bootloop , even if its the old patched one
Click to expand...
Click to collapse
Are you suggesting I use the old stock image where it works before I updated the magisk to version 23?
(I did that and it still bootloops)

Thank you for everyone's help. I've solved this by Uninstalling magisk v23001 and reinstalling magisk v23 thru TWRP in this method https://forum.xda-developers.com/t/...tom-rom-working-on-xiaomi-mi-10t-pro.4246339/

Question Magisk is not installing

The magisk apk, when flashed in TWRP flashes as normal but the app does not show up in the ROM, and the phone doesn't get rooted.
I had this problem on both ArrowOS and Syberia OS now, and I clean flashed both times directly from MIUI.
Can anyone help me out with this?

Install the magisk app

Rename magisk.apk to magisk.zip (only change the last 3 letters) and install it from TWRP-recovery.

zhyylz0201 said:
Install the magisk app
Click to expand...
Click to collapse
I already tried, this happened -

Iceman66 said:
Rename magisk.apk to magisk.zip (only change the last 3 letters) and install it from TWRP-recovery.
Click to expand...
Click to collapse
It didn't work either, when I open magisk app it shows this -

Download Canary version of Magisk (23001) from Github: https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-debug.apk
Rename app-debug.apk to app-debug.zip and flash it with TWRP

Iceman66 said:
Download Canary version of Magisk (23001) from Github: https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-debug.apk
Rename app-debug.apk to app-debug.zip and flash it with TWRP
Click to expand...
Click to collapse
No change

Other method is patching boot.img with magisk manager. You can find some tutorials with google. Extract the boot.img from ROM.zip, put in on internal memory of your phone and patch it with magisk manager app on your phone.
Than flash the patched boot.img with adb or TWRP. You need an extractor tool to get the boot.img from the rom.zip.

Iceman66 said:
Other method is patching boot.img with magisk manager. You can find some tutorials with google. Extract the boot.img from ROM.zip, put in on internal memory of your phone and patch it with magisk manager app on your phone.
Than flash the patched boot.img with adb or TWRP. You need an extractor tool to get the boot.img from the rom.zip.
Click to expand...
Click to collapse
I am using a custom kernel, will that change the process?

You need to reflash the custom kernel again after flashing the patched boot.img, but first check if your phone is rooted. (check in magisk app or install a root check app.)

The boot backup that I took before I flashed my custom kernel is the one that needs to be patched right?
If this isn't the case, can you guide me on how to get the boot.img? I only see payload.bin in my ROM.zip .

Okay, thank you for your help everyone
I ran into a different problem - when I install the patched boot.img, I get magisk but then I boot into TWRP and flash TWRP and my custom kernel, and I lose my root.

Dhruv.m said:
Okay, thank you for your help everyone
I ran into a different problem - when I install the patched boot.img, I get magisk but then I boot into TWRP and flash TWRP and my custom kernel, and I lose my root.
Click to expand...
Click to collapse
You have to patch the boot IMG with the TWRP already flashed, our phone doesn't have a recovery partition, so it's saved in the boot partition and installing Magisk from TWRP deletes the recovery, here is a good tutorial:
TWRP + Root
Hi all. Hope you are good and safe from Covid-19. If you like TWRP as your recovery and want to keep root access as well, I am going to show you how to do that. Because if you take the stock boot.img and patch it via magisk, you will lose TWRP...
forum.xda-developers.com

How to flash magisk zip

How can i flash magisk zip without twrp

PromiseKaunda said:
How can i flash magisk zip without twrp
Click to expand...
Click to collapse
Your device is old, it's better to handle with a new recovery like TWRP than another method (if there was)