Database Users

[Q][HELP] Samsung Galaxy Core Plus (CS02) SM-G350 - CWM Recovery

Hello, I am trying to customize a ROM for the Galaxy Core Plus (SM-G350) -> see links.txt.zip, I was able to root it, but I am not able to get/find a CWM which is running on this device.
So I decided to create an own CWM for it, but my tries failed. (recovery builder, building CWM from scratch ...)
The stock rom (G350XXUAMKB) could be found at -> see links.txt.zip
Anyone can help me creating a CWM for it, please?
Thx
attached the file for the kitchen ( was not able to test it ) and the file with the external links for this post (Specification Core Plus, and stock rom)

xTheer said:
Hello, I am trying to customize a ROM for the Galaxy Core Plus (SM-G350) -> see links.txt.zip, I was able to root it, but I am not able to get/find a CWM which is running on this device.
So I decided to create an own CWM for it, but my tries failed. (recovery builder, building CWM from scratch ...)
The stock rom (G350XXUAMKB) could be found at -> see links.txt.zip
Anyone can help me creating a CWM for it, please?
Thx
attached the file for the kitchen ( was not able to test it ) and the file with the external links for this post (Specification Core Plus, and stock rom)
Click to expand...
Click to collapse
Hi, I want to know your core plus is running on 4.2 android version or 4.1.2 .. and u can(( try )) our cwm ... or ask the maker of our cwm ...
Hit thanks if I have helped uh
Sent from my GT-I8262 using XDA Premium 4 mobile app

Hi,
Android 4.2.2
Baseband G350XXUAMKB
Kernel: 3.4.5-1845929 [email protected] #1
Build: JDQ39. G350XXUAMKB
Wehre to find your CWM? Who was creating your CWM?
Thx
Sent from my HTC One using xda app-developers app

xTheer said:
Hi,
Android 4.2.2
Baseband G350XXUAMKB
Kernel: 3.4.5-1845929 [email protected] #1
Build: JDQ39. G350XXUAMKB
Wehre to find your CWM? Who was creating your CWM?
Thx
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Let some more people buys core plus and u will get cwm
Sent from my GT-I8262 using XDA Premium 4 mobile app

Hello.
I will like to buy this phone but the problem is that this phone is from another operator in my country.
I've read that is possible to root the phone, but my question is that if is possible to sim unlock the phone when rooted?
Best regards :victory:

I am buying this phone yesterday and i really look into a CWM....is there any here?

no currently no any cwm fr core plus
Sent from my GT-I8262 using XDA Premium 4 mobile app

xTheer said:
Hello, I am trying to customize a ROM for the Galaxy Core Plus (SM-G350) -> see links.txt.zip, I was able to root it, but I am not able to get/find a CWM which is running on this device.
So I decided to create an own CWM for it, but my tries failed. (recovery builder, building CWM from scratch ...)
The stock rom (G350XXUAMKB) could be found at -> see links.txt.zip
Anyone can help me creating a CWM for it, please?
Thx
attached the file for the kitchen ( was not able to test it ) and the file with the external links for this post (Specification Core Plus, and stock rom)
Click to expand...
Click to collapse
Hi, how did you success to root this phone? I didn't success yet...

frankee207 said:
Hi, how did you success to root this phone? I didn't success yet...
Click to expand...
Click to collapse
see here !
http://forum.xda-developers.com/showpost.php?p=52329801&postcount=10

Thanks so much!

What's the progress with CWM and roms for Samsung galaxy core plus? I even can't root this phone

A way to root and install custom roms for this phone would be appreciated greatly
Sent from my S3 running AOKP KK 4.4.4 Nightly

Root is done.

tomasX8 said:
Root is done.
Click to expand...
Click to collapse
Hello,
How did you manage that?

klugway said:
Hello,
How did you manage that?
Click to expand...
Click to collapse
vROOT

I have build CWM Recovery for this device.
I've build CWM Recovery for this device but I don't know if it's working because I'm afraid breaking my device...
I'm 50% sure that my current version doesn't work because I'm missing some values...
If you have experience and want to help me, please help me then
(I can give my current files if you ask)
Unfinished files with errors (I believe that I have the errors.)
- BoardConfig.mk
Code:
BOARD_KERNEL_CMDLINE :=
BOARD_KERNEL_BASE := 0x
BOARD_KERNEL_PAGESIZE :=

So how is it going now? Any progresses so far?

Polyparadox said:
So how is it going now? Any progresses so far?
Click to expand...
Click to collapse
I'm still stuck with some values and sizes...

santeri3700 said:
I'm still stuck with some values and sizes...
Click to expand...
Click to collapse
Maybe I can help you. I can't program in java but maybe I could help you in any other way.
I really want to have a custom recovery system for our phone models.

Polyparadox said:
Maybe I can help you. I can't program in java but maybe I could help you in any other way.
I really want to have a custom recovery system for our phone models.
Click to expand...
Click to collapse
I would really appreciate it!
Do you have any experience with Linux? Do you have Ubuntu..? Do you use IRC?
---------- Post added at 10:40 AM ---------- Previous post was at 09:52 AM ----------
I have made some progress!
Everything else is ready (I think) but I'm not sure how to get the partition sizes..
BoardConfig.mk:
Code:
BOARD_KERNEL_CMDLINE :=
BOARD_KERNEL_BASE := 0x82000000
BOARD_KERNEL_PAGESIZE := 4096
# fix this up by examining /proc/mtd on a running device
BOARD_BOOTIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_USERDATAIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_FLASH_BLOCK_SIZE := 131072
/proc/emmc:
Code:
dev: size erasesize name
mmcblk0p1: 00000800 00000400 "cal"
mmcblk0p2: 00000200 00000400 "sysparm_dep"
mmcblk0p3: 00000200 00000400 "parm-spml_dep"
mmcblk0p4: 00000200 00000400 "RF_CAL_FILE"
mmcblk0p5: 00004000 00000400 "KERNEL"
mmcblk0p6: 00004000 00000400 "RECOVERY"
mmcblk0p7: 00009600 00000400 "modem"
mmcblk0p8: 00000400 00000400 "reserved"
mmcblk0p9: 00001000 00000400 "SBL1"
mmcblk0p10: 00001000 00000400 "SBL2"
mmcblk0p11: 00004000 00000400 "PARAM"
mmcblk0p12: 00000400 00000400 "DTSBK"
mmcblk0p13: 00000400 00000400 "DTS"
mmcblk0p14: 00000200 00000400 "FOTA_SIG"
mmcblk0p15: 0000a000 00000400 "efs"
mmcblk0p16: 00064000 00000400 "CSC"
mmcblk0p17: 00241570 00000400 "system"
mmcblk0p18: 0000f000 00000400 "HIDDEN"
mmcblk0p19: 0046c000 00000400 "userdata"
Boot.img unpacking log:
Code:
BOARD_KERNEL_CMDLINE
BOARD_KERNEL_BASE 82000000
BOARD_PAGE_SIZE 4096
[email protected]:~/buildsource#

