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.
Related
I can't seem to locate the directory folder that the new firefox app downloads to. anyone?
Nevermind, it goes right to the sdcard, no folder. I didn't see the files because the downloads failed...
can't seem to get the download folder to change.
I went into:
about:config
created a new string: browser.download.dir
set the value to: /mnt/extSdCard/Downloads/
Restarted Firefox
But still the downloads go into the sdcard/downloads
I've also tried:
/extSdCard/Downloads/
/sdcard/
/extSdCard/
/mnt/sdcard
none of these have any effect.
Any ideas?
Bump:beer:
Sent from my SGH-I747M using Tapatalk 2
Im also looking for changing my dl directory. It have work once for me when modifying the "browser.download.folderList" after creating the browser.download.dir string. But after reboot of firefox the next dl will go back again to the sdcard.
Wonder if anyone else could tell how to do it
creating a new string is a good step for changing your dl directory. But you should also add this step to make it work.
Modify the value of "browser.download.folderList" from 1 to 2
Thats it!!
Click to expand...
Click to collapse
When editing your old posts, try not to delete the original information that could have been useful to others.
People won't have known what value to put into the string.
Sent from my SGH-I747M using Tapatalk 2
I hate managing folders so now I use directory bind which allows me to bind two folders together. Basically you create another downloads folder on your external sd card and use directory bind to "bind" them. Checkbox to transfer contents and your downloads (source) folder will be dumped into the empty folder you've created automatically (destination must be empty when checking the box). When altering files in either downloads folder, the changes appear in both. When you look at storage, the original source folder is not calculated into your used internal storage amount even though every other app sees files in there (since that would defeat the purpose). I use it for my downloads, camera and several apps and game folders not designed to be pushed to SD. Instead of continuously resetting app download destinations, I sit back and relax knowing every app downloads to the proper place (minus the rogues who think they deserve their own folder lol). When flashing a new ROM, simply unbind everything first and disable autostart, backup with titanium backup, after restore, you should be good (depending on your new version of android in which case you may need to adjust some settings). If setting up from scratch again, assuming your working folder structure is still in tact, you can bind again without ticking the box (since the files are in their proper place and a transfer is no longer necessary).
You can get it here, it looks like it hasn't been updated in a while, but I've tested it from Android 4.0 through 4.2.2 and it's perfect (settings adjustments will likely be required): http://forum.xda-developers.com/showthread.php?t=1410262
Hi everyone, was a solution found to that still issue? I tried to move the default download folder to the ext SD card with settings into about:config, I changed as well the "browser.download.folderList" value to 2 and add a "browser.download.defaultFolder" string, but everything failed, please does someone know what to do? Or is there another setting menu or mod/Exposed module to achieve this..?
Thanks in advance for the help!
May I Taste said:
Hi everyone, was a solution found to that still issue? I tried to move the default download folder to the ext SD card with settings into about:config, I changed as well the "browser.download.folderList" value to 2 and add a "browser.download.defaultFolder" string, but everything failed, please does someone know what to do? Or is there another setting menu or mod/Exposed module to achieve this..?
Thanks in advance for the help!
Click to expand...
Click to collapse
Use this config (I am assuming you're on 4.4 and have used SDFixer)
SeraphSephiroth said:
Use this config (I am assuming you're on 4.4 and have used SDFixer)
Click to expand...
Click to collapse
Hi, thanks for your help, but it still don't work for me. What I don't understand is that the path can be whether
/storage/sdcard1/Download
or
/ext_card/Download
Maybe you know why? I'm running CM11 nightlies (4.4.4) on Xperia Z2
May I Taste said:
Hi, thanks for your help, but it still don't work for me. What I don't understand is that the path can be whether
/storage/sdcard1/Download
or
/ext_card/Download
Maybe you know why? I'm running CM11 nightlies (4.4.4) on Xperia Z2
Click to expand...
Click to collapse
With a r/w sd? Use a root explorer to find the path to the r/w sd
I'm very busy and sorry not to say anything for long but thank you much for your answer and help.
My path is correctly pointing the SD, I checked carefully the settings and got no success. Then suddenly Firefox began to write on ext sd, but still this is only sometimes! I tried to see if the files type or size had something to do with that behavior but it seems to be just erratic..
It actually seems that it's the "Flash Video Downloader" module who sends files into the internal storage regardless of the browser settings..
This Avatar.apk is for those who have upgraded to Froyo with an unofficial build that doesn't include a working Avatar app, but desire a working Avatar.apk that launches the DRM protected copy of the movie included with the phone.
Some caveats/disclaimers: I don't own a Vibrant; I have an i9000 Galaxy S and a Nexus One. I don't plan on providing much support for this, but it shouldn't need it. All the usual "I am not responsible for damage to your phone" disclaimers apply; if you don't know how to use adb and don't have root, go find out how in the appropriate FAQs.
Back story: My friend owns a Vibrant and hated it (slow/laggy). I thought upgrading it to a Froyo build would make him happy, so I did with Team Whiskey's Onyx version (very slick, better than the best ROM I have on i9000 IMHO). He was disappointed that the Avatar shortcut/app on the desktop disappeared, so I pulled the apk from a 2.1 build and pushed it to the phone, but it didn't work.
A little investigation showed that the apk file has an xml resource that is hard-coded to look for the encrypted/drm copy of the movie in the path "/sdcard/sd/movie/AVATAR.dcf", but the Froyo builds mount the external card as "/sdcard/external_sd/" so the app doesn't work.
All I did here was edit the xml file to the correct path, repacked the apk, signed it, pushed it to the phone with adb to /system/app. The apk was then available to add as a desktop shortcut again, and it opens the movie as expected.
The file won't install like a regular apk (at least it wouldn't for me), it must be pushed to /system/app to work - use this command:
adb push <your path>/Avatar.apk /system/app
You could also probably download the apk and copy it over to /system/app with Root Explorer or any other file manager that lets you write to /system/app.
I have only tested this with Team Whiskey's Onyx build and by pushing via adb. I can't test any other ROM since I don't own a Vibrant.
I know a lot of people consider the Avatar.apk to be bloatware and ask how to remove it, but I see a lot of people asking for it back because it's convenient and a great show-off feature on the phone for non-Galaxy S owners.
Additional disclaimers: I did quite a bit of searching here on XDA for an apk that took this approach and didn't find one. If it's already out there, I apologize for this post and can link to it. All I found was an apk that requires you to have a non-encrypted mp4 copy of the movie. I also found a lot of bad information about you could use the original 2.1 version if you just de-odexed it and other stuff like that. Again, this will ONLY work on a 2.2 Froyo ROM because of the change in mounting path of the external sdcard.
credit/thanks to Brut.all for his apktool and to jessetbenton for his Mac-friendly android auto signing applet.
Edit: I only modded the English language part of the apk, it may not work properly if you're using a different language.
Here's the apk, enjoy:
Wow, that first post is a lot of words for such a simple posted apk! LOL. I just wanted to make sure to cover all the bases for any criticisms I might be getting.
Thanks dude, I kept trying to install the old avatar.apk, and when I tried opening avatar, it kept giving me "file not found"
Oh, btw works on Eugene's Macnut R12
You could also just make a folder named "sd" on the sd card, and move the Movie folder there. Works just fine for me.
pablizzo said:
You could also just make a folder named "sd" on the sd card, and move the Movie folder there. Works just fine for me.
Click to expand...
Click to collapse
Yes, but then you lose that 1gb of space on your internal sdcard.
I'd have gone for a symlink approach instead, but the internal card is plain old FAT32 and doesn't support them.
Or just use the stock froyo Avatar.apk? Lol. Worked for me...
distortedloop said:
Yes, but then you lose that 1gb of space on your internal sdcard.
I'd have gone for a symlink approach instead, but the internal card is plain old FAT32 and doesn't support them.
Click to expand...
Click to collapse
1 out of ~13gb is fine with me
rk0 said:
Or just use the stock froyo Avatar.apk? Lol. Worked for me...
Click to expand...
Click to collapse
Ah, that's good. Where'd you get it? I thought there wasn't a Vibrant specific Froyo yet - all I see on samfirmware.com are 2.1 builds. Like I said, I'm not a Vibrant owner, so don't really keep up with its developments.
Thanks for posting that.
pablizzo said:
1 out of ~13gb is fine with me
Click to expand...
Click to collapse
Yeah, to each his own.
My internal 16gb on the i9000 is almost full (nandroid backups, media, etc), and I have an external 16gb that's more than half full. I prefer to keep large media files on the external, obviously YMMV.
Glad you had a solution that works for you.
Nice thanks
Been looking all over this...thanks
Sent from my XDA app cuz I'm stalking your mom....
distortedloop said:
Ah, that's good. Where'd you get it? I thought there wasn't a Vibrant specific Froyo yet - all I see on samfirmware.com are 2.1 builds. Like I said, I'm not a Vibrant owner, so don't really keep up with its developments.
Thanks for posting that.
Click to expand...
Click to collapse
Deodexed JK2 Rom.
rk0 said:
Deodexed JK2 Rom.
Click to expand...
Click to collapse
Thanks for the response.
I wish someone had answered any one of the dozens of posts I read where people were complaining or asking about this with that info. Would have saved me the trouble here.
Actually, it worked out well for me anyways. I have a couple of apps with the same problem where I really want to force them to use the external card instead of the internal. Now I've learned an approach I can use to "fix" or mod those apps. I wish app developers would let you specify a preferred working directory - hard coded paths aren't usually a good idea in my opinion.
At any rate, based on the number of views of the thread, and over 140 downloads between my version and yours, seems like a lot of people didn't know about this, and we've given them a working solution. That's a good thing in my opinion.
can u make this work from terminal?
Please help me to get Avatar working !
Iam on Darky's 10.2 ROM(GB 2.3.4), bullet kernel & KB5 modem.
and the movie is at the same folder structure since, my phone came stock.
I tried:
1.) I cleared drm content and drm protected content & restarted my phone two times- then downloaded the app from http://forum.xda-developers.com/showthread.php?t=774078 but it won't install.
2.) I used the Android customisation suite from http://forum.xda-developers.com/showthread.php?t=894794 and created a zip with just the avatar.apk , cleaned dalvik cache, and the installed the zip from CWM, still the application just clicked, but no response/error message whatsoever.
3.) I downloaded a terminal emulator & tried to push the apk from this thread and I get adb:not found.
Please guide me, what needs to be done, as I haven't seen the movie [email protected]!
Great work I know this has been a huge issue for many many people ...I no longer have avatar on my phone but I sure missed the launcher at one time back when I first flashed my phone
Shortbus-Driver said:
Great work I know this has been a huge issue for many many people ...I no longer have avatar on my phone but I sure missed the launcher at one time back when I first flashed my phone
Click to expand...
Click to collapse
Buddy, I haven't been able to get it working, thru any of these methods!
I guess, I might have been doing something wrong in ADB Push. But I even tried with a Root File Explorer and replacing the Default Application that i had flashed using zip generated by Android Customization Tool(ACS) , with one provided in the two links(one of them, gives application not installed,probably the bigger in size one, and so installed the other one, thereby replacing the default that I talked above). but for no good.
Avatar, still doesn't work. Please help, guys!!
Well as many of you know we're over most of the hurdles we needed to jump with the CM7 build for Nook tablet.
Updates for the internal version are simple via CWM, the SD version is not so simple of course.
I'm assuming that it should be possible to built an APK that gains superuser permissions then copies the new files to the system. Can anybody confirm this is possible please?
We need to know that we can tell our SD user that they can update their version just as easy as the internal user
Thanks in advance for your help again everyone!
Well presumably this is how ROM Manager and Metamorph both do their thing, just in a slightly more round about way (as they don't come with the files they need to copy). I'm almost 100% sure this is possible, but I've never tried it personally.
EDIT: Looks like this is how you'd do it: http://developer.android.com/reference/java/io/File.html. Specifically the renameTo() method.
CelticWebSolutions said:
Well as many of you know we're over most of the hurdles we needed to jump with the CM7 build for Nook tablet.
Updates for the internal version are simple via CWM, the SD version is not so simple of course.
I'm assuming that it should be possible to built an APK that gains superuser permissions then copies the new files to the system. Can anybody confirm this is possible please?
We need to know that we can tell our SD user that they can update their version just as easy as the internal user
Thanks in advance for your help again everyone!
Click to expand...
Click to collapse
Well there are about a dozen ways to do this. First of one of the hardest things is comming up with the commands/script. I can defiantly do this. If you want an apk, there are a few guys whom could port my script to an apk. I'm going to make a script here that will format, and create partitions and extract directly from the nook, no need to go through the fancy formatting and such, just go into terminal and run the script. Ill post a prototype for you to have the testers test!
Do you think something like BacksideUpdater inside custom ROM for LG Optimus V?
made by JerryScript
JerryScript i very nice guy, I bet if you ask him, he will let you play with his code
if is it what you looking for
Yes, this is possible. I wrote an app that flashes the recovery partition for my older Froyo phone in the very rudimentary Basic4Android. Copying files under root privileges was part of this process. Fairly easy if you find the right coding examples in whatever your development platform of choice.
xdajunkman said:
Yes, this is possible. I wrote an app that flashes the recovery partition for my older Froyo phone in the very rudimentary Basic4Android. Copying files under root privileges was part of this process. Fairly easy if you find the right coding examples in whatever your development platform of choice.
Click to expand...
Click to collapse
So one of the problems is its not really copying. Its more of an extraction from one place to another. We are required to use dd, and fdisk(for formatting).
GREAT! I was worried updates would be to complicated for people
Sent from my Nook Tablet using xda premium
... and I was worried that I might have to wipe my NT clean again to get the updates. After a week with this wonderful upgrade, I've got a LOT of customization I don't want to lose...
Whoops, wrong button with the thanks. Anyway, it occurs to me you could just have people run a script from a terminal emulator. That would probably be the simplest way to do it. Make an Update folder on the SD card, add it to the PATH by default, and users could just copy over the update files and run the script. Just a thought.
Sycobob said:
Whoops, wrong button with the thanks. Anyway, it occurs to me you could just have people run a script from a terminal emulator. That would probably be the simplest way to do it. Make an Update folder on the SD card, add it to the PATH by default, and users could just copy over the update files and run the script. Just a thought.
Click to expand...
Click to collapse
Has to be simple, something like copy an update.zip onto the SD card then run the apk which will automatically run the update in the zip But my knowledge of such things is limited so I need help there
Same process. With the above method, the user would only have to copy over the file, open a terminal, and type 'update'. With the apk idea you just have to add a little more time for someone to actually write the app (not that it would take too long).
Sycobob said:
Same process. With the above method, the user would only have to copy over the file, open a terminal, and type 'update'. With the apk idea you just have to add a little more time for someone to actually write the app (not that it would take too long).
Click to expand...
Click to collapse
Hmm.... that sounds good.
Anybody know how to actually implement it ?
Dammit, idk why I keep hitting the thanks button thinking it's reply >.>
Anyway, it's just a matter of setting the PATH variable to include /sdcard/Update/ or something similar. To make an actual update, make a folder called Update, fill it with all the files that need to be copied over (probably in a directory structure), and write a script that actually copies everything over. You'll need to make sure sh is in /system/bin (I think it is by default).
You could zip the the files as well, using gunzip (busybox?) to extract them before copying them, then deleting them when you're done, just to keep it cleaner for the user.
The only downside to all this is that I don't know how you would flash a kernel.
Sycobob said:
Dammit, idk why I keep hitting the thanks button thinking it's reply >.>
Click to expand...
Click to collapse
That makes two of us!
Sycobob said:
Anyway, it's just a matter of setting the PATH variable to include /sdcard/Update/ or something similar. To make an actual update, make a folder called Update, fill it with all the files that need to be copied over (probably in a directory structure), and write a script that actually copies everything over. You'll need to make sure sh is in /system/bin (I think it is by default).
You could zip the the files as well, using gunzip (busybox?) to extract them before copying them, then deleting them when you're done, just to keep it cleaner for the user.The only downside to all this is that I don't know how you would flash a kernel.
Click to expand...
Click to collapse
I'm guessing you'd just flash it as usual, surely that one is the easiest? Copying stuff to boot partition would hopefully be just as simple, I was mainly worried about updating system files. I could do with building one for the current update to test the theory!
Enable Copy & Paste on the Nook Tablet
Background
The lack of copy & paste functionality on the Nook Tablet is one of the most annoying "features" of the B&N firmware and it affects not just geeks like me but also the average user. This thread and this thread are two of many, many threads complaining about the missing copy & paste. This thread proposes a "fix" by combining the Hacker's Keyboard and Swype, but is still really lame.
The method I will describe here solves the problem by replacing /system/framework/framework.jar which contains the code for Android widgets like text fields. I have merged into the stock /syste/framework/framework.jar the code responsible for copy & paste from the Android source code.
Instructions
Video walkthrough: http://www.youtube.com/watch?v=7V70a3FYbt4
0. Before you proceed, know that THIS IS EXPERIMENTAL SOFTWARE THAT PROBABLY VOIDS YOUR WARRANTY AND MAY PERMANENTLY OR TEMPORARILY BRICK YOUR TABLET. Even though it worked for me, it may not work for you, and worse, it is quite possible that it could cause your tablet to boot-loop or die. I AM NOT RESPONSIBLE FOR ANY POSSIBLE DAMAGES TO YOUR TABLET / ANYTHING ELSE CAUSED BY THIS METHOD. BY USING IT YOU AGREE TO ASSUME ALL RESPONSIBILITY FOR YOUR ACTIONS.
1. Your tablet needs to be rooted for this to work. If you have not rooted it yet, search this forum for instructions.
2. Since we will be copying files to /system, you will need to install ES File Explorer or Root Explorer or whatever other app that allows you to do that.
3. Download the file that corresponds to your OS version from below:
1.4.2 (16GB/8GB): http://www.mediafire.com/?5pf2aegq02194lq MD5: ef35d35daffd0d9574f48a43ccc4b58c1.4.0 (16GB): http://www.mediafire.com/?es6gd31wzr7yk8a MD5: 99d2e7eff173fbdc77c79b4f4a6ff53c
The 1.4.0 version has been reported to cause boot loops for some people, while it has worked for others. You have been warned.If you're on a different OS version, post the file /system/framework/framework.jar form your tablet and I will make a package for it.
4. Extract file contents to microSD card, and insert microSD card into the tablet.
5. Using ES File Explorer / Root Explorer, copy the extracted file framework.jar.new to the directory /system/framework/. (If you're using ES File Explorer, make sure "Up to Root", "Root Explorer", and "Mount File System" are checked in settings.)
6. Copy the extracted file uim-sysfs to /system/bin/.
7. Go to /system/bin/, and change the permissions of the file uim-sysfs to executable. (If using ES File Explorer, long press -> Properties -> Change -> Check everything under "execute".)
8. Power off tablet and power on again. The tablet should take much longer to boot this time than normally, so no need to worry. When the tablet boots up, you will most likely see lots of force close dialogs. This is normal.
9. Wait one minute. You could be stuck in a boot loop if you don't wait.
10. Power off tablet and power on yet again. This time it should also take much longer to boot; the boot times will return to normal after several reboots.
11. Profit.
Force close issues
The first time you run some (read most) apps after applying this hack would likely result in force closes. While annoying, there is no way to get around it due to how the Dalvik VM caches references to /system/framework/framework.jar. In addition, every time you install new apps or update apps, you will have to reboot the machine before those apps are usable; you will get a force close when you try to use those apps until you reboot.
The solution is simply to reboot your tablet each time you get a force close error from an app that worked fine before this hack. The force close error for that particular app should go away following a reboot. If you get a force close from another app after that, just reboot again.
How it works
The information below is for people interested in understanding how this stuff works. If you just wanted to enable copy and paste on your tablet, you can stop reading.
This hack is based on the exploit explained at http://forum.xda-developers.com/showthread.php?t=1534518. The uim-sysfs script in the attached file saves the stock /system/framework/framework.jar, copies over my modified framework.jar.new, and restarts the zygote process. After the zygote process has loaded my framework.jar.new, the uim-sysfs script restores the stock /system/framework/framework.jar so that /init will not bail on the next boot.
To enable copy & paste in /system/framework/framework.jar, I decompiled the stock implementation and merged in related code from AOSP. The two classes I changed are android.widget.TextView and android.widget.EditText. For android.widget.EditText, I simply used the AOSP implementation because the only difference between the two was in the enabling of copy & paste. I manually merged android.widget.TextView because there appears to be B&N enhancements in it in addition to disabling copy & paste.
The exact steps I took as well as a diff of my modifications are documented in post #12.
Disclaimer
Again, this is experimental software. That it worked for me does not mean it will work for you, or that it won't brick your tablet. I am not responsible for any possible damages resulting from using this method.
Here i post framework.jar from stock 1.4.0 rooted
~ Veronica
lavero.burgos said:
Here i post framework.jar from stock 1.4.0 rooted
Click to expand...
Click to collapse
OK. Looks like the framework.jar from 1.4.0 is different from 1.4.2; I've merged in the same changes. If you're feeling brave, the package I've made for 1.4.0 is here.
MD5: 99d2e7eff173fbdc77c79b4f4a6ff53c
Can you confirm whether this works?
16gb Nootlet with 1.4.0 rom, rooted, OTA blocked yada yada.
Stayed at the "read forever" screen almost forever, then finally started up. Fellow victims take note, it isn't dead so be patient.
Lots of FC, the last persistent one was the launcher (ADW ipaidforthis version)
Powered off and on again after waiting way longer than 1 minute.
Second boot forever at "read forever" screen so far.
If it comes back to life I'll try the 1.4.0 version & let you know.
[Edited to add}
... time passes ...
Any way out of the "ADWLauncherEX" force-close loop? Does Android have a "safe mode" boot option like Windows? (sorry)
No, I haven't installed CWM recovery yet. Remind me to do that if this thing ever gets over its mental breakdown.
jichuan89 said:
OK. Looks like the framework.jar from 1.4.0 is different from 1.4.2; I've merged in the same changes. If you're feeling brave, the package I've made for 1.4.0 is here.
MD5: 99d2e7eff173fbdc77c79b4f4a6ff53c
Can you confirm whether this works?
Click to expand...
Click to collapse
Thanks can't test right now 'cause im finishing another project and then i have to test the tun.ko module for CM9 busy bee .
~ Veronica
cellhead said:
Stayed at the "read forever" screen almost forever, then finally started up. Fellow victims take note, it isn't dead so be patient.
...
Second boot forever at "read forever" screen so far.
Click to expand...
Click to collapse
Thanks for mentioning this. Will add to instructions.
cellhead said:
Any way out of the "ADWLauncherEX" force-close loop?
Click to expand...
Click to collapse
Getting FC's is normal - as the instructions state you probably have to reboot a number of times before all FC's disappear. Any luck so far? If not, please let me know and I will post a recovery SD card image that will allow you to undo this hack.
Also - as I said clearly in the instructions (Compatibility section), before you try this out on your 16GB, you should post your /system/framework/framework.jar so I can verify that this works on the 16GB. I don't have the 16GB tablet so I don't know if this works on it at all. Anyone?
Thanks. You may want to feature the version info prominently in the OP. I got my issue solved in a roundabout way when it finally went into a boot loop and triggered the factory reset. That got me back to 1.4.0 unrooted, and without the FC problems. Reran indirect's rooting script and I'm back to some semblance of normality.
Ain't complaining, I took on the risk of trying your copy/paste fix and went on an unplanned adventure. Such is life as a RL software tester ;-)
I'll wait and see how things shake out. You're onto something good here, so once it's a little safer for the normals to apply it, I'll give another go.
For the record, 16g Nook tablet, rooted via indirect, OTA blocked, v1.4.0
cellhead said:
You may want to feature the version info prominently in the OP.
Click to expand...
Click to collapse
You're right...really sorry about that.
On the other hand, did you try the files in the original post, or did you use the files for 1.4.0 I posted in the 3rd post?
The ones in the original post. Then I read the third post, but was unable to get it to boot far enough that I could replace the files and try again.
Sent from my BNTV250 using xda premium
cellhead said:
The ones in the original post. Then I read the third post, but was unable to get it to boot far enough that I could replace the files and try again.
Click to expand...
Click to collapse
The files in the original post are modified from 1.4.2 and would most certainly not have worked on 1.4.0...I should have made that clearer. Sorry.
The files in the 3rd post though are modified from 1.4.0 (thanks to lavero.burgos) and should work for you. Any chance you could test them out?
--- EDIT ---
Also - I've made a bootable SD card that will remove this hack and fix the tablet even if something goes wrong and you cannot boot into the system to remove the files directly. I can post it if someone needs it.
Cool hack, but why all these doubts and asks for 16gb's framework.jar ? What users have on devices comes from vendor firmware package(s), and you can see at http://www.barnesandnoble.com/u/Software-Updates-NOOK-Tablet/379003187/ that there's no separate versions for 8gb vs 16gb. That page (and pages for other releases) should be also the authoritative place for getting framework.jar .
On the related note, would you care to provide exact instructions how to make framework.jar with c&p functionality? That would help to keep it updated across vendor upgrades, and also for making sure that new framework.jar contains only changes related to c&p and nothing else ;-). Granted, such instructions would be long and boring, so writing them in the shell script language rather than English would be a good idea ;-).
pfalcon said:
Cool hack, but why all these doubts and asks for 16gb's framework.jar ? What users have on devices comes from vendor firmware package(s), and you can see at http://www.barnesandnoble.com/u/Software-Updates-NOOK-Tablet/379003187/ that there's no separate versions for 8gb vs 16gb. That page (and pages for other releases) should be also the authoritative place for getting framework.jar .
Click to expand...
Click to collapse
Thanks for the link! I went and downloaded the update archive and extracted it, and can confirm that the /system/framework/framework.jar in that archive (which I'd assume is the same as on the NT 16GB/1.4.2) is different from the same file on my NT 8GB/1.4.2., which confirms my hypothesis in posts #11 and #14 in http://forum.xda-developers.com/showthread.php?t=1517513&page=2. The bizarre thing is that if you unzip the files they produce the exact same content; it looks like they differ only in some sort of signature. But this means that my framework.jar will work on both the 8GB and 16GB on 1.4.2. So thanks again for the link!
pfalcon said:
On the related note, would you care to provide exact instructions how to make framework.jar with c&p functionality? That would help to keep it updated across vendor upgrades, and also for making sure that new framework.jar contains only changes related to c&p and nothing else ;-). Granted, such instructions would be long and boring, so writing them in the shell script language rather than English would be a good idea ;-).
Click to expand...
Click to collapse
What I did was this. You need zip, unzip and a tool called apktool. I'm assuming the framework.jar from the Nook is called ~/framework.jar.nook and the framework.jar from vanilla Android (AOSP) is ~/framework.jar.aosp.
1. Extract framework.jar into a directory z:
Code:
$ unzip framework.jar -d z
2. Use apktool to disassemble framework.jar.nook:
Code:
$ apktool d ~/framework.jar.nook
3. Disassemble framework.jar from AOSP.
Code:
$ apktool d ~/framework.jar.aosp
4. Compare and modify framework.jar.nook.out/smali/android/widget/{TextView,EditText}.smali against framework.jar.aosp.out/smali/android/widget/{TextView,EditText}.smali. My diff file can be downloaded here. Apply diff with
Code:
$ cd framework.jar.nook.out; patch -Np1 < jichuan89_nook_text_hack.diff; cd ..
5. Recompile Nook's framework.jar:
Code:
$ apktool b framework.jar.nook.out
6. Repackage modified Nook's framework.jar into ~/framework.jar.new
Code:
$ cp framework.jar.nook.out/build/apk/classes.dex z/classes.dex
$ cd z; zip -r ~/framework.jar.new META-INF classes.dex preloaded-classes; cd ..
framework.jar in that archive (which I'd assume is the same as on the NT 16GB/1.4.2) is different from the same file on my NT 8GB/1.4.2
Click to expand...
Click to collapse
I just tried to compare framework.jar I have on my device after 1.4.2 OTA update vs downloaded from B&N site - they turned out to be the same, md5sum is 795ae49e2b05b05c999a424a7d84b36b. Anyway, good news that contents were the same in your case too. It might be that 8Gb's initial in-flash 1.4.2 indeed was packaged differently than 16Gb's 1.4.2 update (that's idea somehow backed by the fact that 16Gb's initial in-flash 1.4.0 is not available on B&N site). Again, good to know that actual contents are the same, so 1.4.3 would be common either (which makes full sense, otherwise B&N just makes it harder on themselves).
What I did was this.
Click to expand...
Click to collapse
Thanks for the instructions and the diff! I with that all hacks posted on the forum came in such form ;-)
pfalcon said:
I just tried to compare framework.jar I have on my device after 1.4.2 OTA update vs downloaded from B&N site - they turned out to be the same, md5sum is 795ae49e2b05b05c999a424a7d84b36b.
Click to expand...
Click to collapse
Nice - thanks for confirming this. That's really helpful to know.
pfalcon said:
It might be that 8Gb's initial in-flash 1.4.2 indeed was packaged differently than 16Gb's 1.4.2 update (that's idea somehow backed by the fact that 16Gb's initial in-flash 1.4.0 is not available on B&N site). Again, good to know that actual contents are the same, so 1.4.3 would be common either (which makes full sense, otherwise B&N just makes it harder on themselves).
Click to expand...
Click to collapse
Right - it would make economic sense for B&N to make the software on the two tablet models to be as close as possible. I do hope they'll make their and our lives easier by just using the same version of the same damn files in the next update for the two models, as you said.
Sent from my Nook Tablet using XDA
I can make CWM flashable zip with original framework.jar for the ones having troubles until is fully tested. Tomorrow i'll jump back to stock 1.4.0 to test this hack and report back.
~ Veronica
A flashable zip would be cool if for no other reason than simplicity and reduced panic on the part of newcomers and when re-flashing the stock ROM.
I'm going to try this, so with me luck, but first: Do I need to boot into CWM to do this?
CRE said:
A flashable zip would be cool if for no other reason than simplicity and reduced panic on the part of newcomers and when re-flashing the stock ROM.
I'm going to try this, so with me luck, but first: Do I need to boot into CWM to do this?
Click to expand...
Click to collapse
No - this is for the stock firmware. CWM should have copy & paste already because it doesn't use B & N's framework.jar.
CWM as in ClockWorkMod not CM7 as in CyanogenMod v7.
EDIT:
To clarify, I didn't know if I could do this while the NT was booted normally or if I needed to boot with ClockWorkMod to ensure that the OS didn't try to access that file.
CRE said:
CWM as in ClockWorkMod not CM7 as in CyanogenMod v7.
EDIT:
To clarify, I didn't know if I could do this while the NT was booted normally or if I needed to boot with ClockWorkMod to ensure that the OS didn't try to access that file.
Click to expand...
Click to collapse
No. If there were requirements I would have put them in the instructions. It doesn't matter how you boot.
Sent from my Nook Tablet using XDA
Thank you. I guess I'll repartition first then get this out of the way too.
Hi
I am currently running the latest cm 10.2 nightlies. Before when using the 10.1 nightlies I used this mod to swap the internal and external sd cards.
The mod made a simple modification to the vold.fstab, and worked well.
However with the change to 10.2 and 4.3 I discovered this no longer worked, the reasons for this are to due to changes google made (listed here). I have tried making edits to the new fstab.smdk4210 file, but they don't seem to stick and I have yet to succeed at swapping the cards.
Can anyone provide help or suggestions on this matter?
Thanks
Force. said:
Hi
I am currently running the latest cm 10.2 nightlies. Before when using the 10.1 nightlies I used this mod to swap the internal and external sd cards.
The mod made a simple modification to the vold.fstab, and worked well.
However with the change to 10.2 and 4.3 I discovered this no longer worked, the reasons for this are to due to changes google made (listed here). I have tried making edits to the new fstab.smdk4210 file, but they don't seem to stick and I have yet to succeed at swapping the cards.
Can anyone provide help or suggestions on this matter?
Thanks
Click to expand...
Click to collapse
+1, even I am looking for the same thing and wants to workout. I cannot keep my stuff on the internal memory, I have a 32 GB SD card, more then enough to enjoy without problems.
+1 looking for same , this is the only thing holding me back from upgrading to 4.3.
where is the fstab.smdk4210 file located? i'll take a look and have a go at modifying it
alkspo said:
+1 looking for same , this is the only thing holding me back from upgrading to 4.3.
where is the fstab.smdk4210 file located? i'll take a look and have a go at modifying it
Click to expand...
Click to collapse
The file is located in the system root.
Found Solution
Props to honeyx for the solution, found here.
To swap SDCards
edit build.prob (found in /system) and add:
Code:
# Change to 1 for swapping SD cards
persist.sys.vold.switchexternal=1
below
Code:
# Storage configuration
ro.vold.switchablepair=/storage/sdcard0,/storage/sdcard1
This modification will probably revert after every nightly flash, so I am looking into making a flashable zip that will make the modification each time, I don't have a lot of experience with this so if anyone else wants to make one and share it that would be welcome.
EDIT: Ok I have made a flashable zip, it seems to do the trick. However you flash it at your own risk. It is designed only for cm10.2, and as it works by replacing the build.prop it might cause problems if the build.prop is edited in later nightlies.
The md5 hash for the zip is:
Code:
02f299cf38442d18338e56856fdcd0d0
Works great, mate. Tanks!
samukinson said:
Works great, mate. Tanks!
Click to expand...
Click to collapse
No problem. But like I said the zip is a bit experimental so be careful.
Force. said:
Props to honeyx for the solution, found here.
To swap SDCards
edit build.prob (found in /system) and add:
Code:
# Change to 1 for swapping SD cards
persist.sys.vold.switchexternal=1
below
Code:
# Storage configuration
ro.vold.switchablepair=/storage/sdcard0,/storage/sdcard1
This modification will probably revert after every nightly flash, so I am looking into making a flashable zip that will make the modification each time, I don't have a lot of experience with this so if anyone else wants to make one and share it that would be welcome.
EDIT: Ok I have made a flashable zip, it seems to do the trick. However you flash it at your own risk. It is designed only for cm10.2, and as it works by replacing the build.prop it might cause problems if the build.prop is edited in later nightlies.
The md5 hash for the zip is:
Code:
02f299cf38442d18338e56856fdcd0d0
Click to expand...
Click to collapse
This is what I was looking for.... Many thanks. Works flawless. I hope I won't need to flash it again after next nightly...
Force. said:
No problem. But like I said the zip is a bit experimental so be careful.
Click to expand...
Click to collapse
@Force.
could you please make a zip like that for CM10.2 xperia go?
I give you the build.prop of xperia go CM10.2
I was looking for this, but for i9100G cm10.2 and i9100G stock 4.1.2
Anyone can help doing it?
Sent from my GT-I9100G using xda app-developers app
Force. said:
No problem. But like I said the zip is a bit experimental so be careful.
Click to expand...
Click to collapse
thankss bro i was search about 3day and i found it the solution here nice work
Works Great
Force. said:
Props to honeyx for the solution, found here.
To swap SDCards
edit build.prob (found in /system) and add:
Code:
# Change to 1 for swapping SD cards
persist.sys.vold.switchexternal=1
below
Code:
# Storage configuration
ro.vold.switchablepair=/storage/sdcard0,/storage/sdcard1
This modification will probably revert after every nightly flash, so I am looking into making a flashable zip that will make the modification each time, I don't have a lot of experience with this so if anyone else wants to make one and share it that would be welcome.
EDIT: Ok I have made a flashable zip, it seems to do the trick. However you flash it at your own risk. It is designed only for cm10.2, and as it works by replacing the build.prop it might cause problems if the build.prop is edited in later nightlies.
The md5 hash for the zip is:
Code:
02f299cf38442d18338e56856fdcd0d0
Click to expand...
Click to collapse
Thanks for this info. I, similar to others, have been searching for this for a couple days now. It works great.
Just FYI for those who don't have these options in your build.prop, you can just add them in (I added them above additional properties, you have to add both switchablepair and switchexternal lines, the comments don't hurt either)
has anyone got this method working with SGS3 i9300 or i9305 on cm 10.2 as I have tried various methods so far and none work.
been scouring internet for weeks no working method yet
Does it work with the ace 2
Paranoid rookie
dwhite1972 said:
Does it work with the ace 2
Paranoid rookie
Click to expand...
Click to collapse
Tried it phones sorta just a black screen possible bricked
I9070
Hey.
I own a Samsung Galaxy S Advance (10.2 cm janice)
I need to set the external SD card as an internal storage.
Could you write me what to rewrite everything to make it work correctly?
Looking for a long time, but I can not find anything.
If anyone had done zip file with the modified file vold. , I would be very happy.
Sorry for the font, but it is Google Translate.
thank you
You cannot flash this on other devices, This zip flashes a different build.prop. So your device will have identity problems
You can do this yourself on other cm10.2 devices by using a root file explorer. go to /system, open build.prop with a root text editor (otherwise, copy it to sdcard, edit it and copy it back to /system). And add the 4 lines to build.prop.
I have tried this with cm10.2 on xcover 2. It surely did something, at least more than other things I tried, but it is not working correctly yet. com.android.media-something is forced closed and the external sd is shown as non mounted.
Force. said:
Props to honeyx for the solution, found here.
To swap SDCards
edit build.prob (found in /system) and add:
Code:
# Change to 1 for swapping SD cards
persist.sys.vold.switchexternal=1
below
Code:
# Storage configuration
ro.vold.switchablepair=/storage/sdcard0,/storage/sdcard1
This modification will probably revert after every nightly flash, so I am looking into making a flashable zip that will make the modification each time, I don't have a lot of experience with this so if anyone else wants to make one and share it that would be welcome.
EDIT: Ok I have made a flashable zip, it seems to do the trick. However you flash it at your own risk. It is designed only for cm10.2, and as it works by replacing the build.prop it might cause problems if the build.prop is edited in later nightlies.
The md5 hash for the zip is:
Code:
02f299cf38442d18338e56856fdcd0d0
Click to expand...
Click to collapse
I thought that would swapping with the date 2gb partition. This 2gb partition is causing me problems to install apps. Could you please do a file back to the default?