Develop Bugs

After flashing TWRP, will not boot system

Good morning,
I'm sure it's something I'm missing. I had my tablet unlocked and running fine with TWRP. I went to Omni then to Preview 2. All was well.
Last night I decided to try SuperSU 2.72. I factory reset my Pixel C by installing the latest firmware. I then used fastboot to flash TWRP. It goes into TWRP fine but now it will not boot system any longer. It goes directly into TWRP when I have it boot system. Is this an encryption problem. I've tried both TWRP versions and same behavior.
Any idea what I'm doing wrong?
Thanks!

if you have 3.0.2 i think there was a problem with early build causing this. there was a link posted for the new one that supposedly fixed it. or just use the 3.0.0 build.

Mike02z said:
Good morning,
I'm sure it's something I'm missing. I had my tablet unlocked and running fine with TWRP. I went to Omni then to Preview 2. All was well.
Last night I decided to try SuperSU 2.72. I factory reset my Pixel C by installing the latest firmware. I then used fastboot to flash TWRP. It goes into TWRP fine but now it will not boot system any longer. It goes directly into TWRP when I have it boot system. Is this an encryption problem. I've tried both TWRP versions and same behavior.
Any idea what I'm doing wrong?
Thanks!
Click to expand...
Click to collapse
It seems some people have problems installing the NYCHitman1 TWRP version.
Most of them complaining because of boot problems.
To fix it:
Pls use xceed TWRP 3.0.0-0 version: http://forum.xda-developers.com/pix...official-twrp-2-8-7-0-pixel-c-dragon-t3288243
Or use my repacked TWRP 3.0.2-0 version : TWRP_dragon_3.0.2.0.img
Pls install TWRP via fastboot and boot directly into TWRP.
Install stock kernel (boot.img) via "fastboot" or use the TWRP flashable version from here: Update.ZIP_Nexus_Ryu_MXC89F-kernel_dragon.zip
Install SuperSU.zip 2.72 directly afterwards in TWRP - no reboot in between.
Download: http://forum.xda-developers.com/pixel-c/development/twrp-flashable-monthly-update-zip-pixel-t3375591
Good luck !

followmsi said:
It seems some people have problems installing the NYCHitman1 TWRP version.
Most of them complaining because of boot problems.
To fix it:
Pls use xceed TWRP 3.0.0-0 version: http://forum.xda-developers.com/pix...official-twrp-2-8-7-0-pixel-c-dragon-t3288243
Or use my repacked TWRP 3.0.2-0 version : TWRP_dragon_3.0.2.0.img
Pls install TWRP via fastboot and boot directly into TWRP.
Install stock kernel (boot.img) via "fastboot" or use the TWRP flashable version from here: Update.ZIP_Nexus_Ryu_MXC89F-kernel_dragon.zip
Install SuperSU.zip 2.72 directly afterwards in TWRP - no reboot in between.
Download: http://forum.xda-developers.com/pixel-c/development/twrp-flashable-monthly-update-zip-pixel-t3375591
Good luck !
Click to expand...
Click to collapse
Thanks guys! I did go back to 3.0.0-0 and it now boots into system. I'll also try your repackaged version of 3.0.2-0. I'm on my work PC but I don't see a link to your version. Is my work PC just hiding it or can I find it somewhere else? Thanks again!

Mike02z said:
Thanks guys! I did go back to 3.0.0-0 and it now boots into system. I'll also try your repackaged version of 3.0.2-0. I'm on my work PC but I don't see a link to your version. Is my work PC just hiding it or can I find it somewhere else? Thanks again!
Click to expand...
Click to collapse
Here is the direct link for TWRP_dragon_3.0.2.0.img:
https://onedrive.live.com/?authkey=...&id=479EB75F5DD9DA59!131&cid=479EB75F5DD9DA59
Here is the complete folder: (TWRP flashable stock kernel)
https://onedrive.live.com/?authkey=!ABLdSOKIeXgg_XU&id=479EB75F5DD9DA59!117&cid=479EB75F5DD9DA59
Cheers

