recovery

MP3 players All other MP3 players
61

I just finished installing wmp10. I think not having the mtp setting was what was making it difficult to connect initially (when I first got it).

At this point, I’m looking for some other firmware. It seems like it loses USB on the device as soon as I run the zsi command, which is the firmware loader.

I somehow got it to show up as a removable device in windows explorer, alongside my HD partitions. Since then I’ve managed to lose all my documentation that got me that far >.< Time to clean out my files.

62

I just got a reply from sansa saying basically “we didn’t read your email, here’s our form letter resolution, genius.” and “please try this, then contact us again if needed.”

So I did that, copied in my connectivity log, and am going to go and work on my car. At least that, I can smack it when it’s being stupid.

I might try to install rockbox… I think I’d do that only as a last resort though, until this is working normally again.

I’m looking for any different version of the connect’s firmware, older or newer. If anyone can help with that, it would be great. I already have the one from a few pages back in this thread.

63

There is no rockbox for the Connect, unfortunately.

64

@promisedplanet wrote:

@larlos wrote:
I already disabled the windows firewall, and the problem continues.

 

Yep, well, it’s not a firewall issue because the recovery tool’s log shows a response from the zing.net server.  I sent that log to SanDisk, so they should have known that.  I guess they didn’t look at the log.

Just got another email from SanDisk tech support, thought you guys might find this amusing …

In my email to them, I mentioned the error in the tool’s log after the tool attempted to download the firmware images from zing.net.  SanDisk’s response was “we’ve ended our partnership with zing.net” and “you must not have the latest version of the tool, uninstall yours and install this one (URL)”.

Just for chucks, I did what they requested, then sent them the portion of the log showing that the tool still attempts to download the firmware images from zing.net.

Egads.

65

Hmm I was sure I ran across some page saying there was a rockbox version for the connect. I just checked the page though and no go. Must have been my mistake.

Anyway, Sandisk is going to replace it for me, which helps me, but doesn’t really help anyone else in this situation. Hopefully, it’s just a fluke and nobody else has this same issue as I did.

The recovery program really is not working though - it’s extremely stupid to make the recovery tool fail if it can’t get new firmware.

The only reason I could see for it is if the device will only upgrade firmware, and not re-load existing firmware. I’ve come across other deivces that work that way.

66

I picked up a new white box Connect today and I somehow “bricked” it.  I hadn’t seen that term before today but it fits.  Anyway I didn’t have any problem downloading an installing the recovery tool but it refuses to recognize my Internet connection.

 So I down loaded the files from the link earlier in this discussion and moved on to try the command line method.  After screwing around with it for a while I got the parameters right and it comes up and says that it found the files then it just sits there for several minutes then times out saying it the device was not found.

I’ve tried all the USB ports on my computer and disconnected and reconnected the USB cord several times.  Can anybody tell me what I’m doing wrong?  I copied the files to the cmdline directory and gave it the command

“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”

67

I’ve had problems communicating with the Connect over USB when connected to a USB hub, but it was fine when connected directly to a USB port on my PC.  Not sure why.  I know you said you tried all the USB ports on your PC.

I’m still waiting for SanDisk to respond to my last email to them, 2nd in a series, regarding the problem with the Recovery Tool not being able to download the firmware images.

68

I don’t think it’s a problem with the USB ports.  I have a rather hotrod motherboard so I decided to try it on my wife’s computer and my old dog laptop as well.  All had the same results.  I was wondering if the program in the background was causing the problem since it pops up when the player is pluged into a port, so I tried copying the directory to the root of C: and uninstalling the program.  Then I tried it again command line with the same results.  At this point I’m thinking it’s screwed and I’m out the money I paid for it.

Tony

69

One more thing.  The recovery program I downloaded is verrsion 12.0.0.49974.  I’ve read here that this is supposed to be a new version of the programe.  Anybody have an earlier version that may have a different command line program?

If so, coult you zip it up and send it to me at technojock@yahoo.com?

Tony

70

Absolute Geneious!   This worked perfectly.  Brought my Connect back to life.  Thanks for the posts.

71

I’ve put the nesw files into the cmdline folders, but when I try putting in the commands it says it cannot find the file.

And yes I did check to make sure the files were acually there, and that I didn’t make any mistake in typing.

Any idea what I’m doing wrong?

djc

72

Put exactly the same name of files in the cmdline.

73

I personally want to thank Larlos and others for posting to this site in regards to the Connect.   Yes I intentionally bricked mine when it came as the wifi was not enabled.  I followed SanDisks directions to use the recovery tool …

I got the same problem that others here have. . . it failed to recognize my internet connection.

after some major serching I found the posts here.  B-E-A-utiful.

Too bad that sans doesn’t employ those here that solved the problem.  How dumb it this on Sansa’s Part??

This was the first . . and it will be the last Sansa I buy.

74

–Put exactly the same name of files in the cmdline.

I thought I had, but when I tried again I caught myself typing exe instead of ext, so maybe that’s what happened before.

worked this time!

thanks everyone!

DJC

75

@zie wrote:

 

Too bad that sans doesn’t employ those here that solved the problem.  How dumb it this on Sansa’s Part??

Well, the only reason we have to go through this manual recovery hell in the first place is because SanDisk won’t acknowledge that there’s a problem accessing the firmware images at zing.net, which is causing the recovery tool to fail.

76

@geezertony wrote:

One more thing.  The recovery program I downloaded is verrsion 12.0.0.49974.  I’ve read here that this is supposed to be a new version of the programe.  Anybody have an earlier version that may have a different command line program?

Where are you getting that version information?  Which executable are you referring to?

 

77

Okay, I “bricked” my New SAnsa connecet right out of the box. I went to the Sansa Recovery tool and as the rest of you have noted, their server is down or unavalable or whatever. I called Sasa and they say they are working on it.

So I went the commnad line route, downloaded the stuff from megaupload, but then I get:

File yeverest_zap_ota_rel_ext_prod_1.1.1.50371.tar.gz.e not found

Can one of you kind souls please help me?

Thanks!

78

Never mind… got it. Had to rename the files.  Thanks for your efforts!

79

Can you send me the recovery image files?  I would greatly appreciate it.  I am going through the same problems that you were having.

Thanks a bunch!!!

KO

80

Sorry, My email is k_omalley09@yahoo.com