problem with boot.img

[ulysses]

i'm currently running Damage Control 3.2.3, and i've recently used cyanogenmod 6.
i've tried flashing DC3.5 and fresh3.1.0.1. both of which give me errors when it gets to "boot.img".
i thought at first it was DC3.5, but like i said, fresh is doing it too. i've tried flashing with clockwork and with amon ra. i've downloaded the ROMs multiple times and also directly to my phone.
i've used OMJs rom in the past. then went to DC3.2.3. tried cyan6 for a bit and went back to dc3.2.3 just recently with a netarchy kernal.

*edit*
i've wiped cache, data, dalv, and even batt stats.. sometimes even twice as a "junt in case"


any suggestions?
thanks,
-u

[Pao]

You are wiping, correct? You did not mention anything about wiping the phones data/cache/dalvik

[ulysses]

Originally Posted by Pao

You are wiping, correct? You did not mention anything about wiping the phones data/cache/dalvik

yes, sorry, forgot to mention that. lol

[ulysses]

bump...
anyone?
i've tried other 2.2 roms, and i still get this error. is there a step i missed? i'm confused because i flashed cyanogenmod6 (2.2)

thanks

[tool2269]

what kernal are you on? settings>abt phone>software info

have you tried flashing a different kernal?

[ulysses]

Originally Posted by tool2269

what kernal are you on? settings>abt phone>software info

have you tried flashing a different kernel?

2.6.26-netarchy-toastmod-3.7.5
i flashed DC3.2.3 then threw the dc compatible kernel on it.
so far, from what i've flashed, it's had no problem with 2.1 roms, but whenever i try a 2.2, that's when it fails at boot.img. but that doesn't make sense because i HAVE been able to successfully flash cyanogenmod6 on it. but that was it.

could the kernel be the culprit? i ask because i thought that when in recovery, it didn't matter.

tonight i'll try to flash my nand of cyan, then try to wipe/flash one of the ROMs that have been giving me problems.

[ulysses]

ok, i'm not sure if i'm reading this right, but according to this, there are bad blocks on my phone? last portion of my recovery.log

mtd: not erasing bad block at 0x001e0000
mtd: not erasing bad block at 0x00260000
calling command write_raw_image
Writing BOOT:...
mtd: not writing bad block at 0x001e0000
mtd: not writing bad block at 0x00260000
E:Error finishing BOOT:
mtd: not writing bad block at 0x00260000
E:Failure at line 396:
write_raw_image PACKAGE:boot.img BOOT:
Installation aborted.
Failure at line 6:
install_zip SDCARD:/DamageControl-3.5-final.zip

is there a way to repair this? i was googling around, and found this,
http://forum.xda-developers.com/showthread.php?t=731657
in the last post on the second page, the OP said they updated hboot and fixed the issue, but i don't think there are any other versions of hboot.



please? anyone that understands this better than i do?

thanks much

[TheBundo]

I read the forums extensively, and have yet to see a convincing reason to leave DC 3.2.3. It is so stable for me, that I can't see introducing more problems into my life. Maybe I need to drink more.......

[ulysses]

Originally Posted by TheBundo

I read the forums extensively, and have yet to see a convincing reason to leave DC 3.2.3. It is so stable for me, that I can't see introducing more problems into my life. Maybe I need to drink more.......

i didn't say there was anything wrong with DC 3.2.3.
what i'm saying is that from what's on the log file, it looks like my phone has some bad blocks in the internal memory. can i fix it? if not, how would one go about getting the phone replaced? i can't ecactly call sprint and tell them that i discovered this while trying to flash a custom ROM... lol