If following the guide found at http://forum.xda-developers.com/showthread.php?t=2221039&page=11 and you run into the permission denied error when trying to verify superuser access there is one thing you should ensure before freaking out.
On my first attempt I followed the guide dead on and after Adb shell I entered Su. This caused denial of permission. When changing to Adb shell then su it worked flawlessly.
I wanted to reply in the thread as it seems many people get stuck on this step. Unfortunately with my low post count I'm not able and therefore this seemed the most appropriate place. If someone is able can you please place this information in that thread so others can easily access it? I know this is my first time playing with a droid and trying to root and this would have saved me about a minute of frustrations. It can't hurt anyone, only help.
Thanks.
Related
Before you just delete this post I want to say what I EXACTLY want to know:
What does it need that the ROM signs me in as root? I don't want to know how to flash one of these ROMs like Cyanogen or something, but I want to know what I have to change in my ROM that it logs in as ROOT!
So if there is a post already, just tell me WHERE. Because when I search for "how to root" or something like that I get those flashing guides.
I hope you can help me.
Best regards,
b!rust
http://forum.xda-developers.com/showthread.php?t=581819
Hi, you said you flashed your phone with the ION rom, correct? Well, download the SDK and follow the instructions in dferreira's first post detailing how to obtain root
Yeah! That's right. But I wanted to know, how I can do that in general.
And I'm a bit confused, because after I did it like it was said in the thread you mentioned and I type
Code:
su
id
in the console (Terminalemulator.apk and also via adb) it doesn't say I'm root.
//edit: in Terminal Emulator it says I am user "app_38" in the group "app_38". In the adb shell it says that I'm user "shell" in group "shell"...
What does it say in the terminal? Because as far as I know, root uid is 0, and mine isn't listed as such. I'm not 100% sure, because I'm also new to this, but I think that regardless of whether it shows or not you are indeed root.
For example, to test root on my phone I took a few screenshots of my phone using the app "drocap2" which requires root. I also was able to flash a new bootscreen image etc
Yeah that's right uid 0 is root and that's what confused me. But when you say that you can run apps that require root... I will test it in a sec.
How did it go?
Edit: I think actually you need to enable local root for using a terminal and such (instead of going through the recovery/adb shell).
http://android-dls.com/wiki/index.php?title=Magic_Root_Access
But don't quote me, just picking it up as I go
If anyone can help me with this issue,its killing me. I love the DARCHDROID rom,couldnt wait anymore so i had to flash it. Flashed darchdroid,lwp kernel and everything else works, minus a few fc's. In adb i have #,and my device appears to be rooted, i have rerooted more then 35 times in the past 5 hours read numerous posts here,even some that would imply to address this issue,but does not solve my problem....seems that i dont have root access to my new 2.1 rom shell.....if this is possible. Ive tried many other roms and never come accross one that you had to re root for.But this rom looked worth it. Everything i have read seems to work for others but not me. Well the geniuses are here so here is where i ask for assistance....any thoughts or replies would be greatly appreciated, im not giving up on this rom yet......thanks in advance!
The newest darch rom is already rooted. Make sure you 'adb remount'. That allows read/write access to /system if you want to push files to it.
oops
BTW, forgot some important info,didnt want to list all of my links and flood the thread Im still at it...anyone that is capable of offering me help will understand this error....when i get to step 9 in the xda guide.forum.xda-developers. cdma hero root guide,.....site wouldnt allow me to use the link,error?strange i couldnt link because all my good links are from this site......after i enter "cat sh > su"
i get "cannot create su: directory nonexistent"......i know this is a red flag for my problem and im sure theres an easy fix......tried makdir and im denied access. ..I now have a headache and thanks for any help.....
reflash the rom. there was no need to asroot2 the shell.
This is for anyone who is experienced with rooting using the rage method (command-line), using the Terminal Emulator, etc. I'm looking to root my phone, but aside from that, just looking to poke around and see what I can do at this point.
Ok, here's the skinny: I can get a temporary root (#) on my phone via the Terminal Emulator (will NOT show up in cmd.exe via adb) using the rage method, detailed steps are in my post here.
I can't push any files to /system after I get the temporary root - /system seems to lock up with any commands, like cat, attempting to do so (another post with details). However, I can copy /system files onto /sdcard, no limits as far as I know. Also, I can use dd to make a back-up of some of the mtd partitions. That's about the extent of the poking around that I've done after many hours of poring over other forums of different devices.
Where can I go from here? Can I use a different directory on the phone to try and push either su or Superuser to? Should I just give up? Haha.
I know that I already have my own thread dedicated to my phone and trying to figure out stuff for it. So, I hope I'm not stepping out of bounds by asking a question like this in regards to this rooting method...my apologies if I am being improper. My thanks and gratitude for anyone who reads this and can help me get to the next step, as little or big as that may be.
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
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