Series1 DirecTiVo Software Update (3.5.0) Migration Thread

[schampio]

Any way to verify whether they actually put an LBA48 kernel in with this one. Wouldn't that be nice? No more trashed S1's when the updates come out.

[Blackfoot]

Any way to verify whether they actually put an LBA48 kernel in with this one. Wouldn't that be nice? No more trashed S1's when the updates come out.
Based on the previous posts about multiple reboots, I would highly doubt this kernel has LBA48 support. Not to mention they have not done it with any of the previous 3.5x releases. I'm still trying to find out what is included with this update. And hopefully someone can tear the tivoapp apart soon.

[gohrnz]

so what does it take to get the new echo -ne ******** statement to turn off tystream encryption on this new 3.5c code?

[tivoupgrade]

Any way to verify whether they actually put an LBA48 kernel in with this one. Wouldn't that be nice? No more trashed S1's when the updates come out.

Yes (mentioned earlier in this post (http://www.tivocommunity.com/tivo-vb/showthread.php?p=4941247&&#post4941247)) You need to get your unit up and running on your network; get a copy of lba48chk, ftp it over and then run it from the telnet prompt; the output will show you whether the kernel is able to read beyond the 137GB boundary of your drive.

If you are not comfortable doing that, don't pull your hair out; best to assume it is NOT an LBA48 kernel as it would likely be a much bigger revision change. Just install the LBA48 kernel as previously prescribed. Either that or downrev to 3.5b and sit tight until more is known.

[rpongett]

We've not heard anything from anyone about 3.5c; but the fact that you have it is an indication that something is going on (and that others may get it too) and yes, you'd need to put the LBA48 kernel back on...

Some follow-up questions:

What type of kit did you put in - and how long ago did you get it? What version of the software was on it prior to 3.5c?

The curious thing, to me, is that ever since 3.5b started shipping, we've set up these drives, by default, to not automatically upgrade unless you explicitly change the dialing prefix and have the system dialing out.

So what I'm wondering is... was your unit making its daily call by itself? Did you make any changes to the software on the drive after we sent it?

More info is good, even if it doesn't seem important...


Thx,
LouAfter Imaging my drives with InstantCake 3.5b months ago, I set my Series 1 Dtivo (Phillips) to dial out via internet for PPV purposes. ,#401. I thought I'd blocked software upgrades, but there were a few different things I was messing around with a few months ago, and I think I enabled them again.

Yesterday, it upgraded to 3.5c and, unlike last time, completely nuked my system. Reboot loop (reboot, powering up screen, gray almost there screen, repeat). No way to get in. After yanking the drives and going through Linux CD boot on the PC, it had flipped my active partition to #4, but oddly kept my boot partition at #6. No idea why, but it did. I tried to flip back to both options (3/4 and 6/7). All of this involving multiple drive yankings back and forth from Tivo to PC and back, which are just excruciatingly slow and annoying for me after a while on diagnosis. No luck.

I finally (setting it back to boot 6th and active 7th) at least got serial output (it was also at least showing the DVRUpgrade splash pic for "Almost There"), but I didn't have time for further operation attempts. After seeing the mfsd error killing it every time, that was it. No idea what caused it beyond it likely not having an LBA48 Kernel, though my older systems at least booted up on the new partition in the past after such upgrades. Not this one.

I could have gone for some attempted long LBA48 Kernel fixes from the PC and messarounds, but I HAD to have this thing up and running with guide data for Saturday. These things many times take hours of back and forth tinkering. No other option.

So I wiped it and threw on InstantCake 3.5b. I now have upgradesoftware=false as a bootpage parameter and put the export lines for that variable in the proper spots in rc.sysinit. I'm hoping that will barricade me against further system detonations via update. I think I'm sticking with 3.5b on this box for the duration of its life now.

If you're interested, a copy of the serial output during the reboots is on this thread:

http://www.tivocommunity.com/tivo-vb/showthread.php?t=364479

[danmcd]

If I see or hear anything my end, or we make any updates to the tools, I'll let you know; please do let us know if/when you get your system straightened out.

Lou

PS As was pointed out by one of the guys here: "isn't it interesting that DirecTV tends to roll out these updates right before a new TV season starts?"

Bad news, I used copykern (3.1.x+ kernel, which is IIRC the LBA48 one), but even after a
full reformat stored programs are corrupt and cause crashes.

Is there ANYTHING that can help me? I don't have a instacake CD, but I suppose if reverting to a no-upgrade 3.5b would do the trick, I guess it would work.

PLEASE help, my kids are gonna be not please if Monday's PBS KIDS don't record! :)

Dan

[tivoupgrade]

I've confirmed that the 3.1.0+ kernel mentioned in the first post does work fine with 3.5c, so if you using a standard mfstools backup created from a 3.5c system, you can safely use CopyKern to replace the kernel, or just manually dd the kernel into the appropriate partition. You'll need to do a killinitrd FIRST, or install your CacheCard/TurboNet drivers (the Silicondust utility will kill the initrd for you). IE, don't replace your kernel until AFTER you've killed your initrd.

[danmcd]

I shelled out for InstantCake and I reverted to 3.5b. So far, so good, and I'm assuming that all I lose would be PPV via TiVo itself.

I've confirmed that the 3.1.0+ kernel mentioned in the first post does work fine with 3.5c.

I tried this with the 4.04 LBA free disk, like I said earlier, and it failed. Unless the kernel also reverts when one does "erase and reformat" or whatever-that-menu-option-is, I think I did everything properly. Let me give my precise steps:

1.) Discovered 3.5c had been installed, thanks to power-flickers that caused reboots.

