Disco'd after Authority Block firmware installed
-
- Junior Member
- Posts: 381
- Joined: Fri Oct 28, 2005 8:43 am
The connect and disconnect function changes two values in the DCT's NVRAM it is not nessesary to use a specific version of NVRAM to accomplish the control of this state. The following paired values control the connection state in ver 7.93 of the application.
00200F2A 00 = Disconnected
0020B13E F0 = Disconnected
00200F2A 01 = Connected
0020B13E F1 = Connected
The possible reasons for your situation are as follows.
1 - The flash was not accually performed with the ABAC firmware.
2 - usbbdm missed something.
3 - There is more than one way for the CC to control the state.
4 - To remain connected the application requires some piece of information that is blocked.
I would not replace the NVRAM.
Just verify that you did flash it with the ABAC firmware. Remmember on PH7 and up do not start the programming at 400000 always start at 406000.
Then reconnect it.
00200F2A 00 = Disconnected
0020B13E F0 = Disconnected
00200F2A 01 = Connected
0020B13E F1 = Connected
The possible reasons for your situation are as follows.
1 - The flash was not accually performed with the ABAC firmware.
2 - usbbdm missed something.
3 - There is more than one way for the CC to control the state.
4 - To remain connected the application requires some piece of information that is blocked.
I would not replace the NVRAM.
Just verify that you did flash it with the ABAC firmware. Remmember on PH7 and up do not start the programming at 400000 always start at 406000.
Then reconnect it.
-
- Junior Member
- Posts: 21
- Joined: Wed Jul 27, 2005 9:16 pm
- Location: NewYork&Chicago
- Contact:
-
- Junior Member
- Posts: 156
- Joined: Wed Oct 12, 2005 7:03 pm
OK, I left the NVRam alone after my last disconect, and just did a
program 406000 aa000
With the firmware. The box worked for five minutes and then shut it's self off. I did it three times and the same results. What is the proper steps to use the firmwear? What I did first was follow the "0" guide. When that didn't work I used a working NVram & did a program 400000 200000. Then I tryed just the program 406000 aa000.
Am I missing something? I thought I was doing everything right, but the bix keeps getting disconected. Is it possible that the CC has a timer set for communication to the head end?
program 406000 aa000
With the firmware. The box worked for five minutes and then shut it's self off. I did it three times and the same results. What is the proper steps to use the firmwear? What I did first was follow the "0" guide. When that didn't work I used a working NVram & did a program 400000 200000. Then I tryed just the program 406000 aa000.
Am I missing something? I thought I was doing everything right, but the bix keeps getting disconected. Is it possible that the CC has a timer set for communication to the head end?
-
- Junior Member
- Posts: 156
- Joined: Wed Oct 12, 2005 7:03 pm
-
- Junior Member
- Posts: 381
- Joined: Fri Oct 28, 2005 8:43 am
GTF696,
I have checked both the nvram and the code. The nvram is in the disconnected state. The addresses are slightly different from what I have but the data structure seems to be the same.
The firmware is not the ABAC version and seems to have additional code that I have not seen before. This would give in to the following possibillities.
1) The CC is targeting certain UID's with a disfunctional/modified or new firmware.
2) The firmware file your using is corrupt/incorrect.
A possible solution quite is simple. Spoof the UID with a known good authed UID or other UID and lets see what happens. I can program it for you if you need help with that. It would be best if the spoofed UID was real and authed but it does not have to be. You can PM me one if you can one otherwise I can create one for you.
I have checked both the nvram and the code. The nvram is in the disconnected state. The addresses are slightly different from what I have but the data structure seems to be the same.
The firmware is not the ABAC version and seems to have additional code that I have not seen before. This would give in to the following possibillities.
1) The CC is targeting certain UID's with a disfunctional/modified or new firmware.
2) The firmware file your using is corrupt/incorrect.
A possible solution quite is simple. Spoof the UID with a known good authed UID or other UID and lets see what happens. I can program it for you if you need help with that. It would be best if the spoofed UID was real and authed but it does not have to be. You can PM me one if you can one otherwise I can create one for you.
Who is online
Users browsing this forum: No registered users and 9 guests