all security test failed 100% solution! (TIPS) (ANSWERED) - GSM-Forum

akashrana_sky · 06-23-2010, 20:17

Many people posted in this forum about security test failed !

we know that_______
when come security test failed ______

solution_____
1. super sd auth or pmm auth __than write good or modified pm ( must need pm 1 & 309)
or, 2. sd repair ___ super sd auth or pmm auth ____ than write good or modified pm ( must need pm 1 & 309)

My question ______
when we not success by up system
than what can we do for repair security test failed?

yes! we have this solution______

1. first backup rpl ( go > imei and security tab > imei rebuild > backup rpl)
2. erase old pm ( go > pm tab > erase )
3. Reset npc data ( go> imei and security tab> reset NPC data)( must backup rpl before do this)
4. Erase pm again (go > pm tab > erase )
5.Write rpl from backup ( go > imei and security tab > imei rebuild > restore imei)
6. go pm tab > super sd auth or pmm auth > than write good or modified pm ( must need pm 1 & 309)

7. erase pm again

8. Recover CERT ( go>imei and security tab> imei rebuild > recover cert)
9. give full factory reset

your phone must come back from security test failed
it is 100% tasted by me.

Don't forget to press thanks button !

unicomtogo · 06-23-2010, 20:27

Quote:

Originally Posted by akashrana_sky

Many people posted in this forum about security test failed !

we know that_______
when come security test failed ______

solution_____
1. super sd auth or pmm auth __than write good or modified pm ( must need pm 1 & 309)
or, 2. sd repair ___ super sd auth or pmm auth ____ than write good or modified pm ( must need pm 1 & 309)

My question ______
when we not success by up system
than what can we do for repair security test failed?

yes! we have this solution______

1. first backup rpl ( go > imei and security tab > imei rebuild > backup rpl)
2. erase old pm ( go > pm tab > erase )
3. Reset npc data ( go> imei and security tab> reset NPC data)( must backup rpl before do this)
4. Erase pm again (go > pm tab > erase )
5.Write rpl from backup ( go > imei and security tab > imei rebuild > restore imei)
6. go pm tab > super sd auth or pmm auth > than write good or modified pm ( must need pm 1 & 309)

7. erase pm again

8. Recover CERT ( go>imei and security tab> imei rebuild > recover cert)
9. give full factory reset

your phone must come back from security test failed
it is 100% tasted by me.

Don't forget to press thanks button !

a thread about security test fail was posted already in this forum by Mr Hasnain. so useful

akashrana_sky · 06-23-2010, 20:41

Quote:

Originally Posted by unicomtogo

a thread about security test fail was posted already in this forum by Mr Hasnain. so useful

i don't see this by search______
but it is my real and own!

thanks of replay!

dil7689 · 06-23-2010, 20:43

thanks to post

good job

kamrancool · 07-02-2010, 09:19

if this u not post this im gonig to die lots lots and lots of thanks

mahir ashab · 07-02-2010, 10:11

yes br. this is old story but always new for new users. of course very good job akashrana. many thanks.

thanks
mahir ashab

mitobest · 07-02-2010, 16:25

thanks.....bigboss......

naurah · 07-02-2010, 16:36

great job..thxxxxxxxx

joker1222000 · 07-03-2010, 10:53

tested & work 10000000000000000000000000%

sagi2 · 07-03-2010, 13:03

Nokia 3120c-1c RM-364
8. Recover CERT ( go>imei and security tab> imei rebuild > recover cert)

Begin Certificate Request ...

[InternalErrorFault] CERT [0565888] data not found in database (case id=0xCE02)

what now...? wait..?

delwar_us · 07-03-2010, 13:08

thanks brother for good solution

harisa · 07-08-2010, 08:17

SERVER->Served by MXKEY - BLADE X at host1, agent version 1.1 revision 0.1

Using device: UFS_USB V2.8 (c) SarasSoft 2007.
Library version: 1.0.0.8929(24-06-2010), 1.0.0.14574(24-06-2010)

Product: V 07.20 05-10-09 RM-243 (c) Nokia
ApeCoreSw: 07.20