[Q] Android TV on Nexus Q?

Anyone else curious if Android TV will work on the Nexus Q?
If it is I am definitely going to try to port a version to it.

I was just wondering about this myself.
Here's something else they just released yesterday that might be of interest to us:
Google Cast Receiver
https://play.google.com/store/apps/details?id=com.google.android.apps.mediashell

Diznario said:
I was just wondering about this myself.
Here's something else they just released yesterday that might be of interest to us:
Google Cast Receiver
https://play.google.com/store/apps/details?id=com.google.android.apps.mediashell
Click to expand...
Click to collapse
Nice, I was wondering the same thing. I haven't seen anything indicating it wouldn't work. These things might end up front and center in my livingroom again...

Google Cast Receiver APK
Diznario said:
I was just wondering about this myself.
Here's something else they just released yesterday that might be of interest to us:
Google Cast Receiver
https://play.google.com/store/apps/details?id=com.google.android.apps.mediashell
Click to expand...
Click to collapse
Nice! Anyone hosting the Apk yet? Anyone peeked inside to see the minimum API level? Or try side loading it (potentially to system/priv-app) yet to another device?
Better yet, anyone have a system dump or factory image from an ADT-1 (Android TV Dev box given out at I/O today)? I'd bet it has an unlockable bootloader, so hopefully we'll have factory restore images.

It would be cool if the Android TV firmware could be ported or the Google Cast Reciver app could be sideloaded on the Nexus Q. I hope we can do this. I love the hardware. Small and stylish and sounds great.
Does the chromecast (Google Cast Reciver app) support multi room playback?

Anyone have any updated info on this? I would be amazing if we could sideload onto a Nexus Q - it was the perfect hardware for powering my outdoor speakers (I put it in a waterproof box).

Gtvhacker have uploaded the build.prop from a ADT-1 Android TV. So we can now spoof the Play store into thinking our device is a ADT-1 Android TV. Will have a try later.
http://gtvhacker.com/index.php/ADT-1_Android_TV_Sample_Build.prop

darren1 said:
Gtvhacker have uploaded the build.prop from a ADT-1 Android TV. So we can now spoof the Play store into thinking our device is a ADT-1 Android TV. Will have a try later.
http://gtvhacker.com/index.php/ADT-1_Android_TV_Sample_Build.prop
Click to expand...
Click to collapse
I tried to change the build.prop file on my Q to spoof the Play Store but no luck. Im located in sweden and only got that the app is not available in my country.

mannberg said:
I tried to change the build.prop file on my Q to spoof the Play Store but no luck. Im located in sweden and only got that the app is not available in my country.
Click to expand...
Click to collapse
Could you copy and post your build prop please?
Sent from my OnePlus One using xda app

Moose0704 said:
Could you copy and post your build prop please?
Click to expand...
Click to collapse
I can post my build.prop when I get home (@work). But I only changed these parameters:
ro.build.version.sdk=20
ro.build.tags=release-keys
ro.product.model=ADT-1
ro.product.brand=google
ro.product.name=molly
ro.product.device=molly
ro.product.manufacturer=Google
ro.build.fingerprint=google/molly/molly:L/LPV79/1236599:user/release-keys
ro.build.thumbprint=L/LPV79/1236599:user/dev-keys
this is the my edited build.prop. Anyone that is US based that can try to spoof the Play Store?
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=KOT49H
ro.build.display.id=cm_steelhead-userdebug 4.4.2 KOT49H 7bfcd95679 test-keys
ro.build.version.incremental=7bfcd95679
ro.build.version.sdk=20
ro.build.version.codename=REL
ro.build.version.release=4.4.2
ro.build.date=Fri Jan 3 13:23:17 PST 2014
ro.build.date.utc=1388784197
ro.build.type=userdebug
ro.build.user=howard
ro.build.host=thunderbolt
ro.build.tags=releas-keys
ro.product.model=ADT-1
ro.product.brand=google
ro.product.name=molly
ro.product.device=molly
ro.product.board=molly
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Google
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=omap4
# ro.build.product is obsolete; use ro.product.device
ro.build.product=molly
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=molly-user L LPV79 1236599 release-keys
ro.build.fingerprint=google/molly/molly:1236599:user/release-keys
ro.build.characteristics=nosdcard
ro.cm.device=steelhead
# end build properties
#
# from device/google/steelhead/system.prop
#
com.ti.omap_enhancement=true
#define a property for hdmi sink channel count
dolby.audio.hdmi.channels=0
persist.hwc.primary.tv=1
# Default color is 0x00385c
persist.sys.ringcolor=14428
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.rommanager.developerid=cyanogenmod
ro.com.google.clientidbase=android-google
keyguard.no_require_sim=true
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.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.build.selinux=1
persist.sys.root_access=1
ro.cm.version=11-20140103-UNOFFICIAL-steelhead
ro.modversion=11-20140103-UNOFFICIAL-steelhead
ro.cmlegal.url=http://www.cyanogenmod.org/docs/privacy
ro.config.ringtone=Orion.ogg
ro.config.notification_sound=Argon.ogg
ro.config.alarm_alert=Hassium.ogg
net.dns1=8.8.8.8
net.dns2=8.8.4.4
ro.carrier=unknown
wifi.interface=wlan0
hwui.render_dirty_regions=false
ro.sf.lcd_density=213
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=512k
dalvik.vm.heapmaxfree=2m
persist.sys.dalvik.vm.lib=libdvm.so
dalvik.vm.lockprof.threshold=500
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt

