Database Info

Question Noobe

I would like to know exactly what these do before i do them. sorry guys im a noobe..
Build:RA-magic-v1.2.3G
- wipe sd:ext partition
- Wipe SD:dalink-cache
- part sd:fat32+ext2+swap
- part sdnly fat32
- repair ext filesystem
- convert ext2 to ext3
- fix apk uid mismatches
- fix rotate
- USB Mass storage on
- USB Mass Storage off
Also how do you flash this recovery img from the Recover Flasher App, VS using CMD & fastboot.

jdubdieslo said:
I would like to know exactly what these do before i do them. sorry guys im a noobe..
Build:RA-magic-v1.2.3G
- wipe sd:ext partition
- Wipe SD:dalink-cache
- part sd:fat32+ext2+swap
- part sdnly fat32
- repair ext filesystem
- convert ext2 to ext3
- fix apk uid mismatches
- fix rotate
- USB Mass storage on
- USB Mass Storage off
Also how do you flash this recovery img from the Recover Flasher App, VS using CMD & fastboot.
Click to expand...
Click to collapse
wipe sd: ext partition- deletes your apps on your ext partiton
wipe sd: davlik-cache wipes your cache on your sd
part sd: fat32+ext2+swap makes the three partitions you need to run hero roms
parted sd: fat32 only- just partitions your memory card for a fat32 for stock roms like cyanogen
convert ext2 to ext3- does exactly what it says. makes ext2 to ext3
repair ext filesystem- do this after you choose to convert ext2 to ext3
fix apk uid mismatches- does exactly what it says
fix rotate- fixes auto rotate issues some roms have
usb mass storage on- allows you to access your fat32 part of your sd from the recovery
usb mass storage off- turns off the mounting of your sd from the recovery
to flash it using the recovery flasher app, just look at the unlockr's video and substitute the recovery image name for the one that is in the video. Voila.
Hope this helps

Applause...
Getting a straight answer sometimes is the most difficult part of installing a rom.

thelastgoodbrother said:
Applause...
Getting a straight answer sometimes is the most difficult part of installing a rom.
Click to expand...
Click to collapse
lol thats very true but come on if you can't do the research to figure out the basic youll be posting another thread the next day but this time it'll be called "stuck on the g1 screen" lol sometimes not giving a straight answer may save their phone... but thats just my opinion

So use part sd: fat32+ext2+swap when useing hero rom... what if i use hero rom & go back to cyanogen can i leave it that way or do i need to parted sd: fat32 only? also if i did part sd: fat32+ext2+swap And then did part sdnly fat32 would it override the part sd: fat32+ext2+swap. another question i dont even know what ext 2 is so moving it to ext 3 would be? sorry guys im new at this.. just wanted to clarify this. is fat32 letting me store apps to sd? because i removed the sd card while phone was on & notices it froze; i put it back in removed & rrplaced battery and it was fine again.. also i noticed i part sd: fat32+ext2+swap again before i read your replies to see what it would do and everything on my sd card was goin..
also what is swap i saw an app that saved a swap file on sd..
thanks everyone for you help. loving the android community. as soon as i get some extra cash i will be donating to people that helped me make my android stand out from any one's android on my end of the computer. thanks

jdubdieslo said:
So use part sd: fat32+ext2+swap when useing hero rom... what if i use hero rom & go back to cyanogen can i leave it that way or do i need to parted sd: fat32 only? also if i did part sd: fat32+ext2+swap And then did part sdnly fat32 would it override the part sd: fat32+ext2+swap. another question i dont even know what ext 2 is so moving it to ext 3 would be? sorry guys im new at this.. just wanted to clarify this. is fat32 letting me store apps to sd? because i removed the sd card while phone was on & notices it froze; i put it back in removed & rrplaced battery and it was fine again.. also i noticed i part sd: fat32+ext2+swap again before i read your replies to see what it would do and everything on my sd card was goin..
also what is swap i saw an app that saved a swap file on sd..
thanks everyone for you help. loving the android community. as soon as i get some extra cash i will be donating to people that helped me make my android stand out from any one's android on my end of the computer. thanks
Click to expand...
Click to collapse
If you are running a hero rom and want to go to cyanogen, you can leave the fat32+ext2+swap. Just make sure that you wipe your sd partition and davlik cache using the options in the recovery image. Do this every time you are flashing any new rom for that matter, whether it's a different hero rom or a stock rom.
Ext is the partition of your memory card that stores all your apps. This was necessary for the g1 because it only had like 80 mb of memory for apps. The mytouch has nearly 300 so apps2sd is not really necessary, but most custom ROMs include this anyway. Ext3 is what most of these ROMs operate on. Ext2 is an old outdated version that no one really uses anymore and ext4 is even newer than ext3 but is not really necessary.
Fat32 only does not let you store your apps on your sd. It does not have the ext partition to let that happen. I don't know why your phone froze when you took your sd card out. It shouldn't have. When you part your memory card, whether its just fat32 or the combo fat, ext, and swap your memory card gets wiped and formatted to whatever you have, so of course you will lose all your contents on the memory card. It wipes and reformats all 3 partitons, or just the one if you are doing only the fat32.
As for swap, this is necessary for hero. Hero phones have 288 mb of ram and the mytouch only has 192mb so if you don't have this, the phone lags so bad and hangs up and you get constant load screens. The app you saw is known as swapper. Yes it does put a swap file on your sd card, but if you go into advanced settings, it lets you use your swap partition of your memory card, which is what you should always choose.
Keep them questions rolling, I like being able to contribute whenever I can.