2.) Verified that my saved programs were shot to hell.

3.) Yanked drive, did copykern.

4.) Reinstalled drive, immediately selected "erase and reformat".

5.) Recorded programs still caused reboots.

6.) Decided $20 is enough for another few months before the great HD leap, and reverted to 3.5b with phone-home disabled (thanks to InstantCake).

I'll be sticking with 3.5b for now, I guess, and I hope others have better luck. If there's obvious dain-bramage in the above steps, please let me know.

Dan

[tivoupgrade]

I shelled out for InstantCake and I reverted to 3.5b. So far, so good, and I'm assuming that all I lose would be PPV via TiVo itself.



I tried this with the 4.04 LBA free disk, like I said earlier, and it failed. Unless the kernel also reverts when one does "erase and reformat" or whatever-that-menu-option-is, I think I did everything properly. Let me give my precise steps:

1.) Discovered 3.5c had been installed, thanks to power-flickers that caused reboots.

2.) Verified that my saved programs were shot to hell.

3.) Yanked drive, did copykern.

4.) Reinstalled drive, immediately selected "erase and reformat".

5.) Recorded programs still caused reboots.

6.) Decided $20 is enough for another few months before the great HD leap, and reverted to 3.5b with phone-home disabled (thanks to InstantCake).

I'll be sticking with 3.5b for now, I guess, and I hope others have better luck. If there's obvious dain-bramage in the above steps, please let me know.

Dan

I think the reason it didn't work for you is because you did not kill your initrd, you only replaced your kernel.

Doint the C&D everything was not necessary, and it shouldn't/wouldn't have made a difference (other than erasing your stuff).

[danmcd]

I think the reason it didn't work for you is because you did not kill your initrd, you only replaced your kernel.

Hmmm, now I am confused. The first time I did this (3.1 --> 3.5) I remember having to scrounge around and find kill_initrd. The second time (3.5 --> 3.5b) I remember just doing copykern, and that's it. I didn't take notes on the second time I did it, but maybe I powered off right after the service upgrade, THEN did copykern. Is it possible the D* upgrade configures the moral equivalent of running kill_initrd before the reboot into the new version? (Either that or I was flying on auto-pilot and d-loaded or floppied kill_initrd.)

Well, at least I know what to do again. BTW, InstantCake worked well, but its advanced
mode gave me some problems (possibly just extra noise that frightened me into trying again) before I recabled the PC I borrowed to InstantCake's preferred setup.

Thanks!
Dan

[tivoupgrade]

Not sure about your initrd situation as sometimes a new initrd is installed with a new version of the code and sometimes it isn't. Perhaps the last time, it wasn't necessary to kill it but this time it was. In either case, the safest and best way is to assume that you need to do it and perform a killinitrd before replacing the kernel (or to use nic_install which automatically will test and kill it, if necessary).

Of course, if its never been done before - ie, you have 3.5c on a unit which has NEVER been upgraded, you will need to tivoflash the drive (any newcomers should absolutely read the first post of this thread!)

