[2014.05.01][ROOT] Mobile ODIN v4.20

Search This thread

Chainfire

Moderator Emeritus / Senior Recognized Developer
Oct 2, 2007
11,452
87,856
www.chainfire.eu
I don't see anything weird with the .tar files themselves. This problem only happens on D710 ? And it ALWAYS happens with .tar, or have you succeeded flashing some .tar ?

Just tried .tar flashing on several of my devices, seems to work fine :X
 

xenix96

Senior Member
Dec 31, 2011
999
763
Samsung Galaxy S23 Ultra
[HELP] Partiton Table for GT-P6800 // Chainfire need your help :)

When i flash on my SGT 7.7 GT-P6800 with Mobile Odin pro it flash like this:

Paramameter
Kernel
Recovery
System
Modem
Hidden
Cache

So is that meaning the partiton table of my SGT 7.7 GT-P6800 is like this?

/dev/block/mmcblk0p1 = Param
/dev/block/mmcblk0p2 = Kernel
/dev/block/mmcblk0p3 = Recovery
/dev/block/mmcblk0p4 = System
/dev/block/mmcblk0p5 = Modem
/dev/block/mmcblk0p6 = Hidden
/dev/block/mmcblk0p7 = Cache


I made .pit file with Heimdall this is the text version:

Heimdall v1.3.1, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au

This software is provided free of charge. Copying and redistribution is
encouraged.

If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/

Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...

Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...

Beginning session...
Session begun with device of type: 131072

Downloading device's PIT file...
PIT file download sucessful

Entry Count: 15
Unknown 1: 0
Unknown 2: 0
Unknown 3: 0
Unknown 4: 0
Unknown 5: 0
Unknown 6: 0
Unknown 7: 0
Unknown 8: 0


--- Entry #0 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 0
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 0
Partition Block Count: 0
Unknown 2: 0
Unknown 3: 0
Partition Name: GANG
Filename: emmc.img


--- Entry #1 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 1
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 0
Partition Block Count: 0
Unknown 2: 0
Unknown 3: 0
Partition Name: BOOT
Filename: boot.bin


--- Entry #2 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 4
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 8192
Partition Block Count: 40960
Unknown 2: 0
Unknown 3: 0
Partition Name: EFS
Filename: efs.img


--- Entry #3 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 2
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 49152
Partition Block Count: 2560
Unknown 2: 0
Unknown 3: 0
Partition Name: SBL1
Filename: Sbl.bin


--- Entry #4 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 3
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 53248
Partition Block Count: 2560
Unknown 2: 0
Unknown 3: 0
Partition Name: SBL2
Filename:


--- Entry #5 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 5
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 57344
Partition Block Count: 16384
Unknown 2: 0
Unknown 3: 0
Partition Name: PARAM
Filename: param.lfs


--- Entry #6 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 6
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 73728
Partition Block Count: 16384
Unknown 2: 0
Unknown 3: 0
Partition Name: KERNEL
Filename: zImage


--- Entry #7 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 7
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 90112
Partition Block Count: 16384
Unknown 2: 0
Unknown 3: 0
Partition Name: RECOVERY
Filename: recovery.img


--- Entry #8 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 8
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 106496
Partition Block Count: 409600
Unknown 2: 0
Unknown 3: 0
Partition Name: CACHE
Filename: cache.img


--- Entry #9 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 9
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 516096
Partition Block Count: 32768
Unknown 2: 0
Unknown 3: 0
Partition Name: MODEM
Filename: modem.bin


--- Entry #10 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 10
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 548864
Partition Block Count: 1703936
Unknown 2: 0
Unknown 3: 0
Partition Name: FACTORYFS
Filename: factoryfs.img


--- Entry #11 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 11
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 2252800
Partition Block Count: 27582464
Unknown 2: 0
Unknown 3: 0
Partition Name: DATAFS
Filename: data.img


--- Entry #12 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 12
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 29835264
Partition Block Count: 917504
Unknown 2: 0
Unknown 3: 0
Partition Name: HIDDEN
Filename: hidden.img


--- Entry #13 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 13
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 30752768
Partition Block Count: 16384
Unknown 2: 0
Unknown 3: 0
Partition Name: FOTA
Filename:


--- Entry #14 ---
Unused: Yes
Partition Type: 1 (Unknown)
Partition Identifier: 9
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 0
Partition Block Count: 0
Unknown 2: 0
Unknown 3: 0
Partition Name:
Filename:

Ending session...
Rebooting device...

So i am abit confused now ... can you plz say me the right Partition Table for my SGT 7.7 GT-P6800 cause i want to clear somethings with the root file in SGT 7.7 Forum


Summary:

See here [GUIDE] Root - version & directorys of SU & BUSYBOX where it flashes i use the same file! :)

It is -> @root - /system/xbin/su & @root - /system/xbin/busybox

Yeah but the updater-script mounts /dev/block/mmcblk0p4 as system. As far as i know the system is at mmcblk0p9 on P6800. I have no idea whats mmcblk0p4.

