Database Users

Only Boots into Recovery

I was having some pretty serious problems with Bionix 1.7 (couldn't download from market, unusably bad GPS, etc), which I thought I had successfully flashed yesterday afternoon. I decided to use Clockwork Mod to restore a backup I made before I flashed Bionix. This hung up for quite a while (upwards of 20 minutes) so I figured something had gone wrong. I held the power button until the screen turned off, and that put me right into Android Recovery, where I get the options to reboot (puts me right back there), reinstall packages (puts me into Clockwork Mod, which I'll get to in a second) or delete user data / cache, which I haven't messed with.
If I go into Clockwork Mod, I can tell it to try to restore one of my previous backups again, but it hangs up indefinitely (upwards of several hours) at "Restoring data..." (with either immvbsd.lck or .pc_syncstream below that). I can also still see the Bionix .zip on my SD card, but when I tell Clockwork Mod to install that .zip it gets this far:
Formatting DATA:...
Copying files...
E:Failure at line 81:
copy_dir PACKAGE:data DATA:
Installation aborted.
Ideas?

Okay, so apparently, the problem may have been that I didn't disable the Voodoo lagfix before I flashed back to my old ROM. I figured you only had to disable the lagfix if you were upgrading, not flashing back. So, I used ADB to push a disable-lagfix file to /sdcard/voodoo and rebooted. I heard Linda say that my file system converted back to RFS, and my phone went back to recovery. From here, I tried two things:
1. Attempted to flash back to a previous Nandroid backup. No matter what backup I pick (and I have several), they all complete successfully. However, when I choose to reboot my phone, it boots into recovery.
2. Attempted to install Bionix 1.7 though Clockwork. It appears to install successfully and gives me an "Installation complete." message, but puts me right back in recovery. Rebooting the phone from here puts me back into recovery again.
Since I'm on a mac right now, I'm really avoiding having to get on a Windows machine just to use ODIN, but I will if that's my only way out. Any alternatives?

opiomorph said:
Okay, so apparently, the problem may have been that I didn't disable the Voodoo lagfix before I flashed back to my old ROM. I figured you only had to disable the lagfix if you were upgrading, not flashing back. So, I used ADB to push a disable-lagfix file to /sdcard/voodoo and rebooted. I heard Linda say that my file system converted back to RFS, and my phone went back to recovery. From here, I tried two things:
1. Attempted to flash back to a previous Nandroid backup. No matter what backup I pick (and I have several), they all complete successfully. However, when I choose to reboot my phone, it boots into recovery.
2. Attempted to install Bionix 1.7 though Clockwork. It appears to install successfully and gives me an "Installation complete." message, but puts me right back in recovery. Rebooting the phone from here puts me back into recovery again.
Since I'm on a mac right now, I'm really avoiding having to get on a Windows machine just to use ODIN, but I will if that's my only way out. Any alternatives?
Click to expand...
Click to collapse
Unfortunately it sounds indeed like you need to use ODIN to flash and re-partition your phone's file system. You're going to need to make sure you use the stock rom (JFD) to do this, other wise you'll be stuck in the recovery loop yet again with a different error message.
So far as being on a Mac goes, I've heard that some people have luck using ODIN through the newer version of parallels. Or you could of course just boot camp your machine if you happen to have a copy of Windows laying around. Parallels sounds like it might be the easier solution if you don't want to go through th hastle of installing a full blown windows load.
Just my .02 cents!

cathardicnotion said:
Unfortunately it sounds indeed like you need to use ODIN to flash and re-partition your phone's file system. You're going to need to make sure you use the stock rom (JFD) to do this, other wise you'll be stuck in the recovery loop yet again with a different error message.
So far as being on a Mac goes, I've heard that some people have luck using ODIN through the newer version of parallels. Or you could of course just boot camp your machine if you happen to have a copy of Windows laying around. Parallels sounds like it might be the easier solution if you don't want to go through th hastle of installing a full blown windows load.
Just my .02 cents!
Click to expand...
Click to collapse
Using ODIN worked. Thanks for the reassurance. :3

I really messed up the flashing process. Voodoo possibly the culprit. Please help!