Well in case of "recovery bootloop" start your device in bootloader mode and type "fastboot reboot" in command shell. That works mostly. No need to flash another recovery.

redukt said:
Well in case of "recovery bootloop" start your device in bootloader mode and type "fastboot reboot" in command shell. That works mostly. No need to flash another recovery.
Click to expand...
Click to collapse
And connect everytime with PC to do a manual reboot via fastboot .. seems a little bit too much for a simple reboot. At least for me
A proper TWRP with proper vboot will boot always correctly, like the one from xceed.
Did you ever had to do a manual reboot on his version ?
Should be fixed at the root cause .. Hope you agree ?
Cheers

I think there´s a little missunderstanding
The fastboot command helps you to get out of "recovery bootloop". After this you can reboot your device how offen you want without issues.
And yes with all existing TWRP versions I had some reboot hickups and have solved it with the fastboot method...

redukt said:
I think there´s a little missunderstanding
The fastboot command helps you to get out of "recovery bootloop". After this you can reboot your device how offen you want without issues.
And yes with all existing TWRP versions I had some reboot hickups and have solved it with the fastboot method...
Click to expand...
Click to collapse
Interesting .. I did not have any reboot issues with xceed TWRP versions .. I had to use the fix fastboot option once, but this is another topic.
But thanks for your information ...

followmsi said:
It seems some people have problems installing the NYCHitman1 TWRP version.
Most of them complaining because of boot problems.
To fix it:
Pls use xceed TWRP 3.0.0-0 version: http://forum.xda-developers.com/pix...official-twrp-2-8-7-0-pixel-c-dragon-t3288243
Or use my repacked TWRP 3.0.2-0 version : TWRP_dragon_3.0.2.0.img
Pls install TWRP via fastboot and boot directly into TWRP.
Install stock kernel (boot.img) via "fastboot" or use the TWRP flashable version from here: Update.ZIP_Nexus_Ryu_MXC89F-kernel_dragon.zip
Install SuperSU.zip 2.72 directly afterwards in TWRP - no reboot in between.
Download: http://forum.xda-developers.com/pixel-c/development/twrp-flashable-monthly-update-zip-pixel-t3375591
Good luck !
Click to expand...
Click to collapse
Hi.. after installing TWRP my phone nokia 3 TA-1020 I only booted to system once, when I restarted it later it does not boot the system but boots to TWRP. what can I do so that it will be rebooting to system instead of TWRP your help will be highly appreciated, thanks in advance.

Annan Denis said:
Hi.. after installing TWRP my phone nokia 3 TA-1020 I only booted to system once, when I restarted it later it does not boot the system but boots to TWRP. what can I do so that it will be rebooting to system instead of TWRP your help will be highly appreciated, thanks in advance.
Click to expand...
Click to collapse
Wrong device thread .. anyway just restore "stock" ROM/recovery to make it working again.
Good luck !

Help with Suhide in Zenfone2

Hello guys, somebody can help me install Suhide on Zenfone 2? I've tried the guides around, everything went fine thru the install in temporary TWRP, but when I relock the bootloader I end up in a bootloop.
My steps:
1-Unlocked phone with the unlock.bat
2-Turn off Cellphone
3-Started in Bootloader
4-Flashed Temporary TWRP
5-Go into Recovery
6-Flashed Magisk, SuperSu for magisk (2.76), dropped command in terminal echo "SYSTEMLESS=true" > /data/.supersu, flashed SuperSu (2.78)
7-Reboot into Bootloader
8-Relock phone with restore.bat
Even if I just flash SuperSu for Magisk (2.76) and doesn't update to 2.78 my phone ends in Bootloop.
Are I missing something?

Try using the tool. It might be easier. http://forum.xda-developers.com/showthread.php?t=3458145
Sent from my ASUS_Z00AD using Tapatalk

kenbo111 said:
Try using the tool. It might be easier. http://forum.xda-developers.com/showthread.php?t=3458145
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
so, I'm supposing that the fifth option in this tool is SuHide instead of PHH?

