Develop Bugs

[RECOVERY][unofficial][anthias / zenwatch] TWRP 3.0.2

TWRP recovery 3.0 zenwatch
How to install ​Use this giude to unlock bootloader and boot fastboot/recovery
http://forum.xda-developers.com/zenwatch/general/guide-how-to-access-recovery-zenwatch-t3167623
Warning ! Unlock bootloader wipe your data!​
update
Twrp 3.0.2 For android wear 1.4
NOT INSTALL ON ANDROID WEAR 1.3 !
Download twrp 3.0.2
installation
Code:
fastboot flash recovery twrp-3.0.2_anthias.img
Photos
{
"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"
}
Stock Recovery for Android Wear 1.4
installation stock recovery
Download stock recovery
Code:
fastboot flash recovery recovery_MEC23S.img
OLD VERSION FOR ANDROID WEAR 1.5 / TWRP 3.0 /TWRP 3.0.1
Download twrp 3.0.1-0 Zenwtach AW 1.4
Download twrp 3.0
OLD VERSION FOR ANDROID WEAR 1.3 / TWRP 2.8.7.0
old version (for android wear 1.3) download twrp mega.nz
Reboot into bootloader and flash recovery
Code:
fastboot flash recovery twrp_2.8.7.0_anthias.img
source https://github.com/asyan4ik/asus_anthias/tree/master

acbka said:
Twrp recovery 2.8.7.0 zenwatch
How to install ​
Use this giude to unlock bootloader and boot fastboot/recovery
http://forum.xda-developers.com/zenwatch/general/guide-how-to-access-recovery-zenwatch-t3167623
Warning ! Unlock bootloader wipe your data!
download twrp basketbuild.com
Reboot into bootloader and flash recovery
Code:
fastboot flash recovery twrp_2.8.7.0_anthias.img
Click to expand...
Click to collapse
I am not able to download the file. Getting a 404 error off the page. Any chance you could upload it to another service?
Thanks in advance!

btonetbone said:
I am not able to download the file. Getting a 404 error off the page. Any chance you could upload it to another service?
Thanks in advance!
Click to expand...
Click to collapse
Same. Thanks.

Ups , i fix this today ...
Sorry

hecksagon said:
Same. Thanks.
Click to expand...
Click to collapse
reload to mega . sorry

Fantastic! Flashed it and used it to flash a Wear version of SuperSU. Watch is rooted, without having to use KingRoot!
Let's see, somebody posted a system image a while back, didn't they? I guess I could flash that to unroot if there's a firmware update.

CSX321 said:
Fantastic! Flashed it and used it to flash a Wear version of SuperSU. Watch is rooted, without having to use KingRoot!
Let's see, somebody posted a system image a while back, didn't they? I guess I could flash that to unroot if there's a firmware update.
Click to expand...
Click to collapse
Yes, I pulled a system image and another user modified to successfully pass the checks that occur during updates (the original pull didn't pass). Check out this thread: http://forum.xda-developers.com/zenwatch/development/root-t3163248
Makes sure you read up on it, though, as it sounds like you'd need to do some legwork to get the system image to work. Relevant posts in that thread are 32, 52, and 54.
Hopefully, though, having TWRP means that someone smarter-than-I-am may develop even more elegant solutions!
Cheers!

Now that we have twrp we can do a system pull from an unrooted device. The system image posted in the other thread will only work on the previous version of Android Wear. Do not flash if you are up to date.

Flashing the system.img for the ZenWatch on LCA43 does work but I wouldn't recommend it (I had to recently wipe my watch to test something), as long as you do an update path from flashing to directly flashing the OTA zip, but it's long winded (of course now that we have TWRP, updates and flashing back to "stock" will be so much easier). That, and KingRoot seems to leave a lot of trace files.
Also as a sidenote, because of SuperSu, I was able to install Stericson's BusyBox from the app (sideloaded apk). KingRoot's root authorization window didn't play well with Android Wear.

itechnoguy said:
Flashing the system.img for the ZenWatch on LCA43 does work but I wouldn't recommend it (I had to recently wipe my watch to test something), as long as you do an update path from flashing to directly flashing the OTA zip, but it's long winded (of course now that we have TWRP, updates and flashing back to "stock" will be so much easier). That, and KingRoot seems to leave a lot of trace files.
Also as a sidenote, because of SuperSu, I was able to install Stericson's BusyBox from the app (sideloaded apk). KingRoot's root authorization window didn't play well with Android Wear.
Click to expand...
Click to collapse
The current system image in the other thread still has Kingroot on it. After removing that I tried to flash SuperSU but that force closes. Would like to get somebody who has not rooted to do a twrp backup and post it. We should be able to make a new flashable clean system image from that.

hecksagon said:
The current system image in the other thread still has Kingroot on it. After removing that I tried to flash SuperSU but that force closes. Would like to get somebody who has not rooted to do a twrp backup and post it. We should be able to make a new flashable clean system image from that.
Click to expand...
Click to collapse
Make sure you're using this zip file to install SuperSU (it seems to be the same binary as Chainfire's) since the app itself doesn't work, and this one doesn't require authorizations (not completely safe, but it works).
(also, don't forget to unroot from the KingRoot app first; the unroot seems to be clean enough to use Wear SuperSU)

itechnoguy said:
Make sure you're using this zip file to install SuperSU
Click to expand...
Click to collapse
That's the one I used, and it works. (Though there's no authorization popups, as you said.)