Hi everyone, this is my first post. I am one of those who waited patiently for 2.2 that I decided to finally root today. I followed all the instructions to root from the sticky here. The process went without a hitch and I flashed the jk6 stock from Team Whiskey from the development section.
I really enjoyed the 2.2 experience while it lasted until I flashed the JL5+voodoo kernel from supercurio's thread. I was under the impression that you could flash different kernels over the old ones. It went through the process of partitioning to ext4. Once it was done, I went to settings and about phone to see if there was JL5 anywhere and it wasn't. It still showed JK6. So I panicked. I disabled voodoo through clockwork recovery and went to the process of reverting back to rfs which I believed. I used odin to flash back to jfd. I know, I didn't restore the backup from clockwork because I wanted to start over( I still have those backups on my external sd card). To my knowledge, the flashing to jfd would completely wipe the data, replace the baseband, kernel, recovery and os.
I then used samsung kies mini to update to JI6. Everything went ok so I decided to root again. Instead of loading the update.zip to internal sdcard. I decided to use tga_gunnman once click root. That process went great until went it rebooted, the clockwork recovery screen popped up to my amazement. It seemed that there were still original files since the first time I rooted. I checked my files on my vibrant to find that I still had original files such as the clockwork back up, titamium back up, and even voodoo. I thought the flashing would completely remove all the data and files. So I panicked again. At this point, I don't know what I did that now I can't get to my log in screen and the screen I get is a picture of a phone, an exclamation, and a computer on my phone. I tried using odin again through download mode to go back to stock but under the message box on odin, it stops at cache.rfs. It has been stuck there for a long time and nothing is happening. I can't even get into recovery mode either.
Now I am not even sure if I properly disabled voodoo or deleted it which I thought the flashing back to jfd would do. I don't know if my partition is still rfs or ext4. I can't use my phone at all. Did I completely brick my phone? How do I fix the mess I got myself into? I really do appreciate anyone's help. I apologize for the length of this post. I wanted to be detailed as possible. Thank you.
EDIT: Spoke too soon. I used a different version of odin and now im back to stock jfd, but the original files are still there including the voodoo folder. I thought it wipes all the data. Also how do I know that the data partition is originally rfs and not ext4? I want to make sure before I root again. Thanks.

Can you get to recovery and restore your backup you created? I just read where you said you can not get in to recovery. What method are you using to try to access recovery?

well if you are back to stock, but just the folder is lingering around, cant you just reformat your sd card?
settings>sd card phone storage>format.

I did a back up using clockwork. I originally was trying to do to the recovery mode by pressing the vol keys and power and that didn't work. I actually got it back to stock jfd by using a different version of odin. My problem now is that I still have some original files on my phone including the voodoo folder. My understanding of flashing was that it wipes everything from your phone. I am not sure if i still have root access even after flashing back to stock jfd. Also if my partition is back to rfs or still stuck at ext4. I am a little confused here. I am afraid if i root again that the original files and folders from my first root will interfere with the new root method.

so If I format the internal sd card, will it completely erase all traces from my first root?

neotoky said:
I did a back up using clockwork. I originally was trying to do to the recovery mode by pressing the vol keys and power and that didn't work. I actually got it back to stock jfd by using a different version of odin. My problem now is that I still have some original files on my phone including the voodoo folder. My understanding of flashing was that it wipes everything from your phone. I am not sure if i still have root access even after flashing back to stock jfd. Also if my partition is back to rfs or still stuck at ext4. I am a little confused here. I am afraid if i root again that the original files and folders from my first root will interfere with the new root method.
Click to expand...
Click to collapse
When you flash a new rom, or back to stock, it does not (usually) wipe the contents of your sd cards (internal or external). And if you are successfully running stock 2.1, you can rest assured you're back to rfs - so if that voodoo folder is making you nervous you can just delete it (it's only relevant if you have voodoo enabled). You're fine to re-root with whatever method you prefer.
Sounds like the soft-brick you experienced was purely from odin hanging on you, and that icon you saw has become a frequent visitor on my phone since I routinely have odin hanging issues (hence my avatar). I've found that v1.3 treats me the best, but sounds like whatever version you updated to worked, so there's no reason to deviate.

Download OCLF from the market and you will find out if you are currently rooted still.

