free counters

Wednesday, September 29, 2010


Main component versions in the release:
• DK2 Driver Version

• Nokia Connectivity Cable USB Driver Version

• Flash Update Package

• FLS-x Drivers Version 2.09.28 1. Main changes & error corrections from previous version New Products added

• RM-640, RM-662, RX-90 New features:

• New version of Autotuning and RF Losses

• New version of Flash Update Package

• New versions of Product and Instrument API Error Corrections & changes

• RF Autotuning improvements for RM-497 and products using same engine enablingull repair service concept support for RM-497

• Improvements for ALS Calibration

• improvements to WLAN Size 4 TX tuning

• Improvements to CU-4 voltage settings

• Improvements to EM calibrations and CU-4 voltage handling

• Flashing improvements to dead phone flashing

• Improvements to label printing Corrections to Genius cases # 158703, #156736, #160883, #160361, #162759, #159362, #160796, #156018, #157265 2. Known errors & limitations

• Software downgrade with Tucson system is only possible for BB 5.0 products supporting the Data Package 2 concept.

• Flashing with setup FLS-5, SS-46 and product specific adapter is not supported anymore. FLS-5 is supported with phone specific cables only.

• If you install old DCT-4 data packages, Flash Update Package File installation path may be wrong. This is caused by very old DCT-4 data
packages which contain Flash Update Package and overwrite current information during installation. If you experience problems when updating FPS-x prommers, please check that Phoenix “Prommer maintenance” is looking for the files from the correct location which is “C:\Program Files\Common Files\Nokia\Tss\Flash”. If not, Phoenix will show error “Update via ini – file failed”. In this case, select “Update” from that Phoenix “Prommer maintenance” – UI, browse to correct directory and select “fpsxupd.ini” for all other prommers except the FPS-8.

• Refurbishment flashing and product code change for RX-51 product requires SX-4 card to be available

• FPS-21 flashing for RX-51 works only with TCPIP connection. FPS-21 prommer with new HW version is needed to correct this, and it is estimated to be available by the end of 2010.

• Please refer to product specific documents and instructions concerning the limitations of the RX-51 product

• RX-51 flashing does not work when CU-4 is used

• When version 2010_12_8_42304 or newer with FUSE connection manager is installed on top of older Phoenix versions, there may be an additional delay of several minutes when you start Phoenix for the first time. Please wait patiently; Phoenix will start after configuration is finished.

• When using Data Package download functions with online connection, download times may occasionally be long. This is not caused by Phoenix (or Care Suite). The download speed from online servers is occasionally is known to be slow, depending on how data is buffered on caching servers.

• Note concerning the installation and use with Administrator and User rights - If you install Phoenix, start Phoenix and configure connections from FUSE connection manager as Administrator, you may not be able to start Phoenix after you log off and try to use Phoenix with User Rights afterwards

• If you experience the above mentioned problem: - Log on as Administrator - Deleted Fuse folder and its contents from: C:\Documents and Settings\All Users\Application Data\Nokia\ - After this Fuse’s connection list will be empty and it can be used directly with guest/admin rights. - This has to be done only once.

• After you close Phoenix, it may not restart. To rectify this: - Use Windows Task Manager to manually shut down phoenix.exe and FuseService.exe processes, or optionally restart your PC

• Mass memory content file flashing does not work for all products over USB – FPS-10 or FPS-21 Flash Prommer must be used! Please use only one connection for one Flash Prommer ( USB or TCPIP ). If both USB and TCPIP connection are configured to same Flash prommer, FUSE will be unstable. Supported operating systems and user rights

• Windows XP Service Pack 1 or higher

• When installing Phoenix into Win XP you must have local admin rights.

• When using in Win XP, user must have power user rights.

Download Link:

4share link
Phoenix Service Software 2010.24.008.43820 EN.rar - 4shared.com - online file sharing and storage - download

Thursday, September 23, 2010

Nokia 5630 XM Firmware V13 Is Hacked By PNHT

[Thx Adonix, Steven25 & Szakalit ]

Do this hack at your own risk, you may damage your phone!

First I have to say that this was very hard work for all guys form PNHT
Adonix without You this hack will be never possible so BIG THX

This HACK is only for Nokia 5630 XM RM-431 v13 Only !!!!

Step 1:

First you have to download your firmware files using navifirm then copy all files to:
"C:\Program Files\Common Files\Nokia\DataPackage\Products\RM-431\"

Step 2:

