SE-NSE Forums:

Jump to content

Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic
  • Bookmark

Help Please! error Rate Topic: -----

#1 User is offline   chukchuk11 Icon

  • n00b
  • Group: Members
  • Posts: 8
  • Joined: 28-November 07

Posted 07 December 2007 - 11:41 AM

what should i do?help...thx


19:17:27| XS++ v3.1 (Darwin) Ready !

19:17:27| Executed on Microsoft Windows XP

19:17:36|

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

19:17:36|

19:17:36| TURN OFF PHONE!

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

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

19:17:36|

19:17:41| Baseband ID: 9900

19:17:41| Protocol Version: 3.1

19:17:41| Phone name detected!

19:17:41|

19:17:41| Profiling SEMC phone...

19:17:41| Platform: DB2020

19:17:41| OTP CID: 51

19:17:41| EROM CID: 52

19:17:41| EROM Color: Red

19:17:41| IMEI: 35536301xxxxxx

19:17:41| Phone ID: W850

19:17:41| Region: APAC

19:17:41| CDA: CDA102568/101 R5A

19:17:41| Firmware Version: R1JG001

19:17:41| EROM: R3A022

19:17:41| Ready for operation!

19:17:47| After making any changes with FSX

19:17:47| you must press the 'Shutdown' button

19:17:49|

19:17:49| Sending db2020_cid01_prodid_p3j.bin...

19:17:49| Applet ID: 070129 0950 NGUCXC1250330_DB2020_PRODUCTIONIDLOADER_P3J

19:17:49| This is a PRODUCTION_ID loader

19:17:49|

19:17:49| Sending db2020_mem_patcher_cid52_r2a006.bin...

19:17:50| Applet ID: 061205 1523 HANCXC9876543210_DB2020_MEM_PATCHER_R2A006 0

19:17:50| This is a MEM_PATCHER loader

19:17:50|

19:17:50| Sending db2020_red52_cs_r3a009.bin...

19:17:52| Applet ID: 070410 1557 HANCXC1250562_DB2020_CSLOADER_R3A009

19:17:52| This is a CHIPSELECT loader

19:17:52| Activating loader...

19:17:52| Activating GDFS...

19:18:09| This loader is UNLOCKED

19:18:09| Success! CS-loader has been unlocked!

19:18:09| Please wait while XS builds a list of directories...

19:18:09| Activating filesystem

19:18:12| Command: Error 0x02

19:18:12| Command: Error 0x02

19:18:12| Command: Error 0x02

19:18:12| Command: Error 0x02

19:18:12| Command: Error 0x02

19:18:12| Command: Error 0x02

19:18:12| Command: Error 0x02

19:18:12| Command: Error 0x02

19:18:12| Command: Error 0x02

19:18:12| Command: Error 0x02

19:18:12| Command: Error 0x02

19:18:12| Command: Error 0x02

19:18:12| Command: Error 0x02

19:18:12| Command: Error 0x02

19:18:12| Command: Error 0x02

19:18:12| Command: Error 0x02

19:18:12| Command: Error 0x02

19:18:12| Command: Error 0x02

19:18:12| Command: Error 0x02

19:18:12| Command: Error 0x02

19:18:12| Command: Error 0x02

19:18:12| Command: Error 0x02

19:18:12| Command: Error 0x02

19:18:12| Command: Error 0x02

19:18:12| Command: Error 0x02

19:18:12| Command: Error 0x02

19:18:12| Command: Error 0x02

19:18:12| Command: Error 0x02

19:18:12| Command: Error 0x02

19:18:13| Command: Error 0x02

19:18:13| Command: Error 0x02

19:18:13| Command: Error 0x02

19:18:13| Command: Error 0x02

19:18:13| Command: Error 0x02

19:18:13| Command: Error 0x02

19:18:13| Command: Error 0x02

19:18:13| Command: Error 0x02

19:18:13| Command: Error 0x02

19:18:13| Command: Error 0x02

19:18:13| Command: Error 0x02

19:18:13| Command: Error 0x02

19:18:13| Command: Error 0x02

19:18:13| Command: Error 0x02

19:18:13| Command: Error 0x02

19:18:13| Command: Error 0x02

19:18:13| Command: Error 0x02

19:18:13| Command: Error 0x02

19:18:13| Command: Error 0x02

19:18:13| Command: Error 0x02

19:18:14| Command: Error 0x02

19:18:14| Command: Error 0x02

19:18:14| Command: Error 0x02

19:18:14| Command: Error 0x02

19:18:14| Command: Error 0x02

19:18:14| Command: Error 0x02

19:18:14| Command: Error 0x02

19:18:14| Command: Error 0x02

19:18:14| Command: Error 0x02

19:18:14| Command: Error 0x02

19:18:14| Binary acknowledge failed with: 15

19:18:14| Command: Error 0x15

19:18:14| Binary acknowledge failed with: 15

19:18:14| Command: Error 0x15

19:18:14| Binary acknowledge failed with: 15

19:18:14| Command: Error 0x15

19:18:14| Binary acknowledge failed with: 15

19:18:14| Command: Error 0x15

19:18:14| Binary acknowledge failed with: 15

19:18:14| Command: Error 0x15

19:18:14| Binary acknowledge failed with: 15

19:18:14| Command: Error 0x15

19:18:14| Binary acknowledge failed with: 15

19:18:14| Command: Error 0x15

19:18:14| Binary acknowledge failed with: 15

19:18:14| Command: Error 0x15

19:18:15| Binary acknowledge failed with: 15

19:18:15| Command: Error 0x15
0

#2 User is offline   Malfreds Icon

  • Non-se-nse
  • PipPipPip
  • Group: Members
  • Posts: 137
  • Joined: 07-April 07
  • Location:MX
  • Mobile:K810 Noble Blue full modded

Posted 08 December 2007 - 03:19 AM

What did you try to do? Name files also.
0

#3 User is offline   chukchuk11 Icon

  • n00b
  • Group: Members
  • Posts: 8
  • Joined: 28-November 07

Posted 21 December 2007 - 08:52 AM

View PostMalfreds, on 2007-12-08 03:19, said:

What did you try to do? Name files also.


i just start fsx..beacause i want to put walkman skins/change font using xs++ 3.1
whats wrong?thx
0

#4 User is offline   solidhelix08 Icon

  • Padawan
  • Pip
  • Group: Members
  • Posts: 31
  • Joined: 28-October 07

Posted 21 December 2007 - 09:20 AM

i get the "Command: Error 0x02" when i'm browsing my phone's FS. dunno if this is a critical error. do you hold the "c" button when you are browsing your FS?
0

SE-NSE

#5 User is offline   number1 Icon

  • scots Level SE-NSE Addict
  • PipPipPipPipPipPipPipPipPipPipPip
  • Group: Members.
  • Posts: 5,350
  • Joined: 06-May 07
  • Gender:Male
  • Location:Uk,Kent,Sittingbourne
  • Mobile:Sony Ericsson P1 & Nokia N97
  • Tutorials Submitted:2

Posted 21 December 2007 - 11:24 AM

it's probley just a bug with xs++ try again
Posted Image
Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic
  • Bookmark

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users