Sprint TV for Mogul!!! 11-28-07 - NO LONGER WORKING

[maxxed]

it worked for me but i recently have been getting channel currently not available. I installed it onto the main memory. ran it once. copied the cache folder over it and wala. i also keep a copy of the cache folder in my device. so whenever i get an error or something i just copy it over and replace it.

[rvashi]

Originally Posted by JHComputerGuy

Earlier, I posted that I got my Sprint TV to work and I gave instructions on how I got it to work. A day later, it did not work anymore. A day after that it did. It is working off an on.

Okay...well, it seems that you failed to mention after your post with instructions that it actually "did not" work for you a day later. If you would have mentioned that then I would not have bothered but assuming that you had it working properly to-date, I asked if it had somethng to do with the ROM version. And it could definately have something to do with the ROM that you are using (otherwise, why did you instruct on updating the ROM to 2.17 in your previous instruction post). If one is using a Mogul-Touch hybrid ROM, there are some aspect of the Touch (Vogue) ROM such as drivers and XIP that are being used in this ROM which could possibly make Sprint TV think of the device as a Mogul. I also understand that this is being corrected at Sprint server end but you can fool the server into thinking the Client is a Touch (Vogue) instead of a Mogul by ROM adjustments...it might not have to all that involved such as changing the ESN to that of a Touch (Vogue).

I hope that clears up why I was asking the question that I was. I'm a senior member so for the most part, I don't ask repetative questions unless that question has not been answered before...and the ROM version question has not been answered before.

[JHComputerGuy]

Originally Posted by rvashi

Okay...well, it seems that you failed to mention after your post with instructions that it actually "did not" work for you a day later. If you would have mentioned that then I would not have bothered but assuming that you had it working properly to-date, I asked if it had somethng to do with the ROM version. And it could definately have something to do with the ROM that you are using (otherwise, why did you instruct on updating the ROM to 2.17 in your previous instruction post). If one is using a Mogul-Touch hybrid ROM, there are some aspect of the Touch (Vogue) ROM such as drivers and XIP that are being used in this ROM which could possibly make Sprint TV think of the device as a Mogul. I also understand that this is being corrected at Sprint server end but you can fool the server into thinking the Client is a Touch (Vogue) instead of a Mogul by ROM adjustments...it might not have to all that involved such as changing the ESN to that of a Touch (Vogue).

I hope that clears up why I was asking the question that I was. I'm a senior member so for the most part, I don't ask repetative questions unless that question has not been answered before...and the ROM version question has not been answered before.

Rvashi, this reply was not directed at you. Sorry if it seemed that way. I am using rom 2.17, as i mentioned in my instruction post. Also, in my post, i was not telling or recommending that anyone install 2.17. i was just listing what i did to get it to work.

My last post was mainly for everyone that has read through 350 posts and are still asking about the 7000 error which has been discussed many times on this thread.

Again, sorry about that rvashi.

[woody88]

I got the channel line up coming up ok. However, once I get to browsing and click on any content, my screen often turns off when I click on the content, and when I touch the screen again, I am where I was, at the content selection screen. Am I doing something wrong? I had uninstalled sprint TV, reinstalled and re-rared the cache folder back into sprint tv, and it is still not working. Does anyone have any suggestions?

[benoldcrap]

I just noticed this and hadn't seen it mentioned yet. When you go to the help screen in the options menu and scroll all the way down, there are 2 IDs.

Mine are:

Release ID: winmo-st1.5-01005

Customer ID: 0E2B9-39850-B95AC

The Customer ID will not give me my ESN in any in other sequence, so I don't know what is creating that Customer ID, or if it's any different then anybody else's since this was a hacked app. I don't think the program is broadcasting our ESN's though.

Can anyone else confirm different ID numbers?

Does anyone think they could hack the app so that it only broadcasted an ID of our choosing?

...just some food for thought.

[pdx77]

It's a different ID for everyone, that info is also saved in your registry as well. In fact if you do a hard reset, even reflash your phone and reinstall, you still get the same ID.

[Primenall]

Originally Posted by pdx77

It's a different ID for everyone, that info is also saved in your registry as well. In fact if you do a hard reset, even reflash your phone and reinstall, you still get the same ID.

So is there a way to put a legit Touch id into the registry and have it work?

[benoldcrap]

You may be on to something, Primenall.

HKLM\Software\SprintTV\CID is your Customer ID. I'm guessing the UID key would also have to be changed to that of a Touch, but it could work.

Can anyone with a Touch share their reg values for those keys?

I haven't tested this, but I would also guess that those key would automatically change when you start or exit the program, so someone more technically inclined then me might have to write a script to have those change over to a Touch's IDs everytime it starts up.
...just guessing on that though.

[pdx77]

Originally Posted by Primenall

So is there a way to put a legit Touch id into the registry and have it work?

Simply editing the registry with the id of a touch won't work, I've tried that, and still got the same results.

[canospinach]

Originally Posted by pdx77

Simply editing the registry with the id of a touch won't work, I've tried that, and still got the same results.

The real key here would be to emulate (think clone) a touch esn.

The system has to believe the handset is a touch from the moment you get network.

The authentication is a combination of software (application) and hardware (ESN, MSID) in order to work.

ESN/IMEIs are like MAC addresses with network adaptors, each one is individual and keyed to make/model of the handset. The minute the system gets an authentication request from your handset for network access it registers your esn as well as other subscriber info.

This is what i have tried to more simply explain all along, that modifying the STV app and your handset OS settings is only half the task. Its really not more complicated than cloning a touch esn for this situation. Its a bit of a futile task unless you address the hardware/network aspect.

Cloning handsets is illegal with criminal penalties if your caught using a "cloned" handset on a network. Sprint uses an "Approved ESN/IMEI List" which means you would need to duplicate an existing, pre-approved ESN. The duplicate ESN will get picked up by the network.

------------------
FYI for those thinking about how this impacts the Open Network/Handset Alliance, it really does not. The alliance is more about OpenSource OS for the handsets themselves. The Network portion would still need to have a handset screened by the system in order to function. If it were a "home built" device it would use an approved radio kit which would come with the appropriate "usable" ESN. There are no plans to allow "home built" radios themselves to access the network. Each network has an enormous budget directed to testing handsets for network usablity prior to launch (i know we all wonder how some still make it) with manufacturers often having to make hardware mods to satisfy the carrier (good example is the 6700 antenna "nub" they added it because they thought it would improve CDMA PCS reception).