Best to use the systemless Magisk root. You can easily turn root off and on with the app. Read through the thread there a little. The tool does a lot.
Sent from my ASUS_Z00AD using Tapatalk

kenbo111 said:
Best to use the systemless Magisk root. You can easily turn root off and on with the app. Read through the thread there a little. The tool does a lot.
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
I was using Magisk+PHH, I want to use Suhide to test, because I used to use SuperSU.

I'd recommend not mixing Magisk and suhide, since suhide depends on SuperSU's su.d method for systemless add-ons.
If you are intent on using Magisk, make sure you are flashing the v6 zip that has been patched for zf2 or else you will get stuck on first boot. After Magisk is installed, you can install SuperSU 2.76 for Magisk from the Magisk thread without issue. To upgrade to SuperSU 2.78, do not flash any zip, just reboot and upgrade the SuperSU apk from the play store and do the upgrade as prompted when you open the app.
If you want to use the latest suhide (v0.53) with SuperSU v2.78-SR1, you need a patched zip to install SuperSU and allow zf2 to boot. I've attached the zip here, though I've only tested it on my own ZE551ML. Credits for original patch go to @shakalaca. With this zip, follow the instructions as given in the suhide thread.
Good luck.

Abex, thank you, I will try tomorrow when I arrive on my Job, there is my PC with all the stuff to do, I will post news if everything went fine or goes bad

abex181 said:
I'd recommend not mixing Magisk and suhide, since suhide depends on SuperSU's su.d method for systemless add-ons.
If you are intent on using Magisk, make sure you are flashing the v6 zip that has been patched for zf2 or else you will get stuck on first boot. After Magisk is installed, you can install SuperSU 2.76 for Magisk from the Magisk thread without issue. To upgrade to SuperSU 2.78, do not flash any zip, just reboot and upgrade the SuperSU apk from the play store and do the upgrade as prompted when you open the app.
If you want to use the latest suhide (v0.53) with SuperSU v2.78-SR1, you need a patched zip to install SuperSU and allow zf2 to boot. I've attached the zip here, though I've only tested it on my own ZE551ML. Credits for original patch go to @shakalaca. With this zip, follow the instructions as given in the suhide thread.
Good luck.
Click to expand...
Click to collapse
thanks. I was searching this for a long time.
is there a place where to find @shakalaca's contributions to Zenfone?

Abex, when I flash SuperSu 2.76 or 2.78-R1, even the version you've posted I got stuck into loading screen.

Hi all.
I am currently having the exact same issue with my Zenfone 2 ZE551ML. Things I have learned (Which may be very obvious to some)
The device cannot boot with the bootloader unlocked.
Locking the Bootloader with any kind of custom recovery installed causes the device to only boot into the bootloader. Recovery or stock ROM cannot be accessed.
The only way around this is to unlock the bootloader, flash the stock recovery and then relock the bootloader.
Steps I have taken:
1) Unlock the bootloader
2) Boot into the bootloader and flash latest TWRP recovery for ZF2 (twrp-3.0.2-0-Z00A.img)
3) Reboot into TWRP recovery
4) Flash the Xposed Uninstaller (latest version)
5) Flash the Magisk Uninstaller (latest version)
6) Flash Magisk-v6_repack_for_zf2_601.zip
7) Flash SuperSU-v2.76-magisk.zip
8) Enter TWRP Terminal, issue command - echo "SYSTEMLESS=true" > /data/.supersu
**Note at this point, I get no response from the terminal, just the next command line. I think I should be expecting one? And therefore something is failing at this step?**
9) Flash SR1-SuperSU-v2.78-SR1-20160915123031-fix_for_zf2.zip
10) Flash xposed-v86.2-sdk23-topjohnwu.zip (I am lead to believe that this is the only version that won't trip Safetynet, even later versions like 86.5 do)
11) Flash suhide-0.53.zip
12) Reboot to Bootloader
13) Flash the stock recovery
14) Lock Bootloader and reboot
This causes a bootloop on the splashscreen (White on black, so bootloader is locked) and on one attempt, a notification before the splashscreen informing me the device failed verification. The only solution I have found for this is to re-unlock the bootloader, enter recovery (stock) and sideload UL-Z00A-WW-4.21.40.134-user.zip
Then reboot to bootloader, lock bootloader again and reboot. No data missing or anything, but the phone is not rooted.
I'm wondering if suhide or superSU require the bootloader to be unlocked permanently- in which case, we need a solution for that. Could this be the case?
Or is it that we need a superSU v2.76 fix for Zf2 version, much like the v2.78 graciously posted by abex?
Perhaps it makes sense to sideload the Stock Marshmallow ROM at some point via TWRP, BEFORE returning to stock recovery? But even then, I think flashing it before superSU v2.76 seems pointless, as there are issues there- and does flashing it after simply wipe out all the hard work?

