Posts: 4
Joined: Jan 2015
Reputation:
0
Seems to be a problem in the updater-script but when I make any change here it fails signature verification.
I have no clue at all how to resign or by-pass verification.
format("yaffs2", "MTD", "userdata", "0"); <--- does this need another arg ??
I tried changing to format("yaffs2", "MTD", "userdata", "0", "/userdata"); but it fails signature verification.
a similar command in the same script has 5 args --> format("yaffs2", "MTD", "system", "0", "/system");
Please help.
Posts: 1
Joined: Mar 2009
Reputation:
0
2015-01-18, 06:10
(This post was last modified: 2015-01-18, 06:28 by racerx509.)
Hi many thanks for updating this old box. added some new life to the girl.. The os installs just fine on my 2.0 unit, but I"ve lost all network connectivity. No wireless or wired, but usb seems fine. Tried 123114b, 011015 and an old frodo update from 20140507. I guess the 2.0 unit has a different nic card? M3 rev 2.0. Performed a full cache and system delete before updating too. What can i do to fix this?
Posts: 91
Joined: Aug 2013
Reputation:
3
I should have known this one wasn't going to work when the words "MX Linux" showed up on the screen.
For some reason, my Slav (2.2) simply will not run any build based on that code.
Well.... if my new quad core box ever actually makes it across the Pacific, I guess I'll finally get to try Kodi 14.0 out, but this one is apparently going to stay stuck in Gotham land.
Posts: 91
Joined: Aug 2013
Reputation:
3
The flash appears to be successful. No error messages at all. Then when I reboot, it crashes on the logo. It's been the same result on every build I've tried that's based on the MX Linux code.
Oddly enough, I have no problem with other Linux builds for this box (J1nx, STTV, etc.) but none of those builds have updated past Frodo. Even the Gotham build I've been using was something I got from the Pivos board and swapped the proper remote configs in to get it to work.