Theres an app called Super SUMe, in the Play Store that'll switch out KingRoot for SuperSU. Super easy to do, one click to complete the process. Have no idea if it'll work on watches, but I guess it doesnt hurt to try? Make sure you make backup first, now that TWRP is available..
Hoping to get this watch today! or maybe the Moto360..

Talysdaddy said:
Theres an app called Super SUMe, in the Play Store that'll switch out KingRoot for SuperSU. Super easy to do, one click to complete the process. Have no idea if it'll work on watches, but I guess it doesnt hurt to try? Make sure you make backup first, now that TWRP is available..
Hoping to get this watch today! or maybe the Moto360..
Click to expand...
Click to collapse
It'll probably remove KingRoot successfully, but the Zenwatch can't launch the SuperSU app, so root authorization dialogs never show up (the su binary still gets installed, but it can't do anything without permission from the app first).

Boooooo moto 360. It's sooo damn big.

@acbka How did you set up your build environment? I wasn't exactly sure what to initially use (other than not using the CyanogenMod sources since it doesn't work well with building TWRP; I'm assuming Omni 5?).

itechnoguy said:
@acbka How did you set up your build environment? I wasn't exactly sure what to initially use (other than not using the CyanogenMod sources since it doesn't work well with building TWRP; I'm assuming Omni 5?).
Click to expand...
Click to collapse
hi . i update first message .
add my github

Message for all you zenwatch 2 people.. Don't try to flash this recovery. You will have a soft brick. And with no resources at this time. There is no fix.
Sent from my ASUS_Z00A using Xparent BlueTapatalk 2

Has anyone pulled the stock system partition? I, stupidly, didn't do it before I installed SuperSU. I'd like to be able to go back to stock, if there's another firmware update.

I need a link to the stock recovery.IMG file

Factory Firmware or OTA

I'm just interested in people's opinion on this matter. When manually updating your phone, do you choose to Flash the Factory firmware or sideload the OTA image using adb through the stock recovery? Why do you choose that option? Just interested in others responses.
DU 9.0

I use the factory image with the -w removed. I root so need the boot.img to patch, which the factory image has and the ota doesn't.

jd1639 said:
I use the factory image with the -w removed. I root so need the boot.img to patch, which the factory image has and the ota doesn't.
Click to expand...
Click to collapse
+1 for the same reasons! Easier and more convenient IMHO.
Cheers...
Sébastien.

I'm completely stock, and plan on staying that way, so I just wait for the OTA.

bobbyphoenix said:
I'm completely stock, and plan on staying that way, so I just wait for the OTA.
Click to expand...
Click to collapse
Same here stock rooted on Android 10, I just take OTA and follow magisk steps to update and keep root. No need to ever touch a PC or patch boot.img.

For monthlies I sideload the OTA.
It is quick easy and has no impact on my current setup.
I flash factory when there is a substantial change like 9->10 or I done f*cked up and just need a do over.

parakleet said:
For monthlies I sideload the OTA.
It is quick easy and has no impact on my current setup.
I flash factory when there is a substantial change like 9->10 or I done f*cked up and just need a do over.
Click to expand...
Click to collapse
Same here. With the OTA it's no fuss, no muss. Just download the OTA and sideload it. It doesn't wipe so no need to open anything in a file editor and worry about messing something up.

I've been doing factory images each month since the original Pixel release. Sometimes I'll remove the -w, sometimes I won't.
The biggest drawback is that Google Play Music thinks its a new device every time and counts against the limit of devices. You can also only remove a few devices per year. I've had to contact support a few times to have them clear out my device list.

boostedduece said:
Same here stock rooted on Android 10, I just take OTA and follow magisk steps to update and keep root. No need to ever touch a PC or patch boot.img.
Click to expand...
Click to collapse
How do you take the OTA while rooted?
Edit: Nvm, found the tutorial. Now the question is, would that tutorial work with a custom kernel installed?

Yes, I have done it multiple times on pie and Android 10 using a custom kernel, you need to reflash the kernel though, since it gets replaced with stock.
I used to do the flash all method, now I just update from my couch, lol.
Works every time.
Edit: disable all modules before hand
https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md

Would someone mind laying out the steps to take the OTA without using a PC and messing with the patched boot img?

Androider4Life said:
Would someone mind laying out the steps to take the OTA without using a PC and messing with the patched boot img?
Click to expand...
Click to collapse
Google, magisk XDA

Androider4Life said:
Would someone mind laying out the steps to take the OTA without using a PC and messing with the patched boot img?
Click to expand...
Click to collapse
Hi,
Just go to the link in the post above yours..! ?
Here it is for the lazy guys/girls:
Simply disable automatic updates in Dev options if not already > restore stock boot.img using uninstall option in bottom main screen of Magisk > take ota "without" clicking reboot now! > Go back in Magisk and select install > install to "inactive slot" > reboot> done!
Cheers,
Sébastien.

5.1 said:
Hi,
Just go to the link in the post above yours..!
Here it is for the lazy guys/girls:
Simply disable automatic updates in Dev options if not already > restore stock boot.img using uninstall option in bottom main screen of Magisk > take ota "without" clicking reboot now! > Go back in Magisk and select install > install to "inactive slot" > reboot> done!
Cheers,
Sébastien.
Click to expand...
Click to collapse
This is butter

I followed this procedure but when I exited the OTA, Magisk was gone. What step did I miss? How do I restore root? Thank you!

STraver said:
I followed this procedure but when I exited the OTA, Magisk was gone. What step did I miss? How do I restore root? Thank you!
Click to expand...
Click to collapse
Did you reboot after restoring the stock boot image and before taking the ota? Now you'll have to get the stock boot.img on your device and patch it with magisk. Then flash the patched image from your pc using fastboot.

jd1639 said:
Did you reboot after restoring the stock boot image and before taking the ota? Now you'll have to get the stock boot.img on your device and patch it with magisk. Then flash the patched image from your pc using fastboot.
Click to expand...
Click to collapse
Okay lesson learned! Thanks for responding. I did reboot after restoring stock image but not after the OTA as the directions said.

5.1 said:
Hi,
Just go to the link in the post above yours..!
Here it is for the lazy guys/girls:
Simply disable automatic updates in Dev options if not already > restore stock boot.img using uninstall option in bottom main screen of Magisk > take ota "without" clicking reboot now! > Go back in Magisk and select install > install to "inactive slot" > reboot> done!
Cheers,
Sébastien.
Click to expand...
Click to collapse
When i go into Magisk and Choose Uninstall> Restore Images, I get "Stock backup does not exist"
EDIT: Ended up just pulling a boot.img from the latest factory image, flashing that via fastoot, flashing the lastest factory image with -w removed from the flash-all.bat, patching the boot.img with magisk and flashing that patched img in fastboot.

Androider4Life said:
When i go into Magisk and Choose Uninstall> Restore Images, I get "Stock backup does not exist"
EDIT: Ended up just pulling a boot.img from the latest factory image, flashing that via fastoot, flashing the lastest factory image with -w removed from the flash-all.bat, patching the boot.img with magisk and flashing that patched img in fastboot.
Click to expand...
Click to collapse
Hello,
Strange you didn't have the backed up stock boot.img. It is located in /data if you scroll at the bottom, you should see it! :good:
{
"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"
}
Glad you got it sorted anyway!
Cheers...
Sébastien.

Install OTA with root

I have a doubt. What should I do if I have magisk installed and I want to update by OTA?

Ruvahkiin said:
I have a doubt. What should I do if I have magisk installed and I want to update by OTA?
Click to expand...
Click to collapse
1. Update and DONT reboot.
2. In magisk: install --> install to inactive slot (after OTA)
3. Reboot.

Shouldn't it be like this?
1.Turn off all modules in Magisk
2.Uninstall Magisk / Restore Image /DON'T Reboot
3.Install OTA / DON'T Reboot
4.Start Magisk Manager and click Install to inactive slot / Reboot.
Because if you update before restoring stok boot.img your phone gets many many problems and perhaps you must perform factory reset to let it work properly after OTA.
Tapatalk via OnePlus 7T

Riski3Run said:
Shouldn't it be like this?
1.Turn off all modules in Magisk
2.Uninstall Magisk / Restore Image /DON'T Reboot
3.Install OTA / DON'T Reboot
4.Start Magisk Manager and click Install to inactive slot / Reboot.
Because if you update before restoring stok boot.img your phone gets many many problems and perhaps you must perform factory reset to let it work properly after OTA.
Tapatalk via OnePlus 7T
Click to expand...
Click to collapse
No. You can do it like you said but it's not necessary.
I heard on other phones you will get issues but not with OnePlus.

I just uninstall magisk and leave modules installed, update, install magisk to inactive slot, reboot.

I did not uninstall Magisk, just disabled the one module that I was using. My steps:
In Magisk Manager: Disable all Magisk modules, reboot
Install OTA update / DON'T Reboot
Open Magisk Manager: click on Install/Install/Direct Install, DON'T Reboot
Once again in Magisk Manager: click on Install/Install/Inactive Slot
Reboot

Kollachi said:
1. Update and DONT reboot.
2. In magisk: install --> install to inactive slot (after OTA)
3. Reboot.
Click to expand...
Click to collapse
Can you confirm this works with the 10.0.12 update? I'm honestly confused because every answer is different.
And also, should I let my phone download the whole update, which it wants me to because it detects the root, or should I do only the OTA via Oxygen Updater?
Thanks in advance.

kaeptn1 said:
Can you confirm this works with the 10.0.12 update? I'm honestly confused because every answer is different.
And also, should I let my phone download the whole update, which it wants me to because it detects the root, or should I do only the OTA via Oxygen Updater?
Thanks in advance.
Click to expand...
Click to collapse
Mine was from 10.0.11 to 10.0.12 HD65AA. I let the phone update though the OTA. Root was detected and it downloaded the entire update, i proceeded with install, just did not reboot when it completed.

I am also getting confused now...
Someone says if we are rooted we won't get OTA but full ROM update.
Tell me what I have OTA or full ROM update? (see screenshot) Which steps with Magisk must I take to update from 10.0.11HD65BA to 10.0.12HD65BA without loosing any data.
Thanks in advance.
{
"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"
}
Tapatalk via OnePlus 7T

Riski3Run said:
I am also getting confused now...
Someone says if we are rooted we won't get OTA but full ROM update.
Tell me what I have OTA or full ROM update? (see screenshot) Which steps with Magisk must I take to update from 10.0.11HD65BA to 10.0.12HD65BA without loosing any data.
Thanks in advance. View attachment 5077859
Tapatalk via OnePlus 7T
Click to expand...
Click to collapse
2.6 GB is the full rom.
As it was written:
- Disable all modules, reboot
- Do the full download as suggested and the upgrade via system updater and DO NOT REBOOT
- install magisk to inactive slot, reboot
- boom Chaka laka!
Gesendet von meinem HD1903 mit Tapatalk

So no need to restore first via Magisk stock boot.img coz update will overwrite to stock anyway?
I am so "scared" coz last time I did wrong from 10.01.09 to 10.01.10 and I had to factory reset and waste whole day to install everything again and root it again.
Edit:
I don't have TWRP so after update must simply flash via fastboot magisk_patched.img 10.0.12HD65BA or what?
Tapatalk via OnePlus 7T

Updated from 10.0.11 to 10.0.12 and all I did was:
1. Disable all magisk modules
2. Updated from normal ota, didn't reboot
3. Back to magisk manager and click on Install/Install/Direct Install
4. Again in magisk manager click on Install/Install/Inactive Slot
5. Reboot
6. Activate all modules.
Done no patching no nothing

danielud said:
Updated from 10.0.11 to 10.0.12 and all I did was:
1. Disable all magisk modules
2. Updated from normal ota, didn't reboot
3. Back to magisk manager and click on Install/Install/Direct Install
4. Again in magisk manager click on Install/Install/Inactive Slot
5. Reboot
6. Activate all modules.
Done no patching no nothing
Click to expand...
Click to collapse
3. Step isn't needed because OTA will install to the other partition and your active one will be untouched. And I personally didn't deactivate modules.
---------- Post added at 12:50 PM ---------- Previous post was at 12:43 PM ----------
Riski3Run said:
I don't have TWRP so after update must simply flash via fastboot magisk_patched.img 10.0.12HD65BA or what?
Tapatalk via OnePlus 7T
Click to expand...
Click to collapse
You can also do this:
1. fastboot boot magisk_patched.img
2. Magisk manager --> Install --> install --> direct install
3. Reboot
With this method you wont get bootloops or anything. Because if you boot the image only it's not temporary. That's why you install in magisk manager.

Question [CLOSED] POCO F3 GLOBAL STUCK ON BOOT LOGO. HELP NEEDED.

Ok, so for some reason, my poco f3 global (alioth, miui 12.5.1) is stuck on boot logo (the screen that shows poco f3) after flashing a magisk patched boot image of the same firmware.
I don't have twrp, also adb command to remove magisk doesn't work. any workaround to remove magisk using a fastboot command? :/ any other way? can I install twrp at this stage without losing data?
I am genuinely sick of this device, a part from the very VERY bad quality of the hardware, NFC did not work for me even on stock bl locked firmware, a lot of issues happened when I rooted it for the first time and made me lose data. now today the device updated automatically to miui 12.5.1 and made me lose root despite having all auto update options disabled. I am genuinely considering throwing away this phone if I lose data this time. please help.

just flash a new boot image without magisk from the rom you were flashing.
next time you want magisk just boot the alpha twrp the F3 has and flash magisk as normal from there

metalspider said:
just faslh a new boot image without magisk from the rom you were flashing.
next time you want magisk just boot the alpha twrp the F3 has and flash magisk as normal from there
Click to expand...
Click to collapse
Thanks for the reply, Im on it right now, also curious about the second part, what is the alpha twrp? can you elaborate? As you see I mentioned having not installed twrp.

Ghostface009 said:
Thanks for the reply, Im on it right now, also curious about the second part, what is the alpha twrp? can you elaborate? As you see I mentioned having not installed twrp.
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/recovery-alpha-teamwin-recovery-project.4272625/
Code:
Fastboot boot
the TWRP
This way will not install TWRP in the device but can use TWRP.
There's option in Developer option as Automatic system updates.
{
"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"
}
Free phones welcomed.

pl1992aw said:
https://forum.xda-developers.com/t/recovery-alpha-teamwin-recovery-project.4272625/
Code:
Fastboot boot
the TWRP
This way will not install TWRP in the device but can use TWRP.
There's option in Developer option as Automatic system updates.
Free phones welcomed.
Click to expand...
Click to collapse
That sounds really good. could be useful.
Sadly this option in dev options was already disabled, yet it updated itself automatically. which is the thing that enraged me the most.

Ghostface009 said:
That sounds really good. could be useful.
Sadly this option in dev options was already disabled, yet it updated itself automatically. which is the thing that enraged me the most.
Click to expand...
Click to collapse
As you wrote earlier, you had root access before MIUI update.
Once you get root, use Debloater to debloat the updater.
Code:
com.android.updater
is one of it.
Maybe there's other ones, but I don't have this phone, can't tell much about it.

Ghostface009 said:
Ok, so for some reason, my poco f3 global (alioth, miui 12.5.1) is stuck on boot logo (the screen that shows poco f3) after flashing a magisk patched boot image of the same firmware.
I don't have twrp, also adb command to remove magisk doesn't work. any workaround to remove magisk using a fastboot command? :/ any other way? can I install twrp at this stage without losing data?
I am genuinely sick of this device, a part from the very VERY bad quality of the hardware, a lot of issues happened when I rooted it for the first time and made me lose data. now today the device updated automatically to miui 12.5.1 and made me lose root despite having all auto update options disabled. I am genuinely considering throwing away this phone if I lose data this time. please help.
Click to expand...
Click to collapse
have you managed to fix your issue? what rom version are you running, do you need stock boot.img still?

Ghostface009 said:
Thanks for the reply, Im on it right now, also curious about the second part, what is the alpha twrp? can you elaborate? As you see I mentioned having not installed twrp.
Click to expand...
Click to collapse
Alpha TWRP is simply an unofficial TWRP developed by Nebrassy. It can do most of the things. One of which, flashing magisk. So you should give it a shot.

Issue solved after flashing unmodified boot.img, thanks all.
laid1995 said:
Alpha TWRP is simply an unofficial TWRP developed by Nebrassy. It can do most of the things. One of which, flashing magisk. So you should give it a shot.
Click to expand...
Click to collapse
Unfortunately it doesn't boot, I entered the fastboot command and it's just a black screen. I guess this doesn't work with MIUI 12.5.1, and that means Im stuck without root thanks to xiaomi
I also tried the adb command to remove magisk modules, didn't work, says inaccessable or not found

Cmn, stop blame Xiaomi and read and learn more before doing something that can mess up ur phone. Just a friendly advice
If u can boot to fastboot u can try to flash a stock ROM using MiFlash with "keep user data" checked....maybe u'll be lucky and ur phone will boot normally.

Alin45 said:
Cmn, stop blame Xiaomi and read and learn more before doing something that can mess up ur phone. Just a friendly advice
If u can boot to fastboot u can try to flash a stock ROM using MiFlash with "keep user data" checked....maybe u'll be lucky and ur phone will boot normally.
Click to expand...
Click to collapse
...But they did tho
The phone boots now, but still, I lost magisk and now I cannot install it on this update.
The phone also can't pass safetynet for some reason, despite having stock boot.img restored and leaving no trace of magisk.
All that could've been avoided if the device just did as it was told to, not to automatically update itself.

reg66 said:
have you managed to fix your issue? what rom version are you running, do you need stock boot.img still?
Click to expand...
Click to collapse
12.5.1
flashing stock boot.img of 12.5.1 (extracted using payload dumper tool) solved the issue
However, I can't root rhe phone on this update anyway, tried to boot alphatwrp and failed, Also safetynet fails

Ghostface009 said:
12.5.1
flashing stock boot.img of 12.5.1 (extracted using payload dumper tool) solved the issue
However, I can't root rhe phone on this update anyway, tried to boot alphatwrp and failed, Also safetynet fails
Click to expand...
Click to collapse
Safetynet fails because of the unlocked bootloader (most probably). Being unable to use TWRP is strange. Did u use the correct command in fastboot mode (fastboot boot xxxxx.img)? Also, what error did u get when TWRP failed to boot?

Alin45 said:
Safetynet fails because of the unlocked bootloader (most probably). Being unable to use TWRP is strange. Did u use the correct command in fastboot mode (fastboot boot xxxxx.img)? Also, what error did u get when TWRP failed to boot?
Click to expand...
Click to collapse
Thanks for the reply, yep unlocked bl also could be a reason, I want to think reasonably now
No error when booting twrp, just a black screen, tried to press power button or vol buttons and swipe on screen to unlock (even tho nothing appears) and its still a black screen.
Ill post on alphatwrp, maybe it doesn't support miui 12.5.1 firmware.

Ghostface009 said:
Thanks for the reply, yep unlocked bl also could be a reason, I want to think reasonably now
No error when booting twrp, just a black screen, tried to press power button or vol buttons and swipe on screen to unlock (even tho nothing appears) and its still a black screen.
Ill post on alphatwrp, maybe it doesn't support miui 12.5.1 firmware.
Click to expand...
Click to collapse
Strange....TWRP works fine with my xiaomi.eu weekly ROM (which is 12.5.x version), so I guess this isn't the problem. Seems ur issue is over my knowledge, so....I give up lol

Alin45 said:
Strange....TWRP works fine with my xiaomi.eu weekly ROM (which is 12.5.x version), so I guess this isn't the problem. Seems ur issue is over my knowledge, so....I give up lol
Click to expand...
Click to collapse
Maybe due to the difference between global and eu roms
Ik you gave all you can but what would you suggest to do for my situation in order to root this phone and pass safetynet again?

have you double checked it's not a corrupt twrp img, and that you are using the '2' version of twrp? (there's two floating around) from here

