Database Users

[Q] Having trouble installing CM 10.1 on AT&T Galaxy S4

I've tried using several different guides published on XDA and other forums, and I still cannot get CM 10.1 to install correctly on my AT&T Galaxy S4. I have been able to successfully root the phone and install the latest version of TWRP (using the instructions here: http://forum.xda-developers.com/showthread.php?t=2262996). However, when I try to flash CM 10.1 using the file found here: http://wiki.cyanogenmod.org/w/Jflteatt_Info , it fails. After reboot, it loads the Samsung Custom screen for about 10 seconds, and then everything goes black. I have to pop the battery out to power off. Luckily, I was able to use Odin 3.07 to flash the phone back to its original firmware. I've tried to do this at least half a dozen times, but to no avail. Does anyone have an idea of what I could be doing wrong? I would greatly appreciate any help, or if someone could just point me in the right direction. Thanks.

mcostltpa said:
I've tried using several different guides published on XDA and other forums, and I still cannot get CM 10.1 to install correctly on my AT&T Galaxy S4. I have been able to successfully root the phone and install the latest version of TWRP (using the instructions here: http://forum.xda-developers.com/showthread.php?t=2262996). However, when I try to flash CM 10.1 using the file found here: http://wiki.cyanogenmod.org/w/Jflteatt_Info , it fails. After reboot, it loads the Samsung Custom screen for about 10 seconds, and then everything goes black. I have to pop the battery out to power off. Luckily, I was able to use Odin 3.07 to flash the phone back to its original firmware. I've tried to do this at least half a dozen times, but to no avail. Does anyone have an idea of what I could be doing wrong? I would greatly appreciate any help, or if someone could just point me in the right direction. Thanks.
Click to expand...
Click to collapse
I am in exactly same boat but right now I am using same custom recovery as you and afraid to do anything else. But I think here is what's going on. CM10.1 you're trying to install is not LOKID (LOKI is something to trick bootloader because our device bootloader is locked) So that LOKI thing should be on rom itself AND kernel. Our recovery does not auto-LOKI roms that's why you installing them and they're fail. So you need to install new recovery with AUTO-LOKI feature installed if you look in developer section you'll see. Now here is my question. How do I go from TWRP that been installed via GooManager to CWM - Auto-Loki edition ? Anyone 1.2.3.4 guide for us ?
Here are new Recovery that have AUTO-LOKI feature. IF your ROM/KERNEL already preLOKI (pre patched) it will still work it'll know rom pre-patched.
http://forum.xda-developers.com/showthread.php?t=2291956
So anyone can get quick guide how to move from TWRP to CWM from above ?

[Q] Trying to install liquidsmooth to S4

I am sure my answer has been posted before, but i couldn't find what i was looking for after scouring google and XDA for a few days now so my apologies in advance.
I have the ATT I337 s4 with 4.4.2 firmware and am trying to install liquidsmooth V3.2 but obviously its not working. I keep getting an error that states:
"E: signature could not be verified"
"E: whole package signature could not be verified"
And then the phone factory resets itself and reboots.
What I have done: Rooted the phone with towelroot, then installed supersu, disabled knox, and then installed busybox.
Some posts I read said that i need to use safestrap to install liquidsmooth, so i tried that as well, and it says the installation is successful, but the program state never changes to show "installed" and the button to reboot into recovery never gets activated.
I am not sure what I am doing wrong, but I think from what I have read that I need a custom boot loader in order to get the install to work, such as CWM, but then i run into other posts that say:
"NOTE – For AT&T/Verizon users with Android 4.3/4.4.2 or higher, you cannot use the LOKI method, you need to use SafeStrap Recovery to install custom ROMs, see How to Install Custom ROMs on AT&T/Verizon Galaxy S4 using SafeStrap instead!"
Im hoping someone can fill in the gaps that I am missing because it is getting annoying having my phone factory reset after every attempt and having to start over again, but its better than a brick lol.
Let me know what you think, and please help get me in the right direction

What firmware version are you on? Go to settings, more, about device and look at the last three characters of your build number.
Nvm, I read your firmware as 4.2.2. You're either on nb1 or nc1. Either case you'll need to use safestrap. See in the general forum index, all things at&t.... It'll have everything you need.
PS, you won't be able to install liquidsmooth on your device. Only touch wiz based roms
Sent from my Nexus 5 using XDA Free mobile app

[Q] G870W Recovery

Hello there!
I've successfully rooted my (Rogers) S5 Active / G870WVLU1ANH3 / kltevlactive using CF Auto Root, blowing my knox and all that, works great.
However, I'm now trying to flash either TWRP or CWM Philz for klte (which may have not been to smart come to think about that, but I recall reading it should work just fine) using Odin, and I can't get into recovery. Whenever I attempt to boot into recovery, I end up with "cannot do normal boot".
I recall reading a SafeStrap for G900 works for the G870, but I can't find the thread again, and don't want to just try and see what happens.
I've also tried flashing a recovery using either TWRP app and RomManager, I have yet to try Rashr, but since all the recoveries I've found are for klte, instead of kltevlactive, I'm slightly worried.
I'm not all that new to rooting, but I'm quite new (and upset ) at the Samsung realm, any chance you guys would know what could get me going with a custom recovery?
I also have a Xposed Framework installed, I read it could cause issues with SafeStrap, but I don't suppose it would affect flashing a rom from Odin/whatever else?
My SELinux on the phone claims to be "Enforcing", if that matters, perhaps.
Thanks!

Im having The same issue please help
Sent from my SM-G870W using XDA Free mobile app

Any luck on this? I've scoured the forums with no luck, although I see people mentioning they have it.

