Anyone use the magisk bootloopsaver module with our phones? Wanted to make sure it wouldn't mess anything up before I installed it lol
Veid71 said:
Anyone use the magisk bootloopsaver module with our phones? Wanted to make sure it wouldn't mess anything up before I installed it lol
Click to expand...
Click to collapse
Using it on OOS11. Saved me when one of the recent Magisk Canary releases had conflicts with modules and caused bootloops, it's a Godsend.
Basically if you bootloop because of modules, the boot animation stays on for like a minute, then the device restarts with all modules disabled (except for the Magisk Bootloop Saver module). You will need to re-enable them manually afterwards (and subsequently rebuild substratum themes etc).
Fishawy said:
Using it on OOS11. Saved me when one of the recent Magisk Canary releases had conflicts with modules and caused bootloops, it's a Godsend.
Basically if you bootloop because of modules, the boot animation stays on for like a minute, then the device restarts with all modules disabled (except for the Magisk Bootloop Saver module). You will need to re-enable them manually afterwards (and subsequently rebuild substratum themes etc).
Click to expand...
Click to collapse
Awesome thanks man!
Magisk has this by default for a long time now. pressing down vol key on boot will boot into safe mode with all modules disabled
Try this.
JohnFawkes said:
Magisk has this by default for a long time now. pressing down vol key on boot will boot into safe mode with all modules disabled
Click to expand...
Click to collapse
True, but this module makes it a normal boot not into safe mode.
TheKnux said:
Try this.
Click to expand...
Click to collapse
Will it work on a12l?
Tazist said:
Will it work on A12l?
Click to expand...
Click to collapse
@Tazist Try it. Sorry, the xda app is ****ing stupid.
Does anyone have a fresh copy of this? I keep getting an unzip error. Is development dead?
Droid_Nut said:
Does anyone have a fresh copy of this? I keep getting an unzip error. Is development dead?
Click to expand...
Click to collapse
Why not use magisk delta this have a bootloop protect build in
Thank you, should I patch the boot image or not?
ChrisFeiveel84 said:
Why not use magisk delta this have a bootloop protect build in
Click to expand...
Click to collapse
Tell us more, is it a module, or a version of Magisk?
Droid_Nut said:
Thank you, should I patch the boot image or not?
Click to expand...
Click to collapse
For magsik delta ?
Droid_Nut said:
Tell us more, is it a module, or a version of Magisk?
Click to expand...
Click to collapse
Is a magsik version from huskydg with build in bootloop protect and magisk hide
So its a fork of Magisk. https://magiskzip.com/magisk-delta/
ChrisFeiveel84 said:
For magsik delta ?
Is a magsik version from huskydg with build in bootloop protect and magisk hide
Click to expand...
Click to collapse
Huskydg also made the bootloop module, so patch it for either?
Actually never mind I just patched it on 3 phones with no problem.
As far as Delta, the newest Lsposed requires Zygisk, so you might find that you will need that anyways as more modules go that route. Any ways, I will give Delta try some time.
ChrisFeiveel84 said:
For magsik delta ?
Is a magsik version from huskydg with build in bootloop protect and magisk hide
Click to expand...
Click to collapse
I installed Delta, can I now turn off the bootloop module?
Droid_Nut said:
I installed Delta, can I now turn off the bootloop module?
Click to expand...
Click to collapse
No then when you enable it on magsik this isnatlled this modul
Few days ago, magisk brought update. I updated and restarted. 1st restart was ok, but 2nd restart after updating youtube revanved module caused bootloop. I had to flash firmware in, data gone. Will this module really help me if it happens next time or i should use TWRP. TWRP is not available for my device BTW. I will try to build it as it's open source.
Related
So I rooted and I am having 2 issues.
1. When ever I boot I get a message stating my phone has internal problems?..
How do I fix/remove this message
2. When I chose magisk to test safety net it FC running 14.5 if I update magisk keeps FC won't even update..
How do i check for safety net?.
Thanks in advance.
egren58 said:
So I rooted and I am having 2 issues.
1. When ever I boot I get a message stating my phone has internal problems?..
How do I fix/remove this message
2. When I chose magisk to test safety net it FC running 14.5 if I update magisk keeps FC won't even update..
How do i check for safety net?.
Thanks in advance.
Click to expand...
Click to collapse
The message is actually harmless. It's due to magisk patching the stock kernel. I would flash a custom kernel, like Flash kernel from here....
https://forum.xda-developers.com/pixel-2-xl/development/taimen-flash-kernel-1-00-t3702057
And then flash magisk 16.0. Both of them in TWRP. Disable your lock screen security first before you enter twrp. Then flash the kernel, and then magisk. Then all should be good :good:
Badger50 said:
The message is actually harmless. It's due to magisk patching the stock kernel. I would flash a custom kernel, like Flash kernel from here....
https://forum.xda-developers.com/pixel-2-xl/development/taimen-flash-kernel-1-00-t3702057
And then flash magisk 16.0. Both of them in TWRP. Disable your lock screen security first before you enter twrp. Then flash the kernel, and then magisk. Then all should be good :good:
Click to expand...
Click to collapse
This works?.
egren58 said:
This works?.
Click to expand...
Click to collapse
It's what most of us do all the time. Don't seen why it wouldn't
Badger50 said:
It's what most of us do all the time. Don't seen why it wouldn't
Click to expand...
Click to collapse
Will try
egren58 said:
Will try
Click to expand...
Click to collapse
If it hangs up at the white Google screen for a while, just do a hard reset with the power button :good:
My preference is for the ElementalX kernel - it comes with a cool management app - and battery tracking.
Sent from my Pixel 2 XL using XDA Labs
I tired all arm64 custom roms for moto z play, some arm, tried mixing with all kernels and magisk/without magisk.
And i can't pass safetynet on all these configurations
That's the point of SN. Those ROMs aren't certified by Google so they don't want you to pass. That's not a problem of any ROM, that's how it's intended to work
But I have passed with magisk
Artim_96 said:
That's the point of SN. Those ROMs aren't certified by Google so they don't want you to pass. That's not a problem of any ROM, that's how it's intended to work
Click to expand...
Click to collapse
But on my old phone, i was using custom roms (not certificed), and SN was passing.
mijing said:
But I have passed with magisk
Click to expand...
Click to collapse
With ROM you using?
dawidrejowski said:
With ROM you using?
Click to expand...
Click to collapse
Im using official Validus ..you can try universal safety net fix to pass safety net.I'm using this.
dawidrejowski said:
But on my old phone, i was using custom roms (not certificed), and SN was passing.
Click to expand...
Click to collapse
How old of a phone? My last phone (HTC One M8) passed on custom ROMs because it didn't seem to report the bootloader was unlocked. But I have safety net passing on custom ROMs on my Z play thanks to magisk and universal safteynet fix beta 5.
mijing said:
Im using official Validus ..you can try universal safety net fix to pass safety net.I'm using this.
Click to expand...
Click to collapse
What do you mean by "universal..." - magisk? if so, which release are you using? Thanks!
KrisM22 said:
What do you mean by "universal..." - magisk? if so, which release are you using? Thanks!
Click to expand...
Click to collapse
Universal safetyNet Fix(v2 Beta 5) is the module of Magisk
mijing said:
Universal safetyNet Fix(v2 Beta 5) is the module of Magisk
Click to expand...
Click to collapse
That is a very old one - could you please attach it to your post for a few minutes? TIA!
KrisM22 said:
That is a very old one - could you please attach it to your post for a few minutes? TIA!
Click to expand...
Click to collapse
Yes it is too old but till now it is usefull as you can see
mijing said:
Yes it is too old but till now it is usefull as you can see
Click to expand...
Click to collapse
I found it up on
https://androidfilehost.com/?fid=673368273298984533
is that it?
I'll go try it on AOSP 8.1 Alberto97
Yes,It Is. but I dont Know about AOSP Is it will work or not
mijing said:
Yes,It Is. but I dont Know about AOSP Is it will work or not
Click to expand...
Click to collapse
lots of red messages so far - what version of magisk MANAGER are you using? (magisk/settings/about) - I tried 4.3.1 but no go.
EDIT I see you're running 16 of magisk, but have added module 14 2-5. How did you manage to add that?
KrisM22 said:
lots of red messages so far - what version of magisk MANAGER are you using? (magisk/settings/about) - I tried 4.3.1 but no go.
EDIT I see you're running 16 of magisk, but have added module 14 2-5. How did you manage to add that?
Click to expand...
Click to collapse
Yes I'm using v16 of magisk with module
Go to magisk manager - module - + bottom (for add Module) install it
If installation fail you can flash with recovery that's it.
(My English? )
mijing said:
But I have passed with magisk
Click to expand...
Click to collapse
Edit: Never mind I saw what Rom you were running.
mijing said:
Yes I'm using v16 of magisk with module
Go to magisk manager - module - + bottom (for add Module) install it
If installation fail you can flash with recovery that's it.
(My English )
Click to expand...
Click to collapse
Your English is excellent!!!
I now have a very tiny understanding of Magisk Modules...
I started with 1600 this time (it later updated the mgr).
I thought this failed before so it may be necessary to try to add module with magisk, let it fail, then boot to recovery, flash that old 2 beta 5 zip (flash goes fine) , and reboot and I find that old 2 beta 5 zip is now in magisk modules. YOU THE PERSON!!! (gender non-specific version of you da man!)
I went on to do my usual of install TBPro, restore my stuff(obviously root works), reboot to recovery to backup at this point. and test. SafetyNet passes fully, Pogo plays, Netflix shows in gpstore. And I now have a working 8.1 on my MZP.
HUGE THANKS for your patience!!!!!!!
KrisM22 said:
Your English is excellent!!!
I now have a very tiny understanding of Magisk Modules...
I started with 1600 this time (it later updated the mgr).
I thought this failed before so it may be necessary to try to add module with magisk, let it fail, then boot to recovery, flash that old 2 beta 5 zip (flash goes fine) , and reboot and I find that old 2 beta 5 zip is now in magisk modules. YOU THE PERSON!!! (gender non-specific version of you da man!)
I went on to do my usual of install TBPro, restore my stuff(obviously root works), reboot to recovery to backup at this point. and test. SafetyNet passes fully, Pogo plays, Netflix shows in gpstore. And I now have a working 8.1 on my MZP.
HUGE THANKS for your patience!!!!!!!
Click to expand...
Click to collapse
Im glad you have fix your problem
KrisM22 said:
Your English is excellent!!!
I now have a very tiny understanding of Magisk Modules...
I started with 1600 this time (it later updated the mgr).
I thought this failed before so it may be necessary to try to add module with magisk, let it fail, then boot to recovery, flash that old 2 beta 5 zip (flash goes fine) , and reboot and I find that old 2 beta 5 zip is now in magisk modules. YOU THE PERSON!!! (gender non-specific version of you da man!)
I went on to do my usual of install TBPro, restore my stuff(obviously root works), reboot to recovery to backup at this point. and test. SafetyNet passes fully, Pogo plays, Netflix shows in gpstore. And I now have a working 8.1 on my MZP.
HUGE THANKS for your patience!!!!!!!
Click to expand...
Click to collapse
Check for Bluetooth and wifi if they are working correctly. I flashed the fix on AOSP and my Bluetooth crashed, needed to restore backup.
So I have spent a bit of time testing out project treble roms, cant get any to boot unfortunately. It might be a twrp thing who at this point knows?
Hopefully some Roms & possibly kernels will pop up In the coming weeks or months
Was worth a try, if anyone has had success with GSI's and getting them to boot, please share your method......:good:
I got my S10E to boot phh's v112 gsi, backlit broken so screen very dim, some other bugs to: some settings and apps crash.
How to:
Make sure you have an exynos version
Have an stock rom installed, bootloader unlocked and rebooted into stock and make sure oem unlocking in greyed out in dev settings.
Install recovery (latest fixed version)
Use multidisabler and format data (https://forum.xda-developers.com/galaxy-s10/development)
Reboot recovery
Install GSI, A/B version
Mount system and use TWRP file explorer to delete rw-system.sh in system/bin
Reboot , may need to press power, volume up and bixby few sec in inital boot.
Successfully flashed ......just transitional animation bug, brightness can't be adjusted....but it's not dim....Pixel Experience Rom.
Pixel Dust ......
Just testing out one more, they both boot fine (Pixel Experience & Pixel Dust). ..
Obviously Fingerprint Scanner is non functional also the same brighteness bug (cannot adjust).
Here are some screens of Pixel Dust.
I'm guessing with a little bit of work these roms will be just fine....:good:
Root also works as it should, as your booting to a rooted system....
Thanks to you both for your testing on GSI roms.
If you report the bugs with logcat to phh telegram group i suppose he will fix it for sure.
NisseGurra said:
I got my S10E to boot phh's v112 gsi, backlit broken so screen very dim, some other bugs to: some settings and apps crash.
How to:
Make sure you have an exynos version
Have an stock rom installed, bootloader unlocked and rebooted into stock and make sure oem unlocking in greyed out in dev settings.
Install recovery (latest fixed version)
Use multidisabler and format data (https://forum.xda-developers.com/galaxy-s10/development)
Reboot recovery
Install GSI, A/B version
Mount system and use TWRP file explorer to delete rw-system.sh in system/bin
Reboot , may need to press power, volume up and bixby few sec in inital boot.
Click to expand...
Click to collapse
So its the A/B not the A only version right?
I was getting bootloops every time i try to install a GSi.
uvitor said:
So its the A/B not the A only version right?
I was getting bootloops every time i try to install a GSi.
Click to expand...
Click to collapse
Yes, s10X uses a/b gsi's
NisseGurra said:
Yes, s10X uses a/b gsi's
Click to expand...
Click to collapse
Thanks. By the way, do we stilll have the magisk after GSi? In other words, as of S10 now have restriction on installation of magisk into system partition and it has to be installed into recovery partition, (the Method using Ian's patched TWRP and Magisk), how GSi interact with root and TWRP?
Thanks in advance.
uvitor said:
Thanks. By the way, do we stilll have the magisk after GSi? In other words, as of S10 now have restriction on installation of magisk into system partition and it has to be installed into recovery partition, (the Method using Ian's patched TWRP and Magisk), how GSi interact with root and TWRP?
Thanks in advance.
Click to expand...
Click to collapse
Gsi do not touch recovery or magisk, maybe needed to patch recovery.img with magisk to be able to boot tho
Duncan1982 said:
Pixel Dust ......
Just testing out one more, they both boot fine (Pixel Experience & Pixel Dust). ..
Obviously Fingerprint Scanner is non functional also the same brighteness bug (cannot adjust).
Here are some screens of Pixel Dust.
I'm guessing with a little bit of work these roms will be just fine....:good:
Root also works as it should, as your booting to a rooted system....
Click to expand...
Click to collapse
You can control thé brightness with modifying a build.prop setting just check the git issue on phh site.
Do you mean with last (fixed ?) twrp, can we power off the phone without bootloop ? [emoji16]
thebigtross said:
You can control thé brightness with modifying a build.prop setting just check the git issue on phh site.
Do you mean with last (fixed ?) twrp, can we power off the phone without bootloop ? [emoji16]
Click to expand...
Click to collapse
Yes booting is fine. Can you link the issue please, i cant seem to find it. Thanks.
sir-harlekin said:
Yes booting is fine. Can you link the issue please, i cant seem to find it. Thanks.
Click to expand...
Click to collapse
+1, i don't think it can be fixed by build.prop.
NisseGurra said:
+1, i don't think it can be fixed by build.prop.
Click to expand...
Click to collapse
Tweak
/sys/class/backlight/panel0-backlight/brightness
/sys/class/leds/lcd-backlight/brightness
Or Try
setprop persist.sys.qcom-brightness 255
And reboot
Or getprop |grep brightness to get value
thebigtross said:
Tweak
/sys/class/backlight/panel0-backlight/brightness
/sys/class/leds/lcd-backlight/brightness
Or Try
setprop persist.sys.qcom-brightness 255
And reboot
Or getprop |grep brightness to get value
Click to expand...
Click to collapse
How do you get root after flash GSI? I used the TWRP(and Magisk) pached by Ian's method and got root on Stock after install the MAgisk Mananger also patched by ian. After flash any GSi, i loose root and im not able to install any magisk manager.
uvitor said:
How do you get root after flash GSI? I used the TWRP(and Magisk) pached by Ian's method and got root on Stock after install the MAgisk Mananger also patched by ian. After flash any GSi, i loose root and im not able to install any magisk manager.
Click to expand...
Click to collapse
Twrp is root, so if you reboot by the method you should be aware of then you'll be booted into a rooted system :good:
uvitor said:
How do you get root after flash GSI? I used the TWRP(and Magisk) pached by Ian's method and got root on Stock after install the MAgisk Mananger also patched by ian. After flash any GSi, i loose root and im not able to install any magisk manager.
Click to expand...
Click to collapse
Flash magisk ou supersu from twrp as usally.
Not the patched or prepatched provided file lol.
Else some aosp roms are prerooted with supersu. They are tagged *-su* in filename
NisseGurra said:
Gsi do not touch recovery or magisk, maybe needed to patch recovery.img with magisk to be able to boot tho
Click to expand...
Click to collapse
does that mean the Snapdragon USA version can try it?
sorry, I am new to rooting
vonDubenshire said:
does that mean the Snapdragon USA version can try it?
sorry, I am new to rooting
Click to expand...
Click to collapse
No, all us snapdragons have locked bootloaders, no root.
In the meantime, is someone running GSI as a daily driver?
sir-harlekin said:
In the meantime, is someone running GSI as a daily driver?
Click to expand...
Click to collapse
I am. BUT there are several bugs to be addressed such:
Not working:
Bluetooh/NFC
Fingerprint
Proximity sensor
Auto brightness (manual does)
MTP
Force closes on any app info in settings
Im using because the progect is very promising and phhusson is open to user's reports so, im trying exactly to do that feedback and speed up the development.
Hi, I'd like to flash some magisk Modules that I suspect may break some things, and cause a bootloop usually I wouldn't worry as I can just delete this modules from recovery and everything would work again. But since our device (OP9P) doesn't have a recovery yet, is there any way to fix if something goes wrong?
Can you not uninstall/flash modules through magisk?
Levi4cyber said:
Hi, I'd like to flash some magisk Modules that I suspect may break some things, and cause a bootloop usually I wouldn't worry as I can just delete this modules from recovery and everything would work again. But since our device (OP9P) doesn't have a recovery yet, is there any way to fix if something goes wrong?
Click to expand...
Click to collapse
Not sure if it still works, but you should be able to go in through safe mode to delete magisk. Not sure about just modules, but it would get you out of a hole anyway.
hallo dare said:
Not sure if it still works, but you should be able to go in through safe mode to delete magisk. Not sure about just modules, but it would get you out of a hole anyway.
Click to expand...
Click to collapse
Yes, that's a really good suggestion, I was in that situation couple of days ago, force reboot to safe mode, you don't have to do anything in safe mode, then just do a normal system boot and all modules should be disabled and just uninstall them before your next reboot.
Levi4cyber said:
Hi, I'd like to flash some magisk Modules that I suspect may break some things, and cause a bootloop usually I wouldn't worry as I can just delete this modules from recovery and everything would work again. But since our device (OP9P) doesn't have a recovery yet, is there any way to fix if something goes wrong?
Click to expand...
Click to collapse
if you are getting bootloops and in a jam, use method 2 (adb) to remove modules, this method saved me when a module caused a BL situation, only downside is it will remove all modules.
How to Fix Bootloops caused by Magisk Modules (Using TWRP Recovery or ADB)
Has your Android device entered a bootloop after installing a Magisk Module? Then this guide can help you fix that. In this guide, I will show you how to fix bootloops caused by Magisk Modules using…
www.thecustomdroid.com
oscarmaldonado said:
Yes, that's a really good suggestion, I was in that situation couple of days ago, force reboot to safe mode, you don't have to do anything in safe mode, then just do a normal system boot and all modules should be disabled and just uninstall them before your next reboot.
Click to expand...
Click to collapse
For some unknown reason my modules are still installed after reboot in save mode.
Am I doing something wrong?
netgar said:
For some unknown reason my modules are still installed after reboot in save mode.
Am I doing something wrong?
Click to expand...
Click to collapse
Hey there bud, what exactly are you trying to do, a bad module creating a boot loop in you phone?
oscarmaldonado said:
Hey there bud, what exactly are you trying to do, a bad module creating a boot loop in you phone?
Click to expand...
Click to collapse
I did before so I had to basically reinstall all my apps from scratch.
I installed bootloop saver module and I hope I will be safe once any not compatible module will cause bootloop.
I'm not safe since after reboot from save mode all my modules are still active and installed.
use this command in debugging mode enabled
Code:
adb wait-for-device shell magisk --remove-modules
I tried a mod from here but it put my phone into a bootloop, I think it was for android 9.
how did you install it, via magisk, recovery or others?
JuanTamqd21 said:
how did you install it, via magisk, recovery or others?
Click to expand...
Click to collapse
It was either magisk or recovery
MikeRWK said:
It was either magisk or recovery
Click to expand...
Click to collapse
How to Uninstall a Magisk Module and Magisk zip from a Rooted Device
You might have often come across a boot loop on your smartphone due to a specific Magisk Module. This is quite a common problem as sometimes, a cific
www.getdroidtips.com
JuanTamqd21 said:
How to Uninstall a Magisk Module and Magisk zip from a Rooted Device
You might have often come across a boot loop on your smartphone due to a specific Magisk Module. This is quite a common problem as sometimes, a cific
www.getdroidtips.com
Click to expand...
Click to collapse
I'm long after wiping the phone and starting fresh. I just need to disable the camera sound