• 5,808,347
  • 38,479

Posts Tagged: odin


The kernel files have been released for the Android 4.4 KitKat update on the Samsung Galaxy Note 3! That and much more news is covered by Jordan, as he reviews all the important stories from this weekend. Included in this week’s news is the announcement that the full Smart Social Camera Experience has been ported to Android 4.3 Xperia Devices and Mobile ODIN has been updated with more features and support for more devices!

Be sure to check out the the other videos released this last week on XDA Developer TV. XDA Developer TV Producer TK released an Xposed Tuesday video for Root Cloak, he then reviewed the Omate TrueSmart smartwatch 2.0, and finally he gave us an Android App Review of Calendar Status. Pull up a chair and check out this video.



We first featured XDA Senior Recognized Developer Chainfire‘s Mobile ODIN app a little over two years ago. Ever since the beginning, Mobile ODIN has allowed users to flash ODIN-flashable firmwares directly from the device itself, without the need to connect to a full computer.

Over the course of the app’s various updates, Mobile ODIN has evolved considerably—both adding support for new devices, as well as gaining new abilities. Now with an update to version 4, the app has gained even more abilities, as well as compatibility with a few more devices.

The most notable feature new to version 4 relates to its ability to flash modem images. As these partitions are protected, flashing may be temperamental on certain devices. To protect against this, new code was added to detect the protection, and if enabled, skip flashing the affected partition. That said, it’s still possible to flash complete firmwares and modems via Mobile ODIN. Just now, it takes a safer approach by checking for protections that could cause issues.

Another new feature unique to version 4 is its ability to automatically reboot your phone into download mode following a Mobile ODIN flash. This is useful in case you wish to flash bootloaders, trustzone, and other partitions that are not flashed via Mobile ODIN. Using this, you can flash an Android update while preserving root thanks to EverRoot, automatically boot to download, and flash the specific partitions that were skipped.

The built-in version of SuperSU was updated to 1.89, which was created to support the latest Samsung Android 4.4 firmwares. And finally, this update brings support for various variants of the Galaxy S 4 and Galaxy Note 3.

Head over to the Mobile ODIN thread and Chainfire’s Google+ announcement to get started.


Odin and Heimdall were pretty badass gods in the Nordic mythology. But to Samsung device owners, these are important and powerful tools designed to flash stock ROM files, much like Flashtool on Sony phones. In short, they are an essential part of Samsung Android development here at XDA.

Many times in the past, we’ve talked about XDA Senior Recognized Developer AdamOutler‘s CASUAL, otherwise known as Cross-platform Android Scripting Unified Auxiliary Loader.  The cross-platform Java-based tool allows you to perform many cool tasks like rooting, flashing stock ROMs. and so on.

The project is now on a different level, as Adam has presented JOdin3, a web browser-based and offline flashing tool. With JOdin3, you are able to flash stock Samsung firmware directly from your browser. The project is a collaboration of between Adam and XDA Senior Developers Benjamin Dobell and Ralekdev, and XDA Senior Members Loglud and jrloper.

You need to have Java installed on your PC in order to use JOdin3. Heimdall is also required, but it will be automatically downloaded and installed. As it’s a cross-platform tool, it works flawlessly on Windows, Mac, and Linux.

More information regarding this project can be found in the original thread. You can read more about CASUAL on the official website of the project.

[Thanks to XDA Recognized Contributor benkxda for the tip!]

nature UX

Well, it’s been a long time coming. But after a whole load of nay-saying, conjecture, and incessant optimism, Samsung Galaxy S II owners can finally grab hold of a leaked Samsung test build of Android 4.1.

Although Jelly Bean has been available for the Galaxy S II for some time now, there’s been no sign of a version from Samsung. But thanks to XDA Forum Member izap, build XXLSJ based on Android 4.1.2 is now available to download. The build features the latest version of TouchWiz known as Nature UX, which will give your Galaxy S II something of an S III look and feel. And to quote one user – “It’s freaking smoooooooooooth…”

