Author Topic: OpenDingux update 2014-05-05 (Read 32581 times)

mth · « **on:** May 05, 2014, 01:22:19 am »

After the less than successful release last weekend, we spent a lot of time debugging and testing and came up with a fix. Many good SD cards gave their life (*1) so that you can enjoy the latest improvements to OpenDingux.

Download and instructions, as well as the release notes, can be found on gcw-zero.com as usual.

Note: The actual corruption fix is in the kernel, so it will only take effect after the update is successfully installed. But the checksum verification is fixed now, so if there is a corruption, the update will abort without leaving your Zero in an unbootable state. If this happens, just try to apply the update again until it succeeds.

A new version of the toolchain was released as well.

Special thanks to Nebuleon for helping with testing and for a great spark of insight about what could be causing the corruption, which was almost correct and saved a lot of searching.

(*1) Actually, all the cards are still working, which shows that SD cards are not as easily depleted as I had feared. But they got stressed quite a bit when we copied files over and over again to check for corruptions.

Edit: There was another bug in the checksum computation, causing all installs that require a system partition resize to be flagged as corrupted even if they succeeded. This bug was fixed in the "-take2" version of the updater OPK. If you downloaded the updater soon after it was released, please download again.

AtariHERO · « **Reply #1 on:** May 05, 2014, 01:47:50 am »

" error , flashed image is corrupted "
thinkgeek unit

should i try again ?

mth · « **Reply #2 on:** May 05, 2014, 01:50:58 am »

Yes, please try again, without rebooting inbetween. Only one particular memory page (4K out of 256/512MB) can corrupt, so it's likely that page won't be used every time.

AtariHERO · « **Reply #3 on:** May 05, 2014, 01:52:43 am »

red screen
message :

Opendingux Update 2014-05-05

ERROR!
Flashed image id corrupted !
OK

hi-ban · « **Reply #4 on:** May 05, 2014, 01:58:07 am »

It updated successfully on my unit.
Maybe the file got corrupted when transferring it to the GCW. Try deleting the opk and sending it again to your GCW.

Mookie7162 · « **Reply #5 on:** May 05, 2014, 01:59:56 am »

I just got the same error on a ThinkGeek unit, trying again... I'll keep you posted

Mookie7162 · « **Reply #6 on:** May 05, 2014, 02:02:17 am »

Quote from: AtariHERO on May 05, 2014, 01:52:43 am

red screen
message :

Opendingux Update 2014-05-05

ERROR!
Flashed image id corrupted !
OK

Tried a second time, same message

AtariHERO · « **Reply #7 on:** May 05, 2014, 02:06:03 am »

downloaded again and reflashed several times,
same error
thinkgeek unit's issue ?

AtariHERO · « **Reply #8 on:** May 05, 2014, 02:14:59 am »

10 reflashes, no luck

Nightfuse · « **Reply #9 on:** May 05, 2014, 02:16:46 am »

I have the same problem with my thinkgeek unit too. I've tried about 20 times and still haven't gotten it to work.

mth · « **Reply #10 on:** May 05, 2014, 02:17:52 am »

Edit: This breaks on older OD versions, please don't use it.

I've created a mini update that replaces only the kernel. If the full update keeps running into corruptions, please install the kernel-update first, followed by the full update.

Please let me know if this solves the problem; if it does I'll put it on the web site as well.

hi-ban · « **Reply #11 on:** May 05, 2014, 02:18:11 am »

Did you copy the update OPK into (A) the internal memory, or (B) in a microSD card?

If (A), then try (B).
If (B), then try (A).

Nebuleon · « **Reply #12 on:** May 05, 2014, 02:23:16 am »

Yeah... the update is being carried out by a kernel that causes corruptions. To update properly requires either lots of luck, or something that updates the kernel which then writes correctly.

I am trying to run the updater like you guys and get endless failures, but on my first run from a reflashed October (2013-10-03) the updater succeeded.

~~Please transfer mth's kernel (#10) first, then let it update (and, of course, keep retrying until it stops failing), allow it to boot into the kernel, and update to 05-05.~~

If that also fails, we may need to retract this updater as well. But it detecting the corruption is a great step, and obviously it's better than letting the corrupted install go through.

edit: Clarified which version I updated from. I've been testing May 5 a lot, so installing May 5 from a kernel that can't cause corruptions would be a Catch-22.

patrick81 · « **Reply #13 on:** May 05, 2014, 02:26:23 am »

Hey i have the same error message. I tried this first and the update went through fine. Now i see the new "GCWZERO" introduction but it keeps rebooting. I would like to try to install the full one but how can i do that while this keeps rebooting. :S

Quote from: mth on May 05, 2014, 02:17:52 am

I've created a mini update that replaces only the kernel. If the full update keeps running into corruptions, please install the kernel-update first, followed by the full update.

Please let me know if this solves the problem; if it does I'll put it on the web site as well.

patrick81 · « **Reply #14 on:** May 05, 2014, 02:29:03 am »

haha i can't seem to turn this off. It keeps rebooting.

Edit: okay i think i found a way to turn it off but now i can't turn it on. :/

Nebuleon · « **Reply #15 on:** May 05, 2014, 02:29:13 am »

Quote from: patrick81 on May 05, 2014, 02:26:23 am

Hey i have the same error message. I tried this first and the update went through fine. Now i see the new intro "GCWZERO" but it keeps rebooting. I would like to try to install the full one but how can i do that while this keeps rebooting. :S

Quote from: mth on May 05, 2014, 02:17:52 am
I've created a mini update that replaces only the kernel. If the full update keeps running into corruptions, please install the kernel-update first, followed by the full update.

Please let me know if this solves the problem; if it does I'll put it on the web site as well.

Boot from the OpenDingux Rescue CD v0.2 provided by pcercuei, let it flash the system partition only to recover the function of your GCW Zero, then install the kernel mini-update followed by the full update.

Press Select while your unit is in its boot loop, and hold it until the screen stops displaying something for at least 10 seconds. This will put it in the USB boot mode required by the rescue CD as well.

Nightfuse · « **Reply #16 on:** May 05, 2014, 02:30:24 am »

The Kernel updates okay by itself but when it restarts after installing the new kernel, it gets stuck in a bootloop

mth · « **Reply #17 on:** May 05, 2014, 02:32:07 am »

You can boot an old kernel by holding X when the unit restarts.

gustavolatil · « **Reply #18 on:** May 05, 2014, 02:33:17 am »

i had the brick update installed successfully, tried to do the update and get the error (red screen), updated the kernel and then successfully updated...
but! now the icons take a second to appear in the screen at boot and after i close a opk...
is there something wrong?

Nebuleon · « **Reply #19 on:** May 05, 2014, 02:35:24 am »

Quote from: gustavolatil on May 05, 2014, 02:33:17 am

i had the brick update installed successfully, tried to do the update and get the error (red screen), updated the kernel and then successfully updated...
but! now the icons take a second to appear in the screen at boot and after i close a opk...
is there something wrong?

Nope. That's just how long it takes to read the OPKs' icons, exactly as before.

Now you get your battery status, card capacity and the time before icons are fully loaded.

Author Topic: OpenDingux update 2014-05-05 (Read 32581 times)

mth (OP)

mth (OP)

mth (OP)

Nebuleon

Nebuleon

mth (OP)

Nebuleon