There are a few misconceptions on what the wipe is.
/sdcard and external SD card are user accessible areas of the phone, and when it states that the ROM wipes your phone it does not touch these (there was only one incarnation of TW ROM's that inadvertently formated the entire filesystem for some users).
If you must format the phone to its complete stock form in ODIN you can use re-partition check box - the results are still mixed if it formats the entire FS or not, but most probably it will for you. So all your pictures, etc. should be backed up no matter what.

I appreciate the help guys. Thanks very much. The version of odin I used originally was v1.00 and the one I used to fix the problem was v1.70. My question now is did I properly flash the JL5 kernel over the JK6 even though when I checked the information on my phone it still stated as JK6? Also how do you properly reflash to a different kernel as well as modems? Do you overwrite the kernel or do you have to go back to stock before trying a new one? Thanks.

neotoky said:
I appreciate the help guys. Thanks very much. The version of odin I used originally was v1.00 and the one I used to fix the problem was v1.70. My question now is did I properly flash the JL5 kernel over the JK6 even though when I checked the information on my phone it still stated as JK6? Also how do you properly reflash to a different kernel as well as modems? Do you overwrite the kernel or do you have to go back to stock before trying a new one? Thanks.
Click to expand...
Click to collapse
I'm not sure why you would flash the JL5 kernel. Does it have any added benefit over the JK6? If you want, you can flash the JL5 MODEM through clockwork using the JL5_modem.zip file posted in many threads.
You should not have to go back to a stock kernel before trying a new one, but if you flash a Voodoo kernel that converts your system to ext4, then you must convert it back to RFS before flashing another kernel. An easy way to be postively sure that you are in RFS is by getting "Terminal Emulator" from market, and type "su" press enter, and then "mount" and press enter. If you see rfs next to data, dbdata, datadata, and system, then you know your system is converted back to RFS. Otherwise, in Voodoo mode it will read ext4 next to those.
Also, if you are really paranoid about getting a fresh start, you can mount your internal SD on your computer and just delete everything on there. Don't worry, all the important Android system files will be restored upon each reboot. All the other crap on there will be erased.

Help! Stuck in ClockWork! E:Can't open /cache/recovery/log

Using: ClockworkMod Recovery v2.5.1.0
Completely powering off and/or rebooting system from recovery, keep getting stuck back into recovery and cannot get anything to boot, even after restoring the very first backup I made.
Error is: E:Can't open /cache/recovery/log
What I did:
1: Rooted using this: http://forum.xda-developers.com/showthread.php?t=808103
2: Booted into ClockWorkMod Recovery and made a backup.
3. Wiped cache/data and tried flashing midNIGHT midNIGHT ROM v3.2 CW3/EXT4 AIO (Build Your Own ROM Edition UPDATED) from here: http://lostandtired.com/android-development (it seemed to install just fine!)
4. Tried to boot but it would not go past the Samsung boot logo
5. Yanked battery, reinstalled, same problem.
6. Wiped again, tried to restore backup, now it automatically boots into recovery and shows this error at the bottom.
Please help!
EDIT:
When I try to restore a backup (that I made before doing anything) It says:
Checking MD5 sums...
Restoring system...
Restoring data...
.android_secure.img not found. Skipping restore of /sdcard/.android_secure.
Restoring cache...
sd-ext.img not found. Skipping restore of /sd-ext.
Restore complete!
E:Can't open /cache/recovery/log

Please help me, I will pay you!
I just got this phone a few days ago... so I'm freaking out right now!
EDIT: I just installed Odin and booted into "download mode" -- downloading the stock tar now... I hope this takes care of it

Problem solved.
Odin FTW!!!

Your problem was that you flashed an ext4 only rom in rfs. You need to convert file systems to use midnight.
As you figured out, Odin puts everything back to stock.
Also, the nandroid backup and restore does not restore your kernel. If you are using to to restore, make sure you have a kernel on the sdcard to flash.

It must be going around
Man I am having the same problem you did I want to know where did you get your odin file from mine says it is installed but I dont see where to open it. I had my epic for about 3wks going crazy as well need your help but very optimistic

What are you trying to open?
If odin flashed your phone, then just turn the phone on and you have the rom that odin flashed.

relief
Prblem solved thanks guys

I've done the exact same thing. same phone same everything lol, but when i use odin, my computer doesnt recognize my samsung epic4g, i"ve restarted my computer and uninstalled and redownloaded my drivers twice. I'm trying the process with all the computers in my house, but in the meantime, could someone please give my some hints or tips as to what i could do otherwise?
EDIT: i almost get this driver error message "BlackArmor NAS 1D | no driver found"
Not quite sure why something so simple is turning out to be complicated. Also i run Windows7 32-bit

Fire n mage said:
I've done the exact same thing. same phone same everything lol, but when i use odin, my computer doesnt recognize my samsung epic4g, i"ve restarted my computer and uninstalled and redownloaded my drivers twice. I'm trying the process with all the computers in my house, but in the meantime, could someone please give my some hints or tips as to what i could do otherwise?
EDIT: i almost get this driver error message "BlackArmor NAS 1D | no driver found"
Not quite sure why something so simple is turning out to be complicated. Also i run Windows7 32-bit
Click to expand...
Click to collapse
Same problem here. I have to use a different computer. You very well may have a an internal USB problem like me. Has nothing to do with Windows. Hardware problem. Find another computer to do your flashing with.

h8uman said:
Same problem here. I have to use a different computer. You very well may have a an internal USB problem like me. Has nothing to do with Windows. Hardware problem. Find another computer to do your flashing with.
Click to expand...
Click to collapse
Alright thanks, i may have to use a friends computer at this point lol
EDIT: I've established a connection to one computer! =D so hopefully it'll flash fine
FIXED!!!

Cool
Fire n mage said:
Alright thanks, i may have to use a friends computer at this point lol
EDIT: I've established a connection to one computer! =D so hopefully it'll flash fine
FIXED!!!
Click to expand...
Click to collapse
Nice!! Welcome Back

OMG, I thought I bricked my phone... thankfully I stumbled across this thread and also this video on youtube: /watch?v=pleE_tzmiMo
I was trying to install midNIGHT ROM when this happened... I guess I need to read futher on how to properly install the ROM (Unless someone has a quick hint as to what I need to make it work)
With Odin, It will restore back to the factory firmware and work just fine, but If I re-root the phone and try to restore my nandroid backup it just hangs at the Samsung screen again. Any ideas?

just advanced restore /data and see if that gets around what is causing your phone to hang. Were you running a rom when you did the backup? You may need to reflash that rom, then advanced restore /data.
And get cwm 3 to flash midnight and other ext4 roms. There is a different one-click just for that after you do the one-click v2.5.5.

Do you have links to cwm3 and the one-click that you mentioned?
This is my first attempt at flashing the EPIC, so my backup was not a modified rom. (When I had my Hero I had no issues at all flashing a custom rom)
When this happens I am have to reflash with odin back to stock firmware, as my backups don't work for some reason. Strangely if I try to restore my nandroid backup after the stock firmware is back on there, I get the same results of it hanging on the samsung screen.

Yes, as has been mentioned, if you're going to a rom that uses the ext filesystem, you have to use the cwm3. I don't have the link., but if you look up "Randy Shear" on youtube, he has a video posted on how to install it.

[ROM] Bonsai User Discussion

This post is only for discussing all issues regarding the use of the Bonsai roms. We can talk here about any version from 1.0.0 to x.x.x
Due to some political issues please do not post any links to the Bonsai website! This thread is just for us users and don't expect the developers of Bonsai to ever visit here.
One last thing >
nor

Yes this try to keep this thread open.
Sent From My Evo Killer!

So is there a way to get a 600mhz step in the kernal for bonsai 4.0 last i heard he was going t put it in back in 3.0.1 but still not there. Or is there an easy way to included it in the kernal page file or something that set cpu uses? Also is there a way to get the voodoo color fix or a tweak that works that will make the brightness lower at the lowest setting for 4.0 becase the brightness on this screen is way to brght at night time. I used to have a tweak like this in syndicate rom for 2.1 it was great. Any info would be great thanks guys.
Sent from my SPH-D700 using XDA App

I installed bonsai 4.0.0.1 and it flashed fine, then it tried to restart and got stuck at the samsung boot screen, would not go past that.
So I battery pulled and tried to install another rom (verion 4) and it had an error in CW installing,
Then I tried installing a rom I have used before (epic experience) and CW would not install that one either.
So I used Odin to go back to stock everything and then unlocked it and now I am on a stock rom rooted.
Why do you think it is hanging there? I am scared to flash again as I think it will do the same? But if the forum needs the exact error msg I will install it again as I really want to get this rom working.
Thanks,
Force

forcelite said:
I installed bonsai 4.0.0.1 and it flashed fine, then it tried to restart and got stuck at the samsung boot screen, would not go past that.
So I battery pulled and tried to install another rom (verion 4) and it had an error in CW installing,
Then I tried installing a rom I have used before (epic experience) and CW would not install that one either.
So I used Odin to go back to stock everything and then unlocked it and now I am on a stock rom rooted.
Why do you think it is hanging there? I am scared to flash again as I think it will do the same? But if the forum needs the exact error msg I will install it again as I really want to get this rom working.
Thanks,
Force
Click to expand...
Click to collapse
Were you using CWM 3.0.0.6 or 3.0.0.5 ?
Sent from my SPH-D700 using Tapatalk

Good question as i was just going to as a question about EXT4 and CW.
The rom manger is version 3.0.1.4
however the CW mod flashed is version 3.0.2.4
It only has 2 to choose from in rom manger, 3.0.2.4 or an older 3.0.1.4
Not sure were people are getting these other versions from.
Force
PS I booted into CW and saw it was v2.5.1.0
am I way off?

abrcrmdl23 said:
So is there a way to get a 600mhz step in the kernal for bonsai 4.0 last i heard he was going t put it in back in 3.0.1 but still not there. Or is there an easy way to included it in the kernal page file or something that set cpu uses? Also is there a way to get the voodoo color fix or a tweak that works that will make the brightness lower at the lowest setting for 4.0 becase the brightness on this screen is way to brght at night time. I used to have a tweak like this in syndicate rom for 2.1 it was great. Any info would be great thanks guys.
Click to expand...
Click to collapse
I can't remember what stepping is on the kernel as we have been beta testing 4.0.1 and have been mainly dealing with a new setCPU governor called interactive. Were also still working on the other governor called smartass as well. I think that the stepping goes directly from 400 to 800, but we are always looking to go faster and with better battery life. I'll bug Randy and Mammon about it.
The sound will be Voodoo version 7, but I don't think the Voodoo color fix is going to make it into 4.0.1. Sorry, but we can't do everything...at least not all at the same time.

forcelite said:
I installed bonsai 4.0.0.1 and it flashed fine, then it tried to restart and got stuck at the samsung boot screen, would not go past that.
So I battery pulled and tried to install another rom (verion 4) and it had an error in CW installing,
Then I tried installing a rom I have used before (epic experience) and CW would not install that one either.
So I used Odin to go back to stock everything and then unlocked it and now I am on a stock rom rooted.
Why do you think it is hanging there? I am scared to flash again as I think it will do the same? But if the forum needs the exact error msg I will install it again as I really want to get this rom working.
Thanks,
Force
Click to expand...
Click to collapse
Did I see a similar post on the Bonsai website earlier today? I just want to verify that you were using CWM 3.0.0.6 as anything else will cause problems like that. Also when you get to these kinds of problems you should attempt a second flash of Bonsai before going to the trouble of a ODIN job. A second flash seems to fix a whole variety of odd kind of problems.
As you can imagine with all the beta testing I do I'm always finding ways to corrupt my phone. Some days I have managed to bork it 3-5 times.
I decided to test out today a 4.0.1 install directly from DI18 > CWM 3.0.0.6 > Bonsai 4.0.1 full rom. It went great with no problems at all and running just fine, so far

I think that is my problem, I am using a the CW that came with the one click unroot.
So I guess I need to do this, even if I am already rooted?
http://forum.xda-developers.com/showthread.php?t=897612&highlight=EXT4
PS
I booted into CW and saw it was v2.5.1.0

bluetooth
I could not get bonsai 3.0.1 or 4.0.0 to pair with my bluetooth headset. Tried pairing on an epic with acs 1.1 and paired fine. Anyone else have a pairing problem?

forcelite said:
Good question as i was just going to as a question about EXT4 and CW.
The rom manger is version 3.0.1.4
however the CW mod flashed is version 3.0.2.4
It only has 2 to choose from in rom manger, 3.0.2.4 or an older 3.0.1.4
Not sure were people are getting these other versions from.
Force
PS I booted into CW and saw it was v2.5.1.0
am I way off?
Click to expand...
Click to collapse
Do not use Rom Manager to be installing the beta CWM files. The correct way is with one of the 1 step CWM tools in the development forum. 3.0.2.4 is half-finished and is very difficult even to navigate through the various menu's. I know this because I tried out that CWM version for some grins one day. It will majorly screw your Epic if your not extremely careful. When DI18 was prevalent Rom Manager worked great to root your phone. When we started the move into the Froyo roms Rom Manager quit working and that is why the 1 click then became more prevalent.
Just follow the directions posted all over the place and Bonsai will install just fine and you will be a happy camper.

I am installing it now after updating to CW3 (from CW2.5) . I think it will come out fine now, I am an idiot and didn't realize the original one click root installed an older version of CW.
Thx All,
Force

forcelite said:
I think that is my problem, I am using a the CW that came with the one click unroot.
So I guess I need to do this, even if I am already rooted?
http://forum.xda-developers.com/showthread.php?t=897612&highlight=EXT4
PS
I booted into CW and saw it was v2.5.1.0
Click to expand...
Click to collapse
The linked one is the correct one for Bonsai version 4.x.x.

olddocwhite said:
I could not get bonsai 3.0.1 or 4.0.0 to pair with my bluetooth headset. Tried pairing on an epic with acs 1.1 and paired fine. Anyone else have a pairing problem?
Click to expand...
Click to collapse
Some people do and some don't I do know that Randy has instituted quite a few bluetooth linux upgrades into 4.0.1 rom. Some people are able to clear the data, but the problem usually reappears. Mattalica76 has the link to a more permanent fix to this problem, give him a PM.

Duplicate... Sorry

forcelite said:
I am installing it now after updating to CW3 (from CW2.5) . I think it will come out fine now, I am an idiot and didn't realize the original one click root installed an older version of CW.
Click to expand...
Click to collapse
Don't beat yourself up as we all have been there. It's a process of learning new skills and a new language. Give yourself a pat on the back for getting through this when 98% of the world would have said screw it or not even tried at all.

Actually it didnt boot this time either, it installed the firs ttime fine, then kept booting after samsung in a loop,
So I went into CW3 and tried to flash bonsai 4.0.01 again and it gave me this error. It is long, however I shortened it, I have the whole error photo copied)
Finding package
Opening package
Install update
Assert failed getprop (“ro.product.device)”)
Sph-700
E:error in /SDcard/bonsai……….
(status 7)
Installation aborted