Using cached productData[145000105B5E0058A5C0577980BD3FC057D0586E] ...

Authenticating to SUPERDONGLE using security server ...
SUPERDONGLE authorized

!
Writing PM from Node ...
Section: 1
- Key: 0, size 114 bytes written.
- Key: 1, size 4 bytes written.
- Key: 2, size 98 bytes written.
- Key: 4, size 110 bytes written.
- Key: 5, size 4 bytes written.
- Key: 6, size 98 bytes written.
- Key: 8, size 110 bytes written.
- Key: 13, size 98 bytes written.
- Key: 15, size 4 bytes written.
- Key: 16, size 98 bytes written.
- Key: 18, size 98 bytes written.
- Key: 20, size 98 bytes written.
- Key: 22, size 16 bytes written.
- Key: 23, size 4 bytes written.
- Key: 24, size 84 bytes written.
- Key: 25, size 4 bytes written.
- Key: 26, size 110 bytes written.
- Key: 27, size 4 bytes written.
- Key: 28, size 98 bytes written.
- Key: 29, size 10 bytes written.
- Key: 31, size 98 bytes written.
- Key: 33, size 36 bytes written.
- Key: 34, size 80 bytes written.
- Key: 40, size 16 bytes written.
- Key: 41, size 182 bytes written.
- Key: 42, size 4 bytes written.
- Key: 43, size 36 bytes written.
Warning: failed to write 1 - 44 (182 bytes)
- Key: 46, size 64 bytes written.
Section: 309
- Key: 0, size 4 bytes written.
- Key: 1, size 2 bytes written.
- Key: 2, size 12 bytes written.
- Key: 4, size 12 bytes written.
- Key: 5, size 12 bytes written.
- Key: 7, size 12 bytes written.
- Key: 8, size 12 bytes written.
- Key: 17, size 12 bytes written.
Completed in 2.875 s
Writing PM from Node ...
Section: 1
- Key: 0, size 114 bytes written.
- Key: 1, size 4 bytes written.
- Key: 2, size 98 bytes written.
- Key: 4, size 110 bytes written.
- Key: 5, size 4 bytes written.
- Key: 6, size 98 bytes written.
- Key: 8, size 110 bytes written.
- Key: 13, size 98 bytes written.
- Key: 15, size 4 bytes written.
- Key: 16, size 98 bytes written.
- Key: 18, size 98 bytes written.
- Key: 20, size 98 bytes written.
- Key: 22, size 16 bytes written.
- Key: 23, size 4 bytes written.
- Key: 24, size 84 bytes written.
- Key: 25, size 4 bytes written.
- Key: 26, size 110 bytes written.
- Key: 27, size 4 bytes written.
- Key: 28, size 98 bytes written.
- Key: 29, size 10 bytes written.
- Key: 31, size 98 bytes written.
- Key: 33, size 36 bytes written.
- Key: 34, size 80 bytes written.
- Key: 40, size 16 bytes written.
- Key: 41, size 182 bytes written.
- Key: 42, size 4 bytes written.
- Key: 43, size 36 bytes written.
Warning: failed to write 1 - 44 (182 bytes)
- Key: 46, size 64 bytes written.
Section: 309
- Key: 0, size 4 bytes written.
- Key: 1, size 2 bytes written.
- Key: 2, size 12 bytes written.
- Key: 4, size 12 bytes written.
- Key: 5, size 12 bytes written.
- Key: 7, size 12 bytes written.
- Key: 8, size 12 bytes written.
- Key: 17, size 12 bytes written.
Completed in 2.844 s
Writing PM from Node ...
Section: 1
- Key: 0, size 114 bytes written.
- Key: 1, size 4 bytes written.
- Key: 2, size 98 bytes written.
- Key: 4, size 110 bytes written.
- Key: 5, size 4 bytes written.
- Key: 6, size 98 bytes written.
- Key: 8, size 110 bytes written.
- Key: 13, size 98 bytes written.
- Key: 15, size 4 bytes written.
- Key: 16, size 98 bytes written.
- Key: 18, size 98 bytes written.
- Key: 20, size 98 bytes written.
- Key: 22, size 16 bytes written.
- Key: 23, size 4 bytes written.
- Key: 24, size 84 bytes written.
- Key: 25, size 4 bytes written.
- Key: 26, size 110 bytes written.
- Key: 27, size 4 bytes written.
- Key: 28, size 98 bytes written.
- Key: 29, size 10 bytes written.
- Key: 31, size 98 bytes written.
- Key: 33, size 36 bytes written.
- Key: 34, size 80 bytes written.
- Key: 40, size 16 bytes written.
- Key: 41, size 182 bytes written.
- Key: 42, size 4 bytes written.
- Key: 43, size 36 bytes written.
Warning: failed to write 1 - 44 (182 bytes)
- Key: 46, size 64 bytes written.
Section: 309
- Key: 0, size 4 bytes written.
- Key: 1, size 2 bytes written.
- Key: 2, size 12 bytes written.
- Key: 4, size 12 bytes written.
- Key: 5, size 12 bytes written.
- Key: 7, size 12 bytes written.
- Key: 8, size 12 bytes written.
- Key: 17, size 12 bytes written.
Completed in 2.906 s
how to repair warning failed to write 1-44[182 bytes]