As for "noise" - no idea what that is (your CD-ROM, perhaps?). Advanced mode just gives you the ability to define the device names instead of going with the default (CD-ROM - primary slave, Target Drive - secondary masteR)...

In any case, glad you got it working, thanks for your support in picking up IC. Will update this thread when IC versions are updated.

[lew]

Do we know what changes with 3.5c? Is there a message that tells us? I'm surprised the previous software version didn't take care of DST.

[vancod]

My S1 DTiVo (GXEBOTD) just got 3.5c - does anyone know what the offset for the CSO "no scramble" is yet??

TIA
Don

EDIT:
Just found this, will test tonight:
<sigh> my post count prohibits me from adding the link, but see the threat titled " 3.5c-01-1-031" on DD

[rpongett]

Do we know what changes with 3.5c? Is there a message that tells us? I'm surprised the previous software version didn't take care of DST.Same question. That would be surprising since the last upgrade was supposed to take care of those issues.

Also, I decided to stick it out at 3.5b, at least for now. I'll have to risk a "managed" upgrade later if there is some major fix I simply have to have in it, which I doubt. Changed the bootpage parameters and rc.sysinit set variables accordingly.

But my system keeps rebooting at 2:30am. It's not my purposeful safereboot through cron (those are at 4:00am every other day).

Is that my system trying to install 3.5c every night?

[Blackfoot]

Same question. That would be surprising since the last upgrade was supposed to take care of those issues.

Also, I decided to stick it out at 3.5b, at least for now. I'll have to risk a "managed" upgrade later if there is some major fix I simply have to have in it, which I doubt. Changed the bootpage parameters and rc.sysinit set variables accordingly.

But my system keeps rebooting at 2:30am. It's not my purposeful safereboot through cron (those are at 4:00am every other day).

Is that my system trying to install 3.5c every night?
Yes. Your system thinks it needs to be running 3.5c so it reboots every night at 2:30 to kick off the upgrade. I know there was a way to trick the HR10-250's into thinking the system had the latest version, but I don't recall it, nor if it would work on a S1 unit. I'm in the same boat. I've modified my rc.sysinit file, but not the bootpage.

[rpongett]

Yes. Your system thinks it needs to be running 3.5c so it reboots every night at 2:30 to kick off the upgrade. I know there was a way to trick the HR10-250's into thinking the system had the latest version, but I don't recall it, nor if it would work on a S1 unit. I'm in the same boat. I've modified my rc.sysinit file, but not the bootpage.
Lovely.

I still don't know if there are any benefits of 3.5c, and I'm not going to through the upgrade hassle unless it's something big.

[ronsch]

I did a controlled upgrade last night and it took less than four hours. That included a dinner break :) and a lack of preparation on my part as I couldn't find my Jenkins boot cd when it came time to use it. Had to reconfigure my PC and boot up Windows again to burn a new copy. That time also included a complete backup of the software once I was done.

There is no database conversion in this upgrade and the 3.5b LBA48 kernel seems to be working fine. There are no differences from 3.5b that I've been able to see so far.

[rslatkin]

My S1 DTiVo (GXEBOTD) just got 3.5c - does anyone know what the offset for the CSO "no scramble" is yet??

TIA
Don

EDIT:
Just found this, will test tonight:
<sigh> my post count prohibits me from adding the link, but see the threat titled " 3.5c-01-1-031" on DD

It's also in the DD General Tivo Development thread called "tivoapp patches", along with the patches for 30 second skip and backdoors.

[lew]

Lovely.

I still don't know if there are any benefits of 3.5c, and I'm not going to through the upgrade hassle unless it's something big.

I can't imagine DTV/Tivo is going to the trouble of upgrading software on the series 1 units, that haven't been sold for years, unless it does something.

Earlier this year DTV changed the guide data format and the tivos couldn't handle it
http://www.tivocommunity.com/tivo-vb/showthread.php?t=336122

I wonder if the old units are being upgraded so they can work with some changes DTV is making?

I may do a controlled upgrade, the new TV season will be starting soon and I don't want to find out the upgrade was necessary.

[Dojimaster]

