Database Users

Samsung Galaxy J3 sm-j320zn

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!!

Nobody?

mathius89 said:
Nobody?
Click to expand...
Click to collapse
Also trying to find a root for mine. The only thing I haven't tried is cf auto root

mathius89 said:
Nobody?
Click to expand...
Click to collapse
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

j320zn
please help how to rootj320zn me try all root tools :

mathius89 said:
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!!
Click to expand...
Click to collapse
You need V2.79 sr3

Samsung Galaxy j320zn
ashyx said:
You need V2.79 sr3
Click to expand...
Click to collapse
Can you explain what your answer means is there a way to root the phone thats successful?

jdkeys said:
Can you explain what your answer means is there a way to root the phone thats successful?
Click to expand...
Click to collapse
Ashyx means you need SuperSU version 2.79 sr3.
---------- Post added at 10:50 AM ---------- Previous post was at 10:49 AM ----------
Wulfie217 said:
Ashyx means you need SuperSU version 2.79 sr3.
Click to expand...
Click to collapse
If I remember rightly that can be found here on XDA somewhere.

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.

mathius89 said:
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!!
Click to expand...
Click to collapse
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?

Winston Churchill said:
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?
Click to expand...
Click to collapse
J320fn has the same specs so there's a good chance it will work for j320zn

ashyx said:
J320fn has the same specs so there's a good chance it will work for j320zn
Click to expand...
Click to collapse
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.

Winston Churchill said:
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.
Click to expand...
Click to collapse
Very minimal on details.
'Hasn't worked' neither helps you or anyone else.
Explain the details of 'hasn't worked' if you require assistance.

ashyx said:
Very minimal on details.
'Hasn't worked' neither helps you or anyone else.
Explain the details of 'hasn't worked' if you require assistance.
Click to expand...
Click to collapse
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.

Winston Churchill said:
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.
Click to expand...
Click to collapse
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.

Winston Churchill said:
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.
Click to expand...
Click to collapse
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.

ashyx said:
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.
Click to expand...
Click to collapse
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

420blazedman said:
Also trying to find a root for mine. The only thing I haven't tried is cf auto root
Click to expand...
Click to collapse
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:

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.

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.

Rooting SM-S920L

Tracfone version
I'm having no luck with Kingroot. It says no root available for device.
According to 'one-click-root' website, the device has no way of rooting it.
Is there any updated information?
.
device specifics:
model: SM-S920LZAATFN
android: 5.0.2
build: LRX22G.S920LUDU1APK2
hardware version: S920L.03
.
[edit: was hoping to change the title to reflect that this post is about the tracfone version]

TWRP recovery method?
TWRP recovery method?
I've read that a phone may possibly be able to be rooted by using odin to download a TWRP recovery, then booting into that new recovery using hardware keys, instead of rebooting normally. And this results in a rooted phone?
I think I have seen a TWRP that may work with this phone. Any help is appreciated. I'd like to be able to update this thread to include a step by step approach to this and other versions of the same model 920.
I'll continue to post updates as I discover more information.

