UFSx Sarasoft Trick & Tips

Bookmark and Share
What will we discuss here is about erase - and BACKUP.
Just in case if there is something "incredible", you should always backup 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 them easily about the category.
How:
Read PM with the address of the start / end at the contents of only 208.
If the area is considered empty, well, UFS can not do backup IMEI.
Now to do a backup, simply click on: "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 like this
Code:
IMEI / ESN Backup data1 Saved as
\ Products \ Rh-19 \ Rh-19_352937001838975_Back.rpl
Backup Valid Only if PM data [208.0] is Original
Bad IMEI Number: 352937001838975
Reading UEM Aborted "Bad IMEI Number" because we cancel the creation process ask *.
Appropriate description 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 ??????????? re-enter the residence by way of "Write UEM".
For example:
Code:
IMEI: ??????-??-??????-?
RPL File Info:
IMEI: 352937001838975
CHCK: -11 367
Warning: No data2 Record
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 SIM_PROG_DATA in good re-Files Imei

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, determining the appropriate definition of flash address 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, address the course 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 usage.
Tip: will the 1081 recognize as when using v3.2 UPP / 3.2e
and will recognize as 0081 when using UPP v2.x

Fl0: 0x00000000-0x007FFFFF, 0001267E, Amd 29BDS643HT
Fl0 = Flash ZERO .. not ef TEN
0x00000000-0x007FFFFF = Area that is in use.
Amd 29BDS643HT = Brand flash that is in use
Same definition for Fl1 and Fl2, the same information.

So, if you want a full erase, and do not have erase files, we have to do 3 times the erase process. Address that they use the appropriate definition tsb.
Fl0: start: 0x00000000 end: 0x007FFFFF
Fl1: start: 0x02000000 end: 0x027FFFFF
Fl2: start: 0x04000000 end: 0x047FFFFF


Ex: my 7650 detected 2 areas?
Code:
1st Boot Ok, WD2, UPP: 0081
Fl0: 0x00000000-0x00FFFFFF, 00EC22F8, Sams K8S2815ET
Fl1: 0x02000000-0x023FFFFF, 000122D1, Amd 29BDS323D
Such 7610 ... 6670 ... 3230 .. for example, that have ic flash 2in1
1 ic flash with 2 allocation. It's just that there are two flash ic detected 3 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 Bounds why can this be? Fit discussed in the previous pages. This is the area defined in that purpose.
When we look at Fl0: 0x01000000-0x017FFFFF,
while the erase command on the UFS is 0x01000000-0x01FFFFFF
then we will find the Out of Chip Bounds
So who needs to look in the erase-erase her (full) This is the END address.
Attention:
IMEI is in UEM and IC Fl0

MCU Sw = (Master Control Unit) Includes Primary Data HP -> Version / Date / Type / Model of HP who was Connect.PPM Sw = (Post Programmable Memory) Includes HP Data Language Pack (must be the same version with MCU) DSP Sw = (Data Signal Processor) which contains the data stored in the CPU MADDSP isw = Contains ROM Type HP DCT3 in the event this ROM5 (MAD So who listed is v18) PPM Language Pack Lp = L = Bhs Indonesia (8210) ASIC = Application Specific Integrated Circuit = CPU is the CPU 8210/3310 MAD2WD1 DCT3COBBA = IC Audio Hardware Nokia DCT3 with ID 31 and Serial Number page. If the S / N = 00000000 then COBBA damaged / non-terdetectProd. Id = code ProduksiMsId = Mobile Serial Identity = Identity Code of ponselIMEI Net = Net IMEI can reply diganti2IMEI OSN = IMEI Original Serial Number (Imei who saved pd Flash IC) can be replaced pd Kedua2nya DCT3Security = security code / Security Code pd HP NokiaLocks = Network lock: MCC (Mobile Country Code) and MNC = Mobile Network Code) standard is the Network Code 000-00. In addition to HP's code was then locked juncture




MCU Sw = HP Key Data (If Corrupt HP Matot, etc.) PPM Sw = Data Language Pack HP (If Corrupt HP Blank) Prd.Cd = Product Code (Can be modified to fit the Back Casing with Prime Edit) RB Cd = Basic Product Code = equal Prd.CdPro. Sn = Product Serial NumberHW = Hardware ID phone tsbPCI = Peripheral Component Interconnect (Line between components) UEM = Universal Energy Management ID = IC Power Nokia DCT4/WD2UPP = Universal Phone Processor ID = CPU Nokia DCT4/WD2RFIC = Radio Frequency IC ID = Identity Signal Processor IC Data Signal Processor NokiaDSP = IDLCD = Type Liquid Crystal Display which terpasangIMEI = International Mobile Equipment Identity = No. IMEI SIM Lock ponsel.SLconf = Configuration = network code. Standard state is 001-01. In addition, the HP SIM juncture terkunciSLprof = SIM Lock Lock ProofSLvar = variableSLaux = SIM Lock auxiliaryProvider: Operators who lock the phone. Test Equipment is a normal condition (non-locked) Not found means the state is locked (4 locks) below is the code that needs pd cell phone pressed to unlock the network.



{ 0 komentar... Views All / Send Comment! }

Post a Comment