RIFF JTAG – eMMC Partition Table FullFlash Image Files Processing Plugin (eMMCDiskPartitions.dll) v2.00

23.11.2012   RIFF JTAG – eMMC Partition Table FullFlash Image Files Processing Plugin (eMMCDiskPartitions.dll) v2.00

This plugin is a powerfull tool which enormously simplifies resurrection process (providing you have the required boot files from an official firmware or you have a ‘donor’ device) for those devices which are not yet supported by a dedicated resurrector DLL.

This plugin works with eMMC image files and phones which have following formatting:

  •  Image Files or Phones with Standard Master Boot Record (MBR) and Extended Boot Record (EBR) formatting. Most of eMMC-bootable mobile phones have their eMMC memory formatted in such style. In this case partitions are accessed in standard way, by Partition ID: for example boot loader partitions or OS image partition (compare with qualcomm MIBIB partitioning: while ‘MIBIB’-type partitions have standalone partition descriptor block which contains info on all partitions and is posistioned in a definite NAND address, the eMMC partitioning is one MBR sector at fixed position + a chain of EBR sectors which are scattered throughout the eMMC address space in a literally random way);
  •  Image Files or Phones which do not have standard Master Boot Record (MBR) and Extended Boot Record (EBR) formatting, but instead, partition information for such phones is taken from the PIT Table (some Samsung phones);
  •  Image Files or Phones which do not have standard Master Boot Record (MBR) and Extended Boot Record (EBR) formatting, but instead, partition information for such phones is taken from the EFI Table (some Samsung, LG, Pantech and other phones).

Please note, in previous versions this plugin worked only with devices from topic #1, while #2 was supported by different plugin. Now everything is combined in this plugin (as well as EFI support added), and other eMMC plugin (PIT-Based) become obsolete, and no longer will be supported.

With the help of this plugin you can do:

  •  Disassemble a full (or, since eMMC full image files are too large, a partial) eMMC Image File previously obtained with JTAG Manager (DCC Read/Write Page);
  •  Inspect each partition contents;
  •  Save separate partitions to HDD;
  •  Save all partitions as standalone files to HDD;
  •  Build-up your own full image file: for this you need to read from device (by clicking “Load Image from Device” button) or open from file (by clicking “Load Image from File” button) the eMMC partitioning data and then by selecting desired partitions click “Inject Into Partition” button to upload data from file into selected partition. Then you can save all full image file to HDD or flash injected partitions directly into device;
  •  Write a chosen partition directly into device;
  •  Read a chosen partition directly from device and substitute old partition contents to new ones;
  •  Create eMMC partitioning snapshot (that is storing info on full EBR chain: each EBR sector position).
  •  Restore eMMC partitioning from previously taken file: it is convenient if eMMC memory is erased and all formatting data is lost.
  •  Plugin supports new RIFF™ shrinked binary files format (*.riffpbin): which allows to shrink huge eMMC Image files into small sized-files (for example, Image File for 14GB empty eMMC chip is shrinked into ~10 KByte(!) size), thus HDD space is preserved, while performance is not visibly effected.

Please note, direct read/write operations from/to the device will require proper resurrector to be set (Resurrector Settings: thus before clicking the Activate Plugin button make sure proper model is selected as well as other settings like TCK/RTCK frequencies).

This plugin will support all possible devices, based either on Samsung Exynos or Qualcomm cores with eMMC memory as boot device.

Please visit RIFF Box FAQ page for detailed instructions !

Sample partition layout from Pantech Sky IM A850L boot repair pack, based on QUALCOMM APQ8064:
.

RIFF JTAG – eMMC Partition Plugin v1.0 (Qualcomm EBR-MBR based eMMC flash images processing)

RIFF JTAG – eMMC Partition Plugin v1.0 (Qualcomm EBR-MBR based eMMC flash images processing)