Top Nurse said:
Don't beat yourself up as we all have been there. It's a process of learning new skills and a new language. Give yourself a pat on the back for getting through this when 98% of the world would have said screw it or not even tried at all.
Click to expand...
Click to collapse
Thanks for the support T Nurse,
I loaded the EC05 stock from Odin as I still dont have a grasp on EXT4 file system.
last thing I tried was cw3.0.0.6 and loaded Bonsai and it installed, just hung at samsung screen. might be a corrupt rom file.
1) So after flashing CW3, bonsai is supposed to change the file system over to EXT4 automatically after flashing, correct?
2) will windows 7 be able to read the sd card after it is changed over to ext4 (by bonsai), or will it have 2 partitions, one windows can read fat32 and the other ext4 it cant.

forcelite said:
Thanks for the support T Nurse,
I loaded the EC05 stock from Odin as I still dont have a grasp on EXT4 file system.
last thing I tried was cw3.0.0.6 and loaded Bonsai and it installed, just hung at samsung screen. might be a corrupt rom file.
1) So after flashing CW3, bonsai is supposed to change the file system over to EXT4 automatically after flashing, correct?
2) will windows 7 be able to read the sd card after it is changed over to ext4 (by bonsai), or will it have 2 partitions, one windows can read fat32 and the other ext4 it cant.
Click to expand...
Click to collapse
CWM3 will convert your filesystem to ext4 the first time you boot into it. It won't touch the sdcard so that won't be converted. After CWM is finished with the conversion, do not reboot the phone, you will then flash Bonsai.

