You are on page 1of 113

SUGAR trouble shooting

March.2019 V2.7
Document history
2.7 2019-3-22 Export log. Please wait… at page110 and 005009 on page111 and Page 112 Fisherman
2.6 2019-01-29 Model 8262 SN issue and 8079 SN and CU issue. Slide 109 Fisherman
2.5 2018-11-5 Power on with Fastboot mode aftter SUGAR download. Slide 108 Fisherman
2.4 2018-8-14 ERROR CODE=20003. Slide 107 Fisherman
2.3 2018-7-17 S_GET_DLL_VER_FAIL(ERROR CODE=1006) Slide 105 Fisherman
2.2 2018-7-13 Can’t find IMEI configuration file on server, please connect with server adiminstrator(Error code=10014) Fisherman
Error code: ERROR CODE=0X7d01
2.1 2018-6-01 Fisherman
Symptom: (FOTA) Http bad request
2.0 2018-5-9 Error code: ERROR CODE=21004 Fisherman
1.9 2018-5-08 Error code: ERROR CODE=c0050009 Fisherman
Error code: ERROR CODE=0X7d01
1.8 2018-5-03 Fisherman
Symptom: (FOTA) Http bad request
1.7 2018-4-17 ERROR CODE=c0050001 Fisherman
Error code 40026 on QCT GUTO2
1.6 2018-04-03 Fisherman
ERROR CODE=0X7d01 on MTK GOTU2
1.5 2017-08-28 Update with Neon dead with AAK version software Fisherman
1.4 2017-07-30 Update: Error code added for a quick search David C.
Update: Symptom: Using an Invavid operation for Tool configuration. Please ask for help.(Error code=4023)
(slide96)
Update: IMEI can not read from file on server configuration (slide79)
1.3 2017-05-12 Fisherman
Update: Generate FT File Error then customize Y580 (slide94)
Update: CONNECT FOTA SERVER ERROR(error code=20003) (slide80)
Update: Comment: File must be processed by TS before offline tool was released(slide 72)

Update: Tool prompt (FOTA)Network error! (Error code=30022) (slide 53)


Update: Something bad happened in your program . Would you like to save a diagnostic file? (Sllide 76)
Update: SUGAR MTK SPV4.1.8 with regard to Check SUM error(Error code=30024) (Slide 52)
1.2 2017/03/02 Fisherman
Update: Download NOT-HLOS failed(error code=40023) (slide75)
Update: BlackBerry Argon Kill switch error(slide79)
Update Black berry Neon phone can not power on (keep stay at fastboot menu) after download(slide78)

