Related
can anyone tell me what the ADB shell command is for going up one directory. I can use "cd" to enter a directory, but always have to exit because cd.. doesn't work like in windows. Also tried cd home, to no effect.
Thanks,
Will
Code:
cd ..
Notice the space. Windows forgives leaving it out, Linux doesn't.
oh...you are the bomb. I was getting so tired of having to exit just to go up one directory.
Thank you.
Will
No problem. Another quick tip, cd / takes you all the way to the root of your file system. Just in case you get lost somewhere
pwd shows you where you are as well.
so im stuck and can not figure this out. for some reason the permissions for the download folders on my sd card do not have any user permissions checked. i can not download anything at all but the market is fine as it is on the internal memory i suppose. the only reason i came across the user permissions issue was because i found another post where someone had the same problem with downloading and corrected the issue by using root explorer and manually adding user permissions to any folder he used for downloading. now... here is my problem... i used root explorer and when i try to add user permissions to these folders, the settings that changed do not stick. i check mark the 3 boxes and accept the changes but if i go back into that folders specific permissions, they are unchecked once again. how can i get it to not revert back or better yet how can i just resolve the issue in whole so i dont have to keep fixing folder permissions on the sd card for app that downloads? i dont see why the sd card of all places would start having these permission issues. the guys post i came across tried to tie this issue to the fix permissions option in rom manager saying it may have caused the problem but i didnt use rom manager to fix permissions until this problem started. i was on liberty 1.5 rom then reverted back to rooted stock where i still have the problem with all downloading except the market again. any help would be greatly appreciated!
58 views and not a single response? wow.... so very shocking to see that, i bet if i had post this in the dev forum i would have gotten 15+ responses just to say that im in the wrong section then anther 30 for people to argue back and fourth on how everyone is being rude or that this is the reason devs stay in irc...
Give this a try if you have the sdk and adb set up.
from a command prompt:
1) adb devices (make sure that your phone shows up)
2) adb shell
3) su (assuming you have rooted your phone)
4) cd /mnt/sdcard/download (or whatever the folder on your sdcard for downloads is called)
5) chmod 777 /mnt/sdcard/download (or whatever your download folder is called)
this should change the permissions on your sdcard to have full permissions.
thanks for your reply! im grateful, but wouldnt that only change the permissions for the "download" folder? which is mostly only a default location for apps such as the browser?
The way sysadmin-x is suggesting makes the permissions way different than they are by default, I wouldn't recommend doing it that way.
If you want to change permissions on the entire sd card to what they are by default, try running(as root)
Code:
chown -R system:sdcard_rw /mnt/sdcard && chmod -R 075 /mnt/sdcard
Edit: that code messes up the permissions on one folder, after running that you should also run
Code:
chown -R root:root /mnt/sdcard/.android_secure && chmod -R 000 /mnt/sdcard/.android_secure
Just do this: download a terminal emulator from the market. Open the app. Type su and press enter. Give it root access. Type chmod 777 /sdcard and press enter.
Please note you need root to do this
this light sensor is really pissing me off , is there any way to shut it off , i'v found a way that is telling me to chmod 777 the patch file after installing it manually but idon't know what chmod 777 is and how to do this please help me
Is stock eclair there isn't a GUI option to disable it.
About chmod 777, I haven't done it yet... but I guess you have to adb shell something.
To know how to use those commands, just have a click on the search button...
maveloth said:
Is stock eclair there isn't a GUI option to disable it.
About chmod 777, I haven't done it yet... but I guess you have to adb shell something.
To know how to use those commands, just have a click on the search button...
Click to expand...
Click to collapse
i searched and found nothing please help it's pissing me off for real !! se u suck i bought this phone because of it's design but their software update service sux !
I have found what you were looking for [just search in devs forum].
Here it is an explaining link:
http://forum.xda-developers.com/showthread.php?t=888232
maveloth said:
I have found what you were looking for [just search in devs forum].
Here it is an explaining link:
http://forum.xda-developers.com/showthread.php?t=888232
Click to expand...
Click to collapse
thanks i found this thread before but i can't apply this method because i don't know how to chmod777 the file so i can't get this to work ? can you try it and then tell me how to exactly do it please , thanks again m8
First thing, you have to learn how to adb shell.
But you have to make everything ok before using it.
So, let's see how it has to be done..
Download the .zip file posted on the other thread [linked above].
Using root explorer, just copy and paste the content of the .zip file under the /etc/ path of the phone.
After you have done this, let's adb shell.
1. Download this file: http://db.tt/cq44S4v
2. Extract the adb.zip file to C:\adb [there will be a folder named "adb" within the C:\ path, with 3 files within it].
3. On your phone, click Settings > Applications > Development, and make sure USB Debugging is on.
4. Plug your phone into your computer via USB cable [it needs to be on]. It should say installing drivers if your phone is plugged for the first time and you are using Windows.
4.1 You'd better install the drivers which comes with X8 software [PC Companion], or just google for them.
5. After it installs the drivers, go to the Start menu and type "cmd" into the search bar to open the command prompt.
6. Type the following into the command prompt window [hitting enter at the end of every line]:
Code:
cd\
cd adb
adb devices
You should see a serial number pop up, it’s the serial number of your phone. This means you are all set.
After all this procedure, you can finally "chmod" your files.
Always from the CMD, type this:
Code:
adb shell
You should see a "#" on the left. That's good.
Now enter the path with the file to chmod:
Code:
cd /etc
Then finally chmod it:
Code:
su chmod 777 hw_config.sh
You're done.
Hope this helps.
maveloth said:
First thing, you have to learn how to adb shell.
But you have to make everything ok before using it.
So, let's see how it has to be done..
Download the .zip file posted on the other thread [linked above].
Using root explorer, just copy and paste the content of the .zip file under the /etc/ path of the phone.
After you have done this, let's adb shell.
1. Download this file: http://db.tt/cq44S4v
2. Extract the adb.zip file to C:\adb [there will be a folder named "adb" within the C:\ path, with 3 files within it].
3. On your phone, click Settings > Applications > Development, and make sure USB Debugging is on.
4. Plug your phone into your computer via USB cable [it needs to be on]. It should say installing drivers if your phone is plugged for the first time and you are using Windows.
4.1 You'd better install the drivers which comes with X8 software [PC Companion], or just google for them.
5. After it installs the drivers, go to the Start menu and type "cmd" into the search bar to open the command prompt.
6. Type the following into the command prompt window [hitting enter at the end of every line]:
Code:
cd\
cd adb
adb devices
You should see a serial number pop up, it’s the serial number of your phone. This means you are all set.
After all this procedure, you can finally "chmod" your files.
Always from the CMD, type this:
Code:
adb shell
You should see a "#" on the left. That's good.
Now enter the path with the file to chmod:
Code:
cd /etc
Then finally chmod it:
Code:
su chmod 777 hw_config.sh
You're done.
Hope this helps.
Click to expand...
Click to collapse
lol it's freaking hard , thanks for your help m8 i appreciate it is there any easier way?
Have you tried installing Spare Parts from the market. I know it has light sensor tweak option plus has tons of other useful tweaks and monitors.
Sent from my I7500 using Tapatalk
Master Darko said:
Have you tried installing Spare Parts from the market. I know it has light sensor tweak option plus has tons of other useful tweaks and monitors.
Sent from my I7500 using Tapatalk
Click to expand...
Click to collapse
tried it still no use , the sensor is still working !!
To start off I want to say, I am NOT claiming to have created this exploit, I am merely letting people know that it works on the arc.
All credit for this goes to Chainfire and The Android Exploid Crew
The origional thread is here: http://forum.xda-developers.com/showthread.php?t=1044765
Download here
Install the APK and run it.
For people getting "could not extract assets" error execute
adb shell rmdir /data/local/tmp
and then
adb shell mkdir /data/local/tmp
Click to expand...
Click to collapse
Quote posted by jassired
works for me
So just push the apk to the phone, install and you're done?
no need to "push", just stick it on your sd card and install
diggedy said:
no need to "push", just stick it on your sd card and install
Click to expand...
Click to collapse
I get the error thing...and I can't find the effing map where I need to remove stuff....
where do I find the god damned map to remove the files I need to remove when it only fails to install?????
I've checked every single map on the memory card, going nuts here...
Cim_XII said:
where do I find the god damned map to remove the files I need to remove when it only fails to install?????
I've checked every single map on the memory card, going nuts here...
Click to expand...
Click to collapse
What do you mean?
double post :s will use this later
I have put the .apk in my download map on the sd card of the phone, installed the apk and run it and I get the: "could not extract assets" error execute
and then when I get that I am supposed to remove some files from a map on the sd card, and I cannot find said map....I hava rebooted the phone, and I still cannot find data/local/tmp or what ever map I need to find.....
Cim_XII said:
I have put the .apk in my download map on the sd card of the phone, installed the apk and run it and I get the: "could not extract assets" error execute
and then when I get that I am supposed to remove some files from a map on the sd card, and I cannot find said map....I hava rebooted the phone, and I still cannot find data/local/tmp or what ever map I need to find.....
Click to expand...
Click to collapse
you need to execute the commands in the origional post via ADB with USB debugging enabled, because the location is in the system and ironicly you dont have the root privelages to delete them
I don't even know what ADB is....that's how much I know...
Cim_XII said:
I don't even know what ADB is....that's how much I know...
Click to expand...
Click to collapse
I have attached it to this post. ADB is the Android Debug Bridge. It is used to excecute commands on android devices. Just extract the zip, then open a command prompt and change to the directory of ADB, then excecute the commands.
if you get the error for esset you need to remove all the files inside to /data/local/tmp/
press: adb shell
press ls /data/local/tmp
and remove one by one the files as my example:
$ ls /data/local/tmp/
ls /data/local/tmp/
Superuser.apk
Gingerbreak
runscript
sysrun
$ rm /data/local/tmp/Superuser.apk
rm /data/local/tmp/Superuser.apk
$ rm /data/local/tmp/Gingerbreak
rm /data/local/tmp/Gingerbreak
$ rm /data/local/tmp/runscript
rm /data/local/tmp/runscript
$ rm /data/local/tmp/sysrun
rm /data/local/tmp/sysrun
and now try again with app and may it works (in my case, works)
dh2311 said:
I have attached it to this post. ADB is the Android Debug Bridge. It is used to excecute commands on android devices. Just extract the zip, then open a command prompt and change to the directory of ADB, then excecute the commands.
Click to expand...
Click to collapse
maybe I should've mentioned I'm on a Mac computer with no access to windows....damn, this is so frustrating....
Ah... Its still possible you just have to get the android sdk for mac.
Get the SDK from here
Then in the tools folder ADB should be there
Then its commands as normal I think... not sure tho, don't have a mac.
Search around on here for tutorials, I'm sure someone has put up a tutorial on setting up adb on mac
dh2311 said:
Ah... Its still possible you just have to get the android sdk for mac.
Get the SDK from here
Then in the tools folder ADB should be there
Then its commands as normal I think... not sure tho, don't have a mac.
Search around on here for tutorials, I'm sure someone has put up a tutorial on setting up adb on mac
Click to expand...
Click to collapse
kewl, and the exact commands is in post #1 right?
so this root's the OS, title is confusing, does it enable fastboot? allow you to flash custom roms?
should be....
dh2311 said:
you need to execute the commands in the origional post via ADB with USB debugging enabled, because the location is in the system and ironicly you dont have the root privelages to delete them
Click to expand...
Click to collapse
did exactly what you said, but get the message
adb: permission denied
No does not enable fastboot
I can't seem to get any other keyboards to work. I have a stock NC 1.2 that was rooted first with MiniRooter (I think it is called) that OC'd it with the 1.2 GHz Kernel and then I MN with the most recent one as it had more options I wanted. But I can't seem to get a keyboard to work.
I have the gingerbread keyboard and thumb keyboard apk's and put them both in system/app with Root Explorer, reboot and nothing, I have tried to manually install them by clicking and using the package installer, nothing. Don't know what is up. none of them show up in the nook color tools under keyboard, but they show up in the manage programs...
anyone? It doesn't seem to make sense and I don't know enough about Android to troubleshoot.
all i have to do to try new keyboards is:
1) download new kb from the market.
2) install the new kb.
3) go into settings and make sure the keyboard is checked.
4) go to a text field and long press.
5) keyboard options will appear.
6) check the kb you want to use.
thats it. thats all i have to do for a new keyboard.
not sure about pushing the kb apk into syetem/app maybe its best to just install them.
boxcar8028 said:
all i have to do to try new keyboards is:
1) download new kb from the market.
2) install the new kb.
3) go into settings and make sure the keyboard is checked.
4) go to a text field and long press.
5) keyboard options will appear.
6) check the kb you want to use.
thats it. thats all i have to do for a new keyboard.
not sure about pushing the kb apk into syetem/app maybe its best to just install them.
Click to expand...
Click to collapse
my problem is that when I go into settings it isn't there to be checked..
I'm pretty sure that you'll HAVE to use ADB. Here's what I just did with the SlideIT keyboard on rooted 1.2. I put the apk on C: of my PC. Then in adb typed:
Code:
cd \
adb push <application_name>.apk /system/app
adb reboot
After the Nook reboots go into NookColor Tools, tap Keyboards and you should see it there.
If we're talking about SlideIT downloaded from the Market, then in ADB you may need to do:
Code:
adb shell remount rw
adb pull /data/app/<application_name>.apk
adb rm /data/app/<application_name>.apk
adb push <application_name>.apk /system/app
adb chmod 644 /system/app/<application_name>.apk
adb shell remount ro
Then reboot >nookcolor tools>keyboards>slideit.
KWKSLVR said:
I'm pretty sure that you'll HAVE to use ADB. Here's what I just did with the SlideIT keyboard on rooted 1.2. I put the apk on C: of my PC. Then in adb typed:
Code:
cd \
adb push <application_name>.apk /system/app
adb reboot
After the Nook reboots go into NookColor Tools, tap Keyboards and you should see it there.
If we're talking about SlideIT downloaded from the Market, then in ADB you may need to do:
Code:
adb shell remount rw
adb pull /data/app/<application_name>.apk
adb rm /data/app/<application_name>.apk
adb push <application_name>.apk /system/app
adb chmod 644 /system/app/<application_name>.apk
adb shell remount ro
Then reboot >nookcolor tools>keyboards>slideit.
Click to expand...
Click to collapse
when I get a chance I will give it a go. Thanks
KWKSLVR said:
I'm pretty sure that you'll HAVE to use ADB. Here's what I just did with the SlideIT keyboard on rooted 1.2. I put the apk on C: of my PC. Then in adb typed:
Code:
cd \
adb push <application_name>.apk /system/app
adb reboot
After the Nook reboots go into NookColor Tools, tap Keyboards and you should see it there.
If we're talking about SlideIT downloaded from the Market, then in ADB you may need to do:
Code:
adb shell remount rw
adb pull /data/app/<application_name>.apk
adb rm /data/app/<application_name>.apk
adb push <application_name>.apk /system/app
adb chmod 644 /system/app/<application_name>.apk
adb shell remount ro
Then reboot >nookcolor tools>keyboards>slideit.
Click to expand...
Click to collapse
I can't get the first part to work, it says not found. Where do I put the apk? I have it on c: on my comp.
Omega Ra said:
I can't get the first part to work, it says not found. Where do I put the apk? I have it on c: on my comp.
Click to expand...
Click to collapse
Which part specifically doesn't work?
Are you getting that after typing:
Code:
adb push <application_name>.apk /system/app
If so, try typing
Code:
adb kill-server
and try again
The apk is in the right place if it's in root on C: (and it is). Typing cd \ is pointing adb to look into C: for the apk you're trying to install. It's probably not the cleanest way to do it, but I've just always done it that way so people might wanna paint me silly.
KWKSLVR said:
Which part specifically doesn't work?
Are you getting that after typing:
Code:
adb push <application_name>.apk /system/app
If so, try typing
Code:
adb kill-server
and try again
The apk is in the right place if it's in root on C: (and it is). Typing cd \ is pointing adb to look into C: for the apk you're trying to install. It's probably not the cleanest way to do it, but I've just always done it that way so people might wanna paint me silly.
Click to expand...
Click to collapse
okay, let me try the kill server thing
Omega Ra said:
okay, let me try the kill server thing
Click to expand...
Click to collapse
no go, still says not found. I even renamed the apk to make sure I knew how many spaces and such...nothing...
hang on, I was in adb shell, went to normal root, I have to mount it as r/w first...
how do I do that lol
EDIT: Nevermind, I used rootexplorer to get it r/w and now the keyboard is there thanks a lot!
Are you in recovery or is your nook booted up?
Reboot your Nook and try
Code:
adb kill-server
again. Then
Code:
adb start-server
And attempt to install again. If that doesn't work, if your nook is still booted up (not in recovery), try:
Code:
adb remount
and try to install. If that doesn't work, try:
Code:
mount -o rw,remount
If you're trying to do this with your Nook booted into recovery, try:
Code:
mount -o rw,remount /dev/block/mtd3 /system
to get read/write and go from there.
Omega Ra said:
EDIT: Nevermind, I used rootexplorer to get it r/w and now the keyboard is there thanks a lot!
Click to expand...
Click to collapse
I almost suggested that, but it seemed so janky. But what works, works!
Glad you got it running!
KWKSLVR said:
I almost suggested that, but it seemed so janky. But what works, works!
Glad you got it running!
Click to expand...
Click to collapse
yeah, but sadly I had a beta of thumbkeyboard that was expired lolol, then put in perfect keyboard and that didn't show at all...ugh..lol