DIY time : crash course in brain surgery
Ok, so I've read a bit of stuff in the forums on the SM-S920L, mostly about the StraightTalk variant, which apparently uses the same system rom, though I'm not so sure.
At any rate, rather than just throw carp at the phone and hope it sticks, I'm going to teach myself how to do it all myself, a-z, 1,2,3... etc., starting with making stock images of the various components, for recovery purposes. Perhaps the phone can be used as a TracFone again someday, though I have no desire to do so, having already bought another for cheaper that even works better, though not as fancy, just newer.
So, I'll leave it here for now and just update the primary with new information as I discover it, starting with the extraction of the stock images, hopefully without goofing up the phone, lol.
This is an unpopular phone, at least for hackers. But it will be a good tool for expanding my knowledge.
Any help appreciated, such as, 'Is this even necessary? There are files here here and here that will do it all'.
(lol, nope... so far I've discovered there is no root option, kingroot no work, etc. There seems to be no posts with information specifically regarding the TracFone 'variant' of this model. It suggests that i can use the StraightTalk files for it, which may work, but there are many questionable unanswered problems.)

friimynd said:
Ok, so I've read a bit of stuff in the forums on the SM-S920L, mostly about the StraightTalk variant, which apparently uses the same system rom, though I'm not so sure.
At any rate, rather than just throw carp at the phone and hope it sticks, I'm going to teach myself how to do it all myself, a-z, 1,2,3... etc., starting with making stock images of the various components, for recovery purposes. Perhaps the phone can be used as a TracFone again someday, though I have no desire to do so, having already bought another for cheaper that even works better, though not as fancy, just newer.
So, I'll leave it here for now and just update the primary with new information as I discover it, starting with the extraction of the stock images, hopefully without goofing up the phone, lol.
This is an unpopular phone, at least for hackers. But it will be a good tool for expanding my knowledge.
Any help appreciated, such as, 'Is this even necessary? There are files here here and here that will do it all'.
(lol, nope... so far I've discovered there is no root option, kingroot no work, etc. There seems to be no posts with information specifically regarding the TracFone 'variant' of this model. It suggests that i can use the StraightTalk files for it, which may work, but there are many questionable unanswered problems.)
Click to expand...
Click to collapse
Definitely don't use kingroot.
Do you have a laptop or pc? If so I can help you out. I have the same phone. Mine is straight talk, but it's sm-s920l a tracefone just through straight talk.

c3p0u812 said:
Definitely don't use kingroot.
Do you have a laptop or pc? If so I can help you out. I have the same phone. Mine is straight talk, but it's sm-s920l a tracefone just through straight talk.
Click to expand...
Click to collapse
Ya I got the straight talk, I have been using king root but I totally bricked and wiped my phone on purpose because I wanted to start fresh and let it update. Having a problem though I used twrp and nuked all my ****, or so I thought. I'm trying to OTA update I'm currently on 5.0.2 and it's saying I have a system update and even after I checked everything to be deleted it still says error and one of my files is modified or some**** like that. I think it's like admin.prop so **** it. I do however want to go systemless root. What do you suggest is the best root and rom for our device?
To answer op question yes your phone is the same as ours. Mine even shows tracphone on boot.

Inuyashian said:
Ya I got the straight talk, I have been using king root but I totally bricked and wiped my phone on purpose because I wanted to start fresh and let it update. Having a problem though I used twrp and nuked all my ****, or so I thought. I'm trying to OTA update I'm currently on 5.0.2 and it's saying I have a system update and even after I checked everything to be deleted it still says error and one of my files is modified or some**** like that. I think it's like admin.prop so **** it. I do however want to go systemless root. What do you suggest is the best root and rom for our device?
To answer op question yes your phone is the same as ours. Mine even shows tracphone on boot.
Click to expand...
Click to collapse
Well for our phone there is only one custom ROM and it's LineageOS 13.0 https://forum.xda-developers.com/grand-prime/development/unofficial-cyanogenmod-13-0-galaxy-t3491494 It's android 6.0 and it can be rooted too. It's not being updated anymore for our device as far as I know. There is Lineage 14.* but not for our variant.
For systemless root you'll want to go with Magisk. https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 I had Lineage, and don't get me wrong it's worth checking out, but I downgraded back to stock and went with Magisk. You can even get Xposed throughMagisk.
If I was you, I would flash back to stock. You can go to this thread https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 and download the first two, Stock Boot and Stock Recovery. Make sure to unzip them because you need the md5 files they extract. I'd wipe everything again and then get into download mode. On your PC fire up Odin, I'm using version 3.10 http://odindownload.com/download/clean/Odin_3.10.0.zip Click BL use the stick boot md5 and then under ap use the stock recovery md5. When it reboots and you set it up do not turn reactivation lock on.
If you don't already have Magisk on your sd card get it on there and install through twrp. It will ask if you want to root. Might make a back up after. I always make backups and then transfer from sd to my pc. I can restore to like 6 different versions of my phone right now lol I'm no expert, I haven't been messing around with all this for long so I hope that all makes sense. :fingers-crossed:

c3p0u812 said:
Well for our phone there is only one custom ROM and it's LineageOS 13.0 https://forum.xda-developers.com/grand-prime/development/unofficial-cyanogenmod-13-0-galaxy-t3491494 It's android 6.0 and it can be rooted too. It's not being updated anymore for our device as far as I know. There is Lineage 14.* but not for our variant.
For systemless root you'll want to go with Magisk. https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 I had Lineage, and don't get me wrong it's worth checking out, but I downgraded back to stock and went with Magisk. You can even get Xposed throughMagisk.
If I was you, I would flash back to stock. You can go to this thread https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 and download the first two, Stock Boot and Stock Recovery. Make sure to unzip them because you need the md5 files they extract. I'd wipe everything again and then get into download mode. On your PC fire up Odin, I'm using version 3.10 http://odindownload.com/download/clean/Odin_3.10.0.zip Click BL use the stick boot md5 and then under ap use the stock recovery md5. When it reboots and you set it up do not turn reactivation lock on.
If you don't already have Magisk on your sd card get it on there and install through twrp. It will ask if you want to root. Might make a back up after. I always make backups and then transfer from sd to my pc. I can restore to like 6 different versions of my phone right now lol I'm no expert, I haven't been messing around with all this for long so I hope that all makes sense. :fingers-crossed:
Click to expand...
Click to collapse
Haha ya it does I just wish they didn't treat our phone like it has Ebola or some****. All kinds of **** for the other ones. I agree on the magisk because I really want to try that out. Alright thanks for all the helpful links I come to this site to find **** for ours and I end up looking at a bunch of cool stuff I can't have.
I'm waiting on the pixel 2 XL before I upgrade. We just missing out on too much stuff. I think magisk will keep me busy in the meantime though. Thanks again man I'm Soo add once I get here on all the stuff then I wonder well will this work or this work and by then just like awwww **** it.

Inuyashian said:
Haha ya it does I just wish they didn't treat our phone like it has Ebola or some****. All kinds of **** for the other ones. I agree on the magisk because I really want to try that out. Alright thanks for all the helpful links I come to this site to find **** for ours and I end up looking at a bunch of cool stuff I can't have.
I'm waiting on the pixel 2 XL before I upgrade. We just missing out on too much stuff. I think magisk will keep me busy in the meantime though. Thanks again man I'm Soo add once I get here on all the stuff then I wonder well will this work or this work and by then just like awwww **** it.
Click to expand...
Click to collapse
Hey, I thought I'd let you know LineageOS 14.1 is available to us now. I can't find a specific thread on it, but you can download it from http://grandprime.ddns.net/jenkins/job/LOS_Builds/# Flash it with twrp. You will want to flash that and then flash open gapps [ARM - 7.1] and then whichever from here http://opengapps.org/ I did all that first, set it up rebooted and then installed Magisk.
It has Substratum pre-installed and it let's you theme it nicely. There is only an unofficial xposed version so far.
Anywho, thought I'd throw that out there.

thanks for the replies, gives me inspiration to keep on trying; the phone is pretty ho-hum with default stuff and the general blah blah of social media, etc.;
thanks for the tips, feel free to post more details as they come in

My Turn
I'm about to try and put 14.1 and Magisk on mine. Wish me luck!

downloading twrp recovery and rooting
in google search up twrp click on the first link then click on devices on the top right corner then search up your phone download the twrp.img.tar file
power off your phone and press volume down + home button + power button to boot into download mode
in odin select AP then select the twrp.img.tar you downloaded then press start
your phone will reboot then download the SuperSU zip file
then go to settings then go to find my mobile you have to get a samsung account then you will see reactivation lock option turn that off
then power off your phone then press volume up + home button + power button to reboot into twrp recovery
once booted tap the install option then select where you downloaded the supersu zip file swipe to flash it once done flashing you will see the reboot system option to reboot your phone
then your phone should be rooted!

Is there an up to date guide for Rooting A2017G B04?

I am looking unlock and root my European Axon 7 running Android 7.1, and all of the guides seem to be for The US version and for Android marshmallow, do I need to revert my phone to an older version (if so how would I go around doing so?). Is there any up to date guides for rooting my version of the phone?

King Norman said:
I am looking unlock and root my European Axon 7 running Android 7.1, and all of the guides seem to be for The US version and for Android marshmallow, do I need to revert my phone to an older version (if so how would I go around doing so?). Is there any up to date guides for rooting my version of the phone?
Click to expand...
Click to collapse
https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
I used this guide 2 weeks ago to unlock my wife's german axon 7, her phone was on 7.1 stock too, but no issue, you don't have to be on marshmallow. Only advice I can give you is to read the guide 2 times or more and take your time.
Btw after you done everything use the b05 modem, my wife has no call issues with this version. I flashed the dark rom to her phone, works nearly perfect.

King Norman said:
I am looking unlock and root my European Axon 7 running Android 7.1, and all of the guides seem to be for The US version and for Android marshmallow, do I need to revert my phone to an older version (if so how would I go around doing so?). Is there any up to date guides for rooting my version of the phone?
Click to expand...
Click to collapse
coremania said:
https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
I used this guide 2 weeks ago to unlock my wife's german axon 7, her phone was on 7.1 stock too, but no issue, you don't have to be on marshmallow. Only advice I can give you is to read the guide 2 times or more and take your time.
Btw after you done everything use the b05 modem, my wife has no call issues with this version. I flashed the dark rom to her phone, works nearly perfect.
Click to expand...
Click to collapse
Why though? I also used that one, but you should try axon7toolkit. It seemingly does everything automatically and with an ok CMD interface

Choose an username... said:
Why though? I also used that one, but you should try axon7toolkit. It seemingly does everything automatically and with an ok CMD interface
Click to expand...
Click to collapse
Yes that's a nice option too, but reading, understanding and knowing what you're doing always works. I'm not a fan of Kit's.
personal choice I think. But you're right.

coremania said:
Yes that's a nice option too, but reading, understanding and knowing what you're doing always works. I'm not a fan of Kit's.
personal choice I think. But you're right.
Click to expand...
Click to collapse
It seems like very few people actually use the kit. Kinda defeats the purpose.
But yeah, that guide was how I learnt how to install TWRP via axon7tool whenever I needed it.

coremania said:
https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
I used this guide 2 weeks ago to unlock my wife's german axon 7, her phone was on 7.1 stock too, but no issue, you don't have to be on marshmallow. Only advice I can give you is to read the guide 2 times or more and take your time.
Btw after you done everything use the b05 modem, my wife has no call issues with this version. I flashed the dark rom to her phone, works nearly perfect.
Click to expand...
Click to collapse
Thanks for the help! Unfortunately I must have done something wrong and I think I've soft bricked my phone! :'(

King Norman said:
Thanks for the help! Unfortunately I must have done something wrong and I think I've soft bricked my phone! :'(
Click to expand...
Click to collapse
Toolkit or step by step with the guide ? just start from scratch again, or try with the kit.

coremania said:
Toolkit or step by step with the guide ? just start from scratch again, or try with the kit.
Click to expand...
Click to collapse
Step by Step, I managed to unlock it and flash the bootstack, but I hit an error when trying to flash LOS and so decided to reboot the system and try again, however when rebooting the system I got the error "Your device software can't be checked for corruption, Please lock the bootloader". And I cant seem to access TWRP anymore, just the stock recovery.
Im just wondering if I can just flash stock because I cant use my phone at all atm

King Norman said:
Step by Step, I managed to unlock it and flash the bootstack, but I hit an error when trying to flash LOS and so decided to reboot the system and try again, however when rebooting the system I got the error "Your device software can't be checked for corruption, Please lock the bootloader". And I cant seem to access TWRP anymore, just the stock recovery.
Im just wondering if I can just flash stock because I cant use my phone at all atm
Click to expand...
Click to collapse
Then flash twrp again, if your on stock recovery. You need twrp. Something must replaced twrp with the stock recovery.
After you flashed twrp use the files from the official Los thread
Bootloader and modem.

coremania said:
Then flash twrp again, if your on stock recovery. You need twrp. Something must replaced twrp with the stock recovery.
After you flashed twrp use the files from the official Los thread
Bootloader and modem.
Click to expand...
Click to collapse
Unfortunately I cant seem to view the phone as an adb device, unless i select the "Apply update from adb" option in the stock recovery, however this only lets me sideload and i cant reboot it to edl mode or anything like that to install TWRP.

What happens if you are on stock recovery and type adb reboot edl. Another way to get to edl mode can be to shut down the phone and press both volume keys while connecting the USB cable, I read that somewhere here, may need some trys.
Btw,
"Your device software can't be checked for corruption" this is normal if your unlocked.

coremania said:
What happens if you are on stock recovery and type adb reboot edl. Another way to get to edl mode can be to shut down the phone and press both volume keys while connecting the USB cable, I read that somewhere here, may need some trys.
Btw,
"Your device software can't be checked for corruption" this is normal if your unlocked.
Click to expand...
Click to collapse
I tried the volume button thing and it must have worked because i redid the scripts and managed to get TWRP back up!
now I just need to do the universal bootstack, the N_Modem thing, and then LOS Right?
Thanks so much for your help

King Norman said:
I tried the volume button thing and it must have worked because i redid the scripts and managed to get TWRP back up!
now I just need to do the universal bootstack, the N_Modem thing, and then LOS Right?
Thanks so much for your help
Click to expand...
Click to collapse
Good, you did it. Yes, after you flashed the latest official twrp,
flash the bootloader zip and modem zip which are linked at the first page of the Los thread, then your prefered rom with gapps and root if you like.
DON'T relock your bootloader !!!
Have fun!

[Q] TWRP on J320ZN

I have a Galaxy J3 (2016) J320ZN.
I have rooted it, and would like to install TWRP then xsposed, maybe even another ROM if there is any that will work.
Will the TWRP posted here for other models work on my phone?
How about ROMs? Thank you.:silly:

azlemad said:
I have a Galaxy J3 (2016) J320ZN.
I have rooted it, and would like to install TWRP then xsposed, maybe even another ROM if there is any that will work.
Will the TWRP posted here for other models work on my phone?
How about ROMs? Thank you.:silly:
Click to expand...
Click to collapse
I've only just worked this out myself and was going back to update my post...did a search and that's how I found your question.
I've had so much trouble with this... either, you couldn't get root using SuperSU.zip through TWRP (there's another thread on this)... because you'd get stuck in a bootloop and my "solution" was to flash CF-Auto-Root again... without realizing that CF-Auto-Root wipes to stock recovery XD. Through this, though I lost my phone re-set up and TWRP.... I saw that there was a dm-verity error which I don't understand but know there is a patch.... and maybe that's why people were getting bootloops? I'm really not an expert at all. I just try until something works.
SO, you could just first try flashing TWRP for J3lte from the link I provided and then the latest SuperSU and see if that works now.....(earlier versions did not) if it doesn't work and you get stuck in a bootloop then flash CF-Auto-Root (available at: https://download.chainfire.eu/986/C...3lteusc-j3lteusc-smj320r4.zip?retrieve_file=1) and start again. I PERSONALLY only had success without a bootloop ONCE I added the dm-verity patch to my install procedure:
The TWRP that will work for the J320ZN is j3lte: https://dl.twrp.me/j3lte/
I used the latest version twrp-3.2.1-0-j3lte.img.
If you need in-depth help look for a tutorial or quote me and I'll respond & try walk you through it. I know that model J320YZ uses the same TWRP and there is a tutorial on XDA for the basics.....
Once TWRP is installed and you've booted into TWRP recovery and you've formatted, Install SuperSU.zip through the "Install" button on TWRP. You must have SuperSU.zip on your external SD card (click "Select Storage" to select it).
https://download.chainfire.eu/1220/SuperSU/SR5-SuperSU-v2.82-SR5-20171001224502.zip
I used v.2.82 SR5
Finally, BEFORE REBOOTING, I installed no-verity-opt-encrypt-6.0.zip using the same TWRP "Install" button method - which was also on my external SD card
https://androidfilebox.com/miscellaneous/dm-verity-and-forced-encryption-disabler/
Then you can reboot, and set up your phone. Xposed works. If you already ran the fixes using Apps2SD to fix security measures that prevntd Link2SD from creating mountscripts, that stays fixed after all of this.
BACK UP YOUR PHONE FIRST 'cos you'll have to reset it all up again. Samsung Smart Switch (on your PC) helps, as will Titanium Backup.
Now.... as I said I'm not an expert. I don't understand why things are the way they are. Nor am I responsible if the dm-verity wasn't needed, which is why maybe you should just try TWRP then latest SuperSU first. BUT for me, I had bootloop and needed the 3rd step of dm-verity patch.
As for Custom ROMS... I have no real interest in those, so that's something you'll have to experiment with yourself, or ask someone else

IMPORTANT: I thought I'd better add that once you've got TWRP and root installed... and want to install Xposed, you cannot use the official version for Android 5.1.1. It will not work on our Samsung Touchwiz Stock ROMS. You can either install a custom ROM first, or you will have to use the Unofficial version by wanam that will work on device.
Here's a tutorial: https://www.tricksfolks.com/install-xposed-framework-samsung-lollipop-marshmallow/
Make sure to select from the download links the file for 5.1.1 and our hardware is arm so download that file, not arm64 version or x86 version. Should be xposed-v87.1-sdk22-arm-custom-build-by-wanam.zip
Also note, I had some issues with the Xposed Installer (apk) - latest one 3.2. Didn't want to register the wanam framework that I flashed in TWRP. So, I rolled back to 3.1.5 and that works OK. You'll have a big red warning telling you not to update THEIR framework... but ignore that and just go to Downloads and install away.
The article I linked above with the tutorial and download links has an earlier version of the Xposed Installer so you could try that if you can't find v.3.1.5. Just don't use v.3.2
ALSO ANYBODY PLEASE UPDATE ME IF YOU GOT TWRP AND ROOT WITH OR WITHOUT DM-VERITY PATCH. I'd like to know so I can learn more about this stuff. Still a novice.

Annnnnd I just realized you were the one that PMed me a few weeks ago to get me working on this and that you'd broken your phone hehehehe.
Well, I'm just updating it on all the J320ZN threads now for future folk.

Winston Churchill said:
Annnnnd I just realized you were the one that PMed me a few weeks ago to get me working on this and that you'd broken your phone hehehehe.
Well, I'm just updating it on all the J320ZN threads now for future folk.
Click to expand...
Click to collapse
lol
yeah, that was me sadly -_-
But thank you very much anyway, for taking the time and effort to post this, I'm sure it'd be useful to somebody out there

Winston Churchill said:
I've only just worked this out myself and was going back to update my post...did a search and that's how I found your question.
I've had so much trouble with this... either, you couldn't get root using SuperSU.zip through TWRP (there's another thread on this)... because you'd get stuck in a bootloop and my "solution" was to flash CF-Auto-Root again... without realizing that CF-Auto-Root wipes to stock recovery XD. Through this, though I lost my phone re-set up and TWRP.... I saw that there was a dm-verity error which ...
As for Custom ROMS... I have no real interest in those, so that's something you'll have to experiment with yourself, or ask someone else
Click to expand...
Click to collapse
Wow, thanks for going through the pain so I may not have to go through so much. Would you be able & willing to help me get my wife's SM J320ZN rooted so I can get the sd card used for apps? She doesn't need too much on there but the bloody thing goes to low memory way too soon. I'd love to know if I can get a better os on there too if you can make any suggestions.
I've got enough knowledge to be able to install lineageOS onto my crappy moto e & get that working ok but I'm still on the steep learning curve.
If you can, please provide a step-by-step guide to do this? I know you've said most of what needs to happen in your posts, but when I see "Once TWRP is installed and you've booted into TWRP recovery and you've formatted,..." I'm wondering what should get formatted, what shouldn't, etc
Warm regards

Need support on 7.1.2 for Y5 2017 mya-l22

I have successfully booted the rr 7.1.2 rom from 4pda on my device every thing seems very well except in performance its much slower than the stuck firmware , also i have check the antutu score and it get lower by 10k points , i have check the gpu with another app and the working percent was stuck at 0%
So if any one could help fixing the hwc , kernel , hw coding and decoding,, it will make the device fly again

fir1996 said:
I have successfully booted the rr 7.1.2 rom from 4pda on my device every thing seems very well except in performance its much slower than the stuck firmware , also i have check the antutu score and it get lower by 10k points , i have check the gpu with another app and the working percent was stuck at 0%
So if any one could help fixing the hwc , kernel , hw coding and decoding,, it will make the device fly again
Click to expand...
Click to collapse
I have been trying to get this room to work but failed everytime, because of the encryption.
Everytime I get decryption successful but something went wrong. As far as I understand the encryption should be disabled on this ROM completely, but I can't get it done. I tried reformatting data to ext4 but that didn't work.
Edit: The problem was that I was using Magisk as root solution. I tried with the provided SuperSU and it all worked.
My device runs well with rr. I only notice the performance issue on startup, right after but the phone is very slow.
I noticed that there is no swap memory use in this ROM, while in stock there was a deal memory partition.
I'll try to figure out if we can enable it in this ROM. That might improve performance.

JudgeDread11 said:
I have been trying to get this room to work but failed everytime, because of the encryption.
Everytime I get decryption successful but something went wrong. As far as I understand the encryption should be disabled on this ROM completely, but I can't get it done. I tried reformatting data to ext4 but that didn't work.
Edit: The problem was that I was using Magisk as root solution. I tried with the provided SuperSU and it all worked.
My device runs well with rr. I only notice the performance issue on startup, right after but the phone is very slow.
I noticed that there is no swap memory use in this ROM, while in stock there was a deal memory partition.
I'll try to figure out if we can enable it in this ROM. That might improve performance.
Click to expand...
Click to collapse
Don't mean to hijack this thread but im desperate. Im trying to root mt MYA L22 but can't seem to find the right instructions. Posted here two times but no one is replying. Could you tell me how you unlocked bootloader on your phone? I already have the code from Huawei website. I am stuck at the cmd prompt when i type "list adb devices" from a cmd prompt opened through the adb and fastboot folder that ive downloaded. It says adb devices attached but shows nothing after that, basically an empty list. Any advice would be greatly appreciated!

Dylan2232 said:
Don't mean to hijack this thread but im desperate. Im trying to root mt MYA L22 but can't seem to find the right instructions. Posted here two times but no one is replying. Could you tell me how you unlocked bootloader on your phone? I already have the code from Huawei website. I am stuck at the cmd prompt when i type "list adb devices" from a cmd prompt opened through the adb and fastboot folder that ive downloaded. It says adb devices attached but shows nothing after that, basically an empty list. Any advice would be greatly appreciated!
Click to expand...
Click to collapse
It was a long time ago since I setup fastboot and ADB. I used this thread
https://forum.xda-developers.com/showthread.php?t=2277112&page=53

JudgeDread11 said:
It was a long time ago since I setup fastboot and ADB. I used this thread
https://forum.xda-developers.com/showthread.php?t=2277112&page=53
Click to expand...
Click to collapse
I went through that thread. I understand you rooted it but then started having problems? Like you couldn't download? Where you able to solve those problems? Now I am worried to root it.

Dylan2232 said:
I went through that thread. I understand you rooted it but then started having problems? Like you couldn't download? Where you able to solve those problems? Now I am worried to root it.
Click to expand...
Click to collapse
I'm not sure which post you saw, but I think my post on there were with an other device and yes, I have never bricked a device unrecoverable (yet).
That said, you will always be taking a risk when rooting or trying custom ROMS.
Then again if you never take risks you won't get anywhere. The question is how much are you willing to risk. In this case are you willing to risk your phone for the extra possibilities you might get when rooting it
First think you need to do before modifying anything is learning how to backup and restore.

JudgeDread11 said:
I'm not sure which post you saw, but I think my post on there were with an other device and yes, I have never bricked a device unrecoverable (yet).
That said, you will always be taking a risk when rooting or trying custom ROMS.
Then again if you never take risks you won't get anywhere. The question is how much are you willing to risk. In this case are you willing to risk your phone for the extra possibilities you might get when rooting it
First think you need to do before modifying any freething is learning how to backup and restore.
Click to expand...
Click to collapse
Thanks JudgeDread. Yes, I've rooted several phones in my life time. I understand the risk, but I tend to research about that particular rooting method with my phone before going ahead and doing it. I feel like the rooting method for my phone is particularly more risky, not because of what I read but rather from what info I am NOT able to find. Did you have a Huwaei Y5 2017 MYA l22 that you rooted successfully without issues? Can you point me to the instructions? That thread is a bit confusing.

Dylan2232 said:
Thanks JudgeDread. Yes, I've rooted several phones in my life time. I understand the risk, but I tend to research about that particular rooting method with my phone before going ahead and doing it. I feel like the rooting method for my phone is particularly more risky, not because of what I read but rather from what info I am NOT able to find. Did you have a Huwaei Y5 2017 MYA l22 that you rooted successfully without issues? Can you point me to the instructions? That thread is a bit confusing.
Click to expand...
Click to collapse
Yes exact same model, rooted and after several tries custom ROM.
I unlocked using the official method and then flashed TWRP in the recovery partition.
The difficulty was to get back into TWRP after rebooting. So I would advice to immediately install a root solution. I used Magisk. While root works without problem Magisk modules will only work if you use the f2fs workaround.
I am now running Resurrection remix (Android 7.1.2) without many issues. Only every now and then a forced close of the system UI.
It took some time to get it running. Because I used a different root solution the provided on the same page as the ROM. So on install use the provided SuperSU. After install you can change of you want.
Also the patches are needed. I still have bad videos on YouTube but haven't looked into the issue much yet.

hi , good news for Huawei y5 2017(MYA-L22) users.
Download latest lineage14.
visit to my blog.
cheers
https://p55novo.blogspot.com/2018/07...e-141-for.html

JudgeDread11 said:
Yes exact same model, rooted and after several tries custom ROM.
I unlocked using the official method and then flashed TWRP in the recovery partition.
The difficulty was to get back into TWRP after rebooting. So I would advice to immediately install a root solution. I used Magisk. While root works without problem Magisk modules will only work if you use the f2fs workaround.
I am now running Resurrection remix (Android 7.1.2) without many issues. Only every now and then a forced close of the system UI.
It took some time to get it running. Because I used a different root solution the provided on the same page as the ROM. So on install use the provided SuperSU. After install you can change of you want.
Also the patches are needed. I still have bad videos on YouTube but haven't looked into the issue much yet.
Click to expand...
Click to collapse
Thanks again for replying. Unfortunately though, 80 percent of what you just said flew over my head
I am not an expert but I can follow instructions! Any step by step guide on how to root it? So far I've gotten the unlock code from Huawei. I downloaded the ADB and fast boot folder and launched from that folder the cmd prompt. I type in "list of ADB deviced" and below comes an empty list. Please share what you did.

Dylan2232 said:
Thanks again for replying. Unfortunately though, 80 percent of what you just said flew over my head
I am not an expert but I can follow instructions! Any step by step guide on how to root it? So far I've gotten the unlock code from Huawei. I downloaded the ADB and fast boot folder and launched from that folder the cmd prompt. I type in "list of ADB deviced" and below comes an empty list. Please share what you did.
Click to expand...
Click to collapse
For rooting you need unlocked bootloader ( if you don't do ir then below won't work).
1)download the 4pda app from google play store and register an account .
2) download the TWRP.img file from 4pda website here is the link
https://4pda.ru/forum/index.php?showtopic=823938&view=findpost&p=74424572
3) enable developer mode in your phone by going to setting about phone , tap 6 times on the build number.
4)go to developer mode and enable usb debugging and oem factory unlock .
5) go to your pc install adb here link https://forum.xda-developers.com/showthread.php?t=2588979
6) now conect the phone to the pc and run cmd , type adb reboot bootloader . (Your device ahould restart and enter bootloader mode (white screen)).
7) now take the TWRP.img (must be copyied to desktop ) and type in cmd cd desktop.
8) type fastboot flash recovery TWRP.img (change the file name to TWRP ).
9) type fastboot reboot.
Now you have successfully install TWRP on your device.
Continue... If replied