This plugin works with eMMC image files which have standard Master Boot Record (MBR) and Extended Boot Record (EBR) formatting. Most of eMMC-bootable mobile phones have their eMMC memory formatted in such style. In this case partitions are accessed in standard way, by Partition ID: for example boot loader partitions or OS image partition (compare with qualcomm MIBIB partitioning: while ‘MIBIB’-type partitions have standalone partition descriptor block which contains info on all partitions and is posistioned in a definite NAND address, the eMMC partitioning is one MBR sector at fixed position + a chain of EBR sectors which are scattered throughout the eMMC address space in a literally random way).
This plugin is a powerfull tool which enormously simplifies resurrection process (providing you have the required boot files from an official firmware or you have a ‘donor’ device) for those devices which are not yet supported by a dedicated resurrector DLL.
Please note, such phones as Samsung Exynos MCU based pohones (for example I9100, P6200, P6800, N7000, I9220 and etc), though have eMMC chip, are not partitioned in MBR way and thus are not the subject for the current plugin. These phones are to be processed by different plugin.

With the help of this plugin you can do:

  •  Disassemble a full (or, since eMMC full image files are too large, a partial) eMMC Image File previously obtained with JTAG Manager (DCC Read/Write Page);
  •  Inspect each partition contents;
  •  Save separate partitions to HDD;
  •  Save all partitions as standalone files to HDD;
  •  Build-up your own full image file: for this you need to read from device (by clicking “Load Image from Device” button) or open from file (by clicking “Load Image from File” button) the eMMC partitioning data and then by selecting desired partitions click “Inject Into Partition” button to upload data from file into selected partition. Then you can save all full image file to HDD or flash injected partitions directly into device;
  •  Write a chosen partition directly into device;
  •  Read a chosen partition directly from device and substitute old partition contents to new ones;
  •  Create eMMC partitioning snapshot (that is storing info on full EBR chain: each EBR sector position).
  •  Restore eMMC partitioning from previously taken file: it is convenient if eMMC memory is erased and all formatting data is lost.
  •  Plugin supports new RIFF™ shrinked binary files format (*.riffpbin): which allows to shrink huge eMMC Image files into small sized-files (for example, Image File for 14GB empty eMMC chip is shrinked into ~10 KByte(!) size), thus HDD space is preserved, while performance is not visibly effected.

Please note, direct read/write operations from/to the device will require proper resurrector to be set (Resurrector Settings: thus before clicking the Activate Plugin button make sure proper model is selected as well as other settings like TCK/RTCK frequencies).
.

RIFF JTAG – Direct JTAG Access to Flash Memory Plugin v1.00 released

16.12.2011 Direct JTAG Access to Flash Memory Plugin v1.00

Release info:

This plugin performs direct access to a flash memory used in the selected target. No DCC Loader is used here, thus it is completely independent of target hardware implementation (RAM memory availability, visibility, addressing and layout, core clocking, etc.). Main disadvantage is a noticeable data exchange speed decrease comparing to the DCC Loader’s data exchange speeds (approximately 10…20 times slower).

With the help of this plugin you can do:

  • Read selected flash memory range;
  • Write selected flash memory range;
  • Erase selected flash memory range.

Currently supported memory controllers are:

  • OneNAND Memory (connected directly to the MCU’s address space);
  • CFI Compliant NOR Memory with CFI Command sets 0x0001, 0x0002, 0x0200 and 0x0003;
  • NAND Controller in MSM6250, MSM6250A;
  • NAND Controller in QSC6055, QSC6085, QSC6240, QSC6270;
  • NAND Controller in MDM6085, MDM6200, MDM6600;
  • NAND Controller in MSM6245, MSM6246, MSM6270, MSM6275, MSM6280, MSM6280A, MSM6281, MSM6290, MSM6800A, MSM6801A;
  • NAND Controller and OneNAND Controller in MSM7225, MSM7227, MSM7625, MSM7627;
  • NAND Controller in MSM7200, MSM7200A, MSM7201A, MSM7500, MSM7500A, MSM7501A, MSM7600;
  • NAND Controller in QSD8250, QSD8650;
  • eMMC Controller #2 in MSM7230, MSM8255, MSM8255T;
  • eMMC Controller #0 in S5PV310;


