Debranding Mobile 3 K800 with generic Apac
Hi, I just Successfully Debranded a K800 using XS++
k800_r1je001_fs_hutch_1_red52.fbn k800_r1ej001_main_hutchison_wi_red52.mbn
Using Custpack: CDA102568/101 APAC Generic Asia & Pacific
(the closest I could get to CDA102511/83 EUROPE_2 Generic Australia)
My question is Successful Flash but now phone display and keypad won't light up like it used to, or it is delayed & sometimes refuses to light up
Is tjis a common occurence?
Thnx Burgs
Debranding vodafone K800i
Can anybody tell me how can i debarand my K800i from vodafone firmware to Asia (pakistan)
Re: Debranding Mobile 3 K800 with generic Apac
You need to flash your phone with generic main, adequate fs and custom pack!
Re: Debranding Mobile 3 K800 with generic Apac
Quote:
Originally Posted by
debeliz
You need to flash your phone with generic main, adequate fs and custom pack!
But looking thru the list it becomes confusing as to which one is best
Re: Debranding vodafone K800i
Don't know if this will help but take a look at this page then go to
Download & pick the appropriate one
Top Sony - Languages Description
Burgers:cool:
Re: Debranding Mobile 3 K800 with generic Apac
If you use a 3 branded firmware you must choose a 3 related cp (HUTCH_1 language/zone).
For APAC language you must flash with a generic firmware (no-brand) with APAC FS and with a generic cp APAC.
Re: Debranding Mobile 3 K800 with generic Apac
It takes 15 seconds to light up after I have pressed a key
Why is this SO? (Professor Julius Sumner Miller)
Re: Debranding Mobile 3 K800 with generic Apac
Not with 3 any more with optus australia and under no contract so do what I like?
Re: Debranding Mobile 3 K800 with generic Apac
Quote:
Originally Posted by
burgers
It takes 15 seconds to light up after I have pressed a key
Why is this SO? (Professor Julius Sumner Miller)
Have you changed the lighteffetct driver? Try to restore its from original
The path is: \TPA\PRESET\SYSTEM\lighteffect\systemeffects
Re: Debranding Mobile 3 K800 with generic Apac
- 1st I would like to know if your phone is CID49. The XS++ log should tell you that.
- you debranded your phone by flashing another BRANDED firmware k800_r1ej001_main_hutchison_wi_red52.mbn which kind of defeats the purpose
- if your phone is CID52, there are much newer firmware versions from the download area you can use
Re: Debranding Mobile 3 K800 with generic Apac
you know you're right once flashed CID 52 from CID 49 not wise... I was looking for a close resemblance for main generic unbranded firmware for Australia but D/L the wrong one. using R1EJOO1 CID 52 with CDA Hutchison 1 102568/101
Re: Debranding Mobile 3 K800 with generic Apac
Maybe you can tell from all the mumble in this extract:-
17:57:47| Hold 'C' button on phone and connect phone NOW.
17:57:47| You have 30 seconds...
17:57:47|
17:57:52| Baseband ID: 9900
17:57:52| Protocol Version: 3.1
17:57:52| Phone name detected!
17:57:52|
17:57:52| Profiling SEMC phone...
17:57:52| Platform: DB2020
17:57:52| OTP CID: 49
17:57:52| EROM CID: 52
17:57:52| EROM Color: Red
17:57:52| IMEI: 35170701xxxxxx
17:57:52| Phone ID: K800
17:57:52| Region: HUTCH_2
17:57:52| CDA: CDA102511/2 R6A
17:57:52| Firmware Version: R1JE001
17:57:52| EROM: R3A011
17:57:52| Ready for operation!
17:58:35| ~~~~~~~~~~ Custpack information ~~~~~~~~~~
17:58:35| Custpack: EUROPE_4 (CDA102511/101) (K800)
17:58:35| Generic(non-branded) custpack: Yes
17:58:35| Allowed languages: en, da, fi, is, sv, no,
17:58:35| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
17:58:43| ~~~~~~~~~~ Custpack information ~~~~~~~~~~
17:58:43| Custpack: APAC (CDA102568/101) (K800)
17:58:43| Generic(non-branded) custpack: No
17:58:43| Allowed languages: en, ms, id, tl, vi, zs,
17:58:43| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
17:58:50|
17:58:50| Sending db2020_cid01_prodid_p3j.bin...
17:58:50| Applet ID: 070129 0950 NGUCXC1250330_DB2020_PRODUCTIONIDLOADER_P3J
17:58:50| This is a PRODUCTION_ID loader
17:58:50|
17:58:50| Sending db2020_mem_patcher_cid52_r2a006.bin...
17:58:51| Applet ID: 061205 1523 HANCXC9876543210_DB2020_MEM_PATCHER_R2A006 0
17:58:51| This is a MEM_PATCHER loader
17:58:51|
17:58:51| Sending db2020_cid52red_flash_r2a005.bin...
17:58:51| Applet ID: 061201 1314 HANCXC1329129_DB2020_FLASHLOADER_R2A005
17:58:51| This is a FLASH loader
17:58:51| Now flashing firmware main...
17:59:00| Flashing d:\se debranding\current software\k800_r1ej001_main_hutchison_wi_red52.mbn
17:59:00| Header type: BABE
17:59:00| 455 flashblocks
18:02:43| Finishing flash
18:02:43| Done flashing
18:02:43| Now flashing filesystem...
18:02:43| Flashing d:\se debranding\current software\k800_r1je001_fs_hutch_1_red52.fbn
18:02:43| Header type: BABE
18:02:43| 225 flashblocks
18:04:33| Finishing flash
18:04:34| Done flashing
18:04:34|
18:04:34| Sending db2020_red52_cs_r3a009.bin...
18:04:35| Applet ID: 070410 1557 HANCXC1250562_DB2020_CSLOADER_R3A009
18:04:35| This is a CHIPSELECT loader
18:04:35| Activating loader...
18:04:35| Activating GDFS...
18:04:52| This loader is UNLOCKED
18:04:52| Success! CS-loader has been unlocked!
18:05:02| Uploading file /tpa/preset/custom/preloaded_config.xml
18:05:02| Done uploading
18:05:02| Uploading /files_to_upload to phone...
18:05:02| Sending shutdown command to phone...
18:05:02| Customizing was SUCCESSFUL!
18:05:02| Disconnecting phone...
18:05:02| You may now unplug your phone.
18:05:02| Flashing was successful
18:05:04| Disconnected... Unplug the phone
18:09:14| Shutting down...