x2-02 contact service

[kabul]

Flash log;

Number of Image Files: 3

Processing Image File : 
 rm694__10.90.mcusw
Processing Image File : 
 rm694__10.90.ppm_r
Processing Image File : 
 rm694__10.90.image_r_059D7R6_059M795_276_01


AUTO SELECTED DEAD USB FLASHING...

 If Flashing DOES NOT Start in 5 Seconds,
 Then Perform Steps 1, 2, 3 and 4...

1. Remove USB and Battery...
2. Insert USB.
3. Insert Battery. (Some phones boot automatically)
4. Please Power on phone shortly...


Infineon USB Boot: F00A1FB300020303010100FF
Sending PBL...
PBL Successfully Sent...
Sending SBL...
SBL Successfully Sent...
Setting Transmission Speed Done...
Flash Chip Manufacturer: Intel Electronics Corp.
Flash Boot Successful...



Sections         : 04
Current File    : rm694__10.90.mcusw
Compile Name: rm694__10.90.mcusw_ebl_psi.fls
Image Type   : Main Firmware
Data Size       : 27528584 Bytes

Sending Certificate Block
FIRMWARE Certificate Block Sent Successfully...
 Processing Section 01 of 04
FIRMWARE Erase Block: 0x40000000~0x4001FFFE
Start Erasing...
Erasing Please Wait...
Block Erase Done...
Preparing Data Blocks...
Data Size: 131072 bytes
Data Checksum: CCF5
Uploading Data Blocks to phone...
Block Write Successful...
FIRMWARE Data Blocks uploaded to phone...
 Processing Section 02 of 04
FIRMWARE Erase Block: 0x40040000~0x4005FFFE
Start Erasing...
Erasing Please Wait...
Block Erase Done...
Preparing Data Blocks...
Data Size: 131072 bytes
Data Checksum: 7ACE
Uploading Data Blocks to phone...
Block Write Successful...
FIRMWARE Data Blocks uploaded to phone...
 Processing Section 03 of 04
FIRMWARE Erase Block: 0x40060000~0x4015FFFE
Start Erasing...
Erasing Please Wait...
Block Erase Done...
Preparing Data Blocks...
Data Size: 1048576 bytes
Data Checksum: B83E
Uploading Data Blocks to phone...
Block Write Successful...
FIRMWARE Data Blocks uploaded to phone...
 Processing Section 04 of 04
FIRMWARE Erase Block: 0x40280000~0x41BFFFFE
Start Erasing...
Erasing Please Wait...
Block Erase Done...
Preparing Data Blocks...
Data Size: 26214400 bytes
Data Checksum: DB4E
Uploading Data Blocks to phone...
Block Write Successful...
FIRMWARE Data Blocks uploaded to phone...
Data Verification Successful...


Sections         : 01
Current File    : rm694__10.90.ppm_r
Compile Name: package_r.ppm_ebl_psi.fls
Image Type   : PPM Image
Data Size       : 5374292 Bytes

Sending Certificate Block
PPM Certificate Block Sent Successfully...
 Processing Section 01 of 01
PPM Erase Block: 0x41C00000~0x422FFFFE
Start Erasing...
Erasing Please Wait...
Block Erase Done...
Preparing Data Blocks...
Data Size: 5370948 bytes
Data Checksum: 06D3
Uploading Data Blocks to phone...
Block Write Successful...
PPM Data Blocks uploaded to phone...
Data Verification Successful...


Sections         : 01
Current File    : rm694__10.90.image_r_059D7R6_059M795_276_01
Compile Name: rm694__10.90.image_r_059D7R6_059M795_276_01.fls
Image Type   : CONTENT Package
Data Size       : 15207696 Bytes

Sending Certificate Block
CONTENT Certificate Block Sent Successfully...
 Processing Section 01 of 01
