File Management

[dereksurfs]

Ok,

I finally rooted my NC without much trouble. The thing I'm trying to figure out now is the best way to manage files. I intalled Astro File Manager which is pretty good for viewing. But I am running into difficulty editing. Here are a couple of questions:

1. Can I simply use my computer plugged into the the nook and windows explorer to access /system/apps files? I am able to get to some directories, but are these hidden to MS? This would seem easier although I know we are dealing with a different OS. So things could get messy.

2. How does one edit files in system/apps which are read only? Is best to change their permissions first like most Unix OSs? If so how?

Here is what I am trying to do. I want to go back to the original NC keyboard. I read the thread about this in which Scion provided the original LatinIME.apk file. So I downloaded it to my pc. Then sideloaded it to the NC in a temp directory.

Now I would like to backup the android keyboard file first renaming it to something like LatinIME.apk.Old. So I tried renaming it. But it said I don't have permission. Next I thought Ok, I'll make a copy and rename the copy. But it never seemed to copy. Once I back it up, then I'll delete the original and replace with the sideloaded one.

Is this mainly a permissions issue? If so what's the best or easiest way of going about this sort of file management?

BTW, I'm an old unix programmer. I'm just not sure if I need to go into that mode here form a console app. Maybe that would be easier - simply chmod 777 the file.

Derek

[zartemis]

Originally Posted by dereksurfs

1. Can I simply use my computer plugged into the the nook and windows explorer to access /system/apps files? I am able to get to some directories, but are these hidden to MS? This would seem easier although I know we are dealing with a different OS. So things could get messy.

2. How does one edit files in system/apps which are read only? Is best to change their permissions first like most Unix OSs? If so how?

BTW, I'm an old unix programmer. I'm just not sure if I need to go into that mode here form a console app. Maybe that would be easier - simply chmod 777 the file.

Well, if you remember your unix stuff, you can remount the system mount point read/write (that's probably what is blocking you) and yes, indeed, use chmod to change permissions if you need to using a terminal emulator app or by accessing the shell via adb (either over USB or ADBWireless).

If you don't mind paying for an app, you can also just pick up root explorer which will give you one-button access to remounting /system r/w and allow you to change simple permissions (but not setuid or setgid) via GUI (faster than typing on the Nook's keyboard, IMO).

[dereksurfs]

Ok, first of all a big thank you to Zartemis!

I finally got this working. But it was a royal pain. I'll include the steps for those who may want to do this or something similar. This might save you some time.

1. download terminal emulator app
2. download ADBWireless
3. download Android SDK on notebook
4. download Java SDK on notebook
5. set windows PATH environment variable to point to adb folder:<Android Install Directory >\android-sdk-windows\platform-tools
6. Enable ADBWireless from NC
7. connect to NC from Windows command prompt using adb connect <NC IP>
8. adb shell
9. remount the system mount point read/write (see link above)
10. cd system/app
11. chmod 777 LatinIME.apk
12. cat LatinIME.apk > LatinIME.apk.Orig (this backs up the original)
13. rm LatinIME.apk
14. cd to the directory with the sideloaded LatinIME.apk file
15. cat LatinIME.apk > /system/app/LatinIME.apk
16. Go into nook tools and reselect the keyboard

Derek

[dereksurfs]

The biggest annoyance was trying to use the ADB Shell from the NC. Android's ADB Shell is weak. It doesn't even have the cp command which is a basic unix shell command. And using the limited keyboard doesn't help. I was seriously considering installing bash shell which has many more standard features. But I'm not sure how much trouble it would be. I've seen some threads where others have discussed using bash on Android. I think they had to install and configure it. If I was going to do Android development I would switch shells for sure.

BTW, I'm sure using tools such as root explorer would help simplify this process. However having familiarity with shell commands when needed is helpful as well.

Derek

[zartemis]

Originally Posted by dereksurfs

The biggest annoyance was trying to use the ADB Shell from the NC. Android's ADB Shell is weak. It doesn't even have the cp command which is a basic unix shell command.

Install Busybox and then you'll have cp and others.

Also a clarification: you shouldn't need to use both adbwireless and terminal emulator, they both do essentially the same thing: adb gives you access to the Nook shell from your PC keyboard (via the 'adb shell' command) and teminal emulator gives you access to the Nook shell using the Nook itself (unless futzing with the keyboard files made you lose all keyboard temporarily? -- in which case you'd need just adb).

BTW, I'm sure using tools such as root explorer would help simplify this process. However having familiarity with shell commands when needed is helpful as well.

Yes to both: Root explorer is handy and shell familiarity is useful. Also, Root explorer is a paid app and the other two methods are free.

[dereksurfs]

Thanks,

I saw BusyBox mentioned as well. I'll give it a look. I just thought bringing a more robust shell like bash would make life easier. But I'm not sure if its worth it. Adding BusyBox looks pretty straight forward. I may even try both and see which I prefer.

With regards to installing and using terminal emulator, it was more of a convenience thing to have as an option. It's nice to have around to do a quick check from the device. But you are right, it is not necessary for this excercise.

Derek