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?
Related
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
Attempting to root my G2 following this method. http://forum.xda-developers.com/showthread.php?t=928160
I installed Terminal Emulator and it keeps force closing, so I found another one called Android Terminal Emulator on the market and installed that. It opens up and I see the following line:
export PATH=/data/local/bin:$PATH
$ $
I have an active cursor but guide did not mention that I'd see this or that one of the Terminal Emulators would keep force closing on me. I'd post this in the original thread but I'm not allowed apparently. Any help would be appreciated!
After your temp rooted with Visionary, you open terminal emulator and type "su" without the quotes. That will cause a superuser popup that you need to accept and then you should see a # sign and then you can continue with the rooting process.
Awesomeness.. thank you. Just wanted to be sure I was doing everything right! I think I was successful. I don't own a brick and when I booted into Recovery it says S-OFF. I have yet to flash a ROM. Can I get rid of Visionary at this point?
killswitch11 said:
Can I get rid of Visionary at this point?
Click to expand...
Click to collapse
Yes
Sent from my Vision using XDA Premium App
killswitch11 said:
Awesomeness.. thank you. Just wanted to be sure I was doing everything right! I think I was successful. I don't own a brick and when I booted into Recovery it says S-OFF. I have yet to flash a ROM. Can I get rid of Visionary at this point?
Click to expand...
Click to collapse
Yep. Your rooted and ready to flash roms!
Sent from my HTC Vision using XDA App
Running CM9, set root access to ADB and apps yet my adb doesn't detect my T989. I'm running CM9 on my T300T and ADB works just fine. Anybody else have the same problem and can offer a solution?
Are you sure all your drivers have been installed properly for your phone... If not problem solved click here
playya said:
Are you sure all your drivers have been installed properly for your phone... If not problem solved click here
Click to expand...
Click to collapse
Thanks! My T989 worked pre-CM9 so I believe my drivers should be updated. I'll double check the drivers and also check your link out
mcho19 said:
Running CM9, set root access to ADB and apps yet my adb doesn't detect my T989. I'm running CM9 on my T300T and ADB works just fine. Anybody else have the same problem and can offer a solution?
Click to expand...
Click to collapse
Is it not seeing the phone at all? have you tried adb devices? The only issue i have usin ADB on CM9 or AOKP is the ability to mount system as r/w. Like "adb remount" returns with an error saying i dont have the permissions.
elesbb said:
Is it not seeing the phone at all? have you tried adb devices? The only issue i have usin ADB on CM9 or AOKP is the ability to mount system as r/w. Like "adb remount" returns with an error saying i dont have the permissions.
Click to expand...
Click to collapse
Again use the above link posted I had this same problem with the Sprint variant and CM9. Also the above app by Chainfire - "who makes nothing whack" will also work on stock kernels
playya said:
Again use the above link posted I had this same problem with the Sprint variant and CM9. Also the above app by Chainfire - "who makes nothing whack" will also work on stock kernels
Click to expand...
Click to collapse
Thanks! All i had to do was "adb kill-server" and replug the phone in. *facepalm* i feel stupid xD
Hi all, I wanted to make a logcat, because, believe me, even I hate submitting a bug without a logcat.
So, I searched up on Google and and learnt how to do one using terminal emulator. My questions:
1: Does the terminal emulator session run even after flashing a mod to your rom, and let's say, the phone doesn't boot up?
2. How to stop the the logcat and save it? The command, logcat > /sdcard/ apparently doesn't work because new things keep on happening and I can't type that fast.. So how do I do it?
(And BTW, I have tried using alogcat but doesn't work on jb)
any help would be appreciated.
Thanks!
https://sites.google.com/site/androidsamurai/Home/adb-for-dummies-1
http://forum.xda-developers.com/showthread.php?t=1747544
http://mobility.forumsee.com/a/m/s/p12-9379-050574--installing-adb-sdk-and-how-make-logcat.html
https://sites.google.com/site/androidhowto/how-to-1/save-logcat-to-a-text-file
Lloir said:
https://sites.google.com/site/androidsamurai/Home/adb-for-dummies-1
http://forum.xda-developers.com/showthread.php?t=1747544
http://mobility.forumsee.com/a/m/s/p12-9379-050574--installing-adb-sdk-and-how-make-logcat.html
https://sites.google.com/site/androidhowto/how-to-1/save-logcat-to-a-text-file
Click to expand...
Click to collapse
Thanks a bunch, the links were helpful, especially the last one. But I still can't save it, I can't type that fast! Its like i type the word 'logcat' and something new happens and its gone!Or is it just impossible to do from terminal emulator?
Sent from my One V using xda app-developers app
do the following
su
logcat > /sdcard/namehereforlogcat.txt
Lloir said:
do the following
su
logcat > /sdcard/namehereforlogcat.txt
Click to expand...
Click to collapse
Great.
But q no. 1..?
Sent from my One V using xda app-developers app
you dont, you run it via adb logcat on your pc terminal
So i was going to flash over a 4.4 rom to my Galaxy nexus, but since i was very tierd i didn't pay to much attention to what i was doing. I flashed in the rom but forgot to flash in the gapps, and for some reason CWM got deleted. So now im running 4.4 with no gapps and no CMW. And that's not all.. the worst thing is that my usbport seems to be broken, i can't connect with usb to my computer so i cant put anything on the phone.
Is there anyway i can fix this problem? Or is my nexus officialy dead :crying:
If you have the Play Store app, or a browser so that you can get to the Play Store, and you still have root, you could download two free apps: Goo Manager, which has ROMs and gapps which you can download, and Recovery Tools, which allows you to flash CWM or TWRP.
Sent from my VZW Galaxy Nexus using xda app-developers app
If your usb port is dead, you may not be in a great situation. Your best bet if it works, is to go into fastboot and flash recovery again.
If you are rooted but have broken USB you have other options. You could sideload apps, transfer via wifi or just browse to them on the internet (not sure if your ROM came with a browser). An app that can install a custom recovery would be ideal, Goo Manager, ROM Manger, or something like that (maybe there are better options here, I am a little out of the loop on these apps). You could also download the proper GApps.
If you aren't rooted and you don't have functional USB, you indeed may have an issue. Fixing the USB may be your only solution.
cupfulloflol said:
If your usb port is dead, you may not be in a great situation. Your best bet if it works, is to go into fastboot and flash recovery again.
If you are rooted but have broken USB you have other options. You could sideload apps, transfer via wifi or just browse to them on the internet (not sure if your ROM came with a browser). An app that can install a custom recovery would be ideal, Goo Manager, ROM Manger, or something like that (maybe there are better options here, I am a little out of the loop on these apps). You could also download the proper GApps.
If you aren't rooted and you don't have functional USB, you indeed may have an issue. Fixing the USB may be your only solution.
Click to expand...
Click to collapse
Im not sure if im rooted actually. I think im still rooted tho. But the problem is that i cant install any apks for some reason.
Eskimox said:
Im not sure if im rooted actually. I think im still rooted tho. But the problem is that i cant install any apks for some reason.
Click to expand...
Click to collapse
What happens when you try?
Eskimox said:
Im not sure if im rooted actually. I think im still rooted tho. But the problem is that i cant install any apks for some reason.
Click to expand...
Click to collapse
you are enabling third party apps through the developers settings right?
Eskimox said:
Im not sure if im rooted actually. I think im still rooted tho. But the problem is that i cant install any apks for some reason.
Click to expand...
Click to collapse
Which ROM are you currently on? SlimKat, Dreams or A taste of KitKat?
Metalero9389 said:
you are enabling third party apps through the developers settings right?
Click to expand...
Click to collapse
Yes i am, still dosen't work to install any apps. I dont think you can install any apps if you dont have gapps.
RajatPatel said:
Which ROM are you currently on? SlimKat, Dreams or A taste of KitKat?
Click to expand...
Click to collapse
I am on Dreams.
Eskimox said:
Yes i am, still dosen't work to install any apps. I dont think you can install any apps if you dont have gapps.
I am on Dreams.
Click to expand...
Click to collapse
You can try ADB over WiFi if you can confirm you are rooted.
Download the file flash_image in your PC from here and also download CWM recovery from here and then follow these steps:
Extract the flash_image.zip to a folder name say XYZ
Then in your phone, goto developers option and enable ADB over network. Make sure your PC and Mobile are on same WiFi network. After you enable it, you will get and ip:host (e.g 192.168.x.x:5555)
Now on your PC, copy both downloaded files to XYZ folder and do a shift+right click and select "Open Command Window here" and execute following code.
Code:
adb connect 192.168.x.x:5555
adb root
adb push flash_image /data/local
adb shell chmod 777 /data/local/flash_image
adb push recovery-clockwork-touch-6.0.4.3-maguro.img /data/local/
adb shell chmod 777 /data/local/recovery-clockwork-touch-6.0.4.3-maguro.img
adb shell /data/local/flash_image recovery /data/local/recovery-clockwork-touch-6.0.4.3-maguro.img
If this goes successful, your recovery is back. Try rebooting to recovery to confirm that.
Wish you luck :good:
P.S The issue is caused due to ROM as it this particular ROM flashes stock recovery over your custom recovery :silly:
RajatPatel said:
You can try ADB over WiFi if you can confirm you are rooted.
Extract the flash_image.zip to a folder name say XYZ
Then in your phone, goto developers option and enable ADB over network. Make sure your PC and Mobile are on same WiFi network. After you enable it, you will get and ip:host (e.g 192.168.x.x:5555)
Now on your PC, copy both downloaded files to XYZ folder and do a shift+right click and select "Open Command Window here" and execute following code.
Code:
adb connect 192.168.x.x:5555
adb root
adb push flash_image /data/local
adb shell chmod 777 /data/local/flash_image
adb push recovery-clockwork-touch-6.0.4.3-maguro.img /data/local/
adb shell chmod 777 /data/local/recovery-clockwork-touch-6.0.4.3-maguro.img
adb shell /data/local/flash_image recovery /data/local/recovery-clockwork-touch-6.0.4.3-maguro.img
If this goes successful, your recovery is back. Try rebooting to recovery to confirm that.
Wish you luck :good:
P.S The issue is caused due to ROM as it this particular ROM flashes stock recovery over your custom recovery :silly:
Click to expand...
Click to collapse
wow this might work. I just have one problem, i cant find the option you are talking about. Are you sure its accessible without having to install any apps. I have been looking around on the internet and most people seems to be using some kind of app to access that option.
Eskimox said:
wow this might work. I just have one problem, i cant find the option you are talking about. Are you sure its accessible without having to install any apps. I have been looking around on the internet and most people seems to be using some kind of app to access that option.
Click to expand...
Click to collapse
Its in settings itself. If you can't see developers option in your settings, then goto setting > about phone and tap 5 times on "build number"
RajatPatel said:
Its in settings itself. If you can't see developers option in your settings, then goto setting > about phone and tap 5 times on "build number"
Click to expand...
Click to collapse
no yeah i know that, but i cant find the setting to activate to ADB over network.
Eskimox said:
no yeah i know that, but i cant find the setting to activate to ADB over network.
Click to expand...
Click to collapse
Here is a screenshot that might help you.
Sent from my Galaxy Nexus using xda app-developers app
RajatPatel said:
Its in settings itself. If you can't see developers option in your settings, then goto setting > about phone and tap 5 times on "build number"
Click to expand...
Click to collapse
RajatPatel said:
Here is a screenshot that might help you.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I guess im not rooted then coz i cant find that setting
Eskimox said:
I guess im not rooted then coz i cant find that setting
Click to expand...
Click to collapse
Can you see root access option just over these debugging options? If yes, then select apps and adb
Sent from my Galaxy Nexus using xda app-developers app
There is an APK somewhere on the web which installs any gapp you pick in android right away.
Unfortunately, it doesnt work in 4.4
Sent from my Galaxy Nexus using xda app-developers app
Actually the apk for gapps android installer is working for 4.4 . I can send it to you, if you want.
Sent from my Galaxy Nexus using xda app-developers app