Actual recovery can be done from commandline (assuming you’ve run the “normal” recovery atleast once to download recovery images, and you’ve put those in cmdline directory, and you’re issuing those commands being chdired there):
Larlos, good job! I can see in the recovery tool’s log where those two command line programs are executed. Evidently the recovery tool itself won’t continue to execute those programs if it can’t download the firmware ( “recovery images” ) first.
So now we’ll have to get SanDisk to admit there’s a problem with accessing the files at the zing.net server, otherwise there’s going to be more confused Sansa Connect owners …
First you should copy the four files in the folder below C:\Program Files\SanDisk\Sansa Connect Device Recovery\RecoveryImages to C:\Program Files\SanDisk\Sansa Connect Device Recovery\cmdline. I’m not sure if this folder is named the same on every system … on my PC, it’s C:\Program Files\SanDisk\Sansa Connect Device Recovery\RecoveryImages\003500000da4b464402f654403007f07
Then after running the command prompt, you’ll need to go to the cmdline directory:
c:
cd "\Program Files\SanDisk\Sansa Connect Device Recovery\cmdline
Interesting that the file names were different … I wonder if that means they’re different versions of the firmware? Do you have the Internet Radio function now?
FWIW, the “50239” part of the “everest” images coincides with the OS firmware version. My other two files have “65799” in them, which coincide with the “ZAP” version number displayed on my Connect.
Message Edited by PromisedPlanet on 08-08-2009 12:05 PM
@promisedplanet wrote:
Interesting that the file names were different … I wonder if that means they’re different versions of the firmware? Do you have the Internet Radio function now?
Does anybidy kno where I can download the firware files? I’m doing this with a new Connect, and have never downloaded the files- now I have a bricked connect.
Does anybidy kno where I can download the firware files? I’m doing this with a new Connect, and have never downloaded the files- now I have a bricked connect.
Does anybidy kno where I can download the firware files? I’m doing this with a new Connect, and have never downloaded the files- now I have a bricked connect.
Not cool.
Just as another data point to give to SanDisk … are you also getting the same error when you try to use the Sansa Connect Recovery Tool?
Yes, I experienced the exact same issue as everyone else in this thread mentioned the past few days.
Seems like terrible coding to me to REQUIRE an internet download of firmware and not have a failsafe option of using locally stored firmware files, especially because anybody attempting to do this has to brick their player until they can complete the process.
I’m using my new connect to replace an E200 series player that accidentally got left on a car dash and destroyed. I loved the E200 and by extension, sansa.
So far, the connect has been ticking me off at every turn. Nowhere in any documentation did it tell me the wireless would be disabled, which is the whole reason I bought the player. I’m having problems getting videos to work, the player hangs when I go to play one.
This is all for a different thread- suffice to say that I am not the happiest of campers tonight.
Thanks for the person that steered me to the files. That at least got the player unbricked.
You know, I was reading up on the “304 - not modified” error that I was seeing in my recovery tool log, and found it indicates that “the resource for the requested URL has not changed since last accessed or cached”, and is not necessarily an error. I’m wondering if that status code is expected by the tool when the firmware hasn’t changed since it was last downloaded.
Looking back at my log, I’m thinking now that my particular situation may have been caused by the fact that I had my Connect on a USB hub instead of directly to a USB port. My USB connection sometimes “drops” when I’ve connected to the hub (I’ve seen this when copying songs onto the Connect), and this may have been what was happening when I had problems with the recovery tool. I saw the 304 error in the log and thought that was the cause, but now I’m thinking it wasn’t.
Hey everyone. I have a sansa connect just like you all. Had the darndest time getting it to connect the first time, and have since lost my how-to for it.
Device refused to even detect, so I forced recovery mode, then got stuck in it like you all. I even tried going through the config for the recovery program and making security exceptions in IE and mozilla for every site, but no luck still.
I followed the steps (great by the way) and it appears to work, but after entering the second command line, I just wind up with it hanging at receiving software.
Here’s what my console looks like, any suggestions would be great.
(((Step 1)))
C:\Program Files\SanDisk\Sansa Connect Device Recovery\cmdline>zsi_fw.exe -w everest_vmlinux_ext_prod_1.1.1.50239.srr.e evere
st_initrd_ext_prod_1.1.1.50239.srr.e
ZSI FW load starting.
Found encrypted file: everest_vmlinux_ext_prod_1.1.1.50239.srr.e
Found encrypted file: everest_initrd_ext_prod_1.1.1.50239.srr.e
Open USB Device start
found a device!
Attempting to open \?\usb#vid_0781&pid_7481#5&34d1e36e&1&5#{184954e0-9128-11db-b606-0800200c9a66}
opened device!
completeDeviceName = (\?\usb#vid_0781&pid_7481#5&34d1e36e&1&5#{184954e0-9128-11db-b606-0800200c9a66})
Opened successfully.
data completeDeviceName = (\?\usb#vid_0781&pid_7481#5&34d1e36e&1&5#{184954e0-9128-11db-b606-0800200c9a66}\PIPE00)
Opened successfully.
Loading: 1008000 16809984 1754944
Done!
Loading: 4400020 4294967295 1783808
Done!
(((Step 2)))
C:\Program Files\SanDisk\Sansa Connect Device Recovery\cmdline>zaprecover.exe -t 600000 -f yeverest_zap_ota_rel_1.1.2.65799.t
ar.gz.e yeverest_zap_ota_rel_ext_prod_1.1.2.65799.sig
ZSI FW load starting.
Found encrypted file: yeverest_zap_ota_rel_1.1.2.65799.tar.gz.e
Found unencrypted file: yeverest_zap_ota_rel_ext_prod_1.1.2.65799.sig
Timeout! Device not found.
((That’s where it hangs))
It timed out once, so I changed the “-t 60000” by adding a few more 0’s. It was still hanging this morning when I woke up.
>.<
Message Edited by bigwilliex on 08-12-2009 01:08 PM
You may know this already from looking at a log previously posted here, but the next thing that zaprecover.exe tries to do after “Found unencrypted file” is make a connection over USB to Connect, after which it displays “found device!” again. So it seems like there’s some USB problem there.
I don’t know if it’s related, but the Connect’s USB support has always seemed a little flaky. At least that’s what I’ve observed when syncing media onto it, though that may actually be an issue with its MTP implementation.
Yeah, I’ve noticed that the connect is a real flake when it comes to USB connections.
After running the first command (the zsi one) I can watch the connect consistently disappear out of device manager.
Is everyone else running wmp10 or 11? I hate wmp, so mine’s still version 9. I don’t think it’s related, but just in case.
I removed the -t string and it immediately times out.
I also tried running the second command line first, with no change.
I was thinking maybe an earlier version of the zap recovery images may work better if I can find them. It would be nice if the .exe’s came with a little more of a -? dialogue.
