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..
I've created an app for dual booting automatically to Android or WM6. V2.3.2 can boot multiple version of Android on a single SD card and can be customized for text content and language. See post #2 for documentation and screenshots.
The "lite" version is a replacement for using a file explorer to run CLRCAD then HaRET, allowing Android to be started with a single tap on an icon. To install the lite version, simply un-RAR the contents to your Android folder then use a file explorer to create a Start Menu shortcut.
Please leave feedback and suggestions/questions.
French translation:http://forum.xda-developers.com/showpost.php?p=13123392&postcount=151
Documentation and Screenshots
RunDroid app v2.3.2 for HTC HD2 by Pop45398 (@ XDA Developers)
This app can start Android on an SD card automatically on boot-up or with a single tap, thus allowing for an easy dual boot to Android or Windows Mobile, and should be compatible with all versions run with CLRCAD/HaRET. It features a setup menu which allows for user customization including setting the timeout before the default OS is started, thus allowing time to access the setup menu or select a non-default OS. It is actually a MortScript and corresponding MortRunner with a custom icon. It may work on other WM6 devices.
CHANGES:
Version 2.3.2 added a new subroutine to rename the Android folder back to its original name when “Enable Builds” is selected if RunDroid had renamed the folder to Android. This eliminates the folder being renamed to Android[1]. (Thanks to crazycranky!)
Version 2.3.1 features language/text customization. By editing RunDroid.ini with a text editor the user can now change all text for desired content and language (with exception of button text, i.e. Ok/Cancel, Yes/No). There is no longer a need to edit the script for non-English ROMs where the SD card is not called “Storage Card”, a directory tree will appear for the user to locate the SD card’s root.
Version 2.2.1 features some minor changes over v2.1.1. A StartUp shortcut is no longer used for auto-launching at boot-up, instead it is launched during the init process before StartUp programs, hence the elimination of creating and deleting shortcuts from the Setup Menu. A new option to Enable Sense has been added so that Sense can be easily re-enabled if somehow not properly re-enabled during script execution. A setup.dll is now used to run Install and Uninstall scripts.
Version 2.1.1 represents a major overhaul from version 1 and features the ability to boot to a basically unlimited number of Android builds and a guided setup that walks through the setup process on initial running. It will scan all folders in the SD card's root for Android builds, indicated by the presence of HaRET.exe. It asks whether to use each build then asks if it requires renaming the folder to Android in order to run (some builds don't require being in the Android folder). A .cab file is used for installation which is now in the RunDroid folder in the root of the device. The folder name is used for displaying the build's name in RunDroid, with one caveat: if there is more than one build and one of them is named Android, that folder will be renamed to Android[1] so that the selected build folder can be renamed to Android (which is renamed back to original when another build is selected), hence descriptive folder names should be used.
INSTALLATION:
Simply copy the .cab file to the SD card and run it with a file explorer to install. Version 2.3.1 MUST be installed to the device due to hard coded addresses required for auto-launching. This also eliminates the occasional possibility of the SD card not being initialized before RunDroid is started during boot-up. If during installation the SD card is not found by the default name “Storage Card” (usually due to a non-English ROM) a directory tree will appear for choosing the correct SD card root, not Android folder (see screenshots below for an example).
OPERATION:
Start RunDroid with the Start Menu icon. On initial running, a guided setup will walk through the settings. Menus are self-explanatory (see screenshots). Selection is done by double-tapping an entry or tapping once then tapping OK. Only the main (Boot Selection) menu is timed for auto-selecting. If auto-running at boot-up is NOT desired, select “Disable AutoStart” during initial setup or later from the Setup Menu. The Timeout Delay may be adjusted to suit the user and system (see ISSUES section below). Whenever another build is added or deleted, one is no longer desired to be run, or a folder name changed, Enable Builds must be selected from the setup menu which will once again walk through the setup of builds and default OS selection (but not other settings). Builds are displayed in alphabetical order and can only be rearranged by renaming folders, like by adding a number at the beginning of folder names.
ISSUES:
Startup programs, including HTC Sense and Notifications, etc, can briefly interfere with the ability to make selections, causing the default OS to be started before menu selections can be made. To combat this, if enabled and not already started, Sense is disabled then re-enabled on app exit. The Timeout can be adjusted to help with this. If the Timeout is set too low and selecting the Setup Menu or Boot to Windows is not possible, simply re-install the .cab. If unable to boot to Windows because Android starts before the menu appears, power off the device, remove the SD card, then power on the device; if not already at the menu, start RunDroid and go to the Setup Menu and adjust the Timeout to allow more time to access the menu, then power down and re-insert the SD card.
CUSTOMIZATION:
The user interface can be customized for text size, font type, language, and size of menu selection entries by editing RunDroid.ini with a (pure text) editor such as Notepad. Once RunDroid is installed, locate the .ini file in the RunDroid folder in the root of the device (not SD card) and open or copy to PC then open.
The following variables control the font and size of menu entries:
FontSize=23
EntryScale=1.3
FontType=Tahoma
Increase or decrease FontSize to make menu selection text larger or smaller. EntryScale controls the size of menu selections, larger size makes selections easier to make. The scale is in percentage of the font size, i.e. 1.3 equals 130% of the font size. To use a different FontType than Tahoma, the desired font must be installed on the device.
In addition to descriptive variable names, to make RunDroid.ini easier for editing text content and language certain conventions are used:
Variables containing “Sel” are for menu selection entries.
......WMsystemSel=Windows Mobile
Variables Containing “Hint” are for the text that appears in the upper portion. Note that “Setup Menu” is preceded by a period and several spaces. The spaces are to center the text; the period is required because leading spaces will otherwise be ignored and the text will begin on the left instead of centered.
......SetupMenuHint=. Setup Menu
Variables containing “Txt” are for messages and questions which pop-up in new windows.
......NoBuildsMessTxt=There were no Android builds using HaRET.exe found on this SD card.
Do not change the actual variable names, for example “TimeoutMessHint=”, only the text following the “=” sign as these names are hard coded into the script and the new text will not appear.
Editing prior to completing the initial setup is preferred. Once editing is complete, copy the modified file to \RunDroid, overwriting the original. A copy of the modified RunDroid.ini file should be saved somewhere besides \RunDroid because if RunDroid is reinstalled or a newer version installed the entire folder will be deleted along with the modified file. Once reinstalled, copy the modified file to \RunDroid before completing the initial setup.
Let me try.
Works Great!
Thanks
shadowburt said:
Works Great!
Thanks
Click to expand...
Click to collapse
78 downloads (and another dozen in another thread) and finally some feedback, was beginning to wonder if it only works for me. Am glad it works for you.
My original intent was just to make a script that runs CLRCAD then HaRET by simply tapping an icon on the Start Menu instead of using a file explorer to run them separately like the chefs all say. That is what the "lite" version does. I then remembered I had routines in other scripts I'd written a few years ago that could be used to spice it up.
Hi, I´m gonna try it i a minute - sounds goode - thank you!!!
pronor
Is there interest in RunDroid having the ability to select different Android builds from the same SD card? If enough interest I can do this but because most builds require being located in the Android folder a small .ini file will be required in each build folder so that folders can be renamed then renamed back when a different build is selected. Sorry, I can't edit the original post to make it a poll so you will have to post your interest in this mod.
Pop45398 said:
Is there interest in RunDroid having the ability to select different Android builds from the same SD card? If enough interest I can do this but because most builds require being located in the Android folder a small .ini file will be required in each build folder so that folders can be renamed then renamed back when a different build is selected. Sorry, I can't edit the original post to make it a poll so you will have to post your interest in this mod.
Click to expand...
Click to collapse
Hooo man i want this +1
Pop45398 said:
Is there interest in RunDroid having the ability to select different Android builds from the same SD card? If enough interest I can do this but because most builds require being located in the Android folder a small .ini file will be required in each build folder so that folders can be renamed then renamed back when a different build is selected. Sorry, I can't edit the original post to make it a poll so you will have to post your interest in this mod.
Click to expand...
Click to collapse
That would be awsome!!!
New version
yesucan said:
Hooo man i want this +1
Click to expand...
Click to collapse
palmbluetooth said:
That would be awsome!!!
Click to expand...
Click to collapse
I've PMd y'all a download link for v2.01. The new version represents a major overhaul from v1.02 and features the ability to boot to an unlimited number of Android builds and a guided setup that walks through the process on initial running. It will scan all folders in the SD card's root for Android builds, indicated by the presence of HaRET.exe, then ask whether to use that build, then ask if it requires renaming the folder to Android to run (some builds don't require being in the Android folder). A .cab file is used for installation which is now in the RunDroid folder (when installing, be sure to select Storage Card) . The folder name is used for displaying the build's name in RunDroid, with one caveat: if there is more than one build and one of them is named Android, that folder will be renamed to Android[1] so that the selected build folder can be renamed to Android (which is renamed back to original when another build is selected). Whenever another build is added/deleted, one no longer desired to run, or folder named changed (in this case the Droid.ini file in that folder should be deleted), Enable Builds must be selected from the setup menu which will once again walk through the initial setup of builds (but not other settings).
I've tried every combination I could think of and the folder renaming process seems to work fine. Please post if you find any issues.
PS> Order of build appearance is by alphabetical order and can only be rearranged by renaming folders, for example by placing a number at the beginning of the folder name; however, more than 1-9 will screw that up because 10 will appear before 2, etc.
Pop45398 said:
I've PMd y'all a download link for v2.01. The new version represents a major overhaul from v1.02 and features the ability to boot to an unlimited number of Android builds and a guided setup that walks through the process on initial running. It will scan all folders in the SD card's root for Android builds, indicated by the presence of HaRET.exe, then ask whether to use that build, then ask if it requires renaming the folder to Android to run (some builds don't require being in the Android folder). A .cab file is used for installation which is now in the RunDroid folder (when installing, be sure to select Storage Card) . The folder name is used for displaying the build's name in RunDroid, with one caveat: if there is more than one build and one of them is named Android, that folder will be renamed to Android[1] so that the selected build folder can be renamed to Android (which is renamed back to original when another build is selected). Whenever another build is added/deleted, one no longer desired to run, or folder named changed (in this case the Droid.ini file in that folder should be deleted), Enable Builds must be selected from the setup menu which will once again walk through the initial setup of builds (but not other settings).
I've tried every combination I could think of and the folder renaming process seems to work fine. Please post if you find any issues.
PS> Order of build appearance is by alphabetical order and can only be rearranged by renaming folders, for example by placing a number at the beginning of the folder name; however, more than 1-9 will screw that up because 10 will appear before 2, etc.
Click to expand...
Click to collapse
Thanks man . will try it out ..
Hello,
Is it possible to have the link to download the latest release?
Thank you
tristano said:
Hello,
Is it possible to have the link to download the latest release?
Thank you
Click to expand...
Click to collapse
Sent you a PM.
Thank you.
Downloading.
Gonna try it
Pop45398 said:
Sent you a PM.
Click to expand...
Click to collapse
Can you please post the download link for v2.01? Thanks.
would like to try it out mate....
thanks
Could I have the link also pls ) to the latest version
Thanks)
I got problem when i install the 2.0.1 version follow the instruction . After doing set up press yes to all folder but i don't see the Android folder in the main screen only window . Reinstall delete RUNDROID folder still the some . thanks.
yesucan said:
I got problem when i install the 2.0.1 version follow the instruction . After doing set up press yes to all folder but i don't see the Android folder in the main screen only window . Reinstall delete RUNDROID folder still the some . thanks.
Click to expand...
Click to collapse
After install was there a RunDroid folder in the root of your SD card? When running the .cab file you must select to install to Storage Card, not to the Device which is the default when installing cabs. It's best if you don't have an Android folder to start with. Each build should have a meaningful name which will be renamed to Android if required, however the original name will appear in the menu, not Android. I found a problem when reinstalling because of the Droid.ini files that were created on the first install but don't think that is your problem. I have now fixed v2.02 to delete all Droid.ini files whenever a setup of builds is done, whether on initial setup or when Enable builds is selected from the setup menu. Sent PM with new link.
Pop45398 said:
After install was there a RunDroid folder in the root of your SD card? When running the .cab file you must select to install to Storage Card, not to the Device which is the default when installing cabs. It's best if you don't have an Android folder to start with. Each build should have a meaningful name which will be renamed to Android if required, however the original name will appear in the menu, not Android. I found a problem when reinstalling because of the Droid.ini files that were created on the first install but don't think that is your problem. I have now fixed v2.02 to delete all Droid.ini files whenever a setup of builds is done, whether on initial setup or when Enable builds is selected from the setup menu. Sent PM with new link.
Click to expand...
Click to collapse
Thanks man ,will try out now .And give feedback . Will hit the thanks button tomorrow. Finish used already .
Edit: It works ! thanks .
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!
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.
Hi guys and girls,
I lost track of what ROM version my Nandroids are containing. I use to add the ROM version to the original file name but I couldn't do it lately.
Is there an easy way to check which ROM version a Nandroid contains?
I am posting this in the general Android forum because my question surely isn't device-specific.
I own a Motorola Defy+ and I'm running CM 7.2 at the moment but tried JellyBean lately.
Thanks!
eTaurus
Make a text file list and keep it in your /clockworkmod/backup folder. Just copy and paste the new backup folder name/date in to the text file and write a small description.
Mine's called Appendix.txt and has everything from GB to CM10. I keep a copy on my sdcard and comp - only thing is you can't read that list in cwm recovery, so you have to have an idea of what's what before you go to restore.
Sent from my phone's mind
Thank you for answering.
Your solution is as good as mine as I rename the backup folder by adding the ROM and the release date to its name. But I did some Nandroids lately without having time to rename the folder and now I don't recall what version the Nandroid contains.
I came to a "solution" by using the app "Nandroid browser". With it I can look into the files the Nandroid contains. There is an app called "HwaSettings.apk" so it has to be JellyBean because CM 7.2 doesn't have hardware acceleration.
Cheers,
eTaurus