Nokia Lumia 535 Dead Boot Repair

Lots of people having this problem by flashing wrong firmware on Nokia Lumia Rm-1090, So after that Lumia 535 is now totally dead. In this post i am going to share how i fixed dead lumia rm-1090 using atf box.

Some Qualcomm phones can be recovered via USB cable only. But in this case USB method was not working so i used eMMC method to recover Lumia RM-1090.

1. You must have ATF Box with JTAG Activation.
2. You must have good soldering skills.
3. Solder eMMC TP as shown in video or available at ATF support.
4. Download LUMIA_535_RM-1090_BIG_BOOT .mmc file below.
5. Follow the video below.

File Link: LUMIA_535_RM-1090_BIG_BOOT_02048.00000.14457.51004.mmc

 LUMIA RM-1090 DEAD BOOT REPAIR VIDEO:

Let me know via comments if have any problem? Follow this blog and YouTube Channel for more.

Nokia Lumia 535 soft bricked done.

Hi, Here i am posting Nokia Lumia 535 RM-1090 unbrick info how i have done this if you have any bricked phone in hands  you can contact me via Email pakfones@gmail.com or Whatsapp +923004537079 I will try to help you or come to my Service lab with phone.

Phone condition before.

 

 1= Download firmware with product code.

2= Select downloaded file see picture below.

3= Flash (if you have drivers already installed)

Press volum down key and connect usb cable if you have already installed drivers then flashing will start if you have not drivers installed already the install drivers. Nokia_Connectivity_Cable_Driver.msi

phone screen after start flashing

 

Phone screen after flashing done.

Here is complete log of flashing with infinity best.

Connect phone on selected interface...

Core : v2.09 , WP8x FlashEngine : v8.8

FFU : RM1090_02063.00000.15114.43005_RETAIL_prod_signed_1029_02089E_000-PK.ffu
Checking FFU file, wait...
FFU Revision ID   : 2.0
FFU Model ID      : Nokia.MSM8212.P6214
FFU RootKeyHash   : 990935FEFD1FF4177F728E3629EDA3798CFDEB75
FFU Languages     : Portuguese(Brazil) , Russian , Belorusian , fr-ca , Indonesian , Korean , Polish , Ukrainian , Uzbekistan(Latin) , Catalan , Swedish , Bulgarian , Japanese , Spanish , English (UK) , Czech , Latvian , Slovak , Chinese , sr-latn-rs , af-za , Hindi (India) , gl-es , Turkish , Thai , Italian , Danish (Denmark) , ha-latn-ng , Slovenian , Malay (Malaysia) , Lithuanian , Persian (Iran) , Kazakh , Romanian , English , eu-es , Estonian , Filipino (Philippines) , Greek , Norwegian (Bokmal , Norway) , Finnish , Vietnamese , Arabic , Croatian , Portuguese(Portugal) , Chinese(Taiwan) , Macedonian , Hungarian , Spanish(Mexico) , Azerbaijan(Latin) , German , Albanian , Dutch (Netherlands) , French , Hwbre (Israel) ,
FFU ChipSectors   : 15155200
FFU Header        : 0x000E0000
FFU Payload       : 0x696A0000
FFU FastVerify    : Ok

Waiting for phone...
Dead mode is selected , no phone in normal mode found
1. Press and hold "Volume Down"
2. Insert USB cable
3. Hold button until phone will be detected

Device catched in BOOT mode!
Boot Mode confirmed!
Setting Preloder
Collect Info...
Setting Application
Setting Secure
Collect Info...
=== Nokia Flash App info :
Protocol Version        : 2.34
Protocol Implementation : 2.59
=== Phone Initial info :
Phone RMxxx ID : RM-1090
Phone Model ID : Nokia.MSM8212.P6214.1.1
Phone Model PC : 059W7L1
Phone IMEI     : 357819062227766
=== eMMC info :
eMMC Vendor : Samsung
eMMC CID : 0015
eMMC Size : 7456 MiB
=== Security Initial info :
Security Status   : 010100000101
Secure Boot : Enabled
Secure eFUSE : Enabled
JTAG : Disabled
RDC Key : Not Present (Retail)
UEFI SBoot : Enabled
SecHW Key : Exists
Device RootKey    : BC2353ACA62C327ECCD582A281CA4A5672F35001
=== Other info :
SD present        : False

Full Check skipped , will be checked by ImageSignature


