killhdinitrd vs. kernel version?

[Stew]

I'm trying to hack an HR10-250, running 3.1.5e, for the first time, using an old
Fedora Core 1 box to do the mods.

I copied the original drive to a WD2500JB using dd. BTW, a short copy run as
a test was quite slow (full copy would take almost 7 hours), but adding the
parameter bs=1024 allowed the copy to complete in just under 2.5 hours.
The copy (unhacked) runs fine in the DVR.

When I tried to run killhdinitrd 0.9.3 on a kernel copied from partition 6:
orig blocks = 00000f71
orig image size = 001ee3e0 (excludes header)
extended image size = 001eebe0
kernel+initrd length = 001ee1d8 (excludes sig)
kernel+initrd crc32 = f053627d
fatal: no exploit found for this kernel

Tried partition 3:
orig blocks = 00000f71
orig image size = 001ee3e0 (excludes header)
extended image size = 001eebe0
kernel+initrd length = 001ee1b8 (excludes sig)
kernel+initrd crc32 = aa296699
fatal: no exploit found for this kernel

I guess that my 3.1.5e is not close enough to the 3.1.5 that killhdinitrd 0.9.3
supports. If that is not correct, what may be wrong with my environment?

Assuming that they are indeed incompatible, is there another version of
killhdinitrd that works with 3.1.5e? If not, is it feasible to modify the source
code? Is there any good descriptive info that would help me do that?

I saw a thread suggesting that 3.1.5 be used. Is anything important lost in
this downgrade? Or, do I need to chain-load 3.1.5e (or something else)?
If so, would it be safe to test with 3.1.5 and then add the chain-load?

Thanks in advance for any suggestions.

[Jamie]

...I guess that my 3.1.5e is not close enough to the 3.1.5 that killhdinitrd 0.9.3 supports.Correct.
Assuming that they are indeed incompatible, is there another version of killhdinitrd that works with 3.1.5e?Nope.If not, is it feasible to modify the source code? Is there any good descriptive info that would help me do that?It's feasible, but not trivial, and unnecessary (see below). I saw a thread suggesting that 3.1.5 be used. Is anything important lost in this downgrade?Nothing at all. In most cases, the difference between kernel .px packages in different tivo software revisions is all in the initrd (which killhdintird allows you to bypass), not in the kernel itself.

[captain_video]

Download the $5 LBA48 enhanced boot CD from PTVUpgrade. It contains the killhdinitrd'd 3.1.5 kernel you need for your HDTivo. You can use it with any 3.1.5x HDTivo OS version. Here's the link:

http://www.ptvupgrade.com/products/software/lba48/index.html

[wadsworthj]

I had a similar problem this evening:

orig blocks = 00000f71
orig image size = 001ee3e0 (excludes header)
extended image size = 001eebe0
kernel+initrd length = 001ee1d7 (excludes sig)
kernel+initrd crc32 = 334df219
fatal: no exploit found for this kernel

running 3.1.5f

after reading this thread I downloaded the $5 ptvupgrade cd and am still having the same problem.

I'm extraordinarily experienced working with hardware and relatively comfortable in a linux environment but this is my first tivo. any help greatly appreciated.

[cheer]

Same problem, same solution. Don't try and use killhdinitrd on a 3.1.5f kernel. Just use the 3.1.5 kernel that came on the ptvupgrade CD.

[wadsworthj]

Thanks cheer,

Immediately after posting last night I did some more searching and found the solution...

I apologize for the hasty post, but this was the only thread that came up when i searched for "no exploit found for this kernel"

If anybody else finds this thread through a search for "fatal: no exploit found..." please go to this thread and follow Cheer's general steps: http://www.dealdatabase.com/forum/showthread.php?t=49870

seems to be working for me.

Thanks all.