CONTENT Erase Block: 0x42300000~0x43E1FFFE
Start Erasing...
Erasing Please Wait...
Block Erase Done...
Preparing Data Blocks...
Data Size: 15204352 bytes
Data Checksum: 1955
Uploading Data Blocks to phone...
Block Write Successful...
CONTENT Data Blocks uploaded to phone...
Data Verification Successful...

[kabul]

solved my probllem jast flash for BB5 Easy Service Tool (BEST)


Log;

card found: S/N xxxxxxxxxxx
registered to: Kabul

Connect phone on selected interface...

Connect phone on selected interface...

Core : v1.42 , FlashEngine : v1.25

Selected FlashSettings : FullFlash
Check FlashFiles, Please, wait...

Files Set for Flashing :
MCU : rm694__10.90.mcusw
PPM : rm694__10.90.ppm_r
CNT : rm694__10.90.image_r_059D7R6_059M795_276_01
Flashing phone now...
Check files done...
-> SWversion check skipped : Dead mode selected
Dead Mode is Selected
Waiting for USB device...

-> If Windows say "Unrecognized device" - just reinsert battery
-> If flashing freeze - reinsert cable and try again
--- Press phone's power button or insert charger! ---

Connection opened successfully
DBG : F00A1FB300020303010100FF
CPUID : SGOLD 213
2nd boot Ok, 01
2nd ready, AA
Sending Algo
Algo sent Ok
BL : Quantum_Bootloader_10.46_M1S1
Speed accepted, use 6.500.000
FLASHID : 89008289
FLIC conf set, RST set
Boot done!

   ===Flashing [MCU]===
File : rm694__10.90.mcusw
Image : rm694__10.90.mcusw_ebl_psi.fls
Cert block found, sending....
Cert sent
Found 5 region(s)
Processing Region 1/5
Erase , Start : 0x40000000 , Len : 0x00020000
Erasing, wait ... 
Erase done, time : 00:00:00 
Write , Start : 0x40000000 , Len : 0x00020000
Flashing , wait ...
Region flash done, time : 00:00:00
Processing Region 2/5
Erase , Start : 0x40040000 , Len : 0x00020000
Erasing, wait ... 
Erase done, time : 00:00:00 
Write , Start : 0x40040000 , Len : 0x00020000
Flashing , wait ...
Region flash done, time : 00:00:00
Processing Region 3/5
Erase , Start : 0x40060000 , Len : 0x00100000
Erasing, wait ... 
Erase done, time : 00:00:06 
Write , Start : 0x40060000 , Len : 0x00100000
Flashing , wait ...
Region flash done, time : 00:00:01
Processing Region 4/5
Erase , Start : 0x40280000 , Len : 0x01980000
Erasing, wait ... 
Erase done, time : 00:02:23 
Write , Start : 0x40280000 , Len : 0x01900000
Flashing , wait ...
Region flash done, time : 00:00:50
Processing Region 5/5
Erase , Start : 0x43E20000 , Len : 0x00040000
Erasing, wait ... 
Erase done, time : 00:00:00 
No write data, skip

   ===Flashing [PPM]===
File : rm694__10.90.ppm_r
Image : package_r.ppm_ebl_psi.fls
Cert block found, sending....
Cert sent
Found 1 region(s)
Processing Region 1/1
Erase , Start : 0x41C00000 , Len : 0x00700000
Erasing, wait ... 
Erase done, time : 00:00:28 
Write , Start : 0x41C00000 , Len : 0x0051F444
Flashing , wait ...
Region flash done, time : 00:00:07

   ===Flashing [CNT]===
File : rm694__10.90.image_r_059D7R6_059M795_276_01
Image : rm694__10.90.image_r_059D7R6_059M795_276_01.fls
Cert block found, sending....
Cert sent
Found 2 region(s)
Processing Region 1/2
Erase , Start : 0x42300000 , Len : 0x01B20000
Erasing, wait ... 
Erase done, time : 00:01:26 
Write , Start : 0x42300000 , Len : 0x00E80000
Flashing , wait ...
Region flash done, time : 00:00:24
Processing Region 2/2
Erase , Start : 0x43E60000 , Len : 0x000E0000
Erasing, wait ... 
Erase done, time : 00:00:05 
No write data, skip

