How I fixed writing recovery error

endsleym · #1 (**permalink**) 03-24-2011, 08:51 PM

if you getting this error:
error writing recovery: No space left on
mtd: skipping write block at 0x00400000
mtd: erase failure at 0x00420000 (I/O error)
mtd: erase failure at 0x00420000 (I/O error)
mtd: skipping write block at 0x00420000
mtd: erase failure at 0x00440000 (I/O error)
mtd: erase failure at 0x00440000 (I/O error)
mtd: skipping write block at 0x00440000
mtd: erase failure at 0x00460000 (I/O error)
mtd: erase failure at 0x00460000 (I/O error)
mtd: skipping write block at 0x00460000
mtd: erase failure at 0x00480000 (I/O error)
mtd: erase failure at 0x00480000 (I/O error)
mtd: skipping write block at 0x00480000
mtd: erase failure at 0x004a0000 (I/O error)
mtd: erase failure at 0x004a0000 (I/O error)
mtd: skipping write block at 0x004a0000
mtd: erase failure at 0x004c0000 (I/O error)
mtd: erase failure at 0x004c0000 (I/O error)
mtd: skipping write block at 0x004c0000
mtd: erase failure at 0x004e0000 (I/O error)
mtd: erase failure at 0x004e0000 (I/O error)
mtd: skipping write block at 0x004e0000
error writing recovery: No space left on device device.

You are not the only one and after searching around I could not find an answer that worked. I wanted to change my recovery (to make sure my RSA keys were backed up). I could not find any answers which worked for me. So after countless hours, I realized that I still had S-ON so I tried unrevoked forever (if you do not have a working recovery I can post how to get around that too) and what do you know I no longer get those errors and I can change recoveries all day. So it seems having S-ON may be causing some of people's inability to write to recovery.

**lkillen** · #2 (**permalink**) 03-24-2011, 11:19 PM

S off is necessary to install not Certed files.

endsleym · #3 (**permalink**) 03-25-2011, 01:06 AM

The odd thing is I was rooted and switched recoveries at least twice before I started getting that error.

mktw · #4 (**permalink**) 11-23-2011, 04:05 PM

Hi,

I'm facing the same errors while doing flash_image from terminal.. (though i'm on different device lenovo A60 Android 2.3)
can u explain whats S-ON and how to do it?

Thanks in advance..

Quote:

Originally Posted by endsleym

if you getting this error:
error writing recovery: No space left on
mtd: skipping write block at 0x00400000
mtd: erase failure at 0x00420000 (I/O error)
mtd: erase failure at 0x00420000 (I/O error)
mtd: skipping write block at 0x00420000
mtd: erase failure at 0x00440000 (I/O error)
mtd: erase failure at 0x00440000 (I/O error)
mtd: skipping write block at 0x00440000
mtd: erase failure at 0x00460000 (I/O error)
mtd: erase failure at 0x00460000 (I/O error)
mtd: skipping write block at 0x00460000
mtd: erase failure at 0x00480000 (I/O error)
mtd: erase failure at 0x00480000 (I/O error)
mtd: skipping write block at 0x00480000
mtd: erase failure at 0x004a0000 (I/O error)
mtd: erase failure at 0x004a0000 (I/O error)
mtd: skipping write block at 0x004a0000
mtd: erase failure at 0x004c0000 (I/O error)
mtd: erase failure at 0x004c0000 (I/O error)
mtd: skipping write block at 0x004c0000
mtd: erase failure at 0x004e0000 (I/O error)
mtd: erase failure at 0x004e0000 (I/O error)
mtd: skipping write block at 0x004e0000
error writing recovery: No space left on device device.

You are not the only one and after searching around I could not find an answer that worked. I wanted to change my recovery (to make sure my RSA keys were backed up). I could not find any answers which worked for me. So after countless hours, I realized that I still had S-ON so I tried unrevoked forever (if you do not have a working recovery I can post how to get around that too) and what do you know I no longer get those errors and I can change recoveries all day. So it seems having S-ON may be causing some of people's inability to write to recovery.