Samsung Galaxy J3 sm-j320zn

[mathius89]

Hello,

I can't find nothing for sm-j320zn version, I tried to install TWRP and I did it, but when I try to install the Supersu the mobile goes to a bootloop...

Help! Thank you so much!!

 

[mathius89]

Nobody?

 

[420blazedman]

Nobody?

Also trying to find a root for mine. The only thing I haven't tried is cf auto root

 

[raymondbernard]

Nobody?

I have an j320w8 samsung please help
Build
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
telephony.lteOnCdmaDevice=0
persist.eons.enabled=true
rild.libpath=/system/lib/libsec-ril.so
persist.security.ams.enforcing=3
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
ro.adb.secure=1
persist.sys.usb.config=mtp
ro.zygote=zygote32
dalvik.vm.image-dex2oat-Xms=64m
dalvik.vm.image-dex2oat-Xmx=64m
dalvik.vm.dex2oat-Xms=64m
dalvik.vm.dex2oat-Xmx=512m
ro.dalvik.vm.native.bridge=0
debug.atrace.tags.enableflags=0
#
# BOOTIMAGE_BUILD_PROPERTIES
#
ro.bootimage.build.date=Mon Jan 2 15:19:13 KST 2017
ro.bootimage.build.date.utc=1483337953
ro.bootimage.build.fingerprint=samsung/j3xltebmc/j3xltebmc:6.0.1/MMB29K/J320W8VLU2AQA1:user/test-keys

Sent from my Samsung SM-J320W8 using XDA Labs

 

[hartej singh]

j320zn

please help how to rootj320zn me try all root tools :

 

[ashyx]

Hello,

I can't find nothing for sm-j320zn version, I tried to install TWRP and I did it, but when I try to install the Supersu the mobile goes to a bootloop...

Help! Thank you so much!!

You need V2.79 sr3

 

[jdkeys]

Samsung Galaxy j320zn

You need V2.79 sr3

Can you explain what your answer means is there a way to root the phone thats successful?

 

[Wulfie217]

Can you explain what your answer means is there a way to root the phone thats successful?

Ashyx means you need SuperSU version 2.79 sr3.

---------- Post added at 10:50 AM ---------- Previous post was at 10:49 AM ----------

Ashyx means you need SuperSU version 2.79 sr3.

If I remember rightly that can be found here on XDA somewhere.

 

[Winston Churchill]

Working root?

What did any users here use to root the J3 SM-J320ZN? I can't get it to root and I'm spitting chips.

 

[Winston Churchill]

Hello,

I can't find nothing for sm-j320zn version, I tried to install TWRP and I did it, but when I try to install the Supersu the mobile goes to a bootloop...

Help! Thank you so much!!

mathius, which TWRP did you successfully install for SM-J320ZN? I'm so confused. I've looked at sites with tables for different models, and this model isn't available. I've sort of looked here, and done a Google search and it points me to 3.02 for SM-J320H. Is this the one you used?

I've got the SuperSU v.2.79 sr3 that was recommended ready. Now I don't know what TWRP to try lol.

I'm so upset. This is my first new phone in 6 years (I've been stuck on Gingerbread with a bizarre/rare Australian model phone that could not get custom ROMS). I'm disabled, it took me so long to get this phone and I find out I can't root it? Useless to me unless I can get root.

Also anyone, would the fact the phone is locked make things more difficult? Obviously people are having trouble rooting this model regardless, but will this interfere further, esp. with things like TWRP?

 

[ashyx]

mathius, which TWRP did you successfully install for SM-J320ZN? I'm so confused. I've looked at sites with tables for different models, and this model isn't available. I've sort of looked here, and done a Google search and it points me to 3.02 for SM-J320H. Is this the one you used?

I've got the SuperSU v.2.79 sr3 that was recommended ready. Now I don't know what TWRP to try lol.