tazz9690 said:
If you are running a hero rom and want to go to cyanogen, you can leave the fat32+ext2+swap. Just make sure that you wipe your sd partition and davlik cache using the options in the recovery image. Do this every time you are flashing any new rom for that matter, whether it's a different hero rom or a stock rom.
Ext is the partition of your memory card that stores all your apps. This was necessary for the g1 because it only had like 80 mb of memory for apps. The mytouch has nearly 300 so apps2sd is not really necessary, but most custom ROMs include this anyway. Ext3 is what most of these ROMs operate on. Ext2 is an old outdated version that no one really uses anymore and ext4 is even newer than ext3 but is not really necessary.
Fat32 only does not let you store your apps on your sd. It does not have the ext partition to let that happen. I don't know why your phone froze when you took your sd card out. It shouldn't have. When you part your memory card, whether its just fat32 or the combo fat, ext, and swap your memory card gets wiped and formatted to whatever you have, so of course you will lose all your contents on the memory card. It wipes and reformats all 3 partitons, or just the one if you are doing only the fat32.
As for swap, this is necessary for hero. Hero phones have 288 mb of ram and the mytouch only has 192mb so if you don't have this, the phone lags so bad and hangs up and you get constant load screens. The app you saw is known as swapper. Yes it does put a swap file on your sd card, but if you go into advanced settings, it lets you use your swap partition of your memory card, which is what you should always choose.
Keep them questions rolling, I like being able to contribute whenever I can.
Click to expand...
Click to collapse
ao since ext 2 is outdate we want to convert ext 2 to ext 3 then repair ext filesystemafter words.. so if you convert ext 2 to ext 3 is there only a ext 3 now or both ext 2 and it adds a ext 3? also what does dalvik mean? also i thought apps to sd was a big deal because if you switch roms all your apps are still there, but if you wipe ext partition then you lose the apps so the real reason is just for phone with low ram and cant store many apps at once.. intresting..and wats up with not wipe data/factory reset after installing roms? whats the reason behind that, i notice my IME keyboard is no longer there when i do that.. im trying to think of more questions lol. thanks a million.

jdubdieslo said:
ao since ext 2 is outdate we want to convert ext 2 to ext 3 then repair ext filesystemafter words.. so if you convert ext 2 to ext 3 is there only a ext 3 now or both ext 2 and it adds a ext 3? also what does dalvik mean? also i thought apps to sd was a big deal because if you switch roms all your apps are still there, but if you wipe ext partition then you lose the apps so the real reason is just for phone with low ram and cant store many apps at once.. intresting..and wats up with not wipe data/factory reset after installing roms? whats the reason behind that, i notice my IME keyboard is no longer there when i do that.. im trying to think of more questions lol. thanks a million.
Click to expand...
Click to collapse
if you convert ext2 to ext3, there will only be ext3. It converts it from ext2, it does not make an additional partition. Davlik cache, if I am not mistaken is all your cache from your browser to google maps gets saved to your sd card as well instead of your phone memory. The apps2sd was originally for the fact that you keep your apps, but when flashing hero roms, it did not work for some reason and it resulted in boot loops. So that's why they say always format your ext if flashing from a different rom. For stock roms, I don't believe this would be an issue so you probably could go on without wiping your sd as long as you are moving from a stock rom to another stock. It will not work if you go from stock to hero, and vice versa. Wipe data/factory reset clears all the settings from your phone so you do not have any lingering settings stored on the phone from an old rom when you flash a different one. The only time that you do not need to do this is if you are flashing a newer version of the same rom. The IME is probably still there, it just got unchecked from the input method. Go to locale and text and recheck the "input" box and it should work again.

yeah it is safest way to wipe and reformat the sd card before flashing a new rom.
tazz9690 said:
if you convert ext2 to ext3, there will only be ext3. It converts it from ext2, it does not make an additional partition. Davlik cache, if I am not mistaken is all your cache from your browser to google maps gets saved to your sd card as well instead of your phone memory. The apps2sd was originally for the fact that you keep your apps, but when flashing hero roms, it did not work for some reason and it resulted in boot loops. So that's why they say always format your ext if flashing from a different rom. For stock roms, I don't believe this would be an issue so you probably could go on without wiping your sd as long as you are moving from a stock rom to another stock. It will not work if you go from stock to hero, and vice versa. Wipe data/factory reset clears all the settings from your phone so you do not have any lingering settings stored on the phone from an old rom when you flash a different one. The only time that you do not need to do this is if you are flashing a newer version of the same rom. The IME is probably still there, it just got unchecked from the input method. Go to locale and text and recheck the "input" box and it should work again.
Click to expand...
Click to collapse
Previously I got a 2GB micro-sd card. so no problem for me to move my music, photos, videos and backup apps to my pc.
But i just bought a 8GB card 2 weeks ago and man, backup all before flashing a rom is pain in the a** . but can't help flashing this and that ROMs hee hee
so no choice. yesterday I flashed Eugene's supermagic rom. awesome!
cheers

