software support h17 sagem 9xx - GSM-Forum

raino · 10-06-2002, 09:05

hi,

a lot of soft can unlock or calculate sagem 9xx,302x , but they nearly all that don't support h17.

where have soft support h17 phone?

thanx

giorgi2002 · 10-06-2002, 14:36

hi
i have good software for hashtable 17 phones

Trier · 10-06-2002, 15:39

Everybody can have h17 calculator but minds are not so trained to see it.

**latigido** · 10-06-2002, 15:42

What is different in your sowtware comparing to free Sagem calculators???
I think your good soft can`t help raino.

chris922 · 10-06-2002, 17:57

Hi Raino...

Whats the Problem with your phone?
If it is "only" simlocked, all standard unlockers should work.
- If its something else, get your PhoneID with Sagem Loader Pro
- Calculate your new fields 251 252 253 with values 00, 0000000000000000000000 and 0000000000000000. How to do this, i explained here, several times (Search a little bit the forum).
If this does not help, correct the checksums with sagemdr.

giorgi2002 · 10-06-2002, 20:08

hi chris922
sagemdoctor not worck for hashtable 17 wrong chaksum repeared

chris922 · 10-06-2002, 20:31

hi giorgi..
I never had a Hash 17 phone in my hands,..
What is special with them?
If that are the checksums, that are not acessable with sagemdr (With known datacable commands) , its hard...
Have you software that can do this (without directly programming the eeprom)?

raino · 10-07-2002, 04:45

hi,

these phones are 'simlock' only.

sagemdr can't support h17 ,so can't do checksum.

chris922 · 10-07-2002, 11:05

I think, the data from fields 191/251 are incorrect with both phones...
Do you have normal simlock or simlock before entering the PIN / simlock without SIM?

To get the PhoneID id absolutly no problem from the second phone. It is included in the log...
[1:2600249508f7bec60834c87505aa9bda11a5da
11a5da1100000000000000000000000000000000]
-> Crypted ID = 9508F7BEC60834C87505AA9B -> ID= 033171006D08

For the first Phone, this should be no problem , too, because the
ID "crypted by logger" 959f067de1c0 is included.
For this, i suppose the MW Bootstraptool, to get the correct ID.

If you have the ID for both, you can repair your phone...
You are right... Sagemdr has not hash 17 (I never noticed that).
So, you have to repair it by hand...
Tell me fields 251 252 253 for both phones.
I hope you haven't tried to correct the checksums with sagemdr.. If you did, its some more work :-)

raino · 10-27-2002, 08:17

hi,

now I have some data about h17, I have tested , the code is right.

chris922 · 10-28-2002, 08:31

IN these log - files,the phoneID is crypted (a little bit), so you cannot use it directly to calculate the code with it.
Read the ID with MWbootstraptool-> ANd now you can calculate the code the well known way...

raino · 10-28-2002, 09:00

Hi,

what is the correct ID? the MWbootstraptool can't read ID.

why do you know the ID is wrong?

If use your sw clac3.4.3, what mode i must select?

if enter these ,is it right?

uncrypted field: 41
crypted field: 05e1bcf19f20
mode is 1

thanks

chris922 · 10-28-2002, 13:28

083A23421121463139 -> PhoneID = 101B0B61E440 (Lock level 13)

083A23321821603468 -> PhoneID = 16115329E340 (Lock level 13)

But you are right.. Theres no free soft, that can handle these LOG files, because that dammed logger did not give the plain phoneID.
every byte can be XORed by 0x80...
So you have to to brute force in 64 steps :-)

But i think, the bootstraptool should be able to handle these phones. The logger can do, too.
What kind of logger did you use?

raino · 10-29-2002, 03:29

thanks chris922.

I read with logger4.0.

chris922 · 10-29-2002, 08:03

As theres no soft available that can handle these hash17 logged IDs, i included an option for this in my calc.

Here's my calc 4.1
http://www.cbot-gsm.de/wbboard/misc2...tachmentid=430

33224111268304- 9 -> 90888be1e4c0

With XOR 80, i mean the phoneID...

In the log, the ID is 90888be1e4c0
now, the first byte can be 90 or 90 XOR 80 -> 90 or 10
second byte can be 88 or 08
third byte cn be 8B or 0B
fourth byte can be BE or 3E
fifth byte can be E4 or 64
sixth byte can be c0 or 40
Now you have to try it out... decrypt field 191. If the checksum is correct->you have chhsen the correct combination. If not, you have to choose another combination.

10-06-2002, 09:05	#1 (permalink)
raino No Life Poster Join Date: Feb 2002 Location: china Posts: 457 Member: 9315 Status: Offline Thanks: 0 Thanked 0 Times in 0 Posts	software support h17 sagem 9xx hi, a lot of soft can unlock or calculate sagem 9xx,302x , but they nearly all that don't support h17. where have soft support h17 phone? thanx Last edited by raino; 10-31-2002 at 02:49.

10-07-2002, 04:45	#8 (permalink)
raino No Life Poster Join Date: Feb 2002 Location: china Posts: 457 Member: 9315 Status: Offline Thanks: 0 Thanked 0 Times in 0 Posts	hi, these phones are 'simlock' only. sagemdr can't support h17 ,so can't do checksum. Last edited by raino; 10-31-2002 at 02:47.

10-27-2002, 08:17	#10 (permalink)
raino No Life Poster Join Date: Feb 2002 Location: china Posts: 457 Member: 9315 Status: Offline Thanks: 0 Thanked 0 Times in 0 Posts	hi, now I have some data about h17, I have tested , the code is right. Last edited by raino; 10-31-2002 at 02:47.

10-29-2002, 03:29	#14 (permalink)
raino No Life Poster Join Date: Feb 2002 Location: china Posts: 457 Member: 9315 Status: Offline Thanks: 0 Thanked 0 Times in 0 Posts	thanks chris922. I read with logger4.0. Last edited by raino; 10-31-2002 at 02:48.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

10-06-2002, 14:36	#2 (permalink)
giorgi2002 Freak Poster Join Date: Jun 2002 Location: Georgia Tbilisi Age: 33 Posts: 489 Member: 12524 Status: Offline Thanks: 2 Thanked 1 Time in 1 Post	hi i have good software for hashtable 17 phones

10-06-2002, 15:39	#3 (permalink)
Trier No Life Poster Join Date: Jan 2001 Location: Who Knows!! Posts: 1,123 Member: 3035 Status: Offline Thanks: 0 Thanked 0 Times in 0 Posts	Everybody can have h17 calculator but minds are not so trained to see it.

10-06-2002, 15:42	#4 (permalink)
latigido Product Manager Join Date: Feb 2002 Location: Europe Posts: 4,895 Member: 9544 Status: Offline Thanks: 128 Thanked 2,000 Times in 332 Posts	What is different in your sowtware comparing to free Sagem calculators??? I think your good soft can`t help raino.

