Haxorware Forums
5101 to 5101E - Printable Version

+- Haxorware Forums (http://www.haxorware.com/forums)
+-- Forum: General (http://www.haxorware.com/forums/forumdisplay.php?fid=6)
+--- Forum: Modems (http://www.haxorware.com/forums/forumdisplay.php?fid=7)
+--- Thread: 5101 to 5101E (/showthread.php?tid=770)

Pages: 1 2


RE: 5101 to 5101E - Firefighter1428 - 23-02-2011

Beginning Cable Modem operation...


CM> Attempting Downstream FEC lock @ freq= 421750000 Hz, QAM64
Deleting DOCSIS 1.0 CoS Settings for SID 0
0x0003f674 [CmDocsisCtlThread] BcmDocsisCmHalIf:Big GrineleteAllServiceFlows: (DOCSIS CableModem HalIf) Deleting all Upstream and Downstream Service Flows, along with associated Classifiers and PHS rules...
Stopping DHCP/ToD/TFTP (client requested)...
DefaultSnmpAgentClass::RestartPendingEvent for SB5102 CM Agent w/ BRCM Factory Support
SB5102 CM Agent w/ BRCM Factory Support resetting to default state.
SB5102 CM Agent w/ BRCM Factory Support destroying users...
Pausing trap thread
SB5102 CM Agent w/ BRCM Factory Support destroying notifies...
Resuming trap thread
SB5102 CM Agent w/ BRCM Factory Support destroying views...
SB5102 CM Agent w/ BRCM Factory Support sending deferred traps...
Done w/ deferred traps.
SB5102 CM Event Log w/ BRCM Factory Support sending deferred async messages...
Done w/ deferred msgs
SB5102 CM Agent w/ BRCM Factory Support defering traps.
SB5102 CM Agent w/ BRCM Factory Support setting V1/V2 view to unrestricted
SB5102 CPE Agent w/ BRCM Factory Support setting V1/V2 view to docsisCpeView
Non-Vol Settings successfully written to the device.
0x0003f688 [CmDocsisCtlThread] BcmCmDocsisCtlThread::ResetRngState: (CmDocsisCtlThread)

@@@@@ In ResetRngState, fRemainingInitRngPowerSteps 17
Attempting Downstream FEC lock @ freq= 415750000 Hz, QAM64
0x0003f688 [Scan Downstream Thread] BcmVendorCmDownstreamScanThread::ThreadMain: (Scan Downstream Thread) Downstream Channel scan stopped!
0x0003f69c [CmDocsisCtlThread] BcmCmDocsisCtlThread::SyncStop: (CmDocsisCtlThread)

*
* Locking off-frequency so that we don't receive any
* messages or data. Ignore the scan messages that follow...
*

0x0003f69c [Scan Downstream Thread] BcmVendorCmDownstreamScanThread::ThreadMain: (Scan Downstream Thread) Scanning for a Downstream Channel...

mot_scanList: Setting override freq @ 7000000
Scanning DS Channel at 7000000 Hz... (Initial target freq)
0x0003f69c [Scan Downstream Thread] BcmVendorCmDownstreamScanThread::ThreadMain: (Scan Downstream Thread) Scanning for a Downstream Channel...

mot_scanList: Setting override freq @ 0
Attempting Downstream FEC lock @ freq= 409750000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 403750000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 397750000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 391750000 Hz, QAM64

CM> Attempting Downstream FEC lock @ freq= 385750000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 379750000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 373750000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 367750000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 361750000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 355750000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 349750000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 343750000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 337750000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 331750000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 325750000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 319750000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 313750000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 307750000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 301750000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 295750000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 289750000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 283750000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 277750000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 271750000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 265750000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 259750000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 253750000 Hz, QAM64
Favorite[0].freq = 300000000
Attempting Downstream FEC lock @ freq= 300000000 Hz, QAM64/256
Favorite[1].freq = 332000000
Attempting Downstream FEC lock @ freq= 332000000 Hz, QAM64/256
Favorite[2].freq = 334000000
Attempting Downstream FEC lock @ freq= 334000000 Hz, QAM64/256
Go back to 1st favorite
Attempting Downstream FEC lock @ freq= 247750000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 241750000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 235750000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 229750000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 223750000 Hz, QAM64


RE: 5101 to 5101E - drewmerc - 23-02-2011

theres something the isp dont like about your modem which is stopping it getting a lock
could be the mac,spoof,bpi or the need for certs

if it was me i'd dump the non vol from your working modem and upload that to haxorware


RE: 5101 to 5101E - Firefighter1428 - 23-02-2011

whats the link to dump my working (stock) modem to the new one? And thanks!


RE: 5101 to 5101E - drewmerc - 24-02-2011

jtag it, theres many guides on how to backup your modem


RE: 5101 to 5101E - Firefighter1428 - 24-02-2011

Dose Jtag needs the hardware connection on the inside? or can you do it by USB?


RE: 5101 to 5101E - ABMJR - 24-02-2011

Hardware 10 pin header connected to the inside...

There is a way via the coax, but the explanation is too long and I am not in the mood to write it. So, just JTAG whether its a Parallel or USB type


RE: 5101 to 5101E - Firefighter1428 - 24-02-2011

K I will try