A-H-T · 07-08-2010, 10:54

will try soon and post feedback

wbr.

andre128 · 07-15-2010, 08:32

mine is superdongle invalid, after repair sd become security test failed.

i follow method sucess fix security test failed but now back to superdongle invalid

defrianto · 07-15-2010, 08:50

thanks brother for good solution............

06-23-2010, 20:17	#1 (permalink)
akashrana_sky No Life Poster Join Date: Jan 2010 Location: Bangladesh Posts: 1,091 Member: 1220933 Status: Offline Sonork: 100.1590184 Thanks Meter: 471	all security test failed 100% solution! (TIPS) (ANSWERED) Many people posted in this forum about security test failed ! we know that_______ when come security test failed ______ solution_____ 1. super sd auth or pmm auth __than write good or modified pm ( must need pm 1 & 309) or, 2. sd repair ___ super sd auth or pmm auth ____ than write good or modified pm ( must need pm 1 & 309) My question ______ when we not success by up system than what can we do for repair security test failed? yes! we have this solution______ 1. first backup rpl ( go > imei and security tab > imei rebuild > backup rpl) 2. erase old pm ( go > pm tab > erase ) 3. Reset npc data ( go> imei and security tab> reset NPC data)( must backup rpl before do this) 4. Erase pm again (go > pm tab > erase ) 5.Write rpl from backup ( go > imei and security tab > imei rebuild > restore imei) 6. go pm tab > super sd auth or pmm auth > than write good or modified pm ( must need pm 1 & 309) 7. erase pm again 8. Recover CERT ( go>imei and security tab> imei rebuild > recover cert) 9. give full factory reset your phone must come back from security test failed it is 100% tasted by me. Don't forget to press thanks button !

07-02-2010, 09:19	#5 (permalink)
kamrancool Junior Member Join Date: May 2010 Location: pakistan Posts: 8 Member: 1309734 Status: Offline Sonork: adnanishaque_korai Thanks Meter: 2	lots of thanks if this u not post this im gonig to die lots lots and lots of thanks

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Anybody know solution	Robi	Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L )	1	12-10-2014 12:35
where to find a working program all they have some errors ??	fondas	Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L )	2	12-12-2012 13:26
Solution for GSM phones!?!?!?!?	todosije	Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L )	6	12-16-2010 05:52
All 4 locks on 6110	steve	Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L )	2	04-19-2010 02:44
all for GSM: http://fly.to/spear	spear	GSM Mobile Links	0	07-11-1999 22:01

06-23-2010, 20:43	#4 (permalink)
dil7689 No Life Poster Join Date: Jul 2009 Posts: 599 Member: 1080396 Status: Offline Thanks Meter: 1,661	thanks to post good job