Currently supported chipsets and cores for JTAG I/O operations:

  • Generic ARM Cores: ARM7, ARM9 (ARM920, ARM926, ARM946), ARM11, CORTEX-A8,CORTEX-A9;
  • Qualcomm QSC Family: QSC1100, QSC1110, QSC6010, QSC6020, QSC6030, QSC6055, QSC6085, QSC6240, QSC6270;
  • Qualcomm MSM Family: MSM6000, MSM6150, MSM6245, MSM6246, MSM6250, MSM6250A, MSM6260, MSM6275, MSM6280, MSM6280A, MSM6281, MSM6800A, MSM6801A, MSM6290, MSM7225, MSM7227, MSM7625, MSM7627, MSM7230, MSM8255, MSM8255T, MSM8260;
  • Qualcomm QSD Family: QSD8250, QSD8650;
  • Qualcomm ESM Family: ESM7602A;
  • Qualcomm MDM Family: MDM6085 MDM6200, MDM6600;
  • OMAP Family: OMAP1710, OMAP3430, OMAP3630, OMAP4430;
  • NVIDIA Family: TEGRA2;
  • Marvell/XScale Family: PXA270, PXA271, PXA272, PXA310, PXA312, PXA320.
  • Samsung Processors: S5P6422, S5PV310.

Memory reading/programming logic is almost same as is performed on the DCC Read/Write page in the JTAG Manager – Main and Spare fields, Auto FullFlash size detection, ability to flash image files (for NAND)., etc. Users familiar with the DCC Read/Write page features will not be required to learn almost anything new in order to be able to use this plugin. Thus it means data files read from memory by this plugin (partial or full flash image) can be flashed back through the DCC Read/Write page, and vice versa.
Here, it is user’s task now to know such info about target as what exact MCU is used in current device, what memory is used (NAND, OneNAND, NOR, eMMC/SD, MDOC or other), which component of target system can see this memory (for example NAND memory is usually visible to MCU’s Embedded Memory Controller, while NOR is directly accessible by the MCU itself; OneNAND memory in most cases is directly accessible by MCU but sometimes it can be visible via MCU’s Embedded Memory Controller).

Please note main differences with the DCC Read/Write methods:

  • Exact chipset (MCU) name selection is required;
  • Memory type selection is required (for example: NAND or NOR memory);
  • Which component of target system can see this memory (for example: MCU itself or MCU’s Embedded Memory Controller): the ‘Memory Type & Host’ setting;
  • Memory Controller Mode is introduced here (while on DCC Read/Write page in the JTAG Manger the Memory Controller Mode was automatically chosen depending on ROMi Address Space selected). Many Qualcomm NAND Controllers are widely configurable, for example they allow for firmware to select any desired position of bad block marker byte inside of NAND page’s main or spare area, and upon reads/writes this byte will be handled by controller itself, making it ‘invisible’ in the NAND page data. Thus reading NAND with configuration different to the one used by the manufacturer for writing data into this NAND memory (firmware for example) will result in 1 byte to be erroneously read or lost. In many cases (by many manufacturers) the default bad block marker position is configured to be at offset 0x01D1 in the page’s main area (abbreviated Memory Controller Mode you will see in the list as this: “M:0200/S:10/BM:01D1” – meaning NAND controller to be configured for main area 0x0200 bytes, spare area 0x0010 bytes, bad block marker position in main area (BM) at offset 0x01D1 (BM:01D1)); other most common case is for bad block marker to be at position 0x0006 in spare area (such abbreviated Memory Controller Mode you will see in the list as this: “M:0200/S:10/BS:0006” – meaning NAND controller to be configured for main area 0x0200 bytes, spare area 0x0010 bytes, bad block marker position in spare area (BS) at offset 0x0006 (BS:0006));
  • During NAND read operations, if ECC Module Enable is checked, the ECC status is checked too. Thus make sure to disable ECC checks during reads unless you’re in need for an advanced operation.