tazz9690 said:
if you convert ext2 to ext3, there will only be ext3. It converts it from ext2, it does not make an additional partition. Davlik cache, if I am not mistaken is all your cache from your browser to google maps gets saved to your sd card as well instead of your phone memory. The apps2sd was originally for the fact that you keep your apps, but when flashing hero roms, it did not work for some reason and it resulted in boot loops. So that's why they say always format your ext if flashing from a different rom. For stock roms, I don't believe this would be an issue so you probably could go on without wiping your sd as long as you are moving from a stock rom to another stock. It will not work if you go from stock to hero, and vice versa. Wipe data/factory reset clears all the settings from your phone so you do not have any lingering settings stored on the phone from an old rom when you flash a different one. The only time that you do not need to do this is if you are flashing a newer version of the same rom. The IME is probably still there, it just got unchecked from the input method. Go to locale and text and recheck the "input" box and it should work again.
Click to expand...
Click to collapse
so when going to another rom should you part the sd before or after the rom is loaded? and honestly im running out of questions.. i got one that is throwing me off.. i have my phone in fastboot and in device manager it show andriod bootloader (cant remember the exact device); i type in the cmd
cd desktop
cd fastboot
then the code for the custom splash and i get
< waiting for device > and it just sits there. nothing will happen. & my splash is still stock.. the file is at the rights bytes and i have the folder on my cd on the desktop and the driver i beleive is installed correctly on the cp. what am i doing wrong?

I think the Title should be Changed, Something Like Recovery-101. Know Your Phone.
Alot of great Info for New comers

jdubdieslo said:
so when going to another rom should you part the sd before or after the rom is loaded? and honestly im running out of questions.. i got one that is throwing me off.. i have my phone in fastboot and in device manager it show andriod bootloader (cant remember the exact device); i type in the cmd
cd desktop
cd fastboot
then the code for the custom splash and i get
< waiting for device > and it just sits there. nothing will happen. & my splash is still stock.. the file is at the rights bytes and i have the folder on my cd on the desktop and the driver i beleive is installed correctly on the cp. what am i doing wrong?
Click to expand...
Click to collapse
Part the sd before you load the rom onto the phone. if it has apps2sd and you try to part your memory card after, you will get stuck at the splash more than likely because you are missing key components that are stored onto the sd, like all your apps for example that come with the ROM.
In fastboot, when it's plugged in, on the phone does it say "Fastboot USB"?
You might want to try to reupload the drivers for the fastboot. That may be why it's hanging. I never use fastboot through the desktop. I always use fastboot through the SDK folder on my C:\ drive. It always worked for me that way. For some reason I could never get it to work with the "cd destop" but thats just me.

tazz9690 said:
Part the sd before you load the rom onto the phone. if it has apps2sd and you try to part your memory card after, you will get stuck at the splash more than likely because you are missing key components that are stored onto the sd, like all your apps for example that come with the ROM.
In fastboot, when it's plugged in, on the phone does it say "Fastboot USB"?
You might want to try to reupload the drivers for the fastboot. That may be why it's hanging. I never use fastboot through the desktop. I always use fastboot through the SDK folder on my C:\ drive. It always worked for me that way. For some reason I could never get it to work with the "cd destop" but thats just me.
Click to expand...
Click to collapse
i figured taht was the right order part sd then load rom because i did it and it worked lol, and since it worked i never tried it rom the part sd. so do cyanogen roms have app2sd? and does the cyanogen rom have a overclocker built in now because i tried to use my overclock widget and it doesnt work and the phone seems as if its running faster even with out my widget..
and yes it says fastboot usb & ive tried uninstalling & reinstall the drivers mutliple times and still get < waiting for device > so if i do it on the c:/ drive were do i place the fastboot folder? /c:/fastboot? and what would the code be?
cd c:/
cd Fastboot
thent he other code that i have saved at home the flash_splash one? i cant remember it.
one really dumb question. i rooted my pops mytouch lol because he was complaining about the mytouch stock because of numerous things. so i rooted it to 4.2.2 and out of all things he is now complaining about the stock ringtones.. lol. anyone know where to get the stock ringtones? if not its cool i told him id make sum ringers with ringdroid for him like the temptations and willie nelson lol.. thanks all for your support.

