Directv Now Error 40 (Failed Security Check) - Nexus 6P Q&A, Help & Troubleshooting

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

Related

[ICS build.prop] Official ICS, Chinese build's, Eos nightly 36 -fixes Gameloft games!

UPDATE/NOTE: Only the official ICS build and the Chinese build's build.prop files fixes games by Gameloft and some others. Some will still freeze, though.
I'm posting this for those who wish to know the difference between the two since the build.prop from the Chinese ICS' build has most games (mainly Gameloft) working again. In case some of you wish to customize a build.prop of your own, this should be a good place to start. Keep in mind that what I'm doing here is simply showing both build.prop differences. Nothing more.
I did a comparison between the two using the Eos nightly (#36) one as the "original" to be compared against. Here are the results:
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=[U][COLOR="Red"]IML77[/COLOR][/U][B][COLOR="Blue"]I.7.1-14[/COLOR][/B]
ro.build.display.id=[U][COLOR="Red"]EOS IML74K Nightly 36[/COLOR][/U][b][COLOR="Blue"]wifi_hubble-userdebug 4.0.3 I.7.1-14 1325304510 test-keys[/COLOR][/b]
ro.build.version.incremental=[U][COLOR="Red"]eng.buildbot.20120113.032705[/COLOR][/U][B][COLOR="Blue"]1325304510[/COLOR][/B]
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.3
ro.build.date=Fri [u][COLOR="Red"]Jan 13 03:27:32 PST 2012[/COLOR][/u][b][COLOR="Blue"]Dec 30 21:45:39 CST 2011[/COLOR][/b]
ro.build.date.utc=[U][COLOR="Red"]1326454052[/COLOR][/U][B][COLOR="Blue"]1325303139[/COLOR][/B]
ro.build.type=[U][COLOR="Red"]eng[/COLOR][/U][B][COLOR="Blue"]userdebug[/COLOR][/B]
ro.build.user=[U][COLOR="Red"]buildbot[/COLOR][/U][B][COLOR="Blue"]hudsoncm[/COLOR][/B]
ro.build.host=[U][COLOR="Red"]typhoon[/COLOR][/U][B][COLOR="Blue"]il93lnxdroid48[/COLOR][/B]
ro.build.tags=test-keys
ro.product.model=[U][COLOR="Red"]Xoom[/COLOR][/U][B][COLOR="Blue"]MZ604[/COLOR][/B]
ro.product.brand=[U][COLOR="Red"]motorola[/COLOR][/U][B][COLOR="Blue"]MOTO[/COLOR][/B]
ro.product.name=[U][COLOR="Red"]tervigon[/COLOR][/U][B][COLOR="Blue"]wifi_hubble[/COLOR][/B]
ro.product.device=[U][COLOR="Red"]wingray[/COLOR][/U][B][COLOR="Blue"]wifi_hubble[/COLOR][/B]
ro.product.board=
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Motorola
ro.product.locale.language=[U][COLOR="Red"]en[/COLOR][/U][B][COLOR="Blue"]zh[/COLOR][/B]
ro.product.locale.region=[U][COLOR="Red"]US[/COLOR][/U][B][COLOR="Blue"]TW[/COLOR][/B]
ro.wifi.channels=
ro.board.platform=tegra
# ro.build.product is obsolete; use ro.product.device
ro.build.product=[U][COLOR="Red"]wingray[/COLOR][/U][B][COLOR="Blue"]wifi_hubble[/COLOR][/B]
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=[U][COLOR="Red"]tervigon-user[/COLOR][/U][B][COLOR="Blue"]wifi_hubble-userdebug[/color][/B] 4.0.3 [U][COLOR="Red"]IML77 239789 release[/COLOR][/U][B][COLOR="Blue"]I.7.1-14 1325304510 test[/COLOR][/B]-keys
ro.build.fingerprint=[U][COLOR="Red"]motorola/tervigon/wingray:4.0.3/IML77/239789:user/release[/COLOR][/U][B][COLOR="Blue"]MOTO/wifi_hubble/wifi_hubble:4.0.3/I.7.1-14/1325304510:userdebug/test[/COLOR][/B]-keys
ro.build.characteristics=tablet
# end build properties
# RIL and telephony related settings
rild.libargs=-d /dev/chnlat10
rild.libpath=/system/lib/libmoto_ril.so
persist.ril.mux.ttydevice=/dev/usb/tty2-1:1.2
persist.ril.mux.noofchannels=8
persist.ril.modem.mode=1
persist.ril.modem.ttydevice=/dev/usb/tty2-1:1.4
ro.telephony.default_network=4
# The OpenGL ES API level that is natively supported by this device.
# This is a 16.16 fixed point number
ro.opengles.version = 131072
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.[U][COLOR="Red"]com.android.dateformat=MM-dd-yyyy[/COLOR][/U][B][COLOR="Blue"]build.version.full=Blur_Version.71.0.14.MZ604.Retail.en.05
ro.mot.setuptype=2[/COLOR][/B]
ro.config.ringtone=[U][COLOR="Red"]Ring_Synth_04.[/COLOR][/U][B][COLOR="Blue"]Sceptrum.[/COLOR][/B]ogg
ro.config.notification_sound=[u][COLOR="Red"]pixiedust[/COLOR][/u][B][COLOR="Blue"]Cobalt[/COLOR][/B].ogg
ro.config.alarm_alert=[U][COLOR="Red"]Alarm_Classic[/COLOR][/U][B][COLOR="Blue"]Cesium[/COLOR][/B].ogg
[B][COLOR="Blue"]keyguard.no_require_sim=true[/COLOR][/B]
[I][COLOR="YellowGreen"]ro.setupwizard.mode=OPTIONAL[/COLOR][/I]
[B][COLOR="Blue"]drm.service.enabled=true[/COLOR][/B]
wifi.interface=wlan0
wifi.supplicant_scan_interval=15
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
ro.[U][COLOR="Red"]kernel.android.checkjni=1[/COLOR][/U][B][COLOR="Blue"]com.google.gmsversion=4.0_r0[/COLOR][/B]
[I][COLOR="Green"]ro.setupwizard.mode=OPTIONAL[/COLOR][/I]
[B][COLOR="Blue"]dalvik.vm.lockprof.threshold=500[/COLOR][/B]
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Key:
Underline = Deletion
Bold = Insertion
Italic = Moved from
Italic = Moved to
I added the files for download for those of you who want to build your own and get the games working. This is only good until Team Eos includes updated build.prop in future nightlies.
UPDATE: Thanks to tcrews for providing the official ICS Xoom build.prop. The attached zip now contains all three build.prop files. I also attached the comparison file in Word format which compares all three build.prop files.
UPDATE 2: Thanks gffmac for the flashable official OTA build.prop.
Please report back if you have games that worked fine in Honeycomb that no longer worked when you switched to ICS but is now working again with ICS using a customized build.prop.
All my games worked fine in Honeycomb but some stopped working in ICS. Upon using the build.prop from the Chinese build, all my Gameloft games are working again. Zombie Rider (non-Gameloft), which didn't work upon flashing ICS roms, works with the build.prop but only briefly. It then FCs.
This one may work better....from the official Xoom ICS update..
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=IML77
ro.build.display.id=IML77
ro.build.version.incremental=239789
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.3
ro.build.date=Fri Dec 16 21:20:15 UTC 2011
ro.build.date.utc=1324070415
ro.build.type=user
ro.build.user=android-build
ro.build.host=vpbs27.mtv.corp.google.com
ro.build.tags=release-keys
ro.product.model=Xoom
ro.product.brand=motorola
ro.product.name=tervigon
ro.product.device=wingray
ro.product.board=
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Motorola
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
# ro.build.product is obsolete; use ro.product.device
ro.build.product=wingray
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=tervigon-user 4.0.3 IML77 239789 release-keys
ro.build.fingerprint=motorola/tervigon/wingray:4.0.3/IML77/239789:user/release-keys
ro.build.characteristics=tablet
# end build properties
# RIL and telephony related settings
rild.libargs=-d /dev/chnlat10
rild.libpath=/system/lib/libmoto_ril.so
persist.ril.mux.ttydevice=/dev/usb/tty2-1:1.2
persist.ril.mux.noofchannels=8
persist.ril.modem.mode=1
persist.ril.modem.ttydevice=/dev/usb/tty2-1:1.4
ro.telephony.default_network=4
# The OpenGL ES API level that is natively supported by this device.
# This is a 16.16 fixed point number
ro.opengles.version = 131072
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.config.ringtone=Sceptrum.ogg
ro.config.notification_sound=Cobalt.ogg
ro.config.alarm_alert=Cesium.ogg
keyguard.no_require_sim=true
ro.setupwizard.mode=OPTIONAL
drm.service.enabled=true
wifi.interface=wlan0
wifi.supplicant_scan_interval=15
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
ro.com.android.wifi-watchlist=GoogleGuest
ro.error.receiver.system.apps=com.google.android.feedback
ro.setupwizard.enterprise_mode=1
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.clientidbase=android-google
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Click to expand...
Click to collapse
ZEN Pinball THD
GOF 2 THD
Nova 2
Modern combat 2
havent tested more
tcrews said:
This one may work better....from the official Xoom ICS update..
Click to expand...
Click to collapse
Thanks! I'll give this a try and do a comparison, too.
LPHS said:
ZEN Pinball THD
GOF 2 THD
Nova 2
Modern combat 2
havent tested more
Click to expand...
Click to collapse
I have the same results, too.
tcrews said:
This one may work better....from the official Xoom ICS update..
Click to expand...
Click to collapse
can anyone confirm this? and is it possible to get a CWM flashable zip?
shakuyi said:
can anyone confirm this? and is it possible to get a CWM flashable zip?
Click to expand...
Click to collapse
I'm testing it right now. I'll report back in a minute.
How are u guys changing this are you just flashing the zip after the nightly or using advanced thanks I've been wanting to play my games would b nice to have
shaggy5991 said:
How are u guys changing this are you just flashing the zip after the nightly or using advanced thanks I've been wanting to play my games would b nice to have
Click to expand...
Click to collapse
build.prop files can be edited directly from Root Explorer or similar file managers with root access and preferably with the capability to mount R/W access.
Of course, it's tedious to edit line by line especially with an on-screen virtual keyboard so you can download the file instead and copy and paste it under /system. Don't forget to backup your original build.prop by renaming with a .bak extension or something similar.
Okay, so I just tested and can confirm that the official stock ICS for Xoom's build.prop works just like the Chinese build's. In terms of Chinese build vs. official build, the games that freezes still freezes and the games the used to not work but now works still works.
I'll update the OP.
can you upload the build prop of the official ota
LPHS said:
can you upload the build prop of the official ota
Click to expand...
Click to collapse
+1
Sent from my Xoom using Tapatalk
LPHS said:
can you upload the build prop of the official ota
Click to expand...
Click to collapse
banny7000 said:
+1
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
Yup, it's in the OP. I just updated it. If you want to copy and paste tcrews' post, it's also there in page 1.
Can Simone put together a flashable zip so we can flash it with every nightly
shaggy5991 said:
Can Simone put together a flashable zip so we can flash it with every nightly
Click to expand...
Click to collapse
You can simply open the nightly zip, delete the build.prop in the /system folder and drop the one you want in there. I'd make one but I'm busy at work and I'm about to head home. (Woohoo! Long weekend awaits!)
shaggy5991 said:
Can Simone put together a flashable zip so we can flash it with every nightly
Click to expand...
Click to collapse
Try this, let me know if it works.
gffmac said:
Try this, let me know if it works.
Click to expand...
Click to collapse
Zip worked but Gameloft games are still not working for me. I tried asphault gt, uno, and galaxy on fire 2 ( which I realize is not a gameloft game but failed just the same
Tried the Zip
I tried the zip file, games worked but Verizon 4G wouldn't activate with the build prop as written. Had to go back to TeamEOS' original. I'm going to try to hack up a version that'll work with Verizon's service.
Hi, I have another chinese tablet PC and I tried your tweak, it works great ! Gameloft games appear now.
But I still don't see many apps on the Market, such as Facebook. Does facebook appear on your market ?
Thanks a lot !
The latest nightly from Team Eos should work for most games now. These build.props are no longer needed.

[ROM] I9100UHLB2 [14.02.2012][Android 2.3.6]

PDA: I9100UHLB2
PHONE: I9100UHKK1
CSC: I9100ZTOLB2
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=GINGERBREAD
ro.build.display.id=GINGERBREAD.UHLB2
ro.build.version.incremental=UHLB2
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.6
ro.build.date=Tue Feb 14 19:05:43 KST 2012
ro.build.date.utc=1329213943
ro.build.type=user
ro.build.user=se.infra
ro.build.host=SEP-69
ro.build.tags=release-keys
ro.product.model=GT-I9100
ro.product.brand=samsung
ro.product.name=GT-I9100
ro.product.device=GT-I9100
ro.product.board=GT-I9100
ro.product.cpu.abi=armeabi-v7a
# Samsung Specific Properties
ro.build.PDA=I9100UHLB2
ro.build.hidden_ver=I9100UHLB2
ro.build.changelist=966147
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=s5pc210
# ro.build.product is obsolete; use ro.product.device
ro.build.product=GT-I9100
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=GT-I9100-user 2.3.6 GINGERBREAD UHLB2 release-keys
ro.build.fingerprint=samsung/GT-I9100/GT-I9100:2.3.6/GINGERBREAD/UHLB2:user/release-keys
# Samsung Specific Properties
ro.build.PDA=I9100UHLB2
ro.build.hidden_ver=I9100UHLB2
ro.build.changelist=966147
ro.tether.denied=false
ro.flash.resolution=1080
# end build properties
Download:
http://hotfile.com/dl/147977848/617a21f/GT-I9100_ZTO_I9100UHLB2_I9100ZTOLB2_I9100UHKK1.zip.html
woot
i thought they were gona stop everything with 2.3.6 and start with 4.0
qwerty warrior said:
woot
i thought they were gona stop everything with 2.3.6 and start with 4.0
Click to expand...
Click to collapse
You were wrong
Armanderli
This is a brazilian rom and my question is:
This rom has multi csc for other languages?
qwerty warrior said:
woot
i thought they were gona stop everything with 2.3.6 and start with 4.0
Click to expand...
Click to collapse
So guess when Brazil will get ICS ... NOT beginning of March for sure
Waiting on intratechs input on this
Sent from my GT-I9100 using xda premium
Mods - CWM Flashable
I flashed this rom today. Feels good, so i made myself a few mods. Just thought of sharing. It will work on odexed too.
It contains a few more apps/mods that i use. Backup before use.
Following are included in the zip file.
1. 1% battery mod ( Green Circle battery )
2. ICS animations
3. Smooth spinners ( credit to hyperdroid team )
4. CRT on/off
5. Slimmer sliders
6. GB Keyboard
7. Lidroid Mod ( Credit to Li )
8. Gallery app with Sony Bravia Engine ( Credit to ykk_five )
9. A few more that i forget...
Get it from here.
Is this rom more to the style of WXLA4 with the ICS type answer / reject call icons??
kersey said:
Is this rom more to the style of WXLA4 with the ICS type answer / reject call icons??
Click to expand...
Click to collapse
Yes.
Sent from my GT-I9100 using Tapatalk
Better than LA4?
superleeds27 said:
Better than LA4?
Click to expand...
Click to collapse
Can't say. Looks similar.
Sent from my GT-I9100 using Tapatalk
Think I'll give it a try this evening as i think ICS is some weeks away yet.
Sent from my GT-I9100 using Tapatalk
The newest?
Is the browser back to normal here or still a wobbly mess like in LA4 and XILA2? What i mean is does it lock onto text properly again without wobbling left and right while scrolling..
Sent from my GT-I9100 using Tapatalk
xath23 said:
Is the browser back to normal here or still a wobbly mess like in LA4 and XILA2? What i mean is does it lock onto text properly again without wobbling left and right while scrolling..
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
That's sorted out in this build.
Anyone nice enough to make this a CWM flashable zip?
Mobile ODIN Pro to the rescue here
sileshnair said:
I flashed this rom today. Feels good, so i made myself a few mods. Just thought of sharing. It will work on odexed too.
It contains a few more apps/mods that i use. Backup before use.
Following are included in the zip file.
1. 1% battery mod ( Green Circle battery )
2. ICS animations
3. Smooth spinners ( credit to hyperdroid team )
4. CRT on/off
5. Slimmer sliders
6. GB Keyboard
7. Lidroid Mod ( Credit to Li )
8. Gallery app with Sony Bravia Engine ( Credit to ykk_five )
9. A few more that i forget...
Get it from here.
Click to expand...
Click to collapse
very thanks my brother.
downloading rom to test your mod.
superleeds27 said:
Better than LA4?
Click to expand...
Click to collapse
Flashed it this afternoon and all is well. It is as good as LA4
One difference I have found is that it comes with Google+ and Messenger+ and no Gmail app, which I don't think was the case with LA4.
kersey said:
Flashed it this afternoon and all is well. It is as good as LA4
One difference I have found is that it comes with Google+ and Messenger+ and no Gmail app, which I don't think was the case with LA4.
Click to expand...
Click to collapse
weird, that shouldn't be the case...
try going to "Privacy" and restoring everything from there... It will restore and re-install the CSC aswell ...
Marcio_Bianco said:
weird, that shouldn't be the case...
try going to "Privacy" and restoring everything from there... It will restore and re-install the CSC aswell ...
Click to expand...
Click to collapse
I've flashed (via Mobile Odin) and restored my apps (via Titanium Backup) as I usually do using a XEU CSC and have never noticed Google+ there or Gmail missing.
This actually suits me better as I normally remove Gmail and use Kaiten instead

[Stock Official Firmwares] I9300XXBLG8(4.0.4) - United Kingdom (BTU) [27-07-12]

hi new fw probbably the fix for search
http://www.hotfile.com/dl/164621029/66b622f/I9300XXBLG8_I9300OXABLG8_BTU.zip.html
thx to samfirmware!
Is it rooted
Sent from my GT-I9300 using xda premium
port76 said:
Is it rooted
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
no no it is stock directly from samsung
this must be awesome update
Hi to all I am using the LG6 firmware when I check for updates via the phone it downloads the new firmware and reboots to update when it arrives at 28% i get the exclamation error ... any ideas why please?
Can anybody try if voodoo sim unlock works with this fw? Thanks in advance.
Just downloaded LG8, can confirm search is back.
Man I only flashed my phone yesterday which removed the search, now it's back... Which is it Samsung
Sent from my GT-I9300 using xda app-developers app
does somebody find a changelog for this firmware?
except the google search?
Launcher redraw
Is the launcher redraw (after exiting RAM intensive tasks) solved?
I'm interested in Apex and Nova as I do not use TW, in my experience any way they behave in a similar way from this view point!
Thanks.
vittogn said:
Is the launcher redraw (after exiting RAM intensive tasks) solved?
I'm interested in Apex and Nova as I do not use TW, in my experience any way they behave in a similar way from this view point!
Thanks.
Click to expand...
Click to collapse
Using Apex you can anyways avoid redraw by checking "keep in memory"
Can some one please post an insecure kernel for this rom?
Regards
watsa said:
Using Apex you can anyways avoid redraw by checking "keep in memory"
Click to expand...
Click to collapse
It doesn't work for me.
I have a 6 home pages set up. They all are pretty full of scrollable widget.
Both Nova and Apex have a 40 MB RAM usage, but I read RAM quantity is not the issue.
Sent from my GT-I9300 using Tapatalk 2
davidd6 said:
does somebody find a changelog for this firmware?
except the google search?
Click to expand...
Click to collapse
The changelog is the same as LG6, the only difference is a new modem which you can flash by itself and the reintroduction of local search.
I9300XXBLG8
Base Firmware: I9300XXBLG8(4.0.4)
Modem: I9300XXLG8
CSC: I9300OXABLG8
Build Date: 26-07-2012
Changlist: 928452
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=IMM76D
ro.build.display.id=IMM76D.I9300XXBLG8
ro.build.version.incremental=I9300XXBLG8
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.4
ro.build.date=Thu Jul 26 12:15:02 KST 2012
ro.build.date.utc=1343272502
ro.build.type=user
ro.build.user=se.infra
ro.build.host=SEP-107
ro.build.tags=release-keys
ro.product.model=GT-I9300
ro.product.brand=samsung
ro.product.name=m0xx
ro.product.device=m0
ro.product.board=smdk4x12
ro.product.cpu.abi=armeabi-v7a
ro.product_ship=true
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=GB
ro.wifi.channels=
ro.board.platform=exynos4
# ro.build.product is obsolete; use ro.product.device
ro.build.product=m0
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=m0xx-user 4.0.4 IMM76D I9300XXBLG8 release-keys
ro.build.fingerprint=samsung/m0xx/m0:4.0.4/IMM76D/I9300XXBLG8:user/release-keys
ro.build.characteristics=default
# Samsung Specific Properties
ro.build.PDA=I9300XXBLG8
ro.build.hidden_ver=I9300XXBLG8
ro.build.changelist=928452
# end build properties
Download:
Hotfile direct link:
https://hotfile.com/dl/164641212/ab9b296/GT-I9300_BTU_I9300XXBLG8_I9300OXABLG8_I9300XXLG8.zip.html
here's the official ota update.zip. THIS IS ONLY FOR THOSE COMING FROM LG6 to LG8. that's 5.40MB file.
copied from cache/fota folder.
hope this could help the devs see what other changes/updates were made since it consists of more apk's than just the well known localized search.
aside from other apk's, there is also a patch folder.
:good:
http://forum.xda-developers.com/attachment.php?attachmentid=1224986&d=1343391390
by the way those coming from BLFB, will need what i read in the other thread the 20+MB OTA update.
since that poster said he's from lg6 same as mine, and his friend was coming from BLFB and mentioned it was 20+MB.
:victory:
vittogn said:
It doesn't work for me.
I have a 6 home pages set up. They all are pretty full of scrollable widget.
Both Nova and Apex have a 40 MB RAM usage, but I read RAM quantity is not the issue.
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
Seems to be better. So far after flashing no redraw (Nova) even after extensive browsing session!
Sent from my GT-I9300 using Tapatalk 2
Ugh, stop opening identical threads, this needs to go in the official FW thread:
http://forum.xda-developers.com/showthread.php?t=1646610
thread closed, please post if the main firmware thread
http://forum.xda-developers.com/showthread.php?t=1646610
regards
Chris

[ROM] N7000XXLRQ [28.08.2012][Android 4.0.4]

N7000XXLRQ
Base Firmware: N7000XXLRQ(4.0.4)
Modem: N7000XXLRK
CSC: N7000DBTLRQ
Build Date: 28-08-2012
Changlist: 1068447
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=IMM76D
ro.build.display.id=IMM76D.XXLRQ
ro.build.version.incremental=XXLRQ
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.4
ro.build.date=Tue Aug 28 15:48:42 KST 2012
ro.build.date.utc=1346136522
ro.build.type=user
ro.build.user=se.infra
ro.build.host=SEP-86
ro.build.tags=release-keys
ro.product.model=GT-N7000
ro.product.brand=samsung
ro.product.name=GT-N7000
ro.product.device=GT-N7000
ro.product.board=smdk4210
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=GB
ro.wifi.channels=
ro.board.platform=exynos4
# ro.build.product is obsolete; use ro.product.device
ro.build.product=GT-N7000
ro.tether.denied=false
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=GT-N7000-user 4.0.4 IMM76D XXLRQ release-keys
ro.build.fingerprint=samsung/GT-N7000/GT-N7000:4.0.4/IMM76D/XXLRQ:user/release-keys
ro.build.characteristics=phone
# Samsung Specific Properties
ro.build.PDA=N7000XXLRQ
ro.build.hidden_ver=N7000XXLRQ
ro.build.changelist=1068447
# end build properties
Download:
https://hotfile.com/dl/170548186/9f14672/GT-N7000_DBT_N7000XXLRQ_N7000DBTLRQ_N7000XXLRK.zip.html
You test this one already?
I am downloading it but hotfile is very slow. Whoever downloaded and installed it, kindly confirm whether this has updates as in chinese rom for note.
http://forum.xda-developers.com/showpost.php?p=31086185&postcount=1
Has anybody tried this and confirmed it works and any changes?
Its in Checkfus as well, so its official. Quicker download than hotfile too
Edit: Interesting, S-Cloud is included. Will flash later to test
Edit: Holy smoke its fast! New setup routine, presumably using the S-cloud features. Backup, settings, MMS, SMS etc. with option to restore. This is Samsung account, not google feature.
Did I mention it flies! Stock kernel
Edit: Alphabetical TW Grid! Yay! I dont have an S3, but will guess its a similar launcher or the same.
EDIT: Rooted via the new SuperSU method in Dr. Ketans thread.
hkgrob said:
Its in Checkfus as well, so its official. Quicker download than hotfile too
Click to expand...
Click to collapse
Thanks. Totally forgot about checkfus
Sent from my GT-N7000 using xda app-developers app
Got the OTA update this morning, 196 mb or something like that. Nice and quick.
OTA update in Germany, downloading now...
Sent from my GT-N7000 using xda app-developers app
Edit 15:22:
Changelog (so far i can tell)
http://forum.xda-developers.com/showthread.php?t=1870701
- new launcher (like the Galaxy S3)
- new gallery with fancy 3D effects
- new contact list
- new folder handling
- pop-up video can now be resized
- slightly changed contact list layout
- you can now save contacts in the S-Clound (like google contacts)
- performance improved!
- added camera motion for lockscreen - settings -> display (only works with wipe lockscreen)
- added S-Cloud (there is no dedicated App but after flashing you will be asked if you want to sycn all your settings with samsung)
- added new motion: call contact currently displayed if you raise the phone
- added bloatware (NTV, Lieferheld, ChatOn, myTaxi)
- added flipboard as systemapp (can't be removed)
- black clipping not fixed
edit: Livebyte was faster
the new gallery
http://www.youtube.com/watch?v=HkixyhGDbGA
Heard someone said s3 launcher included? Can anyone confirm
Sent from my GT-N7000 using Tapatalk 2
Does the new ROM feature toggles that are similar to s3 in the notification drawer?
Can somone mirror this? The hotfile link is super slow and it keeps saying dl unsuccessful
So if it has the new tw does this mean that Jellybean will come very soon couple of weeks? Wondering again I just heard it came wih the new launcher
Maybe is samsungs way of getting users ready for jb?
Sent from my GT-N7000 using Tapatalk 2
marcviado said:
Can somone mirror this? The hotfile link is super slow and it keeps saying dl unsuccessful
Click to expand...
Click to collapse
Use Checkfus.
nandihno said:
So if it has the new tw does this mean that Jellybean will come very soon couple of weeks? Wondering again I just heard it came wih the new launcher
Maybe is samsungs way of getting users ready for jb?
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
well, Samsung tweeted few days ago that JB is comming very soon - so i would say yes
about the S3 Launcher, i tell you everything in a few minutes
garytube said:
about the S3 Launcher, i tell you everything in a few minutes
Click to expand...
Click to collapse
Let us know. If it has the Nature UX launcher it will be great
Can anyone please post screenshots of new firmware
Sent from my GT-N7000 using xda premium
Installing. Will post on completion
checkfus is down for me, just hangs on downloading presets
just flashed...
I am getting the null keyboard error. Any fixes?
re-flashed... it seems ok now.
itsfragi said:
Use Checkfus.
Click to expand...
Click to collapse
Do i dl that from the playstore? Chus i downloaded the free version and its not working

How to play Fortnite on Our ZuK Z2 (GUIDE)

First
1. Download and install New Oxygen 5.0.4 rom in forum with SafetyNet checked !
2. Next flash as the dev of the room said!
3. Flash Magisk 16.0
4. Now boot into the rom
5. Install build.prop from Playstore
6. Edit the build prop with the following sets
ro.product.brand=samsung
ro.product.manufacturer=samsung
ro.build.product=starlte
ro.product.device=starlte
ro.product.model=SM-G960F
ro.product.name=starltexx
Note : I found this to be very laggy so use S7 build prop if u need performance
And Reboot.
Now follow the below steps
5 simple steps
1.download the original app Fortnite installer and install fortnite
2.after install don't open
3.open magisk and hide fortnite based apps and hide the magisk manager itself in the setting wait ....and reboot.
4.dont waste time go and play it will work ....?
ZuK can handle the game at ~20-28fps avg .....
Enjoy Forniters .....
Any doubt don't comment the whole post
Can you please give me the s7 build prop ??
Thank you..
aniket10singh16 said:
Can you please give me the s7 build prop ??
Thank you..
Click to expand...
Click to collapse
ro.build.flavor=hero2ltexx-user
ro.product.model=SM-G935F
ro.product.brand=samsung
ro.product.name=hero2ltexx
ro.product.device=hero2lte
ro.product.board=universal8890
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=arm64-v8a
ro.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=arm64-v8a
ro.product.manufacturer=samsung
ro.product.locale=en-GB
ro.wifi.channels=
ro.board.platform=exynos5
# ro.build.product is obsolete; use ro.product.device
ro.build.product=hero2lte
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=hero2ltexx-user 7.0 NRD90M G935FXXU1DQB7 release-keys
ro.build.fingerprint=samsung/hero2ltexx/hero2lte:7.0/NRD90M/G935FXXU1DQB7:user/release-keys
ro.build.characteristics=phone,emulator
# Samsung Specific Properties
ro.build.PDA=G935FXXU1DQB7
ro.build.official.release=true
ro.build.official.protect.apk=false
ro.build.hidden_ver=G935FXXU1DQB7
ro.config.rm_preload_enabled=0
ro.build.changelist=10422490
ro.product_ship=true
ro.chipname=exynos8890
Can you provide a zip to do these changes.Not working for me.
https://www.google.co.in/amp/s/foru...ow-to-play-fortnite-smoothly-z2-t3829324/amp/
Go to this thread and make this settings to play smoothly
does it work on any other rom ?
Yes it works on DotOs bro ....I just used...its running more smooth and use s7 build props
I use magisk module to fake my device as s7. Delete folder. Magisk hide to the app. Delete the magisk folder.
Still when I jump out of the bus it kick me out.
can't play at all.........
always kick me out, say connection lost.
does it require magisk core only mode?
locolyric said:
I use magisk module to fake my device as s7. Delete folder. Magisk hide to the app. Delete the magisk folder.
Still when I jump out of the bus it kick me out.
can't play at all.........
always kick me out, say connection lost.
does it require magisk core only mode?
Click to expand...
Click to collapse
Well Don't jump lol???
locolyric said:
I use magisk module to fake my device as s7. Delete folder. Magisk hide to the app. Delete the magisk folder.
Still when I jump out of the bus it kick me out.
can't play at all.........
always kick me out, say connection lost.
does it require magisk core only mode?
Click to expand...
Click to collapse
yes it requires core only mode and also check the safety net ..
still im playing with Dot Os
darkmoon kernel and s7 build props...
in darkmoon kernel under volt the large core little to reduce the heat
didn't get any mail from epic...when i signed in i did all these things and they said u r in waiting list..
I changed my phone name from zuk z2 to s9+
I use nameless kernel . Zram as 570. Clear all recent task before entering game.
Still , some time the game will have no response. I can see the kill noticifaction . I see the background movement but I just can't interact with anything on the screen in this game.
I force to use home button and end this game .......
Sent from my SM-G935U using Tapatalk
Which is the best rom for fortnite and what's zram?
sameer 100 said:
didn't get any mail from epic...when i signed in i did all these things and they said u r in waiting list..
I changed my phone name from zuk z2 to s9+
Click to expand...
Click to collapse
locolyric said:
I use nameless kernel . Zram as 570. Clear all recent task before entering game.
Still , some time the game will have no response. I can see the kill noticifaction . I see the background movement but I just can't interact with anything on the screen in this game.
I force to use home button and end this game .......
Sent from my SM-G935U using Tapatalk[/QUOprops
Yeah thats says that ur having 3GB model then
Go to an very light weight ROM so that there is no problem in background ,use pico gapps,and finnaly use a hard task killer (root) any app , make sure u have 1gb or more...
Don't modify zram ...it make device in stable
And also don't use s9 props use s7 props or else phone can't handle the pressure lol!
Do these the fortnite will work like charm
My config
Dot os
Nameless kernel
Big core under clocked to 1.9
Small core under clocked to 1.5( i t has effect in loading )
Under clock becoz CPU is not deal here GPU is main so to reduce heat under clock will help
S7 build props
Enjoy fortnite in Zukky:silly:
Click to expand...
Click to collapse
Pls someone kind enough provide us a s7 twrp flashable build prop
Which has a backup script for original build prop
Or a uninstall or restore script embedded in it
Pls someone
hf958 said:
Pls someone kind enough provide us a s7 twrp flashable build prop
Which has a backup script for original build prop
Or a uninstall or restore script embedded in it
Pls someone
Click to expand...
Click to collapse
Bro don't expect it ...just do as I say
Edit the build prop save on sdcard
Next on twrp backup the real one and finally paste it in system
Don't forget to mount system first..
After this click on build prop and run CHMOD755
Fornithe

Categories

Resources