Related
Today I just tried to install some fonts using Root Explorer and all of a sudden I was stuck in boot loops. So I tried to boot into recovery mode and there was an update.zip on my device (probably from when I was originally rooting) which I think the recovery mode ran. After that, I was in clockwork and I flashed a new font.zip file and that still left me in a boot loop state.
I fixed the boot loop by manually changing permissions on DroidSans.ttf and DroidSans-Bold.ttf to match the other fonts and change owner/group to root:root.
This stopped the boot loop but now every time I boot my phone it force closes all my apps that were previously on sd. I'm not sure why this is happening and it might be other apps that are also not on my sd. It is also not showing all of my installed apps and Launcherpro no longer runs and I am stuck with default htc sense launcher. I would prefer to not wipe the entire phone to fix this.
I have tried a different sd card with the same data and I have also tried formatting the sd card and copying my files back on. Still stuck with force close errors. I am not sure what to do at this point. Any help?
Try fix permissions.
I have tried running the fix_permissions script. Didn't seem to work. Unless there's another method you are referring to. I am unable to launch ROM Manager and it seems like all of my apps are 'new' and never launched before from what they show. Including my alarm settings, those are missing too.
Think I'd restore a backup taken prior to all the font changes. You did make a backup, didn't you?
________________________________
Unrevoked forever
SkyRaider Sense 3.5
Radio 2.15.00.09.01
rigman said:
Think I'd restore a backup taken prior to all the font changes. You did make a backup, didn't you?
________________________________
Unrevoked forever
SkyRaider Sense 3.5
Radio 2.15.00.09.01
Click to expand...
Click to collapse
I do have a backup but unfortunately its a little bit old and I would rather fix this if possible. It feels like some folder is missing permissions. Because even stock Google talk crashes and market crashes when I try to view an app but I can search around if I want.
Another route I can go is to backup my data for apps and then install a new Rom as I have been wanting to. This would allow me to fix my problems but I need to know what folders I have to manually backup for saves.
Well some good news. After messing around with permissions on some files on the sdcard I was able to restore my notification sound back and also able to make GTalk work properly. So it looks like there is hope yet.
Where do apps store settings such as configuration, db, etc?
It looks as if my data/data partition is wiped? I'm not sure what happened but I guess that means all my app saves are gone.
Am I right to assume that?
I used this application NotEnoughSpace made by a xda member and using it to symlink some of my apps from data partition to a new area on emmc seems to work. However when I try to restore back to my data partition, it doesn't work.
So this leads me to believe that the permissions on my data partition are off and I need to change the permissions, owner, and group for the data partition and all files inside it. The command would be:
Code:
chmod 664 data/*
chown root:root data/*
And run this while outside of the main data folder. As long as the right owner/group is root:root.
Can someone confirm?
It looks like /data/cache is mainly used by Market for storing downloads. Quite a bit of space can be taken up there. And it looks like one can just relocate that to storage (with root);
Code:
su
mkdir /storage/cache
cd /data
rm -rf cache
ln -s /mnt/storage/cache /data/cache
/data/cache won't be available for any apps that need it directly on boot, and those apps may crash, but I haven't noticed anything like that happening on my A43.
As usual with such tricks, use at your own risk and make a backup.
Currently I can't any of the busybox installers to reinstall it, they
all report not able to get root immediately after superuser says
it has root privs.
Can I push the busybox executable to /system/xbin manually?
Would I do better to just reflash the rom, over the existing one,
(running install-script will put back busybox and and symlinks).
help
Are you able to get su permission for other apps still?
You can push it manualy to /system/bin or /system/xbin, just make sure to set the correct permissions owner and group. rwxr-x-r-x and root for owner and group.
[Resolved] I ended up restarting with a wipe and new rom install
It was just to complicated due to so many basic functions
being in the busybox binary.
I did a TiBu of my apps and system data and exported people data
to a vcf. Wiped and re-installed the rom, restored my export of the
people data, restored my apps+data and system data. rebooted,
installed a ext4 compatible kernel, rebooted, installed the ext4 no
data limit (/data/data to /data), rebooted, installed the ext4 kernel
again, (as the ext4 zip puts its own), rebooted, installed the UOT
Kitchen Circle Battery, installed the zip to fix recticle & recurring
warning box, rebooted, setup people group for full page people
widget, rebooted to recovery to run a new nandroid after all the
patching was done.
*sigh*
Tedious, but everything is working as I'd planned .
WITH THE NEW CM10 PARTITION LAYOUT THIS SET OF SCRIPTS HAS NO USE ANYMORE, USE IT ONLY IF YOU KNOW WHAT YOU ARE DOING AND YOU ARE SURE YOU NEED THIS.
WHY?
Many people have complained that the new Cyanogenmod 10 partition layout reserved too little space for user application and their data. While I don't find this to be a great deal (having 100+ installed apps usually means many of them are not even used) the solution to the problem is pretty simple, so I've created this tool suite.
FAQ
WHAT DOES THOSE SCRIPTS DO?
Automatic Edition
0.4 AppMover Enabler.zip
When you flash this file if necessary your apk files will be moved to system and a new script will be put in addon.d, this will backup and restore automatically your apps every time you update your rom
This require the rom support, you can check it out HERE if your rom support this function.
0.4 AppMover Disabler.zip
This file will revert everything disabling the automatic backup and restore system and moving apps back to /data. If there is not enough space in /data the script will exit with an error without removing anything.
Developer Edition
0.3dDeveloperEdition.zip
This file contains a modified updater-script and a shell script so that when installing a rom patched with them it will move, backup and restore apks files according to necessity: if the apps are already been moved to /system it will backup them, update the rom and restore the apps; if the apps are still in /data it will update the rom and then move the apps to /system/user_app
Compact Edition
AppToggler.zip
This files moves /data/app to /system/user_app or moves them back to /data/app if you already activated this. If there is not enough space to move the files the script just revert back to a safe condition. You can check the results of the operation in /sdcard/AppMover.txt.
Since the apk files are written only during application installation/updates this should have little to none performance impact while freeing about 70% of the space in /data.
You should use this script just once to move your apk files to the bigger, slower /system partition. Use it again if you want to move them back to the faster /data partition
BackupAndRestore.zip
This files create a backup of /system/user_app to /sdcard/AppBackup.tar. If /system/user_app doesn't exists but there is /sdcard/AppBackup.tar the script assumes you have just updated your rom and restores the backup.
You should use this script before and after every rom update since the CM10 update script formats the /system partition wich now contains your apk files
Normal Edition (Discontinued)
AppMover.zip
This script moves /data/app (the folder where downloaded apk are stored) to a new directory in system (/system/user_app) and then create a symlink to that directory.
AppReverter.zip
This script moves back app to /data/app and deletes /system/user_app.
WARNING: Flash this file only if you are sure there is enough space in /data for all the apps! If not you will end with a full /data partition (and relative forcecloses) and you will lose some apps
AppBackup.zip
This script will backup all your app files in an archive in /sdcard
WARNING: Make sure you have enough space in /sdcard for all your apps.
AppRestore.zip
This script will restore the apps from the archive in /sdcard
HOW TO USE:
Automatic Edition
If you want to move your apps to /system just flash AppMover Enabler.zip, this will take care of moving the apk files and preserve them during rom updates
WARNING: During rom updates ensure you have enough space in /emmc and/or /sdcard for the backup of your apk files, if not you will lose all your apps. Ensure your rom is supported (you can check it here). Consider that rom updates will now take longer, even 3 or 4 times what it used to be depending on how many apps you have installed.
If you want to move your apps back to /data flash AppMover Disabler.zip, this will also disable the backup and restore function. If there is not enough space in /data the script will exit with an error before doing anything.
Developer Edition
Replace the rom files with the one in the archive and then flash the rom normally. Make sure you have backupapps.sh in the root of the rom archive and that updater-script is correctly replaced in /META-INF/com/google/android
Compact Edition
To move your apps to /system you have to flash AppToggler.zip. This should be the first and only time you flash this file since now the fix is applied to a directory level. Newer apps will be installed directly to /system/user_app.
BEFORE flashing/updating your rom you will have to run BackupAndRestore.zip and AFTER flashing the rom you will have to run BackupAndRestore.zip again, not doing so will remove all the apps from your phone since at every update /system dir gets formatted.
If you want to move back all your apps to /data you can just flash AppToggler.zip again.
Normal Edition (Discontinued)
To move your apps to /system you have to flash AppMover.zip. This should be the first and only time you flash this file since now the fix is applied to a directory level. Newer apps will be installed directly to /system/user_app.
BEFORE flashing/updating your rom you will have to run AppBackup.zip and AFTER flashing the rom you will have to run AppRestore.zip, not doing so will remove all the apps from your phone since at every update /system dir gets formatted. Note that AppBackup.zip and AppRestore.zip will work both with /system/user_app and with /data/app, so you can use this two file for backup and restore apps (but not their data) in any rom/occasion.
If you want to move back all your apps to /data you can flash AppRevert.zip
If you done everything good and you get a bootloop try to fix permissions in CWR
If the phone works fine but reboots when you try to install new application it is probably because the OS can't write on /system/user_app for some reason.
Try those steps and report if any of those solves the problem:
Open the terminal or use adb shell and type
Code:
su
mount -o rw,remount /system
and/or
Code:
su
chmod 0777 /data/app
chown 1000:1000 /data/app
In alternative you can try this:
feroxxx said:
[...]
i have problem with reboot issue but solved it wipe cache,dalvik,fix permission and remove google play app's update.no reboot now.
[...]
Click to expand...
Click to collapse
Try to keep in mind that this scripts completely moves /data/app to /system partition. This normally is not a problem, however if you flash something in CWR that needs to read/write something in /data/app (like fixing permissions) make sure to mount /system partition manually
This script should have little to no impact on your rom performance but you may notice some performance loss installing/updating apps.
You may use this script in your rom (integrating the backup/restore into the installation script of a rom would make life simpler for everyone) or improve it, I just ask you to give me some credit.
DISCLAIMER:
This script may contain bugs and is far from perfect. Read instruction twice and make a full nandroid backup before flashing anything, since human errors could be pretty devastating. Anyhow in case of problems I will try to help and improve the scripts but I won't be responsible for any damage to your phone or data, including -but not limited- to: bootloops, app or data loss, alien invasion and thermonuclear war.
==================================================
DOWNLOAD LINK
==================================================
CHANGELOG:
23th September 2012
V 0.5 (All versions) - Updated init.d script, renamed again as S99SystemApps to make it work on devil kernel. Now the script renames init.d scripts that doesn't start with S#. Is still possible that some scripts get executed after mine, but should be pretty rare.
V 0.5 Automatic Edition - Modified so that in case of problems the phone will reboot before deleting anything, thanks to Silentbob999 for the idea.
19th September 2012
V 0.4.2 Compact Edition - Fixed a typoes in AppToggler and BackupAndRestore.
V 0.4.2 Automatic Edition - Fixed the error you get if you try to flash the Enabler this just after formatting data (didn't test it, but it should work).
V 0.4.1 Init.d Updater - Published a flashabile file to update the init.d script so that you can use the updated one without having to toggle apps or extract it manually from the archive.
V 0.4.1 Compact Edition - Little update to AppToggler so that even if exits on error it still updates the init.d script
V 0.4.1 (All Versions) - Updated init.d script, added some fixes for problem no norma user should ever experience
17th September 2012
V 0.4 Automatic Edition - Automatic version published
V 0.4 Developer and Compact Edition - Renamed /etc/init.d/S99SystemApps in /etc/init.d/z99SystemApps, this will make less likely that some script gets executed after it and sets back /system to read only
14th September 2012
V 0.3.2 (both) - Hotfix, looks like the hotfix applied to init.d did the trick, same correction applied to remaining scripts
13th September 2012
V 0.3.1 (both) - Hotfix, seems that on some phones /system is mounted as read only. Modified init.d script to remount /system in RW if needed
V 0.3 developer edition - Almost rewritten from scratch, now there should be no problems if flashing from gingerbread and if any problem occurs the script should stop before deleting anything. Completely rewritten log system. Temporary apk backup will now be placed in /data /emmc or /sdcard, according to where there is enough space. Added file in init.d that helps preventing corruptions, hopefully system reboots when new applications are installed are gone.
V 0.3 compact edition - Added a lot of space checks. The backup is now saved on /emmc, if there is not enough space there is saved on /sdcard. If there is not enough space anywhere script will now exit with error. Completely rewritten log system. Added file in init.d that helps preventing corruptions, hopefully system reboots when new applications are installed are gone.
Normal Edition - Dropped unless I get enough requests to work on it, is almost equivalent to the compact version and having to work and test 3 version instead of 2 is just time consuming.
5th September 2012
V 0.2.5 developer edition - New version to replace CM10 stock update script, intended to be used by developers in their rom
30th August 2012
V 0.1c compact edition - Initial compact edition Release
V 0.2.5 - Fixed the error where app folder was restored in /system/user_app for good
25th August 2012
V 0.2 - Fixed an error in AppBackup.zip that could lead to follow recursively the symlink of the app directory (again and again and again..)
22th August 2012
V 0.1 - Initial Release
Sounds good. Thanks.
It would be better if we can choose the apps to be removed. Thus an app is needed, I think.
what's the difference with titanium backup?
dongfangri said:
Sounds good. Thanks.
It would be better if we can choose the apps to be removed. Thus an app is needed, I think.
Click to expand...
Click to collapse
You are right, but yhea... without an app would be pretty hard to setup the script. Maybe I could make so that moving apps with root explorer to another dir will trigger a script in init.d to create the symlink, but I think it doesn't make much sense since the performance loss of apk on /system is near to 0 (CM9 and all the rom before that had apks on the partition we now use for /system)
forziere said:
what's the difference with titanium backup?
Click to expand...
Click to collapse
It's not intended to be a backing up tool (even if at some degree works for app backup/restore) but just to move ALL apks in /system where there is a lot of unused free space. You can do it pretty easily by hand if you know some basic linux commands but is still more complex/time consuming than using an automated script like this
Hey, thanks, it's that I was loonking for, works great on MIUIV4 Jelly Bean by Andy Thomson !
Great idea
If i will flash the cm10, i will use your scripts
It's a great idea, but then the app work very well from system/user_app?
esticbo said:
It's a great idea, but then the app work very well from system/user_app?
Click to expand...
Click to collapse
I've published this set of scripts also to get some feedback. Personally I can't find any problem nor performance differences (except the fact that before I had 40mb free in /data and now there are 300) between having apk in /data or in /system but I guess different people with different phones may have different perceptions and results.
By the way my phone is pretty old and it lagged a lot before Pawitp introduced the new memory layout, so I guess I have the old, slower, memory. Fact is I read somewhere (on the CM10 thread I think) that old memory is slow just in writing operations and apk files are written just during installation/update.
As soon as I get some more feedback, I will update the OP with this informations, but before this I have to know if the script can create problems or slowdowns of any sort.
This sounds like a really good idea. Does this do the equivalent of Wendigogo's script by moving the lib files to the slower partition only? Or does it move more than just the lib files?
Vertron said:
This sounds like a really good idea. Does this do the equivalent of Wendigogo's script by moving the lib files to the slower partition only? Or does it move more than just the lib files?
Click to expand...
Click to collapse
It's /data/app that is moved so it's only apks.
Updated with a bugfix to the AppBackup.zip file, if anyone is using this is way better to update
Vertron said:
This sounds like a really good idea. Does this do the equivalent of Wendigogo's script by moving the lib files to the slower partition only? Or does it move more than just the lib files?
Click to expand...
Click to collapse
It's not like "my" datafix because CM move all /data to the speedy partition (and increase its size to 420Mo).
I've made something equivalent on my phone to move apk (on /data/app) to the /system partition. And I brake my CM when upgrading it cause installation process format /system and I forgot to backup my apks.
The best solution was to create a specific /data partition and use the speedy partition for /datadata (as in CM9/7) but pawitp's don't want to do that cause the partition layout will be SGS specific and CM is NOT an SGS rom...
For now this is the best solution ( do you backup users:groups a specific rights for each app?).
Bad news for those having lots of big apps...
Envoyé depuis mon GT-I9000 avec Tapatalk
Wendigogo said:
It's not like "my" datafix because CM move all /data to the speedy partition (and increase its size to 420Mo).
I've made something equivalent on my phone to move apk (on /data/app) to the /system partition. And I brake my CM when upgrading it cause installation process format /system and I forgot to backup my apks.
The best solution was to create a specific /data partition and use the speedy partition for /datadata (as in CM9/7) but pawitp's don't want to do that cause the partition layout will be SGS specific and CM is NOT an SGS rom...
For now this is the best solution ( do you backup users:groups a specific rights for each app?).
Bad news for those having lots of big apps...
Envoyé depuis mon GT-I9000 avec Tapatalk
Click to expand...
Click to collapse
DerTeufel1980 is using a different partition for his Helly Bean rom that has a /data and /datadata partition, so your datafix script should work for his rom at least.
Hopefully other roms will use DerTeufel1980's layout instead as they don't have the same limitations as CM10.
Happy to report this fix has been working perfectly for me on CM10. Thanks so much!
Kino87 said:
WHY?
Many people have complained that the new Cyanogenmod 10 partition layout reserved too little space for user application and their data. While I don't find this to be a great deal (having 100+ installed apps usually means many of them are not even used) the solution to the problem is pretty simple, so I've created this tool suite.
WHAT DOES THOSE SCRIPTS DO?
AppMover.zip
This script moves /data/app (the folder where downloaded apk are stored) to a new directory in system (/system/user_app) and then create a symlink to that directory.
AppReverter.zip
This script moves back app to /data/app and deletes /system/user_app.
WARNING: Flash this file only if you are sure there is enough space in /data for all the apps! If not you will end with a full /data partition (and relative forcecloses) and you will lose some apps
AppBackup.zip
This script will backup all your app files in an archive in /sdcard
WARNING: Make sure you have enough space in /sdcard for all your apps.
AppRestore.zip
This script will restore the apps from the archive in /sdcard
HOW TO USE:
To move your apps to /system you have to flash AppMover.zip. This should be the first and only time you flash this file since now the fix is applied to a directory level. Newer apps will be installed directly to /system/user_app.
BEFORE flashing/updating your rom you will have to run AppBackup.zip and AFTER flashing the rom you will have to run AppRestore.zip, not doing so will remove all the apps from your phone since at every update /system dir gets formatted. Note that AppBackup.zip and AppRestore.zip will work both with /system/user_app and with /data/app, so you can use this two file for backup and restore apps (but not their data) in any rom/occasion.
If you want to move back all your apps to /data you can flash AppRevert.zip
If you done everything good and you get a bootloop try to fix permissions in CWR
This script should have little to no impact on your rom performance but you may notice some performance loss installing/updating apps.
You may use this script in your rom (integrating the backup/restore into the installation script of a rom would make life simpler for everyone) or improve it, I just ask you to give me some credit.
DISCLAIMER:
This script may contain bugs and is far from perfect. Read instruction twice and make a full nandroid backup before flashing anything, since human errors could be pretty devastating. Anyhow in case of problems I will try to help and improve the scripts but I won't be responsible for any damage to your phone or data, including -but not limited- to: bootloops, app or data loss, alien invasion and thermonuclear war.
==================================================
DOWNLOAD LINK
==================================================
CHANGELOG:
V 0.2 - Fixed an error in AppBackup.zip that could lead to follow recursively the symlink of the app directory (again and again and again..)
V 0.1 - Initial Release
Click to expand...
Click to collapse
Errors found in AppRestore.zip. The script moves the fold /data/app into /system/user_app. It should be all apks in /data/app, isn't it?
zhuzf said:
Errors found in AppRestore.zip. The script moves the fold /data/app into /system/user_app. It should be all apks in /data/app, isn't it?
Click to expand...
Click to collapse
Depends, AppRestore.zip is used to restore the backup created with AppBackup.zip.
AppBackup.zip creates a .tar file that includes the path from the root (so if you have your apps in /data/app you will have those two directorys in the .tar, otherwise you will have /system/user_app). At the restore time the .tar is simply extracted to the root.
Maybe you are confusing AppRestore (used to restore backups) with AppRevert (used to move back apps in /data/app), but still... it does what it should do (I think).
Soon I will release a 0.3 version that aggregate AppMover and AppReverter in a single package that toggles the place where apps are stored and aggregate AppBackup and AppRestore so that if it finds /system/user_app it will create a backup and if it doesn't find it it will restore it (bringing down the number of zips from 4 to 2, but the operations you have to do remains the same). Less chances to human errors and more to script bugs, so if something happens you can blame it on me
Right now I'm thinking to a complete rework with a couple of alternatives since I think this suite is a little bit impractical:
- create something that changes the partition layout splitting /system in a 512mb partition for /system and a 1536mb partition for /data/app... Still I'd prefear to find some alternative since this solution could create pretty big problems if something goes wrong and it won't have native support in the roms/kernels (wich means you would still have to flash a file every time you update the rom to tell it how to manage the partitions and I'm not really shure what would happen when the CM updater script tries to format system and it finds is smaller than intendend, so it may be impossible to do).
- Create an alternative update script that replaces the one in the CM10 zip and does what I wrote above (you would have to modify the CM10 zip every time, but it would be as simple as drag and drop one file in it).
- As alternative to the the repartitioning create an image file of an ext4 partition and mount it runtime (like we did with One Click Lagfix a couple of years ago). It should be easy to customize the zip so that you can chose where to create this file and how big it has be so that you can place it in /system but also in /sdcard or in /emmc. Still... you will have to flash something that teaches how to handle it to the rom every time you update it and if you put in /system you will still have to backup and restore it every damn time (so I guess is pretty useless).
To be honest I don't think that altering the partition layout without official support in the rom is a practical solution since I think negative aspects are way bigger than positive ones but I still think this solution is quite annoying if you update your rom often as I do, so if anyone has suggestions they are welcome.
By the way while I can see the actual rom partitioning has some serius limitations but I understand the reasons behind Pawitp decisions and I hope we won't get different partition layouts on different roms (that will just be a mess e we will end up with different version of kernels ad patches.. We need no more fragmentation than we already have with our device being 2 years old and having roms starting from 2.1 to the actual 4.1.1)
Kino87 said:
- create something that changes the partition layout splitting /system in a 512mb partition for /system and a 1536mb partition for /data/app... Still I'd prefear to find some alternative since this solution could create pretty big problems if something goes wrong and it won't have native support in the roms/kernels (wich means you would still have to flash a file every time you update the rom to tell it how to manage the partitions and I'm not really shure what would happen when the CM updater script tries to format system and it finds is smaller than intendend, so it may be impossible to do).
- Create an alternative update script that replaces the one in the CM10 zip and does what I wrote above (you would have to modify the CM10 zip every time, but it would be as simple as drag and drop one file in it)
Click to expand...
Click to collapse
That looks like the best solution imo. Changing the update script on each rom before you update it. I assume this will work on all roms, not just CM10?
I assume that will make the partition layout similar to DerTeufel1980's new layout?
I thought of a hopefully good idea that would allow you to update nightly roms. If it is possible and someone is willing to develop it.
For this to work you'll have to create an ext4 partition on an external sdcard of about 700mb.
Basically there will be 4 scripts, 1 of them to move /data/app to /system/app with a symlink. One for simply moving it back to /data/app if wanted. Then the other 2 scripts is to move /app to the sdcard partition when you want to update a nightly.
So my idea is; you install the rom for the first time, then run the 1st script to move /data/app to /system/app.
If you want to update the rom. Run a second script which moves /system/app to the external sdcard partition. Then flash the nightly rom as normal. Then install a 3rd script which moves /app from the external sdcard partition back to system/app.
The 4th script is to simply move everything back to /data/app if wanted.
The only downside to this is losing some space from your external sdcard. But it's worth it imo for having alot more storage space and having the ability to update nightly roms.
Do you think this is a feasible idea, or will updating the rom break the symlink?
Vertron said:
I thought of a hopefully good idea that would allow you to update nightly roms. If it is possible and someone is willing to develop it.
For this to work you'll have to create an ext4 partition on an external sdcard of about 700mb.
Basically there will be 4 scripts, 1 of them to move /data/app to /system/app with a symlink. One for simply moving it back to /data/app if wanted. Then the other 2 scripts is to move /app to the sdcard partition when you want to update a nightly.
So my idea is; you install the rom for the first time, then run the 1st script to move /data/app to /system/app.
If you want to update the rom. Run a second script which moves /system/app to the external sdcard partition. Then flash the nightly rom as normal. Then install a 3rd script which moves /app from the external sdcard partition back to system/app.
The 4th script is to simply move everything back to /data/app if wanted.
The only downside to this is losing some space from your external sdcard. But it's worth it imo for having alot more storage space and having the ability to update nightly roms.
Do you think this is a feasible idea, or will updating the rom break the symlink?
Click to expand...
Click to collapse
This is how it works already.. well.. almost.
The Backup and Restore scripts do exactly what you want to do on an external partition (the only difference is that they don't copy the apk on an ext4 partition but they store them in a tar archive on /sdcard that preserve users and permissions regardless of the filesystem in use).
Would make a little more sense to use directly an ext4 partition on the sdcard or external sdcard since it would avoid you the trouble to backup your apps every time you update the rom (but then you will still have to flash a file at every update that tells to mount this external partition) but even then... I'm not fond of altering the partition layout at all even if doing it on /sdcard or /emmc would make it pretty easy to restore in case of problems.
By the way: I've finished the compact version of the suite (0.1c) and fixed a couple of bugs in the old version. Is actually online BUT IS NOT TESTED IN ANY WAY. Don't use it until I update the OP and even then do a nandroid backup before using it, it may be pretty buggy.
Hopefully if there are no bugs in a couple of hours of test I will report back
If your apps are backed up by using AppBackup.zip and you flash a updated rom, do you have to flash AppRestore.zip before the device boots with the new rom or can you let it boot then turn it off and run the script in recovery after?
Hey guys
let me give you some background informatie as to what happend
I went on a flashing spree today and I bumped into something irritating!
I've flashed JBSourcery V4.5 but it didn't satisfy my personal needs (didn't have some mods that I liked).
So back into recovery, factory reset, cache wipe... all the standard cleaning stuff. Next on my list was
LiquidSmooth and that's where my problem started. I was in recovery, wiped the lot and wanted to flash
LiquidSmooth which was already on my SDcard (I came prepared ) So I chose "Install ZIP from SD" and
my heart skipped a beat. Normally I'd see all my folders on my SD... Now I only saw "0", "Legacy" and "obb".
I kept my cool and opened each one untill I found my SD contents which where stuffed into the "0" folder.
No big deal... I could flash LiquidSmooth so everything was fine. Next one was XenonHD. Still same problem
but I could flash my stuff.
Long story short, how do I get my internal memory back to how it was?
Something on a side note though, It's only like that in recovery. If I connect my phone via USB it's normal. (Samsung Galaxy Nexus -> Internal Memory -> ...)
Ideas are welcome!
Thanks in advance! :good:
diSke
Move them with Root Explorer or hook it up to the comp and move them. Or check out some of the other threads about the /0/ folder, there are allot of them.
WiredPirate said:
Move them with Root Explorer or hook it up to the comp and move them. Or check out some of the other threads about the /0/ folder, there are allot of them.
Click to expand...
Click to collapse
Oh great... and I added one to the lot... Sorry guys!
Didn't think of searching with the "0" folder as keyword.
Thanks though for the reply and solution!
One quick question, do you know if the "Legacy" and "obb" folders are important?
I'm sure they are significant for some reason, but I am unsure of their specific purpose. I would for sure keep them in tact.
Hmmm... I moved them and now all my sd card files are scattered around...
Some in legacy, some in "0", some in media... probably best to wipe the lot and start from scratch?
From another post about Android 4.2's filesystem setup:
Cilraaz said:
Source: init.tuna.rc
Code:
on init
# See storage config details at [URL="http://source.android.com/tech/storage"][COLOR=#0066cc]http://source.android.com/tech/storage[/COLOR][/URL]
mkdir /mnt/shell/emulated 0700 shell shell
mkdir /storage/emulated 0555 root root
export EXTERNAL_STORAGE /storage/emulated/legacy
export EMULATED_STORAGE_SOURCE /mnt/shell/emulated
export EMULATED_STORAGE_TARGET /storage/emulated
# Support legacy paths
symlink /storage/emualted/legacy /sdcard
symlink /storage/emualted/legacy /mnt/sdcard
symlink /storage/emualted/legacy /storage/sdcard0
symlink /mnt/shell/emulated/0 /storage/emulated/legacy
[...]
# virtual sdcard daemon running as media_rw (1023)
service sdcard /system/bin/sdcard /data/media /mnt/shell/emulated 1023 1023
class late_start
[...]
Click to expand...
Click to collapse
You said which ROMs you flashed, but what version of Android are you on now? It sounds like you might be back on 4.1.x, since you're seeing 0, legacy, and obb in /sdcard.
If you went back to 4.1.x, then 0, legacy, and obb are not important. Only /data/media matters on 4.1.x. If you are on 4.1.x, go to /data/media/0 and copy all of the files there to /data/media, then reboot. That will fix your setup. Once that's done and 0, legacy, and obb are all empty, they are safe to delete.
If you are on 4.2 or 4.2.1, then the above quote is accurate. Your information should be in /data/media/0 and the system should be properly fuse mounting and symlink'ing to showyour data into /sdcard.
When moving files around, it's usually best to do it at the source (within /data/media) so you don't have to worry about the fuse mounts and symlinks causing a problem.
I switched from 4.1 to 4.2.1.
Problem is I started switching things around and now my sd card files seem te be everywhere.
Can't figure out what is what...
I moved everything from "data/media/0" to "data/media"
but now my system can't find my files.
When I try to move everything back it says "unable to execute the command"
diSke said:
I switched from 4.1 to 4.2.1.
Problem is I started switching things around and now my sd card files seem te be everywhere.
Can't figure out what is what...
I moved everything from "data/media/0" to "data/media"
but now my system can't find my files.
When I try to move everything back it says "unable to execute the command"
Click to expand...
Click to collapse
As my post said, if you're on 4.2.1, your files should be in /data/media/0. You'll see copies of them in multiple places (/storage/emulated/legacy, /sdcard, /mnt/shell/emulated/0, /mnt/sdcard, /storage/sdcard0, and /data/media/0), but these are fuse mounts and symlinks. Your data only "physically" exists in one place: /data/media/0. After rebooting, your files should be found in /sdcard, rather than /sdcard/0. If not, then you might have the multiple 0 folder issue (e.g. /data/media/0/0/0, which ends up being /sdcard/0/0) from having an outdated version of your recovery.
Long story short, if you're on 4.2.1, then any files from your "SD Card" should be found in /data/media/0. If you're on 4.1.x, then they should be in /data/media.
If you're getting that error when trying to copy from /data/media to /data/media/0, then you'll need to check that /data/media is mounted as r/w and that you have write permission to the 0 folder within it. You should also be copying these files around as root (either through terminal emulator or a root file browser like Root Explorer).
Cilraaz is correct, however if you are looking for an easy way to straighten it out you can do the following.
Copy everything you want to save to the computer.
Reboot into recovery and format data. (Not wipe data actually format.)
Reboot phone and data partition will be good to go again.
Copy files back from computer and you should be as you were previously.
Of course all other data will be gone but I'm sure if you are a crack flasher you can get all that back.
G-Nexus Sent
ifly4vamerica said:
Cilraaz is correct, however if you are looking for an easy way to straighten it out you can do the following.
Copy everything you want to save to the computer.
Reboot into recovery and format data. (Not wipe data actually format.)
Reboot phone and data partition will be good to go again.
Copy files back from computer and you should be as you were previously.
Of course all other data will be gone but I'm sure if you are a crack flasher you can get all that back.
G-Nexus Sent
Click to expand...
Click to collapse
Good call on the computer backup. You don't need to wipe data, though. Just backup what you want to save from storage to your computer, then flash userdata.img from the stock 4.2.1 ROM, which will wipe out and re-create the /data/media partition. Then when you reboot, the fuse mounts and symlinks will be properly recreated and you can use MTP to copy your data back (or adb push it to /data/media/0 or /sdcard).
Thanks guys.
Fixed it differently though, Completely wiped everything again and started from scratch.
Made a backup earlier of everything I wanted to save except for messages which I forgot (damnit)
But it's all good now
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator