101 Reply by Duane

  • Duane
  • Duane
  • Blue Octy
  • Offline
  • From: San Diego, CA
  • Registered: 2006-08-24
  • Posts: 8,211

Re: UNBRICK YOUR HID-C10 DASH

sjpackage wrote:

Diamaunt: I've done exactly -- EXACTLY -- as you advised in your email this afternoon (Tue., July 25).
THE.  DEVICE.  STILL.  DOES.  NOT.  WORK.


While I can be respectful -- to a point -- I really resent the implication that I'm somehow the problem.

There is a chance that your device is somehow behaving differently than the others we've run into so far.

One question - have you *ever* used the USB port on this device, either for a manual firmware update or to play music, photos or videos?  If not, maybe the issue is that the USB port is, and has always been, nonfunctional on this device.

If Sony made a change in the last week, we have not been able to independently confirm it.  The "1604" is actually build number automatically generated by the build system when the image is build, so a new build *should* have a different number.  Given how the build system works, it's actually very tough to override that, but I suppose it's possible.

Unfortunately, if the installed firmware is indeed different, or your machine is simply not recognizing the USB port in addition to the touchscreen issues, we have no other method to unbrick it.  Sorry about that.

Duane's Website

102 Reply by Duane

  • Duane
  • Duane
  • Blue Octy
  • Offline
  • From: San Diego, CA
  • Registered: 2006-08-24
  • Posts: 8,211

Re: UNBRICK YOUR HID-C10 DASH

ajnaro wrote:

No success.

I followed the installing instructions exactly. I downloaded the 1.7.1526 firmware and the winmd5free program and the sum checked. I downloaded "unbrick_20170715_1.zip" from the blog. Following the instructions, after the dots the "Special Options" mode appeared, but I would not say “very briefly”. The dash eventually rebooted but wound up in the same state as before. I tried a second time with a different dongle that has light. It flashed several times, but not continuously. Unfortunately, the result was the same as before: Sony on the main screen and flashing Sony below.

I have the unbrick.log file. It begins with:

ACE: BlueOcty dash unbricker 1.0.0
2017-07-25 20:43:08 TRACE: =============================
2017-07-25 20:43:08 TRACE: * executing /mnt/usb/unbrick_sync
2017-07-25 20:43:08 backtick('/mnt/usb/unbrick_sync')
2017-07-25 20:43:08 TRACE: ** unbrick_sync result=1

2017-07-25 20:43:08 TRACE: * executing /mnt/usb/unbrick_async
2017-07-25 20:43:08 ClientObject::Initialize() successfully loaded 1 preinstalled libraries
2017-07-25 20:43:08 SensorObject::SensorObject() g_bend_device 0x0
2017-07-25 20:43:08 SensorObject::SensorObject() g_accel_device 0x5e20d0 fd 11
2017-07-25 20:43:08 SensorObject::SensorObject() reading version 5 data, 72 bytes per record
2017-07-25 20:43:08 ClientObject::MainLoop() - masterInstance step time = 0, frame interval = 83
2017-07-25 20:43:08 ExecStreamRequest::Open(nice -n 10 /mnt/usb/unbrick_async) pipe file handle 12
2017-07-25 20:43:08 ClientObject::RegisterForEvent(mmobj=2b54c618) registering event 'FlashPlayer'
2017-07-25 20:43:08 ClientObject::RegisterForEvent(mmobj=2b54c618) registering event 'BIVLCore'
2017-07-25 20:43:09 FrameBuffer::GetDriverValue(alpha) - unable to open /proc/driver/undefinedalpha r/o
2017-07-25 20:43:09 FrameBuffer::SetDriverValue(alpha) - failed to open /proc/driver/undefinedalpha w/o
2017-07-25 20:43:09 FrameBuffer::GetDriverValue(enable) - unable to open /proc/driver/undefinedenable r/o
2017-07-25 20:43:09 FrameBuffer::SetDriverValue(enable) - failed to open /proc/driver/undefinedenable w/o

and continues.  Should I post the fully log here, or send it somewhere?

