Hey everyone, I used to have the older 1.4 eclipse rom with the PBJ kernel for the ep4 kernel version. Things were fine and working great. I then dropped my phone into some water, awesome. Got a new replacement droid and saw that eclipse rom 2.0 was out for the OTA FP1 kernel build. I went ahead and put on CWM through ODIN and flashed the 2.0 rom with superuser by installing from the zip in CWM. I can still boot into CWM and the eclipse rom is still running.
However, I am noticing a lot of weird issues that tells me something is not right. I just installed the PBJ kernel for FP1 builds (0542 i think). I went to the immuts website and checked my phone's About menu and it matches the kernel version he says it should be (if installed). Great, so I this is saying the kernel is installed. Previously before installing the kernel, I was able to use wifi tether without an issue. Now I can't "phone is in an unknown state" or some similar error. Also, when opening up the terminal emulator and trying to get root permissions (su) I get permission denied from superuser. No block on the app is set in the superuser app. I also downloaded the Voltage Control app and when opening it says that I am not root and must be root. I also got a root checker and superuser won't give it permissions and it says I am not on a rooted device.
What gives? I have been reading about the EXT4 conversion. Do I need to do this or is it already done for me? Did I install this kernel the wrong way?
The root issue is common on PBJ 0524. It has to do with permissions on the su binary getting messed up. The simplest fix is to download the binary from http://downloads.androidsu.com/superuser/su-bin-3.0.3.2-efghi-signed.zip and reflash it in CWM. Make sure you mount /system before you flash or it won't work.
ext4 conversion has to be done manually. You can use imoseyon's kernel at Rootz to do the conversion and then flash PBJ over it, or you can use imunt's ext formatter. The ext formatter will wipe everything, so you'll have to reflash and restore your data.
EDIT: I only really recommend worrying about ext4 if you plan to do CWM backups. rfs works just fine otherwise.
Was the phone on stock FP1 before you flashed Eclipse and the kernel?
If so, then it sounds like you might just have to flash the superuser zip to get root back. I know some others have been having problems with losing root when updating. Here's the link to the su binary from androidsu.com.
Thanks! I was on stock FP1 before I flashed so I did not need to flash back to the previous version and then OTA update. I appreciate the help!
Need to Root
Sounds like you just don't have root access. Do you have su installed? Did your rom come pre rooted?
I got the Eclipse Rom 2.0. I would imagine that it would be rooted already but who knows..
Eclipse is already rooted. The su binary is on the phone, but the problem is with permissions getting messed up during the kernel installation. It's a well documented problem and there are several solutions to it...the simplest is to just reflash the binary. dwitherell has an adb based solution over in the Tweaked thread.
Related
What part of rooting a phone gives you root?
Does installing CWM recovery enable root access?
Or does installing the superuser.zip file give it?
In other words, what is preventing you in a stock system from obtaining root?
daystrom said:
What part of rooting a phone gives you root?
Does installing CWM recovery enable root access?
Or does installing the superuser.zip file give it?
Just trying to have a basic understanding of the process and how it works.
Click to expand...
Click to collapse
CWM is just recovery, it is NOT root
rooting is simple. people think of it as some voodoo, but its not.
when you root, you are adding 2 files to your /system
/system/app/Superuser.apk
and
/system/bin/su
su is the binary that allows Superuser.apk to grant root permissions to you the user, or to an app that is requesting it (assuming you grant the permission when prompted)
rooting isnt some magical process, it actually has nothing to do with anything OUTSIDE of the OS.
if you use CWM to flash a rooted rom, then you have root in that rom.
if you use CWM to flash a non-rooted rom, then you will not have root, plain and simple. you will still have CWM, but no root.
the 2 items (cwm and superuser/root) are NOT equivalent
Great info!
What is stopping you however from adding those files to a stock system? CWM recovery has to be installed first to install the su files. Why?
daystrom said:
Great info!
What is stopping you however from adding those files to a stock system? CWM recovery has to be installed first to install the su files. Why?
Click to expand...
Click to collapse
if you are booted into CWM you have read/write access to /system which allows you to add the necessary files for you to gain root access.
if you are booted into the OS, /system is mounted as read-only and you would have to rely on an actual exploit of the OS in order to 'temp-root' so that the rooting tool can gain the read/write access it needs to inject the root files. since 2.3.6 fixed all the current exploits CWM is required for rooting, until someone finds an exploit in 2.3.6 that allows them to gain that temp access .
you can completely add those files to a stock system, assuming you install CWM or are on an android version < 2.3.6
on 2.3.5 you could use the zergrush exploit to get permanent root without having to flash anything in ODIN to gain CWM...in fact, on 2.3.5 you can root your stock system and never even install CWM or go any farther than rooting it.
Awesome, I appreciate your knowledge!
Pirateghost said:
if you are booted into CWM you have read/write access to /system which allows you to add the necessary files for you to gain root access.
if you are booted into the OS, /system is mounted as read-only and you would have to rely on an actual exploit of the OS in order to 'temp-root' so that the rooting tool can gain the read/write access it needs to inject the root files. since 2.3.6 fixed all the current exploits CWM is required for rooting, until someone finds an exploit in 2.3.6 that allows them to gain that temp access .
you can completely add those files to a stock system, assuming you install CWM or are on an android version < 2.3.6
on 2.3.5 you could use the zergrush exploit to get permanent root without having to flash anything in ODIN to gain CWM...in fact, on 2.3.5 you can root your stock system and never even install CWM or go any farther than rooting it.
Click to expand...
Click to collapse
OK sorry just to clarify if we used a oneclick method to root that utilizes the zergrush exploit on 2.3.5 then we will be able to get the ICS OTA update when it comes next year?
All I did was follow the instructions provided on this link:
http://www.addictivetips.com/mobile...s-ii-skyrocket-on-gingerbread-with-one-click/
which says that the root method i used is: "This is why, Shabbypenguin and the team at Android Creative Syndicate have brought us the Easy Root for the Skyrocket. The script, uses the brilliant zegrush exploit and will have your device rooted in no time."
After rooting I used bloat freezer to "freeze" bloatware because i've read elsewhere that completely uninstalling could prevent you from getting OTAs correctly.
Sorry I'm such a noob at this...
You need stock recovery and bloatware can be frozen but not deleted
---------- Post added at 03:36 PM ---------- Previous post was at 03:33 PM ----------
Thats all. You dont have to use the oneclick to be able to get an ota. You . can use the odin method then flash the stock recovery.tar. its so simple. You can root use cwm recovery then if theres an ota just odin the stock tar. And u can take the ota
I'm one of those who seems to still have problems with all the ROMs that I don't when Odining the stock. I still have the shutdown lockup no matter what I do when flashing ROMs (tried mhx's SuperLite and NexusMod).
But the one that's really driving me nuts is that despite superuser permissions seemingly working fine, I can't modify/remove system files. Can't replace my build.prop, system apps, anything. If I paste something new or rename a file it'll act like it worked but it won't have done anything. If I paste over something it says not enough space.
Has anyone else observed this issue? Is there a fix?
Do you have an insecure kernel? If not you won't be able to write to system from within ICS.
mohan_kr or romracer unsecured ics kernels,
promiseofcake said:
Do you have an insecure kernel? If not you won't be able to write to system from within ICS.
Click to expand...
Click to collapse
Yeah, they both use romracer's kernel, so that must be in. Any downside to flashing the stock kernel?
Now that you mention it, I am having a hell of a time writing /system from within ICS too. I am using romracer's kernel as well. In addition, my sysrw, sysro, remount etc system/xbin files (pushed via recovery ADB) keep disappearing. I'm stumped.
Frogacuda said:
I'm one of those who seems to still have problems with all the ROMs that I don't when Odining the stock. I still have the shutdown lockup no matter what I do when flashing ROMs (tried mhx's SuperLite and NexusMod).
But the one that's really driving me nuts is that despite superuser permissions seemingly working fine, I can't modify/remove system files. Can't replace my build.prop, system apps, anything. If I paste something new or rename a file it'll act like it worked but it won't have done anything. If I paste over something it says not enough space.
Has anyone else observed this issue? Is there a fix?
Click to expand...
Click to collapse
promiseofcake said:
Now that you mention it, I am having a hell of a time writing /system from within ICS too. I am using romracer's kernel as well. In addition, my sysrw, sysro, remount etc system/xbin files (pushed via recovery ADB) keep disappearing. I'm stumped.
Click to expand...
Click to collapse
Hey guys take a look at this post.
http://forum.xda-developers.com/showpost.php?p=24740309&postcount=37
galaxyuser88 said:
Hey guys take a look at this post.
http://forum.xda-developers.com/showpost.php?p=24740309&postcount=37
Click to expand...
Click to collapse
galaxyuser88 said:
1. Odin the 1-Click ICS rom.
2. Flash CWM (any version, they all work).
3. Flash SuperUser.
4. Install BusyBox <<<< make sure you add busybox before you flash your favorite rom. Otherwise you will have problems.
5. then flash your favorite Rom.. Enjoy.
Click to expand...
Click to collapse
I don't really know how that would help, for example when you get to step 5, many roms wipe /system, /data, /cache, etc. What good would doing these flashes first be? I don't see how it could honestly do anything.
This is a longshot, but what are you using to write files? I don't remember which rom I used, but when I used Root Explorer, it didn't work. But, when I switched to ES Explorer (turn on root explorer option), it did. Maybe try another file explorer?
jedah said:
This is a longshot, but what are you using to write files? I don't remember which rom I used, but when I used Root Explorer, it didn't work. But, when I switched to ES Explorer (turn on root explorer option), it did. Maybe try another file explorer?
Click to expand...
Click to collapse
Root Explorer is no go. But I am talking about mounting rw over adb.
EDIT:
Why don't you try to use SuperSu instead of Superuser. I am getting perfect reboots now with the SuperSu binary. I will try the /system mounting.
EDIT2:
Mounting /system failed, boo.
I am having the same issue with NexusMod ICS 3.
U can not adb push to system while device is running.
Shutdown bootup cwm non touch recovery mount system then u can push to system all u want......but u can use root explorer to write to system as well iffffffffffffffffff
---------- Post added at 01:46 AM ---------- Previous post was at 01:44 AM ----------
You flash this in cwm http://forum.xda-developers.com/showpost.php?p=21750986&postcount=1
Reboot
Open new SuperSU app and let it update binary
I was playing with my TF101 earlier today and went to check Titanium Backup when I was given a surprise, I can't use it anymore. My tablet had been rooted since the day I got it nearly a year ago but somehow my busybox got uninstalled. I have not done anything that would cause it to be uninstalled, and when I try to install it again no program is able to. When trying to update the Su binary Superuser fails to gain root access as well, so something weird happened in the past few days (looking at my most recent Titanium Backups manually it seems it happened after 6/3, but I don't know why).
My first attempt to fix was re-flash the most recent Honeycomb-based Revolver update (3.11.1) and run "Fix Permissions" but that didn't help. I'm thinking the only way to be able to fix this is to do a wipe and re-install of everything, or even a new nvflash, but my most recent backup is months old (I'd been travelling and not messing with ROMs so I didn't have a need for a backup).
Does anyone have suggestions as to what else I can do before I try and do a wipe/install?
Thanks
In terminal, does "which su" and "which busybox" return anything?
How about "ls -l /system/*/su" and "ls -l /system/*/busybox"
You probably have 2 versions and one is not does not have the su id set.
sent while running with scissors
gee one said:
In terminal, does "which su" and "which busybox" return anything?
Click to expand...
Click to collapse
I tried running it in "Android Terminal Emulator" but for some reason it doesn't work anymore, it loads and then auto closes... so I did it in "System Tuner"s terminal emulator.
I ran both and got "Failed to run: Error running exec(). Command: [which, su] Working Dierctory:null Environment: null"
How about "ls -l /system/*/su" and "ls -l /system/*/busybox"
Click to expand...
Click to collapse
for both of these i get "No such file or directory"
I honestly have no idea what is going on because this last week I used it as a netbook while travelling Korea and for the 4 months prior I haven't been able to access the internet regularly so I haven't been playing around with CWM, flashing new roms, etc. I think the newest apps I've installed were mixi (like Facebook, but Japanese), Skype, and Temple Run, none of which require root access.
shadowmonk36 said:
I was playing with my TF101 earlier today and went to check Titanium Backup when I was given a surprise, I can't use it anymore. My tablet had been rooted since the day I got it nearly a year ago but somehow my busybox got uninstalled. I have not done anything that would cause it to be uninstalled, and when I try to install it again no program is able to. When trying to update the Su binary Superuser fails to gain root access as well, so something weird happened in the past few days (looking at my most recent Titanium Backups manually it seems it happened after 6/3, but I don't know why).
My first attempt to fix was re-flash the most recent Honeycomb-based Revolver update (3.11.1) and run "Fix Permissions" but that didn't help. I'm thinking the only way to be able to fix this is to do a wipe and re-install of everything, or even a new nvflash, but my most recent backup is months old (I'd been travelling and not messing with ROMs so I didn't have a need for a backup).
Does anyone have suggestions as to what else I can do before I try and do a wipe/install?
Thanks
Click to expand...
Click to collapse
Don't do the wipe yet, just use Recovery to reinstall the same ROM and it may help. It maybe related to kernel or /system/bin or /system/xbin (or even etc).
I tried reflashing the most recent Revolver Honeycomb update (3. 11.1) but it didn't help, still have the problem.
Re-manually install busybox and SU using the superuser.zip that's flashable in cwm, then Install SuperSU and update binary with that. Should fix all issues, I prefer SuperSU to superuser since it doesn't glitch as much. xD
Thing O Doom said:
Re-manually install busybox and SU using the superuser.zip that's flashable in cwm, then Install SuperSU and update binary with that. Should fix all issues, I prefer SuperSU to superuser since it doesn't glitch as much. xD
Click to expand...
Click to collapse
I will give that a try, as soon as I can find the superuser.zip file in question. I googled for it, and looked on XDA but I can't seem to locate it. Could you help point me in the right direction?
I re-thought about what tingtan said and I realized that just an update wouldn't necessarily have everything needed so I found the most recent full ROM and flashed it followed by the update and it looks like things are fixed.
I'd still like a link to that superuser.zip file for the future, but now I can backup and I might try playing with ICS now.
Superuser.zip link: http://androidsu.com/superuser/
I prefer SuperSU though, all preference.
Thing O Doom said:
Superuser.zip link: http://androidsu.com/superuser/
I prefer SuperSU though, all preference.
Click to expand...
Click to collapse
Thanks, that is the one I found but since you were talking about SuperSU I wasn't sure if it was correct. I will also give SuperSU a try, but after I reflash everything (it broke again shortly after I got my titanium backup done).
I was originally rooted by using invisiblek's original "stock" root, which contained some Sprint stuff, so I opted to do a clean start from a stock Verizon rom, but to save time I rooted using the adb script method from GS3DebugFSRoot http://forum.xda-developers.com/showthread.php?t=1792342 instead of Root66, which requires a 1.5 GB image download then must be flashed through Odin.
I did this to avoid some of the strange app behaviors from the rooted "Sprint" rom, but after rooting through adb with an automated script, some root apps don't function properly, even though they're getting root permission.
After doing some research and restoring my sprint NAND backup several times to compare, the main things I noticed are:
1. After rooting through adb, the Superuser.apk app is installed in /data/app (which is a user app location) as opposed to /system/app in the case of the flashable root method.
2. Superuser.apk is called com.noshufou.android.su-1.apk instead
3. Superuser.apk from a flashed rom has these permissions (seen using root-expl)
rwsr-sr-x, but the adb method file xxxxxx.su-1.apk has these permissions rwxrwxr-x
4. The owner of the file is "root" when flashed through Odin, but "system" when rooted with adb.
Otherwise, the su binary itself is ok, it is a newer version and larger in size compared to the flashed versions, but it has the right permissions and is located correctly in /system/xbin.
I tried deleting the xxxxx.su-1.apk in /data/app and copying Superuser.apk to /system/app, to make it a system app, reset permissions and "owner" and "group" to root, but lost root after rebooting, so had to start back from my NAND backup again.
Does anyone know how to make Superuser a system app in the /system/app folder without losing root?
Also, I'm not sure this is the cause, but Titanium Backup has a hard time detecting root every time I start it, and has to be restarted multiple times, which wasn't a problem when flashed root w/ Odin, and most importantly, DroidWall is not blocking ANYTHING, whether it's in whitelist or blacklist mode, which it did when I used Odin to flash a rooted rom. I've tried everything, bu to no availe, can a dev that might have an idea what is going on here, help me with this and point me in the right direction to look for what to fix to get DroidWall to work, and if that is causing these issues, to get Superuser installed in the right folder?
Thank you
Nvm, I can't seem to find it again, I know I saw it somewhere though. If this was the OG Droid or Droid 2 I could tell you how to adb push no problem, but it's my first Samsung device. I don't know if anything is different, and I don't wanna be responsible for a brick :S
I bought this phone yesterday, Rooted this morning before work, Voodoo backed it up, and updated to the newest update,
Now when I try to Restore root everything looks grand except Superuser says the su binary is not found.
The su binary is located in /system/bin I believe or xbin but none the less its there. some apps can access root while other cannot..
Any Ideas anyone can give me besides rooting once again, Not an option at work.
Thanks in advanced,
If not let me know and Ill Root again once I'm home, Just looking to play on the slow day.
It's been my experience that on this particular phone Voodoo OTA Root Keeper isn't effective. Simply save the SuperSU.zip on your external SD card and reflash via custom recovery after updating..
The only thing simple is the belief in simplicity.
Haven't Bootloader unlocked yet, used the moto2failgo, or how ever it was to root this morning, so this is what it will be once again once I get home, Thanks for the response, Makes my wonder, the only App that continues to function with root access (aside from Voodoo its self) is Titanium Backup, I am wondering if this is because it has its own busybox and i had not install busybox prior to the update, and cannot now due to lost root.