There's a simple fix to make the Nook app work and sync correctly under honeycomb (it should work on froyo as well, but I have not tested it).
[Note that although I did this to fix the Nook app, it should also help other apps needing to access the sdcard. If your sdcard is not detected at all it may fix that as well.]
First you need to add the following two lines:
Code:
export EXTERNAL_STORAGE /sdcard
export INTERNAL_STORAGE /media
after the line
Code:
export ANDROID_DATA /data
at the start of your init.rc file using NotePad+ or whatever unix-format editor you like. Use "adb pull init.rc" on your computer to grab the init.rc off your nook.
To put back the modified init.rc, while connected to your nook,
Code:
adb shell mount -o remount,rw rootfs /
adb push init.rc init.rc
What you've just done is re-enabled your sdcard so that the nook app can read your files on it in /sdcard/Nook/MyDocuments. For books, put your epubs in the "Books" subdirectory (/sdcard/Nook/MyDocuments/Books)
The next step is to make sure the Nook app has proper permissions to access /sdcard. This may or may not be necessary. Do it only if you still have trouble syncing (note that you'll never be able to sync if you aren't connected to the net so check that before chmodding).
adb shell, then type su, and chmod 6755 /data/app/bn.ereader-1.apk
My nook app was listed as bn.ereader-1, but yours may just be bn.ereader.apk or even bn.ereader-2.apk (depends on how many times you had to try and download it).
Reboot your device and sync'ing should now work.
One issue I have after chmoding this is that if I try to use the softkey back while reading an epub, the app will crash. Use the option button then home option instead within the nook app. If yours works without chmodding, (just doing init.rc) then you may be able to avoid this issue. I needed to chmod in order to get it to sync beyond after the first time I enabled the export commands in init.rc
is this nook app from the market or stock reader app with store and all that good stuff?
bigted41 said:
is this nook app from the market or stock reader app with store and all that good stuff?
Click to expand...
Click to collapse
It is the market app. As such, it only reads off /sdcard rather than /media.
It does have a store section, although I agree it's not as pretty as the stock reader app.
AFAIK the stock apps are integrated into one big framework/gui and none of that is compatible with HC. I did try getting the stock software to run and the closest I got was the blank silver-text Android screen from screwing up internal files and having to adb fix things.
Thanks OP! This rocks!
I appreciate the effort. I've been using Aldiko Premium and Moon Reade Pro because I could figure this out. Great job m8!
FWIW I did the edits with Root Explorer and the built in text editor.
2 questions on this:
1) I downloaded the nook app from the market and it looks like it works. Why would I do this... (see question 2)
2) Will this allow me to transfer books from Calibre onto the nook. Right now when I transfer them the Nook app doesn't detect them.
Fishfoot said:
2 questions on this:
1) I downloaded the nook app from the market and it looks like it works. Why would I do this... (see question 2)
2) Will this allow me to transfer books from Calibre onto the nook. Right now when I transfer them the Nook app doesn't detect them.
Click to expand...
Click to collapse
You need to copy those Calibre (epub format) books to the SDCard under Nook\MyDocuments
They show up in the Nook app under the bottom right button called "MyFiles"
(I had problems too and through trial and error that's how it works)
Sorry I didn't spell out the full path where to actually put the books. Updated the OP to be clearer
Good work. This is much appreciated. I just wish we could get the stock Nook Apps working. It's the only thing keeping me on autonootered eclair.
Sent from my Barnes & Noble NookColor via XDA App
Alright, you said this *should* apply to Froyo/Gingerbread renditions right?
I've tried this on Gingerbread, and everytime I push the edited init.rc to my Nook or edit it in Root Explorer and then reboot, it loses all changes. How do I get the changes to stick?
Oddly enough, Nook app seems to still work in Gingerbread because init.rc symlinks /mnt/sdcard to /sdcard.
Thought occurs to me. What would it take to symlink /mnt/sdcard to /external_sd instead and then mount /dev/block/mmcblk0p8 to /media and symlink that to /sdcard (and get the changes to stick of course)?
Upon reboot, the 'init.rc' goes back to the default settings. Do I need to set permissions on the 'init.rc' file as well as the .apk?
Thank you thank you thank you!
My NC wouldn't download a book today on CM7, v14. I found this and saw that INTERNAL_STORAGE variable was not set and set it in init.rc. BAM! it worked.
If anyone has any advice on making this work in Froyo, it would be appreciated.
In the Customized Nookie Froyo 0.6.8 on emmc, we have two init files: init.rc and init.froyo.rc. They have slightly different labels and mounts in each.
Should we be editing both of these? If so, how do we prevent them from automatically reverting to default upon reboot (which they do)?
diaknia said:
Alright, you said this *should* apply to Froyo/Gingerbread renditions right?
I've tried this on Gingerbread, and everytime I push the edited init.rc to my Nook or edit it in Root Explorer and then reboot, it loses all changes. How do I get the changes to stick?
Oddly enough, Nook app seems to still work in Gingerbread because init.rc symlinks /mnt/sdcard to /sdcard.
Thought occurs to me. What would it take to symlink /mnt/sdcard to /external_sd instead and then mount /dev/block/mmcblk0p8 to /media and symlink that to /sdcard (and get the changes to stick of course)?
Click to expand...
Click to collapse
If you are having trouble with it remembering the settings on reboot, you might need to change the init.rc in ramdisk.cpio (it might be reading the init.rc from the ramdisk rather than the init.rc file in rootfs).
You have to pull the cpio, extract it, change the init.rc in it, remake the cpio file, and push it back to the device. Unfortunately, I can't be of much more help at present as I no longer have a NC. I chickened out and got an iPad and sold the NC. Sorry guys.
I intended to host one after making one myself (for a different tweak I was going to attempt), but didn't end up having time before I sold the nook.
Related
For those of you who got the Market working, there is a Market update that is getting released. I installed it on my HTC HD2, but the same file would not work on the Nook. I did some searching and found one that works on the Galaxy Tab w/stock Eclair. It works on the NC!!
Requirement: You MUST have a working market. Follow this thread or this thread for more excellent info (and work) on enabling the Market.
Simply replace the Vending.apk in /system/app/ with this file (rename it Vending.apk first), reboot, and you are good to go! I would recommend backing up the original Vending.apk so that you can replace it if anything should go wrong for you.
You can use Root Explorer with /system/app in r/w mode, but it is simple to do via adb as well:
adb shell mount -o remount,rw /dev/block/mmcblk0p5 /system
adb shell mv /system/app/Vending.apk /system/app/oldVending.apk
adb push Vending.apk /system/app
adb reboot
**If you have problems, simply delete the Vending.apk, and replace it with the oldVending.apk
There is a newer version of the Market posted by devis and Xhorder in this post. Please use it instead. It fixes the weird star artifacts of this version. Instructions are exactly the same.
DO NOT simply click it to install. If it happened to work for you that way, you were lucky. You really should replace the Vending.apk with this file. Also, I saw one user report that the search function didn't allow Market searches. I believe they are the only one with that issue, and I'm not sure how they installed this. I assume they did not follow instructions, as my guide backs up the original file, and the person with the issue is asking for the orig apk. So, YMMV, but follow this instructions, and you should be fine.
Sweet! Worked for me. Danke, Herr Bimboy.
Very nice!
I actually found that the new market apk you provided installs fine as an update (no replacement of /system/app/Vending.apk needed). I opted for that as the safer option.
Thanks again!
Works very well! Very nice interface.
One issue: The "OK" and "Update" buttons are sometimes just slivers at the top of the screen. Doesn't prevent it from working though. You just have to be careful with your clicking.
Adding: This version doesn't have the problem of not listing all of the apps when you're in portrait mode. It simply works. And when you tell it to install/update an app, it does it RIGHT FRIGGIN' NOW and I mean Fassssst!
Thanks! Works great.
One question - Is there any way to get the fingerprint from the tab w/eclair? This would potentially give us access to some tablet-specific apps, like WSJ...
The new auto nooter installs he mew market ffor you...
Pinesal said:
The new auto nooter installs he mew market ffor you...
Click to expand...
Click to collapse
Awesome! I was hoping the script would get updated to include this.
FYI: Those considering updating to this version, it puts buttons up top where you can barely press them for confirmations.
-CC
EDIT: as mentioned by johnopsec above post
Anybody tried searching? Mine's kicking me back into the NC's search engine as opposed to the market one...
barrosd12 said:
Anybody tried searching? Mine's kicking me back into the NC's search engine as opposed to the market one...
Click to expand...
Click to collapse
I just did a search for Zeam in the Market and it came up fine for me. So does pinball.
barrosd12 said:
Anybody tried searching? Mine's kicking me back into the NC's search engine as opposed to the market one...
Click to expand...
Click to collapse
The old market did that too. I don't think we'll see a fix for that before a Froyo port. The upper search link doesn't always work either. The Market is expecting the upper status bar to be on the top of the screen, and we do not have that.
I wondered if that was just on mine lol , frustrating
So frustrated! I finally get my market working today and then I try this upgrade and it won't work. So I try to go back to the old one and it has stopped working too. I don't get what I did wrong. Of everything I did to get my nook rooted and working, this was the simplest part.
New version won't work in mine either. After accepting the agreement, it just closes.
Market 2.26 is supposed to be for Froyo+ only. How did you guys get it to Work?
Switched back to old Market.. everything is ok again
Tried this, got to click "accept" and then it vanished. Back to old market for me too.
I updated it with Astro and it worked fine. It's better to install apk's with Astro than others methods.
Guys, as I mentioned, do not just adb install, or click do a normal install. Save out your /system/app/Vending.apk and use this file to replace it, after renaming it Vending.apk. Then reboot.
I also tried simply installing it, and the Market app would only briefly flash or I could get to the catalog but not get to the details page of any app without force closing. That's why you should back up the Vending.apk file.
So, REPLACE the /system/app/Vending.apk, reboot and you'll be fine.
First, rename the file to Vending.apk
Use adb:
adb shell mount -o remount,rw /dev/block/mmcblk0p5 /system
adb shell cp /system/app/Vending.apk /system/app/oldVending.apk
adb push Vending.apk /system/app/
adb reboot
king conan said:
I updated it with Astro and it worked fine. It's better to install apk's with Astro than others methods.
Click to expand...
Click to collapse
I did this too, I just saved it to my mircoSD card and open Astro, clicked on the .apk and ran upgrade and everything works great now. My market is working 100%
I guess Astro knows what is doing because before update it warns about you' re updating a system app.
Pinesal said:
The new auto nooter installs the new market for you...
Click to expand...
Click to collapse
Is this confirmwed that auto nooter (Windows version) does include the newer Market app?
Here is an apk for Google Talk that I have hacked to work on the NC. Rename /system/app/Talk.apk to something else and stash this one in there.
http://www.muffinworld.net/android/nookcolor/Talk.apk
You WILL need a different keyboard other than the stock one! This one is great:
http://forum.xda-developers.com/showpost.php?p=9826968&postcount=11
Known Issues:
App exits immediately if you tap on a contact's avatar. This is because the contact management dependencies are not available on the NC.
Thank you very much. It works well.
I'm curious... what did you modify to get the Talk.apk to work?
Could you post a link on how to replace the keyboard? I think you rename the new one latinime.apk and place it somewhere...
Sent from my LogicPD Zoom2 using Tapatalk
No, you need to go to /system/app/ and rename LatinIME.apk to something else and then install the multitouch keyboard APK I linked to and reboot. That's it.
Mistar Muffin said:
Here is an apk for Google Talk that I have hacked to work on the NC. Rename /system/app/Talk.apk to something else and stash this one in there.
http://www.muffinworld.net/android/nookcolor/Talk.apk
You WILL need a different keyboard other than the stock one! This one is great:
http://forum.xda-developers.com/showpost.php?p=9826968&postcount=11
Known Issues:
App exits immediately if you tap on a contact's avatar. This is because the contact management dependencies are not available on the NC.
Click to expand...
Click to collapse
All hail the Muffin Man!
This got Talk to work...thank you...but the keyboard is being truncated. I am only seeing the top 2 rows...
rxr said:
This got Talk to work...thank you...but the keyboard is being truncated. I am only seeing the top 2 rows...
Click to expand...
Click to collapse
That's why you need to switch keyboards
I am using smart keyboard pro and the talk apk you posted doesnt work. I even tried changing the permissions and nothing happened.
Ellerbestyle said:
I am using smart keyboard pro and the talk apk you posted doesnt work. I even tried changing the permissions and nothing happened.
Click to expand...
Click to collapse
Did you also apply the hack to enable Gmail and Android Market previously posted by Mistar Muffin? I believe those steps are a prerequisite to get GTalk to work.
Hmm...this is where I am...gmail/market all set, original talk application didn't work, so I renamed the talk apk's to end in bak, so they wouldn't be running in the background.
I've renamed the other two back to normal, and have slid the apk from this thread over into system/apps. I can't install it from the unit (not allowed anymore since the gmail/market install)
Talk doesn't appear in my app list. Is it because I haven't installed the apk? Assuming this is the case, if I install it using adb when I get home, that should clear thigns up, correct?
graymulligan said:
I've renamed the other two back to normal, and have slid the apk from this thread over into system/apps. I can't install it from the unit (not allowed anymore since the gmail/market install)
Talk doesn't appear in my app list. Is it because I haven't installed the apk? Assuming this is the case, if I install it using adb when I get home, that should clear thigns up, correct?
Click to expand...
Click to collapse
OK. I'm going to assume that you have remounted the /system filesystem as read-write since you say that you renamed the original Talk.apk. Really no need to rename it as it is not an original system binary and it doesn't and will never work.
So, with /system read-write, copy the NEW Talk.apk into /system/app
Change it's permissions to 755 (rwx-rx-rx).
Reboot.
works great. thanks, muffin!
johnopsec said:
OK. I'm going to assume that you have remounted the /system filesystem as read-write since you say that you renamed the original Talk.apk. Really no need to rename it as it is not an original system binary and it doesn't and will never work.
So, with /system read-write, copy the NEW Talk.apk into /system/app
Change it's permissions to 755 (rwx-rx-rx).
Reboot.
Click to expand...
Click to collapse
can permissions be changed within root explorer?
on vending.apk, for example, long press to get to the permissions option. Theres a 3x3 grid with 'read' 'write' 'execute' as columns and 'user' 'group' 'others' as rows.
edit: dont mean to get off topic but my market worked when i checked all the boxes in the row 'user' then rebooted. so maybe that works for talk as well.
johnopsec said:
OK. I'm going to assume that you have remounted the /system filesystem as read-write since you say that you renamed the original Talk.apk. Really no need to rename it as it is not an original system binary and it doesn't and will never work.
So, with /system read-write, copy the NEW Talk.apk into /system/app
Change it's permissions to 755 (rwx-rx-rx).
Reboot.
Click to expand...
Click to collapse
I renamed them to .apk, from .bak. I had changed them rather than moving or deleting them, and meant that I had renamed them to their original names. Which still makes no sense...lol.
I didn't think to change the permissions...I had it sitting at rwx-r-r, swapping to rwx-rx-rx did the trick. Thanks for putting up with stupid questions, your help is greatly appreciated.
Link issues
The "talk.apk" link doesn't work for me; I've tried copying and pasting the link on both Google Chrome and also on IE9, chrome says the site doesn't exist and IE does nothing (acts as if I just clicked the refresh their default homepage).
Ok (after rooting) here is how I installed GApps (Market, Google Framework, etc) on the Nook Tablet, as well as the steps I took to stabilize everything...
1. Downloaded GApps package from goo-inside.me and extracted files.
2. Deleted the setupwizard.apk file from the set of extracted files (in the system\app folder).
3. Copied "system" folder from extracted files to tablet via USB.
4. Used Root Explorer to remount /system and copy files into their designated locations, and also set permissions (644) on all copied apk's in /system/app folder.
5. Rebooted.
6. Ran the market, signed in with my Google account, and downloaded/installed Superuser. Ran the binary update within the app.
7. Install any additional apps from Android Market.
8. Profit.
Known issues...
1. If setupwizard.apk ends up on your tablet you will not be happy.
2. A factory reset is recommended after installing GApps (though probably not necessary).
3. Not all apps show in the Market. Perhaps a build.prop tweak will fix this???
Enjoy!!!
this is a second good news after rooting!
anlong:
Use either wireless adb found here: https://market.android.com/details?id=siir.es.adbWireless
or use debugging toggle found here: http://code.google.com/p/secure-set.../detail?name=ADBWidget-0.2-alpha.apk&can=2&q=
^ instructions for that:
Download ADBWidget.apk
Copy ADBWidget.apk to /system/app (you can use root explorer or something.)
Add ADBWidget to your home screen
Anlog,
I was able to get SuperUser installed following the directions on the other discussion! Thanks for much for all your hard work.
Working on getting Google Apps installed right now.
Update: Well I have SuperUser on my Nook, but whenever I try to copy anything to \system\app it tells me I don't have permissions. Looks like I can't get root to actually run.
run chmod 4755 /system/bin/su
which version of Gapps do I need Cyanogen 6 MDPI?
Make sure root is fully working before you try to install GApps. Use the latest ones for CM7 (I think its from August). You need to remount /system as RW before copying the files and setting permissions. Root Explorer lets you do all of that.
All of this could be done with an ADB script as well, but I won't have time to write one today. Anyone?
anlog said:
3. Not all apps show in the Market. Perhaps a build.prop tweak will fix this???
Enjoy!!!
Click to expand...
Click to collapse
Chainfire should fix it too, and youll be able to run all the tegra 2 also.
Drewmungus said:
Chainfire should fix it too, and youll be able to run all the tegra 2 also.
Click to expand...
Click to collapse
Do not install chainfire! I just tried it and it boot-looped, had to force factory restore.
Finally figured out what was wrong initially, root does not seem to work unless you manually enter commands. Attempted market setup, for some reason it is still force closing every time. Any chance someone who got it working could upload exact files they used.
bkerk25 said:
Finally figured out what was wrong initially, root does not seem to work unless you manually enter commands. Attempted market setup, for some reason it is still force closing every time. Any chance someone who got it working could upload exact files they used.
Click to expand...
Click to collapse
What gapps did you use?
I used the cyanogen 7 universal gapps.
Well, I may have royally screwed up. I followed this tutorial, and I copied over the entire Apps folder from the gapps download. Now I get numerous force closes, and I have no keyboard! Any suggestion?
theundeadelvis said:
Well, I may have royally screwed up. I followed this tutorial, and I copied over the entire Apps folder from the gapps download. Now I get numerous force closes, and I have no keyboard! Any suggestion?
Click to expand...
Click to collapse
I ran into issues copying the whole folder over. I am currently running the google market though.
do everything one step at a time, install the googleframework first (from the directions on the kindle page), then do the market. I ran into the first time through the market would not actually connect so I rebooted the NT.
*note*
each time you reboot your NT you need to go in and what appears is toggle the usb debugging off then on, same with the "auto mount", and I did the unknown sources as well (not sure if this is necessary). It appears a reboot resets the flags and our menu isn't actually writing the settings so you have to toggle it.
Push comes to shove, start over with fresh reboot. It took me a few times (as it probably did others as well).
ok, so can someone who is patient tell me where I need to copy the system folder? help the feeble minded, please.....
JoeM01 said:
ok, so can someone who is patient tell me where I need to copy the system folder? help the feeble minded, please.....
Click to expand...
Click to collapse
lol, i have been struggling with this exact same thing. for those of us who cant fill in the blanks of the brief instructions we need an exact step by step please
suicideclown said:
lol, i have been struggling with this exact same thing. for those of us who cant fill in the blanks of the brief instructions we need an exact step by step please
Click to expand...
Click to collapse
It needs go in system/apps
Drewmungus said:
It needs go in system/apps
Click to expand...
Click to collapse
i'm copying from the system/apps directory (unzipped gapps files), to where on the nook?
I tried copying the files into several locations, but nada.
this is literally the last thing need to knock out for me to be set until the days of ported roms.
please. halp (lelu dallas, multipass).
Drewmungus said:
It needs go in system/apps
Click to expand...
Click to collapse
that part is clearly stated but using root explorer and getting it to mount doesnt seem to work properly on my device. I have root and superuser. titanium backup works fine. for some reason root explorer on es explorer says it fails every time
-1 Go download latest Gapps and extract the contents to your HD. There will be two folders, one of which is "system."
-2 In the system folder there will be more folders, one of which is "app." Inside of app are all the system APKs.
-3 Detele SetupWizard.apk
-4 Now copy the app folder to the root of your NT SD card via USB.
-5 Next step you need to use ADB or Root Explorer...I used Root Explorer.
-6 Open root explorer, then go to sdcard and you should see the APP folder you copied.
-7 Once there, hit menu -> multi select > then put a check mark to what you want copied then hit the copy button.
-6 now hit back untill you're back in the root
-8 Then navigate to system, and at the top you should see button "Mount RW" hit that button.
-9 Then go into the App folder, and hit paste.
-10 All the selected APKs are now in the system/app folder.
-11 Now you need to give each of the copied apps permission by long-clicking on it till a menu comes up, hit permissions, then check all the check boxes next to "Owner"
-12 After you did that to all the apps hit the "mount RO" button on top of the screen
-13 Reboot the NT.
That should do it...hopefully I havent missed anything.
Okay, I don't know how this happened, but I have a strange directory on my external SD card called "D/cuments".
Here is the strange thing. It doesn't show up in root explorer. However, if I adb shell in, I can see it. Also, in Windows explorer, I can see it. But I can't delete it.
If I set my USB connect to PC Mode, I can rename it and delete it from Windows explorer, but it reality, it doesn't happen. If I adb shell in, I'll still see the "D/cuments" folder when I do an ls. If I do an ls -l in adb shell, it not there.
If I set USB connection to USB Mass Storage mode, I can still see the "D/cuments" folder in Windows explorer, but I cannot delete it or rename it as I get the following error:
Cannot delete file: Cannot read from the source file or disk.
I have no idea how this file showed up on my SD card.
Any ideas? I really want to avoid having to reformat the card, but I guess my only recourse is to copy everything over, reformat the SD card, and then copy everything back.
Thanks!
Haha...sorry I was about to suggest u format the card before I read the last part of ur post
Had u installed any new apps recently? Or been messing around with ur sdcard?
ashclepdia said:
Haha...sorry I was about to suggest u format the card before I read the last part of ur post
Had u installed any new apps recently? Or been messing around with ur sdcard?
Click to expand...
Click to collapse
I had been restoring some nandroid backups, but that's about it.
I'm in the process of backing up the SD card and getting ready to reformat it. <sigh> Since it's 32gb and I have my music on it, it's going to take some time. Yuck!
I wonder if it has just been there for a long time but u just never noticed it b before lol
But I was gonna say if it ain't a big file and it isn't hurting anything u might as well just leave it there instead of screwing with it and possibly killing your card some how
ashclepdia said:
I wonder if it has just been there for a long time but u just never noticed it b before lol
But I was gonna say if it ain't a big file and it isn't hurting anything u might as well just leave it there instead of screwing with it and possibly killing your card some how
Click to expand...
Click to collapse
It's empty and takes up zero storage. It's just kind of annoying seeing it there.
What's really strange is, if I use the default ls command in ADB, it shows up. If I do an ls -l, it doesn't show up.
Code:
# ls
ls
...
Documents
com.espn.score_center
Cut the Rope
data
[B][COLOR="Red"]D/cuments[/COLOR][/B]
download
ezPDFReader
...
#
#
#
# ls D*
ls D*
D/cuments: No such file or directory
#
Then, if I use the ls command in BusyBox, it still doesn't show up. It's really strange.
I don't know if it could have been malware, but I don't run any suspicious applications. All my apps are purchased from the Market or Amazon Market, other than of course, various flash zip files from XDA, but even then, the only things I've flashed/installed that are not from the market are as follows:
Eclipse 1.3
2.3.4 build.prop Mashup
DX2 Battery Fix
BSR
All of these I downloaded from XDA and have used for months, so I've never seen this before.
I did have other directories show up that I was able to delete that looked like the wonderful Windows short-hand for long file names. You know, those stupid filenames with tildes (~) in them to fit the 8.3 filename format? Really strange.
The only thing I can think of that might have caused this, now that I think of it, was when I was connected via PC Mode and was copying files from my SD card to my hard drive. It hung and wouldn't stop and I had to go, so I tried cancelling the copy and it wouldn't cancel. I then tried to eject the phone via the windows "remove hardware" quick access icon and that didn't work, so I had to just pull the USB cable from the PC. Not sure if that could have caused this or not, but I wasn't copying anything TO the SD Card. I was copying FROM the SD card.
Oh well.
That could easily cause problems like you're seeing. If you haven't formatted the card yet, try running chkdsk on it from Windows. chkdsk (drive letter) /f
Might have info on it for plug and play and thats why you cant delete it. Flash drives have files on them for that even if they are formatted. That may be it. I do not know for sure.
Before doing anything drastic, try something easy: reconnect it to your windows install and try safely removing. Sometimes it'll lock a file if it is unmounted uncleanly.
If that doesn't work, I'd head back to the terminal and try a few more things. Android will have problems with a file containing a slash because slashes indicate separate directories. It's probably getting confused. I'd try doing ls -la followed by the filename (cap sensitive!) in quotation marks. That should tell the shell to interpret the name as a single entity instead of trying to split it into a directory called D containing a file called cuments, which it might be doing. If it shows the file that way, run rm the same way. If it sees the file at that point but can't operate on it, su to root first and then maybe try using rm -rf.
Edit: Actually, after further consideration, there's going to be no way to remove the file from within Android. Any utility that you use to try to remove it will interpret it as a file within a directory instead of a single directory. There's no way to create such a file from within the system, so it shouldn't exist, period. There's no way to get to it from within your phone since forward slashes are hardcoded into the kernel as indicators for directories, so the usual tricks, like escaping the slash with a backslash or using quotation marks won't work. You're going to have to deal with the file from within Windows by mounting your sd card. That's the only way you'll ever get rid of it short of a reformat.
robocuff said:
That could easily cause problems like you're seeing. If you haven't formatted the card yet, try running chkdsk on it from Windows. chkdsk (drive letter) /f
Click to expand...
Click to collapse
That fixed it! I ran the Error-checking tool from Local Disk Properties in Windows Explorer, had it automatically fix file system errors and scan for and attempt recovery of bad sectors. Once that happened, the "D/cuments" folder became "DOCUME~1" and I could see the files inside of it.
Thanks again for the simple, yet effective, tip!
Sooooo
What was in the folder? Lol.....
You know, "Documents"
RyanThaDude said:
You know, "Documents"
Click to expand...
Click to collapse
Must have been a NOClist lol
ashclepdia said:
Must have been a NOClist lol
Click to expand...
Click to collapse
Well, it was a Mission that was Impossible trying to delete it before I ran check disk on it.
Glad to hear that fixed it for ya. Anytime odd things like that start happening, chkdsk is always my first resort. It's not always the answer but it's one of the easiest things you can do and, well, I don't know about you but I've always been one to take the easy way out if I could.
Have you tried to solve this with specialized software?
When I receive this kind of messages, or messages like path too long, Could not find this item, Error Copying File or Folder, etc.
dan_lee_01 said:
When I receive this kind of messages, or messages like path too long, Could not find this item, Error Copying File or Folder, etc.
Click to expand...
Click to collapse
What is this I don't even
the run on sentences are driving me
ashclepdia said:
the run on sentences are driving me
Click to expand...
Click to collapse
What is wrong with run on sentences they seem to work find and the get the point across too and they aren't that hard to read and follow and they are easier to type atleast I thinks so don't you?
Sent from my Cyanocrack using Xparent Blue Tapatalk
motcher41 said:
What is wrong with run on sentences they seem to work find and the get the point across too and they aren't that hard to read and follow and they are easier to type atleast I thinks so don't you?
Sent from my Cyanocrack using Xparent Blue Tapatalk
Click to expand...
Click to collapse
Lol
sorry I meant the incomplete are driving me
So I repartitioned my media and storage drives yesterday, and although I did have a few problems (post #156-158) I finally managed to repartition and proceeded mounting the drives in 1.4.1 rooted B&N. Also checked if they worked via usb to computer which they did. I then decided that I wanted to try cm7 today and installed it flawlessly. Only problem is that now my newly resized 10GB internal media partition don't show up. So tried installing the;
[CM7][GB] Soft-mod RibbonICS ROM by veronica, but still no change.
In the storage settings i've tried to mount the
Additional storage/mnt/sdcard/_internalSD but doesen't work and thats probably also just the folder I created myself as instructed in the soft-mod.
So yeah I'm wondering if I can only use the extended media part in stock rooted B&N or if its got to do with the problems I had with the process. Or mayb I just need to mount the media drive somewhere?
Please help
Went into adb-shell in CWM and checked via the p command if the media drive was there which is was
(looked like this: 10 1611MB 11.6GB 9989MB fat32 media msftres)...so it really should work.....shouldn't it?
Edit: actually the above is not entirely correct: I have found my media partition in the file browser now but its just not really accessible it seems. Is it just not mounted or what?
Included in the soft-mod for cm7 is also an application called multi-mount sd lite which should help with this but it force-closes on me even after i fix permissions need help with this..
nook tablet cm7 can not access internall sd
Hi
I loaded cm7 onto my nook tablet 16g internal SD using your latest Zip and it worked like a charm. Thank everybody.
only problem I have is that I can't access the internal SD from my windows computer. It accesses the external one fine but not the internal one.
can download app into internal via web and brows around it.
It doesn't seem to be mounted for external USB access.
Can anyone help with this?
Thanks Martyn
There's a typo in two lines of the build.prop. Described here: http://forum.xda-developers.com/showthread.php?t=1540272&referrerid=4611244
But the link to the corrected build.prop there doesn't work! There's a good link further down the thread...but I attached mine here if you want to use it.
Just download to the root of your removable sdcard and install it from CWM. Or extract it and copy it to /system with your favorite file explorer to overwrite the "typo" version.
EDIT: by "mine" I mean my copy of Celtic's.
OOPS!
Sorry. My reply above was to kingtechmartyn, not the OP domiel...didn't mean to hijack the thread.
Very sorry.
There's a typo in two lines of the build.prop. Described here: http://forum.xda-developers.com/showthread.php?t=1540272&referrerid=4611244<br />
<br />
But the link to the corrected build.prop there doesn't work! There's a good link further down the thread...but I attached mine here if you want to use it.<br />
Just download to the root of your removable sdcard and install it from CWM. Or extract it and copy it to /system with your favorite file explorer to overwrite the "typo" version.<br />
<br />
EDIT: by "mine" I mean my copy of Celtic's.
Click to expand...
Click to collapse
Just remember when changing build.prop to always make a backup of the original so if you want to revert you can.
Sent from my Nook Tablet using xda premium
I don't know if its specific to root explorer or not, but whenever I modify a build.prop that I have navigated to via root explorer, it automatically adds a .bak extension to the original build.prop file.
for an edit of build.prop, be sure to use the correct edit tool which places a 'line feed' at the eol and not a 'carriage return and line feed'.
hth.
Cubanluke88 said:
I don't know if its specific to root explorer or not, but whenever I modify a build.prop that I have navigated to via root explorer, it automatically adds a .bak extension to the original build.prop file.
Click to expand...
Click to collapse
Normal
Cubanluke88 said:
I don't know if its specific to root explorer or not, but whenever I modify a build.prop that I have navigated to via root explorer, it automatically adds a .bak extension to the original build.prop file.
Click to expand...
Click to collapse
you are right, normally a backup is automatically created. But, I have seen a lot of requests since November when we started messing with this device of people making mistakes and not having a backup. So it is always a good idea to copy and then save to the sd card just in case.
Sent from my Nook Tablet using xda premium
Well to be quite honest, before you make any sort of system modifications, you should always make a nandroid backup.
Having a backup of the build.prop or whatever file is nice because it allows you to quickly revert. But a nandroid backup protects you from when the damn thing decides to temp brick.
build prop differences
Also be aware that the build prop typo correction from the Team B CM 7 release (and I believe the RC2 release from a different source I cannot remember) is different from the mods Veronica released - she has developed her own build prop to handle the internal storage. I also had problems with the included Multi Mount SD Card Lite included in her mod and purchased the full version for $.99 which corrected the problems. Also note that there is an underline before _InternalSD in the full release of her mod which is different from just the small mod that handles the Internal over External SD card. Make sure you are being consistent with the folder name you create with the mod version you have installed.
Cubanluke88 said:
Well to be quite honest, before you make any sort of system modifications, you should always make a nandroid backup.
Having a backup of the build.prop or whatever file is nice because it allows you to quickly revert. But a nandroid backup protects you from when the damn thing decides to temp brick.
Click to expand...
Click to collapse
exactly, if more people would do this there might be fewer issues due to being able to restore if there is a oops moment.
Sent from my Nook Tablet using xda premium
Hi Bernardicus
Thanks heaps you are a champion!
I don't even know how to get terminal into su yet so you zip was a god send.
Now I have to work out how to enlarge the 1g of memory, i must admit it's very fulfilling modifying my Nook, looking forward to be proficient enough to return the favors from you all.
RhinoNelson said:
Also be aware that the build prop typo correction from the Team B CM 7 release (and I believe the RC2 release from a different source I cannot remember) is different from the mods Veronica released - she has developed her own build prop to handle the internal storage. I also had problems with the included Multi Mount SD Card Lite included in her mod and purchased the full version for $.99 which corrected the problems. Also note that there is an underline before _InternalSD in the full release of her mod which is different from just the small mod that handles the Internal over External SD card. Make sure you are being consistent with the folder name you create with the mod version you have installed.
Click to expand...
Click to collapse
Absolutely correct. I'm running her ribbon ics mod now on top of the Team B CM7 ROM (and loving it). She also modded the vold.fstab in /system/etc to reflect those changes in build.prop. I ended up replacing her vold.fstab with the Team B version and editing her build.prop to reflect the corrected "typos" in the Team B build.prop. (I know, I de-modded the mod, but for some reason, using the multi mount widget to do something that the OS should handle made the hairs on the back of my neck stand up!)
I'm spending more time modifying this thing that actually using it! But it has been fun.
bernardicus said:
Absolutely correct. I'm running her ribbon ics mod now on top of the Team B CM7 ROM (and loving it). She also modded the vold.fstab in /system/etc to reflect those changes in build.prop. I ended up replacing her vold.fstab with the Team B version and editing her build.prop to reflect the corrected "typos" in the Team B build.prop. (I know, I de-modded the mod, but for some reason, using the multi mount widget to do something that the OS should handle made the hairs on the back of my neck stand up!)
I'm spending more time modifying this thing that actually using it! But it has been fun.
Click to expand...
Click to collapse
I'm running Veronica's NT_CM7_Ribbon_ICS_v2.1 and I have the same problem. I replaced her vold.fstab with the Team B version and edited her build.prop. Now I can mount the Internal SD on my computer. Thanks for the help.