1.1 2017/01/18 Update : SUGAR ST/ Get version time out (Slide 73) Fisherman
1.0 2016/11/02 Creation Fisherman
Rev, Date Modification description Modified By
1. SUGAR error trouble shooting
Error code: 20003
Root Cause: server port were not enable on gateway. SUDH: Provide file or data download for clients.
Solution: Enable port for server on gateway. IP Name Port
52.200.46.60 VPC-gotu-amsu1-sugar 30008
52.200.34.216 VPC-gotu-amsu2-sugar 30008
52.200.44.249 VPC-gotu-amsu-sugar13 30008
52.71.47.32 VPC-gotu-amsu-sugar14 30008
52.200.31.135 VPC-gotu-amsu-sugar15 30008
52.16.239.174 VPC-gotu-amsu-sugar17 30008
52.16.175.72 VPC-gotu-amsu11-sugar 30008
52.31.98.171 VPC-gotu-amsu-sugar16 30008
Sumaster server: it is responsible for client requests 52.50.221.240 VPC-gotu-amsu-sugar18 30008
and determines which software or files shall be 52.16.21.159 VPC-gotu-amsu12-sugar 30008
downloaded according to IMEI and CU. 52.77.14.24 VPC-gotu-amsu-sugar20 30008
IP Name Port 52.76.11.240 VPC-gotu-amsu-sugar21 30008
46.51.185.96 gotu-sumaster 30007 52.77.125.194 VPC-gotu-amsu8-sugar 30008
52.71.171.248 VPC-gotu-sumaster2 30007 52.74.193.43 VPC-gotu-amsu-sugar19 30008
54.251.105.17 gotu-sumaster3 30007 52.77.103.235 VPC-gotu-amsu9-sugar 30008
When download speed Sumaster server: it is responsible for client requests and
is 0kb/s, the network determines which software or files shall be downloaded
may has problem. In according to IMEI and CU.
order to diagnose IP Name Port
network. Please telnet 46.51.185.96 gotu-sumaster 30007
or ping SUGAR 52.71.171.248 VPC-gotu-sumaster2 30007
server. 54.251.105.17 gotu-sumaster3 30007
You will get a mess
screen if network is SUDH: Provide file or data download for clients.
accessible when telnet IP Name Port
server. 52.200.46.60 VPC-gotu-amsu1-sugar 30008
For example: 52.200.34.216 VPC-gotu-amsu2-sugar 30008
Runcmd 52.200.44.249 VPC-gotu-amsu-sugar13 30008
telnet 52.200.46.60 52.71.47.32 VPC-gotu-amsu-sugar14 30008
30008 52.200.31.135 VPC-gotu-amsu-sugar15 30008
You will get screen 52.16.239.174 VPC-gotu-amsu-sugar17 30008
with mess . 52.16.175.72 VPC-gotu-amsu11-sugar 30008
52.31.98.171 VPC-gotu-amsu-sugar16 30008
52.50.221.240 VPC-gotu-amsu-sugar18 30008
52.16.21.159 VPC-gotu-amsu12-sugar 30008
52.77.14.24 VPC-gotu-amsu-sugar20 30008
52.76.11.240 VPC-gotu-amsu-sugar21 30008
52.77.125.194 VPC-gotu-amsu8-sugar 30008
52.74.193.43 VPC-gotu-amsu-sugar19 30008
52.77.103.235 VPC-gotu-amsu9-sugar 30008
Error code: 20002 / 21001
Root cause: Port for servers is not enable on gateway
Solution: Enable server IP and servers sites on gateway
Server Port DESC
g2slave-ap-north-01.tctmobile.com 80/443 Slave CDN
g2slave-eu-west-01.tctmobile.com 80/443 Slave CDN
g2slave-us-east-01.tctmobile.com 80/443 Slave CDN
54.225.78.202 80/443 Zerorating & encrypt
54.225.87.236 80/443 Zerorating & encrypt
54.195.239.239 80/443 Zerorating & encrypt
54.195.240.212 80/443 Zerorating & encrypt
54.249.227.45 80/443 Zerorating & encrypt
54.249.227.54 80/443 Zerorating & encrypt
54.238.56.196 80/443 Encrypt
46.51.183.28 80/443 Encrypt
75.101.149.79 80/443 Encrypt
g2master-ap-north.tctmobile.com 80/443 Sumaster
g2master-ap-south.tctmobile.com 80/443 Sumaster
g2master-cn-north.tctmobile.com 80/443 Sumaster
g2master-eu-west.tctmobile.com 80/443 Sumaster
g2master-sa-east.tctmobile.com 80/443 Sumaster
g2master-us-east.tctmobile.com 80/443 Sumaster
g2master-us-west.tctmobile.com 80/443 Sumaster
g2slave-ap-north-01.tclcom.com 80 S3
g2slave-eu-west-01.tclcom.com 80 S3
g2slave-ap-south-01.tclcom.com 80 S3
g2slave-us-east-01.tclcom.com 80 S3
Root cause: If you can not telnet and meet this
symptom
Solution: Enable telnet client on control panel.
Control PanelProgramsTurn Windows features
on of off Telnet CilentOK
1.SUGAR MTK SP
When you see such message during downloading process

Error code: 4014


