I have looked all over for the answer to this and I am at my wits end...
I have been trying out different roms and themes to find that sweet spot for me, and I think I have now. I know that alt+w on the bootloader only wipes factory data and such, and that if I reformat my sd card it'll wipe everything including my ext2 partition. But I don't want all of that to happen. I want to wipe the apps I have on my sd card but keep the music, movies, etc I have on there without having to uninstall each one thru a file mgr (I have 83 apps right now).
The problem I am having that is making me do this is that when I flash cyan3681 and start over at the adp screen where you tap the android, right after that it starts showing force closes for a number of apps, and it always opens open overclocker and kinda hangs there. On top of all that, at some point, it messed with some apps in my drawer and either won't allow me to access them anymore or it shows the stock apk icon with the little gear and the page behind it.
I just want a fresh start, without having to spend an hour(s?) doing it. Thanks for any help.
run this in terminal
su
rm -rf /system/sd/*
Bzerk1 said:
a question on this, can you use this command in the console of cyanogen recovery 1.4 (alt+X)? and do you stil have to input
su before rm -rf/system..... ?
Click to expand...
Click to collapse
in recovery console just type
mount /system/sd
rm -rf /system/sd/*
alritewhadeva said:
run this in terminal
su
rm -rf /system/sd/*
Click to expand...
Click to collapse
a question on this, can you use this command in the console of cyanogen recovery 1.4 (alt+X)? and do you stil have to input
su before rm -rf/system..... ?
Bzerk1 said:
a question on this, can you use this command in the console of cyanogen recovery 1.4 (alt+X)? and do you stil have to input
su before rm -rf/system..... ?
Click to expand...
Click to collapse
You would be running in recovery console so you would need to use alritewhadeva's method posted a couple posts up:
Do this before the above:
Code:
# mount -o rw /dev/block/mmcblk0p2 /system/sd
Thank you, that worked perfectly.
I am M3 said:
Do this before the above:
Code:
# mount -o rw /dev/block/mmcblk0p2 /system/sd
Click to expand...
Click to collapse
just "/# mount /system/sd" works fine
Adam17 said:
Thank you, that worked perfectly.
Click to expand...
Click to collapse
You're welcome. Please change the thread title to [SOLVED]
Related
Shot me if this was asked before (plenty of gun apps on the market)
What are the Pros and Cons of running the following off the sdcard:
/data/data
/data/app-private
/data/dalvik-cache
I have read that some of you do all of the above to sdcard, some dont.
So I would like to know what you run off your sdcard and why or why not.
Thanks
Pro: Marginally more memory to store your apps.
Con: A dozen threads on the forum every day from newbies who don't know how to search asking how to create an ext2 partition or fix their unbootable device.
jashsu said:
Pro: Marginally more memory to store your apps.
Con: A dozen threads on the forum every day from newbies who don't know how to search asking how to create an ext2 partition or fix their unbootable device.
Click to expand...
Click to collapse
Lmao!!!
I should not laugh I WAS one of them (maybe still am)
Lakers3408 said:
Shot me if this was asked before (plenty of gun apps on the market)
What are the Pros and Cons of running the following off the sdcard:
/data/data
/data/app-private
/data/dalvik-cache
I have read that some of you do all of the above to sdcard, some dont.
So I would like to know what you run off your sdcard and why or why not.
Thanks
Click to expand...
Click to collapse
Pro's - virtually unlimited storage by moving dalvik and cache's
cons - none i have found
DONT MOVE DATA!! Caused all kinds of problems for me. If you move dalvik no need to move data, its a working alternative to moving data.
jashsu said:
Pro: Marginally more memory to store your apps.
Con: A dozen threads on the forum every day from newbies who don't know how to search asking how to create an ext2 partition or fix their unbootable device.
Click to expand...
Click to collapse
haha, and about 10-20 emails a day to me from people on the market asking why my apps to sd program won't work for them. BTW: my app won't allow you to do anything if you don't have the setup right, so you might wanna use it if you're a newbie at this stuff and worried about an unbootable device. Also, I agree with Ryanmo5: moving data SOMETIMES works but even if you do it perfectly sometimes android just doesn't like you.
Ryanmo5 said:
Pro's - virtually unlimited storage by moving dalvik and cache's
cons - none i have found
Click to expand...
Click to collapse
So other than storage on the phone itself, there is no other benefit?
Lakers3408 said:
So other than storage on the phone itself, there is no other benefit?
Click to expand...
Click to collapse
Well put it this way, i have installed 20 plus apps/games since i move dalvik and my storage went down 1 mb. That includes ghwt which is 10mb's installed. Is that not enough of a pro? lol
Ryanmo5 said:
Well put it this way, i have installed 20 plus apps/games since i move dalvik and my storage went down 1 mb. That includes ghwt which is 10mb's installed. Is that not enough of a pro? lol
Click to expand...
Click to collapse
Im sold!!... Doing it now, Thanks for the advice.
Ok having a bit of an issue
How EXACTLY do I need to type the command in Terminal?
I dont want to mess things up and have to re-install all my (75) apps/games.
Thanks
1) reboot and backup!
2) connect phone and don't mount
3) Command Prompt:
4) adb shell
5) #mkdir /system/sd/dalvik-cache
6) #busybox cp -a /data/dalvik-cache /system/sd/dalvik-cache
7) #rm -R /data/dalvik-cache
8) #ln -s /system/sd/dalvik-cache /data/dalvik-cache
9) #reboot
Ryanmo5 said:
1) reboot and backup!
2) connect phone and don't mount
3) Command Prompt:
4) adb shell
5) #mkdir /system/sd/dalvik-cache
6) #busybox cp -a /data/dalvik-cache /system/sd/dalvik-cache
7) #rm -R /data/dalvik-cache
8) #ln -s /system/sd/dalvik-cache /data/dalvik-cache
9) #reboot
Click to expand...
Click to collapse
Thanks for the instructions a real help.
I did #5 and #6 then got a call in the middle of doing this and my phone rebooted.
So then after the reboot I did #7, #8 and #9.
Now how will I know it everything worked???
I forgot to check my phone memory before doing this so I cant really tell if my phone memory incressed.
Easy way to tell is get the my account app from t mobile in market. Then hit phone on top. It will tell you how much storage you have. In terminal emulator type in
su
ls -l /system/sd
dalvik should be in list, if it is your good to go. If you ever want to reverse type in
rm /data/dalvik-cache; cp -a /system/sd/dalvik-cache /data/dalvik-cache
Remember that phone can only hold so much so storage if reversed.
If I delete the /data/dalvik-cache folder from the phone will it recreate itself. From what I'm reading this may assist in fixing my phone boot errors.
Don't think it will cause a problem. You can try rebooting after removing the files (dalvik).
I would recommend deleting it in Counsole just because it'd be safer for all your apps and processes, but it should be recreated in Android's framework.
needed to remove /data/dalvik-cache
Metatronx said:
If I delete the /data/dalvik-cache folder from the phone will it recreate itself. From what I'm reading this may assist in fixing my phone boot errors.
Click to expand...
Click to collapse
thanks this was just what I needed... I was having the same error with the first boot as you had in some of your earlier comments in the thread. used adb to connect and remove the dalvik-cache file and then reboot... the next reboot nicely passed the 'G1' screen...and looks like my g1 may be back and running... if the endless force closes ever end
lukekirstein said:
I would recommend deleting it in Counsole just because it'd be safer for all your apps and processes, but it should be recreated in Android's framework.
Click to expand...
Click to collapse
How do you do that?
ThR1LL said:
How do you do that?
Click to expand...
Click to collapse
reboot in recovery
alt X to go into counsol
hit enter to get in SU mode
if you don't have apps2sd
mount data
rm -r data/dalvik-cache
reboot
if you have apps2sd
mount system/sd
rm -r system/sd/dalvik-cache
reboot
Good luck
borodin1 said:
if you have apps2sd
mount system/sd
rm -r system/sd/dalvik-cache
reboot
Good luck
Click to expand...
Click to collapse
is it the same commands in adb?
So I have an old file left over that I never got rid of when I set up swap on Cyan 3.6.8.1 or whatever.
Since if I remember correctly swap/compcache is set up by default on the newer versions should I get rid of that old userinit file? If so how would I go about doing that from the console in recovery?
if you have no userinit.sh then compache is done by default in his newer builds
try
Code:
su
mount -o rw /dev/block/mmcblk0p2 /system/sd
rm /system/sd/userinit.sh
reboot
though just on general principle of the app i would get root explorer from the market bc you can access /system/sd from it and delete whatever you want while not having to do any terminal commands
Thanks!
Yaboiaj said:
Thanks!
Click to expand...
Click to collapse
your are welcome
something weird happened on my phone when I installed the SuperD 1.9.3 rom. I've never had this problem before, so see if you can help me. I installed Chompsms and Acontacts amongst a variety of other apps. Well, I was texting earlier, when my phone froze. No biggy, I popped the battery out, placed it back in, and turned it on. Well I got the green boxes in place of the the logos for Chomp and Acontacts. I clicked on them and it said that the apps weren't installed? um, ok. I have aps2sd with ext3, so I figure something must have corrupted the file, no biggy, I'll just redownload it. So I go to the market, and it says the program is installed. I click on the program to try to reinstall, and the bottom where it says "open, uninstall" are greyed out. So the app isn't installed, but it is, so I can't uninstall and re-install. Anyone, help please? I really use these 2 apps!
Delete the apk's from /system/sd/
It also sounds like your marketdb file is still there too. I've had this problem with Backup for root users. It'll import the marketdb but sometimes it won't import the APK's. So that leaves you with no apps and the market seeing that you already have it. I'm trying to find where the program is pulling that file, and i'll let you know. If anyone else knows where it's at feel free to jump in.
nolimit78 said:
If anyone else knows where it's at feel free to jump in.
Click to expand...
Click to collapse
/data/data/ I think.
evilkorn said:
/data/data/ I think.
Click to expand...
Click to collapse
That's what I was thinking but I didn't see it there...
While Im still looking for that file, you could also do the following:
Code:
Use switchrom and save your rom
flash a new rom
download the apks that are giving you problems (if its not too many)
use linda to save the apks to your SD card
switchrom back to the old rom
download and use linda to install the apks you saved.
It's not pretty but it'll get the job done.
Had a little time to look at the phone, did you try to delete the folder in /data/data/com.android.vending/?
Goto terminal emulator.
Type - mount -o remount,rw /dev/block/mtdblock3 /system (enter)
Type - rm /data/data/com.android.vending/databases/* (enter)
Type - reboot (enter)
Words in bracket are instructions and not to be typed.
shadowch31 said:
Goto terminal emulator.
Type - mount -o remount,rw /dev/block/mtdblock3 /system (enter)
Type - rm /data/data/com.android.vending/databases/* (enter)
Type - reboot (enter)
Words in bracket are instructions and not to be typed.
Click to expand...
Click to collapse
yeah I found that it was in the vending/databases folder, I just hadn't had time to post until now. Good job!
i had the same problem and it worked...at first the terminal emulator went like 'are you root' and im like whaaat...i have cynogen 4.2.14.1...so had to type su before the 3 lines of codes...it worked
In the latest cm9 nightly build - update-cm-9-20120419-NIGHTLY, my wifi is not work with my own kernel.
So, I checked the catalog, and found this: wifi modules was changed.
http://review.cyanogenmod.com/#/c/14910/1/BoardConfigCommon.mk
old path: /system/modules/bcm4329.ko
new path: /system/lib/modules/bcm4329.ko
It will cause your wifi not work with custom kernel.
If your wifi is not work, just make a symbol link, type these command in the terminal:
su
mount -o remount,rw /system
ln -s /system/modules/bcm4329.ko /system/lib/modules/bcm4329.ko
#Thanks Paragon_X, I forgot to tell you to remount /.
mount -o remount,ro /system
Or, you are the kernel developer, your should put your kernel modules in both path, or link them.
Thanks
I confirm this change as well and the fix worked.
I have the wifi authentication problem. Do I flash the download link from the link you posted?
Paragon_X said:
I have the wifi authentication problem. Do I flash the download link from the link you posted?
Click to expand...
Click to collapse
That is not a download link, its a Git review...
Sent from my Nexus S using Tapatalk 2
DaXmax said:
That is not a download link, its a Git review...
Sent from my Nexus S using Tapatalk 2
Click to expand...
Click to collapse
Okay thanks so regarding the command written... is there spaces in there or am I seeing things?
ln -s /system/modules/bcm4329.ko /system/lib/modules/bcm4329.ko
I'm not familiar with typing in superuser so I have to ask
There are spaces.
If you are unfamiliar with the spaces, then you will be unfamiliar with the before and after commands around that command too:
mount -o remount,rw /system
and
mount -o remount,ro /system
Thanks for the fix!
Sent from my Nexus S using XDA
Thanks that will be handy for surprised users, if CM actually thought things through, they would link the dirs to allow a transition time where kernels work with modules in old location and new location.
Sent from my Galaxy Nexus
Hi,im kinda really noob at this stuff atm but do we type this in command prompt or terminal emulator (or any other program like that). And can someone confirm the code is:
su
mount -o remount,rw /system
ln -s /system/modules/bcm4329.ko /system/lib/modules/bcm4329.ko
#Thanks Paragon_X, I forgot to tell you to remount /.
mount -o remount,ro /system
the "fix" is included in the latest trinity kernels. wifi works with the newest cm9(nightlies and kangs), older cm9, and every other rom.
simms22 said:
the "fix" is included in the latest trinity kernels. wifi works with the newest cm9(nightlies and kangs), older cm9, and every other rom.
Click to expand...
Click to collapse
Im using matrix kernel v19 cfs and the latest CM9 v7. Trying to get the wifi working now and its hard.
Heres what i have done using terminal emulator
Typed in "su". Pressed enter. I granted super user permissions.
Typed in "mount -o remount,rw /system" . Pressed enter. Didnt say anything
Typed in "ln -s /system/modules/bcm4329.ko /system/lib/modules/bcm4329.ko". Pressed Enter
It showed up "link failed File exists"
now its changed to "255|[email protected]:/". Before it was "[email protected]:/"
I than typed in "mount -o remount,ro /system"
My wifi still doesnt work
I'll reply here to. The reason you can not link (ln) is that there is a file where you are trying to add a "shortcut" just remove the bcm*.ko file in /system/lib/modules and copy the module from /system/modules there. I used root explorer then it's just cut and paste
Sent from my Nexus S using Tapatalk 2
TigaTiger said:
Im using matrix kernel v19 cfs and the latest CM9 v7. Trying to get the wifi working now and its hard.
Heres what i have done using terminal emulator
Typed in "su". Pressed enter. I granted super user permissions.
Typed in "mount -o remount,rw /system" . Pressed enter. Didnt say anything
Typed in "ln -s /system/modules/bcm4329.ko /system/lib/modules/bcm4329.ko". Pressed Enter
It showed up "link failed File exists"
now its changed to "255|[email protected]:/". Before it was "[email protected]:/"
I than typed in "mount -o remount,ro /system"
My wifi still doesnt work
Click to expand...
Click to collapse
same problem here, also when i use any root explorer ( free ) i cant get permision to do this, and i have rooted my phone... anyone knows why ?
Sejmir said:
same problem here, also when i use any root explorer ( free ) i cant get permision to do this, and i have rooted my phone... anyone knows why ?
Click to expand...
Click to collapse
Mount /system as R/W (read-write) first.
kong said:
Mount /system as R/W (read-write) first.
Click to expand...
Click to collapse
didnt quite get you, but il google it tnx for the tip m8
Thanks! Wi-Fi now working. Very simple. Just copy & paste to new lib/modules location using root explorer.
Beamed from my Nexus S using Tapatalk 2
Sejmir said:
didnt understand you, mount /system in recovery then run emulator or root explorer or smthing else ?? sry im totaly new to androids, but never too late to learn new things
anywys have a lots of googling to do, coz il learn how to do this via adb shell...
Click to expand...
Click to collapse
root explorer has an option in the top of the screen, mount r/w. press it, it will now say mount r/o, thats what you want.
skitapa said:
I'll reply here to. The reason you can not link (ln) is that there is a file where you are trying to add a "shortcut" just remove the bcm*.ko file in /system/lib/modules and copy the module from /system/modules there. I used root explorer then it's just cut and paste
Sent from my Nexus S using Tapatalk 2
Click to expand...
Click to collapse
I still have no luck. Is the error everyone getting the authentication problem? and simply wifi indicator wont popup?
For all the people who dont get this too well, especielly me. Could an experienced, someone who knows this, write out the complete instructions and codes to do it. Preferably in detail because some of us have no idea what we are suppose to do. And suggest what type of programs we should be using. thanks in advance.
Ok. Let's take it from the start. When android boots it loads the kernel to handle all the drivers and inner workings of the OS. It also loads modules, that's optional drivers loaded on demand. Now CM9, used to load it's modules from /system/modules but has changed it's location to /system/lib/modules. This is new to the people making custom kernels which kernel installs it's modules in the wrong place. This makes the new kernel try to load the old module but fails because of different kernel source versions. Now, our task is to move the new module in /system/modules to /system/lib/modules overwriting the old one.
Start a terminal.
Type su and enter to become superuser which is the only user with rights to change system files.
Now if there is a box asking you to allow this, press allow.
Now type:
mount -o remount, rw /system
This will make the system folder and child folders writable.
type:
rm /system/lib/modules/bcm*
That will remove the old module.
Type:
cp /system/modules/bcm* /system/lib/modules
Reboot and it should work.
Sent from my Nexus S using Tapatalk 2