forcelite said:
Thanks for the support T Nurse,
I loaded the EC05 stock from Odin as I still dont have a grasp on EXT4 file system.
last thing I tried was cw3.0.0.6 and loaded Bonsai and it installed, just hung at samsung screen. might be a corrupt rom file.
1) So after flashing CW3, bonsai is supposed to change the file system over to EXT4 automatically after flashing, correct?
2) will windows 7 be able to read the sd card after it is changed over to ext4 (by bonsai), or will it have 2 partitions, one windows can read fat32 and the other ext4 it cant.
Click to expand...
Click to collapse
After flashing the boot script of cwm 3.0.0.6 you then have to power off. Then hold down the camera button, vol down, and power keys at the same time and the EXT4 script will automatically start to format your system. Please keep in mind that it is not formatting the SD card, but only the read only memory of the phone.
After you finished a few beers it will be done and will drop you back to cwm. Do not reboot, but flash bonsai. After bonsai is finished then reboot.
Sent from Bonsai 7.0.3

Cant get Vibrant to start help plz!

Ok i was on ICS passion then all of a sudden my phone said something about encryption an that it had failed an only option was to reset phone so i hit reset then it went to recovery mode an green android came up with chest open then error message happened an so i booted in to recovery then i try to go in sd an it would not allow me to so i then tried to odin an flashed then i powered on it gies to vibrant screen then it just shuts off so i then flashed Eugene froyo that does not brick then it takes me to stock recovery an says an i cant click on anything in recovery can only move -- movi_checking done!...
update media, please wait
E:Can't mount /dev/block/mmcblk0p1
(No such file or directory)
E:copy_dbdata_media:Can't mount SDCARD:
your storage not prepared yet, please use UI me
nu for format and reboot actions.
Here are instructions i have followed an no luck http://forum.xda-developers.com/showthread.php?t=1043892
Ok I think you got some extra cache or some other piece of data that did not get wiped. either way, do this in this sequence and you should be ok
1. Download Eugenes 'Froyo that does not brick' file.
2. Extract the files.
3. Open Odin, plug in your phone, then put it into download mode.
4. load the PIT file in appropriate area.
5. load the .tar file in the PDA area.
6. DO NOT check 're-partition'.
7. Click start, let it finish. Your phone will load and reboot into stock recovery. It will error out again. DONT panic! This is what's supposed to happen.
8. Now, pull your battery.
9. Load the JFD rom for the vibrant'.
10. Extract the files.
11. Once again, open Odin, plug in your phone, put into download mode.
12. Load the PIT file into the appropriate area and the .tar in the PDA area.
13. THIS TIME you want to check the 're-partition' box.
14. Now click start, let it finish, and this time your phone will load up just fine!
15. Then, root the phone and you can flash your new Rom.
doing this method will get everything back to normal and the phone will work just like it did right out of the box
It is #7 that is important when it reboots into recovery after froyo that does not brick then pull the battery and go back into download mode and flash the JFD, This will clear everything out and put you back into stock
Good luck

