ASMOBILEZ

1st Boot Err: Bad Resp UPP

Very simple if you know how the process works Flasher tool.

when we press the button "check" on the software sarasoft, what happened?!??
Flasher tool will recognize the processor of the mobile phone.
If everything is Okay then we will see
1st Boot OK, UPP WD2: xxxx => UPP type used by mobile phones
Mobile rebooting

You can see from here can know that the flashing process ALWAYS starts with the introduction of the CPU / UPP who used mobile phones by Flasher tool.
(Simply put, if we want "ngborol" minimal brain must connect dong first street, right?!?? Hehehe)

So if there => 1st Boot Err: Bad Resp UPP
means due to CPU / UPP CAN NOT WORK.

UPP Why can not work?!??
could be due to two main points are:
1. UPP was damaged.
2. UPP did not get the supply voltage and clock.
(A trivial like this. Why TV can not flame?!?? Cause there are two: the cord is not in the plug so there is no electricity or running his TV who was damaged. So do not jump in gebuk2 tv well if we do not want to turn on, check mas cord first. already in conspicuous or not )


UPP get the supply voltage is distributed by the UEM.
Each IC MUST get a new supply voltage ic it could work!
EVERY working voltage for IC called Fio.
Flash IC, RF Processor, RAM, and UPP also would get distributed to the Management FiO fine day by the UEM (Universal Energy very name Management)!
There was one more special working voltage supplied by the UEM UPP, was named vCore voltage.

So if the 1st boot err cases like the above who happened, what should we do?!??
Fio and vCore voltage checks issued by the UEM (Can be seen in the schematics). If it does not come out or not issued in accordance demi like there in the schematics (smaller or larger), mean UEM damaged.
If all the voltages required by the UPP to work is normal (FiO and vCore) means his UPP damaged.

If FiO, vCore and UPP was NORMAL => Secured 1st Boot Ok SURE!
if time will dilfash error, a different story !

BY HARDWARE
• open the lines of books, there would have vCore
example hp 7610 = vCore can be checked on the c372. and Fio v 1.8 in uem, in c1xx (sorry forgot) .. it is like there is absolutely ga voltage or the very small GA = 100% HP would be able to be detected by Flasher box = 1st boot err:, but not in the node's UPP damage 100%, try the check SMPS ic (logic defective SMPS )<--... = could in jumpers, but if 7610 had not already tried to jumpers = hp can live, but there ga vCore voltage to a suitable one, so na hot cpu , 3660 horror .. if dah often try it ... the conclusion = 1st boot err = check vCore & Fio, vbat, dkk.sperti antecedent post om morph, direct jngan host cpu, uem angakat, can be ancur tuh hp.
• Jgn dr forgot to measure the distribution of clock, either 26MHz or 13Mhz.
• if the conclusion 1st boot err = not necessarily uem, UPP .... with check = new procedure could in conclusion, Fio, vCore, clock, vbat, line.thx


1. Response 1st Boot Err: Bad
Resp UPP, 02 00 72/02 00 72 FFFF

Such responses are generated when the process who fail to boot up the phone EEPROM part due to insufficient voltage.
Failure EEPROM boot up process is generally caused by a voltage of no Ternado to the HP Power Supply IC (PD CCONT DCT3, UEM DCT4/WD2 PD). Therefore if we find a view like this make sure the cable is damaged flash off, so did the program interface and the battery connector on hp non-soiled or damaged.
On the condition of good conbat da flash cable, can be ascertained that the damage occurred at block power.Reball IC IC Power (CCONT / UEM), the first step to turn the HP who died because of wrong usage not because the procedure happens disconnected PD service.Umumnya BGA foot Ic or because the quality of tin-me-down IC legs. If after Rebaall Hp Ic power conditions remain dead ... check the RF IC (Hagar, Helga, helgo, Mjolner), after his re reball jg .. This section gives the same response occurs when a line break or damage the components.
Can be concluded that the response of 1st Boot Err: Bad Resp UPP, 02 FFFF 72 occurs when the sequence block components and RF Power Ic Ic occurs in the machine or line break at the foot of BGA Ic.Respons TSB inadvertent damage to the mob because without EEPROM EEPROM who respond produced this is boot OK.Respons LBH lots found not in the logic unit supporting section tetepi hp ..
If we cross-checked with the reading of the DC Power Supply usually undertow generated by the impedance of this HP rate between 0.00 s / d 0.2 ampere non-constant.
klo 0.02 ampere reading results ... most likely damaged in the Software or EEPROM