Battery Level : 41%
Battery Level enough to flash

FFU : RM1090_02063.00000.15114.43005_RETAIL_prod_signed_1029_02089E_000-PK.ffu
Flashing FFU
Sending FFU Header CertData
Header sent , accepted :)
Perform Data Partition Erase
Erase done
Sending FFU Payload Data...
Finishing flashing

Flashing done!
Green Light :)

Image Sent, processing PostFlash
Make Factory Set : Ok
Restore RAMBkp : Ok
PostFlash Finished

Total flash time : 00:07:57

Rebooting

Connect phone on selected interface...

Good Luck!

How to move Apps, Games from Internal storage to SD Card in Nokia X/X+/XL

How to move your Apps, Games from Internal storage to SD card in your Nokia X/X+/XL.

Things you gotta do before proceeding :
-= Root your Nokia X - Before Update v11.1.1 and After Update v11.1.1
-= Install FolderMount [ROOT] from Play Store.

-= Watch This Video : Click to watch on Youtube:

nokia x seriese flashing tool and how to

DESCRIPTION

The all members of xda-developers, and the author can not be held responsible for any damage to any of your devices after applying the following.

Technically, if you realize the flashing operation, you lose the warranty of your Android Nokia. However, I think that the "after sales services" do not watch it...

This tutorial, will deal that the method with Nokia Care Suite, because is the solution more complete than the other methods. This may serve to downgraded, flashed, *unbranded, unbricked, updated your Android Nokia. By cons, the flashing operation will not desimlock your Android Nokia!

Note that what are the latest versions in date of Nokia Care Suite and of Data Package Manager.

To illustrate my example (this is just example among many other), I take a Nokia X (aka Nokia A110/Nokia Normandy) with such as Product Code/Stock ROM 059V301 RM-980 GLOBAL SWAP (Firmware 10.0.3, Nokia X 1.0). I emphasize the fact that this is just an example, I could very well do the manipulations with Nokia XL for example, or any other Android Nokia.

If you have any problems with this tutorial, error flash, etc... please, post report on this thread with a screenshot and with your Hardware Product Type & Hardware Product Code, and not by Private Message!
Also note, that you can click on the images to enlarge.

For files that are downloaded via htcfanboys.com, please, do not reupload elsewhere.


*Unbranded allows removing operators settings by changing of ROM. This allow get the features/options not "flanged" and generally have updates more quickly than if you were branded.

PREREQUISITES

• Download and install if you don't have this software Nokia Care Suite 5.1.83.1414 (full install), or if you already have this software Nokia Care Suite 5.1.83.1414 (update only).
• Download and install Data Package Manager 4.2 (2013.7.5).
• Download and unzip to where you want UserGroupsConfiguration.
• Remove the SIM card during the all process!
• For those which have a WP8 Nokia Lumia with a μSD card, it is advisable to remove the µSD card during the all process!

AUTHENTICATION FILE FOR NOKIA CARE SUITE SERVER

• For Windows x86 (32 bits) PC
  
  
  

• For Windows x64 (64 bits) PC
  
  
  

DOWNLOAD STOCK ROM

• Run Nokia Care Suite software and double-click on the Data Package Manager category. Make sure that Nokia Care Suite Server is selected and click on Ok.
  

• If for one reason or another, the authentication with the Nokia Care Suite Server is not performed, so click on Work offline and on Ok. In the top left of the Data Package Manager window, click on File, on Work Online and on Ok.

• Fill in the two parameters Product Type and Product Code. Click on Search button. Right-click on the file found and click on Download Selected and wait the completed download to 100%.
  

• For only those, who have downloaded Stock ROM without using the Data Package Manager category (for example those who have gone through htcfanboys.com, mrcrab.net, NaviFirm+ (3.1), etc...) you must copy the downloaded files in the following directory: C:/ProgramData/Nokia/Packages/Products/RM-XXX (where XXX is your RM (RM-XXX = Product Type, and you can find your RM with the link Product Type & Product Code), for example for me with my Nokia X it is RM-980).

FLASH STOCK ROM

• Run Nokia Care Suite software and double-click on the Product Support Tool For Store 5.0 category. Click on Work offline. Stay in mode No connection.
  

• In top left of the Product Support Tool For Store 5.0 window, click on File and then on Open Product. Find your Android Nokia, or in the Filter box, tap on keyboard the Product Type of your Android Nokia (in my case, a (RM-980) Nokia X) and select your Android Nokia. Then click on Open.
  

