[UPDATE][RECOVERY][OFFICIAL][3.3.1-1][TWRP]Samsung J5 Prime - Samsung Galaxy J5 PRIME ROMs, Kernels, Recoveries,

Team Win Recovery Project 3.3.1-1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
WARNING : Flashing a custom recovery to your device will trip the Knox warranty bit on your phone. Check with your mobile provider to see if they will still cover warranty on Knox bit triggered devices. If you understand this risk, continue on.
You generally don't have to worry, as it's incredibly hard to brick a Samsung device, and physical damage warranties should be exempt from Knox triggering.
WHAT IS TWRP?
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
Downloads
Download the TWRP image :
TWRP 3.3.1-1
Direct Download Page
Download Odin and the drivers :
I highly recommend using Odin to flash when possible.
You can find a zip containing Odin as well as Samsung's Mobile drivers here:
https://build.nethunter.com/samsung-tools/
Download RMM bypass and no-verity-opt-encrypt zip files :
you will need to flash this no-verity-opt-encrypt-6.0.zip to be able to boot the device without encryption all data is going to be lost.
you will need to flash this RRM Bypass by Messa to disable RMM without it on android 8 you will not be able to boot after restart .
FULL STEPS FOR OBTAINING ROOT
follow these instructions:
1- In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
2- Now go to Settings -> Developer options. (above About device)
3- You need to enable OEM unlock, otherwise you might end up with boot problems or be unable to flash later on.
4- Extract Odin_3.12.3.zip to your computer.
5- Install Samsung Mobile Phone Drivers for Odin to find your device.
6- Download the .tar image of TWRP
7- Reboot your device into Download mode. To do this, select reboot from the power menu and hold the [Volume Down] +[Home] buttons while your device reboots.
8- Once you reach the Download mode warning screen, press [Volume Up] to continue.
9- Open Odin and place that TWRP tar file in the [AP] slot and disable Auto-Reboot , then press [Start].
Hold [Volume Down] + [Home] + [Power] to get out of Download mode and immediately swap to [Volume Up] when the screen blanks.
10 - If you don't see then TWRP boot splash try again from step 6.
10.5- now flash RMM-Bypass and no-verity zip files its very important .
11. If you want to be rooted Use Magisk:
Download the latest Magisk.
Without exiting TWRP, transfer the Magisk zip to your device over MTP* and flash it using [Install] in TWRP.
You will need an external SDcard for this method, if you don't have one you will have to use adb sideload to install Magisk.zip
12 . Go to [Reboot] -> [System].
Wait 2-5 minutes for your device to finish setting itself up.
13. flash the no-opt-no-verity.zip to disable the encryption if you want to be able to access your data via TWRP .
FEATURES
MTP support
Micro SDcard and USB OTG storage support
Full SELinux support
Built in android 6.0 tree
KNOWN ISSUES
Samsung encryption is not supported yet in TWRP 3.0
Data Partition
Because Encryption is not yet working ,If you want to be able to access data parition you have to format data and flash no-verity-opt-encrypt/
Updates
-Fixed OTG issue.
-Fixed SD card mount issue.
CONTACT & SUPPORT
You can find us on IRC at #twrp on chat.freenode.net.
You can also post in this thread and I will attempt to answer any questions you may have.
TWRP: https://github.com/omnirom/android_bootable_recovery (android-6.0)
Device tree:https://github.com/awab228/android_device_samsung_on5xelte (android-6.0)
Kernel Source : https://github.com/awab228/android_kernel_samsung_on5xelte (android-6.0)
TeamWin Recovery Project (TWRP), Tool/Utility for the Samsung J5 Prime
XDA:DevDB Information
[OFFICIAL][RECOVERY][TWRP][G570F], Tool/Utility for the Samsung Galaxy J5
Contributors
awab228, Captain_Throwback
Source Code: https://github.com/omnirom/android_bootable_recovery
Version Information
Status: Stable
Current Stable Version: 3.3.1-1
Stable Release Date: 2019-08-03
Created 2018-06-19
Last Updated 2019-12-5

---

Reserved
Confirmed working on :
1. 6.0
2. Nougat 7.0
3. Oreo 8.0
And all variation F M Y .
Becareful when rooting on android Oreo 8.0 might loose baseband

---

Reserved
Update:
-Fixed OTG issue , thanks to **prabhjot368
-Latest TWRP build [3.3.1-1]
-Fixed SD Card mount issue
-latest TWRP build [3.2-3.1]
-Added RMM bypass file
Don't forget to hit thank you button
?

---

Hello,
I tested on SM-G570M, running Nougat 7.0 firmware.
By odin, it install OK-SUCCESS, then i click on volume down+power to reboot (as i have disable the auto-reboot option inside odin)
But i could NOT enter to recovery mode, it shows a red alert: "only official released binaries are allow to be flashed"
But when i enter to download mode it shows: CUSTOM on recovery but i could not enter to device as shows always that alert.
I think the bootloader only access signed versions of the recovery. Any ideas to solve this?