Download the TWRP again.
Follow the guide with pictures: https://forum.xda-developers.com/t/4288121/post-85137963
Do Clean Flash custom ROMs steps up to step 13. Ignore step 8, 9 and the flash part of 12.
If this way still can't get you TWRP, then you might want to try latest MIUI by Xiaomi.eu. Read somewhere it has built in TWRP, so once flashed, you have TWRP. Verify yourself by reading in other posts though.
Remember
EEA (official) is different from Xiaomi.eu (custom ROM)
Click to expand...
Click to collapse

reg66 said:
have you double checked it's not a corrupt twrp img, and that you are using the '2' version of twrp? (there's two floating around) from here
Click to expand...
Click to collapse
yep, the one I used was '2' version. I double checked for corruption and downloaded the same twrp again with same result :/

pl1992aw said:
Do Clean Flash custom ROMs
Click to expand...
Click to collapse
So my only way to get magisk again is flashing custom roms? it is how it is? :/

Cant install last version of Magisk 26.1 on my phone

When im try to download and install Magisk 26.1 on my phone nothing happend then when i close Magisk and i open again i receive this message : "Update to the full version of Magisk Manager to complete the installation. Do you want to proceed with the download and instrallation?" then i press ok and nothing happend....any tip?

roberto_1986 said:
When im try to download and install Magisk 26.1 on my phone nothing happend then when i close Magisk and i open again i receive this message : "Update to the full version of Magisk Manager to complete the installation. Do you want to proceed with the download and instrallation?" then i press ok and nothing happend....any tip?
Click to expand...
Click to collapse
It seems Magisk can´t redirect to your custom recovery. If your recovery can admit flash the latest Magisk apk as a zip, you can install it directly from there.

