Database Users

[Q&A] [ROM][N910W8][AOA1]Stock Rooted Deodexed (Regular/Debloated versions)

Q&A for [ROM][N910W8][AOA1]Stock Rooted Deodexed (Regular/Debloated versions)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][N910W8][AOA1]Stock Rooted Deodexed (Regular/Debloated versions). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

work with encryption?
do you think it will allow encryption? I haven't had much luck yet with any rom except stock for root, twrc, and then encryption. my work email requires it or I'd skip it entirely...
thx

Colin Marr said:
do you think it will allow encryption? I haven't had much luck yet with any rom except stock for root, twrc, and then encryption. my work email requires it or I'd skip it entirely...
thx
Click to expand...
Click to collapse
I haven't tried but it's possible. Not sure why encryption doesn't work on other roms, but the "regular" version of this one is basically stock with root, TWRP, busybox, etc. I've disabled securestorage and added r/w permissions for SD card too, but if that's a problem you can reverse those two changes by following the steps in OP2 in my dev thread. If you test it out please report back and let us know if it worked

Deleted

resolving LTE display issue
Hi,
I believe I have replaced the Systemui.apk correctly with the correct permissions using Root Explorer but still see the 4G rather than the LTE in the bar.
Any ideas?
Thx.
Nick
ps thanks for the debloated ROM - working great for me with KT Kernel

nbogod said:
Hi,
I believe I have replaced the Systemui.apk correctly with the correct permissions using Root Explorer but still see the 4G rather than the LTE in the bar.
Any ideas?
Thx.
Nick
ps thanks for the debloated ROM - working great for me with KT Kernel
Click to expand...
Click to collapse
Check out this post from my other thread in the dev section. I think you'll also need the platform file, not just the Systemui.apk. Let us know if that does the trick.
http://forum.xda-developers.com/showthread.php?p=58766618

UPDATE!
v2.1 of the roms are now live! Based on the latest N910W8 BOC4 5.0.1 Lollipop firmware. See OP in the dev thread for updated details, instructions, notes, and download links: http://forum.xda-developers.com/showthread.php?p=58717681

Still no luck
sefrcoko said:
Check out this post from my other thread in the dev section. I think you'll also need the platform file, not just the Systemui.apk. Let us know if that does the trick.
http://forum.xda-developers.com/showthread.php?p=58766618
Click to expand...
Click to collapse
Thanks - I replaced the platform in permissions/etc/ with the updated one but at reboot still 4G.
Any other thoughts?
Thx.
Nick

nbogod said:
Thanks - I replaced the platform in permissions/etc/ with the updated one but at reboot still 4G.
Any other thoughts?
Thx.
Nick
Click to expand...
Click to collapse
What version of the rom are you flashing? Debloated v1.1 or 2.1? The files I linked were from the AOA1 base so not clear if they will work on BOC4.

1.1 and A0A1 base files
sefrcoko said:
What version of the rom are you flashing? Debloated v1.1 or 2.1? The files I linked were from the AOA1 base so not clear if they will work on BOC4.
Click to expand...
Click to collapse
A01A Base and debloated V1.1.
I appreciate you taking the time to respond - not really a big deal - just more a point of trying to figure it out for myself at this point. I will likely flash to 5.01 debloated now anyway - I have KT kernel running with the 1.1. Does the 5.01 have it's own kernel? (sorry if this is a naive question).
Thanks again.

nbogod said:
A01A Base and debloated V1.1.
I appreciate you taking the time to respond - not really a big deal - just more a point of trying to figure it out for myself at this point. I will likely flash to 5.01 debloated now anyway - I have KT kernel running with the 1.1. Does the 5.01 have it's own kernel? (sorry if this is a naive question).
Thanks again.
Click to expand...
Click to collapse
Happy to help . v2.1 (i.e. Lollipop) has the stock kernel. If you have already updated to BOC4 through Odin at least once before then the kernel will work for you when you flash v2.1. If not, you'll need to flash a compatible custom kernel (e.g. AEL, KT, etc) to avoid boot loops after installing v2.1. See OP in my dev thread for full instructions.
Not sure about the LTE icon. Maybe try copying the CSC folder from another working rom to v1.1 and try flashing that? If you're on kitkat and running xposed there is also a module you can download called LTE Switcher or something like that. I've used it before and it worked for me.