jdubdieslo said:
i figured taht was the right order part sd then load rom because i did it and it worked lol, and since it worked i never tried it rom the part sd. so do cyanogen roms have app2sd? and does the cyanogen rom have a overclocker built in now because i tried to use my overclock widget and it doesnt work and the phone seems as if its running faster even with out my widget..
and yes it says fastboot usb & ive tried uninstalling & reinstall the drivers mutliple times and still get < waiting for device > so if i do it on the c:/ drive were do i place the fastboot folder? /c:/fastboot? and what would the code be?
cd c:/
cd Fastboot
thent he other code that i have saved at home the flash_splash one? i cant remember it.
one really dumb question. i rooted my pops mytouch lol because he was complaining about the mytouch stock because of numerous things. so i rooted it to 4.2.2 and out of all things he is now complaining about the stock ringtones.. lol. anyone know where to get the stock ringtones? if not its cool i told him id make sum ringers with ringdroid for him like the temptations and willie nelson lol.. thanks all for your support.
Click to expand...
Click to collapse
Cyanogen's rom has dynamic apps2sd. If it senses that you have a partition, it will do apps2sd. If you don't have an ext, it will save it to the phone, so it will work that way too.
For the fastboot, do you even have your computer set up for the use of ADB and fastboot? Like having the latest SDK downloaded and set up for your computer? That might be why it says, waiting for devices. When you do cd fastboot, afterward type fastboot devices and see if in the cmd it says "HTC Bootloader" or "Android Bootloader" I am not sure which one it is.
As for the ringtones, here is the link for the download in Cyanogen's 4.2.2 threat http://n0rp.chemlab.org/android/audio-resources.zip That downloads a zip of all the stock ringtones. Just upzip the file and place it on the root of your sd card.

tazz9690 said:
Cyanogen's rom has dynamic apps2sd. If it senses that you have a partition, it will do apps2sd. If you don't have an ext, it will save it to the phone, so it will work that way too.
For the fastboot, do you even have your computer set up for the use of ADB and fastboot? Like having the latest SDK downloaded and set up for your computer? That might be why it says, waiting for devices. When you do cd fastboot, afterward type fastboot devices and see if in the cmd it says "HTC Bootloader" or "Android Bootloader" I am not sure which one it is.
As for the ringtones, here is the link for the download in Cyanogen's 4.2.2 threat http://n0rp.chemlab.org/android/audio-resources.zip That downloads a zip of all the stock ringtones. Just upzip the file and place it on the root of your sd card.
Click to expand...
Click to collapse
thats good to know. so if you ext 2 will cm use ext 2 & if you converted it will it use ext 3? also how can i tell what i have ext 2 or ext 3 other than knowing if i click convert to ext 3? i downloaded the SDK and used the usb folder when the computer was looking for drivers & it says it installed drivers successfully; so now when im in fastboot usb on my phone the computer in device manager shows bootloader (cant remember exactly what it says untill i get home); & when my phone is in recovery the driver shows ADB (cant remember the exact name till i get home also); and then i do the codes because my fastboot & sdk folders are on my desktop; when i downloaded the sdk folder i dont think i did anything with it as far as isntalling it, what does the sdk folder do? lol. sorry..
thanks for the ringtones my pops says mucho gracias.

jdubdieslo said:
thats good to know. so if you ext 2 will cm use ext 2 & if you converted it will it use ext 3? also how can i tell what i have ext 2 or ext 3 other than knowing if i click convert to ext 3? i downloaded the SDK and used the usb folder when the computer was looking for drivers & it says it installed drivers successfully; so now when im in fastboot usb on my phone the computer in device manager shows bootloader (cant remember exactly what it says untill i get home); & when my phone is in recovery the driver shows ADB (cant remember the exact name till i get home also); and then i do the codes because my fastboot & sdk folders are on my desktop; when i downloaded the sdk folder i dont think i did anything with it as far as isntalling it, what does the sdk folder do? lol. sorry..
thanks for the ringtones my pops says mucho gracias.
Click to expand...
Click to collapse
I don't think any builds use ext2 anymore. They all either use ext3 or ext4. You have to make an ext2 first though, before you can convert it to ext3. Same goes for ext4, you have to have ext3 before you can upconvert to it. Just use ext3 just to be safe. If you go into "Parted" through the recovery image by typing in "parted /dev/block/mmcblk0" in adb shell, then typing 'print' it will show how big your fat32 is, it'll say which ext you have as well as your size, and the same for linux swap.
For a SDK, the folder stores the drivers needed for fastboot and adb in it. You should save it to the root of your C:\ drive because it makes things easier. I recommend you set up SDK using this thread guide: http://forum.xda-developers.com/showthread.php?t=532719
Setting up the Android 1.5r2 SDK
Download the file from above
Unzip to your desktop
Take the "android-sdk-windows-1.5_r2" folder and move it to the root of your hard drive (C:\)
Right click on My Computer and click properties
Select the Advanced Tab or Advanced System Setting (Vista)
Select Environment Variables...
Press New
For Variable Name type: adb
For Variable Value type: C:\android-sdk-windows-1.5_r2\tools
--------------------------------------------------------------------------
Preparing your phone for ADB
Go to Settings on your phone
Select Applications
Select Development
Make sure 'USB Debugging' is checked
--------------------------------------------------------------------------
Installing Drivers
Plug in your phone through USB and DO NOT MOUNT IT!!!!!
Your computer should see a new device and try to install Android 1.0 driver (If it doesnt, scroll down to the "Im not getting a notification of Android ADB when i plug in my USB" section)
Let it load
Once it cant find them select "Install drivers from my pc"
The drivers you need are in the Android SDK 1.5r2 folder (C:\android-sdk-windows-1.5_r2\usb_driver)
Depending on your OS pick x86 or amd64
You ADB Android Device should now be installed! Good Job
Those are basically what you need to look at.