The Root Cause might be: Battery is exhausted.
And the Solution is to : Charge battery
If despite this action, your receive the same message then please process as follow:
Restart your PC
Change a charged battery to test
Contact your RSH technical support
Error code: 5069
Symptom: Download bloader failed
Root cause: Memory damaged, such as memory insufficient soldering or ESD damage
Solution: It is a HW damage.
Error code: 10043
Root cause: Software package is damaged. Or DB file was deleted during use AOSD
package.
Solution: unzip AOSD and launch tool directly from AODS/tool
Root cause: Phone does not response.
Solution: Stop remove battery Upgrade connect phone put battery back to phone
Error code: 21006
Root cause: CU color code wrong causes software is no available
Solution: Change to correct CU to download
Error code: 10005
Root cause: Selected a wrong model. Here It was selected project name (Onetouch PIXI 7)
Solution: I213 should be selected.
Root cause: Phone is rooted.
Solution: Click Yes to accept so as to process download if CCM approve to do.
•In the upgrading process, if pop-up dialog box “ILLEGAL REWRITE” means the phone have been rooted.
•Also we can check the root by a separate button “CheckRoot”
•There are three kinds of Root and two sites to prompt Rooted In the upgraded process:
SU Root: Phone OS will write a record(string) on a zone if phone ROM was refreshed by other tool or system was modified by
root directly. Then phone was verdicted as ROOT if SUGAR detects this record(string).
When begin downloading and check the HS’ information
Error Code is R01
Image Root: System file has been illegally rewritten
OS has a dedicated string inside 3 imagine files. SUGAR will find it on these files. Phone was verdicted as ROOT if SUGAR
does NOT find that string.
When finished the software download from servers to PC local, and prepared to write into HS
Error Code is R00
IMEI Root: IMEI number has been illegal rewritten
When begin downloading and check the HS’ information
Error Code is R03
Error code: 10037
Root cause: High speed driver is not installed
Solution: Install driver again or manually install it during system searching or try enter
download mode
Error code: 21006
Root cause: Software is not synchronized to server.
Solution: Contact TS to upload software to server
Error code: 21006
Root cause: RC input Wrong CU after IMEI authorized. We don't have 5020X-2DALGR1 but 5020D-
2[ABCDEFGHIJ]ALGR1.
Solution: Change to correct CU.reference.
Error code: 4010
Root cause: Port is not available when tool try to refresh phone. Battery is exhausted or connection is loose
Solution1: Click OK Not close SUGAR tool Disconnect phone Remove battery Put battery back to phone 
Click upgrade again Connect phone
Solution2: Charge battery or check USB connection.
Solution3: Close tool and download again.(Comment: no need delete session for this error code=4010)

Case1 Case2 Case3


Error code: 21019
Root cause: trunks was spoiled during transfer from server
Solution: Delete session on options  close SUGAR Download again.