sefrcoko said:
Happy to help . v2.1 (i.e. Lollipop) has the stock kernel. If you have already updated to BOC4 through Odin at least once before then the kernel will work for you when you flash v2.1. If not, you'll need to flash a compatible custom kernel (e.g. AEL, KT, etc) to avoid boot loops after installing v2.1. See OP in my dev thread for fill instructions.
Not sure about the LTE icon. Maybe try copying the CSC fder from another working rom to v1.1 and try flashing that? If you're on kitkat and running xposed there is also a module you can download called LTE Switcher or something like that. I've used it before and it worked for me.
Click to expand...
Click to collapse
Thanks - I will install a custom kernel post-2.1 flash to get the BOC4 update. Appreciate you taking the time. I'll keep working away at the LTE issue. Let you know if I figure it out.

nbogod said:
Thanks - I will install a custom kernel post-2.1 flash to get the BOC4 update. Appreciate you taking the time. I'll keep working away at the LTE issue. Let you know if I figure it out.
Click to expand...
Click to collapse
Yes just confirming that you should be able to get the LTE icon by copying the CSC folder from stock or from the Regular version to your phone (after installing the Debloated version of course).:good:
---------- Post added at 11:28 AM ---------- Previous post was at 11:26 AM ----------
Debloated 2.2 released!
Notes:
Used a new debloat process and also fixed FC when using the front-facing camera.
If you get any FCs after initial setup (such as Google Maps or Samsung Link Platform), just make sure to update the problematic app from the Play Store or Samsung's Galaxy Apps store and then you should be good to go!
All details, instructions, and links can be found in the Dev thread OP:
http://forum.xda-developers.com/note-4/snapdragon-dev/trltecan-n910w8-aoa1-stock-rooted-t3025538

Samsung Provider Codes not working
Hi there, Great Rom!
One thing that isn't working is the service provider code of *#2263# isn't working (MMI error).
Thanks again!

whoatemyling said:
Hi there, Great Rom!
One thing that isn't working is the service provider code of *#2263# isn't working (MMI error).
Thanks again!
Click to expand...
Click to collapse
Thanks!
Are you using the Regular or Debloated version of the Rom?

sefrcoko said:
Thanks!
Are you using the Regular or Debloated version of the Rom?
Click to expand...
Click to collapse
I've tried both versions and neither version can access the RF Band Selector menu. It comes up with a MMI error. I've gone through and tried manually selecting a provider and that didn't work neither. IMEI is intact, and no issues with making receiving calls or texts. Flashed back to stock via Odin and no issues with getting to that menu.

whoatemyling said:
I've tried both versions and neither version can access the RF Band Selector menu. It comes up with a MMI error. I've gone through and tried manually selecting a provider and that didn't work neither. IMEI is intact, and no issues with making receiving calls or texts. Flashed back to stock via Odin and no issues with getting to that menu.
Click to expand...
Click to collapse
Hmm that's strange...I could understand an issue with the Debloated version since things were removed, but the Regular version is basically just a rooted and deodexed version of stock. You have a N910W8, and not using any other mods or kernels, correct? Not sure why it would work on stock BOC4 but not the Regular Rom since they are essentially the same...

sefrcoko said:
Hmm that's strange...I could understand an issue with the Debloated version since things were removed, but the Regular version is basically just a rooted and deodexed version of stock. You have a N910W8, and not using any other mods or kernels, correct? Not sure why it would work on stock BOC4 but not the Regular Rom since they are essentially the same...
Click to expand...
Click to collapse
Yes I had the same thought, so I went from the debloat to the regular. I also ensured that I wiped 3x in TWRP in all required sections (all except internal storage and SD Card), before doing the flash to debloat or regular. Also made sure I waited 5 minutes post boot and then reboot before going through the setup wizard.
In any case, not a deal breaker for some, but may be fore those that are looking to enable LTE on N910W8 (Wind purchased phones).
I am running a N910W8, with no other mods or kernels. I was running straight stock w/root, before flashing the ROM's. Ensured that I was running BOC4 before flash. Not sure why, unless the base ROM you're using in the Deodex and Debloat doesn't have that menu's within it's native firmware, but I was under the impression that the firmware for canadian models were all identical with their own carrier codes attached to the firmware. (CSC Code chage *#272*IMEI#).

