Problem Repair Nokia Lumia 900.1 RM-808

[xKxOxDx]

I have repaired Boot by JTAG


Flash proce make according to your Product code, the first few times gave me error, then insisting Full flash, but it stuck in the logo.

Log Boot-EFS-IMEI

Default language ID 0x200A
JTAG Interface Connected, S/N 0xB2783E44
Resetting and Exploring JTAG chain...No Devices found in Chain!
Loading AFP (Please Wait)...OK
AFP revision 4, compiled 07/12/2013 10:33:00 p.m.

================================================== ========
Phone Type : Lumia 900 RM-808, RM-823
CPU Type : Qualcomm MDM9200 (MODEM)
Storage TYpe: NAND 128MB
================================================== ========
1. Make sure JTAG Connection is 100% OK
2. Always Disconnect the Phone BATTERY
3. Connect USB Cable to Phone
4. Connect RJ-45 JTAG Cable to ATF Box
5. Select the Correct Phone Type RM-XXX
6. Use RESET JTAG button to check the JTAG Connection
7. Click RESTORE BOOT button to Start Boot Repairs
----------------------------------------------------------

Resetting and Exploring JTAG chain...No Devices found in Chain!
Resetting and Exploring JTAG chain...No Devices found in Chain!
Resetting and Exploring JTAG chain...No Devices found in Chain!
Resetting and Exploring JTAG chain...2 Device(s)
Device #1 ID 0x100590E1 IR7
Device #2 ID 0x203F10E1 IR4
Restore Boot...
Waiting for Device Connection 60 second(s)...OK
Resetting and Exploring JTAG chain...OK
Halting Core...OK
Initializing Device...OK
Detecting ONFI #1 ID...MICRON MT29F1G08ABBDAH4, 128 MiB
Testing Device Memory...OK
Sending Flash Loader...OK
Bad Blocks Request...OK
Restoring Partition #1...OK
Restoring Partition #2...OK
Restoring Partition #3...OK
Restoring Partition #4...OK
Restoring Partition #5...OK
Restoring Partition #6...OK
Restoring Partition #7...OK
Restoring Partition #8...Flash Write Error at 0x00BF0000, Bad Answer from Loader 0x0, 0x1D04
Resetting and Exploring JTAG chain...2 Device(s)
Device #1 ID 0x100590E1 IR7
Device #2 ID 0x203F10E1 IR4
Restore Boot...
Waiting for Device Connection 60 second(s)...OK
Resetting and Exploring JTAG chain...OK
Halting Core...OK
Initializing Device...OK
Detecting ONFI #1 ID...MICRON MT29F1G08ABBDAH4, 128 MiB
Testing Device Memory...OK
Sending Flash Loader...OK
Bad Blocks Request...OK
Restoring Partition #1...OK
Restoring Partition #2...OK
Restoring Partition #3...OK
Restoring Partition #4...OK
Restoring Partition #5...OK
Restoring Partition #6...OK
Restoring Partition #7...OK
Restoring Partition #8...OK
Restoring Partition #9...OK
Restoring Partition #10...OK
Restoring Partition #11...OK
Boot Restore Done!
================================================== ===========
Assemble Phone and Start Normally
If Phone cannot Start, perform USB Firmware Update Procedure
================================================== ===========

Completed in 0h 5m 31s. Code Download Speed 382 KiB/sec.
Loading AFP (Please Wait)...OK
AFP revision 4, compiled 11/12/2013 10:38:00 a.m.

================================================== ========
Phone Type : Lumia 900 RM-808, RM-823
CPU Type : Qualcomm MDM9200 (MODEM)
Storage TYpe: NAND 128MB
Fix Type : Repair Stuck at Logo Boot
================================================== ========
1. Make sure JTAG Connection is 100% OK
2. Always Disconnect the Phone BATTERY
3. Connect USB Cable to Phone
4. Connect RJ-45 JTAG Cable to ATF Box
5. Select the Correct Phone Type RM-XXX
6. Use RESET JTAG button to check the JTAG Connection
7. Click RESTORE BOOT button to Start Boot Repairs
----------------------------------------------------------

Resetting and Exploring JTAG chain...2 Device(s)
Device #1 ID 0x100590E1 IR7
Device #2 ID 0x203F10E1 IR4
Restore Boot...
Waiting for Device Connection 60 second(s)...OK
Resetting and Exploring JTAG chain...OK
Halting Core...OK
Initializing Device...OK
Detecting ONFI #1 ID...MICRON MT29F1G08ABBDAH4, 128 MiB
Testing Device Memory...OK
Sending Flash Loader...OK
Bad Blocks Request...OK
Restoring Partition #1...OK
Boot Restore Done!
================================================== ===========
Assemble Phone and Start Normally
If Phone cannot Start, perform USB Firmware Update Procedure
================================================== ===========

Completed in 0h 0m 19s. Code Download Speed 293 KiB/sec.
Loading AFP (Please Wait)...OK
AFP revision 4, compiled 03/02/2014 02:05:00 a.m.

