Database Users

[GUIDE]Enable Multi User Mode on Note 5

HI. I don’t know why, but Samsung did not add multi user support on our beloved note5.
If u want to try it here is the guide to set it up.
I tested and confirm 100% working. This is applicable for all variants.
1. Open up root explorer
2. Navigate to /system
3. Paste in the following line at the bottom of your build.prop
Code:
# Multi Users
Fw.max_users=3
Fw.show_multiuserui=1

Thanks

Sound awesome

Thanks for posting this.

daviefl86 said:
HI. I don’t know why, but Samsung did not add multi user support on our beloved note5.
If u want to try it here is the guide to set it up.
I tested and confirm 100% working. This is applicable for all variants.
1. Open up root explorer
2. Navigate to /system
3. Paste in the following line at the bottom of your build.prop
Code:
# Multi Users
Fw.max_users=3
Fw.show_multiuserui=1
Click to expand...
Click to collapse
I tried this on my SM-N920T but i dont see an option to enable this feature. I restarted the device and still dont see anything.
Sent from my SM-N920T using the XDA Free mobile app
ROOTED
Model: SM-N920T
ROM: THRASHROM3.4-BOH6_9-11-2015
Kernel: arter97-kernel-n920tw8-misc-lzo

@babaroye
In Darthstalker rom the feature shows up in settings under the Device section... it's baked into the rom.
With this mod, I would assume it's in the same place in every rom, but I'm not positive.
Here is the way that @jovy23 listed this mod in his build.prop file
#Enable MultiUser Support
fw.power_user_switcher=1
fw.show_hidden_users=1
fw.show_multiuserui=1
fw.max_users=10

dandroid7 said:
@babaroye
In Darthstalker rom the feature shows up in settings under the Device section... it's baked into the rom.
With this mod, I would assume it's in the same place in every rom, but I'm not positive.
Here is the way that @jovy23 listed this mod in his build.prop file
#Enable MultiUser Support
fw.power_user_switcher=1
fw.show_hidden_users=1
fw.show_multiuserui=1
fw.max_users=10
Click to expand...
Click to collapse
Thank you its now showing.
Sent from my SM-N920T using the XDA Free mobile app
ROOTED
Model: SM-N920T
ROM: THRASHROM3.4-BOH6_9-11-2015
Kernel: arter97-kernel-n920tw8-misc-lzo

dandroid7 said:
@babaroye
In Darthstalker rom the feature shows up in settings under the Device section... it's baked into the rom.
With this mod, I would assume it's in the same place in every rom, but I'm not positive.
Here is the way that @jovy23 listed this mod in his build.prop file
#Enable MultiUser Support
fw.power_user_switcher=1
fw.show_hidden_users=1
fw.show_multiuserui=1
fw.max_users=10
Click to expand...
Click to collapse
I tried creating a new user, the device just restart then go back to my original settings that i have. This happens when i try to use the Guest user as well. Not sure whats going on there. I am using jthrasher Thrashrom3.4.
Sent from my SM-N920T using the XDA Free mobile app
ROOTED
Model: SM-N920T
ROM: THRASHROM3.4-BOH6_9-11-2015
Kernel: arter97-kernel-n920tw8-7.0Beta2

thanks

I think it has been asked but didnt see an answer! Users are showing in settings after adding to prop build but when i hit guest user or set up new user, the phone reboots:what: Anyone have fix or solution? Thanks

Anyone successful on Marshmallow?

reekotubbs said:
Anyone successful on Marshmallow?
Click to expand...
Click to collapse
#Enable MultiUser Support
fw.power_user_switcher=1
fw.show_hidden_users=1
fw.show_multiuserui=1
fw.max_users=3
I am on Marshmallow and this worked
I did not try it with 10 actually
so I directly changed it to 3 instead of 10
and it worked so I don't know if that might help
Try it and let us know
Thanks :good:

Works in every version of marshmallow? Even the most recent ones?

It's possible to enable on nougat?
Thanks

dandroid7 said:
@babaroye
In Darthstalker rom the feature shows up in settings under the Device section... it's baked into the rom.
With this mod, I would assume it's in the same place in every rom, but I'm not positive.
Here is the way that @jovy23 listed this mod in his build.prop file
#Enable MultiUser Support
fw.power_user_switcher=1
fw.show_hidden_users=1
fw.show_multiuserui=1
fw.max_users=10
Click to expand...
Click to collapse
thanks bro now work grat

Next Step?
I have followed all the steps above.
When I get to adding a user it goes through a new user setup just fine until it gets to the end.
Then it gives an unexpected error box when you click finish. Then I have to restart to get out of new user setup.
Model= SM-N910T
Android version 6.0.1
Security Patch July 1, 2017
Rooted

