How to Imei Change MTK CPU? MTK imei change (Mode 1)

How to Imei Change MTK CPU?


MTK imei change (Mode 1)

Read More

Volcano Box User About Imei Change Check Out

---

[Volcano Box User ] About SPD Imei Change Check out !!!!

Read More

All success stories Volcano BOX with Huawei, ZTE , Vodafone ,and other

---

Phone Huawei G6005



100% Sucess VolcanoBox



Firmware G6005 Here

Read More

Blackberry Tool USB Flasher

 Blackberry Tool USB Flasher & Flashing Tutorial


Blackberry Tool USB Flasher


Siantar Blackberry Tool.rar



Flashing Tutorial



Films - Download - 4shared

Read More

cherry mobile f17 Earpiece Speaker problem easy solved

---

piranhabox - cherry mobile f17 Earpiece Speaker problem easy solved

bootkey

press *+power on fast detect

Read More

Free Samsung Editor v2.0 Released. Totaly remaked.

---

Samsung Editor V2 Released. Totaly remaked.

WHY you need this?

Becouse you can create custom firmwares!! with your own language for samsung phones.



THIS TOOL IS FREE FOR Z3X BOX Owners

We decide remake Editor from Zero.

Soon will be added many phones,

+ bonus android editor will be here also

If you have any suggestion - phone adding, etc.


Added:

- E1230

- E1220T

- E1200T

- E1200M

- E1195

- E1190

- E1180

- E1170i

- E1150

- E1130B

- E1130

- E1080W

- E1050

- E1150i

- z710*

- z650*

- z630*

- z620*

- z510*

- z320i*

- z370

- z810

- z310

- z107

- z105

- Saving/restoring settings in translate window

- Better quallcom model detection by firmware file

- EN-RU-UA dictionary based on original samsung translations

* – Except firmwares with Flash menu
New:

- Faster showing cells after loading firmware process

- Editor now remember latest used dictionary

- Editor now can translate multiple languages at one time
Fixed:

- Fixed bug when SamsEd can not open when dictionary file does not exists

- Fixed recent files list updating when selecting firmware from recent files list

Read More

Samsung Galaxy/Nexus eMMC - P1000, i9023, i9020T, M200S and variations

---

Hello dear RIFF Box users !


In order to diagnose possible problems with mass memory chips (internal
disk) in above listed models, we've added ROM2/3 chip detection to DCC
loaders.

This applies to following models:

• Samsung Galaxy (P1000/i9000/T959, m110s, m180s)


• Samsung Nexus (i9023, i92020, m200s, m200k)

Explanation:

Above listed models have two memory chips:

• NAND chip which holds bootloader and part of system software (ROM1),


• eMMC chip which holds user data and in Nexus phones complete OS (system software). (ROM2 and ROM3)

In case that eMMC is faulty, Galaxy models will hang on startup screen, or show message "Unable to mount x drive",
Nexus models will not start at all, or just will show black screen with low backlight.



To diagnose if eMMC is faulty or not, use the following method:

• Galaxy models:

Select P1000 DLL, and on DCC TAB select ROM2, set any data length size,

click "Read Memory".

If You get "error 0x28" on reading attempt, it means that eMMC is faulty and You have to replace it.

• Nexus models

Select i9020A DLL, and on DCC TAB select ROM2, set any data length size,

click "Read Memory".

If You get "error 0x28" on reading attempt, it means that eMMC is faulty and You have to replace it.







Examples:


Here is sample log from P1000 with working mass memory:

Quote:

