|
|
 |
|
Welcome to the GSM-Forum forums. You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. Only registered members may post questions, contact other members or search our database of over 8 million posts. Registration is fast, simple and absolutely free so please - Click to REGISTER! If you have any problems with the registration process or your account login, please contact contact us . |
| |||||||
| Register | FAQ | Donate | Forum Rules | Root any Device | ★iPhone Unlock★ | ★ Direct Codes ★ | Direct Unlock Source |
 |
| | LinkBack | Thread Tools | Display Modes |
12-07-2011, 09:36
| #1 (permalink) |
| Freak Poster  Join Date: Aug 2003 Location: Bulgaria Age: 36
Posts: 254
Member: 37668 Status: Offline Thanks Meter: 15 | Problem with N97 RM-507 Now I'm trying to repair it with MT-Box. The PCB is in good condition, without any damage. Here is the FBUS log: Code: Selected Highest installed version: 22.2.110
Mcu RM-507_22.2.110_prd.core.C00
Ppm RM-507_22.2.110_prd.rofs2.V28
Ppm RM-507_22.2.110_C01_prd.rofs3.fpsx
Content RM505_507_22.0.110_uda_9_001.uda.fpsx
Content RM505_APE_ONLY_ENO_09w23_v0.072.fpsx
MemoryCardContent
RM505_RM507_101_000_M021_32G.fpsx
Using Tx2 Data line.
BB5 PM back Phone is in: Phone is not responding!
Processing File: RM-507_22.2.110_prd.core.C00
Boot...
RAPIDOv11_2nd.fg
FAILED TO RECEIVE DEVICE CONFIGURATION!
Can't find CMT Loader
%%%%%%%% ERROR BOOTING: Here is the dead USB log: Code: Switched to USB BUS
Using Tx2 Data line.
BB5 PM back Phone is in: Phone is not responding!
Processing File: RM-507_22.2.110_prd.core.C00
Boot...
CONNECT PHONE to USB and Power ON phone!
Pooling for phone...
\\?\nmwcd#vid_0421&pid_0106&if_oth#6&77ca5e2&1&00#{4f919102-4adf-11d5-882d-00b0d02fe381}
Sending ULO code
Isa UPDAPP
RAP3NAND
PASUBTOC
UPDAPP
Pooling for device removal...
Device removed
Pooling for ADL device...
\\?\nmwcd#vid_0421&pid_0105&if_oth#6&1b06a9af&1&00#{4f919102-4adf-11d5-882d-00b0d02fe381}
CMT Certificates
NOT SUPPORTED
Erase[296.87 MB]...
erasing APE [00040000 to 00082FFF]
erasing APE [00083400 to 003FFFFF]
erasing APE [00800000 to 00D5FFFF]
erasing APE [00D60000 to 0AB9FFFF]
erasing APE [0ABA0000 to 0F71FFFF]
erasing APE [079A0000 to 09C9FFFF]
erasing APE [09CA0000 to 0AB9FFFF]
erasing APE [00400000 to 007FFFFF]
in 11.64s
Flash[106.34 MB]...in 41.69s
* * Processed file in 72.88 seconds
Processing File: RM505_507_22.0.110_uda_9_001.uda.fpsx
Boot...
Pooling for ADL device...
\\?\nmwcd#vid_0421&pid_0105&if_oth#6&1b06a9af&1&00#{4f919102-4adf-11d5-882d-00b0d02fe381}
Erase[0.00 MB]...
in 0.13s
Flash[8.79 MB]...in 3.38s
* * Processed file in 3.63 seconds
Processing File: RM-507_22.2.110_prd.rofs2.V28
Boot...
Pooling for ADL device...
\\?\nmwcd#vid_0421&pid_0105&if_oth#6&1b06a9af&1&00#{4f919102-4adf-11d5-882d-00b0d02fe381}
Erase[0.00 MB]...
in 0.31s
Flash[23.86 MB]...in 8.91s
* * Processed file in 9.34 seconds
Processing File: RM-507_22.2.110_C01_prd.rofs3.fpsx
Boot...
Pooling for ADL device...
\\?\nmwcd#vid_0421&pid_0105&if_oth#6&1b06a9af&1&00#{4f919102-4adf-11d5-882d-00b0d02fe381}
Erase[0.00 MB]...
in 0.00s
Flash[0.01 MB]...in 0.03s
* * Processed file in 0.16 seconds
Processing File: RM505_APE_ONLY_ENO_09w23_v0.072.fpsx
Boot...
Pooling for ADL device...
\\?\nmwcd#vid_0421&pid_0105&if_oth#6&1b06a9af&1&00#{4f919102-4adf-11d5-882d-00b0d02fe381}
Erase[0.00 MB]...
in 0.05s
Flash[2.75 MB]...in 1.14s
* * Processed file in 1.28 seconds
Restarting device...
Pooling for device removal...
Device disconnected.
* * * Phone flashing done in 1:31 minutes
Post Flash serial tunning of phone....
Pooling mode for full factory set...
Phone not responding, try to set manually! Please, tell me if this is software problem ! Thanks in advance, Ivailo |
 |