• Bottom left, click on Programming, and then click on Recovery.
  

• Click on Update list. Select the Stock ROM downloaded. Click on Start. Wait a little that Product Support Tool For Store 5.0 verifies of data Packages integrity then it starts flashing operation, and it will show you an error (it indicates that the application has lost the connection, but this is normal because the phone is not connected).
  

• Connect the USB end into the USB port of your PC. Turn off your Android Nokia. Press and keep the Volume Down button and the Power button. Once a vibration felt, release the Power button. Release the Volume Down button after 15 seconds. Connect the other USB end to the USB port of your Android Nokia. Click on Retry in Recovery window.
  

• If a error message like this during flashing: "MSG_INVALID_SIZE_SECURE_FLASH_RESP: 0x00040006" If that happens, try changing the USB port where your Android Nokia is connected. For example, if it's a USB 3.0 port, try to connect it to a USB 2.0 port. Thanks to @whoadood for this observation

• If a message like this during flashing: "You have chosen not assigned product code for this device, do you wish to continue?" This is normal, it just means that the Product Code/Stock ROM chosen does not matches with that of the Android Nokia. But do not worry, this is quite normal. Click on OK.

• Wait the flashing process. Click on Close.

• Congratulation, the process of flash is end! You're with a new Stock ROM on your Android Nokia!

Nokia 101 not charging after few seconds (Done)

Friends today i got a nokia 101 with not charging after few seconds i see tis fault in nokia first time never seen before. and done by this method as shown in picture.

Thank you!

keep visiting for more unique solutions.

1616lcd and keypad light

Nokia 5130 MMC soltion

Nokia 5130 insert sim solution

Nokia Bicycle Charger

Charge your phone with free and eco-friendly energy when you on bicycle.

Use your own pedal power to charge your phone for free, efficiently and reliably, when you cycle. This durable charging kit is a convenient way to make sure you can stay in touch.

Dimensions:
Dynamo: 40.5 x 94.5 mm
Charger: 70 x 34 x 21 mm
Phone holder
Connecting cables: 500 mm + 375 mm (from charger to dynamo), 350 mm (from charger to phone)

Connectors:
2 mm charging interface

Power generation:
Compatible with bottle type bicycle dynamos with 6 V/3 W and 12 V/3 W output
5.0 V/450 mA/15 km/h.
Maximum current 70 mA
Charging starts at ~6 km/h and maximum output is achieved at 25 km/h.
Charging stops when the speed reaches 50 km/h.
Charging time depends on cycling speed, for example a Nokia 1202 with a 860 mAh battery can be charged with about 20 minutes of cycling at a speed of about 10 km/h (for the Nokia 1202 this would mean approximately 57 mins talk time or 74 h standby time)

Sales Package contents:
Bottle Dynamo for Bicycles
Nokia Bicycle Charger DC-14
Nokia Phone Holder for Bicycles CR-124
4 black re-usable cable ties
Plastic bag (to protect the phone against dust and humidity)

Repair any water damage LCD any phone

Some time we are receiving water damage phones with spots in lcd,s or some time getting dead phone and when we finish our job some lcd,s shocking us because of spots so if you have problem like this you can repair lcd spots without changing lcd,s just remove lcd from mobile. now remove its papers layers carefully. some time papers gone totally damage and not clean able then we need to change them from other damage lcd,s.

Enjoy

Understand the SIM Card working system on All Cell Phones.

Sample Nokia because its all systems on the basis of his work similar


At pin Simcard must consist of 6 Pin .. consisting of:

simclock
simdata
simreset
VSIM
Ground
Nc (Not Connetcetd)

all phones must be composed of six pins is just ....

Consider the following schematic:

If we look at it ... workflow from the sim card is ....
From the sim connector ===> ====> Simcard Emif Power Ic
This applies to all phones ....

In detail we take the example image below:

This point should we really understand .... because the work will be very decisive steps which we will do ....

PIN2 is important that we have noticed is all the PIN2 must be in a state connected to each other according to the path ... except for NC path alias not connected or not connect to mana2


STEP 2 simcard in determining damages is ....

1. Simcard replace first ... lest we not read sim card mobile phone sim card because it is damaged ... oon's really tuh hehehheheh
2. If the sim is ok ... measuring inhibition of 5 pins in it ... VSIM particular point, the data sim, sim sim clock and reset ....