Flashing done!
Total flash time : 00:05:55
Reboot phone now...

Reading Phone Info....
Connected phone -   X2-02
Software Info:     V 10.90 12-12-11 RM-694 (c) Nokia            
IMEI:  351695054354446
PPM version :   V 10.90 12-12-11 RM-694 (c) Nokia             R
Product code:  059D1B3
Checking...
SimLock status : SimLock is Ok
Security status : Security is Ok
Read Info Done!
Settings After Flash Defaults...
ProductTuneSet...OK!
SwUpgradeSet...OK!
Checking User Certificates...
Total - 42 certs
Data exist, skip certificate repair...
Set phone to Normal mode...

AfterFlash operations done ;D
Done!
Connect phone on selected interface...


Elapsed: 00:06:57
Connect phone on selected interface...

[atif ikram]

Post scan logs bec in logs SD is not clear and also tell is connects service show in start up or after Nokia logs?!??

[kabul]

Originally Posted by atif ikram

Post scan logs bec in logs SD is not clear and also tell is connects service show in start up or after Nokia logs?!??

no bro start up after connects service show

[srinibas]

Flashing is not the solution of Contact Service or you can say Contact Service never fix by flashing .


Br - srinibas

[willydewi]

X2-02 Contact Service Problem Solved Using Phoenix Crack

Flashing started
Creating product data items list
Product data items list created
Backup not required
Flashing phone
Initializing
Download files list initiated
Waiting for USB device...
Booting...
Boot failure (0x8401F182)
Failed to boot device
Flash operation failed
Starting to recover the phone
Recovering phone
Initializing
Download files list initiated
Booting...
Sending EBL loader...
Sending EBL...
Boot successful
Downloading file: rm694__10.90.mcusw
Erasing 131070 bytes...
Total progress: 6%
Sending data...
Total progress: 13%
Erasing 131070 bytes...
Total progress: 20%
Sending data...
Total progress: 26%
Erasing 1048574 bytes...
Total progress: 29%
Total progress: 31%
Sending data...
Total progress: 40%
Erasing 26214398 bytes...
Total progress: 42%
Total progress: 44%
Total progress: 46%
Sending data...
Total progress: 48%
Total progress: 50%
Total progress: 52%
Erasing 262142 bytes...
Total progress: 56%
Total progress: 60%
Downloading file: rm694__10.90.ppm_x
Erasing 5812158 bytes...
Total progress: 62%
Total progress: 64%
Total progress: 66%
Total progress: 68%
Sending data...
Total progress: 71%
Total progress: 75%
Total progress: 79%
Downloading file: rm694__10.90.image_x_059D1V9
Erasing 15597566 bytes...
Total progress: 81%
Total progress: 83%
Total progress: 85%
Sending data...
Total progress: 87%
Total progress: 89%
Total progress: 91%
Erasing 917502 bytes...
Total progress: 94%
Total progress: 97%
Total progress: 100%
Resetting device
Phone recovery completed. Waiting for phone to boot up
Bootup successful
Verifying communication to product (before flash finalizing)
Communication verified
Product code changed
Doing factorysets
Factorysets complete
Reading Dynamic Camera Configuration ID 1
Updating configuration of camera with ID 1
Dynamic Camera Configuration updating failed: 0x84167501 - AudioVisual: No configuration file matching the camera name string 06150123 was found.
Loading default data to phone
Loading default data to phone
Getting Data Package
Reading product state
Starting backup/restore sub-procedure: data item pre-delay
data item pre-delay
data item pre-delay
Sub-procedure completed: Succeeded., result code: 0
Starting to backup/restore data item: ProductProfile, version: 1.1
Data Item backup/restore completed: Succeeded., result code: 0
Starting backup/restore sub-procedure: data item post-delay
data item post-delay
data item post-delay
Sub-procedure completed: Succeeded., result code: 0
Starting backup/restore sub-procedure: data item pre-delay
data item pre-delay
data item pre-delay
Sub-procedure completed: Succeeded., result code: 0
Starting to backup/restore data item: DateTimeSettings, version: 1.0
Data Item backup/restore completed: Succeeded., result code: 0
Starting backup/restore sub-procedure: data item post-delay
data item post-delay
data item post-delay
Sub-procedure completed: Succeeded., result code: 0
Starting backup/restore sub-procedure: data item pre-delay
data item pre-delay
data item pre-delay
Sub-procedure completed: Succeeded., result code: 0
Starting to backup/restore data item: ISSVariantActivator, version: 1.0
Data Item backup/restore completed: Succeeded., result code: 0
Starting backup/restore sub-procedure: data item post-delay
data item post-delay
data item post-delay
Sub-procedure completed: Succeeded., result code: 0
Backup/restore result: 0 out of 3 items were not backed up
Default data loading complete
Stopping all operations, returning phone to default mode
All operations completed
Firmware updating succeeded.

