Related
Hey folks
Updated my N700 rom to the version listed in the title (which I got here) and it comes with CWM's SuperUser installed as sys app.
I have the following problem: it says outdated binary and I can't install them or update them. Of course since it's a sys app I can't delete and try to use Chainfire's SuperSU which is the one I prefer. And I don't have root access now, can't restore my Titaium Backups and such.
Downloaded the "fix" from CWM's Market links and reinstalled the app manually but I keep getting the same problem: no SuperUser binary installed and no root access.
Thanks in advance!
Try flashing the supersu zip file that's used for rooting. Or better, try flashing xxlsz Philz kernel zip from recovery.
flashed the supersu.zip and still no luck, will dig for PhilZ kernel now.
http://forum.xda-developers.com/showthread.php?t=1538053
Just flashed Sinless ROM and although it came with SuperSU by chainfire. I decided I wanted to remove it and install superuser by clockworkmod instead. For some reason superuser app didn't actually root the system, so I attempted to uninstall it and reinstall SuperSU. This is where I'm stuck. I cannot remove superuser app no matter what I try, even deleting it with a file manager or disabling the app. Anyone have any ideas? Really need my root back. Thanks
One Hype said:
Just flashed Sinless ROM and although it came with SuperSU by chainfire. I decided I wanted to remove it and install superuser by clockworkmod instead. For some reason superuser app didn't actually root the system, so I attempted to uninstall it and reinstall SuperSU. This is where I'm stuck. I cannot remove superuser app no matter what I try, even deleting it with a file manager or disabling the app. Anyone have any ideas? Really need my root back. Thanks
Click to expand...
Click to collapse
If it's in /system, you need root to remove it (which you don't have). I suggest going into recovery and then flashing Superuser with the SU binaries that allows root to work.
Link to ClockworkMod's Superuser: http://download.clockworkmod.com/superuser/superuser.zip
KiraYahiroz said:
If it's in /system, you need root to remove it (which you don't have). I suggest going into recovery and then flashing Superuser with the SU binaries that allows root to work.
Link to ClockworkMod's Superuser: http://download.clockworkmod.com/superuser/superuser.zip
Click to expand...
Click to collapse
Tried this and that is what I am attempting to remove from the system to no avail. Anything else I can try? I don't know why it won't give superuser access either.
One Hype said:
Tried this and that is what I am attempting to remove from the system to no avail. Anything else I can try? I don't know why it won't give superuser access either.
Click to expand...
Click to collapse
So flashing that zip didn't flash the SU binaries either?
Try flashing this then: http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip
The main important thing is to get the SU binaries installed to allow the superuser apps to work. Once you have that installed try to change superuser apps again (do not choose the full remove option as that will also remove the SU binaries).
Another option is to try flash the ROM again.
KiraYahiroz said:
So flashing that zip didn't flash the SU binaries either?
Try flashing this then: http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip
The main important thing is to get the SU binaries installed to allow the superuser apps to work. Once you have that installed try to change superuser apps again (do not choose the full remove option as that will also remove the SU binaries).
Another option is to try flash the ROM again.
Click to expand...
Click to collapse
Just did this buy with v.1.8 of SuperSU and everything worked perfect. Thank you
This patcher is now outdated. Use the new SuperSU instead. http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
This zip is a systemless version. That means that you'll get root and be able to use it normally, but your system partition will not be modified, like in normal root methods. Only for Marshmallow.
Keep reading for disadvantages and advantages
Chainfire had released a newer version of his SuperSU that doesn't need to modify the system partition to provide root access. This method doesn't have much of a practical application right now, but it allows you to flash OTA updates without having to unroot or flash the stock system partition.
HOW TO USE:
If you have rooted before, flash the system partition (or reinstall the ROM) before flashing this zip.
Download the attached zip, and flash it from a recovery (I tested it with TWRP).
Download SuperSU 2.56 from here: http://forum.xda-developers.com/showpost.php?p=63197935&postcount=2 (Just download the apk)
Reboot to TWRP. If it asks you whether you want system to be mounted as r/w, and if you want to take OTAs later, choose to keep system read-only (this will replace TWRP with stock recovery on reboot).
Flash SuperSU-v2.56-20151030013730.zip
Reboot
TWRP will say that you are not rooted, just ignore that. Do not tell it to root it.
This will work with all Marshmallow kernels, even the stock kernel.
Drawback : A factory data reset will remove superuser privileges. If that happens, simply flash SuperSU-v2.56-20151030013730.zip again.
TO RECEIVE OTA UPDATES :
Just make sure not to do anything that modifies /system. For example, no build.prop changes, and no system app removal. Or even if you do these, make sure to undo these changes before flashing an OTA. You can flash OTAs without unrooting now.
Flash the stock boot.img for your current Android version before flashing OTAs.
BUGS :
I didn't find any, yet, but Chainfire wrote the following on his thread:
Apps with hardcoded paths to su (seriously?) will bork
Factory reset unroots
Factory reset wipes pin
...
Bugs... Bugs everywhere!
ADDITIONAL INFO :
This zip will replace sepolicy as mentioned on Chainfire's thread (thanks to @metaspook for the patched sepolicy, which I extracted from his zip), so you'll be able to get root access even on SELinux enforcing kernels (only the stock MM kernels right now). Also, you can flash any other kernel (as long as it comes in a zip format, not as an img) before or after flashing this, and you'll still have root access.
out386 said:
Chainfire had released a newer version of his SuperSU that doesn't need to modify the system partition to provide root access. This method doesn't have much of a practical application right now, but it allows you to flash OTA updates without having to unroot or flash the stock system partition.
HOW TO USE:
Download the attached zip, and flash it from a recovery (I tested it with TWRP).
Download SuperSU 2.56 (or newer, if it supports systemless mode) from here: http://forum.xda-developers.com/showpost.php?p=63197935&postcount=2 (Just download the apk)
Flash SuperSU-v2.56-20151030013730.zip
Reboot
This will work with all Marshmallow kernels, even the stock kernel.
Drawback : A factory data reset will remove superuser privileges. If that happens, simply flash SuperSU-v2.56-20151030013730.zip again.
TO RECEIVE OTA UPDATES :
Just make sure not to do anything that modifies /system. For example, no build.prop changes, and no system app removal. Or even if you do these, make sure to undo these changes before flashing an OTA. You can flash OTAs without unrooting now.
Flash the stock boot.img for your current Android version before flashing OTAs.
BUGS :
I didn't find any, yet, but Chainfire wrote the following on his thread:
Apps with hardcoded paths to su (seriously?) will bork
Factory reset unroots
Factory reset wipes pin
...
Bugs... Bugs everywhere!
ADDITIONAL INFO :
This zip will replace sepolicy as mentioned on Chainfire's thread (thanks to @metaspook for the patched sepolicy, which I extracted from his zip), so you'll be able to get root access even on SELinux enforcing kernels (only the stock MM kernels right now). Also, you can flash any other kernel (as long as it comes in a zip format, not as an img) before or after flashing this, and you'll still have root access.
Click to expand...
Click to collapse
Well done bro!
I'm just waiting for this
Help regarding installation
I am using MicroMax Android One with Marshmallow
Currently, I've not tired the phone.
When I open recovery, I see some options like Apply update from SD card, mount, cache wipe, factory reset, etc.
So which option should I use to flash the zip file.
out386 said:
Chainfire had released a newer version of his SuperSU that doesn't need to modify the system partition to provide root access. This method doesn't have much of a practical application right now, but it allows you to flash OTA updates without having to unroot or flash the stock system partition.
HOW TO USE:
Download the attached zip, and flash it from a recovery (I tested it with TWRP).
Download SuperSU 2.56 (or newer, if it supports systemless mode) from here: http://forum.xda-developers.com/showpost.php?p=63197935&postcount=2 (Just download the apk)
Flash SuperSU-v2.56-20151030013730.zip
Reboot
This will work with all Marshmallow kernels, even the stock kernel.
Drawback : A factory data reset will remove superuser privileges. If that happens, simply flash SuperSU-v2.56-20151030013730.zip again.
TO RECEIVE OTA UPDATES :
Just make sure not to do anything that modifies /system. For example, no build.prop changes, and no system app removal. Or even if you do these, make sure to undo these changes before flashing an OTA. You can flash OTAs without unrooting now.
Flash the stock boot.img for your current Android version before flashing OTAs.
BUGS :
I didn't find any, yet, but Chainfire wrote the following on his thread:
Apps with hardcoded paths to su (seriously?) will bork
Factory reset unroots
Factory reset wipes pin
...
Bugs... Bugs everywhere!
ADDITIONAL INFO :
This zip will replace sepolicy as mentioned on Chainfire's thread (thanks to @metaspook for the patched sepolicy, which I extracted from his zip), so you'll be able to get root access even on SELinux enforcing kernels (only the stock MM kernels right now). Also, you can flash any other kernel (as long as it comes in a zip format, not as an img) before or after flashing this, and you'll still have root access.
Click to expand...
Click to collapse
Good work n thanks for mention bt can't understand why u created a patcher again where I'v already created one!
Its ok, good job.
Good.... Thanks for posting
metaspook said:
Good work n thanks for mention bt can't understand why u created a patcher again where I'v already created one!
Its ok, good job.
Click to expand...
Click to collapse
Yes, well, I would never have reposted the same thing, so, I'm sorry if it seemed like that.
This one uses Chainfire's new systemless root method. Unlike other root methods that need modifications to /system, this method uses modifications to the boot image to set up and run the su daemon from a loop device on the /data partition and achieve root. Right now, that doesn't have much of an advantage except to make flashing OTAs easier. Chainfire made it because future devices might need it. I made the patch because someone on FB asked about it.
<accidental double post, sorry. Can't delete>
kalpitandroid said:
I am using MicroMax Android One with Marshmallow
Currently, I've not tired the phone.
When I open recovery, I see some options like Apply update from SD card, mount, cache wipe, factory reset, etc.
So which option should I use to flash the zip file.
Click to expand...
Click to collapse
You need to install a custom recovery first. Go to the Android One (First generation) General forums on this site. You'll find a how-to at the very top of the list of threads. Once you have a custom recovery, flash this using the "install zip" option.
out386 said:
Yes, well, I would never have reposted the same thing, so, I'm sorry if it seemed like that.
This one uses Chainfire's new systemless root method. Unlike other root methods that need modifications to /system, this method uses modifications to the boot image to set up and run the su daemon from a loop device on the /data partition and achieve root. Right now, that doesn't have much of an advantage except to make flashing OTAs easier. Chainfire made it because future devices might need it. I made the patch because someone on FB asked about it.
Click to expand...
Click to collapse
Hmm... gotcha now.. Good work!
If u ever need any help just pm.
Thank you...
out386 said:
<accidental double post, sorry. Can't delete>
Click to expand...
Click to collapse
**** The posted systemless kernel is only compatible with SuperSU 2.56!!! ****
*** Starting with SuperSU 2.60+ kernel can now be auto-patched for systemless root. ***
**As of 06 December 2015 flar2 has released ElementalX 6.02 for Sense Marshmallow **
* If you still desire a stock kernel with systemless root but want to use newer SuperSU see below *
Messed around with the boot.img from today's Marshmallow update and have made it compatible with systemless root.
Systemless root in general is experimental and so is the kernel. I've literally just made it and tested it enough to that it boots and apps are able to be granted root access, so flash at your own risk.
Kernel has been running without issue.
Other than systemless root compatibility, this kernel is completely stock and no other modifications made.
Intructions - Systemless:
Download kernel from here.
Download SuperSU 2.56 beta from this post (only one that works with this method of root).
Copy both to phone
Flash the image directly using TWRP (toggle from ZIP to IMG under install)
Immediately flash SuperSU-v2.56-20151030013730.zip afterwards.
Reboot
TWRP will notify of no SU when you reboot, click DO NOT INSTALL as TWRP needs to be updated to detect this root method (it only looks in /system)
Instructions - Traditional:
Download kernel from here.
Download SuperSU 2.52 beta from this thread (it's the M compatible version)
Copy both to phone
Flash the image directly using TWRP (toggle from ZIP to IMG under install)
Immediately flash BETA-SuperSU-v2.52.zip afterwards.
Reboot
Keeping stock kernel with updated SuperSU:
If you prefer running the stock kernel with systemless root and want to stay current on SuperSU versions you need a stock kernel when you update SuperSU. When SuperSU installs it tries to restore a backup it made of your boot.img from the last time SuperSU was installed. Since this was made before auto patching there won't be a backup. Also, in newer versions it detects if your device needs systemless or if it can modify /system. If TWRP hasn't been told to keep system read-only it will likely default to a /system install. So, if you want to keep stock kernel and systemless root there are two things you are going to need:
Stock Kernel: You can actually use the kernel provided for traditional root as a stock kernel for the purpose of these instructions.
Systemless Override: To guarantee that SuperSU gives you the systemless install over /system you need to create a file called ".supersu" with the line "SYSTEMLESS=true" and place it in /data in TWRP before you install (eg. /data/.supersu). Alternatively, you can download this one (extract from the ZIP and place in /data).
When the file is placed in /data flash the boot.img in TWRP and then flash SuperSU. It will make a backup when it installs so don't remove it as it will look for this backup again when you install an updated version.
Note: These are only to tide us over until HTC releases source allowing awesome devs like flar2 to work their kernel magic.
Not checked yet, but is systemless the only way to do it on 6.0 ?
Electronic Punk said:
Not checked yet, but is systemless the only way to do it on 6.0 ?
Click to expand...
Click to collapse
No, you can still do it by modifying /system, but Marshmallow made it so kernels had to be modified as well to allow root. @Chainfire took it a step further, since we already have to modify the boot.img we can modify it a little more and remove the need to alter /system and make it easier to accept OTA updates. The link I put in the OP explains it a little more, but here it is again.
Added root modified kernel for using "traditional" (modifies /system) root to the OP along with link to current Marshmallow compatible SuperSU.
I'm trying to do a systemless root. Just to confirm, I should flash the latest TWRP. Then from there flash the kernel then SuperSU both through TWRP?
mcta said:
I'm trying to do a systemless root. Just to confirm, I should flash the latest TWRP. Then from there flash the kernel then SuperSU both through TWRP?
Click to expand...
Click to collapse
If you still have stock kernel and no root you can just flash the latest SuperSU (v2.65).
If you're systemless already but don't have a backup you need to flash a boot.img that isn't already systemless modified as SuperSU will abort the install.
You can't flash the one in the OP for traditional (modifies /system) root and it will patch that one, but unless your set your /system partition to read-only, it will install using traditional root (this is the case with any unmodified boot.img not just this one because it's modified for traditional root). To make sure SuperSU installs using systemlesss you need to place the mentioned .supersu file in /data/ o make sure system is read-only in twrp. You also want to use latest SuperSU.
Just make sure you don't let TWRP install it's own SuperSU package that it includes. TWRP by default can't detect systemless root installs, so each time you reboot from TWRP it will warn that there is no root access on the device. It is important you make sure to click DO NOT INSTALL.
If you don't want to be bugged with the no root message in TWRP you can download this version which has the incompatible SuperSU package removed disabling the root check.
HAHAHAHAHA!!!!! Silly me...... it was written up there......
mcta said:
I'm trying to do a systemless root. Just to confirm, I should flash the latest TWRP. Then from there flash the kernel then SuperSU both through TWRP?
Click to expand...
Click to collapse
Okay, hopefully this is a stupid question, but I want to be sure before I flash something to boot.
I followed the instructions before the later versions of SuperSU betas came out, so I have the above linked custom boot image, but would like to be able to update to later versions. Can I safely assume that the boot_signed.img file I pulled out of ROM.ZIP in the Developer Edition Marshmallow RUU is the correct "stock" bootloader? Note that I ran the RUU, let it pause on accepting the license, then pulled the ROM.ZIP out of the temp folder to extract the binary.
Hi! Im pretty much new to rooting and I was wondering does the phone have to be S-OFF or S-ON. If it has to be S-OFF, how do you do it?
Thank you for help!
Ok guys here is a custom recovery for the metro 2016 variant of the Galaxy J700t1 (Metro PCS) Flash with FlashFire or with Odin. Custom recovery but it won't mount the internal sd yet. Can't flash or backup.. so its still a work in progress, but its a working recovery other than that lol. Must be rooted first. Make sure that you download root file explorer and ensure you have a copy of su and busybox in your /system/bin and /system/xbin folders. Make sure you have USB debugging on, OEM on, and unknown sources on in System-Developer options. Thanks to Paco for the root exploit! But we needed a recovery for this fine device. Enjoy!
EDIT: SOME CLARITY FOR EVERYONE... ok, so here's the deal. In marshmallow the system is write protected after you trip KNOX 0x1. The system will persist and will lose integrity if the stock kernel's "CASHE" gets changed. hmmm.... so. this is what you need your system to be at if you want to flash a custom kernel or recovery with flashfire or flashify: After you root with Paco's method, you should be on stock rooted rom with stock recovery. when you flash with flashfire DO NOT WIPE CASHE OR DALVIK CASHE OR FORMAT CASHE in ANY WAY ... IT WILL SEND YOU INTO THE "RESET MODE"... NO worries tho. If this happens to you , ODIN this stock kernel CASHE that i'm posting below and you should boot back up. Keep in mind what you're doing as well... if for some reason you hit the "RESET" SCREEN, don't flip... just ODIN the partition you changed back to stock whether it be the kernel or in this case the RECOVERY. ... also, try not to use ever root in flashify/ flashfire because it lowers the permissions for the SU binaries and removes SU from some of the system folders.
INSTRUCTIONS:
1. start from stock if you can.
2.root via paco's method HERE
3.I would make sure you have a stock copy of the stock firmware (ROM KERNEL RECOVERY) on your computer just in case
HERE
4.download my cwm port for the j700t1 below and put it on the root of your drive or anywhere on your phones internal memory (not your external sd card)
5. Download root browser from the playstore as well as flashfire or flashify or both.
6.rename the cwm.img to recovery.img with root browser and ensure that you have SU and Busybox in /system/bin , /system/xbin , and it wouldn't hurt to have it in ~#/sbin as well..... AND check the permissions with root browser to make sure the permissions are set to 0777 (rwrwrwrw)
7. In "Flashfire" click the "+" symbol - click "Flash firmware package" -- Go to the cwm "recovery" file you put on your internal sd card and select the file. Fireflash will bring a screen up saying "Partitions" at the top showing the package. Click the check mark at the top right. FlashFire will go back to the "Actions" screen. Click"reboot" toward the bottom. Under the "reboot" screen, click recovery to boot directly into your new recovery after the flash. Uncheck Preserve recovery- click the check mark at the top right again. Click "Flash" at the bottom. --- wait. Device will reboot... flashfire will take over and your loading screen willl flash by... phone will boot back up into CWM....
To Flash ODIN tars --- Rename the perspective tar to the partition it goes to before trying to odin. Example: rename "cwm.recovery.img." to just "recovery.img" ... Same with the stock kernel tar below. . rename to "boot.img" then ODIN.
Sideload apps or ROMS or ZIPS just don't wipe any cashe partitions until we can get a good custom kernel. I could use the help with the kernel I will be honest. I can get it done but with a lot of trial and error. Anyone who can remove the SELinux write protection from the kernel please contact me.. I'm working on it. I was able to get a custom kernel to boot. but still no r/w mount for the USB yet. Just keep the CASHE lol. One more thing.. if your'e testing kernels, everytime you have to odin a stock kernel you will LOSE ROOT, so go ahead and re-root again.
https://drive.google.com/file/d/0B_WsJ57QBykaQ3ROeFZnajNzbmc/view?usp=sharing --- CWM img
CWM.TAR-- (new
--Stock Kernel CASHE.tar
Stock KERNEL
Team Rejectz
removed as it was reported not working by @timmetal6669
messi2050 said:
I worked on the kernel you asked for , i hope that it will help you getting a working twrp for your phone
Permissive kernel
https://www.mediafire.com/download/gd51y458vkzwmve
Completely disabled selinux kernel
https://www.mediafire.com/download/ui6udkamk1dkqq4
Click to expand...
Click to collapse
thank you!! the one I sent you? will flash right away
timmetal6669 said:
thank you!! the one I sent you? will flash right away
Click to expand...
Click to collapse
You are welcome ! No i didn't recieve anything , I compiled this one
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=Sm-j700t
messi2050 said:
I worked on the kernel you asked for , i hope that it will help you getting a working twrp for your phone
Permissive kernel
https://www.mediafire.com/download/gd51y458vkzwmve
Completely disabled selinux kernel
https://www.mediafire.com/download/ui6udkamk1dkqq4
Click to expand...
Click to collapse
not working...
do not flash this
Here is an odin flashable copy of the j700t1 stock kernel to get you booting again. just go into download mode, open odin and flash this if you happened to flash one of the kernels above
https://drive.google.com/open?id=0B_WsJ57QBykaSDRlQXlXSnpSd28
messi2050 said:
You are welcome ! No i didn't recieve anything , I compiled this one
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=Sm-j700t
Click to expand...
Click to collapse
No wonder it looped, we are the j700t1 variant.... Grab this stock boot.img i just posted above and see what you can do it with this instead lol.:good:
timmetal6669 said:
No wonder it looped, we are the j700t1 variant.... Grab this stock boot.img i just posted above and see what you can do it with this instead lol.:good:
Click to expand...
Click to collapse
Hmmm.... 2 members tested the first one and the phone booted up correctly , i can't disable selinux from the bootimage as Samsung is forcing selinux in the kernel , i need to build the kernel from source to do that
messi2050 said:
Hmmm.... 2 members tested the first one and the phone booted up correctly , i can't disable selinux from the bootimage as Samsung is forcing selinux in the kernel , i need to build the kernel from source to do that
Click to expand...
Click to collapse
Sent me into a loop... but I'm the metro pcs variant
Oh update... If anyone uses that odin flashable stock boot.img .. remember it IS a stock boot img. you will lose root. but you won't lose your system and your apps.. so just re root using paco's CF autroot exploit.
messi2050 said:
Hmmm.... 2 members tested the first one and the phone booted up correctly , i can't disable selinux from the bootimage as Samsung is forcing selinux in the kernel , i need to build the kernel from source to do that
Click to expand...
Click to collapse
might just be what i'll have to do.. the boot image is its own source
So no progress on the recovery to backup or flash yet?
Krumplife4400 said:
So no progress on the recovery to backup or flash yet?
Click to expand...
Click to collapse
Im working on it. the recovery is flashable and it works... just won't mount the SD right now... I have to right a script or look for a work around.. give me a bit...might take a few days. I'm a single dad and im' in school. I do this cuz i love it and I just bought this phone... Don't worry.,.. I'll be making ROMs before you know it... lol... mods everything... look up my threads lol
Thanks keep up the good work
Are you able to mount USB-OTG?? I am about to leave work so I haven't had a chance to play yet!
I can confirm it boots on j700t as well. I haven't flashed anything but it's there. I got twrp to boot and stay for roughly 5 minutes but still cannot mount anything either.
Sent from my SM-J700T using XDA-Developers mobile app
Verification Failed
I got this after flashing the cwm.img in FF. I did rename it to recovery.img is that why it failed? I could not get odin or FF to actually attempt a flash otherwise. Odin failed attempt NANDWRITE and FF complains about partition matching. I did have su and BB in the /system/bin and /system/xbin folders. Busybox permissions were 0777 and su permissions were 0755
Edit: i just rebooted the device and it booted right up. I tried to reboot recovery and it was back to stock so idk . I am definitely missing a step somewhere..
!Led*Eyes! said:
I got this after flashing the cwm.img in FF. I did rename it to recovery.img is that why it failed? I could not get odin or FF to actually attempt a flash otherwise. Odin failed attempt NANDWRITE and FF complains about partition matching. I did have su and BB in the /system/bin and /system/xbin folders. Busybox permissions were 0777 and su permissions were 0755
Edit: i just rebooted the device and it booted right up. I tried to reboot recovery and it was back to stock so idk . I am definitely missing a step somewhere..
Click to expand...
Click to collapse
Start over.
Set up phone like day one
Re-root with cf auto root
Update su binaries
Install BusyBox
Install flashify
Download IMG from op
After download, tap on IMG file should bring up flashify as an option
Flash IMG and reboot
Profit.
- I see you're good but no cwm? Skip start over root part and use flashify.
-sent from this device using this app.
So flashify over flashfire ? Ill give it a shot. Thanks
!Led*Eyes! said:
So flashify over flashfire ? Ill give it a shot. Thanks
Click to expand...
Click to collapse
No problem
sent from the interwebs using dis here application an m'digits....
I decided to just try it with flashify without reverting everything back to stock and voila! I chose the google drive option when searching for the file so it did download it again.... i re member reading something a while back about about a similar issue with not being able to mount the sdcard because the fs was encrypted and the recovery couldnt read it. I think they overcame by formatting the sdcard but i do not know .. i realize that simply formatting the sd in recovery and trying to mount would be fruitless but could the trouble be in the "expected recovery key" ? Just a thought. Thanks again timmetal6669 & OriginalShinken1 for the beta and the help. You guys are so close!
Has anyone tried to sideload a ROM yet since we can't flash?