I was trying to install my apps to my sd card today and now my phone wont reboot. This is what went down. I partitioned my 4g micro sd card, or so i thought. I used Paragon and it gave me an error after reboot;
invalid partition data- partition control blocks information incompatible"
So I restarted my computer. I checked on my phone and it showed i only had 3 gigs available. The partition i made was for 1, so i figured what the hell. It did work. I checked in Paragon and it showed the two partitions. Anyway, i proceeded to input the prompts in adb and it connected, but the second cmd wouldnt work $ mkdir /backup. I went ahead and followed the rest of the commands. At $ adb shell reboot the phone of course rebooted.
I didnt finish the last two commands but accidently restarted my phone. Now it hangs at the G1 screen. rooted g1 by the way.
I have wiped the data and cache, but of course that will do nothing in this case. So it does get me to that screen. I can also hold the camera and power and see my skating androids. But how do i get my phone to boot back up?
At the recovery utility using Alt X to get to console gives me a # prompt.
Help would be greatly appreciated guys, i dont have another phone haha!
Thanks
I'm guessing what you means by "I didnt finish the last two commands but accidently restarted my phone." is that you weren't able to do the "ln -s /system/sd/app /data/app"? If so then at that # prompt, you need to type those very same commands,
Code:
ln -s /system/sd/app /data/app
reboot
hopefully will work after that
Nope. Thats a no go. However, i decided to throw the update back onto my sdcard via sdcard reader. I put the sd card back in and its about done updating back to rc33. I'll report. Seems good so far.
Its all good!
Thanks
you wiped data and that symbolic link is still there?
I wiped my phone and want to redo the app to sd process, but the apps are still on my sd card ext2 partition is there a way I can restore those apps after a wipe or do I have to wipe the ext2 partition and just start over, if so how would I go about doing so.
Joeriginal said:
I wiped my phone and want to redo the app to sd process, but the apps are still on my sd card ext2 partition is there a way I can restore those apps after a wipe or do I have to wipe the ext2 partition and just start over, if so how would I go about doing so.
Click to expand...
Click to collapse
You've done accidentally what I did intentionally.
I moved apps and data over to the SD ext2 partition, then intentionally wiped the phone to start as fresh as possible.
I thought all I needed to do was recreate the symlinks with:
Code:
ln -s /system/sd/app /data/app
ln -s /system/sd/data /data/data
reboot
That should have worked, but didn't. Maybe you'll have better luck than I did.
I was using the LucidREM mod of the JF1.42 firmware which comes with scripts for moving the data and apps.
If you aren't using this version, you'll need repeat the whole manual process of modifying the mount.d and init.rc files so you can see the /system/sd partition on the card.
If you are, you can use the copy.sh undoapps and copy.sh undodata commands and that will put everything back on your phone. At that point it should be exactly as it was before.
If successful, you can try moving everything back either with the Market app, or one of the other scripts floating around on here....
For what it's worth, I never could get things to work when I moved /data/data.....I've had to keep that on my phone and just move the apps. Others seem to have more success moving both without issue.
Joeriginal said:
I wiped my phone and want to redo the app to sd process, but the apps are still on my sd card ext2 partition is there a way I can restore those apps after a wipe or do I have to wipe the ext2 partition and just start over, if so how would I go about doing so.
Click to expand...
Click to collapse
I can give you the code to do it, or you can just use my app that runs the same commands I'd give you. If you use the app just uncheck the checkbox before pressing the move apps to sd button. If you want to go the code route, follow my tutorial starting from the recovery terminal part.
EDIT: oh and 4phantomii: did you just do that code or did you rm -r /data/data and rm -r /data/app first? If you didn't remove the directories first I have no idea what that would do but it seems like it'd make a symlink INSIDE the /data/app and /data/data rather than making them the symlinks.
Well, some of you may have heard my ramblings around here that I've been working with some of the devs here(JF and MartinFick deserve major praise, probably more than me) on getting a better way to do the whole apps to sd thing.
After 3 days of talking/discussing/working on it, I've finally reached the fruits of that investigation and thought I'd share. This new method uses the filesystem unionfs to essentially meld the /data directory with the /system/sd directory, so that they appear to be one. This has the potential to allow users to move specific apps to or from the sd card, is far more stable than the normal symlink method(will still boot, etc even if there's no SD card) and should be easier to set up. Now, onto the tutorial of setting this up.
BIG DISCLAIMER NOTE: This is a major hack of the phone and it is fully possible that it will break your phone(I've seen no permanently bricked phones but that doesn't make it impossible). Use this method, and my app along with it at your own risk.
REQUIREMENTS:
1: This only works on JF(possibly only on 1.5, not sure about the others) and The Dude's v.1.0 or greater. The Dude's 1.0 or greater actually does the steps in this tutorial for you so you can just run appstosd2 and set it all up from there if you're using his ROM.
2: This still requires you to have 2 partitions set up, first FAT32 and second ext2. Although you can use the appstosd2 app attached to this post and available in the market for $0.99 which will partition the card for you.
3: If you want your apps to go to the sd card, you must have a directory "/system/sd/app" If you didn't have apps to sd before on the ext2 partition do the following in terminal emulator or run my appstosd2 app after finishing the tutorial:
Code:
su
mkdir /system/sd/app
If you want the private-apps, or dalvik-cache moved you can replace "app" in that code with ""app-private", or "dalvik-cache" respectively. Do not copy "data" to the sd card. My script will delete it on the next reboot.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
Alright, first there's some files you need.
1: init.rc in .zip attached to this thread
2: a2sd.sh in .zip attached to this thread
All the above listed files should be put on your sd card(my tutorial will assume they are in the root directory of the sdcard(the topmost folder)
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
If you need to undo the normal apps to SD first do the following in the recovery terminal(it's not strictly necessary but I'd recommend it):
Code:
mount data
rm /data/app
mkdir /data/app
if you moved the dalvik cache, repeat steps 2-3 with "dalvik-cache" instead of app. Ditto with "data" for the data cache.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
Then go to terminal emulator and type the following:
Code:
su
cp /sdcard/init.rc /data/
cp /sdcard/a2sd.sh /data/
Then reboot and you're set. By default all future apps are installed to the sd card. In order to move an app to the internal memory do the following in terminal emulator:
Code:
su
cp /system/sd/app/[the app you want to move] /system/intmem/app/
rm /system/sd/app/[the app you want to move]
I will be incorporating this into my appstosd app soon(probably as a JF and TheDude-only version until the rest of the devs get on board).
I have included a copy of appstosd 2, which will copy all apps from internal memory to the sd card with an option to remove them from the internal memory. This will only work if you have followed this tutorial.
If you don't have partitions set up, appstosd2 will now do that for you with user-set partition sizes.
NOTE: If you're using The Dude's ROM and find yourself with an outdated version of this since he doesn't always update his ROMs at the same time I update this, do the following in terminal emulator to update(after putting a2sd.sh from the attached a2sd.zip on your sdcard):
Code:
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
rm /system/bin/a2sd.sh
cp /sdcard/a2sd.sh /system/bin/
reboot
For JF1.5, do the following to update:
Code:
su
rm /system/intmem/a2sd.sh
rm /system/intmem/init.rc
cp /sdcard/a2sd.sh /system/intmem/
cp /sdcard/init.rc /system/intmem/
reboot
NOTE FOR UPDATERS: If you had your data on the sdcard(/system/sd/data), it WILL GET DELETED with the new version. This is a necessity in order to get both wallpaper and protected apps working. I recommend moving it back to the phone.
EDIT: And here's another tutorial from ThatsBS(might be easier for the less tech savvy to follow?):
I am still learning a lot everyday from this forum. So for people new to this process let me noobify it, if I can, as I am one too.
Start by reading the first page!! Get all the stuff you need from page 1. (apps2sd2.zip and a2sd.zip )
I started from a fresh wipe and flash of jf1.51 adp.
A newly formatted fat32, non partitioned sd.
Put the init.rc and app2sd.sh on the sd (the files NOT the zip)
Then go to the terminal emulator and typed:
su
cp /sdcard/init.rc /data/
cp /sdcard/a2sd.sh /data/
Then reboot
Next I ran the apps2sd 2 app. It will ask you how much to you want to partition. I did 3000mb the first successful time and the dreaded low mem notice would not leave the status bar. I have read not to make it more then 1500mb. Have a good connection, dont force close it. It will reboot.
Next, after the reboot, I ran the apps2sd 2 app again and pressed "copy apps to sd" (let it do its thing)
Reboot.
Next I went back to the emulator and typed:
su
mkdir /system/sd/app-private
mkdir /system/sd/dalvik-cache
Reboot.
Go back to the apps2sd 2 app and hit move dalvik-cache.
Reboot for good measure and your done.
I did this in about 10 mins. Worked flawlessly.
I have a ?, if i have been using your app what dod i do diferent or what should i change?
Thanks
Good job, thanks!
[email protected] said:
will still boot, etc even if there's no sim card
Click to expand...
Click to collapse
You mean SD card?
[email protected] said:
Alright, first there's some files you need.
1: unionfs.ko from here:
Click to expand...
Click to collapse
JF1.5 build has already unionfs.ko in it, doesn't it? Is there any difference between this unionfs.ko and the one included?
1. I hear unionfs is not really stable at this point, is it true?
2. Why do you want to move the whole /data folder to sd, instead of just /data/app, /data/app-private?
3. You might want to add a command to remove previous app2sd changes (i.e. delete symlinks, create folders.)
4. How do you put selected apps to internal memory after this? Copying to /data will copy to sd card again.
The whole idea is really interesting! Thank you for your work!
ArmandHammer said:
I have a ?, if i have been using your app what dod i do diferent or what should i change?
Thanks
Click to expand...
Click to collapse
You don't have to do anything different. It will find all the apps you put on the sd card. If you want to set the phone back to normal(so the phone memory apps can still be there), you can do the following in the recovery terminal:
Code:
mount data
rm /data/app
rm /data/dalvik-cache (only if you moved the dalvik-cache)
mkdir /data/app
mkdir /data/dalvik-cache
@Dimath: yes, I did mean SD card, good catch
1:JF didn't mention it and from a little bit of using it, it seems stable to me. Plus, no matter how much I've screwed up, I haven't managed to boot loop my phone yet.
2: You could just mount those independently. I might end up doing that eventually but for now the way it is works for reasons I'll get to.
3: True, although it's not strictly necessary. If apps2sd already works, this won't break it. I'll put in a guide on undoing the symlink method
4: Actually, no. My script sets the internal memory as the main file system in the union, so apps automatically go there. Moving apps to the sd card just involves copying them to /system/sd.
Ok, just a little confusing.
I didn't use the apps2sd to move apps over to my SD card. What I did was set it with the busybox ls command. I guess that's the symlink.
My question is, if I didn't use apps2sd, can I still use your method? I also moved the dalvik cache also, everything works fine for me now, my apps go directly to the SD card when installing since my memory stays at around 65 MB no matter what I do.
Just need some laymen terms to help me understand that if I'm NOT using apps2sd, and I just linked them with the recovery method, what's my pitfalls / advantages?
Thanks.
larrygates said:
Ok, just a little confusing.
I didn't use the apps2sd to move apps over to my SD card. What I did was set it with the busybox ls command. I guess that's the symlink.
My question is, if I didn't use apps2sd, can I still use your method? I also moved the dalvik cache also, everything works fine for me now, my apps go directly to the SD card when installing since my memory stays at around 65 MB no matter what I do.
Just need some laymen terms to help me understand that if I'm NOT using apps2sd, and I just linked them with the recovery method, what's my pitfalls / advantages?
Thanks.
Click to expand...
Click to collapse
Yes, any other method of apps to sd currently uses the same symlink method, so following the directions as if you installed my app will work. A note though is that all future apps will install to the internal memory by default. I did that because it's MUCH easier to move apps from the memory to the sd card than vice versa. You can use the code I posted if you want it the other way around.
would this also work for /data/data and app-private?
or is this particular setup only for dalvik-cache and app?
oh and before I do this, just wondering, so in theory, since I have a 1.5GB ext2 partition, my free memory will be 1.573GB (1.5GB + 73Mb internal)? The internal memory will just run down and switch over to the sdcard when needed (but be seen as one filesystem)?
andonnguyen said:
would this also work for /data/data and app-private?
or is this particular setup only for dalvik-cache and app?
Click to expand...
Click to collapse
This works for the whole /data folder and everything under it. Everything is automatically installed to the phone memory right now so you can just move over anything you don't want on it(will be making an app to do this automatically)
EDIT: oh and anything you already moved over to the sd card will still show up.
Code:
su
mount -o remount,rw /dev/block/mtdblock3 /system
cp /sdcard/unionfs.ko /system/
cp /sdcard/init.rc /data/
cp /runme.sh /data/
cp /sdcard/a2sd.sh /data/
I see, when I run these lines of code (I can do this from adb also right using adb remount) this IS the new symlink method. It's just all at one time without me having to manually link anything.
Right?
larrygates said:
Code:
su
mount -o remount,rw /dev/block/mtdblock3 /system
cp /sdcard/unionfs.ko /system/
cp /sdcard/init.rc /data/
cp /runme.sh /data/
cp /sdcard/a2sd.sh /data/
I see, when I run these lines of code (I can do this from adb also right using adb remount) this IS the new symlink method. It's just all at one time without me having to manually link anything.
Right?
Click to expand...
Click to collapse
Wrong, no symlinks here. Pure unionfs goodness. Basically it convinces the operating system that /data and /system/sd are the same thing. So anything that's on /system/sd shows up under /data but everything that's normally under /data is still there. Think of it like what happens in windows when you merge folders with the same name, but in this case in actuality everything stays exactly where it was.
New news: If you haven't seen it, I updated this tutorial(and the scripts with it) quite a bit and would now consider it to be completely fully functional.
Also The Dude will be sending me an advance copy of his next ROM tomorrow to verify it works. In his build the apps to sd will be automatic, with no user setup(although if you want apps on the sd card you'll have to make an app directory under /system/sd(mkdir /system/sd/app), ditto for dalvik-cache and data).
Finally, I will attempt to add this into my apps to sd app tonight, thus rounding out everything I can do.
After all this, the only thing left is for Haykuro to build it into his ROM and me to make an app to move specific apps to/from the sd card automatically.
This will no doubt be the method of choice in no time. Great work. Sticky?
If anyone dl'd the latest version(that fixed the race condition, etc), please download the one I just put up. I made that one in windows and I believe the funky carraige return(that indicates a new line) that windows uses screwed it up
So I got some kind of error, and I don't know what is going on.
I put in all the lines in the terminal emulator app..
but after line cp /runme.sh /data/ it gives me an error
it says "cp: cannot stat '/runme.sh': No such file or directory
Any help? I rooted my phone just so I could run my apps off of my SD card.. and now I can't figure out how to get it to work. Somebody help me please.
GTASouthPark said:
So I got some kind of error, and I don't know what is going on.
I put in all the lines in the terminal emulator app..
but after line cp /runme.sh /data/ it gives me an error
it says "cp: cannot stat '/runme.sh': No such file or directory
Any help? I rooted my phone just so I could run my apps off of my SD card.. and now I can't figure out how to get it to work. Somebody help me please.
Click to expand...
Click to collapse
Which ROM is this? JF1.5 should have runme.sh there...
[email protected] said:
Which ROM is this? JF1.5 should have runme.sh there...
Click to expand...
Click to collapse
Ok, I am going to re-partition my memory card.. and then re flash to JF1.5 and try it again.
Just tried it, one issue I'm seeing is android seems to install [email protected]@[email protected] into /system/intmem/dalvik-cache at boot. Is there anyway to have that only in my dalvik-cache on the sdcard?
Its a fairly large file at 3megs so I want it to reside solely on the sdcard and even if I delete it from intmem, whenever I reboot it gets added again.
Now when I display the internal phone storage from the settings menu, it shows up at 835 megs.
I wonder if this is possible to use unionfs and make an ext2 fs object as a file on the FAT fs. That way no 2nd partition is necessary. Plus, if you remove the sdcard, everything will still work.
Maybe we could combine unionfs and this method that uses an ext2 image on the fat32 for apps to sd.
http://forum.xda-developers.com/showpost.php?p=3402947&postcount=687
mkefs can be downloaded here:
http://sites.google.com/site/juanjosec/android
dwang said:
I wonder if this is possible to use unionfs and make an ext2 fs object as a file on the FAT fs. That way no 2nd partition is necessary. Plus, if you remove the sdcard, everything will still work.
Maybe we could combine unionfs and this method that uses an ext2 image on the fat32 for apps to sd.
http://forum.xda-developers.com/showpost.php?p=3402947&postcount=687
mkefs can be downloaded here:
http://sites.google.com/site/juanjosec/android
Click to expand...
Click to collapse
I've been looking at that possibility with JF and MartinFick as well, seems like it could be a good plan but I wanted to get this bit done first. It's a good point about the dalvik-cache, but in order to fix it JF(in this case) would have to change /init.rc to make sure to do this bit before building the dalvik-cache.
Can't download apps from market
hmm so I didn't hit any errors when doing this, but afterwards I am unable to download any apps from the market. It just continually says "Starting Download..." Everything else seems to work well.
I had this same issue when I tried to manually setup apps to sd using the symbolic links. I narrowed the issue down and figured out this only occurred after I moved the dalvik-cache over to the sd card. I'm assuming I'm doing something wrong, but can't seem to figure it out. Any pointers in a general direction would be most helpful
I'm using JFv1.50 ADP1.5, not the modded version by LucidREM. For some reason the bootloader couldn't pickup his version on my phone and --edit-- I'm pretty sure I have the SD card partitioned correctly... everything else seemed to work ok. The ext2 partition shows up as the correct size
*EDIT* So apparently my issue was the SD card as well. Just did a format of the sd card and it fixed it. I also formatted data and cache (alt+w in recovery mode). Thanks MarcusMaximus!
[email protected] said:
New news: If you haven't seen it, I updated this tutorial(and the scripts with it) quite a bit and would now consider it to be completely fully functional.
Also The Dude will be sending me an advance copy of his next ROM tomorrow to verify it works. In his build the apps to sd will be automatic, with no user setup(although if you want apps on the sd card you'll have to make an app directory under /system/sd(mkdir /system/sd/app), ditto for dalvik-cache and data).
Finally, I will attempt to add this into my apps to sd app tonight, thus rounding out everything I can do.
After all this, the only thing left is for Haykuro to build it into his ROM and me to make an app to move specific apps to/from the sd card automatically.
Click to expand...
Click to collapse
If I have apps2SD and the dalvik-cache both moved on the dudes builds already, do I still have to create those directories or will my existing setup still work fine? I would like to know what kind of issues I may run into when the dude releases .95 with this (hopefully, not getting my hopes up just in case).
So apparently I have to use my computer or root explorer to write to my SD card since the 3.2 update. Does anyone know how this might be fixed to allow general file managers or applications to take advantage of?
same here....
f'ing moto fail here....this is NOT sd support to me
i have been using file manager HD and it will copy files to & from the sd card and delete from the sd card. it just wont "move" to the sd card.
EDIT- was using root explorer...not the other one.
Did you do anything special since upgrading to #Version three point two? I use the same program and it won't move, copy, or delete.
jase33 said:
i have been using file manager HD and it will copy files to & from the sd card and delete from the sd card. it just wont "move" to the sd card.
Click to expand...
Click to collapse
I can copy from the SD card but not paste to using the same software...this mean its read only
To be clear, I updated using update.zip and now running tiamat kernel, but I'm sure it was read only before I flashed the new kernel
I updated to 3.2 with ota and manually rooted. using stock kernel. write to sd works fine. maybe the method you updated from or the kernel you use is causing an issue.
sdcard
heh i find it amusing:
Real SDCard = /mnt/external1
Same ole crap SDCard = /mnt/sdcard, /sdcard, /data/media, and i bet more if i care to look harder.
jase33 said:
I updated to 3.2 with ota and manually rooted. using stock kernel. write to sd works fine. maybe the method you updated from or the kernel you use is causing an issue.
Click to expand...
Click to collapse
Are u talking about the Sdcard folder or the external1 folder?
I updated via update.zip method
Edit: Attached screenshot of my external1 permission
jase33 said:
i have been using file manager HD and it will copy files to & from the sd card and delete from the sd card. it just wont "move" to the sd card.
Click to expand...
Click to collapse
Moving from one source to another isn't possible. It's a linux/android thing. So that's nothing to worry about.
Remount /mnt/external1 as read/write
Here's what I've done to make /mnt/external1 read/write accessible:
adb shell or any other terminal emulator to get to a shell on the xoom
su to get to the # prompt
umount /mnt/external1
mount -t vfat -o fmask=0000,dmask=0000,rw /dev/block/platform/sdhci-tegra.2/mmcblk0p1 /mnt/external1
That remounts the sdcard without using vold, which is enforcing a mask on the perms.
Now to get this to happen at boot...
Stealyourface said:
Moving from one source to another isn't possible. It's a linux/android thing. So that's nothing to worry about.
Click to expand...
Click to collapse
Yeah I know.....I was just responding simply
Sent from my HD2
Stealyourface said:
Moving from one source to another isn't possible. It's a linux/android thing. So that's nothing to worry about.
Click to expand...
Click to collapse
I move files all the time in Linux, via both command line and file manager. I don't know where you are getting this "Linux/Android can't move files" from.
Given up and revert back to Tiamat 1.1
I reflashed stock and upgraded to 3.1 then 3.2 only to learn that the SD card was not writable within the xoom. I have full confidence that one of the devs will release a mod for 3.2 to get us all the features that we are accustomed to. Until then I've flashed back to Tiamat 1.1.
ekarelis said:
Here's what I've done to make /mnt/external1 read/write accessible:
adb shell or any other terminal emulator to get to a shell on the xoom
su to get to the # prompt
umount /mnt/external1
mount -t vfat -o fmask=0000,dmask=0000,rw /dev/block/platform/sdhci-tegra.2/mmcblk0p1 /mnt/external1
That remounts the sdcard without using vold, which is enforcing a mask on the perms.
Now to get this to happen at boot...
Click to expand...
Click to collapse
This is exactly right. It appears vold is now placing special perms above standard media_rw perms. So, apps without this level of permission can not write to external storage. We will address this in the upcoming Tiamat Rom release.
looking forward to 3.2 cusrom rom
Thanks brd. Very much looking forward to the tiamat 3.2 based rom.
mambomta said:
I move files all the time in Linux, via both command line and file manager. I don't know where you are getting this "Linux/Android can't move files" from.
Click to expand...
Click to collapse
Move a file from your xoom (if you even have one) from internal storage to external. It either won't let you, or it'll get corrupted in the process.
Stealyourface said:
Move a file from your xoom (if you even have one) from internal storage to external. It either won't let you, or it'll get corrupted in the process.
Click to expand...
Click to collapse
My Xoom should arrive tomorrow. If the Xoom is not allowing a move, it is a bug, not a limitation in Linux.
I just has my USCC Galaxy S3 replaced under warranty. To save my internal SD files, I used an ADB pull /storage/sdcard0 in recovery. When I got the new phone rooted and CM10 installed, I booted to recovery and used an ADB push to restore the files. The files all ended back on the SD card, but now my apps cannot write to the folders on the SD card. The permissions are set to 644, and I cannot change them. I have tried with chmod and through file managers to change to 777, and although they claim success, the permissions stay 644. I'm unsure where to go from here, but I really would like to keep these files on my device. Any ideas on how to fix these permissions? Thanks!
Try copying/moving files around using the phone's file manager, & see if the changes stick. Also try "adb shell" -> "su", and change permissions that way, & see if it sticks.
Make sure you have an updated busybox.
Well, I tried moving them with file manager, su and updated busybox, changing permissions, and then I finally decided to go into recovery, pull, and format /sdcard. Once I did that, my apps were able to use the card again. I then was able to copy over the files via usb mount to windows. This seems to be working so far.
Thanks!