Thanks for your help.

Well, it looks like the unbricker successfully launch and attempted to run the script that perform the update.

Based the behavior, it looks like it did not find the "update.zip" file.  Can you confirm the 1.7.1526 updatt, named "update.zip" was present on the root level of the dongle?  If so, please confirm the file size.  We did have one user that had the correct name and correct size, but the file itself was corrupted.  Not sure what the cause of that was, but it can happen if, for instance, you remove a dongle from a PC of Mac prematurely.

Duane's Website

  • Registered: 2017-07-25
  • Posts: 1

Re: UNBRICK YOUR HID-C10 DASH

I was able to succesfully restore my Dash back to clock mode using the steps listed in this topic. I did not connect the device to my wifi network. I know this is silly, but one of my very favorite features is the screen timer mode for dimming and Power Save to completely shut down the screen at night. I like it really dark, and with no clock, so that I am not tempted to be a raging insomniac. Is there any way to use this feature in it's current state? If I connect to my wifi network, will it force me to update again?

  • Registered: 2017-07-23
  • Posts: 6

Re: UNBRICK YOUR HID-C10 DASH

Duane wrote:
sjpackage wrote:

Diamaunt: I've done exactly -- EXACTLY -- as you advised in your email this afternoon (Tue., July 25).
THE.  DEVICE.  STILL.  DOES.  NOT.  WORK.


While I can be respectful -- to a point -- I really resent the implication that I'm somehow the problem.

There is a chance that your device is somehow behaving differently than the others we've run into so far.

One question - have you *ever* used the USB port on this device, either for a manual firmware update or to play music, photos or videos?  If not, maybe the issue is that the USB port is, and has always been, nonfunctional on this device.

If Sony made a change in the last week, we have not been able to independently confirm it.  The "1604" is actually build number automatically generated by the build system when the image is build, so a new build *should* have a different number.  Given how the build system works, it's actually very tough to override that, but I suppose it's possible.

Unfortunately, if the installed firmware is indeed different, or your machine is simply not recognizing the USB port in addition to the touchscreen issues, we have no other method to unbrick it.  Sorry about that.




Hello again Duane,



Again, at the outset, let me clear -- I'm grateful to you. Diamaunt and others in this forum for the help and suggestions. I'm very clear: Sony -- and only Sony -- is the bad guy here. If Sony could spend less time making tired Spiderman movies -- and spend more time on actual customer service -- then I think we'd all be better off.



There are two baffling aspects about this:


1. I have two, apparently identical Dashes. Why did one get the 1604 update and works just fine as a decent
    alarm clock -- while the other got the same update and has been nothing but problems?


2. On Sun., July 16 -- the day after you uploaded your software -- I used a Sandisk 4 GB USB stick (with a
    one-half square inch flashing light) to relay your software to the problem Dash. Granted, I used a method
    slightly different than what you advised -- but it worked.


    On Sat., July 22, I chose to move the device to another room. Upon plugging the unit it, the device loaded
    1526 software -- and, of course, asked for the 1604 update. Yes, I now know I should have skipped it.
    Instead, I chose to accept it -- in the hope that the device would load the same version of 1604 software
    that my good device received. Instead, I received Never Ending Headache Software.


    That night -- using the same, flashing Sandisk USB stick -- I tried the same combination, and in the same
    manner, that worked July 16. When that failed, I tried the exact method you prescribed the day before.
    In recent days -- with Diamaunt's aid -- I've tried honing that effort. Still, nothing has worked.



I'm very hopeful that Chumby can salvage a nifty little device Sony gave up on way too soon.

105 Reply by Duane

  • Duane
  • Duane
  • Blue Octy
  • Offline
  • From: San Diego, CA
  • Registered: 2006-08-24
  • Posts: 8,211

Re: UNBRICK YOUR HID-C10 DASH

We have no idea why some devices work and others don't.  We don't know why some devices that fail to become clocks will still have working touchscreen in Special Options mode, while others don't.  We don't know why some of the devices that work, sometimes fail later.