Open serial port...OK Connecting to the RIFF Box...OK Firmware Version: 1.35, JTAG Manager Version: 1.48 Selected Resurrector: [Samsung P1000 V1.0.4786.9062] Connecting to the dead body...OK Detected dead body ID: 0x1BA00477 - CORRECT! Set I/O Voltage reads as 2.80V, TCK Frequency is 8 MHz Settings Code: 0x20010B00000000000000000000100000 Resurrection sequence started. Establish communication with the phone...OK Initializing internal hardware configuration...OK Uploading resurrector data into memory...OK Starting communication with resurrector...OK Detected an Initialized FLASH1 Chip, ID: 0x00EC/0x0050 (512MB) Detected an Initialized FLASH2 Chip, ID: 0x0002/0x0100 (SEM16G, 0x0003B5400000 Bytes = 14.83 GB) Detected an Initialized FLASH3 Chip, ID: 0x0002/0x0100 (SEM16G, 0x000000100000 Bytes = 1.00 MB) Reading FLASH1 address space from 0x000000000000 to 0x0000000FFFFF Completed in 00:00:01.280 (Average Transfer Rate: 825.00 kB/s)

Here is log from device which has faulty mass memory chip:

Quote:

[08-Jan-13 18:12:03] Open serial port...OK [08-Jan-13 18:12:03] Connecting to the RIFF Box...OK [08-Jan-13 18:12:03] Firmware Version: 1.35, JTAG Manager Version: 1.48 [08-Jan-13 18:12:03] Selected Resurrector: [Samsung I9020 eMMC V1.0.4756.65088] [08-Jan-13 18:12:03] [08-Jan-13 18:12:03] Connecting to the dead body...OK [08-Jan-13 18:12:03] Detected dead body ID: 0x1BA00477 - CORRECT! [08-Jan-13 18:12:03] Set I/O Voltage reads as 2.81V, TCK Frequency is 8 MHz [08-Jan-13 18:12:03] Settings Code: 0x20020B00000000000000000000000200 [08-Jan-13 18:12:03] [08-Jan-13 18:12:03] Resurrection sequence started. [08-Jan-13 18:12:03] Establish communication with the phone...OK [08-Jan-13 18:12:03] Initializing internal hardware configuration...OK [08-Jan-13 18:12:03] Uploading resurrector data into memory...OK [08-Jan-13 18:12:03] Starting communication with resurrector...OK [08-Jan-13 18:12:03] [08-Jan-13 18:12:03] Detected an Initialized FLASH1 Chip, ID: 0x00EC/0x0060 (1024MB) [08-Jan-13 18:12:03] WARNING: DCC Loader was unable to initialize FLASH2 chip. Error code: 0x00000036 [08-Jan-13 18:12:03] [08-Jan-13 18:12:03] ERROR: Selected FLASH2 Chip was not Recognized by the DCC Loader. Terminating.

In this case mass memory is either not present or it developed failure. Only NAND chip (ROM1) functions will remain accessible.

Quote:

Open serial port...OK Connecting to the RIFF Box...OK Firmware Version: 1.34, JTAG Manager Version: 1.48 Selected Resurrector: [Samsung M200S V1.0.4787.59328] Restarting target (nRST Low then High)...OK Connecting to the dead body...OK Detected dead body ID: 0x1BA00477 - CORRECT! Set I/O Voltage reads as 2.80V, TCK Frequency is 1 MHz Settings Code: 0x20030600000000000000000000100000 Resurrection sequence started. Establish communication with the phone...OK Initializing internal hardware configuration...OK Uploading resurrector data into memory...OK Starting communication with resurrector...OK Detected an Initialized FLASH1 Chip, ID: 0x00EC/0x0050 (512MB) Detected an Initialized FLASH2 Chip, ID: 0x0002/0x0100 (SEM16G, 0x0003B5400000 Bytes = 14.83 GB) Detected an Initialized FLASH3 Chip, ID: 0x0002/0x0100 (SEM16G, 0x000000100000 Bytes = 1.00 MB) Reading FLASH3 address space from 0x000000000000 to 0x0000000FFFFF ERROR: Read Failed with Error Code: 0x28. Terminating at 0x000000000000

In this case eMMC is also faulty, and need to be replaced.

Read More