Hello,
I come from after checking a Youtube Video about this feature.
This is the code I used.
#Multi User
fw.max_users=30
fw.show_multiuserui=1
fw.show_hidden_users=1
fw.power_user_switcher=1
It worked, and I could successfully set up different users, and boot into their profiles.
The only thing missing is the button to switch the users after setting them up.
Not like in the video, on my device, this yellow button is missing!
<- how it looks in the video
I even tried to change [fw.max_users=30] to 3 or 5, but with no success.
I am using a Samsung Galaxy S10+ [SM-975F/DS] with Android 12 Stock ROM, and ONE UI 4.1.

Directv Now Error 40 (Failed Security Check)

Has anyone tried using Directv Now on a ROM/Rooted device? There are a number of reports of people receiving an Error 40 because they are rooted, or on a ROM etc. I was hoping we could make a thread to troubleshoot.
Some findings so far from another thread (Fire TV):
URL: http://forum.xda-developers.com/fire-tv/help/directv-love-root-users-t3510461
Quote:
I signed up today for DirecTV Now only to be greeted on my FireTV with the following error:
Code:
Code:
This video failed to load. Restart the app and launch your content again. Or search for Error 40 in the Help Center. (QP1005)
Hrmm.. that's weird. So I looked up Error 40, and it says there's a network problem. I tried it on my non-rooted Nexus 6P and it worked flawlessly. So I jumped in to logcat and found some interesting messages:
Code:
Code:
I/drm_oal ( 4862): IsDeviceRooted: 0x0000000000000002
and
Code:
Code:
D/NewRelicGateway(14071): ERROR event was recorded. Error description = Failed preparing the player because device security check failed due to: (FileSystem)(com.quickplay.vstb.core:1005)
So I installed xposed and RootCloak 2 hoping it would help. I added it to the list of apps and it still had the same problem.
Next thing I did was pull the apk from my Fire TV. After some digging, I found that lib/armeabi/libdrmagent_downloadable_jni.so had some interesting strings in it, including a check for Cyanogen:
Code:
Code:
ro.build.product
ro.build.tags,release-keys,OnePlus3#%?OnePlus2#%?OnePlus#%?Z26CL#%?STUDIO_C,ro.build.type,user,#%?
ro.build.display.id,cm_,#%?,ro.build.display.id,cyanogen,#%?,ro.build.type,debug,#%?,ro.build.type,userdebug,#%?,ro.build.host,cyanogenmod,A0001#%?
and a list of strings for paths it might check:
Code:
Code:
/system/bin/su,#%?,/system/xbin/su,#%?,/sbin/su,#%?,/system/su,#%?,/system/bin/.ext/.su,#%?,/system/usr/we-need-root/su-backup,#%?,/system/xbin/mu,#%?
su,#%?,busybox,#%?
type %s
test -u `whence -p %s`
/data,#%?,/system,#%?,/system/bin,#%?,/system/sbin,#%?,/system/xbin,#%?,/vendor/bin,#%?,/sys,#%?,/sbin,#%?,/etc,#%?,/proc,#%?,/dev,#%?
/isdrmXXXXXX
Why do they even care if you're rooted?? So lame...
Since they appear to be checking for root in a C/C++ .so file, is Xposed useless here?
Click to expand...
Click to collapse
My findings:
I do not have Root, and I can use Android Pay without issue. With that said, I cannot use Directv Now. I am currently on the PureNexus ROM
Logcat:
Code:
12-01 08:11:13.942 23249 23361 I drm_oal : IsDeviceRooted: 0x0000000000000001
Code:
12-01 08:11:14.107 23249 23674 D NewRelicGateway: ERROR event was recorded. Error description = Failed preparing the player because device security check failed due to: (Property, SignedDevice)(com.quickplay.vstb.core:1005)
My assumption is that it is in the build.prop. My "build.type=user".
Any one have any other findings?

I'm very happy to announce I've fixed my own issue, and my original hunch was correct. It is associated with the build.prop.
The fix is as simple as changing the ro.build.tags line.
From: ro.build.tags=test-keys
To: From: ro.build.tags=release-keys

mazz0310 said:
I'm very happy to announce I've fixed my own issue, and my original hunch was correct. It is associated with the build.prop.
The fix is as simple as changing the ro.build.tags line.
From: ro.build.tags=test-keys
To: From: ro.build.tags=release-keys
Click to expand...
Click to collapse
Mine was already on release-keys so what now? Did you get it to work on your 6P? I have Xposed installed too and I'm still on 6.0 btw.
Thanks
Sent from my Nexus 6P using Tapatalk

mazz0310 said:
I'm very happy to announce I've fixed my own issue, and my original hunch was correct. It is associated with the build.prop.
The fix is as simple as changing the ro.build.tags line.
From: ro.build.tags=test-keys
To: From: ro.build.tags=release-keys
Click to expand...
Click to collapse
You are the man!

volcalstone said:
Mine was already on release-keys so what now? Did you get it to work on your 6P? I have Xposed installed too and I'm still on 6.0 btw.
Thanks
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I don't have experience with Xposed (lately) so I'm not sure. But I do know you have to be rooted in order to use Xposed which is probably what is causing the issue. I would recommend "Hide My Root". I know some users say that using that has resolved the issue but I'm not sure if it hides Xposed.
Let us know if you find an answer.
venelar said:
You are the man!
Click to expand...
Click to collapse
@venelar
Thank you, glad I could help someone!

