Related
I had to reset my phone today, since for some odd reason, I switched it off and back on, and it wouldnt get back the flashing android screen (havent even made any changes to it recently, God knows why it decided to do this).
Anyway, I figured, format the phone, reflash JF 1.5, and then move apply apps2sd (I already have my apps on my SD card, just have to link them back to the phone so it can see them), and the small customisations I can do later, I would get my phone back to functioning level.
I am using these instruction from SDK on my computer:
1. Check if your phone is recognised.
adb devices
2. Mount the phone into ADB.
adb remount
3. Bring up the shell.
adb shell
4. Check if /system/sd is visible.
df
5. Skip this step if you already have your apps on SD.
cp -a /data/app /system/sd
6. Skip this step if you already have your app-private on SD.
cp -a /data/app-private /system/sd
7. Remove the current apps folder on device.
rm -r /data/app
8. Remove the current app-private folder on device.
rm -r /data/app-private
9. Link the app folder on sd to the one on device.
ln -s /system/sd/app /data/app
10. Link the app-private folder on sd to the one on device.
ln -s /system/sd/app-private /data/app-private
11. Finally Reboot.
reboot
Well, I can flash the phone fine, but when I am trying to follow the instructions for relinking the apps from SD to the phone (stage 4), it doesnt show /system/sd, instead it shows /sdcard.
Does this mean I should change the following steps to say 'sdcard' instead of '/system/sd'? I have tried this with no luck, shows me the android screen indefinitely.
I have an ext2 partition on the phone on which I have my apps, I have done this whole process before many times, but not for a while so I am missing something important.
And I am skipping steps 5 and 6, since I have already got all my apps on my SD card.
Any help would be must appreciated, this is wasting quite a bit of my time.
PS: the only thing I have changed since I last did this, was I flashed the phone with a google ion build, while it had JF 1.5 on it. What I did notice after that was the phone ran a lot slower. That is the only change I can think of which separates this process working perfectly previously, and not at all now.
Um reformat your entire card to fat32. And then use cyanogen's recovery 1.31. to split your sd into 2 partitions. Msg me on gtalk or by email and I'll help you out
Many thanks for the reply.
Hmm I would have thought a reformat of the SD card would be last resort, is there no way to sort this out without going down that route?
Don't think there's another way, You could try switching ROMS see if that fixes it...
Might not need to reformat it all just yet.. Been awhile since I used JF, but I don't think it automatically mounts /system/sd
I think you might need the init.rc from this post -- http://forum.xda-developers.com/showthread.php?t=512743
Personally - and I try not to be preach about it, but I think CM users can't help that -- I'd suggest trying CyanogenMod since you're reflashing anyway. It isn't quite as stock as JF, but it is rock solid and fast, and it should pickup your existing A2SD partition automatically.
Agreed with Saiboogu. Try out Cyanogen's ROM you will NOT regret it
Ok, I am up for that.
BTW, when I format my phone (Alt+W I believe), and start it up again, its firmware is still upgraded.
If I reflash with a ROM, will that cause any problems or slowing, will it be overwriting anything? I guess I dont quite understand what the formatting of the phone is doing, and what it is leaving behind, and then what reflashing with a ROM is doing on top of that.
Also,m when you say Cyanogen's rom will do apps2sd automatically..how? Will it recognise the apps currently on the ext2 partition of my SD card? It wont delete them will it?
It will not delete them. It uses bind mounts to automatically do the apps to sd . Just wipe and flash
Ok, giving it a try now.
Hmm something I should have asked beforehand, my partition is ext2, do I need to change that to ext3 before I flash the cyanogen ROM?
Like alritewhadeva said - it just recognizes your existing apps.
A wipe clears out all the custom data.. Your settings, application data in the /data partition, your google account data that is synced to the phone. It doesn't touch the actual OS, which is why your ROM is still installed after a wipe.
With that said.. Cyanogen builds can be "broken" if you wipe after a flash. So always either just flash, or wipe *then* flash.
PERFECT! its worked like a charm! no hassle at all!
Great! You won't regret it.
one problem I have noticed, my camera keeps force closing (wont even start up without force closing straight away).
Any solution to this? Have tried going into the camera app in applications manager and clearing defaults, but no defaults were set.
That one sounds familiar, but I can't find an actual reference to it right now. Probably want to search the Cyanogen thread for mentions: http://forum.xda-developers.com/showthread.php?t=518851
Also keep an eye out for updates - Cyanogen is prolific, and will probably get one released sometime this evening. It may fix the issue.
That one sounds familiar, but I can't find an actual reference to it right now. Probably want to search the Cyanogen thread for mentions: http://forum.xda-developers.com/showthread.php?t=518851
Also keep an eye out for updates - Cyanogen is prolific, and will probably get one released sometime this evening. It may fix the issue.
Edit: Ah, here it is - http://forum.xda-developers.com/showthread.php?t=536687
He says he had to wipe his SD card, repartition and everything. Not sure if that is your issue or not.
Ah I posted a fix for that just take the camera.apk from an older cyanogen build (3.6.5) and push it over.
so put the camera.apk on sdcard
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd sdcard
cp Camera.apk /system/app
reboot
I am afraid due to my pathetic ignorance of how android works, I cant decipher what you said.
How do I get the camera apk? And once I acquire it, and put it on my SD card (I am assuming not in any folder, just on the main directory of the card), I use the terminal emulator to type in those commands?
well thats rather funny, just switched my phone on and off and the camera is working now.
raukodur said:
well thats rather funny, just switched my phone on and off and the camera is working now.
Click to expand...
Click to collapse
well then awesome
Great that you got it working. For future reference (because these things do happen occasionally), alritewhadeva was suggesting that you download an older version of CM (link on his build thread), unzip it and find the camera.apk file. Then place that file on your sd card, and follow his directions in Terminal Emulator on the phone.
Hey guys. I just followed the new and improved apps2sd2 method and when I went to apps2sd2 I clicked copy all apps to sd card and now after my phone restarted I have no apps and my sd card seems to be ... wiped. I just looked around and foudn out that my computer is not recognizing the other partition so it thinks my 8gb card is 6 gb. That means my apps may still be there, how can I retrieve them?
Kavin2468 said:
Hey guys. I just followed the new and improved apps2sd2 method and when I went to apps2sd2 I clicked copy all apps to sd card and now after my phone restarted I have no apps and my sd card seems to be ... wiped. I just looked around and foudn out that my computer is not recognizing the other partition so it thinks my 8gb card is 6 gb. That means my apps may still be there, how can I retrieve them?
Click to expand...
Click to collapse
You need to use terminal to type:
$su
#cp -r /system/sd/app /data/app
that's where the apps are usually located on the sdcard. Or you can try using Root Explorer to access that folder and see if they're there. Its probably just missing some symlinks tho which is easy enough to fix. Again, back in terminal:
ln -s /data/app /system/sd/app
should do the trick.
h.nocturna said:
You need to use terminal to type:
$su
#cp -r /system/sd/app /data/app
that's where the apps are usually located on the sdcard. Or you can try using Root Explorer to access that folder and see if they're there. Its probably just missing some symlinks tho which is easy enough to fix. Again, back in terminal:
ln -s /data/app /system/sd/app
should do the trick.
Click to expand...
Click to collapse
I thought the new method used unionfs rather than symlinks :-/
AdrianK said:
I thought the new method used unionfs rather than symlinks :-/
Click to expand...
Click to collapse
Eh, I'm just doing this off the top of my head from when I used the app. Sometimes it wouldn't work, and I would just link it manually cuz at least I could access the partition.
I have partitioned sd card and I have the hello im apk on the sd and I want it on my phone because it wont let me change my buddy pic it says please make sure your sd card is in the phone so Im going to try to put it back on internal storage to see if it works. So how do I move it? I parted with apps2sd but the app wont work with cyan 4.0.1 so how Do I move it?
Apps2sd is really an all or nothing proposition. You can't have one app on internal memory and the rest on the SD card.
If you want to get rid of apps2sd altogether I can tell you how to move everything back.
OTOH, if an app is complaining about the sd card it's probably talking about the fat32 partition that it wants to store images on. Is your fat32 close to being full or something?
on a side note im on cyan 4.0.1 I was at 3.6.8.1 when I used the apps2d app and now when I try to open it it says Oops! Looks like you need to go through the tutorial to set up apps to sd. Please go to blah blah blah why is it doing this
what do I have to do to get this app running gain I already haves apps going to sd.
The top part of Cyanogen's stable thread says not to use any other method of apps to sd because his has a script built in.
So. Stop fiddling with whatever apps2sd app you have.
go to terminal and type:
Code:
su
ls /dev/block/mm*
Tell me what you see. (And please take a moment to make your posts a little more readable, I'm having a hard time deciphering what you're asking/saying. )
what Am I suppost to do? I dont want to do it without knowing
open the application 'terminal emulator' -- this is like the dos 'command prompt' in windows or a term window in Linux
type 'su' and press enter -- this Switches User to root, or the administrator of the machine (your phone)
type 'ls /dev/block/mm*' -- 'ls' is 'list' directories. /dev is where all the devices are, block is hard-drive like devices (your internal memory and the sd card) and mm* is every block device that starts with 'mm....' which should be mmcblk0 (the sdcard), mmcblk0p1 (the fat32 partition) and mmcblk0p2 (the ext partition)
If the last exists, the cyanogen automatic apps2sd will have already moved all your applications there. If only one exists, it means you either formatted the whole SD card to ext2 for apps2sd (and left nothing fat32) or formatted none of it and your apps are already on your phone.
if your 'ls /dev/block/mm*' says that you have a mmcblk0p2, than run "ls /system/sd/app/*" and you should see a bunch of files ending in .apk. If so, then you have to undo apps2sd to get the Hello IM app back to internal memory.
Report back on the outputs of the above and further instructions will be provided.
Ok Iv done all that so how do I undo them and if so how will I get them back?
Tell me what all that said back when you typed it in. THEN I can tell you what to do.
I see all my apk files now what? I want to move that 1 app onto the phone memory and every other apk on the sd. Im ready for the next step.
I see a bunch of files ending in .apk now what?
Hmm. I just looked up 'Hello IM!' and see that it's a paid app.
So, we can move just paid apps to the internal memory and leave the free ones on the sd card.
if yes run the following in terminal emulator:
su
rm /data/app-private
mkdir /data/app-private
cp /system/sd/app-private/* /data/app-private
Copying the apps may not work and you may have to uninstall/reinstall, but when you install them they'll be on the internal memory.
Oh, but cyanogenmod will put them back on the sd card when you reboot, so if having the app on the internal memory does fix the problem, you'll have to edit the a2sd script.
The problem isn't that your apps are on the sdcard. The app itself doesn't know. Your partions may be out of whack or the app itself may just need to be reinstalled.
When your apps are on the sdcard they are on a different partition then what every app uses your sdcard for. Not sure if I wrote that where you can comprehend it or not...
wat do u mean out of wack
PsychoI3oy said:
If you want to get rid of apps2sd altogether I can tell you how to move everything back.
Click to expand...
Click to collapse
I've done some searching, and haven't found any way to do this that has worked for me. Could you please pass some of this info along?
Thanks.
HowTo - un-apps2sd (on CyanogenMod)
Ok, this is based on the assumption that you are running a Cyanogen rom. I'm sure it could be adopted for use on another one, but Cyanogen 4.0.x is what I'm running. You'll probably have to re-install any paid apps (app-private) but normal apps should run fine after this.
Instructions for use with adb:
Code:
adb remount
adb push a2sd.txt /system/bin/a2sd
adb shell
# rm /data/app
# mkdir /data/app
# cp /system/sd/app/* /data/app/
# rm /data/app-private
# mkdir /data/app-private
# cp -r /system/sd/app-private/* /data/app-private
# reboot
for terminal emulator, assuming the new a2sd.txt is on your sdcard:
Code:
mount -o rw,remount /system
mount -o rw,remount /data
cp /sdcard/a2sd.txt /system/bin/a2sd
and then continue the adb instructions from after 'adb shell'
after reboot you can confirm that it worked by running:
ls -l /system
from terminal emulator (no need to remount/su) and you should see 'app' and 'app-private' as directories (and not app -> /system/sd/app).
If you're running some other a2sd method, you'll have to edit/remove the script that's doing the linking, then delete the symlinks and copy back (should be similar to above).
The modified a2sd.txt attached just takes away the apps-to-sd part. Dalvik-cache is still run from /system/sd/ as are whatever other magical juicy bits he's got in there.
If you upgrade to another Cyanogen rom, the new version of a2sd will get pushed and everything will be moved back. The only way to get rid of it permanently would be to delete the ext2/3/4 partition on your sd card.
If you decide you want apps2sd again and don't want to upgrade, just put the a2sd.orig.txt back as /system/bin/a2sd and reboot, it'll automagically move everything back to the /system/sd/app on your ext partition.
I just did the un-apps2sd then put the original back and everything's fine (and was fine with un-apps2sd).
That should cover most things....
Thank you so much for the step by step instructions.
One minor correction, maybe, shouldn't there be a '/' at the end of the second to last line?
Also, for me I didn't copy over the modified a2sd.txt file. After I copied everything to internal I shutdown the phone and deleted the ext partition. All seems to be working well!
Thanks again.
daveerickson said:
Thank you so much for the step by step instructions.
One minor correction, maybe, shouldn't there be a '/' at the end of the second to last line?
Also, for me I didn't copy over the modified a2sd.txt file. After I copied everything to internal I shutdown the phone and deleted the ext partition. All seems to be working well!
Thanks again.
Click to expand...
Click to collapse
Trailing slashes are optional in most shells, including this one.
Glad it worked for you.
these doesn't seem to be working for 4.2.1, no a2sd file exists in /system/bin, maybe he moved it somewhere else, i'm trying to find it but i'm not being lucky.
any help?
No, he broke up the bits that were in a2sd and spread them across several files in /system/etc/init.d/
http://wiki.cyanogenmod.com/index.php/Removing_Apps2SD has the instructions now.
After having apps working fine on my phone for a while now... a lot of the apps on my g1, once started, make me force close them.. apps include: anything that uses the accelerometer [except iliter?], lock 2.0, ringers extended.. and a bunch of other ones. I dont think the apps are corrupt considering that they have worked previousally and just started not working. Could the ext2 partition on my sd be full? I set the partition to 700mb and i only have about 20 apps or less.
Maybe somebody could advise on what this might be.. thanks!
Also, every time i turn my phone on i get process com.htc.calender stopped unexpectedly and asks a force close. it asks me to f.close it like 3 times when i first turn on the phone. YES I DID WIPE BEFORE FLASHING THIS ROM. Is there a way to just get rid of this process entirely? becuase after i force close if i go to calander in the menu it works.
what rom are you currently using? what was the rom you used before flashing to your current rom? did you try deleting your dalvik-cache? what about running fix_permissions?
I know when I went from a hero rom to cupcake, I had those same issues so if that is the same problem than you are gonna have to format your ext partion and reload your files, I know if you search the forums though there is a command that you enter in the terminal to just delete the files doing it to you
if you went from a hero rom to a cupcake rom then you need to go into the recovery console and type
Code:
mount /system
rm /system/sd/app_s/*
rm /system/sd/dalvik-cache/*
if that still does not fix it then you will need to just use
Code:
mount /system
rm /system/sd/*
david1171 said:
what rom are you currently using? what was the rom you used before flashing to your current rom? did you try deleting your dalvik-cache? what about running fix_permissions?
Click to expand...
Click to collapse
Running Cyan 4.02 + 1.4 [before this was running JACHero] and no i didnt delete my dalvik-cache??? <--whats that?
It's where your system wipes anything, just type in the codes that were posted and you will be alright, hero leaves files on your ext partion that need to be removed because they do not work with the non hero framework, the code that was post will remove those files, you must type them in the recovery console and not terminal emu
gridlock32404 said:
It's where your system wipes anything, just type in the codes that were posted and you will be alright, hero leaves files on your ext partion that need to be removed because they do not work with the non hero framework, the code that was post will remove those files, you must type them in the recovery console and not terminal emu
Click to expand...
Click to collapse
Will give that a try! thx.
Is that going to delete any of my apps?
Also-- is there a way to confirm that my apps are being automatically installed on my SD?
It will not delete any of your apps just the left over hero junk. To conform just go into manage apps under settings and check the space that is free internal and see how much is used of your ext
gridlock32404 said:
It will not delete any of your apps just the left over hero junk. To conform just go into manage apps under settings and check the space that is free internal and see how much is used of your ext
Click to expand...
Click to collapse
went into manage apps in settings... how do i check the space used by the ext? Menu option only include sort & filter
ALSO i know i sound exteremly noobie.. but..
mount /system
rm /system/sd/app_s/*
rm /system/sd/dalvik-cache/*
Do i replace the *'s with something else, or am i to actually type "*"
Whoops I meant sdcard and storage, sorry bout that I have been up since 5 yesterday and is now 3 in the afternoon so on that note, nighty night. Good luck
ONe more ?
Everytime i type rm /system/sd/app_s/* it tells me cannot remove - no such file or directory.
says the same thing with the rm davvik-cahce thing.
and yes i am in console in recovery.
Try without the *.
Than it's quite possible that you might have to format your sd card, backup your files using I think using app manager and backup for root users, transfer your files onto your computer and format, be a real good time to set yourself up with a nice 96mb swap file. Don't feel bad I plan to reformat mine tomorrow just to get all the old crap off just to have a clean slate
Thank you david I must be tired I didn't notice when he asked about the * and I also said the dalvik cache wipes to your system instead of writes, just noticed that after I just reread my post
I flashed Maxisma's v1.6.1 last night, and my apps are installing to my SD, but they're also installing to my internal memory. Right now I only have 31 MB left. Does anyone know what I can do to get them removed from my internal memory and have them only installed on my sd card.
The System apps are installed on the data partition (rosie, htc widgets, etc....)
If you really prefer them on your sd card
you can symlink /data/app_s
back to
/system/sd/app_s
I find it better that they are on the data partition because Im not gonna use the data partition that much and it makes it easier to wipe from hero to cyan
B-man007 said:
The System apps are installed on the data partition (rosie, htc widgets, etc....)
If you really prefer them on your sd card
you can symlink /data/app_s
back to
/system/sd/app_s
I find it better that they are on the data partition because Im not gonna use the data partition that much and it makes it easier to wipe from hero to cyan
Click to expand...
Click to collapse
All of my apps are installing in both system/sd/app and /data/app. It's not just the system apps. I've downloaded them from the market, and installed apks manually and they all go both places for some reason.
I don't know if this is related to the other problem or not, but it's also taking about 5 seconds for the screen to come on after pushing menu from when the phone is locked.
rp1783 said:
I don't know if this is related to the other problem or not, but it's also taking about 5 seconds for the screen to come on after pushing menu from when the phone is locked.
Click to expand...
Click to collapse
thats a rom related problem.
how do you know its installing to the data partition? can you see the files in an explorer? because when you install an app, its cache is stored on the data partition and can be as big as the app itself
well, not only does it show in the root file explorer, but it's also taking tons of internal storage. I'm at 30 MB right now. I'm just wanting to have everything installed to the SD except the system apps. When I first flashed the rom, I had 47 MB. After installing all my stuff I'm at 30.
Does anyone have any suggestions on this? I'm at 27 MB free on Maxisma's 1.7. I'm not sure what else to try I've tried removing the apps from the internal memory, and it deletes them, I've tried removing them from the SD card, which also deletes them.
rp1783 said:
Does anyone have any suggestions on this? I'm at 27 MB free on Maxisma's 1.7. I'm not sure what else to try I've tried removing the apps from the internal memory, and it deletes them, I've tried removing them from the SD card, which also deletes them.
Click to expand...
Click to collapse
have you upgraded to his latest rom?
maybe that will fix the problem (you can also nandroid and reflash the version you have)
if those dont work, you may have to symlink /data/apps to /system/sd/apps
i believe an old symlink may still be there cause it to go to both places but im not 100% sure. did you wipe before installing?
B-man007 said:
have you upgraded to his latest rom?
maybe that will fix the problem (you can also nandroid and reflash the version you have)
if those dont work, you may have to symlink /data/apps to /system/sd/apps
i believe an old symlink may still be there cause it to go to both places but im not 100% sure. did you wipe before installing?
Click to expand...
Click to collapse
Yeah, I wiped, I also just flashed 1.7.1 about 20 minutes ago, and I'm at 26MB now. How do I symlink?
Ugh. Don't worry about it. That's just your data cache taking up space on your /data/ partition. Your apps are still installing to /system/sd/app/ the reason you see them in /data/app is because /data/app/ is symlinked to /system/sd/app/ to that the system is fooled to think that everything in /system/sd/app is actually in /data/app (which is basically the entire concept behind apps2sd). The only real thing you can do to increase your internal memory is to do the same with the system apps. Go look up the tutorial to symlinking your folders via busybox. Everyone used to have to do that manually before these scripts were out so they should still work. Or you can symlink your data to /system/sd/data/ one or the other. Your choice.
h.nocturna said:
Ugh. Don't worry about it. That's just your data cache taking up space on your /data/ partition. Your apps are still installing to /system/sd/app/ the reason you see them in /data/app is because /data/app/ is symlinked to /system/sd/app/ to that the system is fooled to think that everything in /system/sd/app is actually in /data/app (which is basically the entire concept behind apps2sd). The only real thing you can do to increase your internal memory is to do the same with the system apps. Go look up the tutorial to symlinking your folders via busybox. Everyone used to have to do that manually before these scripts were out so they should still work. Or you can symlink your data to /system/sd/data/ one or the other. Your choice.
Click to expand...
Click to collapse
So....this should work...
ln -s /data /system/sd/app
??
no..... the data is already symlinked properly....
if you want more space, your gonna have to symlink /system/app to /system/sd/app_s
If you install something, it will take up space on your data partition......its the cache
wipe and reflash. youll get the space back and the apps will still be there
you can leave it the way it is though. its not gonna fill up anytime soon. have you also cleared your browser cache? that can take almost 10mb of space under normal usage
should be
ln -s /system/app /system/sd/app_s because as B-man said above, apps2sd is already done for you. This is to move system apps (nandroid before you attempt it)
Alternatively, you can try:
ln -s /data/data /system/sd/data
to move your /data/data folder to /system/sd/data with the above command, but I think there's already a script set up for this that is enabled via editing the user.conf. Its at the top "data2sd" or something like that. Try setting that to "1" before using the symlink. But make sure you already: mkdir /system/sd/data so that it has a folder to symlink to. Never actually tested this feature, so I would nandroid/switchrom before attempting this.
EDIT: Formatting/Clarity
OK, I actually did this:
cd /data/data/com.android.browser/cache
rm -R webviewCache
mkdir /sdcard/webviewCache
ln -s /sdcard/webviewCache webviewCache
Which took care of about 8 MB. So I think I should be good going forward. I saw some other things I can do too, like moving the google maps cache, I think that should help too.
Thanks so much for everything.
rp1783 said:
OK, I actually did this:
cd /data/data/com.android.browser/cache
rm -R webviewCache
mkdir /sdcard/webviewCache
ln -s /sdcard/webviewCache webviewCache
Which took care of about 8 MB. So I think I should be good going forward. I saw some other things I can do too, like moving the google maps cache, I think that should help too.
Thanks so much for everything.
Click to expand...
Click to collapse
Looks good except that I would link it to something on /system/sd/(webviewCache) so that if you decide to mount your sdcard, and use the browser at the same time (for some godforsaken reason) then your phone won't go to hell trying to figure out where to put its cache.