So far the general feedback seems to be quite positive, and it looks like the i9100 is handling the transition to an official version of Jellybean quite well. You’ll need to be familiar with Odin to flash this latest build, as there’s currently no flashable .zip available. If you’re not familiar with Odin, I’d strongly suggest you read up first to save yourself from running into trouble further down the line.

If you want to take this build for a spin, check out the original forum thread for the details and those all important download links.


Finally we got to the third and final part of this interesting interview:
If you missed previous parts, you can find them in here for Pt. 1, and here for Pt. 2

orb3000: What would you recommend to anyone interested in entering the
high-level hardware mod world?

AdamOutler: I would recommend getting a hold of some tools and hardware, get
on google and do it!

I’d choose the standard $60 Radio Shack temperature controlled soldering
iron, some breadboards, leds, 1kohm resistors, and a microcontroller. Any
open-hardware development board will teach you how to work with inputs and
outputs. One of my favorite development boards is the Arduino series. Some people may say, “hey, Arduino is not real hardware development, it’s too easy…BlaBlaBla… Whatever, they’re cheap and
work well. let me ask you, if you’re trying to prototype or learn
something, should it be easy or convoluted?. I’ve managed to make several
devices which solve real-world problems using my Arduinos including EMF
detection for locating a source of interference at work and UART processing
for developing Unbrickable Mod.

To really get into digital communications, you’ll want some additional tools
like the Bus Pirate. The Bus Pirate is a universal serial interface used to
communicate with just about anything at low speeds. It’s open-hardware and
known as The Hacker’s Multi-tool.

For troubleshooting and circuit identification, you’ll want something like
the Logic Sniffer. It can record digital highs and lows then display them on your desktop screen where you can run filters and detect logical patterns.

While I’m at it… I don’t think I can hammer this point enough; Use
With Open-Hardware(like OMAP44xx) you can get all the information you need.
With proprietary hardware (like Qualcrapp processors) you have nothing to
work with.

orb3000: Why is your adamoutler.com main site generally down?

AdamOutler: My main webserver is a Texas Instruments EvalBot.
This is a Texas Instruments Development Board with an ARMv3 processor. Its
form-factor is designed to roll around the floor, bounce off walls, turn 90
degrees and keep going. For some reason it came with an Ethernet port, so I
re purposed the device to serve web pages. It does not do a very good job
and it locks up all the time. I could probably use a real web-server instead
of a development board on wheels.

orb3000: Finally, please tell us a bit of the Adam outside the hardware world, what do you do for a living? What is your current device?

AdamOutler: Heh, the funny thing is that what I do for a living is in the
hardware world… I’m an electronics tech. I have been working in
electronics for 13 years. In 1999, I joined the Army as a Radar Repairer
and my job was to keep multi-million dollar Artillery, Rocket and Missile
Radars operational at all costs. I changed jobs to be a Biomedical
Equipment Technician after working with Radars in Iraq.

I’m currently in the Civil Service, but I’m still performing Inspection, PM,
calibration, and rebuilding medical equipment (like infusion pumps, x-rays
and ultrasounds) in a hospital as my daily job. Being a biomed and keeping
things in-line with regulations is a stark contrast to modifying radars.
When I’m at work, non-manufacturer authorized modifications can kill
someone. When I get home and work on mobile devices, I can kinda “let
loose”. The worst that can happen with mobile devices is it breaks. At
work, I could face much worse. :)

My current daily phone is an Infuse 4G. My current Dev phone is a Samsung Captivate. My current development tablet is Nook Tablet.

orb3000: Thanks a lot for your time, any final comments you want to make?

AdamOutler: Yes. Since this will be on the XDA Portal and many
manufacturers will see this..

I believe Google chose OMAP4460 because it is the only truly open-hardware
processor available. Open-Hardware means device manufacturers can be
self-sufficient and modders can get the information they need.
Closed-Hardware means it has a relatively short life-cycle.