No luck on my N7 '13 trying to pull the Cast Receiver apk using the build.prop either. It gets flagged as the wrong hardware still.

Grishka11 has posted the apk on this thread
http://forum.xda-developers.com/har...ast/apk-adt-1-cast-receiver-leanback-t2814210
Only installs on Kit Kat or Android L. Doesn't do anything on my Nexus 10 running 4.4.2. Decompiled and altered the minimum sdk version and installed it on a Jellybean Android box and again does nothing.

I got this in logcat when I installed
./adb logcat | grep mediashell
I/PackageManager( 462): Running dexopt on: com.google.android.apps.mediashell
I/ActivityManager( 462): Force stopping com.google.android.apps.mediashell appid=10093 user=-1: update pkg
W/PackageManager( 462): Unknown permission android.permission.ACCESS_DRM_CERTIFICATES in package com.google.android.apps.mediashell
W/PackageManager( 462): Unknown permission android.permission.HDMI_CEC in package com.google.android.apps.mediashell
D/BackupManagerService( 462): Received broadcast Intent { act=android.intent.action.PACKAGE_ADDED dat=package:com.google.android.apps.mediashell flg=0x4000010 (has extras) }
I/ThemeManager( 713): Handling new theme package: com.google.android.apps.mediashell
I/InstallAppProgress( 3442): Finished installing com.google.android.apps.mediashell
D/PackageBroadcastService( 960): Received broadcast action=android.intent.action.PACKAGE_ADDED and uri=com.google.android.apps.mediashell
I/IcingCorporaProvider( 898): Updating corpora: APPS=com.google.android.apps.mediashell, CONTACTS=MAYBE
Click to expand...
Click to collapse
and I cant find a running service for the cast app
./adb shell service list
Found 82 services:
0 sip: [android.net.sip.ISipService]
1 phone: [com.android.internal.telephony.ITelephony]
2 isms: [com.android.internal.telephony.ISms]
3 iphonesubinfo: [com.android.internal.telephony.IPhoneSubInfo]
4 simphonebook: [com.android.internal.telephony.IIccPhoneBook]
5 nfc: [android.nfc.INfcAdapter]
6 assetredirection: [com.android.internal.app.IAssetRedirectionManager]
7 media_router: [android.media.IMediaRouterService]
8 print: [android.print.IPrintManager]
9 assetatlas: [android.view.IAssetAtlas]
10 dreams: [android.service.dreams.IDreamManager]
11 commontime_management: []
12 samplingprofiler: []
13 diskstats: []
14 appwidget: [com.android.internal.appwidget.IAppWidgetService]
15 backup: [android.app.backup.IBackupManager]
16 uimode: [android.app.IUiModeManager]
17 serial: [android.hardware.ISerialManager]
18 usb: [android.hardware.usb.IUsbManager]
19 audio: [android.media.IAudioService]
20 wallpaper: [android.app.IWallpaperManager]
21 dropbox: [com.android.internal.os.IDropBoxManagerService]
22 search: [android.app.ISearchManager]
23 country_detector: [android.location.ICountryDetector]
24 location: [android.location.ILocationManager]
25 devicestoragemonitor: []
26 notification: [android.app.INotificationManager]
27 profile: [android.app.IProfileManager]
28 updatelock: [android.os.IUpdateLock]
29 servicediscovery: [android.net.nsd.INsdManager]
30 connectivity: [android.net.IConnectivityManager]
31 wifi: [android.net.wifi.IWifiManager]
32 wifip2p: [android.net.wifi.p2p.IWifiP2pManager]
33 netpolicy: [android.net.INetworkPolicyManager]
34 netstats: [android.net.INetworkStatsService]
35 textservices: [com.android.internal.textservice.ITextServicesManager]
36 network_management: [android.os.INetworkManagementService]
37 clipboard: [android.content.IClipboard]
38 statusbar: [com.android.internal.statusbar.IStatusBarService]
39 device_policy: [android.app.admin.IDevicePolicyManager]
40 lock_settings: [com.android.internal.widget.ILockSettings]
41 mount: [IMountService]
42 accessibility: [android.view.accessibility.IAccessibilityManager]
43 input_method: [com.android.internal.view.IInputMethodManager]
44 bluetooth_manager: [android.bluetooth.IBluetoothManager]
45 input: [android.hardware.input.IInputManager]
46 window: [android.view.IWindowManager]
47 alarm: [android.app.IAlarmManager]
48 consumer_ir: [android.hardware.IConsumerIrService]
49 vibrator: [android.os.IVibratorService]
50 battery: [android.app.IBatteryService]
51 hardware: [android.os.IHardwareService]
52 content: [android.content.IContentService]
53 account: [android.accounts.IAccountManager]
54 user: [android.os.IUserManager]
55 entropy: []
56 permission: [android.os.IPermissionController]
57 cpuinfo: []
58 dbinfo: []
59 gfxinfo: []
60 meminfo: []
61 procstats: [com.android.internal.app.IProcessStats]
62 activity: [android.app.IActivityManager]
63 package: [android.content.pm.IPackageManager]
64 scheduling_policy: [android.os.ISchedulingPolicyService]
65 telephony.registry: [com.android.internal.telephony.ITelephonyRegistry]
66 display: [android.hardware.display.IDisplayManager]
67 appops: [com.android.internal.app.IAppOpsService]
68 usagestats: [com.android.internal.app.IUsageStats]
69 batterystats: [com.android.internal.app.IBatteryStats]
70 power: [android.os.IPowerManager]
71 sensorservice: [android.gui.SensorServer]
72 SurfaceFlinger: [android.ui.ISurfaceComposer]
73 media.audio_policy: [android.media.IAudioPolicyService]
74 media.camera: [android.hardware.ICameraService]
75 media.player: [android.media.IMediaPlayerService]
76 media.audio_flinger: [android.media.IAudioFlinger]
77 drm.drmManager: [drm.IDrmManagerService]
78 batterypropreg: [android.os.IBatteryPropertiesRegistrar]
79 android.security.keystore: [android.security.keystore]
80 common_time.config: [android.os.ICommonTimeConfig]
81 common_time.clock: [android.os.ICommonClock]
Click to expand...
Click to collapse
And nothing that is named cast, mediashell or something similar in ./adb shell ps. Maybe something with the unknown permission.

