Related
a big part of this new tutorial is not from me, credits go to tot31
New version out !!
Now you can choose if you also want to move the dalvik cache an the /data/data directory to sd (if you have an slow sd-card this will be a bit laggy) (to use this you can now use the update funktion)
and i've added an update funktion and protectet the install function so now you can't install app2sd two times an brick your fimrware
and if this help you you can help/thanks me
If You have an x10 mini (pro) go here :
http://forum.xda-developers.com/showthread.php?t=804574
The leds on boot are Now working :
blue means:
no proplem with sd card booting normal
purple/voilet means
sdcard malfunktion booting with failsafe
.
How To : App2sd on Xperia X10i
Pre Installation.
Root the phone by using z4root ( http://forum.xda-developers.com/showthread.php?t=833953 )
Step 1 : Preparing your micro SD Card.
Please refer to this link ( http://forum.xda-developers.com/wiki/index...rd_partitioning ) on how to prepare your micro sd card.
For better performance I would advise that you use a Class 10 card instead of the original card that comes with the phone because the card is only Class 2 card. For more infomation on speed class rating of sd card please go here -> http://en.wikipedia.org/wiki/Secure_Digital
An excerpt taken from wikipedia :-
The following are the ratings of some currently available cards:
* Class 0 - These cards do not specify performance, which includes all legacy cards prior to class specifications.
* Class 2 - Minimum of 2 MB/s performance. Lowest speed for SDHC cards.
* Class 4 - Minimum of 4 MB/s performance.
* Class 6 - Minimum of 6 MB/s performance.
* Class 10 - Minimum of 10 MB/s performance.
Note : The recommended maximum size of ext2 partition is 1.4GB. I've tried 3GB before and ended up with unstable system and eventually crash the phone. So if you're really greedy since you've bought a 16GB or 32GB card to partition the ext2 more than the recommended size and if your phone is unstable, you've been warn but normaly 1.4 GB are enough
Step 2 : Download the related files.
1. App2sd : see attachment
2. adb shell : see attachment
Step 3 : Enabling USB Debugging mode on you phone.
Go to Settings -> Applications -> Development -> USB Debugging (check this option).
Step 4 : Installing App2sd.
Create a folder name adb in your pc and extract all the files from adb.zip into this folder.
Connect your phone to your pc and mount the sd card. Extract all the file from app2sd2.1.zip to the root of your sd card. Make sure to unmount the sd card before continue the next step.
In your pc open up a dos terminal box by typing cmd in the Search programs and files box.
Type
cd /adb
then type
adb shell
then type
sh /sdcard/app2sd.sh
you'll be presented by this screen...
+________________________________+
|********************************|
|*Welcome To wolfilein's App2sd *|
|*installing script *|
|********************************|
+------------------------------------------+
~this version should be go on any device ~
+___________________+
|********************|
|* Menu *|
|* *|
|*[0] install app2sd *|
|* *|
|*[2] exit *|
|********************|
+-------------------------+
[0]
now just press the enter key & wait.
Important : Make sure to set your phone screen timeout to the max because Superuser will ask for your permission to allow this script to run. If your screen goes blank, you can't see this prompt and the installation will fail.
after a while you'll get this..
busybox is /system/bin/busybox
rm failed for /etc/mount_sd.sh, No such file or directory
+________________________________+
|********************************|
| finished going reboot now |
|********************************|
+-----------------------------------------+
the both messages above doesn't mean that your installation has failed
Finally after a reboot, your phone is ready with app2sd. From now on when you install any applications it will save into your sd card.
Disclaimer : Do this at your own risk. I will not responsible if any injuries or damage occur to you or your phone
Good, But can someone make a more detail guide on step by step to get this done.
Thank you
How to partition the sd card without bootlodaer?
Sorry if this is a noob question.
Wenner said:
How to partition the sd card without bootlodaer?
Sorry if this is a noob question.
Click to expand...
Click to collapse
Use a MicroSD reader and a linux system?
No need for card reader, just plug the phone and use parted
i will add some pictures if a have the time
if I understand this correctly, this script essentially creates link to sd card directory, where previously is a directory of apps.
nice trick, but without any failsafes.
I mean, if you remove sd card you are without /data/app/ directory at all!
there should be some failsafe...
method 1:
script at startup checking:
if there is a symbolic link to sdcard? (check attributes of /data/app/ )
if directory is a symbolic link and no data exists inside (for example specific directory/file is not existent) ->point the symbolic link to /data/app2/ directory.
to make it work,
/system/app2 directory should be created:
Code:
busybox cp -a /data/app /data/app2
instead of removing it in your script:
Code:
"rm -r /data/app "
also make some specified light flash on the phone, to warn user that old backup copy is used because of sd card malfunction (i've documented a way to do this in:
http://forum.xda-developers.com/wiki/index.php?title=Xperia_X10#Leds_and_backglight )
for example pink led:
Code:
echo 15 > /sys/class/leds/ledc:rgb1:red/brightness
echo 2 > /sys/class/leds/ledc:rgb1:green/brightness
echo 3 > /sys/class/leds/ledc:rgb1:blue/brightness
method 2:
even better way would be that sd card partition is mounted on every start on system OVER old /data/app/.
this works always in linux - you can mount over non-empty directory without a problem
so, if the sd card is not accessible - dont mount sd card apps directory and like in method 1, flash the led or something, and old apps directory would work without doing anything more
to check:
- does mounting over non-empty directory works also in android?
- what is the way to add startup script init in the system?
(possibly executed from sd card - when no card is visible, the script would not execute, right )
- why there is a 1.4GB limit ? is this a ext2 limit on android ?
yes doun't normaly you don't remove your sdcard
devein said:
- does mounting over non-empty directory works also in android?
- what is the way to add startup script init in the system?
(possibly executed from sd card - when no card is visible, the script would not execute, right )
- why there is a 1.4GB limit ? is this a ext2 limit on android ?
Click to expand...
Click to collapse
1. Yes
2. exec your script from either /etc/mount_iso.sh or /system/drm/DxDrm/drm.sh
3. There is no such limit, rather an advised value
So... It works or not?
Can someone post something like the rooting instruction for App2SD?
Eg: Step 1 - Step 2
With all the links to apps required.
That would be a great thread for everyone !
Thank you
if i had the time i make this the folloing days
check this out, i've made partitioning tutorial for windows users:
http://forum.xda-developers.com/wiki/index.php?title=SD_card_partitioning
I will copy any tutorials on X10 wiki at http://forum.xda-developers.com/wiki/index.php?title=Xperia_X10#Fixes.2C_Hints_.26_Tips
I've done all steps but i dont know if it works or not how should i know .....
i installed so many games and app and still 350mb left in device memory
Sent from my X10i using the XDA mobile application powered by Tapatalk
so now i will make/add some screens
hmm
i just keep getting permission denied when it trys to apply apps2sd thru the app2sd.sh i rooted via the one click universal android root
****
I did the commands in the end thru terminal on the device all went well apart from it could not locate busybox which was extracted as stated onto root of sd. The phone restarted and basically will not load past the sonyericsson swirly logo. checked on logcat and its crashing due to being unable to mount applog partition.
So the entire Sdcard need to be format as Ext2 or as mutch as u want , let say around 1 Or 2 GB?
Witch one need to be primary and witch need to be logical?
thx
Sent from my X10i using XDA App
yes you must make a
"second" patition with ext2 wich is a primary partition
androidfanboi said:
I did the commands in the end thru terminal on the device all went well apart from it could not locate busybox which was extracted as stated onto root of sd. The phone restarted and basically will not load past the sonyericsson swirly logo. checked on logcat and its crashing due to being unable to mount applog partition.
Click to expand...
Click to collapse
The same story with me....
hi all! im new TF user but i tough i could post here some fixes and scripts that i use on my Samsung galaxy 3 but beaware that i have not tested these but they should work on every device im not responsible for any damage that may occur when you apply these scripts!!
1st there are 3 app2sd scripts
What is App2sd? App2sd is a utility which automatically moves some/all your data partition to your ext sd partition. So, your internal space is partially/not used
Which app2sd version should i choose? As you can see, there are 3 versions: App2sd-v1, App2sd-v2 & App2sd-v3.
Differences in versions App2sd-v1: It is the normal app2sd script. This script moves your /data/app/ & /data/log/ to your sdcard's ext partition. It is very fast but your real internal space will be full if you install many apps. This version is not recommended. App2sd-v2: It is an enchanced version of app2sd, which moves /data/app/, /data/log/ & /data/dalvik-cache/ to your sdcard's ext partition. It is fast and you can install many apps until your internal memory reaches 0mb.. Is is recommended for sdcards class2 - class4. App2sd-v3: It is an ultra enchanced version of app2sd, which is like data2sd, but you won't have so many lag like data2sd. App2sd-v3 moves /data/app/, /data/log/, /data/dalvik-cache/ & /data/data/ to your sdcard's ext partition. Your internal memory won't be used unless you do install so many apps and your sdcard's partition get full! SDcard class6+ is highly recommended! Conlusion: If you have class2 or class4 sdcard use App2sd-v2. If you have class6 sdcard use App2sd-v3.
Requirements You must have a kernel which supports init.d & ext4. And you must have an ext partition in your sdcard. Ext4 is recommended. And last thing... You need android 2.2.
How do i check my sdcard's class? Remove your sdcard from your phone and check if you see a circle with a number. If your dont see anything, you may have a class2 sdcard.
How to partition my sdcard? Download MiniTool Partition Wizard Home Edition 6.0. But make a backup before
How to install the script? Take a nandroid backup. Download it from links below and decompress it to your sd. You can either adb push this script in /system/etc/init.d/ or copy it with root eplorer to /system/etc/init.d/. Type the commands: adb shell (adb only) su mount -o rw,remount /dev/block/stl6 /system chmod 777 /system/etc/init.d/* chown 0.0 /system/etc/init.d/* Then reboot in recovery and do a wipe data/factory reset. All your data will be wiped. From now on some/all of your data (depends on the script version) will be moved to your sd automatically. Before you restore your apps with titanium, go in titanium preferences and select to force restore apps to internal memory. Don't move apps to external!!
Why i see only 200mb as internal? App2sd is invisible You can check your sdcard's ext partition in Titanium Backup.
=> app2sd script v.1
http://forum.xda-developers.com/attachment.php?attachmentid=592379&d=1305062488
=>app2sd script v.2
http://forum.xda-developers.com/attachment.php?attachmentid=592380&d=1305062488
=> app2sd script v.3
http://forum.xda-developers.com/attachment.php?attachmentid=592381&d=1305062488
credits go to KYRILLOS13 who introduced these on SG3!
then there is sd card reading speed fix
How to make it work!
At first it needs root & busybox...
Download the script, choose the cache size you want between 1024, 2048, 3072, 4096 kb! (Recommended size: 2048kb)
Extract the .zip file you downloaded and put the 77sdcardspeedfix in your sdcard.
Run root explorer and move the file in /system/etc/init.d/ (If there is no init.d folder, create one!).
You can also adb push 77sdcardspeedfix /system/etc/init.d/
Run a Terminal Emulator/Adb and type the commands:
Code:
adb shell (if you are using Terminal Emulator, skip this command)
su
chmod 777 /system/etc/init.d/77sdcardspeedfix
chown 0.0 /system/etc/init.d/77sdcardspeedfix
reboot
After that the phone will reboot. You will see that your sdcard reading speed has increased!
thanks for BRAINMASTER who made the script!
more scripts coming soon!!
[HOWTO] get ADB up and running (easy way)
ADB is an acronym for Android Debug Bridge and is a development tool for the Android Mobile Operating System
NOTE this is only for windows!
-open this link --> http://adf.ly/Xfyl wait 5 secs and click upper right corner "skip ads" it will download a program that automaticly installs android sdk (wich includes ADB)
-Open the app, leave the destination as C:\ and click ok/install
-Installing ADB/USB Drivers:
*NOTE* You may need additional (Device Specific) Drivers for your Device!
- Connect your Android Device to your PC using the provided USB Cable or just a plain ole 6-pin to 4-pin usb cable... (I prefer to use one with a ferite core)
- When the new hardware device notification pops-up on your pc point windows to the driver folder we moved to our C-drive(C:\android-sdk-windows\google-usb_driver) and install the adb driver.
** if your having issues with installing ADB drivers read this --> http://dl.dropbox.com/u/20575563/ADB...or_dummies.pdf
-Running ADB from the Command Prompt:
-Windows XP: Select Start or Tap the Windows Key on your Keyboard, select
"Run" and type "CMD" then hit "Enter".
-Windows Vista/Win7: Select Start or Tap the Windows Key on your Keyboard, select the search box on the left and type "cmd" then hit "Enter".
Add the "ADB" directory path as a system variable in windows:
-To do this right-click on "My Computer" and select Properties. Next select the Advanced tab(Advanced Settings in Vista/7) then select Environment Variables.
-Click "New" under System Variables and add the following:
Variable =
Code:
adb
value =
Code:
C:\android-sdk-windows\platform-tools
-Call up your Command Prompt:
Time to start adb
- Open up a Command Prompt Windows
- Type the commands below:
Code:
cd C:\android-sdk-windows\platform-tools
<= press enter
Code:
adb.exe
<= press enter
and voila You will see alot of scripting fly through the command prompt window.
***note! you have to enable usb debugging in --> settings --> applications --> developement --> check usb debugging
tutorial is not made by me, its made by AndroidSamurai. i found it after lot of researching, so i tough i could share it with you!
[HOWTO] edit BUILD.prop
1. open root explorer
2. go to /system, find build.prop, change to read/write mode. open the build.prop in text editor
* change build version: 4th line should say ro.build.display.id=(here you write your build version name), reboot and check build version in "about phone"
* change model number: 15th line should say ro.product.model=(here write your model number ), reboot and check model number in "about phone"
* change firmware version: 8th line should say ro.build.version.release=(here write your firmware version, like 4.x ice cream sandwich), reboot and check firmware version in "about phone"
you can also change different things but ill write a guide of that later
hope you like it!
also reserved for later use
updated how to´s
over 100 views but no replys.... are you there ? if you like these ill provide more scirpts, how to's and fixes
Considering the TF is android 3.x based I assume this is just a typo in the first post "Requirements You must have a kernel which supports init.d & ext4. And you must have an ext partition in your sdcard. Ext4 is recommended. And last thing... You need android 2.2."
Thanks for the post
1 question:
WHY use app2sd on a device with 16gb of internal storage?
DroidRevenge said:
1 question:
WHY use app2sd on a device with 16gb of internal storage?
Click to expand...
Click to collapse
well, maybe you have 16gb of music and you wnt to have somegames too : D
jazux said:
well, maybe you have 16gb of music and you wnt to have somegames too : D
Click to expand...
Click to collapse
Why not put the music on the microsd card instead? Then you wouldnt need apps2sd.
stuntdouble said:
Why not put the music on the microsd card instead? Then you wouldnt need apps2sd.
Click to expand...
Click to collapse
true.. well the script is there if someone wants it
jazux said:
true.. well the script is there if someone wants it
Click to expand...
Click to collapse
Ehhh....just a couple notes about the "speed fix" at least. First, it's easy enough to test using hdparm. Second, none of those scripts will work for the external card because that's not where the readahead knob is located. Third, the only script that will work is one that would be exceptionally ill advised to use. The scripts writing to .../vold/179:0 or mmcblk0 adjust the readahead for all of the mmc0 partitions, ie, /system, /cache, /data, etc. If you set readahead to some obscene value, you'll certainly end up thrashing data as you do all sorts of unnecessary readahead. (ie, you readahead on a file, you don't use the section of data which was read ahead, it gets flushed from memory, you readahead on another file, don't use it, it gets flushed from memory, etc, etc.)
Fourth, I actually did test this when I first got my Transformer, and the difference is read speeds was only about 1.5% for a readahead value at the default 128kB or 2048kB for either the internal or my external class 10. YMMV.
edit - Please update the op so we don't keep spreading bad information.
Waste Thread
lol don't you think this thread is crap and it should be deleted
jazux said:
true.. well the script is there if someone wants it
Click to expand...
Click to collapse
But does it work with android 3.2??? or only 2.2?
stuntdouble said:
Why not put the music on the microsd card instead? Then you wouldnt need apps2sd.
Click to expand...
Click to collapse
because some reason the stock music player and many other music player dont even read music on the microsd card.
Add the fact we are starting to get large games that has gigabyte worth of data to download(shadowgun)
victorythagr8 said:
because some reason the stock music player and many other music player dont even read music on the microsd card.
Add the fact we are starting to get large games that has gigabyte worth of data to download(shadowgun)
Click to expand...
Click to collapse
What are you talking about? The stock music app absolutely DOES read music off the microSD. I don't keep any music on the internal SD.
You guys are arguing over a several month old thread that someone necroed.
philburkhardt said:
What are you talking about? The stock music app absolutely DOES read music off the microSD. I don't keep any music on the internal SD.
Click to expand...
Click to collapse
i confirm it,i have msic on sdcard and gb of gameplay files on internal memory from the day that i buy transformer,half summer!
Jazux thanks so much you rule
Sent from my Transformer TF101G using Tapatalk
firstly I'm not responsible for any kind of damage caused to you
but I have tried all the things on my galaxy fit before explaining here
It's not copied from somewhere instead It's based on my experience on my galaxy fit.
For Non Rooted Devices
There is nothing other then using app2sd apps. Then move all the movable items to sd card. After installing app2sd all newly installed apps are automatically moved to external storege.
I uses app2sd by sam lu.
But for non rooted users I will highly recommend to root there device and make the best use of this smartphone.
for beginners everything about rooting/custom roms/nandroid backups etc is explained in this thread
http://forum.xda-developers.com/showthread.php?t=1606380
thanks a lot to A.cid for this wonderful guide
For Rooted Device
apps required
1.Root explorer or similiar
2.Link2SD (Link2sd Setup is explained later in this post)
step 1.Removing Useless system apps from stock or custom rom
go to /system/app using root explorer and mount as r/w
now delete unwanted apps
I will prefer freezing the app first using link2sd and then if phone is working fine then you can unfreeze and then delete that app
Step 2. Removing dalvik cache files
go to /data/dalvik-cache
now search for the dalvik cache files of deleted system apps
it will having name like
[email protected]@[email protected]
delete this file
Step 3. Linking files to Sd-ext or second partition of Sd card
if you have finished Link2sd setup then you can proceed further
open link2sd and then create Link for all the apps you want to linked to sd card
check all the 3 box 1. link apk 2. link dex 3. link lib files
and then your app will be moved to the sd-ext partition
if there are apps which are used very frequently then i prefer not linking dex files to sd card. link only apk for them.
currently system apps can't be linked using link2sd
In the case if app is not working properly after linking then remove links for that app.
Plz help me to improve this article.
suggestions and questions are welcomed.
forgive me for my poor english
Plz help in improving this article. If there is anything wrong in this post let me know. and if you have any other simple method to do this plz post here and help beginners to get more space. But try not to post complicated method which beginners find hard to perform
this post is for beginners
Link2SD steup on galaxy fit
Copied from A.cid main article from
http://forum.xda-developers.com/showthread.php?t=1606380
There are a lot of ways and scripts to transfer apps from your internal memory to the sd ext partition, but the most consistent method I found was Link2sd.
This method works across all roms (rooted stock and custom, both) that I’ve tried, even on all variations of CyanogenMod7 (CM7) as well as on ICS CM9, and is very easy to setup and use.
However, if a custom rom already has DarkTremor's a2sd (a2sdgui app will be present) or any similar script, then DO NOT configure them.
for example: Creeds v3 has a2sdgui, and if i want to use Link2sd, then after flashing Creeds, i SHOULD NOT run a2sdgui, and directly install (and configure) Link2sd...if you run/configure a2sdgui, then it will clash with the working of Link2sd.
Similarly, if any custom rom has any memory hack already implemented, then you cannot use Link2sd...
Steps to setup Link2sd:
• Download Link2sd from Play Store (it’s a free app).
• After it gets installed, run it, and allow root access.
• You will get a message to select the format of your sd partition, select “ext3”.
• Link2sd will then automatically create mount scripts that it requires to work, and will then tell you to reboot your phone.
• Do a proper reboot, and not a ‘hot reboot’.
• After rebooting, open up Link2sd, press menu then select “settings”.
• Select/check the options “automatically link newly installed applications to sd”, “auto link notification”, “relink lib files at boot” (and “fast scroll”, if you want).
• For “install location” option, select “internal”.
• Then go to “auto link settings” and select/check all the three options (you can skip/ unselect “link dalvik-cache file” if you wish)
• Done
Now, every new app that you will install will automatically be moved to your sd ext partition.
Link2sd is also an excellent (and fast loading) app manager, with which you can freeze, uninstall, re-install…though you can move only user apps to sd-ext partition.
Also, there is no point in having your entire phone memory empty, so you probably should unlink the dex (dalvik cache) of your apps. I usually link only the apk and lib files, and leave the dex files unlinked and on the phone storage, so as to avoid any sluggishness in operation., though if your phone memory still fills up, you can link the dex of your rarely-used apps, and leave the dex of important and frequently used apps on the phone storage.
Suppose a custom rom has s2e/app2sd pre-implemented, then after a fresh install, FREEZE the app (rather than uninstall), and then install Link2sd...
Also, if you get error "mount script not created", then choose partition as ext4 (rather than ext3 mentioned below), even though your partition might be ext3...(don't know why this happens with some roms )
In some custom Roms Link2sd doesn't mount sd-ext partition even after selecting correct type of partition in that case try to select other types whether they are working or not
Like in Chocobread v3.2 it worked after selecting partition as ext4
Plz view this thread if you are still facing any problem
Go through this thread
http://forum.xda-developers.com/showthread.php?t=1698813
What happens when we install a new app??
I'm not a developer but this is what I experienced
/data directory is the space which is shown as Internal Storage in phone
/system directory has nothing to do with this internal storage
when we install a new app then it during the installation process three things happens
1.it creates an apk file in /data/app
2.creates an .dex file in /data/dalvik-cache
3.creates one folder in /data/data
when we move apps to sd that apk file moved to sd storage in
.android secure folder and creates an .asec file there
so basically that .dex file and data files are responsible for eating our internal space and for the apps which can't be moved to sd that apk file is also responsible.
we can't use widgets if app is on sd storage.
so in order to use widgets we have to move back to internal storage.
this is where Link2sd helps us
link2sd links selected files to sd-ext partition and for system it still appears in internal storage but it's not there actually.
While for system apps
.apk files remains in /system/app
only .dex files are in data/data directory
we can use widgets of system apps even apk files are not in /data/app directory
so it is recommended that if you want to use widget of the app but you don't want it on internal space(as it is using much more space while it is in internal memory)
here is the solution
create an apk file for that app using any backup app
then move that file to /system/app
change the permissions to rw-r--r--
for this simply see the permissions of any other system app and apply same here
to system
Simply partition your sd card via cwm.. U can get as much internal space as u want..
amn_grg said:
Simply partition your sd card via cwm.. U can get as much internal space as u want..
Click to expand...
Click to collapse
Let consider your post now tell me how to install 100 apps having size more than 500 mb
Without using link2sd or a2sd or any simliar app
Sent from my GT-S5670 using xda premium
Nikhil_G said:
Let consider your post now tell me how to install 100 apps having size more than 500 mb
Without using link2sd or a2sd or any simliar app
Sent from my GT-S5670 using xda premium
Click to expand...
Click to collapse
By symlinking apps manually, one by one...:beer:
Possible - yes
Feasible - no
Everything is possible bro!
Typed using a small touchscreen
a.cid said:
By symlinking apps manually, one by one...:beer:
Possible - yes
Feasible - no
Everything is possible bro!
Typed using a small touchscreen
Click to expand...
Click to collapse
Yeah right...
Informative Thread
amn_grg said:
Simply partition your sd card via cwm.. U can get as much internal space as u want..
Click to expand...
Click to collapse
can you detail the procedure please.
vikrant prabhakar said:
can you detail the procedure please.
Click to expand...
Click to collapse
partition ur sd card through cm recovery then install s2e from play store now all cm7 rom come with pre install s2e script .
Another way is to use terminal emulator .
Download terminal emulator from the PlayStore and then run the following codes:
Code:
su
*grant/allow superuser permissions*
Code:
pm set-Install-Location 2
exit
exit
Note: sometimes if you get an error you may have to run
Code:
pm setInstallLocation 2
if it fails.
All this does is it allows moving many apps that aren't normally movable to the SD card. After running these codes you should be able to move apps to the SD card via Settings>Apps.
This code also sets the default location for apps to install into as the SD card.
What i do for more internal memory..!
Partitioning your sd card is an option. But if you have a sd card of less storage then this option is ruled out. I use a 2gb sd card and partitioning it is not very feasible for me. so...
1. If I'm on a stock gingerbread ROM i use this script http://forum.xda-developers.com/showthread.php?t=2303856 .
(I dont use it very often. Only if necessary.) And i odex the ROM if it is de-odexed by using http://forum.xda-developers.com/showthread.php?t=2303856 Universal Odex Script by MatrixDJ96. Odexing works very well!!! :good:
2. For a custom ROM not many modifications are needed. I just remove the unwanted apps using Link2SD. :good:
Hi All,
I got errors mentioned in the title and after few searches, found that there are few Galaxy SL owners who had got into this issue.
Currently Known Root Cause:
A hardware issue possibly due to a board issue or loose attachment of internal SD card to the motherboard (Grrrrrrr SAMSUNG!)
Symptoms:
- Suddenly core applications like phone/messaging start force closing (sometimes all open apps). Only a reboot will solve the issue.
- Sudden reboot of the phone after few hours of running (or even sleeping)
- Sometimes the restart itself hanging with a yellow message "Unknown Upload Mode"
- Message in status bar "Internal SD card has been removed unexpectedly" or "Internal SD card not accessible" or something like "Damaged SD card"
Known Solution:
1. Replacement of board from Samsung Service Center (Good for you if you are within the warranty period)
2. Do some hardware hack to remove the internal SD completely (http://forum.xda-developers.com/showthread.php?t=1651619)
I got this issue just after I finished my warranty period, and hence, I was trying to find if I can do something about this issue by my own. What I wanted was to actually swap my internal SD storage with a proper external SD storage. This is not same as the popular "swapping the internal and external SD card" topic, but that and something more as well!! This will solve the issue of force closes and sudden reboots (may still not solve issue of reboot getting stuck, but I assume phone will not need frequent reboot after solving first 2 issues!)
Galaxy SL has 3 partitions created in the card:
1. ext3 partition for data
2. another small FAT partition - (for what? not sure)
3. Third FAT partition which acts as the normal internal SD card (which is accessible when working as USB mass storage)
Intention here is to move all the partitions to the external SD. Looking at the mount points and vold.fstab, I could not find where the 2nd partition in the above list is mounted/used (If anyone knows, please let me know). So I decided to move atleast the ext3 (data) and fat (/sdcard) to the external SD.
Following are the steps I followed for doing the same:
WARNING!!!
1. Copy these at your own risk. I am not responsible if you brick your phone or lose your data/applications/settings or if the phone goes to a boot loop!
2. Do not continue if you do not understand what is written here
3. Doing this will change the /data partition. So wiping data partition in the normal way will not work (say from CWM). You may need to do 2 steps - wipe (internal) data normally (say using CWM), wipe (external SD) data manually by disabling the script mentioned in the procedure and wiping using make_ext4fs tool (steps are given in PART 3 of this post).
4. This has been tested only on CM9 Alpha 6-11 / rooted DDLF2. Theoretically it may or may not work on other ROMs, depending on other tweaks and changes in the system, no guaranty offered!
5. In case you mess it up, most of the time (but no guarantees!), you can recover by flashing from beginning using ODIN some base versions like KPE and then come to your normal ROM, followed by a nandroid recovery (so better do a nandroid backup before you try anything .
Pre-requisites:
- Rooted Phone
- Kernel with init.d support (and preferably ext4 as well if you want that)
- Basic ADB knowledge
- A blank micro SD card with at least class 4 (class 6 or greater preferred) speed and with sufficient capacity - say 8/16/32 GB
PART 1 - PREPARING THE EXTERNAL SD
--------------------------------------------------------------------
0. !!! FIRST !!!
Do a Nandroid Backup (and also other app level backups like Titanium or MyBackup)
Backup contents of your FAT partition (mmcblk0p1) - ie, the internal SD card card
Backup contents of your external SD card
1. Download sdparted-recovery.zip from web (http://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage - check messages like 11 to see the basic usage) and extract the contents
2. Using ADB, copy the extracted files in sdparted directory into /system/bin, change permission for all of them to 755 using chmod
3. Put a clean external SD card into the phone
4. In an ADB shell, run /system/bin/parted giving mmcblk1 as the target. Now resize the existing FAT partition (this is the first and default partition in the card). Tips:
print gives the existing partition(s)
help gives help on various options
for resizing and creating partitions, inputs should be derived from the initial print output (which gave the first and last points)
Eg: If card is 16GB, and you want to reserve 4GB for data, then resize the first partition to 12GB
5. Create a new partition of type ext2 with remaining size (say 4G in our case). Save and quit parted.
7. (Do this only if your kernel supports ext3/ext4) Run "tune2fs -j /dev/block/mmcblk1p2" to convert ext2 to ext3
8. (Do this only if your kernel supports ext4) Using ADB, copy "make_ext4fs" (attached) to /system/bin
9. (Do this only if your kernel supports ext4) Convert ext3 partition to ext4 using make_ext4fs ("make_ext4fs /dev/block/mmcblk1p2")
10. Now the partitions are ready
- They will be visible as mmcblk1p1 (FAT) and mmcblk1p2 (ext4) when you cat the /proc/partitions
- They will be visible as partitions 1(FAT) and 2 (ext4) in the print output of parted.
Confirm the above before proceeding further.
PART 2 - SWAPPING EXTERNAL AND INTERNAL SD
---------------------------------------------------------------------------------
1. Write a script, say 00remnt similar to the attached sample file which currently I am using (If you do not follow the script, better don't proceed. Else check if things are fine for your current base ROM settings)
2. Push this into /etc/init.d/ using ADB
3. Change permissions of the file to 755
4. If you need, copy the contents of your internal SD card FAT partition (/sdcard) to the external SD card FAT partition (/sdcard/external_sd or /emmc)
5. Use the popular (relevant methods) to swap the internal and external FAT partitions (which actually changes the vold.fstab contents). Normal search in the forum will give you the available methods - some ROMs support it as options, others have mods which will accomplish the same
5. Reboot and enjoy
Voila!!! Now the system is not using internal SD card (for most purposes) at all!! And your phone can now run for days without abrupt force closes and reboot. You still may get a message like SD card is removed/damaged, (and /emmc or /sdcard/exteranal_sd may become inaccessible - so better use it only as a temporary storage!). But you can safely ignore these messages as that is the internal SD card which we are not using anyway... Enjoy...
PART 3 - WIPING DATA PARTITION (in case you need this step later)
-----------------------------------------------------------------------------------------------------------
1. Change permission of the 00remnt to 644
2. Reboot the phone (now the phone will come up with default internal SD partition for data)
3. From ADB shell, execute "make_ext4fs /dev/block/mmcblk1p2" (see PART 1 on how to get this tool)
4. Change permission of the 00remnt to 755
5. Reboot the phone to recovery, wipe the /data as normal
rgds,
Dipu.
PS: If any one knows how our phone uses the 2nd partition in the internal SD card, please let me know... I am assuming that it is not used for any critical purposes (as my phone ran successfully for few days without any issue). May be it is used in some kernel/ROM, if so, please let me know.
Though i didn't understand a word(being an internee dentist) it will be useful to others.appreciate your efforts!!
Sent from my GT-I9003 using xda app-developers app
This is what i call a complete and useful guide.
This should become a sticky.. now... NOW!
+1 for sticky, superb info.
that would be a really nice sticky
i had the motherboard changed..
Thanks Dipu K for your efforts.
I've tried this solution in my I9003, and I have only a problem: When reboot the phone, /data is copied into de Ext4 partition on SD card, but all aplications have errors because isn´t possible to unmount /data,
Here is the messaje in remnt-log (only a few lines):
Code:
...
3. Make Directory --->
4. Mount new data partition from external SD --->
5. Copy the current files in /data
6. Remove current files in /data
7. Unmount /data
umount: can't umount /data: Device or resource busy
8. Remove dir /data as a safety measure
9. Linking external sd data partition as /data
10. Final Mount status --->
...
What can I do to correct this?
Thanks
bfsa said:
...
What can I do to correct this?
Thanks
Click to expand...
Click to collapse
Finally, I've changed a line on 00remnt, and seems to work properly: busybox umount -l /data 2>> /system/remnt-log
Where can I get make_ext4fs? Sadly the same case has happened to me...
Hi Guys.
I am using alpha 4 from last one month and experience was awesome but from last 1 week I am getting lot of FC for lot of services like exchange service gapps what's up camera and lot more. I am not sure why FC issue started happening from last one week.
History :
I was using CM 10 alpha 1 then alpha 2 then alpha 3 and now on alpha 4.
I really fed up with Force close issue from last one week . I tried reboot but still 80% of apps and services getting FC. Please guide me on this .
Sent from my GT-I9003 using xda app-developers app
Sent from my GT-I9003 using xda app-developers app
hi all, i have a galaxy i9003 with a corrupted or completely dead (not sure) internal memory chip. I have come to this conclusion after 3 days of trying to install custom and stock roms. I can access recovery and download mode but i cant install any ROM, the phone keeps rebooting after the SAMSUNG (whole screen black except SAMSUNG in the middle). All i have is atm this http://forum.xda-developers.com/showthread.php?t=1351056 installed on my phone via ODIN. I dont have knowledge about ADB, can somebody help me out with instructions more?
Pre-requisites:
- Rooted Phone
Click to expand...
Click to collapse
Is there a solution without a rooted phone or can I root it somehow, even if the there is a hardware defect? I got an error with /dev/block/mmcblk1p that rfs can't be written.
I have a problem. My friend gave me an i9003. Wipe is not working at all, even from Recovery. I connect the phone to PC and use the internal card, no matter what I do, changes don't apply. I copy/paste/delete/format/even odin flash, no good. Everything comes back as before reboot. What is it related to?
I used to have an i9000, but nothing applies to i9003. I flashed i9000 1000 times and at last got a mmcblk02 error, fixed it with external sd swap. I'm thinking of swapping emmc with sd on this one too, but cant install a rom from CWM, I can install CWM from ODIN though and can flash CFROOT too, but in CWM internal storage can't be mounted... Motherboard problem?
I will try to use this guide and report back soon...
allxx said:
I have a problem. My friend gave me an i9003. Wipe is not working at all, even from Recovery. I connect the phone to PC and use the internal card, no matter what I do, changes don't apply. I copy/paste/delete/format/even odin flash, no good. Everything comes back as before reboot. What is it related to?
I used to have an i9000, but nothing applies to i9003. I flashed i9000 1000 times and at last got a mmcblk02 error, fixed it with external sd swap. I'm thinking of swapping emmc with sd on this one too, but cant install a rom from CWM, I can install CWM from ODIN though and can flash CFROOT too, but in CWM internal storage can't be mounted... Motherboard problem?
I will try to use this guide and report back soon...
Click to expand...
Click to collapse
Please do send us a report, I'd appreciate it very much. Have to deal with a similar situation as well for an old i9003. I've tried to employ the steps mentioned here but could not get it to work as well.
Hi everybody!
Had to remove the internal SD to install everything on the external one by following the mentioned post. Nothing else worked.
http://forum.xda-developers.com/showthread.php?t=1651619
can anyone here recomended me custom rom that already with swap sdcard?
Dipu K said:
Hi All,
I got errors mentioned in the title and after few searches, found that there are few Galaxy SL owners who had got into this issue.
Currently Known Root Cause:
A hardware issue possibly due to a board issue or loose attachment of internal SD card to the motherboard (Grrrrrrr SAMSUNG!)
Symptoms:
- Suddenly core applications like phone/messaging start force closing (sometimes all open apps). Only a reboot will solve the issue.
- Sudden reboot of the phone after few hours of running (or even sleeping)
- Sometimes the restart itself hanging with a yellow message "Unknown Upload Mode"
- Message in status bar "Internal SD card has been removed unexpectedly" or "Internal SD card not accessible" or something like "Damaged SD card"
Known Solution:
1. Replacement of board from Samsung Service Center (Good for you if you are within the warranty period)
2. Do some hardware hack to remove the internal SD completely (http://forum.xda-developers.com/showthread.php?t=1651619)
I got this issue just after I finished my warranty period, and hence, I was trying to find if I can do something about this issue by my own. What I wanted was to actually swap my internal SD storage with a proper external SD storage. This is not same as the popular "swapping the internal and external SD card" topic, but that and something more as well!! This will solve the issue of force closes and sudden reboots (may still not solve issue of reboot getting stuck, but I assume phone will not need frequent reboot after solving first 2 issues!)
Galaxy SL has 3 partitions created in the card:
1. ext3 partition for data
2. another small FAT partition - (for what? not sure)
3. Third FAT partition which acts as the normal internal SD card (which is accessible when working as USB mass storage)
Intention here is to move all the partitions to the external SD. Looking at the mount points and vold.fstab, I could not find where the 2nd partition in the above list is mounted/used (If anyone knows, please let me know). So I decided to move atleast the ext3 (data) and fat (/sdcard) to the external SD.
Following are the steps I followed for doing the same:
WARNING!!!
1. Copy these at your own risk. I am not responsible if you brick your phone or lose your data/applications/settings or if the phone goes to a boot loop!
2. Do not continue if you do not understand what is written here
3. Doing this will change the /data partition. So wiping data partition in the normal way will not work (say from CWM). You may need to do 2 steps - wipe (internal) data normally (say using CWM), wipe (external SD) data manually by disabling the script mentioned in the procedure and wiping using make_ext4fs tool (steps are given in PART 3 of this post).
4. This has been tested only on CM9 Alpha 6-11 / rooted DDLF2. Theoretically it may or may not work on other ROMs, depending on other tweaks and changes in the system, no guaranty offered!
5. In case you mess it up, most of the time (but no guarantees!), you can recover by flashing from beginning using ODIN some base versions like KPE and then come to your normal ROM, followed by a nandroid recovery (so better do a nandroid backup before you try anything .
Pre-requisites:
- Rooted Phone
- Kernel with init.d support (and preferably ext4 as well if you want that)
- Basic ADB knowledge
- A blank micro SD card with at least class 4 (class 6 or greater preferred) speed and with sufficient capacity - say 8/16/32 GB
PART 1 - PREPARING THE EXTERNAL SD
--------------------------------------------------------------------
0. !!! FIRST !!!
Do a Nandroid Backup (and also other app level backups like Titanium or MyBackup)
Backup contents of your FAT partition (mmcblk0p1) - ie, the internal SD card card
Backup contents of your external SD card
1. Download sdparted-recovery.zip from web (http://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage - check messages like 11 to see the basic usage) and extract the contents
2. Using ADB, copy the extracted files in sdparted directory into /system/bin, change permission for all of them to 755 using chmod
3. Put a clean external SD card into the phone
4. In an ADB shell, run /system/bin/parted giving mmcblk1 as the target. Now resize the existing FAT partition (this is the first and default partition in the card). Tips:
print gives the existing partition(s)
help gives help on various options
for resizing and creating partitions, inputs should be derived from the initial print output (which gave the first and last points)
Eg: If card is 16GB, and you want to reserve 4GB for data, then resize the first partition to 12GB
5. Create a new partition of type ext2 with remaining size (say 4G in our case). Save and quit parted.
7. (Do this only if your kernel supports ext3/ext4) Run "tune2fs -j /dev/block/mmcblk1p2" to convert ext2 to ext3
8. (Do this only if your kernel supports ext4) Using ADB, copy "make_ext4fs" (attached) to /system/bin
9. (Do this only if your kernel supports ext4) Convert ext3 partition to ext4 using make_ext4fs ("make_ext4fs /dev/block/mmcblk1p2")
10. Now the partitions are ready
- They will be visible as mmcblk1p1 (FAT) and mmcblk1p2 (ext4) when you cat the /proc/partitions
- They will be visible as partitions 1(FAT) and 2 (ext4) in the print output of parted.
Confirm the above before proceeding further.
PART 2 - SWAPPING EXTERNAL AND INTERNAL SD
---------------------------------------------------------------------------------
1. Write a script, say 00remnt similar to the attached sample file which currently I am using (If you do not follow the script, better don't proceed. Else check if things are fine for your current base ROM settings)
2. Push this into /etc/init.d/ using ADB
3. Change permissions of the file to 755
4. If you need, copy the contents of your internal SD card FAT partition (/sdcard) to the external SD card FAT partition (/sdcard/external_sd or /emmc)
5. Use the popular (relevant methods) to swap the internal and external FAT partitions (which actually changes the vold.fstab contents). Normal search in the forum will give you the available methods - some ROMs support it as options, others have mods which will accomplish the same
5. Reboot and enjoy
Voila!!! Now the system is not using internal SD card (for most purposes) at all!! And your phone can now run for days without abrupt force closes and reboot. You still may get a message like SD card is removed/damaged, (and /emmc or /sdcard/exteranal_sd may become inaccessible - so better use it only as a temporary storage!). But you can safely ignore these messages as that is the internal SD card which we are not using anyway... Enjoy...
PART 3 - WIPING DATA PARTITION (in case you need this step later)
-----------------------------------------------------------------------------------------------------------
1. Change permission of the 00remnt to 644
2. Reboot the phone (now the phone will come up with default internal SD partition for data)
3. From ADB shell, execute "make_ext4fs /dev/block/mmcblk1p2" (see PART 1 on how to get this tool)
4. Change permission of the 00remnt to 755
5. Reboot the phone to recovery, wipe the /data as normal
rgds,
Dipu.
PS: If any one knows how our phone uses the 2nd partition in the internal SD card, please let me know... I am assuming that it is not used for any critical purposes (as my phone ran successfully for few days without any issue). May be it is used in some kernel/ROM, if so, please let me know.
Click to expand...
Click to collapse
Somebody's Samsung Galaxy SL i9003 had wiped the internal SD card by itself! Is this even possible that it just wipes/formats on it's own? Is there any advice? The contacts appear to still be there.
This Script + boot.img Aims to make as much as possible use of the sdcard (ext2 Partition) and use it as the internal space of the phone.
Anyone who got the time to download v2 can use the "upgrade-from-v2" script to upgrade to version 3 (you need 2 reboots), in version 3 (if you installed v1 you need to wipe/factory + format ext2)
In version 3 the script deletes Maps.apk and Street.apk & language Packs of keyboard. (if you want it, backup those apks and install them again to /data) with the space left in /custpack partition the script is able to link all dalvik of system and custpack apps, this drives the reads/write of the sdcard to 0 zero, everything in the phone is fast as normal since it will use its nand, and the sd is dedicated to every new apk is installed.
Change log:
Version 5
1. Changed the way it copies files to retain file attributes
2. Copy with force over-write
3. Check for deleted apps and delete files from ext durring the schedule check for linking.
This change will correct problems were one app would brake after a reboot (if this app was installed before)
Note: file name says v4 but its v5
Version 4 Deals with random broken libraries after a reboot.
Notice:
Use a Fast SDCard class 6 or 10 with good response time
* First boot up takes much longer.
* Then you have to reboot again 1 time to be fully installed.
* Give the ext2 partition 1.5 Giga Or 2giga its enough.
Troubleshooting:
* If you having problems with an app, uninstall it, reboot, then install it again.
Back up all of your apps:
adb shell
mkdir /sdcard/myapps
cp /data/app/* /sdcard/myapps
Click to expand...
Click to collapse
And after the wipe etc.
adb shell
cp /sdcard/myapps/* /data/app/
reboot
Click to expand...
Click to collapse
Installation
1. While the phone is turned on completely, (and rooted run Setup.bat
2. Turn off phone and flash the new boot.img (sd-boot.img )
3. Turn on phone enter to recovery and wipe/factory data.
4. Format sdcard with ext2 Partition, insert it, turn on phone and wait a lot for the first boot as it will take time
Only at your own risk Be careful because you have to flash the modified boot.img to use it.. flash it using the files you used to flash boot for rooting the phone.
Note: All bugs have been fixed, version 6. Actually with a class 10 my phone runs more smoothly and faster even than stock rom... if anyone is intersting for a release.. leave a comment.
frapedas said:
This Script + boot.img Aims to make as much as possible use of the sdcard (ext2 Partition) and use it as the internal space of the phone.
Anyone who got the time to download v2 can use the "upgrade-from-v2" script to upgrade to version 3 (you need 2 reboots), in version 3 (if you installed v1 you need to wipe/factory + format ext2)
In version 3 the script deletes Maps.apk and Street.apk & language Packs of keyboard. (if you want it, backup those apks and install them again to /data) with the space left in /custpack partition the script is able to link all dalvik of system and custpack apps, this drives the reads/write of the sdcard to 0 zero, everything in the phone is fast as normal since it will use its nand, and the sd is dedicated to every new apk is installed.
Change log:
Version 5
1. Changed the way it copies files to retain file attributes
2. Copy with force over-write
3. Check for deleted apps and delete files from ext durring the schedule check for linking.
This change will correct problems were one app would brake after a reboot (if this app was installed before)
Note: file name says v4 but its v5
Version 4 Deals with random broken libraries after a reboot.
Notice:
Use a Fast SDCard class 6 or 10 with good response time
* First boot up takes much longer.
* Then you have to reboot again 1 time to be fully installed.
* Give the ext2 partition 1.5 Giga Or 2giga its enough.
Troubleshooting:
* If you having problems with an app, uninstall it, reboot, then install it again.
Back up all of your apps:
And after the wipe etc.
Installation
1. While the phone is turned on completely, (and rooted run Setup.bat
2. Turn off phone and flash the new boot.img (sd-boot.img )
3. Turn on phone enter to recovery and wipe/factory data.
4. Format sdcard with ext2 Partition, insert it, turn on phone and wait a lot for the first boot as it will take time
Only at your own risk Be careful because you have to flash the modified boot.img to use it.. flash it using the files you used to flash boot for rooting the phone.
Note: All bugs have been fixed, version 6. Actually with a class 10 my phone runs more smoothly and faster even than stock rom... if anyone is intersting for a release.. leave a comment.
Click to expand...
Click to collapse
Hi frapedas, sorry for the late reply
This works in 991D?
I cant get dalvik cache in SD card with Yuwing scriptz
qashqool said:
Hi frapedas, sorry for the late reply
This works in 991D?
I cant get dalvik cache in SD card with Yuwing scriptz
Click to expand...
Click to collapse
yes it should work