apps2sdcard removing problem - G1 Q&A, Help & Troubleshooting

Hello, I followed this guide: http://wiki.cyanogenmod.com/index.php/Removing_Apps2SD
It says:" Then proceed to the ADB instructions from after 'adb shell' " so I jumped those steps:
Code:
adb remount
adb shell
Why are they shown anyway if you have to jump them?
Then
Code:
rm /data/dalvik-cache
did not work so i used
Code:
rm -r /data/dalvik-cache
instead but it also did not work because the dir was busy. Any ideas?
Thank you very much.

Wait, what are you trying to do, remove the apps2sd function? If so backup the contents of your card, format it and copy the contents back. You'll be without an ext partition so the phone will have to install apps to the nand.

Yes, thanks. But Apps2SDCard will be reinstalled of course.

What? You need to be more clear on what you want to achieve.... if you dont have an EXT partition, apps2sd is disabled.

Related

How to remove (live)wallpaper

I can't find a thread for this, but how would I delete stock wallpapers or stock live wallpapers. I prefer to pick and choose which ones to remove to try and save a little space.
I have a rooted N1 with Cyan's mod. I'm comfortable using ADB, just don't know the proper commands, locations of wallpapers or names of specific files.
Me too. want to know where the files are located.
Me three. I've searched around in nearly every directory and cannot find them. I would like to remove the stock htc wallpapers to save space.
adb shell rm /system/app/LiveWallpapers.apk
adb shell rm -r /data/data/com.android.wallpaper
adb uninstall com.android.wallpaper
adb shell rm /system/app/MagicSmokeWallpapers.apk
adb shell rm -r /data/data/com.android.magicsmoke
adb shell rm /system/app/VisualizationWallpapers.apk
adb shell rm -r /data/data/com.android.VisualizationWallpaper
adb uninstall com.android.VisualizationWallpaper
adb shell rm /system/app/Mode10Wallpapers.apk
LiveWallpapers.apk = contains nexus and water live wallpaper and some other i cant remember
wallpapers are located inside of /system/framework/framework-res.apk and does require slight knowledge of how to edit framework files
hey i follow the first adb then i got this (?) then no go???what i need to do after (?)
vinny.1967 said:
hey i follow the first adb then i got this (?) then no go???what i need to do after (?)
Click to expand...
Click to collapse
Check if ur phone is detected by adb (adb devices). Then do an adb remount and the run the above adb commands
My device is detected but i try to put in the above commands I it says that its a read-only file system.
Static wallpapers (except the single default wallpaper) are stored in your launcher or in CM6 or Kang-o-rama a special wallpapers app.
It's much easier to download ES File Explorer, turn on root functions, mount system as read/write (same menu) and selectively delete the files you want from /system/app/ and /data/data/ as above.
But really, you're not going to save any user space as all because, for the most part, you're deleting stuff from /system which you don't otherwise need space on.

app2sd for spica