Short Manual how to Read/Write/Erase memory:

  • Select chipset (MCU) used in the current target (for example MSM6280);
  • Select memory type and it’s host (MCU or MCU’s Embedded Memory Controller);
  • Setup TCK/RTCK frequencies, JTAG I/O Voltage levels, target’s core position on the JTAG scan chain (TAP#);
  • Connect target device to the RIFF BOX, make sure it has power, and click Connect & Flash ID button to ensure target device is connected and selected memory is initialized and visible;
  • All further actions are completely same as is done when using DCC Read/Write page features.

Most common errors which can happen during direct read/write operations:

  • The NRST signal is neglected by user. Please take into account that NRST signal is the most important one. Making system reset helps debugger (RIFF BOX) to establish device into 100% pre-known hardware state, which guarantees that a MCU’s memory controller selected by user will be configured as it should be and successful memory access will be established;
  • Cannot connect to selected memory (Connect & Flash ID): check NRST signal; check Reset Method in settings; make sure proper MCU, memory type and controller is selected in settings; in case NOR or directly accessible OneNAND memory is selected make sure valid memory base is set;
  • “Resetting and Halting Target…” fails: make sure device is powered and power on key (if present) is pressed during this stage; some devices like HTCs based on the MSM8255 chipsets are fused, and JTAG may be enabled only by started firmware – thus you may need to vary the Reset Method settings: disable reset at all (which is not desirable though) or adjust higher waiting time after system is reset by the NRST signal assertion to the moment when an attempt to HALT core is made (for fused HTCs based on MSM8255 this is 670 ms and more);

RIFF JTAG – HTC Advantage X7510 (HTC Athena) Unbrick – Boot Repair supported

04.04.2011  HTC Advantage X7510 (HTC Athena) Unbrick – Boot Repair supported

Resurrection of HTC Athena is easy. Most convenient is to have USB cable connected and battery inserted.
If during connection progress bar in JTAG Manager keeps running from 0 to 100% press with stylus the reset button on the phone (reset button is near to the JTAG pads).
Resurrector will reflash IPL and SPL areas. You can select SPL version to be flashed in the settings window which popups before resurrection. IPL which is flashed: “ATHENA IPL DVT 2.02 H3” version.
Current resurrector works only with HTC Athena hardware revisions which have DiskOnChip H3 memory chip installed. If you have hardware revision with DiskOnChip G4 memory chip used then select different resurrector.

To resurrect HTC Athena with DiskOnChip H3:

  • Solder JTAG cable to HTC Athena JTAG pads;
  • Insert battery and connect USB cable to phone and PC;
  • Make sure HTC Athena is selected in the list of models;
  • Click Resurrect button;
  • Wait till software signals a successful operation completion;
  • Disconnect USB cable, de-solder JTAG wires;

Now phone is in bootable condition, that is, even if it does not start up normally you can flash it using known flashing methods.

To enter download mode:

  • Disconnect PC cable;
  • Insert battery;
  • Hold ‘Camera’ key and press ‘Power ON’ key or use stylus to press ‘Reset’ button. In few seconds you should see TriColor picture.

Additional info:

  • DiskOnChip H3’s full NAND memory chip is divided into partitions by the internal memory controller. Thus DCC Loader creates virtual FLASH chip for each partition – you can read/write these partitions by selecting proper ROM index (“Access ROMi Address Space”) on the JTAG Manager’s DCC Read/Write page;
  • DiskOnChip H3 has no spare zones, thus only Main field must be used during write operations. ECC Enable checkbox has no meaning here.

Please click “Check For Updates” button in order to download and apply new files. Closing all running application before starting update process is recommended.

RIFF JTAG Features

RIFF JTAG firmware supports following features at the moment:

  • ARM7/ARM9/ARM11  PXA3xx,  PXA270, Cortex-A8, OMAP850, Cortex-A9 , Cortex-A15, Cortex-A5 Dual/Quad cores support;
  • Multiple  devices  on  JTAG  chain  are supported, thus TAP number selection is available;
  • Any custom voltage  level selection  from range ~1.4V to 3.3V
  • TCK/Adaptive clocking selection
  • Halt core (NRST is not changed)
  • Reset core (NRST is applied before halt)
  • Direct  Read  memory  (by  8/16/32-bit bytes/half-words/words)
  • Direct  Write  memory  (by  8/16/32-bit bytes/half-words/words)
  • Access  to  the  control  registers  of ARM core (coprocessor 15)
  • Program code breakpoints
  • Run core
  • Custom scripting and DCC loader support (trace32 compatible)
  • Custom GDB Server Available
  • I/O pins detection !Unique feature offered only by RIFF JTAG

This is result of six months hard work. And we just started -;)
Stay tuned for more !