whoatemyling said:
Yes I had the same thought, so I went from the debloat to the regular. I also ensured that I wiped 3x in TWRP in all required sections (all except internal storage and SD Card), before doing the flash to debloat or regular. Also made sure I waited 5 minutes post boot and then reboot before going through the setup wizard.
In any case, not a deal breaker for some, but may be fore those that are looking to enable LTE on N910W8 (Wind purchased phones).
I am running a N910W8, with no other mods or kernels. I was running straight stock w/root, before flashing the ROM's. Ensured that I was running BOC4 before flash. Not sure why, unless the base ROM you're using in the Deodex and Debloat doesn't have that menu's within it's native firmware, but I was under the impression that the firmware for canadian models were all identical with their own carrier codes attached to the firmware. (CSC Code chage *#272*IMEI#).
Click to expand...
Click to collapse
Thanks for the info. Strange indeed! Yes the Canadian roms should all basically be the same as you mentioned. This one is based directly off the stock Bell BOC4 firmware from sammobile so not clear why it would on stock but not this version. I've read something about Wind phones being a little different from the other Canadian variants in some way (I forget the specifics now), but that was a while back and I'm not sure if it's actually true or even related to this lol. Either way I will take a look over the weekend and post if I find anything of interest.

Regular/Debloated 2.3 released!
Notes:
Based on new BOE1 firmware released for the N910W8.
All details, instructions, and links can be found in the Dev thread OP:
http://forum.xda-developers.com/note-4/snapdragon-dev/trltecan-n910w8-aoa1-stock-rooted-t3025538

EFIDroid for the Samsung Galaxy Note 4/Note Edge (Snapdragon Variants)

More details in the Verizon Note 4 forum here.
XDA:DevDB Information
EFIDroid, Kernel for the T-Mobile Samsung Galaxy Note 4
Contributors
abraha2d, m11kkaa
Source Code: https://github.com/efidroid
Kernel Special Features: UEFI, MultiBoot
Version Information
Status: Beta
Current Beta Version: 0.1
Beta Release Date: 2017-03-18
Created 2017-03-20
Last Updated 2017-03-31

THIS IS INCREDIBLE!! Greatest thing since sliced bread where is the donation link this an amazing piece of development 2nd lvl bootloader f yaaaa!!

