Develop Bugs

Trouble rooting at last step.

Hey, I just got my G2 today and am trying to root it through adb. I get to the last part of the tutorial under getting perm-root, and i put in /data/local/tmp/root in the root terminal, and it gives me a whole bunch of busybox: /system/bin/"": Input/output error's, and at the end says cp: cant creat /system/bin/su Input output error and unable to chmod /system/bin/su no such file or directory.

what method are you using to root?

Hey Andy, I'm having the same problem the original poster is. I'm using the rage/gfree method and everything works like a charm right up to the last step. I'm getting the "unable to chmod /system/bin/su: no such file or directory"
This was also reported here: http://forum.xda-developers.com/showthread.php?t=897499&highlight=chmod+0755+/data/local/tmp/*
(Though, unlike the guy in that thread, I didn't try to use visionary AT ALL (didn't download it or install it or anything) and ONLY followed the wiki's guide, which uses the rage/gfree method.)
All three of us seem to have ended up with the problem though and from reading through that thread I posted the link to above and from what I've done 8 times now tonight, we've followed the steps exactly.
Any ideas? I would love to get this thing perma rooted.
Thanks so much to you and anyone else for any help.

Are you sure there weren't any errors before that one? I would have guessed you had an error in the cp command as well...
Make sure you have the su file on the root of your SD card. It was the first file you pushed in the wiki guide. If that file is not there, just push it to your SD card again and then re-run the root script in terminal.

Finally got it worked out late last night. Turns out that I had put a copy of the su file on the card while it was mounted to my computer, before I mounted it on the phone, prior to following the root steps. I guess this somehow messed with adb pushing it correctly.
So if that is happening to you, clear out the unnecessary files first and only move the necessary files to the card via adb.
After that, it worked like a charm. I am now perma-rooted.
Sent from my T-Mobile G2 using XDA App

And thanks so much ian. What you said got me thinking about removing the su file altogether and starting it fresh.
Sent from my T-Mobile G2 using XDA App

I dont know why it was giving me errors, but all i had to to was flash recovery through adb and flash a rooted rom and everything worked great.

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

[Q] Bin4ry root method

Hi, I saw Bin4ry root method that can be done with locked bootloader. I tried it on my Gnexus but it doesn't work.
Can someone make it working on the galaxy nexus?

Lorenzo_9 said:
Hi, I saw Bin4ry root method that can be done with locked bootloader. I tried it on my Gnexus but it doesn't work.
Can someone make it working on the galaxy nexus?
Click to expand...
Click to collapse
makes it working with a locked bootloader, on Sony NXT, and we don't have /data/local.prop, at least checking it on the device/gui, in the shell it could be different.

Ok. But in some nexus 7 it works so I thought it could be done in Gnexus
Sent from my Galaxy Nexus using xda app-developers app

Lorenzo_9 said:
Ok. But in some nexus 7 it works so I thought it could be done in Gnexus
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
That's a very interesting way to get root! Props to Bin4ry for this .
I was just going over his script, and I may have an idea. Can you tell me where if fails for you?

efrant said:
That's a very interesting way to get root! Props to Bin4ry for this .
I was just going over his script, and I may have an idea. Can you tell me where if fails for you?
Click to expand...
Click to collapse
Here's what I get with the script:
Normal Mode enabled!
Please connect device with ADB-Debugging enabled now....
3995 KB/s (1085140 bytes in 0.265s)
1399 KB/s (22364 bytes in 0.015s)
3771 KB/s (843503 bytes in 0.218s)
Please look at your device and click RESTORE!
If all is successful i will tell you, if not this shell will run forever.
Successful, going to reboot your device!
Waiting for device to show up again....
mount: permission denied (are you root?)
remount failed: Operation not permitted
/system/xbin/su: cannot open for write: Read-only file system
Unable to chmod /system/xbin/su: No such file or directory
/system/app/Superuser.apk: cannot open for write: Read-only file system
Unable to chmod /system/app/Superuser.apk: No such file or directory
rm failed for /data/local.prop, No such file or directory
You can close all open command-prompts now!
After reboot all is done! Have fun with Root!
Bin4ry
Premere un tasto per continuare . . .

