07-22-2012 05:52 AM
hi, i'm trying to update my dev alpha to 10.0.6 but every time i start the update it fails at the downloading.
always when i reach module 35 of 39 it says that i lost my internet connection and i need to start again.
maybe my connection is just to slow? i download with 200kb/s (dsl 2000)
what can i do? any solutions?
Solved! Go to Solution.
07-22-2012 11:54 AM
I had a similar problem. My download attempts froze after some time (modul 24 or 35). I believe this are the biggest files. But I didn't get any error message. It just froze.
So I used the "tcpview" tool from Microsoft's free Sysinternals suite and closed all connections of the process "Loader.exe". Then it started again and after several attempts I could download all files and my Dev Alpha got updated.
07-22-2012 11:57 AM
so it seems like BB has a timeout after the download fails.
maybe they can increase it for the people with a slow internet connection?
07-22-2012 12:20 PM
07-22-2012 12:28 PM
Actually my internet connection is not the fastest but it is not slow either (I use a 16 Mbit/s DSL connection). Using the tcpview tool I could see the real progress in terms of downloaded bytes and it was pretty fast until it froze. I don't know why this happened. Also RIM uses obviously Akamai servers for the update distribution so there should be no issue with overloaded servers or something.
Anyway after four or five attempts where I had to close the stalled connection as described above it worked for me. Also I think that the updater did not download all files again (though it said so). I'm not sure about the this but my last attempt went pretty fast.
07-23-2012 04:57 AM
I have the same problem. What is truely weird is that the modules are not cached on disk. So it always starts at 0 again and you wait for a long time just to find it failing shortly before the finish line.
I managed to work around using the desktop manager on a macintosh. There it was no issue. So I think it is a problem of the Windows Software.
Nevertheless I am now stuck because the device somehow downraded itself after reboot. Update seems to work but after it is done I am still on the 10.0.4 version. Repair is broken because the Desktop manager does not wait long enough for the device to reboot.
I would join the previous post: this is the worst update scenario I have ever seen!
What puzzles me is that they got it right on the playbook and now it is a complete mess..
07-23-2012 06:18 AM