In July patch the notification LED is bugged and doesn't blink, i made a fix for that problem with a magisk module.
Download: https://mega.nz/#!CQMCASZJ!6ICaOGMMK1vVmbcUcG2RyZh3q1NSw9oiDYyrw346o4s
Thanks to ChonDoe from Telegram Group.
Love you. Thanks.
Thanks bro. If you are from Latin America, write me in person to Telegram to join the group of the A1 A1 of Latinos. https://t.me/Zamb_Ale
Does it really work? I flashed the module in Magisk 16.6, rebooted phone, but LED still doesn't blink.
_mysiak_ said:
Does it really work? I flashed the module in Magisk 16.6, rebooted phone, but LED still doesn't blink.
Click to expand...
Click to collapse
Not working for me too.
Data erased
I flashed but it wiped my data, like a factory reset
Module corrupting data here :crying:
_mysiak_ said:
Does it really work? I flashed the module in Magisk 16.6, rebooted phone, but LED still doesn't blink.
Click to expand...
Click to collapse
For me work bro, idk why it's the problem exactly, I'm using magisk 16.0, a friend told me it didn't work for him and then he installed the July patch by fastboot and the module it worked.
sipollo said:
Not working for me too.
Click to expand...
Click to collapse
Sorry for the inconvenient guys, for me worked and idk why it's the problem with no work in others phones...
Thanks man..
Please create a zip for reverting back to how things were before
coolasnju1993 said:
Please create a zip for reverting back to how things were before
Click to expand...
Click to collapse
You can just uninstall it directly from Magisk Manager.
dgadelha said:
You can just uninstall it directly from Magisk Manager.
Click to expand...
Click to collapse
Only if i had the option to. The thing is that after installing and rebooting the module cannot be seen in the magisk manager
Notification light issue
Hi,
My mi a1 notification light not blinking and always on for notification after July update.please let me know the solution..
any other solutions without root?
BunkerBert said:
any other solutions without root?
Click to expand...
Click to collapse
Try waiting for August update that maybe will fix it (and maybe break another thing).
Related
Just downloaded the game not a fan tho, Wanted to try. I'm on RR 7.1.1 Unified builds and magisk enabled. The game seem to be force closing all the time. A red Nintendo screen splashes and fades away. I'm not t=sure the problem is with the ROM or app itself. I tried clearing cache,Rebooting and all.
Anyone facing the same issue?
Anyone knows how to fix?
app is good. i got it on my op3 stock and it works fine. looks like its an rom related problem.
doesn't work on my OnePlus 2 with RR 7.1.1
sasanksai said:
Just downloaded the game not a fan tho, Wanted to try. I'm on RR 7.1.1 Unified builds and magisk enabled. The game seem to be force closing all the time. A red Nintendo screen splashes and fades away. I'm not t=sure the problem is with the ROM or app itself. I tried clearing cache,Rebooting and all.
Anyone facing the same issue?
Anyone knows how to fix?
Click to expand...
Click to collapse
had the same issue , turns out it's failing a safetynet issue .
install magisk SU to pass safetynet issue and it should work fine.
See my sig, works with that system.
pawanraju said:
had the same issue , turns out it's failing a safetynet issue .
install magisk SU to pass safetynet issue and it should work fine.
Click to expand...
Click to collapse
Yes did that too. My magisk passed safetynet also i tired hiding magisk for mario. Didn't help tho
sasanksai said:
Just downloaded the game not a fan tho, Wanted to try. I'm on RR 7.1.1 Unified builds and magisk enabled. The game seem to be force closing all the time. A red Nintendo screen splashes and fades away. I'm not t=sure the problem is with the ROM or app itself. I tried clearing cache,Rebooting and all.
Anyone facing the same issue?
Anyone knows how to fix?
Click to expand...
Click to collapse
Sam here
its a problem with supersu root, if you use Magisk (you can hide it inside official app) won't have problems. I can play to Pokemon GO and SM Run without problem using it
MasterJack1697 said:
Sam here
Click to expand...
Click to collapse
enter in Magisk app - Settings - Magisk Hide
enable it and enjoy the game
Spector_Prophet said:
its a problem with supersu root, if you use Magisk (you can hide it inside official app) won't have problems. I can play to Pokemon GO and SM Run without problem using it
enter in Magisk app - Settings - Magisk Hide
enable it and enjoy the game
Click to expand...
Click to collapse
Same with that, doesn't work..
I think it would be interesting to kow if ppl who say it fails to work use OxygenOS or something else. My configuration works for PKMN Go and Mario Run without ANY problems at all.
ManuBBXX said:
Same with that, doesn't work..
Click to expand...
Click to collapse
are you using custom rom? because some roms have root included and you manage it in developer options.
With Magisk configurated and included root turn off, you should play without problems
Spector_Prophet said:
are you using custom rom? because some roms have root included and you manage it in developer options.
With Magisk configurated and included root turn off, you should play without problems
Click to expand...
Click to collapse
I use latest BJRR RR from Eliminater, wich includes by default magisk
Rooted systemless with magisk, safetyCheck pass, magisk hide enabled !
ManuBBXX said:
I use latest BJRR RR from Eliminater, wich includes by default magisk
Rooted systemless with magisk, safetyCheck pass, magisk hide enabled !
Click to expand...
Click to collapse
ouch..... I haven't more ideas
hope someone can help you
How to install Magisk on RR 7.1.1?
Hi! I have a one plus one and I am running Lineage OS 14.1-20170130 (7.1.1) and I can't play aswell.
I get the red Nintendo splash screen and it closes.
Running latest lineage weekly with zenith EAS 004 kernel and magisk and no issues whatsoever, I was able to start up the game and make a profile and play without any craziness
Update the magisk to latest version11.6 ! It helped me....
Hope it helps you. Thanks!
Yep, just tried with magisk and it worked. I found it on this reddit just after my previous post. At the r/LineageOS subreddit (the name of the post is "Super Mario Run came out about minutes ago, but crashes on start (Kenzo)" ). (I can't post urls yet)
Doesn't work on latest RR with latest magisk, safetyCheck pass and hide too.
I was on my previous install with latest RR AND superSU
I dirty flashed the ROM to remove superSU and work root with magisk
Is dirty flash is enough to remove superSU ?
ManuBBXX said:
Same with that, doesn't work..
Click to expand...
Click to collapse
-Deleted-
Can anyone confirm if Magisk root works with the 8.1 release?
It Works
Its working but when you reboot the device I'm getting the "there's an internal problem with your device " which has to do with a mismatch between the Vendor and System Partitions. Only happens after flashing the 14.5(1456) Build either from TWRP or using the boot.img patcher in Magisk Manager. Not sure how to fix this error but otherwise everything is working.
Edit: Picture for reference
Edit 2: Root, safetynet pass, and modules are all working just an annoying error message on boot.
Edit 3: Known issue with the 1456 build of Magisk. Developers are already aware of it. Information below.
topjohnwu said:
The additional avb-verity removal from DTBO on the Pixel 2 devices results in a scary pop-up. No need to worry here, it's Google warning you that your vendor partition doesn't work as expected. I decided to strip off avb-verity to make modifications to the vendor partition possible, as people tend to modify their partitions a lot, and not sure if this might save a few soft brick devices.... As the old dm-verity and avb-verity works so different, it is very difficult for me to come up with a proper way that doesn't complicate things on the user side.
Click to expand...
Click to collapse
Itachisasuke said:
Its working but when you reboot the device I'm getting the "there's an internal problem with your device " which has to do with a mismatch between the Vendor and System Partitions. Only happens after flashing the 14.5(1456) Build either from TWRP or using the boot.img patcher in Magisk Manager. Not sure how to fix this error but otherwise everything is working.
Click to expand...
Click to collapse
Yep, Magisk works....unfortunately the error upon boot is there. Prior to Magisk, 8.1 didn't show the error. After the Magisk flash, the error always pops up upon start up.
Guess I'll wait with re-rooting then.
Colchiro said:
Guess I'll wait with re-rooting then.
Click to expand...
Click to collapse
Why, it still works fine. Just ignore the message :good:
Badger50 said:
Why, it still works fine. Just ignore the message :good:
Click to expand...
Click to collapse
Does it still pass Safetynet?
MrBrady said:
Does it still pass Safetynet?
Click to expand...
Click to collapse
Yup :good:
The error is just an annoyance, you still have root and pass safety net. I used Magisk on the last Beta build and got the same error It did not impact anything.
Sav_Droid said:
Yep, Magisk works....unfortunately the error upon boot is there. Prior to Magisk, 8.1 didn't show the error. After the Magisk flash, the error always pops up upon start up.
Click to expand...
Click to collapse
14.4 doesn't show the error message, but fails the SafetyNet check. Android Pay still works, though.
Do you need to flash stock 8.0 boot.img before applying 8.1 OTA?
swooperstar said:
Do you need to flash stock 8.0 boot.img before applying 8.1 OTA?
Click to expand...
Click to collapse
Yes I would def uninstall magisk before going on to 8.1 and flash boot.img to both slots
lucky_strike33 said:
Yes I would def uninstall magisk before going on to 8.1 and flash boot.img to both slots
Click to expand...
Click to collapse
I didn't.
Sideloading the new OTA will overwrite the patched image
Just curious, but wondering why people are in such a rush to install 8.1. With all of the contact sync issues oh, this would drive me absolutely crazy. I might just wait until January to update unless there is a quick fix.
Cowbell_Guy said:
Just curious, but wondering why people are in such a rush to install 8.1. With all of the contact sync issues oh, this would drive me absolutely crazy. I might just wait until January to update unless there is a quick fix.
Click to expand...
Click to collapse
Probably just because we can. We flashaholics gotta have our fix! Everything is working fine on my end. Then again, all my contacts are synced through Gmail :good:
Cowbell_Guy said:
Just curious, but wondering why people are in such a rush to install 8.1. With all of the contact sync issues oh, this would drive me absolutely crazy. I might just wait until January to update unless there is a quick fix.
Click to expand...
Click to collapse
Contact sync issues? Never had that before.. what's the issue exactly? Not getting all of them or all the info?
You can get rid of the error message by rooting with Magisk, then uninstalling Magisk Manager, reflashing the stock (or your kernel's) dtbo, then rebooting and reinstalling Magisk Manager. Passes SafetyNet and have full root.
jbarcus81 said:
Contact sync issues? Never had that before.. what's the issue exactly? Not getting all of them or all the info?
Click to expand...
Click to collapse
Some Google contacts aren't syncing since installing the 8.1 official release. I have this issue and so do many others. There's a thread taking about it in this section already. It effected almost all of the contacts I talk to the most.
There is a workaround. Go into the web interface of Google contacts on your computer and edit the contract to reminder their profile URL and it forces the sync to go through for that contact. I did this for my 10 most frequent contacts. However, this would be a nightmare to do for every contact.
Google development is aware of the issue and working on a fix.
---------- Post added at 03:27 AM ---------- Previous post was at 03:27 AM ----------
gettingerr said:
You can get rid of the error message by rooting with Magisk, then uninstalling Magisk Manager, reflashing the stock (or your kernel's) dtbo, then rebooting and reinstalling Magisk Manager. Passes SafetyNet and have full root.
Click to expand...
Click to collapse
What's "dtbo"?
Yeah I did this too and bam,,,error message on boot gone LOL,,,just have to stay with Magisk Manager 5.4.0 and not update through Magisk. But it all works, safety net pass.
gettingerr said:
You can get rid of the error message by rooting with Magisk, then uninstalling Magisk Manager, reflashing the stock (or your kernel's) dtbo, then rebooting and reinstalling Magisk Manager. Passes SafetyNet and have full root.
Click to expand...
Click to collapse
Archangel said:
Yeah I did this too and bam,,,error message on boot gone LOL,,,just have to stay with Magisk Manager 5.4.0 and not update through Magisk. But it all works, safety net pass.
Click to expand...
Click to collapse
I actually was curious what would happen if I used the latest Magisk Manager, and nothing happened. So I am using the latest. No error and no issues that I can note. Except maybe installing modules if you're into that sort of thing.
---------- Post added at 05:07 AM ---------- Previous post was at 05:06 AM ----------
sn0warmy said:
What's "dtbo"?
Click to expand...
Click to collapse
No clue. http://lmgtfy.com/?q=dtbo
I didn't read the links but maybe something there can explain it.
I found the smart lock did not work after root, no matter using beta magisk 14.5 or stable 14. I would like to make sure if this is a problem of my own, or a general case, so that I can decide whether to report this to the developers. Thank you.
I'm using beta 14.5 and when I open smart lock it asks for a pin and then shows a blank white screen. No options to add devices. I've been using face unlock so I didn't notice until I checked after seeing this.
Try this.
Oneplus forums
It worked for me.
shadeau said:
I'm using beta 14.5 and when I open smart lock it asks for a pin and then shows a blank white screen. No options to add devices. I've been using face unlock so I didn't notice until I checked after seeing this.
Click to expand...
Click to collapse
Exactly the problem I have, so this should be a problem of magisk. I guess magisk is not compatible with 5t now, some other people report they have problem with their wifi after root (I also found wifi is slower).
I tried supersu as well, but it can cause a battery drain. So there is no perfect root for 5t till now.
Beaster said:
Try this.
Oneplus forums
It worked for me.
Click to expand...
Click to collapse
It will become blank again after reboot... It's perfect if I uninstall magisk or use supersu instead.
simonand said:
It will become blank again after reboot... It's perfect if I uninstall magisk or use supersu instead.
Click to expand...
Click to collapse
I second that, it turns blank again after reboot. or sometime during use. So irritating.
I just found out that Magisk itself doesn't seem to be the problem.
I did a fresh install, installed magisk without any problem. The problem started after installing a module from within Magisk...
After that Smart Lock blanked out and removing the module doesn't change anything.
Bart1981 said:
I just found out that Magisk itself doesn't seem to be the problem.
I did a fresh install, installed magisk without any problem. The problem started after installing a module from within Magisk...
After that Smart Lock blanked out and removing the module doesn't change anything.
Click to expand...
Click to collapse
What module did you install? I seem to get this problem even with out magisk. Maybe twrp is the cause?
tyrone1 said:
What module did you install? I seem to get this problem even with out magisk. Maybe twrp is the cause?
Click to expand...
Click to collapse
I guess I was mistaken... A later attempt I also got a blank screen after a while.
Not shure why. In the beginning it seems all ok also after a couple of reboots, but then after a certain time and a reboot it's there. again.
I tried uninstalling some modules to see if they were the cause I updated magisk to the beta channel in an attempt to fix it I also can't install new modules either. As far as I can tell I still have root as I have many things that rely on it. The logs are of the first time it happened I rebooted and it failed again giving me the second log. I reinstalled the 15.3 version of magisk and attempted to install a module it failed giving me the third log and the screenshot is after I upgraded magisk to the beta channel. @topjohnwu any idea what might be causing this I saw a post from a few months back but it didn't have a solution
is no one else having this issue?
razgriz1234 said:
is no one else having this issue?
Click to expand...
Click to collapse
I have the same issue. I have been flashing them from TWRP for now until it gets resolved.
CyberpodS2 said:
I have the same issue. I have been flashing them from TWRP for now until it gets resolved.
Click to expand...
Click to collapse
how do you flash them if they are supposed to be systemless? sorry if its a stupid question i still dont completely understand magisk as its the first phone ive had it on
solved with magisk 16.0 version
Hey guys.
I would like to ask you, if it's possible to use bank apps + root on this device?
I tried it yesterday several times and couldn't get it to work. On my previous phones if worked perfectly.
What I did:
- unlock OP7T
- root with self-made Magisk patched boot
- hide Magisk Manager itself
- hide the bank app
It worked even yesterday on my other phone, before I switched to 7T.
I'm wondering why it doesn't work on 7T and maybe there is some fix for it?
What happens when you try the bank apps? I've used several (US Bank, Chase, Discover, etc.), and haven't had any issues
It could be detecting another root app or even a folder associated with a root app (Pokemon Go does this with the Magisk Folder). Start digging through your storage to see if there's anything that might be root related.
Kollachi said:
Hey guys.
I would like to ask you, if it's possible to use bank apps + root on this device?
I tried it yesterday several times and couldn't get it to work. On my previous phones if worked perfectly.
What I did:
- unlock OP7T
- root with self-made Magisk patched boot
- hide Magisk Manager itself
- hide the bank app
It worked even yesterday on my other phone, before I switched to 7T.
I'm wondering why it doesn't work on 7T and maybe there is some fix for it?
Click to expand...
Click to collapse
Have you installed magisk with another package name (4th voice on settings)?
giacomowrc said:
Have you installed magisk with another package name (4th voice on settings)?
Click to expand...
Click to collapse
Yep did it.
MansonDroid said:
It could be detecting another root app or even a folder associated with a root app (Pokemon Go does this with the Magisk Folder). Start digging through your storage to see if there's anything that might be root related.
Click to expand...
Click to collapse
Nah. Seems to be the same as my other device.
adobrakic said:
What happens when you try the bank apps? I've used several (US Bank, Chase, Discover, etc.), and haven't had any issues
Click to expand...
Click to collapse
Could your try the app i used? Does it work for you?
https://play.google.com/store/apps/details?id=com.starfinanz.mobile.android.pushtan
S-pushTan works fine with root, just tried.
Lupus77 said:
S-pushTan works fine with root, just tried.
Click to expand...
Click to collapse
Strange. Don't get it, why it's not working for me.
Did you try hiding them using Magisk Hide?
cucumbersmell said:
Did you try hiding them using Magisk Hide?
Click to expand...
Click to collapse
Yeah sure.
Try restoring Magisk Manager via Settings and hide Magisk Manager again.
Lupus77 said:
Try restoring Magisk Manager via Settings and hide Magisk Manager again.
Click to expand...
Click to collapse
Did that too. But something doesn't work correctly.
Rootchecker says I'm rooted and also magisk says installed. Also the apps have root rights in magisk. But root doesn't work lol.
I have completely uninstalled magisk and reflashed it again. Root works now. But magisk hide is broken. Maybe OxygenOS is the reason.
Kollachi said:
Did that too. But something doesn't work correctly.
Rootchecker says I'm rooted and also magisk says installed. Also the apps have root rights in magisk. But root doesn't work lol.
I have completely uninstalled magisk and reflashed it again. Root works now. But magisk hide is broken. Maybe OxygenOS is the reason.
Click to expand...
Click to collapse
Oxygen os cant be the reason when its working for everyone else....start everything again afresh. Something you are messing up...i would restore the phone with msmdownload tool to be sure everything is back to normal then start everythung again
v.konvict said:
Oxygen os cant be the reason when its working for everyone else....start everything again afresh. Something you are messing up...i would restore the phone with msmdownload tool to be sure everything is back to normal then start everythung again
Click to expand...
Click to collapse
Yep I thought the same to start with MSMTool.
I never used OxygenOS also on the other OnePlus devices. That's why I thought there is something wrong with it.
BTW which version of magisk do you guys use?
Here it works great. Have hide my bankapp in magisk, than repack magisk have give it the name "funny" now my bankapp works great. I use the latest Canary magisk