Try using the attached script instead of the Runme.bat that Bin4ry had included, and let me know if there is any change.
EDIT: Deleted attachment.

efrant said:
Try using the attached script instead of the Runme.bat that Bin4ry had included, and let me know if there is any change.
Click to expand...
Click to collapse
It doesn't work:
Please connect device with ADB-Debugging enabled now....
3260 KB/s (1085140 bytes in 0.325s)
325 KB/s (22364 bytes in 0.067s)
2366 KB/s (843503 bytes in 0.348s)
Please look at your device and click RESTORE!
If all is successful i will tell you, if not this shell will run forever.
Successful, going to reboot your device!
Waiting for device to show up again....
mount: permission denied (are you root?)
/system/bin/su: cannot open for write: Read-only file system
Unable to chmod /system/bin/su: No such file or directory
link failed Read-only file system
/system/app/Superuser.apk: cannot open for write: Read-only file system
Unable to chmod /system/app/Superuser.apk: No such file or directory
rm failed for /data/local.prop, No such file or directory
You can close all open command-prompts now!
After reboot all is done!
Premere un tasto per continuare . . .

Try running it as a superuser (sudo su). Seems this is for Windows, try running as administrator.
Also, including 'adb remount' in the script before the files are pushed may help with the read-only errors.
Sent from my Transformer TF101 using Tapatalk 2

@efrant
like someone said before, could be a problem the fact that we don't have the file /data/local.prop ?
the script say succesfull even the file is not found i though

andQlimax said:
@enfrant
like someone said before, could be a problem the fact that we don't have the file /data/local.prop ?
the script say succesfull even the file is not found i though
Click to expand...
Click to collapse
Nope, it wouldn't have to do with that.
If I understand correctly how this is supposed to work, is that Android will look for local.prop when booting, and if the qemu flag is set to 1 in that, then shell will run as root. What this does is supposed to do is create the local.prop file with ro.kernel.qemu=1, so that on the following reboot, adb will run as root.
I'm not sure why it's failing. I'll post in Bin4ry's thread for him to have a look over here. Hopefully he can sort it out with folks here testing (as I'm sure he doesn't have the GNex).