Got it started
I got it booted though a very hard process an now i cant get my sd card to mount it says when i go into anything media related it says "Your phone does not have a SD card inserted" an Externel dont mount either

Which sd card isnt working... internal sd, or external sd?

kf7strng said:
Which sd card isnt working... internal sd, or external sd?
Click to expand...
Click to collapse
Both of them aren't working

Jasonhunterx said:
Both of them aren't working
Click to expand...
Click to collapse
Don't use eugene's rom, since you were using an ICS rom follow these steps
flash froyo bootloaders
flash regular jfd and TICK REPARTITION ( ICS/CM7/CM9 change the partition layout and you need to flash correct partition table for stock rom to work )
back in bussiness.
http://forum.xda-developers.com/showthread.php?t=848737

jrafael said:
Don't use eugene's rom, since you were using an ICS rom follow these steps
flash froyo bootloaders
flash regular jfd and TICK REPARTITION ( ICS/CM7/CM9 change the partition layout and you need to flash correct partition table for stock rom to work )
back in bussiness.
http://forum.xda-developers.com/showthread.php?t=848737
Click to expand...
Click to collapse
it never booted on Eugene rom it just went to recovery an gave me an error the one time i got it booted was on 2.1 Stock all the phone does is go to vibrant screen then shut down an no boot loop just off it has done this before an i fixed but Sd was not working an first time apps worked but then 2nd time no apps worked besides browser messenger

