Database Users

Problems preparing to flash ROM

My vibrant is running stock 2.2 Froyo. Lately, it dies silently and so frequently in sleep that I can't rely on it for every day usage. I've missed many important calls. So I am trying prepare my phone to flash another ROM. First, I got the phone rooted no problem at all.
Then the first problem I have is with the ROM manager. I purchased the Premium Version 3.0.1.3 and flashed the latest ClockworkMod Recovery 2.5.1.2. Upon rebooting into Recovery, there is, however, no Nandroid backup, just the normal menu shows up with
Samsung Recovery Utils -for BML-
.reboot now
.reinstall packages
.delete all user data
.delete cache data
.format internal sd card
I remove update.zip on the phone and on the sd card and retried and retried without success. Why don't I have Nandroid backup showing up to save the phone before flashing new ROM?
The second problem is with the Titanium Backup. I downloaded the free version and it works fine and could get root privilege without problem. Then I purchased the donated version and followed the instruction to uninstall the app and reinstall it to get the upgrade through the license file. The license file is read correctly and the upgrade version acknowledges that. However, Titanium Backup paid version now fails to get root privilege. I verify that other apps can get root without problem. I've searched all over yesterday and it seems that few people have the same problem getting root with the upgraded version, but no one has offered a solution.
So here I am paying but not able to backup the phone to start flashing anything. Could someone enlighten me about what I did wrong here?
Thank you.

For recovery, just select reinstall packages. Sometimes you have to do it twice.
For titanium backup, click the problems button to get the latest busybox.
You should be good after that.
Sent from my GT-I9000 using XDA Premium App

What offdutyninja808 said, also check your Superuser app, click Titanium and tell it to forget it if it's there.
We'll get you sorted out!

I have the same set-up and I have the same issue. I've selecting reinstall packages several times. Did not work. I tried different, methods: using Rom Manager and AIO Vibrant Toolbox. Didn't work. At first it said said it wasn't signed, and I four a fix for that. Now It loads and says replacing stock recovery with Clockwork... but boots back into the stock one. Is there anything else I can do?

birgertime said:
What offdutyninja808 said, also check your Superuser app, click Titanium and tell it to forget it if it's there.
We'll get you sorted out!
Click to expand...
Click to collapse
+1 Both Off duty and birgertime are correct. Most of the new roms will delete all things for you unless they say to do something particular (like some of the EDT roms) you should be ok, we are here to help if you run into further problems

If hitting "reinstall packages" don't take you to the clockwork recovery, also you can just reinstall the recovery thru rom manager.
Then once you reboot and if it don't take you to clockwork recovery, then hit reinstall packages again. Ya should get to it the second time.
I had this issue a lot when first rooted the phone and installed clockwork recovery.
Sometimes it will even boot halfway into stock recovery then quickly reboot itself into clockwork.
Also, just make sure that there is only ONE update.zip in there. So delete the update.zip using "my files" then open Rom Manager and choose install clockwork recovery. That way you are sure there is only one update.zip there then try the previous mentioned methods

Thanks for your advice. I still have problem with selecting "reinstall packages" in the Recovery menu. If I select that, it says:
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
This repeats if I keep selecting "reinstall packages" again. My SD card is still the original 2GB card that comes with the phone. It still has plenty of space.
Thanks again for helping

FWIW, I upgraded BusyBox and could solve the Titanium Backup problem. However, still can not do a nandroid backup as mentioned above, even with the donated version. So I abandoned my plan to flash another ROM and stay with the rooted stock.
However, what a difference it makes when I replace the 2GB SD card that came with the Vibrant with a 16GB SD card class 10. The unit comes up faster, the UI is no longer sluggish as before. I hope that this was the issue that caused my Vibrant to die in sleep. I need to phone for daily use and don't have a lot of time to muck around with it. Maybe next year when I have another phone to use as main phone, then I can take some risk to flash without nandroid backup. For now I hope that it no longer dies in sleep. Thanks for all your help.

Just a quick note to end this thread.
Since I have plenty of disk space on the internal memory, I removed the SD which I don't need and the phone seems to become reasonably fast responsive with rooted stock 2.2. It's now quite usable for me so I have no more need to flash it with another ROM. People who complain about slowness of their stock 2.2 ROM should try to remove the SD card first.
Thanks again for all your help.

