Database Develop

[Q] su freezes programs asking for root access, need fix.

I have a Samsung Galaxy Ace from Telcel in Mexico running CyanogenMod 7.2.0 stable, using Link2SD and ClockworkMod 5.0.2.7 (I think, will edit later).
As of lately I've been getting some random weird behavior with su. Every now and then, it will cause any app asking for root access to freeze, and after much wailing and desperate fiddling the only way I could fix it was by restoring a known-good Clockwork backup. It's been happening for about a week already about every 2 days or so and I am sick and tired of having to restore backups all the time.
Is there a way to manually fix su without having to restore an older backup? If not or if I am completely in the wrong, then just what is going on?

Did you update su binary?
Sent from my GT-S5830 using xda premium

Some time ago I updated my su binary to the latest version.
If this is the problem, is there a way to downgrade su? I have previously tried to look for a way to do it but found nothing.

download superSu from the market . i was having the same problem and for me is work now...good luck

OK, I just tried running SuperSU. It didn't work, when I start it it says I should update my su binary and then it gets stuck forever trying to install it.
I can't do it right now because I'm at work, but I'm thinking about something like this to downgrade su:
Make a CWM backup
Extract the backup's system.tar under Linux on my desktop computer (not Windows because that would break the files' UNIX-like attributes).
Replace the current su binary with an older su from a previous backup.
Repack and recalculate the MD5 hashes
Flash the modded backup with CWM
Since it won't be until 8 hours later that I'll have a chance to test it, what could possibly go wrong?

Da_Nuke said:
OK, I just tried running SuperSU. It didn't work, when I start it it says I should update my su binary and then it gets stuck forever trying to install it.
I can't do it right now because I'm at work, but I'm thinking about something like this to downgrade su:
Make a CWM backup
Extract the backup's system.tar under Linux on my desktop computer (not Windows because that would break the files' UNIX-like attributes).
Replace the current su binary with an older su from a previous backup.
Repack and recalculate the MD5 hashes
Flash the modded backup with CWM
Since it won't be until 8 hours later that I'll have a chance to test it, what could possibly go wrong?
Click to expand...
Click to collapse
Just replace it manually.MD5 might create some problems otherwise.Or have you tried that already?
Insert witty sentence here

[WARNING] - Before you root!

Before you root your LG Revolution:
Install the latest USB driver software
http://www.lg.com/us/support-mobile/lg-LGVS910
===============
You MUST do this.
===============
All Credit goes to das7982,
I just found the answer.
___________________
use root explorer and go into
system/etc/ and delete the file called
install-recovery.sh
Why? BECAUSE Clockwork will not work without deleting the install-recovery.sh
because it is a shell script designed to over write any new recovery you try to flash over it.
THEN ROOT:
Download
http://forum.xda-developers.com/showthread.php?t=1348557
Extract and run "V8 all in one root + CWM"
and choose install root and CWM and viola.

Generally I would move this thread as a duplication, however, until the OP of the root tools adds this in his first post, I'll let it stay.
The install-recovery.sh and on other devices boot-recovery.p are previously known issues which cause the installed custom recoveries to get overwritten when booting back into a stock rom. This file should be deleted after root, and before installing a custom recovery, unless you plan to boot immediately into Custom Recovery and install a custom rom.
The issue, is you have to ROOT FIRST and gain /System RW.
So the title should be "Before you install CWM". (not sure how the root tool works if you can just root only, or if the author can add the cmd to delete this file when rooting and installing CWM. Should be able to somehow. They do it in the 500 forum)
But sometimes people miss this 1 little step, so the thread will remain.
Rock On!
MD

I thought this thread was a joke because to root your phone via PC you have to install the drivers so ADB can even see the hardware...

Lol
I was gonna say who has a revo that is not rooted.

This makes sense. Bcuz of the .p file or the install-recovery.sh, the aio's repeatedly fail at fully installing cwm. If you push cwm directly from the device, you don't even have to mess with the .p or the install-recovery.sh.
Regardless of anything, It's a good find KangKilla. Awesome clarification MD.

Can't Root Galaxy Mini (GT-S5570)