2. Response 1st Boot Err: Bad
Resp UPP, 03 00 72/03 00 72 FFFF

This response PD Tornado soft appearance is generally caused by damage to the logic unit such as CPU (MAD, UPP), and RAM hp.
If you find die total Hp condition with a response like this confirm for me Reball CPU, if unsuccessfully before his part in Reball RAM (re-solder) or a dressing.
Usually hp with this action could come back to life.
Jgn forget to confirm the condition of flash cable, conbat, non-damaged soft program, because these conditions also gave a response action Unresponsive who sama. this section will result in severe damage added Hp.
When compared with the reading of the DC Power Supply resultant very small currents of about 0.02 amperes is not constant.

• could have? because BAD RESPONSE UPP could be due to many things ....!!!!!!!!
voltage problems:
1: V BAT = 3.7 volts (the voltage distribution on UEM)
2: Fio = vCore = 1.8 volts (the distribution of the UPP)
vCore problem happened mostly lost because of the device
WD2 hp vCore in supply with separate components (emif vCore)
if this happens emif direct damage alone voltage jumper to FiO
VCore voltage TSB because it uses 1.8 volts


nb: the above voltage (V BAT, Fio, vCore) also are needed by other devices
such as: V BAT ----> PA IC, UEM, IC Light, DLLs
Fio-vCore ----> RF ICs, UPP, RAM, IC DLL RADIO
"BUT WE JUST ABOVE REVIEW BAD RESPONSE Discussing UPP"

problems, damage to components:
1: Cristal clock
2: RF IC
3: UEM
4: UPP
into four components could cause the UPP BAD RESPONSE
nb: only with the four components that alone without other components must be in pairs
and we make sure the good - stress distribution is also okay
we can try to check with the dongle and we will get the 1st boot

FLASH V, V REF, VR, V LED, the V SIM this DLL does not affect the occurrence of UPP BAD RESPONSE

Here is little discription about Nokia PM file..!

first, basics.

SEMC created few types of PDA:

db200x+nexperia
m600,w950,w960,p1,p990

such phones have two security type - NEW and OLD.
Identify button will show security type - it will write "NEW SECURITY detected" with NEW security phones.

if is better to install PDA phone drivers and PDA flash drivers before any operation.

phone drivers:

Small Info About Imei (?????????????) Damaged In Dct4 Wd2 Tiku..

There Is No Perfect Method To Know Uem Is Good Or Not.
There Is No Perfect Method To Know After Rpl Write Phone Watch Dog Timer Will Work More Then 32sec Or Not.

Here Is Litel Info About What I Know About Dct4 Wd2 Tiku Phone Imei (???????????????)
Damaged And This May Help Users To Find Fastest Way To Repair There Phone And Easily Also.........
1 = What Is Rezone Phone Show Imei (?????????????????)?
A. There Is Only 2 Rezone I Know [1] Phone Flash Ic Losted Imei Info In Pm (Eeprom) 208..[2] Phone Uem Damaged .

2 = What Is Rezone Phone Off In 32sec?
A. There Is Only 2 Rezone Uem Watch Dog Timer Start To Make Phone Off In 32 Sec.. [1] Uem Test Phone Flash Ic Imei Is Not Found Same Of Found Damaged Imei (???????????) [2] Phone Uem Is Damaged

