Hey guys,
Hope it's OK to post this here.
Just 2 things. Just unlocked and rooted P4XL, yay! Haha. Everytime I flash a module in Magisk, the phone gets to the Google logo after reboot and stays. I have to manually reset (power button for 10secs) then it boots normal and the module is there working. Is there something I haven't set? Is this normal?
The second thing was, can anyone point me in the direction of a high brightness mod for the P4XL. I know there's a shell command and then you have to make a tasker task to lock it in on screen wake but, is there a Magisk mod or something that I haven't found yet?
Thanks in advance as always guys.
Lambetts said:
Hey guys,
Hope it's OK to post this here.
Just 2 things. Just unlocked and rooted P4XL, yay! Haha. Everytime I flash a module in Magisk, the phone gets to the Google logo after reboot and stays. I have to manually reset (power button for 10secs) then it boots normal and the module is there working. Is there something I haven't set? Is this normal?
The second thing was, can anyone point me in the direction of a high brightness mod for the P4XL. I know there's a shell command and then you have to make a tasker task to lock it in on screen wake but, is there a Magisk mod or something that I haven't found yet?
Thanks in advance as always guys.
Click to expand...
Click to collapse
EX kernel and the other two that are posted on this site both have high brightness mode as an option. I'm not sure if the problem you are having is with Magisk or the module itself. This happened with my device on occasion. I flashed the magisk modified boot IMG to both partitions and it hasn't done it since. That could be pure luck but in my case it seems to have worked.
Lambetts said:
Hey guys,
Hope it's OK to post this here.
Just 2 things. Just unlocked and rooted P4XL, yay! Haha. Everytime I flash a module in Magisk, the phone gets to the Google logo after reboot and stays. I have to manually reset (power button for 10secs) then it boots normal and the module is there working. Is there something I haven't set? Is this normal?
The second thing was, can anyone point me in the direction of a high brightness mod for the P4XL. I know there's a shell command and then you have to make a tasker task to lock it in on screen wake but, is there a Magisk mod or something that I haven't found yet?
Thanks in advance as always guys.
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=flar2.hbmwidget
This should take care of your HBM if using a custom kernel. The other problem sounds like a module problem as the previous poster stated :good:
murphyjasonc said:
EX kernel and the other two that are posted on this site both have high brightness mode as an option. I'm not sure if the problem you are having is with Magisk or the module itself. This happened with my device on occasion. I flashed the magisk modified boot IMG to both partitions and it hasn't done it since. That could be pure luck but in my case it seems to have worked.
Click to expand...
Click to collapse
Thanks for your reply.
How is EX Kernel currently? Anyone tried it on this device yet?
Thanks again! ☺
Lambetts said:
Thanks for your reply.
How is EX Kernel currently? Anyone tried it on this device yet?
Thanks again!
Click to expand...
Click to collapse
EX Kernel is what I'm currently using. It's very stable and I haven't had any issues at all. I'm not sure if there is a download link or not but it can be installed from the EXKM app. I am also using the HBM app that Badger50 linked to. It works great.
Lambetts said:
Thanks for your reply.
How is EX Kernel currently? Anyone tried it on this device yet?
Thanks again! ☺
Click to expand...
Click to collapse
murphyjasonc said:
EX Kernel is what I'm currently using. It's very stable and I haven't had any issues at all. I'm not sure if there is a download link or not but it can be installed from the EXKM app. I am also using the HBM app that Badger50 linked to. It works great.
Click to expand...
Click to collapse
+1. Ex kernel has been flawless for me as well! Combine that with the EXKM and HBM app, and you've got winner for sure! :good:
Badger50 said:
+1. Ex kernel has been flawless for me as well! Combine that with the EXKM and HBM app, and you've got winner for sure! :good:
Click to expand...
Click to collapse
I used EX quite a bit on my N6P. Loved it. Just thought I'd ask. Thanks heaps guys, I really appreciate your help.
But there's no MajMod for HBM currently is there, or that you know of?
Thanks again.
Lambetts said:
I used EX quite a bit on my N6P. Loved it. Just thought I'd ask. Thanks heaps guys, I really appreciate your help.
But there's no MajMod for HBM currently is there, or that you know of?
Thanks again.
Click to expand...
Click to collapse
None that I know of. However, if your running the Ex kernel, all you need is the HBM widget and your all set :good:
Badger50 said:
None that I know of. However, if your running the Ex kernel, all you need is the HBM widget and your all set :good:
Click to expand...
Click to collapse
So it's a turn on and it stays on?
Lambetts said:
So it's a turn on and it stays on?
Click to expand...
Click to collapse
It's a toggle switch basically :good:
Badger50 said:
It's a toggle switch basically :good:
Click to expand...
Click to collapse
So I should tasker trigger it on screen wake really...
Retyped sorry. Delete please.
Side question. This device is set up like the P2XL yeah? Treble? Slot a and Slot b? I wish it was like it used to be, system, boot and recovery haha. But anyway, it is what it is.
Does anyone know where to get the EX Kernel zip? For some reason flashing shoots back an error when trying to download and install from EXKM
Lambetts said:
Hey guys,
Hope it's OK to post this here.
Just 2 things. Just unlocked and rooted P4XL, yay! Haha. Everytime I flash a module in Magisk, the phone gets to the Google logo after reboot and stays. I have to manually reset (power button for 10secs) then it boots normal and the module is there working. Is there something I haven't set? Is this normal?
The second thing was, can anyone point me in the direction of a high brightness mod for the P4XL. I know there's a shell command and then you have to make a tasker task to lock it in on screen wake but, is there a Magisk mod or something that I haven't found yet?
Thanks in advance as always guys.
Click to expand...
Click to collapse
Just when you flash any module do not reboot by magisk. Reboot by Power button. That what I do
Sent from my Pixel 4 XL using Tapatalk
---------- Post added at 09:10 AM ---------- Previous post was at 09:08 AM ----------
rickysidhu_ said:
Does anyone know where to get the EX Kernel zip? For some reason flashing shoots back an error when trying to download and install from EXKM
Click to expand...
Click to collapse
For now only way to download the kernel only from the application
Sent from my Pixel 4 XL using Tapatalk
I just tried to flash EX Kernel through app and it did the same thing as a Majisk Mod and stuck on the google label and had to hold the power button to reboot, it did and it doesn't seem to have flashed... Thoughts? What am I doing wrong? Haha.
Lambetts said:
I just tried to flash EX Kernel through app and it did the same thing as a Majisk Mod and stuck on the google label and had to hold the power button to reboot, it did and it doesn't seem to have flashed... Thoughts? What am I doing wrong? Haha.
Click to expand...
Click to collapse
Read [emoji1375]
Sent from my Pixel 4 XL using Tapatalk
I worked it out. All good. As far as I've 'READ' twrp isn't available for the P4XL so, the app was assuming I had a custom recovery. But I don't, so I flashed the downloaded zip through the app (using the in app Flash tool) and rebooted manually. Seems to have stuck. For anyone that might read this, so that it HELPS them. That's what we're here for! Good job.
So maybe I could run a script to enable HBM on every boot? Anyone know if that's possible? Sorry, I'm not much of a script-er. Haha.
Thanks again guys. ☺
Lambetts said:
I worked it out. All good. As far as I've 'READ' twrp isn't available for the P4XL so, the app was assuming I had a custom recovery. But I don't, so I flashed the downloaded zip through the app (using the in app Flash tool) and rebooted manually. Seems to have stuck. For anyone that might read this, so that it HELPS them. That's what we're here for! Good job.
So maybe I could run a script to enable HBM on every boot? Anyone know if that's possible? Sorry, I'm not much of a script-er. Haha.
Thanks again guys. ☺
Click to expand...
Click to collapse
Why would you need a script? It's already enabled if your using the Ex kernel and have root. You could either turn it on under settings/graphics in the EXKM app, or just use the toggle that the HBM widget allows :good:
Badger50 said:
Why would you need a script? It's already enabled if your using the Ex kernel and have root. You could either turn it on under settings/graphics in the EXKM app, or just use the toggle that the HBM widget allows :good:
Click to expand...
Click to collapse
Argh, I think I've completely misunderstood the HBM mode and what it's supposed to do. I read that it's supposed to push your screen a bit past it's Max brightness so you can see it outside better. Something like from 350nits to like 550nits. When I enable that mode in EX, it just keeps it on full, the screen already does that outside. Haha.
So either this isn't what I'm looking for or, I've completely misunderstood what it had the potential of doing.
Related
As the title says, I'm trying to see if magisk will work, and wanted input before I flash it.
jrk190 said:
As the title says, I'm trying to see if magisk will work, and wanted input before I flash it.
Click to expand...
Click to collapse
It works, I currently use it for root, ViPER, and Xposed.
I actually went ahead and installed it before you replied, and I've been looking for something like it for ages. It's really well done.
Thanks for the heads up. I just converted from SuperSU to Magisk with phh SuperUser with no problems. Works great.
yes, it's work, [kingroot]
Hi, can you post the link of the guide that you used to install and get the Magisk working??? I need a newbie friendly guide to get that poke go working -.-
turron83 said:
Hi, can you post the link of the guide that you used to install and get the Magisk working??? I need a newbie friendly guide to get that poke go working -.-
Click to expand...
Click to collapse
This is the guide I used: http://www.androidpolice.com/2016/09/11/guide-play-pokemon-go-0-37-rooted-android-magisk/
Thanks!! i only did the first step and after the rebooting, i can get into pokemon go and play!!
Cya guys!!
turron83 said:
Thanks!! i only did the first step and after the rebooting, i can get into pokemon go and play!!
Cya guys!!
Click to expand...
Click to collapse
The first part, you mean just unroot part?
Sent from my R1 HD using Tapatalk
Yes, installed so I could keep adblock and still play Pokemon Go with my kids. Used SuperSU full unroot and then followed the guides here on XDA for how to install it - works great
Installed following the android police tutorial. Root and xposed working. However, when I switch "Root Toggle" in Magisk Manager to the off position, it switches itself back to the on position. Anyone else getting this?
Edit:
This works, per u/Howie_The_Lord on reddit:
Quote:
It seems that this happens, when you ROM is preeroted, you need to delete the system/xbin/su with TWRP and let Magisk mount its own there.
Source: https://www.reddit.com/r/pokemongode...0_with_magisk/
Though, now I get a screen on PoGo saying that my device is not compatible. At least I’m past the authentication.
Trying using Automagisk. It's truly a set it and forget it. http://www.androidpolice.com/2016/0...oid-pay-without-constantly-toggling-root-off/
ytsejam1138 said:
Trying using Automagisk. It's truly a set it and forget it. http://www.androidpolice.com/2016/0...oid-pay-without-constantly-toggling-root-off/
Click to expand...
Click to collapse
I may look into this.
edit, just tried works great on pokemon-go.
Sent from my R1 HD using Tapatalk
This works, per u/Howie_The_Lord on reddit:
It seems that this happens, when you ROM is preeroted, you need to delete the system/xbin/su with TWRP and let Magisk mount its own there.
Click to expand...
Click to collapse
Source: https://www.reddit.com/r/pokemongodev/comments/5265m1/037_on_rooted_android_50_with_magisk/
Though, now I get a screen on PoGo saying that my device is not compatible. At least I’m past the authentication.
stevenlb said:
This works, per u/Howie_The_Lord on reddit:
Source: https://www.reddit.com/r/pokemongodev/comments/5265m1/037_on_rooted_android_50_with_magisk/
Though, now I get a screen on PoGo saying that my device is not compatible. At least I’m past the authentication.
Click to expand...
Click to collapse
I never got this or any problems.
installed
Magisk-v6.zip
rebooted
installed
phh-superuser-17-magisk.zip
rebooted
went to playstore
installed
phh's SuperUser
installed
Magisk_Manager_v1.2.apk
installed
AutoMagisk v1.0.apk
works great.
Hi all.
I installed cm13 on my mi5 pro yesterday. Looking good so far. I only have minor issues. The first and most important is I can't swap the back and recent button. I've already got used to miui method ( back on the right, recent button on the left).
How can I change them on cm13? Unfortunately closed+gravity can't help me, because after installing them my banking app (Barclay's) thinks that my phone is rooted and closes with an FC. I've also tried the buttons on the screen option, but in this way I lose screen size, though I can change the buttons I believe.
The other small issue is that I don't really like the menu in this alphabetical order system. Can I use something else instead? Like what is in Nova launcher, just a normalenu, nothing else.
Thanks for the help in advance.
Cheers!
the first issue is related to kernel... when cm will be based on the kernel released from xiaomi, the problem will be solved. don't worry, developers are working on it
I found the a method and it is working:
https://www.androidfilehost.com/?fid=457084094631642269
GrooveHero said:
Hi all.
I installed cm13 on my mi5 pro yesterday. Looking good so far. I only have minor issues. The first and most important is I can't swap the back and recent button. I've already got used to miui method ( back on the right, recent button on the left).
How can I change them on cm13? Unfortunately closed+gravity can't help me, because after installing them my banking app (Barclay's) thinks that my phone is rooted and closes with an FC. I've also tried the buttons on the screen option, but in this way I lose screen size, though I can change the buttons I believe.
The other small issue is that I don't really like the menu in this alphabetical order system. Can I use something else instead? Like what is in Nova launcher, just a normalenu, nothing else.
Thanks for the help in advance.
Cheers!
Click to expand...
Click to collapse
For the drawer style you can change that in the launcher's settings. Long press a free spot on your home screen, then press settings and change style to "compact".
This swaps the two capacitive buttons around to xiaomi setup instead of Google
you can also find it on this url: https://store.shade.sh/mi5/ from the unofficial cm13 weekly build thread if you do not wish to download it from myself
Thank you guys its working like a miracle.
Now I have another problem, but this time it looks massive.
So my problem is that cm13 is pre rooted when you install it. Well, I have no problem with it, but unfortunately my banking app ( Barclay's) has. I can't use it, because it says rooted device not supported. I've already checked developer options, and root access is disabled, but this doesn't help, I still have issues with the app. I tried flash SuperSU+binaries from twrp, opened app after flash and use full unroot, same problem, banking app thinks my phone is still rooted. I'm thinking about trying out the slim (aosp based) ROM if I can't find any working method.
Can you guys help me with this?
Thank you one again
GrooveHero said:
Thank you guys its working like a miracle.
Now I have another problem, but this time it looks massive.
So my problem is that cm13 is pre rooted when you install it. Well, I have no problem with it, but unfortunately my banking app ( Barclay's) has. I can't use it, because it says rooted device not supported. I've already checked developer options, and root access is disabled, but this doesn't help, I still have issues with the app. I tried flash SuperSU+binaries from twrp, opened app after flash and use full unroot, same problem, banking app thinks my phone is still rooted. I'm thinking about trying out the slim (aosp based) ROM if I can't find any working method.
Can you guys help me with this?
Thank you one again
Click to expand...
Click to collapse
Root cloak via xposed maybe? Not sure if still supported though!
Harrynowl said:
This swaps the two capacitive buttons around to xiaomi setup instead of Google
you can also find it on this from the unofficial cm13 weekly build thread if you do not wish to download it from myself
Click to expand...
Click to collapse
great! thank you very much!
Harrynowl said:
Root cloak via xposed maybe? Not sure if still supported though!
Click to expand...
Click to collapse
Tried out this method, but as soon as I tried to start banking app, it closed with an fc. Yes I remember now, that was the problem few days back.
Hm...I can't think anything else..
GrooveHero said:
Tried out this method, but as soon as I tried to start banking app, it closed with an fc. Yes I remember now, that was the problem few days back.
Hm...I can't think anything else..
Click to expand...
Click to collapse
I'm unsure, sorry!
GrooveHero said:
Tried out this method, but as soon as I tried to start banking app, it closed with an fc. Yes I remember now, that was the problem few days back.
Hm...I can't think anything else..
Click to expand...
Click to collapse
Try using shade.sh's userbuilds. They are built without built in root. They are under the category "userbuilds" on his website.
Success!
I had to install aosp to to realize what's the problem here. After I did that the same problem happened.: Banking app says my phone is rooted. So I tried doing the same methods on aosp what I did on cm13, except Xposed+gravity because I knew my apps gonna FC. So I tried safe unroot apk from play store, no luck. I also tried this app the night before.
Then i thought maybe I should enable root in developer options, because yesterday morning with this was a half success, Barclays mobile banking app( debit card) said, the device is rooted, I touched ok, then it started without any problems. It was only half success, because the other app Barclaycard (credit card) didn't work, same problem: the phone is rooted. So I tried out the following, and that was the complete success:
Enabled root access for apps only in dev options than i started safe unroot from play->everything's working like a charm.
Thank you guys for help!
Hi,
I'm running stock ROM with TWRP recovery.
I've managed to successfully root my Note with Magisk.
Somehow I noticed that my device loses root after a reboot and sometimes even randomly. When I go into the custom recovery and flash Magisk 14 or 14.3 everything works fine for while, till it loses root again.
Could someone shed some light on my issue, please?
Thanks in advance.
I've also themed Magisk Manager with Substratum could that be the issue?
I'm also running stock rom, losing magisk root from time to time.
When root is lost, I'm getting a notification that "new magisk V14 is available.
Reinstalling with TWRP only to lose it again a day or two later.
You all need to change your settings in magisk manager. I had the same problem. Change your update channel to Beta. This will keep magisk 14.3 installed once you flash it in recovery after setting this. :highfive:
Are you using the hide root feature?
If so then that is probably your issue.
opasha said:
You all need to change your settings in magisk manager. I had the same problem. Change your update channel to Beta. This will keep magisk 14.3 installed once you flash it in recovery after setting this. :highfive:
Click to expand...
Click to collapse
This worked for me, thank you!!
ALEXRUSS55 said:
This worked for me, thank you!!
Click to expand...
Click to collapse
Welcome :highfive:
jpasint said:
Are you using the hide root feature?
If so then that is probably your issue.
Click to expand...
Click to collapse
What issue does this cause?
I have the same issue with last magisk beta, 16.4.. have anyone found a fix?
stiffis said:
I have the same issue with last magisk beta, 16.4.. have anyone found a fix?
Click to expand...
Click to collapse
Flash magisk v16.4, then open magisk manager disable magisk hide, for keep your root
kenpaci said:
Flash magisk v16.4, then open magisk manager disable magisk hide, for keep your root
Click to expand...
Click to collapse
Looks like that worked, thanks!
stiffis said:
Looks like that worked, thanks!
Click to expand...
Click to collapse
But it losses Android pay. Anyone with other solution to keep root and hide it?
Best regards
Webgurru
webgurru said:
But it losses Android pay. Anyone with other solution to keep root and hide it?
Best regards
Webgurru
Click to expand...
Click to collapse
Try disabling MagiskHide and re-enable it again (try also with a reboot between disabling and enabling)
stiffis said:
Try disabling MagiskHide and re-enable it again (try also with a reboot between disabling and enabling)
Click to expand...
Click to collapse
If I disable it, won't secure apps that run in the background pick up root? I'm guessing I should freeze them first or something?
hshah said:
If I disable it, won't secure apps that run in the background pick up root? I'm guessing I should freeze them first or something?
Click to expand...
Click to collapse
Try closing those apps first, I think it goes ok as long you don't start the apps yourself because most off the apps checks root at startup, but I can't guarantee you anything
Something weird has happened... I've not actually changed anything but now I tend to lose root immediately after rebooting.
I'm a technical person so whilst I say nothing has changed, I know that it probably has and I just can't remember.
I need Hide, so disabling that is not an option... I have no idea where to even start debugging this
Sent from my Samsung Galaxy Note 8 using XDA Labs
hshah said:
Something weird has happened... I've not actually changed anything but now I tend to lose root immediately after rebooting.
I'm a technical person so whilst I say nothing has changed, I know that it probably has and I just can't remember.
I need Hide, so disabling that is not an option... I have no idea where to even start debugging this
Sent from my Samsung Galaxy Note 8 using XDA Labs
Click to expand...
Click to collapse
Hi,
Same thing happening to me. Lost root soon after restart. I need it hide. Any genius mind can suggest some solution?
Best regards,
Webgurru
webgurru said:
Hi,
Same thing happening to me. Lost root soon after restart. I need it hide. Any genius mind can suggest some solution?
Best regards,
Webgurru
Click to expand...
Click to collapse
I've been posting my analysis here:
https://forum.xda-developers.com/apps/magisk/unofficial-magisk-v10-beta-built-t3521901
We have some smart guys (ie @topjohnwu @Didgeridoohan @kantjer etc) and I don't know enough to sort this so the least I can do is provide as much information as possible
hshah said:
I've been posting my analysis here:
https://forum.xda-developers.com/apps/magisk/unofficial-magisk-v10-beta-built-t3521901
We have some smart guys (ie @topjohnwu @Didgeridoohan @kantjer etc) and I don't know enough to sort this so the least I can do is provide as much information as possible
Click to expand...
Click to collapse
Any luck or help from this thread to resolve?
webgurru said:
Any luck or help from this thread to resolve?
Click to expand...
Click to collapse
Only been spamming the thread with my woes since yesterday so still early days. I'm certainly not expecting an immediate fix because this has been going on for quite some time and if it was easy, we wouldn't be having this conversation.
hshah said:
Only been spamming the thread with my woes since yesterday so still early days. I'm certainly not expecting an immediate fix because this has been going on for quite some time and if it was easy, we wouldn't be having this conversation.
Click to expand...
Click to collapse
Thanks. In my point of view this look to be a bug in Magisk. Did you tried some older version?
Hey. Are substratum overlays working on rooted S10 devices?
Considering root, full blacked out themes is the main wish i have ?
they do, no problemo!
chieco said:
they do, no problemo!
Click to expand...
Click to collapse
Gitta l root then. Thanks ?
Sent from my SM-G973F using XDA Labs
chieco said:
they do, no problemo!
Click to expand...
Click to collapse
Do you need to reboot the phone for the overlays to activate, too?
And if so, do they activate with a normal reboot or will you have to always reboot into Magisk?
CountVonKrolock said:
Do you need to reboot the phone for the overlays to activate, too?
And if so, do they activate with a normal reboot or will you have to always reboot into Magisk?
Click to expand...
Click to collapse
Yes, you need to reboot for them to apply. No, they will not show up if you boot without Magisk.
Also on the topic, you don't want to install Andromeda. That can get you in trouble and lead to overlays that may not be able to be removed without a factory reset.
patrickneil said:
Yes, you need to reboot for them to apply. No, they will not show up if you boot without Magisk.
Also on the topic, you don't want to install Andromeda. That can get you in trouble and lead to overlays that may not be able to be removed without a factory reset.
Click to expand...
Click to collapse
OK thanks for clearing that up!
I'd be fine with the rebooting but there's no way on Earth I would constantly remember to boot into recovery just to get Magisk working. This just makes it a nightmare to use the phone with root, I rather maintain the S10e in the drawer and keep using the S7. I f*cking hate Google so much... >_<
any suggestions on how to fix this? updated to the Mar 2020, extracted the boot image, patched in Magisk, flashed, and rebooted like I have done with the previous updates, however once the device is booted up all I get is a black screen! device is still responsive as pressing the power button brings up a menu allowing me to shutdown or reset. flashing a non-modded boot allows me to use the device normally again. help!
dimm0k said:
any suggestions on how to fix this? updated to the Mar 2020, extracted the boot image, patched in Magisk, flashed, and rebooted like I have done with the previous updates, however once the device is booted up all I get is a black screen! device is still responsive as pressing the power button brings up a menu allowing me to shutdown or reset. flashing a non-modded boot allows me to use the device normally again. help!
Click to expand...
Click to collapse
Did you remove all modules prior to rooting March update?
Tulsadiver said:
Did you remove all modules prior to rooting March update?
Click to expand...
Click to collapse
@Tulsadiver no, I neglected to do that since I was able to do so previously without ever having to... any idea how to do so at this point? do I need to wait for an updated image from your thread of https://forum.xda-developers.com/pixel-4-xl/how-to/magisk-modules-disabler-booting-magisk-t3990557 ?
dimm0k said:
@Tulsadiver no, I neglected to do that since I was able to do so previously without ever having to... any idea how to do so at this point? do I need to wait for an updated image from your thread of https://forum.xda-developers.com/pixel-4-xl/how-to/magisk-modules-disabler-booting-magisk-t3990557 ?
Click to expand...
Click to collapse
The old one might work but I'm making a new one for you now...
Edit: here it is
https://www.androidfilehost.com/?fid=4349826312261736126
Tulsadiver said:
The old one might work but I'm making a new one for you now...
Edit: here it is
https://www.androidfilehost.com/?fid=4349826312261736126
Click to expand...
Click to collapse
woohoo! this worked... now I need to figure out which module is fscking me... while you were making this, I followed the steps in your thread to attempt to create a boot image with core only, but mine didn't work. any idea why? regardless, thank you!!
dimm0k said:
woohoo! this worked... now I need to figure out which module is fscking me... while you were making this, I followed the steps in your thread to attempt to create a boot image with core only, but mine didn't work. any idea why? regardless, thank you!!
Click to expand...
Click to collapse
Did you put the whole folder from the zip file?
ramdisk/overlay.d
Tulsadiver said:
Did you put the whole folder from the zip file?
ramdisk/overlay.d
Click to expand...
Click to collapse
hah! I'm in idiot running around with my head cut off. I just checked, I dumped that folder into the root and not into ramdisk! anyway, turns out the culprit of my issue was your mod to increase the notifications to 7! hopefully you can make an updated mod for this update when you get some time
dimm0k said:
any suggestions on how to fix this? updated to the Mar 2020, extracted the boot image, patched in Magisk, flashed, and rebooted like I have done with the previous updates, however once the device is booted up all I get is a black screen! device is still responsive as pressing the power button brings up a menu allowing me to shutdown or reset. flashing a non-modded boot allows me to use the device normally again. help!
Click to expand...
Click to collapse
I was able to update and root, but latest Magisk stable is showing ctsprofile as false. Any ideas on how to fix this?
EVR_PR said:
I was able to update and root, but latest Magisk stable is showing ctsprofile as false. Any ideas on how to fix this?
Click to expand...
Click to collapse
I don't have the link handy, but there's a gpay module fix that should fix that for you. I'm definitely able to use Google Pay now!
dimm0k said:
I don't have the link handy, but there's a gpay module fix that should fix that for you. I'm definitely able to use Google Pay now!
Click to expand...
Click to collapse
Is it the MagiskHide Props Config module the one you're talking about?
So, I can't get Magisk to patch the boot image. It crashes every time I click let's go. I was on canary, went to the stable channel, rebooted, pushed the boot file over a few times, still nothing. Any ideas?
dimm0k said:
woohoo! this worked... now I need to figure out which module is fscking me... while you were making this, I followed the steps in your thread to attempt to create a boot image with core only, but mine didn't work. any idea why? regardless, thank you!!
Click to expand...
Click to collapse
Did you figure out which module? I have the same problem.
EVR_PR said:
I was able to update and root, but latest Magisk stable is showing ctsprofile as false. Any ideas on how to fix this?
Click to expand...
Click to collapse
Same issue, here's what I'm seeing with the ctsprofile. Magisk might need to be updated to support this feature drop.
dimm0k said:
hah! I'm in idiot running around with my head cut off. I just checked, I dumped that folder into the root and not into ramdisk! anyway, turns out the culprit of my issue was your mod to increase the notifications to 7! hopefully you can make an updated mod for this update when you get some time
Click to expand...
Click to collapse
I had some stuff running. Here you go.
Tulsadiver said:
I had some stuff running. Here you go.
Click to expand...
Click to collapse
Hey Tulsadiver, does your MagiskManager pass CTSProfile or are you using a module to fix the issue of it failing?
---------- Post added at 06:15 PM ---------- Previous post was at 06:13 PM ----------
arh2o said:
Same issue, here's what I'm seeing with the ctsprofile. Magisk might need to be updated to support this feature drop.
Click to expand...
Click to collapse
I dont have the preserve dm-verity option on nor did I have it on when I patched the boot image. Seems like that doesn't make a difference either?
EVR_PR said:
Hey Tulsadiver, does your MagiskManager pass CTSProfile or are you using a module to fix the issue of it failing?
---------- Post added at 06:15 PM ---------- Previous post was at 06:13 PM ----------
I dont have the preserve dm-verity option on nor did I have it on when I patched the boot image. Seems like that doesn't make a difference either?
Click to expand...
Click to collapse
Mine shows it as passing. I'm using beta channel.
Weiii said:
Did you figure out which module? I have the same problem.
Click to expand...
Click to collapse
for me it was the module provided by Tulsadiver to increase the notifications to 7... I'm guessing any modules that makes changes to system files might likely be the culprit. list your modules, but all I can do is take a guess as to which one it would be
dimm0k said:
for me it was the module provided by Tulsadiver to increase the notifications to 7... I'm guessing any modules that makes changes to system files might likely be the culprit. list your modules, but all I can do is take a guess as to which one it would be
Click to expand...
Click to collapse
For me it was smali patcher, i think. Not 100% sure because I booted from Tulsadrivers once I got stuck at the Google logo, this took me into safe mode inside of magisk. Every time I would reboot (after deleting the magisk cache file) with smali patcher enabled it would get stuck. After I disabled magisk safe mode I re-installed smali patcher(re-creating the zip on my desktop). After that everything booted fine and passed all safetynet checks.
EVR_PR said:
Is it the MagiskHide Props Config module the one you're talking about?
Click to expand...
Click to collapse
No, not magisk props config. I linked the module he was referring to. Make sure during installation you hit the volume up key when it prompts you to at the end because you need to let it clear the gpay data.
1dopewrx05 said:
No, not magisk props config. I linked the module he was referring to. Make sure during installation you hit the volume up key when it prompts you to at the end because you need to let it clear the gpay data.
Click to expand...
Click to collapse
I went ahead and installed the Magisk Props config module before I read your message and that fixed the problem. Apparently Google forgot to certify this specific build for ATT (the one ending 004.A1). Thank you for your help though.