Please see here for instructions on how to make a read out of your GDSF General Usage - XS++
FIRST STEPS TO FLASHING:
There are a few things you must check before flashing.
Firstly, what kind of Firmware (Software) do we need??? I will be flashing a K800 with K810 software (killing two birds with one stone shall we say
(You cannot just flash any phones Firmware into your phone though, as not all SE’s can be converted).
Secondly what CID#/Color does our Firmware need to be??? We can check this by simply connecting to XS++ and reading the phones information like below.
Note: When you connect a DB2020 phone to XS++, if the phone has an EROM CID or 49 or 51 it will ask you if you wish to update the EROM CID to 52, it’s best to say YES and flash with CID52 files, there are 2 reasons why its recommended, firstly, all the latest DB2020 Firmware’s are for CID52 only, the second reason is if you plan on patching the phone, you will need to be CID52.
QUOTE
21:33:04| XS++ v3.1 (Darwin) Ready !
21:33:04| Executed on Microsoft Windows Vista
21:33:17|
21:33:17| Attempting to open the interface...
21:33:17|
21:33:17| TURN OFF PHONE!
21:33:17| Hold 'C' button on phone and connect phone NOW.
21:33:17| You have 30 seconds...
21:33:17|
21:33:22| Baseband ID: 9900
21:33:22| Protocol Version: 3.1
21:33:22| Warning: IMEI name does not match GDFS name (IMEI:K800 GDFS:K810)
21:33:22| ...using IMEI name
21:33:22|
21:33:22| Profiling SEMC phone...
21:33:22| Platform: DB2020
21:33:22| OTP CID: 49
21:33:22| EROM CID: 52
21:33:22| EROM Color: Red
21:33:22| IMEI: 35170801xxxxxx
21:33:22| Phone ID: K800
21:33:22| Region: EUROPE_2
21:33:22| CDA: CDA102568/200 R2A
21:33:22| Firmware Version: R8BA024
21:33:22| EROM: R3A011
21:33:22| Ready for operation!
21:33:24|
21:33:24| Sending db2020_cid01_prodid_p3j.bin...
21:33:25| Applet ID: 070129 0950 NGUCXC1250330_DB2020_PRODUCTIONIDLOADER_P3J
21:33:25| This is a PRODUCTION_ID loader
21:33:25|
21:33:25| Sending db2020_mem_patcher_cid52_r2a006.bin...
21:33:25| Applet ID: 061205 1523 HANCXC9876543210_DB2020_MEM_PATCHER_R2A006 0
21:33:25| This is a MEM_PATCHER loader
21:33:25|
21:33:25| Sending db2020_cid52red_flash_r2a005.bin...
21:33:25| Applet ID: 061201 1314 HANCXC1329129_DB2020_FLASHLOADER_R2A005
21:33:25| This is a FLASH loader
21:33:25| Sendinging shutdown signal to phone...
21:33:25| Done.. You may now connect again...
21:33:25| Shutting down...
21:33:04| Executed on Microsoft Windows Vista
21:33:17|
21:33:17| Attempting to open the interface...
21:33:17|
21:33:17| TURN OFF PHONE!
21:33:17| Hold 'C' button on phone and connect phone NOW.
21:33:17| You have 30 seconds...
21:33:17|
21:33:22| Baseband ID: 9900
21:33:22| Protocol Version: 3.1
21:33:22| Warning: IMEI name does not match GDFS name (IMEI:K800 GDFS:K810)
21:33:22| ...using IMEI name
21:33:22|
21:33:22| Profiling SEMC phone...
21:33:22| Platform: DB2020
21:33:22| OTP CID: 49
21:33:22| EROM CID: 52
21:33:22| EROM Color: Red
21:33:22| IMEI: 35170801xxxxxx
21:33:22| Phone ID: K800
21:33:22| Region: EUROPE_2
21:33:22| CDA: CDA102568/200 R2A
21:33:22| Firmware Version: R8BA024
21:33:22| EROM: R3A011
21:33:22| Ready for operation!
21:33:24|
21:33:24| Sending db2020_cid01_prodid_p3j.bin...
21:33:25| Applet ID: 070129 0950 NGUCXC1250330_DB2020_PRODUCTIONIDLOADER_P3J
21:33:25| This is a PRODUCTION_ID loader
21:33:25|
21:33:25| Sending db2020_mem_patcher_cid52_r2a006.bin...
21:33:25| Applet ID: 061205 1523 HANCXC9876543210_DB2020_MEM_PATCHER_R2A006 0
21:33:25| This is a MEM_PATCHER loader
21:33:25|
21:33:25| Sending db2020_cid52red_flash_r2a005.bin...
21:33:25| Applet ID: 061201 1314 HANCXC1329129_DB2020_FLASHLOADER_R2A005
21:33:25| This is a FLASH loader
21:33:25| Sendinging shutdown signal to phone...
21:33:25| Done.. You may now connect again...
21:33:25| Shutting down...
See how I’ve highlighted a few lines in my XS++ log file, the orange line where it says my IMEI name does not match the GDSF name, don’t worry about that... the chances are it will say that on a phone that’s just rolled out the factory
The next highlighted line states the OTP CID#, we take absolutely no notice to this one, DON’T let it confuse you...
And the next highlighted line is an important one, the EROM CID#, in my case its 52, my Firmware MUST match that number....
And the last highlighted line is also an important one, EROM Color, in my case the phones certificate color is red (will be red in most cases), my Firmware MUST also match this color...
So now we know that the Firmware we need must be K810 RED52 we need to find our files 3 in total....
We need a Main Firmware File, an FS Firmware File and a Cust Pack to Customize the phone after flashing, I’m going to choose R8BA024 Firmware as its the latest and most moddable K810 Firmware version, I also need to select a Firmware Region, I live in the UK so I will be using a “Europe 2” Firmware set, and the Main Firmware File to match that is a Main Generic, and the Cust Pack I will be using is “CDA102568_11_R8A_GENERIC_EUROPE_2” which is a K810 Generic Europe 2 Cust Pack (This should match your phone’s FS Firmware File that you will be flashing with).......
There is an easy way to determine which firmware region you already have which will help you determine which files you need, this is by tacking note or the selectable languages while writing sms (Please refer to topsony language list for more info), some phones will state the Region in the phones Service Menu (and the current CDA), from the home screen press >*<<*<* then select “Service Info then Software Info”.
So the 3 files I will be flashing with are (Notice where it says RED52 at the end of the two Firmwae Files.... EROM Color = RED..... EROM CID = 52):
Main Firmware: K810_R8BA024_MAIN_GENERIC_SM_RED52.mbn
FS Firmware: K810_R8BA024_FS_EUROPE_2_RED52.fbn
Cust Pack: CDA102568_11_R8A_GENERIC_EUROPE_2.rar
So now I know which Firmware files I will be flashing the phone with let’s get started (backup any important data as it will ALL be lost while flashing).
Flashing with jdflasher.
(we’ll be covering flashing/K800 – K810 conversion and patching in this tutorial).
To set up jdflasher please look here = General Usage - jdflasher or here jdflasher
Start up Far Manager and press Alt+F1 then 4 to stat jdflasher plugin, and you should be presented with this screen.

In the Script section choose your phone model, I’m using DB2020 (K800), in the port section choose your cable type, I’m using DCU-60 (standard USB lead that comes with the phone), in the speed section select the highest available (921600
Now that we have set up jdflasher to be used with our phone press jump down into the large rabbit-hole, you should now see a screen that looks like this.

Connect your phone in the usual way, remove battery, sim card and memory card, insert the battery and press and hold the “C” button down on your phone and connect your USB lead to the phone, you should now see a screen that looks like this.

Because we are just flashing our phone we need to select “oflash” and you’ll come to a screen that looks like this (some phones will be prompted to remove the battery and reconnect to jdflasher (i.e. CID49 DB2010, just follow the on screen instructions given by jdflasher (explained in the General Usage – jdflasher thread)).
(Some phone you can press “bflash” but since we are flashing DB2020, if we do that we’ll end up bypassing security which is not needed (we’ll come to that in the patching section)).

I’ve already browsed to the Firmware files that I’ll be flashing with (see right window), if you haven’t then do so now.
Now move the cursor over your Main firmware file and press F5-copy (or you can use your mouse to drag firmware file over to the left window), now you’ll see a screen like this.
(If you have a DB2020 and plan on applying QAPatch, skip flashing Main as we do that again while applying the QAPatch)

Press copy and you’ll come to a screen like this.

We need to select flash as babe (it should be set as babe by default, but check just incase), then press “yeah flash it” lol mint.
After press flash the flashing process will begin and you’ll see a screen that looks like this.

Once the Main firmware file has finished flashing, repeat the process with the FS firmware file.

Now we have successfully flashed our phone, we need to upload a cust pack (or we will get the “Configuration Error Please Contact Your Service Provider” error message that worrys people so much lol), DO NOT SWITCH THE PHONE ON!!!
Ok you should already have read the General Usage – jdflasher thread (if you haven’t then do so now as it will explain how to upload files to the Internal FS i.e. your Cust Pack).
Connect your phone to jdflasher and browse to dir “/tpa/preset/custom”, this is where we place our Cust Pack, most cust packs come with lots of files named “FM_SOUNDS_HOOK_3.itm” and so on, these to me are useless
(Some Network Provider’s now require a unique Pass and Username now like T-Mobile UK, if your network requires these then the preloaded_config.xml file is also useless)
Highlight the Customize.xml file and press F5-Copy (its best to press F5 to copy this file or it has a tendency to copy to doja or drm lol).
Your phone should now look like this.

Now press “..” to move to the root or the Internal FS until jdflasher ask’s you if you would like to shut down CSLoader, select yes (if you are using CID49 DB2010 you will also be asked if you would like to restore firmware, select yes and that will flash rest file for you).
Now the phone is completely flashed and is safe to exit jdflasher and switch on the phone.
If you are converting your K800 to K810 than we also need to upload some K800 Light Effects or our KeyPad won’t light up correctly.
Upload the K800 light effects to “/tpa/preset/system/lighteffect/systemeffects/” (just replace the current light effects with the new ones).

When you first switch your phone after flashing, the phone will initialize and you will see a please wait screen spear, once the loading bar has finished then the phone is ready to use.

















