FAQ from MOBILE-FILES.COM

[GSM™]

1.
Choose correct model ( DB200x/DB201x/DB2020/PNX5230 CID49/CID50/CID51/CID52/CID53 supported )

2. Choose "SETTINGS" tab.
Check

"PATCH OTP<>GDFS CHECK IN FIRMWARE"
"ALLOW TO CHANGE IMEI WHEN UNLOCKING"
for DB2012/DB2020 only
"USE SERVER FOR UNLOCK/FLASH"
"USE ALTERNATIVE SECURITY BYPASS"


3. go back to SEMC tab, press UNLOCK

4. when prompted, enter required IMEI

NOTE:
REAL IMEI NOT changed, flashpatch "forges" IMEI via some trick.
no worry though, network (and customer) will see NEW IMEI.
but, once phone will be updated on SEUS it will return to original IMEI.
same applies to flashing main part of firmware.

BE AWARE THAT CHANGING IMEI IS ILLEGAL AND PROHIBITED BY LAW.
USE IT FOR EDUCATIONAL PURPOSE OR IF YOU HAD CHANGED FLASH CHIP WITH ALREADY FILLED OTP!!!

[GSM™]

about gdfs file formats.

there is 2 gdfs format,which setool2 can support.

first format is "common" format, "small" file , where only units and their values stored.
that file must be written using "misc. files" edit and "write gdfs" button.
such file can be produced with "read gdfs button"
if gdfs area is damaged, or loader can't find be written and thats why we came to ...
second format. it is pure flash image of gdfs area.
can be written only as "firmware files". can be written regardless of damaged or not gdfs area.

i suggesting to use "gdfs-in-ssw-format" in situations of "complete dead" phone (for example, after we tried to write s700 firmware into k300 )

[GSM™]

q: how to enable amr on xxx ?

a:
for db2010 phones, execute following script

execute following script.

gdfswrite:000000a60001020405

[GSM™]

If you are experiencing cable issues, it might help lowering the latency.

Standard symptom: "llbug: can't get all data, got:0 expected:***"