jdubdieslo said:
I would like to know exactly what these do before i do them. sorry guys im a noobe..
Build:RA-magic-v1.2.3G
- wipe sd:ext partition
- Wipe SD:dalink-cache
- part sd:fat32+ext2+swap
- part sdnly fat32
- repair ext filesystem
- convert ext2 to ext3
- fix apk uid mismatches
- fix rotate
- USB Mass storage on
- USB Mass Storage off
Also how do you flash this recovery img from the Recover Flasher App, VS using CMD & fastboot.
Click to expand...
Click to collapse
Don't mean to hijack your thread OP, but I do have a question that I hope someone can answer. When partitioning the SD card, you choose the option I put in Bold. After that, could you use this link:
http://forum.xda-developers.com/showthread.php?t=535914
To adjust the different sizes of the 3 partitions? I know that in order to run any Hero ROMS, your SD card has to be partitioned with at least 3 (fat32+ext2+swap) parts. This is the only part that still confuses me when it comes to adequately rooting.

If you are using ubuntu, you create the partitions you want, as well as the size. If you use the recovery image, you would just be adding an unnecessary step because it will just get deleted when you make your partitions again with Ubuntu.

tazz9690 said:
I don't think any builds use ext2 anymore. They all either use ext3 or ext4. You have to make an ext2 first though, before you can convert it to ext3. Same goes for ext4, you have to have ext3 before you can upconvert to it. Just use ext3 just to be safe. If you go into "Parted" through the recovery image by typing in "parted /dev/block/mmcblk0" in adb shell, then typing 'print' it will show how big your fat32 is, it'll say which ext you have as well as your size, and the same for linux swap.
For a SDK, the folder stores the drivers needed for fastboot and adb in it. You should save it to the root of your C:\ drive because it makes things easier. I recommend you set up SDK using this thread guide: http://forum.xda-developers.com/showthread.php?t=532719
Those are basically what you need to look at.
Click to expand...
Click to collapse
So if u have a ext 3 how do u get ext 4? Also wat is linux swap? And yea i didnt do all that im sure thats why i was getting < waiting for device >. I will let u know the outcome of the splash screen... thanx.

jdubdieslo said:
So if u have a ext 3 how do u get ext 4? Also wat is linux swap? And yea i didnt do all that im sure thats why i was getting < waiting for device >. I will let u know the outcome of the splash screen... thanx.
Click to expand...
Click to collapse
If you want ext3, you have to go into parted like I stated in a previous post and create your partitions that way. From there, to upgrade to ext3, you type "upgrade_fs". You now have ext3. If you want ext 4, after that you would type
"tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p2
e2fsck -fpDC0 /dev/block/mmcblk0p2"
That's just too much work for me. I am fine with ext3. If you want a more in depth explanation, go to this thread: http://forum.xda-developers.com/showthread.php?t=534714&highlight=wipe+partition
Linux swap, I believe I explained in one of my early posts. The mytouch only has 192 mb of ram. The Hero's have 288 and so do the 32A board Sapphire phones like the HTC Magic and the Rogers Magic. Since we were unfortunate to get that low of Ram, if you try to run a hero rom without the linux partition, the phone will lag, freeze, and get load screens constantly. Using a linux swap partition makes it possible to run the Hero ROM's at a decent speed, though it will not be as fast as if you had the actual HTC Hero phone or a 32A Sapphire.

link2sd

I installed this and have all apps set. I thought this would save more internal space than just installing to sd? I have not gained any space with this??? I do however notice they load faster at boot though. am I incorrect in thinking it would gain me internal storage?
thanks
Sent from my VM670 using Bumblebee rom and Tapatalk

You need to manually move whatever your want to SD. (In settings you can choose apps, dalvik cache and libs; do not bother with libs, they will be back to /system after reboot). Anything already on SD (the native way, in android_secure on FAT) needs to be moved back to phone first.
N.B. You need a second partition for this on your SD card, in case you have not done it, it will not work at all

I moved everything back to phone then did the link2sd with libs and see no difference in space left
Sent from my VM670 using Tapatalk

is there a way to delete the lib file I did link? very confused why internal storage stayed the same?
Sent from my VM670 using Tapatalk

What lib file? Yeah, you are very confused really.

because you said not to bother with linking the libs..
my real question is this...
should link2sd save more internal space than just moving all apps to sd? if so.. mine did not..
thanks for the help
Sent from my VM670 using Tapatalk

Dunno how are you checking the saved/free space, if it is some widget then I would suggest to reboot the phone.

Hi! I'm on LG Optimus One and Gingerbread-2.3.4-rc4.1 /CM7 rom. My SD has one 512 MB ext3 partition and one 3,5 GB fat32 partition, class 4. When I run link2sd and choose ext3 (or other) type file system I receive this error:
Mount script error
Mount script cannot be created.
mount: mounting/dev/block/void/179:2 on /data/sdext2 failed: Device or resource busy.
I have reformatted the SD and reinstalled the rom more times but the error persists...
Please, Doktornotor, can you help me to found the culprit?