this is app2sd for spica, i'm using xjd1 firmware (eclair 2.1) + root_lkupdate_v3_pda
first, I will not responsible for any damage of your device...
you will need a partitioned sdcard, just use paragon partition manager to create fat32 and ext2 partition, create fat32 first then ext2
it's recommended that you use at least class 4 microsd...
here it is:
#mount -o remount,rw,codepage=utf8,vfat,xattr,check=no /dev/stl6 /system
#busybox df -h --> make sure /sdcard is on /dev/block//vold/179:1
#cd / --> go to root directory
#mkdir /system/sd
#mount -t ext2 /dev/block/mmcblk0p2 /system/sd
#busybox df -h --> make sure /dev/block/mmcblk0p2 is mounted on /system/sd, if the mounting process fails you can't continue...
#mkdir /system/sd/app
#cd /data/app
#cp * /system/sd/app <-- if you do fresh firmware update, skip this step
#cd /data
#rm -r app
#ln -s /system/sd/app /data/app
basically app2sd is ended here, but you will lost app2sd every phone reboots, so you'll need to edit install-recovery.sh, add "mount -t ext2 /dev/block/mmcblk0p2 /system/sd" in the last line...or simply download edited install-recovery.sh here: http://cid-c4b7e1a837cca944.skydrive.live.com/self.aspx/.Public/install-recovery.sh
install-recovery.sh is meant to autorun app2sd when phone reboots...
#cd /system
#chmod 0777 etc
#mv /system/etc/install-recovery.sh /system/etc/install-recovery.old --> backup the oiriginal install-recovery.sh
#exit
$exit
prompt>adb push install-recovery.sh /system/etc --> push downloaded install-recovery.sh to spica, don't turn off phone if pushing install-recovery fails!!!
if you wan't to turn off your phone you'll need to type:
#mv /system/etc/install-recovery.old /system/etc/install-recovery.sh
to restore install-recovery.sh to the original one...then you can safely turn off your spica...
prompt>adb shell
$su
#cd /system
#chmod 0755 etc
#chmod 0755 etc/install-recovery.sh
reboot to check if it works...
I will try to answer any questions you may have about the tut here but be forewarned, I'm no guru when it comes to this stuff. Therefore, if a question is asked that I can't answer, it would be appreciated if someone else who can does so.
I successfully allocated 560mb for /data/app
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
this credited to mboisker
Update:
it seems live wallpaper not working for me after using app2sd, it always force closed
don't know the problem, maybe the microsd is causing the problem...
nice work!!!
please ignore
ok so i have found me a free copy of paragon and have partitioned to fat32. how would i then create ext2 on the sdcard? ive been looking through the program and am not seeing how to creat ext2. Suggestions? I use win7 32bit. Thanks
johnnywhojr said:
ok so i have found me a free copy of paragon and have partitioned to fat32. how would i then create ext2 on the sdcard? ive been looking through the program and am not seeing how to creat ext2. Suggestions? I use win7 32bit. Thanks
Click to expand...
Click to collapse
first you need to delete all partition...
now, create fat32 partition first, specify how much mb you want to create for fat32
and then create partition again, choose ext2 for file system...
that's all...
darkcell said:
first you need to delete all partition...
now, create fat32 partition first, specify how much mb you want to create for fat32
and then create partition again, choose ext2 for file system...
that's all...
Click to expand...
Click to collapse
i have allocated 5gb for fat32. but when i attempt to partition to ext2, my only choices are 'not formatted' or 'fat16' or 'fat32' or 'apple hfs'
so im close but just not there. lol
johnnywhojr said:
i have allocated 5gb for fat32. but when i attempt to partition to ext2, my only choices are 'not formatted' or 'fat16' or 'fat32' or 'apple hfs'
so im close but just not there. lol
Click to expand...
Click to collapse
what version your paragon?
try to install version 10
darkcell said:
what version your paragon?
try to install version 10
Click to expand...
Click to collapse
ive downloaded 2010 free edition and demo edition. i am also inprocess of 9.0 professional. so, once that is done and installed i will try again. looks like a little trial and error til i get it. thanks for the replys and point in the right direction!
UPDATE: So i dl'd 9.0 pro. and it worked to create ext2 on the sdcard. so now i will attempt this again and go from there. again thanks for the help.
2nd update:
#mkdir /system/sd/app
#cd /data/app
#cp * /system/sd/app <-- if you do fresh firmware update, skip this step
#cd /data
#rm -r app
#ln -s /system/sd/app /data/app
got to #rm -r app and it deleted all my apps and wouldnt allow me to carry on. so i would assume that this should be done using adb?
That's wonderful !
Would it be possible to store some apps on the SD card, and let others in the phone's memory ?
Thanks in advance
johnnywhojr said:
ive downloaded 2010 free edition and demo edition. i am also inprocess of 9.0 professional. so, once that is done and installed i will try again. looks like a little trial and error til i get it. thanks for the replys and point in the right direction!
UPDATE: So i dl'd 9.0 pro. and it worked to create ext2 on the sdcard. so now i will attempt this again and go from there. again thanks for the help.
2nd update:
#mkdir /system/sd/app
#cd /data/app
#cp * /system/sd/app <-- if you do fresh firmware update, skip this step
#cd /data
#rm -r app
#ln -s /system/sd/app /data/app
got to #rm -r app and it deleted all my apps and wouldnt allow me to carry on. so i would assume that this should be done using adb?
Click to expand...
Click to collapse
no, before you rm -r app, you should cp * /system/sd/app as told in above steps, so the applications still there in /system/sd/app, and now link the app to /data/app/ with ln -s /system/sd/app /data/app
so the /data/app is basically just a link to /system/sd/app now since it has been removed...
That's wonderful !
Would it be possible to store some apps on the SD card, and let others in the phone's memory ?
Thanks in advance
Click to expand...
Click to collapse
no it's not possible, the apps only installed on sdcard now...
darkcell said:
no, before you rm -r app, you should cp * /system/sd/app as told in above steps, so the applications still there in /system/sd/app, and now link the app to /data/app/ with ln -s /system/sd/app /data/app
so the /data/app is basically just a link to /system/sd/app now since it has been removed...
Click to expand...
Click to collapse
I printed the instructions out and followed step by step. i wi ll however try again. lol i really dont mind flashing my phone again. i like the trial and error part. i did exactly as mentioned.
d
UPDATE: Just attempted this again and again my phone crashed. are you sure its rm first then ln or is it ln first then rm? also does it matter that i'm using a latest firmware from samsung-firmwares?
lol i think i know what happened. is that it may have copiued my files over before i could ln them
johnnywhojr said:
lol i think i know what happened. is that it may have copiued my files over before i could ln them
Click to expand...
Click to collapse
No, the instructions are correct. They copy the files over, remove them from their original location & finally link the now empty source directory to point to the new app filled directory on the sdcard.
If you tried to do it the other way around & created the link first you'd no longer be able to access the apps in /data/app in order to copy them to the sd card.
Why don't you try the process from scratch after a nandroid restore & then cut & paste the entire sequence of commands & their output into this thread?
lol...too late. have already reflashed. may attempt again. i usuallly delete all stock apps anyways to clear space using root explorer or through connectbot. what my problem was as soon as i typed in rm -r app, everything went funny and lost my terminal. so i could ln -s /system/sd/app /data/app. so not sure why that happened. lol, once i get that figured, i still need to figure out the next step. lol i dont mind the trial and error. its a lot more exciting than a damn blackberry or iphone.
johnnywhojr said:
lol...too late. have already reflashed. may attempt again. i usuallly delete all stock apps anyways to clear space using root explorer or through connectbot. what my problem was as soon as i typed in rm -r app, everything went funny and lost my terminal. so i could ln -s /system/sd/app /data/app. so not sure why that happened. lol, once i get that figured, i still need to figure out the next step. lol i dont mind the trial and error. its a lot more exciting than a damn blackberry or iphone.
Click to expand...
Click to collapse
do you use terminal in the phone? or adb shell via PC?
terminal in the phone. i havent figured out adb. i do however have sdk installed. lol havent had this spica more than a month and its been flashed about 10 times...lolol. i'm learning as i go. slowly figuring this out.
johnnywhojr said:
terminal in the phone. i havent figured out adb. i do however have sdk installed. lol havent had this spica more than a month and its been flashed about 10 times...lolol. i'm learning as i go. slowly figuring this out.
Click to expand...
Click to collapse
you can't do app2sd via phone terminal, it's for adb shell...
lol yup found that out. twice. lol
darkcell said:
you can't do app2sd via phone terminal, it's for adb shell...
Click to expand...
Click to collapse
What makes you think that? All it involves is moving some files, creating a symbolic link & editing one other file. That said, I'd use adb if I was at my PC, if only because it gives me a proper keyboard & decent sized terminal.
cauli said:
What makes you think that? All it involves is moving some files, creating a symbolic link & editing one other file. That said, I'd use adb if I was at my PC, if only because it gives me a proper keyboard & decent sized terminal.
Click to expand...
Click to collapse
Would you mind explaining how this could be done using terminal without losing anything?

