ATENTION BUG READING HASH FOR BF v3.4_rev2.1!!! - GSM-Forum

MOBICOM · 05-13-2011, 12:29

I run 3 phones brute force with unsuccessful end, and i discover that latest mobileEx_setup_v3.4_rev2.1_20110505_.exe have bug reading hash from phones or with simply words means that reading from phone totally wrong 40 numbers/letters of hash. I check this with Dejan's soft and online mx converter and also with mt-box. Reading hash with 3.4_rev1.9 is OK
for now I only test root hash 9DDBFCFE6E73CED7D8C6268C8EB85723 and hash is readed wrong in all readed phones

Br.

skkeptik2 · 05-13-2011, 15:40

total difrent hash from other tools, but i think is possible why i got always wrong codes........ on mx key

i think mx key encrypt hashes in some way , and on calculation is difrent from standard .....

br skkeptik !!!!

MOBICOM · 05-13-2011, 15:48

Maybe you are right, because I only read hashes with mx and bf them with ocl 0.5
We need to wait answer from Manole

POLARBOX_TEAM · 05-13-2011, 15:50

same here.maybe bug..not solve new hash read sha file from mx box...

MPhoneClinic · 05-16-2011, 02:34

Quote:

Originally Posted by MOBICOM

I run 3 phones brute force with unsuccessful end, and i discover that latest mobileEx_setup_v3.4_rev2.1_20110505_.exe have bug reading hash from phones or with simply words means that reading from phone totally wrong 40 numbers/letters of hash. I check this with Dejan's soft and online mx converter and also with mt-box. Reading hash with 3.4_rev1.9 is OK
for now I only test root hash 9DDBFCFE6E73CED7D8C6268C8EB85723 and hash is readed wrong in all readed phones

Br.

But my SHA1 (hash) file is read from ATF and still say "Cannot finid any compatible GPU"

WHY???????????????????????

dimityr.milev · 05-16-2011, 12:04

3.4 rev 2.1 have bug read hash
39CA1EEDD756D32784E86A6F2DEB5ABA4A0C8AAA-corect with 1.9 version
693B5FC1D4BF3BA9D191031080848F14693B5FC1-incorect with 2.1 version

mxkay please chek this: mad:

we are lost time

sekharsun28 · 05-16-2011, 12:07

waiting for manole sir answer

MobiLuy.co.yu · 05-17-2011, 15:36

v3.5 is ok, don't panic

dimityr.milev · 05-18-2011, 19:28

Quote:

Originally Posted by MPhoneClinic

But my SHA1 (hash) file is read from ATF and still say "Cannot finid any compatible GPU"

WHY???????????????????????

may by you stopet more times BF proces and start ageyn ,
and soft not ask for random file ,and clone some row
i test this more times
you must waiting all proces , or clouse sl3 task and start ageyn

dimityr.milev · 05-18-2011, 19:29

thanks ...............

dimityr.milev · 05-18-2011, 19:31

thanks .............

05-13-2011, 12:29	#1 (permalink)
MOBICOM No Life Poster Join Date: Jun 2004 Location: MACEDONIA Posts: 1,895 Member: 67805 Status: Offline Thanks Meter: 364	ATENTION BUG READING HASH FOR BF v3.4_rev2.1!!! I run 3 phones brute force with unsuccessful end, and i discover that latest mobileEx_setup_v3.4_rev2.1_20110505_.exe have bug reading hash from phones or with simply words means that reading from phone totally wrong 40 numbers/letters of hash. I check this with Dejan's soft and online mx converter and also with mt-box. Reading hash with 3.4_rev1.9 is OK for now I only test root hash 9DDBFCFE6E73CED7D8C6268C8EB85723 and hash is readed wrong in all readed phones Br.

05-13-2011, 15:40	#2 (permalink)
skkeptik2 Freak Poster Join Date: Apr 2004 Age: 49 Posts: 328 Member: 63120 Status: Offline Thanks Meter: 58	same problem total difrent hash from other tools, but i think is possible why i got always wrong codes........ on mx key i think mx key encrypt hashes in some way , and on calculation is difrent from standard ..... br skkeptik !!!!

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Need software upgrade for Nokia 5110	ptkrf	Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L )	30	02-24-2016 10:21
DES key Driver	black	Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L )	8	02-08-2014 04:50
8810 mbus-cable	zfrank	Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L )	2	05-19-1999 13:12

05-13-2011, 15:48	#3 (permalink)
MOBICOM No Life Poster Join Date: Jun 2004 Location: MACEDONIA Posts: 1,895 Member: 67805 Status: Offline Thanks Meter: 364	Maybe you are right, because I only read hashes with mx and bf them with ocl 0.5 We need to wait answer from Manole

05-13-2011, 15:50	#4 (permalink)
POLARBOX_TEAM No Life Poster Join Date: May 2009 Location: destination SL3 brute force Posts: 677 Member: 1021855 Status: Offline Sonork: BLACKBERRY INSIDE Thanks Meter: 600	same here.maybe bug..not solve new hash read sha file from mx box...

05-16-2011, 12:04	#6 (permalink)
dimityr.milev No Life Poster Join Date: Sep 2007 Location: Bulgaria,Assenovgrad Age: 46 Posts: 852 Member: 591325 Status: Offline Thanks Meter: 151	3.4 rev 2.1 have bug read hash 39CA1EEDD756D32784E86A6F2DEB5ABA4A0C8AAA-corect with 1.9 version 693B5FC1D4BF3BA9D191031080848F14693B5FC1-incorect with 2.1 version mxkay please chek this: mad: we are lost time

05-16-2011, 12:07	#7 (permalink)
sekharsun28 Banned Join Date: Mar 2007 Location: BALAJI TECHNOLOGIES Age: 38 Posts: 813 Member: 462076 Status: Offline Sonork: 100.1586314 Thanks Meter: 307	waiting for manole sir answer

05-17-2011, 15:36	#8 (permalink)
MobiLuy.co.yu No Life Poster Join Date: Jan 2006 Location: Serbia, Jagodina Age: 48 Posts: 557 Member: 221170 Status: Offline Thanks Meter: 110	v3.5 is ok, don't panic

05-18-2011, 19:29	#10 (permalink)
dimityr.milev No Life Poster Join Date: Sep 2007 Location: Bulgaria,Assenovgrad Age: 46 Posts: 852 Member: 591325 Status: Offline Thanks Meter: 151	thanks ...............

05-18-2011, 19:31	#11 (permalink)
dimityr.milev No Life Poster Join Date: Sep 2007 Location: Bulgaria,Assenovgrad Age: 46 Posts: 852 Member: 591325 Status: Offline Thanks Meter: 151	thanks .............