PIN2 is to determine where on the connector ... the steps we need to do is to determine which point PIN2 Ground on the sim card connector ....

You have to understand ... that the ground would be in one corner of the sixth PIN2 .. as shown below:

If you notice ... then the ground of the sim card connectors are located on the bottom right corner ...

to determine the next titik2 ....

that is certain!!
ground position to deal with VSIM
On the ground must have NC
His next composition of the next sequence certainly like the picture above ....


Well,.,, After we know titik2 of PIN2 in accordance with its name ... then the next step is ... by measuring the resistance in the pin data, clock, reset and VSIM ....

if there are no obstacles in the climb, ... hence can be sure that your cell phone damage is a line break between emif simcard with connectors or damage to the emif simcard ....

steps you should do is ... by lifting emif sim card ... then measure the correlation between the broken lines in accordance track down emif sim ...

if the line is not severed was good aka .. hence can be sure that ... emif simcard must BROKEN! solution is to replace or men jumper emif emif simcard simcard in accordance with the track ... for example at the above phone .. jumper the trick is as follows:

The next ......
if it turns out after doing resistance measurements in the ... all the normal barriers .. (If necessary, compare with the value at normal cell phone)
then ... steps should be done is by measuring the voltage on the connector .... VSIM measuring at the measuring point in accordance with the determination of this VSIM pin ...

VSIM measurements should be made on the phone the first time in the light ... Why? because when the phone is the first time live ... then he will check the existence of sim and will appear voltage of 1.8 v. .. if the mobile phone sim card does not detect the presence of the tension that had been at 1.8v will fall directly on the point of ZERO ... but if the phone can detect the card then the voltage will be increased to 3 volts ...

so do not be surprised .. if the phone had been living so many seconds ... you will not be able to measure the presence of voltage at 1.8v the sim card ... this is what often happens and becomes kekeliaruan .. and always raises the question ... "Kok kok VSIM voltage measurement his breast I not ever stress ya ????"

hehhehehhhe

more ... if after doing measurements proved that the voltage stress is apparently no voltage NOL aka ... then it should do that best is to replace the Power Ic .. because the stress is coming from the UEM ... but .. replace the IC power because it has a big risk .... and also requires a high cost due to power ic pretty good price ... then ... the stress is enough to outsmart us by fetching from another voltage ...


Whether the voltage from which we'd better get me??

you do not take away from the stress of other 1.8v .. example taken from Fio ... because the possibility of success will be very small ....

Why?

because when simcar unreadable ... there must be a voltage of 3 volts instead 1.8v ....
8.1 The stress voltage is the basis for detecting the presence of sim ...

The most appropriate is ... by making jumpers from 3-volt voltage for others ....

nah on the phone because we very rarely voltage 3 volts .. then we usually menjumper of voltage at 2.8v .. example of the Vaux voltage of 2.8v .....
this forum actually do have a jumper from Vbat .... and successful ...
it is okay to do .. and will be successful .. but because there is excess voltage that should only 3 volts (VSIM) to Vbat (3.7V) .. hence the risk it faces is the possibility of rapid destruction of our CIP sim card ....


The next step ....

if we measure it on the path constraints VSIM not normal .. aka height .. then we have to do is to disconnect the capacitor on the path that led to ground .. because damage to the capacitor on the line can be caused sim unreadable ...

Here are disposed capasitor2:

Note the capacitor which given a yellow color ....

capasitor2 unplug serve targeted if the obstacle in the path simcard problem ....

Next ........

If we measure it all turned out normal barriers ... The next step is to lift emif sim ... then measure the resistance in between emif Power Ic simcard that led to the one in emif ... the goal is to find out .. whether between emif simcard and power ic .... there is a line break

if there is no increased resistance value .. hence can be sure that there is line break between emif and power ic .. then the solution is to jumper between emif simcard into power ic in accordance with the broken lines ...


If after performing the measurement .. apparently all the normal barriers .. then jumper simcard emif first ... if after to jumper emif simcar normal direct phone .. hence can be sure the damage to emif ....


but if it turns out after to jumper emif ... no sim card also read ... hence can be sure damage to the power ic ....

Nokia 6500S auto off at startup solution

Hi, friends here is the method of repairing nokia bb5 phones auto off atstartup.

Q = why this problem comes in bb5 phones mostly?

Ans = because in mostly cases we used or someone used lower version of firmware or cpu is faulty.