|
12-07-2011, 14:48
| #3 (permalink) |
| Freak Poster Join Date: Aug 2003 Location: Bulgaria Age: 36
Posts: 254
Member: 37668 Status: Offline Thanks Meter: 15 | I have tried Cyclone via FBUS but with no success: Code: Initializing FBUS... All initialized - Ready to work Failed to read info -> Phone not detected Retrieving Variants for Product RM-507 - wait... 3 Variants Retrieved Processing pre flash tasks... Pre flash tasks finished, continuing... Processing RM-507_22.2.110_prd.core.C00 (CMT)... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101031103 CMT_EM_ASIC_ID: 00000296 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 09B00014BBDA01583E709EA1121AF946A62E4C75 CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE CMT_BOOT_ROM_CRC: 4B9B7510 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! RM-507_22.2.110_prd.core.C00, Type: Flash Image, Algo: XSR 1.5, BB5 Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.11.24.0, Algo: BB5 Flashbus Write baud set to 650Kbits Flashbus Read baud set to 98Kbits Using NEW BB5 FLASHING PROTOCOL Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 If software STUCK HERE with box TX LED lit, that means: 1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!) 2. Your cable is not TX2 Enabled! 3. Transmission error occured, try again In either cases, you need to reconnect your box from USB. FlashChip[0,CMT]: 0x0000000000000000, Unknown, RAM FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC FlashChip[0,CMT]: 0x0400000000000000, Unknown, NOR FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR FlashChip[0,CMT]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.11.24.0, Algo: XSR 1.5 Initializing TurboCache... TurboCache Loaded! Writing CMT PASUBTOC Certificate... Writing CMT ALG Certificate... CMT Algorithm Ready! Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Adding FUR Client (CMT, State: Ready)... CMT FUR Ready! Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: DAEF2C397A3F8FC5CA8B1F429D73C94C4A25B15B Flashbus Write baud set to 5.0Mbits Sending Certificates... Certificates OK Partitioning... Partitioning OK Started group flash erase EraseArea[0,CMT]: 0x00040000-0x00082FFF, ONENAND EraseArea[0,CMT]: 0x00083400-0x003FFFFF, ONENAND EraseArea[0,CMT]: 0x00800000-0x00D5FFFF, ONENAND EraseArea[0,CMT]: 0x00D60000-0x0AB9FFFF, ONENAND Erase Partition (CMT) Waiting 320s for erasure finish... Erase taken 0.984s Writing all blocks... Initializing TurboCache... TurboCache Loaded! Writing CMT ADA Certificate... Writing CMT KEYS Certificate... Writing CMT PRIMAPP Certificate... Writing CMT RAP3NAND Certificate... Writing CMT PASUBTOC Certificate... Writing CMT PAPUBKEYS Certificate... Writing CMT SOS*UPDAPP Certificate... Writing CMT SOS*DSP0 Certificate... Writing CMT SOS*ISASW Certificate... Writing CMT SOS+CORE Certificate... Writing CMT SOS+ROFS1 Certificate... Programming Status OK! All blocks written OK! Time taken 121.922s Flashing Speed: 7316.69 kBit/S Restarting MCU... Processing RM-507_22.2.110_prd.core.C00 (APE)... Processing RM-507_22.2.110_prd.rofs2.V28 (CMT)... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101031103 CMT_EM_ASIC_ID: 00000296 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 09B00014BBDA01583E709EA1121AF946A62E4C75 CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE CMT_BOOT_ROM_CRC: 4B9B7510 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! RM-507_22.2.110_prd.rofs2.V28, Type: Flash Image, Algo: XSR 1.5, BB5 Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.11.24.0, Algo: BB5 Flashbus Write baud set to 650Kbits Flashbus Read baud set to 98Kbits Using NEW BB5 FLASHING PROTOCOL Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 If software STUCK HERE with box TX LED lit, that means: 1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!) 2. Your cable is not TX2 Enabled! 3. Transmission error occured, try again In either cases, you need to reconnect your box from USB. FlashChip[0,CMT]: 0x0000000000000000, Unknown, RAM FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC FlashChip[0,CMT]: 0x0400000000000000, Unknown, NOR FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR FlashChip[0,CMT]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.11.24.0, Algo: XSR 1.5 Initializing TurboCache... TurboCache Loaded! Writing CMT PASUBTOC Certificate... Writing CMT ALG Certificate... CMT Algorithm Ready! Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Adding FUR Client (CMT, State: Ready)... CMT FUR Ready! Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: DAEF2C397A3F8FC5CA8B1F429D73C94C4A25B15B Flashbus Write baud set to 5.0Mbits Started group flash erase EraseArea[0,CMT]: 0x079A0000-0x09C9FFFF, ONENAND Waiting 320s for erasure finish... Erase taken 0.203s Writing all blocks... Initializing TurboCache... TurboCache Loaded! Writing CMT SOS+ROFS2 Certificate... Programming Status OK! All blocks written OK! Time taken 28.250s Flashing Speed: 7086.38 kBit/S Restarting MCU... Processing RM-507_22.2.110_prd.rofs2.V28 (APE)... Processing RM-507_22.2.110_C01_prd.rofs3.fpsx (CMT)... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101031103 CMT_EM_ASIC_ID: 00000296 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 09B00014BBDA01583E709EA1121AF946A62E4C75 CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE CMT_BOOT_ROM_CRC: 4B9B7510 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! RM-507_22.2.110_C01_prd.rofs3.fpsx, Type: Flash Image, Algo: XSR 1.5, BB5 Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.11.24.0, Algo: BB5 Flashbus Write baud set to 650Kbits Flashbus Read baud set to 98Kbits Using NEW BB5 FLASHING PROTOCOL Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 If software STUCK HERE with box TX LED lit, that means: 1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!) 2. Your cable is not TX2 Enabled! 3. Transmission error occured, try again In either cases, you need to reconnect your box from USB. FlashChip[0,CMT]: 0x0000000000000000, Unknown, RAM FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC FlashChip[0,CMT]: 0x0400000000000000, Unknown, NOR FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR FlashChip[0,CMT]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.11.24.0, Algo: XSR 1.5 Initializing TurboCache... TurboCache Loaded! Writing CMT PASUBTOC Certificate... Writing CMT ALG Certificate... CMT Algorithm Ready! Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Adding FUR Client (CMT, State: Ready)... CMT FUR Ready! Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: DAEF2C397A3F8FC5CA8B1F429D73C94C4A25B15B Flashbus Write baud set to 5.0Mbits Started group flash erase EraseArea[0,CMT]: 0x09CA0000-0x0AB9FFFF, ONENAND Waiting 320s for erasure finish... Erase taken 0.93s Writing all blocks... Initializing TurboCache... TurboCache Loaded! Writing CMT SOS+ROFS3 Certificate... Programming Status OK! All blocks written OK! Time taken 0.93s Flashing Speed: 793.81 kBit/S Restarting MCU... Processing RM-507_22.2.110_C01_prd.rofs3.fpsx (APE)... Processing RM505_507_22.0.110_uda_9_001.uda.fpsx (CMT)... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101031103 CMT_EM_ASIC_ID: 00000296 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 09B00014BBDA01583E709EA1121AF946A62E4C75 CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE CMT_BOOT_ROM_CRC: 4B9B7510 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! RM505_507_22.0.110_uda_9_001.uda.fpsx, Type: Flash Image, Algo: XSR 1.5, BB5 Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.11.24.0, Algo: BB5 Flashbus Write baud set to 650Kbits Flashbus Read baud set to 98Kbits Using NEW BB5 FLASHING PROTOCOL Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 If software STUCK HERE with box TX LED lit, that means: 1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!) 2. Your cable is not TX2 Enabled! 3. Transmission error occured, try again In either cases, you need to reconnect your box from USB. FlashChip[0,CMT]: 0x0000000000000000, Unknown, RAM FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC FlashChip[0,CMT]: 0x0400000000000000, Unknown, NOR FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR FlashChip[0,CMT]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.11.24.0, Algo: XSR 1.5 Initializing TurboCache... TurboCache Loaded! Writing CMT PASUBTOC Certificate... Writing CMT ALG Certificate... CMT Algorithm Ready! Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Adding FUR Client (CMT, State: Ready)... CMT FUR Ready! Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: DAEF2C397A3F8FC5CA8B1F429D73C94C4A25B15B Flashbus Write baud set to 5.0Mbits Started group flash erase EraseArea[0,CMT]: 0x0ABA0000-0x0F71FFFF, ONENAND Waiting 320s for erasure finish... Erase taken 0.422s Writing all blocks... Initializing TurboCache... TurboCache Loaded! Programming Status OK! All blocks written OK! Time taken 11.343s Flashing Speed: 6500.53 kBit/S Restarting MCU... Processing RM505_507_22.0.110_uda_9_001.uda.fpsx (APE)... Processing RM505_APE_ONLY_ENO_09w23_v0.072.fpsx (CMT)... Booting CMT... CMT_SYSTEM_ASIC_ID: 000000010000022600010006400C192101031103 CMT_EM_ASIC_ID: 00000296 CMT_EM_ASIC_ID: 00000B22 CMT_PUBLIC_ID: 09B00014BBDA01583E709EA1121AF946A62E4C75 CMT_ASIC_MODE_ID: 00 CMT_ROOT_KEY_HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE CMT_BOOT_ROM_CRC: 4B9B7510 CMT_SECURE_ROM_CRC: 3E691FF8 CMT Ready! RM505_APE_ONLY_ENO_09w23_v0.072.fpsx, Type: Flash Image, Algo: XSR 1.5, BB5 Searching for BootCode: DualLine 32Bit RAPIDOv11_2nd.fg, Type: 2nd Boot Loader, Rev: 512.11.24.0, Algo: BB5 Flashbus Write baud set to 650Kbits Flashbus Read baud set to 98Kbits Using NEW BB5 FLASHING PROTOCOL Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 If software STUCK HERE with box TX LED lit, that means: 1. You have not attached yellow TX2 Adapter (IT IS REQUIRED FOR BB5 PHONES WHEN USING JAF/UFS CABLES!) 2. Your cable is not TX2 Enabled! 3. Transmission error occured, try again In either cases, you need to reconnect your box from USB. FlashChip[0,CMT]: 0x0000000000000000, Unknown, RAM FlashChip[0,CMT]: 0xFFFF000000000000, Unknown, MMC FlashChip[0,CMT]: 0x0400000000000000, Unknown, NOR FlashChip[1,CMT]: 0x0000000100000000, Unknown, NOR FlashChip[0,CMT]: 0x00EC004000000121, Samsung, ONENAND Requested Algorithm: XSR 1.5 (CMT) Searching for BootCode: DualLine 32Bit FlashChip 0x00EC0040 (Samsung), Size: 256MBytes, VPP: Not Supported RAPIDOv11_XSR15_alg.fg, Type: Algorithm, Rev: 512.11.24.0, Algo: XSR 1.5 Initializing TurboCache... TurboCache Loaded! Writing CMT PASUBTOC Certificate... Writing CMT ALG Certificate... CMT Algorithm Ready! Default Transmission Mode Requested by Loader: Dual Line, 32 bit, Overriding Transmission Mode Requested: Dual Line, 32 bit, Accepted: Dual Line, 32 bit Box TX2 Data Pin set to: Service Pin 3 Adding FUR Client (CMT, State: Ready)... CMT FUR Ready! Box VPP disabled Internal CMT Phone VPP Enabled PAPUBKEYS Hash for CMT: DAEF2C397A3F8FC5CA8B1F429D73C94C4A25B15B Flashbus Write baud set to 5.0Mbits Sending Certificates... Certificates OK Started group flash erase EraseArea[0,CMT]: 0x00400000-0x007FFFFF, ONENAND Waiting 320s for erasure finish... Erase taken 0.32s Writing all blocks... Initializing TurboCache... TurboCache Loaded! Writing CMT SOS*ENO Certificate... Programming Status OK! All blocks written OK! Time taken 3.297s Flashing Speed: 6996.25 kBit/S Restarting MCU... Processing RM505_APE_ONLY_ENO_09w23_v0.072.fpsx (APE)... All images processed OK! Processing post flash tasks... Setting Factory Defaults... May be hardware problem ? |
| |
|
| Bookmarks |
| |
Similar Threads | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Help with 6110 | paulomt1 | Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L ) | 2 | 05-25-2009 16:29 |
| NHE_8 wont work with NHEK5689.dll v3 | steve | Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L ) | 0 | 07-23-1999 15:48 |
| HELP: Problem with 5110 | Xabi | Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L ) | 1 | 07-16-1999 00:44 |
| Netmonitor with FBus???? | ratzfatz | Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L ) | 4 | 06-09-1999 17:04 |
|
|
Linear Mode
