Jump to content


- - - - -

Why W580 Start Fsx Will Hv Error 0x02?

Started by jamesyee94, Jul 18 2009 06:18 AM

  • Please log in to reply
7 replies to this topic

#1 OFFLINE   jamesyee94

jamesyee94
  • New Members

    • n00b

  • 7 posts

Posted 18 July 2009 - 06:18 AM

why w580 start FSX will hv error 0x02?
at the bottom there also write....found:/tpa/user/theme/???????????????????????????????]
wat wrong?

#2 OFFLINE   Boysie

Boysie
  • Super Moderators

    • Mrs Miggins

  • 37,152 posts
  • Gender:Can't decide
  • Location:Between a rock and a hard place
  • Mobile:X10 (CM10.1 v10) - K800
  • Tutorials Submitted:One or two

Posted 18 July 2009 - 07:33 AM

Log please... :)

Personal messages that have no need to be private will not be answered. We have a forum for asking questions so please use it.

#3 OFFLINE   jamesyee94

jamesyee94
  • New Members

    • n00b

  • 7 posts

Posted 23 July 2009 - 07:45 AM

har?
wat log?

#4 OFFLINE   jamesyee94

jamesyee94
  • New Members

    • n00b

  • 7 posts

Posted 23 July 2009 - 07:58 AM

16:00:18| XS++ v3.1 (Darwin) Ready !

16:00:18| Executed on Microsoft Windows XP

16:00:26|

16:00:26| Attempting to open the interface...

16:00:26|

16:00:26| TURN OFF PHONE!

16:00:26| Hold 'C' button on phone and connect phone NOW.

16:00:26| You have 30 seconds...

16:00:26|

16:00:36| Baseband ID: 9900

16:00:36| Protocol Version: 3.1

16:00:36| Warning: IMEI name does not match GDFS name (IMEI:NULL GDFS:W580)

16:00:36| ...using GDFS name

16:00:36|

16:00:36| Profiling SEMC phone...

16:00:36| Platform: DB2020

16:00:36| OTP CID: 51

16:00:36| EROM CID: 52

16:00:36| EROM Color: Red

16:00:36| IMEI: 35256002xxxxxx

16:00:36| Phone ID: W580

16:00:36| Region: APAC

16:00:36| CDA: CDA102295/1   R2A

16:00:36| Firmware Version: R6BC002

16:00:36| EROM: R3A022

16:00:36| Ready for operation!

16:00:40| After making any changes with FSX

16:00:40| you must press the 'Shutdown' button

16:00:41|

16:00:41| Sending db2020_cid01_prodid_p3j.bin...

16:00:41| Applet ID: 070129 0950 NGUCXC1250330_DB2020_PRODUCTIONIDLOADER_P3J

16:00:41| This is a PRODUCTION_ID loader

16:00:41|

16:00:41| Sending db2020_mem_patcher_cid52_r2a006.bin...

16:00:42| Applet ID: 061205 1523 HANCXC9876543210_DB2020_MEM_PATCHER_R2A006 0

16:00:42| This is a MEM_PATCHER loader

16:00:42|

16:00:42| Sending db2020_red52_cs_r3a009.bin...

16:00:44| Applet ID: 070410 1557 HANCXC1250562_DB2020_CSLOADER_R3A009

16:00:44| This is a CHIPSELECT loader

16:00:44| Activating loader...

16:00:44| Activating GDFS...

16:00:59| This loader is UNLOCKED

16:00:59| Success! CS-loader has been unlocked!

16:00:59| Please wait while XS builds a list of directories...

16:00:59| Activating filesystem

16:01:01| Command: Error 0x02

16:01:01| Command: Error 0x02

16:01:01| Command: Error 0x02

16:01:01| Command: Error 0x02

16:01:01| Command: Error 0x02

16:01:01| Command: Error 0x02

16:01:01| Command: Error 0x02

16:01:01| Command: Error 0x02

16:01:01| Command: Error 0x02

16:01:02| Command: Error 0x02

16:01:02| Command: Error 0x02

16:01:02| Command: Error 0x02

16:01:02| Command: Error 0x02

16:01:02| Command: Error 0x02

16:01:02| Command: Error 0x02

16:01:02| Command: Error 0x02

16:01:02| Command: Error 0x02

16:01:02| Command: Error 0x02

16:01:02| Command: Error 0x02

16:01:02| Command: Error 0x02

16:01:02| Command: Error 0x02

16:01:02| Command: Error 0x02

16:01:02| Command: Error 0x02

16:01:02| Command: Error 0x02

16:01:02| Command: Error 0x02

16:01:02| Command: Error 0x02

16:01:02| Command: Error 0x02

16:01:02| Command: Error 0x02

16:01:02| Command: Error 0x02

16:01:02| Command: Error 0x02

16:01:02| Command: Error 0x02

16:01:02| Command: Error 0x02

16:01:02| Command: Error 0x02

16:01:02| Command: Error 0x02

16:01:02| Command: Error 0x02

16:01:02| Command: Error 0x02

16:01:03| Command: Error 0x02

16:01:03| Command: Error 0x02

16:01:03| Command: Error 0x02

16:01:03| Command: Error 0x02

16:01:03| Command: Error 0x02

16:01:03| Command: Error 0x02

16:01:03| Command: Error 0x02

16:01:03| Command: Error 0x02

16:01:03| Command: Error 0x02

16:01:03| Command: Error 0x02

16:01:03| Command: Error 0x02

16:01:03| Command: Error 0x02

16:01:03| Command: Error 0x02

16:01:03| Command: Error 0x02

16:01:03| Command: Error 0x02

16:01:03| Command: Error 0x02

16:01:03| Command: Error 0x02

16:01:03| Command: Error 0x02

16:01:03| Command: Error 0x02

16:01:03| Command: Error 0x02

16:01:03| Command: Error 0x02

16:01:04| Command: Error 0x02

16:01:04| Command: Error 0x02

16:01:04| Command: Error 0x02

16:01:04| Command: Error 0x02

16:01:04| Command: Error 0x02

16:01:45| Shutting down FS Services

#5 OFFLINE   Boysie

Boysie
  • Super Moderators

    • Mrs Miggins

  • 37,152 posts
  • Gender:Can't decide
  • Location:Between a rock and a hard place
  • Mobile:X10 (CM10.1 v10) - K800
  • Tutorials Submitted:One or two

Posted 23 July 2009 - 08:26 AM

Not sure. Reflash it and try again. :)

Personal messages that have no need to be private will not be answered. We have a forum for asking questions so please use it.

#6 OFFLINE   jamesyee94

jamesyee94
  • New Members

    • n00b

  • 7 posts

Posted 24 July 2009 - 07:40 AM

but reflash n try many time also same problem......

#7 OFFLINE   jamesyee94

jamesyee94
  • New Members

    • n00b

  • 7 posts

Posted 24 July 2009 - 03:37 PM

pls help me....
gt some body know how to slove this problem ma?

#8 OFFLINE   santae3

santae3
  • New Members
  • PipPipPipPipPipPip

    • Se-nse-ual

  • 943 posts
  • Gender:Male
  • Location:Chennai, Tamil Nadu, India
  • Mobile:Nokia 1100

Posted 24 July 2009 - 04:28 PM

try setool or jdflasher

Posted Image

Patch Porting Tools

ArOfGnEu

Back to XS++ R&D

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

  1. SE-NSE Forums
  2. → Sony Ericsson Legacy Sytems (JAVA, Symbian & Windows)
  3. → SE Firmware
  4. → Research & Development
  5. → XS++ R&D
  6. Privacy Policy
  7. SE-NSE Rules, Terms & Conditions ·