10-06-2002, 17:57	#5 (permalink)
chris922 No Life Poster Join Date: Mar 2002 Posts: 774 Member: 10175 Status: Offline Thanks: 0 Thanked 0 Times in 0 Posts	Hi Raino... Whats the Problem with your phone? If it is "only" simlocked, all standard unlockers should work. - If its something else, get your PhoneID with Sagem Loader Pro - Calculate your new fields 251 252 253 with values 00, 0000000000000000000000 and 0000000000000000. How to do this, i explained here, several times (Search a little bit the forum). If this does not help, correct the checksums with sagemdr.

10-06-2002, 20:08	#6 (permalink)
giorgi2002 Freak Poster Join Date: Jun 2002 Location: Georgia Tbilisi Age: 33 Posts: 489 Member: 12524 Status: Offline Thanks: 2 Thanked 1 Time in 1 Post	hi chris922 sagemdoctor not worck for hashtable 17 wrong chaksum repeared

10-06-2002, 20:31	#7 (permalink)
chris922 No Life Poster Join Date: Mar 2002 Posts: 774 Member: 10175 Status: Offline Thanks: 0 Thanked 0 Times in 0 Posts	hi giorgi.. I never had a Hash 17 phone in my hands,.. What is special with them? If that are the checksums, that are not acessable with sagemdr (With known datacable commands) , its hard... Have you software that can do this (without directly programming the eeprom)?

