I’ve unlocked two white box Connects using this method so far. Everything is great except for the micro SDHC slot. It doesn’t appear to support SDHC. It does work after a fashion. If I format the card in another device, the Connects will recognize the cards full capacity, but file transfers slow to a crawl after the rirst couple tracks, then start to throw errors. I cannot format the card to full capacity in either Connect. I’ve tried four different cards so pretty sure the cards aren’t the problem. Has no one else had this problem? Using WMP 11 on XP.
I currently have the firmware, that was provided via the link at the top of this thread, loaded on my Connect, and it supports a 16GB microSDHC card without a problem. Well, the only real problem is that if the card is fully loaded and in the player, it won’t be available via MTP on powerup. That’s no problem for me, though, I just take the card out, put it in a USB reader/writer, and sync it via MSC.
I have a sansa connect bought on ebay approx 8-10 months ago. “Downgraded” with no issues. My friend bought one recently and tried to downgrade with the nowifi setup file. It installs a firmware 1.2.x without wifi. I still had the DeviceRecoverySetup.exe file I had downloaded, **UNINSTALLED THE DEVICERECOVERYSETUP-NOWIFI** ran DeviceRecoverySetup.exe, etc, and while it is still downloading it appears to be pulling the correct fimrware.
I do believe I have a defective Connect. Bought 2 off a deal of the day site last week.
Got one up and running, no problem, using the method in this thread.
The second one never shows the yellow clock. It just goes back to the SanDisk screen, then I eventually get a “No Device Found” in the cmd window for the manual update.
I do believe this one needs to go back to Sansa. Unless anyone has any suggestions?
CASansa wrote:
I do believe I have a defective Connect. Bought 2 off a deal of the day site last week.
Got one up and running, no problem, using the method in this thread.
The second one never shows the yellow clock. It just goes back to the SanDisk screen, then I eventually get a “No Device Found” in the cmd window for the manual update.
I do believe this one needs to go back to Sansa. Unless anyone has any suggestions?
Make sure the Connect is completely powered down (not just in sleep mode) before starting the process.
But the “no device found” sounds like a USB problem. Try again using the same USB port and the same USB cable as the other Connect, if you haven’t already. Make sure the other end of the USB cable is well-seated into the Connect’s USB port.
Also, in case there’s some intermittent issue with your own USB port, you could try another USB port, and try a different computer.
If you need to return the Connect, you may be able to return it to the company from which you bought it, but you won’t be able to return it to Sansa (SanDisk). The Connect has been discontinued for some time.
Message Edited by PromisedPlanet on 12-27-2009 09:18 AM
Yep, tried all that.
I’ll see what I can do about returning it.
Hi!
I seem to be stuck - my screen has the yellow clock and says “receiving software” i’m not sure what went wrong as i followed the directions in the original post. i’ve attached the recovery log text below. any suggestions? thanks!
===== Begin execution =====
30 Dec 2009 22:36:32,171 INFO - Executing process C:\Program Files\SanDisk\Sansa Connect Device Recovery.\cmdline\zsi_fw.exe -r 32…
30 Dec 2009 22:36:32,515 INFO - ZSI FW load starting.
30 Dec 2009 22:36:32,515 INFO - Open USB Device start
30 Dec 2009 22:36:32,515 INFO - found a device!
30 Dec 2009 22:36:32,515 INFO - Attempting to open \?\usb#vid_0781&pid_7481#5&1ea0b166&0&2#{184954e0-9128-11db-b606-0800200c9a66}
30 Dec 2009 22:36:32,515 INFO - opened device!
30 Dec 2009 22:36:32,515 INFO - completeDeviceName = (\?\usb#vid_0781&pid_7481#5&1ea0b166&0&2#{184954e0-9128-11db-b606-0800200c9a66})
30 Dec 2009 22:36:32,515 INFO - Opened successfully.
30 Dec 2009 22:36:32,515 INFO - data completeDeviceName = (\?\usb#vid_0781&pid_7481#5&1ea0b166&0&2#{184954e0-9128-11db-b606-0800200c9a66}\PIPE01)
30 Dec 2009 22:36:32,515 INFO - Opened successfully.
30 Dec 2009 22:36:32,515 INFO - ID: 0035000010641887c9f82100030033d2
30 Dec 2009 22:36:32,515 INFO - Device ID=[0035000010641887c9f82100030033d2]
30 Dec 2009 22:36:45,734 INFO - Requesting images from [https://SC01-P031.zing.net/UserPortal/Updates/Recovery.aspx?\_zinfo=d%3D0035000010641887c9f82100030033d2%2Czkf%3D0.0.0.1%2Cv%3D2]
30 Dec 2009 22:36:47,734 INFO - Downloading [https://SC01-P031-W002.zing.net/UserPortal/Updates/Content.aspx/Software/Firmware/everest\_vmlinux\_ext\_prod\_1.1.1.50239.srr.e?\_zinfo=d%3D0035000010641887c9f82100030033d2%2Czkf%3D0.0.0.1%2Cv%3D2] to [C:\Program Files\SanDisk\Sansa Connect Device Recovery\RecoveryImages\0035000010641887c9f82100030033d2.downloading\everest_vmlinux_ext_prod_1.1.1.50239.srr.e]
30 Dec 2009 22:37:18,281 INFO - Downloading [https://SC01-P031-W002.zing.net/UserPortal/Updates/Content.aspx/Software/FileSystem/everest\_initrd\_ext\_prod\_1.1.1.50239.srr.e?\_zinfo=d%3D0035000010641887c9f82100030033d2%2Czkf%3D0.0.0.1%2Cv%3D2] to [C:\Program Files\SanDisk\Sansa Connect Device Recovery\RecoveryImages\0035000010641887c9f82100030033d2.downloading\everest_initrd_ext_prod_1.1.1.50239.srr.e]
30 Dec 2009 22:37:48,078 INFO - Downloading [https://SC01-P031-W002.zing.net/UserPortal/Updates/Content.aspx/Software/Platform/yeverest\_zap\_ota\_rel\_1.1.2.65799.tar.gz.e?\_zinfo=d%3D0035000010641887c9f82100030033d2%2Czkf%3D0.0.0.1%2Cv%3D2] to [C:\Program Files\SanDisk\Sansa Connect Device Recovery\RecoveryImages\0035000010641887c9f82100030033d2.downloading\yeverest_zap_ota_rel_1.1.2.65799.tar.gz.e]
30 Dec 2009 22:42:31,578 INFO - Downloading [https://SC01-P031-W002.zing.net/UserPortal/Updates/Content.aspx/Software/Platform/yeverest\_zap\_ota\_rel\_ext\_prod\_1.1.2.65799.sig?\_zinfo=d%3D0035000010641887c9f82100030033d2%2Czkf%3D0.0.0.1%2Cv%3D2] to [C:\Program Files\SanDisk\Sansa Connect Device Recovery\RecoveryImages\0035000010641887c9f82100030033d2.downloading\yeverest_zap_ota_rel_ext_prod_1.1.2.65799.sig]
30 Dec 2009 22:42:32,437 INFO - Setting location of image file firmwareUrl for device 0035000010641887c9f82100030033d2 to C:\Program Files\SanDisk\Sansa Connect Device Recovery\RecoveryImages\0035000010641887c9f82100030033d2\everest_vmlinux_ext_prod_1.1.1.50239.srr.e
30 Dec 2009 22:42:32,453 INFO - Setting location of image file filesystemUrl for device 0035000010641887c9f82100030033d2 to C:\Program Files\SanDisk\Sansa Connect Device Recovery\RecoveryImages\0035000010641887c9f82100030033d2\everest_initrd_ext_prod_1.1.1.50239.srr.e
30 Dec 2009 22:42:32,453 INFO - Setting location of image file platformUrl for device 0035000010641887c9f82100030033d2 to C:\Program Files\SanDisk\Sansa Connect Device Recovery\RecoveryImages\0035000010641887c9f82100030033d2\yeverest_zap_ota_rel_1.1.2.65799.tar.gz.e
30 Dec 2009 22:42:32,453 INFO - Setting location of image file platformSignatureUrl for device 0035000010641887c9f82100030033d2 to C:\Program Files\SanDisk\Sansa Connect Device Recovery\RecoveryImages\0035000010641887c9f82100030033d2\yeverest_zap_ota_rel_ext_prod_1.1.2.65799.sig
30 Dec 2009 22:42:32,468 INFO - Calling sw update tool with => [“C:\Program Files\SanDisk\Sansa Connect Device Recovery.\cmdline\zsi_fw.exe” -w “C:\Program Files\SanDisk\Sansa Connect Device Recovery\RecoveryImages\0035000010641887c9f82100030033d2\everest_vmlinux_ext_prod_1.1.1.50239.srr.e” “C:\Program Files\SanDisk\Sansa Connect Device Recovery\RecoveryImages\0035000010641887c9f82100030033d2\everest_initrd_ext_prod_1.1.1.50239.srr.e”]
30 Dec 2009 22:42:32,578 INFO - sw update tool output – start:
30 Dec 2009 22:42:33,000 INFO - ZSI FW load starting.
30 Dec 2009 22:42:33,000 INFO - Found encrypted file: everest_vmlinux_ext_prod_1.1.1.50239.srr.e
30 Dec 2009 22:42:33,000 INFO - Found encrypted file: everest_initrd_ext_prod_1.1.1.50239.srr.e
30 Dec 2009 22:42:33,000 INFO - Open USB Device start
30 Dec 2009 22:42:33,000 INFO - device failed to open.
30 Dec 2009 22:42:33,000 INFO - no more items. done.
30 Dec 2009 22:42:33,000 INFO - Failed to GetUsbDeviceFileName err - 0
30 Dec 2009 22:42:33,000 INFO -
30 Dec 2009 22:42:33,000 INFO - sw update tool returned with exit code [-1]
30 Dec 2009 22:42:33,000 INFO - sw update tool output – end
30 Dec 2009 22:42:33,031 ERROR - Unexpected error occurred while recovering the device.
ZING.DeviceRecovery.Managers.CouldNotRecoverDeviceException: sw update tool failed to copy firmware image to the device. Exit code [-1]
at ZING.DeviceRecovery.Managers.DeviceRecoveryManager.RecoverDeviceInternal(Object notUsed)
===== End execution =====
These lines indicate the problem:
30 Dec 2009 22:42:33,000 INFO - Open USB Device start
30 Dec 2009 22:42:33,000 INFO - device failed to open.
30 Dec 2009 22:42:33,000 INFO - no more items. done.
30 Dec 2009 22:42:33,000 INFO - Failed to GetUsbDeviceFileName err - 0
This indicates a USB problem communicating with your Connect.
Also, the log indicates that you are attempting to run the Recovery Tool as downloaded from Sandisk, rather than running the individual programs (zsi_fw.exe, zaprecover.exe) that you should have downloaded from the megaupload.com link.
I’d suggest trying it again, but running the two individual programs manually. Follow the process described in the 7th post of this thread:
http://forums.sandisk.com/sansa/board/message?board.id=connect&thread.id=2793
Message Edited by PromisedPlanet on 12-31-2009 10:33 AM
i posted too soon! i reran the recovery.bat file and it worked just fine! you are right, i must have had the other recovery program running by accident. thanks for your response and your help! have a great new year!
You’re welcome and happy new year to you too, enjoy your Connect!
PromisedPlanet: Kudos on your in-depth research on and sharing of info for the wifi-“inizing” of the Sansa Connect. As impressed new owners of 2 white box units, we are in XP, and at step #3, but not savvy as to “In the same directory, create a file called recovery.bat containing the lines”
If you might take time to explain accomplishing that procedure, we would be most appreciative!
Howdy;
I originally describing making a batch file (recovery.bat) to execute the two commands ( the ones that begin with “zsi_fw.exe” and “zaprecover.exe” ), but that’s not really necessary. You can do the following instead:
a) Open a command window (start->run, enter “cmd”, press return)
b) Enter the following into the command window (be sure to include the quotes):
c:
cd “\Program Files\SanDisk\Sansa Connect Device Recovery\cmdline”
c) Copy-and-paste each of the two commands for updating the firmware, one at a time, into your command window. Make sure the first one is complete before doing the second one. To paste into a command window, you just right-click within the command window and select “paste”. Here are the commands again:
zsi_fw.exe -w everest_vmlinux_ext_prod_1.1.1.50239.srr.e everest_initrd_ext_prod_1.1.1.50239.srr.e
zaprecover.exe -t 600000 -f yeverest_zap_ota_rel_1.1.2.65799.tar.gz.e yeverest_zap_ota_rel_ext_prod_1.1.2.65799.sig
Message Edited by PromisedPlanet on 01-05-2010 05:31 PM
Mission accomplished courtesy of your “dumbing down” the .bat file procedure for us! The Connect is such a cool little unit, and recovering its wifi feature courtesy of your postings makes its that much more of a treat! Thank you very much for sharing your knowledge!
I have downloaded both links you put up, but the othe stuff confuses me…
NinjaofCaedus wrote:
I have downloaded both links you put up, but the othe stuff confuses me…
OK, well, if you want help, post another note telling us what’s confusing you. We can’t read your mind.
Hi folks, I followed these instructions to the _T_, after trying the normal methods of recovery. I have repeated it after charging over and over and it does the same thing in every case. The recovery software every time always says it was successful, but the player itself goes through “Receiving software”, followed by “Verifying Software”, and then “Installing Software” – and during the “Installing Software”, it also displays “Can’t Find Image”. At this point, it fails with an “Error” and then tries to reboot. When it reboots, it starts loading normally, but after going through the first purple icon, it crashes on the second icon, faults to “Error” and then shuts down.
I am at my wits end. I have tried this on Windows 7 and Windows XP systems.
Please help.
Please copy and paste your entire recovery session from the command window to a new post here.
I reloaded my player sometime back using the great instructions found here and it gets internet radio and I don’t think I entered any information about any on-line music account but it plays and works great. The problem is i really like the classic rock channel it has and would like to know what service it’s being streamed from so that I could subscrbe one of my other players to it. Does anyone know what service the connect streams from now ??
It’s still Yahoo Launchcast:
PromisedPlanet wrote:
Regarding viruses etc., they are targeted towards operating systems, like Windows. The Connect does not run an operating system. Also, it isn’t a general networking device, it only downloads audio streams and Flickr photos (with the necessary uploaded information only for authentication and to receive the streams/photos).
Nit pick: the Sansa Connect firmware is Linux + busybox LUA and more. So it does run an OS. But your point is well-taken.
(I’m here because I’m thinking about buying a Sansa Connect and I am trying to figure out the lay of the land. Too bad that the SC won’t load firmware that isn’t cryptographically signed by Zing. As was pointed out (by you, I think) this is a great resource for understanding the guts of the SC.)
