[Nexus One Q&A, Help & Troubleshooting] goldcd:
I'm unsure if this is two problems or one, but just hoping somebody around here might have a clue what is up with my Nexus.

The background:

Worked my way up through the Cyanogen ROMS without any issue, switching from AmonRa to ClockworkMod about half way through.

Obviously I had to get Froyo on the phone, so installed Paul's and was happily on FRF50.

No issues whatsoever so far, until I noticed FRF72 was about today.

Tried to install the 1.8M patch - and it failed - ah well.

Tried to revert back to FRF50 with my nandroid backup and that failed as well...

..I am now worried.

I deleted some caches - and my nandroid backup worked... then I started fiddling again.. and same errors re-appeared.

Finally got the backup to take again - and I'm now leaving my phone well alone.

The errors:

When trying to install a flash image (every one I've tried so far) I get an error very similar to this one in the log:

...

calling command format

Formatting BOOT:...

mtd: not erasing bad block at 0x00220000

calling command write_raw_image

Writing BOOT:...

mtd: not writing bad block at 0x00220000

E:No space left on device

minzip: Process function elected to fail (in inflate)

E:Error writing BOOT:

E:Failure at line 69:

write_raw_image PACKAGE:boot.img BOOT:

Installation aborted.

Failure at line 6:

install_zip SDCARD:/clockworkmod/download/...​

I've just got one bad block listed above, but quite often more than one and on a seemingly wide selection of addresses.

I've not managed to get a single image to install on my phone at all (even going back to the OOB stock image).

When the Nandroid restore fails, it seems to write OK to the boot, but then just hangs locking the entire phone (batter out time) when writing the the data or system partitions.

I ended up going partition by partition to restore the image (2 goes on system, 7th time the charm on data).

The questions:

1) I assume I've got duff blocks on my partitions.

2) I assume I've got so many on root, that space is 'less than expected' - hence the no space left errors?

3) So assuming there's limited space, why does the restore seem to work, but images flashing onto boot fail?

4) Is the issues with nandroid restore likely to be the same (happens with the last 3 backups I've taken)? I don't seem to get a log written as it's just hanging.

5) Is my flash 'degrading' - I'm fine if stuff is marked as duff in the factory, but the ability of my flash seems to still be in a bit of 'flux'

7) Is there anyway I can scan the flash on my phone to get an overall status of the memory (~ChkDsk)?

The Big question:

8) Is there anything I can do, other than get the phone back to HTC?

I'm assuming an inability to flash a standard 'released by google build', would count as being a fault.

Most advice just seems to be to:

a) clear stuff

b) format stuff - oh and you sometimes get the bad block messages.

c) Just don't try to force write to those bad blocks, by writing less to the partition.

d) Google may alter the size of the partitons in the future, so there's enough working blocks for me in each of them.

Any help would be most welcome. I'm feeling quite glum about the whole drama.