All of my DSR6000R got hit with the 3.5c update :(

I have pulled the drives and tried to use copykern and I get this note:

tpip: unknown boot block signature: 0x34b98ad1




Any ideas or suggestions? Never had this occur before!

[tivoupgrade]

All of my DSR6000R got hit with the 3.5c update :(

I have pulled the drives and tried to use copykern and I get this note:

tpip: unknown boot block signature: 0x34b98ad1


Any ideas or suggestions? Never had this occur before!

It doesn't sound like you are doing it correctly; works fine for me. Are you following the instructions documented in the first post of this thread?

[Dojimaster]

It doesn't sound like you are doing it correctly; works fine for me. Are you following the instructions documented in the first post of this thread?

With the lba48 disk in, I cannot seem to kill initrd

Any suggestions? I ran the nic_install disk from silicone dust (to kill initrd), but I cannot load the lba48 disk without rebooting which I assume defeats the purpose

[Dojimaster]

Would the Universal Boot CD be more helpful than the lba48 $5 cd?

[tivoupgrade]

Would the Universal Boot CD be more helpful than the lba48 $5 cd?

Only in that you wouldn't need to go find the SiliconDust CD which you already have, anyway.

Here is all you need to do:

1) boot the silicondust CD and run nic_config; let it find the initrd and kill it..
2) reboot with the FREE LBA48 CD and run CopyKern, choose the 3.1.0+ kernel

That's it; you don't need to spend a dime.

:-)

[Dojimaster]

Only in that you wouldn't need to go find the SiliconDust CD which you already have, anyway.

Here is all you need to do:

1) boot the silicondust CD and run nic_config; let it find the initrd and kill it..
2) reboot with the FREE LBA48 CD and run CopyKern, choose the 3.1.0+ kernel

That's it; you don't need to spend a dime.

:-)

Thanks - i will try again, but I have tried this and I am getting the same boot block signature warning, and also notification right after the command from copykern is run that says

No such file or directory

I really appreciate your help!

[Dojimaster]

Only in that you wouldn't need to go find the SiliconDust CD which you already have, anyway.

Here is all you need to do:

1) boot the silicondust CD and run nic_config; let it find the initrd and kill it..
2) reboot with the FREE LBA48 CD and run CopyKern, choose the 3.1.0+ kernel

That's it; you don't need to spend a dime.

:-)

Sadly still not sucessful. What i find odd is when the software went to 3.5b, I didn't have these problems.

Is it normal to get the "boot block signature" warning, and "No such file or directory" warning?

Am I expecting these not to happen when they always do?

Is there another way to tell if the kernel has been updated?

Thanks again.

[tivoupgrade]

Sadly still not sucessful. What i find odd is when the software went to 3.5b, I didn't have these problems.

Well, if its not working then there may be other issues that are affecting things. Perhaps you corrupted the drive in one of your previous attempts. Best to restore the drive and try again, so that you are starting from a known place.

[Dojimaster]

I'll try that.

I pulled the drives out of a second DSR6000R and am having the same exact issues, on the first attempt.

I built all these drives with Instant Cake. Have you guys had any trouble since 3.5c or is this unique?

[tivoupgrade]

I'll try that.

I pulled the drives out of a second DSR6000R and am having the same exact issues, on the first attempt.

I built all these drives with Instant Cake. Have you guys had any trouble since 3.5c or is this unique?

We've not had any trouble at all; none of the units in our lab (created with InstantCake) moved from 3.5b to 3.5c unless the upgrade was "forced"

All of the updated versions of InstantCake 3.5c (just released) were made using images modified in the same way I've recommended here, ie. once the images were updated from 3.5b to 3.5c, they were backed up (for safe-keeping) then nic_config was run, then CopyKern, and then embedded into InstantCake.

