Just in case if there is something "extraordinary", you should always backup Budayakan IMEI.
- Backup IMEI:
Here we discuss the general course, that generation which has the IMEI DCT4 pm Field in the area [208], for example; all DCT4-WD2: 7650, 36xx, 3230, 3100 / 3200 etc..
1100, 2300, 2600, etc.. not included in this category. We can recognize it easily about that category.
How:
Read PM with the address of the start / end in the content of 208.
When an empty area in the state, well, UFS can not do backups IMEI.
Now to do a backup, simply click: "Rd UEM", after the phone read, we just CANCEL.
(If you will create a file *. ask, could be in ok .. ok .. ok ...)
Example: 3100 - RH-19
So the information on the UFS will be like this
Code:
IMEI / ESN Backup data1 Saved as
\ Products \ Rh-19 \ Rh-19_352937001838975_Back.rpl
Backup Data Valid Only if AM [208.0] is Original
Bad IMEI Number: 352937001838975
Reading UEM Aborted "Bad IMEI Number" because we ask to cancel the process of making *.
As per the information above, the IMEI is stored in C: \ Program Files \ Nokia \ Phoenix \ Products \ RH-19 as the Rh-19_352937001838975_Back.rpl. If at a later time you find this phone
with IMEI ??????????? then re-enter the residence by way of "Write UEM".
example:
Code:
IMEI: ??????-??-??????-?
RPL File Info:
IMEI: 352937001838975
CHCK: -11,367
Warning: No Record Data2
IMEI:?
PROD:?
1st Boot Ok, DCT4, UPP: 1120
FlId Aliasing with: 00EC22F0
Fl0: 0x01000000-0x017FFFFF, 00EC22F2, Sam K5U64418TM
Algorithm: u_amd.fia, Ver: 4.52.0
UEM Writing Done, Time: 00:02
Warning: No File Imei SIM_PROG_DATA in good re-
Code:
MCU Sw: V 31.06 25-11-05 RH-19 (c) Nokia.
PPM Sw: V 31.06 25-11-05 RH-19 (c) Nok V
Prd.Cd: 0511598
Bpr.Cd: 0511478
Pro.Sn: 2FC223722
HW: 2702
PCI:
UEM: 8
UPP: 4384
RFIC: 0300
DSP: N5.20
LCD: SED15G10ITO
IMEI: 352937-00-183897-5
SLconf: 001-01-00000000000
SLprof: 000000000000000-2
SLvar: 00553529370018389700
SLaux: 00025555
Provider: Test Equipment
# Pw + 025 193 047 303 202 +1 #
# Pw + 293 515 711 147 122 +2 #
# Pw + 402 327 524 055 132 +3 #
# Pw + 248 835 463 670 341 +4 #
# Pw + 846 951 061 441 262 +5 #
# Pw + 737 150 157 513 464 +6 #
# Pw + 255 805 273 350 215 +7 # Imei good return
- Flash Addressing - Identifying
Yes, the determination of the flash according to the definition address is detected by the UFS. Still the same phone with the example above.
Code:
1st Boot Ok, DCT4, UPP: 1120
FlId Aliasing with: 00EC22F0
Fl0: 0x01000000-0x017FFFFF, 00EC22F2, Sam K5U64418TM
Algorithm: u_amd.fia, Ver: 4.52.0 @ Fl0: Since only one IC flash installed.
To 0x01000000-0x017FFFFF: Definition of the address area of the flash ic.
With the Start-end 0x01000000 and ends at 0x017FFFFF.
If you will do what is called FULL ERASE, addressed only as defined earlier.
Example: Sam K5U64418TM: ic brand of flash is detected.
The introduction of mobile phones with more than 1 flash ic.
Code:
1st Boot Ok, WD2, UPP: 1081
Fl0: 0x00000000-0x007FFFFF, 0001267E, Amd 29BDS643HT
Fl1: 0x02000000-0x027FFFFF, 0001267E, Amd 29BDS643HT
Fl2: 0x04000000-0x047FFFFF, 0001267E, Amd 29BDS643HT @ UPP: 1081> CPU is in use.
Tip: will be recognized as a 1081 when using v3.2 UPP / 3.2e
and will be recognized as the 0081 when taking UPP v2.x
Fl0: 0x00000000-0x007FFFFF, 0001267E, Amd 29BDS643HT
Fl0 = Flash ZERO .. not ef TEN
0x00000000-0x007FFFFF = Area that is in use.
29BDS643HT = Brand amd flash that is in use
The same definition for Fl1 and Fl2, the same information.
So if want a full erase, and do not have erase files, we have to do 3 times the erase process. Addresses in use by definition they will be.
Fl0: start: 0x00000000 end: 0x007FFFFF
Fl1: start: 0x02000000 end: 0x027FFFFF
Fl2: start: 0x04000000 end: 0x047FFFFF
Ex: 7650's kedetek 2 areas?
Code:
1st Boot Ok, WD2, UPP: 0081
Fl0: 0x00000000-0x00FFFFFF, 00EC22F8, Sams K8S2815ET
Fl1: 0x02000000-0x023FFFFF, 000122D1, Amd such 29BDS323DMaksudnya 3230 .. 7610 ... 6670 ... ic example is a flash 2in1
1 ic flash by 2 allocation. It's just that there are two flash ic detected three areas.
Code:
1st Boot Ok, WD2, UPP: 1081
Fl0: 0x00000000-0x00FFFFFF, 00EC22F8, Sams K8S2815ET ---> This area is in a flash the same IC
Fl1: 0x02000000-0x02FFFFFF, 00EC22F8, Sams K8S2815ET ---> This area is in a flash the same IC
Fl2: 0x04000000-0x047FFFFF, 00EC22FA, Sams K8S6415ET
About Out of Chip Bounds
Code:
1st Boot Ok, DCT4, UPP: 1120
FlId Aliasing with: 00EC22F0
Fl0: 0x01000000-0x017FFFFF, 00EC22F2, Sam K5U64418TM
Algorithm: u_amd.fia, Ver: 4.52.0
Area1: 0x01000000-0x01FFFFFF Out of Chip BoundsKenapa can this be? As per discussed in the previous page. This is the area defined in that purpose.
When we look at the Fl0: 0x01000000-0x017FFFFF,
while the erase command on the UFS is 0x01000000-0x01FFFFFF
then we will find Out of Chip Bounds
So that needs to look within erase-erase (full) This is the END address.
Caution:
IMEI is in the UEM and IC Fl0
