|
Welcome to the GSM-Forum forums. You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. Only registered members may post questions, contact other members or search our database of over 8 million posts. Registration is fast, simple and absolutely free so please - Click to REGISTER! If you have any problems with the registration process or your account login, please contact contact us . |
|
Register | FAQ | Donate | Forum Rules | Root any Device | ★iPhone Unlock★ | ★ Direct Codes ★ | Direct Unlock Source | Search | Today's Posts | Mark Forums Read |
| LinkBack | Thread Tools | Display Modes |
01-13-2007, 13:03 | #1 (permalink) |
Freak Poster Join Date: Nov 2005 Location: Ardahan Posof çilvana
Posts: 421
Member: 198839 Status: Offline Thanks Meter: 28 | @ Odia the Ultimate >> Can we have some NEWS about new hwk 3.04 ??? what will be added ? when ? will it be very easyly crackable like all versions ? |
01-13-2007, 17:51 | #3 (permalink) |
No Life Poster Join Date: Apr 2001 Location: Where dreams become reality. Age: 54
Posts: 5,752
Member: 4042 Status: Offline Thanks Meter: 24,046 | |
01-16-2007, 08:53 | #14 (permalink) |
No Life Poster Join Date: Aug 2005 Location: MY
Posts: 2,443
Member: 172261 Status: Offline Thanks Meter: 374 | Code: MTB NK 1.28 SX4 Server emulation Release notes: Bugfixes: BB5 RPL Write – added 20seconds delay between certificate write, and serial sending of simlock and SuperDongle data. NOTE – in order for simlock sending to succeed, phone should power on in LocalMode. If it doesn't correct your cable. In case that phone has some problem with powering on in LocalMode, connect phone, manually power it on in LocalMode, and then choose write RPL Again, MT will detect that Phone has valid Imei, and offer choice to skip certificate sending and do the serial sending only. New features: BB5 ASKs created with MTBox can be computed through GTServer. For more information see the release notes of GTSAccess 1.34 . Added SX4 Authorization for PMM write on BB5 phones. BB5 phones have protection for writing RF(1 ) and Energy(309, 0x135 in hex) settings in eeprom. NOT HAVING THOSE SETTINGS IN PHONE, IS KNOWN AS 'CONTACT RETAILER PROBLEM', OR 'SECURITY ERROR' IN SELF TEST. In order to write those settings phone requires an authorization that only SX4 smart card can perform. As those cards are hard to get, we've added server support for this authorization. To authorize, connect BB5 phone, and power it on. Press SX4 button ( located in Eeprom control page). If you have SX4 card connected to PC, MT will use it to compute the authorization password and send it to phone. If you don't have card, MT will connect to server to compute authorization password. In order to connect to server, you must have 'saved' valid account information for GT Server, and the account must have at least 1 credit left. The computation is FREE, your account will not be charged. Because the authorization procedure must complete in very short time, if you have bad internet connection, you may have to try a few times, before it is successful. Onece you've authorized phone, you may write PM settings to phone. If phone is restarted, you need to authorize again. To restore PM of phone, after eeprom is eerased: 1.Connect phone. 2.Make sure it has serial communication ( recommend to see it responds to phone info in local mode). 3.Load the PM file ( load file, in Eeprom controls page). 4.Mark Section( resource) 308 (0x134) and press Write Selected. 5.Restart phone. Either disconnect and reconnect phone to MT, or change mode to Test. 6.Press SX4 button, and wait for it to display that authorization was successful. 7.Press Write All button. If no error are report, then you've successful restored the PM of the phone. With the support for PM authorization we've ensured that our clients are able to actually service BB5 phones. Now you can make complete backup of IMEI and EEProm, change flash and restore IMEI and Eeprom with no additional charge for you. WARNING: many of you will try to downgrade phones, by erasing the Eeprom and then restoring after phone is flashed with lower version. There is significant risk, that phone will not accept simlock data ( 308, in hex 0x134) from higher version. So you still risk to end with damaged phone. That is why we recommend to avoid downgrading. If this happens you have two options: restore phone back to high version, and then write PM, or compute RPL and write RPL to phone. So if you really need to downgrade some BB5, you may have to compute RPL for it! For those who wish to make full erase of BB5 phones, we've created 4 files. BB5Erase_8MBrap.bin – fully erase first 8MB of RAP3 flash. BB5Erase_16MBrap.bin - fully erase first 16MB of RAP3 flash. BB5Erase_EE_8MBrap.bin – erase only eeprom located at the end of 8th MB BB5Erase_EE_16MBrap.bin – erase only eeprom located at the end of first 16th MB. !!!! VERY IMPORTANT !!!! ALL WE KNOW FOR PROBLEMS WHIT BAD QUALITY SERVICE CABLES. ON THIS CASE IS CRITICAL PHONE TO BE IN LOCAL OR TEST MODE after RESTART from certificate write. so please check this link: http://forum.gsmhosting.com/vbb/show...58&postcount=6 Problem is also 10 to 8 pin adapter cable connectors have very poor contact of GND and this come a big problem. (we already start producing new type adapter cable) Some times is need to push hard RG45 to adapter to be able to have any communication. So if you not see this: Simlock send - SUCCESSFULL!!! SuperDongle send - SUCCESSFULL!!! Simple check YOUR cable connection befor make any posting on forums. BR GT |
Bookmarks |
Thread Tools | |
Display Modes | |
| |
|