Database Info

[Q] Superuser permissions

Hello
Have unlocked the phone and installed custom android OS a while ago, but then all of a sudden i do not have root access anymore, even tryed to reinstall the phone. Though i do have a bad feeling about it wasn't needed
My problems is that im unable to give programs root access, it looks like the phone is not rooted acording to the programs.
Also if i try the following:
adb shell
su
then i get "permission denied"
Can't seem to figure out where my flaw is. Even tryed to
Anyone got an idea to what the problem might be? Have looked through the nexus s forum for clues but no luck.
/Fonain

fonain said:
Hello
Have unlocked the phone and installed custom android OS a while ago, but then all of a sudden i do not have root access anymore, even tryed to reinstall the phone. Though i do have a bad feeling about it wasn't needed
My problems is that im unable to give programs root access, it looks like the phone is not rooted acording to the programs.
Also if i try the following:
adb shell
su
then i get "permission denied"
Can't seem to figure out where my flaw is. Even tryed to
Anyone got an idea to what the problem might be? Have looked through the nexus s forum for clues but no luck.
/Fonain
Click to expand...
Click to collapse
Most likely the permissions on the su binary are f'd up (assuming it's present). The easiest fix is just to reflash the su binary (mount /system first) through CWM.

do you by any chance have a guide to do that? or a link to one?

fonain said:
do you by any chance have a guide to do that? or a link to one?
Click to expand...
Click to collapse
There are several rooting guides here if you do not have CWM installed:
http://forum.xda-developers.com/showthread.php?t=1067813
They will go over quite a few things. However, if you are unlocked and have fastboot set up it's as simple as downloading the recovery image, and then using fastboot to flash the recovery (fastboot flash recovery recovery.image.name.img)
Once CWM is installed boot into recovery and flash the su binary here:
http://forum.xda-developers.com/showthread.php?t=682828

well the funny thing is that i already have 2.3.6.1 installed, but i still dont have su rights.
When i try to follow the buttom guide where to install superuser. where it states that i should write "adb remount". Then i get the message back where it says "Operation not allowed", or when i type su i get the message "permission denied".
I seriously don't understand what i have done wrong :S
/Fonain

krohnjw said:
Most likely the permissions on the su binary are f'd up (assuming it's present). The easiest fix is just to reflash the su binary (mount /system first) through CWM.
Click to expand...
Click to collapse
Thanks for this, solved my issue

thanks figured it out
/Fonain

Sorry to bring back an old topic, but Ive petty much done everything and still the SU no permission no root access for everything occurs. NO TIT backup, no rommanager, no nothing T_T, why???

try chmod the folder/file or using sudo

james7132 said:
try chmod the folder/file or using sudo
Click to expand...
Click to collapse
Can you elaborate please. Whats chmod or sudo and how do I go about doing them?

[Q] motorola i886, halfway rooted... i think