[Latifkhan75]

Originally Posted by srinibas

Flashing is not the solution of Contact Service or you can say Contact Service never fix by flashing .


Br - srinibas

bro x2_02 and same family sets cotect service can be solved by flashing onl;y by best infinity dongle i try by atf but no sucess.but i personly 3 sets x2_02 repair by best dongle

[srinibas]

Originally Posted by Latifkhan75

bro x2_02 and same family sets cotect service can be solved by flashing onl;y by best infinity dongle i try by atf but no sucess.but i personly 3 sets x2_02 repair by best dongle

Not want to arguments

Again saying CS cant fix by flashing by any tool.


Br - srinibas

[willydewi]

Originally Posted by srinibas

Not want to arguments

Again saying CS cant fix by flashing by any tool.


Br - srinibas

that's your opinion ...but i did it ...tested contact service solved today

[srinibas]

Originally Posted by willydewi

that's your opinion ...but i did it ...tested contact service solved today

From your above posted log it is not proved that your set was in CS .

1st know the cause of CS in BB5, then it will clear you to understand it will fix by flashing or not .

Br - srinibas

[unuunu]

Originally Posted by srinibas

from your above posted log it is not proved that your set was in cs .

1st know the cause of cs in bb5, then it will clear you to understand it will fix by flashing or not .

br - srinibas

yes srinibas babu...you are right...cs can not be solved by flashing....

[willydewi]

Originally Posted by srinibas

From your above posted log it is not proved that your set was in CS .

1st know the cause of CS in BB5, then it will clear you to understand it will fix by flashing or not .

Br - srinibas

yes.that's my fault,i didn't take any picture of phone while contact service showing in the screen

but i said this only to give input for atf team
maybe next update can repair contact service in x2-02 ,because the other tool already can repairing contact service problem in x2-02


only that's it and no offense

[unuunu]

Originally Posted by willydewi

yes.that's my fault,i didn't take any picture of phone while contact service showing in the screen

but i said this only to give input for atf team
maybe next update can repair contact service in x2-02 ,because the other tool already can repairing contact service problem in x2-02


only that's it and no offense

but brother can u tellme plz......for which reason ur mobile was in contact service?

[Latifkhan75]

u belive or not but we did it.cs cause reset counter can repair by flashing with best dongle

[willydewi]

Originally Posted by unuunu

but brother can u tellme plz......for which reason ur mobile was in contact service?

the phone comes to my shop already contact service and i checked all component of phone ..it's all good and then i try to reheat cpu ic and flash ic but problem still same..the last i try to flash
1. flash using atf >>>still contact service
2. flash using mx-key >>>still contact service

and the last ..try flash using phoenix crack >>>phone become normal