MXBOX / HTI (High Tech Interface) INFO - 101 : SAFE CROSS FLASHING on last post

[gbluez]

How to install mobileex


example on winxp
















BR

[gbluez]

How to configure mobileex directory

(Nokia Module)



















BR

[gbluez]

--- reserved page for newer tips ---

[gbluez]

Hi,
After you have done installed our new update: 3.5rev1.4, you will have 3 new shortcut icon on your desktop. They are:
- mobilEx 3.5
- SL3 Logger
- SL3 Bruteforce





This is new our program that is intended to handle SL3 unlock jobs. This program need to run alone. You will need to close mobileEx main program before executing this software.


Mark 'Nokia USB Connection' on this right corner. Make sure that phone is ALIVE and all needed drivers are intalled correctly.
- connect a turned on phone to USB, select PC Suite mode.



you can try to 'Read Phone Info' just to verify that attached phone is detected correctly.

- Press 'Read SL3 Hash' to start the unlock process.
Follow on screen messages that comes, CAREFULLY



Finally, read .sha is done. You can proceed to start the bruteforcer. make sure that brute force engine is configured properly.**



**
Configuring SL3 Bruteforce.

if you set bruteforce engine like on first image.

[gbluez]

How to use it?

- Read hash as usual, you can do it by USB or FBUS.



- choose drop down menu, press convert log.
you also can do what you want. convert from any log to any logs!

[gbluez]

how to use Fire.exe on the new mobileex 3.5rev1.4:

http://forum.gsmhosting.com/vbb/f550...2/#post7812280

thanks to harry0909

[gbluez]

To use this SL3 Unlock service, you will need your self registered on our server.

- Open SL3 Logger application


Go to 'Online Logger' tab

1. Register HTI to use this service
(choose your password here !)

- Press 'Register' button. Fill your detail CORRECTLY


fill your registration detail, a valid email and remember your password also

- Initial step for SL3 unlock service is done


OK, you are now registered.


Login .....



Logged in..

2. Top up HTI credit to be able to use this service

3. Login using password chosen when registration


after logged in, you can see your credits ammount, and current job in queue.
'average waiting time': ETA of your code after uploaded


NOTE for SL3 Unlock:
SL3 Unlock is in beta stage
Beta test resellers will be chosen.
This resellers can chose their beta test users.
To be a beta test user please contact your reseller.


- Let's start the unlocking; First Step




- Read SL3 HASH



4. Upload Hash, select sha or log files


5. Wait for few minutes (As displayed on waiting time)



6. Job Status are displayed once you Upload Hash and everytime you Login
use Login button, to check or request codes for uploaded hash(if any)

re-login to see your unlock job

Your code is ready ...



!! Pay attention on mouse right click menus !!
7. When status is "finished", right click on individual hash and select one of menus
> use mouse right click to directly send codes to phone




And that's it !!




BR
MX Team

[gbluez]

Here is some error that might be seen

CARD ERROR:


on this error: check card reader (bend, badly soldered) also possible your windows is bad, check also usb cable for box.


BOOT ERROR


CHECK YOUR PHONE SELECTION !


BAD POWER TRANSISTOR OR CABLE NOT CONNECTED AT ALL


caused by short circuited phone, wrong polarity when using JIG type cable, etc
measure vbatt on cable before decide to change the power transistor!!!


BAD POWER TRANSISTOR #2
- on normal phone, SCAN OK, BOOT ONLY OK on FIRST TIME, NO SCAN AFTER. - collector and emitor is shorted out.



how to change POWER TRANSISTOR ON YOUR OWN RISK. click here



################################################## ##
THESE ERRORS BELLOW, SHOULD BE SEND TO RESELLER
################################################## ##

http://forum.gsmhosting.com/vbb/f550/very-important-information-about-some-malfunctioned-hti-mxbox-1412835/

CMT Data :
SYSTEM ASIC ID: 000000010000022600010006030C192101033000 [RAP3G ver: PA 3.x]
EM0 ID: 00000296
EM1 ID: 00000B22
PUBLIC ID: 27200106017D4950DCA9E6FFB470256ECB89F4D0
ASIC MODE ID: 00
ROOT KEY HASH: 9DDBFCFE6E73CED7D8C6268C8EB85723
ROM ID: 273F6D55DFAAF68F
SecondaryBoot: RAP3Gv3_2nd.fg [BB5] version: 9.11.1 revision: 0.0 size: 0x3C00
Supported Ids: 0103192101003000, 010C192101003000, 0103192101013000, 010C192101013000, 0103192101003100, 010C192101003100, 0303192101023000, 030C192101023000, 0303192101033000, 030C192101033000, 0103192101001101, 010C192101001101, 0003192101001002, 000C192101001002, 0013192101001002, 001C192101001002
eBB5ProtocolType: OLD

