- Register
- Help
- Remember Me?

1. If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Page 1 of 4 1 2 3 ... Last

- Jump to page:

Results 1 to 10 of 40

# Thread: FAQ from MOBILE-FILES.COM

- ###### Thread Tools

  - Show Printable Version

- ###### Display

  - Linear Mode
  - Switch to Hybrid Mode
  - Switch to Threaded Mode

1. 02-05-2010, 01:06 PM #1
   GSMâ„¢
   - View Profile
   - View Forum Posts
   - Private Message
   Super Moderator

   Join Date
     Feb 2010
   Location
     MySQL
   Posts
     41

   ## FAQ from MOBILE-FILES.COM

   > Q: what is db2000,db2010,db2020,pnx5230,db3150,db3210 ?
   > A: that is chipsets of new SEMC phones.
   > db2000 (otherwise called marita "full") is inside next phones: z1010/v800/z800/w900/lg3g/sharp3g
   > db2010 (otherwise called "marita compact") is inside j300/k300/k500/k700/s700/k750 phones.
   > db2020 (otherwise called "marika") is inside k610/k550/k790/k800/w850/w880/z610/well, almost in all new phones.
   > pnx5230 is philips chipset and can be found inside z310,w350,w380,z555 phones.
   > db3150 is A2 generation, phones like k850,w910,w890,z750,etc have it
   > db3200,db3210,db3350 is further revisions of A2 platform.
   > Q: how to enable "search mode" and "GSM/3g networks" in "mobile networks" menu item of v800/k600/k608 ?
   > A: use following script (all in one string,without spaces !!!!)
   > Code:

   >     gdfswrite:00020CCD00000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000000000000000000000000

   > Q: i unlocked my z520 and my phone is dead !!! help ! help !
   > A:detach phone from cable, remove battery for 20 seconds ,then insert it back and try to turn phone on. must be ok.
   > still not work ? select in "main firmware file" edit file eroms\k750_w800_z520_new_erom.ssw and flash it.
   > detach cable, remove battery, wait for 20 seconds, insert it back.
   > must work.
   > if still not work - you made something besides simple pressing "unlock" button and phone must be repaired other way.
   > Q: i flashed my phone and it became dead !!! aaargh !!! help me , help !
   > A:relax. current semc phones can't be killed completely by software. well, some can, but setool2 will not allow it to do it.. simple
   > general way to do:
   > scenario:
   > a friend comes with phone. phone not powers on at all.
   > way:
   > 1. try to flash phone with corresponding flashfiles. if it flashes - good, flash it.
   > following step should not be applied to db2020/pnx5230/db2010 cid49/cid50/cid51/cid52 phones.
   > 2. if after complete phone reports "csloader startup error, fs startup error 1,2,23" then you need to restore erom.
   > all needed EROMs is inside "eroms" folder of setool2 distribution.
   > for db2000 phones erom is z800_v800_k600_old_erom.ssw
   > for db2010 phones erom is k750_w800_z520_old_erom.ssw
   > for w550/w600/s600 phone erom is w550_erom.ssw
   > when flashing EROM you MUST set cid to OTP cid !!!!!
   > 3. if after succefull flashing (complete ok) phone powers on with white screen/freezes on "please wait" step - you need to UNLOCK phone
   > 4. if it can't be unlocked - most probably gdfs is damaged and you must rewrite gdfs with re-formatting (go to settings tab, check "format gdfs").
   > all needed gdfs is inside "gdfs_in_bin_format,gdfs_in_ssw_format" folders of setool2 distr.
   > select corresponding gdfs in "misc files" edit and press "write gdfs"
   > always make "unlock" after write gdfs.
   > please note, that you SHOULD NOT mess with gdfs in db2020 phones, pnx5230 phones, cid50/51/52 db2010 phones.
   > actually, you only can safely rewrite gdfs on db2000/db2010 cid16/29/36/49 phones.
   > Q: how to remove "strange" "1e0w" or simular from service menu?
   > A:
   > for z1010 use script:
   > gdfswrite:00040CBF00
   > for all other db2000/db2010 phones use script:
   > gdfswrite:00020CB800
   > for db2020 use next script
   > gdfswrite:00020DE400000000000000000000
   > Q: i really like to make some pre-defined email/gprs account !
   > A:all pre-defined gprs and so on account stored in customize.xml file.
   > you can readout that file from phone with such accounts,using script command
   > readfile:/tpa/preset/custom/customize.xml
   > (file will be in PC directory ph_out\tpa\preset\custom\customize.xml)
   > then you can modify it as you need and write back into phone with script command
   > wrfile:test.xml,/tpa/preset/custom/customize.xml

   Reply With Quote

