[OFFICIAL][RECOVERY]TWRP 3.1.x for Galaxy SM-J5008/H/F/G/M/NO/Y/FN

Dec 26, 2016
22
4
0
Is Adoptable Storage supported on this recovery? Adopted storage doesn't appear (because of the decryption) on some devices, said TWRP team. But they've fixed it years ago already. Btw, j500f Nougat
 

JosephDM

Senior Member
Dec 12, 2016
777
358
0
@vince2678 congratulations with your official twrp status but a user complaint about error 7 while flashing rom so he needed to add "j5nltexx" in the updater script... I thought you fixed it before giving official status buddy, so the most stable build remains the 28 may build for FN
 

vince2678

Recognized Developer
Jul 5, 2016
1,071
1,900
0
@vince2678 congratulations with your official twrp status but a user complaint about error 7 while flashing rom so he needed to add "j5nltexx" in the updater script... I thought you fixed it before giving official status buddy, so the most stable build remains the 28 may build for FN
That should be fixed in the builds at twrp.me/devices/j5nltexx.html

If you can test the builds yourself and find that the problem is still there, tell me.
 

serdotlinecho

Senior Member
Jun 25, 2015
286
106
0
That should be fixed in the builds at twrp.me/devices/j5nltexx.html

If you can test the builds yourself and find that the problem is still there, tell me.
I have J500G. I got an error when flashing Lineage 14.1. Please, do take a look at the log that I've attached. Hope you will fix this issue on the next build.
 

Attachments

JosephDM

Senior Member
Dec 12, 2016
777
358
0
That should be fixed in the builds at twrp.me/devices/j5nltexx.html

If you can test the builds yourself and find that the problem is still there, tell me.
Tested on FN like I said before there's still error 7 issue, other F user confirmed this error 7 problem with official version. Maybe if you compare the 28 may build with the latest will find the problem :)
 

American_Jesus

Senior Member
Mar 9, 2016
508
298
73
Lisbon
The issue is wrong ro.product.device
I fixed that on J500F, replaced j5nltexx with j5nlte.

I was having the same problem when using DualBootPatcher, it gets the product device from recovery, changed ro.product.device j5ltexx to j5lte on default.prop and repacked the recovery, and now the issue is gone.

I've attached the getprop from TWRP 3.0.2 (with multirom) by ganesh and 3.1.1 to compare it.

Heres all the correct names:
Code:
MODEL        NAME       DEVICE
SM-J5008     j5ltezm    j5ltechn
SM-J500F     j5ltexx    j5lte
SM-J500FN    j5nltexx   j5nlte
SM-J500G     j5ltedx    j5lte
SM-J500H     j53gxx     j53g
SM-J500M     j5lteub    j5lte
SM-J500N0    j5ltekx    j5ltekx
SM-J500Y     j5yltedo   j5ylte
Source: https://autoroot.chainfire.eu/
 

Attachments

vince2678

Recognized Developer
Jul 5, 2016
1,071
1,900
0
I have J500G. I got an error when flashing Lineage 14.1. Please, do take a look at the log that I've attached. Hope you will fix this issue on the next build.

Tested on FN like I said before there's still error 7 issue, other F user confirmed this error 7 problem with official version. Maybe if you compare the 28 may build with the latest will find the problem :)

The issue is wrong ro.product.device
I fixed that on J500F, replaced j5nltexx with j5nlte.

I was having the same problem when using DualBootPatcher, it gets the product device from recovery, changed ro.product.device j5ltexx to j5lte on default.prop and repacked the recovery, and now the issue is gone.

I've attached the getprop from TWRP 3.0.2 (with multirom) by ganesh and 3.1.1 to compare it.

Heres all the correct names:

Source: https://autoroot.chainfire.eu/
I've sent the changes to the twrp people for submission, depending on how busy they are, the issue should be fixed and new builds issued in the next few day(s).
 

urgot245

Senior Member
Aug 26, 2017
72
14
0
Ok guys, newest twrp updates support installing any aroma package.

Go grab it, also join this chat @GrandPrimeTWFZ for newer updates.
Tried to flash twrp 3.1.1-1 from twrp app and i couldnt boot in system or recovery. It showed samsung logo and it showed like i was in download mode. I needed to reflash 3.1.1-0 to work again