================================================== ========
Phone Type : Lumia 900 RM-808, RM-823
CPU Type : Qualcomm MDM9200 (MODEM)
Storage TYpe: NAND 128MB
Fix Type : Restore Original IMEI
================================================== ========
1. Make sure JTAG Connection is 100% OK
2. Always Disconnect the Phone BATTERY
3. Connect USB Cable to Phone
4. Connect RJ-45 JTAG Cable to ATF Box
5. Select the Correct Phone Type RM-XXX
6. Use RESET JTAG button to check the JTAG Connection
7. Click RESTORE BOOT button to Start Boot Repairs
----------------------------------------------------------

Waiting for Device Connection 60 second(s)...OK
Resetting and Exploring JTAG chain...OK
Halting Core...OK
Initializing Device...OK
Detecting ONFI #1 ID...MICRON MT29F1G08ABBDAH4, 128 MiB
Testing Device Memory...OK
Sending Flash Loader...OK
Restoring IMEI 3597460428XXXX...OK

Log FLASH:

Windows Phone Flashing Started

ADSP File Found:
RM808_13w10_prod_generic_adsp.esco
AMSS File Found:
RM808_13w10_prod_generic_amss.esco
WPOS File Found:
RM808_13w10_prod_attus.esco
USER AREA ERASE File Found:
RM808_13w10_prod_generic_user_area_erase.esco
MDM AMSS File Found:
RM808_13w10_prod_generic_mdm_amss.esco
MDM DSP1 File Found:
RM808_13w10_prod_generic_mdm_dsp1.esco
MDM DSP2 File Found:
RM808_13w10_prod_generic_mdm_dsp2.esco
WARNING: OSBL File is not Loaded

================================================== ====
Windows Phone Lumia Flasher
================================================== ====

If the Phone is ALIVE
1. Power On the Phone and Connect it to the USB Port

If the Phone is DEAD
1. Press and Hold the VOLUME UP button
2. Connect it to the USB Port while still Pressing
the VOLUME UP button
3. Continue to Press the VOLUME UP button for 8 more
seconds
================================================== ====


Sending AMSS Certificate
HASH: 8D46D4B7D643AF3C506945E7DA6386CCAA23D980
Certificate Size: 449 Bytes
Status : WRITE AMSS CERTIFICATE SUCCESS

Sending AMSS Data Blocks
(Please Wait for 25 Seconds...)
Status : AMSS WRITE SUCCESS

Sending ADSP Certificate
HASH: 8D46D4B7D643AF3C506945E7DA6386CCAA23D980
Certificate Size: 449 Bytes
Status : WRITE ADSP CERTIFICATE SUCCESS

Sending ADSP Data Blocks
(Please Wait for 25 Seconds...)
Status : ADSP WRITE SUCCESS

Sending MDM AMSS Certificate
HASH: 8D46D4B7D643AF3C506945E7DA6386CCAA23D980
Certificate Size: 447 Bytes
Status : WRITE MDM AMSS CERTIFICATE SUCCESS

Sending MDM AMSS Data Blocks
(Please Wait for 25 Seconds...)
Status : MDM AMSS WRITE SUCCESS

Sending MDM DSP1 Certificate
HASH: 8D46D4B7D643AF3C506945E7DA6386CCAA23D980
Certificate Size: 447 Bytes
Status : WRITE MDM DSP1 CERTIFICATE SUCCESS

Sending MDM DSP1 Data Blocks
(Please Wait for 25 Seconds...)
Status : MDM DSP1 WRITE SUCCESS

Sending MDM DSP2 Certificate
HASH: 8D46D4B7D643AF3C506945E7DA6386CCAA23D980
Certificate Size: 447 Bytes
Status : WRITE MDM DSP2 CERTIFICATE SUCCESS

Sending MDM DSP2 Data Blocks
(Please Wait for 100 Seconds...)
Status : MDM DSP2 WRITE SUCCESS

Sending WPOS Certificate
HASH: 8D46D4B7D643AF3C506945E7DA6386CCAA23D980
Certificate Size: 1412 Bytes
Status : WRITE WPOS CERTIFICATE SUCCESS