case1 case2
Root cause: Wait for IMEI check, checking session and network problem.
Solution: Delete session close SUGAR try again.
In case of this symptom persists, please contact RSH to support.
Error code: 10002
Root cause: CU written on memory was overwrote, erased or SUGAR reading CU length (game
rule) does not match with HDT tool written.
Solution: Optimized tool (game rule does match).
Error code: 3040
Root Cause: Not clear
And the Solution is to : need a charged battery to trigger
If despite this action, your receive the same message then please process as follow:
Launch tool again.
Change a charged battery to test
Contact your RSH technical support
Error code: 5008
Root cause: Software is not loaded completely.
Solution: Please try again.
Error code: 4008
Root cause: New and OLD library is not compatible this symptom.
Solution: Upgrade tool.
Error code: 4001
Root cause: Duplicate SW
Solution: Delete duplicate ones
Error code: 5008
Root cause: Software is not loaded completely.
Solution: Try again.
Error code: 5008
Root cause: Load software in offline by Dongle
Pixi3-4.5_4G_VF_Main_Code_C7C,
Pixi3-4.5_4G_VF_CommercialDB_V26,
V795-2XVDES1_V01.
Actually, these software are wrong. It is not according software tracking.
Solution: Load software strictly according to software tracking sheet. Such as:
V795-2XVDES1_V02
Pixi3-4.5_4G_VF_Main_Code_C7C
Pixi3-4.5_4G_VF_CommercialDB_V28
Error code: 4008
Root cause: Offline in Dongle mode. Error as herein hints.
Port disappear during software downloading because of no power(battery) when download for bare PCBA or phone without
battery or battery without charge.
Solution: provide power source if download for PCBA by socket or charge battery if download for phone.
Error code: 1013
Root cause: SW(preloader file) does not match phone’s flash
Solutions:
1. Close tool and launch tool again to test. Battery should be remove and plug again.
2. If you meet this symptom again, please restart PC.
3. If upload solution does not take effect. Please contact RSH to ask R&D release new tool
Error code: 21039
Root cause: network is not stable and too slow, downloading too long will cause this failure
Solution: offline download
Error code: 1003
Root cause: Chip ID on configured on software or tool does match that on phone
Solution: Release new tool.
Error code: 10005
Root cause: Phone IMEI is null or tablet WIFI that has no IMEI
Solution: Check IMEI by *#06# if it is a phone. If it is a tablet. Then tool must be optiomized.
Error code: 10033
Root cause: no such CU in DB(color is wrong usually)
Solution: change another CU that exists
Error code: 1002
Root cause: Offline in Dongle mode. Error as herein hints.
Log shows: C:\SUGAR_MTK_SP\tool\..\bin\data\c2crhk50ar20.mbn),remote file(false).
Actually there is not Perso file for this project. So the software in Bin is wrong.
Solution: After all software in data of bin are deleted and unzip software to Data in Bin. Iusse was solved.
Error code: 1002
Root cause: Online downloading, but the SW on the server is not complete (missing preloader file).
Solution: upload complete SW to server
Error code: 3152
Root cause: when download in SUGAR offline mode
Solution: Clear your bin folder but put correct bins of PERSO/MAINCODE/DB
Root cause: Model quantity on tool was modified induce tool can read correct model quantity and can not be
launched.
Solution: R&D optimize tool. Tool can launch after optimized.
Error code: 1002
Root cause: Model is wrong when select 5015D to download. 5015 should be selected.
Solution: Select 5015.
The instruction at "0X1000a4b9" referenced to memory at "0x10125000" . The memory could not be “read”
Error code: 30022 / 21002 / 1002
Root cause: Network is not stable or software version on server has problem
Solution: Change the CU that are included
Error code: 21002 / 21009
Root cause: Load file from FOTA server error! Because network has something wrong to server.
Solution: New otu.dll released to embed new version tool.
Error code: 21013 / 30014
Root cause: Load file from FOTA server error! Because network has something wrong to server.
Solution: New otu.dll released to embed new version tool.
Root cause: Tool try to read OTP zone when it tests Reserver Partion Size. But this OT-8063(PIXI4-7 WIFI
has no OTP zone. So tool reads it failed.
Solution: Modify source code as NOT read OTP zone and optimize tool to SUGAR MTK_SP_Gotu2 v4.1.5
Error code: 6045
Root cause: Because of software size, some imagine file was zip on server so as to decrease size and
increase download speed. It is still zipped after it was downloaded to PC. So SUGAR must unzip it before
write to phone. The problem is that this version SUGAR does NOT unzip software and write it to phone.
Solution: Optimize software code (SUGAR MTK_SP_GUTO3 V4.1.5) so as to unzip software before it was
written to phone.
Error code: 1006
Root cause: software was intended to move from GUTO1 TO GOTU2. The problem this CU software still
on GOTU1 server and NOT ready on GOTU2 server. However, this version SUGAR version tool piont
GOTU2 server..
Solution: synchronize software to GOTU2 and publish for online download.
Symptom: We have problem with 5045 model. The 5045 model is frozen after updating from Sugar MTK SP 2015
3.4.5 version. We can use old Sugar version (3.6.4) for this model
Root cause: system file format is different on GOTU1 (y7efcc44bp20.mbn) and GOTU2
(Y7EFCCQ1BP20.zip_125668) . SUGAR_MTK_SP_2015 3.4.5 links to GOTU2 , did not take compress software issue. So
did not assemble it as correct file.
Solution: optimize code on SUGAR_MTK_SP 2015 3.4.5 test and make it unzip Y file.

Frozen on Alcatel Frozen on Alcatel Power on


Symptom: COM port is busy! Don’t change product now!
Root cause: Draw down Product Models menu during downloading.
Solution: Click OK and not click Product Models menu arrow.
Symptom: refresh too fast to believe. Only 34 seconds! Too fast to believe.
Root cause: Software checks tablet software version and finds it is same as it on SUGAR tool when
download at second time.
Solution: Force to load software to device again even software version equal between device and SUGAR
tool
Error code: 30024
Symptom: Anovo down OT-8063 met this Create folder failed and Check SUM error(Error code=30024) .
Root cause: Account and ID was not correctly authorized on server to download software.
Solution: IT reset account and ID on system
Error code: 30022
Symptom: Tool prompt (FOTA)Network error!
Root cause: Network is not stable.
Solution: debugging
2. SUGAR QCT SP
Error code: 40022
Root cause: CU no in the DB
Solution: Change the CU that are included
Error code: 9023
Root cause: IMEI txt file in wrong path
Solution: Put it to the right path and download again
Error code: 5002 / 9001
Root cause: Phone or PCBA status is not ready to download MPRG.
Solution:Open socket if download for PCBA and check driver status. Herein is the driver has problem.Try to reboot phone
is download for handset.

Case1
Case2
Error code: 40004
Root cause: EMMC mass storage disc driver is not installed by system
Solution: Try again or install driver again or enter download mode.
Manually install EMMC mass storage disc driver or restart PC. Power on/off phone to make phone
in a ready status.
Error code: 20001
Root cause: Software is not synchronized to server. Software is not available on server or CU
(6039S-2AALUS0) is a Develop software that would not be released for online upgrade
Solution: Change CU to download
Root cause: Search 9008 time over thanks to driver is not ready or HW problem.
Solution: Install driver manually. If manually failure, please reset phone or restart PC. If symptom
persists, please contact RSH for technical support.
Error code: 20007
Root cause: Session between server and tool failed
Solution: Delete session  close tool try again
Try to power on phone is recommended before try to download again.
Error code: 40022
Root cause: Software is not download completed or failed
Solution: Delete session try again to download.
COMMENT: Close tool after session was deleted. Phone should be power on/off before download again.
Error code: 40004
Root cause: Mass storage device driver is not install by PC automatically
Solution: Power key & V+ &V- key to connect phone again to install disc driver.
Error code: 40023
Root cause: PC HD memory is exhausted.
Solution: Release HD memory by delete software under Bin\data.
Error code: 40023
Root cause: Connection between sever and PC or phone to PC is not good.
Solution: Try download again to fix the problem in this case
Error code: 40023
Root cause: Network is not stable induce system file download failure.
Solution: Delete session and try again to download
Root cause: Software and tool is not compatible.
Solution: R&D optimize tool
Error code: 40003
Root cause:
Solution:
Error code: 20003
Root cause: Connection between PC and server is not good
Solution: Set IP on gateway
Error code: 20004
Root cause: Network issue induce software load failure from server.
Solution: delete session SUGAR power off/on phone , Later launch tool and test again.
Error code: 40006
Root cause: DB file in configuration is wrong.
Solution: Encrypt DB file.
Comment: File must be processed by TS before offline tool
was released.
Error code: 20004
Root cause: Load file from FOTA server error! Because network has something wrong to server.
Solution: New otu.dll released to embed new version tool.
Error code: 20001
Symptom: Both RCs in Middle east and Russia meet software not available issue even TS in China test is OK
Root cause: Account (ID and Password) is NOT authorized or authentification is not passed on SUGAR tool
Solution: New tool SUGAR QCT SP 11.1.2. was released by change source code.
Error code: 40023
Symptom: Download NOT-HLOS failed(error code=40023)
Root cause: Account and password created by first generation system which is not decode by new coding system
Solution: reset account and password on news system.
Symptom: Something bad happened in your program . Would you like to save a diagnostic file?
Root cause: Account issue(account from TS enable to download but tool crash when use RC account)
Solution: fix account on server

TW with RC account and password on RC PC TW with TS account and password on RC PC


Symptom: Black berry Neon phone can not power on (keep stay at fastboot menu) after download
Root cause: software AAF959 have bug)
Solution: Upgrade software to AAI75