Solution = First full flash phone with latest firmware after full rpl and pm backup try to downgrade fix with mxkey  go to Nokia service tool > service tab > quick fix > tick bb5 sw downgrade fix > do selected job.

see log below.

Using device: UFS_USB V2.8 (c) SarasSoft 2007.

Library version: 1.0.0.9274(01-03-2011), 1.0.0.15761(01-03-2011)

CMT Data :

SYSTEM ASIC ID: 000000010000022600010006010C192101003000 [RAP3G ver: PA 3.0]

EM0 ID: 00000295

EM1 ID: 00000B22

PUBLIC ID: 06500117CC137D56556B24999D2261F4E01F38D6

ASIC MODE ID: 00

ROOT KEY HASH: BAF3A9C3DBFA8454937DB77F2B8852B1

ROM ID: 273F6D55DFAAF68F

 SecondaryBoot: rap3gv3_2nd.fg [BB5]  version: 1.30.0 revision: 0.0 size: 0x3C00

 Supported Ids: 0103192101003000, 010C192101003000, 0103192101013000, 010C192101013000, 0103192101003100, 010C192101003100, 0303192101023000, 030C192101023000, 0303192101033000, 030C192101033000, 0103192101001101, 010C192101001101, 0003192101001002, 000C192101001002, 0013192101001002, 001C192101001002

FlashID0: 0001 003F  - 0000 8A21 [AMD 72NS512PD,512 Mbits] type: NOR,CMT

ExtBUSC: 0000 0000 0000 0000 0000 0000 0000 0000

TransmissionMode: 16Bit

 Algorithm: RAP3Gv3_algo.fg [BB5 ALGORITHM]  version: 1.40.0 revision: 0.0 size: 0x22C10

 Supported Ids: 0103192101003000, 010C192101003000, 0103192101013000, 010C192101013000, 0103192101003100, 010C192101003100, 0303192101023000, 030C192101023000, 0303192101033000, 030C192101033000, 0003192101002000, 000C192101002000, 0003192101002100, 000C192101002100, 0003192101002200, 000C192101002200, 0003192101012200, 000C192101012200, 0103192101001101, 010C192101001101, 0003192101001002, 000C192101001002, 0013192101001002, 001C192101001002

CMT PAPUBKEYS HASH: A69838E8C5F20150E64E2E6E06DE6E50B26B593F

TransmissionMode: DDR&TX2

Processing MCU file: rm240__03.80.mcusw

 [BB5,BB5 ALGORITHM]  size: 19.84 MB

 Supported Ids: 0103192101003000, 010C192101003000

Erase size: 21.12 MB

CMT NOR area [00000000-0001FFFF]

CMT NOR area [00040000-000BFFFF]

CMT NOR area [000C0000-0013FFFF]

CMT NOR area [013C0000-0153FFFF]

CMT NOR area [00140000-013BFFFF]

erased in 1 min 17.188 sFlash programming ...

CMT PAPUBKEYS: A69838E8C5F20150E64E2E6E06DE6E50B26B593F (RAP Certificate 84 v1) written.

Programming completed in 2 min 4.266 s

Processing PPM file: rm240__03.80.ppm_m1

 [BB5,BB5 ALGORITHM]  size: 4.51 MB

 Supported Ids: 0103192101003000, 010C192101003000

Erase size: 6.50 MB

CMT NOR area [01540000-01BBFFFF]

erased in 24.703 sFlash programming ...

Programming completed in 28.266 s

Processing CNT file: rm240__03.80_ism_006.image_m1_SWAP

 [BB5,BB5 ALGORITHM] page size: 128 K size: 10.76 MB

 Supported Ids: 0103192101003000, 010C192101003000

Erase size: 35.87 MB

CMT NOR area [01EC0000-03F9FFFF]

CMT NOR area [01BC0000-01EBFFFF]

erased in 2 min 29.953 sFlash programming ...

Programming completed in 1 min 7.078 s

Total time for flashing process(boot+erase+write) was 7 min 59.000 s

Using device: UFS_USB V2.8 (c) SarasSoft 2007.

Library version: 1.0.0.9274(01-03-2011), 1.0.0.15761(01-03-2011)

CMT Data :

SYSTEM ASIC ID: 000000010000022600010006010C192101003000 [RAP3G ver: PA 3.0]

EM0 ID: 00000295

EM1 ID: 00000B22