@kemp7, @Alterius:
If, after flashing a zip, you are getting stuck on boot or find that you can only boot to recovery, you can try flashing the boot.img from UL-Z00A-WW-4.21.40.134-user.zip in fastboot. This should get rid of any modifications to the boot image made by the various systemless mods you may have flashed previously. Any files added to the filesystem will still be present, but there should be no hook to load any systemless scripts like su.d or magisk. If you were using a custom kernel, it will no longer be installed. Of course, if you reflash the MM update zip in its entirety, this will be included, though I thought I should mention this to save you some time.
Before flashing any zip, you should try to get a general idea of what it will modify. If you've been flashing many zips and getting errors, it's a good idea to go back to a clean slate before trying something new. In fact, every time you flash a recent SuperSU zip, the script actually restores the boot image to a backup that was made the first time you flashed a recent SuperSU zip. This behaviour may be desirable, or it may unwittingly uninstall a custom kernel....
I also have to reiterate that its probably a bad idea to mix Magisk-based systemless mods with ones based on SuperSU's su.d.
Regarding the zip of SuperSU v2.78-SR1 that I posted, I'm not sure if it will work if you re-lock your bootloader afterwards. I can only report what I've tested and I keep my phone unlocked. That being said, the ZF2 can definitely boot with an unlocked bootloader, modified recovery, root, kernel, etc. Note that for MM rom, you will need to flash a modified TWRP in order to boot in to android (3.0.2-M1).
In this thread, I've reported a working instance of SuperSU v2.78-SR1, systemless xposed v86.2, and suhide v0.53 on my ZF2 with unlocked bootloader and TWRP-3.0.2 installed. To get there, I've only just followed the instructions on the suhide thread, except with the zips replaced with the ones patched for our ZF2 that I posted in that thread.
If you are having trouble, go back to stock MM rom. You can do this by flashing the stock recovery.img from the 4.21 zip in fastboot, then ADB sideload the whole zip. I think you should be able to do this with unlocked bootloader. Reboot into android to make sure all your data is still there.
Then, you can flash TWRP 3.0.2 for MM roms using fastboot. Your bootloader will need to be unlocked for permanent custom recovery. You might be able to dothe following with temporary TWRP (fastboot boot TWRP.img), but I haven't tested this.
From there you can follow the instructions in the suhide thread: flash SuperSU v2.78-SR1, (optionally reboot first, there will be a couple boot cycles before android starts up), flash suhide v0.53, (optional reboot), optionally flash systemless xposed v86.2, wipe dalvik cache, reboot.

Abex, thank for all the support again!
I've downloaded all the modified files for zenfone 2 from your posts ( SR1-SuperSU-v2.78-SR1-20160915123031-fix_for_zf2.zip and xposed-v86.2-sdk23-topjohnwu_repack_for_zf2.zip ), except the suhide installer (suhide-0.53.zip) that is the original file from suhide thread.
For Unlock & reLock Bootloader I was using one tool I found here on XDA that comes with two files (unlock.bat & restore.bat from this thread) but it makes my phone unbootable if I just unlock it if I remember correctly.
Theres any good and safe tool that do you recommend for just Unlock the bootloader so I can give I try?
Today I did a mess on my phone while trying to figure out the things, so I reflashed a RAW imagem from LL .196 and did the upgrade with the MM zip on Internal Card, then did a factory reset afterwards, so I'm basically "starting fresh" , so I believe that theres no trace from my old messy tries.

