[MASTER THREAD][SM-J260F/G/M/Y/DS][J2CORELTE] Samsung Galaxy J2 Core 2018

[$_Vladislav]

Versions: SM-J260M/DS (LATIN); SM-J260Y/DS (Philippines); SM-J260G/DS (India); SM-J260F/DS (CIS)

*CIS - Union of Independent States (Russia, Kazakhstan, Tajikistan, Uzbekistan, Armenia, Belarus, Azerbaijan, Kyrgyzstan, Moldova)

NETWORK
Technology GSM / HSPA / LTE
2G bands GSM 850 / 900 / 1800 / 1900 - SIM 1 & SIM 2
3G bands HSDPA 850 / 900 / 2100 - J260Y/DS, J260G/DS, J260F/DS
HSDPA 850 / 900 / 1700(AWS) / 1900 / 2100 - J260M/DS
4G bands LTE band 2100, 1800, 850, 2600, 900, 700, 2600, 2300, 2500 - J260Y/DS,
LTE band 2100, 1900, 1800, 1700/2100, 850, 2600, 900, 700, 700, 700 - J260M/DS
LTE band 2100, 1800, 850, 2600, 900, 800 - J260G/DS
LTE band 800, 850, 900, 1800, 2100, 2300, 2500, 2600 - J260F/DS
Speed HSPA 42.2/5.76 Mbps, LTE Cat4 150/50 Mbps
GPRS Yes
EDGE Yes
LAUNCH
Announced 2018, August
Status Available. Released 2018, August
BODY
Dimensions 143.4 x 72.1 x 8.9 mm (5.65 x 2.84 x 0.35 in)
Weight 154 g (5.43 oz)
SIM Dual SIM (Micro-SIM, dual stand-by)
DISPLAY
Type PLS TFT LCD capacitive touchscreen, 16M colors
Size 5.0 inches, 68.9 cm2*(~66.7% screen-to-body ratio)
Resolution 540 x 960 pixels, 16:9 ratio (~220 ppi density)
Protection Corning Gorilla Glass (unspecified version)
PLATFORM
OS Android 8.1 Oreo (Go edition)
Chipset Exynos 7570 Quad (14 nm)
CPU Quad-core 1.4 GHz Cortex-A53
GPU Mali-T720
MEMORY
Card slot microSD, up to 256 GB (dedicated slot)
Internal 8 GB, 1 GB RAM
MAIN CAMERA
Single 8 MP, AF, f/2.2
Features LED flash, HDR, panorama
Video 1080p@30fps
SELFIE CAMERA
Single 5 MP, f/2.2
SOUND
Loudspeaker Yes
3.5mm jack Yes
COMMUNICATIONS
WLAN Wi-Fi 802.11 b/g/n, Wi-Fi Direct, hotspot
Bluetooth 4.2, A2DP
GPS Yes, with A-GPS, GLONASS, BDS
Radio FM radio
USB microUSB 2.0, USB On-The-Go
FEATURES
Sensors Accelerometer, proximity
Messaging SMS(threaded view), MMS, Email, Push Email, IM
Browser HTML
BATTERY
Removable Li-Ion 2600 mAh battery
MISC
Colors Black, Gold, Lavender
SAR 0.61 W/kg (head) * * 0.61 W/kg (body) * *
SAR EU 1.39 W/kg (body) * *
Price About 100 EUR

 

[alameery13]

(ذ)

 

[galaxys]

It's a February 2019 2 Year old thread...

 

[Vanxploit]

How to fix safetynet in my device j260g ?

 

[EyzTOP01.L]

This thread would be almost unattended, for me it's a fresh start, interested on building the TWRP recovery project for SM-J260M ( The common Latin-American variant I think, 2018 version) and have seen your posted trees on GitHub, given the fact that this user: https://github.com/Vladislav4KZ belongs you. In the case that you can advice me a little nuances for this device --being a noobie on this matter-- please are you able to describe how you grasped the kernel tree? I´ve picked a kernel tree from: https://github.com/MT6797/kernel-3.18 . Due to I've looked on my phone's settings that it's Linux kernel version was 3.18.14 (See Attachment below) .

About the vendor tree, which one have you used? I'm currently picking this universal exynos7570 Android8.1 vendor tree from: https://github.com/OpenExynos/android_vendor_samsung_slsi_exynos7570/tree/android-8.1.0_r1 .

