This is the Magisk module that can disable HTC boot sound (HTC_Sense5_Boot.mp3)
Link: https://github.com/zjbbhsso/disablehtcbootsound
zjbbhsso said:
This is the Magisk module that can disable HTC boot sound (HTC_Sense5_Boot.mp3)
Link: https://github.com/zjbbhsso/disablehtcbootsound
Click to expand...
Click to collapse
Any way to replace the boot animation? I tried to just throw a new one into the folder and reboot but it didn't seem to wanna work. Anytime I tried I got the default silver android one.
Related
I need help as I locked myself out of the phone somehow!
I have xposed installed, and I have gravitybox and wanam installed (as well as sense toolbox)
i check the feature that does crt animation for screen off and also fade on screen on, however I think I have some conflicting settings I may not be aware of as when I try to turn on my screen I get both animations at once it seems. I can't access anything at all and if I swipe up from the bottom of the screen I get a vibration.
I have TWRP installed so I can probably disable one of the mods if I only knew in which directory it was and what it was called :crying:
Please help I don't want to re-install all my apps
And it would be nice to use my phone again lol
RAMBOcoder said:
I need help as I locked myself out of the phone somehow!
I have xposed installed, and I have gravitybox and wanam installed (as well as sense toolbox)
i check the feature that does crt animation for screen off and also fade on screen on, however I think I have some conflicting settings I may not be aware of as when I try to turn on my screen I get both animations at once it seems. I can't access anything at all and if I swipe up from the bottom of the screen I get a vibration.
I have TWRP installed so I can probably disable one of the mods if I only knew in which directory it was and what it was called :crying:
Please help I don't want to re-install all my apps
And it would be nice to use my phone again lol
Click to expand...
Click to collapse
have you tried disabling xposed from recovery? Select ''install'' from recovery then choose Xposed-Disabler-Recovery.zip
alray said:
have you tried disabling xposed from recovery? Select ''install'' from recovery then choose Xposed-Disabler-Recovery.zip
Click to expand...
Click to collapse
Thanks for the info I didn't have the file but I should keep it handy.
I actually solved the problem I just restarted and was able to use the phone as long as the screen didn't shut off. So I just turned off the offending feature.
Do boot animations in the theme engine work for anyone else or am I doing something wrong? They work fine on my nexus 4 but the nexus 6 retains the default boot animation. An example is the dark material theme. When I apply it on my nexus 4, I can reboot and see the blacked out boot animation. On the nexus 6 I get the default CM boot animation. I can change it if I replace /system/media/bootanimation.zip. Adding /data/local/bootanimation.zip has no effect.
Some nexus 6 have boot animations in the /OEM partition that override all others. Depends which nexus 6 you've got (getting carrier version)
I do have the ATT version, however I removed everything from that partiton to get rid of the boot animation it was pulling from there.
Same Issue Here
I am experiencing the exact same issue. I got my Nexus 6 from Google and the OEM partition is completely empty. Soft reboot displays themed boot animation. Full reboot does not. I believe this must have something to do with permissions during boot. I have flipped the SuperSU flag to apply during boot up (Which, maybe, worked one time?).
Still looking for a solution...
KKenna said:
Soft reboot displays themed boot animation. Full reboot does not.
Click to expand...
Click to collapse
+1. I dug out the bootanimation from the theme apk and placed it in system\media chmod 644.
Found a temp fix
KKenna said:
I am experiencing the exact same issue. I got my Nexus 6 from Google and the OEM partition is completely empty. Soft reboot displays themed boot animation. Full reboot does not. I believe this must have something to do with permissions during boot. I have flipped the SuperSU flag to apply during boot up (Which, maybe, worked one time?).
Still looking for a solution...
Click to expand...
Click to collapse
http://forum.xda-developers.com/android/software/arm-arm64-android-5-0-lollipop-t3032247
check this thread out, when i did what they said i could change it and yes you have to use root browser I tried it with xposed dint work and you will have to do this every time after a nightly flash basically after every flash well thats what i got to do, thats the reason i said temp fix and does your stock cm boot animation feel a bit laggy ? cause mine does
After I installed Magisk 16.0 on my OnePlus 3T with OOS Open Beta 23, when I long press the power button, it instantly leads me to the OOS boot animation, I don't get the 1+ and powered by android screen nor I get the unlocked bootloader warning. Thus I can't boot to fastboot or recovery when rebooting via power button. I can turn off the phone by pressing the power button for a very long time while the phone is loading though. What should I do?
No problem here. Have you got Substratum and installed some themes?
przemcio510 said:
No problem here. Have you got Substratum and installed some themes?
Click to expand...
Click to collapse
No I don't, I use the following modules: Adaptive Icons Round Mask, Busybox for Android NDK, Magisk Google DNS, OP3T Front Camera Fix and YouTube Vanced Black.
NeoMember said:
No I don't, I use the following modules: Adaptive Icons Round Mask, Busybox for Android NDK, Magisk Google DNS, OP3T Front Camera Fix and YouTube Vanced Black.
Click to expand...
Click to collapse
I would uninstall Magisk and see if the problem goes away then reinstall Magisk only and check that all is well. The do the modules one at a time checking that you can reboot normally.
Sent from my OnePlus3T using XDA Labs
BillGoss said:
I would uninstall Magisk and see if the problem goes away then reinstall Magisk only and check that all is well. The do the modules one at a time checking that you can reboot normally.
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
Well, for some reason my device was unable to boot to system, so I started fresh with Magisk and problem is gone now. Still don't know the reason though.
Hi All. After I installing magisk modules I restart the phone to activate the module the Pixel not boot and stop in Google logo I have to hold the power button for like 17 a second for force restart then boot again perfect.
The question is that normal or i have done something wrong
Sent from my Pixel 2 using Tapatalk
DinarQ8 said:
Hi All. After I installing magisk modules I restart the phone to activate the module the Pixel not boot and stop in Google logo I have to hold the power button for like 17 a second for force restart then boot again perfect.
The question is that normal or i have done something wrong
Click to expand...
Click to collapse
Interestingly I am having a similar issue. Whenever I add or remove a module through magisk and then reboot, It freezes up right after login and I need to hard boot it again then all is fine. Are you running the custom kernel or is it the stock one? Also are you using Edge Sense Plus??
@CyberpodS2
I don't know if this normal with everyone or not. Everything is Stock and i don't use Edge sense plus
Sent from my Pixel 2 using Tapatalk
Don't reboot through magisk when the module installs, instead restart using the power button after you finish the install of the module.
DinarQ8 said:
I don't know if this normal with everyone or not. Everything is Stock and i don't use Edge sense plus
Click to expand...
Click to collapse
Well it's not "normal" but it might be harmless. Maybe something that the Magisk folks need to work on. We are barely out of release and already it's rooted, custom kernel, themes, mods, xposed. There are bound to be bugs at this early point. Lol
---------- Post added at 10:18 PM ---------- Previous post was at 10:17 PM ----------
wgrant said:
Don't reboot through magisk when the module installs, instead restart using the power button after you finish the install of the module.
Click to expand...
Click to collapse
I'll give that a run. Thanks.
Hi there!
Just a quick question. Finally afer so much time since the actual update to emui 9.1 (Psmart Fig-lx1) Ive finally managed to get that **** done - i mean rooting that mother****er
From what I gathered if I want to reboot the phone I have to hold that power vol + button 'n 'stuff. So question remains simple.
**So if i would instal a magisk module and it reboots my phone - do I need to just hold that vol + button and the planet wont go boom, or is ther aleoso some specific stuff You need to co?
**Also - what does 'recovery mode option in Magisk Manager means?
Cheers!
Why would you have to hold the vol + button to reboot at all? That's not normal.
Sent from my LG-US998 using Tapatalk
kenbo111 said:
Why would you have to hold the vol + button to reboot at all? That's not normal.
Sent from my LG-US998 using Tapatalk
Click to expand...
Click to collapse
A recent method on installing magisk trough a patched recovery image require exacly that. And it's not the end. When You boot normally no buttons - You've got non rooted system (without magisk)
When You keep Vol+ till splash screen You've got system with magisk (full root)
And when You keep that VoL allll the way - You suppose to boot into recovery.
I too don't know how they pulled this off but just in case something wouild go wronga after instalation of the meodules I'd like to know in advence
That's wierd! I've never heard of that before
Sent from my LG-US998 using Tapatalk
kenbo111 said:
That's wierd! I've never heard of that before.
Click to expand...
Click to collapse
It's uncommon, but not unheard of. Rebooting that way be needed for devices where a Magisk patched boot image is swapped with the recovery image (since the modified boot image couldn't be put in place of the original, untampered one for some reason). In such cases, if you reboot to recovery, the Magisk modified boot image will be loaded instead of the recovery, which will lead to booting into a rooted ROM. This is how root also works for Samsung S9 and Note 9.
shadowstep said:
It's uncommon, but not unheard of. Rebooting that way be needed for devices where a Magisk patched boot image is swapped with the recovery image (since the modified boot image couldn't be put in place of the original, untampered one for some reason). In such cases, if you reboot to recovery, the Magisk modified boot image will be loaded instead of the recovery, which will lead to booting into a rooted ROM. This is how root also works for Samsung S9 and Note 9.
Click to expand...
Click to collapse
That sounds both incredibly annoying and tedious but also quite handy when it comes to recovering from bootloops when you aren't near a PC ?
Sent from my Pixel 3a XL using XDA Labs
Skittles9823 said:
That sounds both incredibly annoying and tedious but also quite handy when it comes to recovering from bootloops when you aren't near a PC ?
Click to expand...
Click to collapse
Yet, it is. That's why I'll never buy devices that can't be easily rooted. I forgot to add, since the images are swapped (original boot becomes recovery and recovery becomes Magisk patched boot), a normal reboot would lead to booting to recovery everytime and rebooting to recovery (either by a key combo or from the ROM itself) is needed to boot to system. Good times.
shadowstep said:
Yet, it is. That's why I'll never buy devices that can't be easily rooted. I forgot to add, since the images are swapped (original boot becomes recovery and recovery becomes Magisk patched boot), a normal reboot would lead to booting to recovery everytime and rebooting to recovery (either by a key combo or from the ROM itself) is needed to boot to system. Good times.
Click to expand...
Click to collapse
Ahh my brain hurts lmao.
I thought it would boot into an unrooted system if not using the recovery shortcut. Yea that does sound irritating.
Skittles9823 said:
Ahh my brain hurts lmao.
I thought it would boot into an unrooted system if not using the recovery shortcut. Yea that does sound irritating.
Click to expand...
Click to collapse
I am sure, lol. Also, if it boots to an unrooted system if not using the recovery shortcut and to a rooted system if using that recovery shortcut, how do you access recovery? Be glad you have a much more root-friendly device.
shadowstep said:
Also, if it boots to an unrooted system if not using the recovery shortcut and to a rooted system if using that recovery shortcut, how do you access recovery? Be glad you have a much more root-friendly device.
Click to expand...
Click to collapse
Haha yea, that's true.
Sent from my Pixel 3a XL using XDA Labs
shadowstep said:
Yet, it is. That's why I'll never buy devices that can't be easily rooted. I forgot to add, since the images are swapped (original boot becomes recovery and recovery becomes Magisk patched boot), a normal reboot would lead to booting to recovery everytime and rebooting to recovery (either by a key combo or from the ROM itself) is needed to boot to system. Good times.
Click to expand...
Click to collapse
In fact, the images are not swapped (at least on S10). If you hold the Vol key long enough, the recovery kernel will boot the recovery system, and if you release it, it'll boot android. So, a rooted system runs on the recovery kernel.
Keule-T said:
In fact, the images are not swapped (at least on S10). If you hold the Vol key long enough, the recovery kernel will boot the recovery system, and if you release it, it'll boot android. So, a rooted system runs on the recovery kernel.
Click to expand...
Click to collapse
Not sure about the S10, but they are definitely swapped for S9. More information can be taken from this XDA article (and the thread links referenced in it). :good:
given nice contidions, any phone can break just by using magisk modules that do tricky stuff to ur image. and since that applies on any magisk module for a varius of reasons, wellp there is no "safe" module. under certain circumstances every module can break **** down.