vegoja said:
THIS IS INCREDIBLE!! Greatest thing since sliced bread where is the donation link this an amazing piece of development 2nd lvl bootloader f yaaaa!!
Click to expand...
Click to collapse
Believe me, I didn't do much work. You can donate to @m11kkaa, though. He's the developer of EFIDroid (if you didn't already know that...). I believe he has a donation link in his profile...
Sent from my Samsung Galaxy Note 4 using XDA Labs

This is great but is there a way to uninstall it (if necessary) and get back to the primary ROM (stock or Lineage OS) without losing data?

tried to do a bit of light research and couldn't find what's different between this and other preexisting multiboot solutions. I've been using Dual Boot Patcher for sometime without issues. Is this somehow better? and if so, how?

Mtotallywired said:
tried to do a bit of light research and couldn't find what's different between this and other preexisting multiboot solutions. I've been using Dual Boot Patcher for sometime without issues. Is this somehow better? and if so, how?
Click to expand...
Click to collapse
EFIDroid is what you would call a "second-stage bootloader". The main advantage over Dual Boot Patcher (at least for me) is that you no longer have to patch zip files before installing. Also, EFIDroid is more than just a multi-boot solution. Quoting @m11kkaa:
efidroid tries to focus on simplicity, and doesn't require any kernel modifications etc.
in general: well having such a powerful bootloader in your boot stage gives you lots of possibilities, like multiboot, replacements/additions for kernels/ramdisk/cmdline.
This project has a lot more potential than what's currently implemented. i.e. you can give samsung devices fastboot and sony devices a standalone recovery. Also you can natively boot GNU GRUB if you're into booting linux kernel's the desktop way.
Click to expand...
Click to collapse
The two solutions are similar enough that you can migrate your setup from Dual Boot Patcher to EFIDroid without losing any data. I'll try to post a guide later this week.

I was I under the impression dual boot required multiple ROMs running the same kernel... If that is the case a huge advantage efi has is each ROM having their own boot img. I'm currently running 3 ROMs a lollipop a marshmallow and of course a nougat. I really just wanted to see all 3 latest android os running flawlessly on 1 device. And I did just that hats off to the developer for this.

baharvey7817 said:
This is great but is there a way to uninstall it (if necessary) and get back to the primary ROM (stock or Lineage OS) without losing data?
Click to expand...
Click to collapse
There's an uninstall button in the app. Or, you could just flash the original boot.img via TWRP (basically what the uninstall button does).

I'm a noob...What is this? Where do I need to go to learn about why I would want this...Please explain lol

mlock420 said:
I'm a noob...What is this? Where do I need to go to learn about why I would want this...Please explain lol
Click to expand...
Click to collapse
you can look at their website, and then decide if you want this level of control over your phone.
http://efidroid.org/

Thanks for bringing us this tool. One thing I can't figure out...how do we Odin a different bootloader? I have DOK2 loaded now, and want to put Dr. Ketan's on the phone. The sub instructions say to Odin the BL and CP, as the ROM is generally generic. There us also a datafix and an essential fix that needs to be applied. Doing all of that is easy, but how do I keep two separate bootloaders (LP and MM) totally separate? If I flash a LP over a MM, my camera breaks, and if I flash a MM over LP, WiFi breaks. And I'm not talking about dirty flashes, a full system, data, and cache wipe 3x. Only Odin back to the base ROM keeps my phone happy.

1freedude said:
Thanks for bringing us this tool. One thing I can't figure out...how do we Odin a different bootloader? I have DOK2 loaded now, and want to put Dr. Ketan's on the phone. The sub instructions say to Odin the BL and CP, as the ROM is generally generic. There us also a datafix and an essential fix that needs to be applied. Doing all of that is easy, but how do I keep two separate bootloaders (LP and MM) totally separate? If I flash a LP over a MM, my camera breaks, and if I flash a MM over LP, WiFi breaks. And I'm not talking about dirty flashes, a full system, data, and cache wipe 3x. Only Odin back to the base ROM keeps my phone happy.
Click to expand...
Click to collapse
There's no way to have two different bootloaders. EFIDroid comes between the bootloader and the boot.img, so it has no control over the bootloader.
EDIT: EFIDroid may be able to emulate the behavior of another bootloader... you would have to ask @m11kkaa for details...

Where can I download this for T-mobile ??
Sent from my SM-N9300 using Tapatalk

CousinMikeyP said:
Where can I download this for T-mobile ??
Sent from my SM-N9300 using Tapatalk
Click to expand...
Click to collapse
Here is the LINK. You can see more info HERE

I downloaded and started up the EFIdroid unofficial apk but got the following message:
=====================================
Error
Can't load device info. Please check your connection.
/data/user/0/org.efidroid.efidroidmanager.debug/files/devices.json (No such file or directory)
override ota server try again
===============================================
Could you please explain what's going on? Seems that this version is different from the one i downloaded in March. Could it be that it's not getting root access? What can I do to get around this error?

baharvey7817 said:
I downloaded and started up the EFIdroid unofficial apk but got the following message:
=====================================
Error
Can't load device info. Please check your connection.
/data/user/0/org.efidroid.efidroidmanager.debug/files/devices.json (No such file or directory)
override ota server try again
===============================================
Could you please explain what's going on? Seems that this version is different from the one i downloaded in March. Could it be that it's not getting root access? What can I do to get around this error?
Click to expand...
Click to collapse
I will have to look into it... The EFIDroid app error messages are not exactly the most helpful kind. (Good thing the app is being phased out soon). That particular error message could mean many things, but most likely it's a connection issue. We will continue this in Slack.

Will this work on tw 7.0 if i was porting a rom. Also why wont aosp kernel work on tw.. i always thought tw was aosp with skin..

Go to back to the link posted above where you got the unofficial apk and go to post #83. The OP posted an apk there that works fine on our phone.
baharvey7817 said:
I downloaded and started up the EFIdroid unofficial apk but got the following message:
=====================================
Error
Can't load device info. Please check your connection.
/data/user/0/org.efidroid.efidroidmanager.debug/files/devices.json (No such file or directory)
override ota server try again
===============================================
Could you please explain what's going on? Seems that this version is different from the one i downloaded in March. Could it be that it's not getting root access? What can I do to get around this error?
Click to expand...
Click to collapse

RaySCLA said:
Go to back to the link posted above where you got the unofficial apk and go to post #83. The OP posted an apk there that works fine on our phone.
Click to expand...
Click to collapse
Tried what you suggested but it didn't work either. So, I chose the 'nuclear option': I wiped the phone completely then reinstalled the stock Marshmallow ROM. using Odin. After that i installed TWRP v3.0.2 (trltetmo) and Supersu v2.79 as well as Busybox v1.26. Only then was I able to install EFIDroid successfully. Now, I'm able to boot the stock rom as well as Resurrection Remix.
It seems that if your going to install EFIDroid you must have the phone rooted using SuperSU. Using Magisk to root your phone instead of SuperSu won't work (at least it didn't work in my case).