SubwayChamp said:
It seems Magisk can´t redirect to your custom recovery. If your recovery can admit flash the latest Magisk apk as a zip, you can install it directly from there.
Click to expand...
Click to collapse
Hi and ty for answer!
Im using custom recovery LR TWRP and i dont know if i can flash from there anyway i never had issue by updating magisk!
i saw other ppl with my same problem and seems like i can fix by unROOT and then install last magisk update 26.1 from zero!
Now im busy and cant unROOT my phone but tomorrow i will doing a fresh install and i let u know if all was good ty!!!

roberto_1986 said:
Hi and ty for answer!
Im using custom recovery LR TWRP and i dont know if i can flash from there anyway i never had issue by updating magisk!
i saw other ppl with my same problem and seems like i can fix by unROOT and then install last magisk update 26.1 from zero!
Now im busy and cant unROOT my phone but tomorrow i will doing a fresh install and i let u know if all was good ty!!!
Click to expand...
Click to collapse
Just to add more on this, waiting for your feedback, it seems to me, not an issue with Magisk itself, but with the inability of the device to be sent to recovery using scripts (Magisk is updated using recovery scripts, not on-the-go), versus the ability to boot to recovery using hardware buttons.

SubwayChamp said:
Just to add more on this, waiting for your feedback, it seems to me, not an issue with Magisk itself, but with the inability of the device to be sent to recovery using scripts (Magisk is updated using recovery scripts, not on-the-go), versus the ability to boot to recovery using hardware buttons.
Click to expand...
Click to collapse
Hi im back!
I did fresh install and i was able to install last magisk 26.1 BUT i received this problem:
{
"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"
}
Then i installed SafetyNet 2.4.0 and both basic integrity and CTS passed BUT everytime i open Magisk i receive the same messages from the first screenshot then i flashed again from magisk last update AGAIN and now seens like all fine...
what caused this problem? im really fixed??? ty so much for your support!!!

