Related
Hey guys,
Just wanted to know how many of you ditched the Xposed on marshmallow for the latest 7.1.1 Android based oxygenos?
Since we don't know when nougat will be supported by xposed, is staying on marshmallow worth it?
Even though most of the modules I use are more or less esthetical, there's one thing I can't live without - youtube background playback and ad block.
Share your thoughts!
Xposed over any OS without Xposed. I have never even flashed Nouget because I know its just a waste of time for me. Ive been on cm13 since the day it came out. DEC 11 2016.
If all you need is the youtube modules, there's modded youtube apps out now with adblock and background playback. Check it out here.
I've also packaged the app in a convenient Magisk module, which you can find here.
It works exactly like the xposed-modified YouTube app, but it works on Nougat.
Anova's Origin said:
If all you need is the youtube modules, there's modded youtube apps out now with adblock and background playback. Check it out here.
I've also packaged the app in a convenient Magisk module, which you can find here.
It works exactly like the xposed-modified YouTube app, but it works on Nougat.
Click to expand...
Click to collapse
Hey Anova, what is this Magisk thingy you're talking about?
Also... For me The most important is gravitybox then come youtube modules and mock mock locations.
You think it's worth the upgrade? I personally never had a phone that would get updates so quickly or even at all. So I have no idea what to expect.. Would I have to reroot, reinstall recovery or it's all a piece of cake and only the exposed won't affect anything? Lemme know.
Crishien said:
Hey Anova, what is this Magisk thingy you're talking about?
Also... For me The most important is gravitybox then come youtube modules and mock mock locations.
You think it's worth the upgrade? I personally never had a phone that would get updates so quickly or even at all. So I have no idea what to expect.. Would I have to reroot, reinstall recovery or it's all a piece of cake and only the exposed won't affect anything? Lemme know.
Click to expand...
Click to collapse
Magisk is a framework that allows you to make temporary changes to your /system partition at boot, without actually modifying the partition. It works by superimposing user-defined changes to files in /system during boot; changes are reverted to their stock state afterwards. These user-defined changes are loaded into Magisk through Magisk modules. While a lot of people may think it's similar to Xposed, they're really nothing alike. I mentioned Magisk for the YouTube app because it is merely convenient. You could manually replace the YouTube APK in system without any additional software, but Magisk will do it for you while applying all the correct permissions, etc. As a bonus, Magisk also includes its own rooting method that works, for the most part, as well as SuperSU. This means that you can flash only Magisk to root your phone (flashing SuperSU is optional and is really based on personal preference, Magisk will work with SuperSU if you flash that first).
Because of what Magisk is and how it works, it is not able to modify your device in the same way that Xposed can. This means that mods like gravitybox and mock mock locations cannot be implemented with Magisk. Technically, all Magisk modules can be installed without Magisk by manually editing/replacing things in the /system partition. What is special about it is that Magisk does these things systemlessly, meaning that (with the proper configurations), you can modify /system without triggering safetynet.
For the modified YouTube app I was talking about, that was actually modded and compiled as a stand-alone APK by someone on XDA. It does not alter your current YouTube app, but rather outright replaces it.
As for upgrading to Nougat, it's really up to personal choice. I personally never used Xposed for anything other than YouTube Adaway and Background Playback, and to top it off I rarely use YouTube on my phone anyways so upgrading was an easy choice for me. If you do end up wanting to upgrade, do the following:
1) Download the full ROM of whatever version of OOS you want to use (4.1.0 is the latest, on Android 7.1.1). Do not use the "Upgrade Phone" option in settings if you are already rooted or have modified anything in your /system partition, as it will cause problems.
2) Flash the full zip in TWRP, wipe cache/Dalvik, then immediately flash the latest Magisk.zip (from the main Magisk thread on XDA)
3) Boot, then download Magisk Manager from the Play Store
At this point, Magisk will have been fully installed and your phone should be rooted. You can confirm through the Magisk Manager app
Anova's Origin said:
Magisk is a framework that allows you to make temporary changes to your /system partition at boot, without actually modifying the partition. It works by superimposing user-defined changes to files in /system during boot; changes are reverted to their stock state afterwards. These user-defined changes are loaded into Magisk through Magisk modules. While a lot of people may think it's similar to Xposed, they're really nothing alike. I mentioned Magisk for the YouTube app because it is merely convenient. You could manually replace the YouTube APK in system without any additional software, but Magisk will do it for you while applying all the correct permissions, etc. As a bonus, Magisk also includes its own rooting method that works, for the most part, as well as SuperSU. This means that you can flash only Magisk to root your phone (flashing SuperSU is optional and is really based on personal preference, Magisk will work with SuperSU if you flash that first).
Because of what Magisk is and how it works, it is not able to modify your device in the same way that Xposed can. This means that mods like gravitybox and mock mock locations cannot be implemented with Magisk. Technically, all Magisk modules can be installed without Magisk by manually editing/replacing things in the /system partition. What is special about it is that Magisk does these things systemlessly, meaning that (with the proper configurations), you can modify /system without triggering safetynet.
For the modified YouTube app I was talking about, that was actually modded and compiled as a stand-alone APK by someone on XDA. It does not alter your current YouTube app, but rather outright replaces it.
As for upgrading to Nougat, it's really up to personal choice. I personally never used Xposed for anything other than YouTube Adaway and Background Playback, and to top it off I rarely use YouTube on my phone anyways so upgrading was an easy choice for me. If you do end up wanting to upgrade, do the following:
1) Download the full ROM of whatever version of OOS you want to use (4.1.0 is the latest, on Android 7.1.1). Do not use the "Upgrade Phone" option in settings if you are already rooted or have modified anything in your /system partition, as it will cause problems.
2) Flash the full zip in TWRP, wipe cache/Dalvik, then immediately flash the latest Magisk.zip (from the main Magisk thread on XDA)
3) Boot, then download Magisk Manager from the Play Store
At this point, Magisk will have been fully installed and your phone should be rooted. You can confirm through the Magisk Manager app
Click to expand...
Click to collapse
Thanks for such a detailed description of everything! You're the best! I seriously decided to upgrade tomorrow.
Just last couple questions before I do... Should I delete anything? Like xposed itself with it's modules, or does the system upgrade wipe everything itself? Should I perform any backups other than usual titanium ones?
Thanks in advance
Crishien said:
Thanks for such a detailed description of everything! You're the best! I seriously decided to upgrade tomorrow.
Just last couple questions before I do... Should I delete anything? Like xposed itself with it's modules, or does the system upgrade wipe everything itself? Should I perform any backups other than usual titanium ones?
Thanks in advance
Click to expand...
Click to collapse
You should delete the Xposed modules prior to updating, as they are saved as user apps and will not be wiped with an upgrade. Delete the Xposed framework app as well for the same reason. Updating should erase all of the background stuff that the Xposed originally installed in /system. Take a nandroid prior to updating just in case.
Anova's Origin said:
You should delete the Xposed modules prior to updating, as they are saved as user apps and will not be wiped with an upgrade. Delete the Xposed framework app as well for the same reason. Updating should erase all of the background stuff that the Xposed originally installed in /system. Take a nandroid prior to updating just in case.
Click to expand...
Click to collapse
Thanks again, mate!
Is this the one I should download? https://forum.xda-developers.com/oneplus-3t/how-to/rom-oos4-0-nougat-op3t-leaked-t3523482
Crishien said:
Thanks again, mate!
Is this the one I should download? https://forum.xda-developers.com/oneplus-3t/how-to/rom-oos4-0-nougat-op3t-leaked-t3523482
Click to expand...
Click to collapse
Yes, that will work. OnePlus has not yet released the official zip through their website at this time, otherwise I would advise you to use the official zip.
Anova's Origin said:
Yes, that will work. OnePlus has not yet released the official zip through their website at this time, otherwise I would advise you to use the official zip.
Click to expand...
Click to collapse
Great, thank you. Imma let you know how it goes later today.
Anova's Origin said:
Yes, that will work. OnePlus has not yet released the official zip through their website at this time, otherwise I would advise you to use the official zip.
Click to expand...
Click to collapse
Not sure if I did anything wrong or I'm just impatient... But I flashed the update successfully and deleted dalvik. But got stuck at boot logo. Been hanging like this for 15 minutes, phone got hot and drained half its juice. So I reverted for now.... I'll try again at home with a charger... ?
954wrecker said:
Xposed over any OS without Xposed. I have never even flashed Nouget because I know its just a waste of time for me. Ive been on cm13 since the day it came out. DEC 11 2016.
Click to expand...
Click to collapse
what can xposed do that you actually need that you can't do with magisk?
EuEra said:
what can xposed do that you actually need that you can't do with magisk?
Click to expand...
Click to collapse
I don't think magisk can handle what xposed can handle.
954wrecker said:
I don't think magisk can handle what xposed can handle.
Click to expand...
Click to collapse
Indeed I will miss gravitybox. But if there is any other way to make my buttons do what I like which is (on the left - menu button with double tap for previous app/ home is home and recents on long press / right is back.)
Other than that it's all purely visual enhancement such as perfect color bar, media visualizer, and ****.
On the other hand I've just encountered a slight difficulty... Magisk won't work properly if I had Supersu previously installed, right?
Crishien said:
Indeed I will miss gravitybox. But if there is any other way to make my buttons do what I like which is (on the left - menu button with double tap for previous app/ home is home and recents on long press / right is back.)
Other than that it's all purely visual enhancement such as perfect color bar, media visualizer, and ****.
On the other hand I've just encountered a slight difficulty... Magisk won't work properly if I had Supersu previously installed, right?
Click to expand...
Click to collapse
What are you gaining if I may ask? I have never tried 7.0 or magisk because I see ZERO benefit and Id lose all my favorite modules.
954wrecker said:
What are you gaining if I may ask? I have never tried 7.0 or magisk because I see ZERO benefit and Id lose all my favorite modules.
Click to expand...
Click to collapse
That's what I wanna find out. I wanna see what's the new Android about. And I'm sure rovo will find a solution soon. And we will see xposed for nougat.
GravityBox is terrible and has slowed down every phone it's ever been put on (from my experience).
Xposed is a hack and it's shameful how it's holding back advancement.
Nougat > any hack
MattBooth said:
GravityBox is terrible and has slowed down every phone it's ever been put on (from my experience).
Xposed is a hack and it's shameful how it's holding back advancement.
Nougat > any hack
Click to expand...
Click to collapse
My phone is just as fast with xposed as it is without. All my apps work perfectly so I say any OS with Xposed is > Nougat
954wrecker said:
I don't think magisk can handle what xposed can handle.
Click to expand...
Click to collapse
Most of that is either completely unnessecary, pointless, or magisk can do it if people start developing for it. I have none of it (except no ads on youtube and the ability to turn off the screen) and i am completely fine. I think you tell yourself you need all that stuff but you actually don't, staying versions behind on the OS for it seems stupid.
954wrecker said:
My phone is just as fast with xposed as it is without. All my apps work perfectly so I say any OS with Xposed is > Nougat
Click to expand...
Click to collapse
Well that's your opinion and you're entitled to it, but I've noticed the total opposite across several devices. I always try Xposed on a new phone and I always massively dislike the way it works. Intercepting code that was not supposed to be intercepted just adds overhead. There's a good reason AOSP devs will refuse to look at any bug report that has Xposed in the logs.
EDIT:
Anyway, the battery savings from Nougat are too good to pass over. The only thing I need to customise on my phone is having the Google Dialer, and AdAway, whilst still keeping SafetyNet as passing, which Magisk does perfectly.
EuEra said:
Most of that is either completely unnessecary, pointless, or magisk can do it if people start developing for it. I have none of it (except no ads on youtube and the ability to turn off the screen) and i am completely fine. I think you tell yourself you need all that stuff but you actually don't, staying versions behind on the OS for it seems stupid.
Click to expand...
Click to collapse
Exactly, unless you use every setting on GravityBox then it's not entirely necessary, yet even if those functions are off or there are features of GravityBox you don't use, their code is still run. The bigger it gets the more the overhead there is. If you don't use, say, the network speed monitor, it's hook is still active. I could be wrong, but last time I dabbled with Xposed, this was the case.
If anything, smaller more granular modules would be better for GB. One module for network speed. One module for changing the on-screen buttons, etc. That way you only install modules that you use, rather than a whole library of them where you might only use 2-3 of the actual features.
At least 2 of my Apps refuse to start. One is my banking app and they do not offer any other way of interaction.
The problem is that the phone in fact is not rooted! It's just "OEM unlocked" to be prepared for root (which I need for E.g. titanium backup, but only maybe once a month).
Please give me a way out of this vicious circle!
I cannot remove the OEM unlock because it requires full wipe every time. Or is there a way?
Or what can I possibly tell the App Provider to improved their Code so that Oneplus phone state is being recognized (more) correctly?
Any help would be greatly appreciated.
Use Magisk I guess? Use it to hide root from that app.
Reeb_Lam said:
Use Magisk I guess? Use it to hide root from that app.
Click to expand...
Click to collapse
In fact I already flashed an official image and still (with no zip installed via TWRP) I'm getting refusals from these apps.
So for sure some apps decide from something else then simply an installed "root" manager or the installed "su" binaries.
What else could they decide from? "OEM unlock" was my first guess (and it would also be the worst, because as far as I know it can't be "hidden" temporarily, or can it?), but maybe there are other settings. Does anybody know more?
ako673de said:
In fact I already flashed an official image and still (with no zip installed via TWRP) I'm getting refusals from these apps.
So for sure some apps decide from something else then simply an installed "root" manager or the installed "su" binaries.
What else could they decide from? "OEM unlock" was my first guess (and it would also be the worst, because as far as I know it can't be "hidden" temporarily, or can it?), but maybe there are other settings. Does anybody know more?
Click to expand...
Click to collapse
You need to do some reading about Safetynet. If you're OEM unlocked you fail Verified Boot checks. Most custom Kernels include a bypass for this. Magisk alone should also work. I think you missed one important step:
Open Play Store Settings. Scroll down. It says 'Uncertified' at the bottom, right? Now install and set up Magisk. Go to system App Settings and clear Data and Cache for Play Store. Return to the Play Store Settings and scroll down. Now it should say 'Certified'. It might not be immediate, but it will happen. Now your Banking Apps work.
If you don't want, or have no luck with Magisk, simply flash a Custom Kernel that bypasses Verified Boot, and works with OOS.
Simple.
Thank you. That was for sure a major part of the overall issue. Unfortunately it didn't yet fix it. I'm now certified in play store and magisk succeeds with both safety net checks (which however it also did before). And root is disabled in magisk. dm-verity does not show the warning during Boot and the Check itself should be disabled (I followed the recommendation in another Thread to Patch the Boot Image).
Anything else you can imagine?
ako673de said:
Thank you. That was for sure a major part of the overall issue. Unfortunately it didn't yet fix it. I'm now certified in play store and magisk succeeds with both safety net checks (which however it also did before). And root is disabled in magisk. dm-verity does not show the warning during Boot and the Check itself should be disabled (I followed the recommendation in another Thread to Patch the Boot Image).
Anything else you can imagine?
Click to expand...
Click to collapse
Link to other Thread?
I don't know Magisk but are you hiding Root from your Banking App? Have you cleared Data and Cache for the Banking App since getting Certified?
First my phone did not Boot any more after installing superSU. Fixed that by patching Boot.img (to disable dm-verity) according to this thread: https://forum.xda-developers.com/oneplus-3t/how-to/disable-dm-verity-force-encryption-op3t-t3688748
Now data and cache of all (now) 3 affected Apps has been cleared and Magisk is configured to be hidden for them, but still no change.
However, in Magisk there is the "extended" option "AVB 2.0/keep dm-verity", which is unticked. I'm not sure, should I try to set it?
Any other idea?
ako673de said:
Any other idea?
Click to expand...
Click to collapse
Nope. If Play Store says Certified you should be good to go. I can only imagine it's a Magisk issue. Post screenshots of your config and let the Magisk experts pick through them. Maybe there's something not set up correctly.
ako673de said:
First my phone did not Boot any more after installing superSU. Fixed that by patching Boot.img (to disable dm-verity) according to this thread: https://forum.xda-developers.com/oneplus-3t/how-to/disable-dm-verity-force-encryption-op3t-t3688748
Now data and cache of all (now) 3 affected Apps has been cleared and Magisk is configured to be hidden for them, but still no change.
However, in Magisk there is the "extended" option "AVB 2.0/keep dm-verity", which is unticked. I'm not sure, should I try to set it?
Any other idea?
Click to expand...
Click to collapse
Hide Magisk Manager. I had to do that to get my banking app to work.
Edit: you may need to reboot after hiding Magisk Manager and clear you banking app's data before it works.
Sent from my OnePlus3T using XDA Labs
Thank you, indeed that WORKED! Well, at least for 2 out of 3 Apps. I think I can tell which one: "HVB banking". Maybe could somebody cross-check this one on his/her phone?
After firmware update to OOS 5.0.5 I now have the problem that my PlayStore can no longer be convinced in any way to show that it's certified. But interestingly my banking Apps work (currently really no root app installed). I even waited for one day because earlier in this thread somebody mentioned that it might take awhile. Is there anything special I need to care about under the new OS version?
ako673de said:
After firmware update to OOS 5.0.5 I now have the problem that my PlayStore can no longer be convinced in any way to show that it's certified. But interestingly my banking Apps work (currently really no root app installed). I even waited for one day because earlier in this thread somebody mentioned that it might take awhile. Is there anything special I need to care about under the new OS version?
Click to expand...
Click to collapse
Did you reflash custom kernel after update?
I'm not using any. What I did right after the update is to disable dm-verity (with a patched boot.img), like I did last time. But magisk is not yet re-installed because I wanted to see at least once the HypoVereinsbank App working, which it in fact does (different to last time when the phone was not rooted as well, and the store not certified!).
ako673de said:
But magisk is not yet re-installed
Click to expand...
Click to collapse
That's why... You can't pass the ctsProfile check if your bootloader is unlocked, and if you can't pass the ctsProfile check the Play Store won't be certified. You need Magisk for that...
Now I'm getting confused. The initial mail of this thread explains the situation as it was when I opened this thread:
--> Original ROM, no root, and banking apps didn't work <--
The advice to clear data of the PlayStore immediately brought the PlayStore back to "certified".
This is clearly in contrast to what you're saying now.
I can imagine only one reason: Maybe the older PlayStore had a bug and therefore was able to "certify" even with unlocked bootloader?
Sidenote: My main intention to do the firmware upgrade was that the "safety net checks" in Magisk suddenly stopped working one day (with the error message "invalid response", most probably you know what I'm talking about, I've read some comments from you on this issue). Therefore it's maybe really not too unlikely that Google has changed something very basic. Could you please confirm?
Edit: Now magisk is back, version 16.7, and in fact PlayStore is back to "certified" AND now even the HypoVereinsbank App works. Just one thing remains: magisk safety net check still says "invalid response" (after it downloaded some "FOSS" code, which it didn't do last time, when it was still working).
ako673de said:
Edit: Now magisk is back, version 16.7, and in fact PlayStore is back to "certified" AND now even the HypoVereinsbank App works. Just one thing remains: magisk safety net check still says "invalid response" (after it downloaded some "FOSS" code, which it didn't do last time, when it was still working).
Click to expand...
Click to collapse
https://www.didgeridoohan.com/magisk/MagiskHide#hn_The_response_is_invalid
Sorry, now comes a probably often asked question: do I need the safetynet check option in magisk for something real? Or do the alternative apps fulfill all possible needs? What are these needs? Isn't that exactly what the PlayStore does to determine "certified"?
After quite some months of absolutely no "root" problems with any of my apps, since today o2banking again doesn't work.
I tried to update Magisk, but after update of the Magisk manager app to v7.1.1(203) it reports that Magisk is not installed at all, and any update of Magisk itself resulted in just the same. So I reverted back to v6.1.0(165) and everything seems to be okay, except that o2banking doesn't work. SafetyNet is clean, Magisk is hidden for o2banking and Magisk manager is repacked.
Does anybody know what the problem might be? Especially with that new version of the manager app, but also with Magisk v19.0 which cannot be installed from v6.1.0 (max. is v18.1). Any ideas welcome! I'm now on OOS 5.0.8 by the way.
SOLVED it myself: As mentioned somewhere in the update FAQ of Magisk there was a bug in manager v6.1.0 that causes the updated v7.1.1 to co-exist with the old version if the old version has been re-packed. If anybody encounters the same problem, the solution is at the bottom of this page: https://www.didgeridoohan.com/magisk/ManagerIssues.
o2banking will then still not work. Update to v19.0 is mandatory. But that is no problem then any more...
probably your banking app identified oxygen os as custom rom and have root. 1 out of 3 banking app in my phone doesn't work with lineageos even though i already hide magisk, but when running oxygen os with magisk hide, and also hide magisk manager (turn it on in magisk manager setting) all 3 banking app work just fine. maybe try sending a message to bank app developer to add oxygen os as exception.
Did you notice my edit? It was a problem with magisk manager update and magisk main version. Now everything is back up and running.
Just wanted to create a thread similar to the Pokémon Go one because i've seen the only one having problems with this app and magisk despite the John announncement made in September...
Anyway, back to the main topic, in this thread i would like to gather all users with some requirements:
- Fate GO istantly closes, opens the default mail app and prompts the "Error 61" in the mail, other errors have nothing to do with magisk.
- Latest version of Magisk Dev
- Magisk Hide enabled and Fate GO ticked in the list
- Magisk Manager hidden
- Check if other apps (Like GPay for example) find Magisk/Root or not
- Safetynet "full" passes
- No Xposed
- Running the uninstaller of magisk makes Fate GO working normally
- Always write: ROM, Kernel, Magisk Version, Fate GO version and region (NA, CN, JP ecc...)
Thanks in advance to everyone that will help with this problem or share their experiences or thoughts, and if someone else would like to test itself you can find the apk on APKPure if it's no present on play store.
Make sure USB debugging is disabled, then if that doesn't work, clear the data for the app
Sent from my Pixel using Tapatalk
Hello, I'm sorry for you, but I'm the same, and the worst is that I recently installed magisk, just yesterday, because I thought it would work with Fate G / O but apparently I happen the same as you, it was supposed to be fixed, right?
By the way, just to complete other apps I can't find magisk.
-StockRom Android 6.
-Kernel 3.18.19+
-Last Magisk Dev
-Last ver JP and NA
Chocobubba said:
Make sure USB debugging is disabled, then if that doesn't work, clear the data for the app
Click to expand...
Click to collapse
Debug usb has nothing to do with error 61, which is magisk, that's why I specified it in the list xD
Niiya said:
Hello, I'm sorry for you, but I'm the same, and the worst is that I recently installed magisk, just yesterday, because I thought it would work with Fate G / O but apparently I happen the same as you, it was supposed to be fixed, right?
By the way, just to complete other apps I can't find magisk.
-StockRom Android 6.
-Kernel 3.18.19+
-Last Magisk Dev
-Last ver JP and NA
Click to expand...
Click to collapse
Yep, it was supposed to bi fixed since September, but the majority of the players here and on reddit reported the opposite, I've tried anything suggested and to ask it many times in many threads and for now I'm stuck with a not-rooted OP6...
Btw I got it "barely working" with the app "Island" but I say "barely" because sometimes it didn't work.
Killua96 said:
Debug usb has nothing to do with error 61, which is magisk, that's why I specified it in the list xD
Yep, it was supposed to bi fixed since September, but the majority of the players here and on reddit reported the opposite, I've tried anything suggested and to ask it many times in many threads and for now I'm stuck with a not-rooted OP6...
Btw I got it "barely working" with the app "Island" but I say "barely" because sometimes it didn't work.
Click to expand...
Click to collapse
I tried flashing the reddit hide zip and several more until I surrendered, after all I gave him delete without remembering to save the save code.
It's weird, because I installed magisk believing that go would work, if a bank app works because it wouldn't work fate GO?
It seems that I was wrong.
Niiya said:
I tried flashing the reddit hide zip and several more until I surrendered, after all I gave him delete without remembering to save the save code.
It's weird, because I installed magisk believing that go would work, if a bank app works because it wouldn't work fate GO?
It seems that I was wrong.
Click to expand...
Click to collapse
Btw my bank app doesn't work with and without magisk, anyway the problem is that FGO was advised as playable since September and it's not...
Hello, i get some problems like this. My device - Asus me302kl with Nitrogen os 8. I install magisk (canary), hide fate app, and rebuilt magisk with new package name. After killing process in app settings i can play, but after some time (i think when magisk has autolaunch) fate found magisk and i recieve error 61. After this I need restore and rebuild package again, for normal fgo launch.
Now i try something for stable result.
This could be interesting: https://twitter.com/topjohnwu/status/1064941972375392257?s=19
Let's see if he can do something about it...
Killua96 said:
This could be interesting: https://twitter.com/topjohnwu/status/1064941972375392257?s=19
Let's see if he can do something about it...
Click to expand...
Click to collapse
And in fact now magisk is not detected at all by FGO, finally...!
For a moment I got error 43 so I deactivated the USB debug, but then I went back to error 61, is it still possible that it is an error of my device?
The developer options are activated permanently because oem unlock is activated.
Niiya said:
For a moment I got error 43 so I deactivated the USB debug, but then I went back to error 61, is it still possible that it is an error of my device?
The developer options are activated permanently because oem unlock is activated.
Click to expand...
Click to collapse
If you have added fgo to the magisk hidelist, and have hidden MagiskManager trough the option in the settings then you could try to use the ProcGate apk and see if the proc bug is the issue.
FGO works well now, no errors or anything. This is great because I use root regularly, but wasn't willing to let go of it.
:victory:
I have android 6, well I can always use an emulator.
Just tried this game and can't open just white screen and there some gmail option
-AEX N 7.1
-latest mgisk cannary
-3.10.108
-latest NA
I can play dragalia lost just fine with magisk hide,this game sure annoyingxD
Edit: Oookay its weird,I just reboot my device and it work like a charmxD
Niiya said:
I have android 6, well I can always use an emulator.
Click to expand...
Click to collapse
Check with procgate app if you have leaks, if there are unfortunately there aren't solutions atm on Android versions bellow nougat...
Well looks like this topic is a bit dead. Is Fate GO still working with Magisk?
I can't seem to get it working. Keep getting error 61 & 60
Running on 7.1 LineageOS with latest canary build
Both Fate GO & MM are hidden
All safetynet checks passed
Freshly flashed ROM, no Xposed or anything
No leaks detected in Procgate
Running magisk uninstaller makes Fate GO working normally
AsakuraVN said:
I can't seem to get it working. Keep getting error 61 & 60
Running on 7.1 LineageOS with latest canary build
Both Fate GO & MM are hidden
All safetynet checks passed
Freshly flashed ROM, no Xposed or anything
No leaks detected in Procgate
Running magisk uninstaller makes Fate GO working normally
Click to expand...
Click to collapse
What error code you have last? 61?
Try hide MM from framework+google apps
Lordische said:
What error code you have last? 61?
Try hide MM from framework+google apps
Click to expand...
Click to collapse
Already tried. Right now it's 60.
Guilhermex12 said:
Well looks like this topic is a bit dead. Is Fate GO still working with Magisk?
Click to expand...
Click to collapse
Yes. Poke GO and FGO work with Magisk - at least with 17.4 and 18.1. i played Fate a few days ago, no problem on Pie.
I have the latest Magisk and Magisk Manager installed and it works perfectly for a while until it says "Magisk not installed." in red letters. When I reboot I have root again. Any ideas what is happening here? I'm on the latest OTA of stock ROM.
This happens since xx.13 version of Stock ROM, at least on my device.
I have fully uninstalled Magisk 7 hours ago, and reinstalled again. Currently still having root. Reinstalled the same version 17.4 (Beta)
Whatever the problem may be i suspect its Magisk hide. Since I am on a different "experiment" at the moment, would you volunteer in disabling Magisk hide?
I am here to report that a fresh reinstallation of Magisk did not solve the issue
Trying latest canary as of writing
Yeah, it's a weird issue. It hasn't happened since I made the original post. I do use Magisk Hide for a few apps so that may be what's triggering it. I'm not sure. I haven't noticed a pattern yet as to what seems to trigger the loss of root.
I am on Canary and root loss still happens. Ok going to disable Magisk Hide and hopefully i need not to use the bank apps for two days
It just happened again on my device. :-\
I have disabled Magisk Hide since i made the last post. I can confirm root loss did not happen.
It's counter intuitive to use Magisk without Magisk Hide. Hmm.
JFYI: never happened here in 3 weeks on stock 10.0.14.0 with Magisk 19.4 and MagiskManager 7.3.4; was regularly happening on stock 10.0.13.0 with Magisk 19.3 and MagiskManager 7.3.2.
I just started to happen with me. I've found out that it's something with magisk hide, once deactivated the problem stopped, but now I have a new one xD
Since my last post, I enabled Magisk hide, but stopped hiding magisk from Play Services. So far no root loss. Perhaps OP could try this too, if play services is indeed in your hide list.
---------- Post added at 03:27 PM ---------- Previous post was at 03:27 PM ----------
Aerobatic said:
JFYI: never happened here in 3 weeks on stock 10.0.14.0 with Magisk 19.4 and MagiskManager 7.3.4; was regularly happening on stock 10.0.13.0 with Magisk 19.3 and MagiskManager 7.3.2.
Click to expand...
Click to collapse
I have this issue since 10.0.13.0, and after updated to 10.0.14.0. In fact, I have even clean flashed stock 10.0.14.0 and the issue persisted regardless.
xdxita said:
I just started to happen with me. I've found out that it's something with magisk hide, once deactivated the problem stopped, but now I have a new one xD
Click to expand...
Click to collapse
What is the new problem? ?
I just noticed my error in writing just now. I didn't clean flash .14, but rather formatted /data (hard reset).
Posting as a new post instead of edit because it has been hours [emoji3061]
And yes, as of writing this one, i still have root.
Hi guys
After unlocking bootloader and installing the EU rom as I did previously I now seem to have a constant freezing issue where I have to keep rebooting the phone. Sometimes it works and sometimes you open a app and you just get a blank white screen just sitting there. The only thing different I have to to previously is use magisk delta rather than the normal magisk.
Anyone else having this issue?
Regards
Probably caused by magisk/modules . Try different magisk or without magisk.
Bobfish said:
Probably caused by magisk/modules . Try different magisk or without magisk.
Click to expand...
Click to collapse
No modules installed. Magisk used to be good but now it's a ****show where they changed the zygisk something where unless it's enabled you cant hide apps which then defeats the purpose of using banking apps as it's det xted some bull along those lines hence wanted to try delta magisk as it lets you also install and extract boot and root without using a pc. Much better at working than not al magisk.
I don't understand why good stuff has to go restarted rather than get easier and better.
Sorry I sound a bit frustrated as another issue I'm having is this bastard what's app migration of chats from iPhone to android. My gosh what a nightmare that is. Still haven't managed to transfer