Hi
I've a Galaxy Mini with XWTN firmware (flashed via ODIN from here )
I had them with the stock recovery and without root, but due to the low memory I wanted to root them for install a sd-ext partition. I did these steps:
- Replaced the stock recovery with this and next with this
-Formatted the sd card using CWM for create a 256 MB sd-ext partition
- Attempted to root the phone flashing Universal_gb_root_v25.zip and Upd_1.zip. The two files failed and CWM show me an error status 7. Also I used SuperOneClick 2.3.3, but doesn't work
- I looked into the updater-script of flashable zips and I noticed that the "Universal_gb_root_v25.zip" updater-script contains a reference to "ro.product.device=GT-S5570L". I looked into the build.prop of my ROM and I noticed that "ro.product.device" is GT-S5570, not GT-S5570L. So, I edited the updater-script into the zip for match "GT-S5570", thinking I could solve the problem, but CWM continues to show me an status 7 error. The other zip I tried, "Upd_1.zip", have the "ro.product.device=GT-S5570" in their updater-script, but CWM show the error anyway.
Considering that these zips are for flash with stock recovery, and I'm using CWM, maybe if I use the stock recovery the zips works? Is there a way to back to stock recovery without flashing the whole rom in ODIN again? (due to data lose)
Thanks.

xsam123 said:
Hi
I've a Galaxy Mini with XWTN firmware (flashed via ODIN from here )
I had them with the stock recovery and without root, but due to the low memory I wanted to root them for install a sd-ext partition. I did these steps:
- Replaced the stock recovery with this and next with this
-Formatted the sd card using CWM for create a 256 MB sd-ext partition
- Attempted to root the phone flashing Universal_gb_root_v25.zip and Upd_1.zip. The two files failed and CWM show me an error status 7. Also I used SuperOneClick 2.3.3, but doesn't work
- I looked into the updater-script of flashable zips and I noticed that the "Universal_gb_root_v25.zip" updater-script contains a reference to "ro.product.device=GT-S5570L". I looked into the build.prop of my ROM and I noticed that "ro.product.device" is GT-S5570, not GT-S5570L. So, I edited the updater-script into the zip for match "GT-S5570", thinking I could solve the problem, but CWM continues to show me an status 7 error. The other zip I tried, "Upd_1.zip", have the "ro.product.device=GT-S5570" in their updater-script, but CWM show the error anyway.
Considering that these zips are for flash with stock recovery, and I'm using CWM, maybe if I use the stock recovery the zips works? Is there a way to back to stock recovery without flashing the whole rom in ODIN again? (due to data lose)
Thanks.
Click to expand...
Click to collapse
I think, you have followed the tutorial of rooting wrongly..
If you wanna root your mini, you can try this tutorial..

xsam123 said:
Hi
I've a Galaxy Mini with XWTN firmware (flashed via ODIN from here )
I had them with the stock recovery and without root, but due to the low memory I wanted to root them for install a sd-ext partition. I did these steps:
- Replaced the stock recovery with this and next with this
-Formatted the sd card using CWM for create a 256 MB sd-ext partition
- Attempted to root the phone flashing Universal_gb_root_v25.zip and Upd_1.zip. The two files failed and CWM show me an error status 7. Also I used SuperOneClick 2.3.3, but doesn't work
- I looked into the updater-script of flashable zips and I noticed that the "Universal_gb_root_v25.zip" updater-script contains a reference to "ro.product.device=GT-S5570L". I looked into the build.prop of my ROM and I noticed that "ro.product.device" is GT-S5570, not GT-S5570L. So, I edited the updater-script into the zip for match "GT-S5570", thinking I could solve the problem, but CWM continues to show me an status 7 error. The other zip I tried, "Upd_1.zip", have the "ro.product.device=GT-S5570" in their updater-script, but CWM show the error anyway.
Considering that these zips are for flash with stock recovery, and I'm using CWM, maybe if I use the stock recovery the zips works? Is there a way to back to stock recovery without flashing the whole rom in ODIN again? (due to data lose)
Thanks.
Click to expand...
Click to collapse
First...you were supposed to root first and then replace the recovery...
Second...I didnt wanted to thanks...
Sent from my GT-S5570 using xda app-developers app

Try flashing a custom rom in your phone They usually comes up with a super user access (it means that you are rooted )
[ROM][CM7.2][ODEXED][30-04-2013] New Experience v9.8.0 - xda-developers
http://forum.xda-developers.com/show....php?t=1648213
This rom also comes up with many scripts/tweaks!
This is the one that I'm using
Im not saying its the best, there are many roms that have different features !
Please press thanks if I helped!

[MM] [Flashable] Patcher to provide root access without /system modification

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

CWM RECOVERY for Galaxy J700t1 (Metro PCS variant)

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?