How to undo mimocam's lag fix.

Hi people!
I'd like to install one click lag fix, but i already had mimocam's lag fix applied and i cant, so....
How can i undo mimocams lag fix?
P.d: i used the search, but nothing found......thanks!
Sent from my GT-I9000 using Tapatalkthing
adb shell
su
busybox rm /data/data
busybox cp -rp /disk/data /data/
busybox rm /data/data.bak
busybox rm -r /disk/data
The first command puts you into the command line on the phone.
the second line gives you root access
the third line removes the soft symlink that we created in the original instructions
the fourth line copies the stuff from your ext partition back to the phone
the fifth line deletes the backup of your original data partition you made
the sixth line deltes the data partition on your ext partition - this is optional step and BE SURE your cp in line four was successful first.
We could alternately just mv the /data/data.bak back to /data (busybox mv /data/data.bak /data/data) after removing the symlink, but that would put your /data/data folder back to where it was before you started, so any app changes you made while residing on ext partition would be lost.
Use the same procedures to undo the market fix stuff.
distortedloop said:
Use the same procedures to undo the market fix stuff.
Click to expand...
Click to collapse
hey... could you elaborate on that?
thanks,
thomas
EDIT: I have found this here:
Code:
adb shell
su -
busybox rm /data/data
busybox rm /system/media
busybox cp -rp /disk/data /data/
busybox cp -rp /disk/media /system/
Am I safe to assume that if I've done a hard reset and flashed a new firmware it will have removed the fix? Or do I still need to undo it?
tschmidt84 said:
hey... could you elaborate on that?
thanks,
thomas
EDIT: I have found this here:
Code:
adb shell
su -
busybox rm /data/data
busybox rm /system/media
busybox cp -rp /disk/data /data/
busybox cp -rp /disk/media /system/
Click to expand...
Click to collapse
Don't forget to rm the .bak folder for /system/media.bak if you have it, otherwise you're wasting disk space.
Nicolopolus said:
Am I safe to assume that if I've done a hard reset and flashed a new firmware it will have removed the fix? Or do I still need to undo it?
Click to expand...
Click to collapse
Yes, any new firmware flash should wipe these fixes. However, your ext partition will still have the apps and other stuff on it. Not an issue since you can't use that space without running a lag-fix kernel that mounts it, or you repartition the sdcard.
last question: when I try to rm the data.bak, it tells me: "data.bak is a folder!"... what is that about?
tschmidt84 said:
last question: when I try to rm the data.bak, it tells me: "data.bak is a folder!"... what is that about?
Click to expand...
Click to collapse
When you did the fix in the first place it backed up the original folder by renaming it to .bak, so it is a folder, it's the original /data/data folder that you had before doing the fix!
You might have to use rm -r to remove it, or to be really safe, just use Root Explorer or the like and delete it.
Pretty easy to screw up your phone if you mistype with the rm or rm -r.