We have a thread where we asked people about the manufacture date of the device to see if there's any correlation there, but it seems there isn't.

As we put in the original post, it appears that a reapplication of the 1604 firmware will sometimes fail on a device that did not fail before, but seems to always fail if it ever failed.  In other words, we have yet to see a device that requires unbricking successfully install 1604 again without bricking.

We've heard anecdotally, but have not been able to prove, that the the bricked state seems more picky about USB than unbricked devices, and at this point, it might be related to phases of the moon for all we know.

Based on downloads, at this point, it looks like we've unbricked well north of 1100 devices.

Duane's Website

  • Registered: 2017-07-24
  • Posts: 6

Re: UNBRICK YOUR HID-C10 DASH

Thank you very much for your reply.

I tried again, with the same result. The size of the update.zip file is 99,391 KB.

I have a screen print of the dongle directory, but I don't know how to insert it.  The size of update.zip is 99,391 KB. All files are listed without any directory structure.

The beginning of the log is:

2017-07-25 20:43:07 Logging to /mnt/usb/unbrick.log.txt
2017-07-25 20:43:07 -- done with config file, processing command line --
2017-07-25 20:43:07 main() - warning, cannot find /usr/widgets/preload.swf, no default preloads in effect
2017-07-25 20:43:07 ClientSettings::AddArgument() adding safeMode=1
2017-07-25 20:43:07 GetRegisteredInstancePid(/var/run/chumbyflashplayer.pid) open failed, errno = 2 (No such file or directory)
2017-07-25 20:43:07 ClientSettings()::Dump
2017-07-25 20:43:07  fileName:                 /usr/widgets/controlpanel.swf
2017-07-25 20:43:07  asynchronous load:        f
2017-07-25 20:43:07  memory blocks:            1024 (32768 K) (0 K master, 0 K slave)
2017-07-25 20:43:07  screen_size:              800X480
2017-07-25 20:43:07  screen_stride:            1600
2017-07-25 20:43:07  screen_rotate:            0
2017-07-25 20:43:07  screen_update:            T
2017-07-25 20:43:07  flash_quality:            2
2017-07-25 20:43:07  sound_buffers:            16
2017-07-25 20:43:07  sound_sample_rate:        44100
2017-07-25 20:43:07  sound_channels:           2
2017-07-25 20:43:07  sound_bytes_per_channel:  2
2017-07-25 20:43:07  sound_samples_per_buffer: 512
2017-07-25 20:43:07  allowCrossdomain:         F
2017-07-25 20:43:07  url_cache_blocks:         4096K
2017-07-25 20:43:07  url_cache_aggression_lvl: 5
2017-07-25 20:43:07  htmlCacheWriteInterval:   60
2017-07-25 20:43:07  htmlCacheStatsFile:       (null)
2017-07-25 20:43:07  maxSecondsRuntime:        86400
2017-07-25 20:43:07  preloadCount:             1
2017-07-25 20:43:07     /mnt/usb/unbrick.swf
2017-07-25 20:43:07  argument_count:           1
2017-07-25 20:43:07   safeMode=1
2017-07-25 20:43:07 main() - PATH = /usr/local/mrua/MRUA_src/rmchannel/ios_client/:/usr/local/mrua/MRUA_src/rmchannel/test/:/usr/local/mrua/MRUA_src/rmchannel/xos2k_client/:/usr/local/mrua/MRUA_src/llad_xtest/:/usr/local/mrua/MRUA_src/llad_smallapps:/usr/local/mrua/MRUA_src/xbin/:/usr/local/mrua/MRUA_src/rmfp/test/:/usr/local/mrua/MRUA_src/rmoutports/test/:/usr/local/mrua/MRUA_src/bin/:/usr/local/mrua/MRUA_src/samples/:/usr/local/mrua/bin/:/usr/bin:/bin:/usr/sbin:/usr/local/sbin:/sbin:/usr/chumby/scripts
2017-07-25 20:43:07 main() - no http_proxy set from environment
2017-07-25 20:43:07 GetRegisteredInstancePid(/var/run/x2test.pid) open failed, errno = 2 (No such file or directory)
2017-07-25 20:43:07 BtPlayObject::GlobalInit() - btplay is not running
2017-07-25 20:43:07 HTTPCacheObject::<constructor> passing memory block 0x2b0e4008 for 4613734 bytes to cache heap manager
2017-07-25 20:43:07 ChumbyMem::ctor() using heap memory 0x2b0e4008 size 4505kB
2017-07-25 20:43:07 ChumbyMem::LinkPrivate(mgr=005cc6c8) previous head is 00000000
2017-07-25 20:43:07 HTTPCacheObject::GlobalInit() - creating global instance of cache manager 005cc128
2017-07-25 20:43:07 SoundObject::GlobalInit()
2017-07-25 20:43:07 OpenSoundOutputSync() - no action taken, soundoutputsyncname not set
2017-07-25 20:43:07 FrameBuffer::GetDriverValue(enable) - unable to open /proc/driver/undefinedenable r/o
2017-07-25 20:43:07 FrameBuffer::SetDriverValue(enable) - failed to open /proc/driver/undefinedenable w/o
2017-07-25 20:43:07 FrameBuffer::GetDriverValue(alpha) - unable to open /proc/driver/undefinedalpha r/o
2017-07-25 20:43:07 FrameBuffer::SetDriverValue(alpha) - failed to open /proc/driver/undefinedalpha w/o
2017-07-25 20:43:07 HTTPCurlObject::CurlGlobalInit(/usr/share/certs/curl-ca-bundle.crt,true) - enabling SSL
2017-07-25 20:43:07 Starting flashplayer, use libcurl = Y, HTTPObject::flags = 9
2017-07-25 20:43:07 HTTPCurlObject::CurlMultiInit() returned handle 005d59e8, HTTPObject::g_globalOptions=9
2017-07-25 20:43:07 ClientObject::ClientObject(this=0x005d6640) asynch load = n
2017-07-25 20:43:07 SI_GetRawTime() - successfully opened /dev/timerm, handle 6
2017-07-25 20:43:07 ClientObject(1) mmobj=0x2b54c618, PlatformPlayer=0x2b5550c8
2017-07-25 20:43:07 ChumbyMem::ctor() using heap memory 0x72000000 size 4096kB
2017-07-25 20:43:07 ChumbyMem::LinkPrivate(mgr=005d52e0) previous head is 005cc6c8
2017-07-25 20:43:07 DisplayObject::<ctor>(this=72000024) writing to /dev/fb0 for 750K
2017-07-25 20:43:07 FrameBuffer::<constructor>(0,800X480) 1600 bytes per line, 768000 == buffer size
2017-07-25 20:43:07 FrameBuffer::AssureFrameBuffer() file for /dev/fb0 is 0x5d8e40 (fileno 7)
2017-07-25 20:43:07 800x480, 16bpp, size in KBytes=750, pagesize=16K, size was 750K
2017-07-25 20:43:07 Increasing frame buffer size to 766K
2017-07-25 20:43:07 FrameBuffer::AssureFrameBuffer() Fix alignment 0x8f3fe26c -> 0x2b64e26c.
2017-07-25 20:43:07 FrameBuffer::AssureFrameBuffer() m_frame_buffer=0x2b64e26c allocated 0x2b64c000
2017-07-25 20:43:07 FrameBuffer::GetFrameBuffer(0, 800X480) - creating new FrameBuffer instance 5d8dd0
2017-07-25 20:43:07 DisplayObject::<ctor>(this=72000024) got fb=005d8dd0 for 800X480 idx=0 768000 bytes