3 = Is It Possible Imei In Phone And Phone Still Off In 32sec?
A. Yes If Flash Area Imei Not Same As Uem Imei.
If Rpl Calc With Different Imei Then Uem One.
If Phone Have Patched Imei.
Phone Uem Is Damaged

4 = Is It Possible Because Of Damaged Imei Area Phone Show Contact Service?
A. Yes It Is Possible. To Be Sure For It Check Uem Imei And Calculate Rpl For It And Write It To Phone And Check Phone.

5 = Is There Any Way To Backup Imei Area Before Flashing?
A. Yes All Tools F.E Jaf Box & Mt Box Have Option To Backup Flash Area Imei Pm(Eeprom) Field 208.
B. You Can Backup Pm(Eeprom) Field 208 And Save As Data1= ******xx Rpl .Replace Xx Place With 208 Field Data

6 = Is There Any Way To Repair Phone Without Backup?
A. There Is 2 Way If U Have Ask For Same Working Phone Then U Can Calc Rpl Free Link Is Here
Note Only Rpl Extract Possible For Working Phone Ask. For This Link Thanks Go To Mr.Al

7 = Is There Any Way To Make Rpl Without Paying?
A. Yes There Is But For Working Phones Only If U Have Damaged Already Then No Free Way Till Now. Link Is Here
Note Only Rpl Extract Possible For Working Phone Ask. For This Link Thanks Go To Mr.Al

8 = Is There Any Way To Find That Calculated Rpl Is For My Phone Imei?
A. Yes Link Is Here. You Can Check Rpl Also There
Note Only Rpl Extract Possible For Working Phone Ask. For This Link Thanks Go To Mr.Al

9 = What Is Rpl Have In It?
A. Its Have Imei Data And Password To Stop Uem Timer To Making Phone Off In 32sec.
B. Its Main Part Is Imei Restore Uem Compare Both Imei And Let Phone Work Perfectly.

10 = How To Know What Is Uem Imei ?
A.There Are Many Way & Box Do But You Can See 2 Way Here.
[1] Jaf Box + Pkey Go To Imei Tool. Read Uem Its Show U Valid Uem Imei.
[2] Mt Box Nokia Press Read Ask And Its Show Uem Imei .

11 = How To Know Uem Is Damaged Or Not?
A. When We Read Uem Imei Its Show Imei Like 31*********xx Or Abcdsx3245323 Or 000000000 Or Near About Same Number But Only 1 Or 2 Digit Different..
F.E 351102602736638 Valid Imei For 3650 Without Having Phone. How Do I Know? Link Is Here
But If U Have Imei 351102002036038 U Can Check This Imei At Already Given Link Its Show U Another Model Or Invalid Imei Means Uem Is Damaged.
At Site I Can See Imei Registered At 3650 So This Is Valid Imei For 3650 Phone If Ur Phone Is 3650 U Can Calc Rpl And Repair Phone.
12 = What Is Best Way To Repair Imei Damaged Phone & Which Tool?
A. All Tools Are Sames..Way To Repair Just Be Sure Which Rpl U Need Because Flash Area Can Be Rewrited Many Time We Want.Uem Area Write Only 1 Time. Calc Of Ask 2 Rpl Also Same By All U Can Use Any Service To Calc Ask 2 Rpl For Dct4 Wd2 Tiku Phones. Which U Likes ..

13 = If Uem Imei Is Valid Then We Don't Need To Change Uem?
A. Yes If Uem Have Valid Imei Then You Have Flash Area Imei Damaged Or You Have Changed Flash Ic...Just Calc Data1 = Flash Area Imei.And Repair Phone Without Changing Uem.