try to partition your sd card via adb. idk why, but when i tried to partition via clockwork, i had sd-ext as read-only. u can check if link2sd is mounting ok in shell (comand: mount) and look for /dev/block/void/179:2 on /data/sdext2 line . also check if ext partition is ro or wr.

Thanks for the hints! After many tries formatting the sd by linux or windows I have reached a conclusion: my SD is faulty and I will retry tomorrow (I hope) with a new one. See you!

Hi! After many tries I've changed my choices, uninstalled link2sd, uninstalled the ROM, keeping my good old SD.
Installed CM 7.1-RC0 6.5.5 by Mik_os, installed DT a2sd, et voila all runs flawlessly... seems like a miracle!

[Q] How to partiton sd card from CWM Recovery?

Okay, so, I want to flash hephappy's Cyanogenmod 9 (which looks amazing, btw you should check it out) which requires partitoning of the sd card. This is exactly what it says:
-Partition sdcard: swap-size: 64MB, Ext2-size: 300MB, Continue partitioning, SD:ext2 to ext3
So, I already know this means I have to move the contents of my sd card to a computer if I don't want its contents to be deleted. But anyway, how would I do this through ClockworkMod Recovery version 5.0.2.0? Also, for this ROM, is it completely necassary to paartiton my sd caard, what will happen if i don't, because I don't really need apps on my sd card.
Thanks in advance

It's not necessary
Will run perfect without it. If you want to use swap just use an app that creates a virtual swap on your sd.
Send from my phone...

Wait so your saying I don't even need to patition my sd card? Also, what does swap mean? (lol)

CWM doesn't give you option for creating a partition of 300mb,it gives either 256 or 512 mb.better use amonRA recovery or 512 mb partition.In order to partition first of all BACKUP all the data of your sd card then boot into CMW then go to advanced then partition then create partition then enter the given values of swap and memory.then wait for a while then you are done!! the memory card will be formated too so copy back the backed up files
---------- Post added at 07:47 AM ---------- Previous post was at 07:43 AM ----------
me_death said:
CWM doesn't give you option for creating a partition of 300mb,it gives either 256 or 512 mb.better use amonRA recovery or 512 mb partition.In order to partition first of all BACKUP all the data of your sd card then boot into CMW then go to advanced then partition then create partition then enter the given values of swap and memory.then wait for a while then you are done!! the memory card will be formatted too so copy back the backed up files
Click to expand...
Click to collapse
I also suggest you better use amonRA it partition is really needed then because according to above required requirements,amonRA recovery fulfills it exactly.you can partition 300mb,with swap size 64 mb and upgrade from ext2 to ext3 in that recovery.

I did this yesterday successfully... Backup ur six card data before u do this, cos it gets erased. In Cwm, go to partition sdcard, select ext size 512(doesn't matter if it's not 300) thn swap size 64. After success, reboot phone, install link2sd, run it, allow superuser access, select ext 2 wen it asks, reboot, open link2sd, goto settings, and select automatic linking.
Voila.. U are done!!
Works on my phone. Tested...
Sent from my LG-P500 using XDA

Ever heard of 4ext recovery ??
Sent from my HTC nexus one using XDA

[SOLVED] Forced Close of core (or all) apps, Internal SD removed unexpectedly...

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.

[MOD] Data2SD (Enhanced) - I/O Fix