I'm so upset. This is my first new phone in 6 years (I've been stuck on Gingerbread with a bizarre/rare Australian model phone that could not get custom ROMS). I'm disabled, it took me so long to get this phone and I find out I can't root it? Useless to me unless I can get root.

Also anyone, would the fact the phone is locked make things more difficult? Obviously people are having trouble rooting this model regardless, but will this interfere further, esp. with things like TWRP?

J320fn has the same specs so there's a good chance it will work for j320zn

 

[Winston Churchill]

J320fn has the same specs so there's a good chance it will work for j320zn

Thanks for the response.

I've tried flashing TWRP for the J320FN model from a tutorial I found here on xda. I've tried a couple of times. Odin says it's flashed OK but it hasn't worked in reality.

Sigh. A bit devastated.

 

[ashyx]

Thanks for the response.

I've tried flashing TWRP for the J320FN model from a tutorial I found here on xda. I've tried a couple of times. Odin says it's flashed OK but it hasn't worked in reality.

Sigh. A bit devastated.

Very minimal on details.
'Hasn't worked' neither helps you or anyone else.
Explain the details of 'hasn't worked' if you require assistance.

 

[Winston Churchill]

Very minimal on details.
'Hasn't worked' neither helps you or anyone else.
Explain the details of 'hasn't worked' if you require assistance.

Sorry. What I meant was nothing appears to be different at all. When I try to flash in Odin, it hits "Reset" section quickly, my phone reboots itself. I wait awhile and eventually Odin gives me the (1) success / (0) fail type message and I get the green "Pass" to indicate that it was successfully flashed. But, there is no difference to my system at all, and when I boot to recovery, it's still stock recovery if that makes sense.

Something to note: my phone is currently locked to my provider (so I can only use a Telstra SIM). Would this impact being able to flash TWRP? Otherwise, it's just not the right one to use.....ZN isn't compatible with FN maybe.