Simply cannot achieve root

Good evening all. I consider myself an advanced Android user but this one is just absolutely killing me and I know it's something easy. I simply cannot get root following these steps on Chainfire's thread
"- reflash stock boot.img
- fastboot boot /path/to/twrp.img
- TWRP install twrp.zip
- reboot into recovery
- TWRP install supersu.zip"
I have never attempted the version Chainfire released which is CF auto root, boot to root. Since I am interested in obtaining both TWRP and root I decided to go with chainfire's instructions using TWRP's boot image and TWRP zip install. I can fast boot boot the image , I can install TWRP from the zip just fine , I reboot into recovery then install SuperSU zip then reboot into the operating system and it says I have no root ....what am I doing wrong? This is killing me because I know I'm doing something wrong and it's really really easy. I can't really seem to find a good answer in the Q&A forum. Feeling defeated LOL. I would appreciate anybody's guidance

See you using 2.79 SR2?

bash_array said:
Good evening all. I consider myself an advanced Android user but this one is just absolutely killing me and I know it's something easy. I simply cannot get root following these steps on Chainfire's thread
"- reflash stock boot.img
- fastboot boot /path/to/twrp.img
- TWRP install twrp.zip
- reboot into recovery
- TWRP install supersu.zip"
I have never attempted the version Chainfire released which is CF auto root, boot to root. Since I am interested in obtaining both TWRP and root I decided to go with chainfire's instructions using TWRP's boot image and TWRP zip install. I can fast boot boot the image , I can install TWRP from the zip just fine , I reboot into recovery then install SuperSU zip then reboot into the operating system and it says I have no root ....what am I doing wrong? This is killing me because I know I'm doing something wrong and it's really really easy. I can't really seem to find a good answer in the Q&A forum. Feeling defeated LOL. I would appreciate anybody's guidance
Click to expand...
Click to collapse
You did fine until the last step. Go get yourself SU 2.79 SR2 and flash that in twrp RC1 and call it a night. I can think of at least 4 ways of achieving root but twrp RC2 + SU 2.79 SR2 is the latest method.

i think now you booted into the os you need to reboot into twrp then flash SU

quangtran1 said:
You did fine until the last step. Go get yourself SU 2.79 SR2 and flash that in twrp RC1 and call it a night. I can think of at least 4 ways of achieving root but twrp RC2 + SU 2.79 SR2 is the latest method.
Click to expand...
Click to collapse
I've been trying to flash SR4 this whole time... So flash SR2? I'll try it and report back. You guys rock.

bash_array said:
I've been trying to flash SR4 this whole time... So flash SR2? I'll try it and report back. You guys rock.
Click to expand...
Click to collapse
SR4 is 2.78. SR2 is 2.79 (latest).
That said, in practice, either will work.
Which TWRP have you been using? If you use SR4 with TWRP RC1, you'd have to delete the fstab file. That's why you go with 2.79 SR2.

quangtran1 said:
SR4 is 2.78. SR2 is 2.79 (latest).
That said, in practice, either will work.
Which TWRP have you been using?
Click to expand...
Click to collapse
RC1 of the latest TWRP. 3.0.0.2

That's why you couldn't install root.
If TWRP RC1 + SU 2.78 SR4, must delete fstab before flashing SU.
If insist on SU 2.78, then use TWRP Alpha2, not RC1.
If TWRP RC1 + 2.79 SR2, no need to delete fstab.

quangtran1 said:
SR4 is 2.78. SR2 is 2.79 (latest).
That said, in practice, either will work.
Which TWRP have you been using? If you use SR4 with TWRP RC1, you'd have to delete the fstab file. That's why you go with 2.79 SR2.
Click to expand...
Click to collapse
OK everyone in here that helped me out are complete and total bad asses! 2.79 SR2 Version was the ticket. I'm rooted. Shoot guys thanks so much!!! I appreciate it alot