PUBLIC ID: 06500117CC137D56556B24999D2261F4E01F38D6

ASIC MODE ID: 00

ROOT KEY HASH: BAF3A9C3DBFA8454937DB77F2B8852B1

ROM ID: 273F6D55DFAAF68F

 SecondaryBoot: rap3gv3_2nd.fg [BB5]  version: 1.30.0 revision: 0.0 size: 0x3C00

 Supported Ids: 0103192101003000, 010C192101003000, 0103192101013000, 010C192101013000, 0103192101003100, 010C192101003100, 0303192101023000, 030C192101023000, 0303192101033000, 030C192101033000, 0103192101001101, 010C192101001101, 0003192101001002, 000C192101001002, 0013192101001002, 001C192101001002

FlashID0: 0001 003F  - 0000 8A21 [AMD 72NS512PD,512 Mbits] type: NOR,CMT

ExtBUSC: 0000 0000 0000 0000 0000 0000 0000 0000

TransmissionMode: 16Bit

 Algorithm: RAP3Gv3_algo.fg [BB5 ALGORITHM]  version: 1.40.0 revision: 0.0 size: 0x22C10

 Supported Ids: 0103192101003000, 010C192101003000, 0103192101013000, 010C192101013000, 0103192101003100, 010C192101003100, 0303192101023000, 030C192101023000, 0303192101033000, 030C192101033000, 0003192101002000, 000C192101002000, 0003192101002100, 000C192101002100, 0003192101002200, 000C192101002200, 0003192101012200, 000C192101012200, 0103192101001101, 010C192101001101, 0003192101001002, 000C192101001002, 0013192101001002, 001C192101001002

CMT PAPUBKEYS HASH: A69838E8C5F20150E64E2E6E06DE6E50B26B593F

TransmissionMode: DDR&TX2

Reading CMT NPC  (0x168 bytes)

Imei: 3568540xxxxxxx

NPC_DATA saved OK

RPL saved to "C:\mobileEx\3.4\data\backup\RPL\3568540xxxxxx_NPC.rpl"

Erasing CMT  NPC ... OK

Applying BB5 SW Downgrade patch ...

Reading signatures ...OK.

PM backup saved to "C:\mobileEx\3.4\data\backup\3568540xxxxxxx_20110508100002_308.1.PM"

BB5 SW Downgrade patch OK.

CMT Data :

SYSTEM ASIC ID: 000000010000022600010006010C192101003000 [RAP3G ver: PA 3.0]

EM0 ID: 00000295

EM1 ID: 00000B22

PUBLIC ID: 06500117CC137D56556B24999D2261F4E01F38D6

ASIC MODE ID: 00

ROOT KEY HASH: BAF3A9C3DBFA8454937DB77F2B8852B1

ROM ID: 273F6D55DFAAF68F

 SecondaryBoot: rap3gv3_2nd.fg [BB5]  version: 1.30.0 revision: 0.0 size: 0x3C00

 Supported Ids: 0103192101003000, 010C192101003000, 0103192101013000, 010C192101013000, 0103192101003100, 010C192101003100, 0303192101023000, 030C192101023000, 0303192101033000, 030C192101033000, 0103192101001101, 010C192101001101, 0003192101001002, 000C192101001002, 0013192101001002, 001C192101001002

FlashID0: 0001 003F  - 0000 8A21 [AMD 72NS512PD,512 Mbits] type: NOR,CMT

ExtBUSC: 0000 0000 0000 0000 0000 0000 0000 0000

TransmissionMode: 16Bit

 Algorithm: RAP3Gv3_algo.fg [BB5 ALGORITHM]  version: 1.40.0 revision: 0.0 size: 0x22C10

 Supported Ids: 0103192101003000, 010C192101003000, 0103192101013000, 010C192101013000, 0103192101003100, 010C192101003100, 0303192101023000, 030C192101023000, 0303192101033000, 030C192101033000, 0003192101002000, 000C192101002000, 0003192101002100, 000C192101002100, 0003192101002200, 000C192101002200, 0003192101012200, 000C192101012200, 0103192101001101, 010C192101001101, 0003192101001002, 000C192101001002, 0013192101001002, 001C192101001002

CMT PAPUBKEYS HASH: A69838E8C5F20150E64E2E6E06DE6E50B26B593F

TransmissionMode: DDR&TX2

Updating CMT  NPC ...OK

