Related
I flashed Eugene's Vibrant9 and it was working fine. I was testing a backup application I have and did a master reset through recovery. Wiped cache and user data. Now when I start up a lot of processes force close, but one continues to the point where I cannot do ANYTHING on the phone. android.process.media/phone is in the force close.
My thought is if I had an update.zip saved to the internal memory I could run through recovery and flash that, but for some reason I do not. Without being able to get into the phone to mount I cannot move the file to the internal memory.
Right now my thought is I either have to find a way to be able to the notifications to mount the SD or there be another way to make this work. I have tried going through safe mode and it is no different than booting the normal way.
Any suggestions?
And it's fixed. It required quite a bit of work.
First one problem was it unrooted itself when I did this.
Push the root zip through adb and flash. Do the same for clockwork recovery. Do the same with the rom. Problem solved.
Never again.
THIS UTILITY IS FOR FASCINATE TOUCHWIZ FROYO/GINGERBREAD ONLY
UPDATED FOR EC09 GINGERBREAD
I have created a format utility that can be used from within CWM3 recovery. Just select the ZIP in CWM3 recovery, and the package will do ALL of the work for you.
These utilities come in two independent packages which will completely format your device with EXT4. As a bonus, it will create all directories and setup all ownership and permissions in accordance to the Fascinate.
Voodoo recovery does not currently allow you an option to select a format style, and furthermore does not truly format any partition unless it runs through the Voodoo "lagfix" transition upon booting the device.
There is one caveat in order to use EXT4: you need a kernel that supports it, and this would be using a "Voodoo" style kernel that has built in support. Luckily, most of the "good" kernels available have this ready to go.
Understand that this package will completely wipe your system, data, datadata (dbdata), and cache. This is a "full" wipe of the device. If you already have a ROM installed on your device and want to keep your device the way it is, and also want EXT4, then use the Voodoo method to switch to EXT4. The reason for this is because it backs up your data before it formats.
After you use this package, you can install any ROM of your choosing, as the package will already self-manage Voodoo's methods for "enabling" or "disabling" the "lagfix".
--------
Please report if the package is not working.
A good indicator of this is if you try to install the package and it only takes 1 second to work, then says it is finished. This means it is probably not working, however, if you are formatting the same type of file system over itself with no pre-existing data on the device, it will take the aforementioned 1 second to work.
To see if it worked: mount each partition in CWM3 recovery, then adb shell into your device and type the mount command, in the listing you should see what file system your partitions are using. If the big four all say EXT4, then the package install has been successful.
In order to assure that it will work correctly, use the latest version of a CWM3 recovery that you can find. I can personally vouch for nemesis2all's OTB CWM3 Recovery v3.0.2.8x.OTBv2. Unfortunately not all CWM3 recoveries are the same, and yours may not work with these utilities. If you find a recovery that works fine, post it here and I will update this.
--------
Packages updated: 6/28/2011 - 12:57PM EST
EXT4 Format ALL (formats everything): http://www.mediafire.com/?6hx7f8g7c8vv6xz
EXT4 Format CACHE: http://www.mediafire.com/?2621a888ydv41mg
EXT4 Format DATA: http://www.mediafire.com/?ck2bb340yybpe4z
EXT4 Format DBDATA: http://www.mediafire.com/?ahxzs8xsyyvemed
EXT4 Format FOTA: http://www.mediafire.com/?42ijpi67grdb6mm
EXT4 Format PREINSTALL: http://www.mediafire.com/?d42as1l3pdbhr2t
EXT4 Format SYSTEM: http://www.mediafire.com/?rgs46hhq8qd951t
--------------------
If you like my work, consider donating, or thanking me by clicking the thanks button
thanks for this
navenedrob said:
I have created two format utilities that can be used from within CWM3 recovery. Just select the type of file system you want to use, select it in CWM3 recovery, and the package will do ALL of the work for you.
These utilities come in two independent packages which will completely format your device with either RFS or EXT4. As a bonus, it will create all directories and setup all ownership and permissions in accordance to the Fascinate.
Voodoo recovery does not currently allow you an option to select a format style, and furthermore does not truly format any partition unless it runs through the Voodoo "lagfix" transition upon booting the device.
There is one caveat in order to use EXT4: you need a kernel that supports it, and this would be using a "Voodoo" style kernel that has built in support. Luckily, most of the "good" kernels available have this ready to go.
Understand that this package will completely wipe your system, data, datadata (dbdata), and cache. This is a "full" wipe of the device. If you already have a ROM installed on your device and want to keep your device the way it is, and also want EXT4, then use the Voodoo method to switch to EXT4. The reason for this is because it backs up your data before it formats.
After you use this package, you can install any ROM of your choosing, as the package will already self-manage Voodoo's methods for "enabling" or "disabling" the "lagfix".
Please report if the package is not working.
A good indicator of this is if you try to install the package and it only takes 1 second to work, then says it is finished. This means it is probably not working, however, if you are formatting the same type of file system over itself with no pre-existing data on the device, it will take the aforementioned 1 second to work.
To see if it worked: mount each partition in CWM3 recovery, then adb shell into your device and type the mount command, in the listing you should see what file system your partitions are using. If the big four all say EXT4 or RFS (depending on script used), then the package install has been successful.
In order to assure that it will work correctly, use the latest version of a CWM3 recovery that you can find. I can personally vouch for nemesis2all's OTB CWM3 Recovery v3.0.2.8x.OTBv2. Unfortunately not all CWM3 recoveries are the same, and yours may not work with these utilities. If you find a recovery that works fine, post it here and I will update this.
Click to expand...
Click to collapse
Ok, I think I'm having a complete idiot moment here so please be patient with me. What would be the benefits of me running this on my device that is currently running jt's CM7 with OTB 1.5 kernel and EXT4 (voodoo for those who don't know) already converted? Thanks in advance.
It would be of no use. Unless you need to format your entire device.
So this would be a good thing to flash in place of wiping between rom flashes? Does it have any benefits compared to a regular data and cache wipe when you are already converted to ext4?
It would be a good idea to flash it in that scenario, yes. Currently no ROM will do the job that this package will for you, which is why a lot of ROM's say not to wipe your device, because you'll run into major issues if you do. When you do your "wipes" through recovery it doesn't really do anything besides a recursive delete of files, so it doesn't really format anything (even though it says "format" in the menu system). The only time it actually does any formatting is during the Voodoo transition. When you do wipe those areas, it does not leave the file structure intact and also does not leave the ownership and permissions intact. These packages completely solve that problem. Also, these packages are focused on performance so everything is done that is possible to make sure that your file system is as fast as possible.
navenedrob said:
It would be a good idea to flash it in that scenario, yes. Currently no ROM will do the job that this package will for you, which is why a lot of ROM's say not to wipe your device, because you'll run into major issues if you do. When you do your "wipes" through recovery it doesn't really do anything besides a recursive delete of files, so it doesn't really format anything (even though it says "format" in the menu system). The only time it actually does any formatting is during the Voodoo transition. When you do wipe those areas, it does not leave the file structure intact and also does not leave the ownership and permissions intact. These packages completely solve that problem. Also, these packages are focused on performance so everything is done that is possible to make sure that your file system is as fast as possible.
Click to expand...
Click to collapse
Ok, so basically what you are saying is this would be ideal to use instead of data/cache/dalvik wipe for rfs to rfs and ext4 to ext4, correct? Thanks in advance.
That's correct.
I've teamed up with nemesis2all and we are thinking about adding all of these abilities to the OTB kernel, so you'll be able to choose different kinds of file systems and format options through CWM3 recovery instead of having to use these packages here. That will come when it comes, but for now this is the ideal solution.
EXT2/EXT3/EXT4/XFS/RFS etc...
Also, I've updated the attachments in the post.
navenedrob said:
That's correct.
I've teamed up with nemesis2all and we are thinking about adding all of these abilities to the OTB kernel, so you'll be able to choose different kinds of file systems and format options through CWM3 recovery instead of having to use these packages here. That will come when it comes, but for now this is the ideal solution.
EXT2/EXT3/EXT4/XFS/RFS etc...
Also, I've updated the attachments in the post.
Click to expand...
Click to collapse
Just to let you know, I ran the ext4 package and I got some serious lag issues after I installed my rom and it actually starting going into a soft boot loop. It began to act very weird and unstable. I booted back into recovery and I wiped everything the way I usually do and formatted the system/data/dbdata/cache manually in mounts and storage and reinstalled. It's better than it was but it still seems like it is kinda slower and more laggier than it was before I ran the package. Any ideas? Thanks man.
You'll need to give me more information than that to determine your problem.
What kernel are you using? What recovery are you using? What ROM are you running? What are the results of running the mount command with all partitions mounted?
navenedrob said:
You'll need to give me more information than that to determine your problem.
What kernel are you using? What recovery are you using? What ROM are you running? What are the results of running the mount command with all partitions mounted?
Click to expand...
Click to collapse
OTB 1.5, CM7. It's kinda weird. When I ran your package and then flashed cm7 and booted it, it was laggier than I have ever seen my phone and when I would try to do certain operations it would soft boot. At one point I couldn't even turn wifi on. So, I booted back into recovery and wiped and manually formatted everything and reinstalled everything. After that it was still kind of laggy but much better. I restored all of my apps and got my phone back to all my custom settings. Then I began to notice that it wasn't really lagging anymore, in fact it seemed pretty snappy. I ran quadrant to see if the numbers were the same as before to determine if I was in fact ext4 converted. Surprisingly the numbers were higher than normal. And I even noticed in titanium backup that some of my internal memory had been freed up. I can't explain it but everything seems to be running really good right now. It's almost like after running your package the phone had to be conditioned, and once it was conditioned it ran real good. But, that doesn't explain why it was soft booting and wifi wouldn't work. Who knows.
Not really sure exactly, it actually could have been a few different things causing the "issues". I'm going to try your exact scenario and see what happens.
kidserious said:
OTB 1.5, CM7. It's kinda weird. When I ran your package and then flashed cm7 and booted it, it was laggier than I have ever seen my phone and when I would try to do certain operations it would soft boot. At one point I couldn't even turn wifi on. So, I booted back into recovery and wiped and manually formatted everything and reinstalled everything. After that it was still kind of laggy but much better. I restored all of my apps and got my phone back to all my custom settings. Then I began to notice that it wasn't really lagging anymore, in fact it seemed pretty snappy. I ran quadrant to see if the numbers were the same as before to determine if I was in fact ext4 converted. Surprisingly the numbers were higher than normal. And I even noticed in titanium backup that some of my internal memory had been freed up. I can't explain it but everything seems to be running really good right now. It's almost like after running your package the phone had to be conditioned, and once it was conditioned it ran real good. But, that doesn't explain why it was soft booting and wifi wouldn't work. Who knows.
Click to expand...
Click to collapse
It's possible that since you wiped your market was trying to restore all your apps in the back ground which was taking all your memory up and making your phone lag. But after you restored all your apps it was all set
Coreyc1123 said:
It's possible that since you wiped your market was trying to restore all your apps in the back ground which was taking all your memory up and making your phone lag. But after you restored all your apps it was all set
Click to expand...
Click to collapse
What I meant was as soon as it booted (during setup wizard) it was super laggy. I download TB from the market by itself and it took forever to register. I was doing the GPS fix and it soft booted. I couldn't turn wifi on and it soft booted. All before I did a batch restore in TB. And I know that the market begins to sync automatically as it always does but this was much much different.
Sent from my SCH-I500 using Tapatalk
kidserious said:
What I meant was as soon as it booted (during setup wizard) it was super laggy. I download TB from the market by itself and it took forever to register. I was doing the GPS fix and it soft booted. I couldn't turn wifi on and it soft booted. All before I did a batch restore in TB. And I know that the market begins to sync automatically as it always does but this was much much different.
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
I had these same symptoms one time that I installed kasonate v7, but after reflashing, the next time it didnt.
I know you're not talking about the same cm version, but they might be related and not related to the format utility.
Ok, I ran this package again to make sure that I didn't do something wrong and to see if I would get the same results. I ran the package, flashed cm7 then gapps then OTB GB 1.5. all from the recommended recovery in your post. Again I ended up in a soft boot loop and wifi was acting up again and was causing a boot loop. So once again I booted into recovery and wiped data/cache/dalvik normally and formatted manually via mounts and storage and reinstalled again and she's running like a dream. Very weird but I must say I am very happy with the results I ended up with, regardless of how I got them. So obviously, this was not your intention for it to be done this way but I do see an improvement in responsiveness, speed and memory being freed up. Before, my free internal memory was 1.49 and now it is 1.52. Thank you sir, I appreciate this.
Thanks for this utility! Works great. Went from Jt's cm7 to the miui/touchwiz rom and ran the utility in between. My phone is running faster than ever and no issues. Thanks again!
Sent from my SCH-I500 using XDA App
Yeah running this on mesmerize with heinz 57 best my phone has ever run quadrant of 2250s @ 1.5 ghz
Sent from my SCH-I500 using XDA App
stephenj37826 said:
Yeah running this on mesmerize with heinz 57 best my phone has ever run quadrant of 2250s @ 1.5 ghz
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
You're welcome, the utility enables a few nice options as far as file system performance is concerned, that Voodoo doesn't at this time.
Do tell oh and thanks a million
Sent from my SCH-I500 using XDA App
Hello, I'm running RR 2.6.1 with Dorimanx's latest kernel and I've run into a huge problem.
I'm not sure what the trigger is but I think it could be updating the SuperSU app, or it could just be that I'm super unlucky. In any case, I really really hope someone will be able to help me here.
I was facing random freezes and SODs on the kernel but I was in the midst of tweaking my settings to see if I could fix it. I updated the SuperSU app on the bus on the way home, went home & tried to power my phone on but it wouldn't work so I force-restarted by holding down the power button. When it rebooted, I had all sorts of FCs so I went to CWM Recovery & cleared cache & dalvik & fixed permissions. Nothing worked. Here's what I've tried so far:
- reflashing the kernel
- reflashing the ROM
- re-rooting via Odin
- flashing another kernel (I tried fluxi but it was stuck at the animation screen & wouldn't boot)
- Googled for how to fix process.acore and Gapps FCs, tried to clear all the Google-related apps' data but they wouldn't clear
- trying to delete the apparent offending files from /data/data/... via adb and Android Explorer but it didn't work, kept saying it was read-only or something, even though I followed all the instructions to SU and mount as RW
By this time, exTweaks didn't recognise the kernel as compatible, Whatsapp and TB FC'd, just about everything FC'd.
I went into CWM Recovery to try and make a Nandroid but it said "Error while making a backup of /data".
I am truly at my wits' end. My phone wouldn't even let me access it after the right passcode was input. At this point, I just want to go in and backup my Whatsapp and relevant TB apps.
Please, if anyone is able to help me, PM me or something. I'm on Skype if you're so kind as to be willing to walk me through anything you think may help.
Thank you.
Flash a clean ROM, wipe cache and dalvik, do a factory reset and start from scratch.
Multiple fc can be caused due to several reasons like:
-wrong phone.apk
-wrong framework
-wrong ROM
-too much undervolt
Sorry for telling but my first sentence might be your fastest approach.
Tapatalked from my Samsung GT9100
Tyrol said:
Hello, I'm running RR 2.6.1 with Dorimanx's latest kernel and I've run into a huge problem.
I'm not sure what the trigger is but I think it could be updating the SuperSU app, or it could just be that I'm super unlucky. In any case, I really really hope someone will be able to help me here.
I was facing random freezes and SODs on the kernel but I was in the midst of tweaking my settings to see if I could fix it. I updated the SuperSU app on the bus on the way home, went home & tried to power my phone on but it wouldn't work so I force-restarted by holding down the power button. When it rebooted, I had all sorts of FCs so I went to CWM Recovery & cleared cache & dalvik & fixed permissions. Nothing worked. Here's what I've tried so far:
- reflashing the kernel
- reflashing the ROM
- re-rooting via Odin
- flashing another kernel (I tried fluxi but it was stuck at the animation screen & wouldn't boot)
- Googled for how to fix process.acore and Gapps FCs, tried to clear all the Google-related apps' data but they wouldn't clear
- trying to delete the apparent offending files from /data/data/... via adb and Android Explorer but it didn't work, kept saying it was read-only or something, even though I followed all the instructions to SU and mount as RW
By this time, exTweaks didn't recognise the kernel as compatible, Whatsapp and TB FC'd, just about everything FC'd.
I went into CWM Recovery to try and make a Nandroid but it said "Error while making a backup of /data".
I am truly at my wits' end. My phone wouldn't even let me access it after the right passcode was input. At this point, I just want to go in and backup my Whatsapp and relevant TB apps.
Please, if anyone is able to help me, PM me or something. I'm on Skype if you're so kind as to be willing to walk me through anything you think may help.
Thank you.
Click to expand...
Click to collapse
Try the following:
-Download this: Ultimate kernel cleaning script
-Reboot to CWM recovery
-Flash Ultimate kernel cleaning script
-Under kernel specific option, Reset extweaks settings
-format /system (under Mount and storage)
-Flash ROM (RR 2.61)
-Flash Gapps
-wipe cache partion
-wipe dalvik cache (under advanced)
-fix permissions (under advanced)
-Reboot your phone
My above steps will not wipe your and should definitely fix your problem
good luck
Thank you both for your suggestions!
Unfortunately, I didn't get to try them but I'll definitely be checking this again if (touch wood) this happens again. Hopefully it'll be useful to someone else facing similar issues, I know I couldn't find clear answers on what to do.
@jokesy If the /data partition is somehow stuck at read-only, I'm not sure formatting /system will help. I could be wrong, I apologise if I sound ungrateful ('cause I do appreciate your help) but wouldn't reflashing a ROM kind of overwrite the existing /system files already?
I'm not aware of the details and technicalities of what exactly happens during a ROM flash but according to the AROMA installer, it seems like /system is wiped first.
What I did
Gave up on backing up apps & WhatsApp through the normal ways, most of my TB apps are backed up daily anyway, just lost some data like that for Sleepbot.
Pulled WhatsApp database files from /data/data/com.whatsapp via ADB, restored the previous day's Nandroid backup & copied the database files to the relevant directory. I guess it may seem minor, but as everything was melting down on my phone, I kept getting messages from friends about project work in school & other stuff that I couldn't read so I really wanted to not lose all the new messages that had come in.
Restoring my Nandroid (thank God I backup daily) fixed everything, fortunately, but there are little quirks I'm still ironing out. Eg. My Godville app can't seem to connect to the main server & retrieve details of my character despite clearing data, uninstalling & reinstalling. Not too sure why.. :/
-----------------------
サンソングガラクシS II からタパトクで書いた。
@Tyrol
Ididn't know you were using aroma installer though, but formatting /system has nothing to ago with /data sms vice versa
Following my wouldn't have hurt though, ur would only ensure a clean system partition before install.
I'm happy for you
Better luck next time
Swyped from my Samsung Galaxy SII
I recently had a very similar problem. The only way I could resolve it was to also format /data during the usual full wipe re-install
Karl.morteo said:
I recently had a very similar problem. The only way I could resolve it was to also format /data during the usual full wipe re-install
Click to expand...
Click to collapse
Tough luck man. I don't know why the data corrupts spontaneously, it happened once to me when I was playing Plague, everything started FC-ing all of a sudden while I was in-game. Bizarre. Didn't want to do a full wipe so I just restored the /data partition from my latest Nandroid.
-----------------------
サンソングガラクシS II からタパトクで書いた。
This error is still not answered on the forums so im starting a new thread.
i get the error as the title.
sd card space is not the problem.
i tried formatting the sd card.
i have less than 50 apps installed.
wiped dalvik cache, and all other sorts people say on other posts.
(my phone is LG P936 so "fix permission" screws up the phone. all text disappears)
have latest cwm recovery.
and still get the error.
any answers please?
and please dont reply if you are going to write an opinion.
only answers please.
sorry for my rude behaviour but I'm sick and tired of reading posts full of opinions and "maybe"s.
Not sure if you ever got this fixed but I 'm suffering from the same error. I tried pretty much everything you tried (even fix permissions) and I have about 20GB free on my SD card so space shouldn't be an issue. I have not yet tried formatting the SD card since it has always worked and CWM is able to write to it because the following files are created:
- boot.img
- data.ext3.tar
- recovery.img
- system.ext3.tar
The files that are missing are (based on older backups):
- .android_secure.vfat.tar
- cache.ext3.tar (probably because I wiped it first?)
- nandroid.md5
I have attached the log from CWM in the hopes that someone can tell me what is wrong. The error occurs at the end of the progress bar of 'backing up /data'.
hey just use TWRP Recovery. It's way better than CWM. normal backup on cwm took me like an hour but twrp was never longer than 10minutes.
Today I have formatted the SD card and tried again, but as expected it did not change anything.
ceoleaders said:
hey just use TWRP Recovery. It's way better than CWM. normal backup on cwm took me like an hour but twrp was never longer than 10minutes.
Click to expand...
Click to collapse
I guess I will give this a try. Can I just install it over CWM or can they run side by side?
different reciveries cannot be run side by side as they are installed on a different partition. so it will always be installed over your current one.
ceoleaders said:
different reciveries cannot be run side by side as they are installed on a different partition. so it will always be installed over your current one.
Click to expand...
Click to collapse
Well, I tried TWRP and it also fails at backing up my data partition. The log is a bit more clear though and it seems to get stuck on "/data/data/com.android.vending/cache/images" which is the last line before it gives an error. I checked the "images" folder and it seems empty but I cannot delete it. Tried ES File Explorer and Terminal Emulator but no way to get rid of it. The folder appears to be related to Google Play, so I cleared all data and cache from Google Play, even uninstalled the updates but there 's simply no way to get rid of it. I 'm not sure if this is the reason why the backup fails, but I CAN copy the folder and even rename it.
Pff looks like I 'm going to have to do a clean install after all .
Hello, I too have this problem and unfortunately TWRP is not available for my phone.
I used to be able to do CWM backups fine on my old phone, and they work great on my tablet. But they consistently fail at "/data" on my Galaxy Ace II x. Might it be because I'm using Link2SD? I don't see why that would cause a problem, but maybe it's having trouble with the symlinks?
Hmm. Seems the issue was that, despite having only 1.28 GB total available storage space on stock, the backups wanted more than 4 GB. Cleared some room on my microSD card and suddenly backups worked fine! Of course, shortly after I installed CyanogenMod, which has much smaller backups...
Sent from my GT-S7560M using Tapatalk 4
I forgot to report back here but the only way I found to fix the problem was by doing a clean install. After that, I was able to backup my data partition again. I then restored my apps ' data with TB and was unable to backup the data partition again. I 'm guessing one of my apps had corrupt data, but never got to find out which one it was.
maybe your partition not match with recovery, like something wrong vold.fstab
Just in case anyone still wants to know how to fix this, I managed to solve it by running these commands:
1. run adb shell in recovery.
2. unmount data partition (umount /dev/block/mmcblk0p26). -> this one failed so I skipped it
3. run e2fsck /dev/block/mmcblk0p26
See http://forum.xda-developers.com/showpost.php?p=48659092&postcount=868 for original post.
I got a few HTREE errors and a bunch of duplicate names which I renamed when prompted. Booted the phone and rebooted into TWRP and now I am able to backup my data partition again. :good:
EDIT: Problem reappeared so I tried the above commands again but it said that the filesystem was clean. Ran 'e2fsck -f /dev/block/mmcblk0p26' instead and had to fix a bunch of HTREE errors from Facebook again and duplicate names from Xprivacy but now I 'm able to backup my data partition again.
Dude just selest the backup format as both zip and tar filea
After many weeks finding all the possible means to fix my Vibrant with a non-mountable internal SD, here some hints for future users do not waste too much time, as I did, trying to fix it.
Of course there are many "PHD"Threads, regarding this topic, in the forum, but many are kinda confusing or not for this specific mobile model.
If your recovery keeps saying that it "cannot mount internal SDcard"or Cannot mount mmcblk0p2, means your internal SD is gone and you have lost all the data on it (Blame Samsung, and its cheap hardware, for that).
First of all, DO NOT WASTE TIME TRYING TO RECOVER IT.
I have seen many people that have wasted precious time trying to Lagfix, Repartition, Flashing it to stock over and over, popping out batteries and so on, and nothing worked. You can give it a try (other posts have many outcomes). But for me it was only worries and no fun.
here`s how I definitely figured it out:
- If you`re acessing the recovery (CWR, Semaphore, Overstock, or whatever kernel), you`re good to skip the flashing process. If not, Back up all your data (oops, there`s no data to back-up :silly: - So why many posts keep saying that, regarding this issue??) and flash it ODIN back to stock (links and files of how to do it can be found within the forum). I used the SGH-T959.tar and 802.pit file. No need to check any of the options (repartition, reboot,...), but no problem if you do.
- If you have stock or not, remove your external SD card from the phone and plug it into your computer DIRECTLY (do not do it remotely via USB-Phone connections). Download your preferred partitioning software (I use Mini Tool Partition) and reparation your SD card in 2 blocks (one FAT32-Primary and the other EXT(4 or 2)) - Do not need to warn you`ll lose all the data in the SDCard - Doesn`t matter the sizes, but be sure you`ll have, at least, 1gb at each side (otherwise you may not have enought memory for apps and midias). To learn how to do that, please rely on specific posts on this subject.
- Copy your preferred ROM and GApps ZIP file on your FAT32 SDCard partition. Copy also this very handy zip file from this genius guy:laugh: (It will spare you from the annoying task reedit the vold.fstab file and also the risk of screwing-up the installation process and have to start all over, and over - for me was like 200 times). Plug back the SD into the phone and turn it on recovery mode.
- Once you`re in recovery mode (see how to do it over the forum as well), choose the specific ROM for your kernell. I suggest always to use the CWM 5.2 because it handles most of the android versions. And also prefer the Cyanogen Mods, since the SlimBean rom has caused this whole issue with my phone (Yes! The ROM can ruin your device, so choose it wisely).
- Chose install from SD card and then install zip from SDcard. Install your ROM, GApps and the linked vold.fstab.zip file, in a row. If you have an error message during the installation (with a warning sign over the robot), it means you`re under an incompatible kernell and must switch to the one compatible with your Android version (see details about that in the forum as well). If everything installed correctly, reboot the phone and have fun.
- "Voilá", you now may have a fully operating phone again. The bigger the SD card capacity you choose the better.
Hope to have a simple clear summary of how to fix this not-cool-at-all Samsung bug on Vibrants.
This is what I did and it worked for me.
http://forum.xda-developers.com/showthread.php?p=44794712
And 2 posts down I explain what I did