Post Reply 
problem with a polish Wolder-like firmware
2012-01-26, 11:50 GMT
Post: #11
RE: problem with a polish Wolder-like firmware
(2012-01-24 16:32 GMT)SilverBear Wrote:  I'm copying your post now, so we'll have a good English version of the correct method to put in the Wiki once that is back online.

I am probably not bringing the wiki back online in writable mode, insteads opting to move all information to the forum.
The old wiki sadly nevert gained much attention and I don't want to split the little information we currently have over two areas.

You could make a howto post here.;
Just make a post and choose "howto" in the thread prefixes to get a nice [Howto] in front of your thread title. I am looking at nice ways to use these thread prefixes, for instance linking to all [Howto] posts, or linking to all posts tagged [A60]
Visit this user's website Find all posts by this user
Quote this message in a reply
2012-01-26, 23:28 GMT
Post: #12
RE: problem with a polish Wolder-like firmware
(2012-01-23 23:43 GMT)alexkidd Wrote:  But now I'm only able to do a complete update with this two firmwares.... It's clear this firmwares contains a brand-lock like the spanish Wolderboox.

I analyzed the update file of this firmware version and I can confirm that it is using a mechanism to restrict the update possibilities. This is the first time that I see an update that intentionally restricts the possibilies for the user. The story with the Wolder update was a bit different, there the update system was incomplete and preventing any update (I expect they made an error during the firmware creation).

Now that we know that update possibilities can be restricted we should mark firmware versions that have this habit. If you find a new firmware version (60 series) and want to know if it uses 'restricted updates' post it here and I will check it.

[url=http://sourceforge.net/projects/openbooxproject]OpenBOOX[/url]: The open source Boox 60 firmware
[url=http://sourceforge.net/apps/mediawiki/openbooxproject/index.php?title=Main_Page]Wiki[/url] - [url=http://www.youtube.com/user/openbooxproject]YouTube[/url]
Visit this user's website Find all posts by this user
Quote this message in a reply
2012-01-27, 14:46 GMT
Post: #13
RE: problem with a polish Wolder-like firmware
(2012-01-26 23:28 GMT)Koudijs Wrote:  I analyzed the update file of this firmware version and I can confirm that it is using a mechanism to restrict the update possibilities. This is the first time that I see an update that intentionally restricts the possibilies for the user. The story with the Wolder update was a bit different, there the update system was incomplete and preventing any update (I expect they made an error during the firmware creation).

I'm curious to know what this lock works.

I know linux but don't know the embedded systems.

I have seen that the "wolder fix" wipes and rewrites the kernel (zImage) and its initrd (zImage-iniramfs) to allow a correct update.
This means that the lock is in the kernel? What to look for, in the kernel, the software who attempts to update?
Find all posts by this user
Quote this message in a reply
2012-01-28, 14:14 GMT
Post: #14
RE: problem with a polish Wolder-like firmware
The locking mechanism is implemented in the file system which is attached to the update kernel (zImage-initramfs). The init script checks if the update archive contains a customer_id file and if it contains the correct ID (onyx). So once you have installed the update only those updates that contain the same ID will be accepted, all others will be rejected.

The Wolder fix replaces the update kernel (and the normal kernel) with an older version that does not contain the locking mechanism. An alternative is to create a modified update archive that contains the expected ID.

[url=http://sourceforge.net/projects/openbooxproject]OpenBOOX[/url]: The open source Boox 60 firmware
[url=http://sourceforge.net/apps/mediawiki/openbooxproject/index.php?title=Main_Page]Wiki[/url] - [url=http://www.youtube.com/user/openbooxproject]YouTube[/url]
Visit this user's website Find all posts by this user
Quote this message in a reply
2012-01-28, 14:41 GMT (This post was last modified: 2012-01-28 14:46 GMT by alexkidd.)
Post: #15
RE: problem with a polish Wolder-like firmware
I have seen who the customer_id file contains only the "onyx" text and I remember that also the wolder contains the same text as customer id.

We should expect a third reseller to be sure, but I think who onyx have introduced a stupid protection to satisfy a request without create a real solution.
Because,I think, it's possible to upgrade from firmware A to firmware B if both firmwares contains the same customer id also if belong at two different reseller.
Find all posts by this user
Quote this message in a reply
2013-09-27, 13:54 GMT
Post: #16
Exclamation RE: problem with a polish Wolder-like firmware
Hello

I have acquired a used Boox M90 that has the Polish software installed. The above method does not seem to work. The icon indicating "busy" status appears only for a second or two. I am still unable to install non-Polish OS.
Find all posts by this user
Quote this message in a reply
Post Reply