Boot image too large?

[franklinvv]

When I try the new MCR with FroYo, I get the following error message:

Writing BOOT:
E:Error finishing BOOT:
E: Failure at line 386:
write_raw_image PACKAGE:boot.img BOOT:
installation aborted.

I read reports of other people having this issue with this ROM, and even people having this issue with DeFroST. Some people said that it's due to a 'messed up' boot partition, that can't fit the boot image included in the ROM. How can our boot partition be messed up like that?

 

[richardtrip]

When I try the new MCR with FroYo, I get the following error message:

Writing BOOT:
E:Error finishing BOOT:
E: Failure at line 386:
write_raw_image PACKAGE:boot.img BOOT:
installation aborted.

I read reports of other people having this issue with this ROM, and even people having this issue with DeFroST. Some people said that it's due to a 'messed up' boot partition, that can't fit the boot image included in the ROM. How can our boot partition be messed up like that?

That's because you have bad blocks on your boot partition. With 2 bad blocks the boot.img must be < 2304 kb. Will make one tomorrow for defrost.

 

[franklinvv]

I see. So how did I end up having bad blocks? Or are they already present out of the box on some devices?

 

[sucramco]

I see. So how did I end up having bad blocks? Or are they already present out of the box on some devices?

Any info on this yet, as to how, why, way out?

 

[StuMcBill]

I see. So how did I end up having bad blocks? Or are they already present out of the box on some devices?

I think all flash memory has bad blocks. There is nothing you can do about it.

My Nintendo Wii also has bad blocks on the NAND, totally normal.

 

[sucramco]

I think all flash memory has bad blocks. There is nothing you can do about it.

My Nintendo Wii also has bad blocks on the NAND, totally normal.

Interms of installing a new rom, (tried MCR r17) do I have to wait until one will actually fit? If I am right in thinking, the bad blocks mean there is not enough space to install the rom?
So hopefully when the MCR r18 is out, as long as it is smaller then the r17 it will install.

I am learning fast, but there is so much reading, it can be a lot to take in. Yesterday I messed up big time trying to install the rom many different ways, I ended up formatting the sd card before I backed up the back up to the PC. Luckily it was fairly easy launch recovery and install a freshly baked MCR 3.1, and then use Titanium to restore the apps and data. So no harm done, and thanks to everyone here and at Modaco who posted all the info I needed to acheive that.

 

[StuMcBill]

Interms of installing a new rom, (tried MCR r17) do I have to wait until one will actually fit? If I am right in thinking, the bad blocks mean there is not enough space to install the rom?
So hopefully when the MCR r18 is out, as long as it is smaller then the r17 it will install.

I am learning fast, but there is so much reading, it can be a lot to take in. Yesterday I messed up big time trying to install the rom many different ways, I ended up formatting the sd card before I backed up the back up to the PC. Luckily it was fairly easy launch recovery and install a freshly baked MCR 3.1, and then use Titanium to restore the apps and data. So no harm done, and thanks to everyone here and at Modaco who posted all the info I needed to acheive that.

Yeah I think you will have to wait until a boot.img is made that is small enough to fit on your memory, its a bit of a pain, but I don't think there is anything you can do?

 

[sucramco]

I'll just have to hope and pray like the football then.

 

[sbdroid]

When I try the new MCR with FroYo, I get the following error message:



I read reports of other people having this issue with this ROM, and even people having this issue with DeFroST. Some people said that it's due to a 'messed up' boot partition, that can't fit the boot image included in the ROM. How can our boot partition be messed up like that?

Guys,

I also have the same problem and dont know what to do next.
I am on CM but the new CM 5.0.8 also have the boot img more than 2.2 MB so i am stuck.

Neither can upgrade to FROYO as well.

Not sure if any one can help on this

 

[sbdroid]

That's because you have bad blocks on your boot partition. With 2 bad blocks the boot.img must be < 2304 kb. Will make one tomorrow for defrost.

Hi richard, I am new to defrost.

Please let em knwo if you make one. i would like to try it out.

Thanks a lot.

 

[jedisquirrel]

I have issues using large boot images as with modaco roms and richard's earlier rom's but richard's work fine for me now after about 0.6 ish. Hope this helps.

Cheers,
Drew

-------------------------------------
Sent via the XDA Tapatalk App

 

[sbdroid]

I have issues using large boot images as with modaco roms and richard's earlier rom's but richard's work fine for me now after about 0.6 ish. Hope this helps.

Cheers,
Drew

-------------------------------------
Sent via the XDA Tapatalk App

Can i put this ROM on N1

 

[peewster]

Is there a way to fix the badblocks?

 

[sucramco]

Is there a way to fix the badblocks?

I have asked. The only real option is the guys that mod the roms make a smaller boot image. So I have been informed.

It's not good.

 

[ieftm]

Is there a way to fix the badblocks?

These are physical parts of your NAND flash being broken. Small parts, but still.

So no, they can't be repaired.

 

[sucramco]

These are physical parts of your NAND flash being broken. Small parts, but still.

So no, they can't be repaired.

Could we unroot, and get a faulty replacement.

 

[jedisquirrel]

Sorry I didn't reply earlier, didn't see your message.

No because the kernel is different for majority of devices. There would probably be other issues that I'm not aware of either also would imagine.

Drew

I have issues using large boot images as with modaco roms and richard's earlier rom's but richard's work fine for me now after about 0.6 ish. Hope thi

Can i put this ROM on N1

-------------------------------------
Sent via the XDA Tapatalk App

 

[jedisquirrel]

I'm kinda hoping that the official froyo rom will bork the device for us with bad blocks. But I'm almost certain htc will be aware of the issue and the boot image will fit on our devices no problem.

If you were however to accidentally brick your desire, I'm sure they would replace your device.

Drew

-------------------------------------
Sent via the XDA Tapatalk App

 

[sbdroid]

I'm kinda hoping that the official froyo rom will bork the device for us with bad blocks. But I'm almost certain htc will be aware of the issue and the boot image will fit on our devices no problem.

If you were however to accidentally brick your desire, I'm sure they would replace your device.

Drew

-------------------------------------
Sent via the XDA Tapatalk App

Guys,

Any idea on the boot image size of froyo?
Will froyo fix our issues?