At the suggestion of several users, I am forking the previous thread. I am planning on supporting several ROMs and this is the best course to keep everything organized and provide support.
What is this?
Background:
The speed of the flash memory in the Transformer line of tablets is very poor. This is very apparent when installing or updating applications from the Play Store, copying files over USB, or using an app that caches lots of data like a web browser. The tablet will hiccup and stutter due to the I/O bottleneck. Running Androbench shows random write speeds averaging less than .2MB/sec.
The workaround:
Utilizing a fast, class 10 microSD card, we can move the /data partition to something significantly faster. The /data partition is where apps are installed to and where they store their configuration information and data. By redirecting /data to these fast microSD cards, we eliminate this bottleneck from our devices. With a properly fast card, users have reported a complete elimination of I/O related hiccups and system freezes. I have based my enhancements on the initial work by TweakerL on the Transformer Prime. Credit to fordwolden to porting his work to the Infinity.
The enhancements:
Previous implementations of this mod had the internal data partition mounted to /data2, with the media subfolder (your internal user storage) only available via root apps. There were symlinks set up at /sdcardi, etc, but these still required root permission to access. This is due to permissions on the /data partition and applies to both /data and /data2. Google gets around this by creating a "virtual" sdcard that points to /data/media. I have created a second "virtual" sdcard that points to /data2/media. This mod creates the scenario below:
/data = ext4 partition on microSD (fast)
/data2 = ext4 partition on internal storage (slow)
New changes:
/data/media -> Virtual SD Card Daemon -> /storage/sdcard0
/data2/media -> Virtual SD Card Daemon -> /storage/sdcardi
/sdcardi -> Symlink -> /storage/sdcardi
/mnt/sdcardi -> Symlink -> /storage/sdcardi
/storage/sdcardi is the virtual SD card for the internal storage. You should see all the files you had saved to this space before using data2sd. These files should be accessibly by any standard non-root Android app.
Note to kernel developers: This mod is more than just changes to the kernel. In order for the internal storage to be properly mounted at /storage/sdcardi, I have modded the Virtual SD Card Daemon that comes with Android. The stock binary is /system/bin/sdcard. I made a copy, modified it using a hex editor, called it /system/bin/sdcardi, and included it in my flashable zips. If you wish to make a data2sd version of your kernel, you must include this file in your zip. Additionally, be sure to add the "service sdcardi" line to your init.cardhu.rc that I have in mine.
Installation
Requirements
1) Class 10 microSD, at least 8gb
2) A computer with card reader
3) Partitioning software. Recommended: gparted LiveCD
Instructions
1) Decide how big you want to make the ext4 partition for /data. Remember, this is going to be the space for installing applications AND the /sdcard space that games will use the cache their extra data. Kindle books, Dropbox files, pics from the camera WILL ALL GO HERE. Personally, I decided to make the ext4 partition the whole 64gb of my card.
The ext4 partition has to be partition #2 on the microSD card. Why? This is to give people with large cards the option of creating a FAT32 or NTFS area as partition #1. This allows the card to be read by a Windows or Mac computer using a card reader. I use my tablet as my card reader with the USB cable, so I wasn't worried about this. I used gparted to create a small 8mb unformatted partition as partition #1, then a second 64gb partition to fill the rest of the card. I formatted this second partition in ext4.
2) Format your microSD card - Download Gparted Live CD (http://goo.gl/dJQAu) and use Imgburn (http://goo.gl/33MY9) to write to disc. Boot to Gparted using your CD after setting the CD as the primary boot device in your BIOS. Once in Gparted, create the 2 partitions described above, the first partition is Fat32, the second partition is ext4 or ext2. Set both partitions to type: Primary.
3) Insert microSD into tablet and flash any data2sd kernel for your ROM. (Note: Flashing any ROM will overwrite your data2sd kernel. You will have to re-flash the data2sd kernel if you change ROM or even upgrade your current one) After booting back into Android, you should be greeted with the Setup Wizard. Remember, this is a fresh /data partition, so it's a clean slate. It's a good idea to take a TitaniumBackup** ahead of time. I am experimenting with ways to make the transition more painless.
**Note about taking a TitaniumBackup before switching to data2sd. After the conversion, your internal storage will be mounted to /sdcardi. By default, TitaniumBackup looks for previous backups in /sdcard not in /sdcardi. You have two choices. Copy the TitaniumBackup folder from /sdcardi to /sdcard and restart the app, or change the backup location to /sdcardi/TitaniumBackup in the app preferences. Either of these options should work fine.
Optional: Verify data2sd is working. Pick any method you like:
a) Open a file explorer such as Root Explorer, ES, etc. You should see /sdcard and /sdcardi and be able to browse the files within. /sdcard is your ext4 partion on the microSD while /sdcardi is the internal storage. You should able to copy data between them.
b) Download "Androbench" app from the market and run "micro" sdcard check, if you see 0.4mb/sec or more in random write you're on data2sd.
c) Power off your device, remove your microSD card, then power back on your device. You should received an error message "Encryption unsuccessful". Insert microSD and reboot to fix.
Uninstallation
Don't like data2sd? Just flash a non-data2sd kernel using recovery and when you boot back into Android your /data will be on the internal storage. This could also be accomplished by flashing your ROM on top of itself without wiping.
Troubleshooting
1) Grab the mount-data2sd.zip from the second post.
2) Boot into TWRP and flash the mount-data2sd.zip. This will mount the microSD as /data in recovery. It will allow us to wipe it, format, etc using recovery.
3) Wipe "Internal Storage". This will erase the entire ext4 partition on your microSD.
4) Flash ROM
5) Flash data2sd kernel for ROM
*CAUTION*: If you don't flash mount-data2sd.zip before your wipe, you will be wiping your internal memory.
Download data2SD kernels
These are flashable zips. It will disable journaling on the microSD ext4 partition. You do not have to do this manually! Flash these after flashing the ROM.
CyanogenMOD 10.1 - beta2: http://d-h.st/rOe (Based on 4-2 nightly and may behave unexpectedly on other builds)
CleanROM 3.2.2: http://d-h.st/sCa - WORKS WITH CleanROM 3.3!
clemsynTFUniversalCyano650GPUFsyncver3: http://d-h.st/duw
ClemsynTFUniversalStock: http://d-h.st/IBm
clemsynTFUniversal650GPUver7 (Stock/CleanROM): http://d-h.st/S4k

