Results 1 to 10 of 264

Hybrid View

  1. #1
    Recently Initiate EccTM's Avatar
    Join Date
    May 2008
    Device
    K800i (R8BF003 CID53)
    Posts
    16
    Thanks
    3
    Thanked 0 Times in 0 Posts

    Re: Patching CID53 (DB2020)&DB2010,2012

    i have the same problem as Mobile Man, once i go to open the bflash folder, my K800's screen lights up on the "run flashed loader" line, then cuts to File Transfer mode, with Far+JD giving that error... any suggestions?

    K800 - R8BF003 Generic - Red - CID53

    EDIT:
    Mobile Man (and others with same problem), i fixed it on my phone, i turned on my phone and relaunched executor, then reconnected to far+JD using qa2020, all went well from there and i've now a fully unlocked K800 :)
    Last edited by EccTM; 04-13-2009 at 04:30 PM. Reason: Problem Solved

  2. #2
    Recently Initiate
    Join Date
    Jun 2009
    Device
    -
    Posts
    6
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Patching CID53 (DB2020)&DB2010,2012

    Quote Originally Posted by EccTM View Post
    i have the same problem as Mobile Man, once i go to open the bflash folder, my K800's screen lights up on the "run flashed loader" line, then cuts to File Transfer mode, with Far+JD giving that error... any suggestions?

    K800 - R8BF003 Generic - Red - CID53

    EDIT:
    Mobile Man (and others with same problem), i fixed it on my phone, i turned on my phone and relaunched executor, then reconnected to far+JD using qa2020, all went well from there and i've now a fully unlocked K800 :)
    Well EccTM, I have a W880i and I have the same problem, can you explain it a little bit better? Should I transfer the execute.b file to my phone or?
    Please respond on this one, I'm quite frankly lost right now :(
    or could anyone else respond on this one?

  3. #3
    Recently Initiate
    Join Date
    Jun 2009
    Device
    -
    Posts
    1
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Unhappy Re: Patching CID53 (DB2020)&DB2010,2012

    Hi!

    I was trying to unlock the simlock of my W880i (Red CID53, DB2020, Firmware Version: R6BC002.)

    I was following a guide, which wasn't clear enough, I guess.
    As you probably know, there is no executor for my version in the anycid.rar, so I followed the instructions of the guide for these cases:

    - get a main file, which HAS executor in the anycid.rar.
    I picked R8BA24 main and fs files (and also the main and fs files for MY version R6BC002).

    - make rest and qa patch files using R8BA24.mbn.

    - now flash the phone with far using db2020 script, upload the R8BA24.mbn into the oflash folder as a babe image, up-up-up, disconnect, akku out-in.

    - now flash again, now upload the executor files (.b, .jar, .xml) into the \tpa\preset\custom\ folder, and disconnect again, akku out, accepted sim in, akku in, turn on, go to games, start executor, whis supposed to shut down the phone. (it succeeded)

    - now use FAR again, with the proper qa2020.xml, I connected the phone using this script. Enter "bflash".

    [from this point, I was not sure which files has to be copied, I tell the story the way I did.]

    - the guide said, upload here the rest file, but it hadn't mentioned, which version, so I uploaded the rest file (as a babe image) made of the mnb of MY firmware version. (maybe here I was slid:)

    - upload the main file (as a babe image) for MY firmware version

    - upload the qa patch vkp (as a vkp patch) (made by using MY firmware version)

    - upload the unlocking vkp file

    At this point I was shocked, wtf? Which unlocking vkp?

    So I started to seek for other guides, and found one, which mentioned at this last step to upload the fs file, too (for MY frimware version), so I did it, however it didn't mention any unlocking vkp file. (I was more confused at this point.)

    Than disconnect, akku out, (originally unaccepted) simcard in, akku in, turning on.

    I was glad first, because the phone language was set back to mine, the phone was loading something, then it said, not supported SIM, insert blabla.
    Yeah, I screwed something, so I decided to start all over.

    As you see, it seemed that I can start again safely, because the status of my phone was exactly as it had been at the very first time.

    I was planning to upload the other rest file, not the one made of MY main version.

    I did as it was said:
    - connect using db2020, upload the OTHER (R8BA24) main into the oflash folder, than disconnect, akku blabla. Done.

    - Do not turn on, connect again instead, copy the executor files, disconnect, akku out, supported sim in, akku in, turn on, and OOOPS! I got this error:

    "Configuration error. Please contact your network operator or service centre."

    I freezed, what the hell?

    So I started to redo things I'd done: uploaded the OTHER main again, then the main and the fs again, then MY main, my fs, but nothing helped, still throwing the same error.

    Then I figured, whether I sould upload MY main using qa2020, so I connected successfully, but when I tried to enter "bflash" after some loading it halted:

    And right after this error the phone connects to the computer as an USB-storage.

    Now I stopped trying anything, and asked for help.

    Could anyone please help me out? :confused:

    Thanks very much in advance!

    Yours,
    Boss


    MOD:
    I'v figured out the problem, browsing and reading a lot of topics... I needed to customize my phone, which isn't so trivial, when you read this alone, and nothing else. :D

    Thx anyway!
    Last edited by boss_hun; 06-14-2009 at 10:37 PM. Reason: solution found

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •