Related
The first builds of Lineage are out for the shamu finally!
download.lineageos.org
How do I get rid of the ugly watermark across my screen?
The link to the nightly version doesn't work
Link to nightly worked fine for me. Haven't flashed yet, but it downloaded, albeit slowly.
https://download.lineageos.org/shamu
How to remove this cm to lineage migration build background ?
People who have the watermark did you flash the nighly or experimental?
From my understanding the experimental build is only used for migration from CM and will have that watermark no matter what, the nightly build should have no water mark. I believe they posted this info on their site.
You're supposed to flash nightly over experimental. Just read the instructions...
Dopamin3 said:
People who have the watermark did you flash the nighly or experimental?
From my understanding the experimental build is only used for migration from CM and will have that watermark no matter what, the nightly build should have no water mark. I believe they posted this info on their site.
Click to expand...
Click to collapse
can confirm - no watermark at nightly building!
Strange how everytime I try to download the nightly it fails. No matter what browser I use
first run with lineage - every thing works fine!
Does anyone know, how I can get SElinux "enforcing"? - other kernel? whichone? - need it for using Viper4Android
MartinN6 said:
first run with lineage - every thing works fine!
Does anyone know, how I can get SElinux "enforcing"? - other kernel? whichone? - need it for using Viper4Android
Click to expand...
Click to collapse
You mean permissive, but you can use stock kernel enforced, a bit tricky, you need to root with supersu, latest beta sr3 runs fine. Superuser from los page doesn't recognize viper4a for root at all. I flashed latest arise and supersu, reboot, viper4a still not recognized for root, uninstall viper4a driver, supersu recognize viper4a now, confirm it. Reboot to recovery and reflash latest arise. Now it's working.
If you want Dolby too you have to use blackbird kernel and stay permissive.
coremania said:
You mean permissive, but you can use stock kernel enforced, a bit tricky, you need to root with supersu, latest beta sr3 runs fine. Superuser from los page doesn't recognize viper4a for root at all. I flashed latest arise and supersu, reboot, viper4a still not recognized for root, uninstall viper4a driver, supersu recognize viper4a now, confirm it. Reboot to recovery and reflash latest arise. Now it's working.
If you want Dolby too you have to use blackbird kernel and stay permissive.
Click to expand...
Click to collapse
Thanks for advice!!
And yes of course - sorry - I mean "permissive"
I flashed "Viper4Android_Cleaner_v1_3_Android_7x.zip" and than "ViPER4Android_2.5.0.5_guitardedhero.zip"
... and it works without any trouble ...
MartinN6 said:
Thanks for advice!!
And yes of course - sorry - I mean "permissive"
I flashed "Viper4Android_Cleaner_v1_3_Android_7x.zip" and than "ViPER4Android_2.5.0.5_guitardedhero.zip"
... and it works witout any trouble ...
Click to expand...
Click to collapse
Good, if it works that easy, but there was something about the cleaner, don't remember right now exactly, but it breaks something. May it was dolby.
Edit: using the cleaner always kills cast connection, that's why I didn't use it anymore
MartinN6 said:
first run with lineage - every thing works fine!
Does anyone know, how I can get SElinux "enforcing"? - other kernel? whichone? - need it for using Viper4Android
Click to expand...
Click to collapse
Kernel Adiutor Mod should let you toggle that (requires root) under the Misc Controls tab. I would imagine the ad-filled subpar original Kernel Adiutor from the Play Store would too but I wouldn't recommend using that.
Is there an updater built in or do we flash all updates? Reading in other threads that ppl get a update notification when a new build is available. I'm on experimental cuz the nightly link didn't work when I tried last night
Dopamin3 said:
Kernel Adiutor Mod should let you toggle that (requires root) under the Misc Controls tab. I would imagine the ad-filled subpar original Kernel Adiutor from the Play Store would too but I wouldn't recommend using that.
Click to expand...
Click to collapse
Thanks!
I got it and it (Kernel Adiutor mod) works great!
Now AdAway works again (need SElinux permissiv) - that's very good!
Guys, whats your baseband or radio? My proximity sensor isn't working properly on LineageOS...
MartinN6 said:
Thanks!
I got it and it (Kernel Adiutor mod) works great!
Now AdAway works again (need SElinux permissiv) - that's very good!
Click to expand...
Click to collapse
How did you get those SOFT keys from. Pixel
hashtag_harsh said:
How did you get those SOFT keys from. Pixel
Click to expand...
Click to collapse
sorry I don´t understand what you mean with "SOFT keys" ?
Edit: Aah now I know!
Yes, it's from the mod - link next post! ->
hashtag_harsh said:
How did you get those SOFT keys from. Pixel
Click to expand...
Click to collapse
https://forum.xda-developers.com/nexus-6/themes-apps/cool-pixel-mod-android-7-1-1-t3532951
Here you go
---------- Post added at 19:57 ---------- Previous post was at 19:54 ----------
LeroViten said:
Guys, whats your baseband or radio? My proximity sensor isn't working properly on LineageOS...
Click to expand...
Click to collapse
Latest
https://forum.xda-developers.com/ne...-nexus-6-recovery-flashable-fastboot-t3066052
I am creating this guide for Magisk v13 and working modules. Please let me know if there are additional ROMs that this guide works with, but I am trying to keep the steps as simple as possible.
Magisk Installation Instructions:
Download Latest PureNexus / PA ROM and follow those instructions
Boot into the ROM and go through the initial set up, at this point verify that SafetyNet is passing. If it is not you may need to factory reset and re-install your ROM.
Reboot into TWRP
Flash the attached modified Magisk-v13-Pixel (from Goodwin_c)
Flash the attached verified boot signer (from Chainfire)
Reboot the System
Uninstall the version of Magisk Manager that shows up in the drawer
Install the attached version of MagiskManager_v13_new5.apk (from Goodwin_c)
Open Magisk Manager (you may need to wait a bit, I had to clear it from my recents a few times before it launched and asked for file system permissions)
Go to the app settings and tick on Magisk Hide
Re-run SafetyNet and verify it's passing
Working Modules
I will create a video guide on how to modify modules to work with the Pixel phones until Magisk is fully updated to support Pixel.
Modules I have modified to work with Pixel:
Emoji One - systemlessly replaces emojie font with Emoji One.
Tethering Enabler - enables tethering on phones where it is disabled by the manufacturer/provider.
chadgauth said:
I may create a video guide on how to modify modules to work with the Pixel phones until Magisk is fully updated to support Pixel.
I'll attach some working modules that I have modified.
Click to expand...
Click to collapse
Is v13 working for you. I tried it when he first released it. Very glitchy. Went back to 12. A few of us did. That and we couldn't restore a backup with TB.
mac796 said:
Is v13 working for you. I tried it when he first released it. Very glitchy. Went back to 12. A few of us did. That and we couldn't restore a backup with TB.
Click to expand...
Click to collapse
These still looks like the ones @goodwin_c created. If that's the case, then yes, it's very glitchy and you are better off sticking to v12. It is a good starting point though and hopefully he can get an updated v13 working soon!
uodii said:
These still looks like the ones @goodwin_c created. If that's the case, then yes, it's very glitchy and you are better off sticking to v12. It is a good starting point though and hopefully he can get an updated v13 working soon!
Click to expand...
Click to collapse
I was just curious why a guide was made with V13 this might scare people off wanting to run magisk on a pixel V12 is way more stable
mac796 said:
I was just curious why a guide was made with V13 this might scare people off wanting to run magisk on a pixel V12 is way more stable
Click to expand...
Click to collapse
I haven't had any issues yet, but I've only been using it for a few days. I have the Arise module installed and have been using Dolby Atmos while maintaining a clean SafetyNet
chadgauth said:
I haven't had any issues yet, but I've only been using it for a few days. I have the Arise module installed and have been using Dolby Atmos while maintaining a clean SafetyNet
Click to expand...
Click to collapse
That's cool maybe I'll give it another shot.
chadgauth said:
I haven't had any issues yet, but I've only been using it for a few days. I have the Arise module installed and have been using Dolby Atmos while maintaining a clean SafetyNet
Click to expand...
Click to collapse
What rom are you using? The issue I came across that Goodwin confirmed was that root seemed to work, but apps like Titanium Backup didnt work properly. Are you running any apps that require root? And do they seem to perform correctly?
It also looks like he released a v13_new5.apk on his AFH account. Are you still using new1? Just curious if the new5 version might fix any previous issues.
uodii said:
What rom are you using? The issue I came across that Goodwin confirmed was that root seemed to work, but apps like Titanium Backup didnt work properly. Are you running any apps that require root? And do they seem to perform correctly?
It also looks like he released a v13_new5.apk on his AFH account. Are you still using new1? Just curious if the new5 version might fix any previous issues.
Click to expand...
Click to collapse
Yeah, I haven't tried Titanium backup, I'm using Solid Explorer and Greenify with root and they seem to work alright. I am still using new1, I will update to new5 and play with Titanium to see if I can get it to backup and reinstall an app
chadgauth said:
I may create a video guide on how to modify modules to work with the Pixel phones until Magisk is fully updated to support Pixel.
I'll attach some working modules that I have modified.
Click to expand...
Click to collapse
I'm very interessted about how to modify modules to work with Pixel device !
chadgauth said:
I may create a video guide on how to modify modules to work with the Pixel phones until Magisk is fully updated to support Pixel.
I'll attach some working modules that I have modified.
Click to expand...
Click to collapse
The only one I need is Tethering Enabler! Emoji One would be nice to have as well...
Only custom rom? Anyone tried on stock image?
Excuse me, may I know is there a thread by Goodwin_c publishing the modified Magisk?
I just want to keep updated to his modification.
I have been using his modified Magisk v12, but finding it from RR thread.
There is no way to know if it is updated or not.
The zip failed to flash for me. Couldn't unpack boot image.
Pixel running PN 7.1.1, twrp RC1.
maflin18 said:
The zip failed to flash for me. Couldn't unpack boot image.
Pixel running PN 7.1.1, twrp RC1.
Click to expand...
Click to collapse
Try TWRP RC2
TENN3R said:
Only custom rom? Anyone tried on stock image?
Click to expand...
Click to collapse
The stock image should most likely work, if it works for you or someone else in this thread let me know and I'll update the OP.
y2kbugleung said:
Excuse me, may I know is there a thread by Goodwin_c publishing the modified Magisk?
I just want to keep updated to his modification.
I have been using his modified Magisk v12, but finding it from RR thread.
There is no way to know if it is updated or not.
Click to expand...
Click to collapse
I'll update the post date in brackets when I make updates here. Goodwin_c does not have his own thread, so I've just been monitoring his android file host account. The original poster has not updated or maintained his guide from the RR thread, so I created a new one to be as up-to-date as possible and include modules as I modify them.
foski said:
The only one I need is Tethering Enabler! Emoji One would be nice to have as well...
Click to expand...
Click to collapse
I've included both of those. I basically have been using beyond compare to compare the arise module that works with pixel to other modules and re-zipping them and testing with my device.
I see. Thanks.
Btw do you know the difference between v1 and v5 apk?
It seems MagiskHide is gone on v5?
I have tried Magisk-V13 on Pixel-XL with stock ROM.
I haven't tried it with stock kernel, since SafetyNet won't pass (as far as I understand).
Tested with Elemental-X + MagiskManager-v1, SafetyNet does not pass. App always says "cannot use Play service"
Tested with Kirisakura-Rebase-1.36 + MagiskManager-v1, SafetyNet passes.
MagiskManager-v5 does not come with MagiskHide, so I assume it cannot handle SafetyNet.
Both MagiskManager v1 and v5 loads very slowly.
Before the UI could be used normally (it means Magisk is loaded?), ROOT cannot be obtained.
So those boot-up root-required action would probably fail.
Hi everybody,
I want to show you how to install Viper4android on your phone running developer preview 3 or later with Android O.
IM NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR PHONE!!
First download the zip from Androidfilehost or from below.
Zip
https://www.androidfilehost.com/?fid=673368273298967857
Busybox
https://www.androidfilehost.com/?fid=961840155545578665
Extract it to any folder, you will have two files now, a Viper4android App and a flashable Viper4android zip.
Reboot into recovery and install the zip, I also recommend a custom kernel like the Jolla Kernel which already has Android O support for loudness control (for my Nexus 5X).
Boot normally install BusyBox and launch Viper4android.
Select install drivers, grant root permission and wait until it is installed.
If a IO Error occurrs don't worry it'll work anyway.
Reboot and open any file manager.
Delete the Viper4android folder in "/system/priv-app".
Delete "/system/vendor/etc/audio_effects".
Install Viper4android app you downloaded before.
Reboot once again and open Viper4android - driver are working now.
Tested on my Nexus 5X with Android 8 developer preview 3.
Leave a like if it helped.
Reserved
Kindly share BusyBox APK.. as play store busy box unable to work.. can't install properly..
vijaygogawale said:
Kindly share BusyBox APK.. as play store busy box unable to work.. can't install properly..
Click to expand...
Click to collapse
Ok
Done Androidfilehost link is uodated
Thargorsson said:
Ok
Done Androidfilehost link is uodated
Click to expand...
Click to collapse
App installed.. but busy box not installed.. error
vijaygogawale said:
App installed.. but busy box not installed.. error
Click to expand...
Click to collapse
Which device do you have and which Android kernel, android version etc... I need Basic information.
Thargorsson said:
Which device do you have and which Android kernel, android version etc... I need Basic information.
Click to expand...
Click to collapse
Device Angler,
Kernel Stock,
Android 8 DP3,
vijaygogawale said:
Device Angler,
Kernel Stock,
Android 8 DP3,
Click to expand...
Click to collapse
Systemless root?
And which supersu
Thargorsson said:
Systemless root?
And which supersu
Click to expand...
Click to collapse
Magisk v13,
vijaygogawale said:
Magisk v13,
Click to expand...
Click to collapse
Aha I've only tested with latest supersu that might be the problem.
Try the 2.82 version.
Thargorsson said:
Aha I've only tested with latest supersu that might be the problem.
Try the 2.82 version.
Click to expand...
Click to collapse
Will try and report back
vijaygogawale said:
Will try and report back
Click to expand...
Click to collapse
Good. btw did you deleted the old Viper4android folder and installed the new app as user app? And changing enforce to permissive also fix some problems.
Thargorsson said:
Good. btw did you deleted the old Viper4android folder and installed the new app as user app? And changing enforce to permissive also fix some problems.
Click to expand...
Click to collapse
Working now, phonograph not supported.
vijaygogawale said:
Working now, phonograph not supported.
Click to expand...
Click to collapse
Cool
Anybody get this working on Pixel XL (Marlin) on 8.0 - Sept security release? SuperSu 2.82 - SR4
jbirdyRazr said:
Anybody get this working on Pixel XL (Marlin) on 8.0 - Sept security release? SuperSu 2.82 - SR4
Click to expand...
Click to collapse
Hows the exact process you wen through?
I have not implemented yet. Was wondering if anybody else had. Now using SuperSu 2.82-SR5 and TWRP 3.1.1.0. Now that TRWP works now without having to fastboot, I will try this mod. If I get it working I will let you know.
Ah k
I went through the entire procedure including deleting the system app and installing the io fix version.
The app tells me that drivers are working but i there is no difference in sound.
Turing Master power on and off dosen't seam to make any diffrence. What is going on?
snehgada said:
I went through the entire procedure including deleting the system app and installing the io fix version.
The app tells me that drivers are working but i there is no difference in sound.
Turing Master power on and off dosen't seam to make any diffrence. What is going on?
Click to expand...
Click to collapse
Which device, Rom and kernel? And also which music player are you using? Also try enabke developer options in Viper and select disable selinux and/or enable FX compatibility mode.
I'm trying to install the f-droid privileged extension OTA zip, but after flashing it in TWRP, when I open F-Droid, the 'Expert mode' in the settings doesn't show it.
Steps I took....
1. Installed the FDroid.apk downloaded from https://f-droid.org/en/
2. Booted into TWRP and flashed the org.fdroid.fdroid.privileged.ota_2070 downloaded from here;
https://f-droid.org/packages/org.fdroid.fdroid.privileged.ota/
Here's the actual path to the OTA zip;
https://f-droid.org/repo/org.fdroid.fdroid.privileged.ota_2070.zip
Rebooted back into ROM, which by the way is AOSiP 5.6, started F-Droid for the first time, went to settings, Expert Mode, and nothing...
So here the developer puts out the OTA zip to flash in TWRP, it's mentioned here;
https://gitlab.com/fdroid/privileged-extension/
Then it's not working, or I'm missing something? Does anyone know how to do this manually? When I look at the site for the OTA it says this, Fixed OTA ZIP for Android 8.0 Oreo, and the custom roms is Oreo 8.1.0, so maybe this isn't supported?
I know there is Magisk Module and NanoDroid for F-Droid, but for now, I'd like to figure out why this OTA zip is not working?
Also can anyone explain, what the Pros & Cons are of installing manually VS using NanoDroid-Fdroid or Magisk?
Install fdroid priv extension from magisk
apexashwin said:
Install fdroid priv extension from magisk
Click to expand...
Click to collapse
I already know about using NanoDroid-Fdroid or Magisk, I'm just trying to figure out why this won't work manually.
It seems now after looking at this, the DEV hasn't updated this for Oreo 8.1.0 that the custom roms are using, so I'm working on it...
DoR3M3 said:
I already know about using NanoDroid-Fdroid or Magisk, I'm just trying to figure out why this won't work manually.
It seems now after looking at this, the DEV hasn't updated this for Oreo 8.1.0 that the custom roms are using, so I'm working on it...
Click to expand...
Click to collapse
apexashwin said:
Install fdroid priv extension from magisk
Click to expand...
Click to collapse
apexashwin said:
Click to expand...
Click to collapse
LOL, you always give me a funny face...
Anyhow, as I was looking around I found a issue on the Mi A1 that the developer is working on, in case you'd like to follow it, or anyone else interested in this for the Mi A1.
https://gitlab.com/fdroid/privileged-extension/issues/43
DoR3M3 said:
LOL, you always give me a funny face...
Anyhow, as I was looking around I found a issue on the Mi A1 that the developer is working on, in case you'd like to follow it, or anyone else interested in this for the Mi A1.
https://gitlab.com/fdroid/privileged-extension/issues/43
Click to expand...
Click to collapse
Never used it but yea I'll check it out for sure cuz I've been hearing about fdroid alot
apexashwin said:
Never used it but yea I'll check it out for sure cuz I've been hearing about fdroid alot
Click to expand...
Click to collapse
Well, it's the App to use, there's also YalpStore.
This is about MicroG/FakeGapps, using a rom with No Gapps, no Google Play Store, etc...
It's taken me a little time, but I've figured out how to do a nice clean Custom Rom install with NoGapps, and use MicroG.
DoR3M3 said:
Well, it's the App to use, there's also YalpStore.
This is about MicroG/FakeGapps, using a rom with No Gapps, no Google Play Store, etc...
It's taken me a little time, but I've figured out how to do a nice clean Custom Rom install with NoGapps, and use MicroG.
Click to expand...
Click to collapse
I really wanna use my phone Google free but iam afraid cuz most apps i use check for licence and it requires Google play. . wish i can do something about this
Has anyone been able to successfully upgrade to Magisk 17.1 on the latest stock nougat ROM?
Even after the 17.1 Hotfix I still bootloop back into recovery; I've attempted to use the uninstaller first and same result.
Any idea ?
Same here unfortunately
I have this issue too
Anyone aware on how to assist the developer in diagnosing the issue. Seems like no other manufacturers are having the issue with the update.
I have no problem with Magisk 17.1 - but then again I use AOKP - custom roms do not have the problem!
Geez - I dont know how you can use stock - it is useless in comparison to AOKP / Lineage
No custom ROMs have their own set of issues. The best compromise for my usecase was to remain on the latest stock and make all the modifications I required myself.
Are the custom ROMs still on nougat?
Issues ? I don't have any - none ! I use AOKP and it gets updated every week and also gets the monthly security updates - Stock does not.
I have dolby atmos, substratum,magisk and pure freedom.
Oreo is being developed by tdm at the moment - hopefully it will be released soon but I am not holding my breath and am more than happy with what I have right now.
Which version do you guys use prior to 17.1?
16.7
k500zm said:
Issues ? I don't have any - none ! I use AOKP and it gets updated every week and also gets the monthly security updates - Stock does not.
I have dolby atmos, substratum,magisk and pure freedom.
Oreo is being developed by tdm at the moment - hopefully it will be released soon but I am not holding my breath and am more than happy with what I have right now.
Click to expand...
Click to collapse
@k500zm could you possibly tell me how to get dolby atmos working with AOKP? Been a while since I tried, but I couldn't figure it out. Tried to use a Magisk extension but it didn't work. Atmos is the reason I've been staying with stock (that and so snapchat works.)
countercharge said:
@k500zm could you possibly tell me how to get dolby atmos working with AOKP? Been a while since I tried, but I couldn't figure it out. Tried to use a Magisk extension but it didn't work. Atmos is the reason I've been staying with stock (that and so snapchat works.)
Click to expand...
Click to collapse
Go to this post and click on the link and download ViperAtmos 5.5 Sony Beats Edition and flash in twrp
https://forum.xda-developers.com/axo...4#post75053804
k500zm said:
Go to this post and click on the link and download ViperAtmos 5.5 Sony Beats Edition and flash in twrp
https://forum.xda-developers.com/axo...4#post75053804
Click to expand...
Click to collapse
Your link doesn't work. Gonna try to find it on my own but if you can post it I'd appreciate it and so would anyone else who finds this thread.
countercharge said:
Your link doesn't work. Gonna try to find it on my own but if you can post it I'd appreciate it and so would anyone else who finds this thread.
Click to expand...
Click to collapse
There is a whole thread about this in the ZTE AXON 7 MINI THEMES, APPS, AND MODS section below are you just to lazy to look ????
https://forum.xda-developers.com/axon-7-mini/themes/zte-axon-7-mini-lineage-os-dolby-atmos-t3746487
There is the correct link in my post there for viper and atoms !
k500zm said:
There is a whole thread about this in the ZTE AXON 7 MINI THEMES, APPS, AND MODS section below are you just to lazy to look ????
https://forum.xda-developers.com/axon-7-mini/themes/zte-axon-7-mini-lineage-os-dolby-atmos-t3746487
There is the correct link in my post there for viper and atoms !
Click to expand...
Click to collapse
Like I said, your link didn't work, I did search and it lead me to this thread:
https://forum.xda-developers.com/android/software/viperaudio-viperatmos-3-8-sq-driver-t3289075
Sorry.
countercharge said:
@k500zm could you possibly tell me how to get dolby atmos working with AOKP? Been a while since I tried, but I couldn't figure it out. Tried to use a Magisk extension but it didn't work. Atmos is the reason I've been staying with stock (that and so snapchat works.)
Click to expand...
Click to collapse
countercharge,
You need to perform a fresh install of AOKP. These are k500zm's suggested steps:
Wipe system, data, cache, dalvik
Install AOKP rom; get if from http://xfer.aokp.co/?developer=AOKP&folder=tulip
Install unsu to get rid of Supersu.
Install ViperAtmos 5.5 Sony Beats Edition
Install Magisk
Install gapps
Reboot
Delete "audiofx" and "cyanogen audio" services using sdmaidpro or titanium pro
If you want, install Sony Music player from Magisk app
I am attaching the unsu and ViperAtmos files.
Regards
can someone please try this on his tulip https://forum.xda-developers.com/trek-2/themes/sound-mod-dolby-audio-t3835114
just because tulip and jasmine are very similar
please let me know if it works
I have seen a solution for this problem in 4pda forum if someone got this problem maybe they can look at there.
LeonardoGC said:
countercharge,
You need to perform a fresh install of AOKP. These are k500zm's suggested steps:
Wipe system, data, cache, dalvik
Install AOKP rom; get if from http://xfer.aokp.co/?developer=AOKP&folder=tulip
Install unsu to get rid of Supersu.
Install ViperAtmos 5.5 Sony Beats Edition
Install Magisk
Install gapps
Reboot
Delete "audiofx" and "cyanogen audio" services using sdmaidpro or titanium pro
If you want, install Sony Music player from Magisk app
I am attaching the unsu and ViperAtmos files.
Regards
Click to expand...
Click to collapse
So I finally got around to flashing everything tonight, and unfortunately it doesn't seem that dolby atmos or viper4android are working. They're both installed, but they have no effect on the audio and changing/enabling any of the settings doesn't seem to do anything whatsoever to the sound. I also can't seem to remove audiofx with titanium backup pro. Not sure what I did wrong or how to fix it. Any ideas?
Magisk on the latest stock nougat ROM?
RFrancis said:
Has anyone been able to successfully upgrade to Magisk 17.1 [from working 16.7] on the latest stock nougat ROM?
Click to expand...
Click to collapse
I tried to flash Magisk 17.3 and 18.1 without success on the B15 stock firmware. Had to flash back to the noverity B15 kernel to boot up the stock firmware again.
Magisk 16.7 is working! :good: https://github.com/topjohnwu/Magisk/releases/tag/v16.7
SGH-i200 said:
I tried to flash Magisk 17.3 and 18.1 without success on the B15 stock firmware. Had to flash back to the noverity B15 kernel to boot up the stock firmware again.
Magisk 16.7 is working! :good: https://github.com/topjohnwu/Magisk/releases/tag/v16.7
Click to expand...
Click to collapse
It was. Now although security net passes, Google pay stopped working for ever.....and unless there is a way to make magisk 18.1, working on stock, which to me in unheard of, we stock users have to unroot or flash akop and go through the hustle of making sound work with Dolby.
Cheers