error information on ufs and jaf

[mayor_NY]

Who knew there was a need or do not know yet


Description of error in UFS for nokia

1. Error HDAT 14.
a. Check the data cable
b. Change MJOLNER 85% weak.
2. C BUS 9 boot error.
a. Skip BT flashing
b. Change IC flash.
3. ALG 2nd boot error.
a. Check your FIA
b. CHANGE UPP
4. Platform 3, the data error DCT4
a. Change UPP
5. Error 6
a. 90% RAM
b. 10% UPP
6. ALG 1 boot error
a. Reball flash IC 3
b. CHANGE UPP
7. Error 10
a. CHANGE UPP
b. Ic flash Reball
8. Error 6 platform 7
a. Change UPP
9. Error 2 DCT4
a. UPP
10. error HDAT 14 DCT4
a. mjolner
11. WD2 boot error
a. Make sure MAINT board OK
b. Make sure mjolner OK
c. Check use PS, if it rises 0.25 A (make sure UEM OK), UPP damaged.
d. If not up / over 0.25 A, UEM damaged.


DESCRIPTION ERROR ufs.
1. Not connected 45: replace U1
2. Not connected 00: replace the C3 / U2
3. HWK dead / no connect: replace Q1 and Q2
Error Description JAF
________________________________________
Server error 1

Each will start jaf always checks to see if there is software or firmware, but the box can still be used, this message will come on until we update online

* The solution: update online

6630 error sync the phone

Check cable nothing wrong

* Try to Replace Cable TV

Unknown cmd in flash file

Flash files will be used corupted,

* Inlstall repeated flash files and flash back

The same thing for JAF error reading the article can be listened to below:

mcuid aaaa: The phone is not going on or the TX signal line data is too high after power turned on (damage to the CPU, TX less data line connected)

mcuid cccc - The phone can not be issued a signal on TX data line after UEM reset IC (BSI line is not connected properly, check the 3.3 K resistor contained in BSI line, or damaged UEM)

mcuid DDDD - phone signals can not be issued a TX line low after UEM reset the data (perhaps UEM damaged or that have long JAF customer ID 85xxxxxx capacitor with a value of 33 pico b / w mbus-ground must be removed)

mcuid EEEE - CPU there is no response to reflash the data

Error loading boot - problem could not be verified defective RAM or CPU is defective.

Error loading loader - Problems can not be verified RAM, CPU, or Flash IC is damaged.

Error loading aditional loader - Bluetooth module damaged (especially in Ic). To skip bluetooth solution while reflash the phone.

Error erase - Flash IC damaged or bad connect.

Error cmd20 - Bluetooth Ic damaged or bad connect

Error cmd14 - flash chips or old jaf problem until customer id PCB 85xxxxxx must put a 33 pico capacitor b / w mbus-gnd
Flash ic damaged or bad, or connect with old JAF customer ID 85xxxxxx capacitor with a value of 33 pico b / w mbus-ground should be removed.

If the phone can not always go to local mode, please checked contained 68K resistor in BSI line and Ground (Data cable) .