[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

[Q] EVO Rom/Root problems

I am having some serious issues with my evo. I have tried 10 different methods, googled 100 different help guides and still no fix.
I had originally rooted my phone using simple root and put the "fixed" froyo rom on there. Everything worked fine, but I was outdated and having some really slow issues so I wanted to try a new rom...Fresh.
Well I tried a few methods, but I somehow reverted my evo back to a nonroot of the original OS. Whenever i go into hboot, my recovery does not work. I push the PC36img and load it, then restart then I attempt to go to my recovery where it gives me the error picture with the yellow/red triangle. I then select recovery (after pressing UP volume and powerbutton) and try to load update from sd card. Everytime I do that I get a Failed error.
I've tried to reroot using several methods off this website, I've done everything I can to get it working but can't. Any help would be GREATLY appreciated!

Try reflashing your recovery image.

BTW I have hboot 79.0 with S-ON, so it looks like I def became unrooted.

noweakness said:
BTW I have hboot 79.0 with S-ON, so it looks like I def became unrooted.
Click to expand...
Click to collapse
Not sure how it would have just unrooted itself. I would run an RUU from here: http://forum.xda-developers.com/showthread.php?t=884060
Then, I would re-root and start clean again.

Heaterz16 said:
Try reflashing your recovery image.
Click to expand...
Click to collapse
I have a recovery-ra.img, how do I tell it to flash it?
I pulled up this list of recovery files, is there a particular one I should use?
htt p://goo-inside.me/amon_ra/supersonic/

Heaterz16 said:
Not sure how it would have just unrooted itself. I would run an RUU from here: http://forum.xda-developers.com/showthread.php?t=884060
Then, I would re-root and start clean again.
Click to expand...
Click to collapse
Ok I downloaded the top item:
RUU_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed
Ran the exe, surprisingly picked up my phone and started the image update. My phone restarted and it forced closed the app on my computer. Now I have a new HTC logo for about 5 min on my phone not doing anything. Should I wait it out or restart my phone?

noweakness said:
Ok I downloaded the top item:
RUU_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed
Ran the exe, surprisingly picked up my phone and started the image update. My phone restarted and it forced closed the app on my computer. Now I have a new HTC logo for about 5 min on my phone not doing anything. Should I wait it out or restart my phone?
Click to expand...
Click to collapse
I would have waited about ten minutes then restarted the phone. If the phone is stuck at the HTC logo, then I would go ahead and re-run the RUU.
Let me know how it turns out.

Heaterz16 said:
I would have waited about ten minutes then restarted the phone. If the phone is stuck at the HTC logo, then I would go ahead and re-run the RUU.
Let me know how it turns out.
Click to expand...
Click to collapse
ok, finally got it working. Had to restart the phone manually and try it on a different computer. It updated it to the newer version of android and hboot, thank goodness! That was the easiest and most productive thing I've been able to do so far, thanks!
Well now I try to boot into recovery and get the same error:
can't open /cache/recovery/command
Then I get :
E: signature verification failed
Installation aborted
When i try to load update from sdcard

noweakness said:
ok, finally got it working. Had to restart the phone manually and try it on a different computer. It updated it to the newer version of android and hboot, thank goodness! That was the easiest and most productive thing I've been able to do so far, thanks!
Well now I try to boot into recovery and get the same error:
can't open /cache/recovery/command
Then I get :
E: signature verification failed
Installation aborted
When i try to load update from sdcard
Click to expand...
Click to collapse
Ok, so, I think you said you got the RUU working which would have completely restored the phone to unrooted and stock from factory.
Now, you need to re-root your phone using one of the methods on xda. I used the manual method here: http://forum.xda-developers.com/showthread.php?t=829045. However, many people have had success with the one-click methods.
After you re-root (which will likely included installing a recovery), select a rom you want to try, boot to recovery, wipe and flash it. A great starter ROM is MikFroyo 4.6 or 4.5.

Try downloading the PC36IMG.zip from here: http://forum.xda-developers.com/showthread.php?t=705026
put that on the root of your SD card, then boot into HBOOT and it should find that PC36IMG.zip after a few seconds and ask if you want to flash it. Choose yes and let it finish. Should then be able to reboot into recovery.

ok thanks, i'll try it when I get back home

jesuspgt said:
Try downloading the PC36IMG.zip from here: http://forum.xda-developers.com/showthread.php?t=705026
put that on the root of your SD card, then boot into HBOOT and it should find that PC36IMG.zip after a few seconds and ask if you want to flash it. Choose yes and let it finish. Should then be able to reboot into recovery.
Click to expand...
Click to collapse
Ok, I tried this method...the filesize of pc36img.zip is only 3.5mb, but it didn't seem to work. It scanned the file then just went back to the hboot screen with my options never asking to flash.
I'm going to try to reroot using the other method now...

So I clicked the link and he forwarded to the autoroot.bat page so I used his method. It worked well (the 2nd time around) all the way until it started to push amon_ra_1.8-mod.... then after that it says rebooting into the bootloader, and it reboots into it and just says waiting for phone...
It does appear that my phone is rooted now, but my recovery is still not working. If I use ROM manager will it work since my phone is rooted or do I need to have a rooted ROM to run it off of?

noweakness said:
So I clicked the link and he forwarded to the autoroot.bat page so I used his method. It worked well (the 2nd time around) all the way until it started to push amon_ra_1.8-mod.... then after that it says rebooting into the bootloader, and it reboots into it and just says waiting for phone...
It does appear that my phone is rooted now, but my recovery is still not working. If I use ROM manager will it work since my phone is rooted or do I need to have a rooted ROM to run it off of?
Click to expand...
Click to collapse
Does your phone show s-off while in the bootloader? If so you should be able to run the FlashZip script and use that to flash the pc36img-sprintlovers zip. That one contains everything needed to bring your phone up to date and will leave you with a rooted rom and recovery.
Sent from my PC36100 using XDA Premium App

xHausx said:
Does your phone show s-off while in the bootloader? If so you should be able to run the FlashZip script and use that to flash the pc36img-sprintlovers zip. That one contains everything needed to bring your phone up to date and will leave you with a rooted rom and recovery.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
FINALLY! Thanks a million! My recovery is now working and it installed the built in sprinter lovers rom, I guess the anti-virus was stopping it so I disabled it and ran the flash script. I was able to install Fresh on there, just to try it out. I do have a few questions though:
1. I noticed after going through many pages that to update to a newer ROM version you don't always have to wipe clean, you can just install (or flash) the new update? I noticed in Fresh there is a built in app that does that. Is this true for most ROMS or only certain ones?
2. I assume I am using the RA recovery. I noticed the backup/restore feature on there. What exactly does that backup and when should I use it?
3. I've noticed I've been very low with memory on my phone (not SD card), I have about 258MB free. How can I clear space and when I mount my phone what files are important to keep and can I get rid of, is it okay to get rid of my rom.zip's and radio.zip's?
Thanks again to everyone, autoroot was def the most painless root ever.

noweakness said:
FINALLY! Thanks a million! My recovery is now working and it installed the built in sprinter lovers rom, I guess the anti-virus was stopping it so I disabled it and ran the flash script. I was able to install Fresh on there, just to try it out. I do have a few questions though:
1. I noticed after going through many pages that to update to a newer ROM version you don't always have to wipe clean, you can just install (or flash) the new update? I noticed in Fresh there is a built in app that does that. Is this true for most ROMS or only certain ones?
2. I assume I am using the RA recovery. I noticed the backup/restore feature on there. What exactly does that backup and when should I use it?
3. I've noticed I've been very low with memory on my phone (not SD card), I have about 258MB free. How can I clear space and when I mount my phone what files are important to keep and can I get rid of, is it okay to get rid of my rom.zip's and radio.zip's?
Thanks again to everyone, autoroot was def the most painless root ever.
Click to expand...
Click to collapse
1) You'll want to always wipe your cache/dalvik (I do everytime I'm in the recovery) but the Data depends on the ROM. Usually if you are going from one sense rom to another you are ok and the same for AOSP to AOSP. Going from Sense to AOSP you'll need to wipe data though.
2) Autoroot comes with a modified version of AmonRA, they are mostly just speed tweaks. To make a complete backup of your ROM select Boot (kernel), System (ROM), Data (Apps & Settings) and .android (apps on SD card)
3) You can delete the zips from your sd card if you don't need them but that's about normal for free memory.