I think we need those from /system/etc/permissions to keep trying. I'll let Grishka know and see if he can adb pull them. :good:

Anything new yet?

anyone have any luck on this?

Is it possible to root the ZTE Blade V7 Lite?

Hi,
I would love to get mu device (ZTE Blade V7 Lite) rooted but I can't get it to work myself.
I tried KingRoot and KingoRoot (pc and apk). Are there any other possibilities to root this device?
Thanks in advance!

i think I may have found a way to install recovery twrp and flash root but haven't had the nerve to try it because have no stock firmware in case anything goes wrong

here is for the supersu to flash by twrp http://www.mediafire.com/file/55d2pf92w4nwag1/UPDATE-SuperSU-v2.76-20160630161323(2).zip
here is the twrp to flash by sp flashtool http://www.mediafire.com/file/lr3ls9xonfc9trf/zte_v7_lite_twrp.rar
again I found these looking online and don't take credit for other peoples work
I haven't used sp flashtool before so hopefully you might find someone whos used it

Sparko612 said:
here is for the supersu to flash by twrp http://www.mediafire.com/file/55d2pf92w4nwag1/UPDATE-SuperSU-v2.76-20160630161323(2).zip
here is the twrp to flash by sp flashtool http://www.mediafire.com/file/lr3ls9xonfc9trf/zte_v7_lite_twrp.rar
again I found these looking online and don't take credit for other peoples work
I haven't used sp flashtool before so hopefully you might find someone whos used it
Click to expand...
Click to collapse
cant flash the image, ive started building a database for our tool
so far i have
-drivers
-stock firmware(extracted myself)
-scatter file
-semi working recovery
im in the processing of gaining root and fixing recovery, very early stages tho

could you put a link for your stock firmware and scatter file as I have bricked my phone and cant seem to find anywhere a stock firmware and scatter file at all for this device please

Hi guyz @Sparko612 and @Ricky Divjakovski
Have you found a solution for root and unbrick?

Until I can find stock firmware and scatter file then currently not sorry mate

MrOops said:
Hi guyz @Sparko612 and @Ricky Divjakovski
Have you found a solution for root and unbrick?
Click to expand...
Click to collapse
closest i got was dumping the firmware via dirtycow, since then i have discontinued development as i dont have the device anymore..

Sparko612 said:
could you put a link for your stock firmware and scatter file as I have bricked my phone and cant seem to find anywhere a stock firmware and scatter file at all for this device please
Click to expand...
Click to collapse
Hello,
Take the rom from this link. https://drive.google.com/uc?id=0B8NdSu-RzkHNZkZMWmxrOWtWeGs&export=download
It's named: MT6735__ZTE__ZTE_BLADE_V7_LITE__ZTE_BLADE_V0720__6.0__ZTE_BLADE_V7_LITE_B13.zip.
In Smart Phone Flash Tool take the scatterfile from this rom!
IMPORTANT: If you got an error while flashing you have to flash every position at it's own. One after one, Step by step!!
Don't flash the userdata!!
After that i was able to start the phone. Before that, my phone wasn't able to boot, or anything else. No LED, no charging.
Hope it works also for you. Sorry for my english... :good::laugh:

Thankyou followed the guide and phone working again thankyou so much. Only have nv warning err = 0x10 when WiFi is turned on comes up as another WiFi access point

Sparko612 said:
Thankyou followed the guide and phone working again thankyou so much. Only have nv warning err = 0x10 when WiFi is turned on comes up as another WiFi access point
Click to expand...
Click to collapse
Me too, and unknown IMEI also, but here's the solution.
How to Restore NVRAM.bin Using SP Flash Tool & Permanent Fix Invalid IMEI Error.
https://afterroot.wordpress.com/2015/07/22/mtk-restore-nvram-bin/
Here is the NVRAM.bin File. I have uploaded it on google drive!
https://drive.google.com/file/d/0B8NdSu-RzkHNd0NvUGt0N0VKbDQ/view
Greetings.

i want to root my zte blade v7 too but cant make it work please help
---------- Post added at 06:17 AM ---------- Previous post was at 06:13 AM ----------
sepp12 said:
Me too, and unknown IMEI also, but it's not so a big problem for me.
This is because the MAC address begins with an 0.
This can't be fixed permanent without ROOT !!
We have to wait for any rooting solution.
My phone works with this 2 errors anyway.
Greetings.
Click to expand...
Click to collapse
i just cant get it to work and now im getting very impatient

5th july 2017.. anyone know how to root zte blade v7 lite? pls?

Hope dies last.

??
hmmm no root solution yet?

No.

