Hey guys, that's a bit harsh!
I understand the question perfectly, so here's a translation for the grammar and punctuation pedants out there:-

The unfortunate OP has purchased a 200gb upgrade drive for his Series 1 UK (although this is not only applicable to UK machines) TiVo. When he bought the drive he mistakenly asked for it to be supplied with software version 2.5.5a rather than the more usual version 2.5.5 in the misguided belief that this would enable his TiVo to 'see' the full capacity of the drive - for which, of course, all he needs is the LBA48 kernel, not software version 2.5.5a which was issued to a few UK machines to circumvent problems with the way some TVs can't handle the TiVo's teletext output.
As a result of this mistake, when his TiVo made a daily call, the fact that the software version on the drive was different to that assigned to it in TiVo's database triggered the automatic software update process to "upgrade" his TiVo to version 2.5.5. However, because version 2.5.5a has a higher software ID than version 2.5.5, once the "upgrade" had downloaded and been installed on the spare system partition, the process that should run to apply it after the end of a daily call (but before the new guide data is applied to the database) failed with an error and aborted the daily call process too. This has been happening every night since the "upgrade" was downloaded, and the only way he has been able to get any guide data has been to repeatedly re-run Guided Setup, which downloads guide data and applies it without checking for the presence of a pending software update.
The OP also made the mistake of purchasing his drive from a cheap 'n' cheerful eBay seller who probably doesn't understand the problem or know how to fix it, and who is consequently keeping his head down in the hope that somebody else will help his unfortunate customer out.