I am experiencing something similar. I have a rooted SM-G870W (Bell). I tried both TWRP and CWM recovery.
Every time I tried to go to recovery mode either via pressing button combo or from adb (adb reboot recovery),
my phone goes into download mode instead, I get "Downloading... Do not turn off target" screen.
Have you also experienced some weirdness with your rooted phone? On mine if I go into boot into recovery
(this is without custom recovery), do nothing but select reboot, I will get "System UI stopped working".
Or "unfortunately mtp application stopped" . I re-flashed the phone with the stock OEM ROM and I don't
get the issues I sated above.
BTW, how did you get xposed framework installed. Mine said "not yet compatible with Android SDK 21 "
Thanks
kachnitel said:
Hello there!
I've successfully rooted my (Rogers) S5 Active / G870WVLU1ANH3 / kltevlactive using CF Auto Root, blowing my knox and all that, works great.
However, I'm now trying to flash either TWRP or CWM Philz for klte (which may have not been to smart come to think about that, but I recall reading it should work just fine) using Odin, and I can't get into recovery. Whenever I attempt to boot into recovery, I end up with "cannot do normal boot".
I recall reading a SafeStrap for G900 works for the G870, but I can't find the thread again, and don't want to just try and see what happens.
I've also tried flashing a recovery using either TWRP app and RomManager, I have yet to try Rashr, but since all the recoveries I've found are for klte, instead of kltevlactive, I'm slightly worried.
I'm not all that new to rooting, but I'm quite new (and upset ) at the Samsung realm, any chance you guys would know what could get me going with a custom recovery?
I also have a Xposed Framework installed, I read it could cause issues with SafeStrap, but I don't suppose it would affect flashing a rom from Odin/whatever else?
My SELinux on the phone claims to be "Enforcing", if that matters, perhaps.
Thanks!
Click to expand...
Click to collapse

kachnitel said:
Hello there!
I've successfully rooted my (Rogers) S5 Active / G870WVLU1ANH3 / kltevlactive using CF Auto Root, blowing my knox and all that, works great.
However, I'm now trying to flash either TWRP or CWM Philz for klte (which may have not been to smart come to think about that, but I recall reading it should work just fine) using Odin, and I can't get into recovery. Whenever I attempt to boot into recovery, I end up with "cannot do normal boot".
I recall reading a SafeStrap for G900 works for the G870, but I can't find the thread again, and don't want to just try and see what happens.
I've also tried flashing a recovery using either TWRP app and RomManager, I have yet to try Rashr, but since all the recoveries I've found are for klte, instead of kltevlactive, I'm slightly worried.
I'm not all that new to rooting, but I'm quite new (and upset ) at the Samsung realm, any chance you guys would know what could get me going with a custom recovery?
I also have a Xposed Framework installed, I read it could cause issues with SafeStrap, but I don't suppose it would affect flashing a rom from Odin/whatever else?
My SELinux on the phone claims to be "Enforcing", if that matters, perhaps.
Thanks!
Click to expand...
Click to collapse
I am having the same issue. Any solution?

I had the "cannot do normal boot" issue as well after doing something dumb which stopped me being able to get into recovery. Was about to flash the original firmware but flashed twrp with odin instead after doing some research. Fixed my problem easily, hope this helps.

Same story with mine
Hi There
I'm having the same issue but all they talk about here are 900 and we have G870W
If someone find any information and how to flash the 870 I would be greatfull
to them because all I could find on the internet pertains to the 900 this is infurating
and by the way any of you have that OEM button in developer?
I bet not again all I've been reading on S5 Active also mention about the OEM button
and this is total BS because we don't have a OEM button. If we can find
a site that could help use with our particular phone and not just the 900

Hello, I have successfully unlocked the bootloader and rooted my S5 Active SM-G870W using this guide and carefully following the appropriate links for my device:
https://r2.community.samsung.com/t5...ooting-Your-Phone-and-Flashing-A/td-p/2496038
Now I would like to flash a custom recovery such as TWRP, but cannot find a recommended version for the G870W. Does anyone have any suggestions on where to find one, or know if any of the ones for the 900 would work on the 870? It's a Canadian version of the S5. Thanks for any help anyone is able to provide!

Does anyone know if the instructions for installing Lineage for SM-G870A/F (found here: https://lineageosroms.com/klteactivexx/) would work on my SM-G870W, kltevlactive? How much of a chance would there be it would brick it? Help much appreciated!

Cant install custom recovery or root

Hey guys
So i got my galaxy s5 yesterday after my phone contract and because my previous phone was an a3 and there is no custom roms for this i was looking forward to getting my s5 and rooting, getting a custom recovery, custom rom etc but no matter what i do i cant get the custom recovery to boot thus meaning i cant root either every time i try and flash TWRP, CWM or philz it simply goes to a screen where i get the 'recovery is not seandroid enforcing' or something along those lines and then i get a blank screen and have to do a battery pull, i can get into the main system alright but just have no luck whatsoever getting into recovery does anyone have any suggestions? it is a SM-G900F and its a European edition if that helps at all
Thank You in advancew!

Fits the picture. Many users facing problems rooting new s5 G900f
Have a look at this thread
http://forum.xda-developers.com/showthread.php?p=61341980

disobiech said:
Fits the picture. Many users facing problems rooting new s5 G900f
Have a look at this thread
http://forum.xda-developers.com/showthread.php?p=61341980
Click to expand...
Click to collapse
I actually just managed to solve it, i was using twrp 2.8.5.0 and after a bit more looking around apparently newer s5's are having problems with this, downloaded the 2.8.7.0 and it worked straight away!

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.