lost my original image

[ganjaman]

I had my hdd's backwards while running tivoscripts 1_01
I ended up formatting my tivo drive. Yes I am a retard.
So my original image is kaput.
By the way it is a hdvr2
I have a image called DTV-HDVR2.BAK @ 238+ mb but I am not sure how to get it back on the original 40 gb drive.
I also have a file named hdvr2-3.1.1b.mfs @ 281 mb+
I am not sure where to go from here. I have the tivoscripts 1_02 as well and went thru the process and it seemed pretty easy, once I figured out the configuration screw up. I am lost in linux so please take it easy on me.

I could really use some help.
I have too many hours into this already

Thank you for any help.

[PlainBill]

I had my hdd's backwards while running tivoscripts 1_01
I ended up formatting my tivo drive. Yes I am a retard.
So my original image is kaput.
By the way it is a hdvr2
I have a image called DTV-HDVR2.BAK @ 238+ mb but I am not sure how to get it back on the original 40 gb drive.
I also have a file named hdvr2-3.1.1b.mfs @ 281 mb+
I am not sure where to go from here. I have the tivoscripts 1_02 as well and went thru the process and it seemed pretty easy, once I figured out the configuration screw up. I am lost in linux so please take it easy on me.

I could really use some help.
I have too many hours into this already

Thank you for any help.

This really belongs in the Newbie's forum, you aren't the first person to do this, and won't be the last.

You MIGHT be able to hook the 40 Gig and run through the restore phase of TiVoScripts. If it fails, try this:

Make a folder called tivo on your Primary Master hard drive (it may already be there). Copy the two images you have to that folder.

Hook up your 40 gig drive as secondary master.

Boot from TiVoScripts 1.02

Select Monte; skip backup, select Restore.

Go through each step as it mounts the cdrom and your C drive.

Hit Alt-F2 and type in the following command:

mfsrestore -zpi /cdrive/tivo/MYFILENAME.BAK /dev/hdc

(of course, substitute the name of 1 of the files for MYFILENAME.BAK) Remember, Linux is case sensitive - BAK is NOT the same as bak or BaK.

There are four possible outcomes: 1. It will give an error message such as 'No such file or directory' - check the file name and spelling. 2. It will tell you there is not enough room on the target drive - try the other file. 3. It will go through most of the restore, then tell you there isn't enough room - try the other file. 4. It will restore the file - you're good to go to step B.

Step B: Put the drive in the TiVo, step through the menus and select Clear and Delete Everything. It will reboot after it deletes everything. Turn off the power and remove the drive. Now you have an 'original' image on the hard drive.

PlainBill

[malfunct]

He could also boot the sleeper disk, hit ctrl-f2 (or is it alt-f2) and go to the command line. Then he could read the guide on using mfs tools and do the restore that way.

[PlainBill]

He could also boot the sleeper disk, hit ctrl-f2 (or is it alt-f2) and go to the command line. Then he could read the guide on using mfs tools and do the restore that way.
:rolleyes:
You OBVIOUSLY don't make enough mistakes :)

It's Alt-F2

I had considered that. But it would leave him with the problem of figuring out drive assignments, mount points, and mounting drives. I'm sure YOU could do it with your eyes closed in 10 seconds. It would take me at least 10 minutes. I figure let him get the system running, make him a hero for his wife, (fiance, Girlfriend, or significant other - choose no more than two). THEN we throw the 'learn linux or die' test at him.

PlainBill

[ganjaman]

It worked. Thank you.
Hopefully the monte hack will go well.
thanks for all the help.
I feel like Rick James in 1987 without the coke, hookers and money. lol

[ganjaman]

now that I have my image back.
Should I just use the monte hack on the tivoscripts1-02 disk ?
I think I can handle that part now that I wiped not 1 but 3 original 40gb drives.
I hate that hack that disappears when you dont reboot properly.

Thanks again

[PlainBill]

now that I have my image back.
Should I just use the monte hack on the tivoscripts1-02 disk ?
I think I can handle that part now that I wiped not 1 but 3 original 40gb drives.
I hate that hack that disappears when you dont reboot properly.

Thanks again

Yes. Better not press your luck by trying anything fancy. :D

PlainBill

[ganjaman]

Thanks for moving the thread.
Ok I restored both images to see the difference.
One is 3.1.u5-01-2-151
and #2 is 3.1.1b-02-2-151 and calls the model # as 1 HDVR3??
it also had a note attached as follows

The extracted file (HDVR2-3.1.1b.mfs) has a MD5 hash:
a3b24d09d4394a6bf34de4dd846f052a