This is list of supported memory controllers and chipsets and CPU cores using Direct Memory Access :

Currently supported memory controllers are:

  • OneNAND Memory (connected directly to the MCU’s address space);
  • CFI Compliant NOR Memory with CFI Command sets 0×0001, 0×0002, 0×0200 and 0×0003;
  • NAND Controller in MSM6250, MSM6250A;
  • NAND Controller in QSC6055, QSC6085, QSC6240, QSC6270;
  • NAND Controller in MDM6085, MDM6200, MDM6600;
  • NAND Controller in MSM6245, MSM6246, MSM6270, MSM6275, MSM6280, MSM6280A, MSM6281, MSM6290, MSM6800A, MSM6801A;
  • NAND Controller and OneNAND Controller in MSM7225, MSM7227, MSM7625, MSM7627;
  • NAND Controller in MSM7200, MSM7200A, MSM7201A, MSM7500, MSM7500A, MSM7501A, MSM7600;
  • NAND Controller in QSD8250, QSD8650;
  • eMMC Controller #2 in MSM7230, MSM8255, MSM8255T;
  • eMMC Controller #0 in S5PV310;


Currently supported chipsets and cores for JTAG I/O operations:

  • Generic ARM Cores: ARM7, ARM9 (ARM920, ARM926, ARM946), ARM11, CORTEX-A8,CORTEX-A9;
  • Qualcomm QSC Family: QSC1100, QSC1110, QSC6010, QSC6020, QSC6030, QSC6055, QSC6085, QSC6240, QSC6270;
  • Qualcomm MSM Family: MSM6000, MSM6150, MSM6245, MSM6246, MSM6250, MSM6250A, MSM6260, MSM6275, MSM6280, MSM6280A, MSM6281, MSM6800A, MSM6801A, MSM6290, MSM7225, MSM7227, MSM7625, MSM7627, MSM7230, MSM8255, MSM8255T, MSM8260;
  • Qualcomm QSD Family: QSD8250, QSD8650;
  • Qualcomm ESM Family: ESM7602A;
  • Qualcomm MDM Family: MDM6085 MDM6200, MDM6600;
  • OMAP Family: OMAP1710, OMAP3430, OMAP3630, OMAP4430;
  • NVIDIA Family: TEGRA2;
  • Marvell/XScale Family: PXA270, PXA271, PXA272, PXA310, PXA312, PXA320.
  • Samsung Processors: S5P6422, S5PV310.

 

This is the list of devices supported with dedicated RIFF DLL-s:

Alcatel models:

  • Alcatel OT255C
  • Alcatel OT990
  • Alcatel OT995

Haier Models:

  • Haier C2010
  • Haier C2040
  • Haier C2076
  • Haier C300
  • Haier C3010
  • Haier C301R
  • Haier C5100
  • Haier C6000