>>> STOP HERE <<< 

MXKEY [MxKey Team HTI Flasher Interface (WinUSB) 0], SN: C0600EA9
Using device: HTI, FW ver: 00.50, SN: 000035EA
Connection status: NUSB3XHC:NUSB3HUB:USB 2.00 (Full-speed)
Driver: WinUSB, ver: 3.5.1.0 , NTMP ver: 6.1.7601.17514
Module ver: 1.0.0.19798(05-01-2012), Library ver: 1.0.0.13703(05-01-2012)
CMT Data :
SYSTEM ASIC ID: 000000010000022600010006400C192101051105 [RAPIDOYAWE ver: 1.1x]
EM0 ID: 00000296
EM1 ID: 00000B22
PUBLIC ID: 17F00106AA9F0052F52E5495C4991C7159D8EB8E
ASIC MODE ID: 00
ROOT KEY HASH: B8C3ADECFC997FCD8081D3DEAF870B8C
ROM ID: 4B9B75103E691FF8
 SecondaryBoot: RAPIDOv11_2nd.fg [BB5]  version: 11.34.0 revision: 2.0 size: 0x3B80
 Supported Ids: 0003192101001203, 000C192101001203, 4003192101001203, 400C192101001203, 0003192101002003, 000C192101002003, 4003192101002003, 400C192101002003, 4003192101011103, 400C192101011103, 4003192101021103, 400C192101021103, 4003192101031103, 400C192101031103, 4003192101011105, 400C192101011105, 400C192101021105, 400C192101031105, 4003192101051103, 400C192101051103, 400C192101051105, 4003192101051105
eBB5ProtocolType: NEW
ERROR: Packet Error(0xAA), code 0xC1000003
 
>>> STOP HERE <<< 

HTI both have SIX MONTHS warranty.

### use PC with P4 and above, system ram at least 1,5 GByte ###

[gbluez]

Lumia - WP Based

v3.5 revision 1.8, Public-Release

changes:

- Nokia Tool
added: support for Windows Phone 7 platform
       allow normal flashing (Refurbish) and dead mode flashing(Recovery)
       for recovery please select "Nokia DLOAD (Recovery) in connection list
       the drivers located to "data\drivers\nokia\wp"
added: esco file handling

How to install Drivers

No need to install zune. But it's OK if you did it.
There will be appear 2 Lumia on device manager.



- Choose only 1, leave the other. If first one is can't, chose the second one.
Use the driver given here C:\mobileEx\3.5\data\drivers\nokia\wp
- Now it's should be appeared on mobileex interface selection. Choose it. Launch Nokia Module.
- Press Scan, again you will now see another usb 'ding-dong' sound. Install the other Lumia device that appear on device manager. Same driver C:\mobileEx\3.5\data\drivers\nokia\wp.

1. Normal Flashing / Refurbish

• Connect a TURNED ON Phone to USB.
  Needed drivers are placed on C:\mobileEx\3.5\data\drivers\nokia\wp
• Choose attached WP device As interface, launch Nokia Module.
• Load Files ONLY by market drop down
  Flashes are available @ FiRe Agent

2. Recovery Mode / Dead Mode

• Connect Nokia DLOAD (Recovery) as Interface, launch Nokia Module
• Choose phone Model, Load files by market dropdown
• DO NOT CONNECT USB TO PHONE, USE FULLY CHARGED BATTERY.
• PRESS VOLUME UP, insert USB cable to phone.
  Needed drivers are placed on C:\mobileEx\3.5\data\drivers\nokia\wp
• PRESS FLASH

WP Device will not work on Nokia USB ROM. Double check your interface selection.

Known Limitation:
SIMLOCK info is not readed upon phone Scan, method not yet prepared.

[gbluez]

Other team do update .ini files manually, we do it better.
by this feature, you will never see : updated phone list <- from us.

1. Why i don't see RM-xxx ?
- change server host like this.




2. I want to have phone images and product description (not just RM/RH) on my mobileex

Just do this simple 1-2-3




- 1. Mark this option, 2. reload product



3. This process will take few minutes. Depend on your internet speed.

[gbluez]

MCU Verify

This information is to check that SELECTED MCU file is suitable with attached phone or not.
It's very useful to flash same phone type / different RM, check first without wasting time (try to flash) and end up with bad IMEI.



example is 3110 phone, check with 3500 MCU file. It is matched. So cross flashing will not damaged the IMEI.

Another screen shot from newer phone

e.g,
C6-01 RM-718 doesn't have SEAP languages. Load files C6-01 RM-601, press buscheck. If it is matched, means file OK for flashing.



Have a look and test by your self, i.e. C7 RM-675 / C7 RM-691, etc..etc..