07-02-2010, 10:11	#6 (permalink)
mahir ashab No Life Poster Join Date: Sep 2009 Posts: 1,311 Member: 1128573 Status: Offline Thanks Meter: 242	yes br. this is old story but always new for new users. of course very good job akashrana. many thanks. thanks mahir ashab

07-02-2010, 16:25	#7 (permalink)
mitobest Insane Poster Join Date: Feb 2010 Location: manado Posts: 76 Member: 1243993 Status: Offline Sonork: +6287846666699 Thanks Meter: 12	thanks.....bigboss......

07-02-2010, 16:36	#8 (permalink)
naurah Freak Poster Join Date: Nov 2007 Location: gorontalo Posts: 121 Member: 629228 Status: Offline Thanks Meter: 17	great job..thxxxxxxxx

07-03-2010, 10:53	#9 (permalink)
joker1222000 Freak Poster Join Date: Jan 2005 Location: egypt Age: 41 Posts: 120 Member: 107987 Status: Offline Sonork: 1575070 Thanks Meter: 14	tested & work 10000000000000000000000000%

07-03-2010, 13:03	#10 (permalink)
sagi2 Junior Member Join Date: Jan 2005 Age: 44 Posts: 3 Member: 107853 Status: Offline Thanks Meter: 1	Nokia 3120c-1c RM-364 8. Recover CERT ( go>imei and security tab> imei rebuild > recover cert) Begin Certificate Request ... [InternalErrorFault] CERT [0565888] data not found in database (case id=0xCE02) what now...? wait..?

07-03-2010, 13:08	#11 (permalink)
delwar_us Freak Poster Join Date: Dec 2007 Location: dhaka,bangladesh Posts: 340 Member: 649043 Status: Offline Thanks Meter: 18	thanks brother for good solution