I am trying to root a motorola i886. Its a really wierd nextel iDEN PTT phone that is running (i believe) android 2.0 or 2.1 but has no touchscreen...
Basically I have been able to get a root shell (#) from 'adb shell' by pushing some program called psneuter to the phone and running it. Once I had this I could install apps via adb ok, but it seems like whenever I try to run any apps that require root they error saying they do not have root access.
As far as I can tell pretty much every rooting guide for every other phone has you putting 'su' and sometimes 'busybox' into /system/bin and 'Superuser.apk' into /system/app. I did both of these but still got the same errors about apps not having root. I tried a few different versions of these files I found from different sites to no avail. Running su on a terminal emulator on the phone itself would get the error "operation not allowed" or something like that. Then I found some other guide where you just copy 'sh' to 'su' and chmod su to 4755. When I did that I could get to a # prompt on the phone's terminal emulator app by typing 'su' but still got root errors for apps that need root.
I though maybe someone here would know something that I missed. As far as I can tell, I have applied the correct permissions to all these files or have at least tried every combination I can think of to no avail (shouldn't chmod 777 just make everything work?)
Also, does the phone usually come with a stock version of busybox on it? Do you need a specific version of these files for your device or version of android?
When an app on the phone tries to get root access is it just basically trying to run 'su' internally or something like that?
Also forgot to mention I have tried all the one-click-root apps and they do not work for this stupid phone. (well the super one click one was how I figured out how to get the adb shell root but the regular root button doesn't work...)

I can't help with your specific questions, but there is some info about rooting the i1, another iDEN with Android. Although it looks like the i1 is actually Android, and not the Motorola-altered, not-really-Android, proprietary software that the i886 has.
http://www.howardforums.com/showthread.php/1662431-Motorola-i1-Rooted
http://forum.cyanogenmod.com/topic/5520-ive-rooted-my-i1/

garbb said:
I am trying to root a motorola i886. Its a really wierd nextel iDEN PTT phone that is running (i believe) android 2.0 or 2.1 but has no touchscreen...
Basically I have been able to get a root shell (#) from 'adb shell' by pushing some program called psneuter to the phone and running it. Once I had this I could install apps via adb ok, but it seems like whenever I try to run any apps that require root they error saying they do not have root access.
As far as I can tell pretty much every rooting guide for every other phone has you putting 'su' and sometimes 'busybox' into /system/bin and 'Superuser.apk' into /system/app. I did both of these but still got the same errors about apps not having root. I tried a few different versions of these files I found from different sites to no avail. Running su on a terminal emulator on the phone itself would get the error "operation not allowed" or something like that. Then I found some other guide where you just copy 'sh' to 'su' and chmod su to 4755. When I did that I could get to a # prompt on the phone's terminal emulator app by typing 'su' but still got root errors for apps that need root.
I though maybe someone here would know something that I missed. As far as I can tell, I have applied the correct permissions to all these files or have at least tried every combination I can think of to no avail (shouldn't chmod 777 just make everything work?)
Also, does the phone usually come with a stock version of busybox on it? Do you need a specific version of these files for your device or version of android?
When an app on the phone tries to get root access is it just basically trying to run 'su' internally or something like that?
Also forgot to mention I have tried all the one-click-root apps and they do not work for this stupid phone. (well the super one click one was how I figured out how to get the adb shell root but the regular root button doesn't work...)
Click to expand...
Click to collapse
PM to me,i rooted sucefully, and install many applications with android SDK suite.
Regards.

geminis said:
PM to me,i rooted sucefully, and install many applications with android SDK suite.
Regards.
Click to expand...
Click to collapse
Wow, I can't believe someone found this thread and replied after so long. Thanks, but in the meantime I actually figured out how to root it fully and get root apps to work. I think i just tried different su's and superuser.apk's that I found on the internet until one worked...
Now, if you have figured out how to change the nextel push-to-talk chirp/beep sounds then let me know how you did that. I actually found the .wav files for the PTT sounds in some .apk in /system (phone.apk I think?) but for some reason changing them had no effect on the sound the phone makes when using the push-to-talk feature...

Its been 10 years but do you still have the firmware for this device? I need to flash it, it doesnt finish booting up

I don't have a full ROM .zip file for this phone, only some update .zips. But the first link result for a google search for "motorola admiral stock rom" worked for me for downloading a file.
Wrong phone, sorry.

Sorry but i don't understand. Isn't the Motorola admiral a different device? Does that zip work for the i886? If so, how do I flash it, because the i886 doenst have a recovery mode.

Oh, oops sorry, I was confusing this phone with another one. I looked and I don't have and firmware files for this, sorry.

OK, thanks for replying

[Q] My phone obviously has root... but not according to the shell. Need some help!

Hello xda, I have a bit of a problem:
I have a Samsung Exhibit which I rooted using the zergRush method found here on the forums. At first everything worked fine. But recently I was trying to push a modified system app to my phone using adb and it told me the action wasn't permitted. Checking the shell, and terminal emulator on my phone to see if I had superuser permissions failed. So I went about trying to root my phone again, which according to the zergRush script said was successfull, but checking the shell once again showed that I still did not have superuser permissions. I did a factory wipe of my phone in hopes of trying to get it to root again with no success. But here's the weird part, although it doesn't appear I have root access all my apps that require root access (titanium backup, my screenshot app, and some of widgetlocker's features) still fully function.....
Does anyone have any idea what's going on here? I would love my system folder access back
Thanks in advance.

Dumb question, but your H-Boot shows S-Off? Just covering the bases... Also, do you have Super User installed and functional?

To be honest... I don't know what H-Boot or S-Off means. Pretty new to all of this. Mind giving me a walkthrough? I have superuser installed yes. It's granting programs superuser permissions. But I can't access su in terminal emulator or in the shell.

Well, I'm not the top tier technical person here, so I'm not exactly sure on how to get your problem resumed, since I've not heard of that. On the other hand, there might be a different way to accomplish what you are trying to do.
What are you trying to achieve, pushing a modified system app to do what and where? My suggestion, might be to just put it on your phone through USB to the root folder and then move it in ES File manager, or w/e you use. If all you are doing is pushing.
Obviously ADB shell detects your device, but I'm not sure why it is saying it doesn't have SU access. My other suggestion is to redo the ADB/Android SDK installs. I had a problem where I installed them wrong, by installing too much and ADB did not work properly. So, there might be a chance your phone is fine, but the ADB/SDK are not proper, somehow.
Let me know.

If that were the case, and my phone was fine, wouldn't I be able to access super user through terminal emulator on my phone? Right now when typing su in terminal emulator, the pop up to grant superuser permissions appears but when you allow it to have su permission the # doesn't turn to a $ like it should. The more I think about it the more I think it's a problem with superuser. I've seen people talking about an update to superuser that can break your root? Mehhhh.

Seems like other have had this problem too... Not sure if a nandroid recovery will fix this, otherwise you might have to try to unroot, and then reroot.
Sorry, just might have to do a little more digging than I was able to. Good luck

[Q] Reverted to Stock, stuck in roaming, can't root.

Hi, I'm new to all of this. Yesterday I spent a good 9-10 hours messing with my phone, rooting, flashing CM10 with CWM, realizing data doesn't work on it, and trying to revert back.
I finally managed to revert back to stock this afternoon via (http://forum.xda-developers.com/showthread.php?t=1762204), but the stock provided in the OP left me on a startup loop. So I used (http://samsung-updates.com/device/?id=SCH-I535) in the comments, which worked. I am running SCH-I535, so that's all well and good, but after flashing with Odin, I got an error that I was apparently "roaming". Not sure if this is common when reverting to stock or not, but I'm not sure if it's a big deal either, since I was looking to switch to AOKP instead. BUT, I can't root now. I'm using "Root Debug FS" to root, which worked for me each time before. Now I'm getting the following messages:
Code:
Step 1 - Setup...
Copying files:
Copying su:
failed to copy 'su' to '/data/local//su': Permission denied
Copying debugfs:
failed to copy 'debugfs' to '/data/local//debugfs': Permission denied
Copying debugfsinput:
failed to copy 'debugfsinput' to '/data/local//debufsinput': Permission denied
...done copying files.
Linking /system to tmp...
failed on '/data/local/tmp' - Permission denied
link failed File exists
...done linking /system
Rebooting...
(If you see the following error...
...Press any key to continue...)
Unable to chmod /data/local/debugfs: No such file or directory
/system/bin/sh: can't open /data/local/debugfsinput: No such file or directory
Cleaning up...
Restoring tmp...
rm failed for /data/local/tmp, Permission denied
failed on '/data/local/tmp.bak' - No such file or directory
...done restoring tmp
Removing files...
rm failed for /data/local/su, No such file or directory
rm failed for /data/local/debugfs, No such file or directory
rm failed for /data/local/debugfsinput, No such file or directory
...done removing files.
Rebooting...
Testing superuser...
/system/bin/sh: /system/xbin/su: not found
uid and gid should be 0.
Are they? (y/n)
Root not achieved, device needs to reboot. You may want to try running this tool again.
Your device region may not be supported if you see this message again.
Press any key to continue...
I tried googling this and browsing these forums, but to no avail. Any help would be greatly appreciated.

I too jumped the gun.
Pharien said:
Hi, I'm new to all of this. Yesterday I spent a good 9-10 hours messing with my phone, rooting, flashing CM10 with CWM, realizing data doesn't work on it, and trying to revert back.
I finally managed to revert back to stock this afternoon via (http://forum.xda-developers.com/showthread.php?t=1762204), but the stock provided in the OP left me on a startup loop. So I used (http://samsung-updates.com/device/?id=SCH-I535) in the comments, which worked. I am running SCH-I535, so that's all well and good, but after flashing with Odin, I got an error that I was apparently "roaming". Not sure if this is common when reverting to stock or not, but I'm not sure if it's a big deal either, since I was looking to switch to AOKP instead. BUT, I can't root now. I'm using "Root Debug FS" to root, which worked for me each time before. Now I'm getting the following messages:
Code:
Step 1 - Setup...
Copying files:
Copying su:
failed to copy 'su' to '/data/local//su': Permission denied
Copying debugfs:
failed to copy 'debugfs' to '/data/local//debugfs': Permission denied
Copying debugfsinput:
failed to copy 'debugfsinput' to '/data/local//debufsinput': Permission denied
...done copying files.
Linking /system to tmp...
failed on '/data/local/tmp' - Permission denied
link failed File exists
...done linking /system
Rebooting...
(If you see the following error...
...Press any key to continue...)
Unable to chmod /data/local/debugfs: No such file or directory
/system/bin/sh: can't open /data/local/debugfsinput: No such file or directory
Cleaning up...
Restoring tmp...
rm failed for /data/local/tmp, Permission denied
failed on '/data/local/tmp.bak' - No such file or directory
...done restoring tmp
Removing files...
rm failed for /data/local/su, No such file or directory
rm failed for /data/local/debugfs, No such file or directory
rm failed for /data/local/debugfsinput, No such file or directory
...done removing files.
Rebooting...
Testing superuser...
/system/bin/sh: /system/xbin/su: not found
uid and gid should be 0.
Are they? (y/n)
Root not achieved, device needs to reboot. You may want to try running this tool again.
Your device region may not be supported if you see this message again.
Press any key to continue...
I tried googling this and browsing these forums, but to no avail. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Well i too jumped the gun, After installing CM 10.1 build 18 i think it was, my phone has been with no service even with stock OS. I'm super noob at this stuff, and there are so many threads leading me in circles. i'm almost considering buying a new phone....

In betting both of you need to go back to a stock ICS and use the reprovision code in the dialer. You can Google that code. Before doing that check to make sure you have a imie.
To the OP you flashed the latest JB correct, you never said which one you used. If that's the case the root method you're trying will not work. Under development there us a thread for rooting the Jb update.
. LISTEN TO THE POSTER AFTER ME. I THINK HE HAS MORE EXPERIENCE WITH THE CM10.1 THEN I DO AND I MAY BE GIVING YOU EXTRA WORK!
If I helped you in some way.... pass on the favor and help the next person!

ssphaneuf said:
Well i too jumped the gun, After installing CM 10.1 build 18 i think it was, my phone has been with no service even with stock OS. I'm super noob at this stuff, and there are so many threads leading me in circles. i'm almost considering buying a new phone....
Click to expand...
Click to collapse
Flash an unofficial build and change your mobile settings > cdma subscription to ruim/sim and toggle airplane mode.
Sent from my SCH-I535 using xda app-developers app

kintwofan said:
In betting both of you need to go back to a stock ICS and use the reprovision code in the dialer. You can Google that code. Before doing that check to make sure you have a imie.
To the OP you flashed the latest JB correct, you never said which one you used. If that's the case the root method you're trying will not work. Under development there us a thread for rooting the Jb update.
. LISTEN TO THE POSTER AFTER ME. I THINK HE HAS MORE EXPERIENCE WITH THE CM10.1 THEN I DO AND I MAY BE GIVING YOU EXTRA WORK!
If I helped you in some way.... pass on the favor and help the next person!
Click to expand...
Click to collapse
I do seem to have an IMEI. And yes, I flashed the latest build, sorry for lack of clarity. I'll go ahead and look up a stock ICS, though I'm not sure what a reprovision code is, could you explain?

Pharien said:
I do seem to have an IMEI. And yes, I flashed the latest build, sorry for lack of clarity. I'll go ahead and look up a stock ICS, though I'm not sure what a reprovision code is, could you explain?
Click to expand...
Click to collapse
Flash an unofficial build and change your mobile settings > cdma subscription to ruim/sim and toggle airplane mode.
Sent from my SCH-I535 using xda app-developers app

ajrty33 said:
Flash an unofficial build and change your mobile settings > cdma subscription to ruim/sim and toggle airplane mode.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Ah, sorry, thought you might just be replying to the other guy. I can't seem to access the "mobile networks" settings, as it's grayed out. Am I looking in the wrong area? Settings > More settings > Mobile networks
EDIT: I downgraded from JB to ICS in hopes that that would restore data working on my phone. Nothing. I'm going to hold off on bothering with AOKP, because if it's not working on stock, I doubt it'll work on a custom ROM.
I still can't figure out how to change cdma subscription to ruim/sim. "Mobile networks" is no longer grayed out, but I don't see an option for cdma subscription or anything similar.
Any help? Other suggestions?

You most likely lost you imei/min or something, you can check in settings>about phone>status. Easy way to correct it is to flash a older stock ICS image and use the reprovision code. Flash this in odin then type this in the dialer *2767*3855# and that should fix ya back up. Flashing anything carries a risk of dropping your imei but it happens much more on AOSP roms.

http://forum.xda-developers.com/showthread.php?p=35600769
Read post 2
Sent from my SCH-I535 using xda app-developers app

x714x said:
You most likely lost you imei/min or something, you can check in settings>about phone>status. Easy way to correct it is to flash a older stock ICS image and use the reprovision code. Flash this in odin then type this in the dialer *2767*3855# and that should fix ya back up. Flashing anything carries a risk of dropping your imei but it happens much more on AOSP roms.
Click to expand...
Click to collapse
Hmm, that stuck me on a boot loop. I'll try to find another stock ICS. When I dialed that under JB, it sent me to a Verizon line, was that supposed to happen? Is there anything I'm supposed to do from there?
Nevermind! Tried the code under ICS and it worked! Thank you so much to everyone for your help. You're fantastic!

Pharien said:
Hmm, that stuck me on a boot loop. I'll try to find another stock ICS. When I dialed that under JB, it sent me to a Verizon line, was that supposed to happen? Is there anything I'm supposed to do from there?
Nevermind! Tried the code under ICS and it worked! Thank you so much to everyone for your help. You're fantastic!
Click to expand...
Click to collapse
Ya it wont work on JB, it only works on early versions of ICS. They removed it due to a exploit where someone can trigger that code and wipe your phone and crap.

[Q] /system/ rewriting itself

Hi everyone,
I have an HTC One XL telstra mobile and spent 5 hours yesterday unlocking the boot loader, installing CWM and getting root.
Ive verified I have root with an app called root checker basic. Yes I know 5 hours seems excessive so I havent mentioned the entire day spent finding documentation to do it.
So now I'm trying to copy an apk to the /system/app/ folder which has permission 755. Attempt 1 just doesnt do anything attempt 2 reboots the phone. I have changed the permission to 777 same result.
I have copied the apk to /system/ which is also 755 and it goes in. But when I reboot its gone.
The question is could something be protecting the directory and rewriting it on each boot?
Steve

steve-sydney said:
Hi everyone,
I have an HTC One XL telstra mobile and spent 5 hours yesterday unlocking the boot loader, installing CWM and getting root.
Ive verified I have root with an app called root checker basic. Yes I know 5 hours seems excessive so I havent mentioned the entire day spent finding documentation to do it.
So now I'm trying to copy an apk to the /system/app/ folder which has permission 755. Attempt 1 just doesnt do anything attempt 2 reboots the phone. I have changed the permission to 777 same result.
I have copied the apk to /system/ which is also 755 and it goes in. But when I reboot its gone.
The question is could something be protecting the directory and rewriting it on each boot?
Steve
Click to expand...
Click to collapse
There is a write protection on the system partition within hboot 2.14 and up. Some roms have a built in script that mounts it writable it can also be bypassed within twrp.