Samsung: Your Exynos 4210 processor without datasheets is now obsolete
because you chose to keep 1/2 of the datasheets private. I don’t know of a
single person who, with any sort of planning, would say “hey, I want that
processor because of ${Maintainability, Ease of use, Cost Effectiveness}”
All of these qualities are missing when you lock down your datasheets.

Qualcomm: Is there any benefeit to using a Qualcomm processor? Can you
prove it? As far as I can tell, they’re the Celerons of the ARM world.
About the only benefeit to using a Qualcomm processor is integral call
processor. However if the device manufacturers actually cared about the
device and its ability to work through upgrades they would never use
Qualcomm. Here’s a factoid, Qualcomm does not even let the manufacturers
have access to bootloaders. You do realize that the only reason people are
using your chips in their devices is because they think you might know
something they can learn from right?

NVidia: Sure TEGRA extensions are great, but we can’t program them into the
latest versions of Android without knowledge of how they work. You’ve closed
your hardware and thereby stifled development.

Texas Instruments: Good Job! Other processor manufacturers take note. Texas
Instruments is on the rise in the ARM industry because of decisions made by
all other processor manufacturers. We need more Open-Hardware to work with.

BTW… If anyone has access to Samsung Exynos 4210 Chapter 19, entitled
“Boot Sequence” or similar, I need it. The manual I have stops at Chapter

Thats a lot of knowledge!. Hope you all have enjoyed the interview, if so please share it, want someone to be interviewed? Let us know!
Thanks for reading.


Welcome to the second part of the interview with Recognized Developer AdamOutler:
Here you can find the first part in case you missed it.

orb3000: We know you have the longest bash script ever written, what is made for exactly?

AdamOutler: Mythical Librarian was a
project I created over the course of 6 months. At the time, my daughter was
3, could not read and liked TV Shows like Dora the Explorer, Sesame Street
and others. I found a way to make it so she could point to the show she
wanted to watch, with proper naming convention, XBMC could assign pictures
to each episode and she could select which TV Show she wanted to watch. The
idea behind this project was to automate the process of recording a video,
looking up the season and episode numbers, then renaming. Sounds simple

I began with BASHSEXX(Bash SeasonXX, EpisodeXX). It evolved to support
MythTV’s database and was renamed MythSEXX. Eventually it got a small
following, people started reporting bugs, the script was supporting a large
number of functions and databases and was “thinking” on its own, so it was
renamed mythicalLibrarian.

Long story short, it takes a recording, references an online database,
parses, creates a local textual database, looks TVShows up based on
SeriesID, Original Airdate, Show Title and Episode Title, utilizes standard
and fuzzy logic, grades its performance, makes decisions if its going to
redo the lookup at a later time, maintains filesystem symlinks and manages
metadata. It talks to GNOME desktop, XBMC and MythTV. mythicalLibrarian
generates RSS feeds upon each action via Apache web server.
mythicalLibrarian also has the ability to update itself from the latest SVN
or Stable version.

The end result is the user can use XBMC as a better front-end for MythTV.
XBMC uses mythicalLibrarian to get information which downloads cover-art,
fan-art, episode-art, and displays detailed information about the episode,
while MythTV handles disk-space issues and recording.

I believe it’s main portion is now the longest BASH script in existence.

orb3000: Regarding your current projects such as Unsecure boot on the Nook Tablet, running Ubuntu on Nook tablet, Exynos4120 UnBrickable Mod, what is the actual status and what users can expect from those amazing tools?

AdamOutler: While I did put in a lot of research into Unsecure Boot on the
Nook Tablet and even prototyped Nook Tablet ModChips, XDA Junior Member
Bauwks came up with a total software solution. This solution is now the
defacto standard used in all custom Nook Table booting including Ubuntu.

As for Ubuntu booting, there is considerable work going into a Nook Tablet
3.0 Kernel. This is required for proper operation of Ubuntu. The older 2.6
kernel will boot Ubuntu just fine, but there are problems which cannot be
corrected without proper underlying datastructures. The Ubuntu Recovery
system I came up with works well and will recover a dead Nook Tablet from
any known cause of bricking. I will continue this project as soon as I get my hands on a 3.0 kernel.

