Related
Problem: Changes to the system partition are lost when Linux flushes the disk cache: http://pastebin.com/cm75Z9UA
These instructions are a workaround to provide temp root like normal plus persistence because /system /data and /cache are partitions on your SD card. This lets you reboot and even factory reset, while being able to easily restore your settings and such by re-rooting and mounting your SD card partitions back over the internal partitions.
Prerequisites:
SD card partitioned with four partitions:
6GB as fat (for your data, can be bigger or small depending on your card size)
400MB ext3 for /system
1.3GB ext3 for /data
200MB ext3 for /cache
On the phone, enable "USB debugging" in Menu -> Settings -> Applications -> Development
On a PC with the Android SDK tools (adb) installed and working:
adb push Superuser.apk /data/local
adb push busybox /data/local
adb push rage /data/local
adb push resume /data/local
adb push root /data/local
adb push rsync /data/local
adb push setup /data/local
adb push su /data/local
adb install Term.apk
adb shell chmod 755 /data/local/busybox /data/local/rage /data/local/setup /data/local/resume /data/local/rsync /data/local/root
On the phone, open "Terminal Emulator" and type:
/data/local/rage
Wait for it to say "[+] Forked NNNN childs." then press the back button.
Open "Terminal Emulator" again and it should force close.
Open it one more time and the prompt should display "#". Then type:
/data/local/root
/data/local/setup
You may need to re-root after it reloads the GUI, but then it will stick. setup is a script that mounts your SD card partitions and copies the existing. It should only be run once unless you want to erase what you have there previously. This step wont work if you SD card is not partitioned properly.
On future power-ons, run this after temp-root instead of setup:
/data/local/resume
and you should get your Android back how it was.
is it suppose to scan through all apps on phone then reboot
Thanks muchly, I'll try this when my G2 arrives.
I have a question about this method. It looks to me that what setup does is copy the entire system, data, and cache to the SD card. Then, when you run resume, it uses rsync to bring the main system (in the onboard flash) up to date from the SDcard version, and then any changes, even if not actually written to the main system partition due to the HTC copy protection, get written to the sdcard copy of the system. Very clever (if I'm reading this write, otherwise, still clever, but me not so clever as I mis-understood).
The question is this: Are there any glitches or instabilities generated by suddenly changing the system files after the OS is already booted? Do I have to make sure to do this before I begin using my phone after boot or risk making changes that I will then loose when I run resume?
Thanks again for the work putting this together!
Sheep
Sheep, you understand almost completely. Setup does copy the existing data from the internal phone memory to the SD card. However, it then (like resume) doesn't copy anything back, it just mounts the system, data, and cache partitions from the SD card on top of the internal ones.
I had issues with the internal memory reverting back after I make changes to it. It seemed to happen over a short time, or was triggered by things like mounting the SD card to a computer.
I've been using this for about 24 hours with no problems. I've done a couple fresh boots and ran resume. But I didn't test the instructions from scratch, so if anyone tests and finds a problem, let me know!
Any performance hit because of running from SD?
I haven't really noticed any.
How does this impact battery life?
Sent from my T-Mobile G2 using XDA App
Can't say, I've had my phone hooked up most of the time through adb looking for root. Just did this for fun and because I was sick of re-rooting all the time.
looks interesting I'll try it out tomorrow
Sent from my T-Mobile G2
so your sd card has to be partitioned pryor to trying this
pre-partitioned card?
thatruth132 said:
so your sd card has to be partitioned pryor to trying this
Click to expand...
Click to collapse
yes it does
texasaggie1 said:
yes it does
Click to expand...
Click to collapse
and how do i do this on a non-rooted device
thatruth132 said:
and how do i do this on a non-rooted device
Click to expand...
Click to collapse
Use your G1 to partition the card.
Brad
You can also connect your phone to a Linux computer (a LiveCD would be fine) and use gparted or fdisk. Don't forget to backup the contents of your card first!
Pretty cool. But I think I'm gonna wait for a more permanent solution....
sheek360 said:
Pretty cool. But I think I'm gonna wait for a more permanent solution....
Click to expand...
Click to collapse
There are no roms available yet any ways, so to a non dev, non cook like me, the Root is pretty much useless
I'd read that the currently available root was good until a reboot, then I saw this thread that made rerooting after a reboot much easier. Since then I've seen some posts that seem to indicate that a root may spontaneously disappear even without rebooting. Is this the case, some permissions may be lost even if you don't reboot?
I was ready to pull the trigger on this permanent-temporary root until I read that. I'd like to be able to import my old wpa_supplicant.conf file and get my corp ipsec vpn working. I'd also like to be able to get wifi-tether working (although I rarely use it), but if root won't stay 100% until a reboot, then I'm not going to bother.
Dalamak said:
There are no roms available yet any ways, so to a non dev, non cook like me, the Root is pretty much useless
Click to expand...
Click to collapse
Not true. I'm not a dev or a cook, but there are things that you can make the phone do with root besides adding a theme or ROM.
wifi tether
ipsec vpn
backups
etc...
smasraum said:
I'd read that the currently available root was good until a reboot, then I saw this thread that made rerooting after a reboot much easier. Since then I've seen some posts that seem to indicate that a root may spontaneously disappear even without rebooting. Is this the case, some permissions may be lost even if you don't reboot?
I was ready to pull the trigger on this permanent-temporary root until I read that. I'd like to be able to import my old wpa_supplicant.conf file and get my corp ipsec vpn working. I'd also like to be able to get wifi-tether working (although I rarely use it), but if root won't stay 100% until a reboot, then I'm not going to bother.
Click to expand...
Click to collapse
With temp root on the internal system partition, writes would revert back after certain things (after mounting the sd card to a computer through the phone and disconnecting it, I'd always loose root). When running /system from an sd card, no writes can be reverted because none are made, so I've never had to re-root.
how to partition an SD card?
thatruth132 said:
and how do i do this on a non-rooted device
Click to expand...
Click to collapse
I used gparted in ubuntu to do mine. Like SAINTH said, the install disk for ubuntu is also a livecd so you dont even have to install ubuntu if u dont want to
So, I rooted my phone last night, and now I'm running into some slight "permission denied" issues.
In particular:
"File Access Problem Caution, unable to write files. This means your game progress can't be saved! Reason: Access to the path "/mnt/sdcard/Android/data/com.imangi.templerun/files/spaceholder.dat" is denied."
So, I jump onto the phone with adb shell, su, head down to that directory, and can't see anything wrong with permissions. However, I *also* can't create a file in there from the command line...
sh: cannot create test: Permission denied
any thoughts on how to fix this?
Thanks.
-Kevin
Ouch
actually, its even worse...
I can't take pictures...it seems the camera app doesn't have "write" permissions to the DCIM folder, or something.
If I go to the folder, and rename it DCIMold, then take a photo, the new DCIM folder gets created, and the photo is fine...
but there are *NO* differences in file permissions between DCIMold and DCIM.
Anyone?
solution
For anyone that finds this...
here is the solution:
http://forum.xda-developers.com/showthread.php?t=1691097
Same problem
Hello. I have a problem with my motorola defy+ running on gb 2.3.6 and is not ROOTED. Still he has an annoyng problem. After installing an aplication (not from the market) i saw that it didn't save data on the sd card. I uninstalled it and after a data factory reset i install apps such as temple run and Brother in Arms 2. At temple run it gave me this mesage
"File Access Problem Caution, unable to write files. This means your game progress can't be saved! Reason: Access to the path "/mnt/sdcard/Android/data/com.imangi.templerun/files/spaceholder.dat" is denied."
Also at Brother in Arms 2 the game didn't save. I rest the phone abouat 7-8 times.I changed the sd card. Note that the card was a 16 gb kingmax class 6 and put the 2 gb card that came with the phone. It all work smoothly. So what is the problem the sd card or the phone's software. Please answer i'm desparate and tired of wasting time.
This is a graphical, interactive rooting system with the ability to create/restore backups and factory settings.
This has been tested on systems 1.1.5, 1.2.0 (US/UK), and 1.2.1. It will probably work on earlier versions and should be safe to use on future versions. For best results, however, you should be on 1.2.1 before using this tool.
If you've tried rooting your nook unsuccessfully with another utility, it's best to do a factory restore (from NookManager, choose the "Rescue" option and then "Restore factory.zip") and, if your nook came with older firmware, upgrade to the latest 1.2.1 firmware.
Features:
Root your Nook
Backup/Restore
Restore to factory settings
Disable B&N Apps
Custom plugins
How to root:
1. Download NookManager.
2. Unzip the file you downloaded and write the NookManager.img file to an empty SD card. On Windows, you can use disk imager. Linux and mac users can use dd.
Use a real SD card adapter when writing the image, DO NOT USE YOUR NOOK AS THE SDCARD ADAPTER.
If possible, you should use a dedicated SD card for the NookManager image (so you can easily restore from a backup should you ever screw up your Nook). A 512Mb card is big enough for the NookManager image plus a backup of your Nook.
3. Power off your Nook, insert the SD card and power on.
You should see the NookManager boot screen followed within 15 seconds by the welcome screen.
4. Choose "No, continue without wireless"
the wireless option is for advanced users looking to connect directly to their device
5. Make a backup using NookManager! Choose "Rescue" then "Backup" then "Format remaining space on SD card" and finally "Create backup"
Because NookManager cleans the empty space on the Nooks' internal partitions and compresses the backup, it will take at least 15 minutes (and up to 45 minutes) for the backup to complete. Be patient. The final backup file can be as small as only be a few hundred megabytes, depending on the number of downloaded or sideloaded books you have.
6. Copy the backup image to your computer. Connect your Nook to your computer using the USB cable. Copy the 'backup.full.tgz' and 'backup.full.md5' files from the NookBackup drive to your computer.
This is your backup in case anything happens to your SD card. This backup is tied to your individual Nook so keep it safe. It's important to copy this file while your Nook is still booted from the SD card because Windows will normally hide the NookBackup partition on the SD card. If you ever need access to the NookBackup partition again, just boot your Nook using the NookManager SD card and connect the Nook to your computer with the USB cable.
7. Root! After your backup, press "Back" and "Back" to return to the Main Menu. Press "Root" and then "Root my device"
8. That's it! After rooting, pres "Back" and then "Exit". Remove the SD card and put it someplace safe, in case you need to restore to your backup later.
After rooting, you can install Google Apps using straygecko's excellent NTGAppsAttack package if you want to use Google Market/Gmail/Calendar/etc.
[/LIST]
Technical stuff:
The actual rooting function is minimal and as non-invasive as possible:
uRamdisk is patched to enable ADB
the internal database setting is changed to allow installation of non-market apps
the DroidSansFallback font is replaced with the updated font from jellybean to add support for extended characters
the su/Superuser binary/package is installed
Relaunch is installed
ADB Konnect is installed for enabling/disabling ADB over wireless
on systems running firmware 1.2+, the ModManager jars and package are installed
on 1.2+ systems, the PackageInstaller.apk from the 1.1.2 firmware is installed to resolve issues with package installers
and, finally, the Amazon appstore is installed just to have some easy way of downloading new apps. You can uninstall it using ReLaunch if you don't use it.
The uRamdisk patching is done with scripts rather than copying pre-compiled binaries, so this should be safe for all existing versions of the Nook firmware and (hopefully) will be forward compatible with any new releases.
The rooting procedure is non-destructive and can be run multiple times without causing problems.
Under the hood, this is a minimal linux environment with the nook drivers/binaries and a few core android binaries. The display is generated with imagemagick and written directly to the framebuffer.
If you're connecting to NookManager wirelessly over SSH, the username/password is root/root
Wherever possible, the parts of this system are compiled from source including the Linux kernel, uBoot, and all of the buildroot utilities. The hardware drivers and associated binaries are extracted from the 1.2.0 upgrade package.
The source for the project, including an automated buildscript is available at GitHub.
Support for custom menu items and scripts is documented here.
https://github.com/doozan/NookManager/downloads
NookManager.zip
17.9MB · Uploaded 14 hours ago
File was not found.
Click to expand...
Click to collapse
??
Weird. I deleted/re-upped the file and the download link seems to be working now.
ok..now it works. Thanks
Will this work with NoRefresh?
Thanks for the work on this - it was easy and worked great. And if you're planning to update, maybe add ES File Explorer or Titanium Backup in the pre-installed apps; that would make it easier to install apks directly from your SD card instead of having to do it over wireless adb. But thanks regardless.
Can confirm no refresh works great. Installed FBReader, Opera Mobile, ES File Explorer and Kindle app. Great
I just came from a firmware that had the ability to change the hardware buttons for page turning, any chance of this being added?
Thanks for this! Giving it a try.
Just curious though... I'm trying to create the backup of the device and it seems to take forever to format the free space. It also took forever to find the wireless network and I eventually just rebooted it. How long does it usually take?
I'm using a NST on 1.2.0 and have tried a 2GB Sandisk and a 8GB Dane-elec microsd card.
Gonna try redownloading and re-installing the image.
Install apk
Hi, i successfully root my NGL(1.2.0) but, if i try to install apk (Cool Reader) i got an error window "Out of space" and i'm almost sure it must be enough space to install, may someone can help with this ?
mobamoba said:
maybe add ES File Explorer or Titanium Backup in the pre-installed apps
Click to expand...
Click to collapse
Good suggestion, I've added ES File Explorer
Gvr4-330 said:
it seems to take forever to format the free space..and wifi
Click to expand...
Click to collapse
Thanks for reporting this. There was a glitch with the script that formats the SD card and with the wifi loading. Both issues have been fixed in the latest release.
asprin said:
if i try to install apk (Cool Reader) i got an error window "Out of space"
Click to expand...
Click to collapse
How are you trying to install the apk? I'm also using Cool Reader it installed with "adb install" and runs just fine. For best Nook compatibility, use coolreader 3.1.2-27 (12/11/2012 build) or later.
Originally Posted by asprin
if i try to install apk (Cool Reader) i got an error window "Out of space"
Click to expand...
Click to collapse
You get this error when you try to install application from an .apk file on sdcard or when you try to update application via it's built in updater.
ADB install works fine.
Good suggestion, I've added ES File Explorer
Click to expand...
Click to collapse
I use
Rhythm Software - File Manager
http://rhmsoft.com/?p=96
osowiecki said:
You get this error when you try to install application from an .apk file on sdcard or when you try to update
Click to expand...
Click to collapse
I'm not able to replicate this: I can copy coolreader to my sd card, and install it from there with no problems using ES File Explorer or ReLaunch. Maybe you really do have a disk space issue. Try openinng an adb shell and run "df -h" to see disk usage on your mounted partitions.
mobamoba said:
maybe add ES File Explorer
Click to expand...
Click to collapse
osowiecki said:
I use Rhythm Software - File Manager
Click to expand...
Click to collapse
It turns out you can install apks using the file browser in ReLaunch, so I'll be removing ES File Explorer in any future versions.
jeff_kz said:
I'm not able to replicate this: I can copy coolreader to my sd card, and install it from there with no problems using ES File Explorer or ReLaunch. Maybe you really do have a disk space issue. Try openinng an adb shell and run "df -h" to see disk usage on your mounted partitions.
It turns out you can install apks using the file browser in ReLaunch, so I'll be removing ES File Explorer in any future versions.
Click to expand...
Click to collapse
Thx for respond, mate, I tried install with file browser in ReLaunch from sd card, and i cant imagine that can be space issue cause i just start procedure after factory reset and rooting, anyway, thanks for tip, will try tomorrow install new build, and adb install. In general great work you did :good:
jeff_kz said:
I'm not able to replicate this: I can copy coolreader to my sd card, and install it from there with no problems using ES File Explorer or ReLaunch. Maybe you really do have a disk space issue. Try openinng an adb shell and run "df -h" to see disk usage on your mounted partitions.
It turns out you can install apks using the file browser in ReLaunch, so I'll be removing ES File Explorer in any future versions.
Click to expand...
Click to collapse
df :
/dev: 116452K total, 0K used, 116452K available (block size 4096)
/sqlite_stmt_journals: 4096K total, 0K used, 4096K available (block size 4096)
/rom: 16116K total, 227K used, 15888K available (block size 512)
/system: 285583K total, 210922K used, 74661K available (block size 1024)
/data: 824424K total, 304344K used, 520080K available (block size 4096)
/cache: 237987K total, 4179K used, 233808K available (block size 1024)
/media: 245484K total, 40K used, 245444K available (block size 4096)
/sdcard: 31149680K total, 6924320K used, 24225360K available (block size 16384)
Are you using UK or US Nook?
I'm on US Nook FW 1.2 + v176 kernel
I'm able to reproduce the apk install problems now. The "Not enough free space" error is what android throws when the internal PackageManager can't create the temporary apk file. In this case, it turns out that it's a permissions-related read error from the sdcard. I don't know if this is a matter of the internal PackageManager not running with elevated permissions, or if it's that the sdcard is mounted too restrictively.
If I re-mount the sdcard without the restrictive permissions, I can install apks from the sdcard without any errors:
Code:
umount /sdcard
mount -t vfat /dev/block//vold/179:17 /sdcard
If anyone else has any ideas for making this work, I'm open to any suggestions. In the meantime, "adb install" works just fine for installing packages.
I really suggest grabbing Android Commander if you're new to adb to graphically install apps.
jeff_kz said:
Thanks for reporting this. There was a glitch with the script that formats the SD card and with the wifi loading. Both issues have been fixed in the latest release.
Click to expand...
Click to collapse
Thanks for the quick update. I'm going to try it out now and will report back. I'm very excited
It works! Thanks so much for this! Very easy way to root and backup.
With your tool now I use this to read comics, RSS and books. First I need to say thank you.
I installed "D7 Google Reader" and "Google Drive" which requires Google Login. How could I use this software? Thanks
Also I installed version 0.2, I saw 0.3 comes out. Can I just update 0.2 to 0.3 directly? Thanks
so glad I decided to check the nook thread. Finally BN apps gone . Thank You
hi all, anyone have test factory reset on nstg US ? my backup is corrupt.
Envoyé depuis mon GT-N7100 avec Tapatalk
Y.G. said:
I formated my sd card to Ext4 and when insert it in to my phone, it says that's it's blank and has unsupported files. Any reasons for that?
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
The SPH-L710 Samsung Stock LJ7 TW 4.1.1 Android doesn't understand/support the change to ext4 external SD card (microSD) without a few things being done.
I'm working this out right now. So far I have manually been able to mount the newly created ext4 partition on the microSD card through adb, and after some chown/chmod I was able to go back to "Settings and Storage" and the "Mount SD Card" picked it up, and I was up and running ext4. But this didn't persist after a restart. So I'm looking into: /etc/vold.fstab MODS to keep it after restart right Now !!
If Some one else already has this perfected please chime in. I'm wanting to do most of the devices in the house this way when I get time because better performance, having a file system with a journal, and getting rid of thins like 4 Gig per file limitations is pretty Sweet in my humble opinion *Grin*
0) Assuming you already have your microSD card formatted ext4. I also happened to label mine extSdCard for the volume label within gparted
1) Can mount with:
mount -w -t ext4 /dev/block/mmcblk1p1 /storage/extSdCard/
2) To get the correct owner and permissions run:
chown root:sdcard_rw /storage/extSdCard
chmod 775 /storage/extSdCard
3) Should make the extSdCard owner/permissons match the regular internal sdcard you can verify this like so:
cd /storage/ && ls -l
drwxrwxr-x root sdcard_rw 2013-01-12 18:16 extSdCard
drwxrwxr-x root sdcard_rw 2013-01-12 17:05 sdcard0
4) After that you can go to the "Settings and Storage" to run "Mount SD" and you will have ext4 extSdCard Show up and it bring up the File System Status !! --> Until you reboot and it goes to crap because I don't have the vold.fstab edit/MOD complete _yet_ ... So, for now a boot script has been put in place to bring our external SD card back online during restart, so the system will acknowledges it, making the world a better place.
Example of how things look file system wise: mount | grep extSdCard
/dev/block/mmcblk1p1 /storage/extSdCard ext4 rw,relatime,user_xattr,barrier=1,data=ordered 0 0
5) Have not been able to resolve the vold.fstab to make this ext4 extSdCard matter fully Legit (in my opinion), but I did manage to make it remount the card on boot, so its online when the system comes up instead of having to manually mount it. Did this by -->
Added the following lines to the very bottom of: /etc/init.qcom.post_fs.sh
## sponix MOD to match with ktoonz kernel for better power management
stop mpdecision
## sponix MOD to mount extSdCard prior to GUI work around to make ext4 function
## read and write extSdCard mount
chown root:sdcard_rw /storage/extSdCard
chmod 775 /storage/extSdCard
mount -w -t ext4 /dev/block/mmcblk1p1 /storage/extSdCard
chown root:sdcard_rw /storage/extSdCard
chmod 775 /storage/extSdCard
## if you want read only extSdCard mount
## mount -r -t ext4 /dev/block/mmcblk1p1 /storage/extSdCard
Still attempting to automate the process so the Stock+root LJ7 can pick up the extSdCard _normally_ without having to do the mount command manually, but so far its kicking my butt. Also this is more a "General, or Question and Answer type Topic" the Kernel(s) obviously support ext4 the system fs uses/requires it *Grin*.. So we might get Our Friendly Neighborhood Moderator to Migrate it to the proper place to help others. Just hoping to get the last few bumps smoothed out, or find someone that already documented the process that I've overlooked *Grin*..
Current Known Issues: If you unmount the card through the "Settings | Storage | Umount SD" or by hand with umount, you will either need to reboot for it to reattach through the /etc/init.qcom.post_fs.sh boot script script addition, or will have to mount it manually if you want to keep the system up and running. Guess you could also probably just run the /etc/init.qcom.post_fs.sh as root from a terminal emulator (or adb).
Still searching for vold.fstab bits of wisdom but that will have to continue next weekend -->
Sexy and You Know it,
Keep on Flashing,
sponix2ipfw (sponix
:fingers-crossed:
Ha! Sorry. Deleted: Didn't understand that you had it running on boot (can't read properly )
Great idea
Am I really the only one who also thinks this idea is the nuts?
Am I the only one who longs to transform the mess that passes for a filing system on the internal sd using symbolic links into a beautifully organized, encrypted and cloud synced system on my external sd?
Is it just me and a few others that want to be able to achieve the above so that we can move from one ROM to another or recover from a lost phone with the minimum of fuss?
Are we freaks? :cyclops:
Say it isn't so XDA!! :crying:
I'm gonna try this on my international S3 running Null_ Rom 25 JB 4.1.2
PS do you have any idea how the entire ExtSD or just a folder can be enrypted using Cryptonite and automatically mounted at boot time?
emp111 said:
PS do you have any idea how the entire ExtSD or just a folder can be enrypted using Cryptonite and automatically mounted at boot time?
Click to expand...
Click to collapse
Is this along the lines of what you're looking for?
http://forum.xda-developers.com/showthread.php?t=1141467
Also your idea is pretty insane, but also genius
If you get that to work please do come back and share
Insane ideas are the best lol
CNexus said:
Is this along the lines of what you're looking for?
http://forum.xda-developers.com/showthread.php?t=1141467
Also your idea is pretty insane, but also genius
If you get that to work please do come back and share
Click to expand...
Click to collapse
Thank you for your prompt reply, yes it is asking a lot I know but I think that it can be done.
Now if you really thought that idea was insane......check this out:
Imagine that we asked every Android app developer to submit the various paths used for their config (and config backup) files to a central database and had the ability to add or own custom paths (which could be added to the central database once approved).
We could build an script/app that would retrieve a list of currently installed apps on your phone then automatically build a symbolically linked file system (and/or backup file system) in the location of your choice that you could either encrypt and/or sync using your current tools or even incorporate this functionality into the app itself along with the ability to choose what was encrypted/backed up and how i.e. either synced to the Cloud or (S)FTP or SMB as either a dd copy or even a cwm flashable zip.
Could I dare hope for a Tasker module or the ability to add custom scripts?
I wish I could do this myself but my coding skills are non existent
Anyway the LUKS manager app won't automatically mount a file system, but I really like it anyways, thank you for pointing me to it!
And on the Ext4 front, the mount command (yes the 1st one ) failed, maybe the op could offer a suggestion. :angel:
BTW is there a place for people to suggest ideas for apps here?
Wait really it wont? I couldve sworn I remembering that it did
But dude....
You need to learn yourself some java and start whipping stuff up
Idk about the whole central database thing, but the rest could definitely be done with root access
I think the main problem with that is the proprietary aspects...i mean even here on XDA where binaries released are supposed to be GPL compliant, many of them arent and its sad because it deteriorates the overall quality of work thats released afterward
This whole thing is just hard work!
CNexus said:
Wait really it wont? I couldve sworn I remembering that it did
Click to expand...
Click to collapse
Doesn't seem to unfortunately
But dude....
You need to learn yourself some java and start whipping stuff up :D :D[/QUOTE said:
You make it sound soooo easy lol, and at another point in my life maybe it would have been but right now I'm operating at a reduced level due to some unforeseen circumstances that have left me lacking focus, motivation etc
You know all the things you need to be creative, learn etc lol
Anyway back to the matter at hand, I have got my ext4 SD card to the stage where I have to manually mount it from within the Settings/Storage as I'm using the international S3 and don't have the init.qcom.post_fs.sh, I think the qcom refers to Qualcomm chipset in US S3's.
As for modifying vold.fstab so we can avoid the above workaround it would seem that maybe thats a dead end as according to a German guy on android-hilfe. de, Vold may have been modified by Samsung to only deadl with exFAT on External SD's.
Looks like I'm not gonna be in Android nirvana for a while :crying:
Unless anyone else on XDA fancies getting in on this !!!!
Click to expand...
Click to collapse
Got it working ..... kinda
Got an app called ezymount (by ezynow) that automounts my ext4 64GB microSD at boot time.
I have to wait a few seconds for the boot process to complete but it's automatic, am pretty happy!!
Now gotta get symlinks, encryption and cloud synchronization sorted :/
Does anyone know if any scripts are executed (or can be executed) when the SD card is mounted? Of course this would include on boot.
What I am trying to accomplish is that I would like to mount in a second path the fat32 external partition as the system user (with an appropriate umask) so that I can symlink data from the /data/app directory. I don't mind copying the .apk files and just symlinking them individually; I currently have over 5GB of files there, so I know it should really help with saving space. And, this way I can still take advantage of the space as is, rather than losing it all to a directory symlink.
I don't mind resymlinking once in a while after I add/remove some software. I am a long time Linux user (personally and professionally) so a little command line doesn't scare me one bit.
I thought I should mention that I am currently using LRS G Pad, so a solution that works on stock (or stock-like) ROMs is preferred, though I am curious what a custom ROM can buy me in this area also.
Thank you for your help!
IBJamon said:
Does anyone know if any scripts are executed (or can be executed) when the SD card is mounted? Of course this would include on boot.
What I am trying to accomplish is that I would like to mount in a second path the fat32 external partition as the system user (with an appropriate umask) so that I can symlink data from the /data/app directory. I don't mind copying the .apk files and just symlinking them individually; I currently have over 5GB of files there, so I know it should really help with saving space. And, this way I can still take advantage of the space as is, rather than losing it all to a directory symlink.
I don't mind resymlinking once in a while after I add/remove some software. I am a long time Linux user (personally and professionally) so a little command line doesn't scare me one bit.
I thought I should mention that I am currently using LRS G Pad, so a solution that works on stock (or stock-like) ROMs is preferred, though I am curious what a custom ROM can buy me in this area also.
Thank you for your help!
Click to expand...
Click to collapse
Maybe take a look at tasker to initiate a command. I too had hoped to use a Linux command for a different reason, only to find everything to be different enough to be a problem. Tasker will allow the command, but knowing where to put it will be the problem. Writing a script that recognizes "fuse" initiation, outing it in init.d, and then using tasker to initiate the script?
Maybe just tasker, as you can write simple one liners for different tasks(turning things off and on with a simple path).
Doing this from the kernel ramdisk would probably be better.
Please describe exactly how you do this if you figure it out please!
Best regards,