AAF959 AAI95
Error code: 9018
Symptom: Can’t read IMEI configuration file on server, please contact administrator
Root cause: IMEI is not authorized on server to change CU.reference
Solution: declare IMEI
Symptom: BlackBerry Argon Kill switch error
Root cause: Select a wrong product R190 to perform kill switch remove
Solution: select correct R191 product.
Error code: 20003
Symptom: CONNECT FOTA SERVER ERROR
Root cause: same space on available software version
Solution: Upgrade OTUdll. SUGAR tool version upgrade to SUGAR QCT_SPV11.1.3
3. SUGAR ST
Error code: 21001
Root cause: Get version time out. Network issue.
Solution: try again
4. SUGAR MKT FP
Root cause: Software is not ready on server.
Solution: Upload software to server
5. Softwareupgrade
Error code: 404
Root cause: Software is not ready on server.
Solution: Upload software to server
Error code: 10010
Root cause: Software is not ready on server. 2001X-2AALEU0 is developing test software. It would not be upload to
server.
Solution: Customize it.
Root cause: Tool bug.
Solution: Upgrade to softwareupgrade 5.3.3
Error code: 5039
Root cause: Software is not ready on server.
Solution: Upload software to server
6. ODM Multi port download
Play-5 OT-5022
Root causes
1. If software without “SWR”, tips are as below. Picture1
2. If SWR is not matched. tips are as below. Picture2
Solution:
 Unzip tool and load software again.
 If it is not fixed, please restart PC.