107 Reply by Duane

  • Duane
  • Duane
  • Blue Octy
  • Offline
  • From: San Diego, CA
  • Registered: 2006-08-24
  • Posts: 8,211

Re: UNBRICK YOUR HID-C10 DASH

Based on the log, it looks like it successfully ran the unbricker, but had a problem with the update.zip file.

EDIT: actually this looks like it's not finding the "unbrick_sync.sh" and "unbrick_async.sh" files.  It did find the "flashplayer.cfg" and "unbrick.swf" files.   That's a bit weird since they're all supposed to be right next to each other.  Do they show up later in the log?

Duane's Website

  • From: Dallas, Tx
  • Registered: 2011-01-08
  • Posts: 1,262

Re: UNBRICK YOUR HID-C10 DASH

Here are some problems I've seen that people have had:

  • The unbrick files ending up in a subdirectory instead of the root of the USB

  • Corrupted firmware update file, even though it's the right size (check the md5sum)

  • The update file being named wrong, it has to be "update.zip" be careful if on windows if it looks like "update.zip" in the file manager, that it's not named "update.zip.zip", since windows likes hiding some file extensions

  • Not unzipping the unbrick zip file.

Cleaning up any loose bits and bytes.
  • Registered: 2017-07-24
  • Posts: 6

Re: UNBRICK YOUR HID-C10 DASH

