Ran script on 3.0 Machine... now I'm hosed.

[mcukier]

Argggghhh! Being the ***** that I am, I ran the "TivoNet" script on my 3.0 machine.

I had previously enabled dial-in over broadband with the ",#401" dial prefix. Now, however, the dial in doesn't work!! My modem is blown (suprise) so this is the only way my TiVo can connect with the outside world... and I'm losing guide data fast....

I've already attempted to undo most of what the script has done, but seemingly to no avail. Suggestions?

What I've undone:

1) I've renamed the "route.tivo" back to "route" in both partitions

2) deleted "tivone.o", "8390.o", and "probe.o" from lib/modules in both partitions

3) deleted all lines that were added to "rc.sysinit" (in both partitions).

ARRRGGGHHH!! Anyone that can help me will find themselves a new best friend.

Thanks in advance to all who respond...

Cheers,
Mark:confused:

[iansmith]

I did the same thing. When I checked the log files, it was trying to use the modem even though I had it set to ,#401.

I fixed mine by re-enabling initrd and rebooting. The TiVo replaced the messed up files and now it works good.

Make sure your TiVo's networking is correct by pinging some internet sites too.

--
Ian

[horwitz]

How do I "re-enable initrd"?

I'm in the same boat as mcukier -- I ran the TivoNET script on my 3.0 (series 1) machine and my Ethernet connection for guide updating ins't working (I can telnet in and traceroute out, however). My modem stopped working and I now have only 6 days of guide data left.

HELP!

Thanks

p.s. I'd still like to be able to telnet in. I have stuff in /hack and /var/hack -- is anywhere safe from initrd?

[horwitz]

First: PROBLEM SOLVED (or at least so it appears).



I couldn't get any of the kill_initrd binaries to execute by merely FTPing them to my TiVo, I finally gave up and did a kickstart-52. I then took out the drive and ran this script (http://www.jsprod.net/tivo30script.htm) (for my SA v3.0 TiVo). Everything seems great, and I did my first ever over-Ethernet update. Man that was fast (well, the on-line part -- the off-line part took a few hours, what with the TiVo needing to update more than a week's worth of data)!

[TrondTTW]

I did the exact same thing the other night. Or at least I think I did. I've got an SA series 1 TiVo that I was *attempting* to configure for Telnet using these instructions:

http://www.jsprod.net/tivo30script.htm

Using ,#401 has worked in the past for me, but it no longer appears to. The Tivo doesn't request an IP address from my DHCP server so I can't telnet into it either. I'm going home tonight with the plan of sticking the HD into my other computer and gaining access via Dylan. Given that this will be only the 2nd time logged into BASH on my TiVo, I'm not too familiar with what I need to do to make it work again. I'm not quite following these previous posts and would really appreciate some good step-by-step assistance fixing the issue.

Thanks!
Trond

[horwitz]

Originally posted by TrondTTW
I did the exact same thing the other night. Or at least I think I did. I've got an SA series 1 TiVo that I was *attempting* to configure for Telnet using these instructions:

http://www.jsprod.net/tivo30script.htm

Using ,#401 has worked in the past for me, but it no longer appears to. The Tivo doesn't request an IP address from my DHCP server so I can't telnet into it either. I'm going home tonight with the plan of sticking the HD into my other computer and gaining access via Dylan. Given that this will be only the 2nd time logged into BASH on my TiVo, I'm not too familiar with what I need to do to make it work again. I'm not quite following these previous posts and would really appreciate some good step-by-step assistance fixing the issue.

Thanks!
Trond

Is my impression of your situation correct?
Your TiVo was unhacked (except for maybe a larger hard drive) and ,#401 was all you were doing to get Ethernet. And then you ran the above script (http://www.jsprod.net/tivo30script.htm) and your calls no longer work over Ethernet. When you ran the script it worked without any problems. (You had your drive in the primary slave position or changed the script appropriately, etc.)

Here are my two suggestions:

First:
Try rebooting.

Last*: (This is what I ened up doing, but running the v3.0-modified script wasn't the cause of my problem, running the v2.5 script on my v3.0 (SA Series 1) TiVo was.)
Reboot and hold pause until both of your lights turn yellow. Then type 5 2. This should reinstall the OS (I think) and then you take out the drive, put it in your PC, and run the script (http://www.jsprod.net/tivo30script.htm) again.

It should be noted that I am pretty much a total novice. But I'm telling you what I did. YMMV.



*There a several things you could do less drastic than this; except for wiping your whole drive or throwing your TiVo out the window, I'm not sure what's more drastic.