Replies: 4 comments 24 replies
-
|
Been there, done that. The bricked solo is not calling home to get a new firmware load. |
Beta Was this translation helpful? Give feedback.
-
|
It does when you hold the reset button - I have put the json in place and it has tried to fetch the firmware - which I have not put in place yet as I am not sure what version to put into place yet - The json seems to suggest that the 250 version is the latest but requests it is doing against the analytics server seem to suggest that my slingbox may be running a 270 firmware |
Beta Was this translation helpful? Give feedback.
-
|
Based on the URL you mentioned, it almost seems like the version of the SOLO firmware is now 2.1.110. The JSON response suggests that 2.1.250 is the latest firmware (2.1.270 is actually the latest).
http://services.sling.com/configservices/rest/v2/configuration/product/SOLO/version/2.1.110.json |
Beta Was this translation helpful? Give feedback.
-
|
Posting for Mikoshi-nyudo 👍 And without LAN streaming enabled you'll never be able to get SP 1.5 PC or Mac 1.0.10 app to connect and configure any reset Solo or Pro boxes even with the default admin password. Having looked into the firmware versions my best guess is that unlike the ProHD, the Pro and Solo FW are perhaps set by default to have LAN streaming disabled for an unconfigured/reset box. Whether this by their SPARCS control flag that is sticking even after reset or by default in the those Solo and Pro FW, and unlike the ProHD which may be set as default for LAN enabled or their flag (SPARCS bricking parameter) isn't sticking in a FW rollback from reset. In any event, in a Solo or Pro a reset bricked box it shows this; "name":"MySlingbox","isRegistered":"0",..."isConfigured":"0",.."CanStreamOnLan":"0".... and it is likely that during power up behind the scenes through its initial register response to SPARCS after DHCP IP assignment it would receive a control parameter to enable LAN streaming which would then allow SP setup assistant to establish the session and socket, then authenticate Admin control using the default 'admin admin'. Another potential is that in the Ver2.x Solo FW there's specific SPARCS CFG CtrlBits and AdminConnMode controls, being set too. And regardless of either of the two above scenarios there's a catch 22 now, you can't connect to SPARCS without being bricked. And they probably changed the control parameter it now sets as their FW documents states "Slingbox will allow / deny LAN / WAN streaming based on this SPARCS controls". Also in the Solo FW 2.1.270 bin it shows as part of the timebomb limit expired feature "LAN & WAN streaming is not allowed now pro solo iris" which is an clear indication that the Solo Pro and Iris share the same feature-sets when it comes to SPARCS control parameters. However, if you look into the Solo FwV1.2.18 compared to the FwV2.x you'll notice there isn't those same SPARCS CFG Admin Controls and others... the same applies to FW ver 1.0.39 versus 1.4.20 for the Pro. I was going to explain this to the OP through a chat and try work with him to go through all of this, but essentially if it were me I would be hex hacking the header older FW 1.2.18 into higher version, modding the json and feeding a FW upgrade (downgrade) of those older versions which seem less reliant on SPARCS. And might also hopefully have LAN streaming enabled by default to see if the SP can connect with the default admin admin; which defined clearly in the FW and what SP attempts to use on any unconfigured Solo, Pro or ProHD it sees. Of course, there's no guarantee that such a FW rollback from a ver 2 to 1 will not fail and make a true boat anchor of the box. But at the same time, someone has to try it and see, and the OP has setup the server DNS mimicking to give it a go. All I can say is not all the options to unbrick have been explored at this stage, and this is what I would do (and would have already done/tested) if I had a bricked Solo or Pro here. Unfortunately, as Slingboxes aren't even sold in Australia, and my ProHDs (the only units I own) are physically located in Japan, I have to work with others like RandomMan719 and Proudx to do the actual testing and work through things as a process, like we three did on the ProHD unit. Anyway, this is the other part of the initial investigation into the Firmware, SPARCS and SP setup assistant admin password reason for not authenticating, and some thoughts as to how one could try to unbrick a Solo or Pro. It may lead to nothing but hopefully, someone can give it a go, or the OP can publish a guide for others to setup a system to mimic Slings services.sling.com and cbfu-prod.slingbox.com based on what he uses, so someone else might be able to give it try. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
My singbox solo is pretty much bricked and I tried the factory reset to try and configure it with little success.....
BUT - The slingbox is currently unable to make outbound connections as they are blocked with ip tables on my main router. - I have redirected all sling.com etc DNS entries to a honeypod style linux box and in the webserver logs I worked out it tries to pull a json file from http://services.sling.com/configservices/rest/v2/configuration/product/solo/version/2.1.110/device/.json
This bit of Json looks interesting:
{
"config": {
"product-id": "solo",
"set": [
{
"r": {
"type": "get",
"compression": "None",
"crc": -197069916,
"content": "http://cbfu-prod.slingbox.com/Solo/SlingboxSoloFwV2_1_250HwV1_0_3Current.bin",
"name": "solo-firmware",
"version": "2.1.250"
},
"name": "fw-components"
},
{
"r": {
"type": "string",
"latest-forced": "2.1.100",
"content": "normal",
"latest-ver": "2.1.250",
"min-ver": "2.1.250",
"name": "fw-update"
},
"name": "update"
},
{
"r": [
{
"type": "int",
"content": 300,
"name": "inactive-seconds"
},
{
"type": "int",
"content": 86400,
"name": "next-check-seconds"
},
{
"type": "int",
"content": 3,
"name": "read-attempts"
},
{
"type": "int",
"content": 3866688,
"name": "size-bytes"
}
],
"name": "utility"
}
],
"version": "2.1.110"
}
}
This suggests to me it will download the firmware from the given URL and I managed to grab an older version of the FW from there as well so I will be populating my honeypod with the relevant files to see if I can get the slingbox to pull an older version of the firmware when I am local to it.
Does this sound like a plan or am I on a path of total destruction with my brick.
Best regards
Beta Was this translation helpful? Give feedback.
All reactions