Jasonhunterx said:
it never booted on Eugene rom it just went to recovery an gave me an error the one time i got it booted was on 2.1 Stock all the phone does is go to vibrant screen then shut down an no boot loop just off it has done this before an i fixed but Sd was not working an first time apps worked but then 2nd time no apps worked besides browser messenger
Click to expand...
Click to collapse
Hey Jason. I'm in the exact situation you're in. Loaded Passion for about 1 week, got the encryption screen and was forced to reset. Now my SD cards (internal and external) won't load. Have you found a work around for it yet? Cheers Mate.

nope nothing

either of you find a solution? Im having same issue

In the same boat
I am in the same boat. I was using the Euphoria ROM. Yesterday things slowed down on the phone. I rebooted a few times and it crashed. The last couple of times it told me about the encrypted data. That was when I tried to take it back to stock and it won't do anything now other than boot to the vibrant logo and shutdown. Searching for a way to odin a ROM/Kernel that has a CWM recovery so I can go in and manually format the SDcard.

Do what I did, sell it to someone as a wifi hotspot and buy yourself a hercules. You'll never look back
Sent from my SAMSUNG-SGH-T989 using XDA

BUMP
BUMP!
I have had a paper weight for three weeks now because of this partition issue.
there has to be a way to fix this.

webstas said:
BUMP!
I have had a paper weight for three weeks now because of this partition issue.
there has to be a way to fix this.
Click to expand...
Click to collapse
Try this one.
http://forum.xda-developers.com/showthread.php?t=1580902
Sent from my Vibrant using Tapatalk 2

