Samsung Galaxy J3 SM-S320VL need this rooted

[c0b4lt]

has this been tried yet with build number MMB29M.S320VLUDU1APG2 ? also is this going to cause a factory data reset if i take the plunge and try it myself on that version?

Edit:

ok actually tried it anyway. got the eng boot img flashed and settings > about showed SE Linux as permissive. After running Kingroot several times over the course of about an hour however it is not ever able to obtain root. So now I'm kind of stuck with a new VOLTE icon i didnt have before i flashed the eng boot img and the phone forgetting my wifi password every reboot. I also keep getting notifications and/or popups about unauothorized actions detected. I assume that's Knox having a hissy fit.

 

[stanfox]

Why can't you enable OEM unlock? Remove any pin/password from the device first.

I had no problem rooting previous phones or tablets. I never use a pin so thats not the problem. ( only use phone for calls and text) OS on my phone is 5.1.1. When I move the button to unlock, the option comes up to either cancel or enable, press enable and the button just slides back to off. When I look at the system files with Total Commander, there are lots of really weird folders that I can't access and they are all in Chinese in any case so I wouldn't know whats going on

 

[ashyx]

I had no problem rooting previous phones or tablets. I never use a pin so thats not the problem. ( only use phone for calls and text) OS on my phone is 5.1.1. When I move the button to unlock, the option comes up to either cancel or enable, press enable and the button just slides back to off. When I look at the system files with Total Commander, there are lots of really weird folders that I can't access and they are all in Chinese in any case so I wouldn't know whats going on

You could try it without OEM UNLOCK. There's a chance the boot image will flash fine. If not I suggest you update your device to the MM firmware provided.

 

[stanfox]

You could try it without OEM UNLOCK. There's a chance the boot image will flash fine. If not I suggest you update your device to the MM firmware provided.

Yeah, thanks for the reply. Honestly, I have tried every program that I could find. Some come up within seconds and say that "this phone cannot be rooted" I'm sure it probably can but I'm a hardware person and not software so I've got a bit out of my depth. I have tried to load Ver 6. but it won't allow me to do that. I thought if I loaded that it would get rid of the samsung version of 5.1.1. I'm resigned to writing off this phone to experience and never buying one again, at least not in Honkers. What is really annoying is the full page adds that cover the whole screen but some of them are positioned off to one side so the option to just close the add screen is not available and the only way to get rid of it is to reboot the phone.

 

[ashyx]

Yeah, thanks for the reply. Honestly, I have tried every program that I could find. Some come up within seconds and say that "this phone cannot be rooted" I'm sure it probably can but I'm a hardware person and not software so I've got a bit out of my depth. I have tried to load Ver 6. but it won't allow me to do that. I thought if I loaded that it would get rid of the samsung version of 5.1.1. I'm resigned to writing off this phone to experience and never buying one again, at least not in Honkers. What is really annoying is the full page adds that cover the whole screen but some of them are positioned off to one side so the option to just close the add screen is not available and the only way to get rid of it is to reboot the phone.

I'm not sure what you mean?
Root has already been achieved, but you need to flash the eng boot first. Without that it won't work.

 

[Orangejuice484]

Does anyone have the source code of the exploit used?

 

[serfassmike]

so what is the official status on this root method being used on the s320vl with apg2 firmware? Has everything been confirmed safe as not to brick the device considering custom recovery is not an option to get out of either a soft or hard brick.

 

[ashyx]

so what is the official status on this root method being used on the s320vl with apg2 firmware? Has everything been confirmed safe as not to brick the device considering custom recovery is not an option to get out of either a soft or hard brick.

Irrespective of the status the stock firmware is in the thread.

 

[stanfox]

I'm not sure what you mean?
Root has already been achieved, but you need to flash the eng boot first. Without that it won't work.

Root hasn't been achieved. Is there a way to remove Knox from the phone. I think if I can remove that then I may have some success. I can't disable it or uninstall it. I've been using CCleaner to try but without success.

 

[ashyx]

I give up with you guys.

 

[parrotgeek1]

---

 

[serfassmike]

im not brave enough to try this but how about disabling all knox files with package disabler pro, then trying several different rooting apps to see if any root the phone, and if it does, then just enable all knox files before rebooting or turning off the device to minimize the chance of a brick then if it would lose root on the reboot, then just disable knox again and run the app to re root it and just always remember to disable knox before shutting down or rebooting. just an idea

 

[johntheantiqueguy]

Hello all. First off i am new to any of this and ive only rooted three phones. However, I own one of these sm-s320vl's (straight talk) and i want to add something in hopes it might help. if its worthless i appologize. i downloaded an app called "droid secret codes" from google play. one of the codes was *#*#759#*#* it took me to an "RLZ debug UI" where there was another set of OEM options seperate from the developer options one. There was also a code called *#*#STEALTHMODE#*#* that had a bunch of network options. considering i can get in a few cheesy hidden menus but cant even find an MSL or get past a blank service mode menu on this phone...i hope that info helps.

 