Troubles with Rom Manager and Flashing

I am having a lot of issues with Rom manager. Whenever I create a backup and try to back it up it refuses to work. It acts like it worked. But when I try to restore to that backup it says MD5 mismatch. I am currently running a froyo leedroid rom. I have tried to flash over to a GB Leedroid rom and a Coredroid rom. Neither of them work.
It says finding update package
opening update package
can't open file bad.
I am seriously annoyed with rom manager WTF is the point in creating a damn backup if I can't restore it at a later point?

Now my sdcard will not mount says its is mounted as read only and it wont do a damn thing now...

Bump wondering how to check an MD5. Still wondering what is up with Rom manager. Silly question but am I having troubles because I bought a different memory card for the phone? I did a partition and wiped it but just not sure.

http://www.softpedia.com/get/System/File-Management/MD5-Checker.shtml
use that to check the MD5. Obviously something getting corrupt along the way. I cant imagine its the memory card but Im not 100%. Hopefully someone with more knowledge than me will pop along shortly.

berserkerx87 said:
I am having a lot of issues with Rom manager. Whenever I create a backup and try to back it up it refuses to work. It acts like it worked. But when I try to restore to that backup it says MD5 mismatch. I am currently running a froyo leedroid rom. I have tried to flash over to a GB Leedroid rom and a Coredroid rom. Neither of them work.
It says finding update package
opening update package
can't open file bad.
I am seriously annoyed with rom manager WTF is the point in creating a damn backup if I can't restore it at a later point?
Click to expand...
Click to collapse
Hi I'm pretty new here so I'm may be wrong about this, but could it be a problem with Froyo and GB? It's like using office 2010 and 2007 version, may not be backward compatible. But I may be wrong, just a a guess on my part.