Then you have to download rm431_013.009_236.01_UDA_DK_CV_prd.uda.fpsx and copy it to :
"C:\Program Files\Common Files\Nokia\DataPackage\Products\RM-431\"
and overwrite.

Step 3:

From Here Use Either Phoenix Or JAF... But Phoenix Is More Suggestive.

Using Phoenix

Click here to enlarge

Click here to enlarge

Click here to enlarge

Select Scan Products

Click here to enlarge

Program will found phone devices

Click here to enlarge

Select Firmware Update

Click here to enlarge

Select Refurbish

Click here to enlarge

Select OK

Click here to enlarge

Using JAF

Click here to enlarge

& launch JAF v1.98.62.exe

Set options like in picture below:

Click here to enlarge

And select your phone:

Select Nokia 5630 XM With RM-431

Click here to enlarge

JAF will load files copied to "C:\Program Files\Common Files\Nokia\DataPackage\Products\RM-431\"

(On picture is RM-504 but it have to be RM-431)

Click here to enlarge

If JAF doesn't detect your phone, download af_nok4models.ini file from the attachments to your JAF install location

(For Example--- C:\program files\odeon\JAF).

Now TURN OFF your phone !! and then click FLASH button after that press power button

(don't hold it) on your phone and JAF will start flashing.

When flash will finish restart your phone. Download Patches.zip and copy files from Patches.zip to "E:\Patches" and run RP+, select "Install Server RP+" and "Open4All RP+" add them to auto and your phone is HACKED !!!!!!!!

Click here to enlarge

Click here to enlarge

Click here to enlarge

New bb5 schematics in One exe

Click here to enlarge

included in pack:
5230 RM-272 RM-273
5610 RM-242
5610 RM-359
6300 RM-217 RM-222
6555 RM-271/276/289
7210s RM-346
C6-00 RM-612/624
N97 RM-505/507
N900 RX51
X6 RM-551/559


Wednesday, September 22, 2010

Nokia Editor Beta v0.4 [Cook your own Firmware] By PNHT

PNHT presents NokiaEditor Beta 0.4
With this tool you can extract, and repack ROFS2 and UDA files.

1. Download and extract tool.
2. Open tool.
3. Click "Open" button and select rofs2 or uda file
4. Click "Extract" button
5. Files will be extracted to:
a. for rofs2 file "rofs2" folder
b. for uda file "fat16" folder
6. Edit your files (don't close NokiaEditor):
a. for rofs2 open "rofs2" folder and edit files
b. for uda open "fat16.img" in "fat16" folder and edit it with magiciso or winimage
7. After you edited files click "Repack" button
8. Repacked files are in program folder:
a. REB-RM************.rofs2.*** for rofs2 file
b. REB-RM***********.uda.*** for uda file
9. Rename files (delete "REB-" at the beginning of file name) :
a. REB-RM************.rofs2.*** to RM************.rofs2.*** for rofs2 file
b. REB-RM***********.uda.*** to RM***********.uda.*** for uda file
10. Flash you phone with new files.
11. DONE.

Some Screenshots:...

Click here to enlarge

Click here to enlarge

Click here to enlarge

Tips for editing ROFS2 and UDA files:

If you want to add RP+ to your rofs2 file copy only "patcher.ldd" and "patcherShadow.ldd" to sys/bin folder. After flashing install RP+ LiteVersion.

If you want to edit files that are in rofs1 image - copy them to rofs2 folder and edit they will be overwriten after flashing.
Example: if you want to edit file swipolicy.ini (that file is in rofs1) copy swipolicy.ini to rofs2 folder (system/data) and edit - Repack and flash.

Remember that rofs2 file have maximum size (about 33mb) so if you don't have space for your files,mods just delete other language files from rofs2 folder.

Tool tested with 5530, 5800 files!!! I think it will also work with N97 files and others, it will not work with E51 files!!! Not working for your Phone ?? write to me and ill try to add support for your phone.



Click here to enlarge

Sunday, September 12, 2010

1st Boot Err: Bad Resp UPP

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 !

• 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

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

Furious Gold Crack (Old is Gold)


Thursday, September 2, 2010

Tutorial Xperia X10 Hard Reset Successfully DONE


Xperia X10 Hard reset Successfully DONE this will also remove any password you have on the phone.

Click Here To Download PC SUITE

  1. Install it ...THEN


Click here to enlarge

Click here to enlarge

Click here to enlarge

Click here to enlarge

All credits goes to GSM helper

Nokia C 5 Hardware Solutions AIO


Stay Connected