Page 1 of 3 123 LastLast
Results 1 to 25 of 69
  1. lastraid's Avatar
    CrackBerry Genius of Geniuses

    Posts
    8,801 Posts
    PIN
    NED To A Wall
    Thread AuthorThread Author   #1  

    Exclamation Tour Update Though DM - BEWARE

    Just to let you all know. I just attemped the update and it fatal errored on me. Phone is fried. This happened a step 7 of 11, so I am back to my curve for the moment. I was infomed that this does not happen to all devices.

    Called VZW tech and asked to xfered to RIM. They have infomred me that if this happens, the device must be replaced. All known fixes do not work. This does not include JL_Command to wipe the device and reload the OS that I know of.

    I am getting a replacement Tour next week. Damn weekends.
  2. Accidental Post's Avatar
    Slayer of Misinformation

    Posts
    5,346 Posts
    Global Posts
    5,378 Global Posts
    PIN
    Smartphones are for Smart People
    #2  

    Default

    You didn't fry your phone BB's are almost impossiBle to fry. Cmon.

    Posted from my CrackBerry at wapforums.crackberry.com
  3. esalonia's Avatar
    CrackBerry Addict

    Posts
    507 Posts
    #3  

    Default

    What fatal error? Can you be any more specific? Screen shots? Error codes?
  4. lastraid's Avatar
    CrackBerry Genius of Geniuses

    Posts
    8,801 Posts
    PIN
    NED To A Wall
    Thread AuthorThread Author   #4  

    Default

    Quote Originally Posted by esalonia View Post
    What fatal error? Can you be any more specific? Screen shots? Error codes?
    No specific message - just fatal error please try again.
    RACECAR spelled backwards is RACECAR

    The only stupid question, is the one not asked.
  5. Iceman0803's Avatar
    CrackBerry Abuser

    Posts
    492 Posts
    Global Posts
    726 Global Posts
    PIN
    S...ALL THE COOL KIDS HAVE 'EM
    #5  

    Default

    Quote Originally Posted by lastraid View Post
    Just to let you all know. I just attemped the update and it fatal errored on me. Phone is fried. This happened a step 7 of 11, so I am back to my curve for the moment. I was infomed that this does not happen to all devices.

    Called VZW tech and asked to xfered to RIM. They have infomred me that if this happens, the device must be replaced. All known fixes do not work. This does not include JL_Command to wipe the device and reload the OS that I know of.

    I am getting a replacement Tour next week. Damn weekends.
    So if this happens the process for recovering a dead BB will not work? Or were you not able to try?
  6. lastraid's Avatar
    CrackBerry Genius of Geniuses

    Posts
    8,801 Posts
    PIN
    NED To A Wall
    Thread AuthorThread Author   #6  

    Default

    Quote Originally Posted by Iceman0803 View Post
    So if this happens the process for recovering a dead BB will not work? Or were you not able to try?
    I did not try - There were some small annoying issues with mine anyway, so I will take the replacement. I am not sure if the recover a dead bb will work or not.
    RACECAR spelled backwards is RACECAR

    The only stupid question, is the one not asked.
  7. Iceman0803's Avatar
    CrackBerry Abuser

    Posts
    492 Posts
    Global Posts
    726 Global Posts
    PIN
    S...ALL THE COOL KIDS HAVE 'EM
    #7  

    Default

    Quote Originally Posted by lastraid View Post
    I did not try - There were some small annoying issues with mine anyway, so I will take the replacement. I am not sure if the recover a dead bb will work or not.
    Hmm, ok. Thanks for the heads up.
  8. mjbesen310's Avatar
    CrackBerry Genius of Geniuses

    Posts
    5,351 Posts
    Global Posts
    5,352 Global Posts
    #8  

    Default

    no, the phones not fried..... I can understand you dont want to try to wipe the phone since you said you had some other problems with that Tour anyway, but the fatal error can be fixed using a Wipe as I've done that in the past.
    Current Device: Blackberry Bold 9650

    Future Device: Droid Bionic 4G!
  9. lastraid's Avatar
    CrackBerry Genius of Geniuses

    Posts
    8,801 Posts
    PIN
    NED To A Wall
    Thread AuthorThread Author   #9  

    Default

    What wipe method did you use?
    RACECAR spelled backwards is RACECAR

    The only stupid question, is the one not asked.
  10. CafeRacer808's Avatar
    Banned

    Posts
    510 Posts
    PIN
    You show me yours, I'll show you mine. ;)
    #10  

    Default

    Quote Originally Posted by lastraid View Post
    I did not try - There were some small annoying issues with mine anyway, so I will take the replacement. I am not sure if the recover a dead bb will work or not.
    I'd definitely be curious to know if the recover a dead bb process works or not. It's a good way to find out if the RIM tech you spoke to actually knew what they were talking about...
  11. lastraid's Avatar
    CrackBerry Genius of Geniuses

    Posts
    8,801 Posts
    PIN
    NED To A Wall
    Thread AuthorThread Author   #11  

    Default

    Quote Originally Posted by CafeRacer808 View Post
    I'd definitely be curious to know if the recover a dead bb process works or not. It's a good way to find out if the RIM tech you spoke to actually knew what they were talking about...
    True, but this is the lazy side of me. Not to mention a time thing
    RACECAR spelled backwards is RACECAR

    The only stupid question, is the one not asked.
  12. mjbesen310's Avatar
    CrackBerry Genius of Geniuses

    Posts
    5,351 Posts
    Global Posts
    5,352 Global Posts
    #12  

    Default

    Quote Originally Posted by lastraid View Post
    What wipe method did you use?
    I used JL_Command to recover the Blackberry... it worked... its just hard to totally fry a blackberry though.
    Current Device: Blackberry Bold 9650

    Future Device: Droid Bionic 4G!
  13. CafeRacer808's Avatar
    Banned

    Posts
    510 Posts
    PIN
    You show me yours, I'll show you mine. ;)
    #13  

    Default

    Quote Originally Posted by lastraid View Post
    True, but this is the lazy side of me. Not to mention a time thing
    Haha - trust me, I know exactly what you mean.
  14. batotman's Avatar
    CrackBerry User

    Posts
    15 Posts
    #14  

    Default

    Easy fix using loader.exe.
  15. NIKSTORM's Avatar
    CrackBerry Addict

    Posts
    972 Posts
    Global Posts
    1,416 Global Posts
    PIN
    JUST ASK
    #15  

    Default

    at least you were able to try and load this OS, my DM says no update available...good luck with your new phone....i just got a new storm after nine months i know how you feel it gets annoying doing the same thing over and over again to fix a problem that really should not exist with a properly built phone.
    BLAH...BLAH...SMART QUOTE...BLAH
  16. aaronjudze0806's Avatar
    CrackBerry User

    Posts
    62 Posts
    Global Posts
    63 Global Posts
    PIN
    Private
    #16  

    Default

    I installed the update without any issues.
  17. DesertDogs's Avatar
    CrackBerry Addict

    Posts
    774 Posts
    #17  

    Default

    It is a fatal flaw in the new OS. It happens with the same traceable causes as all those old blue screens we used to get on Win95. Bad design is the only common denominator.

    Posted from my CrackBerry at wapforums.crackberry.com
  18. b.asagba's Avatar
    CrackBerry Addict

    Posts
    725 Posts
    Global Posts
    739 Global Posts
    #18  

    Default

    any idea of an OTA update time table.
    Houston Rockets.
    Tennessee Titans.
  19. milly177's Avatar
    CrackBerry Abuser

    Posts
    142 Posts
    #19  

    Default

    Sheesh, thanks for the heads up! Too bad I just started the updating process right before I read your post. Hopefully all goes well! Although I do know that when I use to flash my software for my old WinMo phone, the people that bricked their phones were the ones that didn't have a USB 2.0. What kinda USB port do you have?
  20. a3_star's Avatar
    CrackBerry Newbie

    Posts
    6 Posts
    #20  

    Default

    Tried updating via DM and also received fatal error message. Restarted phone using ALT + Right SHIFT + DEL tried updating again and it worked successfully. Haven't noticed a big difference though.
  21. bcarroll18's Avatar
    CrackBerry User

    Posts
    38 Posts
    #21  

    Default

    I tried checking for an update in DM and on my BB and nothing came up, how could I get this?
  22. 21ce's Avatar
    CrackBerry User

    Posts
    22 Posts
    #22  

    Post

    For the record his blackberry is NOT fried, he just opted to take a replacement. Fatal error means something happened during the install, but he could have easily downloaded BlackBerry Swiss army knife,BBSAK, wiped the device and started anew.
  23. Lovely3800's Avatar
    CrackBerry User

    Posts
    39 Posts
    Global Posts
    49 Global Posts
    #23  

    Default

    Alright so I went ahead and did the update through BM as well and also had the fatal error. So i went and used app loader and rebooted the old OS with nothing else. Then i went ahead and again tried to update the OS and had the same error pop up. So my question is, what are my other options to get this update because obviously its not going to let me do it using the automatic update through BM without erroring. I went to the Verizon site and it doesnt look like the .53 is available for download yet. Any ideas?
  24. sunNsnow's Avatar
    CrackBerry Abuser

    Posts
    108 Posts
    #24  

    Default

    Quote Originally Posted by CafeRacer808 View Post
    I'd definitely be curious to know if the recover a dead bb process works or not. It's a good way to find out if the RIM tech you spoke to actually knew what they were talking about...
    It does work -- I was able to recover a "dead" 8230 where the screen was blank and the red notification light comes on once in a while. And, there was something wrong with the phone, too. I was able to reinstall the original OS (the phone was eventually replaced).
    sunNsnow
  25. lastraid's Avatar
    CrackBerry Genius of Geniuses

    Posts
    8,801 Posts
    PIN
    NED To A Wall
    Thread AuthorThread Author   #25  

    Default

    After a good night sleep, I tried BBSK (1.4) this morning. I have been able to load the 4.7.1.53 OS and the device is up. During sync I got an error and I am working this issue now. Will report later on this issue.

    UPDATE: all sync'd and back up restored
    Last edited by lastraid; 09-19-2009 at 08:52 AM.
    RACECAR spelled backwards is RACECAR

    The only stupid question, is the one not asked.
Page 1 of 3 123 LastLast

Posting Permissions