berserkerx87 said:
It says finding update package
opening update package
can't open file bad.
Click to expand...
Click to collapse
Looks to me like you've got a flaky SD card, certainly I have no problems creating and restoring backups although I am on CM7 but that shouldn't make a difference, first off though make sure youre running the lastest ROM Manager and Clockwork versions then try a different SD card.

Okay I am still having issues with Rom manager. I tried putting in a new sd card and it will not mount to the system. I hit mount and it just pops back up saying its ready to remove. I now can't reboot into recovery nor flash clockwork recovery. It said an error occurred while flashing your recovery.
Also I really don't like that I can't even take a picture or use my camera because it says it can't save to the SD card due to insufficient file permissions. Yes I have done fix permissions in rom manager. But it still wont work..

have you tried to do it directly in CWM?
if so, try to flash a newer CWM version (through fastboot, ROM Manager is known to cause some problems).

Hello iam also having problems but i am have my DHD freeze at the splash screen when trying to enter recovery, any ideas please.

berserkerx87 said:
Okay I am still having issues with Rom manager. I tried putting in a new sd card and it will not mount to the system. I hit mount and it just pops back up saying its ready to remove. I now can't reboot into recovery nor flash clockwork recovery. It said an error occurred while flashing your recovery.
Also I really don't like that I can't even take a picture or use my camera because it says it can't save to the SD card due to insufficient file permissions. Yes I have done fix permissions in rom manager. But it still wont work..
Click to expand...
Click to collapse
ROM manager wouldn't prevent mounting of a new SD card, thats got to be a hardware issue or an issue with your current ROM, try flashing either a different custom ROM or a stock ROM if your SD card woes continue it's a hardware issue, if not it's a ROM issue but either way I think we can safely rule out ROM manager.

sidon100uk said:
Hello iam also having problems but i am have my DHD freeze at the splash screen when trying to enter recovery, any ideas please.
Click to expand...
Click to collapse
Try reflashing Clockwork recovery, either from Fastboot or from ROM manager.

Tried using ROM Manager but got nowhere so i followed this post and it worked first time http://forum.xda-developers.com/showthread.php?t=1003723 , it was great for new guys like me.
But thank you for your help.

I figured out what the problem was. Even though I had formatted that new sd card it still wouldn't mount so I formatted it on the computer and now everything is fine. I don't use that other sd card anymore. I guess it was really just a bad sd card. So a word of advice to everyone that not all sd cards are created equal!
Thanks for all the help everyone!

Wise words there! I've been through 4 memory cards lol and each one broke. One after the other.

I use Rom Manager only to install CWM, and then I flashed all new rom by recovery from SD card.
I propose not to save a money on buying cheap card. It so important

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