Separate names with a comma.
Discussion in 'TiVo Underground' started by wmcbrine, Jan 18, 2011.
kmttg has something now which categorizes by reason all shows that won't record.
Also note that there have been some forum posts about the "Fall" update for Series 4 units geting some new HDUI screens including To Do List, so perhaps TiVo took the opportunity to do it right and provide proper filters so you can only see conflicts you really care about. (Of course just like the improved Guide it means you would actually have to use HDUI to get the improvements which means you have to live with HDUI sluggishness).
I have already downloaded it. It does not start when I open the jar file but I assume it will work; I have not tried to investigate. I certainly should have the association specified but that is the first thing to investigate. This is off-topic for this very useful thread so I don't want to dwell on the off-topic discussion.
When Java 7 was installed it did not remove Java 6. When I execute kmttg using Java 7 javaw explicitly nothing happens. When I execute the exact some thing using Java 6 it works. So I do not know if it is a problem with the way Java is installed, in which case it is not your problem, or if it is something you would be concerned about. If you want me to post more information, just let me know what and where.
I haven't tried Java 7 so could well be issues. I have to keep kmttg Java 5 compatible since some Mac OS's are way behind on Java front.
FYI, I figured out how to get "Recently Deleted" list using "recordingSearch" operation with "state:[deleted]" field. Recordings returned can then be undeleted using "recordingUpdate" operation with "state:complete" field. So next kmttg release will have an additional RPC "Deleted" tab with ability to list and recover deleted shows.
FYI, RPC still works fine as is with the 20.2.2 update being pushed out starting today.
i.e. No changes needed to authentication as was the case last time.
So whatever changes broke it for Virgin and cable company versions do not apply to 20.2.2.
Based on the Android schema.conf file I wrote a script to parse the file and print out a summary of all possible Mind schema v9 operations in a more human readable form. Note that the vast majority of operations are not accessible via RPC, and I've marked each and every operation with a (NO) or (YES) accordingly. In the process of going through that exercise there were a few interesting commands that came up I didn't know worked before, such as:
phoneHomeRequest - initiate a network connection (phone home)
whatsOnSearch - info about what is currently being watched. Only 3 states I've seen so far: "idle", "recording", "liveCache". idle state is if you are currently in a GUI screen or running HME or Flash app, recording if watching a recording, liveCache if viewing live TV. Channel information is given when relevant.
Above 2 I'm making use of in next kmttg release.
Others that are functional via RPC I haven't explored yet that look somewhat interesting:
I uploaded my operation summary file to here in case someone may find it useful:
Thanks... fascinating stuff.
As you know, the iPad interface isn't the only place where these commands are used -- specifically, the pyTivo "push" system communicates with the TiVo "mind" server using "bodyOfferModify", and a few other commands. Now I finally have a formal spec for bodyOfferModify... and I can see that we're already using all the useful fields. But, I can also see that there are other commands that might let us specify more metadata, if we can figure out how to use them.
OK, so Virgin Media in the UK has *finally* released a version of the iPad app that can talk to their version of the TiVo.
Has anyone got a way of capturing the network traffic between the iPad and the TiVo that works (e.g. with the latest US app)? I've got a jailbroken iPad, if that helps.
I've been trying a few different ways to capture the traffic, but this is all new to me, really (I'm a .Net client developer).
Android app is much easier to look at for me if there is an Android version that works with Virgin (I would need the apk file).
Would you be willing to crack the application with your iPad. Plain ipa file is encrypted and there is a small change that the cert password could be found from the binary after it has been decrypted. Process is easy but I don't have any apple devices. Essentially decryption needs to be done on a device which downloaded app from the market.
Yes, I could give that a go if you can point me at a howto.
I've already had a look and found a new cert file, but I checked and the password isn't the same as for the old/US one.
@moyekj : Sorry, no Android app, yet. I would also find that much easier to deal with.
EDIT: Done. I've sent you a link to decrypted binary.
"hackulo.us/wiki/IOS_Cracking" (sorry, i need 5 posts to post links) is pretty interesting article and contains links to methods how apps are cracked. It's pretty automated(Clutch and poedCrackMod) these days meaning you don't need to manually play with memory dumps. To cut the story short, vanilla ios will not execute decrypted apps and that's partly the whole point of jailbreaking iDevices.
Yes, I also checked those new certs. There seem to be one cert per tivo application. There's a separate US apps for phone and tablet for android and both of those have different cert(older android tivo app actually had both of those certs in it). I also checked existing cert from US tivo IOS app and that cert is not a same found from android apps.
Every client cert in tivo's basically maps to a partner id. I believe tivo's firmware contains a set of access rules what these partners are allowed to do via mind protocol(Essentially this means that Virgin itself owns a cert which allows admin access to a device). It was pretty natural step for Virgin to change or disable those partner id's which are used in US.
@swythan Can't yet send pm's, but I'll give it a spin.
It's pretty clear that the passphrase is not clear text in ios binary as it's in android app.
Right... going into a world of arm asm language.
Hah, think I got it. Do people generally post hacking methods to this forum?
FYI, you can use this same protocol to talk to middlemind.tivo.com (port 443) instead of a local series 4 TiVo. For bodyAuthenticate you use mmaCredential with your tivo.com username & password instead of the makCredential used for local TiVo authentication, but from that point on everything else is the same.
This opens up some of the functionality provided by this interface to earlier TiVo models such as series 3. I have yet to explore much exactly what does and does not work when using that host. Note that this is the host that is used in "away" mode by the iOS/Android apps. Depending on how much functionality is available I may add RPC remote support (with likely reduced functionality) for earlier TiVo models in next kmttg update.
Earlier models don't use the same connection to the mind server as the Premiere models. They use the old XMPP/Jabber client/server connection which only supports pushing video downloads, season pass manager updates and not much else. That's why it's not possible to view the Now Playing list for Series 3 models or update the To Do List or Season Passes in real time (the older polling online scheduling method is used).