14 = I Repair Imei ??????????? With Patch Or Other Solution But Phone Is Still Off In 32sec What I Do??
A. Yes Because Patch And Non Repair Rpl Which We Get In Step 6 And 7 Link.Are NOT Able To Send Uem Reset Password To Off UEM Watch Dog Timer So Phone Will Be Off In 32sec All Time. BEST WAY TO REPAIR IT IS BUY ASK 2 RPL LOG AND WRITE REPAIR RPL TO FIX IT IF YOUR UEM IS OK YOU DO NOT NEED TO CHANGE UEM AND PHONE WILL BE REPAIRED FULLY.. BUT IF REPAIR RPL STILL MAKE PHONE OFF IN 32SEC MEANS YOUR UEM HAVE PROBLEM NEED TO REPLACE WITH NEW ONE AND WRITE RPL CALCULATED ONE OR ANY WHICH HAVE DATA1(FOR FLASH AREA) AND DATA2(FOR UEM AREA)


As I Say There Is No Perfect Solution For Uem Testing So This May Help Users To Find There Problem Much Faster ..

HOPE THIS HELP ALL

PLEASE download and READ the attached manual !!!
Here is a pre-view

click here for download

ATTENTION!!!

ASK/RPL calculation will NOT UNLOCK YOUR PHONE !!!
ASK/RPL calculation will NOT CHANGE IMEI, but it will repair it if is 123456****** as it was original before


AF Erase FIles for BB5 Here erase files for BB5.

If you don't know what flash size have you phone, just try all of them until you find one working with your fone.

ATTENTION:

If you are using erase file witout make CTR backup (certificate backup) you may kill your phone FOREVER !!!

ERASe Files
click here for download

JAF-RPL-manual_english.pdf
click here for download

Connect phone

Click
-----------
Log:

JAF version 1.98.9
FILES SET FOR FLASHING:
MCU Flash file: NONE
PPM Flash file: NONE
CNT Flash file: NONE
APE Variant file: NONE
Switching to serial...
Powering the phone...
Setting test mode...
Reading...
MCU SW version: V 04wk47_m_v14
09-02-06
RM-36
(c) Nokia.
HW version: 6001
PCI version:
RFIC version: 150a160f
DSP version: pb04w47v23
Retu version: 32
Tahvo version: 52
Production serial number: CQA650150
Product code: 0522047
Module code:
Basic production code: 0516030
Flash code:
Order number:
Product specific data:
Long production SN:
ATO:
Default SN type:
IMEI plain: 352278010710628
IMEI spare to net: 3A 25 72 08 01 17 60 02
IMEI SV to net: 33 25 72 08 01 17 60 22 F6

LOCK STATUS:

CONFIG KEY: 2440700000000000
Provider: AT&T;U.S.A. (3650)

Block 1:
Lock 1: OPEN Lock 2: OPEN Lock 3: OPEN Lock 4: OPEN Lock 5: OPEN
Block 2:
Lock 1: OPEN Lock 2: OPEN Lock 3: OPEN Lock 4: OPEN Lock 5: OPEN

Searching for saved ini...
Checking for file C:\Program Files\ODEON\JAF\JAF_RM-36.ini
Saved INI not found, loading INI list...
Done!

********How to backup bb5 NPC********

Way #1 (will display more info after)
-----------------------
Untick: use INI
tick: CRT 308
tick: CRT BKP
DO NOT SELECT ANY MCU / PPM
Now click FLASH

Log:

FILES SET FOR FLASHING:
MCU Flash file: NONE
PPM Flash file: NONE
CNT Flash file: NONE
APE Variant file: NONE
Backing up CRT data...
Setting FLASH MODE
Loader version: 01.10.02 -> Revision: 0000
Patching CMT boot step2...
CMT Boot Ready
Loader version: 01.10.01 -> Revision: 0000
CMT Loader Ready
Reading NPC certificate...
Reading VARIANT certificate...
VARIANT CRT empty, skip save...
Reading CCC certificate...
CCC not available...
Reading HWC certificate...
HWC not available...
Saved to C:\Program Files\ODEON\JAF\ProgData\3522781710628_CRT_backup_47173.rpl
Backup CRT OK!
Backing up SIMLOCK data...
Setting local mode...
Reading IMEI...
C:\Program Files\ODEON\JAF\ProgData\352278010710628_CRT_backup_47173.pm
Done!
Backup LCK OK!
Done!
Total time: 0 Minutes, 0 Seconds