My problem is resolved.  One of my files appeared to named update.zip but the name was actually update.zip.zip. This occurred because I renamed the file I had downloaded as update.zip and Windows added a hidden zip extension, as it is wont to do. I am grateful for the help I received in trying to resolve this.

110 Reply by Duane

  • Duane
  • Duane
  • Blue Octy
  • Offline
  • From: San Diego, CA
  • Registered: 2006-08-24
  • Posts: 8,211

Re: UNBRICK YOUR HID-C10 DASH

ajnaro wrote:

My problem is resolved.  One of my files appeared to named update.zip but the name was actually update.zip.zip. This occurred because I renamed the file I had downloaded as update.zip and Windows added a hidden zip extension, as it is wont to do. I am grateful for the help I received in trying to resolve this.

Glad it worked out - that was a very subtle issue!

I think this goes a long way to explain why some people are so sure they did everything right and still had a problem.

Duane's Website

111 Reply by Shana (edited by Shana 2017-07-29 12:23:00)

  • Shana
  • New member
  • Offline
  • Registered: 2017-07-29
  • Posts: 1

Re: UNBRICK YOUR HID-C10 DASH

Hi - I'm trying to apply the 101776156 update and my Dash has been stuck on the Updating software screen for over 40 minutes. It says:
Software update in progress!
Storing checksum: k1.img

DO NOT DISCONNECT THE POWER AT ANY TIME.

Any ideas on what I should do next?
Note - the USB is still blinking orange.

Thanks,
Shana

112 Reply by Tedd

  • Tedd
  • New member
  • Offline
  • Registered: 2017-07-29
  • Posts: 3

Re: UNBRICK YOUR HID-C10 DASH

De-bricked to basic clock and gratefully standing by - thank you!

113 Reply by Tedd

  • Tedd
  • New member
  • Offline
  • Registered: 2017-07-29
  • Posts: 3

Re: UNBRICK YOUR HID-C10 DASH

Thank you from well north of #1100+1

114 Reply by Duane

  • Duane
  • Duane
  • Blue Octy
  • Offline
  • From: San Diego, CA
  • Registered: 2006-08-24
  • Posts: 8,211

Re: UNBRICK YOUR HID-C10 DASH

Shana wrote:

Hi - I'm trying to apply the 101776156 update and my Dash has been stuck on the Updating software screen for over 40 minutes. It says:
Software update in progress!
Storing checksum: k1.img

DO NOT DISCONNECT THE POWER AT ANY TIME.

Any ideas on what I should do next?
Note - the USB is still blinking orange.

Thanks,
Shana

That's not a good sign.  You probably won't have much choice but to try again.  The hope will be that the signatures for the "Safe Mode" (aka "rfs2") and "k2" partitions are correct, if not, then the device is probably bricked completely.

Based on the message, it's trying to store some data, but can't.

That particular behavior may be an indicator of too many bad blocks in the NAND storage, i.e. the memory chip that stores the software may be worn out.

Duane's Website

  • From: Dallas, Tx
  • Registered: 2011-01-08
  • Posts: 1,262