I just had a look over at his thread (I haven't gone through it all yet). Let's see if we can figure this out before we have to bug Bin4ry.
Try doing this steps here to enter the first three lines of code, and see if you end up with a root shell (#) or a normal shell ($).

On the subsequent reboot (after putting the local.prop in place), couldn't you run:
Code:
$ getprop | grep qemu
At least then you could confirm if the setting in local.prop is being read/applied.

Well, I have good news and bad news.
Good news: I tried this out (typing in the commands manually, not using the provided script), and it seems to have given me a root shell. Not sure why others were having issues.
Bad news: Something seems to have gotten corrupt in the process, so I had to wipe.
I may take another stab at trying to figure it out when I have time.

Ok thank you very much for your work
Sent from my Galaxy Nexus using xda app-developers app

http://forum.xda-developers.com/showthread.php?p=31751966

Hey guys, can you please test the new attached v5 in the thread?
I adjusted some stuff, hopefully normal mode should work here then
Regards

Bin4ry said:
Hey guys, can you please test the new attached v5 in the thread?
I adjusted some stuff, hopefully normal mode should work here then
Regards
Click to expand...
Click to collapse
EDIT:
v5 runs through the process but doesn't work at the end, see screenshot.
v6 doesn't work as well. The DOS window forcecloses without a notice, here is a screen right before the crash.
Device specs: Galaxy Nexus, 4.1.1, GSM version, Build JRO03C

Thanks for testing.
can you run most latest version of today? I had an annoying fault inside the script it is now corrected
Regards

Bin4ry said:
Thanks for testing.
can you run most latest version of today? I had an annoying fault inside the script it is now corrected
Regards
Click to expand...
Click to collapse
Great work discovering this exploit, Bin4ry.
Please see the following topic where this discussion is continuing:
[HOW-TO] [GSM & CDMA] How to root without unlocking bootloader (for all ICS & JB)
http://forum.xda-developers.com/showthread.php?t=1894717

Bin4ry said:
Thanks for testing.
can you run most latest version of today? I had an annoying fault inside the script it is now corrected
Regards
Click to expand...
Click to collapse
Still no luck with v9, similar error as in v5: "mount: permission denied". Superuser app isn't being pushed on my phone.
Btw great work on the Tablet S root, worked perfectly!

Different Firmware- can I still root?

I would like to root My LT18i Xperia Arc S, just so I can get rid of the bloatware, although if I could upgrade to ICS as well then that would be cool. I've found loads of instructions on how to root, but none for my firmware version, which is 4.0.2.C.0.5. The phone is locked to Three (a UK network operator). A lot of the instructions talk of downgrading the firmware from various versions to 4.0.2.A.0.42, and then rooting from there, although none list my particular firmware. Is this method possible for my firmware version? If it's not and I try anyway will I wreck my phone? I'd like to be as sure as possible before I start. My boot loader is locked.
Thank you.

timswait said:
I would like to root My LT18i Xperia Arc S, just so I can get rid of the bloatware, although if I could upgrade to ICS as well then that would be cool. I've found loads of instructions on how to root, but none for my firmware version, which is 4.0.2.C.0.5. The phone is locked to Three (a UK network operator). A lot of the instructions talk of downgrading the firmware from various versions to 4.0.2.A.0.42, and then rooting from there, although none list my particular firmware. Is this method possible for my firmware version? If it's not and I try anyway will I wreck my phone? I'd like to be as sure as possible before I start. My boot loader is locked.
Thank you.
Click to expand...
Click to collapse
Have you run SEUS or PC Companion at all? There's been 5 FW releases since then according to Wotan Server.

From what I have heard, the regular root method for GB, 4.0.2.A.0.58 and lower, should work also on 4.0.2.C.0.5 firmware. Give it a try, you got nothing to lose there.

OK, so I really am a total numpty, I was assuming that all updates could come OTA, and because I didn't have any updates available when I checked on the phone I must have the latest version, I hadn't realised that updating it from a PC did a full update. :silly:
So I'm now updated to ICS, although in a way my original question remains... Now my build number is 4.1.L.0.8, so can I follow the root guides for 4.1.A.0.562, for example the guide here: androidauthority.com/xperia-arc-s-lt18i-root-android-4-0-ics-80266 ? And equally importantly, if I try to follow the guide and it doesn't work on my firmware will it simply do nothing, or will it wreck the phone?
Thank you guys, I thought I had done a lot of reading up on rooting and flashing and unlocking boot loaders, but missed the obvious and a simple comment like "Have you tried SEUS" can make all the difference!

timswait said:
OK, so I really am a total numpty, I was assuming that all updates could come OTA, and because I didn't have any updates available when I checked on the phone I must have the latest version, I hadn't realised that updating it from a PC did a full update. :silly:
So I'm now updated to ICS, although in a way my original question remains... Now my build number is 4.1.L.0.8, so can I follow the root guides for 4.1.A.0.562, for example the guide here: androidauthority.com/xperia-arc-s-lt18i-root-android-4-0-ics-80266 ? And equally importantly, if I try to follow the guide and it doesn't work on my firmware will it simply do nothing, or will it wreck the phone?
Thank you guys, I thought I had done a lot of reading up on rooting and flashing and unlocking boot loaders, but missed the obvious and a simple comment like "Have you tried SEUS" can make all the difference!
Click to expand...
Click to collapse
If it doesnt work, your phone should be fine. But that also means that you've been doing something wrong. Give it a go
Sent from Xperia Arc S

I followed the instructions here for rooting:
http://forum.xda-developers.com/showthread.php?t=1601038&nocache=1
It seemed to go through all the stages, the phone rebooted several times and it came up "All done" at the end. The good news is that the phone still works fine, the bad news is that it doesn't seem to be rooted. I've installed Titanium Backup and it comes up with "could not acquire root privileges, please check that your phone is rooted", so I assume this means it hasn't worked? Is there any other way to see if it's rooted? This is the output from running the rooting batch script:
Code:
--- STARTING ----
--- WAITING FOR DEVICE
* daemon not running. starting it now *
* daemon started successfully *
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
rm failed for *, No such file or directory
--- symlinking tmp directory
failed on '/data/local/tmp' - Permission denied
link failed File exists
--- Rebooting
--- WAITING FOR DEVICE TO RECONNECT
--- PLEASE WAIT, THIS MAY TAKE A WHILE
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
--- enabling emulator hack
/system/bin/sh: cannot create /data/local.prop: Permission denied
--- Rebooting
--- WAITING FOR DEVICE TO RECONNECT
--- PLEASE WAIT, THIS MAY TAKE A WHILE
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
--- pushing busybox
3059 KB/s (1075144 bytes in 0.343s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- checking free space on /system
0 KB/s (439 bytes in 1.000s)
--- Free space on /system : 56068 bytes
--- no cleanup required
--- copying busybox to /system/xbin/
/system/xbin/busybox: cannot open for write: Read-only file system
--- correcting ownership
Unable to chmod /system/xbin/busybox: No such file or directory
--- correcting permissions
Unable to chmod /system/xbin/busybox: No such file or directory
--- installing busybox
/system/bin/sh: /system/xbin/busybox: not found
--- pushing SU binary
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
--- cleaning
rm failed for /data/local.prop, No such file or directory
rm failed for /data/local/tmp, Permission denied
failed on '/data/local/tmp.bak' - No such file or directory
--- rebooting
ALL DONE!!!
Press any key to continue . . .

There's four links to root threads now in my guide, give them a read.

Thanks, that guide was very useful. I've actually used a combination of the techniques, and it seems to have worked Here's what I did, might be useful to someone, also please if anyone who knows better than me can see any problems then please let me know if I'm going to have problems in the future
1. Backed up my firmware using the instructions from 100rabh791 here:
http://talk.sonymobile.com/message/178992
2. Flashed back to 4.1.A.0.562 Kernel using Nabeel's instructions here:
http://talk.sonymobile.com/thread/41119?start=0&tstart=0
3. Rooted using DooMLoRD's root kit here:
http://forum.xda-developers.com/showthread.php?t=1601038
At this point I seemed to have a fully working and rooted phone, however I thought it was best to go back to my original build version (4.1.L.0.8), so I re-flashed my backed up firmware, However this lost my root privileges, so I was back to the start. So I re-did steps 1-3 and then:
4. Re-flashed back to my original firmware, but checked the options "Exclude system", "Exclude baseband", "Exclude Fota" and "Exclude TA" (in other words just left Kernel unchecked).
So as I understand it (which I possibly don't), I should be back on my original, most up to date build version, but now have root access, please correct me if there's anything wrong with what I've done.

timswait said:
So as I understand it (which I possibly don't), I should be back on my original, most up to date build version, but now have root access, please correct me if there's anything wrong with what I've done.
Click to expand...
Click to collapse
Nice one, doesn't look like you'll have any issues, but the main thing is you've got root. What does it say in your Settings/About Phone/Build Number?

XperienceD said:
Nice one, doesn't look like you'll have any issues, but the main thing is you've got root. What does it say in your Settings/About Phone/Build Number?
Click to expand...
Click to collapse
4.1.L.0.8 which is what it was on after the official upgrades before I started the rooting process.

[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