2. 02-05-2010, 01:12 PM #2
   GSMâ„¢
   - View Profile
   - View Forum Posts
   - Private Message
   Super Moderator

   Join Date
     Feb 2010
   Location
     MySQL
   Posts
     41

   ##

   > Some general information:
   > CID = Certificate ID. You can say that this "number" defines the version of SE's protection present in the phone. Each CID require their own loaders.
   > New CIDs are deployed from time to time, for the sole reason of preventing them from beeing unlocked/flashed/tampered with by non-SE service tools. Current CIDs in use by SE are 29/36/37/49/50/51/52. SE-based LG/Sharp phones use the same system (but different versions), hence they are supported by SETool. The OTP (One Time Programmable memory) and EROM of a phone might be protected by different CIDs, usually the case in newer K600s/K608s. If SETool reports OTP CID36 and Flash CID49, doing a "Recovery" in the software and replacing the EROM with a CID36 one will render the phone a normal and fully non-TP supported CID36 one.
   > CDA = This "number" defines which variant of a specific firmware a phone is supposed to have.
   > It lets among others SEUS (Sony Ericsson Update Service) know which language-pack/branding/bandlocks a phone is to be flashed with. A generic (unbranded) K750 for use in Scandinavia will be CDA102337/12, whilst a Telenor-branded K750 will be CDA102338/62. Both will be flashed with the same languages/dictionaries, but the latter will be flashed with Telenor-branded firmware (branded firmwares are considered by most as utter crap).
   > BLUE/BROWN/RED:
   > This "color" defines what kind of phone we are dealing with.
   > BLUE phones has been assembled at the factory, but never been programmed with software/GDFS/IMEI (remember kids: the IMEI is stored in the OTP (One Time Programmable memory))
   > BROWN phones are usually "developer phones", for testing. Less restrictions are present, as these are used for "debugging/beta" purposes. In the case of CID36, a phone has to be converted to BROWN for unlocking. If you ever encounter an OTP CID49 BROWN phone, it must be converted to RED for servicing. (Click here for a guide.)
   > RED phones are your typical retail ones.
   > GDFS:
   > This is the phones "stash", where all settings and calibration data is stored (this also goes for the firmwares IMEI-resource as well as the SIMlocks). Similar to other brands use of NVRAM (Non-Viotile Random Access Memory).
   > IMEI = International Mobile Equipment Identity.
   > A 15-digit number which includes information on the origin, model, and serial number of the device. The model and origin comprise the initial 8-digit portion of the IMEI, known as the "Type Allocation Code/TAC". The remainder of the IMEI is manufacturer-defined, with a "Luhn check digit" at the end (which is never transmitted). The "Luhn check digit" is calculated from the rest of the IMEI.
   > It should be noted that in SE-based phones, the IMEI is stored in two places, the OTP (One Time Programmable memory) and GDFS. The GDFS IMEI is normally read from the OTP, but this can be circumvented by SETool function to "change" the IMEI. This patches the firmware into allowing different OTP/GDFS IMEIs. It is the GDFS IMEI that is reported to the network, so changing this will "de-bar" blocked phones. SEUS is not fooled by this, on the other hand, and it should also be noted that doing this is illegal in most countries.
   > EMMA = Service software/solution by SE themselves. Protected by the EMMA smartcard to prevent non-licensed usage. Current version is EMMA3, though EMMA2 is still alive (but kinda useless on newer phones). The EMMA smartcard contains an algorithm that allows EMMA to communicate directly to/with the phones CID, so performing operations the way they were intended. The smartcard and its algorithm has not been cracked. Current EMMA access levels exists:
   > Service Update - Can't unlock phones.
   > Service Update Pro - Can't unlock phones.
   > Network Operator - Can't unlock phones (but sure as hell can lock them ).
   > Service Center Std - Can't unlock phones.
   > Service Center Rc - Can unlock phones, as they have a special version of the smartcard with a CSCA key.
   > Research & Development - Can unlock phones, as they have a special version of the smartcard with a CSCA key.

   Reply With Quote

3. 02-05-2010, 01:13 PM #3
   GSMâ„¢
   - View Profile
   - View Forum Posts
   - Private Message
   Super Moderator

   Join Date
     Feb 2010
   Location
     MySQL
   Posts
     41

   ##

   > q: How to use script to backup GPRS/MMS/Browser settings then write back??
   > a:
   > script
   > Code:

   >     readpkg:/system/wap/profile/

   > will create pkg_imei.pkg
   > then,to write it back use
   > Code:

   >     writepkg:/pkg_imei.pkg

   Reply With Quote

4. 02-05-2010, 01:15 PM #4
   GSMâ„¢
   - View Profile
   - View Forum Posts
   - Private Message
   Super Moderator

   Join Date
     Feb 2010
   Location
     MySQL
   Posts
     41

   ##

   > SEMC posted some documents about problems with Z520.
   > Introduction
   > There is a problem with some Z520 phones where the phone has no network. When you look at the PCB, you may see that R1242 or R1245 are missing, damaged, or askew. (See attached word doc with photos)
   > Comments
   > The problem area on the PCB may appear as mechanical damage. You may even see scrape marks. This is not customer abuse. This damage is being caused in the factory. These phones should be repaired under warranty. Both of the parts (R1242 & R1245) are in the parts list and are shown on the component placing drawing. If you find the part missing, and if the damage does not affect other parts, and if the pads are still intact, replace the missing parts. If the part is slightly askew, and there is not solder damage, then leave it. (The example in the photo is acceptable as is.) If it is severely askew, (less than 50% contact coverage) de-solder and re-solder it.

   Reply With Quote