The device-tree, I've leveraged from SebaUbuntu's device tree generator: https://github.com/twrpdtgen/twrpdtgen . After that, I've chosed the repository from https://android.googlesource.com/platform/build/+/refs/tags/android-8.1.0_r51 to perform the build. I've got some errors, specially when compiling the kernel, I've worked-around the common erros that were most related to an outdated programming language: python2 on files that were being built with python3.
When I've finalized clearing that files, they were few, I've decided to take the kernel and vendor tree out of the build. So i've chosen the omni_device_tree that's for default created when creating the google-Android building repo and syncing it. Got a successful recovery image, until I've tested it and got the problem of the classical blinking-screen when I've booted the device at recovery.

🗨🗨 Questions:

How you grasped the kernel-tree?

Which vendor-tree have you used?

How can I compile the kernel adequately for this model that is a little bit different than your: SM-J260F ?

Have you compiled a recovery image for your device? If yes, were you succesful? What problems you've faced as the main rocks hindering the build process's completion? What you changed, in case you've flashed it but got a blinking screen?

 

[notnoelchannel]

This thread would be almost unattended, for me it's a fresh start, interested on building the TWRP recovery project for SM-J260M ( The common Latin-American variant I think, 2018 version)

Hi, I just built TWRP 3.6.2-9 for your device. Can you test it? Here's the flashable file

 

[EyzTOP01.L]

Hi, I just built TWRP 3.6.2-9 for your device. Can you test it? Here's the flashable file

Thank you, first sucessful TWRP image that past beyond the blinking screen, in fact it booted-up smoothly, unfortunately it's not recognizing the touchscreen and that limits it's ability to test and point more flags about it. What have happened when I've tried to reboot to the system is that it didn't worked, when an odd-recovery image is flashed on this device model seemingly it doesn't return to normality unless you're able to do that from the recovery itself i.e not forcing it by withdrawing the battery or pressing button combinations for restarting; I've fixed that issue by flashing the stock recovery back to the device via Odin ( the only resource for rescuing this device) and worked up to the normal state, no problems after that. Here I show you below, sorry for my phone's state, it has suffered a fall that slapped it's external surface, fortunately hardware still intact, and relative to it's touch sensitivity it works seamlessly as you can note in the next attachment.

There for that particular problem, by changing or adding some flags on your BoardConfig.mk file that lies on the device tree folder you can fix it. It's mentioned on other XDA threads and some TWRP-compiling channels found youtube. I would be pretty grateful in case you show point me out the device, kernel and vendor blobs that you've used for compiling the recovery. As I've previously stated: the blobs I've used led me to the blinking screen failure and I am figuring out about what I've made wrong, I'm a beginner and would appreciate the epiphany that you'd cater me in case you teach me about the code and what you've made, particularly on the blob trees. Thank you very much in advance.

 

[notnoelchannel]

Thank you, first sucessful TWRP image that past beyond the blinking screen, in fact it booted-up smoothly, unfortunately it's not recognizing the touchscreen and that limits it's ability to test and point more flags about it. What have happened when I've tried to reboot to the system is that it didn't worked, when an odd-recovery image is flashed on this device model seemingly it doesn't return to normality unless you're able to do that from the recovery itself i.e not forcing it by withdrawing the battery or pressing button combinations for restarting; I've fixed that issue by flashing the stock recovery back to the device via Odin ( the only resource for rescuing this device) and worked up to the normal state, no problems after that. Here I show you below, sorry for my phone's state, it has suffered a fall that slapped it's external surface, fortunately hardware still intact, and relative to it's touch sensitivity it works seamlessly as you can note in the next attachment.

There for that particular problem, by changing or adding some flags on your BoardConfig.mk file that lies on the device tree folder you can fix it. It's mentioned on other XDA threads and some TWRP-compiling channels found youtube. I would be pretty grateful in case you show point me out the device, kernel and vendor blobs that you've used for compiling the recovery. As I've previously stated: the blobs I've used led me to the blinking screen failure and I am figuring out about what I've made wrong, I'm a beginner and would appreciate the epiphany that you'd cater me in case you teach me about the code and what you've made, particularly on the blob trees. Thank you very much in advance.

I compiled TWRP on android-8.1 branch too. That might be the solve of the no touch problem.

About compiling, you'll just have to get these:
Minimal TWRP manifest twrp-8.1 branch here
And a device tree from here

In the device tree, we already have a prebuilt kernel. So we don't need any kernel source. Same for vendor.

I'll try to fix touch by building on higher branches.

 

[notnoelchannel]

Here's a smaller PORTED twrp version:

 

[EyzTOP01.L]

Here's a smaller PORTED twrp version:

Same issue with the touchscreen, can't swipe to unlock, the only noticeable change was the color and of course it's smaller size. Have you tried adding some flags at the BoardConfig.mk? Could you please try developing with the 9.0 Branch, I only have the 8.1 one and low space on disk. Thanks

 