volcalstone said:
Mine was already on release-keys so what now? Did you get it to work on your 6P? I have Xposed installed too and I'm still on 6.0 btw.
Thanks
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Not sure, here's my setup:
6p with pure nexus 7.0
Magisk v9 and phh's superuser (for Android pay to work), also using magisk to hide root from DirecTV Now but it didn't work til this prop edit
I've done this release-keys edit and from userdebug to user (to make android wear work)

mazz0310 said:
I'm very happy to announce I've fixed my own issue, and my original hunch was correct. It is associated with the build.prop.
The fix is as simple as changing the ro.build.tags line.
From: ro.build.tags=test-keys
To: From: ro.build.tags=release-keys
Click to expand...
Click to collapse
Tried this but no luck

venelar said:
Not sure, here's my setup:
6p with pure nexus 7.0
Magisk v9 and phh's superuser (for Android pay to work), also using magisk to hide root from DirecTV Now but it didn't work til this prop edit
I've done this release-keys edit and from userdebug to user (to make android wear work)
Click to expand...
Click to collapse
I was thinking of using Magisk when I was ready to upgrade to 7.0. I checked that line in my build.prop but it was set to release-keys already. Not sure about doing the latter though as my android wear works already. I'm stuck at this point.
Sent from my Nexus 6P using Tapatalk
---------- Post added at 11:27 AM ---------- Previous post was at 11:24 AM ----------
mazz0310 said:
I don't have experience with Xposed (lately) so I'm not sure. But I do know you have to be rooted in order to use Xposed which is probably what is causing the issue. I would recommend "Hide My Root". I know some users say that using that has resolved the issue but I'm not sure if it hides Xposed.
Let us know if you find an answer.
@venelar
Thank you, glad I could help someone!
Click to expand...
Click to collapse
I tried hide my root too and that didn't work even after clearing the data/cache up. I'm not sure why DirecTV really care about root at this point.
Sent from my Nexus 6P using Tapatalk

I use Magisk Hide to get the app to stream. After flashing Magisk v9 and enabling Magisk Hide, I rebooted the phone and added the Directv NOW app. Works perfectly.
Sent from my Nexus 6P using Tapatalk

xstahsie said:
I use Magisk Hide to get the app to stream. After flashing Magisk v9 and enabling Magisk Hide, I rebooted the phone and added the Directv NOW app. Works perfectly.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Could I use Magisk v9 over my stock 6.0 rom or do I have to flash a whole new rom? I'm. Assuming that I have to use a system less root as well?
Sent from my Nexus 6P using Tapatalk

volcalstone said:
Could I use Magisk v9 over my stock 6.0 rom or do I have to flash a whole new rom? I'm. Assuming that I have to use a system less root as well?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
You should be able to. My Nexus 6P has a stock 6.0.1 rom. I didn't have to enable systemless root, so I didn't have to do this : echo "SYSTEMLESS=true"/data/.supersu
But I didn't think it'll hurt if you systemless root your device.
Sent from my Nexus 6P using Tapatalk

Ok guys, after countless trial and error I finally was able to get Directv Now to work with root. I tried to go back to stock, but that venture lasted for like maybe half a day. This post may be a little long, but I will try to be as detailed as I can. I currently have official stock 7.1.1 rom with Magisk and phh systemless root and Elementalx Kernel. I tried countless combination to try to get Directv Now to work this include Pure Nexus 7.0, RR, and Weta roms with ElementalX and Franco kernel. The root method I used was SuperSu and SUhide (was never able to get device to boot when flashed suhide) with root switcher and also Magisk, phh superuser and root switcher. In the end I was able to get it working only with stock rom with Magisk and phh. I also discovered that it is not a kernel issue or unlocked bootloader as I am unlocked and I have flashed elementalx kernel and haven't had the any issues, I do believe franco kernel will work as well. All you need is to use Magisk hide to hide Directv Now from root and you should be good to go. I was also able to pass safety net test. I think we maybe on the right track in saying that the issue may be build prop related. If someone can post up their build prop I can try to compare it with mine so we can finally get this issue resolved once and for all. Again sorry for the long post.

Just a little extra info...
I have a 5x and was able to get DTVN to work using Magisk and PHH superuser with hide enabled for the app. I also have a cheap android TV box (Nexbox A95x s905x). The TV box will not stream even after I used resetprop to change test-keys -> release-keys and userdebug -> user. I think my next step is to copy as much of the Nexus build.prop as possible over to the TV box given the other strings found in the DTVN apk. I'll update once I've tried this.
Thanks mazz0310.