Before anyone asks, the details are here (http://www.dvrupgrade.com/dvrupgrade-support-center/index.php?x=&mod_id=2&id=115). .

[Dojimaster]

We've not had any trouble at all; none of the units in our lab (created with InstantCake) moved from 3.5b to 3.5c unless the upgrade was "forced"

All of the updated versions of InstantCake 3.5c (just released) were made using images modified in the same way I've recommended here, ie. once the images were updated from 3.5b to 3.5c, they were backed up (for safe-keeping) then nic_config was run, then CopyKern, and then embedded into InstantCake.

Before anyone asks, the details are here (http://www.dvrupgrade.com/dvrupgrade-support-center/index.php?x=&mod_id=2&id=115). .

Perhaps thats my issue. I changed the dialing prefix to ,#401 so I could dial in over the internet, hence my susceptibility to getting updated.

I am downloading the InstantCake 3.5c, and if I don't change the prefix, how does it get the new data and program listings?

Thanks for all your help.

[tivoupgrade]

Perhaps thats my issue. I changed the dialing prefix to ,#401 so I could dial in over the internet, hence my susceptibility to getting updated.

I am downloading the InstantCake 3.5c, and if I don't change the prefix, how does it get the new data and program listings?

Thanks for all your help.

Over the satellite.

Before you put the program into use, please read the release notes (the link I provided in my previous post) very carefully. EVERYTHING we've discussed here about IC is covered there.

Now, with all that said, I'd like to steer the topic back towards the general migration within the context of 3.5x; I don't want this to become a product specific thread (we have those on our own forums). Thx!

[tadgh]

Ok, my hacked up S1 DTivo (DSR6000) went toes up (almost there forever..) with over 100 hours of shows and I just got caller ID and TWP working! --Thanks to IC for making all that easy.

I can't rule out a bad drive, but the timing with the 3.5c update is too coincidental. I have an unlocked Icaked spare drive in there now and am afraid to go any further for fear of it getting nuked by the update. I have a spare because 3.5b bent up my dual drive setup. I split up the team after reading that dual drives are less reliable and didn't need the space as much as I needed to have a spare. Turns out I made a good choice there.

My question is this: How do I tell if it was 3.5c or a bad drive that killed it? I mean is there a chance, I can restore this drive. I had a lot of good stuff on it.

[vancod]

How do I tell if it was 3.5c or a bad drive that killed it? I mean is there a chance, I can restore this drive. I had a lot of good stuff on it.1) Use the drive MFGR bootable diagnostics to check the drive (do NOT attach a TiVo drive and boot into Windoze!)
2) boot with any of several available TiVo boot disks and look at the drive manually - even a simple "pdisk -l" (that's "ell") will at least tell you if the drive is partitioned as a TiVo device (meaning it can help diag the MBR / partitioning)

There are tools to extract video while a TiVo drive is on a PC - see appropriate threads (at least I know there are on the DD forums) You can inject them back into the TiVo or save them off in a couple of formats...

Good luck -
Don
(PS - reliability with dual drives? been running 2 w/a cache card in a GXEBOTD longer than I care to remember....at least 4 years)

[Francesco]

Well, the upgrade appears to have toasted two of my DTiVos' drives.

So I've restored a 3.5 image to them, but without expanding or hacking other than getting the CacheCard drivers running -- in anticipation of getting 3.5c again. They've been up and in the stream for 24 hours now, but no sign of 3.5c. Any idea how long before I can get it? I'd like to finish up and put the lids back on, set up SPs, etc.

[vancod]

Well, the upgrade appears to have toasted two of my DTiVos' drives.

So I've restored a 3.5 image to them, but without expanding or hacking other than getting the CacheCard drivers running -- in anticipation of getting 3.5c again. They've been up and in the stream for 24 hours now, but no sign of 3.5c. Any idea how long before I can get it? I'd like to finish up and put the lids back on, set up SPs, etc.I would imagine that the DTV database is highly confused because you're now running a lesser version than they think you are. You might try forcing a daily call and reboot repeatedly, but I'm not clear if the software updates are via Sat or "phone call".

The upgrade does not nuke /var/hack (at least it did not for me) so I'd say hack away and just make sure you copy any init changes to a text file so you can echo them back in place later.... Not sure - but you might even be able to script the NIC install drivers to re-install on reboot so when you do get 3.5c and reboot you don't have to yank the drive again. Might shoot a note over to the SiliconDust forums on that one

[lew]

Does anyone know what changes are implemented with software version 3.5c?

[vancod]

Does anyone know what changes are implemented with software version 3.5c?Certainly none that are readily apparent with use. Menus still slow, some channel recordings still jittery as a heck (e.g. SPIKE TV), etc. My TWP response is much slower. And, bonus, my unit used to idle at 43 degrees, now it idles at 46 (and it's a cool week here in Hooterville). There's a thread over on DD on the subject, but IIRC no one has really responded with much of relevance to this point....

[bmatson]

In response to a problem in getting the 3.5 update to happen, it was said ...I would imagine that the DTV database is highly confused because you're now running a lesser version than they think you are. You might try forcing a daily call and reboot repeatedly...
This concerns me because my series 1 Tivo died (it had LBA48 installed) at an earlier update MANY months ago, and I am now preparing to revive it. I plan to go back to my original 2.x version and take the upgrade to 3.5c prior to expanding to a large drive and installing the cachecard drivers.

Am I likely to have trouble getting the update because DirecTV thinks I have a newer version than I (will) have?

An unrelated (but related)(???) question - can I leave the cachecard in, but not install the driver (yet - until after taking the upgrade)?

Thanks for the clues.

[vancod]

This concerns me because my series 1 Tivo died (it had LBA48 installed) at an earlier update MANY months ago, and I am now preparing to revive it. I plan to go back to my original 2.x version and take the upgrade to 3.5c prior to expanding to a large drive and installing the cachecard drivers. Am I likely to have trouble getting the update because DirecTV thinks I have a newer version than I (will) have?I can't speak from direct experience since I've never done it, but I know that as a "courtesy" to TiVo folks have tried to NOT back-rev. Not sure how folks are interacting with DTV. I've seen threads where folks talk about running versions "cross hardware" without issue. I'd suggest a search here and over on DD as you're likely to find an answer, failing that consider starting a thread on the subject....An unrelated (but related)(???) question - can I leave the cachecard in, but not install the driver (yet - until after taking the upgrade)?Yes - the cachecard does nothing until the driver is present. However, keep in mind that the cachecard driver IS the NIC driver, so until it goes in you will only have access to the system via serial or by inserting the HD in your peecee. Rather than waiting for the upgrade and doing some kind of 2-step route, perhaps you can search and find someone with the 3.5c slices and just upgrade yourself, get your LBA kernel and cachecard in, and be done with it

I"m assuming as part of this (learning) process that you'll now make a backup of your TiVo once the upgrades are all back in place ;) (if you skip the video content it will easily fit in a single CD)

[clock022]

the garet post!

[tivoupgrade]

In response to a problem in getting the 3.5 update to happen, it was said ...
This concerns me because my series 1 Tivo died (it had LBA48 installed) at an earlier update MANY months ago, and I am now preparing to revive it. I plan to go back to my original 2.x version and take the upgrade to 3.5c prior to expanding to a large drive and installing the cachecard drivers.

Am I likely to have trouble getting the update because DirecTV thinks I have a newer version than I (will) have?

An unrelated (but related)(???) question - can I leave the cachecard in, but not install the driver (yet - until after taking the upgrade)?

Thanks for the clues.

Usually, if you "backrev" a unit, it will just download the latest version of the software. 2.5.2 is VERY VERY old, though and I don't know what what will happen if you dial in (or connect over the network) with something that old. It shouldn't cause any problems, though - worst case is that it won't update.

And there is no problem leaving the CacheCard in there in the interim; it just won't do anything...

[bmatson]

Thanks, Tivoupgrade and Vancod for the responses. I did find an newer backup I had made of version 3.0.1c2, so I guess I'm not backrev'ed that far. I'm now waiting for the update.

One final question, if I may. When I get the update, I'm going to do the LBA48 and cachecard modifications. I would really like to avoid any more updates in the future. I see references to a method of blocking updates, but no specifics. Can anyone point me to a clear explaination somewhere? Also, is there any possible serious downside to rejecting updates? I'm very happy with the way the software works as it is and don't need any new features. I never buy PPV shows, so maybe I don't need the cachecard plugged into the network; is that the case? Is there a better way to avoid updates?

Thanks

bmatson

[vaiolation]

I have been searching the forum and I have not had any luck finding a solution. Please forgive me if this is an inappropriate thread, but...

I am trying to install Steve Jenkins' hack to convert my series 1 Tivo (Sony SVR-2000) to internet capability (fried modem). I was having success until this step:

Before your TiVo can run your rc.sysinit.author file, however, you need to change the permissions of the file so that it is executable. Do this by typing:

chmod 755 rc.sysinit.author [ENTER]

After I enter the above command I get the following message:

chmod: not found

Any ideas or solutions would be appreciated. Thanks.

[Mike Mack]

I had instantcaked, with 3.5b, my SAT-T60 with a 300Gb drive back in July. Everything was working well until the past few weeks I noticed that some shows were pausing in the middle and then the unit would reboot. After checking here I see that 3.5c has been pushed to our units and I have confirmed that it is on my unit as well.
My question is - when I did the 3.5b instantcake upgrade I chose the default of no phone call and I assume that no software update was the default as well. If this is the case then how did my unit get the upgrade?
Please let me know if this upgrade is something that came in over the satellite or otherwise so that I can hold off rebuilding the drive with 3.5b. I would hate to rebuild and have the upgrade hit again.
I also think that it has been too long now for me to do a killinitrd and copykern so rebuilding is probably my only option.

Thanks

[Carlton Bale]

Does anyone have a copy of the 3.5c image for the Philips DSR6000 that they give to me? Please let me know. Thanks!

[master cylinder]

I have had difficulty applying hacks such as noscramble with the IC 3.5c on a T60.

Everyone that I have read about doing the hacks successfully have had the native 3.5c as it upgraded thier tivo's, none have IC'd the drives.

Question: whats different? Has anyone successfully IC'd thier tivo, and got noscramble to work? I can handle everything else if I can get the tivo to not scramble the recordings.

And since I have IC'd the drive I cant get the natural 3.5c from d*tv. So, I feel like I'm in the hole and cant climb out.

ANY suggestions would be appreciated!!!

[tivoupgrade]

I have had difficulty applying hacks such as noscramble with the IC 3.5c on a T60.

Everyone that I have read about doing the hacks successfully have had the native 3.5c as it upgraded thier tivo's, none have IC'd the drives.

Question: whats different? Has anyone successfully IC'd thier tivo, and got noscramble to work? I can handle everything else if I can get the tivo to not scramble the recordings.

And since I have IC'd the drive I cant get the natural 3.5c from d*tv. So, I feel like I'm in the hole and cant climb out.

ANY suggestions would be appreciated!!!

There is nothing different about 'tivoapp' on a drive created with InstantCake and nothing that would prevent you from being able to apply any of the hacks other people are applying to drives created by other methods.

If you are not able to get whatever hack working that you are attempting, then chances are you are just not applying it properly and its nothing more than that.

I can't tell you specifically what you need to do, however it is a simple patch to tivoapp that you are looking for and that information can be found on the other forum.

[GCG]

Has anyone had any trouble as a result of getting 3.5d?

[blips]

Has anyone had any trouble as a result of getting 3.5d?

I have not had any trouble with it. I applied all the same same hacks/offsets to 3.5d as I did to 3.5c.

[GCG]

I have not had any trouble with it. I applied all the same same hacks/offsets to 3.5d as I did to 3.5c.

Is it necessary to run TiVoflash again after the 3.5d update? I had a working CacheCard under 3.5c that stopped working after getting 3.5d. I reinstalled its drivers, but now it doesn't link to my switch (details here (http://www.tivocommunity.com/tivo-vb/showthread.php?t=399813) ) Any ideas? :confused:

[blips]

Is it necessary to run TiVoflash again after the 3.5d update? I had a working CacheCard under 3.5c that stopped working after getting 3.5d. I reinstalled its drivers, but now it doesn't link to my switch (details here (http://www.tivocommunity.com/tivo-vb/showthread.php?t=399813) ) Any ideas? :confused:

You should not have to run Tivo Flash again. I would try re-installing the drivers again. What is your network set up? Do you have the Tivo running DHCP or do you have a static IP for your Tivo?

[tivoupgrade]

You should not have to run Tivo Flash again. I would try re-installing the drivers again. What is your network set up? Do you have the Tivo running DHCP or do you have a static IP for your Tivo?

You definitely won't need to run tivoflash again. However, you WILL need to disable the initrd. Make sure you install the drivers and disable the initrd BEFORE replacing the kernel with CopyKern on the LBA48 boot CD... (if you are using a drive bigger than 137GB...)

[tivoupgrade]

Hello,

We've verified (finally) that the 3.1.0+ kernel provided on the Free LBA48 CD (http://www.tivocommunity.com/tivo-vb/showthread.php?p=2266039#post2266039) works fine with the recently released 3.5d version of the software for Series1 DirecTiVo units (Sony, Philips and Hughes models). Furthermore, we've updated InstantCake for these models (basic and TiVoWebPlus versions), as well.

Lou