Webstas- Just out of curiousity, were you trying to mount your phone to your computer while on ICs when this happened? I have a theory that I believe I know why this is happening. Just need you to see if you remember a few weeks ago and if you had any problems mounting to your PC and then your next reboot you got the Ecnryption Error.

Woodrube said:
Webstas- Just out of curiousity, were you trying to mount your phone to your computer while on ICs when this happened? I have a theory that I believe I know why this is happening. Just need you to see if you remember a few weeks ago and if you had any problems mounting to your PC and then your next reboot you got the Ecnryption Error.
Click to expand...
Click to collapse
no i got up an took a shower then came back it gave me an encryption error then i odin back an more trouble odined a couple more times an now it boot loop an also wont start with eugenes froyo

I know it has been awhile but think back. Were you mounted to your PC at anytime between your last reboot and the Encryption Error? Doesn't have to be right before, the error gets throw on your "next" reboot. And as you know, reboots can happen manually or for something as simple as wrong UV settings.
Looking back in this thread, I saw that you got it to boot up. See if you can do that again and then mount your External via ADB and you should to push the proper commands then. Pretty much your internal is hosed, but me and a few others are working on that too.

Can't get it to boot it makes it to Vibrant screen an shut off an on Eugene"s froyo it gives me a couple of errors an I just can't get it to start anymore it there anyone who has encountered this an got it fixed like I really need this fix I am using a blackberry please save me

YAY
I got it fixed but now im on step 13 of that guide where you have to use ADB an i cant get the phone to show up on my PC what drivers do i need i already have Vibrant drivers but still nothing an the usb works its a samsung USB so can anyone help me with ADB

I am having a similar problem. Was running ICS 4.0.3 w/Euphoria without issue until this morning. Got a couple of errors after a normal recharge. Pulled battery and rebooted, but is stuck in boot loop. Cannot access either recovery or fastboot screen. Vibrant logo flashes and release buttons, but never enters mode. Then cycles to Android screen and would likely stay there until battery died. This is primary phone and need to put back into service quickly. Any assistance will be greatly appreciated. Thanks.
JIM in FLA

Go back to stock 2.1
Sent from my SGH-T959 using XDA