---

droopyar said:
Hello,
I tested on SM-G570M, running Nougat 7.0 firmware.
By odin, it install OK-SUCCESS, then i click on volume down+power to reboot (as i have disable the auto-reboot option inside odin)
But i could NOT enter to recovery mode, it shows a red alert: "only official released binaries are allow to be flashed"
But when i enter to download mode it shows: CUSTOM on recovery but i could not enter to device as shows always that alert.
I think the bootloader only access signed versions of the recovery. Any ideas to solve this?
Click to expand...
Click to collapse
In the settings did you turn on OEM unlocking ? In the developer options.

---

droopyar said:
Hello,
I tested on SM-G570M, running Nougat 7.0 firmware.
By odin, it install OK-SUCCESS, then i click on volume down+power to reboot (as i have disable the auto-reboot option inside odin)
Click to expand...
Click to collapse
You are supposed to quickly press volume up as the screen goes black volume up + home + power instead of volume down + home + power

---

Thanks, nice work
---------- Post added at 02:41 PM ---------- Previous post was at 02:30 PM ----------
Awab228, sdcard no mount

---

AlexVolzsk said:
Thanks, nice work
---------- Post added at 02:41 PM ---------- Previous post was at 02:30 PM ----------
Awab228, sdcard no mount
Click to expand...
Click to collapse
Are you sure sdcard is formatted ?? And working when you start system ?
-------------------
I will test and check

---

awab228 said:
Are you sure sdcard is formatted ?? And working when you start system ?
-------------------
I will test and check
Click to expand...
Click to collapse
But why should I format sdcard)?
Where are you saw)?
Here is an employee of Twrp on your kernel.
https://mega.nz/#!pTZUhaLB!Ff9vWquzKsPudFEUqNVz53QDLPhmAg-obNnND0HqLKo

---

AlexVolzsk said:
But why should I format sdcard)?
Where are you saw)?
Here is an employee of Twrp on your kernel.
https://mega.nz/#!pTZUhaLB!Ff9vWquzKsPudFEUqNVz53QDLPhmAg-obNnND0HqLKo
Click to expand...
Click to collapse
I didn't say you have to format sdcard , I said are you sure the sdcard is formatted and working when you boot into system ?
------------------
What you mean by (here and employee of twrp on your kernel?)
It's not proper English , try to use a translator or post in your native language and I will translate , I think you speak Russian

---

Seems working PERFECT on SM-570M running Nougat 7.0 firmware.
I put OK the recovery , then use MESA to fix the red logo that only official binaries are allow to be flashed, and root it using Magisk
I have a problem related to remount /system as seems it give me an error. Any command to remount /system ok so it is writable? (on NOUGAT)

---

puedo colocar este twrp en mi g570m sin memoria sd y con android 7.0?

---

droopyar said:
I have a problem related to remount /system as seems it give me an error. Any command to remount /system ok so it is writable? (on NOUGAT)
Click to expand...
Click to collapse
The system is writable , it is mounted by default

---

hiortizm said:
puedo colocar este twrp en mi g570m sin memoria sd y con android 7.0?
Click to expand...
Click to collapse
sí puedes, usa odin para flashear la recuperación ,
ya probado

---

I have enable oem unlock. Odin starts flash the file, but in the end show "Only official released binaries are allowed to be flashed (RECOVERY)" and fails. Can someone help me please. I only want to get Root.

---

droopyar said:
Seems working PERFECT on SM-570M running Nougat 7.0 firmware.
I put OK the recovery , then use MESA to fix the red logo that only official binaries are allow to be flashed, and root it using Magisk
I have a problem related to remount /system as seems it give me an error. Any command to remount /system ok so it is writable? (on NOUGAT)
Click to expand...
Click to collapse
what's MESA?

---

lufflima said:
I have enable oem unlock. Odin starts flash the file, but in the end show "Only official released binaries are allowed to be flashed (RECOVERY)" and fails. Can someone help me please. I only want to get Root.
Click to expand...
Click to collapse
Can you attach a photo for your download mode ?

---

