Database Users

[q] such agonizing frustration

Well, here's my story.
Trying to install custom rom for my Note 3. I have version N900V for verizon. I'm assuming whatever I use I can use the N9005 because that's the only one that ever seems to come close to my model number based off the qualcomm chipset? Just a side note I guess. I've currently had success in rooting via one of the "one click" apps called Kingo. Very nice and easy and breezy. The real problem is trying to install a custom recovery via cwm. No matter what I do or try nothing will work. I can gaurantee it.
Also tried looking into twrp but even their app wouldn't install recovery. So I've done many things from using multiple versions of Odin, to many different cwm's, and all making sure I follow the instructions just as outlined to no avail. EVERY single time is a failed attempted with Odin, never passes. I believe I've gotten every different error you could get (all derive from same method anywho so figure they mean the same).
I haven't broken my knox yet so I guess that's good. I'm just not sure why I can't seem to get a recovery installed so i can finally move onto getting the rom installed. Once in download mode with the whole "volume up/home button/ power button" thing I get a few errors in there too such as: Sys rev check fail: no signature, and magiccode check fail: (some error here). Something along those lines. Even when I first started it would say that the signature files couldn't be verified or something. Looked a bit different and I forget how/when I got those messages. Funny thing is when I press volume up and power button with home, I get a recovery that looks just like a cwm one....not sure if there the whole time by default or maybe a feature of the root? Not sure honestly but I tried forgetting the cwm and going to install the rom and of course my luck I wiped data/cache following directions hoping it'd install properly, and I still get errors while trying to do the rom.
So now i'm back at out of box settings(although rooted) and I'm nowhere. If any of you has the slightest idea that could help I can't give up now. Also an interesting tidbit is I don't have the option anywhere for "reactivation lock" being disabled. Not sure why if anyone knows that explanation. Already have USB Debugging enabled so lets get the obvious ruled out too. Also I know my drivers have to be installed correctly since I can get into my phones SD card just fine as well as Odin always recognizes it right away as being added or removed hence the color being either yellow or blue. Tried even ticking everything and nothing and just some. even tried adding the pit file too. probably not necessary. I've had to even try replugging into different USB ports without closing Odin as some have suggested would work, and also closed Odin doing the same thing. No avail. I fear I may not be able to flash cwm for some reason? I would be pretty upset if I couldn't install a custom rom.

ducky06 said:
Well, here's my story.
...
So now i'm back at out of box settings(although rooted) and I'm nowhere. If any of you has the slightest idea that could help I can't give up now.
...
Click to expand...
Click to collapse
Hints - read more, select the right forum:
http://forum.xda-developers.com/verizon-galaxy-note-3