It's been many years since I've flashed or rooted (ordinarily I root tablets with KingoRoot). I remember back in the bad old days that my old phone had the processor or drivers or chip or something that meant I could not run custom ROMS because it was Qualcomm and all the other phones were the other type that released the drivers publicly. Started with B I think (this other chipset or whatever. Sorry I'm not a full on geek to know heh). Anyway, I was wondering if I'm in the same boat again with my Australian phone because it's Qualcomm (or Quadcomm..... something like that)....... hence all the hacks and mods that you guys make won't work.

Does/can installing SuperSU through stock recovery grant root? I tried doing that anyway - executing v2.79 sr3 that you recommended as well as v2.74, which was the package I found in the tutorial for installing TWRP and rooting for J320FN. I got failed messages.

 

[Wulfie217]

Sorry. What I meant was nothing appears to be different at all. When I try to flash in Odin, it hits "Reset" section quickly, my phone reboots itself. I wait awhile and eventually Odin gives me the (1) success / (0) fail type message and I get the green "Pass" to indicate that it was successfully flashed. But, there is no difference to my system at all, and when I boot to recovery, it's still stock recovery if that makes sense.

Something to note: my phone is currently locked to my provider (so I can only use a Telstra SIM). Would this impact being able to flash TWRP? Otherwise, it's just not the right one to use.....ZN isn't compatible with FN maybe.

It's been many years since I've flashed or rooted (ordinarily I root tablets with KingoRoot). I remember back in the bad old days that my old phone had the processor or drivers or chip or something that meant I could not run custom ROMS because it was Qualcomm and all the other phones were the other type that released the drivers publicly. Started with B I think (this other chipset or whatever. Sorry I'm not a full on geek to know heh). Anyway, I was wondering if I'm in the same boat again with my Australian phone because it's Qualcomm (or Quadcomm..... something like that)....... hence all the hacks and mods that you guys make won't work.

Does/can installing SuperSU through stock recovery grant root? I tried doing that anyway - executing v2.79 sr3 that you recommended as well as v2.74, which was the package I found in the tutorial for installing TWRP and rooting for J320FN. I got failed messages.

If I'm reading that correctly it seems like in Odin you have auto reboot turned on. You need to change that under options, the only thing on in Odin should be F.reset time. Then use (iirc) both volume buttons, gone button and power to restart the phone when it's finished.
For some reason having auto reboot off is important.

 

[ashyx]

Sorry. What I meant was nothing appears to be different at all. When I try to flash in Odin, it hits "Reset" section quickly, my phone reboots itself. I wait awhile and eventually Odin gives me the (1) success / (0) fail type message and I get the green "Pass" to indicate that it was successfully flashed. But, there is no difference to my system at all, and when I boot to recovery, it's still stock recovery if that makes sense.

Something to note: my phone is currently locked to my provider (so I can only use a Telstra SIM). Would this impact being able to flash TWRP? Otherwise, it's just not the right one to use.....ZN isn't compatible with FN maybe.

It's been many years since I've flashed or rooted (ordinarily I root tablets with KingoRoot). I remember back in the bad old days that my old phone had the processor or drivers or chip or something that meant I could not run custom ROMS because it was Qualcomm and all the other phones were the other type that released the drivers publicly. Started with B I think (this other chipset or whatever. Sorry I'm not a full on geek to know heh). Anyway, I was wondering if I'm in the same boat again with my Australian phone because it's Qualcomm (or Quadcomm..... something like that)....... hence all the hacks and mods that you guys make won't work.

Does/can installing SuperSU through stock recovery grant root? I tried doing that anyway - executing v2.79 sr3 that you recommended as well as v2.74, which was the package I found in the tutorial for installing TWRP and rooting for J320FN. I got failed messages.

As said above you need to disable auto reboot. It's important to manually boot into recovery immediately after flashing twrp or it will be replaced by stock recovery at first boot.

 

[Winston Churchill]

As said above you need to disable auto reboot. It's important to manually boot into recovery immediately after flashing twrp or it will be replaced by stock recovery at first boot.

Thanks guys.

The problem I'm having is - is there a proper way to boot into recovery from download mode once the flash has finished? I've tried button combos and looked about a bit.

The only thing I've got to work is to exit odin, then take the battery out and boot into recovery using vol up, home and power once I put the battery back in.

When I do that, the Samsung splash screen comes up and in the top left corner it's still saying it's in Odin mode (then it gives my model number and some other details - I can redo if you want to know all the listed details). It appears to just stay stuck at this spalsh screen. I waited about 5 minutes (trying two different times) and it just stays on that splash screen and wont boot to phone or recovery.

Sorry, I'm really hopeless Thanks for your patience.

P.S. So once I take battery out again and restart the phone works fine again because it's obviously reverted to stock recovery again like you said it would if I didn't manually boot to recovery. So it's OK, I've not bricked my phone or anything. I'm just wondering if there's a method I need to do to get it to work other than battery out.

---------- Post added at 05:30 PM ---------- Previous post was at 04:40 PM ----------

I just want to say that I got root for the SM-J320ZN using CF-Auto-Root.

Follow this link to download the package CF-Auto-Root-j3lteusc-j3lteusc-smj320r4.zip:

https://download.chainfire.eu/986/C...3lteusc-j3lteusc-smj320r4.zip?retrieve_file=1

The package came bundled with a version of Odin and some other files, so I extracted them all to a directory, ran Odin, and flashed the .md5 through the AP button. It takes a little while and as it says while it is loading, your phone might reboot several times in the process before it finishes so DON'T interfere with it.

YAY.

Any help on the TWRP issue I'm still having would be greatly appreciated still

 

[hartej singh]

Also trying to find a root for mine. The only thing I haven't tried is cf auto root

root j320zn cf auto root done with odin

---------- Post added at 10:35 AM ---------- Previous post was at 10:19 AM ----------

j320zn root done with cfauto root using odin:

 

[Winston Churchill]

I've finally gotten a TWRP version to work for the J320ZN with no issues. I've had a week of tinkering so I thought I'd go back to my phone and try on that again too after previously giving up.

To repeat what I've already written, the suggested TWRP version for J320FN DOES NOT seem to work. When manually booting to recovery after flashing, you get stuck on the default Samsung boot screen, but with Download Mode text still stuck in the corner (to finally answer your question ashyx)

I got TWRP J3lte to work. To download: https://dl.twrp.me/j3lte/

I've had a BILLION problems doing this... because like the OP, I couldn't get root by using SuperSU.zip through TWRP.... it would cause a bootloop. I tried the suggested version of SuperSU posted by ashyx earlier in the thread... plus the latest with no luck.

My "solution" (LOL) was to flash CF-Auto-Root... without realizing it wiped to stock recovery! So here's me all happy thinking I've got TWRP and root...and gotten rid of the bootloop until I set up my phone and went to recovery to make my first full backup... and saw that not only was I getting stock (DUH lolol), but a dm-verity error.

This is something I know nothing about, other than there is a patch for it. So this time, I decided to try the dm-verity patch and REAL SUCCESS! Root, TWRP recovery (that's still there after multiple checks).

So... if you've tried TWRP j3lte and the latest SuperSU.zip and instead of working, you got bootloop you could try the dm-verity patch in your procedure (also to get rid of the bootloops I just flashed CF-Auto-Root again... but then you'll have to start again with TWRP etc).

My successful procedure was:

1) Install TWRP j3lte as linked above (lastest version twrp-3.2.1-0-j3lte.img)

2) Install SuperSU v.2.82 SR5 through TWRP....https://download.chainfire.eu/1220/SuperSU/SR5-SuperSU-v2.82-SR5-20171001224502.zip

3) THEN BEFORE REBOOT, install Dm-verity and Forced Encryption Disabler patch (no-verity-opt-encrypt-6.0.zip) from https://androidfilebox.com/miscellaneous/dm-verity-and-forced-encryption-disabler/ using the same "Install" button/method in TWRP.