Am I bricking my Samsung Galaxy J5 Prime?
Hi, I followed the instructions to root my Galaxy J5 Prime, SM-G570M, Knox 2.8, Android 7.0, SE for Android 2.4.3, version G570MUBU2BRC2, kernel 3.18.14-12686191. I enabled oem unlock. Odin3 v3.12 starts flashing the file. However, it fails. Here is the log:
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> recovery.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The phone shows in red:
"Only official released binaries are allowed to be flashed (RECOVERY)" .
I Holded [Volume Down] + [Home] + [Power] to get out of Download mode. I also immediately swaped
to [Volume Up] when the screen blanked.
A white circle with a 37% in the middle appeared. It is very slowly growing the percentage (after 20 minutes it is now in 53%).
Am I bricking my Samsung Galaxy J5 Prime?
---------- Post added at 03:44 AM ---------- Previous post was at 02:53 AM ----------
o8oro said:
Hi, I followed the instructions to root my Galaxy J5 Prime, SM-G570M, Knox 2.8, Android 7.0, SE for Android 2.4.3, version G570MUBU2BRC2, kernel 3.18.14-12686191. I enabled oem unlock. Odin3 v3.12 starts flashing the file. However, it fails. Here is the log:
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> recovery.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The phone shows in red:
"Only official released binaries are allowed to be flashed (RECOVERY)" .
I Holded [Volume Down] + [Home] + [Power] to get out of Download mode. I also immediately swaped
to [Volume Up] when the screen blanked.
A white circle with a 37% in the middle appeared. It is very slowly growing the percentage (after 20 minutes it is now in 53%).
Am I bricking my Samsung Galaxy J5 Prime?
Click to expand...
Click to collapse
After I turn on my cel again, , and try the process again from step 6:
Odin3 fails again.
The same red message appears in my cel phone:
"Only official released binaries are allowed to be flashed (RECOVERY)".
---------- Post added at 03:58 AM ---------- Previous post was at 03:44 AM ----------
o8oro said:
Hi, I followed the instructions to root my Galaxy J5 Prime, SM-G570M, Knox 2.8, Android 7.0, SE for Android 2.4.3, version G570MUBU2BRC2, kernel 3.18.14-12686191. I enabled oem unlock. Odin3 v3.12 starts flashing the file. However, it fails. Here is the log:
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> recovery.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The phone shows in red:
"Only official released binaries are allowed to be flashed (RECOVERY)" .
I Holded [Volume Down] + [Home] + [Power] to get out of Download mode. I also immediately swaped
to [Volume Up] when the screen blanked.
A white circle with a 37% in the middle appeared. It is very slowly growing the percentage (after 20 minutes it is now in 53%).
Am I bricking my Samsung Galaxy J5 Prime?
---------- Post added at 03:44 AM ---------- Previous post was at 02:53 AM ----------
After I turn on my cel again, , and try the process again from step 6:
Odin3 fails again.
The same red message appears in my cel phone:
"Only official released binaries are allowed to be flashed (RECOVERY)".
Click to expand...
Click to collapse
The full message in my cel phone:
ODIN MODE
DOWNLOAD SPEED: FAST
PRODUCT NAME: SM-G570M
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
RMM STATE: Prenormal
FAP LOCK: OFF
Seucure Download: Enabled
WARRANTY VOID: 0 (0x0000)
AP SWREV: B:2 K:0 S:0
DID = 06640...
Only official released binaries are allowed to be flashed (RECOVERY)

---

Solution to "Only official released binaries are allowed to be flashed (RECOVERY)"
o8oro said:
Hi, I followed the instructions to root my Galaxy J5 Prime, SM-G570M, Knox 2.8, Android 7.0, SE for Android 2.4.3, version G570MUBU2BRC2, kernel 3.18.14-12686191. I enabled oem unlock. Odin3 v3.12 starts flashing the file. However, it fails. Here is the log:
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> recovery.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The phone shows in red:
"Only official released binaries are allowed to be flashed (RECOVERY)" .
I Holded [Volume Down] + [Home] + [Power] to get out of Download mode. I also immediately swaped
to [Volume Up] when the screen blanked.
A white circle with a 37% in the middle appeared. It is very slowly growing the percentage (after 20 minutes it is now in 53%).
Am I bricking my Samsung Galaxy J5 Prime?
---------- Post added at 03:44 AM ---------- Previous post was at 02:53 AM ----------
After I turn on my cel again, , and try the process again from step 6:
Odin3 fails again.
The same red message appears in my cel phone:
"Only official released binaries are allowed to be flashed (RECOVERY)".
---------- Post added at 03:58 AM ---------- Previous post was at 03:44 AM ----------
The full message in my cel phone:
ODIN MODE
DOWNLOAD SPEED: FAST
PRODUCT NAME: SM-G570M
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
RMM STATE: Prenormal
FAP LOCK: OFF
Seucure Download: Enabled
WARRANTY VOID: 0 (0x0000)
AP SWREV: B:2 K:0 S:0
DID = 06640...
Only official released binaries are allowed to be flashed (RECOVERY)
Click to expand...
Click to collapse
To solve this problem follow the instructions given in youtube: o0T-CR-KpfM
"How to fix missing OEM unlock [RMM Prenormal] on your Samsung Galaxy! Without waiting 7 days!"
(I could not provide the link because:
"To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!")