Since following command dont work on HC i need your help

adb shell
su
cat proc/mtd


Thanks you in advance Chainfire :D

And thanks for the powerfull Mobile Odin pro app :D
 
Last edited:

xenix96

Senior Member
Dec 31, 2011
999
763
Samsung Galaxy S23 Ultra
That partition table isn't right... what are you after exactly? /system? that's mmcblk0p9 on 6800 and mmcblk0p8 on 6810.

Thread: [GUIDE] Root - with the file root.zip

1st of all i wanted know if this is right or not: http://xdaforums.com/showpost.php?p=23327367&postcount=15

Hes right cause you say /system is on 6800 mmcblk0p9 an on 6810 is mmcblk0p8

Then we got a problem like the user davp post here http://xdaforums.com/showpost.php?p=22650451&postcount=98

I wanted now know the full partition table to offer it in developer section in SGT 7.7 Forum in hope some dev will make for us correct working root file.
And in future the full partition table will 100% help devs to create Custom Roms wich not brick devices like here http://xdaforums.com/showthread.php?t=1497916

My purpose is not make a profit from this partition table - My purpose is to bring some clearance in Forum Section: Galaxy Tab 7.7 Android Development

So maybe you will help me with saying me the full partition table for 6800 and 6810. Or just give me the right command ill get it by my self.

Anyways thanks for your reply :)
 
Last edited:

Chainfire

Moderator Emeritus / Senior Recognized Developer
Oct 2, 2007
11,452
87,856
www.chainfire.eu
Depending on your recovery version it will mount the right blocks in /system no matter what command block you put it. Or, recovery may already have mounted /system, which makes the whole point moot.

EDIT: More importantly, I have just read up on the threads you refer to. Some really stupid mistakes have been made by the ROM chefs on the 7.7 ... You flash a kernel into your IBL/PBL partition, yes, that's going to brick to your device. Furthermore, it'll require a JTAG to revive, and service centers usually do not use those. So the repair centers will usually replace the board - while there's physically nothing wrong with the board. The correct partition table would not have helped, becaused the user in question would still have confused boot.bin (IBL/PBL) with boot.img (kernel) - it would not have mattered.

EDIT#2: http://xdaforums.com/showthread.php?t=1534033
 
Last edited:
  • Like
Reactions: xenix96

AboodR

New member
Feb 25, 2012
4
0
Why there is nothing for GT-I8150, :mad:

All developer think about S2, S1, S1+, Nexus, even ACE but Samsung W (GT-I8150) no one think about it, i hate this mobile :(

i want this program on my phone can any one do it, pleeeeeeease :eek:
 

teiglin

Senior Member
Jul 7, 2011
627
134
This is usually a superuser problem. Try rebooting :)

Hah, are we running Windows 95 now? :p

Sadly, that didn't fix it, and I double-checked and other apps are able to elevate just fine. I pulled a logcat but wasn't able to discern anything useful from it--there is a ServiceConnectionLeaked exception, but it seems like that's just a warning rather than anything problematic. Is there some sort of useful logging/debugging info I can get you on this?

Edit: I uninstalled and reinstalled the app and it decided to work now. Whatever. :)
 
Last edited:

Dchibro

Senior Member
Jul 28, 2011
1,040
280
San Diego, CA
So has anyone had a successful flash with a modem.bin file? From reading this thread, it seems others experienced the same thing that I did. The flash seems normal, phone reboots, Mobile Odin does its thing before the OS boots, then when checking the baseband it doesn't change.

I saw someone has successfully flashed a modem.tar, but individual modem files are usually out there as modem.bin. Could be as simple as packing up the modem.bin file into a TAR archive?
 

SimmoF

Senior Member
Dec 6, 2011
642
302
41
Shinjuku City
This is the dump of the Japanese Galaxy S II (Docomo SC-02C).
I believe the system partition is a little larger in exchange for some of the space from the hidden partition.

I hope you can add support for this soon.
 

Attachments

  • mobileodin.txt
    22.3 KB · Views: 3

Chainfire

Moderator Emeritus / Senior Recognized Developer
Oct 2, 2007
11,452
87,856
www.chainfire.eu
So has anyone had a successful flash with a modem.bin file? From reading this thread, it seems others experienced the same thing that I did. The flash seems normal, phone reboots, Mobile Odin does its thing before the OS boots, then when checking the baseband it doesn't change.

I saw someone has successfully flashed a modem.tar, but individual modem files are usually out there as modem.bin. Could be as simple as packing up the modem.bin file into a TAR archive?

This maybe a problem specific to CDMA devices... I'm not sure yet though.
 

xenix96

Senior Member
Dec 31, 2011
999
763
Samsung Galaxy S23 Ultra
Want to add Guide for M.O.Pro to my Thread - Need your okay for this :)

After many Q for how to work/flash by some users i decided to make a Guide in reffering to your manual on (Market)Google Play.