This is done through "Device Manager" (Right-click "My Computer"->"Properties"->"Ports(COM & LPT)". Check the attachments.

Set the latency to "1" and try servicing a phone. Increase the value (once per procedure) until errors start apperaring, then set the previous value.

Example:
Latency 1,2,3,4,5,6,7 goes OK, but then
8 - "llbug: can't get all data, got:0 expected:***"

Set the value to seven or six (to be sure).

if you experiencing same "llbug: can't get all data, got:0 expected:***" using UFS as interface
then you can do one of following (or all)

1. lower speed to 115200
2. use normal SHIELDED USB2.0 cable. it must be SHORT (no more than 30 cm)
3. try to connect UFS into different USB controller on motherboard
4. try to connect UFS into EXTERNAL POWERED USB HUB
Attached Thumbnails

[GSM™]

K790 Phone hang

Only Applicable for K790!

Background:
One of the main reasons for permanent phone hangs at start up or standby
can be resolved by replacing two resistors under the Bluetooth cavity.

Instruction:
ROA (PCB) with revision R3A and R3B have not been modified.
ROA (PCB) with revision R3C has the new resistor values already from
factory.
ROA (PCB) with revision R3D has a new version of Dolphin 2 which prevents
the problem and they SHOULD NOT have the resistors replaced.

For ROA revision R3A and R3B with permanent phone hang at start up or
standby:
Change:
R1404 to 470 ohms, REP 621 003/47.
R1405 to 4.7k ohms, REP 621 004/47
Both resistors are located under the Bluetooth cavity
Attached Thumbnails

[GSM™]

I've made this little guide so that more users will be able to use HyperTerminal in detecting phone HW problems. Too many users are blaiming SETool for their dead phones.

Case:
Let's say you're only getting a white screen when turning your phone on, or that you're getting the infamous "Can't get packet properties."-error.

Solution:
Either pick a random reason (and that won't do much good for your phone )or do the following to see if the phone itself can provide you with a hint:

1: Open HyperTerminal (Start->Programs->Accessories->Communications).
2: Configure a name for the connection. I've called mine "Debug".
3: Select the proper COM port.
4: Configure baudrate and press "OK".
5: In the "Transfer"-menu, click "Capture Text", then choose a path and name for the log. You will see that the "Capture" indicator has been activated.
6: Attach a powered-off phone (the phone might start charging, this is OK). Give it a minute or two to run selftests, then post the captured text as an attachment if you want an opinion from us.

FSFLASH: NAND Flash device @ [0x50000000-0x5FFFFFFF] 262144 Kb
FSFLASH:   Vendor (0x20): ST
FSFLASH:   Device: NAND02GR3B (0x00AA)
............
FSFLASH: Bad block found @ 0x50000000
FSFLASH: Bad block found @ 0x50020000
FSFLASH: Bad block found @ 0x50040000
.................
FSFLASH:   Bad block @ 0x500C0000 replaced by 0x501C0000
FSFLASH:   Bad block @ 0x500E0000 replaced by 0x501E0000
FSFLASH:   Too many bad blocks

If you see this during flashing, it's safe to assume that SETool is not to blaim. (The above error is not related to a case of WSOD, it's only for demonstrational purposes).
Attached Thumbnails

[GSM™]

Q: i flashed CHINESE flash into my P990/M600 phone, but after power on phone starts to reboot ;(

A: "reboot loop" can be fixed by writing
"3_P1A_Zebra_R8_CCPU_GDFS_QWERTY_keyboard_sett ings .gdfs" file in phone.

- go to PDA tab
- select file in misc edit
- press write script. note - if yours PDA is NEW revision, you will need 1 credit.

hint: you can add that file into firmware package with any zip-capable archiver, by doing that you can save one credit when you will flash P990/M600 with chinese flash.

thanks goes to imobile for careful research of that reboot bug.

Q: i want to change keyboard layout on my P990/M600.

A: write desired keyboard settings file, same way as in previous question.

[GSM™]

q: What languages are in PDA generic world1 and generic world2 ?

a: Languages included in World1 and 2 are;
American English (AE), Arabic (AR), Canadian French (CF), Czech (CS), Danish (DA), Dutch (NL), Finnish (FI), French (FR), German (DE), Greek (EL), Hebrew (IW), Hungarian (HU), Latin American Spanish (XL), Norwegian (NO), Polish (PL), Portuguese (PT), Russian (RU), Swedish (SV), Spanish (ES), Turkish (TR).

[GSM™]

Q: I'm unlocking many A1 phones using CSCA method,my comports number is about ~300 and that things really annoy me.
Are there any way to fix it ?

A:

save next strings in file "reset.reg" and execute in windows explorer.
that will reset first available comport to 5. (read: next time new comport will be installed it will be COM5)

important!
you need to UNINSTALL present phone drivers in order to reset comports,which are allocated for them.

REGEDIT4

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\COM Name Arbiter]
"ComDB"=hex:0f,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
  00,00,00,00,00,00,00,00,00,00

improtant update
if you will execute attached .reg file, then SAME MODELS of phones with DIFFERENT IMEI will not be discovered as NEW,
if attached to SAME USB PORT.

[GSM™]

Q: I want to reset lifetime counter,flip counter, etc on DB2020,PNX5230 phone.

A:

execute following script

gdfswrite:00000099000000
gdfswrite:0000009B00000000
gdfswrite:0000009D00000000
gdfswrite:00020E000000000000000000
gdfswrite:00020DC80000000000000000

Q: I want to flip counter on DB2010 phone.


A:

execute following script.

gdfswrite:000200С9С00000000

Q: I want to reset lifetime counter on A2 phone.

A:

execute following script (note, you SHOULD use setool2 >=v0.914012)

tawrite:0002188c00000000
gdfswrite:0000012d00000000
gdfswrite:0000012e00000000
gdfswrite:0000012f00000000
gdfswrite:0000013000000000
gdfswrite:0000013100000000
gdfswrite:0000013200000000
gdfswrite:0000188c00000000

important!
lifetimer will be reset on A2 phones only after firmware reflash. (maybe SEMC will change it in future)