I think I just bit myself in the... W580i

I tried to flash my w580i with the following in Setool2lite...

Files> W580_R6BC002_FS_AMERICA_2_RED52.fbn
Files> W580_R6BC002_MAIN_GENERIC_LA_RED52.mbn
MISC files> HB1-06_Gen_CDA102568_107_R8A_GENERIC_AMERICA_2

however, when I turn on my phone the screen is reeeeeally distorted. On power on, the sony ericsson logo (green ball) is cut in half. Bottom half is lined up to the top and the top half is lined up to the bottom line. "Sony Ericsson" is in the middle, and all of this is elongated vertically.

When it loads to the menu I can barely see what's going on. Everything is transparent, elongated vertically, and overlapping making it impossible to read/do anything. By searching around I assume I messed up the EROM. How do I know if this is the case?

If I did indeed do that, which CID did I have originally?

Oy vay...:(


[EDIT]
Here's the code from Setool...

Code:

---

CDA:CDA102568/107
MODEL:HB1-06 Gen
VARIANT:AMERICA_2
LANGUAGE: EN
LANGUAGE: PB
LANGUAGE: XL

ChipID:9900,EMP protocol:0301
PHONE IS RED RETAIL PRODUCT
FLASH CID detected:52
Speed:921600
OTP LOCKED:1 CID:51 PAF:1 IMEI:XXXX CERT:RED
FLASH CID:52 COLOR:RED
LDR:061201 1314 HANCXC1329129_DB2020_FLASHLOADER_R2A005
Flash ID check:897E
Flash props sent ok
writing C:\Users\ONS\Desktop\W580_R6BC002_FS_AMERICA_2_RED52.fbn
CURRENT FLASH FILE CID:52
SSW uses complete hash, hash len is:4180
Will flash 209 blocks...
SSW loading returns:0
writing C:\Users\ONS\Desktop\W580_R6BC002_MAIN_GENERIC_LA_RED52.mbn
CURRENT FLASH FILE CID:52
SSW uses complete hash, hash len is:9200
Will flash 460 blocks...
SSW loading returns:0
CSloader version:
070410 1557 HANCXC1250562_DB2020_CSLOADER_R3A009
loader startup: executed
loader filesystem startup: executed
loader GDFS startup: executed
Writing package...
Directory: tpa/preset/custom/
CONTENT_DOWNLOAD_HOOK.itm (10240)
Customize.xml (1316)
FM_PICTURES_HOOK_3.itm (10240)
FM_SOUNDS_HOOK_3.itm (10240)
FM_THEMES_HOOK_3.itm (10240)
FM_VIDEOS_HOOK_3.itm (10240)
GAMES_HOOK_3.itm (10240)
MEDIA_PLAYER_HOOK_3.itm (10240)
ORG_APPLICATIONS_HOOK_3.itm (10240)
preloaded_config.xml (148713)
SETT_RINGTONE_HOOK_1.itm (10240)
SETT_SCREENSAVER_HOOK_1.itm (10240)
SETT_STARTSHOW_HOOK_1.itm (10240)
SETT_WALLPAPER_HOOK_1.itm (10240)
VIDEO_PLAYER_HOOK_1.itm (10240)
Phone detached
Elapsed:419 secs.

---

Try to reflash just main again , maybe help

Where can I download the MISC files?

In Setool 2Lite, you must put MAIN first and FS second !

And if that doesn't work, use XS++

Quote:

---

Try to reflash just main again , maybe help

---

tried, no luck

Quote:

---

In Setool 2Lite, you must put MAIN first and FS second !

---

I tried that, still no good.

Quote:

---

And if that doesn't work, use XS++

---

What's the difference??





Am I using the wrong CID or something?

I also didn't back up the GDFS. Could that be the problem?
What does GDFS stand for?

Quote:

---

Originally Posted by Rogue7

I also didn't back up the GDFS. Could that be the problem?
What does GDFS stand for?

---

Connect your phone with XS++ and post log here

Quote:

---

Originally Posted by Rogue7

I also didn't back up the GDFS. Could that be the problem?
What does GDFS stand for?

---

I think you should ask this question before start modding.

Quote:

---

Originally Posted by Rogue7

I also didn't back up the GDFS. Could that be the problem?
What does GDFS stand for?

---

GDFS:This is the phones "stash", where all settings and calibration data is stored (this also goes for the firmwares IMEI-resource as well as the SIMlocks). Similar to other brands use of NVRAM (Non-Viotile Random Access Memory).

Nice day

Quote:

---

Originally Posted by Rogue7

What's the difference??

---

XS++ has been updated more recently I believe. Also, I get the impression it is much more widely used for flashing firmware. I think you will be able to get more help if you still have problems after using it. Try it out and post log SeaMonkey said

I'm in the process of doing this in xs++, however I noticed in the log that my OTP CID is 51, but my EROM CID is 52. Could this be causing the problem?

I was following the steps in the tutorial but noticed that the custom pack is quoted as being a k700. How did that happen? I didn't go any further than step IV. 2. at this tutorial XS++ 2.x Guide - Top Sony Forums because I'm afraid of what the log entails about the wrong recognition of my model nuumber.
And I definitely used the w580 files from this site.

Code:

---

17:11:14| XS++ v3.1 (Darwin) Ready !

17:11:14| Executed on Microsoft Windows Vista

17:13:06|

17:13:06| Attempting to open the interface...

17:13:06|

17:13:06| TURN OFF PHONE!

17:13:06| Hold 'C' button on phone and connect phone NOW.

17:13:06| You have 30 seconds...

17:13:06|

17:13:16| Baseband ID: 9900

17:13:16| Protocol Version: 3.1

17:13:16| Warning: IMEI name does not match GDFS name (IMEI:NULL GDFS:K700)

17:13:16| ...using GDFS name

17:13:16|

17:13:17| Profiling SEMC phone...

17:13:17| Platform: DB2020

17:13:17| OTP CID: 51

17:13:17| EROM CID: 52

17:13:17| EROM Color: Red

17:13:17| IMEI: 01157200xxxxxx

17:13:17| Phone ID: K700

17:13:17| Region: AMERICA_1

17:13:17| CDA: CDA102568/107  R8A

17:13:17| Firmware Version: R6BC002

17:13:17| EROM: R3A022

17:13:17| Ready for operation!

17:13:31|

17:13:31| Sending db2020_cid01_prodid_p3j.bin...

17:13:31| Applet ID: 070129 0950 NGUCXC1250330_DB2020_PRODUCTIONIDLOADER_P3J

17:13:31| This is a PRODUCTION_ID loader

17:13:31|

17:13:31| Sending db2020_mem_patcher_cid52_r2a006.bin...

17:13:32| Applet ID: 061205 1523 HANCXC9876543210_DB2020_MEM_PATCHER_R2A006 0

17:13:32| This is a MEM_PATCHER loader

17:13:32|

17:13:32| Sending db2020_red52_cs_r3a009.bin...

17:13:34| Applet ID: 070410 1557 HANCXC1250562_DB2020_CSLOADER_R3A009

17:13:34| This is a CHIPSELECT loader

17:13:34| Activating loader...

17:13:34| Activating GDFS...

17:13:53| This loader is UNLOCKED

17:13:53| Backing up the GDFS...

17:13:55| Stated variables: 1225

17:14:00| Variables found: 1179

17:14:00| Variables found: 46

17:14:00| Wrote backup to .\Backup\K700_01157200xxxxxx_GDFS_BACKUP.bin

17:14:00| GDFS was backed up successfully!

17:14:00| GDFS operation was successful

17:14:02| Disconnected... Unplug the phone

17:19:16|

17:19:16| Attempting to open the interface...

17:19:16|

17:19:16| TURN OFF PHONE!

17:19:16| Hold 'C' button on phone and connect phone NOW.

17:19:16| You have 30 seconds...

17:19:16|

17:19:28| Did not receive 0x5a. Continuing

17:19:39| Disconnected... Unplug the phone

17:19:45|

17:19:45| Attempting to open the interface...

17:19:45|

17:19:45| TURN OFF PHONE!

17:19:45| Hold 'C' button on phone and connect phone NOW.

17:19:45| You have 30 seconds...

17:19:45|

17:19:52| Did not receive 0x5a. Continuing

17:20:40| Disconnected... Unplug the phone

17:21:28|

17:21:28| Attempting to open the interface...

17:21:28|

17:21:28| TURN OFF PHONE!

17:21:28| Hold 'C' button on phone and connect phone NOW.

17:21:28| You have 30 seconds...

17:21:28|

17:21:49| Baseband ID: 9900

17:21:49| Protocol Version: 3.1

17:21:49| Warning: IMEI name does not match GDFS name (IMEI:NULL GDFS:W580)

17:21:49| ...using GDFS name

17:21:49|

17:21:49| Profiling SEMC phone...

17:21:49| Platform: DB2020

17:21:49| OTP CID: 51

17:21:49| EROM CID: 52

17:21:49| EROM Color: Red

17:21:49| IMEI: 01157200xxxxxx

17:21:49| Phone ID: W580

17:21:49| Region: AMERICA_1

17:21:49| CDA: CDA102568/107  R8A

17:21:49| Firmware Version: R6BC002

17:21:49| EROM: R3A022

17:21:49| Ready for operation!

17:22:11| ~~~~~~~~~~ Custpack information ~~~~~~~~~~

17:22:11| Custpack: EMEA_3 (CDA102286/10) (K700)

17:22:11| Generic(non-branded) custpack: Yes

17:22:11| Allowed languages: en, el, sq,

17:22:11| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

17:22:53|

17:22:53| Sending db2020_cid01_prodid_p3j.bin...

17:22:53| Applet ID: 070129 0950 NGUCXC1250330_DB2020_PRODUCTIONIDLOADER_P3J

17:22:53| This is a PRODUCTION_ID loader

17:22:53|

17:22:53| Sending db2020_mem_patcher_cid52_r2a006.bin...

17:22:54| Applet ID: 061205 1523 HANCXC9876543210_DB2020_MEM_PATCHER_R2A006 0

17:22:54| This is a MEM_PATCHER loader

17:22:54|

17:22:54| Sending db2020_cid52red_flash_r2a005.bin...

17:22:54| Applet ID: 061201 1314 HANCXC1329129_DB2020_FLASHLOADER_R2A005

17:22:54| This is a FLASH loader

17:22:54| Sendinging shutdown signal to phone...

17:22:54| Done.. You may now connect again...

17:22:54| Shutting down...

---

@Rogue7
OTP CID is 51, but my EROM CID is 52. Could this be causing the problem?

No , your CID is 52 so you have correct files . Use XS++ for flashing and add MAIN & FS in
ADD section and CUSTPACK unpack and put folder "tpa" in XS folder "own custpack".
In XS++ in section customization select "own custpack" and when you have all this done press flash (that should be work)

Flashed it with XS++
Still giving me the same problem with the screen.

Log...

Code:

---

10:02:39| XS++ v3.1 (Darwin) Ready !

10:02:39| Executed on Microsoft Windows Vista

10:02:45|

10:02:45| Attempting to open the interface...

10:02:45|

10:02:45| TURN OFF PHONE!

10:02:45| Hold 'C' button on phone and connect phone NOW.

10:02:45| You have 30 seconds...

10:02:45|

10:02:51| Baseband ID: 9900

10:02:51| Protocol Version: 3.1

10:02:51| Warning: IMEI name does not match GDFS name (IMEI:NULL GDFS:W580)

10:02:51| ...using GDFS name

10:02:51|

10:02:51| Profiling SEMC phone...

10:02:51| Platform: DB2020

10:02:51| OTP CID: 51

10:02:51| EROM CID: 52

10:02:51| EROM Color: Red

10:02:51| IMEI: 01157200xxxxxx

10:02:51| Phone ID: W580

10:02:51| Region: AMERICA_1

10:02:51| CDA: CDA102568/107  R8A

10:02:51| Firmware Version: R6BC002

10:02:51| EROM: R3A022

10:02:51| Ready for operation!

10:02:58| ~~~~~~~~~~ Custpack information ~~~~~~~~~~

10:02:58| Custpack: AMERICA_2 (CDA102460/101) (K510)

10:02:58| Generic(non-branded) custpack: Yes

10:02:58| Allowed languages: en, pb, xl,

10:02:58| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

10:03:21|

10:03:21| Sending db2020_cid01_prodid_p3j.bin...

10:03:21| Applet ID: 070129 0950 NGUCXC1250330_DB2020_PRODUCTIONIDLOADER_P3J

10:03:21| This is a PRODUCTION_ID loader

10:03:21|

10:03:21| Sending db2020_mem_patcher_cid52_r2a006.bin...

10:03:22| Applet ID: 061205 1523 HANCXC9876543210_DB2020_MEM_PATCHER_R2A006 0

10:03:22| This is a MEM_PATCHER loader

10:03:22|

10:03:22| Sending db2020_cid52red_flash_r2a005.bin...

10:03:22| Applet ID: 061201 1314 HANCXC1329129_DB2020_FLASHLOADER_R2A005

10:03:22| This is a FLASH loader

10:03:22| Now flashing firmware main...

10:03:23| Flashing c:\users\oons\desktop\try 1\w580_r6bc002_main_generic_la_red52.mbn

10:03:23| Header type: BABE

10:03:23| 460 flashblocks

10:07:17| Finishing flash

10:07:17| Done flashing

10:07:17| Now flashing filesystem...

10:07:17| Flashing c:\users\oons\desktop\try 1\w580_r6bc002_fs_america_2_red52.fbn

10:07:17| Header type: BABE

10:07:17| 209 flashblocks

10:09:02| Finishing flash

10:09:03| Done flashing

10:09:03|

10:09:03| Sending db2020_red52_cs_r3a009.bin...

10:09:05| Applet ID: 070410 1557 HANCXC1250562_DB2020_CSLOADER_R3A009

10:09:05| This is a CHIPSELECT loader

10:09:05| Activating loader...

10:09:05| Activating GDFS...

10:09:26| This loader is UNLOCKED

10:09:26| Success! CS-loader has been unlocked!

10:09:26| Uploading customization files to phone...

10:09:26| Upload ./own_custpack/tpa/preset/custom/CONTENT_DOWNLOAD_HOOK.itm to tpa/preset/custom/CONTENT_DOWNLOAD_HOOK.itm

10:09:26| Activating filesystem

10:09:48| Creating directory tpa

10:09:48| Creating directory tpa/preset

10:09:48| Creating directory tpa/preset/custom

10:09:48| Deleting file tpa/preset/custom/CONTENT_DOWNLOAD_HOOK.itm

10:09:48| Deleted...OK!

10:09:48| Uploading file tpa/preset/custom/CONTENT_DOWNLOAD_HOOK.itm

10:09:48| Done uploading

10:09:48| Upload ./own_custpack/tpa/preset/custom/Customize.xml to tpa/preset/custom/Customize.xml

10:09:48| Creating directory tpa

10:09:48| Creating directory tpa/preset

10:09:48| Creating directory tpa/preset/custom

10:09:48| Deleting file tpa/preset/custom/Customize.xml

10:09:48| Deleted...OK!

10:09:48| Uploading file tpa/preset/custom/Customize.xml

10:09:48| Done uploading

10:09:48| Upload ./own_custpack/tpa/preset/custom/FM_PICTURES_HOOK_3.itm to tpa/preset/custom/FM_PICTURES_HOOK_3.itm

10:09:48| Creating directory tpa

10:09:48| Creating directory tpa/preset

10:09:48| Creating directory tpa/preset/custom

10:09:48| Deleting file tpa/preset/custom/FM_PICTURES_HOOK_3.itm

10:09:48| Deleted...OK!

10:09:48| Uploading file tpa/preset/custom/FM_PICTURES_HOOK_3.itm

10:09:48| Done uploading

10:09:48| Upload ./own_custpack/tpa/preset/custom/FM_SOUNDS_HOOK_3.itm to tpa/preset/custom/FM_SOUNDS_HOOK_3.itm

10:09:48| Creating directory tpa

10:09:48| Creating directory tpa/preset

10:09:48| Creating directory tpa/preset/custom

10:09:48| Deleting file tpa/preset/custom/FM_SOUNDS_HOOK_3.itm

10:09:48| Deleted...OK!

10:09:48| Uploading file tpa/preset/custom/FM_SOUNDS_HOOK_3.itm

10:09:48| Done uploading

10:09:48| Upload ./own_custpack/tpa/preset/custom/FM_THEMES_HOOK_3.itm to tpa/preset/custom/FM_THEMES_HOOK_3.itm

10:09:48| Creating directory tpa

10:09:49| Creating directory tpa/preset

10:09:49| Creating directory tpa/preset/custom

10:09:49| Deleting file tpa/preset/custom/FM_THEMES_HOOK_3.itm

10:09:49| Deleted...OK!

10:09:49| Uploading file tpa/preset/custom/FM_THEMES_HOOK_3.itm

10:09:51| Done uploading

10:09:51| Upload ./own_custpack/tpa/preset/custom/FM_VIDEOS_HOOK_3.itm to tpa/preset/custom/FM_VIDEOS_HOOK_3.itm

10:09:51| Creating directory tpa

10:09:51| Creating directory tpa/preset

10:09:51| Creating directory tpa/preset/custom

10:09:51| Deleting file tpa/preset/custom/FM_VIDEOS_HOOK_3.itm

10:09:51| Deleted...OK!

10:09:51| Uploading file tpa/preset/custom/FM_VIDEOS_HOOK_3.itm

10:09:51| Done uploading

10:09:51| Upload ./own_custpack/tpa/preset/custom/GAMES_HOOK_3.itm to tpa/preset/custom/GAMES_HOOK_3.itm

10:09:51| Creating directory tpa

10:09:51| Creating directory tpa/preset

10:09:51| Creating directory tpa/preset/custom

10:09:51| Deleting file tpa/preset/custom/GAMES_HOOK_3.itm

10:09:51| Deleted...OK!

10:09:51| Uploading file tpa/preset/custom/GAMES_HOOK_3.itm

10:09:51| Done uploading

10:09:51| Upload ./own_custpack/tpa/preset/custom/MEDIA_PLAYER_HOOK_3.itm to tpa/preset/custom/MEDIA_PLAYER_HOOK_3.itm

10:09:51| Creating directory tpa

10:09:51| Creating directory tpa/preset

10:09:51| Creating directory tpa/preset/custom

10:09:51| Deleting file tpa/preset/custom/MEDIA_PLAYER_HOOK_3.itm

10:09:51| Deleted...OK!

10:09:51| Uploading file tpa/preset/custom/MEDIA_PLAYER_HOOK_3.itm

10:09:51| Done uploading

10:09:51| Upload ./own_custpack/tpa/preset/custom/ORG_APPLICATIONS_HOOK_3.itm to tpa/preset/custom/ORG_APPLICATIONS_HOOK_3.itm

10:09:51| Creating directory tpa

10:09:51| Creating directory tpa/preset

10:09:51| Creating directory tpa/preset/custom

10:09:51| Deleting file tpa/preset/custom/ORG_APPLICATIONS_HOOK_3.itm

10:09:52| Deleted...OK!

10:09:52| Uploading file tpa/preset/custom/ORG_APPLICATIONS_HOOK_3.itm

10:09:52| Done uploading

10:09:52| Upload ./own_custpack/tpa/preset/custom/preloaded_config.xml to tpa/preset/custom/preloaded_config.xml

10:09:52| Creating directory tpa

10:09:52| Creating directory tpa/preset

10:09:52| Creating directory tpa/preset/custom

10:09:52| Deleting file tpa/preset/custom/preloaded_config.xml

10:09:52| Deleted...OK!

10:09:52| Uploading file tpa/preset/custom/preloaded_config.xml

10:09:53| Done uploading

10:09:53| Upload ./own_custpack/tpa/preset/custom/SETT_RINGTONE_HOOK_1.itm to tpa/preset/custom/SETT_RINGTONE_HOOK_1.itm

10:09:53| Creating directory tpa

10:09:53| Creating directory tpa/preset

10:09:53| Creating directory tpa/preset/custom

10:09:53| Deleting file tpa/preset/custom/SETT_RINGTONE_HOOK_1.itm

10:09:53| Deleted...OK!

10:09:53| Uploading file tpa/preset/custom/SETT_RINGTONE_HOOK_1.itm

10:09:53| Done uploading

10:09:53| Upload ./own_custpack/tpa/preset/custom/SETT_SCREENSAVER_HOOK_1.itm to tpa/preset/custom/SETT_SCREENSAVER_HOOK_1.itm

10:09:53| Creating directory tpa

10:09:53| Creating directory tpa/preset

10:09:53| Creating directory tpa/preset/custom

10:09:53| Deleting file tpa/preset/custom/SETT_SCREENSAVER_HOOK_1.itm

10:09:53| Deleted...OK!

10:09:53| Uploading file tpa/preset/custom/SETT_SCREENSAVER_HOOK_1.itm

10:09:54| Done uploading

10:09:54| Upload ./own_custpack/tpa/preset/custom/SETT_STARTSHOW_HOOK_1.itm to tpa/preset/custom/SETT_STARTSHOW_HOOK_1.itm

10:09:54| Creating directory tpa

10:09:54| Creating directory tpa/preset

10:09:54| Creating directory tpa/preset/custom

10:09:54| Deleting file tpa/preset/custom/SETT_STARTSHOW_HOOK_1.itm

10:09:54| Deleted...OK!

10:09:54| Uploading file tpa/preset/custom/SETT_STARTSHOW_HOOK_1.itm

10:09:54| Done uploading

10:09:54| Upload ./own_custpack/tpa/preset/custom/SETT_WALLPAPER_HOOK_1.itm to tpa/preset/custom/SETT_WALLPAPER_HOOK_1.itm

10:09:54| Creating directory tpa

10:09:54| Creating directory tpa/preset

10:09:54| Creating directory tpa/preset/custom

10:09:54| Deleting file tpa/preset/custom/SETT_WALLPAPER_HOOK_1.itm

10:09:54| Deleted...OK!

10:09:54| Uploading file tpa/preset/custom/SETT_WALLPAPER_HOOK_1.itm

10:09:54| Done uploading

10:09:54| Upload ./own_custpack/tpa/preset/custom/VIDEO_PLAYER_HOOK_1.itm to tpa/preset/custom/VIDEO_PLAYER_HOOK_1.itm

10:09:54| Creating directory tpa

10:09:54| Creating directory tpa/preset

10:09:54| Creating directory tpa/preset/custom

10:09:54| Deleting file tpa/preset/custom/VIDEO_PLAYER_HOOK_1.itm

10:09:54| Deleted...OK!

10:09:54| Uploading file tpa/preset/custom/VIDEO_PLAYER_HOOK_1.itm

10:09:54| Done uploading

10:09:54| Uploading /files_to_upload to phone...

10:09:54| Sending shutdown command to phone...

10:09:54| Customizing was SUCCESSFUL!

10:09:54| Disconnecting phone...

10:09:54| You may now unplug your phone.

10:09:54| Flashing was successful

10:09:56| Disconnected... Unplug the phone

10:11:19| Shutting down...

---

@Rogue7
Please upload Setol LOG, xs++ almost always shows IMEI MISSMATCH, most of it is not ;)
Regards