This is what I flashed. Works great. Hopefully this thread helps somebody else out

bash_array said:
OK everyone in here that helped me out are complete and total bad asses! 2.79 SR2 Version was the ticket. I'm rooted. Shoot guys thanks so much!!! I appreciate it alot
Click to expand...
Click to collapse
Awesome, another happy customer.

TWRP not persisting through reboot + superSU flashing causes boot issue

Hi!
I'm currently using flash rom and kernel. As I've always done so, I like to flash TWRP and then SuperSU to enjoy the little tweaks offered by root.
Since the last 8.1 update, I'm facing a few issues that in my opinion are correlated.
First, flashing TWRP works well, but it seems not to be systemless, i.e. when I reboot my device the proper way, TWRP disappears.
Secondly, when I try to flash the latest stable SuperSU zip through my working TWRP (it's a one shot...), the process gives me no error, but then on the first boot, I get stuck on the huge Google logo... The only thing I can do is re-flashing boot.img but obviously the SuperSU app didn't install...
What should I do? Install a beta SuperSU version? Try Magisk (honestly, I don't really like it...)
Thanks for your help and patience!

azertguigui said:
Hi!
I'm currently using flash rom and kernel. As I've always done so, I like to flash TWRP and then SuperSU to enjoy the little tweaks offered by root.
Since the last 8.1 update, I'm facing a few issues that in my opinion are correlated.
First, flashing TWRP works well, but it seems not to be systemless, i.e. when I reboot my device the proper way, TWRP disappears.
Secondly, when I try to flash the latest stable SuperSU zip through my working TWRP (it's a one shot...), the process gives me no error, but then on the first boot, I get stuck on the huge Google logo... The only thing I can do is re-flashing boot.img but obviously the SuperSU app didn't install...
What should I do? Install a beta SuperSU version? Try Magisk (honestly, I don't really like it...)
Thanks for your help and patience!
Click to expand...
Click to collapse
Do this, first boot twrp, don't flash it. Once booted flash SU 2.82 SR5. Then boot back into the bootloader from twrp and flash twrp. Works for me.
Sent from my [device_name] using XDA-Developers Legacy app

jd1639 said:
Do this, first boot twrp, don't flash it. Once booted flash SU 2.82 SR5. Then boot back into the bootloader from twrp and flash twrp. Works for me.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Huge thanks for this!!! I was having the exact same problem (boot hangs at Google logo) and this resolved it!
I noticed that afterwards in the apps drawer I could not find any SuperSU, but doing adb shell and then invoking su worked, so I then just installed the supersu app from the play store to handle prompts (it seems without the app, root is enabled silently and doesn't seem like that great of an idea).
-----------EDIT------------
After installing the app from play store, DO NOT allow it to update the supersu binaries! I ran into bootloop again after that, and had to re-flash SR5 again. Seems like that's the magical version to use!

You're right about having super su update. I had the same problem.
Edit, I just checked and I'm actually using SR3. SuperSu then updated those binaries without a problem.

Hi, thanks for the answers. What do you guys mean by 'booting twrp without flashing it'? What's the fastboot command?

azertguigui said:
Hi, thanks for the answers. What do you guys mean by 'booting twrp without flashing it'? What's the fastboot command?
Click to expand...
Click to collapse
fastboot boot (drag and drop twrp.img file here)
Sent from my Nexus 5X using Tapatalk

Well for the record, I did the following
Code:
fastboot boot twrp-3.2.1-0-bullhead
Then, I installed SuperSU downloaded here. I went back to fastboot and used
Code:
fastboot flash twrp-3.2.1-0-bullhead
but I still got stuck on the Google logo, meaning that my boot was corrupted or something... I then flashed the original Google boot.img
Code:
fastboot flash boot.img
and re-did the process of flashing SuperSU but I wisely chose to find a SR5 version of the file. I didn't flash TWRP after that and my phone booted normally with supersu.apk installed in it and the root privileges granted ... I don't know if I should try flashing TWRP again since my phone is working fine right now, but thanks anyway for the tip of booting to TWRP and not flashing it directly!

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/