The Exynos4210 UnBrickable Mod is complete. We are now researching firmware
solutions. I have worked with Rebellos via Internet and it would appear
that the most logical solution would be to simply send it to him. He will
attempt to write new bootloaders and make GS2 UnBrickable Mod a reality.
Believe me, I want this badly as I receive several PMs per week asking about
the status of GS2 UBM.

orb3000: You have opened a thread called Do you want to help out
developers? Got a broken device?
How the project is going, and what would
you like to ask/advice the donors?. We would like to take this opportunity
to remind everyone participating to help us to keep thread clean.

AdamOutler: A broken device may be something most people throw away.
However, to myself and others, they are research tools.
I stated devices in which I am interested at the top of the thread. Many members have posted
other devices which they are willing to part with. I would like to
encourage other developers and hardware hackers to take advantage of this
and use it as a resource for their projects.

Expect the third and last part soon. Thanks for reading.


Finally we are back on the XDA Interview series! For those of you too new to XDA, you may find the previous ones in this links: Interview With XDA Developer pof, Interview with User Experience Admin svetius, Interview with XDA forum Admin mikechannon, etc.

This time we will talk with XDA Recognized Developer AdamOutler. It´s hard to find where to start when you have the pleasure to interview such a versatile Developer with so many active projects.

orb3000: Hi Adam, thanks for taking this time to talk. I will start asking how do you started to work in Unbrickable Mod?

AdamOutler: When I switched from iPhone to Android, I had a feeling of
immense freedom. I could do anything I want with an Android! So I did…
I did something and bricked my phone within about 1 hour of owning it.

I searched for ways to recover bricks and JTAG was the only option for my
device. It required soldering 8 tiny wires and purchasing a very expensive
box. I felt that was unacceptable and there should be another way to reload
firmware so I began research and was pulled into the thread Lets save some
. After locating the hardware modification, I called it UnBrickable Mod because I
knew it had potential to make a device totally UnBrickable.

Cool factoid: The B in UnBrickable is always capitalized because it bypasses
Auto-Correct on Android devices.

orb3000: How Unbrickable Mod works?, can you explain us what is all about?

AdamOutler: That is a very broad question… UnBrickable Mod is a hardware
modification which enables USB upload of bootloaders. I think everyone
wants the reassurance that no matter what they flash on their device it can
be recovered. All CORTEX A8 processors have the ability to boot from USB.
Most modern devices support this and at the same time, most manufacturers
tend to lock this ability down. While UnBrickable Mod is technically a
hardware hack/exploit, it functions to increase device maintainability and
thereby increases device value. Personally, I view UnBrickable Mod as the
way devices should come from the factory.

Here’s a video which explains most of it.

(Note to readers, ignore this paragraph if you’re not a geek) While most
devices have a default failover mode to boot from USB, this is ineffective
if the device locks up on a bootloader. Each device has its own unique boot
mode. Most GalaxyS1 devices use a boot code of 0x9(OneNAND>UART>USB). By
modifying the value from 0x9 to 0x29(UART>USB>OneNAND), the device will
reverse its boot order and thereby cause the device to swap its boot mode
from the default boot first from OneNAND to booting first from UART, then
USB, then OneNAND. It’s not always the same value we’re searching for
though.. Each device has its own unique configuration and processor. A
booting code of 0x9 on a Hummingbird processor does not mean the same on any
other processor, nor is it guaranteed that the boot modes can be swapped,
also memory locations are different per processor.

For example, I’ve just finished locating the modification required on the
Exynos4120 GalaxyS2. As far as I can tell, it will not be possible to
simply swap the boot modes. On the Exynos4120, a temporary connection must
be made in order to make the device attempt to boot from an alternate source
and failover into the USB mode. I chose a switch to make this temporary
connection. See XDA-TV GalaxyS2 Unboxing for more.

