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?
Hi, has anyone managed to get ADB working with Jelly Bean? I'm running CM10 and I can't seem to get ADB working. I've downloaded the drivers from the SDK but windows still says it can't find the driver, even when I manually specify where the driver is.
Try 1wayjonny's Universal Naked Drivers over in his thread in the dev section. It's the best. Be sure to remove all traces of the old drivers first.
Do you have a adb debugging enabled on the phone? CM10 has this disabled by default.
Sent from my Galaxy Nexus using Tapatalk 2
And I'll add adb works when you are on booted and when you are on recovery.
Adb does not work on bootloader, fastboot works on bootloader.
atifsh said:
And I'll add adb works when you are on booted and when you are on recovery.
Adb does not work on bootloader, fastboot works on bootloader.
Click to expand...
Click to collapse
I'm aware of that
strumcat said:
Try 1wayjonny's Universal Naked Drivers over in his thread in the dev section. It's the best. Be sure to remove all traces of the old drivers first.
Click to expand...
Click to collapse
Alright, will do. Not at home now. I've never had any ADB drivers installed as this is a clean windows 7 install.
geoffcorey said:
Do you have a adb debugging enabled on the phone? CM10 has this disabled by default.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Yep, pretty sure I do.
adbWireless
atifsh said:
And I'll add adb works when you are on booted and when you are on recovery.
Adb does not work on bootloader, fastboot works on bootloader.
Click to expand...
Click to collapse
Can you get a log through fastboot? I need to get a log of boot loop
RichyRicho said:
Can you get a log through fastboot? I need to get a log of boot loop
Click to expand...
Click to collapse
If it's already booting then it's no longer in fastboot
Sent from my Galaxy Nexus
Even today, a friend of mine installed the naked drivers, started adb, device found
I watched him as he did it, guiding him through the commands to push, reboot recovery, the works, and Windows 7 pulled it quite well.
I don't use windows at home, but he did it without troubles at all.
So yeah. ADB has been around for ages, and it will be coming back.
And it's the second proof I see: most of these so called issues with drivers, should be handled on <insert host OS here> forums and not on xda. Most of times, users just don't get it.
Sent from my i9250
Pirateghost said:
If it's already booting then it's no longer in fastboot
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
True
Well after some research last night, and some wasted hours, i now know that ADB does not work in boot Not at all.
So how would I get a log from boot? How does everyone else do it?
RichyRicho said:
True
Well after some research last night, and some wasted hours, i now know that ADB does not work in boot Not at all.
So how would I get a log from boot? How does everyone else do it?
Click to expand...
Click to collapse
do you have android debugging turned on? and which drivers are you using? try using the universal naked drivers that re posted in the dev section
k786 said:
do you have android debugging turned on? and which drivers are you using? try using the universal naked drivers that re posted in the dev section
Click to expand...
Click to collapse
Sorry I have an Xperia S...didnt realise which forum i was in...i dont think the S has naked drivers and the 64 bit ones here dont even work
I've done a lot of searching and tried the different suggestions people have mentioned on various sites but I STILL have trouble with "error: device not found" when I try to adb reboot bootloader from my computer. I was actually able to make a connection last night and then I'm not able to again today. I've installed/uninstalled and installed again both the drivers and HTC sync NUMEROUS times. It does show that my phone is being recognized on my computer, just don't know why it won't let me adb. Btw, relative noob here.
Thanks in advance for any help some kind soul might give to me.
scott62185 said:
I've done a lot of searching and tried the different suggestions people have mentioned on various sites but I STILL have trouble with "error: device not found" when I try to adb reboot bootloader from my computer. I was actually able to make a connection last night and then I'm not able to again today. I've installed/uninstalled and installed again both the drivers and HTC sync NUMEROUS times. It does show that my phone is being recognized on my computer, just don't know why it won't let me adb. Btw, relative noob here.
Thanks in advance for any help some kind soul might give to me.
Click to expand...
Click to collapse
Do you have usb debugging on?
Try to restart adb:
adb kill-server
adb start-server
Sent from my HTC One X using xda app-developers app
hahhahhaaa said:
Do you have usb debugging on?
Try to restart adb:
adb kill-server
adb start-server
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Tried that.
You have the latest android SDK with packages installed ?
Or maybe some admin rights problems ?
Is there also a problem when you put the phone in fastboot mode and try various fastboot commands......or is it just adb commands ?
Not using any other extension cables ...only the one that came with the phone ?
Just thinking out loud here
MarcelHofs said:
You have the latest android SDK with packages installed ?
Or maybe some admin rights problems ?
Just thinking out loud here
Click to expand...
Click to collapse
Actually, not sure if I have the "lastest" android SDK...I installed it quite a while ago. Does that get updated?
Well i updated them some time ago....but never had any issues with that....so i'm guessing in the dark for a bit
MarcelHofs said:
Well i updated them some time ago....but never had any issues with that....so i'm guessing in the dark for a bit
Click to expand...
Click to collapse
I'll try googling it to see if I can find out if I can update mine. Thanks, Marcel! Always helpful.
Where does it show that the device is recognized? Windows device manager?
Sent from my HTC One X using xda app-developers app
Did u try the fastboot thing .... When adb is not responding, go put the phone in fastboot USB without making changes and do
Fastboot devices
Just to check if fastboot is working ?
hahhahhaaa said:
Where does it show that the device is recognized? Windows device manager?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Not sure where to check it in device manager. It shows up on my toolbar ("device drivers installed" or something like that).
Try:
android update adb
Sent from my HTC One X using xda app-developers app
scott62185 said:
Not sure where to check it in device manager. It shows up on my toolbar ("device drivers installed" or something like that).
Click to expand...
Click to collapse
Don't know exactly ( i'm dutch )
Configuration settings - device manager (or something similar) - device control ?
MarcelHofs said:
Did u try the fastboot thing .... When adb is not responding, go put the phone in fastboot USB without making changes and do
Fastboot devices
Just to check if fastboot is working ?
Click to expand...
Click to collapse
Do I type in exactly "fastboot devices?" When I do that nothing happens
It says waiting for device ?
In dosprompt
C:\fastboot\fastboot devices
MarcelHofs said:
It says waiting for device ?
Click to expand...
Click to collapse
No, it doesn't do anything (just goes back to C:\Fastboot>)
hahhahhaaa said:
Try:
android update adb
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
type that in my adb?
Files are still in that dir ?
C:\fastboot\ 3 fastboot / adb files ?
MarcelHofs said:
Files are still in that dir ?
C:\fastboot\ 3 fastboot / adb files ?
Click to expand...
Click to collapse
Yeah, you actually gave me the files to put in there when you were helping me a few days ago. lol That's what's weird, it was working, then it wasn't, then it worked once, and now not again...
Yeah .... this is weird ! .... I'm thinking
scott62185 said:
type that in my adb?
Click to expand...
Click to collapse
Yes
Sent from my HTC One X using xda app-developers app
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
http://forum.xda-developers.com/lg-g3/development/root-twrp-root-twrp-tmo-lg-g3-t2821005
Have fun
Woot. Did u try it?
Sent from my LG-D851 using XDA Premium 4 mobile app
Just waiting on pc version
Same waiting on pc version as well
LGG3 and beyond
ive tried 10x with linux version and cant get mine to work so i maybe waiting on pc version as well
Got mine rooted and twrp installed
BACARDILIMON said:
Just waiting on pc version
Click to expand...
Click to collapse
Nice to see you over from Note 3. You switch or the LG G3 just an add-on?
vibrantliker said:
Nice to see you over from Note 3. You switch or the LG G3 just an add-on?
Click to expand...
Click to collapse
Yeah man I feel like the new kid at school.lol. but so much better phone. I did not care for the note 3. So many hardware issues. But loving this beast. Good to see you here. Can't wait to start flashing lol.
Failed the first time, but I tried it again and all worked perfectly. Ran it on Mac OS X 10.9.
Had to change the phone to PTP mode since it defaults to MTP for adb to see it.
Thank you!!!
BACARDILIMON said:
Just waiting on pc version
Click to expand...
Click to collapse
Me too
Wow! How exciting. The only reason I want root is to remove the on screen buttons and install LMT PIE launcher.
Nexus ONE
Hopefully with root I can enable mass storage mode and solve my issues running with my Pioneer AVX1500
Have you windows people tried cygwin to get root?
ThePagel said:
Have you windows people tried cygwin to get root?
Click to expand...
Click to collapse
I'd very much like to know the answer to this as well...
From Windows
Just run the adb commands from the root method in the root thread
adb reboot --bnr_recovery
adb push ./assets/start_restore /temp/start_restore
adb push ./assets/permaroot.bin /temp/start_restore
adb reboot
It's really simple, then install the twrp recovery.img with flashify
you're rooted with recovery
koraun said:
From Windows
Just run the adb commands from the root method in the root thread
adb reboot --bnr_recovery
adb push ./assets/start_restore /temp/start_restore
adb push ./assets/permaroot.bin /temp/start_restore
adb reboot
It's really simple, then install the twrp recovery.img with flashify
you're rooted with recovery
Click to expand...
Click to collapse
Can you explain this adb method it always confusing me Im used to using odin this my first lg device
raw2000j said:
Can you explain this adb method it always confusing me Im used to using odin this my first lg device
Click to expand...
Click to collapse
Same here. I searched for a guide for first timers on LG. It is very different
So I'm rooted and have TWRP now. I know I'm rooted cause exposed framework installed and quickboot app works fine but there's no notification for root request. Is a seperate app needed?
Punchatron said:
So I'm rooted and have TWRP now. I know I'm rooted cause exposed framework installed and quickboot app works fine but there's no notification for root request. Is a seperate app needed?
Click to expand...
Click to collapse
Superuser from playstore
koraun said:
From Windows
Just run the adb commands from the root method in the root thread
adb reboot --bnr_recovery
adb push ./assets/start_restore /temp/start_restore
adb push ./assets/permaroot.bin /temp/start_restore
adb reboot
It's really simple, then install the twrp recovery.img with flashify
you're rooted with recovery
Click to expand...
Click to collapse
This method worked perfectly for me!! Time to remove bloat ?
Sent from my LG-D851 using Tapatalk