Related
Title is self explanatory. Running stock pie. I'm tired let me know if additional info is needed. Not much to add.
billard412 said:
Title is self explanatory. Running stock pie. I'm tired let me know if additional info is needed. Not much to add.
Click to expand...
Click to collapse
Magisk 19 should fix Safetynet issues. If not, use Safetynet patch Magisk module
billard412 said:
Title is self explanatory. Running stock pie. I'm tired let me know if additional info is needed. Not much to add.
Click to expand...
Click to collapse
I can confirm that on my Pixel with newest android, and on my wife's moto g6, that magisk is fully working. both have pie now. both pass safetynet just fine.
HueyT said:
Magisk 19 should fix Safetynet issues. If not, use Safetynet patch Magisk module
Click to expand...
Click to collapse
tried everything. Was running magisk 19 when this occurred. Tried multiple versions of magisk and MM. Tried uninstalling and reinstalling. Tried the safetynet fix. Tried reinstalling the OS and other important partitions with fastboot (everything except bootloaders and a data wipe). And not only did I not fix the safetynet issue I'm stuck with no root at all now (magisk is not installed). This is crazy.
billard412 said:
tried everything. Was running magisk 19 when this occurred. Tried multiple versions of magisk and MM. Tried uninstalling and reinstalling. Tried the safetynet fix. Tried reinstalling the OS and other important partitions with fastboot (everything except bootloaders and a data wipe). And not only did I not fix the safetynet issue I'm stuck with no root at all now (magisk is not installed). This is crazy.
Click to expand...
Click to collapse
Have you tried rooting/magisk the old way? By flashing the no verity boot.img? I posted one a page back or so for the newest pie build. Works great from what I can see.
If it were me, and this is assuming you havent already tried this. I would reflash back to stock and make sure to erase userdata in the process. Then flash twrp and the no verity boot.img. Format data and do a factory reset. When that is done go back into twrp and flash magisk. That has worked fine for me on xt1925-6 variant. I actually just the other day followed the old root instructions and they worked fine for pie as well.
I should mention that to flash the image I extract it into the adb/fastboot dir and run the flash_all.bat in elevated CMD window. I do let it do everything including wipe userdata. Not sure if thats important. But it sounded like you were excluding some of the flashing in your process.
I have installed the latest pie stable on my op 3t. However it would never boot when installing with Magisk.
So for now I have installed it without Magisk and got it to work ok. However now I'm having same problem installing Magisk.
I can install and uninstall it from twrp latest, however when it's installed, it is just stuck on the initial screen with oneplus logo. And never makes it to the circle/dots screen.
I tried using 19. 2, 19.0 Magisk and 18.1.
Is there any logs I can pull or did anyone else have this issue?
Are there any other safe root solutions to try instead?
Any help would be appreciated
anykiel91 said:
I have installed the latest pie stable on my op 3t. However it would never boot when installing with Magisk.
So for now I have installed it without Magisk and got it to work ok. However now I'm having same problem installing Magisk.
I can install and uninstall it from twrp latest, however when it's installed, it is just stuck on the initial screen with oneplus logo. And never makes it to the circle/dots screen.
I tried using 19. 2, 19.0 Magisk and 18.1.
Is there any logs I can pull or did anyone else have this issue?
Are there any other safe root solutions to try instead?
Any help would be appreciated
Click to expand...
Click to collapse
I always flash Magisk BEFORE the first boot. Also no custom kernels, especially not AFTER Magisk flash.
Is this what you did as well?
I couldn't get it to boot up before firstboot. So I went with normal nonroot flash so I could use the phone.
I figured it would not matter if I installed Magisk later.
I might try to reflash everything over again
ast00 said:
I always flash Magisk BEFORE the first boot. Also no custom kernels, especially not AFTER Magisk flash.
Is this what you did as well?
Click to expand...
Click to collapse
topjohnwu says that you flash custom kernel after flashing Magisk
Immortalis said:
topjohnwu says that you flash custom kernel after flashing Magisk
Click to expand...
Click to collapse
Never had this problem until today. So I did some testing.
Magisk 19.1 causes it to get stuck at the OP logo.
I flashed uninstaller, reflashed the ROM, flashed Magisk 19.2 and it worked.
Are you using the 19.2 zip?
ast00 said:
Never had this problem until today. So I did some testing.
Magisk 19.1 causes it to get stuck at the OP logo.
I flashed uninstaller, reflashed the ROM, flashed Magisk 19.2 and it worked.
Are you using the 19.2 zip?
Click to expand...
Click to collapse
Yes, I had problems with 19.1 too, that the phone sometimes (if not always) would boot itself into fastboot mode instead of system, so at that time I moved temporarily to canary builds
I used this zip instead and it worked. Not sure what's different but I'm good now
https://forum.xda-developers.com/oneplus-3t/development/rom-theone3tos-v1-0-t3730932
Hi. I have recently rooted my new pixel 4 with magisk and was installing Riru Edexposed to try and get fingerface working. Unfortunately during installing edexposed my phone got stuck in a bootloop. Because the pixel 4 doesn't have a custom recovery I don't know how to flash the exposed uninstaller zip or even to just access my files. Any help would be much appreciated. Thank you.
Have a look in the apps/themes section.
tulsadiver offers a boot image which removes all magisk modules....
pa.pn2 said:
Have a look in the apps/themes section.
tulsadiver offers a boot image which removes all magisk modules....
Click to expand...
Click to collapse
Is there really no Custom recovery or TWRP for Pixel 4's even tho Root works & ontop of that how're you supposed to flash disable dm-verity if you don't have a flashing ROM installed?
Nightshadex543 said:
Is there really no Custom recovery or TWRP for Pixel 4's even tho Root works & ontop of that how're you supposed to flash disable dm-verity if you don't have a flashing ROM installed?
Click to expand...
Click to collapse
No, no custom recovery yet. I thought it was gonna be a pain but I was able to flash DirtyUnicorns ROM without any issues.
Prey521 said:
No, no custom recovery yet. I thought it was gonna be a pain but I was able to flash DirtyUnicorns ROM without any issues.
Click to expand...
Click to collapse
Goddamnit thanks. TWRP 3.3.1 or Blu-spark don't work? So, that means computer based flashes. That's unfortunate, I'd rather have something installed incase of a Bootloop after attempting root. Makes things less problematic.
Thanks again.
Nightshadex543 said:
Goddamnit thanks. TWRP 3.3.1 or Blu-spark don't work? So, that means computer based flashes. That's unfortunate, I'd rather have something installed incase of a Bootloop after attempting root. Makes things less problematic.
Thanks again.
Click to expand...
Click to collapse
Nope, just fastboot and adb commands for now.
Looks like magisk will add a "module disabler mode" in the next updates when the phone will be rebooted in safe mode.
For now the only thing to do is to flash the custom boot image from tulsadiver that enable core mode only.
I heard about another alternative, from didgeridoohan magisk wiki, but never tried if it works in this case:
Since Magisk v19.4, there's an adb command that can be used to uninstall all modules on your device.
If the device is bootlooping or simply haning on the boot animation you have a good chance that you can use this command to get up and running again.
Hook your device up to a computer (or other device you can run adb from) and execute the following command:
adb wait-for-device shell magisk --remove-modules
After that you can start your device and as soon as adb is available the command will activate, the modules will be removed and the device will reboot. There's of course a chance that the troublesome module has done something that the command can't remove...
Click to expand...
Click to collapse
Just checked out both of those contributors. Good stuff, appreciated.
Phone Model no : Samsung Galaxy S6 / SM-G920F
Security patch date: 01.10.2017
Android version: 7.0
Root status: Yes
Hey guys,
I rooted my phone several weeks ago for the first time via odin and everything went fine. I installed TWRP and Magisk and everything worked out.
Today I was trying to update Magisk from v20.x to v21.x with the inapp option, but now im stuck in a bootloop to download mode, screen says "Downloading... do not turn off target".
Even if I turn the phone off with Power + Home + Vol Down its just restarting right away and getting stuck in the same screen again.
Im still able to enter TWRP Recovery, but I dont know what to do to end the download mode problem when trying to start the phone.
I actually dont know/understand much about that stuff, so I dont know which other info I need to provide.
Is there something I could do without going through the whole flash/root process again?
should i try to delete magisk and install it again? if yes, how do i do it?
Help would be appreciated.
n00btuber said:
Phone Model no : Samsung Galaxy S6 / SM-G920F
Security patch date: 01.10.2017
Android version: 7.0
Root status: Yes
Hey guys,
I rooted my phone several weeks ago for the first time via odin and everything went fine. I installed TWRP and Magisk and everything worked out.
Today I was trying to update Magisk from v20.x to v21.x with the inapp option, but now im stuck in a bootloop to download mode, screen says "Downloading... do not turn off target".
Even if I turn the phone off with Power + Home + Vol Down its just resarting right away and getting stuck in the same screen again.
Im still able to enter TWRP Recovery, but I dont know what to do to end the downloading problem when trying to start the phone.
I actually dont know/understand much about that stuff, so I dont know which other info I need to provide.
Is there something I could do without going through the whole flash/root process again?
should i try to delete magisk and install it again? if yes, how do i do it?
Help would be appreciated.
Click to expand...
Click to collapse
I don't know much about your device but if you can enter TWRP, it's not that bad. First what you can try is to download Magisk uninstaller and flash it in TWRP from USB. However, I don't know what can you do to update Magisk safely. Would be best if you can check your device forum or ask the question there
Lord Sithek said:
I don't know much about your device but if you can enter TWRP, it's not that bad. First what you can try is to download Magisk uninstaller and flash it in TWRP from USB. However, I don't know what can you do to update Magisk safely. Would be best if you can check your device forum or ask the question there
Click to expand...
Click to collapse
Looked like my device forum is pretty dead, which is why I asked the question here again. Thanks for the fast respone
Its probably not possible to just install a Magisk version again and overwrite the current one, probably need to uninstall first and then install it again?
There is a Magisk Module Uninstaller and a Magisk Uninstaller. Are those different things or just the same?
How to Uninstall Magisk Module Using TWRP Recovery | MagiskRoot
Uninstall Magisk Module using TWRP Recovery or Offline whenever you stuck into bootloop. Magisk Module Uninstaller and Magisk Manager for Recovery methods.
magiskroot.net
How to Uninstall Magisk From Android [2 Easiest Method]
Are you facing issues with Magisk? You can uninstall magisk from your phone with these simple and easy steps.
magiskmanager.com
Because the 2nd guide says in the end
Keep in Mind – Whenever you use TWRP as a method to uninstall Magisk, it is imperative to flash the Magisk Module Uninstaller Zip onto your device.
Does this mean I need to do the magisk module one first?
@n00btuber Do not trust those websites. They're in no way official and are just trying to get adc revenue from Magisk's popularity. If you're really unlucky they'll also provide you with malicious zips...
Only download stuff from John's GitHub:
https://github.com/topjohnwu/Magisk
If you need to uninstall Magisk use the uninstall zips from the above linked Github repo, and if you need to uninstall modules (but those will also be removed by the Magisk uninstaller) you can do that directly from TWRP:
https://www.didgeridoohan.com/magisk/Magisk#hn_Uninstalldeletedisable_modules_from_recovery
A lot of times you can just flash another Magisk version over your installed one, but there are times where you do need to uninstall first. Since you have TWRP it can't really hurt to just try flashing whatever Magisk zip you want and it it doesn't work you can just use the uninstaller first.
One other thing to try would be the Canary release, mainly to see if you're affected by any bugs that is present in the current stable release but has been fixed upstream. You'll find the Canary app in the same Github link above.
Didgeridoohan said:
@n00btuber Do not trust those websites. They're in no way official and are just trying to get adc revenue from Magisk's popularity. If you're really unlucky they'll also provide you with malicious zips...
Only download stuff from John's GitHub:
https://github.com/topjohnwu/Magisk
Click to expand...
Click to collapse
Ok.
Was trying to use the uninstaller from his GitHub.
Trying to flash it leads to
"Updater process ended with ERROR:1
Error installing Zip file .....
Updating partition details"
So what to do now?
Trying to just flash any Magisk version to overwrite the current one leads to the same result.
I think it says Unsupported/Unknown image format
Your TWRP might be bugged/incompatible. I'd reflash your stock boot image and then patch the file manually (you'll find the instructions for that on GitHub as well).
Didgeridoohan said:
Your TWRP might be bugged/incompatible.
Click to expand...
Click to collapse
But TWRP worked fine when installing magisk the first time, I even tried the same zip folder I used to install it back then, but it wont work anymore.
Didgeridoohan said:
I'd reflash your stock boot image and then patch the file manually (you'll find the instructions for that on GitHub as well).
Click to expand...
Click to collapse
However, whats my stock boot image and how to reflash it? Cant find a guide for that on GitHub.
Would a Factory Reset wipe all Magisk stuff and my TWRP Partition as well?
Does anyone know what is going on between Magisk and Google? It seems Google has removed Magisk Manager from the Play Store AGAIN! What's more, I downloaded and installed the apk but when I try to use it to install the latest Magisk the install fails. Tried installing the Magisk zip via TWRP, and while it doesn't show any errors, I still don't have root.
Ok I really need some more help @Didgeridoohan
Meanwhile I tried to reinstall TWRP from within TWRP. There was no error so I think it should have worked, but didnt solve the problem.
As soon as I try to boot the system it directly boots download mode and gets stuck in it. The volume buttons wont work or do anything as they are supposed in download mode.
Im still able to get into TWRP, but I still dont know what to do to stop this crashed download mode that starts over and over again.
When trying to flash the magisk uninstall it states "cannot access /data", when trying to flash a magisk installer it states "unsupported/unknown image format"
I dont care about Magisk right now though, I can root and install magisk again as soon as im able to clear the download mode problem. I was just trying this because trying to update magisk from within magisk manager has caused this download mode problem to appear.
Just tell me please how to fix that or how to factory reset my phone so it is able to boot regular again.
Thank you
n00btuber said:
Ok I really need some more help @Didgeridoohan
Meanwhile I tried to reinstall TWRP from within TWRP. There was no error so I think it should have worked, but didnt solve the problem.
As soon as I try to boot the system it directly boots download mode and gets stuck in it. The volume buttons wont work or do anything as they are supposed in download mode.
Im still able to get into TWRP, but I still dont know what to do to stop this crashed download mode that starts over and over again.
When trying to flash the magisk uninstall it states "cannot access /data", when trying to flash a magisk installer it states "unsupported/unknown image format"
I dont care about Magisk right now though, I can root and install magisk again as soon as im able to clear the download mode problem. I was just trying this because trying to update magisk from within magisk manager has caused this download mode problem to appear.
Just tell me please how to fix that or how to factory reset my phone so it is able to boot regular again.
Thank you
Click to expand...
Click to collapse
Sounds to me like you need to reflash your ROM, not TWRP. According to your OP, you're running Android 7, but it doesn't say if it is stock or a custom ROM.. If it is stock, then use Frija.exe to download the ROM and then flash th AP, BL and HOME_CSC md5 files with Odin. If it is a custom ROM, use TWRP to flash the ROM and gapps. DO NOT try to flash Magisk. Right now there seems to be a problem with Google disabling Magisk. Wait till it is resolved before attempting to get root.
@n00btuber Dirty flashing your ROM is most likely the way to go, just like described above.
But @lewmur, what do you mean by "Google disabling Magisk"? If you're talking about SafetyNet there are ways around that (and it doesn't affect root)...
Didgeridoohan said:
@n00btuber Dirty flashing your ROM is most likely the way to go, just like described above.
But @lewmur, what do you mean by "Google disabling Magisk"? If you're talking about SafetyNet there are ways around that (and it doesn't affect root)...
Click to expand...
Click to collapse
I not talking about safety net. Look in Play Store for Magisk Manager. It is no longer there. And even if you download and install the apk, it won't install Magisk. Flashing Magisk from TWRP doesn't give root privileges. This just happened yesterday.
lewmur said:
I not talking about safety net. Look in Play Store for Magisk Manager. It is no longer there. And even if you download and install the apk, it won't install Magisk. Flashing Magisk from TWRP doesn't give root privileges. This just happened yesterday.
Click to expand...
Click to collapse
The Magisk Manager hasn't been on the Play Store for years... Edit: reference - https://forum.xda-developers.com/t/magisk-the-magic-mask-for-android.3473445/post-72508849
Nothing of what you describe has anything to do with Google "disabling Magisk".
Didgeridoohan said:
The Magisk Manager hasn't been on the Play Store for years... Edit: reference - https://forum.xda-developers.com/t/magisk-the-magic-mask-for-android.3473445/post-72508849
Nothing of what you describe has anything to do with Google "disabling Magisk".
Click to expand...
Click to collapse
That 's my mistake. Play Store would put up a lot of "Magisk Manager" stuff, but I never really tried any of it because flashing Magisk would give me the Manager. But even that "stuff" no longer shows up.
Butt Magisk Manager still won't install Magisk. It will download the zip file, but when it attemps to install it, it get an error saying Unsupported/Unknown image format. If I flash it from TWRP, and then open Magisk Manager, it still says N/A under Installed for Magisk.
lewmur said:
Then why won't Magisk Manager install Magisk. It will download the zip file, but when it attemps to install it, it get an error saying Unsupported/Unknown image format. If I flash it from TWRP, and then open Magisk Manager, it still says N/A under Installed for Magisk.
Click to expand...
Click to collapse
That will be an incompatibility between Magisk and your device and has nothing to do with Google (blame your OEM for doing weird stuff instead).
Thanks for the help guys, had to flash the ROM, now its working again.
What should i do/try/check when i have followed the install procedure (correctly and tried severel times) but my phone is not rooted?
LineageOS 20.0, Magisk 23.0
Use magisk 25.2? Did you direct install?
Yeah, well. I need magiks-hide so 23.0 is the latest i can use. Not sure what direct install means, i downloaded the boot.img, install magisk into it using the app, and then did the fastboot flash-thingy.
revt3949 said:
Yeah, well. I need magiks-hide so 23.0 is the latest i can use. Not sure what direct install means, i downloaded the boot.img, install magisk into it using the app, and then did the fastboot flash-thingy.
Click to expand...
Click to collapse
Use magisk delta. It has magisk hide, and a lot more on the latest magisk.
Great, where can i find this magisk delta?
revt3949 said:
Great, where can i find this magisk delta?
Click to expand...
Click to collapse
Where is this?
Yeah well, that does not look like it is matured software: no explaination what magisk delta is, where magisk delta is different from normal magisk, no details on how to install, etc.
Not sure that i want to brick my phone with this tool.
revt3949 said:
Yeah well, that does not look like it is matured software: no explaination what magisk delta is, where magisk delta is different from normal magisk, no details on how to install, etc.
Not sure that i want to brick my phone with this tool.
Click to expand...
Click to collapse
Lmao. Look at its Xda thread. Much better alternative. Has material you, bootloops protection, system installation, different ways to load zygote, sulist, magisk hid, etc,etc. Its like magisk on steroids, while being twice as reliable.
revt3949 said:
Yeah well, that does not look like it is matured software: no explaination what magisk delta is, where magisk delta is different from normal magisk, no details on how to install, etc.
Not sure that i want to brick my phone with this tool.
Click to expand...
Click to collapse
You install same way.
Arealhooman said:
You install same way.
Click to expand...
Click to collapse
How do you mean "the same way"?
I mean with magisk, i unzip the boot.img, patch it using the magisk app and then fastboot flash it on the device. But sure i can not use the magisk app to patch Magisk Delta into the boot.img, right?
So, is there a magisk delta app somewhere that does the patching?
revt3949 said:
How do you mean "the same way"?
I mean with magisk, i unzip the boot.img, patch it using the magisk app and then fastboot flash it on the device. But sure i can not use the magisk app to patch Magisk Delta into the boot.img, right?
So, is there a magisk delta app somewhere that does the patching?
Click to expand...
Click to collapse
Yes. On the GitHub. You can also flash thru twrp. Use previous links I sent.
Just install the magisk delta app and got it all working. The MD app even recognised the existing magisk kernel and offered to do a direct install.
Very happy and thank you for all the support. Will make a donation soon.
lol tried the magisk delta and flashed the .img but in boot loop now.on moto g play 2023.. so maybe no support for that yet.. reflashed original patched boot.img and back
Same here. Direct installed Magisk Delta. But after restart phone become non rooted, unable to prompt magisk. But only magisk delta able to hide the root from banking apps. It is quite irritating. Did you figured anyway on this issue?
Hey Victorlmy i had to flash the original magisk patched file back to get it to boot again... hold the volume down and power buttons till you get it to boot to bootloader and reflash.. still tring to figure out why it didnt boot