writing 'boot'... FAILED

---

Good morning!

With the update from EPE76 to FRF91:

Installing update...
assert failed: write_raw_image("/tmp/boot.img", "boot")
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.

When I tried to update to R21 via recovery-RA-nexus-v1.7.0.1:

Writing BOOT...
E:No space left on device
E:Error writing BOOT:
Failure at line 380:
write_raw_image PACKAGE:boot.img BOOT:

Installation aborted.

If we take boot.img from 2.2 and do «fastboot flash boot boot.img»:

sending 'boot' (2336 KB)... OKAY [ 0.391s]
writing 'boot'... FAILED (remote: image update error)
finished. total time: 1.281s

Via recovery downgrade to ERD79 and download OTA FRF91. Error.
The kernel can't be written because there's not enough boot partition space.

I found a similar problem (forum.xda-developers.com/showpost.php?p=6779420), but the this solution did not help.
Command "fastboot flash zimage zImage" return error.


It is hoped that the problem can be corrected? Reducing the size of boot up such as it was in 2.1? Or maybe you can increase the size of the partition boot?
The fact that Russia is not valid warranty google and I can not fix your phone officially.

Thanks and sorry for my English.

Try this:

In Fastboot USB, flash to Clockwork Recovery (fastboot flash recovery recovery.img). Once you're done with that, enter the recovery and go to the Partition menu and format the boot partition first (and the rest of them, except for SDCard). After that, flash any one of the FRF91 builds available here, such as CM6 RC1 or MCR.

Originally Posted by willverduzco

Try this:
In Fastboot USB, flash to Clockwork Recovery....

Thank you!
I did it, but the result has not changed. If I write boot from FRF91:

>fastboot flash boot boot.img
      sending 'boot' (2336 KB)... OKAY [  0.406s]
                writing 'boot'... FAILED (remote: image update error)
finished. total time: 1.328s

I think have to resize the boot partition, and not just format it.
But superboot.himem.img from EPE76 (2162 KB) installed correctly.

Originally Posted by iNDEX3

It is possible to solve a similar problem with Nexus One?
forum.xda-developers.com/showthread.php?t=731657

from G1 thread http://forum.xda-developers.com/show...71#post7061471


unrelated, but I maybe able to help here

some observasions have been made with older G1 SPL's and newer 'larger' kernels, where they fail to boot, current theory is that for whatever reason the ramdisk actually overwrites the tail end of the kernel in memory. This is unproven, but is academic as the newer SPLs do not have the same issue and are superior in other respects.
In any case I don't belive that the issue you are having is the same, as you are getting a clear message that the boot.img write has failed.
This error could be due to failed nand, where the blocks in boot partition have failed and you have a reduced sized boot partition.

do you get errors with the following ?

fastboot erase boot

does

fastboot flash boot <boot.img>

then work as expected?

also , are you using the same SPL as others, who don't have the same issue?

Thank you for trying to help!

Originally Posted by Firerat

do you get errors with the following ?

fastboot erase boot

>fastboot erase boot
                erasing 'boot'... FAILED (remote: not allowed)
finished. total time: 0.063s

Originally Posted by Firerat

also , are you using the same SPL as others, who don't have the same issue?

Naturally so!

Originally Posted by iNDEX3

Thank you for trying to help!

>fastboot erase boot
                erasing 'boot'... FAILED (remote: not allowed)
finished. total time: 0.063s

Naturally so!

ok, so next option is to write the boot.img to recovery,

fastboot flash recovery <boot.img>

if that works then you will have to get to recovery with

fastboot boot <recovery.img>

not ideal, but if you can do a normal boot via a 'boot to recovery' you have no option


edit:

thinking about I have another option, but its a little bit more complicated

write a custom zImage to /boot
this kernel has its own mtd map, with a new partition where system normally starts ( or maybe cache or data ), and get it to load the ramdisk from that address
This assumes that the problem area is towards the end of boot partition

BUT, tbh , it seems like you have an actual hardware problem, it might be better to return it under warranty, less fun but better solution.

Thanks for help and hint!
That's what has helped:

>fastboot boot boot.img
        downloading 'boot.img'... OKAY [  0.391s]
                       booting... OKAY [  0.063s]
finished. total time: 0.469s

But temporarily. Ie until the first reboot.

But to fully solve the problem I need a magic "recovery.img"? Or something I did not understand?

I tried but failed to write of the default zImage to /boot

Russia is not covered by Google warranty and I can not fix my phone officially.
In addition, the phone works fine with Android 2.1, but I want 2.2

edit:

After "fastboot flash recovery boot.img" I understand what "normal boot via a 'boot to recovery'"
This is what I need! Thank you!

Originally Posted by iNDEX3

Thanks for help and hint!
That's what has helped:

>fastboot boot boot.img
        downloading 'boot.img'... OKAY [  0.391s]
                       booting... OKAY [  0.063s]
finished. total time: 0.469s

But temporarily. Ie until the first reboot.

But to fully solve the problem I need a magic "recovery.img"? Or something I did not understand?

I tried but failed to write of the default zImage to /boot

Russia is not covered by Google warranty and I can not fix my phone officially.
In addition, the phone works fine with Android 2.1, but I want 2.2

well, if we assume that your boot partition is 'broken', then we can use the recovery partition

i.e., instead of writing boot.img to boot, we write it to recovery

fastboot flash recovery <boot.img>

so instead of going into recovery you go into the ROM

if you do this, then you can only get to recovery with

fastboot boot <recovery.img>

but it is more useful to be able to boot the ROM any time than recovery.

the 'trick' with zImage would be a lot more complicated, but would allow you to keep recovery.img on the phone

Actually, I still need to work out if we can load the ramdisk from a separate source to the boot.img, for now useing recovery for boot.img is your best bet

I had similar problems and have concluded that it is due to bad mtd blocks in the boot partition.

I found the address of the bad blocks with the recovery.log from amon ra recovery. After trying to flash some custom kernels.

I currently have a ticket in with htc to send the phone in for repair. Hopefully they will get it fixed up.
________________________
N1 w/ XDA App

Originally Posted by Firerat

well, if we assume that your boot partition is 'broken', then we can use the recovery partition

i.e., instead of writing boot.img to boot, we write it to recovery

This is what I need! Thank you!