I think, I may have found a solution.
www .zunite. org /2016/12/zte-blade-v7-lite-twrp-root .html (sorry for those spaces/I'm not allowed to post urls)
On that website (which is not English unfortunately) there is a guide on how to install TWRP and then SuperSu on the v7 Lite. There are also images of the phone in the twrp menu, so I think it's not a fake. I won't test it, until I have a new phone because I don't want to brick my main device.

Philipp0002 said:
I think, I may have found a solution.
www .zunite. org /2016/12/zte-blade-v7-lite-twrp-root .html (sorry for those spaces/I'm not allowed to post urls)
On that website (which is not English unfortunately) there is a guide on how to install TWRP and then SuperSu on the v7 Lite. There are also images of the phone in the twrp menu, so I think it's not a fake. I won't test it, until I have a new phone because I don't want to brick my main device.
Click to expand...
Click to collapse
Doesn't work. I have tried it a few times. No way to get into TWRP!

How can one use dirtycow to dump ZTE Blade V7 Lite recovery firmware?
Ricky Divjakovski said:
closest i got was dumping the firmware via dirtycow, since then i have discontinued development as i dont have the device anymore..
Click to expand...
Click to collapse
I just got one of these handsets and I've been struggling to look for a way to root it and think it may be possible by following some of the instructions at:
http://4pda.ru/forum/index.php?showtopic=742105&st=100
Unfortunately before I do that I need a copy of my firmware. It seems you managed to get dirtycow to get you into an elevated shell where you could run dd to image your recovery and boot.
How did you do this (in as much detail as you have time to spare).
So far I've read about the various dirtycow exploit packages but from what I understand none will get you to a fully rooted state with 32 bit android 6.
The last supported version is 32 bit android 5.
https://forum.xda-developers.com/android/software-hacking/root-tool-dirtycow-apk-adb-t3525120
Unfortunately the ADB version didn't work.
Code:
[email protected]_BLADE_V0720:/data/local/tmp $ ./exploit.sh
./exploit.sh

 ( )
 ~(^^^^)~
 ) @@ \~_ |\
 / | \ \~ / CVE-2016-5195
 ( 0 0 ) \ | | Lollipop (32bits)
 ---___/~ \ | | SeLinux bye
 /'__/ | ~-_____/ |
o _ ~----~ ___---~
 O // | |
 ((~\ _| -|
 o O //-_ \/ | ~ |
 ^ \_ / ~ |
 | ~ |
 | / ~ |
 | ( |
 \ \ /\
 / -_____-\ \ ~~-*
 | / \ \
 / / / /
 /~ | /~ |
 ~~~~ ~~~~

# Device:P635A32_JP_DWB

-Getting uid 0->Ok.
-Checking permissive run-as.->No
-Dump policy->Ok
(Android M policy compatibility mode)
(Android M policy compatibility mode)
(Android M policy compatibility mode)
(Android M policy compatibility mode)
(Android M policy compatibility mode)
-Dump initreadelf: Error: /data/local/tmp/init.dump: Failed to read file's magic number
printf: 0x: invalid number

Error searching shellcode addr, already patched?
[email protected]_BLADE_V0720:/data/local/tmp $ su
[CODE]
There is also some android 6 64 bit variant.
[url]https://github.com/hyln9/VIKIROOT[/url]
Given my ZTE Blade V7 Lite has a android 6 the first version doesn't sound like it will work.
As for teh second version it seems the ZTE Blade V7 Lite is on a 32 bit kernal so it won't run.
[CODE]
[email protected]_BLADE_V0720:/data/local/tmp $ ./exploit
./exploit
/system/bin/sh: ./exploit: not executable: 64-bit ELF file
[CODE]
[CODE]
Processor : ARMv7 Processor rev 4 (v7l)
processor : 0
model name : ARMv7 Processor rev 4 (v7l)
BogoMIPS : 32.39
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm sha2
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4
Hardware : MT6735P
Revision : 0000
Serial : 0000000000000000
There is also some information at
https://github.com/matteoserva/dirtycow-arm32
But I'm not familiar enough to understand how it relates to the ZTE Blade V7 Lite and if it will be possible.
Any tips you can provide would be much appreciated.

Can I assume this discussion applies to the Blade Max Z as well? It has Android 7.1. There is nothing around about rooting it.

Can someone send me stock LGInCall.apk and LGContacts.apk from system/app-priv?

So I installed twrp, and installed modded stock kernel/ ROM and then flashed superSU.
The only problem i have now is that calls are not being shown in second screen, and are instead shown on main screen with no way to escape them rather than either deny or accept the call.. So i think this must be an old app maybe? The settings in the app for showing calls on second screen while in apps doesn't work either..
I would really appreciate it if someone could send me their LGInCall.apk and LGContacts.apk if they know they allow calls to be shown in second screen.
Thanks in advance

Not sure what the second screen is in reference to really. I would provide those apps to you but I'm not seeing them listed exactly like your request. Here is what I have...
Code:
1|elsa:/ # pm list packages -s
package:com.hy.system.fontserver
package:com.android.LGSetupWizard
package:com.android.cts.priv.ctsshim
package:com.gd.mobicore.pa
package:com.google.android.ext.services
package:com.android.providers.telephony
package:com.google.android.googlequicksearchbox
package:com.android.providers.calendar
package:com.android.providers.media
package:com.lge.systemservice
package:com.google.android.onetimeinitializer
package:com.google.android.ext.shared
package:com.android.wallpapercropper
package:com.quicinc.cne.CNEService
package:com.lge.signboard.initialguide
package:com.lge.vrplayer
package:org.simalliance.openmobileapi.service
package:com.lge.quicktools
package:com.android.documentsui
package:com.lge.mirrorlink
package:com.android.externalstorage
package:com.evernote.promohelper
package:com.lge.android.atservice
package:com.android.htmlviewer
package:com.lge.wfd.spmirroring.source
package:com.lge.app.floating.res
package:com.android.mms.service
package:com.lge.sui.widget
package:com.android.providers.downloads
package:com.lge.camera
package:com.lge.touchcontrol
package:com.lge.effect
package:com.lge.eltest
package:com.lge.LGSetupView
package:com.lge.homeselector
package:com.lge.ime.solution.text
package:com.lge.springcleaning
package:com.crucialtec.uaf
package:com.lge.gnsstest
package:com.lge.fmradio
package:com.lge.wifihotspotwidget
package:com.google.android.configupdater
package:com.lge.musiccontroller
package:com.crucialsoft.fido.client
package:com.android.defcontainer
package:com.android.providers.downloads.ui
package:com.android.pacprocessor
package:com.lge.shutdownmonitor
package:com.lge.videoeditorres
package:com.ipsec.service
package:com.lge.signaturewallpaper
package:com.android.certinstaller
package:com.android.carrierconfig
package:com.google.android.marvin.talkback
package:com.lge.launcher2.theme.optimus
package:com.android.settingsaccessibility
package:android
package:com.lge.upsell
package:com.android.contacts
package:com.qualcomm.wfd.service
package:com.lge.lockscreensettings
package:com.lge.icecontacts
package:com.lge.gallery.vr.wallpaper
package:com.lge.ia.task.incalagent
package:com.lge.wernicke.nlp
package:com.android.egg
package:com.android.mtp
package:com.android.nfc
package:com.android.stk
package:com.android.backupconfirm
package:com.lge.iftttmanager
package:com.lge.exchange
package:com.lge.wapservice
package:com.android.statementservice
package:com.android.calendar
package:com.lge.ia.task.smartsetting
package:com.qualcomm.qti.auth.secureextauthservice
package:com.lge.ims.rcsprovider
package:com.google.android.setupwizard
package:com.lge.ipservice
package:com.qualcomm.qcrilmsgtunnel
package:com.android.providers.settings
package:com.android.sharedstoragebackup
package:com.android.printspooler
package:com.uei.lg.quicksetsdk.irblaster
package:com.ti.server
package:com.android.incallui
package:com.android.frameworks.telresources
package:com.lge.wfds.service.v3
package:com.lge.video.vr.wallpaper
package:com.lge.gnsspostest
package:com.android.inputdevices
package:com.lge.voicecare
package:com.lge.gba.android
package:com.lge.eula
package:com.lge.gcuv
package:com.lge.task
package:com.qti.dpmserviceapp
package:com.lge.themesquare
package:com.lge.theme.blackgold
package:com.lge.gestureanswering
package:com.google.android.webview
package:com.lge.launcher2
package:com.lge.launcher3
package:com.lge.musicshare
package:com.android.server.telecom
package:com.google.android.syncadapters.contacts
package:com.lge.vragent
package:com.android.facelock
package:com.android.keychain
package:com.lge.ipprovider
package:com.google.android.calculator
package:com.android.chrome
package:com.android.gallery3d
package:com.google.android.packageinstaller
package:com.google.android.gms
package:com.google.android.gsf
package:com.google.android.tts
package:com.lge.gnss.airtest
package:com.lge.signboard.settings
package:com.lge.wifi.p2p
package:com.lge.wificall
package:com.lge.bluetoothsetting
package:com.lge.hotspotlauncher
package:com.android.proxyhandler
package:com.google.android.feedback
package:com.google.android.printservice.recommendation
package:com.google.android.apps.photos
package:com.google.android.syncadapters.calendar
package:com.android.managedprovisioning
package:com.lge.coneshortcut
package:com.lge.themeservice
package:com.lge.filemanager
package:com.ipsec.vpnclient
package:com.lge.intelligent
package:com.android.providers.partnerbookmarks
package:com.google.android.gsf.login
package:com.android.wallpaper.livepicker
package:com.android.apps.tag
package:com.lge.easyhome
package:com.lge.hiddenmenu
package:com.lge
package:com.lge.onehandcontroller
package:com.lge.networksettings
package:com.lt.dra
package:com.google.android.backuptransport
package:com.lge.privacylock
package:com.lge.provider.signboard
package:com.lge.mtalk.sf
package:com.android.bookmarkprovider
package:com.android.settings
package:com.lge.conerecent
package:com.qualcomm.location
package:com.qualcomm.simcontacts
package:com.lge.NfcSettings
package:com.lt.echolocate
package:com.android.cts.ctsshim
package:com.lge.appwidget.signature
package:com.qualcomm.qti.tetherservice
package:com.lge.eulaprovider
package:com.lge.ime
package:com.lge.ims
package:com.lge.mlt
package:com.lge.wernicke
package:com.android.vpndialogs
package:com.lge.videoplayer
package:com.qualcomm.location.XT
package:com.lge.lgdrm.permission
package:com.lge.wifisettings
package:com.android.phone
package:com.android.shell
package:com.android.wallpaperbackup
package:com.android.providers.blockednumber
package:com.lge.drmservice
package:com.lge.videostudio
package:com.lge.sizechangable.musicwidget.widget
package:com.android.providers.userdictionary
package:com.lge.hifirecorder
package:com.lge.cic.eden.service
package:com.lge.gnsslogcat
package:com.android.location.fused
package:com.android.systemui
package:com.lge.provider.systemui
package:com.android.bluetoothmidiservice
package:com.lge.provider.lockscreensettings
package:com.lge.clock
package:com.lge.email
package:com.lge.imsvt
package:com.lge.leccp
package:com.lge.music
package:com.lge.inputdevices
package:com.lge.gametuner
package:com.crucialsoft.asm
package:com.lge.lginstallservies
package:com.lge.signboard
package:com.android.bluetooth
package:com.qualcomm.timeservice
package:com.qualcomm.atfwd
package:com.android.providers.contacts
package:com.lge.servicemenu
package:com.android.captiveportallogin
package:com.lge.ime.solution.handwriting
package:com.lge.theme.highcontrast
elsa:/ #
How would those apps have started failing for you?

You could probably press back or home on the navbar to silence the call. If that doesn't work enable the "flip to silence call" under Settings>Call>More>Gestures.

[DISCUSSION][PORT][J600G] Trying to port Prometheus ROM to J6

Hi guys,
Just thought I'd open up a thread where I can share my advancement on porting this great ROM
I am no porting expert, so I am really hoping to get some pointers and maybe some help from users and developers
The link to the ROM I want to port is this: https://forum.xda-developers.com/ga...ment/rom-prometheuslite-a6-port-v1-0-t3810860
Thanks to @ananjaser1211 for giving me the opportunity to port his great work
Both having the same processor makes things a whole lot easier, so there hasn't been much input on my part lol
Here I want to list the things that I have working and not-working so far:
Working:
-Edge screen
-Smart select
-Scroll capture
-Pop-up multiwindow
-Bixby vision (to some extent, haven't gotten it fully functional on the camera)
Most of these are almost framework dependent, so that is why they work pretty well.
Now, on to the things that don't work and I might need some pointers to make them work
Not working:
-Always On Display
-Infinity wallpapers
-Edge lighting (though, I think this doesn't work on the original ROM either)
I am of course still testing a few things here and there and trying to fix as much as possible.
Any suggestion is welcome, though I will try not to modify Anan's original ROM too much to keep it as close to his version as possible
I am attaching a few screenshots of what's working so far
Any questions, feel free to ask. Well, except ETA, I would appreciate that
Thanks guys!

I'm getting a very interesting crash on SystemUI.
It seems that if I replace the SystemUI, even with an exact copy of the UI I am using right now, I get the following crash upon reboot:
Code:
11-06 10:20:55.644 5392 6197 E AndroidRuntime: FATAL EXCEPTION: UEventObserver
11-06 10:20:55.644 5392 6197 E AndroidRuntime: Process: com.android.systemui, PID: 5392
11-06 10:20:55.644 5392 6197 E AndroidRuntime: java.lang.RuntimeException: Unable to open socket for UEventObserver
11-06 10:20:55.644 5392 6197 E AndroidRuntime: at android.os.UEventObserver.nativeSetup(Native Method)
11-06 10:20:55.644 5392 6197 E AndroidRuntime: at android.os.UEventObserver.-wrap3(Unknown Source:0)
11-06 10:20:55.644 5392 6197 E AndroidRuntime: at android.os.UEventObserver$UEventThread.run(Unknown Source:0)
11-06 10:20:55.644 5392 5392 D StorageNotification: onDiskScannedInternal (DiskInfo{disk:179,32}:
11-06 10:20:55.644 5392 5392 D StorageNotification: flags=SD size=63864569856 label= volumeCount=1
11-06 10:20:55.644 5392 5392 D StorageNotification: sysPath=/sys//devices/13560000.dwmmc2/mmc_host/mmc2/mmc2:aaaa/block/mmcblk1
11-06 10:20:55.644 5392 5392 D StorageNotification:
11-06 10:20:55.644 5392 5392 D StorageNotification: )
11-06 10:20:55.644 2652 2652 E audit : type=1300 audit(1541521255.625:347): arch=40000028 syscall=281 per=8 success=no exit=-13 a0=10 a1=2 a2=f a3=eb3da4e0 items=0 ppid=2757 pid=6197 auid=4294967295 uid=10008 gid=10008 euid=10008 suid=10008 fsuid=10008 egid=10008 sgid=10008 fsgid=10008 tty=(none) ses=4294967295 comm="UEventObserver" exe="/system/bin/app_process32" subj=u:r:priv_app:s0:c512,c768 key=(null)
11-06 10:20:55.645 3204 4259 D Notification: allPendingIntents
11-06 10:20:55.645 2837 2837 W keystore: ENTER remove operation from uid 10050
11-06 10:20:55.646 3204 4330 V RescueParty: Disabled because of manual property
11-06 10:20:55.646 3204 4330 D Debug : [email protected] : SHIP
11-06 10:20:55.646 3204 4330 D Debug : [email protected] : debug level:0x4f4c
11-06 10:20:55.646 3204 4330 D Debug : [email protected] : Finally, system will skip dumpstate
11-06 10:20:55.646 2652 2652 E audit : type=1327 audit(1541521255.625:347): proctitle="com.android.systemui"
11-06 10:20:55.646 3204 4330 W ActivityManager: crash : com.android.systemui,0
11-06 10:20:55.646 3204 3224 D SecurityLogAgent:SEDenialService: Got Modify Event and sending Denial Intent for audit.log / "com.android.systemui"
11-06 10:20:55.647 3204 3224 W ContextImpl: Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:0 com.android.server.SEDenialService$AuditFileObserver.onEvent:126 android.os.FileObserver$ObserverThread.onEvent:40 android.os.FileObserver$ObserverThread.observe:-2 android.os.FileObserver$ObserverThread.run:2
11-06 10:20:55.647 3204 4330 W ActivityManager: Process com.android.systemui has crashed too many times: killing!
11-06 10:20:55.648 5392 5392 D StorageNotification: start() notiListSize is [1]
11-06 10:20:55.648 5661 5661 I SEMS:SamsungAccount: Not Skip Name Validation by accountMCC
11-06 10:20:55.649 5392 5392 D StorageNotification: start() Notification ID (27)
11-06 10:20:55.649 5392 6197 I Process : Sending signal. PID: 5392 SIG: 9
You can find the full log: Here
Interestingly, if I reboot normally without replacing SystemUI, the system boots fine.
If I replace the SystemUI (even with a copy of what I currently have in the folder), it crashes upon reboot but works fine if I don't do a reboot
Can't fix it it with a recovery of the /system partition
I have to do a recovery of the /data partition, so I'm sure something gets messed up there
Can anybody help?

Ok, I'm going to have to backtrack a little
Initially, I kept getting crashes on something called SSRM (which exists in system/framework/ssrm.jar)
It was calling some methods that exist in port framework.jar and services.jar but not on stock fw.
I tried to take the easy way out and replace ssrm.jar with stock ssrm.jar because they differ way too much. I'm talking like, SERIOUSLY a lot (80% different in regards to smali and location of said smali, even names.)
It works to get it booted and running without problems, but then I get the issue I stated on post #2 when I want to change anything regarding the SystemUI. I haven't tried installing ROM from a clean install but my best bet is that it's going to cause problems too (will update this post because I want to try it)
So here we go again, attempting the port from 0
I had done very little work on it, anyway so it's not a huge loss
Hopefully ai can come back with positive news on the weekend, where I can give it a better look

workin bro in j600g?

ezer90 said:
workin bro in j600g?
Click to expand...
Click to collapse
Yes, my variant is J600G
However I haven't made any real progress, that's why I haven't shared it yet

ShaDisNX255 said:
Yes, my variant is J600G
However I haven't made any real progress, that's why I haven't shared it yet
Click to expand...
Click to collapse
My variant is J600GM
---------- Post added at 01:31 AM ---------- Previous post was at 01:31 AM ----------
what kernel used in the rom?
---------- Post added at 01:32 AM ---------- Previous post was at 01:31 AM ----------
what kernel used in the rom?

ezer90 said:
My variant is J600GM
---------- Post added at 01:31 AM ---------- Previous post was at 01:31 AM ----------
what kernel used in the rom?
---------- Post added at 01:32 AM ---------- Previous post was at 01:31 AM ----------
what kernel used in the rom?
Click to expand...
Click to collapse
Stock kernel

Hows sensor? Do you yave telegram

slazh101 said:
Hows sensor? Do you yave telegram
Click to expand...
Click to collapse
Sensor? I don't understand.
Ues, same username in Telegram

What about J600F ? Can you add support for J600F later?

zahidul.sifat said:
What about J600F ? Can you add support for J600F later?
Click to expand...
Click to collapse
I can't add support to a device I don't have. Maybe there are no differences between variants but I can't guarantee it

ShaDisNX255 said:
Hi guys,
Just thought I'd open up a thread where I can share my advancement on porting this great ROM
I am no porting expert, so I am really hoping to get some pointers and maybe some help from users and developers
The link to the ROM I want to port is this: https://forum.xda-developers.com/ga...ment/rom-prometheuslite-a6-port-v1-0-t3810860
Thanks to @ananjaser1211 for giving me the opportunity to port his great work
Both having the same processor makes things a whole lot easier, so there hasn't been much input on my part lol
Here I want to list the things that I have working and not-working so far:
Working:
-Edge screen
-Smart select
-Scroll capture
-Pop-up multiwindow
-Bixby vision (to some extent, haven't gotten it fully functional on the camera)
Most of these are almost framework dependent, so that is why they work pretty well.
Now, on to the things that don't work and I might need some pointers to make them work
Not working:
-Always On Display
-Infinity wallpapers
-Edge lighting (though, I think this doesn't work on the original ROM either)
I am of course still testing a few things here and there and trying to fix as much as possible.
Any suggestion is welcome, though I will try not to modify Anan's original ROM too much to keep it as close to his version as possible
I am attaching a few screenshots of what's working so far
Any questions, feel free to ask. Well, except ETA, I would appreciate that[emoji14]
Thanks guys!
Click to expand...
Click to collapse
Please link test rom, my model j600g
Sent from my SM-J600G using XDA-Developers Legacy app

manuelamadeo said:
Please link test rom, my model j600g
Sent from my SM-J600G using XDA-Developers Legacy app
Click to expand...
Click to collapse
Please don't quote the entire OP
I am not done porting it since that is why I haven't shared it yet

ShaDisNX255 said:
Please don't quote the entire OP
I am not done porting it since that is why I haven't shared it yet
Click to expand...
Click to collapse
If you need help, you can count on me, my knowledge is not so many but in what I can help I will.
Sent from my SM-J600G using XDA-Developers Legacy app

I'm probably going to end this project.
While Prometheus ROM is relatively easy to port since both devices share the same processor, I noticed slight differences and it mainly has to do with the screen ratio. I can't activate the full screen on games and I am betting it has to do something in framework. Which is probably easy to revert back to allow it, but I am waaaaaaaay too lazy to look it up
Besides, I've been wanting to port the S9 firmware for a while now, and do it on my own
I am certain that Prometheus is going to be a better alternative than my S9 ported firmware, this is sort of a personal thing. I want to be able to port this firmware by myself.
But who knows, I'll update when I can because I haven't really done anything to the ROM (Prometheus)
I don't think I'll be sharing it either because:
1) It is a half-finished port, there are many bugs to be expected (but from personal use, I haven't experienced any bugs other than theme store crashing about once a day and Bixby vision on camera not working)
and
2) Can't install it by a clean install (wiping /data). I can only get this running on a dirty flash without wiping /data
Lazy lazy lazy is all I can say lol but yeah
After I port my own S9 firmware as a base, maybe I can come back to this as I am sure anan added more things than I would add to mine xD
Thanks everyone for understanding

ShaDisNX255 said:
I'm probably going to end this project.
While Prometheus ROM is relatively easy to port since both devices share the same processor, I noticed slight differences and it mainly has to do with the screen ratio. I can't activate the full screen on games and I am betting it has to do something in framework. Which is probably easy to revert back to allow it, but I am waaaaaaaay too lazy to look it up
Besides, I've been wanting to port the S9 firmware for a while now, and do it on my own
I am certain that Prometheus is going to be a better alternative than my S9 ported firmware, this is sort of a personal thing. I want to be able to port this firmware by myself.
But who knows, I'll update when I can because I haven't really done anything to the ROM (Prometheus)
I don't think I'll be sharing it either because:
1) It is a half-finished port, there are many bugs to be expected (but from personal use, I haven't experienced any bugs other than theme store crashing about once a day and Bixby vision on camera not working)
and
2) Can't install it by a clean install (wiping /data). I can only get this running on a dirty flash without wiping /data
Lazy lazy lazy is all I can say lol but yeah
After I port my own S9 firmware as a base, maybe I can come back to this as I am sure anan added more things than I would add to mine xD
Thanks everyone for understanding
Click to expand...
Click to collapse
I would like you to pass me the link and tinker, continue with your progress, the bug you mentioned is not a problem for me, please send Link for download by private.
Sent from my [device_name] using XDA-Developers Legacy app

Is there any method to root Samsung J600G ???

Good news
Seems that my S9 port is almost ready to go.
I'm testing this whole week to make sure I don't have major bugs, but for the most part it seems to be stable
I am trying to fix just one final thing, which is the Game Tools that don't seem to work, they don't appear on any game
I've lost one neat feature that Prometheus had and that the S9 doesn't, which is Bixby Vision on screen capture. Or even on the camera, for that matter.
In fact, I ditched the S9 camera and kept stock (for now) as I did not want to get into camera specifics for the time being, for this first version all I want to do is get a solid S9 firmware port for you guys to help me figure out some small bugs maybe I can try to fix.
On the flip side, I gained Infinity Wallpapers that I couldn't get to work on Prometheus on the J6 for some reason, but that's my fault as I just didn't give enough effort on it :S
Also Edge lighting works great, I am so happy to have this feature
Huge thanks to @ananjaser1211 for sharing his knowledge and experience on his S9 port and fixes he shared with me, I would have been lost without his help.
I haven't tried things like face recognition, which I believe will also give problems but I'll slowly start testing all these things out and if all goes well, I'll share the ROM in 6 days time
Thanks everyone for being so patient

Good i want to learn how to port ill wait you does this firmware have features for game? Like over locking gpu ? Because some games ceash becuase stock kernel have a default gpu clocm to 343mhz while the gpu came with 1001 mhz..

zzDoWnzz said:
Good i want to learn how to port ill wait you does this firmware have features for game? Like over locking gpu ? Because some games ceash becuase stock kernel have a default gpu clocm to 343mhz while the gpu came with 1001 mhz..
Click to expand...
Click to collapse
Nope, no overclocking features. I didn't touch the kernel as I have 0 knowledge on kernel building and lack my own PC to do so.
I mean the software has "Performance mode" in it, but I doubt it really improves on anything as again, it is stock kernel and lacks modification to unlock some features like AOD.
My humble suggestion would be, don't expect much out of this device. It is a 3 year old processor and if you want any sort of gaming power I would buy a newer phone. Samsung really cheaped out on the J6, just seems like a lazy device lol