HTC Models:

  • HTC 7Pro
  • HTC 8S
  • HTC 8X16GB
  • HTC 8X8GB
  • HTC Amaze4G
  • HTC Artemis
  • HTC Athena
  • HTC ChaCha
  • HTC Chief
  • HTC Click
  • HTC Dash
  • HTC Desire
  • HTC DesireCDMA
  • HTC DesireC
  • HTC DesireHD
  • HTC DesireS
  • HTC DesireV
  • HTC DesireX
  • HTC DesireZ
  • HTC Diamond
  • HTC Dream
  • HTC DroidDNA
  • HTC DroidEris
  • HTC Elf
  • HTC Espresso
  • HTC Evo3DCDMA
  • HTC EVO3D
  • HTC EvoDesign4G
  • HTC EvoView4G
  • HTC Explorer
  • HTC Explorer
  • HTC Flyer4G
  • HTC Flyer
  • HTC Flyer
  • HTC Gene100
  • HTC Glacier
  • HTC HD
  • HTC HD2
  • HTC HD7
  • HTC HD7Pro
  • HTC HDMini
  • HTC Herald
  • HTC Hero
  • HTC Imagio
  • HTC IncredibleS
  • HTC Incredible-2
  • HTC Incredible-C
  • HTC Incredible-S
  • HTC Inspire
  • HTC Jade
  • HTC JetStream
  • HTC Jewel
  • HTC Legend
  • HTC Magic32A
  • HTC Magic32B
  • HTC Magic
  • HTC Mega
  • HTC Mozart
  • HTC MyTouch4G
  • HTC Neon
  • HTC Nexus
  • HTC Niki
  • HTC OneS3
  • HTC OneS4
  • HTC OneV
  • HTC OneXL
  • HTC OneX
  • HTC Polaris
  • HTC Radar
  • HTC Raphael
  • HTC Rezound
  • HTC Rhodium
  • HTC RhodiumW
  • HTC Rhyme
  • HTC Sensation4G
  • HTC SensationXL
  • HTC Sensation
  • HTC Snap
  • HTC Supersonic
  • HTC Surround
  • HTC Tattoo
  • HTC Thunderbolt
  • HTC Titan
  • HTC Topaz
  • HTC Trophy
  • HTC Vivid
  • HTC WildFire
  • HTC WildfireS
  • HTC WildfireSCDMA
  • HTC Wings
  • HTC Wizard
  • HTC Desire SV T326e (HTC Magni)
  • HTC J ISW13HT (HTC Valente)

Huawei Models:

  • Huawei C2605
  • Huawei C2607
  • Huawei C2801
  • Huawei C2806M
  • Huawei C2807
  • Huawei C2808
  • Huawei C2809
  • Huawei C2823
  • Huawei C2830
  • Huawei C2856
  • Huawei C2901M
  • Huawei C2905
  • Huawei C2906
  • Huawei C31
  • Huawei C3200
  • Huawei C3500
  • Huawei C5005
  • Huawei C5100
  • Huawei C5589
  • Huawei C8500
  • Huawei E153U
  • Huawei E1550
  • Huawei E160
  • Huawei E160G
  • Huawei E169
  • Huawei E17X
  • Huawei E220
  • Huawei E5830
  • Huawei E5832
  • Huawei E585
  • Huawei EC1260
  • Huawei EC189
  • Huawei ETS2205
  • Huawei ETS2222
  • Huawei ETS2225
  • Huawei S7
  • Huawei U1270
  • Huawei U1280
  • Huawei U2800
  • Huawei U8110
  • Huawei U8150
  • Huawei U8150D
  • Huawei U8160
  • Huawei U8180
  • Huawei U8220
  • Huawei U8350
  • Huawei U8350-51
  • Huawei U8500
  • Huawei U8650
  • Huawei U8655
  • Huawei U8800
  • Huawei U8800Pro
  • Huawei U8815
  • Huawei U8825D
  • Huawei U8860

LG Models:

  • LG C660H
  • LG CU720
  • LG E400
  • LG E405
  • LG E510
  • LG E612
  • LG E615
  • LG E900
  • LG F100S
  • LG F120K
  • LG F120L
  • LG F160K
  • LG F160L
  • LG F160S
  • LG GM730
  • LG GT540
  • LG LS970
  • LG LSP450T
  • LG P350
  • LG P500
  • LG P698
  • LG P705
  • LG P930
  • LG P970
  • LG P999
  • LG RD3000
  • LG RD3100
  • LG RD3500
  • LG RD3510
  • LG RD3540
  • LG RD3610
  • LG RD3640
  • LG RD6100
  • LG SH860
  • LG SU630
  • LG TD636
  • LG VM265

MicroMax models:

  • Micromax C100
  • Micromax C111
  • Micromax MMX250C

Motorola Models:

  • Motorola W150i
  • Motorola W200
  • Motorola W210

