
I guess something got damaged but the only suspicious log entry mentions that xbmc "failed to get eeprom user settings."
What do?
The time isn't set on boot to a specific date in the last 10 years as you're no longer softmodded. ( the clock loop fix set the time to a preset date, on my softmod I set it to 1/1/2016 )foxinabox wrote:None of those is true in my case, except for not being connected to the internet.
foxinabox wrote:I was never softmodded. This xbox is tsop'd. Manually entering the time or date in settings results in a random combo from the 17th century.
I was once corrected when I made this claim. The tenuous argument made was that you could run the TSOP flash program directly from an exploit rather than installing a softmod.Rocky5 wrote:You had to softmod it to flash the TSOP, but that irrelevant.
Yeah, I did type that out about using a chip but in this day and age it's more common for folk to softmod then TSOP.spicemuseum wrote:I was once corrected when I made this claim. The tenuous argument made was that you could run the TSOP flash program directly from an exploit rather than installing a softmod.Rocky5 wrote:You had to softmod it to flash the TSOP, but that irrelevant.
In this case, however, the cat has been let out of the Fox's bag - he's hardmodded.
I don't disagree.Rocky5 wrote:.... ( also the softmod is a software modification/exploit, so the save is a softmod in the technical sense )spicemuseum wrote:I was once corrected when I made this claim. The tenuous argument made was that you could run the TSOP flash program directly from an exploit rather than installing a softmod....Rocky5 wrote:You had to softmod it to flash the TSOP, but that irrelevant.