lowkeyst4tus said:
Will this work on tw 7.0 if i was porting a rom. Also why wont aosp kernel work on tw.. i always thought tw was aosp with skin..
Click to expand...
Click to collapse
This should work anywhere, regardless of ROM... But btw, it's a stretch to say TW is just a skin on top of AOSP. In fact, TW is probably the farthest you can get from AOSP... There's a lot of significant differences that make AOSP kernels incompatible with TW ROMs...

What Roms is everyone running?

What ROM's are people running on their Verizon LG V20? Im getting ready to root mine and go through that process. Looking over the ROM's though and they seem to be lacking. Back in the day we had tons of options, now we have a handful on XDA. Are there ROM's people are running that arent listed?

Using the LineageOS weekly builds and they've been pretty good. Mostly just missing out on the second screen though.

Ashalinia said:
Using the LineageOS weekly builds and they've been pretty good. Mostly just missing out on the second screen though.
Click to expand...
Click to collapse
Ive been trying to find screenshots as Im pretty particular on my OS. I used to love MIUI when it was around.

Lineage for ls997 is horrible I'm using emotion build 4-16

pbedard said:
Lineage for ls997 is horrible I'm using emotion build 4-16
Click to expand...
Click to collapse
Why is it horrible? And why is Emotion better?

Depend on what device u using

pbedard said:
Depend on what device u using
Click to expand...
Click to collapse
That's true for anything. Just going out on a limb here, I'm guessing since we are in the LG V20 forum its safe to assume we are using that device.
Next time come prepared with proof of your claim. With no proof and bold claims you sound like a fool.

as Android goes further the ROM field is super small now KK had the biggest amount of ROMS not a lot of this model I have this version too we have RR DU is coming down the line Lineage WETA AOKP Here is a list of ROMS https://www.androidfilehost.com/?w=search&s=us996&type=files

I have a ls997 and im running Paranoid Android.

I have a vs995 and I'm running XOSP ?

Did i pick the wrong phone i cant seem to find a whole lot of roms for the verizon variant I want a debloated stock or a twrp stock flashable that i can use magisk on it is inexcuseable how much verizon pushed onto this phone is it such a tall task do i really have to choose between having no root with a carrier bloated rom and a working 2nd screen to use a asop type rom?

mirrin said:
Did i pick the wrong phone i cant seem to find a whole lot of roms for the verizon variant I want a debloated stock or a twrp stock flashable that i can use magisk on it is inexcuseable how much verizon pushed onto this phone is it such a tall task do i really have to choose between having no root with a carrier bloated rom and a working 2nd screen to use a asop type rom?
Click to expand...
Click to collapse
The Verizon build of not so stock is probably what you're looking for. Stock based so everything works minus all the bloat. Has static at boot, search some of the other kernels, there is a few that fix static at boot.

mkfryan said:
The Verizon build of not so stock is probably what you're looking for. Stock based so everything works minus all the bloat. Has static at boot, search some of the other kernels, there is a few that fix static at boot.
Click to expand...
Click to collapse
that is what i tried first but the rom was not rooted...

Gre thanks

mirrin said:
that is what i tried first but the rom was not rooted...
Click to expand...
Click to collapse
Did you flash supersu or magisk? Not all roms come rooted...

None I had issues getting it to work had issues booting found weta it worked it has a janky root but it worked and Pokemon go worked and I don't even get the static lines on the screen...

BroeknOs to be
Currently I'm running stock OS on LightningZap! kernel (still in beta, but looking like I'll have a release soon).
I have gotten BrokenOs running quite well and smoothly. But lacking the second screen is what's holding me back.
On LG V20 AT&T (H910), btw...

Quick Question

So I am on H91810q and I have kept root through the upgrades. Am I still able to flash another rom like LineageOS or am I stuck with stock since I upgraded so far?

Try it -- it isn't going to break your phone
Probably isn't going to run to well on new firmware though. Most of the heavy development was done on much older firmware, and those parts haven't been updated.
-- Brian

runningnak3d said:
Try it -- it isn't going to break your phone
Probably isn't going to run to well on new firmware though. Most of the heavy development was done on much older firmware, and those parts haven't been updated.
-- Brian
Click to expand...
Click to collapse
I'm thinking a TWRP Full Backup of the stock rom and wipe and flash LineageOS. In theory do you think I would be able to restore stock if something doesn't go right?