Does it make a difference in which one I use.
#2 had a diffeent boot procedure that I havent seen before.

I also have a sd-drv-40 waiting for its turn. Do I need a 4.0 image for it?

Thank you plenty

[PlainBill]

Thanks for moving the thread.
Ok I restored both images to see the difference.
One is 3.1.u5-01-2-151
and #2 is 3.1.1b-02-2-151 and calls the model # as 1 HDVR3??
it also had a note attached as follows

The extracted file (HDVR2-3.1.1b.mfs) has a MD5 hash:
a3b24d09d4394a6bf34de4dd846f052a

Does it make a difference in which one I use.
#2 had a diffeent boot procedure that I havent seen before.

I also have a sd-drv-40 waiting for its turn. Do I need a 4.0 image for it?

Thank you plenty

Use the 3.1.1b image. The 3.1.u5 is older.

You CANNOT use a 4.0 image with the SD DRV40. Use the 3.1.1b (or a 3.1.1c if you can find one).

PlainBill

[ganjaman]

This was in the readme attached with the image.
Does it mean anything?

The extracted file (HDVR2-3.1.1b.mfs) has a MD5 hash:
a3b24d09d4394a6bf34de4dd846f052a

It is stuck in the deleting and clearing everything stage. It may just take some more time.

[PlainBill]

This was in the readme attached with the image.
Does it mean anything?

The extracted file (HDVR2-3.1.1b.mfs) has a MD5 hash:
a3b24d09d4394a6bf34de4dd846f052a

It is stuck in the deleting and clearing everything stage. It may just take some more time.

C&D takes up to an hour, for some reason 4.x seems to take the full hour. Have a cup of tea, relax.

The MD5 hash value can be used to determine if the image downloaded correctly (well there apparently is 1 chance in 2^128 that the hash would match even for a corrupted file).

PlainBill

[ganjaman]

It sure took its time.
OK back to the tivoscripts again.
I did the backup phase, It had me reboot and move the primary master and make it the secondary master. It told me it would resume on reboot and didnt. (I hate liars) well anyway I got lost and chose several options and got error messages.
I am reformatting the 120 gb drive and starting over.
If I get the same problem should I go to restore?

[PlainBill]

It sure took its time.
OK back to the tivoscripts again.
I did the backup phase, It had me reboot and move the primary master and make it the secondary master. It told me it would resume on reboot and didnt. (I hate liars) well anyway I got lost and chose several options and got error messages.
I am reformatting the 120 gb drive and starting over.
If I get the same problem should I go to restore?

You misunderstood. There are three hard drives involved.

Storage drive - A drive formatted FAT32, it may be your PCs primary hard drive. It is primary master, and is NEVER moved.

Source drive - The original drive from your TiVo. It is connected as secondary master for the Backup phase, then put on a shelf.

Target drive - The drive which will be in your TiVo when you watch TV. It is connected as secondary master for the Restore, Surgery, and Hacking phases.

PlainBill

[(o)here(o)]

you also don't need to format your new "target" drive. I just deleted all partitions off mine using fdisk and restored to it just like that.

[ganjaman]

alrighty then.
Three drives it is.

be back soon I am sure.

thanks of course

[PlainBill]

you also don't need to format your new "target" drive. I just deleted all partitions off mine using fdisk and restored to it just like that.

You don't even have to delete the partitions. Sleeper's iso takes care of that for you.

PlainBill

[ganjaman]

Ok getting closer.
I am at the point of entering IP addresses.
I have a dlink router and not sure what else to enter
i saw somewhere to enter addresses of
192.168.0.129 for dtivo
192.168.0.1 for gateway
192.168.0.255 for for broadcast and
255.255.255.0 for netmask

but what about my router addy.
yes I am a newbie but persistant..

thanks plenty

[PlainBill]

Ok getting closer.
I am at the point of entering IP addresses.
I have a dlink router and not sure what else to enter
i saw somewhere to enter addresses of
192.168.0.129 for dtivo
192.168.0.1 for gateway
192.168.0.255 for for broadcast and
255.255.255.0 for netmask

but what about my router addy.
yes I am a newbie but persistant..

thanks plenty

The gateway address is the router address. Before using those addresses, verify the IP address of your computer by going to a dos prompt and typing ipconfig. That will give you the subnet mask and default gateway. The broadcast address is the same as the gateway, except the last group is 255. And with that information, you should be able to figure out the Address for the TiVo.

PlainBill

[ganjaman]

i entered in the dos prompt
ipconfig /all

and received ip address of 192.168.0.101
but in zone alarm it shows an addy of 192.168.0.0
and the gateway is 192.168.0.1

thanks for any input