[stanfox]

im not brave enough to try this but how about disabling all knox files with package disabler pro, then trying several different rooting apps to see if any root the phone, and if it does, then just enable all knox files before rebooting or turning off the device to minimize the chance of a brick then if it would lose root on the reboot, then just disable knox again and run the app to re root it and just always remember to disable knox before shutting down or rebooting. just an idea

Been off line for a while. Thanks for the tip. I'll give this ago. Not worried if it screws up the phone, I have screens that come up that cover everything and the only way to get rid of them is to reboot. One way to stop it is to leave wifi turned off but that defeats the purpose of a smart phone.

---------- Post added at 02:09 AM ---------- Previous post was at 02:06 AM ----------

Hello all. First off i am new to any of this and ive only rooted three phones. However, I own one of these sm-s320vl's (straight talk) and i want to add something in hopes it might help. if its worthless i appologize. i downloaded an app called "droid secret codes" from google play. one of the codes was *#*#759#*#* it took me to an "RLZ debug UI" where there was another set of OEM options seperate from the developer options one. There was also a code called *#*#STEALTHMODE#*#* that had a bunch of network options. considering i can get in a few cheesy hidden menus but cant even find an MSL or get past a blank service mode menu on this phone...i hope that info helps.

Now that is interesting. Going to try this on an old phone first, one that rooted with out a problem, just to see what it's all about.

 

[Theddrmasta]

Any progress made here? I can't seem to get past the rebooting thing. It always reboots after I get rooted with kingroot and takes it away.

 

[Curtis1973]

while you have temp root delete knox apps with root explorer. root should then stick upon reboot. worked back on s5 before it had full support and kingroot could only get temp root. after deleting knox apps,root stuck. might work here

 

[Curtis1973]

Two models that may serve as proper kernels...if these in fact have kernel sources in zips. they are not specific to sm-j327v"l" or sm-j320"vl" but may not have to be. Worth looking i to.

Both are 183 mb each.

https://www.mediafire.com/file/a5d32sirbba8u66/SM-J327V_NA_NN_Opensource.zip

https://www.mediafire.com/file/2nlu4er9v15xbrb/SM-J327VPP_NA_NN_Opensource.zip

 

[Curtis1973]

This method is using boot img for the J3 SM-J320M not the SM-J320VL. I am surprised this didnt cause all sorts of device issues. Or even soft brick. Who on the Luna Pro actually used this?

Here we go. This is for S320VLUDU2API3 firmware, but probably works on any revision 2 firmware.


KNOX should remain 0x0



Instructions

1. Enable OEM UNLOCK
In Settings>About>Software info tap the build number 7 times to enable developer options. Once you've enabled developer options, developer options will appear in settings just above the About device option. Open developer options, the 4th or 5th option should be “OEM Unlock”. Turn on.

2. Flash the eng boot image.
This is a special boot image normally used by engineers, it allows selinux to be booted in permissive mode with relaxed root restrictions.
Do not replace this image with the stock image after rooting your device or you will possibly soft brick your device.
(See below for how to recover)
ENG_BOOT_S320VL_API3

3. Install boot image:
Download Odin v3.11.1
Reboot Phone in Download Mode (press and hold Home + Power + Volume Down buttons)
Connect phone and wait until you get a blue sign in Odin
Add the ENG_BOOT_S320VL_API3.tar to AP / PDA
Make sure re-partition is NOT ticked
Click the start button, sit back and wait few minutes
Reboot
Check in Settings>About>Software, your device should be in Selinux permissive mode.

4. Install and run Kingroot:
https://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
Make sure you have an internet connection.
You may need to run Kingroot several times to gain successful root.

5. Install and run SuperSU me to remove Kingroot and convert to SuperSU (not required) :
https://play.google.com/store/apps/...ore&pcampaignid=APPU_1_uzPDVbGyFcGNyATHrqmoCA

6. Wifi fix:

modify the line below in /system/build.prop:

ro.securestorage.support=true to false


Recovering from a soft brick:
Flash the stock firmware provided below wirh ODIN
https://firmwarefile.com/samsung-sm-s320vl

Good luck I hope it works for you.

.

 

[ashyx]

This method is using boot img for the J3 SM-J320M not the SM-J320VL. I am surprised this didnt cause all sorts of device issues. Or even soft brick. Who on the Luna Pro actually used this?

How did you arrive at that conclusion?
It is what it says it is.

 

[Curtis1973]

How did you arrive at that conclusion?
It is what it says it is.

the androidfilehost link you provide for boot img says sm-j320m at top of page

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

download
S320VLUDU2API3_eng_boot.tar

for the Samsung Galaxy J3(J320M), by ashyt16

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

either way it wont flash on my j3 luna via odin. fails with secure check error.