DCT4/BB5 counter: 20
After flash processing...
Waiting for phone to boot...
Setting test mode...
Reading...
Phone type: RM-36, Software version: 04wk47_m_v14
IMEI: 352278010710628
APE Ver: V 5.04.07
15-02-06
RM-36
(c) NOKIA.
Variant Ver: V 5.04.07-APAC2
15-02-06
RM-36
(c)NOKIA
Product Code: 0522047
Done!

Way #2
-----------
Click CRT Tool > Backup CRT

Log:

Setting FLASH MODE
Loader version: 01.10.02 -> Revision: 0000
Patching CMT boot step2...
CMT Boot Ready
Loader version: 01.10.01 -> Revision: 0000
CMT Loader Ready
Reading NPC certificate...
Reading VARIANT certificate...
VARIANT CRT empty, skip save...
Reading CCC certificate...
CCC not available...
Reading HWC certificate...
HWC not available...
Saved to C:\Program Files\ODEON\JAF\ProgData\3522781710628_CRT_backup_410173.rpl
Done!

********* End of backup bb5 NPC********

So, in any case if you got things like this on the phones that you already backed up.......
This way how to restore it:

Click

Log:

FILES SET FOR FLASHING:
MCU Flash file: NONE
PPM Flash file: NONE
CNT Flash file: NONE
APE Variant file: NONE
Switching to serial...
Powering the phone...
Setting test mode...
Reading...
MCU SW version: V 04wk47_m_v14
09-02-06
RM-36
(c) Nokia.
PCI version:
RFIC version: 150a160f
DSP version: pb04w47v23
Retu version: 32
Tahvo version: 52
Production serial number:
Product code: 0522048
Module code:
Basic production code:
Flash code:
Order number:
Product specific data:
Long production SN:
ATO:
Default SN type:
IMEI plain: 12345610654321?
IMEI spare to net: 1A 32 54 16 60 45 23 01
IMEI SV to net: 13 32 54 16 60 45 23 21 F6

LOCK STATUS:

CONFIG KEY: 2BE6807C969DC958
Provider: Unknown provider
Searching for saved ini...
Checking for file C:\Program Files\ODEON\JAF\JAF_RM-36.ini
Saved INI not found, loading INI list...
Setting local mode...
Reading product code...
Product Code: 0522048
FILES SET FOR FLASHING:
MCU Flash file: C:\Program Files\Nokia\Phoenix\Products\RM-36\RM36_4.050407_B5.C0R
PPM Flash file: C:\Program Files\Nokia\Phoenix\Products\RM-36\RM36_4.050407_B5.v36
CNT Flash file: NONE
APE Variant file: NONE
Languages in ppm: Indian,Indonisia,Vietnamese
Done!

Now click CRT Tool
----------------------
1. Operation: Write RPL , Tick Plain RPL
2. Select RPL (you saved it in your folder, remember?)
** in this case, located on C:\Program Files\ODEON\JAF\ProgData\3522781710628_CRT_backup_410173.rpl
3. Write RPL
4. Close

Log:

Scanning RPL file....
NPC DATA OK...
VARIANT DATA NOT FOUND...
CCC DATA NOT FOUND...
HWC DATA NOT FOUND...
SIMLOCK DATA NOT FOUND...
SIMLOCK KEY DATA NOT FOUND...
SUPERDONGLE KEY DATA NOT FOUND...
CMLA KEY DATA NOT FOUND...
WMDRM PD DATA NOT FOUND...
Connecting to phone...
Setting LOCAL MODE...
CMT Boot File: C:\Program Files\ODEON\JAF\Flash\rap3gv2_2nd.fg
Loader version: 01.10.02 -> Revision: 0000
Patching CMT boot step2...
CMT Boot Ready
CMT Loader: C:\Program Files\ODEON\JAF\Flash\RAP3Gv3_algo.fg
Loader version: 01.10.01 -> Revision: 0000
CMT Loader Ready
Writing NPC DATA...
Restarting phone...
Done!