Picture1 Picture2
Kid watch SW10
Root cause: CU on software does not match on device(watch)
Solution: Download correct software or change CU on device(watch)

Q: How to check CU?


A: Please refer to following information

A-- select up key


B– select down key Hold on A+B+C when watch is power
C--SOS on. IMEI and CU, SWV is visable
D—Power key
Ginger XL2 OT-2051
Root cause: CU on software does not match on phone
Solution: Find correct software or change CU on phone

2051D-3*ALE71 Serbia 2051D_L4EN_V1.6_161008_MCP64+64_AL_E7

COMMENT: Please pay attention to CU_Ref on tool UI When meet this problem persists. This CU_REF is read from phone by
tool. You must download a software according to this CU---refer to software tracking sheet.
If you can not see CU_Ref on UI, it means your phone has no CU reference. In this case, please contact RSH technical support.
Plus10 WIFI (OT-8085)

Root cause: Customer_ WIFI random error


Solution: Restart OS and try again
Plus10 WIFI (OT-8085)
Root cause: OS has default product key before OS active. This default product key will be changed after system is active.
Since that update key does not match pre-set key on IMT_WIFI tool. So, tool will prompt wrong product key.
Solution: Please use C:\CUSTOMER_WIFI \TestConsole.exe to MMI test. This tool will not test product key and other items
can be normally test.

Q: Why IMT_WIFI test product key and give RC to test?


A: Device can NOT be active if without product key. So product key must be verified during production so as to SWAP
PCBA.
Plus10 WIFI (OT-8085)

Root cause: CU change tool v1.1 has bug.


