Bad Block Error PLEASE HELP

[saiven]

Ok
So I downloaded the SMupdater from the market and thought i would try it out.

I ran it, rooted and when i went to FLASH the RECOVERY image it looks like its working then stops and says

AN ERROR HAS OCCURRED!
mtd: not writing bad block at 0x00160000

What should I do???
I just got the phone like a week ago...

I have searched google and this forum and have not found anything.
I have tried installing BB but when i try to install SPRecovery using terminal is says almost the same thing and is in same block error.

I really love the and wanna make the most of it.
i started using Roms with the samsung Omnia

PLEASE HELP

Thank you kindly

[hayaku]

just went through this with a friend's phone. there's a bad block in your recovery partition.

we were lucky in that flashing sprecovery to that partition finally worked. we just kept on trying to do this manually - no rhyme or reason why it would've gotten past the bad block, but it did.

smupdater doesn't have all the logic in it necessary to figure out which steps needs to be done and what hasn't yet. so i would recommend doing this manually.

follow the bugless beast step by step guide. chances are you already have root. you will need to get flash_image installed and manually flash the recovery img file in. just follow those steps.

once done with that, you can download the sholes rom tgz file you want and put it on the card. reboot and hold x to get into sprecovery menu. go to install and select rom on sd card. from there, you will get the installation screens and menus from the sholes script and once it's done, you are good to go.

good luck with getting past the bad block. we did this using adb on the computer, not on the droid alone just because it was easier to type...

[Bear in NM]

Got your answer above. If I knew I had a bad block, methinks I might be thinking about a new phone. The problem is how do you tell vzw that you found a bad block doing something "illegal".

Craig

[jhietter]

I know this is an old topic but thought I would add my experience in case anyone else runs into this. I was having issues with the Data wipe, so I used adb via sdk to do a wipe (had never done this before). When I formatted DATA, it told me I had 2 bad blocks and 1 for CACHE.

So today I went to VZW at lunch. I told them that there were bad blocks on the data partition & said "Don't ask me how I know". I had restored to stock condition, so I was going to stick to that story. The guy didn't really give me a hard time - he just gave me a replacement (refurb). I just formatted all partitions and got no errors (woohoo).

My only concern is whether or not this constant wiping and rom'ing can create bad blocks. I don't know if my phone came with them or if I did it.

[brokali]

My second Droid came with bad vblocks same sector one on system one on data I found them when doing an adb format...wonder if that's why clockwork recovery always fails to load the picture and just gives me a could not load PNG file