Then you can reboot and THIS TIME it worked... I've rebooted many times, recovery still there, got root.... Link2SD working fine and I've made several backups to test.

A comedy of errors.....but I FINALLY fixed it just through tinkering. Hope this helps.

 

[Winston Churchill]

Though this thread is probably dead, I did have someone PM me a few weeks ago seeing if I'd found a solution (which is why I've been tinkering). So.....

In future I'd appreciate anyone who follows this updating me about what they had to do - did you get it to work with just TWRP j3lte and the newest SuperSU.zip? Or did you need the patch for Dm-verity/encrypt? It will help me learn what's really going on and why I have to do the things I do. I'm still a novice to things beyond simple rooting.

FOR XPOSED: please note if you're on stock ROM for this device, the Official Xposed Framework WILL NOT WORK. You will land in bootloop. Touchwiz is not supported. You need to install an Unofficial version by wanam. Our chipset is arm so make sure you download the correct version for 5.1.1 arm chipset (not arm64 or x86):
https://www.tricksfolks.com/install-xposed-framework-samsung-lollipop-marshmallow/
Make sure you download the uninstaller.zip for 5.1.1 and have it on your external SD card as well just in case you get into bootloop... then you can go to recovery and just uninstall the framework. This appears to be a custom uninstaller, so use that and NOT the official uninstaller zip for Xposed. It's right at the end of the tutorial (DL link). I had no issues however. Wanam's framework installed fine.

ALSO, the latest (at time of writing) Xposed Installer (apk) v.3.2 doesn't like the unofficial framework - it won't detect it properly plus there are some other annoyances, so I rolled back to v.3.1.5. Older versions shouldn't be too hard to find, but there is a link to an older apk version in the tutorial I just linked with the wanam files.

Finally, If anyone has recommendations for Custom ROMS that work on this model in future, also please let me know here. I'm a bit wary of trying after the trouble I've had with Xposed.