Phone Type: RM-240 (Nokia 6500s-1)

SW Version: V 03.80 10-09-07 RM-240 (c) Nokia            

Imei plain: 3568540xxxxxxxx

Product Code: 0557556

Language Pack:

- not available.

SIMLOCK seems to be valid

SUPERDONGLE_KEY seems to be valid

CMLA_KEY seems to be valid

WMDRM_PD seems to be valid

SIMLOCK_TEST passed

SECURITY_TEST passed

Imei net: 3568540xxxxxxxx

Version: SIMLOCK SERVER

Counter: 0/3, 0/10

CONFIG_DATA: 2440700000000000

PROFILE_BITS: 8000000000000002

BLOCK 1:   1=OPEN 2=OPEN 3=OPEN 4=OPEN 5=OPEN, DATA=FFFFFF

BLOCK 2:   1=OPEN 2=OPEN 3=OPEN 4=OPEN 5=OPEN, DATA=FFFFFF

BLOCK 3:   1=OPEN 2=OPEN 3=OPEN 4=OPEN 5=OPEN, DATA=FFFFFF

BLOCK 4:   1=OPEN 2=OPEN 3=OPEN 4=OPEN 5=OPEN, DATA=FFFFFF

BLOCK 5:   1=OPEN 2=OPEN 3=OPEN 4=OPEN 5=OPEN, DATA=FFFFFF

BLOCK 6:   1=OPEN 2=OPEN 3=OPEN 4=OPEN 5=OPEN, DATA=FFFFFF

BLOCK 7:   1=OPEN 2=OPEN 3=OPEN 4=OPEN 5=OPEN, DATA=FFFFFF

FULL FACTORY... OK

USER DATA... OK

LEAVE FACTORY... OK

SERVICE CENTER... OK

SOFTWARE UPGRADE... OK

PRODUCTION TUNING... OK

Reset User Code (to default:12345) ... OK

Completed in 1.890 s

Enjoy!

7310 Ringer ways

7210 7310c ringer solution and tracks.

Please post comments to improove my work and also learn how to work.

Bookmark this page for more useful stuff. CTRL+D

always check Archives on the side bar for old posts.

NOKIA SIM IC REMOVING AND JUMPERING

Here is youtube video complete.

Be regular user to get more stuff.

E52 Shut off,contact retailer and memory full Solution tested

Hi,

I am sharing here success story with E52.which i got with  memory full, auto shut off after startup and contact retailer fault.

Solution!

Just flash with latest flash files with mx key also don't forget to FULL FACTORY, USER DATA and file system formatting 

 

Here is full log.

[BB5,XSR 1.6]  size: 38.65 MB
 Supported Ids: 4003192102001104, 400C192102001104, 6003192102001104, 600C192102001104, 6003192102011104, 600C192102011104, 6003192102021104, 600C192102021104, 600C192102031104, 6003192102031104
Erase size: 41.75 MB
CMT MuxOneNAND area [07340000-09CFFFFF]
Flash programming ...
Programming completed in 8.140 s
Processing PPM file: rm469_052.003_C00.01_DEFAULT_prd.rofs3.fpsx
 [BB5,XSR 1.6]  size: 7.55 MB
 Supported Ids: 4003192102001104, 400C192102001104, 6003192102001104, 600C192102001104, 6003192102011104, 600C192102011104, 6003192102021104, 600C192102021104, 600C192102031104, 6003192102031104
Erase size: 20.25 MB
CMT MuxOneNAND area [09D00000-0B13FFFF]
Flash programming ...
Programming completed in 1.687 s
Processing CNT file: rm469_052.003_U006.000_prd.uda.fpsx
 [BB5,XSR 1.6]  size: 4.65 MB
 Supported Ids: 4003192102001104, 400C192102001104, 6003192102001104, 600C192102001104, 6003192102011104, 600C192102011104, 6003192102021104, 600C192102021104, 600C192102031104, 6003192102031104
Erase size: 65.25 MB
CMT MuxOneNAND area [0B140000-0F27FFFF]
Flash programming ...
Programming completed in 1.312 s
Processing CNT file: RM469_ENO_09w23v0.a078.01.fpsx
 [BB5,XSR 1.6]  size: 2.54 MB
 Supported Ids: 4003192102001104, 400C192102001104, 6003192102001104, 600C192102001104, 6003192102011104, 600C192102011104, 6003192102021104, 600C192102021104, 600C192102031104, 6003192102031104