Quote:

---

Originally Posted by EdgPaez

@Rogue7
Please upload Setol LOG, xs++ almost always shows IMEI MISSMATCH, most of it is not ;)
Regards

---

I did upload the Setool log (that's the first log in the first post)

I think I might have found the problem. Although I'm not sure how to fix it.
The XS++ log in post #15 shows the following line of code when I load my custom pack...

Code:

---

10:02:58| Custpack: AMERICA_2 (CDA102460/101) (K510)

---

I believe the custom pack is wrong because it states K510. However I have a W580.
When I looked up the K510 i found that it's native resolution is 128x160 pixels, but my W580's native resolution is 240x320 pixels. This might explain why my screen is distorted and stretched.

But I'm confused as to how to fix this. The custompack I used is straight from this site and is labeled w580. Is the custompack on this site wrong?

Quote:

---

Originally Posted by Rogue7

I think I might have found the problem. Although I'm not sure how to fix it.
The XS++ log in post #15 shows the following line of code when I load my custom pack...

Code:

---

10:02:58| Custpack: AMERICA_2 (CDA102460/101) (K510)

---

I believe the custom pack is wrong because it states K510. However I have a W580.
When I looked up the K510 i found that it's native resolution is 128x160 pixels, but my W580's native resolution is 240x320 pixels. This might explain why my screen is distorted and stretched.

But I'm confused as to how to fix this. The custompack I used is straight from this site and is labeled w580. Is the custompack on this site wrong?

---

You didn't choose your phone in Setool ,stayed k510 so try change to your phone and upload custpack one more time.If that don'work you need one more time do full flash but this time be very carefully

Quote:

---

Originally Posted by seamonkey

You didn't choose your phone in Setool ,stayed k510 so try change to your phone and upload custpack one more time.If that don'work you need one more time do full flash but this time be very carefully

---

I'm pretty sure I did. Even so, I did it again (in SEtool) making sure that w580 was selected, and I still have this screen problem. How does doing one more flash fix this? I've flashed this bugger at least 7 times now.

Try this cust : 4shared.com - online file sharing and storage - download w580_CDA102568_107_R8A_GENERIC_AMERICA_2.zip

Quote:

---

Originally Posted by SaNdSuKkA

Try this cust : 4shared.com - online file sharing and storage - download w580_CDA102568_107_R8A_GENERIC_AMERICA_2.zip

---

still not working... worst part is this phone is a gift for my gf.

[EDIT]
navigating through the options, I found that the phone status states it is a W580i.
I'm lost as to what's wrong with it.

I found some other threads with the same issue on some other forums. This is what seems to be the problem/fix.

Quote:

---

OK, I finally got it, at least for now, thanks to (roys89). It's the display driver error. What I did was using XS++, then FSX, then start FSX, then /your phone/ifs/settings/display, at there u should see dispdriver0.dat. Now that's the driver I replaced using w910 display driver which can be found at RapidShare: Easy Filehosting

after the download, extract the file, go to Systems\W910_R1CA031\ifs\settings\display\dispdriv er0.dat. Now drag this dispdriver0 in the XS++ and replace the old one. click shut down, unplug the phone. The phone should be good to go now.

again, credit goes to roys89.

note-the phone freeze when trying to access the camera, but it's still heck alot better than a broken screen.

---

I'm going to try this now. Although I wish I could find the w580i display driver to still have a working camera.

Link to other threads...
Pleas Help - SE-NSE Forums
Debranded W580i: Graphics=WTF HELP? [I TOOK PICS] - SE-NSE Forums

It worked with a simple flash of the right firmware version. For me it was the R8BE001_RED52.

Thanks to all!!!!!!

So what were you doing wrong?

Did you end up using XS++? Did you customize using FSX?

I did find the display driver for the w580i online and tried to replace it with FSX through XS++. The replacement worked, but that didn't fix the problem. I guess the problem is, that on the W580i, you cannot switch firmware versions. I didn't know which version I had originally, but I tried them all and R8BE001_RED52 was the one that worked for me.

I used Setool btw, xs++ was giving me trouble with swaping the custom pack files into it's directory folder.

having the same problem, i can't seem to downgrade my w580i from R8BE001 to R6BC002 :( screen is ****ed up, i want to downgrade because of the light bug in R8BE001

sorry for the double post but i found out why our screens mess up...

it seems that in the older versions of the w580i they used another display driver. so if you bought your phone with R8BE001 you cannot "downgrade" but i think it's possible to flash the old firmware and then flash the display driver from the new firmware in the old firmware. i might try it when i have some time :)

w580i light bug fix - Top Sony Forums

it worked :D

Setool 2Lite & XS++ support DB3150?

Quote:

---

Originally Posted by bril202003

Setool 2Lite & XS++ support DB3150?

---

No. No free tool for now supports db3150 phones.

Have a nice day