Success! Magisk + phh superuser + resetprops --file 5x.build.props allows streaming on my cheap android TV box (NexBox A95X)
Here is the 5x.build.props file which contains the props I pulled from the Nexus 5x build.props file. I don't know which ones were important, but is works
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=NBD90W
ro.build.display.id=NBD90W
ro.build.version.preview_sdk=0
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.base_os=
ro.build.date=Thu Sep 1 06:03:08 UTC 2016
ro.build.date.utc=1472709788
ro.build.type=user
ro.build.user=android-build
ro.build.host=kpfj12.cbf.corp.google.com
ro.build.tags=release-keys
ro.build.flavor=bullhead-user
ro.product.model=Nexus 5X
ro.product.brand=google
ro.product.name=bullhead
ro.product.device=bullhead
ro.product.board=bullhead
ro.product.manufacturer=LGE
ro.product.locale=en-US
# ro.build.product is obsolete; use ro.product.device
ro.build.product=bullhead
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=bullhead-user 7.0 NBD90W 3239497 release-keys
ro.build.fingerprint=google/bullhead/bullhead:7.0/NBD90W/3239497:user/release-keys
# end build properties

jfath said:
Success! Magisk + phh superuser + resetprops --file 5x.build.props allows streaming on my cheap android TV box (NexBox A95X)
Here is the 5x.build.props file which contains the props I pulled from the Nexus 5x build.props file. I don't know which ones were important, but is works
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=NBD90W
ro.build.display.id=NBD90W
ro.build.version.preview_sdk=0
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.base_os=
ro.build.date=Thu Sep 1 06:03:08 UTC 2016
ro.build.date.utc=1472709788
ro.build.type=user
ro.build.user=android-build
ro.build.host=kpfj12.cbf.corp.google.com
ro.build.tags=release-keys
ro.build.flavor=bullhead-user
ro.product.model=Nexus 5X
ro.product.brand=google
ro.product.name=bullhead
ro.product.device=bullhead
ro.product.board=bullhead
ro.product.manufacturer=LGE
ro.product.locale=en-US
# ro.build.product is obsolete; use ro.product.device
ro.build.product=bullhead
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=bullhead-user 7.0 NBD90W 3239497 release-keys
ro.build.fingerprint=google/bullhead/bullhead:7.0/NBD90W/3239497:user/release-keys
# end build properties
Click to expand...
Click to collapse
Are you using the tronsmart rom, or stock rom? Currently trying to get this working with the tronsmart rom on my a95x. So far just editing the build.prop and removing root has not been enough. More details would be awesome. Thanks.

Takenover83 said:
Are you using the tronsmart rom, or stock rom? Currently trying to get this working with the tronsmart rom on my a95x. So far just editing the build.prop and removing root has not been enough. More details would be awesome. Thanks.
Click to expand...
Click to collapse
I'm using the stock rom, but I think any rom should be possible with the right edits. The process is a little off-topic for a Nexus 6P forum, so I sent you a PM.

mazz0310 said:
I'm very happy to announce I've fixed my own issue, and my original hunch was correct. It is associated with the build.prop
Click to expand...
Click to collapse
When I read the subject of your post and saw you were not rooted, I knew it had to be build.prop. I'm glad you got it going!

mazz0310 said:
I'm very happy to announce I've fixed my own issue, and my original hunch was correct. It is associated with the build.prop.
The fix is as simple as changing the ro.build.tags line.
From: ro.build.tags=test-keys
To: From: ro.build.tags=release-keys
Click to expand...
Click to collapse
Just to confirm, you got Directv Now working with Pure Nexus? I'm on Pure Nexus 7.1.1 and still getting error 40 after changing build.prop

A95X
Total noob here but just read you got the Direct TV Now to stream on the Nexbox A95X. If you find time I would appreciate some assistance in getting mine to work.
Thanks, Todd
Takenover83 said:
Are you using the tronsmart rom, or stock rom? Currently trying to get this working with the tronsmart rom on my a95x. So far just editing the build.prop and removing root has not been enough. More details would be awesome. Thanks.
Click to expand...
Click to collapse

338lm said:
Just to confirm, you got Directv Now working with Pure Nexus? I'm on Pure Nexus 7.1.1 and still getting error 40 after changing build.prop
Click to expand...
Click to collapse
Same here bro if you figure out how to get it to work let us now please
Sent from my Nexus 6P using XDA-Developers mobile app

rom advice needed.

newbie question this so forgive me being so niave.
i have a samsung galaxy note 4...its my old phone i have as a spare.
at one stage i had lineage os on it and it was fantastic, slick, fast, clean with superb battery life....but the lineage os for the note 4 was unofficial and was pre-rooted...which meant some apps dont work... snapchat an obvious one.
so... what are my options on roms that are stock android like...which wont be rooted and be stable ?
thanks in advance for any replies.
Sent from my SM-G955F using Tapatalk