Erase size: 4.00 MB
CMT MuxOneNAND area [004E0000-008DFFFF]
Flash programming ...
Programming completed in 0.657 s
Total time for flashing process(boot+erase+write) was 1 min 12.235 s
Waiting for device boot up ...
Device found: nmwcdc\Nokia E52 USB Phonet, PORT_ID: 226500C9
Verifying communication to device OK.

Phone Type: RM-469 (Nokia E52-1)
SW Version: V ICPR82_10w22.3 12-10-10 RM-469 (c) Nokia
Imei plain: 355216*************
Product Code: 05******
Battery voltage: 3761 mV
ApeCoreSw: 052.003
Language Pack:
- not available.

This is SL3 phone(Simlock2 format).
- Avoid SW Downgrade & manual erase to this phone !

SIMLOCK seems to be valid
SUPERDONGLE_KEY seems to be valid
CMLA_KEY seems to be valid
WMDRM_PD seems to be valid
SIMLOCK_TEST passed
SECURITY_TEST passed


Imei net: 355216*******
Version: SIMLOCK SERVER
Counter: 0/3, 0/10

CONFIG_DATA: 2440700000000000
PROFILE_BITS: 0000000000000000

BLOCK 1:   1=OPEN 2=OPEN 3=OPEN 4=OPEN 5=OPEN, DATA=FFFFFF
BLOCK 2:   1=OPEN 2=OPEN 3=OPEN 4=OPEN 5=OPEN, DATA=FFFFFF
BLOCK 3:   1=OPEN 2=OPEN 3=OPEN 4=OPEN 5=OPEN, DATA=FFFFFF
BLOCK 4:   1=OPEN 2=OPEN 3=OPEN 4=OPEN 5=OPEN, DATA=FFFFFF
BLOCK 5:   1=OPEN 2=OPEN 3=OPEN 4=OPEN 5=OPEN, DATA=FFFFFF
BLOCK 6:   1=OPEN 2=OPEN 3=OPEN 4=OPEN 5=OPEN, DATA=FFFFFF
BLOCK 7:   1=OPEN 2=OPEN 3=OPEN 4=OPEN 5=OPEN, DATA=FFFFFF
FULL FACTORY... OK
USER DATA... OK
LEAVE FACTORY... OK
SERVICE CENTER... OK
SOFTWARE UPGRADE... OK
PRODUCTION TUNING... OK
Reset User Code (to default:12345) ... OK
Completed in 1.657 s
Formating FS: C ...
Completed in 0.250 s
Formating FS: D ...
Completed in 0.140 s
Formating FS: Z ...
Completed in 0.125 s

NOKIA bb5 betty & avilmas changing videos.

Hi dear,s i was faced a water damage phone witch is nokia 2700c i inspect it deeply and after checking i found the betty is heating when i tried to power on the phone so i decided to change it with new one but not available in market i asked many friends of mine but not success. so i got a piece of 7210c with contec service and i changed betty from 7210s to 2700c after change not power on i also changed avilmas from 7210 to 2700 nokia after few tries mobile power on successfully.


see videos below.
YouTube - 1st try 2700c betty & avimlma changing


YouTube - 2700c betty & avimlma changing



YouTube - after success re soldring iron cover 2700c betty & avimlma changing.


please don't hesitate to give comments. maybe your comment will improve my work and also someone get help from this thread.


Thanks to all for visiting here.

Nokia 1203 1203 1661 torch light solution

Nokia 1202 1203 1661 Torch light solution just check marked resistance if ok connect it to torch light led leg. and second point is going to  B+ so check it also.

Enjoy!

Nokia 6220C mic solution

Hi friend i am sharing Nokia digital mic solution hope you will enjoy from this a little guide to desoldering and soldering of nokia mic you should desolder it with care because you must care nearest parts of phone also.

and about soldering better way make jumpers and don't miss to connect mic body with ground some of solutions posted on gsm forums not care about this thing if you leave mic boddy and only solder 4 points of mic that will not work so take care of you and mic solution is below of my post comments.

Good Luck

Nokia 2700c power button not working solution

Here is 2700c power key ways just check j2108 if ok then change keypad ic 100% ok this solution also work with 5130

Don't forget to leave comments.

N73 hang on mmc solved

 

Hi i have solved N73 without mmc ok but hang on inserting mmc solved by this method. try this very useful jumper.