5. 02-05-2010, 01:16 PM #5
   GSMâ„¢
   - View Profile
   - View Forum Posts
   - Private Message
   Super Moderator

   Join Date
     Feb 2010
   Location
     MySQL
   Posts
     41

   ##

   > q:
   > I have tried to flash Z1010 with unbranded file. This is the result.
   > Code:

   >     GUI v0.91380009/UNI
   >     Card serial:00000004
   >     Loaded 49 flash descriptors
   >     Open COM port OK
   >     ChipID:7100,EMP protocol:0301
   >     PHONE IS RED RETAIL PRODUCT
   >     FLASH CID detected:29
   >     Speed:921600
   >     DB2000 only supports 460800,fallback.
   >     OTP status:0 locked:1 CID:29 PAF:1 IMEI:35345600144480 CERT:RED
   >     Loader:041214 0759 MATCXC1325712_PRODUCTION R2Z
   >     Flash ID check:8964
   >     Flash props sent ok
   >     Switching to USB...
   >     Phone stays at current interface.
   >     writing C:\Documents and Settings\c1am1k\My Documents\UNLOCK\SONY ERICSON\z1010\z1010_r1h_fs.hk.cry
   >     CURRENT FLASH FILE CID:16
   >     ........
   >     SSW loading returns:0
   >     CSloader version:
   >     041109 1252 GOHCXC125904_SEMC_VIOLA_FILE_SYSTEM_LOADER_R1E
   >     loader startup: executed
   >     loader filesystem startup: executed
   >     csloader refused to start gdfs services,error is:29
   >     loader gdfs startup failed, that is fatal
   >     Elapsed:517 secs.
   >     RECOVERY MODE STARTED
   >     Open COM port OK
   >     DB2000 only supports 460800,fallback.
   >     Recovery:041213 1451 MATCXC1325413_CERTLOADER R3S
   >     Fetching phone data from OTP
   >     OTP status:0 locked:1 CID:29 PAF:1 IMEI:35345600144480 CERT:RED
   >     Recovery succefull. Reflash phone now
   >     Elapsed:17 secs.

   > a:
   > your phone OTP CID is 29, while flashfiles CID is 16. CIDs can be greater, but not lower.
   > you need to do now
   > 1. recovery (you done it)
   > 2. select cid change= redcid16
   > 3. flash main+fs+complete

   Reply With Quote

6. 02-05-2010, 01:17 PM #6
   GSMâ„¢
   - View Profile
   - View Forum Posts
   - Private Message
   Super Moderator

   Join Date
     Feb 2010
   Location
     MySQL
   Posts
     41

   ## .:IMEI CHANGE TUTORIAL FOR SONYERICSSON:.

   > 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!!!

   Reply With Quote

7. 02-05-2010, 01:18 PM #7
   GSMâ„¢
   - View Profile
   - View Forum Posts
   - Private Message
   Super Moderator

   Join Date
     Feb 2010
   Location
     MySQL
   Posts
     41

   ##

   > starting from w810 and z530, semc changed langpack names
   > i'll only write here changed names.
   > c_asia UK TR RU AR
   > cent_europe SK PL HU CS
   > m_east_africa FR FA AR
   > mediterr SQ RO EL BG
   > baltic RU LV LT ET
   > s_asia_levan RU HE FR FA AR

   Reply With Quote

8. 02-05-2010, 01:18 PM #8
   GSMâ„¢
   - View Profile
   - View Forum Posts
   - Private Message
   Super Moderator

   Join Date
     Feb 2010
   Location
     MySQL
   Posts
     41

   ##

   > 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 )

   Reply With Quote

9. 02-05-2010, 01:18 PM #9
   GSMâ„¢
   - View Profile
   - View Forum Posts
   - Private Message
   Super Moderator

   Join Date
     Feb 2010
   Location
     MySQL
   Posts
     41

   ##

   > q: how to enable amr on xxx ?
   > a:
   > for db2010 phones, execute following script
   > execute following script.
   > Code:

   >     gdfswrite:000000a60001020405

   Reply With Quote

10. 02-05-2010, 01:19 PM #10
    GSMâ„¢
    - View Profile
    - View Forum Posts
    - Private Message
    Super Moderator

    Join Date
      Feb 2010
    Location
      MySQL
    Posts
      41

    ##

    > 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

    Reply With Quote

Page 1 of 4 1 2 3 ... Last

- Jump to page:

Quick Navigation F.A.Q. Top

- Site Areas
- Settings
- Private Messages
- Subscriptions
- Who's Online
- Search Forums
- Forums Home
- Forums
- SETool2 Official support (English)
  1. News & Updates
  2. F.A.Q.
- HMD Tool Official support (English)
  1. News & Updates
- Other
  1. Offtopic & Trash

« Previous Thread | Next Thread »

#### Bookmarks

- Digg
- Google
- del.icio.us
- StumbleUpon

#### Posting Permissions

- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts

- BB code is On
- Smilies are On
- [IMG] code is On
- [VIDEO] code is On
- HTML code is Off

Forum Rules