N78 died ,Manole read this

[a38]

N78 dead after write RPL certificate not compatible with their identity in part


SIMLOCK_DATA_1 = D2A2DD2049EB9504C69E82F87C4E7AAEE89C589C8000000000 000000001010000000000000180100
SIMLOCK_DATA_2 = 000000000020000001FFFFFF000000007FFF6F07FFFFFFFFF8 0000340300050300101FFF
SIMLOCK_KEY_DATA_1 = 41AFE9E95DA1C6F5A68943F2BA66D581DA201A5AE5C7365015 2B75C2A03D13C4CBAEC8B98B2087A1
SIMLOCK_KEY_DATA_2 = 060B20F020F750D92D44A61C9E33606413C19023FB12DD1CF6 52AAA75F63957A0D54FDA75489BAB0
SIMLOCK_KEY_DATA_3 = 0E091B4532D5CD7A3B28AC0CBDD765609C484191




There is no way that I generate SIMLOCK-DATA-RPL and Superdongle Key data to be written???

always wrote the certificate to restore the IMEI but SIMLOCKDATA gave me an error saying not are compatible from ID..

So I decided to write with Jaf and there died on mobile

I'm sure the phone does not want to have the section up-DATA SIMLOCK another id


if Manole can be so kind to me and superdongle key simlockdata generate data from home

RAP Data :
SYSTEM ASIC ID: 000000010000022600010006400C192101021103 [RAPIDO3G ver: 1.11]
EM0 ID: 00000295
EM1 ID: 00000B22
PUBLIC ID: 1D10010529BA00585E0437FB9EDB5377BD6304EE
ASIC MODE ID: 00
ROOT KEY HASH: CAEEBB65D3C48E6DC73B49DC5063A2EE
ROM ID: A8C1D6713E691FF8
SecondaryBoot: RAPIDOv11_2nd.fg [BB5] version: 1.37.1 revision: 0.0 size: 0x3B80
Supported RAP Ids: 0003192101002003, 000C192101002003, 4003192101002003, 400C192101002003, 4003192101011103, 400C192101011103, 4003192101021103, 400C192101021103, 4003192101031103, 400C192101031103, 4003192101011105, 400C192101011105, 400C192101021105, 400C192101031105
FlashID0: 00EC 0040 - 0060 0022 [Samsung 2Gb DDP OneNAND,2 Gbits] type: ONENAND,RAP
ExtBUSC: 0000 0000 0000 0000 0000 0000 0000 0000
ExtDEVC: FFFF 0000 - 0000 0000
Algorithm: RAPIDOv11_algo.fg [XSR 1.5] version: 1.40.0 revision: 0.0 size: 0x27520
Supported RAP Ids: 0003192101002003, 000C192101002003, 4003192101002003, 400C192101002003, 4003192101011103, 400C192101011103, 4003192101021103, 400C192101021103, 4003192101031103, 400C192101031103, 4003192101011105, 400C192101011105, 400C192101021105, 400C192101031105
RAP PAPUBKEYS HASH: AA7BE8DEFFAE81DD0C61CB7E127E3A2962651FD6
Original Imei: 35417402023620
35417402023620/9
Original Product code: 0566014

tried to flash it but not start.

if you can generame SIMLOCK RPL DATA AND KEY SUPERDONGLE then I'm sure when writing to flash phone and re-ignite the

my backup

http://www.4shared.com/file/21797151...3620_BACK.html

[Andra]

u miss this part

You got Only NPC? NO PROBLEMO!


br,

[a38]

Originally Posted by MobileEx-Team

u miss this part

You got Only NPC? NO PROBLEMO!


br,

brother no longer works so I flashed it with higher version and big .. I also deleted it and everything and even so the phone will not start in local mode ..


the problem is in the RPL because the information invalidates SIMLOCKDATA has another identity .. when I wrote the certificate RPL the phone died instantly

[a38]

Originally Posted by MobileEx-Team

u miss this part

You got Only NPC? NO PROBLEMO!


br,

You should tell Manole that on your next update adds the ability to repair dead phones SIMLOCK RPL in because I realized that when a phone after a flash and does not respond is because the phone does not pass the safety test

[Andra]

u mean in
service -> quick fix -> bb5 downgrade fix ?


br,

[a38]

Originally Posted by MobileEx-Team

u mean in
service -> quick fix -> bb5 downgrade fix ?


br,

try doing that and nothing does not work

Friend I only ask this:


MX has the power to write lines simlock_data when the telephone esta dead ..??

Example: I know that Pk has the power to write lines HWC CCC NPC when the phone is dead

SIMLOCKDATA lines when they are written to the force yet compatible with the phone kills



I ask them to add power to repair SIMLOCKDATA in dead phones on ..


because my RPL SIMLOCKDATA have information corrupt

not allowing light in the local mode after flash

[eumore79]

why not use usb cable. use mxkey via usb cable.

[a38]

Originally Posted by eumore79

why not use usb cable. use mxkey via usb cable.

I already did and is not responding and not believe phone failure

because the phone never been affected

[a38]

Originally Posted by a38

try doing that and nothing does not work

Friend I only ask this:


MX has the power to write lines simlock_data when the telephone esta dead ..??

Example: I know that Pk has the power to write lines HWC CCC NPC when the phone is dead

SIMLOCKDATA lines when they are written to the force yet compatible with the phone kills



I ask them to add power to repair SIMLOCKDATA in dead phones on ..


because my RPL SIMLOCKDATA have information corrupt

not allowing light in the local mode after flash

help MobileEx-Team

informed to Manole about the problem to see if bad writing RPL SIMLOCK_DATA

[Andra]

can u include the LOG,
where the "BAD WRITING RPL SIMLOCK_DATA"
and upload RPL data ?


br,

[a38]

Originally Posted by MobileEx-Team

can u include the LOG,
where the "BAD WRITING RPL SIMLOCK_DATA"
and upload RPL data ?


br,

I have no record

Damage months ago

but it was the same case of this:http://forum.gsmhosting.com/vbb/show...55#post5388455

My backup:http://www.4shared.com/file/21797151...3620_BACK.html

add REPAIR SIMLOCKDATA RPL for phones died..


My phone can not enter local mode after the flashing

by have misspelled SIMLOCK_DATA RPL

[lilong_lee]

This problem we can solve if you have all back up section if you not back up all section you need buy rpl .........

[a38]

Originally Posted by REDZTER

use tma cable for interface to stable in local mode !

what is the condition of unit ?

DEAD mi friend

is one problema in the certifiacte rpl

[a38]

Originally Posted by lilong_lee

This problem we can solve if you have all back up section if you not back up all section you need buy rpl .........

is that not even turn on in local mode,


then how could he do to write RPL

I own the backup

what happens is that my backup in this party data

SIMLOCK_DATA_1=D2A2DD2049EB9504C69E82F87C4E7AAEE89 C589C8000000000000000001010000000000000180100
SIMLOCK_DATA_2=000000000020000001FFFFFF000000007FF F6F07FFFFFFFFF80000340300050300101FFF
SIMLOCK_KEY_DATA_1=41AFE9E95DA1C6F5A68943F2BA66D58 1DA201A5AE5C73650152B75C2A03D13C4CBAEC8B98B2087A1
SIMLOCK_KEY_DATA_2=060B20F020F750D92D44A61C9E33606 413C19023FB12DD1CF652AAA75F63957A0D54FDA75489BAB0
SIMLOCK_KEY_DATA_3=0E091B4532D5CD7A3B28AC0CBDD7656 09C484191

Not the phone with my identity