Can anybody check out if Motorola use FATX for cell phones of E- and V-Series?

The FS on a mini-sd contains in block 1 partial a FAT16-signature but div. tools reject
to handle it as FAT16!


If you have a suitable card-reader and a sdram formated from an Moto Cell Phone (E- or V-Series),
you are well equipd.

I don't know how to read via P2K (protocol) with an usb-cable.
This will be an good thing to exploit the undocumented attributes.

If it's right that Moto use FATX on Cell Phones, than there are reasons to make xfat to a package!

WTF....does this look like a cell phone forum....NO....reported

FATX is unique to the Xbox and the Xbox 360 - what you have there is FAT16 which is quite common and efficient on small capacity storage.

.. can't find the missing link, right?

I make it simple ..

1. FATX is topix to xbox
2. FS on Motorola is not FAT16!!!
If it is signed as that or not ... It ISN'T! Don't believe?
Check FAT16-Spec and use disk-editor!
3. It has characteristics found in FATX!
4. FATX is topic to xbox. (see 1.)
5. Thesis is Motorola use FATX

Therefore this topic is topic to xbox! report it!

In a mobile forum is the numer of people knowing about FS very rare and more rare about fatx.
Which forum do you want to advice me?

I don't have a Motorola cell phone or a dump of the filesystem from the device, so I can't say for sure if you are right or not. However, I can say that I am as familiar with FATX as it is possible to be / I have developed and maintained a program for reading and writing FATX from a number of devices for quite some time. I am also thoroughly familiar with FAT12, FAT16, and FAT32 / FAT32 long filename support. It is also probably pretty safe to say that Motorola was not reverse engineering Microsoft's file systems for use in their phone.

What is more likely, is that, faced with the 8.3 filename limitations of traditional and not wanting to implement the crappy longfilename format Microsoft crapped on the filesystem, they implemented their own directory entry structure with a larger area for the filename, similar to FATX.

This does not make it FATX - FATX on the Xbox included a 'BRFR' section at the start of the drive (refurb info), Xbox Live data, and a special partition header format - the partition table was stored in the kernel. The 360 has the table in the kernel, and has a signed cryptographic hash to prevent consumers from using cheaper off-the-shelf hard disk drives.

I stand by what I originally posted - it is FAT16 as it says, meaning it uses 16 bit FAT entries. They may have updated the directory entry format to something more modern and flexible, and maybe added something special to the header - but still FAT16. Hell, internally different FATX partitions are referred to as FATX16 or FATX32 - the X just means Xbox, they are just FAT with modern directory entries and no longfilename patch.

This is for posting XBOX 360 software/exploits, read a little better befor you post again

Moving to The Dump

try on www.howardforums.com im sure they can tell you

Do you think we are all cell phone geniuses? common this is xbox-scene. not cellphone-scene. Put your technical cell phone crap somewheres else