[PlainBill]

i entered in the dos prompt
ipconfig /all

and received ip address of 192.168.0.101
but in zone alarm it shows an addy of 192.168.0.0
and the gateway is 192.168.0.1

thanks for any input

What is your network configuration? Do you have a router?

It appears your computer has an IP address of 192.168.0.101, and the router's ip address is 192.168.0.1. I've avoided Zone Alarm, so I have no idea where it came up with 192.168.0.0.

The important thing is the last group must be unique for each device on the network. 192.168.0.129 should be OK for the TiVo, 192.168.101 would NOT be.

PlainBill

[PlainBill]

i entered in the dos prompt
ipconfig /all

and received ip address of 192.168.0.101
but in zone alarm it shows an addy of 192.168.0.0
and the gateway is 192.168.0.1

thanks for any input

What is your network configuration? Do you have a router?

It appears your computer has an IP address of 192.168.0.101, and the router's ip address is 192.168.0.1. I've avoided Zone Alarm, so I have no idea where it came up with 192.168.0.0.

The important thing is the last group must be unique for each device on the network. 192.168.0.129 should be OK for the TiVo, 192.168.101 would NOT be.

PlainBill

[ganjaman]

ok so i have all addresses but the tivo ip.the gateway is
192.168.0.1
So how do I get the tivo ip?

[PlainBill]

i entered in the dos prompt
ipconfig /all

and received ip address of 192.168.0.101
but in zone alarm it shows an addy of 192.168.0.0
and the gateway is 192.168.0.1

thanks for any input

What is your network configuration? Do you have a router?

It appears your computer has an IP address of 192.168.0.101, and the router's ip address is 192.168.0.1. I've avoided Zone Alarm, so I have no idea where it came up with 192.168.0.0.

The important thing is the last group must be unique for each device on the network. 192.168.0.129 should be OK for the TiVo, 192.168.101 would NOT be.

PlainBill

[PlainBill]

i entered in the dos prompt
ipconfig /all

and received ip address of 192.168.0.101
but in zone alarm it shows an addy of 192.168.0.0
and the gateway is 192.168.0.1

thanks for any input

What is your network configuration? Do you have a router?

It appears your computer has an IP address of 192.168.0.101, and the router's ip address is 192.168.0.1. I've avoided Zone Alarm, so I have no idea where it came up with 192.168.0.0.

The important thing is the last group must be unique for each device on the network. 192.168.0.129 should be OK for the TiVo, 192.168.101 would NOT be.

PlainBill

[ganjaman]

cool, on to the final phase.
I have the dssapp howto.txt file.
But little confused. again.
Do I put the newly hacked hard drive in the tivo boot up while connected to my compaq ethernet/usb device? should I let it boot all the way first?
I see these instructions (below) but it doesnt explain how to get access to these files. I can handle the hexedit part. just need the boot up procedure.

P.S. I have a nice suprise for you when I am done.

gracias


edit: DSS HACKING INFORMATION REMOVED

[fixn278]

Discussion of dss hacking and HU card use is prohibited here at Dealdatabase. I suggest you remove it before a moderator bans you.

[acr2001]

Yea you better remove that!!! ;)
(do a google search and youll find the answer to your question on one of the more uhhh..."dark" forums)

[PlainBill]

cool, on to the final phase.
I have the dssapp howto.txt file.
But little confused. again.
Do I put the newly hacked hard drive in the tivo boot up while connected to my compaq ethernet/usb device? should I let it boot all the way first?
I see these instructions (below) but it doesnt explain how to get access to these files. I can handle the hexedit part. just need the boot up procedure.

P.S. I have a nice suprise for you when I am done.

gracias


The easiest way to transfer files between the TiVo and your PC is via FTP. Until I got my ethernet working I used the serial connection and zmodem. FTP is MUCH faster, just make sure you're doing the transfer in binary mode!

PlainBill

[ganjaman]

sorry about that.

[ganjaman]

For some reason I cant boot up.

I'm about to enter week 2 of this project :(

Any advice is appreciated.

[PlainBill]

For some reason I cant boot up.

I'm about to enter week 2 of this project :(

Any advice is appreciated.

Suggested troubleshooting sequence:

Do a restore, test the drive in the TiVo. If it works, all the hardware is probably good. Delete the variables file in /cdrive/tivo. This can cause problems during surgery, but an error message often does not show up.

Do surgery, test the drive in the TiVo. If it fails, you might have a bad hard drive.

If it works, do Hacks. And test again.

I will say it again: Monitoring the console output with a serial cable and Hyperterminal or TeraTerm will give a lot of information as to what is going wrong.

PlainBill