Related
Hi, I'm using Magisk on my LG G2 with RessurectionRemix 5.7 and am looking to update to the Nougat version 5.8. I want to start clean, so will wipe system before the update, but will I have to flash Magisk again after that? What are the steps here, flash the ROM + gapps, unroot, flash Magisk?
de.er said:
Hi, I'm using Magisk on my LG G2 with RessurectionRemix 5.7 and am looking to update to the Nougat version 5.8. I want to start clean, so will wipe system before the update, but will I have to flash Magisk again after that? What are the steps here, flash the ROM + gapps, unroot, flash Magisk?
Click to expand...
Click to collapse
Yep that should be about it. To be sure try safetynet after unrooting and after magisk
guessingagain said:
Yep that should be about it. To be sure try safetynet after unrooting and after magisk
Click to expand...
Click to collapse
Flashed the ROM and magisk last night, so far so good, safetynet passes I went for a clean install this time, but if I was to dirty flash an update now would magisk survive that?
de.er said:
Flashed the ROM and magisk last night, so far so good, safetynet passes I went for a clean install this time, but if I was to dirty flash an update now would magisk survive that?
Click to expand...
Click to collapse
No because Magisk modifies the boot image, which gets overwritten with a new one when you flash a ROM, clean or dirty. So you'll need to flash Magisk again.
The Flash said:
No because Magisk modifies the boot image, which gets overwritten with a new one when you flash a ROM, clean or dirty. So you'll need to flash Magisk again.
Click to expand...
Click to collapse
Was suspecting this might be the case, thanks for clarifying this. At least I know all the steps now, should be only getting more familiar with every flash
de.er said:
Flashed the ROM and magisk last night, so far so good, safetynet passes I went for a clean install this time, but if I was to dirty flash an update now would magisk survive that?
Click to expand...
Click to collapse
afaik Resurrection Remix has addon.d (check if /system/addon.d exists)
you can test this https://github.com/osm0sis/GN-Synap...mdisk/res/synapse/scripts/999-customkernel.sh or modify it to flash magisk instead of the backup (in case you got an updated kernel)
crusader727 said:
afaik Resurrection Remix has addon.d (check if /system/addon.d exists)
you can test this https://github.com/osm0sis/GN-Synap...mdisk/res/synapse/scripts/999-customkernel.sh or modify it to flash magisk instead of the backup (in case you got an updated kernel)
Click to expand...
Click to collapse
wow, that'd be great if it worked. I can confirm addon.d exists, I might try this next time. Do I just put the script into addon.d and flash ROM?
de.er said:
Do I just put the script into addon.d and flash ROM?
Click to expand...
Click to collapse
yes :good:
//btw:
yesterday I posted a feature request to add this to Magisk Manager: https://github.com/topjohnwu/MagiskManager/issues/72
crusader727 said:
yes :good:
//btw:
yesterday I posted a feature request to add this to Magisk Manager: https://github.com/topjohnwu/MagiskManager/issues/72
Click to expand...
Click to collapse
Flashed an RR update to 5.8.1 over the weekend and it went smoother than I expected, to be honest. Didn't use the script you mentioned in the end, just flashed the new ROM, gapps, unsu.zip, magisk and phh's su in TWRP and rebooted. Simple.
de.er said:
Flashed an RR update to 5.8.1 over the weekend and it went smoother than I expected, to be honest. Didn't use the script you mentioned in the end, just flashed the new ROM, gapps, unsu.zip, magisk and phh's su in TWRP and rebooted. Simple.
Click to expand...
Click to collapse
Yes, of course the manual method works :good:
phh-SU was removed in Magisk v11 btw - root is now integrated (MagiskSU).
I still need to have phh's Superuser management app installed. And now on boot I get a notification that my SU binary is out of date. The transition here has been a bit rough.
sweenish said:
I still need to have phh's Superuser management app installed. And now on boot I get a notification that my SU binary is out of date. The transition here has been a bit rough.
Click to expand...
Click to collapse
Are you on about updating your ROM or magisk? Phh su app is required for magisk v10.2, you need to remove it if you're using magisk v11 or later
The Flash said:
No because Magisk modifies the boot image, which gets overwritten with a new one when you flash a ROM, clean or dirty. So you'll need to flash Magisk again.
Click to expand...
Click to collapse
In reference to this, does reflashing Magisk alter anything within Magisk? Namely and really the only thing that would come to mind is it downgrading the Manager app to whatever is in the installer and possibly resetting it settings.
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.
Hello I have questions if somebody success to root Android 11?
And if somebody have guide to to root how to install and flash magisk
oraned said:
Hello I have questions if somebody success to root Android 11?
And if somebody have guide to to root how to install and flash magisk
Click to expand...
Click to collapse
[Guide] Root Pixel 4 XL Android 11 (R)
Thanks
Homeboy76 said:
[Guide] Pixel 4 XL Android 11 (R)
Click to expand...
Click to collapse
Use the latest Canary Manager and install Canary Magisk 20424 or above by patching the boot image. Follow the guide in here... https://github.com/topjohnwu/Magisk
Lughnasadh said:
Use the latest Canary Manager and install Canary Magisk 20424 or above by patching the boot image. Follow the guide in here... https://github.com/topjohnwu/Magisk
Click to expand...
Click to collapse
Canary...just DLs an appdebug.apk. Have the latest magisk and does not boot past the bootloader.
---------- Post added at 04:28 PM ---------- Previous post was at 03:31 PM ----------
I got it working. So all rooted and ready to go on 11
uncheck Recovery Mode where i found this in magisk i cant found
Lughnasadh said:
Use the latest Canary Manager and install Canary Magisk 20424 or above by patching the boot image. Follow the guide in here... https://github.com/topjohnwu/Magisk
Click to expand...
Click to collapse
uncheck Recovery Mode where i found this in magisk i cant found
oraned said:
uncheck Recovery Mode where i found this in magisk i cant found
Click to expand...
Click to collapse
I believe he removed this option on devices with ramdisk because it wasn't needed. That would include this device.
Lughnasadh said:
Use the latest Canary Manager and install Canary Magisk 20424 or above by patching the boot image. Follow the guide in here... https://github.com/topjohnwu/Magisk
Click to expand...
Click to collapse
Opps!
Homeboy76 said:
Please correct me if I am wrong, but don't you use Canary Magisk Manager 20424 to patch the boot.img. Then you use Magisk 20-4.zip (stable)?
Click to expand...
Click to collapse
No. Use Canary Magisk (20424) to patch the stock boot image and then use fastboot to flash that patched boot image. No zips are involved.
Lughnasadh said:
No. Use Canary Magisk (20424) to patch the stock boot image and then use fastboot to flash that patched boot image. No zips are involved.
Click to expand...
Click to collapse
You are correct. I misread your your post. :cyclops:
Canary Magisk (20424) is this the same as magisk canary 20.4?
ok i found the latest canary 20404 and patched the boot img file but still wouldn't boot. i also noticed the original boot img file is 65,000 kb and the patched is 4,000kb so something is wrong i would assume.
kidhudi said:
Canary Magisk (20424) is this the same as magisk canary 20.4?
ok i found the latest canary 20404 and patched the boot img file but still wouldn't boot. i also noticed the original boot img file is 65,000 kb and the patched is 4,000kb so something is wrong i would assume.
Click to expand...
Click to collapse
Canary 20404?
Should be Magisk Canary Manager 20424.
Are you using the latest SDK Platform-tools r 30.0.4?
Thanks I will try that one when I get home. Yes just downloaded a fresh platform told yesterday. The thanks for the help. Much appreciated
kidhudi said:
Canary Magisk (20424) is this the same as magisk canary 20.4?
ok i found the latest canary 20404 and patched the boot img file but still wouldn't boot. i also noticed the original boot img file is 65,000 kb and the patched is 4,000kb so something is wrong i would assume.
Click to expand...
Click to collapse
The magisk_patched.img must be around 32.5MB.
Thanks i finally got it. i think it was because i was transferring the file over the usb cable something went wrong. i uploaded it to google drive then downloaded it to the PC and it all worked out.
weird thing is safteynet is passing with no magisk modules installed.
thanks guys
Anyone else the latest Magisk update causes Bootloop when installing modules?
use 24.1, is perfect
OK THANKS, I HOPE FUTURE UPDATES WILL WORK CORRECTLY ON THE DEVICE
a question: do u have repatched boot.img with new magisk version? you must do it
wetito said:
use 24.1, is perfect
Click to expand...
Click to collapse
I'm still using v23 .. just to be sure lol ! but now i know 24.1 is good thank you!
PonchoNz said:
Anyone else the latest Magisk update causes Bootloop when installing modules?
Click to expand...
Click to collapse
Use Magisk 24.3 and patch the boot file -> Flash the boot file in fastbootd
Done.
i have flashed 24.1 using fastboot. for 24.3 fastbiitd is necessary? i ask just i case in the future i will decide update to latest version
wetito said:
a question: do u have repatched boot.img with new magisk version? you must do it
Click to expand...
Click to collapse
Yep but update it by TWRP
nguadien said:
Use Magisk 24.3 and patch the boot file -> Flash the boot file in fastbootd
Click to expand...
Click to collapse
Done I did it too but when I install a Module called NFS Injector or Magnetar when I restart the device it gives bootloop
PonchoNz said:
Done I did it too but when I install a Module called NFS Injector or Magnetar when I restart the device it gives bootloop
Click to expand...
Click to collapse
Then the problem is the modules you installed, not "latest Magisk update" like you stated.
Not all modules work for all devices, each device reacts to modules very differently, so boot loop caused by modules should not be mistaken for the whole Magisk.
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