Sending WPOS Data Blocks
[BLOCK 1 0x00000000~0x00FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 1837FDB8312AD70870E46763E85A01D7
---------- : 7656D71D3043C3C15F48C5BA99BFFA08
Status : WPOS WRITE SUCCESS
[BLOCK 2 0x01000000~0x016573FF]
Data Size: 0x00657400 Bytes
SHA-256 : 0FBCA994E5431EAE3AFC187E9E5C41C5
---------- : 0559F7F6018D3EAC1C34CE3B1CC4CE26
Status : WPOS WRITE SUCCESS
[BLOCK 3 0x01697400~0x01FFFFFF]
Data Size: 0x00968C00 Bytes
SHA-256 : 2147F706685319A0D7D6D855AFBB2A89
---------- : 5651003D0B7F0835C219914425307D57
Status : WPOS WRITE SUCCESS
[BLOCK 4 0x02000000~0x02FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : CF375D7A29A19655E1E4803C3427664B
---------- : 511632C1CE14C947008C0D60A63DFF94
Status : WPOS WRITE SUCCESS
[BLOCK 5 0x03000000~0x03FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 3AB4F4C67D4D8CAB0757E57E25E42FD8
---------- : 1B3FBB87540BE6C38FAB76B94F5F5731
Status : WPOS WRITE SUCCESS
[BLOCK 6 0x04000000~0x04FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : FC053DE4CADB258B03D36FA58131FB1C
---------- : 6EF15856E1CE0699CBD3BB4F78AB51E4
Status : WPOS WRITE SUCCESS
[BLOCK 7 0x05000000~0x05FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : DE90861B2A1E1CEA76349A9A132C3D11
---------- : 56B4958A62CF9F93F0EA9E32202F6025
Status : WPOS WRITE SUCCESS
[BLOCK 8 0x06000000~0x06FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : DD1E362B16B2B3D2106FB1C98333C6C5
---------- : 87C18B8C0567BB6D5A0D20D22C708E16
Status : WPOS WRITE SUCCESS
[BLOCK 9 0x07000000~0x07FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 28B4B9AB86636E63228ACDD3A2F3EA2D
---------- : DDFF0D9A30CB00955F92ADD1A4298B07
Status : WPOS WRITE SUCCESS
[BLOCK 10 0x08000000~0x08FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : C965454871000C39A561ECB8B0651561
---------- : 2F53CBDFA0E667FD7B05580447559BB8
Status : WPOS WRITE SUCCESS
[BLOCK 11 0x09000000~0x09FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : CAD505E081F2C5004AC59386F66D5154
---------- : C2AC5112895E9EB30F6A645F00E43B45
Status : WPOS WRITE SUCCESS
[BLOCK 12 0x0A000000~0x0AFFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : B111A4B26A32DB56C6C721C8EDFA993F
---------- : C87A5629020410B75A642699AAA45568
Status : WPOS WRITE SUCCESS
[BLOCK 13 0x0B000000~0x0BFFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 302E400A8CB9C5B4515BBC6B59E4F94B
---------- : 67798265EBFCC87E07E7AEE39F9F46C9
Status : WPOS WRITE SUCCESS
[BLOCK 14 0x0C000000~0x0CFFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : EAFDC6A5DF5A1105804A218BC8F9727B
---------- : 15FAAD29A152B7C4257803252EE2784E
Status : WPOS WRITE SUCCESS
[BLOCK 15 0x0D000000~0x0DFFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 321EFA30C38B48BC51F9B6837B8BD3AC
---------- : F041652966E34492DE389602D643626D
Status : WPOS WRITE SUCCESS
[BLOCK 16 0x0E000000~0x0EFFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 8834437A3922DB0B9E57F608B555CC23
---------- : B1F5EC7E310A5DE87232B42821D5AFCC
Status : WPOS WRITE SUCCESS
[BLOCK 17 0x0F000000~0x0FFFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 19A68327642BB3D73FD8A3D35B1ECC79
---------- : E37007E7AA42A338F4D5F2D083FA3F19
Status : WPOS WRITE SUCCESS
[BLOCK 18 0x10000000~0x10FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : E81047312DBBB4FD447F96E22216E289
---------- : EA296E8DC2B60B6DA0F7782920DC8B8F
Status : WPOS WRITE SUCCESS
[BLOCK 19 0x11000000~0x11FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : A102337D2F97E8EF5A39C3611C19B436
---------- : 3FA4CA541CF628A00B046ADCEDA91047
Status : WPOS WRITE SUCCESS
[BLOCK 20 0x12000000~0x12FFFFFF]
Data Size: 0x01000000 Bytes
SHA-256 : 5C99CB9220059CBE8189694B4C290806
---------- : EA806CC2330777B2973B76F81738B7C5
Status : WPOS WRITE SUCCESS
[BLOCK 21 0x13000000~0x1325DBFF]
Data Size: 0x0025DC00 Bytes
SHA-256 : 4E02D8A45EA00FA1DE80ECBB80DC14DC
---------- : 2DA097D56CB11474534AC30CF467D8E5
Status : WPOS WRITE SUCCESS

Sending USER AREA ERASE Certificate
HASH: 8D46D4B7D643AF3C506945E7DA6386CCAA23D980
Certificate Size: 396 Bytes
Status : WRITE ERASE CERTIFICATE SUCCESS

Erasing USER AREA
Status : ERASE SUCCESS

Flashing Done!
Total Flashing Time (Erase + Flashing) : 00:05:47

Then proceeded to give the ATF TP Boot Services according to this image



I detected quite right at first, when selecting the boot and give Repair, gave me error, I forgot to copy the log but it takes capture.





Check points, verify that they are well, they made land 4-6 when connecting the USB cable, fix it, the time to give again, repair everything.


While the capture is not the end I wrote the DBL file all right.
Upon Convey the Flash gives me error, download several times to verify that was not damaged, but still gives error.

I add that it is not possible to fix the BOOT via JTAG as the points 6 and 4 were detached from much solder and where it could not be welded.
I can only via TP Services for ATF.


I appreciate the trouble taken to help me, and sorry for the extensive Post.

[boygeohp1111]

i found same problem with repair jtag in atf