dougm1970 said:
newbie question this so forgive me being so niave.
i have a samsung galaxy note 4...its my old phone i have as a spare.
at one stage i had lineage os on it and it was fantastic, slick, fast, clean with superb battery life....but the lineage os for the note 4 was unofficial and was pre-rooted...which meant some apps dont work... snapchat an obvious one.
so... what are my options on roms that are stock android like...which wont be rooted and be stable ?
thanks in advance for any replies.
Sent from my SM-G955F using Tapatalk
Click to expand...
Click to collapse
U have on this site SuperDeodexedRom that isnt rooted by default: https://forum.xda-developers.com/note-4/development/rom-t3768967
... And U have also Like Stok based if U choose A5 system UI, fast and smooth:
https://forum.xda-developers.com/note-4/development/air-rom-v1-0-t3630284
And so one... Using both on both N4,,, Great roms Stock to near Stock based...

RamHa said:
U have on this site SuperDeodexedRom that isnt rooted by default: https://forum.xda-developers.com/note-4/development/rom-t3768967
... And U have also Like Stok based if U choose A5 system UI, fast and smooth:
https://forum.xda-developers.com/note-4/development/air-rom-v1-0-t3630284
And so one... Using both on both N4,,, Great roms Stock to near Stock based...
Click to expand...
Click to collapse
Air rom unfortunately you can't use some apps due to prerooted rom.
The first rom I used it but if you use any note 7 port the old ui seems outdated. I wish I could unroot someway the Air Rom which I use for daily driver but unfortunately I can't use an app that I need because it's prerooted.

ioannis_m said:
Air rom unfortunately you can't use some apps due to prerooted rom.
The first rom I used it but if you use any note 7 port the old ui seems outdated. I wish I could unroot someway the Air Rom which I use for daily driver but unfortunately I can't use an app that I need because it's prerooted.
Click to expand...
Click to collapse
Why dont U ask dev to Unroot it 4 u???? Give it a try. And as always U can unroot it by installing non rooted kernel after installing rom or inject non rooted kernel into Rom.zip. But, ask Dev, rom is great.
And, Note 7 Ports 4 me r better than s8 etc ports

RamHa said:
Why dont U ask dev to Unroot it 4 u???? Give it a try. And as always U can unroot it by installing non rooted kernel after installing rom or inject non rooted kernel into Rom.zip. But, ask Dev, rom is great.
And, Note 7 Ports 4 me r better than s8 etc ports
Click to expand...
Click to collapse
I already tried to unroot the rom with spacelemon non root version but still the app can't play at the device due to root existance. I

ioannis_m said:
I already tried to unroot the rom with spacelemon non root version but still the app can't play at the device due to root existance. I
Click to expand...
Click to collapse
When you are saying some apps are you talking about safetynet getting tripped? Why not just flash Spacelemon non-rooted and flash latest magisk with prop hide module to get it to work. I was able to pass safetynet with the latest version of AirRom at the time.

