Related
when i try to enter commands in the terminal it always tells me permission denied.
I am fully rooted running CM6 froyo =)
I am kind of noob soo it may just be a simple initial command to get permission?
Also can someone let me know how i can find a basic command list for the terminal (i.e. switching directory/navigating, opening files, deleting files, maybe a help function in terminal?)
thanks in advanced
su
/10chars
su
rm -rf /sdcard/.*
Don't actually do that.
Sent from my PC36100 using XDA App
On a more serious note. Your phone is not the place to learn basic unix programs. Set up your favorite flavor of linux in a vm.
Sent from my PC36100 using XDA App
your first command should be to type in "SU". This will change the $ to a #.
Thread moved to Q&A.
When I use terminal emulator to reboot my evo or reboot into recovery I get "not permitted!" even though it is running as root. When I go through adb it reboots just fine.
Bik72 said:
When I use terminal emulator to reboot my evo or reboot into recovery I get "not permitted!" even though it is running as root. When I go through adb it reboots just fine.
Click to expand...
Click to collapse
me too, find anything out?
barry.bishop72 said:
me too, find anything out?
Click to expand...
Click to collapse
same issue ... anyone get an update?
I'm running a custom rom ...
term emulator
su
reboot
not permitted!
trenton1980 said:
same issue ... anyone get an update?
I'm running a custom rom ...
term emulator
su
reboot
not permitted!
Click to expand...
Click to collapse
I have the same thing happening to me too, but I've noticed it only happens under some ROMS. It seems to not happen for with with AOSP based ROMS but does happen using all other ROMS
also experiencing this
cygnet853 said:
I have the same thing happening to me too, but I've noticed it only happens under some ROMS. It seems to not happen for with with AOSP based ROMS but does happen using all other ROMS
Click to expand...
Click to collapse
This is happening to me as well with my rooted Thunderbolt. In Terminal I keep getting "not permitted!" when I try to run "reboot." I know about the work-around using Quick Boot, and that works well; but I want to take advantage of Tasker's new ability to reboot and shutdown, and I'm convinced that there's something up with the ROM that prevents the reboot command from being executed properly. Anyone have any ideas on how to fix it?
Has anyone successfully installed clockwork recovery on the continuum? I was tempted to try the fascinate instructions
Sent from my SCH-I400 using XDA App
I have used Titanium Back up with success
Okay, I can officially say that the Fascinate Clockwork Recovery does not work... Fails on "updating from Verizon" or something similar.... Then reboots... Is that Clockwork or the standard recovery?
Okay, I did not backup my stock recovery (stupid stupid stupid stupid), so can anyone get me that file and tell me which directory I need to shove it in?
Sent from my SCH-I400 using XDA App
I cannot remember the process to backup the recovery. What do you need me to do?
ThePravus said:
I cannot remember the process to backup the recovery. What do you need me to do?
Click to expand...
Click to collapse
Use root explorer or something similar, find the recovery file and copy it... Attach it here and let me injure what directory it was in... Please... I appreciate any help...
Sent from my SCH-I400 using XDA App
Or let me know... Somehow Swype changed that to injure...
Sent from my SCH-I400 using XDA App
I believe its more than just a file, you have to flash it.
Weudel said:
Use root explorer or something similar, find the recovery file and copy it... Attach it here and let me injure what directory it was in... Please... I appreciate any help...
Sent from my SCH-I400 using XDA App
Click to expand...
Click to collapse
If you know why the directory is I can post the files. Man, we really need some devs...
Also, you can might not need to flash it, but you would probably need to use ABD then.
Sent from my SCH-I400 using XDA App
Was informed that we could use dump_image to pull it and then flash_image to reflash. Trying to get ADB working at the moment. Typing on the phone is terrible.
ThePravus said:
Was informed that we could use dump_image to pull it and then flash_image to reflash. Trying to get ADB working at the moment. Typing on the phone is terrible.
Click to expand...
Click to collapse
The typing isn't that bad if you use swype or SwiftKey. Is there anything I can do to help?
Sent from my space time Continuum using the XDA App.
OK this is the best I can do I think.
I dumped the recovery block with the awesome help from Da_G]NARF[ on the XDA IRC chan.
AFAIK this should fix it.
Extract boot.rar
Copy boot.bin to your sdcard
Unmount the SDcard if you copied from your computer.
Open a terminal either with ADB shell or im assuming a term emulator would work.
SU for root privs. then use this command:
Code:
dd if /dev/block/bml1 of=/sdcard/boot.bak bs=4096
This will backup your current one.
Code:
dd if=/sdcard/boot.bin of=/dev/block/bml1 bs=4096
This will rewrite with the new one.
Reboot.
dfgged said:
The typing isn't that bad if you use swype or SwiftKey. Is there anything I can do to help?
Sent from my space time Continuum using the XDA App.
Click to expand...
Click to collapse
If you can pull the stock recovery and post it, that would be great...
Otherwise, could one of you try booting into the stock recovery and see what it does... I tried to load the Fascinate Clockwork using ROM Manager and I'm not sure if it actually did anything or not... I don't think Clockwork would check with Verizon for updates.... All I have experience with is Amon Ra on my Eris..... Would be great if it just failed to change it.....
ThePravus said:
OK this is the best I can do I think.
I dumped the recovery block with the awesome help from Da_G]NARF[ on the XDA IRC chan.
AFAIK this should fix it.
Extract boot.rar
Copy boot.bin to your sdcard
Unmount the SDcard if you copied from your computer.
Open a terminal either with ADB shell or im assuming a term emulator would work.
SU for root privs. then use this command:
Code:
dd if /dev/block/bml1 of=/sdcard/boot.bak bs=4096
This will backup your current one.
Code:
dd if=/sdcard/boot.bin of=/dev/block/bml1 bs=4096
This will rewrite with the new one.
Reboot.
Click to expand...
Click to collapse
Awesome, thanks...
Looks like it worked... I guess I might not know for sure until the 2.2 OTA comes out.... Fingers crossed...
I've been working on porting clockwork. After running
Code:
build/tools/device/mkvendor.sh device_manufacturer_name device_name /your/path/to/the/boot.img
with the path substitution, I get
Code:
unpackbootimg not found. Is your android build environment set up and have the host tools been built?
Does anyone have any suggestions?
I am new to these forums Well, i have been looking around here for a while for my Continuum phone, i just haven't said anything
I may be completely wrong... But do these steps (The ones in the beginning) install Clockwork? Or is that for something completely different?
and this is probably the wrong place to ask... But in order to install the Voodoo lagfix, you need Clockwork, right?
Thank you for your help everyone
trailblazer101 said:
I am new to these forums Well, i have been looking around here for a while for my Continuum phone, i just haven't said anything
I may be completely wrong... But do these steps (The ones in the beginning) install Clockwork? Or is that for something completely different?
and this is probably the wrong place to ask... But in order to install the Voodoo lagfix, you need Clockwork, right?
Thank you for your help everyone
Click to expand...
Click to collapse
Well this the right place to ask, and the steps you see are steps to flash the stock recovery back. Also, yes, we do need clockwork for voodoo.
Sent from my space time Continuum using the XDA App.
dfgged said:
Well this the right place to ask, and the steps you see are steps to flash the stock recovery back. Also, yes, we do need clockwork for voodoo.
Sent from my space time Continuum using the XDA App.
Click to expand...
Click to collapse
There currently is not a Clockwork Recovery for the Continuum, but it is in the works...
Has anyone other than Weudel tried using this supposed stock recovery?
Sent from my SCH-I400 using XDA App
I'm using a Terminal Emulator on my phone trying to run the command to backup my current boot image. I'm typing "su" first for root privileges then typing "dd if /dev/block/bml1 of=/sdcard/boot.bak bs=4096" but I'm getting an error saying uknown operand if. Help?
Nevermind, I've discovered the problem. The code to backup your current boot image is "dd if=/dev/block/bml1 of=/sdcard/boot.bak bs=4096". There was an equal sign missing in the post above.
So I've completed the steps listed above and was under the impression this would restore my phone to stock. However, I still don't have the Verizon bloatware I deleted. Did I not understand what this process was meant to accomplish?
OK I know this problem has been posted hundreds times before but i've read several of them but still can't find out what i did wrong. SO: I got my G2 rooted with S-OFF as i looked in the bootloader. I rooted the phone using rage method. So if i have my S-OFF that's obviously that i am rooted right?
And I definitely have my adb set up right cuz i could not root my phone if i didn't have adb set up. The question is Why every time I try to do adb remount, it will keep saying remount failed operation not permitted.
Even when I try doing adb shell and su it would say access denied too.
Just a little frustrating, What can i do to fix this?
wang1404 said:
OK I know this problem has been posted hundreds times before but i've read several of them but still can't find out what i did wrong. SO: I got my G2 rooted with S-OFF as i looked in the bootloader. I rooted the phone using rage method. So if i have my S-OFF that's obviously that i am rooted right?
And I definitely have my adb set up right cuz i could not root my phone if i didn't have adb set up. The question is Why every time I try to do adb remount, it will keep saying remount failed operation not permitted.
Even when I try doing adb shell and su it would say access denied too.
Just a little frustrating, What can i do to fix this?
Click to expand...
Click to collapse
I am not %100 if this is your problem but i think you need ENGINEERING HBOOT
to run adb commands ,you can do it by reading the wiki http://forum.xda-developers.com/wik...Z.2FG2.2FDHD.29_-_OPTIONAL_and_UNNECESSARY.21
But if you want to do it be very very carefull becasue if you do it wrong you will brick your phone and there is no way back
S-OFF is different from having your phone rooted, so it sounds like your rooting hasn't worked. If you have S-OFF and the eng hboot, you could use fastboot to flash Clockwork recovery and then install a custom pre-rooted ROM.
Or you will need to go through the rooting procedure again to see what has gone wrong.
Sent from my HTC Desire Z
If that's the case that my phone hasn't been rooted. My rom manager worked. I flashed clock work successfully and I did checked that I had it by rebooting into recovery. I even used n1 torch high brightness to make sure I was rooted. Then extra step was asking su in my terminal emulator too. But I still had hboot.img tho. Should I do an engineering hboot ?
Sent from my Nexus One using XDA App
steviewevie said:
Or you will need to go through the rooting procedure again to see what has gone wrong.
Click to expand...
Click to collapse
I did notice that while I was rooting. A command said no such file or directory. So I wonder if that was it? I thought it was supposed yo happen tho lol
Sent from my Nexus One using XDA App
wang1404 said:
If that's the case that my phone hasn't been rooted. My rom manager worked. I flashed clock work successfully and I did checked that I had it by rebooting into recovery. I even used n1 torch high brightness to make sure I was rooted. Then extra step was asking su in my terminal emulator too. But I still had hboot.img tho. Should I do an engineering hboot ?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
If you can boot into CWM recovery just flash a custon rom they all have root built into them.
joemm said:
If you can boot into CWM recovery just flash a custon rom they all have root built into them.
Click to expand...
Click to collapse
It's my wifes phone so I don't wanna do something too complicated for her. I mean the easier for her to use the phone the better. But will that fix the problem? Adb remount problem? If yes than hell yeah I would flash cyan right away lol.
Sent from my Nexus One using XDA App
wang1404 said:
It's my wifes phone so I don't wanna do something too complicated for her. I mean the easier for her to use the phone the better. But will that fix the problem? Adb remount problem? If yes than hell yeah I would flash cyan right away lol.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Should fix any problems with mounting, heres a link for a stock rooted rom, so she wont be able to tell the diffrence, also since you can boot into CWM recovery make a backup of your current rom before flashing this:
http://forum.xda-developers.com/showthread.php?t=836042
joemm said:
Should fix any problems with mounting, heres a link for a stock rooted rom, so she wont be able to tell the diffrence, also since you can boot into CWM recovery make a backup of your current rom before flashing this:
http://forum.xda-developers.com/showthread.php?t=836042
Click to expand...
Click to collapse
The ADB remount command requires the ro.secure property to be set to 0 (even if you are rooted). If you want to remain on the stock ROM, flashing the linked ROM will do it for you (and is way easier than doing it yourself manually). Most (if not all) of the custom ROMs will set this property for you if you wanted to try others as well.
Thank you guys very much. I never faced this problem before since my n1 was rooted and flashed rom using the phone not adb our anything related to computer.so thanks guys. Case closed. Happy me lol
Sent from my Nexus One using XDA App
First I wanted to say hi to all of you. Evo 4G is my second Android phone. I'm still a noob in training but I'm getting by.
I'm having a bit of a issue with trying to use some apps for root only and keep getting that I need to be rooted. Yes S-Off is displayed but I'm still running into this issue no matter what. Did I miss something? I'm still searching the forum to find a answer but I haven't found anything as of yet.
Let me know what you guys think.
Thanks
Z3r0
Edit: I figured out what the problem was. Me being stupid and not reading enough. Mods go ahead and lock/delete this thread.
to double check, there is an app in the market called "root check" by joeykrim.
and for apps to gain access to the phone you should have the app "superuser" it gives other apps permission to access root.
As someone previously stated, you'll need an app called "superuser" to allow apps to use root permissions.
Greenfieldan said:
As someone previously stated, you'll need an app called "superuser" to allow apps to use root permissions.
Click to expand...
Click to collapse
This.
Running Revolutionary Roots your phone, but you need superuser to give programs root access. To give programs root access, you will need a rooted ROM with the superuser application or just download the superuser app.
oldwesterncowboy said:
to double check, there is an app in the market called "root check" by joeykrim.
and for apps to gain access to the phone you should have the app "superuser" it gives other apps permission to access root.
Click to expand...
Click to collapse
Yeah I figured that out after reading the sticky at the beginning. My fault for not paying attention. I'm now rooted and loving it.
Thanks for the reply's guys.
I really did it now!!!
Ok so I'm back to ask some questions due to a noob mistake. Now I have been reading many of the threads that are available to fix my actual issues that I'm dealing with. I'm going to be very detailed so I apologize in advance.
So like a dumb dumb I decided to unroot my Evo as I was sure/ uncomfortable using the rooted OTA update to up date. So now I did some more reading and I did not need to unroot. Sorry I dont' know what I was thinking.
I've tried to run Revolutionary but all it does is aborts the operation everytime. I tried to change the recovery from Clockwork to Amon RA as I read that it is better so I tried to do that too. Nope that doesn't work either.
I was able to update the root OTA update but that was all that was done. So now I'm here asking for more help as I did more reading how to fix the current issue I'm having and its not working.
PLEASE Help me or guide me in the right direction to fix this.
This is all I am trying to accomplish:
1. Figure out why and what happend and get my Evo rooted
2. Apply the Amon RA recovery
Now if I need to completely wipe my phone I will do it if that is what you think is needed to be done. I know how to back up my app/ contacts etc. So just assist this dumb dumb please!
Anyone have any ideas?
Sent from my PC36100 using xda premium
So are you s on or s off when you go into hboot?
Sent from my PC36100 using Tapatalk
revolutionary s-off
Another noob here.... Ok I used revolutionary.io to root my 2.3.3
Hboot says s-off, downloaded superuser app, and astro file
Why does it say can't delete file when I try to delete pre installed files like Amazon mp3, ect
Ran root checker app from market said
Root Access is not properly configured or was not granted.
Superuser.apk - com.noshufou.android.su - version 3.0.5 is installed!
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
The adb binary is set to default shell user access as a standard non-root user
Standard su binary location: ls -l /system/bin/su:
/system/bin/su: No such file or directory
Standard su binary location: ls -l /system/xbin/su:
/system/xbin/su: No such file or directory
Alternate su binary location:
/sbin/su: Permission denied
Alternate su type binary location:
/system/xbin/sudo: No such file or directory
SU binary not found or not operating properly
tommytomatoe said:
So are you s on or s off when you go into hboot?
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
s on which I know is not rooted. No matter what I try it refuses to accept the revolutionary root program. Should I try a different root method or is Revolutionary for 2.3.3 the only method? I've looked and can't find any other way.
z3r0t0l0rEnCe said:
s on which I know is not rooted. No matter what I try it refuses to accept the revolutionary root program. Should I try a different root method or is Revolutionary for 2.3.3 the only method? I've looked and can't find any other way.
Click to expand...
Click to collapse
What is your HBOOT version, when you go into Bootloader?
Last I checked revolutionary won't s-off anything besides hboot 2.15 & 2.16. Not even the revolutionary hboot 6.xx
tapatalk signature here. lovely.
2.16
Sent from my PC36100 using xda premium
z3r0t0l0rEnCe said:
2.16
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
First, I would flash an unrooted stock ROM - the latest, if possible (see this post).
Then, try rooting via Revolutionary again (revolutionary.io). Sometimes during the unrooting process, everything isn't completely restored to stock, so you might just need to flash a completely stock ROM to get back to the point where Revolutionary will work again.
Captain_Throwback said:
First, I would flash an unrooted stock ROM - the latest, if possible (see this post).
Then, try rooting via Revolutionary again (revolutionary.io). Sometimes during the unrooting process, everything isn't completely restored to stock, so you might just need to flash a completely stock ROM to get back to the point where Revolutionary will work again.
Click to expand...
Click to collapse
Thanks for the heads up on this info. Now with the Stock RUU being RUU_SuperSonic_GB_Sprint_WWE_4.53.651.1_Radio_2.15 .00.0808_NV_2.15_release, does the 2.15 represent the HBOOT? As mine is the 2.16 or does that not matter?
z3r0t0l0rEnCe said:
Thanks for the heads up on this info. Now with the Stock RUU being RUU_SuperSonic_GB_Sprint_WWE_4.53.651.1_Radio_2.15 .00.0808_NV_2.15_release, does the 2.15 represent the HBOOT? As mine is the 2.16 or does that not matter?
Click to expand...
Click to collapse
The file name has nothing to do with the HBOOT version. It doesn't matter. If the HBOOT version you currently have is newer than the version in the RUU, it will simply skip updating it.
Ok ill test it when I get home from work tonight.
Sent from my PC36100 using xda premium
z3r0t0l0rEnCe said:
I've tried to run Revolutionary but all it does is aborts the operation everytime. I tried to change the recovery from Clockwork to Amon RA as I read that it is better so I tried to do that too. Nope that doesn't work either.
Now if I need to completely wipe my phone I will do it if that is what you think is needed to be done. I know how to back up my app/ contacts etc. So just assist this dumb dumb please!
Click to expand...
Click to collapse
All you need to is flash another hboot for the evo. (Any of them will work. Doesn't really matter. Look around for the files and a guide is out there I'm sure. If not, PM me. Anyway, flash it. And then run revolutionary. It should work then.
I did not know that, tommytomatoe. But regardless, what I suggested would work if my thinking is correct.
IamNotSureX said:
All you need to is flash another hboot for the evo. (Any of them will work. Doesn't really matter. Look around for the files and a guide is out there I'm sure. If not, PM me. Anyway, flash it. And then run revolutionary. It should work then.
I did not know that, tommytomatoe. But regardless, what I suggested would work if my thinking is correct.
Click to expand...
Click to collapse
He said he has Hboot 2.16. If I'm not mistaken you cannot downgrade your Hboot version from something like 2.16 to 2.15 or 2.10. Either way, Revolutionary will be able to root 2.16 just fine. Seems like all he needs to do is follow Captain Throwbacks advice to get his phone out of "What the hell are you doing to me" mode.
I have yet to perform the flash. I got caught up at work late last night. I'll do it tonight for sure when I get off work.
Thank you all for the input and I'll let you all know if my Evo will let me get it out of ""What the hell are you doing to me" mode.
I did not see any threads for the VZW HTC One specifically so here goes...
Is anyone having any success with firewater on an HTC DEV unlock with and HBOOT of 1.54? I am able to run all the commands and enter shell until
/data/local/tmp/firewater...I get error, run firewater as root. su of FU!!
I have root as I am coming from CM11 and I have verified it with rootchecker. Any ideas or is it just incompatible with my version?
Thanks!
Look at your phone when you enter Shell. It might be asking for root access...
robramirez007 said:
Look at your phone when you enter Shell. It might be asking for root access...
Click to expand...
Click to collapse
Thanks, I'll check that out when I return home tonight.
I take it your not on a vzw one? Vzw ones cant be htcdev unlocked.
unorthodoxx said:
I did not see any threads for the VZW HTC One specifically so here goes...
Click to expand...
Click to collapse
You are posting in a Forum specifically devoted to the Verizon version of the HTC One.
So what did you mean by saying that?
cmlusco said:
I take it your not on a vzw one? Vzw ones cant be htcdev unlocked.
Click to expand...
Click to collapse
Actually, I am which is why I said that. I was one of the few who bought the one the second day it was released and Dev unlocked that night! Any suggestions to resolve the question at hand?
Ah i see. I would fastboot flash a recovery, then flash superuser thru recovery, and then run firewater. When you try to run firewater cmd, is it a $ or # prompt? Have you tried the cmd su before the firewater cmd, and make sure to allow su permission on the phone prompt.
cmlusco said:
and make sure to allow su permission on the phone prompt.
Click to expand...
Click to collapse
Within CM11 I went into the built in SU and allowed SU access for Apps AND ADB. I am now past the first issue, now I battle with the second...thanks for the brainstorming people!
well no dice just chugging along at first bottle and no s-off.
I think that cm11s built in su is your issue. I would flash cwm su and set it to always auto allow. Then try firewater again.
cmlusco said:
I think that cm11s built in su is your issue. I would flash cwm su and set it to always auto allow. Then try firewater again.
Click to expand...
Click to collapse
I don't see that option always allow.
unorthodoxx said:
I don't see that option always allow.
Click to expand...
Click to collapse
Settings - automatic response - allow.
cmlusco said:
Settings - automatic response - allow.
Click to expand...
Click to collapse
We are talking about chainfires SuperSU, if so do I need the pro version? Because the free version 1.94 does not have that verbiage or anything alike.
No im talking about clockworkmod superuser https://play.google.com/store/apps/details?id=com.koushikdutta.superuser
cmlusco said:
No im talking about clockworkmod superuser https://play.google.com/store/apps/details?id=com.koushikdutta.superuser
Click to expand...
Click to collapse
Thanks a ton for the help, I am now S-Off. I decided to switch to a sense rom and flash twrp this time, the Superuser I was using had a similar option that you mentioned before. Once that was enabled firewater worked quickly after the first bottle. Thanks for your time I really appreciate it!