Patching CID53 (DB2020) and any CID (DB2010,DB2012)

[zylor]

here is a tutorial on how to use far+jdflasher
Flashing with jdflasher - Top Sony Forums
full flash your phone and try to do it again, by the way, what are you trying to do?

When trying to access oflash or ofl it gives me that error... what i was trying to do is the tutorial for converting k800i in k810i :(

[riders4sia]

did you have the latest jdflasher plugin? may be it's becoz of the plugin

[zylor]

I do have this version of the plugin:
jdflasher_text5fix2_cid53

Edit:
Fixed it!!! :D :D :D :D :D :D
Don't update to the latest build of jdflasher
Use the one included in this pack:
Far Manager with JDFlasher plugin.rar
From the tutorial:
Flash K800 CID53 with K810 software CID53 (for begginers)

This fixed the problem and the error is now gone for good!

Btw can anyone help me with patching?
Could anyone explain a newbie this tutorial in simple steps? 'cause the one on 1st page is kinda confusing :S



Could anyone explain a newbie this tutorial in simple steps? 'cause the one on 1st page is kinda confusing :S

I did update my firmware from k800i cid53 to k810i cid 53... and whenever i try to execute executor with anycid for k810i (R8BF003_CXC1250811_GENERIC_SM)
I get a message that the operation failed.. what do i have to do???????????

Edit:

ISSUE FIXED!

[riders4sia]

fully flashed it and try again

[Mobile Man]

I Have Done Every Step Of Patching But When I Was In Step No 10

Now you have opened bflash and bfs
10. Go to bflash and choose rest that we made at start

My Jdflasher Is Show This Maassage{On Picx**...& My Phone Get Turn On Autometicaly..


Now What To Do??

[MemorX]

Hi,

I am trying to patch a K810.

21:23:38| Baseband ID: 9900
21:23:38| Protocol Version: 3.1
21:23:38| Phone name detected!
21:23:38|
21:23:38| Profiling SEMC phone...
21:23:38| Platform: DB2020
21:23:38| OTP CID: 51
21:23:38| EROM CID: 53
21:23:38| EROM Color: Red
21:23:38| IMEI: 35612701xxxxxx
21:23:38| Phone ID: K810
21:23:38| Region: EUROPE_4
21:23:38| CDA: CDA102779/5 R4A
21:23:38| Firmware Version: R8BE001
21:23:38| EROM: R3A022
21:23:38| Ready for operation!

I have found almost all the files I need, except "executor.b", at least one for my firmware. Would someone be kind enough to tell me where I can find such a file? Couldent find one in the download section.

Or will I need to flash my phone with a firmware that matches the "executor.b" in anycid?

Thanks.

[riders4sia]

Hi,

I am trying to patch a K810.

21:23:38| Baseband ID: 9900
21:23:38| Protocol Version: 3.1
21:23:38| Phone name detected!
21:23:38|
21:23:38| Profiling SEMC phone...
21:23:38| Platform: DB2020
21:23:38| OTP CID: 51
21:23:38| EROM CID: 53
21:23:38| EROM Color: Red
21:23:38| IMEI: 35612701xxxxxx
21:23:38| Phone ID: K810
21:23:38| Region: EUROPE_4
21:23:38| CDA: CDA102779/5 R4A
21:23:38| Firmware Version: R8BE001
21:23:38| EROM: R3A022
21:23:38| Ready for operation!

I have found almost all the files I need, except "executor.b", at least one for my firmware. Would someone be kind enough to tell me where I can find such a file? Couldent find one in the download section.

Or will I need to flash my phone with a firmware that matches the "executor.b" in anycid?

Thanks.

i think that's the only way

[Mikki1993]

OK. I read tutorial, and something missed.

Did eny help for K770 ? Becaus SETOOL lite do not support ?

K770 lock. cid 53.

All proces flashing Main + Fs + Pach for corect versio. But when I have question remove patch "YES or NO" I click NO. Try also Yes BUT its same.


sorry for my english.

[juma007]

what is it when i aplicat quick access and my phone don'¨t want to start up

[EccTM]

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 :)