orb3000: For a regular user sometimes so many tools is kind of confusing, please tell us about the supporting software like UnBrickable Resurrector, ModeDetect, and Heimdall One-Click?

AdamOutler: These tools each serve different purposes. Lets start with
Heimdall One-Click


Heimdall One-Click is a cross-platform, all-dependencies-included, single
executable file, firmware packaging and distribution tool. It is superior
to the Windows-only Odin3. Its purpose is to allow users on Linux, Windows
and Mac to use the exact same file to flash firmware onto their device. The
advantages of using Heimdall One-Click over Odin3:
*Utilzing a much safer flashing method
*Allowing those with Windows, Mac and Linux to flash your firmware
*Increasing user-awareness of what is being flashed
*Packing your firmware into a much easier to use One-Click
*Supporting the work of other Open-Source developers

Heimdall One-Click is based on Heimdall by Benjamin Dobell. Heimdall is
actually safer to use than Odin, and Heimdall One-Click adds 6 points of
safety to standard flashing with Odin. I’ve also created a tool to make
Heimdall One-Clicks from Heimdall Tar.GZ packages.


The UnBrickable Resurrector is the firmware/software component to
UnBrickable Mod.


The UnBrickable Resurrector will tell you when you’ve connected a device
which has been properly modified. It also can recognize several other modes
like ADB, Media Player, Mass Storage and many others. By connecting an
UnBrickable Modded device and clicking the “Download Mode” button, you’re
activating a process of uploading customized bootloaders directly into
specific memory locations where they are executed and perform initialization
tasks designed to put your device into Download Mode or Fastboot Mode. The
Resurrector was created as a team effort by Rebellos and Myself.

I designed the high-level Java app and hardware mod while he designed the
HIBL(Hummingbird Interceptor BootLoader) and modified SBL.

ModeDetect was discontinued. It has been replaced and absorbed by the
UnBrickable Resurrector.

Basically, we’ve got Heimdall One-Click which makes loading software easy
and the UnBrickable Resurrector which gets you to the point where you can
load software. The reason for having them be totally separate entities:
Not everyone needs or can use the Resurrector and not everyone needs or can
use Heimdall One-Click. Although they work together to form a total
recovery system, they are separate in that developers may not need a full
300meg firmware flash to put their device into download mode and test a
kernel, and people flashing firmware would be confused by inoperative
buttons and extra status icons.

In short, UnBrickable Resurrector supports several devices and provides
hard-brick recovery to a soft-bricked state. Heimdall One-Click provides
soft-brick recovery to an operational state.

This brings me to my work-in-progress… Why don’t we have any
cross-platform tools which work with every single Android device out there?

CASUAL (Cross-platform ADB Scripting, Unified Android Loader), like the Unbrickable resurrector, will support several devices. Since it only requires 6 commands, it is intended to be an easy-to-learn, Cross-Platform, light-weight scripting language for deploying binaries over ADB with a Graphical User Interface. If you’re a developer who wants to deploy a new root script over ADB, put out a kernel for multiple devices or install applications via adb, CASUAL will be your
application of choice. It works on Linux, Windows and Mac. A basic script can be created by simply putting all of your binaries into a zip file then typing in a few adb commands without the word “adb” and replace file
references with $ZIPFILEfilename.ext. For example:
Shell mkdir /data/tmp
push $ZIPFILEzergRush /data/tmp
shell /data/temp/zergRush
push $ZIPFILEzergRush /system/bin

The end-user of a CASUAL application will not see the script. They will see
a GUI. User will simply plug in their Android Debug Bridge enabled device,
select the operation from a drop-down box, then click the big button. It
will also provide a great way to easily root an Android Virtual Device from
Linux as well. CASUAL will support every single Operating System and every
single Android Device.

Here we end the first part of the interview, stay tuned for the following two parts.
Thanks for reading.