Yes. When you install LOS or a LOS based ROM the only thing that gets flashed is boot and system. Both of those are backed up by TWRP.
-- Brian

runningnak3d said:
Yes. When you install LOS or a LOS based ROM the only thing that gets flashed is boot and system. Both of those are backed up by TWRP.
-- Brian
Click to expand...
Click to collapse
Well I just flashed LOS and I can see the screen flashing on and off but no boot. Any other suggestions? Am I stuck with the stock rom which I am gettings sick of...

Nope, you can't downgrade. Unless someone picks up development on current firmware, you can only use stock.

Not the answer I was looking for lol...

jrosetto said:
Not the answer I was looking for lol...
Click to expand...
Click to collapse
I know this isn't a custom rom but you're like me and on rooted Q, I use to not enjoy stock due to not being able to customize the phone how I liked but the instabilities in the camera and bluetooth and battery life made me appreciate the stock/stock based roms for the V20 and I actually PREFER a fully functional camera nd awesome audio recorder than inferior apps. But! Askermk2000's kernel is COMPATIBLE with rooted 10q, I am using it and it has honestly breathed new life into my phome for sure and since we don't have many rom options at the moment at least throw this kernel on your stock 10q rom and enjoy it! Here's the thread
https://forum.xda-developers.com/v20/development/h918-h910-us996-ucl-mk2000-kernel-t3708330

Gytole said:
I know this isn't a custom rom but you're like me and on rooted Q, I use to not enjoy stock due to not being able to customize the phone how I liked but the instabilities in the camera and bluetooth and battery life made me appreciate the stock/stock based roms for the V20 and I actually PREFER a fully functional camera nd awesome audio recorder than inferior apps. But! Askermk2000's kernel is COMPATIBLE with rooted 10q, I am using it and it has honestly breathed new life into my phome for sure and since we don't have many rom options at the moment at least throw this kernel on your stock 10q rom and enjoy it! Here's the thread
https://forum.xda-developers.com/v20/development/h918-h910-us996-ucl-mk2000-kernel-t3708330
Click to expand...
Click to collapse
Thanks for the suggestion, I'll check it out.

Wifi on Custom OREO ROMs & Kernels

On Custom Oreo ROMs/kernels such Renovate ICE O, Batman ROM, Nox Kernel, notorious kernel , Wifi does not work on my S8 G950F. The only way to make these work up to now, was to restore the boot image from stock rom.
Whilst restoring stock boot.img does resolve the issue, it creates another in that after reboot wifi takes about 2 mins to turn on.
This Solution Worked for me, but doesn't always work for everyone, try it:
https://forum.xda-developers.com/galaxy-s8/samsung-galaxy-s8--s8-cross-device-development/kernel-nox-kernel-v1-t3721469/page18post 174

can you give the link for stock boot.img?

Uz986 said:
can you give the link for stock boot.img?
Click to expand...
Click to collapse
the stock boot is one you would take from twrp, or if you don't have that can install soldier rom, skip all the install options, then just backup boot in twrp

I have very kindly been given a temp fix by @Noxxxious who makes the truly excellent Nox kernel. Will update as this develops & hopefully share a perm fix for everyone

Same
I have the same Problem with my s8 in every custom Rom since oreo i cant Turn in my wifi..

Rb0 said:
I have the same Problem with my s8 in every custom Rom since oreo i cant Turn in my wifi..
Click to expand...
Click to collapse
have a look here https://forum.xda-developers.com/galaxy-s8/samsung-galaxy-s8--s8-cross-device-development/kernel-nox-kernel-v1-t3721469/page18
Post 174. This worked for me now I have wifi on all custom roms

Thought I’d chile in here as well so people learn this problem is for real, and that I know how to flash custom roms....
I am always doing the boot.img trick that @StackOverflow13 taught me a white a go.

meonit said:
Thought I’d chile in here as well so people learn this problem is for real, and that I know how to flash custom roms....
I am always doing the boot.img trick that @StackOverflow13 taught me a white a go.
Click to expand...
Click to collapse
I take it the 2 files trick didn't work for you? So are you facing the issue of really slow WiFi start-up after reboot? Glad your here anyway. The more people we get the more chance a dev or devs will take notice

Still dealing with this in 2020. I'm using a Japanese S8+ with stock Oreo firmware and a custom kernel, the second I flash Magisk and my boot image gets replaced, WiFi breaks. I checked the file directory mentioned in post 174 and I see both files are present on my phone, unless the files @noxxious posted are modified in some way.