Now phone should be "Phone start up failed, Contact Retailer"
** You will need to restore your original CRT PM, in this case is located on
C:\Program Files\ODEON\JAF\ProgData\352278010710628_CRT_backup_47173.pm

Next operation : Click Write PM > Service

Log:

Powering the phone...
Writing PM...
Field: 308, Record: 1, Len: 4096 -> OK
Done!

Last Operation: write full pm.
-------------------------------
You will need SX4 server for this operation.
Tick SX4 AUTH > Service

Log:

Checking for local SX card...
Trying to use SX4 server...
Server say: Hello!
Login...
Detected P-KEY: 9000***x
Server say: Login OK, you are number 1 in the queue, you must wait aprox. 0 seconds...

And Then... > Tick Write PM > click Service
Now select your good PM

Log:

Powering the phone...
Writing PM...

Field: 309, Record: 17, Len: 12 -> OK
Done!

Ensure your self : Click INF

Log:

FILES SET FOR FLASHING:
MCU Flash file: NONE
PPM Flash file: NONE
CNT Flash file: NONE
APE Variant file: NONE
Switching to serial...
Powering the phone...
Setting test mode...
Reading...
MCU SW version: V 04wk47_m_v14
09-02-06
RM-36
(c) Nokia.
HW version: 6001
PCI version:
RFIC version: 150a160f
DSP version: pb04w47v23
Retu version: 32
Tahvo version: 52
Production serial number: CQA650150
Product code: 0522047
Module code:
Basic production code: 0516030
Flash code:
Order number:
Product specific data:
Long production SN:
ATO:
Default SN type:
IMEI plain: 352278010710628
IMEI spare to net: 3A 25 72 08 01 17 60 02
IMEI SV to net: 33 25 72 08 01 17 60 22 F6

LOCK STATUS:

CONFIG KEY: 2440700000000000
Provider: AT&T;U.S.A. (3650)

Block 1:
Lock 1: OPEN Lock 2: OPEN Lock 3: OPEN Lock 4: OPEN Lock 5: OPEN
Block 2:
Lock 1: OPEN Lock 2: OPEN Lock 3: OPEN Lock 4: OPEN Lock 5: OPEN

Searching for saved ini...
Checking for file C:\Program Files\ODEON\JAF\JAF_RM-36.ini
Saved INI not found, loading INI list...
Setting local mode...
Reading product code...
Product Code: 0522047
FILES SET FOR FLASHING:
MCU Flash file: C:\Program Files\Nokia\Phoenix\Products\RM-36\RM36_4.050407_B5.C0R
PPM Flash file: C:\Program Files\Nokia\Phoenix\Products\RM-36\RM36_4.050407_B5.v36
CNT Flash file: NONE
APE Variant file: NONE
Languages in ppm: Indian,Indonisia,Vietnamese
Done!

Best Regards
Thank you Odeon Team for Ultimate Solution

BB5_PM_RPL_Backup_and_RestoreVideo

click here for download

DCT4_PM_Backup_and_RestoreVideo

click here for download

How to Crt or Rpl Restore
How to Read PM area 308
How to unlock Asic 11
How to Erase DCT4
How to Read ASK DCT4
How to unlock BB5
How to Make Full factory
Erasing
How to write PM BB5
How to write DCT4 PM
How to Flash dead phones
How to restore PM 308
How to Sys formatting
How to Read Ask BB5
How to Read UEM DCT4
How to Flash DCT4

click here for download

Part 1

click here for download

Part 2

click here for download