Just take a look on it and let me know if this is okay.
For any improvements i am open.

I wanted to add it on my Sticky Thread: [ROM&GUIDE] Official Firmwares SGT 7.7 P6800 + P6810 Download


######STARTING PREVIEW





Flashing Firmware with Mobile Odin Pro

----- SHORT INTRODUCING -----

Mobile ODIN - Full firmware flashing straight from the device itself!

Mobile ODIN is the on-device firmware flasher of choice. Just throw those firmware files on your (internal or external) SD card, start Mobile ODIN and flash away.

!!! Your device must be rooted to be able to use Mobile ODIN. Check the list below to see if your device is supported !!!



If you use the EverRoot option, Mobile ODIN will root the firmware while you flash it. Checking out that new leaked firmware? No reason to lose root!


Flashing with Mobile ODIN does NOT increase your custom kernel flash counter or make the yellow warning triangle appear.

All partitions are supported, as are loose files, .tar files and .tar.md5 files. Mobile ODIN will even check the MD5 signatures before flashing. While in theory Mobile ODIN can repartition and flash EFS and bootloaders, it will cowardly refuse to do so, for your own safety.

! USE AT YOUR OWN RISK !
----- DEVICE SUPPORT -----​

See the forum thread on XDA-Developers.com ( http://xdaforums.com/showthread.php?t=1347899 ) for more information on how to get your device supported.



----- FLASHING VIA MOBILE ODIN PRO -----​

1.

50106516.jpg


2.

23641010.jpg


3.

57956886.png


4.

17609547.png


5.

72361942.png


----- IMPORTANT TO KNOW-----

This is only a Guide for How to flash via Mobile Odin Pro!!!

For any support post in original xda thread: http://xdaforums.com/showthread.php?t=1347899

ALL RIGHTS RESERVED TO XDA Developer Chainfire

Website: http://www.chainfire.eu/

Mail: market@chainfire.eu



######ENDING PREVIEW




Please let me know as soon as possible - cause i wanted to add this for sure -
 
Last edited:

midi_1996

Senior Member
Aug 8, 2011
305
65
Hi there
I can't flash my gt-i9000 on onecosmic's ics 4.1 with MobileOdin
There's any thing that I can do?
He tell me that he don't know my phone's model.
Tnks for that software.
 

mermaidkiller

Senior Member
Jul 25, 2011
186
14
An official update for ICS 4.0 for the Galaxy S2 is coming.

Can I use Mobile Odin Pro to flash the official ICS 4.0 firmware + kernel ?
 
C

cheyenne

Guest
An official update for ICS 4.0 for the Galaxy S2 is coming.

Can I use Mobile Odin Pro to flash the official ICS 4.0 firmware + kernel ?

I flashed leaked ICS 4.0.3 ROM i9100 (LPH dated february 9) with mobile odin. It's works, but after 4.0.3 was flashed, superuser can not recognise mobile odin app.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    @Chainfire

    what ODIN n Karnel flash for
    Samsung Galaxy A71 (SM-A715F) ?
    3.13.1 is the latest Odin. Always use the latest one.
    You don't flash the kernel, you flash the entire ROM, or individual parts of it. Try https://www.sammobile.com/samsung/galaxy-a71/firmware/ for the ROM (I don't know what country you're in, so you'll have to look).
  • 1484
    Mobile ODIN is the on-device firmware flasher of choice. Just throw those firmware files on your (internal or external) SD card, start Mobile ODIN and flash away.

    ! Your device must be rooted to be able to use Mobile ODIN. Check the list below to see if your device is supported !

    If you use the EverRoot option (Market/Pro version only), Mobile ODIN will root the firmware while you flash it. Checking out that new leaked firmware? No reason to lose root!

    All partitions are supported, as are loose files, .tar files and .tar.md5 files. Mobile ODIN will even check the MD5 signatures before flashing. While in theory Mobile ODIN can repartition and flash EFS and bootloaders, it will cowardly refuse to do so, for your own safety.

    Currently supported devices:

    - Samsung Galaxy S GT-I9000
    - Samsung Galaxy S GT-I9000B
    - Samsung Galaxy S GT-I9000M
    - Samsung Galaxy S GT-I9003
    - Samsung Galaxy S GT-I9003L
    - Rogers Captivate SGH-I896
    - AT&T Captivate SGH-I897

    - Samsung Galaxy S2 GT-I9100
    - Samsung Galaxy S2 GT-I9100T
    - Samsung Galaxy S2 GT-I9100G
    - Samsung Galaxy S2 GT-I9100M
    - Samsung Galaxy S2 SHW-M250S
    - Samsung Galaxy S2 SHW-M250K
    - Samsung Galaxy S2 SC-02C
    - AT&T Galaxy S2 SGH-I777
    - Sprint/Virgin/Boost Epic 4G Touch SPH-D710/VMUB/BST
    - USCC Galaxy S2 SCH-R760

    - Samsung Galaxy S3 GT-I9300
    - Samsung Galaxy S3 GT-I9300T
    - Samsung Galaxy S3 GT-I9308
    - AT&T Galaxy S3 SGH-I747
    - Canadia Galaxy S3 SGH-I747M
    - TMOUS Galaxy S3 SGH-T999
    - Sprint Galaxy S3 SPH-L710
    - VZW Galaxy S3 SCH-I535 (unlock bootloader !)
    - USCC/Cricket/MetroPCS Galaxy S3 SCH-R530/U/M/C

    - Samsung Galaxy S3 LTE SHV-E210S
    - Samsung Galaxy S3 LTE GT-I9305
    - Samsung Galaxy S3 LTE GT-I9305T
    - Samsung Galaxy S3 LTE GT-I9305N

    - Samsung Galaxy S4 LTE GT-I9505
    - Sprint Galaxy S4 SPH-L720
    - T-Mobile Galaxy S4 SGH-M919
    - US Cellular Galaxy S4 SCH-R970
    - Canadia Galaxy S4 SGH-I337M

    - Samsung Galaxy S5 International SM-G900F
    - Samsung Galaxy S5 Oceania SM-G900I
    - Samsung Galaxy S5 Korea SM-G900L
    - Samsung Galaxy S5 Middle and South America SM-G900M
    - Sprint Galaxy S5 SM-G900P
    - US Cellular Galaxy S5 SM-G900R4
    - T-Mobile US Galaxy S5 SM-G900T
    - Metro PCS Galaxy S5 SM-G900T1
    - Canadia Galaxy S5 SM-G900W8

    - Google Galaxy Nexus (GSM) Maguro/Yakju/GT-I9250
    - Google Galaxy Nexus (CDMA/LTE) Toro/Mysid/SCH-I515 (no cdma radio flashing)

    - Samsung Galaxy Note GT-N7000
    - Samsung Galaxy Note GT-I9220
    - Samsung Galaxy Note GT-N7000B

    - Samsung Galaxy Note 2 GT-N7100
    - Samsung Galaxy Note 2 LTE GT-N7105
    - AT&T/Canadia Galaxy Note 2 SGH-I317/M
    - TMOUS Galaxy Note 2 SGH-T889
    - Sprint Galaxy Note 2 SPH-L900
    - VZW Galaxy Note 2 SCH-I605 (unlock bootloader !)
    - USCC Galaxy Note 2 SCH-R950

    - Samsung Galaxy Note 3 SM-N9005
    - Sprint Galaxy Note 3 SM-N900P
    - T-Mobile Galaxy Note 3 SM-N900T
    - US Cellular Galaxy Note 3 SM-N900R4
    - Canadia Galaxy Note 3 SM-N900W8

    - Samsung Galaxy Note 8.0" GT-N5100
    - Samsung Galaxy Note 8.0" Wi-Fi GT-N5110/N5113
    - Samsung Galaxy Note 8.0" LTE GT-N5120

    - Samsung Galaxy Note 10.1" GT-N8000
    - Samsung Galaxy Note 10.1" Wi-Fi GT-N8010/N8013
    - Samsung Galaxy Note 10.1" LTE GT-N8020

    - Samsung Galaxy Tab 7" GT-P1000
    - Samsung Galaxy Tab 7.0 Plus GT-P6200
    - Samsung Galaxy Tab 7.0 Plus Wi-Fi GT-P6210
    - Samsung Galaxy Tab 7.0 Plus GT-P6200L
    - Samsung Galaxy Tab 7.7" GT-P6800
    - Samsung Galaxy Tab 7.7" Wi-Fi GT-P6810
    - Samsung Galaxy Tab 10.1" GT-P7500
    - Samsung Galaxy Tab 10.1" Wi-Fi GT-P7510
    - Samsung Galaxy Tab 2 7" GT-P3100
    - Samsung Galaxy Tab 2 7" Wi-Fi GT-P3110/P3113
    - Samsung Galaxy Tab 2 10" GT-P5100
    - Samsung Galaxy Tab 2 10" Wi-Fi GT-P5110/P5113

    - Samsung Galaxy 5 GT-I5500
    - Samsung Galaxy 5 GT-I5500B
    - Samsung Galaxy 5 GT-I5500L
    - Samsung Galaxy 5 GT-I5500T
    - Samsung Galaxy 5 GT-I5500M
    - Samsung Galaxy 5 GT-I5503
    - Samsung Galaxy 5 GT-I5503T
    - Samsung Galaxy 5 GT-I5508

    More devices to come!

    Flashing with Mobile ODIN does NOT increase your custom kernel flash counter or make the yellow warning triangle appear.

    ! USE AT YOUR OWN RISK !

    Credits
    Aside from my own CF-Root-based flashkernels, Mobile ODIN also uses (with permission) flashkernels built by these users:
    - Codeworkx (I777, D710)
    - Skin1980 (I9003)
    - Kyuta Syoko (I896, I897)
    - Psyke83 (I5500)

    Also many thanks to the various testers!

    Download

    Mobile ODIN Pro - Android Market / Google Play

    Attached is the Lite version of Mobile ODIN - this is a release exclusive to XDA and may not be redistributed ! Please note that you also need to download and install a "FlashKernel" manually if you are using the Lite version. These are listed a few posts down from here. The Pro version will automatically download and install these for you when needed.

    ( < 4.20: 382029 )
    321
    Manual

    Flashing with Mobile ODIN is easy. You start off by starting the app. The app will check your system has everything the app needs to continue (like root). The Pro version will download additional packages if needed automatically - so it is advised to have Wi-Fi available - for the Lite version you need to install the right package manually (see the FlashKernels posts a few posts down).

    Now you should see the main Mobile ODIN screen. It will list a set of partitions. Clicking a partition will allow you to select a file from your SD card to flash to that partition. Do not worry about selecting the wrong file - Mobile ODIN will not let you. Separate files (named after the partition) as well as .tar and .tar.md5 files are supported. Specific .exe files (Odin3Excutor one-click packages) are also supported.

    From the desktop ODIN you may be used to "PDA", "PHONE", and "CSC" buttons. All three of these buttons have been replaced by the "Open file ..." button. This button will open the file you select from the SD card, and find all the partitions it can flash inside that file. So if you select a .tar file containing kernel and modem, the Kernel and Modem partitions will be set up to use that .tar file for flashing. To get the same result as desktop ODIN, use Open file... on .tar files for PDA, PHONE and CSC, in that order.

    Now that we have selected what we want to flash, if you have the Pro version you can proceed to the EverRoot section. The EverRoot options allows you to root your firmware while it is being flashed. Never again will you be without root! Select here which apps you want to inject in the firmware that is being flashed.

    Now that we are all done selecting partitions and configuring EverRoot, we continue to "Flash firmware". Mobile ODIN will gather all the information it needs and perform the flash. Before starting, however, it will check that your battery level is over 50%, and if applicable offer to verify MD5 checksums on the files you have selected to flash. If all is well, it will reboot into recovery mode, and flash the firmware you have selected.

    You can also enable the wipe option. This will wipe both data and cache partition. BEWARE: If you have a device that shares the same space between data and internal sdcard partitions, enabling the wipe option may also wipe the internal sdcard !
    181
    FlashKernels

    I9000: Samsung Galaxy S GT-I9000

    I9100: Samsung Galaxy S2 GT-I9100 and GT-I9100T, SC-02C, SHW-M250S, SHW-M250K v3.0 is a few posts down!
    I9100G: Samsung Galaxy S2 GT-I9100G

    N7000: Samsung Galaxy Note GT-N7000 and GT-I9220 v3.0 is a few posts down!
    N8000: Samsung Galaxy Note 10.1 GT-N8000 v5.0 is a few posts down!

    MAGURO: Samsung/Google Galaxy Nexus (GSM) Maguro/Yakju/GT-I9250
    TORO: Samsung/Google Galaxy Nexus (CDMA/LTE) Toro/Mysid/SCH-I515

    I9300: Samsung Galaxy S3 GT-I9300 and GT-I9300T and GT-I9308 v5.0 is a few posts down!
    I747: AT&T Galaxy S3 SGH-I747 and Canadia Galaxy S3 SGH-I747M
    T999: T-Mobile US Galaxy S3 SGH-T999
    L710: Sprint/C-Spire Galaxy S3 SPH/SCH-L710
    R530: USCC/MetroPCS/Cricket Galaxy S3 SCH-R530/U/M/C
    I535: VZW Galaxy S3 SCH-I535 (requires unlocked bootloader)

    P1000: Samsung Galaxy Tab 7" GT-P1000
    P7500: Samsung Galaxy Tab 10.1" GT-P7500
    P7510: Samsung Galaxy Tab 10.1" Wi-Fi GT-P7510

    P6200: Samsung Galaxy Tab 7.0 Plus GT-P6200 and Wi-Fi GT-P6210
    P6800: Samsung Galaxy Tab 7.7" GT-P6800 and Wi-Fi GT-P6810

    P31xx: Samsung Galaxy Tab 2 7" GT-P3100 and Wi-Fi GT-P3110/P3113
    P51xx: Samsung Galaxy Tab 2 10" GT-P5100 and Wi-Fi GT-P5110/P5113
    176
    Getting your device supported

    The list of devices currently supported by Mobile ODIN is rather short. Not all devices are created equal, and devices need some work to be supported. Currently I am only considering Samsung devices for future support.

    At the minimum, I will need some information from you about your device to figure out the partitions, their layout, and how to flash them. You can gather this information by downloading and installing the app. If your device is not supported, it will offer to make a dump file for you. This will take a while. Post the dump file in this thread.

    If you can find a .PIT or .OPS file for your device, please attach it !

    If the device has an integrated kernel+recovery, an image running CWM5 or 6 is welcome. If separate kernel and recovery partitions are used, I generally need an original recovery.img

    If you are lucky, this will allow me to make your device compatible. It may be required that you do some rather lengthy and extensive testing for me.

    Force device detection (v3.80 and newer)

    For compatibility testing, it is possible to force Mobile ODIN to detect your device as a different device, by executing the following command in adb shell:

    Code:
    am start -a android.intent.action.MAIN -n eu.chainfire.mobileodin.VERSION/eu.chainfire.mobileodin.core.MainActivity --es forcemodel MODEL

    Where VERSION is either lite or pro (depending on what you have installed), and MODEL is the device model identifier.

    For example, if I were using Mobile ODIN Pro and wanted my device to be detected as an international Note 3 (SM-N9005):

    Code:
    am start -a android.intent.action.MAIN -n eu.chainfire.mobileodin.pro/eu.chainfire.mobileodin.core.MainActivity --es forcemodel SM-N9005

    Note that this is dangerous and you should know what you are doing before attempting this. You might brick your device.

    Before reporting success, please make sure you succeeded in flashing an entire stock ROM, including modems!
    155
    Changelogs

    01.05.2014 - v4.20
    - Updated: SuperSU v1.94
    - Updated: Support for:
    --- Samsung Galaxy S5
    ----- International SM-G900F
    ----- Oceania SM-G900I
    ----- Korea SM-G900L
    ----- Middle and South America SM-G900M
    ----- Sprint SM-G900P
    ----- US Cellular SM-G900R4
    ----- T-Mobile US SM-G900T
    ----- Metro PCS SM-G900T1
    ----- Canadia SM-G900W8

    22.03.2014 - v4.10
    - Updated: SuperSU v1.93
    - Fixed: Data Wipe causing recursive 0 folders in internal storage
    - Updated: Support for:
    --- Samsung Galaxy S4 Qualcomm LTE
    ----- Sprint SPH-L720 - 4.4 (v7)
    ----- T-Mobile SGH-M919 - 4.4 (v7)
    ----- US Cellular SCH-R970 - 4.4 (v7)
    ----- Canadia SGH-I337M - 4.4 (v7)
    --- Samsung Galaxy Note3 Qualcomm LTE
    ----- Sprint SM-N900P - 4.4 (v7)
    ----- T-Mobile SM-N900T - 4.4 (v7)
    ----- US Cellular SM-N900R4 - 4.4 (v7)
    ----- Canadia SM-N900W8 - 4.4 (v7)

    16.01.2013 - v4.00 - RELEASE NOTES
    - Updated: SuperSU v1.89
    - Updated: SD card path and filesystem resolution
    - Added: Option to boot to download mode after flash (for bootloader update)
    - Added and Updated: Support for:
    --- Samsung Galaxy S4 Qualcomm LTE
    ----- International GT-I9505 - 4.4 (v7)
    ----- Sprint SPH-L720 - 4.3 (v6)
    ----- T-Mobile SGH-M919 - 4.3 (v6)
    ----- US Cellular SCH-R970 - 4.3 (v6)
    ----- Canadia SGH-I337M - 4.3 (v6)
    --- Samsung Galaxy Note3 Qualcomm LTE
    ----- International SM-N9005 - 4.4 (v7)
    ----- Sprint SM-N900P - 4.3 (v6)
    ----- T-Mobile SM-N900T - 4.3 (v6)
    ----- US Cellular SM-N900R4 - 4.3 (v6)
    ----- Canadia SM-N900W8 - 4.3 (v6)

    04.11.2013 - v3.85
    - Fixed SGS4 I9505 on Android 4.3 issues (new flashkernel!)
    - Fixed CSC issue with >2gb firmwares

    03.11.2013 - v3.80
    - Updated: SuperSU v1.65
    - Updated: Root installation for 4.3+
    - Added: Support for:
    --- Samsung Galaxy Note 3 International SM-N9005

    19.06.2013 - v3.76
    - Fixed: Files from internal SD would not flash on Android 4.2+ devices

    19.06.2013 - v3.75
    - Updated: SuperSU v1.34
    - Various fixes for partitions >2GB
    - Removed format() command warning for non-brickbug devices
    - Not showing some warnings when they aren't relevant
    - Added: Support for:
    --- Samsung Galaxy Note 10.1" LTE GT-N8020
    --- Samsung Galaxy Note 8.0" GT-N5100
    --- Samsung Galaxy Note 8.0" Wi-Fi GT-N5110/N5113
    --- Samsung Galaxy Note 8.0" LTE GT-N5120
    --- Samsung Galaxy S4 Qualcomm LTE
    ----- International GT-I9505
    ----- Sprint SPH-L720
    ----- T-Mobile SGH-M919
    ----- US Cellular SCH-R970
    ----- Canadia SGH-I337M

    23.02.2013 - v3.65
    - Updated: SuperSU v1.10
    - Updated: FlashKernels:
    --- SGS2/I9100: exFAT support
    --- SGN/N7000: exFAT support
    --- SGS3/I9300: SDS patch
    - Added: Support for:
    --- Verizon Galaxy Note 2 SCH-I605 (unlock bootloader !)
    --- Virgin Mobile Epic 4G Touch SPH-D710VMUB
    --- Boost Mobile Epic 4G Touch SPH-D710BST
    --- C-Spire Galaxy S3 SCH-L710
    --- MetroPCS Galaxy S3 SCH-R530M
    --- Cricket Galaxy S3 SCH-R530C

    13.11.2012 - v3.57
    - Fixed: SD card resolution with multiple symlinks
    - Fixed: Issue with fingerprint detection disabling when flashing OTA ZIPs

    13.11.2012 - v3.56
    - Fixed: Several crashes
    - Fixed: External SD filesystem detection

    11.11.2012 - v3.55
    - Added: ACRA crash reporting
    - Added: Generic filesystem warnings if storage's filesystem is unsupported
    - Fixed: exFAT support on S3, Note2 and Note10.1 (new flashkernels)
    - Fixed: Native code performance
    - Fixed: Flicker when AROMA installer is used
    - Added: Support for:
    --- AT&T/Canada Galaxy Note 2 SGH-I317/M
    --- TMOUS Galaxy Note 2 SGH-T889
    --- Sprint Galaxy Note 2 SPH-L900
    --- US Cellular Galaxy Note 2 SCH-R950

    01.11.2012 - v3.50
    - Updated: SuperSU v0.97
    - Updated: Roboto font is now used during flash
    - Fixed: (Pro): Flashcounter no longer triggered on S3, Note2 and Note10.1. But breaks exFAT support! (new flashkernels)
    - Added: Warning when somebody selects an exFAT card
    - Added: Wipe functionality is now available without having to flash anything
    - Added: Support for:
    --- Samsung Galaxy S3 LTE GT-I9305T
    --- Samsung Galaxy S3 LTE GT-I9305N

    15.10.2012 - v3.45
    - Added: Support for:
    --- Samsung Galaxy S3 LTE GT-I9305
    --- Samsung Galaxy Note 2 LTE GT-N7105

    05.10.2012 - v3.40
    - Added: Support for:
    --- Samsung Galaxy S3 LTE SHV-E210S
    --- Samsung Galaxy Note 2 GT-N7100

    02.10.2012 - v3.35
    - Fixed: issue related to cache / csc

    08.09.2012 - v3.30
    - Fixed: issue flashing cache partition, could corrupt entire flash

    31.08.2012 - v3.25
    - Updated: SuperSU v0.96
    - Fixed: Jelly Bean Mobile ODIN injection with multiple versions installed
    - Added: SuperSU Pro is now also injected if installed
    - Added: (experimental, selective, partial) Update ZIP and OTA flashing (Pro version only) to most devices. Might sound like a minor change, but this is the single largest code update yet!
    - Added: Option to extract ZIP files containing partitions
    - Added: Support for:
    --- Samsung Galaxy Tab 7.0 Plus GT-P6200L

    24.08.2012 - v3.10
    - Updated: SuperSU v0.95
    - JellyBean-related bugfixes
    - Added: Support for:
    --- US Cellular Galaxy S3 SCH-R530
    --- VZW Galaxy S3 SCH-I535 (unlock bootloader !)
    --- Samsung Galaxy Note GT-N7000B
    --- Samsung Galaxy Note 10.1" GT-N8000
    --- Samsung Galaxy Note 10.1" Wi-Fi GT-N8010/N8013

    09.07.2012 - v3.00
    - Updated: SuperSU v0.93
    - Fixed: Wipe data/cache issue
    - Added: Unreadable file warning
    - Added: Support for:
    --- Samsung Galaxy S3 GT-I9300T
    --- Samsung Galaxy S3 GT-I9308
    --- AT&T Galaxy S3 SGH-I747
    --- Canadia Galaxy S3 SGH-I747M
    --- TMOUS Galaxy S3 SGH-I999
    --- Sprint Galaxy S3 SPH-L710
    --- Samsung Galaxy Tab 10.1" GT-P7500
    --- Samsung Galaxy Tab 10.1" Wi-Fi GT-P7510
    --- Samsung Galaxy Tab 2 7" GT-P3100
    --- Samsung Galaxy Tab 2 7" Wi-Fi GT-P3110/P3113
    --- Samsung Galaxy Tab 2 10" GT-P5100
    --- Samsung Galaxy Tab 2 10" Wi-Fi GT-P5110/P5113

    07.06.2012 - v2.45
    - Fixed: exFAT Ext.SD support (SGS3, v3 flashkernel)
    - Fixed: ext2/3/4 Ext.SD support (various models)
    - Fixed: Wipe again wipes cache as well
    - Fixed: Recovery now flashes directly
    - Added: Support for:
    --- Samsung Galaxy S2 SCH-R760 (US Cellular)

    31.05.2012 - v2.40
    - Fixed: GooGle Play
    - Fixed: Mounting issue
    - Fixed: Wipe now skips /data/media
    - Added: Developer option warning
    - Added: Support for:
    --- Samsung Galaxy S2 GT-I9100M
    --- Samsung Galaxy S3 GT-I9300

    08.05.2012 - v2.36
    - Added: Wipe dalvik cache option (Pro only)
    - Added: ICS look
    - Fixed: ICS threading issue
    - Updated: SuperSU v0.89
    - Added: Support for:
    --- Samsung Galaxy S2 SHW-M250K
    --- Samsung Galaxy S2 SC-02C

    14.03.2012 - v2.30
    - CWM Manager injection option removed
    - SuperSU updated to v0.80

    10.03.2012 - v2.25
    - Added supports-screens manifest tags
    - Removed menu button visibility on ICS
    - EverRoot now uses SuperSU v0.75 or newer

    09.02.2012 - v2.15
    - Fixed: Cache/CSC sync issue
    - Added: Support for:
    --- Samsung Galaxy S GT-I9003L
    --- Samsung Galaxy S2 GT-I9100G

    07.02.2012 - v2.10
    - Modified: Default install to device memory
    - Added: Support for:
    --- Samsung Galaxy Tab 7.0 Plus GT-P6200
    --- Samsung Galaxy Tab 7.0 Plus Wi-Fi GT-P6210

    06.02.2012 - v2.00
    - Fixed: Problems with dump log
    - Fixed: Clear button sometimes not present
    - Fixed: BML flash freeze issue
    - Added: Visual progress
    - Added: Support for split kernel/recovery devices
    - Added: Support for sd-ext
    - Added: Option to wipe data after flash
    - Added: Internal wildcard support
    - Added: Support for:
    --- Samsung/Google Galaxy Nexus (GSM) Maguro/Yakju/GT-I9250
    --- Samsung/Google Galaxy Nexus (CDMA/LTE) Toro/Mysid/SCH-I515 (no cdma radio flashing)
    --- Samsung Galaxy Tab 7.7" GT-P6800
    --- Samsung Galaxy Tab 7.7" Wi-Fi GT-P6810
    --- Samsung Galaxy S2 SHW-M250S (Korean)
    --- Samsung Galaxy Note GT-I9220
    --- Samsung Galaxy 5 GT-I5500
    --- Samsung Galaxy 5 GT-I5500B
    --- Samsung Galaxy 5 GT-I5500L
    --- Samsung Galaxy 5 GT-I5500T
    --- Samsung Galaxy 5 GT-I5500M
    --- Samsung Galaxy 5 GT-I5503
    --- Samsung Galaxy 5 GT-I5503T
    --- Samsung Galaxy 5 GT-I5508
    - Modified: MobileODIN v2 flashkernels for:
    --- Samsung Galaxy S GT-I9000
    --- Samsung Galaxy Tab GT-P1000
    --- Samsung Galaxy S2 GT-I9100
    --- Samsung Galaxy S2 GT-I9100T
    --- Samsung Galaxy Note GT-N7000

    16.01.2012 - v1.30
    - Fixed: Theme
    - Fixed: Strange characters in file paths
    - Added: Additional file accessability checks
    - EverRoot: Fixed some situations where it failed
    - EverRoot: Storage warnings added
    - FlashKernel: Backed up to SD card instead of /system
    - Dump: Various partition information added

    30.11.2011 - v1.25
    - Fixed nasty flash bug (could corrupt files and cause bootloop). If you've had this problem, please make sure to delete the firmware files from your SD card, and put fresh copies on it from your PC.

    28.11.2011 - v1.20
    - Added support for:
    --- Samsung Galaxy S GT-I9003
    --- Samsung Galaxy S GT-I9000B
    --- Samsung Galaxy S GT-I9000M
    --- Samsung Galaxy S2 GT-I9100T
    --- Rogers Captivate SGH-I896
    --- AT&T Captivate SGH-I897
    --- AT&T Galaxy S2 SGH-I777
    --- Sprint Epic 4G Touch SPH-D710
    - Dump: added env info
    - Dump: added mtdblock info
    - Targetfile now checked for existance before partition wipe
    - Mounter script integrated into flash script
    - ROM Manager API used when needed
    - Added support for reading .exe files (Odin3Excution one-click, MD5 skipped)
    - CWM Manager inject option hidden if not available
    - FlashKernel is now always used if available
    - FlashKernels removed from Market.
    --- (Lite) link to XDA thread
    --- (Pro) automatic download
    - Unexpected partition detection (CM/MIUI)
    - Additional partition aliases added

    16.11.2011 - v1.10
    - Added support for: Samsung Galaxy S GT-I9000
    - Added support for: Samsung Galaxy Tab 7" GT-P1000
    - Fix compatibility issue with CyanogenMod

    15.11.2011 - v1.00
    - Initial release