Nokia Models:

  • Nokia 1006
  • Nokia 1255
  • Nokia Lumia 610

Pantech Models:

  • Pantech A730S
  • Pantech A760S
  • Pantech A770K
  • Pantech A800S
  • Pantech A810S
  • Pantech A820L
  • Pantech A830K
  • Pantech A830L
  • Pantech A830S
  • Pantech A840S
  • Pantech A850K
  • Pantech A850L
  • Pantech A850S
  • Pantech T100K
  • Pantech UM150
  • Pantech UM175

Samsung Models:

  • Samsung A837
  • Samsung A867
  • Samsung A877
  • Samsung A887
  • Samsung A900
  • Samsung B119
  • Samsung B139
  • Samsung B159
  • Samsung B209
  • Samsung B219
  • Samsung B259
  • Samsung B2710
  • Samsung B309
  • Samsung B319
  • Samsung B339
  • Samsung B379
  • Samsung B5330
  • Samsung B5510
  • Samsung B619
  • Samsung B6520
  • Samsung B7320
  • Samsung B7330
  • Samsung B7510
  • Samsung C5510
  • Samsung C6712
  • Samsung E110S
  • Samsung E120L
  • Samsung E120S
  • Samsung E160K
  • Samsung E160L
  • Samsung E189
  • Samsung E329I
  • Samsung F219
  • Samsung F480
  • Samsung F500
  • Samsung F619
  • Samsung G800
  • Samsung G810
  • Samsung i450
  • Samsung I500
  • Samsung I509
  • Samsung i520
  • Samsung I535
  • Samsung I5500
  • Samsung i550
  • Samsung I5510
  • Samsung I559
  • Samsung i560
  • Samsung I5700
  • Samsung I5800
  • Samsung i607
  • Samsung i710
  • Samsung I717
  • Samsung i718
  • Samsung I727
  • Samsung i740
  • Samsung i740
  • Samsung I747
  • Samsung I747M
  • Samsung I7500
  • Samsung I777
  • Samsung i780
  • Samsung I8000
  • Samsung I8000L
  • Samsung I8150
  • Samsung I8160
  • Samsung I8190
  • Samsung i8320
  • Samsung I8350
  • Samsung i8510
  • Samsung I8530
  • Samsung I8700
  • Samsung i8910
  • Samsung I897
  • Samsung I9000
  • Samsung I9001
  • Samsung I9003
  • Samsung i900
  • Samsung i900
  • Samsung I9020A
  • Samsung I9020T
  • Samsung I9023
  • Samsung I9070
  • Samsung I9070P
  • Samsung i908E
  • Samsung I9100
  • Samsung I9100G
  • Samsung I9100GX
  • Samsung I9100P
  • Samsung I9103
  • Samsung I9105
  • Samsung I9108
  • Samsung I9108X
  • Samsung i910
  • Samsung I917
  • Samsung I920
  • Samsung I920
  • Samsung I9210
  • Samsung I9220
  • Samsung I9300
  • Samsung I997
  • Samsung L760
  • Samsung M110S
  • Samsung M130K
  • Samsung M180S
  • Samsung M180W
  • Samsung M190S
  • Samsung M200K
  • Samsung M200S
  • Samsung M240S
  • Samsung M569
  • Samsung M7500
  • Samsung M7600
  • Samsung M820
  • Samsung M828
  • Samsung M8800
  • Samsung M8910
  • Samsung N7000
  • Samsung N8010
  • Samsung P1000
  • Samsung P1000N
  • Samsung P1010
  • Samsung P3100X
  • Samsung P3110X
  • Samsung P3113X
  • Samsung P5100X
  • Samsung P5110X
  • Samsung P5113X
  • Samsung P6200
  • Samsung P6800
  • Samsung P6810
  • Samsung P7320
  • Samsung P960
  • Samsung R530
  • Samsung S109
  • Samsung S189
  • Samsung S239
  • Samsung S3310
  • Samsung S3370
  • Samsung S359
  • Samsung S3850
  • Samsung S5230
  • Samsung S5250
  • Samsung S5260
  • Samsung S5300
  • Samsung S5301
  • Samsung S5360
  • Samsung S5380
  • Samsung S5380D
  • Samsung S5510
  • Samsung S5560
  • Samsung S5560i
  • Samsung S5570
  • Samsung S5570i
  • Samsung S5600
  • Samsung S5660
  • Samsung S5670
  • Samsung S5750E
  • Samsung S5830
  • Samsung S5830G
  • Samsung S5830i
  • Samsung S5830L
  • Samsung S6012
  • Samsung S6102
  • Samsung S6312
  • Samsung S6500
  • Samsung S6500D
  • Samsung S6802
  • Samsung S6810P
  • Samsung S7070
  • Samsung S7230E
  • Samsung S7250D
  • Samsung S7330
  • Samsung S7350
  • Samsung S7350i
  • Samsung S7500
  • Samsung S7500L
  • Samsung S7500T
  • Samsung S7530
  • Samsung S7562
  • Samsung S7562I
  • Samsung S8000
  • Samsung S8300
  • Samsung S8500
  • Samsung S8530
  • Samsung S8600
  • Samsung SC-05D
  • Samsung SC-06D
  • Samsung SPH-D700
  • Samsung SPH-D710
  • Samsung SPH-L710
  • Samsung T479
  • Samsung T499
  • Samsung T589
  • Samsung T669
  • Samsung T679
  • Samsung T749
  • Samsung T759
  • Samsung T879
  • Samsung T919
  • Samsung T939
  • Samsung T959
  • Samsung T959D
  • Samsung T959V
  • Samsung T989
  • Samsung T999
  • Samsung T999V
  • Samsung U700
  • Samsung U800
  • Samsung U900V
  • Samsung W299
  • Samsung W629
  • Samsung YPG1
  • Samsung YPG70
  • Samsung Z240
  • Samsung Z500
  • Samsung Z540
  • Samsung Z630
  • Samsung Z650i
  • Samsung Z710
  • Samsung ZV60
  • Samsung GT-i9105 Galaxy S II Plus
  • Samsung GT-i9082 Galaxy Grand Duos
  • Samsung Gt-S5380k Wave Y