Re: UNBRICK YOUR HID-C10 DASH

Shana wrote:

Hi - I'm trying to apply the 101776156 update and my Dash has been stuck on the Updating software screen for over 40 minutes. It says:
Software update in progress!
Storing checksum: k1.img

DO NOT DISCONNECT THE POWER AT ANY TIME.

Any ideas on what I should do next?
Note - the USB is still blinking orange.

Thanks,
Shana

Check the MD5SUM of the file you downloaded before you try again:
http://forum.chumby.com/viewtopic.php?pid=54865#p54865

Cleaning up any loose bits and bytes.
  • Registered: 2017-07-29
  • Posts: 1

Re: UNBRICK YOUR HID-C10 DASH

I had to register just to thank you for the unbricking help.  Worked like a charm..  So thanks!

117 Reply by rosic

  • Registered: 2017-05-25
  • Posts: 11

Re: UNBRICK YOUR HID-C10 DASH

Unbricked two last evening! thanks for the fantastic instructions!

  • Registered: 2017-08-05
  • Posts: 1

Re: UNBRICK YOUR HID-C10 DASH

I followed the directions exactly as posted and did unbrick my Dash!

It was a little bit of exploration because I did not follow directions exactly.

But I did, and did it exactly as you said, I now have a running Dash.

I can't wait to try some type of a widget or mod to get it out of the stupid clock mode it's in now.

Thank you

  • From: Arlington, VA
  • Registered: 2017-07-07
  • Posts: 2

Re: UNBRICK YOUR HID-C10 DASH

Props to you guys for another successful brick-slayer!

Thanks! Looking forward to the new Chumby OS for Dash.

  • Registered: 2017-08-05
  • Posts: 4

Re: UNBRICK YOUR HID-C10 DASH

Thank you so much, I almost smashed mine in disgust. Now at least I have a clock.

  • From: Dallas, Tx
  • Registered: 2011-01-08
  • Posts: 1,262

Re: UNBRICK YOUR HID-C10 DASH

OVER ONE BILLION SERVED!

Well, ok, not quite one billion...

I just checked the server, and there's been over 3700 downloads from nearly 2900 different IPs of the unbricker.

That's awesome sauce.

Cleaning up any loose bits and bytes.

122 Reply by hanks

  • hanks
  • New member
  • Offline
  • From: San Diego
  • Registered: 2017-08-05
  • Posts: 1

Re: UNBRICK YOUR HID-C10 DASH

Picked one of these up at Goodwill for a few bucks. Successfully Rolled it back! I'm traveling right now and didn't have a USB drive on me. I tried it out with my kindle in USB storage mode and it worked great! Looking forward to the new firmware!

  • From: Dallas, Tx
  • Registered: 2011-01-08
  • Posts: 1,262

Re: UNBRICK YOUR HID-C10 DASH

hanks wrote:

Picked one of these up at Goodwill for a few bucks. Successfully Rolled it back! I'm traveling right now and didn't have a USB drive on me. I tried it out with my kindle in USB storage mode and it worked great! Looking forward to the new firmware!

Ok, so, that's a first... lol many sizes of regular USB sticks, and.... a Kindle.

Sweet, congrats and such smile

Cleaning up any loose bits and bytes.
  • Registered: 2017-06-17
  • Posts: 2

Re: UNBRICK YOUR HID-C10 DASH

Thank you!  I too had the unresponsive touch screen.  After your unbrick update I'm back to the simple clock and the touch screen is working again!  I agree with the others that this was once an amazing bedside clock and is greatly missed.

Will keep watching for updates or a future fix.  Thank you again!!  James in Brooksville, FL

  • Registered: 2017-08-05
  • Posts: 1

Re: UNBRICK YOUR HID-C10 DASH

Just registered to say thank you.  I have unbricked one of my units.  I actually found a brand new one in my closet still shrink wrapped and never opened.  Should I just leave it alone till you are ready with the Chumby update, or mess with this one beforehand.  Thanks again.