Two years ago, who would’ve thought we’d be covering actual tablet development? In that time, we were astonished by the screen size of the HTC Touch HD – 3.7 inch almost seemed too big for our pockets. And see where we landed now: the tablet and smartphone industries are slowly blending together, especially thanks to Dell’s Streak and Samsung’s Galaxy Note. It is incredible to see how these industries change so rapidly. Fortunately, development is more active than ever before, and even tablets are supported on XDA now.

Samsung’s Galaxy Tab 7.7 is their latest addition to the tablet range. Thanks to Chainfire’s efforts to include Galaxy Tab 7.7 support in his Mobile ODIN utility and the successful rooting development, the seven-point-seven will probably receive its very first custom ROM pretty soon. Android Ice Cream Sandwich (4.0) is probably not far from being displayed on a Super-AMOLED Plus tablet display for its very first time – for the Galaxy Tab 7.7 is the only tablet with that screen technology at this moment.

Follow the discussions to stay updated – and you might want to check out the ICS AOSP Build thread to see how the Ice Cream Sandwich development is evolving.


The proverbial train that is CyanogenMod9 keeps on a rollin’ today as it hits another device. This time, it happens to be the Samsung Galaxy Note.

The giant phone gets its giant update to one of the most giant ROMs in the history of ROM making courtesy to XDA member Maui, who’s been kind enough to compile it for everyone toting the super sized phone.

As expected, it is an alpha build and there are some issues. They include:

Bluetooth is unstable. Don’t rely on it just yet
Battery Usage doesn’t work.
MTP Mode does not work. You need to push/pull files via adb
Camera doesn’t work. Will be that way until we can get our hands on a ICS leak for the Galaxy Note

Unlike most CM builds, it is noteworthy to notice that this particular build is flashed via Odin as opposed to ClockworkMod Recovery and if you want the Gapps, then you’ll need to push them via ADB. So if you’re uncomfortable with ADB and need your dose of Gapps, then it’s recommended to get instructions on how to flash Gapps before attempting to flash the ROM. Otherwise you could end up a very unhappy camper (with no Gapps *sadface*) Also, as with any experimental or unstable builds, there’s always the potential for permanent phone damage. Also, as Maui will tell you:

Flashing this rom WILL increase your binary counter and may/will void your warranty.

If that’s something that you happen to not be so worried about, then you can sate your CM9 cravings, grab instructions, download links and screenshots in the original thread.


Chainfire’s abilities know no bounds.  The XDA Moderator and Recognized Developer now presents Mobile ODIN, allowing you to flash firmware from your device, itself.  That’s right, you no longer need to connect your device to your computer.

All right, that’s not perfectly true–Mobile ODIN currently cannot flash PIT, bootloader, or EFS partitions.  You still need your computer for those.  For now.  But if you want to flash a new kernel, system, DBData, data, cache, parameter, or modem partition, Mobile ODIN can do that.  As the developer says,

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.

Mobile ODIN Lite is exclusively available on XDA.  You can find the pro version on the Android Market.  Now, Mobile ODIN Pro has a few extra perks that the regular, old ODIN doesn’t have.  For example, Chainfire includes EverRoot–an option that roots your ROM as you flash it.  With that, you can also automatically flash Superuser, and Mobile ODIN itself, so you’re all ready to flash again when you reboot your new ROM.

Not every device is compatible.  But Chainfire made eight new devices compatible in the second update, and he says he’s willing to work with Samsung phones.  If you install the app on an incompatible device, the app will let you create a dump file, which you can post in the app’s thread.  If you can, also post a PIT file for your device.  Lastly, the developer says, he needs a kernel running ClockworkMod5, though it might work with CWM3 or 4.

To see if your device is compatible–or if there are plans for compatibility–and try it out, please carefully read the source thread.


XDA TV: Most Recent Video

Buy/Sell on Swappa

  • Nexus 5 (Unlocked) buy | sell
  • Galaxy Note 3 (T-Mobile) buy | sell
  • HTC One M7 (Verizon) buy | sell
  • Galaxy S 5 (Unlocked) buy | sell
  • Nexus 7 2013 buy | sell
  • Swappa is the official marketplace of XDA