[EyzTOP01.L]

Sorry, Sir, excuse me for asking advice there, but I got stuck and found no way to get out of this issue when compiling the recovery-image fror the J260M: on my build directory: bionic/libc/bionic/grp_pwd.cpp . This file deploys a bunch of errors that are related with the C++ language, such as = bionic/libc/bionic/grp_pwd.cpp:137:46: error: unknown type name 'android_id_info' or undeclared identifier on some other lines. Finally outputing the following hurdle for continuing the process:

fatal error: too many errors emitted, stopping now [-ferror-limit=] 20 errors generated.​

What could I do, it's my mistake or it's one from the android-security-8.1.0_r81 branch code? ( which was the one I've initialized and synced the repo for building). What have you made to compile the image without those errors?. No matter if I build with/without kernel source this error always stucks my progress.

 

[notnoelchannel]

Sorry, Sir, excuse me for asking advice there, but I got stuck and found no way to get out of this issue when compiling the recovery-image fror the J260M: on my build directory: bionic/libc/bionic/grp_pwd.cpp . This file deploys a bunch of errors that are related with the C++ language, such as = bionic/libc/bionic/grp_pwd.cpp:137:46: error: unknown type name 'android_id_info' or undeclared identifier on some other lines. Finally outputing the following hurdle for continuing the process:

fatal error: too many errors emitted, stopping now [-ferror-limit=] 20 errors generated.​

What could I do, it's my mistake or it's one from the android-security-8.1.0_r81 branch code? ( which was the one I've initialized and synced the repo for building). What have you made to compile the image without those errors?. No matter if I build with/without kernel source this error always stucks my progress.

Build with the device tree and manifest i linked

 

[EyzTOP01.L]

Build with the device tree and manifest i linked

No matter what I've tried, followed your steps closely, even switched to the 9.0 branch but it seems to not work up due to so many erros on the code of the whole android source. What would have I messed up for the Building Platform to deploy so many issues and hence leaving me unsuccesful from completing the recoveryimage compilation . How can I work this? If i haven't wrote the android source code...

 

[Noobmaster205]

any updates?

 

[Parthib]

Same issue with the touchscreen, can't swipe to unlock...

The touch driver doesnt load when you are in recovery mode as you can see here - synaptics_i2c_rmi.c#probe. You should try installing the recovery image in boot partition and see if it works.

If it works then rebuild the kernel with that check disabled, so it works while in recovery mode.

 

[EyzTOP01.L]

Thank you for your reply, a few months ago I managed to build a TWRP with almost all partitions, except "cpefs" partition, working, I've used the kernel source for it, however I've excluded on the main kernel makefile manifest the following files which I've ported from other exynos7570 devices such as the J5 Prime: exynos7570_acpm_draminit_s.fw ; exynos7570_acpm_pedo.fw . By that I've got this result, I'm going to build what you've suggested to look if I can make now the touchscreen driver work, despite that, if you use OTG cable for connecting a mouse, then you can confirm that on this recovery image all of the partition except the one I mentioned above get mounted.

Flash it via Odin.

Wasn't easy, nor impossible. This prototype will hopefully become the effective one.

 

[notnoelchannel]

Thank you for your reply, a few months ago I managed to build a TWRP with almost all partitions, except "cpefs" partition, working, I've used the kernel source for it, however I've excluded on the main kernel makefile manifest the following files which I've ported from other exynos7570 devices such as the J5 Prime: exynos7570_acpm_draminit_s.fw ; exynos7570_acpm_pedo.fw . By that I've got this result, I'm going to build what you've suggested to look if I can make now the touchscreen driver work, despite that, if you use OTG cable for connecting a mouse, then you can confirm that on this recovery image all of the partition except the one I mentioned above get mounted.

Flash it via Odin.

Wasn't easy, nor impossible. This prototype will hopefully become the effective one.

good luck for getting twrp working for this device, if you are tired of building, i can build freely

 

[notnoelchannel]

Okay, i'll try to build the kernel with patched touchscreen driver, wish me luck

 

[notnoelchannel]

Okay, i'll try to build the kernel with patched touchscreen driver, wish me luck

Sorry for disappearing for a long time, now i'm really building the kernel
Edit: it failed

 

[Skorpion96]

just tried to port twrp with Hovatek Samsung Auto TWRP recovery Porter 1.1, give it a try:https://www.mediafire.com/file/92ri...J260YDS-A9-Test-by-autotwrprecporter.img/file
Another thing that can be tried is to take fstab from this build and merge it with old builds and so twrp should be able to mount partitions, this if hovatek build does not boot