Welcome to the CrackBerry Forums Create Your Account or Ask a Question Answers in 5 minutes - no registration required!
Results 1 to 18 of 18
  1. cbzilla's Avatar
    CrackBerry Newbie

    Posts
    7 Posts
    Thread AuthorThread Author   #1  

    Default Error Code: 407

    Hi:
    I bricked my blackberry and gave up after trying every tip under the sun.
    My problem was: After loading the OS (4.7.0.122) on the storm it would reboot and get into a rebooting cycle. Red light on for 12 seconds then off for 5 seconds, and on and on for hours.

    I noticed that using cfp.exe to run cmmands was more dependable than javaloader. Javaloader would not connect at all giving the :
    Connecting to device...debug: COM error during Open: (0x80040001)
    Error: unable to open port
    error.

    while cfp would happily run the info command.

    So I ran this command:
    cfp -u -v5 HOS and the storm reported HOS was set to developer mode.
    After that the storm finally booted to a whitw screen reporting:

    Device Error: 407
    Reset

    ....and there where I am right now.

    Does anyone know what this means and where to go from here?

    Thanks

    StormBricker
  2. savioAMG's Avatar
    CrackBerry Genius

    Posts
    2,343 Posts
    PIN
    HEAD
    #2  

    Default

    I think 407 is some type of authentication error.
  3. cbzilla's Avatar
    CrackBerry Newbie

    Posts
    7 Posts
    Thread AuthorThread Author   #3  

    Default

    ok so I stopped being lazy and ran help :cfp help hos
    ...
    Description:
    ------------
    The HOS takes the device out of Head in Sand mode. Namely, after sending
    this command, the device will NOT reset on a catastrophic error and will display an error code.

    So I need to find out about this catastrophic error 407.

    Any one?
  4. cbzilla's Avatar
    CrackBerry Newbie

    Posts
    7 Posts
    Thread AuthorThread Author   #4  

    Default

    I doubt if its authentication.
    I've never gone past the initialization stage after loading the OS.
  5. patches152's Avatar
    Banned

    Posts
    7,812 Posts
    Global Posts
    8,138 Global Posts
    #5  

    Default

    You need to load the OS all the way. Sounds like you botched the install somehow.

    Posted from my CrackBerry at wapforums.crackberry.com
  6. savioAMG's Avatar
    CrackBerry Genius

    Posts
    2,343 Posts
    PIN
    HEAD
    #6  

    Default

    Quote Originally Posted by cbzilla View Post
    I doubt if its authentication.
    I've never gone past the initialization stage after loading the OS.
    It doesn't seem like it to me either but from what I've read it has something to do with authentication.

    Posted from my CrackBerry at wapforums.crackberry.com
  7. patches152's Avatar
    Banned

    Posts
    7,812 Posts
    Global Posts
    8,138 Global Posts
    #7  

    Default

    when you did the install did you wait until the DM said "operation complete"?
  8. paulwright1's Avatar
    CrackBerry Genius of Geniuses

    Posts
    5,204 Posts
    #8  

    Default

    Quote Originally Posted by patches152 View Post
    when you did the install did you wait until the DM said "operation complete"?

    oh my word, you mean Im suppose to wait until it finishes until I unplug it.

    I have a feeling thats the reason there are allot of people bricking there storms.
  9. patches152's Avatar
    Banned

    Posts
    7,812 Posts
    Global Posts
    8,138 Global Posts
    #9  

    Default

    when i tell people how to install OS builds, i always tell them to plug the USB into the back of the PC if its a desktop, and put the phone back there...and wait till the DM tells you its done...laptops, you're on your own...


    btw, has anyone heard of the acronym 'PEBKAC'?
  10. paulwright1's Avatar
    CrackBerry Genius of Geniuses

    Posts
    5,204 Posts
    #10  

    Default

    Quote Originally Posted by patches152 View Post
    when i tell people how to install OS builds, i always tell them to plug the USB into the back of the PC if its a desktop, and put the phone back there...and wait till the DM tells you its done...laptops, you're on your own...


    btw, has anyone heard of the acronym 'PEBKAC'?
    otherwise known as OPERATOR ERROR

    I always use my laptop for both of my blackberries and never had any problems yet. No USB HUBS and I make sure everything is finished before I unplug it. I even disable my screen saver so I can watch the progress on the update.
  11. patches152's Avatar
    Banned

    Posts
    7,812 Posts
    Global Posts
    8,138 Global Posts
    #11  

    Default

    Quote Originally Posted by paulwright1 View Post
    otherwise known as OPERATOR ERROR

    I always use my laptop for both of my blackberries and never had any problems yet. No USB HUBS and I make sure everything is finished before I unplug it. I even disable my screen saver so I can watch the progress on the update.
    since i have nothing further to contribute to the discussion....

    i'm reporting your signature!!!

  12. paulwright1's Avatar
    CrackBerry Genius of Geniuses

    Posts
    5,204 Posts
    #12  

    Default

    Quote Originally Posted by patches152 View Post
    since i have nothing further to contribute to the discussion....

    i'm reporting your signature!!!

    did you find anything you like?
  13. cbzilla's Avatar
    CrackBerry Newbie

    Posts
    7 Posts
    Thread AuthorThread Author   #13  

    Default

    During the OS install whetehr U use the loader.exe /nojvm or DM or cfp -u load rimxxxx.sfi, the results are:
    1. DM or loader quits with the error "unable to reconnct during a multistage install"

    2. cfp quits saying

    =========load start

    *** CFP Version 3.9.0.57
    *** CMDLine: -u -v5 load rim0x04001404.sfi
    blah blah blah

    --> Connected to bootrom over USB
    Connected

    [ Uploading RAM Image 0x10000000 ]
    blah blah blah

    --> Received COMPLETE_DONE
    [ Writing 0x00000071 ] [############## 100 ##############]

    --> Elapsed time: 51954 ms. Throughput: 2257.791 kbps

    Done.

    more blah

    --> Requesting BootImage Exit

    --> calling BBDevMgr::Unadvise()

    ================= load end

    as you can see loading completes to a 100% to the flash rom, then tries to reboot...and that is when 407 screen shows up.
    Loader is done doing its thing and I should see a 507 error telling me to load java apps now.
    Instead this 407 shows up.

    Question is does anyone know what 407 is?

    Thanks guys/and or gals
  14. paulwright1's Avatar
    CrackBerry Genius of Geniuses

    Posts
    5,204 Posts
    #14  

    Default

    have you tried using the JL CMDR to wipe you device and start over?
  15. paulwright1's Avatar
    CrackBerry Genius of Geniuses

    Posts
    5,204 Posts
    #15  

    Default

    heres the link if you havent tried yet. And I wouldnt use any kind of USB hub when doing anything with your BB.

    http://forums.crackberry.com/f3/how-...l_cmder-53502/
  16. cbzilla's Avatar
    CrackBerry Newbie

    Posts
    7 Posts
    Thread AuthorThread Author   #16  

    Default

    Already tried JLCmdr
    JLCmdr gives that unable to open port error, when trying to communicate.
    No matter which option I try on the JLCmdr.

    I don't use a hib, and connect direct to USB port.

    Any one know how to ask RIM for meaning of this error code?
  17. cbzilla's Avatar
    CrackBerry Newbie

    Posts
    7 Posts
    Thread AuthorThread Author   #17  

    Default any takers for Device errors at boot time

    Anyone have info on how to open a communication port manually in a blackberry connected to th PC? Any tools for this ?
  18. Tripletrouble's Avatar
    CrackBerry User

    Posts
    28 Posts
    PIN
    ney
    #18  

    Default

    Have you tried using another computer. I bricked mine on my office desktop and could never get anywhere with it. I even had it plugged into the back of the pc and would still get errors. I downloaded JL & DM on my laptop and did a wipe and restored .75 on my phone without a hitch. I think there something on my desktop that does not like berry upgrades.

Posting Permissions