[How To] Remove WebTopMod without root! [How To]

Since I was looking to be able to update my phone, I had to remove the WebtopMod. Since the previous instructions required me to root my phone to remove it, which was counterproductive because it would mean loosing the ability to update anyway. I looked through the WebtopMod installation scripts and came up with this guide to remove it:
View attachment WebtopModRemoveGuideNoRoot.txt
Note: I've attached the guide in a separate file, because the forum is stupid and thinks that exe, bak, odex, apk, and dex are valid TLD's and says I can't post external links. If I ever get "approximately eight" posts I'll put it in this post.
If you don't have the original backup files, look in page 3 of the howto post for removing it with root. (Thanks, MotoAtrixFan for posting it and twoeleven99 for alerting me to this)
Happy Updating!
eliplan312 said:
Since I was looking to be able to update my phone, I had to remove the WebtopMod. Since the previous instructions required me to root my phone to remove it, which was counterproductive because it would mean loosing the ability to update anyway. I looked through the WebtopMod installation scripts and came up with this guide to remove it:
View attachment 556542
Note: I've attached the guide in a separate file, because the forum is stupid and thinks that exe, bak, odex, apk, and dex are valid TLD's and says I can't post external links. If I ever get "approximately eight" posts I'll put it in this post.
If you don't have the original backup files, look in page 3 of the howto post for removing it with root. (Thanks, MotoAtrixFan for posting it and twoeleven99 for alerting me to this)
Happy Updating!
Click to expand...
Click to collapse
you can update even if you are rooted you cant update only when you modify the /system or some apps
went step by step through your guide and I still cannot update - the apply_patch_check still fails at DockProvider.apk - aside from reflashing the stock SBF, what do you recommend?
Try this
Try setting the phone to usb mass storage mode and replacing the files in the WebtopModBackup folder on the sd/media area with these: View attachment WebtopModBackup.zip
The files in the archive worked for me, not sure why it wouldn't work. If those don't work for you, please post the console log.
eliplan312 said:
Try setting the phone to usb mass storage mode and replacing the files in the WebtopModBackup folder on the sd/media area with these: View attachment 556596
The files in the archive worked for me, not sure why it wouldn't work. If those don't work for you, please post the console log.
Click to expand...
Click to collapse
Thanks, but something appears to be totally screwed up on my DockProvider and DockService applications on Titanium Backup - they are listed at the bottom with grey slashes through them. The crazy part is.... it works with the webtop hack, but the update doesn't see the correct files, so something is obviously messed up.
Now, by putting the files from the WebtopModBackup on the phone, shouldn't that fix the issue? Then perform the steps in your text doc? I can't believe I'll have to SBF stock in order to fix the stupid DockProvider and DockService!!
What I meant was, replace the files in the WebtopModBackup folder with the stuff in the archive, then re-do the instruction in the text file.
I'm sorry but your instructions aren't working for me. I've followed your instructions very carefully but when I get to the command
cd /mnt/sdcard/WebtopModBackup
I get a directory not found error.
I can change to /mnt/sdcard but when I type 'ls' nothing appears. The directory is empty.
What am I doing wrong?
One thing I've noticed is that when I enter the 'adb.exe shell ./data/local/tmp/psneuter' command, the phone appears to dismount and remount and then when I go into the shell the '/mnt/sdcard' directory is empty.
Yeah I'm also having that problem....I'm trying to push the backup files into the correct folder. However, when I get a read-only error, so from what I read I'm supposed to reboot into recovery mode. When I try to do this the recovery console says e: can't open/cache/recovery/command and I can't connect to my phone. Any help?
To start I want to say Thank you to the OP for posting this. But there are a few errors, so I hope I can help.
To anyone having issues with this, there are a few things that you must have to make this work.
Note this only works for AT&T Atrix as I do not have a Bell Atrix
#1; THE 1st PART DOES NOT WORK if you performed the update. You should be rooted. You can check to see if you updated by pressing menu --> settings --> about phone and your Build version says something like OLYFR_U4_1.5.7 it will not work, you need to skip down to my next post of my coding since you should already be rooted. The 1st part of this uses the method that made rooting possible, since that was removed with the update, it no longer applies. So if you are updated, you should already be rooted and can skip a few steps
#2; You must have a folder called WebTopModBackup with the .bak files in it on the internal memory (not your memory card but the fake internal one). Open the app called Files, select Internal phone storage, select the WebTopModBackup folder and make sure you see the following files, if not you need to get them
Code:
DockProvider.apk.bak
DockProvider.odex.bak
DockService.apk.bak
DockService.odex.bak
PortalApp.apk.bak
PortalApp.odex.bak
#3; Do not mount your sdcard. When you plug in your USB cable to the compter, pull down the drop menu, select the USB connection and make sure None is selected; then press ok. If one of the other options are selected, select None press ok and wait for 30 seconds for the internal and external cards to mount. @Phazoni more than likely this is your issue
#4; USB debugging must be turned on. Press menu --> settings --> applications --> development --> and check USB debugging if not checked
#5; Make sure you have at least 50% battery, just in case
#6; During the steps you mount (make it editable) the /system folder where the files are, if you get a read-only error you did not do step
mount -o rw,remount /dev/block/mmcblk0p12 /system
correctly or your phone is somehow not rooted.
Click to expand...
Click to collapse
Ok now let's look at the code in the OP
Code:
adb.exe push psneuter /data/local/tmp
adb.exe shell chmod 755 /data/local/tmp/psneuter
adb.exe shell ./data/local/tmp/psneuter
adb.exe shell
adb.exe push is the command to copy a file to your phone; so we are making a copy of psneuter and putting it on the phone.
adb.exe shell chmod 755 this gives premission to the phone to use the psneuter file
adb.exe shell ./ this makes the psneuter file run and creates a fake root
adb.exe shell this should really be typed as adb shell but whatever. This takes you into the phone's system to edit the files. While in adb, the line should start with a # if it is a $ then psneuter did not work. Just to try, type su and see if the $ changes to a # if it does continue
Code:
cd /mnt/sdcard/WebtopModBackup
This command takes you to the location of your backup, remeber step 2 & 3, if this folder is empty and you cannot get to it, you have an issue there
Code:
mv DockProvider.apk.bak DockProvider.apk
mv DockProvider.odex.bak DockProvider.odex
mv DockService.apk.bak DockService.apk
mv DockService.odex.bak DockService.odex
mv PortalApp.apk.bak PortalApp.apk
mv PortalApp.odex.bak PortalApp.odex
Personally this is not the best way to do this (rename the files by making copies and then making more copies), but not my code. The mv command moves a file. In this case you are only using it to rename the files removing the .bak from the end. See my code at the bottom
Code:
mount -o rw,remount /dev/block/mmcblk0p12 /system
This mounts the /system folder so you can edit the system files
Code:
cp DockProvider.apk /system/app/
cp DockProvider.odex /system/app/
cp DockService.apk /system/app/
cp DockService.odex /system/app/
cp PortalApp.apk /system/app/
cp PortalApp.odex /system/app/
This code copies the files into the original locations as the correct name. This assumes you are still in the folder where the backups are. If this fails, the /system folder is not mounted, the files are missing or you are in a different folder. This is also missing the chmod /system/app/* coding. I will cover that below
Code:
rm /data/dalvik-cache/[email protected]*.dex
rm /data/dalvik-cache/[email protected]*.dex
rm /data/dalvik-cache/[email protected]*.odex
rm /data/dalvik-cache/[email protected]*.odex
rm is the command to remove/delete a file, running these 4 commands will remove the system cache and will most likely cause your phone to reboot before the next step; that is ok.
Code:
reboot now
This reboots the phone and removes the temp root.
Click to expand...
Click to collapse
See my next post for my coding
AGAIN
Note this only works for AT&T Atrix as I do not have a Bell Atrix
#1; THE 1st PART DOES NOT WORK if you performed the update. You should be rooted. You can check to see if you updated by pressing menu --> settings --> about phone and your Build version says something like OLYFR_U4_1.5.7 it will not work, you need to skip down to my next post of my coding since you should already be rooted. The 1st part of this uses the method that made rooting possible, since that was removed with the update, it no longer applies. So if you are updated, you should already be rooted and can skip a few steps
#2; You must have a folder called WebTopModBackup with the .bak files in it on the internal memory (not your memory card but the fake internal one). Open the app called Files, select Internal phone storage, select the WebTopModBackup folder and make sure you see the following files, if not you need to get them
Code:
DockProvider.apk.bak
DockProvider.odex.bak
DockService.apk.bak
DockService.odex.bak
PortalApp.apk.bak
PortalApp.odex.bak
#3; Do not mount your sdcard. When you plug in your USB cable to the compter, pull down the drop menu, select the USB connection and make sure None is selected; then press ok. If one of the other options are selected, select None press ok and wait for 30 seconds for the internal and external cards to mount. @Phazoni more than likely this is your issue
#4; USB debugging must be turned on. Press menu --> settings --> applications --> development --> and check USB debugging if not checked
#5; Make sure you have at least 50% battery, just in case
#6; During the steps you mount (make it editable) the /system folder where the files are, if you get a read-only error you did not do step
mount -o rw,remount /dev/block/mmcblk0p12 /system
correctly or your phone is somehow not rooted.
Click to expand...
Click to collapse
NOW for my recommended coding
After you follow my 6 steps above do the following
#1. on your compter press start --> run --> Type cmd this will open the command prompt for windows. Then navigate to the folder where the original WebTopMod files are located.
#2a. If are rooted jump down to step 4
#2. If you are not rooted and have not updated your phone type the following letter for letter
Code:
adb push psneuter /data/local/tmp
adb shell
You will now be in the ADB shell.
#3. You should see a $ so type the following
Code:
chmod 755 /data/local/tmp/psneuter
./data/local/tmp/psneuter
#4 This will kick you out of ADB, wait for it and when it does count to 30 for adb to reset. Now type the following:
Code:
adb shell
#5. You should see the # sign, if you see $ type su to change it since you should be rooted either by rooting the phone or using steps 1-3 above for pre-update.
Code:
mount -o rw,remount /dev/block/mmcblk0p12 /system
cp /mnt/sdcard/WebtopModBackupDockProvider.apk.bak /system/app/DockProvider.apk
cp /mnt/sdcard/WebtopModBackupDockProvider.odex.bak /system/app/DockProvider.odex
cp /mnt/sdcard/WebtopModBackupDockService.apk.bak /system/app/DockService.apk
cp /mnt/sdcard/WebtopModBackupDockService.odex.bak /system/app/DockService.odex
cp /mnt/sdcard/WebtopModBackupPortalApp.apk.bak /system/app/PortalApp.apk
cp /mnt/sdcard/WebtopModBackupPortalApp.odex.bak /system/app/PortalApp.odex
chmod 644 /system/app/*
rm /data/dalvik-cache/[email protected]*.dex
rm /data/dalvik-cache/[email protected]*.dex
rm /data/dalvik-cache/[email protected]*.odex
rm /data/dalvik-cache/[email protected]*.odex
reboot now
This
1. mounts the /system folder so you can replace the files then
2. renames nd copies the back-up files to the original locations in one step
3. Then the chmod 644 command sets the correct premissions for the files so they work,
4. clears the cache and
5. reboots the phone.
Click to expand...
Click to collapse
I hope this helps anyone stuck

[Q] Problem SDCARD0 Permisions On Ofical CM12.1 Xperia T Mint

Hi have this CM installed on my Xperia T:
12.20150616-nightly-mint
It works fine but APPS cant write to Internal Memory (SDACRD0), the camera doesn't works, whatsapp cant save images.... ect ect.
Is a Know Issue, to solve it i tried to change permisions via ADB, with this commands:
adb.exe wait-for-device
adb.exe root
adb.exe wait-for-device
adb.exe shell chown -R 2800 /mnt/media_rw/sdcard0
adb.exe shell chgrp -R 2800 /mnt/media_rw/sdcard0
I tried the same on a phone terminal as a root. the message is "operation not permited".
Pelase help
LanderXX said:
Hi have this CM installed on my Xperia T:
12.20150616-nightly-mint
It works fine but APPS cant write to Internal Memory (SDACRD0), the camera doesn't works, whatsapp cant save images.... ect ect.
Is a Know Issue, to solve it i tried to change permisions via ADB, with this commands:
adb.exe wait-for-device
adb.exe root
adb.exe wait-for-device
adb.exe shell chown -R 2800 /mnt/media_rw/sdcard0
adb.exe shell chgrp -R 2800 /mnt/media_rw/sdcard0
I tried the same on a phone terminal as a root. the message is "operation not permited".
Pelase help
Click to expand...
Click to collapse
I had the same problem with it. You should backup everything from your internal sdcard and reformat it from inside Android -> Settings -> Storage and the problem is fixed. After that copy your backup back into your phone. The problem seems to be on how the internal memory is mounted.. I experimented and actually made a shell script that worked on CM 12 to remount the internal memory after booting but stopped working on CM12.1 and had to reformat. I don't know if there's another way.
SOLVED!
captita said:
I had the same problem with it. You should backup everything from your internal sdcard and reformat it from inside Android -> Settings -> Storage and the problem is fixed. After that copy your backup back into your phone. The problem seems to be on how the internal memory is mounted.. I experimented and actually made a shell script that worked on CM 12 to remount the internal memory after booting but stopped working on CM12.1 and had to reformat. I don't know if there's another way.
Click to expand...
Click to collapse
IT WORKS!!!!!!!!!
I backup all internall storage to My computer, I Erased Internal Storage trought settings, I copied all my backup to Internal Storage, and NOW CM 12.1 works FINE!!!!!!!! Camera Works, and whatsapp can save images and videos.
MANY MANY MANY THANKS!!!

Categories

Resources