Database Info

Pixel 3 - Magisk keeps failing to detect it's self

Let me clarify -
Sometimes, seemingly randomly the Magisk manager app reports that Magisk is not installed, While all of my root apps still function fine. But, annoyingly, any apps that detect root.. can now detect root, because magisk hide is not working either. but then if i kill the app and relaunch it sometimes it will report that magisk is installed, sometimes it takes a reboot to get it to detect, sometimes i just plum can't get it to detect no matter what i do. It's like my system and magisk are fighting each other for control of root. I've tried searching for someone else who's experienced this, but to no avail. is there anything anyone can recommend to try?
very big image said:
{
"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"
}
Click to expand...
Click to collapse

Have you tried reflashing factory boot image and doing twrp and magisk from scratch?

Indeed I have.

When did this start happening? After a recent update? Is this your first time rooting the device? More info on your setup would be helpful.
Some steps to try:
Temp boot to TWRP image
Flash latest Canary Magisk Uninstaller
Reboot to System
Temp boot back to TWRP img
Flash latest Canary Magisk Installer
Reboot to System
Install latest Canary Magisk Manager (if not there after Installer flash)?
See if that solves the issue?
I have used this process during my factory updates and it's worked fairly well thus far. I have no kernels installed nor do i have TWRP installed.

update to magisk 22 bootloop problem

Hello,
I have a Galaxy S7 SM-G930FD and It started freezing about 2 months ago.
after taking it to the service for repair they said the Hard is faulty and said they have to change the whole mainboard which they did and it started working again (different IMEI and custom ROM was installed by the service)
As I was going to start installing apps I noticed that the Magisk App is giving me a notification to update it to the latest v22. not knowing that it is a root App I proceeded to update it through the App and BOOM! Bootloops.
I have a backup of the partitions after the Bootloop started to happen with the TWRP.
Things I have tried:
1- Flashing the ROM with the stock from with odin. after flashing it and booting for the first time it goes into the android system upgrade modes then a lengthy erase and then reboots into "No command" blue screen with the yellow exclamation mark. by pressing POWER+VOL UP I see this log:
{
"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"
}
and then after almost 30 seconds, it reboots and this process happens again.
2- I tried installing TWRP again and restoring from the backup I had and wiping/erasing again thinking this could be because of a bad Magisk Update. it didn't work either. after rebooting it's stuck on the first boot Samsung logo with no reboots.
trying to uninstall Magisk with the uninstaller zips didn't work as well and they reported that Magisk is not installed.
I don't mind if the ROM is not stock, however, that is my preference. what can I do to get it to boot again?
Rooting is not a problem as the Knox bit is already set.

Solved it.
The Magisk App had patched the Boot something and it seemed even repartitioning with Odin and erase couldn't get past that. I installed the latest v22 version using TWRP and it finally booted!

Question The system cannot be updated

T-mobile version! After the phone is rooted! Click update and download in the system, then insert an empty slot in magisk, restart, and check the system version number, which is still 11.2.2..2! The system update still prompts 11.2.3.3 update! Unable to update the system now! Flashing back to boot.img without a patch still cannot be updated
{
"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"
}

Your probably gonna have to do a complete uninstall of magisk. Reinstall original boot image then take update . Reflash patched boot image of update to regain root. Just my thoughts.

I had to completely re-lock my bootloader and factory reset to be able to take the update. Make sure your boot.img is stock before doing this though, as having a modified one will render the system unable to boot (you can still access the bootloader, though).

mattie_49 said:
Your probably gonna have to do a complete uninstall of magisk. Reinstall original boot image then take update . Reflash patched boot image of update to regain root. Just my thoughts.
Click to expand...
Click to collapse
Thank you, I have been flashing the boot image to A, now I switch to B, and then flash again. It worked. But the download was more than half, and there was an error

OK！I flashed my phone to the international version based on this GUIDE,Guide reference . and then updated it to EU 11.2.3.3, everything worked normally

And that worked for the TMO 1+ 9?

Yes, I updated it to EU

Can't boot system and/or TWRP running on SM-A12F

I decided to root my phone with running latest version of SM-A12F, but ended of the following:
System: One UI 3.1
Currently Running about
Android Security Patch Level: October 1, 2021
Additional: Unlocked OEM Unlock(Grayed Out), Device Unlocked
Attempt 1. After flashing twrp(many times, but different who bulid twrp), can't boot system. So i decided to flash stock recovery and goes running normal.
Attempt 1b: I flashed multidisabler with twrp but can't boot system and restart freqnently.
Attempt 2: After flashing twrp and vbmeta, booting to TWRP successfully but can't boot System.
Attempt 3: The basic solution about rooting with magisk was successfully but after an hour Google Services got often stopped and Google Apps too. I decided to restart and got warning message about "Security Error: only official BOOT to solve the solution", so i decided to roll back to reflash a new firmware.

Did you fix this issue now cause i only want to flash twrp and prerooted rom not planning to flash lineage build

ジャイッコ said:
Did you fix this issue now cause i only want to flash twrp and prerooted rom not planning to flash lineage build
Click to expand...
Click to collapse
As your expected same question. I did it once and successfully.
Kernel: Psywizz
Root: Magisk
TWRP: edward0181's work
{
"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"
}

What are steps of installing twrp mate including physwiz kernel want to follow ur guide...thanks

Question Rooting attempt ended up with no playstore

I recently attempted to root my op9 following the guide in the pro forum after booting a rooted bootloader and installing via magisk everything seemed fine, I actually use my phone a lot for contactless payments so I needed to pass safetynet and this is where everything went wrong, I followed the magiskhide guide and hid from gms and proceeded to reboot.
When my phone booted up I had lost the playstore and my phone was no longer rooted to make things worse safteynet failure.
In the end I had to flash a standard bootloader into both slots and relock my bootloader just to get stock working correctly.
What could I have possibly done wrong to lose playstore?

Fixed the issue partially following the rooting guide on the pro forum
[GUIDE] [Magisk] [Unlock / ROOT / Keep Root] OOS 13.1.0.500
Different variants of Magisk that are available for use : Magisk Variant Stable / Beta / Canary Release Official Android / OOS OOS 11 and above Maintainer topjohnwu Project Link GitHub Zygisk No...
forum.xda-developers.com
I restarted the process after I factory reset and updated to LE2113_11_F.72
extracted the boot.img and patched it and finally got everything working...
it's been a while since I've rooted anything and the whole ecosystem has changed but I still managed the basics My only thought is I used the wrong bootloader.
{
"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"
}