Develop Bugs

problem getting perm root

im using the rage method and everything worked up until after i used the command gfree - f.
then i input the command sync followed by /data/local/tmp/root, this is what i get
# /data/local/tmp/root
link_image[1995]: failed to link /data/local/tmp/busybox
CANNOT LINK EXECUTABLE
mkdir failed for /system/xbin, File exists
link_image[1995]: failed to link /data/local/tmp/busybox
CANNOT LINK EXECUTABLE
Unable to chmod /system/xbin/busybox: No such file or directory
/data/local/tmp/root: /system/xbin/busybox: not found
cp: not found
cp: not found
Unable to chmod /system/bin/su: No such file or directory
#

if I were you, you should use gfree method... or unfrogivens way
Sent from my HTC Vision using XDA Premium App

I used rage to get temp root, and using gfree but during the last execution, it doesn't work and that's the message I get back
Sent from my T-Mobile G2 using XDA App

This problem sounds familiar, let me look at previous threads I have participated in and see if I can find anything useful
FYI, /data/local/tmp/root is a script that copies busybox and does other root functions.
I'm guessing that the gfree part did work, you can verify this by rebooting into the bootloader and seeing if you have S-OFF
If you are only looking to flash a custom ROM you don't even need to worry about this issue (as long as you do have S-OFF), all you'd need to do is obtain temp root again (using rage or even visionary) then install ClockWorkMod Recovery (I'd recommend using this method), once you have that you can boot into recovery and flash any pre-rooted ROM you want.
Eidt: I found the post I was thinking of, seems like this guy had a similar problem running /data/local/tmp/root
http://forum.xda-developers.com/showthread.php?p=11215689#post11215689
My advice still stands, if you have S-OFF and can get CWM flashed onto your phone (should be able to with temp root) you can flash a custom ROM (which will be pre-rooted) or flash a pre-rooted stock ROM (see this thread)

Hey there,
today I tried to get perma root and followed the guide from cyanogenmod
everything runs great till step 5 in Gaining Permanent Root Access & More
when I enter:
/data/local/tmp/root
I receive the message like nguyenhoanggg described..
link_image[1995]: failed to link /data/local/tmp/busybox
CANNOT LINK EXECUTABLE
mkdir failed for /system/xbin, File exists
link_image[1995]: failed to link /data/local/tmp/busybox
CANNOT LINK EXECUTABLE
Unable to chmod /system/xbin/busybox: No such file or directory
/data/local/tmp/root: /system/xbin/busybox: not found
cp: not found
cp: not found
Unable to chmod /system/bin/su: No such file or directory
for sure plan was to install cyanogenmod but I even want permaroot :/
thanks for any help

this was the similar problem when i rooted my desire Z
just ignore it and install clockworks recovery
your phone should actually be rooted by then~
but make sure before you do gfree command, you have already pushed all the other files into the proper location, IE busybox, SU and root
Good Luck~

I seem to be having a simmilar problem using the rage method. I can transfer everything through adb on my pc. But when i run the /data/local/tmp/rage it completes the action but after reseting the terminal and force closing the first time it will not open the second time. Any advice??

Thanks for answer,
when I have temproot and try to install clockworks it says no root-access using google search to find out how to get permaroot...

I was having same issue and realized that busybox's md5 from cyanogenmod wiki wasn't the same as the one it says. I downloaded the busybox file from this guide. Busybox is in gfree_temp-root.zip file.

Fibriso said:
Thanks for answer,
when I have temproot and try to install clockworks it says no root-access using google search to find out how to get permaroot...
Click to expand...
Click to collapse
What method are you using to install CWM? I suspect that ROM Manager will fail if ou only have temp root but I would expect that the flash_image method will work.

Do you have a guide or a good explaination for the flash_image method you talked about?

sacarino2k2 said:
I was having same issue and realized that busybox's md5 from cyanogenmod wiki wasn't the same as the one it says. I downloaded the busybox file from this guide. Busybox is in gfree_temp-root.zip file.
Click to expand...
Click to collapse
just want to bump / confirm that this worked for me. the gfree_temp-root.zip download from that link worked for me. note the underscore vs. dash from the link off the wiki.
as far as i can tell the problem was with the file named 'root' pointing to to some wrong paths but i couldnt see a difference in between the 2 in a text editor.
i'm now happily running cyanogen 6 on my HTC vision / g2 using the directions off http://wiki.cyanogenmod.com with the other root.zip file

Try again
Sent from my HTC Vision using XDA App

okay, i had this problem this morning trying to root my g2 and i got the same problem. i did get it to work after a couple of hours of trying 2 figure out why it wouldnt give me perm root.
the steps posted on the cyanogen wiki are correct. the only thing that you need to do is download the 02 version of gfree instead of the 04 version, and also download a different busybox (i think thats what i did).
i think i got the different busybox file from here.
you can just start off at the steps where it deals with pushing gfree to your phone. also, just push the gfree file (not the .cpp or whatever type it was that has a bunch of code in it. all you need 2 push is that one single file from that zipped file.
if you did it right, it will just print out one line with the failure regarding the 'file already exists' thingas stated in the cm wiki.

hierophanta said:
just want to bump / confirm that this worked for me. the gfree_temp-root.zip download from that link worked for me. note the underscore vs. dash from the link off the wiki.
as far as i can tell the problem was with the file named 'root' pointing to to some wrong paths but i couldnt see a difference in between the 2 in a text editor.
i'm now happily running cyanogen 6 on my HTC vision / g2 using the directions off http://wiki.cyanogenmod.com with the other root.zip file
Click to expand...
Click to collapse
The problem isn't in the root script. It is in busybox file. It doesn't work for some vision systems. Looks like compatibility compilation issues. So if you get errors running the root script use the busybox binary i posted before.

Fibriso said:
Do you have a guide or a good explaination for the flash_image method you talked about?
Click to expand...
Click to collapse
Here you go:
http://forum.xda-developers.com/showthread.php?t=902493

Just to touch base on this, it is related to the busybox binary on the CM wiki.
We've gone ahead and replaced the 'bad' one about 3 hours ago from this post.
Thanks for all of you who lets us know about the compatibility issues

Proper root or not

When i first bought the t989, i rooted the phone manually by flashing cwm and the su.zip file. Everything seem to have worked then. A month or so back I updated the phone to ICS through the Kies Air application. I tried browsing through my root files and found myself unable to do so. I decided to check my superuser application and noticed another su apk. It wasnt the android face but a superman android icon (sua). I updated the binary on the sua and my phone started resetting on its own. I have flashed stock roms of ics and the problem consisted. Eventually fed up of the 4.0.4 version i flashed back to GB which seems better in phone performance.
Back into stock/unrooted T989, i flashed root again. However i used root checker pro and it verifies root access however I find myself unable to browse root files. Is there another possible way to check through? maybe via terminal emulator?
/--edit 10:28 AM----\
So i did some more searching and found the su command in terminal emulator and the "$" symbol changed to "#"
Im guessing I have root but browsing in the rooted files seems disabled in some apps

brion1020 said:
When i first bought the t989, i rooted the phone manually by flashing cwm and the su.zip file. Everything seem to have worked then. A month or so back I updated the phone to ICS through the Kies Air application. I tried browsing through my root files and found myself unable to do so. I decided to check my superuser application and noticed another su apk. It wasnt the android face but a superman android icon (sua). I updated the binary on the sua and my phone started resetting on its own. I have flashed stock roms of ics and the problem consisted. Eventually fed up of the 4.0.4 version i flashed back to GB which seems better in phone performance.
Back into stock/unrooted T989, i flashed root again. However i used root checker pro and it verifies root access however I find myself unable to browse root files. Is there another possible way to check through? maybe via terminal emulator?
/--edit 10:28 AM----\
So i did some more searching and found the su command in terminal emulator and the "$" symbol changed to "#"
Im guessing I have root but browsing in the rooted files seems disabled in some apps
Click to expand...
Click to collapse
I'm having the same issues with 4.0.4. It's getting me pissed and contemplating doing 4.0.3 where I had access to system files via root explorer. I've been going through different ROMs on 4.0.4 to see if that would alleviate the problem. So far, still issues saying something to the affect that I don't have superuser access even though I can run any rooted application.

Here is the results of using root checker pro
Code:
Congratulations! You have root access!
Super User Applications Status: Superuser application - version 3.0.5 - is installed! SuperSU application - is NOT installed.
System File Properties for Root Access: Standard Location Check Command: ls -l /system/xbin/su: Result: lrwxrwxrwx root root 2012-09-29 00:35 su -> /system/bin/su Analysis: File: su is a symbolic link pointing to another file: /system/bin/su
Standard Location Check Command: ls -l /system/bin/su: Result: -rwsr-sr-x root root 22228 2008-08-01 08:00 su Analysis: Setuid attribute present and root user ownership present. Root access is correctly configured for this file! Executing this file can grant root access!
Alternative Location Check Command: ls -l /sbin/su: Result: /sbin/su: Permission denied Analysis: File system permissions restricted and denied access.
Alternative Location Check Command: ls -l /system/xbin/sudo: Result: /system/xbin/sudo: No such file or directory Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status: Root user id: uid=0(root)
Root group id: gid=0(root)
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User: ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
Results provided on your SGH-T989 device by

Su or superuser
Are you using Superuser or SuperSu try reinstalling the APP from the market.
if not already a system app use titanium backup to convert to system app.

[email protected] said:
Are you using Superuser or SuperSu try reinstalling the APP from the market.
if not already a system app use titanium backup to convert to system app.
Click to expand...
Click to collapse
I've tried updating superuser from the market, even bought the elite version. Tried SuperSu and thus far, no luck. Tried using titanium just now and it didn't work on superuser.
---------- Post added at 12:14 PM ---------- Previous post was at 12:11 PM ----------
I've even reflashed the su signed efghi 3.0.7 apk.

[email protected] said:
Are you using Superuser or SuperSu try reinstalling the APP from the market.
if not already a system app use titanium backup to convert to system app.
Click to expand...
Click to collapse
Ive tried updating su before and the binary which seem to have no changes. As for making su a system app, when i flashed unroot to root, su appeared without me installing. Also, su doesnt seem to appear in titanium backup
/----Edit----\
I'm returning my phone today to fix the broken power button, the stiffness of the D30 case may have caused this.
Is it possible to direct me to a fully working 100% root?

brion1020 said:
Ive tried updating su before and the binary which seem to have no changes. As for making su a system app, when i flashed unroot to root, su appeared without me installing. Also, su doesnt seem to appear in titanium backup
/----Edit----\
I'm returning my phone today to fix the broken power button, the stiffness of the D30 case may have caused this.
Is it possible to direct me to a fully working 100% root?
Click to expand...
Click to collapse
I'm kind of wondering if flashing back to completely stock via Odin, then trying all over again will do it? I know as soon as I did the Kies update from 4.0.3 to 4.0.4 caused this issue on stock rooted.

Hype As Fruck said:
I'm kind of wondering if flashing back to completely stock via Odin, then trying all over again will do it? I know as soon as I did the Kies update from 4.0.3 to 4.0.4 caused this issue on stock rooted.
Click to expand...
Click to collapse
Just Odin back to stock and then reroot. Its super simple. Maybe if you can get back to you recovery somehow you can just flash another rom and install it where you can have your supersu access back.
Sent from my SGH-T989 using xda app-developers app

[Q] SU Binary error upon Execution: No root access

Info: For those of you who need more info on my SU Binary (/system/bin/su), it's NOT out of date. Its the newest version for galaxy s4 m919.
My problem: /system/bin/su (SU binary files) will not execute.
Why?...: Because, access to execute binary files on system is denied (I don't have root access/permission). EEEK.
here's the Logs from root checker Pro: (In no particular order)-
SuperSU application - is NOT installed.
SuperUser - Installed!
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: -rwsr-sr-x root root 380532 2008-08-01 08:00 su
Analysis: Setuid attribute present and root user ownership present. Root access is correctly configured for this file! Executing this file can grant root access!
Standard Location
Check Command: ls -l /system/xbin/su:
Result: lrwxrwxrwx root root 2013-10-11 02:57 su -> /system/bin/su
Analysis: File: su is a symbolic link pointing to another file: /system/bin/su
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Check Command: ls -l /system/xbin
Root User ID and Group ID Status:
SU binary not found or not operating properly.
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin

more details
Extra info that I didn't include: I originally WAS rooted, running stock Samsung ROM (factory ROM) and I rooted using ODIN. So after rooting, I installed CyanogenMod 10.1.3.1, which does not come with root installed by default.
*SIGH* So... I want to know how to root CyanogenMod... So supposedly following the instructions by Root checker pro Logs,
I need to execute /system/bin/su. (Which won't work, unless a magical "S-Off" appears so I can execute it. But, then executing would be pointless because I would be already rooted with S-Off.
Help please, anyone? Could I root cyanogenmod from the computer terminal? Is there a way to override system permissions and execute su binary?

As per all your other post. Have you enable Root in Developer Options? CM ROM now has root disable by default.

Root options...
Root options in CyanogenMod Developer Options are not displayed in my settings...
What exactly does the toggle panel say for it? I can take a screenie of my settings..?
sorry for my ignorance with CyanogenMod... The last time I flashed CyanogenMod
was with CyanogenMod version 5, lol. And that was 3 years ago (I had an HTC Inspire 4G)

System Settings, About Phone, tap on the build number repeatedly until it enables Developer Options. Press back, tap Developer Options. Change Root Access to 'Allow ADB & Apps.'
Let's hope this is the last thread you start for awhile. Search for these answers, they have been answered already ;]

In reply...
dynospectrum said:
System Settings, About Phone, tap on the build number repeatedly until it enables Developer Options. Press back, tap Developer Options. Change Root Access to 'Allow ADB & Apps.'
Let's hope this is the last thread you start for awhile. Search for these answers, they have been answered already ;]
Click to expand...
Click to collapse
Well then. That was not so loving and friendly. Lol. And I have done so, btw.. My developer options are enabled, but the root access panel is not
In there. infact, there was a new section called "SuperUser", and I had set the root access panel to "Allow ADB and Apps" like you said.
But in return, no cigar. No root rights, even still. :/

Same here I'm using beanstalk 4.3 and most of the root apps work but some don't for example gamekiller, the few times I installed it it denied it before the prompt window popped out then after a few tries it finally granted it but before I pressed grant it said WARNING GAMEKILLER HAS A COMMAND (not sure about that part) android.permission.ACCESS_SUPERUSER not declared so I went into super user settings and I checked that option so I tried searching a value number and as soon as I press search it doesn't do anything then I press help and it tells me it needs root access which has been give
Sent from my SGH-M919 using XDA Premium 4 mobile app

Download and flash in recovery: http://download.chainfire.eu/351/SuperSU/UPDATE-SuperSU-v1.65.zip

Yay.
I've flashed that in CM10 ROM several times, and no root. But no worries, I'm running an awesome, fast, great battery life AOSP Based ROM (Completely AOSP, actually) and it comes rooted
The ROM is actually solely based off of googles open source code from android 4.3, with a few of the major components hand-picked from other Dev sources. The ROM is called-
Google Edition s4
For all who wish to download this as well as I did, here's the link to this epic ROM:
http://forum.xda-developers.com/showthread.php?t=2341026

Thanks
Thank you, this method worked for me. So much misinformation out there, I tried like 20 other bogus remedies before this. I could hug you.

same problem
I rooted my phone before,then I unroot it. But now when I am trying to root it again I'm facing same problem with superuser, it's saying that su binary is outdated and its not updating also, and I don't have root permission so that I can fix it with several methods which I found by google it.

Just Rooted My S3 But SU Is Missing A Binary

I just rooted my ATT S3 4.3. I did everything the tutorial said to do except when it got the part wherr odin reboots ur phone, i had to reboot it myself yo makr it go in cwm recovery. So once I was done rooting my phone and turned it on for the 1st time I instantly was greeted with superuser has stopped and security violations. So I tried random fixes from google and it keepa teling me there is no binary code. I can't figure out how to fix this, can anyone help me?

Which tutorial did you follow?

audit13 said:
Which tutorial did you follow?
Click to expand...
Click to collapse
I can't find it anymore. It was on this forum and it said it was for att S3 phones. Is there an area where all the ways to root are?
This is what root checker pro gave me as the results.
Super User Application Status:
SuperSU application - version 1.93 - is installed!
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Standard Location
Check Command: ls -l /system/xbin/su:
Result: -rwxr-xr-x root root 113036 1970-08-25 22:58 su
Analysis: Setuid attribute is NOT present BUT root user ownership is present. Root access is NOT correctly configured for this file!
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1

Try Chainfire's CF autoroot with SuperSU, including google play SSU update to App? It sounds like you failed to reboot into recovery first before doing a normal boot. After flashing via odin, the root is temporary and will be wiped during a normal boot, unless you first reboot into recovery. So, you have to uncheck the reboot after flash option in odin. After successful flash, pull usb cable and boot into recovery using three button method.
Did you use CF autoroot? Try it again.
http://forum.xda-developers.com/showthread.php?t=1963790
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

laughingT said:
Try Chainfire's CF autoroot with SuperSU, including google play SSU update to App? It sounds like you failed to reboot into recovery first before doing a normal boot. After flashing via odin, the root is temporary and will be wiped during a normal boot, unless you first reboot into recovery. So, you have to uncheck the reboot after flash option in odin. After successful flash, pull usb cable and boot into recovery using three button method.
Did you use CF autoroot? Try it again.
http://forum.xda-developers.com/showthread.php?t=1963790
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I did reboot into recovery. I remeber the files I downloaded were named clockword mod and another was called superboot with cwm. Don't k ow if that helps.
I'm having a big issue though, I had tried fixing it by flashing dif ways, now whe I try tk flash it. When it loads up in download mode, my phone turns off or of ot doesn't do that, after I flash my phone and it reboots, it shows a red screen.
EDIT:
I just tried that root method you suggested and I still have the same issues. I don't know what to do!
EDIT 2:
I fixed it by using this site http://www.w0lfdroid.com/2013/12/Fix-Root-Problem-on-Android-4.3-for-Galaxy-S3-S4-Note2-Note3.html. Specifically, these instructions:
Download and install the latest APK for SuperSU like MrW0lf suggested.
I was having the same exact problem (unfortunately, SuperSU has stopped), so I downloaded the latest UPDATE-SuperSU file and extract it to have supersu APK, put it on my SD card in my phone and installed it from there.
It was strange because the version that was already on my phone was the same 1.89 version that I downloaded, but regardless, when I clicked on the APK, it saw it as an update, it asked to disabled knox, and worked like a charm.
- See more at: http://www.w0lfdroid.com/2013/12/Fi...y-S3-S4-Note2-Note3.html#sthash.0nlj3XHO.dpuf
PS: this is the root method I had 1st followed, http://forum.xda-developers.com/showthread.php?t=1726960

[Q] installed weak sauce, firewater soff, and hroot and stuck

Sorry if the answer is somewhere in here but I have been looking for over a day.
This is what I have done:
I have a stock Verizon HTC One
Installed weak sauce gained root access.
Installed Firewater S-Off and HBoot worked Beautiful work thank you after hours of research. - For a Noob it went smooth.
Also flashed PhilZ Touch Advance and when I try to reboot it says: Root access is missing or broken.
Ran Root Checker: You have root access!
Super User Application Status:
SuperSU application - version 1.93 - is installed!
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Standard Location
Check Command: ls -l /system/xbin/su:
Result: -rwxr-xr-x root root 113036 2014-03-30 12:15 su
Analysis: Setuid attribute is NOT present BUT root user ownership is present. Root access is NOT correctly configured for this file!
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
Root user id:
uid=0(root)
Root group id:
gid=0(root)
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
I'm sure the answer is in here I just dont want to F it up and my eyes are crossed from looking for answer.
Thanks Again.

How about just flashing a rooted ROM in your recovery and seeing if it's all good?

That easy?
orangekid said:
How about just flashing a rooted ROM in your recovery and seeing if it's all good?
Click to expand...
Click to collapse
Ok I will try that. Do you think the error is because I installed supersu incorrectly, or wrong method. I believe I dropped and dragged it to my download file then opened it with my file browser and installed. As long as that wont be an issue I will give it a shot. Thank You for responding to my noob question.

habatchaNow said:
Ok I will try that. Do you think the error is because I installed supersu incorrectly, or wrong method. I believe I dropped and dragged it to my download file then opened it with my file browser and installed. As long as that wont be an issue I will give it a shot. Thank You for responding to my noob question.
Click to expand...
Click to collapse
It could be a number of things, but you were going to flash a custom ROM at some point anyways, right?

@PonsAsinorem might be able to help on this.

ROM .... Check
orangekid said:
It could be a number of things, but you were going to flash a custom ROM at some point anyways, right?
Click to expand...
Click to collapse
I took your advice and flashed the NuSenceSix. It went off without a hitch, holding breath eh entire time. Thank you for the push.
I went back to the firewater threads and one thing I didn't do was remove weaksause. Is that something I need to do if I want the root to be permanent? I don't need to go to the android development and go though that process emailing system info or whatever its called do I?
Also I was about to read up on radios and kernals for this ROM as well as try and figure out why I am getting that message in Rootchecker.
Thanks Again for your help.

Please
synisterwolf said:
@PonsAsinorem might be able to help on this.
Click to expand...
Click to collapse
That would be awesome. Any suggestions would be greatly appreciated. As I was telling the Room Moderator I flashed the NuSense6 and it went off without a hitch. however it is Still showing the same messages with rootchecker.
Thank You

synisterwolf said:
@PonsAsinorem might be able to help on this.
Click to expand...
Click to collapse
Sorry for the late response; was at work.
habatchaNow said:
That would be awesome. Any suggestions would be greatly appreciated. As I was telling the Room Moderator I flashed the NuSense6 and it went off without a hitch. however it is Still showing the same messages with rootchecker.
Click to expand...
Click to collapse
If you're S-OFF, you're golden. Most anything after that is going to be a ROM issue. It's been a minute since I ran that ROM, but the early batches had issues with su being configured improperly. The easiest way to fix this would be to flash the update SuperSU zip in recovery.

I miss read the OP-
I thought he was saying that Philz recovery was showing Super User not installed on reboot when the rom is Rooted.
OP-
As for weaksauce, once you have s-off you will no long need the app. you can root any rom by flashing SU.zip if you have an S-off device running a custom recovery.

habatchaNow, what version of PhilZ are you running? There was a bug that misdetecting CM, but that's been fixed, and I don't think this rom ever had the false positive, because root actually wasn't configured properly at the time.

Custom Recovery Version
PonsAsinorem said:
habatchaNow, what version of PhilZ are you running? There was a bug that misdetecting CM, but that's been fixed, and I don't think this rom ever had the false positive, because root actually wasn't configured properly at the time.
Click to expand...
Click to collapse
Let me see, it looks like my custom recovery is PhilZ 6.40.4 Cyogen Mod V6.0.4.8. I think the problem started when I installed and ran super su. I side loaded it( that's moving it onto my device via explorer right?) Do you guys recommend another ROM for my phone? I like the NuSence it just seems like a minor upgrade to the stock ROM. I don't know if this matters but when I open my files on the phone the "root" folder and "sbin" folder are both empty.
One of my challenges is that I don't even know what I don't know so, I really appreciate the help. If you ever need help or advice with health/life/investments I'm your guy.

If you like that ROM, then stick with it. I try not to steer people away from any ROM. To fix your su problem, try flashing this from recovery.
http://download.chainfire.eu/supersu