Solution: CU change tool v1.2 fixed
Symptom: download Y580D-2XTIIT3-R_723M78X_A86M720_714008D_0041000_PTS172_V01 is ok . But tool prompts
Generate FT File Error when download Y580D-2XTBHR1_71U008X_A7TER00_709008D_0023900_PTS094_V01. )
Root cause: modemimage is different between this two software
Solution: R&D temporary create tool TPST_TPW0056000_Setup_for580_FT_FAIL.rar. This tool is only for this case. It is
NOT fit for any models.
Error code: 4023
Symptom: Using an Invavid operation for Tool configuration. Please ask for help.(Error code=4023)
Root cause: tool miss V300.sca and V300.mbn
Solution: R&D temporary provide configuration file V300.sca and V300.mbn. Both file will be merge to tool in next highter
version tool.
Error code: 40023
Symptom: 1163825998(Error code=40023)
Root cause: Phone belong to PP and Signature of phone software is not matched software signature on server.
Solution: Get signature of phone and find exactly signature software from R&D to provide an offline tool to RC.
Error code:
Symptom: Neon dead with AAK version software
Root cause: Phone current software version is AAM. Meanwhile, it is AAK the lower version is available on server. So it is
dead after downloaded by SUGAR.
Solution: Upload AAM to SUGAR server(as AAM is the latest version available to upload).
Error code: ERROR CODE=40026
Symptom: ERROR CODE=40026
Root cause:Network issue.
Solution: Download again.
Error code: ERROR CODE=0X7d01
Symptom: (FOTA) Http bad request
Root cause1: SUGR POT deem its path as SUGAR Tool Path.
Solution: Change SUGAR POT path as SUGAR TOOL path. Release correction SUGAR POT 1.1.5 version.
Root cause2: Firewall block.
Solution. Disable firewall.
Root cause3: Perso file setting compatible issue. HDT tool do not write one flag that induces tool can’t get software
version from server. E.G. symptom on model 5009.
Solution: SUGAR 4.6.7 R write this flag
Error code: ERROR CODE=c0050001
Symptom: Status_Device_CRTL_Exception
Root cause: flashtool library conflicts with tool source code
Solution: Debug and upgrade to SUGAR_MTK_SP_GUTO2 4.6.3.R.
Error code: ERROR CODE=c0050009
Symptom: Status_FORMAT_Exception
Root cause: Battery is exhuasted
Solution:Charge battery and download again.
Error code: ERROR CODE=21004
Symptom: FOTA Connection Failed
Root cause: Network issue
Solution: Test again when network connection is stable.
Error code: ERROR CODE=10014
Symptom: Can’t find IMEI configuration file on server, please connect with server adminstrator.
Root cause: 1. Synchronize IMEI delay from IMEIdeclare system to FTP site. 2. Select wrong model that make SUGAR
tool find wrong folder, specially model should NOT with extension.
Solution: Root cause1, wait for 5 minutes after IMEI was declared. Root cause2, select right model without alphabet
extension.

9003X is wrong 9003 is right


Wait 5 minutes after IMEI was declared
Error code: ERROR CODE=1006
Symptom: Get version and SUGAR prompts S_Get_DLL_VER_FAIL(Error code=1006).
Root cause: Software is not available on server for that CU.reference.
Solution: Upload software to server. Or change CU.reference if it is a DT software. E.g. V500-2AVDEU1 is a DT software
CU.
Error code: None
Symptom: Get version and SUGAR crashes when SUGAR is in change CU.reference feature.
Root cause:
Solution:
Error code: ERROR CODE=20003
Symptom: Your account that login sugar need to update. Please contact zhenghua.gao@tcl.com to handle it.(error
code=20003)
Root cause: account is not synchronized to cloud server.
Solution: IT manually synchronize accounts to server.
Error code: Power on with Fastboot mode after SUGAR download
Symptom: BB phone power on and stay at Fastboot mode after SUGAR download even it is power on normally before
SUGAR refresh.
Root cause: SUGAR software version is lower that FOTA version. End user already upgrade software by FOTA with
higher version. Well SUGAR server keeps lower SW version. So, after SUGAR refreshed, phone SW is read
DOWNGRADE that is not allowed by system.
Solution: Upload highest software to SUGAR sever and refresh software via SUGAR again.
Error code: 10005 or ox2716
Symptom: This handset’s serial number is null or illegal. It can not download.
Root cause: there is no SN and no CU-reference on tracebility.
Solution: user parameter tool to write SN and CU-reference onto memory.
Error code: Export log. Please wait…
Symptom: Export log. Please wait….
Root cause: Read log on memory for boot up failure debug failed
Solution: No need further action but waiting
Error code: 005009
Symptom: Status_Format_Exception
Root cause: Battery power exghuasted
Solution: Install new driver
Error code: Check Log flag. Please wait or Get log fail!
Symptom: Check Log flag. Please wait or Get log fail!
Root cause: Read log on memory for boot up failure debug failed
Solution: No need further action but waiting
THANK YOU

You might also like