dougm1970 said:
newbie question this so forgive me being so niave.
i have a samsung galaxy note 4...its my old phone i have as a spare.
at one stage i had lineage os on it and it was fantastic, slick, fast, clean with superb battery life....but the lineage os for the note 4 was unofficial and was pre-rooted...which meant some apps dont work... snapchat an obvious one.
so... what are my options on roms that are stock android like...which wont be rooted and be stable ?
thanks in advance for any replies.
Sent from my SM-G955F using Tapatalk
Click to expand...
Click to collapse
No worries for you being a newbie, but I just wanted to clarify that you can actually use restricted apps like Snapchat (created a burner account since I don't use it), Netflix, and Android Pay, etc.
Requirements:
- Lastest build from Bonuzzz (Mar.)
- Some basic knowledge on working Magisk
- Download Terminal app
- Possibly a third party file manager (ex. Solid Explorer, ES Files Explorer, etc.)
Steps:
- You need to download this and flash it in your recovery to remove pre-root from your device. https://mirrorbits.lineageos.org/su/addonsu-remove-15.1-arm-signed.zip
- Head over to the Magisk thread and download the latest version of Magisk (16.0). https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
- Flash Magisk in your recovery and and open the Magisk Manager and update it when prompted.
- Head over back to the Magisk thread and download the MagiskHide Props Config module. https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-simple-t3765199
- Open back up Magisk Manager click on the three dashes on the top left and click on the modules tab. Press the button that shows a plus sign and locate the module that you downloaded/saved on your device.
- It should then start flashing through the manager and prompt you to reboot.
- After reboot, download any terminal app (preferably Termux) and open it.
- Type in "Su" and grant it root access. Next, type "props" and it should open up onto an interface.
- Type in "1" to change your device fingerprint and type in "f" to pick a certified fingerprint.
- From here, you can choose whichever certified fingerprint your device wants to be recognized as (I used Samsung Note 5).
- After choosing your certified fingerprint, it will ask you to reboot.
- After reboot, head back into Magisk Manager and click on the SafetyNet Check (It might prompt you to download something). Eventually you should get the same test like in my picture.
- (Optional) Head back into recovery and wipe dalvik cache/cache.
Hopefully this helps out on your problem on apps not working or not letting you install them. Also, this can work for others too that don't use lineage but other Custom ROMs (AirRom, Nemesis, etc.). All you need to do is just install the latest SpaceLemon Non-rooted Kernel or manually unroot and continue with the steps on "Heading over to Magisk Threads". I do hope that this worked for others, and sorry if the instructions are either too long or really complicated on following.

RetroSpect_17 said:
When you are saying some apps are you talking about safetynet getting tripped? Why not just flash Spacelemon non-rooted and flash latest magisk with prop hide module to get it to work. I was able to pass safetynet with the latest version of AirRom at the time.
Click to expand...
Click to collapse
True, and yes, that is solution! :highfive:

RetroSpect_17 said:
When you are saying some apps are you talking about safetynet getting tripped? Why not just flash Spacelemon non-rooted and flash latest magisk with prop hide module to get it to work. I was able to pass safetynet with the latest version of AirRom at the time.
Click to expand...
Click to collapse
No even with non rooted kernel and magisk hide props and safetynet passes correctly the app does not start due to root existance.I don't know what else to do.
RamHa said:
True, and yes, that is solution! :highfive:
Click to expand...
Click to collapse
For me the only solution was to flash the no root stock deodexed rom you wrote above earlier today. With air rom and doing every step to pass safetynet correctly the app recognises root whatever I do.

Just saying, but please don't create a thread like this on the Android Development page again.
Quoted from the rules post: https://forum.xda-developers.com/note-4/development/rules-posting-development-t2868781
"Only the following topics are allowed in DEVELOPMENT area:
[DEV] - Development for any special projects or Apps
[ROM] - Custom ROMs
[KERNEL] - Custom Kernels (usually found in Original Development)
[MOD] - Hack & Modifications for the phone with code only, zips go in themes and apps
[FIX] - Fixes for known issues & bugs
[R&D] - Research & Development for Devs only, when gathering data for a new projects
[HOWTO] / [GUIDE] - How to instructions and Guides (Most of the time should be in General)"

[FORTNITE] Play Fortnite android w/o root and with root (unlocked bootloader)

Play Fortnite on a rooted or unrooted device with that unlocked bootloader​
Hi XDA, I want to show you how to play fortnite with an unlocked bootloader without and with root, here are the steps
Disclaimer: This method will stop the use of magisk modules and magisk hide denies superuser privileges for the root apps hidden, proceed at your own risk and I am not responsible if your account gets banned or for the normal reasons (Thermonuclear war, etc.)​
Without Root
Flash one of these kernels listed
KingKernel by kingbri (self promotion)
Flash Kernel by NathanChance
Stock Kernel with safetynet patch
Use EX kernel manager to check if the kernel is installed
Disable USB debugging
Install Fortnite
Profit
With R00T (Magisk modules will not work with this method)
Flash magisk and one of the kernels listed in the unrooted guide
Open magisk manager and grant superuser to all root apps (This is important later)
Open Fortnite installer and install fortnite but DO NOT OPEN IT
Use magisk hide and manually check all of your root apps + the fortnite installer and fortnite app
go into magisk manager settings
Click the "hide magisk manager option"
wait until the app closes out and a few seconds after that
enable magisk core mode in magisk manager settings
Open a file manager and delete the magisk manager folder as well as other folders such as EX or Alogcat
Disable USB debugging
Launch Fortnite
Profit
Always remember to un-hide root apps when you want to use them and hide them when using fortnite, otherwise, you will be kicked for their stupid "security"
Need an invite? Here's a fix
Open up build.prop in a file manager that is NOT CHECKED ON MAGISK HIDE
Edit build.prop to have these lines
ro.product.brand=samsung
ro.product.manufacturer=samsung
ro.build.product=star2lte
ro.product.device=star2lte
ro.product.model=SM-G965F
ro.product.name=star2ltexx
Save and reboot
Open magisk manager and magisk hide that file manager
Open Fortnite
You should be able to sign in
If you want to, revert your build.prop to the original settings and you will magically be invited since you participated on a "Samsung Device"
Feel free to rant about Epic games security here, because i'm pretty pissed at them for doing this.
Thanks to this youtube video for showing me how to bypass root checks https://www.youtube.com/watch?v=ystVcsFjJaE&t=157s

Mine

Mine again

kernel
those kernels listed are only for pixel devices right?
can you link me a working kernel for Oneplus 5 please.

edmond.yv said:
those kernels listed are only for pixel devices right?
can you link me a working kernel for Oneplus 5 please.
Click to expand...
Click to collapse
In a pixel forum?

No, when I go to the the kernels he linked I saw that the stock kernel with safetynet bypass was for pixel devices. I need a kernel with safetynet bypass but for my OnePlus 5

edmond.yv said:
No, when I go to the the kernels he linked I saw that the stock kernel with safetynet bypass was for pixel devices. I need a kernel with safetynet bypass but for my OnePlus 5
Click to expand...
Click to collapse
What y2grae is saying is that this is a Pixel XL forum, so obviously the kernels will be for Pixels and this method has most likely only been tested on a Pixel XL. You could find your own kernels and see if this method works for your phone as well.
I can confirm that following this guide worked for me. I can for the first time play Fortnite on my phone.
Edit: I just uninstalled the Fortnite Installer once Fortnite was installed. I don't see the point in keeping it unless I am missing something.

LeMoise said:
What y2grae is saying is that this is a Pixel XL forum, so obviously the kernels will be for Pixels and this method has most likely only been tested on a Pixel XL. You could find your own kernels and see if this method works for your phone as well.
I can confirm that following this guide worked for me. I can for the first time play Fortnite on my phone.
Edit: I just uninstalled the Fortnite Installer once Fortnite was installed. I don't see the point in keeping it unless I am missing something.
Click to expand...
Click to collapse
You must keep the Fortnite installer installed. It's what installs updates to the game, and you cannot play on an un-updated game.

stupid question, but i played it on my galaxy s8. but how do i install it on my essential phone now? i dont have any invites. its not that i play it mobile but its nice to have. (and im about to unlock and custom rom my essential phone so yeah..) looking to find how to get it working after that

There is a Reddit Thread that makes it appear like installing Fortnite from Samsungs Galaxy Apps will give you a chance at getting the Galaxy Skin.
I might try using my build prop editor/Galaxy Apps apk and seeing if I have any luck.
Anyone have any input or thoughts about why this might or might not work?
Edit: Seems to be working so far. I changed my build prop, downloaded the installer again and a pop up displayed saying "play 3 matches and unlock the skin in 24-48 hours. Only time will tell if I get it.

LeMoise said:
There is a Reddit Thread that makes it appear like installing Fortnite from Samsungs Galaxy Apps will give you a chance at getting the Galaxy Skin.
I might try using my build prop editor/Galaxy Apps apk and seeing if I have any luck.
Anyone have any input or thoughts about why this might or might not work?
Edit: Seems to be working so far. I changed my build prop, downloaded the installer again and a pop up displayed saying "play 3 matches and unlock the skin in 24-48 hours. Only time will tell if I get it.
Click to expand...
Click to collapse
Do you have the build.prop for the note 9?

kingbri said:
Do you have the build.prop for the note 9?
Click to expand...
Click to collapse
ro.product.brand=samsung
ro.product.manufacturer=samsung
ro.build.product=crownlte
ro.product.device=crownlte
ro.product.model=SM-N960F
ro.product.name=crownltexx
Edit: I have a link to the whole buildprop if you'd rather download the whole txt file. That can be found here.

LeMoise said:
ro.product.brand=samsung
ro.product.manufacturer=samsung
ro.build.product=crownlte
ro.product.device=crownlte
ro.product.model=SM-N960F
ro.product.name=crownltexx
Edit: I have a link to the whole buildprop if you'd rather download the whole txt file. That can be found here.
Click to expand...
Click to collapse
Did it work for you? From what I know, after spoofing it to be more 9, you still have to play 3 games but every time you try, it'll kick you out after you jump out of bus which won't let you complete the 3 games you need for he skin.

HParra97 said:
Did it work for you? From what I know, after spoofing it to be more 9, you still have to play 3 games but every time you try, it'll kick you out after you jump out of bus which won't let you complete the 3 games you need for he skin.
Click to expand...
Click to collapse
I was able to play the three games successfully but I don't think I'll be getting the skin from it as I played them over the weekend and it has been well over 48 hours.
There was a thread in the Pixel XL forum that guided you through playing on a rooted device and it works, but editing the build.prop isn't good enough to trick the game into giving you the skin. I read on a reddit thread that the Tab S4 can award the skin multiple times if you factory reset it because there is no imie linked to it so I might try using that instead.

HParra97 said:
Did it work for you? From what I know, after spoofing it to be more 9, you still have to play 3 games but every time you try, it'll kick you out after you jump out of bus which won't let you complete the 3 games you need for he skin.
Click to expand...
Click to collapse
That's what this guide is for, to make sure you don't get kicked

kingbri said:
That's what this guide is for, to make sure you don't get kicked
Click to expand...
Click to collapse
Understood. I have a question: What makes the particular kernels in the first post so special that they pass safety net? I ask because i have a different device (Galaxy Note5) and im not sure which kernel will support passing the latest "invalid response" error that Magisk is currently having. I'm not asking you hunt kernels for me, but what determines it. I looked at the kernels that you suggested on the first post but they didn't mention any notes of patching safety net.
---------- Post added at 04:05 PM ---------- Previous post was at 03:54 PM ----------
LeMoise said:
I was able to play the three games successfully but I don't think I'll be getting the skin from it as I played them over the weekend and it has been well over 48 hours.
There was a thread in the Pixel XL forum that guided you through playing on a rooted device and it works, but editing the build.prop isn't good enough to trick the game into giving you the skin. I read on a reddit thread that the Tab S4 can award the skin multiple times if you factory reset it because there is no imie linked to it so I might try using that instead.
Click to expand...
Click to collapse
Can you let me know if it works for you? If it does I'd like to try it myself but changing the build.prop and see if it's works too, assuming that I bypass the VPN error that I keep getting.

HParra97 said:
Understood. I have a question: What makes the particular kernels in the first post so special that they pass safety net? I ask because i have a different device (Galaxy Note5) and im not sure which kernel will support passing the latest "invalid response" error that Magisk is currently having. I'm not asking you hunt kernels for me, but what determines it. I looked at the kernels that you suggested on the first post but they didn't mention any notes of patching safety net.
---------- Post added at 04:05 PM ---------- Previous post was at 03:54 PM ----------
Can you let me know if it works for you? If it does I'd like to try it myself but changing the build.prop and see if it's works too, assuming that I bypass the VPN error that I keep getting.
Click to expand...
Click to collapse
The Kernels have nothing to do with the 'Invalid Response' that Magisk is giving you. Magisk gives the 'Invalid Response' not because you fail SafetyNet Check but because Google changed how the API works and Magisk hasn't updated yet to work with it. Even with the 'Invalid Response' you most likely still pass the SafetyNet Check. This has been a known issue for a week or so now.
I believe he chose those Kernels because they include a few extra measures used to hide root/ pass safetynet.

reggiexp said:
stupid question, but i played it on my galaxy s8. but how do i install it on my essential phone now? i dont have any invites. its not that i play it mobile but its nice to have. (and im about to unlock and custom rom my essential phone so yeah..) looking to find how to get it working after that
Click to expand...
Click to collapse
I believe that if you were on the samsung beta, you are automatically invited

kingbri said:
I believe that if you were on the samsung beta, you are automatically invited
Click to expand...
Click to collapse
if i go on epic site it still saya thanks for submitting you are on yhe wait list... been like that for 2 weeks even doh i have it on my phone... and played it can't play it on other phone... sucks...

fixed, don't work anymore.

Moto G4 Plus [XT1643] [HELP] Build Prop cant be modified?

Can Someone tell me way to modify build prop of moto g4 plus to moto z force or some samsung galaxy device like s7/s8
Tried to edit with build.prop app from playstore and manually from es root explorer file with R/W checked up
No matter brand/device/model changed whenever system check app is used its still official one
Please guide me , Saw most of devices like xiaomi are able to change to samsung then why is moto limited and whats causing this problem despite of root

TechNubb said:
Can Someone tell me way to modify build prop of moto g4 plus to moto z force or some samsung galaxy device like s7/s8
Tried to edit with build.prop app from playstore and manually from es root explorer file with R/W checked up
No matter brand/device/model changed whenever system check app is used its still official one
Please guide me , Saw most of devices like xiaomi are able to change to samsung then why is moto limited and whats causing this problem despite of root
Click to expand...
Click to collapse
You want to play Fortnite? Also you didn't mention if you have root at all, nothing about your software side setup you provide
Nevertheless, if you want Fortnite running, we'll, check out the requirements hardware side and some tests like here https://www.xda-developers.com/fortnite-mobile-android-testing-performance/
If it's not about the game, please tell why you want to spoof the manufacturer/model.

strongst said:
You want to play Fortnite? Also you didn't mention if you have root at all, nothing about your software side setup you provide
Nevertheless, if you want Fortnite running, we'll, check out the requirements hardware side and some tests like here https://www.xda-developers.com/fortnite-mobile-android-testing-performance/
If it's not about the game, please tell why you want to spoof the manufacturer/model.
Click to expand...
Click to collapse
Yah, need it for fortnite , bought gltools for it
I'm running 64 bit unofficial pixel experience custom rom
Yah, my phone is rooted with magisk installed
App, I used for checking system info was DevCheck from playstore

TechNubb said:
Yah, need it for fortnite , bought gltools for it
I'm running 64 bit unofficial pixel experience custom rom
Yah, my phone is rooted with magisk installed
App, I used for checking system info was DevCheck from playstore
Click to expand...
Click to collapse
Adreno 530 is minimum requirement and Adreno 405 is in your device.
I guess you tried that method https://forum.xda-developers.com/android/general/fortnite-root-device-t3827880 ?

strongst said:
Adreno 530 is minimum requirement and Adreno 405 is in your device.
I guess you tried that method https://forum.xda-developers.com/android/general/fortnite-root-device-t3827880 ?
Click to expand...
Click to collapse
Yah, actually i saw these ytber run on adreno 306 ,2gb ram
Galaxy A5 https://www.youtube.com/watch?v=ystVcsFjJaE

strongst said:
Adreno 530 is minimum requirement and Adreno 405 is in your device.
I guess you tried that method https://forum.xda-developers.com/android/general/fortnite-root-device-t3827880 ?
Click to expand...
Click to collapse
Why tho, I cant change build prop of moto g4 plus!
changing it still doesnt reflect in any system check app nor in fortnite installer
whereas xiaomi was able to spoof it