07-08-2010, 08:17	#12 (permalink)
harisa Freak Poster Join Date: Sep 2004 Location: PAKISTAN Age: 52 Posts: 261 Member: 81821 Status: Offline Thanks Meter: 14	SERVER->Served by MXKEY - BLADE X at host1, agent version 1.1 revision 0.1 Using device: UFS_USB V2.8 (c) SarasSoft 2007. Library version: 1.0.0.8929(24-06-2010), 1.0.0.14574(24-06-2010) Product: V 07.20 05-10-09 RM-243 (c) Nokia ApeCoreSw: 07.20 Using cached productData[145000105B5E0058A5C0577980BD3FC057D0586E] ... Authenticating to SUPERDONGLE using security server ... SUPERDONGLE authorized ! Writing PM from Node ... Section: 1 - Key: 0, size 114 bytes written. - Key: 1, size 4 bytes written. - Key: 2, size 98 bytes written. - Key: 4, size 110 bytes written. - Key: 5, size 4 bytes written. - Key: 6, size 98 bytes written. - Key: 8, size 110 bytes written. - Key: 13, size 98 bytes written. - Key: 15, size 4 bytes written. - Key: 16, size 98 bytes written. - Key: 18, size 98 bytes written. - Key: 20, size 98 bytes written. - Key: 22, size 16 bytes written. - Key: 23, size 4 bytes written. - Key: 24, size 84 bytes written. - Key: 25, size 4 bytes written. - Key: 26, size 110 bytes written. - Key: 27, size 4 bytes written. - Key: 28, size 98 bytes written. - Key: 29, size 10 bytes written. - Key: 31, size 98 bytes written. - Key: 33, size 36 bytes written. - Key: 34, size 80 bytes written. - Key: 40, size 16 bytes written. - Key: 41, size 182 bytes written. - Key: 42, size 4 bytes written. - Key: 43, size 36 bytes written. Warning: failed to write 1 - 44 (182 bytes) - Key: 46, size 64 bytes written. Section: 309 - Key: 0, size 4 bytes written. - Key: 1, size 2 bytes written. - Key: 2, size 12 bytes written. - Key: 4, size 12 bytes written. - Key: 5, size 12 bytes written. - Key: 7, size 12 bytes written. - Key: 8, size 12 bytes written. - Key: 17, size 12 bytes written. Completed in 2.875 s Writing PM from Node ... Section: 1 - Key: 0, size 114 bytes written. - Key: 1, size 4 bytes written. - Key: 2, size 98 bytes written. - Key: 4, size 110 bytes written. - Key: 5, size 4 bytes written. - Key: 6, size 98 bytes written. - Key: 8, size 110 bytes written. - Key: 13, size 98 bytes written. - Key: 15, size 4 bytes written. - Key: 16, size 98 bytes written. - Key: 18, size 98 bytes written. - Key: 20, size 98 bytes written. - Key: 22, size 16 bytes written. - Key: 23, size 4 bytes written. - Key: 24, size 84 bytes written. - Key: 25, size 4 bytes written. - Key: 26, size 110 bytes written. - Key: 27, size 4 bytes written. - Key: 28, size 98 bytes written. - Key: 29, size 10 bytes written. - Key: 31, size 98 bytes written. - Key: 33, size 36 bytes written. - Key: 34, size 80 bytes written. - Key: 40, size 16 bytes written. - Key: 41, size 182 bytes written. - Key: 42, size 4 bytes written. - Key: 43, size 36 bytes written. Warning: failed to write 1 - 44 (182 bytes) - Key: 46, size 64 bytes written. Section: 309 - Key: 0, size 4 bytes written. - Key: 1, size 2 bytes written. - Key: 2, size 12 bytes written. - Key: 4, size 12 bytes written. - Key: 5, size 12 bytes written. - Key: 7, size 12 bytes written. - Key: 8, size 12 bytes written. - Key: 17, size 12 bytes written. Completed in 2.844 s Writing PM from Node ... Section: 1 - Key: 0, size 114 bytes written. - Key: 1, size 4 bytes written. - Key: 2, size 98 bytes written. - Key: 4, size 110 bytes written. - Key: 5, size 4 bytes written. - Key: 6, size 98 bytes written. - Key: 8, size 110 bytes written. - Key: 13, size 98 bytes written. - Key: 15, size 4 bytes written. - Key: 16, size 98 bytes written. - Key: 18, size 98 bytes written. - Key: 20, size 98 bytes written. - Key: 22, size 16 bytes written. - Key: 23, size 4 bytes written. - Key: 24, size 84 bytes written. - Key: 25, size 4 bytes written. - Key: 26, size 110 bytes written. - Key: 27, size 4 bytes written. - Key: 28, size 98 bytes written. - Key: 29, size 10 bytes written. - Key: 31, size 98 bytes written. - Key: 33, size 36 bytes written. - Key: 34, size 80 bytes written. - Key: 40, size 16 bytes written. - Key: 41, size 182 bytes written. - Key: 42, size 4 bytes written. - Key: 43, size 36 bytes written. Warning: failed to write 1 - 44 (182 bytes) - Key: 46, size 64 bytes written. Section: 309 - Key: 0, size 4 bytes written. - Key: 1, size 2 bytes written. - Key: 2, size 12 bytes written. - Key: 4, size 12 bytes written. - Key: 5, size 12 bytes written. - Key: 7, size 12 bytes written. - Key: 8, size 12 bytes written. - Key: 17, size 12 bytes written. Completed in 2.906 s how to repair warning failed to write 1-44[182 bytes]

07-08-2010, 10:54	#13 (permalink)
A-H-T No Life Poster Join Date: Aug 2003 Location: Palestine Posts: 1,130 Member: 36394 Status: Offline Thanks Meter: 250	will try soon and post feedback wbr.

07-15-2010, 08:32	#14 (permalink)
andre128 No Life Poster Join Date: Aug 2005 Location: MY Posts: 2,369 Member: 172261 Status: Offline Thanks Meter: 364	mine is superdongle invalid, after repair sd become security test failed. i follow method sucess fix security test failed but now back to superdongle invalid

07-15-2010, 08:50	#15 (permalink)
defrianto Freak Poster Join Date: Sep 2007 Posts: 218 Member: 588260 Status: Offline Thanks Meter: 34	thanks brother for good solution............