roberto_1986 said:
Hi im back!
I did fresh install and i was able to install last magisk 26.1 BUT i received this problem:
View attachment 5891073
View attachment 5891075
Then i installed SafetyNet 2.4.0 and both basic integrity and CTS passed BUT everytime i open Magisk i receive the same messages from the first screenshot then i flashed again from magisk last update AGAIN and now seens like all fine...
what caused this problem? im really fixed??? ty so much for your support!!!
Click to expand...
Click to collapse
Like device can´t sent to recovery, then no way to do it manually, because it´ll pass first for the off state, the script will be lost, probably, flashing first the app, and then flashing the zip through the recovery it is fine.
Anyway, TBH, not updating, atleast for now, won´t suppose a non-go.

roberto_1986 said:
Hi im back!
I did fresh install and i was able to install last magisk 26.1 BUT i received this problem:
View attachment 5891073
View attachment 5891075
Then i installed SafetyNet 2.4.0 and both basic integrity and CTS passed BUT everytime i open Magisk i receive the same messages from the first screenshot then i flashed again from magisk last update AGAIN and now seens like all fine...
what caused this problem? im really fixed??? ty so much for your support!!!
Click to expand...
Click to collapse
Ok > Direct install > "Let's go"

SubwayChamp said:
Like device can´t sent to recovery, then no way to do it manually, because it´ll pass first for the off state, the script will be lost, probably, flashing first the app, and then flashing the zip through the recovery it is fine.
Anyway, TBH, not updating, atleast for now, won´t suppose a non-go.
Click to expand...
Click to collapse
OK so u think its not worth update to 26.1 because there is nothing of relevant yet?
How about Madisk delta instead?
When i install recovery LR TWRP 3.3.1 - 1210 i can ROOT directly from there and its auto install Magisk v20.0.
Ty again for your support!!!

roberto_1986 said:
OK so u think its not worth update to 26.1 because there is nothing of relevant yet?
Click to expand...
Click to collapse
Probably, but what I´m saying is that you won´t have issues if you don´t update, only that annoying message.
roberto_1986 said:
How about Madisk delta instead?
Click to expand...
Click to collapse
Magisk is not the culprit.
roberto_1986 said:
When i install recovery LR TWRP 3.3.1 - 1210 i can ROOT directly from there and its auto install Magisk v20.0.
Ty again for your support!!!
Click to expand...
Click to collapse
I can´t remember what version I was using when succesfully updated Magisk, but, I couldn´t, the same as you, with other version.
The whole issue is that device can´t go directly to the recovery, adb reboot recovery is executed silently, but device can´t reach recovery, all resides in the recovery, try a different recovery, maybe OFR, if you care, and with the same Magisk, and you´ll see that you can.