IIRC Verizon uses a locked boot loader. This means you can only load software signed by Verizon onto your device. The error messages seem also to point in that direction.
Someone may correct me if I'm wrong.
---------- Post added at 12:20 PM ---------- Previous post was at 12:04 PM ----------
Another sidenote: You mentioned Kingo. This is suspected to be malware (I didn't follow the corresponding thread, however). Seems to spy IMEIs. Search here at xda for more.
Just a warning for those reading it.

Samsung Galaxy S5 (G870A) Bootloop Fix!

I've recently found away to fix a Galaxy S5 Active stuck in a boot loop. (This method only works if your device is on lollipop 5.0! )
Note: This method only works on the OC5 update.
More firmware support coming soon.
What happened: I accidentally made my Galaxy S5 Active get stuck in a boot loop. I couldn't find a solution for the longest time because the bootloader is locked. Time passed and I eventually found away to fix the boot loop if your devices is running Lollipop 5.0!
Solution:
1. You should always try to fix the boot loop by booting into recovery mode by holding down the Home+Volume-Up Key+Power button. Once the phone logo pops up on the screen releases the power button only, but continue to hold the Home+Volume-Up Key. If it worked is should say "Booting into recovery." or something along those lines in blue letters.
Once you're into recovery use the volume keys to navigate Up and Down. Find wipedata/factory reset. Select it with the power key and navigate down to Yes. Wait till it finishes. Then see if that fixed the problem. If not proceed to next step
2. Since the boot loader is locked it's really difficult to flash any kind of Recovery, ROM, or Stock Rom unless your phone accepts it as a valid file. So here's what you do!: (Method 1)
Download this file and save it to your desktop: https://drive.google.com/open?id=0B3UBRFq3BojVQnBSc3lCSzloYUU
Download ODIN v(3.09): http://odindownload.com/Samsung-Odin/#.VgiJ_8tViko - Extract it to your desktop.
Put your phone in download mode. (Note: Before you do this, install the correct drivers for your phone to your computer.)Make sure your phone is completely off and Hold the Home+Volume Down+Power. You will get a warning message just press the volume up key to continue.
Go to desktop and launch ODIN. After ODIN pops up, plug in your device. (Make sure you have the correct phone drivers installed)
You should see a dialog box in ODIN that say 0:[COM6] in blue. Note: It might be different for everyone, just make sure it says COM.
After that, Under "File [Download]" click "AP" Then navigate to the file you downloaded earlier called "boot.tar"
MAKE SURE RE-PARTITION IS UNCHECKED!
Leave everything else alone then click start. Wait till it says PASS! in green letters in ODIN!
(Method 2):
Go to this link download it to your desktop and follow the instructions: https://drive.google.com/file/d/0B3UBRFq3BojVdXlSUE43VzJPbEU/view?usp=sharing
Done! Your device shouldn't be in a boot loop anymore! If you have any questions let me know!
Note: Once this process is complete, your phone will permanently show a warning in your notifications saying "Unknown action detected." This happens because your phone will detect that your kernel was modified so if you don't want this to happen, then I suggest you wait for a official lollipop OS release.
UPDATE!: You should now be able to download the "Boot.tar" file. Sorry about that!
UPDATE!: New files and instructions added if the first method didn't work!

Having some major issues
First post so forgive me if this is misplaced. Before I was aware I'm unable to down grade from 5.0 or 5.1 version of sm-g870a I attempted to downgrade and apply root from version 4.4.2/4.4.4 via another XDA thread in a faulty attempt to root. At first this presented no issues until restart. At this point the phone is soft bricked and bootloops. Both download mode and system recovery ARE accessible and prior to this I had USB debug open. I have the factory cable and odin identifies the device easily. All other md5 files failed to apply OTHER than one. (4.4.4 ota) I presume because of bootlocks which I'm now aware of. I have attempted three different stock flashes via odin all from XDA all fail at authentication claiming error fused 2 binary 1. I attempted add data pull before all of this and the device ignored a request which prompted a factory reset which was odd. I have attempted installing 3 alternative stock and stock rooted 5.0 and 5.1 firmwares from XDAs threads. All of which failed, hiwever one granted me some precious Information when I slowed down the error message via recording. It states, "Package expects fingerprint of Samsung kltattactive/lteactive:4.4.2/kot49h/g870aucu1ang3:user/release-keys o0A1:user/release-keys this device has kltactive/kltactive. This tells me as far as I know that the device is showing no firmware installed and a double fed file making the attempting installation incompatible. At this point I want to start anew, I have how attempted every route accessible via XDA and feel my options are running very low other than attempting to randomly apply firmware in sequence until odin accepts one and it sticks. That sound like a brick plan however. I don't care what firmware is loaded as long as an OS is accessible. I think this is all available Information I apologize for typos I have been at this for a total of 20 hrs straight. This bootloop was a tired lapse in judgement and has cost me 5 hours of trial and error. Wiping cache fails, reformatting internally fails, as far as I know root was never successful and I THINK philz was successful installed although at this point I cannot recall. Thanks for reading and in advance for any available help. I have SOME c# experience and some java script which is zebra vs dolphin situation I only mention as to aide and explain my trainers of thought. All other languages are vague at best
Edit: I stopped bootloop with the file attached to this thread. It now boots into samsung display bht will not go further and stops there as though it still has no operating system.

Ghujii said:
First post so forgive me if this is misplaced. Before I was aware I'm unable to down grade from 5.0 or 5.1 version of sm-g870a I attempted to downgrade and apply root from version 4.4.2/4.4.4 via another XDA thread in a faulty attempt to root. At first this presented no issues until restart. At this point the phone is soft bricked and bootloops. Both download mode and system recovery ARE accessible and prior to this I had USB debug open. I have the factory cable and odin identifies the device easily. All other md5 files failed to apply OTHER than one. (4.4.4 ota) I presume because of bootlocks which I'm now aware of. I have attempted three different stock flashes via odin all from XDA all fail at authentication claiming error fused 2 binary 1. I attempted add data pull before all of this and the device ignored a request which prompted a factory reset which was odd. I have attempted installing 3 alternative stock and stock rooted 5.0 and 5.1 firmwares from XDAs threads. All of which failed, hiwever one granted me some precious Information when I slowed down the error message via recording. It states, "Package expects fingerprint of Samsung kltattactive/lteactive:4.4.2/kot49h/g870aucu1ang3:user/release-keys o0A1:user/release-keys this device has kltactive/kltactive. This tells me as far as I know that the device is showing no firmware installed and a double fed file making the attempting installation incompatible. At this point I want to start anew, I have how attempted every route accessible via XDA and feel my options are running very low other than attempting to randomly apply firmware in sequence until odin accepts one and it sticks. That sound like a brick plan however. I don't care what firmware is loaded as long as an OS is accessible. I think this is all available Information I apologize for typos I have been at this for a total of 20 hrs straight. This bootloop was a tired lapse in judgement and has cost me 5 hours of trial and error. Wiping cache fails, reformatting internally fails, as far as I know root was never successful and I THINK philz was successful installed although at this point I cannot recall. Thanks for reading and in advance for any available help. I have SOME c# experience and some java script which is zebra vs dolphin situation I only mention as to aide and explain my trainers of thought. All other languages are vague at best
Edit: I stopped bootloop with the file attached to this thread. It now boots into samsung display bht will not go further and stops there as though it still has no operating system.
Click to expand...
Click to collapse
New method for you...

irontaco1 said:
New method for you...
Click to expand...
Click to collapse
Alright this stopped the looping now, to find a proper rom. I believe. Im going tohave to wait for 5.1 in order for it to be successful, however is having 4.4.2 still on it is a bit worrisome, I predict overwriting it should be fine though. Thank you for giving me a way to at least resolve bootlooping. I believe I shoulda have safestrapped the device, but hindsight is always 20/20 eh?

Ghujii said:
Alright this stopped the looping now, to find a proper rom. I believe. Im going tohave to wait for 5.1 in order for it to be successful, however is having 4.4.2 still on it is a bit worrisome, I predict overwriting it should be fine though. Thank you for giving me a way to at least resolve bootlooping. I believe I shoulda have safestrapped the device, but hindsight is always 20/20 eh?
Click to expand...
Click to collapse
I'm glad you got past your Bootloop! If you need anymore help let me know.

Is there a way to root my galaxy s5 active [G870A] on att with 5.0? I'm getting conflicting info and not finding the root.tar I need to flash in order to roll back to 4.4.2 so I can root. Right now I'm just trying to get root. Thanks for any help or direction.
S5 Active

I'd say hold off for a while I did that exact 5 Hong with the s5 active and it bootlocks it. You need to, if you're going to do this install and use safestrap to di so and BACK UP EVERYTHING with safe strap to SD. As long as you follow those method you SHOULD be able to even soft brick it and come back from it.

shadavis08 said:
Is there a way to root my galaxy s5 active [G870A] on att with 5.0? I'm getting conflicting info and not finding the root.tar I need to flash in order to roll back to 4.4.2 so I can root. Right now I'm just trying to get root. Thanks for any help or direction.
S5 Active
Click to expand...
Click to collapse
I haven't found any successful way to to go back to Kit Kat or 4.4.2 for this phone. In fact that's why this thread exist is because people who have tried to flash back to 4.4.2 have failed and got stuck in a Bootloop. So if you plan on trying to find away make sure you back everything up and if you fail you can use this tutorial to get your phone working again.
Make sure you have "USB Debugging" on
Make sure you have the drivers for your phone installed on your PC before you start the process of looking for a root.

Yeah I tried flashing back to 4.4.2 and it was a no go . I had the stuck on 5.0 issue where download mode says "downloading do not turn off ...... " but after I wiped my phone I was able to update to 5.1.1 successfully without any "download interrupted "errors . So at least I'm not stuck on 5.0 now lol
Sent from my SAMSUNG-SM-G870A using Xparent BlueTapatalk 2
---------- Post added at 03:24 PM ---------- Previous post was at 03:21 PM ----------
Although I still have that "Downloading do not turn off target " thing when I try to enter download mode! Sheesh
Sent from my SAMSUNG-SM-G870A using Xparent BlueTapatalk 2

shadavis08 said:
Yeah I tried flashing back to 4.4.2 and it was a no go . I had the stuck on 5.0 issue where download mode says "downloading do not turn off ...... " but after I wiped my phone I was able to update to 5.1.1 successfully without any "download interrupted "errors . So at least I'm not stuck on 5.0 now lol
Sent from my SAMSUNG-SM-G870A using Xparent BlueTapatalk 2
---------- Post added at 03:24 PM ---------- Previous post was at 03:21 PM ----------
Although I still have that "Downloading do not turn off target " thing when I try to enter download mode! Sheesh
Sent from my SAMSUNG-SM-G870A using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
There should not be anything attempting to download when you boot into ''download mode'' if there is, its highly likely there are still particulates of the last bad flash. I would as he said above, enable USB debugging and the like, and install safe strap to be safe. After safe strap is done and youve followed the tutorial which you can find in another thread on this site, boot your phone down and then power it back on, safe strap should come up first, when it does so push the ''recovery'' option to enter safe strap( someone correct me if thats wrong, my phone is currently dead/charging so i cant check) From there you can back up to an SD card, make sure you enable compression when you do.
Once thats done, WIPE YOUR PHONE, and Cache,( maybe dalvik as well if you cant find it dont worry.)and its all on SD CARD, then attempt to dirty flash( I dont recommend), or clean flash your device WITH safe strap. This typically entails downloading a .zip file and opening it THROUGH safestrap, which is done the same way as backing up your data, only via another option in the menu. Simply put; Back up data with safe strap, after thats done push back and choose FLASH, it should show you all available items it can flash from/to, pick and pray. I didnt go this route when I tried, I attempted to brute force the Bootlocked S5A, and it caused some errors that I now have reversed after much pain. If I HAD safe strapped, It may have went smoother for me, and may for you. Safestrap for us Samsung users is the same as Clockwork Mod for the rest if you weren't aware.
I'll edit this when my phone charges and I can walk you through appropriately, if need be MSG me and Ill do it as soon as I receive the message via this thread if I have not already.

hi guys! good day! i have tried the new method twice! and odin fails everytime! the problem is with the modem.bin! is there any way to fix this?

Make sure you're running lollipop and not Kit Kat and make sure you have the correct phone model. If you don't meet both those requirements then it won't work.

it has on lollipop recoverymode comes up with LRX21T.G870AUCU1B0C5. ISNT that lollipop? download mode also says ;A2, P1

abatoir said:
it has on lollipop recoverymode comes up with LRX21T.G870AUCU1B0C5. ISNT that lollipop? download mode also says ;A2, P1
Click to expand...
Click to collapse
Yeah that information is correct. You might want to download the latest version of ODIN and try again. (Make sure you're putting the modem.bin file in the correct spot in Odin.)

I think I have the latest odin.. And modem can only fit in the cp field I think. Its just not working for me. I tried doing each part separately. And the modem flash always fail.
---------- Post added at 06:58 AM ---------- Previous post was at 06:57 AM ----------
I used odin 3.10 and also tried with odin 3.7

Hey irontac. Since you came up with this fix. Are you able to tell me why those s5 go into bootloop like that? By the way mine is not in bootloop. It hangs on the AT&T logo (the glob) . I was thinking maybe I need to flash the system.img , but where can I find that. And how can I flash it by itself? Actually the phone belongs to a friend. He seems to have rooted it. But I don't know what else he messed with.

abatoir said:
Hey irontac. Since you came up with this fix. Are you able to tell me why those s5 go into bootloop like that? By the way mine is not in bootloop. It hangs on the AT&T logo (the glob) . I was thinking maybe I need to flash the system.img , but where can I find that. And how can I flash it by itself? Actually the phone belongs to a friend. He seems to have rooted it. But I don't know what else he messed with.
Click to expand...
Click to collapse
You might want to boot into recovery mode and try to factory reset it normally. If his phone is rooted you could also flash a custom rom to it and get it out of Bootloop.

I also forgot to mention you can't get ahold of the system.img because it's not released to the public.

Yeah. I wanted it back to stock. I downloaded the 5.0 cfg file. Opened it up and I realized that there is no system.img in there. Oh Well. You think it would boot if I used kitKat system.img?

abatoir said:
Yeah. I wanted it back to stock. I downloaded the 5.0 cfg file. Opened it up and I realized that there is no system.img in there. Oh Well. You think it would boot if I used kitKat system.img?
Click to expand...
Click to collapse
If you flash the Kit Kat system.img you might have to downgrade the kernel also. I would give it a try and see if it works.

Root Success SM-G530AZ 5.1.1!!!

All credit goes to captaingowa and his post (http://forum.xda-developers.com/grand-prime/general/att-samsung-galaxy-prime-sm-g530a-links-t3283066) for the AT&T version.
I'm just providing stock kernel for 5.1.1 SM-G530AZ
1. Root SM-G530AZ 5.1.1 with kingroot 4.6.2 or higer (kingroot.net)
2. DON'T Reboot
3. Download and install Flashify on play store or APK
4. Flash stock kernel with flashify (http://www.mediafire.com/download/2fk19cadccq0xd7/boot.img)
5. Reboot.
6. Replace kinguser with supersu (optional) (http://www.mediafire.com/download/x1efi7ev6nf3mvd/Replace_Kinguser_with_SuperSU-v2.0.zip)
7. Enjoy

wally86 said:
All credit goes to captaingowa and his post (http://forum.xda-developers.com/grand-prime/general/att-samsung-galaxy-prime-sm-g530a-links-t3283066) for the AT&T version.
I'm just providing stock kernel for 5.1.1 SM-G530AZ
1. Root SM-G530AZ 5.1.1 with kingroot 4.6.2 or higer (kingroot.net)
2. DON'T Reboot
3. Download and install Flashify on play store or APK
4. Flash stock kernel with flashify (http://www.mediafire.com/download/2fk19cadccq0xd7/boot.img)
5. Reboot.
6. Replace kinguser with supersu (optional) (http://www.mediafire.com/download/x1efi7ev6nf3mvd/Replace_Kinguser_with_SuperSU-v2.0.zip)
7. Enjoy
Click to expand...
Click to collapse
Awesome, thank you so much. Going to try it right now, but I'm betting it will work. Thank you again for putting this all together.

Nice, think I flashed the wrong boot.img from that thread, there are two different img's, one as tar and the other as img. We actually need the img in the tar, which you have posted above. Thanks for posting this up.

guys thank you very much! i will try this and report results to the forum!

HELP!!
kenboyles72 said:
Nice, think I flashed the wrong boot.img from that thread, there are two different img's, one as tar and the other as img. We actually need the img in the tar, which you have posted above. Thanks for posting this up.
Click to expand...
Click to collapse
I tried the same procedure and my wifi will still not work!!!

thecomputerdude87 said:
I tried the same procedure and my wifi will still not work!!!
Click to expand...
Click to collapse
There are a couple things you can do here.
1. Try re-downloading the boot.img and reflashing with flashify
2. Try flashing the boot.img with Odin3
3. Restoring your phone with Kies http://forum.xda-developers.com/showpost.php?p=61977268&postcount=14
I rooted my phone and had to restore with kies three times before i got my wifi working. This is only if I switched to SuperSU, if you stay with kingroot, you wont have the wifi issue.

Help help help!
I did this and now my wifi won't turn on!! AT ALL

so the root metod its safe??? now there is another metod done from between Android using terminal emulator to switch from kingroot to chains fire super su! you have to be fully rooted to be able to work on terminal emulator.
but the root metod for sm g530az its safe?

flashing the stock kernel, do you click boot image or recovery image?
---------- Post added at 06:57 AM ---------- Previous post was at 06:18 AM ----------
OK, I got the wifi to turn back on by using the link above again.
I still cant get the wifi tether app to work, tho.
any suggestions?

well..happy to report that root on criket grand prime sm-g530az its a big...SUCCESS!!!
Im rooted on lollipop 5.1.1.
i do have cwm recovery but i need to flash it and see how it goes.for those with the Wi-Fi problem flash that boot image again.i have two one didn't work so i flash that second and Wi-Fi was working again.
Samsung bootlogo reports as "custom" so guaranty its gone
but I don't care abt that,im rooted thnx guys for sharing all that informacion!

I got the root to work with kingroot, but didn't do the 'optional' SU part, but now I want to.
Can anyone tell me what the step is with that zip file? do I download it directly to the phone? use Flashify? if I'm using flashify, do I flash it as a "boot image", a "recovery image" or a "zip file" ?
LOL talk to me like I'm five, please! I'm a noob at this. I'm smart at some things but this is a little overwhelming. LOL I'm a critical care nurse. I can fix a PERSON, but phones are a little more complicated :laugh:
---------- Post added at 03:39 AM ---------- Previous post was at 03:10 AM ----------
Oh OOH OOOHH!!!
Did that final step and the wifi tethering app WORKS!!!
WHOO HOOOOO!!!!
Thanks, wally, you are AWESOME!!

Root wifi teather
What wifi teather apk do yuo use?

hello try to this post :
http://forum.xda-developers.com/gra...t/cm-13-android-6-0-1-grand-prime-sm-t3291892
this post help you to install custom rom on grand prime sm-g530h and other . . .

adj5064 said:
well..happy to report that root on criket grand prime sm-g530az its a big...SUCCESS!!!
Im rooted on lollipop 5.1.1.
i do have cwm recovery but i need to flash it and see how it goes.for those with the Wi-Fi problem flash that boot image again.i have two one didn't work so i flash that second and Wi-Fi was working again.
Samsung bootlogo reports as "custom" so guaranty its gone
but I don't care abt that,im rooted thnx guys for sharing all that informacion!
Click to expand...
Click to collapse
Wait you have cwm compiled for our sm-g530az? That would be useful

Okay thanks a ton for the info, finally got my wifi back after flashing the correct boot.img, not sure where it was on the original forum never saw it but luckily others that had same issue posted it.
---------- Post added at 09:28 PM ---------- Previous post was at 09:26 PM ----------
Going to try to blow the dust off my builduntu box and see if I cant get us a recovery going for the cricket version, I usually like twrp but now that cwm has touch as well could go that route....is their a custom recovery built for the other variants at all yet....if so then forking those repos would be a good starting point, should only take minor edits to get it working proper for us.

toxinburn said:
Okay thanks a ton for the info, finally got my wifi back after flashing the correct boot.img, not sure where it was on the original forum never saw it but luckily others that had same issue posted it.
---------- Post added at 09:28 PM ---------- Previous post was at 09:26 PM ----------
Going to try to blow the dust off my builduntu box and see if I cant get us a recovery going for the cricket version, I usually like twrp but now that cwm has touch as well could go that route....is their a custom recovery built for the other variants at all yet....if so then forking those repos would be a good starting point, should only take minor edits to get it working proper for us.
Click to expand...
Click to collapse
I already built twrp for this phone, but as you found out, the damn security checks prevent the use of it. This is my device tree, can't remember if I pushed my last commits and I dont have what I had, due to a hdd failure.
https://github.com/LoneStar-/android_device_samsung_grandprimeltetu

kenboyles72 said:
I already built twrp for this phone, but as you found out, the damn security checks prevent the use of it. This is my device tree, can't remember if I pushed my last commits and I dont have what I had, due to a hdd failure.
https://github.com/LoneStar-/android_device_samsung_grandprimeltetu
Click to expand...
Click to collapse
So can you get a custom recovery working for this device? I have tried many ways but they all ended with my flashing stock img. twrp or cwm would be fine by me. Or another alternative is to find out how to disable the security check. Anyway please find a way to get custom recovery for 5.1.1 SM-G530AZ. Thanks

Illyakulinych said:
So can you get a custom recovery working for this device? I have tried many ways but they all ended with my flashing stock img. twrp or cwm would be fine by me. Or another alternative is to find out how to disable the security check. Anyway please find a way to get custom recovery for 5.1.1 SM-G530AZ. Thanks
Click to expand...
Click to collapse
Okay I think we should put our heads together to try and kick this lockdown to the curb, things I have tried so far...I found that on some other variants they have the option within their settings/developer settings menu to enable oem unlock which is what we are needing to be able to flash custom recovery, I have replaced my settings.jar and settings.odex with theirs with no luck the option is still not showing up for me, but I think it may be the right direction into getting that to show up, the question i am now posing is this. Are the checks in place simply reading carrier info to allow/disallow this option? If so would we possibly be able to change the build.prop or other settings with our newly found root access to trick the device into giving this option? If that is the case then we need to get as much info from the stock devices that have that option as possible and maybe try swapping certain files out with theirs to get the option back and/or editing certain files on our own device to get it to show up. It only takes one g530AZ with unlocked bootloader to share the boot.img i would think. I had thought about flashing another boot.img or aboot.img from another variant but I am pretty concerned about brickage although I think it could be recoverable as long as one can get back into download mode. Has anyone zeroed out the download partition to see if a fastboot is hidden behind it?

toxinburn said:
Okay I think we should put our heads together to try and kick this lockdown to the curb, things I have tried so far...I found that on some other variants they have the option within their settings/developer settings menu to enable oem unlock which is what we are needing to be able to flash custom recovery, I have replaced my settings.jar and settings.odex with theirs with no luck the option is still not showing up for me, but I think it may be the right direction into getting that to show up, the question i am now posing is this. Are the checks in place simply reading carrier info to allow/disallow this option? If so would we possibly be able to change the build.prop or other settings with our newly found root access to trick the device into giving this option? If that is the case then we need to get as much info from the stock devices that have that option as possible and maybe try swapping certain files out with theirs to get the option back and/or editing certain files on our own device to get it to show up. It only takes one g530AZ with unlocked bootloader to share the boot.img i would think. I had thought about flashing another boot.img or aboot.img from another variant but I am pretty concerned about brickage although I think it could be recoverable as long as one can get back into download mode. Has anyone zeroed out the download partition to see if a fastboot is hidden behind it?
Click to expand...
Click to collapse
Any progress?

Illyakulinych said:
Any progress?
Click to expand...
Click to collapse
Only thing I have done Is zeroed out the sec partition which caused non problem however it did no good either....also playing around with the databases and able to change some options just not the one in wanting yet...I work a ton son my freetime is limited but if anyone that has a different variant that could share their system apps primarily their settings all and databases and xml associated with it is really like to look through them.
Sent from my SAMSUNG-SM-G530AZ using Tapatalk

AT&T Samsung Galaxy S7 G930A Root Install Instructions?

If anybody can put up a step-by-step guide, or a video that shows how to properly install it all, I'm sure myself, and much of the community would appreciate it.
Recently, my laptop that I had ADB, and every tool imaginable for Androids, and specifically the Galaxy Series, took a huge dump on me and I lost it all. I installed it so long ago, that embarrassingly I've forgotten how I did it all. If someone could post how they rooted their GS7 (non-edge variant), I would be very appreciative. And I'm sure much of the community would be too. I'm embarrassed to even have to ask as someone who used to formerly develop mods on phones. But it is what it is. It's been so long since I've set it all up, and I've had to do so much since that time that I've simply forgotten how I did it/how to do it. Any help would be GREATLY appreciated. Thank you ahead of time...
I've tried following the instructions in the sticky above. I ran the 930X ROOT.TAR in the special version of ODIN. And every ran OK. It said "Success" and then rebooted. All seemed well, then it froze on the AT&T Boot Logo. What can I do from here? I know from history that this is one of the points that people panic and claimed "brick" (though I've never seen a real brick from rooting). Any help would be greatly appreciated

There's a great guide in the Verizon forum. Root was universal based on FW. Just make sure you flash the correct 930 or 935 with the modded odin. I recommend you follow the steps to "unroot" for the sake of doing an extremely in depth factory reset. Also make sure you get chain fires latest supersu built for the s7qc.
Sent from my SAMSUNG-SM-G930A using Tapatalk

twizt3d said:
There's a great guide in the Verizon forum. Root was universal based on FW. Just make sure you flash the correct 930 or 935 with the modded odin. I recommend you follow the steps to "unroot" for the sake of doing an extremely in depth factory reset. Also make sure you get chain fires latest supersu built for the s7qc.
Sent from my SAMSUNG-SM-G930A using Tapatalk
Click to expand...
Click to collapse
thank you for that. I'll check it out. Hopefully it'll get me past this bootscreen issue
yup. Great instructions. All set rooted now. Now time to play with xposed and V4A and the like. Yay

OK. Followed the instructions on the Verizon page and used the PrinceComsy version. Stuck at the AT&T logo. How did you go past this step? Should I have used the standard version? thanks

thanirs said:
OK. Followed the instructions on the Verizon page and used the PrinceComsy version. Stuck at the AT&T logo. How did you go past this step? Should I have used the standard version? thanks
Click to expand...
Click to collapse
(keep in mind this is only my personal experience...)
but the PrinceComsy version of ODIN was the only one to work for me. How far exactly have you gotten in the process before you got stuck at the logo? You do have ADB installed correctly installed on your PC and turned on on your phone right? and cd-ed the specific "super" folder for the SU adb install, right? FYI: It's not a simple root process, like 1-click roots on previous devices. This is more similar to the in-depth root methods like on the N1 and D1 before super nice devs went out of their way to make it simple. So if you're not familiar with ADB shell and the likes, it'll be difficult for you. But, no matter how high and mighty or condescending people act, we've all had to start somewhere. I'll help you get through the process as much as I can

Thanks for your reply. BTW I am fairly experienced in this stuff. This is what I did to get it to work. ADB and drivers all work fine.
Flashed the boot image using the PrinceComsy version. Got stuck at AT&T logo
Attempted to flash with the other version of Odin. When I open Odin, a window would pop-up with some ini issue and Odin would close immediately.
So I moved the ini file from PrinceComsy version to the other version. At this point, Odin would open and detect the phone at the correct COM port
Tried flashing it with this Odin but I got a SHA256 error
SO..
I went back to stock (which deletes all data, no big deal - everything was backed up)
Boot was successful
Re-flashed with the boot image and viola!
52brandon said:
(keep in mind this is only my personal experience...)
but the PrinceComsy version of ODIN was the only one to work for me. How far exactly have you gotten in the process before you got stuck at the logo? You do have ADB installed correctly installed on your PC and turned on on your phone right? and cd-ed the specific "super" folder for the SU adb install, right? FYI: It's not a simple root process, like 1-click roots on previous devices. This is more similar to the in-depth root methods like on the N1 and D1 before super nice devs went out of their way to make it simple. So if you're not familiar with ADB shell and the likes, it'll be difficult for you. But, no matter how high and mighty or condescending people act, we've all had to start somewhere. I'll help you get through the process as much as I can
Click to expand...
Click to collapse
---------- Post added at 08:47 PM ---------- Previous post was at 08:21 PM ----------
OK. Proceeding with the recommended steps in the install guide, I ran into this one nagging pop-up:
Security notice: Unauthorized actions have been detected. Restart your phone to undo any unauthorized changes.
Its a rather annoying notice that keeps popping up. What is the fix for this? Quick 'google' suggested some people uninstalling Knox altogether and it seemed fairly drastic. Suggestions?
thanirs said:
Thanks for your reply. BTW I am fairly experienced in this stuff. This is what I did to get it to work. ADB and drivers all work fine.
Flashed the boot image using the PrinceComsy version. Got stuck at AT&T logo
Attempted to flash with the other version of Odin. When I open Odin, a window would pop-up with some ini issue and Odin would close immediately.
So I moved the ini file from PrinceComsy version to the other version. At this point, Odin would open and detect the phone at the correct COM port
Tried flashing it with this Odin but I got a SHA256 error
SO..
I went back to stock (which deletes all data, no big deal - everything was backed up)
Boot was successful
Re-flashed with the boot image and viola!
Click to expand...
Click to collapse
---------- Post added at 09:08 PM ---------- Previous post was at 08:47 PM ----------
OK never mind please and sorry. Found the answer in the Fix/debloat script.

thanirs said:
Thanks for your reply. BTW I am fairly experienced in this stuff. This is what I did to get it to work. ADB and drivers all work fine.
Flashed the boot image using the PrinceComsy version. Got stuck at AT&T logo
Attempted to flash with the other version of Odin. When I open Odin, a window would pop-up with some ini issue and Odin would close immediately.
So I moved the ini file from PrinceComsy version to the other version. At this point, Odin would open and detect the phone at the correct COM port
Tried flashing it with this Odin but I got a SHA256 error
SO..
I went back to stock (which deletes all data, no big deal - everything was backed up)
Boot was successful
Re-flashed with the boot image and viola!
---------- Post added at 08:47 PM ---------- Previous post was at 08:21 PM ----------
OK. Proceeding with the recommended steps in the install guide, I ran into this one nagging pop-up:
Security notice: Unauthorized actions have been detected. Restart your phone to undo any unauthorized changes.
Its a rather annoying notice that keeps popping up. What is the fix for this? Quick 'google' suggested some people uninstalling Knox altogether and it seemed fairly drastic. Suggestions?
---------- Post added at 09:08 PM ---------- Previous post was at 08:47 PM ----------
OK never mind please and sorry. Found the answer in the Fix/debloat script.
Click to expand...
Click to collapse
so you got it all figured out and running great now right? No other issues right?

Just to add to this, I have verified that this still works using PG1.
http://forum.xda-developers.com/showpost.php?p=67970468&postcount=33

twizt3d said:
Just to add to this, I have verified that this still works using PG1.
http://forum.xda-developers.com/showpost.php?p=67970468&postcount=33
Click to expand...
Click to collapse
Can you please try restoring to af2?

Thanks for the ping. I think so. One thing I ran into which I don't know if its related to rooting. When I am in a phone conversation, audio on the other end goes in and out after a few minutes into the call. This happens with bluetooth or not. Still figuring out this issue.
52brandon said:
so you got it all figured out and running great now right? No other issues right?
Click to expand...
Click to collapse
Seeing battery drain. So went back to stock /unroot for now.

I was not trying to root my phone but reflash to an earlier version. I tried the Prince version of Odin and it did not work. The version that ended up working is in this thread
http://forum.xda-developers.com/att-galaxy-s7/how-to/firmware-g930a-edge-variant-afp-stock-t3415344
http://click.xda-developers.com/api...ww.mediafire.com/download/2t...din_3.12.3.rar

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.