SonyEricsson Models:

  • SE E15a
  • SE U20a
  • SE U20i
  • SE X1
  • SE X10
  • SE X10Mini
  • SE X8

Sierra Models:

  • Sierra 597
  • Sierra 801
  • Sierra U595

Toshiba Models:

  • Toshiba G810
  • Toshiba G900 PDA
  • Toshiba G910
  • Toshiba TG01

ZTE Models:

  • ZTE CN600
  • ZTE AC2746
  • ZTE AC2766
  • ZTE AC30
  • ZTE C335
  • ZTE C370
  • ZTE F160
  • ZTE F280
  • ZTE F285
  • ZTE FWPC26
  • ZTE MF100
  • ZTE MF112
  • ZTE MF170
  • ZTE MF180
  • ZTE MF180S
  • ZTE MF190
  • ZTE MF622
  • ZTE MF626
  • ZTE MF627
  • ZTE MF628
  • ZTE N721
  • ZTE R518
  • ZTE S100
  • ZTE S160
  • ZTE S1602
  • ZTE S165
  • ZTE S170
  • ZTE S185
  • ZTE Skate
  • ZTE V880
  • ZTE V889D
  • ZTE V9
  • ZTE WP829

Various brands and models:

  • Acer S100
  • Anydata ADU 555C
  • ASUS P526
  • CoolPad 5860Plus
  • Daewoo DPN3500
  • DELL Streak
  • DELL XCD28
  • Eten X800
  • EuroSky ES4100
  • Fly IQ285
  • Intex In50
  • iPAQ 614
  • Lenovo LePhone3GW100
  • LinkSys WRT54GL
  • Olive C2110
  • Orange Boston
  • Orton 4100C
  • Qtek 9000
  • RoverPC EvoV7
  • Sungil SXC1080
  • Unicare ChivaC2
  • Unicare UN510BF

Please note – virtually thousands of different models are supported with RIFF Box, If You are advanced user