Recovery
I made a flashable zip to help the recovery console understand our modification. By default, if you go into recovery and do a factory reset, it is formatting the /data partition on the internal storage. The issue same applies to nandroids. We may be using the second partition of our microSD card for /data, but the recovery does not know this. It will look to the internal /data partition during backup and restores.
This zip does not make any modifications to your tablet or copy any files. It simply updates your recovery mount points. The changes are temporary and are lost during the next reboot. You will need to flash it each time you boot into recovery.
After flashing this zip you will be able to:
1) Wipe data / Factory reset. The /data partition on the microSD will be wiped
2) Backup and restore nandroids. The /data partition on the microSD will be backed up or restored.
3) Choose "Flash zip from internal sdcard" and browse the files on the internal storage
4) Access and flash zips from the microSD storage. Choose "Flash zip from internal sdcard" and notice the !microSD folder at the top. This is a symlink that will kick you over to the microSD storage. This !microSD folder appears on your internal storage after you flash this zip for the first time. It remains unless you delete it. Even so, next time you enter recovery this !microSD symlink will not go anywhere until you flash this zip.
Please report your experience with this.
http://d-h.st/pPe

This one too.

So this is basically flashable on CleanRom 2.3 right? Only thing wrong is that it doesn't show up in windows over USB? I can live with that as long as apps can read it in the Android OS itself.

can I use flash this on cleanrom 2.3 to diasable journalling on my ext4 partition

Diogenes5 said:
So this is basically flashable on CleanRom 2.3 right? Only thing wrong is that it doesn't show up in windows over USB? I can live with that as long as apps can read it in the Android OS itself.
Click to expand...
Click to collapse
Nope. This has changes to framework-res.apk which is ROM specific. I will post a CleanROM 2.3 version in a few minutes for you guys.

Thanks - Appreciate your hard work
---------- Post added at 08:46 PM ---------- Previous post was at 08:37 PM ----------
wow that was fast-thanks
---------- Post added at 08:58 PM ---------- Previous post was at 08:46 PM ----------
i was getting 6000 with clemsyn -I got low 5000's with this new mod

clownberg said:
i was getting 6000 with clemsyn -I got low 5000's with this new mod
Click to expand...
Click to collapse
This is not clemsyn's kernel, this is the stock CleanROM 2.3 kernel. I will mod clemsyn's latest kernel and post it for you.

Mistar Muffin said:
This is not clemsyn's kernel, this is the stock CleanROM 2.3 kernel. I will mod clemsyn's latest kernel and post it for you.
Click to expand...
Click to collapse
Unable to have it work with cleanrom. Boot loop

titou00075 said:
Unable to have it work with cleanrom. Boot loop
Click to expand...
Click to collapse
Use recovery to wipe the /cache partition. Due to the changes in framework-res.apk this may be necessary if you aren't coming from a completely clean install of a ROM.
I just booted to recovery and wiped my microSD /data partition. I also wiped /cache and /system. I installed CleanROM 2.3 and in the same recovery session I flashed the clemsynTF700ver22GPU650VC-data2sd kernel and it booted right up.

May be a stupid question but do you still need TWO primary partitions on the SD card (i.e., first is FAT32 while second is Ext4 and used by the mod)? If this isn't necessary or not possible, should the recovery (i.e., installation) files be placed in internal storage?
Forgot to mention I'm using Windows 7 MTP and CleanROM 2.3

Mistar Muffin said:
Use recovery to wipe the /cache partition. Due to the changes in framework-res.apk this may be necessary if you aren't coming from a completely clean install of a ROM.
I just booted to recovery and wiped my microSD /data partition. I also wiped /cache and /system. I installed CleanROM 2.3 and in the same recovery session I flashed the clemsynTF700ver22GPU650VC-data2sd kernel and it booted right up.
Click to expand...
Click to collapse
Ok thanks. Will do:thumbup:

Your Awesome, Thank you!

cheers
Thanks Gonna try this.
done the work install all three files in the OP, however it is taking a long time to boot....Can someone give me an idea as to how long this normally take onn first bootup after a fresh install?
please advise
tyfoxx

Couldyou make one for blackbean? i tried thecm 1029,but it doesnt boot. Would greatly appreciate it.

Sweet
I just ran every shortcut I could think of:
I used Mini partition tool to reduce reduce my 32 gig fat down to 16 gigs & then created a 16 gig ext4 partition.
Wiped everything in twrp and re flashed Clean 2.3 then the new zip.
All I can say is WOW.

Restored everything. Works great no more stalls and stable so far. Hope it stays this way. Now to focus on battery life.
Sent from my HTC Ruby using xda app-developers app

Diogenes5 said:
Restored everything. Works great no more stalls and stable so far. Hope it stays this way. Now to focus on battery life.
Sent from my HTC Ruby using xda app-developers app
Click to expand...
Click to collapse
Glad it's working! I've prepared a little treat for everyone to make our recovery lives a little easier. Need to test a few more things before I post!

I'm running CleanROM 2.3 and ClemsynTF700ver22GPU650VC (awesome combo, btw). If I want to use this MOD, should I need to flash first CleanROM-2.3-data2sd.zip and later ClemsynTF700ver22GPU650VC-data2sd.zip, right? Of course, also, formating my microSD using ext4.

Awesome work here Mistar!!!! Thank you so very much for this!!! Gonna replace my SanDisk 32gb Class 4 card with a SanDisk 64gb Class 10 before I run this on CleanRom. I'm super excited about this mod!!!!!! Thanks a million!!!!!!
Sent from my EVO 4G LTE using xda premium