10-07-2002, 11:05	#9 (permalink)
chris922 No Life Poster Join Date: Mar 2002 Posts: 774 Member: 10175 Status: Offline Thanks: 0 Thanked 0 Times in 0 Posts	I think, the data from fields 191/251 are incorrect with both phones... Do you have normal simlock or simlock before entering the PIN / simlock without SIM? To get the PhoneID id absolutly no problem from the second phone. It is included in the log... [1:2600249508f7bec60834c87505aa9bda11a5da 11a5da1100000000000000000000000000000000] -> Crypted ID = 9508F7BEC60834C87505AA9B -> ID= 033171006D08 For the first Phone, this should be no problem , too, because the ID "crypted by logger" 959f067de1c0 is included. For this, i suppose the MW Bootstraptool, to get the correct ID. If you have the ID for both, you can repair your phone... You are right... Sagemdr has not hash 17 (I never noticed that). So, you have to repair it by hand... Tell me fields 251 252 253 for both phones. I hope you haven't tried to correct the checksums with sagemdr.. If you did, its some more work :-)

10-28-2002, 08:31	#11 (permalink)
chris922 No Life Poster Join Date: Mar 2002 Posts: 774 Member: 10175 Status: Offline Thanks: 0 Thanked 0 Times in 0 Posts	IN these log - files,the phoneID is crypted (a little bit), so you cannot use it directly to calculate the code with it. Read the ID with MWbootstraptool-> ANd now you can calculate the code the well known way...

10-28-2002, 09:00	#12 (permalink)
raino No Life Poster Join Date: Feb 2002 Location: china Posts: 457 Member: 9315 Status: Offline Thanks: 0 Thanked 0 Times in 0 Posts	Hi, what is the correct ID? the MWbootstraptool can't read ID. why do you know the ID is wrong? If use your sw clac3.4.3, what mode i must select? if enter these ,is it right? uncrypted field: 41 crypted field: 05e1bcf19f20 mode is 1 thanks

10-28-2002, 13:28	#13 (permalink)
chris922 No Life Poster Join Date: Mar 2002 Posts: 774 Member: 10175 Status: Offline Thanks: 0 Thanked 0 Times in 0 Posts	083A23421121463139 -> PhoneID = 101B0B61E440 (Lock level 13) 083A23321821603468 -> PhoneID = 16115329E340 (Lock level 13) But you are right.. Theres no free soft, that can handle these LOG files, because that dammed logger did not give the plain phoneID. every byte can be XORed by 0x80... So you have to to brute force in 64 steps :-) But i think, the bootstraptool should be able to handle these phones. The logger can do, too. What kind of logger did you use?

10-29-2002, 08:03	#15 (permalink)
chris922 No Life Poster Join Date: Mar 2002 Posts: 774 Member: 10175 Status: Offline Thanks: 0 Thanked 0 Times in 0 Posts	As theres no soft available that can handle these hash17 logged IDs, i included an option for this in my calc. Here's my calc 4.1 http://www.cbot-gsm.de/wbboard/misc2...tachmentid=430 33224111268304- 9 -> 90888be1e4c0 With XOR 80, i mean the phoneID... In the log, the ID is 90888be1e4c0 now, the first byte can be 90 or 90 XOR 80 -> 90 or 10 second byte can be 88 or 08 third byte cn be 8B or 0B fourth byte can be BE or 3E fifth byte can be E4 or 64 sixth byte can be c0 or 40 Now you have to try it out... decrypt field 191. If the checksum is correct->you have chhsen the correct combination. If not, you have to choose another combination.