On Galaxy J5 2016 (J510H) fastboot doesnt work about lk2nd HOT 14 CLOSED

the dtb line says 248/.../5 so your file is dts/msm8916/msm8216-samsung-r05.dts. (note the 8216 for 3g-only SoC)

You can find those numbers in that file, this is why I told you to check dts/msm8916/msm8216-samsung-r<XX>.dts, sorry that I wasn't clear enough

So now all works fine, I will make a PR, thanks!

from lk2nd.

if your device shows "model = unknown" on the screen, you will need to add it to the lk2nd's device database.

You would need to add something like this to a correct dts/msm8916/msm8216-samsung-r<XX>.dts file:

I think there should be a "DTB" line on the screen that would show which file to pick.

from lk2nd.

if your device shows "model = unknown" on the screen, you will need to add it to the lk2nd's device database.

You would need to add something like this to a correct dts/msm8916/msm8216-samsung-r<XX>.dts file:

lk2nd/dts/msm8916/msm8916-samsung-r04.dts

Lines 44 to 50 in 6b85f2e

	j5xnltejv {
	model = "Samsung Galaxy J5 2016 LTE (EUR)";
	compatible = "samsung,j5xnlte", "qcom,msm8916", "lk2nd,device";
	lk2nd,match-bootloader = "J510F*";
	#include "msm8916-samsung-j5.dtsi"
	};

I think there should be a "DTB" line on the screen that would show which file to pick.

Compiled with

j5xn3g {
		model = "Samsung Galaxy J5 2016 (SM-J510H)";
		compatible = "samsung,j5xn3g", "qcom,msm8916", "lk2nd,device";
		lk2nd,match-bootloader = "J510H*";

		#include "msm8916-samsung-j5.dtsi"
	};

and have stucked on logo

from lk2nd.

If you compile lk2nd without any changes, does it work?

Could you tell me what was in the DTB line on screen and what file did you add the above to?

from lk2nd.

does it work?

No

from lk2nd.

How do you build and install the lk2nd image?

from lk2nd.

How do you build and install the lk2nd image?

make TOOLCHAIN_PREFIX=arm-linux-gnueabihf- lk2nd-msm8916

heimdall flash --BOOT lk2nd.img

from lk2nd.

Maybe should I compile 64 bit?

from lk2nd.

Can you get an arm-none-eabi- toolchain? lk2nd is always 32bit but I won't be surprised if it won't build properly with a hf toolchain...

from lk2nd.

Can you get an arm-none-eabi- toolchain? lk2nd is always 32bit but I won't be surprised if it won't build properly with a hf toolchain...

So it works, let me compile with

j5xn3g {
		model = "Samsung Galaxy J5 2016 (SM-J510H)";
		compatible = "samsung,j5xn3g", "qcom,msm8916", "lk2nd,device";
		lk2nd,match-bootloader = "J510H*";

		#include "msm8916-samsung-j5.dtsi"
	};

from lk2nd.

@TravMurav Model it still unknown

from lk2nd.

Could you tell me what was in the DTB line on screen and what file did you add the above to?

then let's continue with the second question :)

from lk2nd.

Could you tell me what was in the DTB line on screen and what file did you add the above to?

then let's continue with the second question :)

DTB - <248 0xf808ff01 0 0x5>

I put in dts/msm8916/msm8916-samsung-r04.dts

from lk2nd.

the dtb line says 248/.../5 so your file is dts/msm8916/msm8216-samsung-r05.dts. (note the 8216 for 3g-only SoC)

You can find those numbers in that file, this is why I told you to check dts/msm8916/msm8216-samsung-r<XX>.dts, sorry that I wasn't clear enough

from lk2nd.