cant update to latest version of droidmod(BADBLOCK)?

[droidor]

ive been trying to update to the latest version of droid mod for EVER so here i am. im a noob and not tech savvy and thats why i picked droid mod. now im stuck with version 1.0. i get an error that says (An Error has occurred!
mtd.MEMGETBADBLOCK returned 1 at 0x004600
(errno=0)!!!!! i will paypal 5$ to anyone that can help me fix it!

[Corinacakes]

there's a new version of droidmod out?

[hookbill]

I saw that Droidmod had a new version today. I have not downloaded it so I can't tell you about any issues, but you don't have to offer money for help. We are all here to help each other.

Have you tried restarting your Droid or a 30 second battery pull? Other then that I have no answers. Maybe somebody else will have a better solution, have you looked at the message boards at DroidMod - Everything Droid doesn't, DroidMod does. That might be your best solution.

[droidor]

there's a new version of droidmod out?

no the latest version that came out a while ago. but new to me if i can ever get it to work. version 11 (0.1.1)

[Corinacakes]

Ok....link? All i see on their website is v1.0.0. What is this you say!?

[JLags917]

Im not sure but i think dm updater is just 1.1 not the actual rom itself i could be wrong..

[droidor]

Ok....link? All i see on their website is v1.0.0. What is this you say!?

DroidMod Updater 11 - DroidMod

[Dave12308]

ive been trying to update to the latest version of droid mod for EVER so here i am. im a noob and not tech savvy and thats why i picked droid mod. now im stuck with version 1.0. i get an error that says (An Error has occurred!
mtd.MEMGETBADBLOCK returned 1 at 0x004600
(errno=0)!!!!! i will paypal 5$ to anyone that can help me fix it!

This error is basically telling you that a portion of your flash RAM has gone bad. If you were to boot into recovery and manually format the partitions, it would help narrow down exactly WHICH partition the bad flash block is in (and would also erase all of your data, so take that as a word of caution).

That is the one problem with flash RAM, erasing and rewriting blocks will eventually cause them to fail. I have a couple of bad MTD blocks in my DATA partition, for example - however, in my case they cause no issues. It could be that your bad block is somewhere in the recovery partition; i've heard of that causing problems like you describe when trying to flash a new "ROM".

Unfortunately, there's no way to fix memory blocks that have physically gone bad. The only real 'fix' would be to return the device to Verizon. However, good luck explaining to them how you figured out the blocks are bad. There's no way to know that without doing something (flashing a custom ROM) that voids your warranty.

You COULD try following the directions in the thread on how to use the SBF file to go back to stock; but that won't fix the problem most likely. However, it MAY work - I suspect that somewhere in the SBF flashing process, bad MTD blocks are flagged and the system acts like they're not there. I'm not sure that the recovery partition (if that is indeed where your bad blocks are) has enough space to flash the custom recovery, however, once it has bad blocks. I believe it's only big enough to hold the recovery image, with no extra space - but i've been wrong before.

[droidor]

ive been trying to update to the latest version of droid mod for EVER so here i am. im a noob and not tech savvy and thats why i picked droid mod. now im stuck with version 1.0. i get an error that says (An Error has occurred!
mtd.MEMGETBADBLOCK returned 1 at 0x004600
(errno=0)!!!!! i will paypal 5$ to anyone that can help me fix it!

This error is basically telling you that a portion of your flash RAM has gone bad. If you were to boot into recovery and manually format the partitions, it would help narrow down exactly WHICH partition the bad flash block is in (and would also erase all of your data, so take that as a word of caution).

That is the one problem with flash RAM, erasing and rewriting blocks will eventually cause them to fail. I have a couple of bad MTD blocks in my DATA partition, for example - however, in my case they cause no issues. It could be that your bad block is somewhere in the recovery partition; i've heard of that causing problems like you describe when trying to flash a new "ROM".

Unfortunately, there's no way to fix memory blocks that have physically gone bad. The only real 'fix' would be to return the device to Verizon. However, good luck explaining to them how you figured out the blocks are bad. There's no way to know that without doing something (flashing a custom ROM) that voids your warranty.

You COULD try following the directions in the thread on how to use the SBF file to go back to stock; but that won't fix the problem most likely. However, it MAY work - I suspect that somewhere in the SBF flashing process, bad MTD blocks are flagged and the system acts like they're not there. I'm not sure that the recovery partition (if that is indeed where your bad blocks are) has enough space to flash the custom recovery, however, once it has bad blocks. I believe it's only big enough to hold the recovery image, with no extra space - but i've been wrong before.

looks like im sol???

[droidor]

so can i put a different rom like bugless beast on or am i sol there too?