Chainfire is a well-known developer on XDA. He has released numerous apps that are extremely useful. One of particular interest is Mobile ODIN. As the name of the app suggests, it flashes Samsung firmware onto your device. This is extremely helpful as it is often annoying to have to rely on your computer to flash back to stock. Furthermore, some of you may experience problems due to the USB port on your computer or phone. Also, this will not trip your flash counter.
USE WITH CAUTION. I AM NOT RESPONSIBLE IF YOU BRICK YOUR DEVICE OR YOUR CAT GOES ON FIRE
This will not flash/re-partition PIT, IBL/PBL, SBL & EFS. (No need to anyways...)
To flash via Moile ODIN, you must have ROOT
As a safety precaution, you must have 80% battery power!
1. Go to Chainfire's thread for Mobile ODIN (here) and download the following files:
MobileODINLite-v3.00.apk
MobileODIN_FlashKernel_I747-v2.0.apk
[OPTIONAL] If you're feeling generous, then go do Chainfire (he deserves it!) and yourself a favor and download the paid app via the Play Market. Pro can inject root in the stock firmware prior to flashing!
Note: If you downloaded Mobile ODIN Pro, you wont need to install MobileODIN_FlashKernel_I747-v2.0.apk as it will automatically download the corresponding apk for your device.
2. Once you've downloaded and installed the two apps, go download AT&T stock firmware. As this is a huge file, download it on strong WiFi connection.
(MD5: 66c6dfae34fd06c098f07537d19943c2) <- MD5Sum of the zip file
3. Extract zip and place tar.md5 in the root of your internal sdcard.
4. Open Mobile Odin > select Open File... > I747UCALEM_I747ATTALEM_I747UCALEM_HOME.tar.md5
It will not flash the following files in tar:
aboot.mbn
sbl2.mbn
sbl3.mbn
rpm.mbn
tz.mbn
5. Check wipe data and cache & dalvik cache* and flash (select Check for MD5 sum).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Note*: While it is not necessary to wipe data and cache & dalvik cache in the app, it is suggested as to prevent boot loops.
nice guide
Pardon my ignorance, but when you say "It will not flash the following files in tar:"... are those files not needed at all or do we need to add them manually?
I don't think so as you don't need to flash boot loaders. Also, repartition is not necessary as were not using hellraised roms (yet).I am not 100% sure tho.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
tamanaco said:
Pardon my ignorance, but when you say "It will not flash the following files in tar:"... are those files not needed at all or do we need to add them manually?
Click to expand...
Click to collapse
I believe it's a "safety" feature that the dev built in, because unless absolutely necessary, you generally don't want to mess with bootloaders, as those are the few items that can seriously f up (aka "Hard" brick) a phone if it goes bad. Also, it was found that some of the latest leaks from Samsung on various devices contained some shady bootloaders that noobs were indiscriminately flashing, so again, this helps save them from themselves
Related
Hi,
We would like to make a idiot proof ROM upgrade method.
Too many people are, for example, accidentally upgrading P9000 ROM onto I9000.
That will brick a phone.
My suggesting is this.
Set phone to usb debugging mode.
Have a single tool that automatically does the following (unfortunately, only possible on a rooted phone):
1) Uses adb to backup the bml1 and bml3 boot loaders. (Might as well backup efs also and check the user has root. If a user cannot get root, they really should not be flashing their ROM in the first place. Some method to automatically check if the phone is "network locked" might help. Can you do things like *#06# from the adb command line?)
2) Do a checksum on the bml1 and bml3 backups to identify which boot loader is actually on the device, and therefore identify the device. I.e. I9000 or P9000.
3) Check the USB ID of the phone is correct.
4) Double checks that the boot loader files provided by the user are compatible.
5) Automatically use adb to switch the phone into download mode
6) Flash only a compatible bootloader.
If a new ROM is published with a new boot loader, prevent the user from using it, until developers upgrade HEIMDALL one-click to recognize the new boot loader.
Have another tool, that does similar, but that will never flash the bootloader. Instead it uses the files provided by the user to flash only the rest of the phone, and never the bootloaders.
So long as the boot loaders are not touched, even if boot loaders are in the user provided file, the user can always recover using the 301K JIG.
Another thing to consider is the PIT. Have the tool implement a feature to read the PIT from the phone and if the PIT provided by the user is the same, automatically do not re-partition.
If the PIT needs changing, only flash the PIT and with the bootloader tool (described above).
This will ensure the user can still reach Download mode, even though the user will have to flash an ROM to be able to boot the phone into Android after that. But the important bit is that the phone will not become a Brick.
Of the current PIT files, I don't think any of them wipe the BML1 and BML3 boot partitions.
They only modify the size of the system and data partitions.
The main way to make all this "safe" is to separate the "repartitioning and installing boot loaders" from the "ROM install".
"ROM install without PIT and bootloaders" is 100% safe, installing boot loaders and PIT is the risky bit, so provide a tool that does it safely.
Maybe include a good boot.bin and Sbl.bin with the safe bootloader tool.
What do people think?
I'm working with Benjamin Dobell, the developer of Heimdall. There will be several features in the first release..
The specs on the .9A release planned features are:
Open source - everyone can contribute
Java app- Cross platform, One download handles all major platforms
One Click Packaging-Developer can add in their PIT, PBL, SBL, Kernel, Modem and FactoryFS(ROM) by dropping files into the zip
Heimdall included-installed automatically for the platform the user is running
User Awareness-User must check "flash bootloader" and they must be "sure they want to do this" which will make it a 3 click operation
The 1.0 release will include more features. I'll make sure to point Benjamin to this thread.
it would be awesome to see this fly
It's good to hear that...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I cannot wait to see this! I am an Ubuntu user with Windows 7 only for Odin. Would love to have a reason not to use Windows.....ever.
Sent from my SAMSUNG-SGH-I897 using XDA App
As somewhat of a trial run, I branched this project into "One-Click UnBrick". This installs heimdall and will execute the close-pc-screen command. I am still working on it. The main problem is Win7 drivers. Distributing them in a one-click manner is tough. I've already worked around win7 UAC, registry, filesystem issues, and VC++ issues. The last problem is to figure out how to get the drivers to install for a Gadget device.
So I have the odin pda tar file - PDA_S5360_DDLF2.tar.md5
I unzipped it and extracted the following files:
Code:
1) boot.img
2) param.lfs
3) sbl.bin
4) system.img
5) userdata.img
I opened system.img and added/removed some apps inside the app folder. Saved system.img and exited. Look below:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
These are the five files again from pda.tar which I'm putting in the tar archive
Code:
1) boot.img
2) param.lfs
3) sbl.bin
4) system.img (edited using ultraiso: see above)
5) userdata.img
I used the following code in terminal to make the tar ball:
Code:
tar -H ustar -c boot.img param.lfs sbl.bin system.img serdata.img > Custom_PDA_S5360.tar
The I used the following commands to md5 it:
Code:
md5sum Custom_PDA_S5360.tar
md5sum –t Custom_PDA_S5360.tar >> Custom_PDA_S5360.tar
mv Custom_PDA_S5360.tar Custom_PDA_S5360.tar.md5
Now i have the custom pda.tar.md5 with me. I'm a little scared to flash it without knowing whether it could brick my phone or not.
I need some guidance and advise from the senior xda gurus.
Will it work? Or not?
Or will I end up with a bricked phone?
Am I wasting my time?
Connect your phone to odin and flash it...
If it doesn't work flash stock...
And if flashing stock fails goto service center and sae " I swear i am never going to use that online update again!!!"
Globally recognised and certified NOOB
alkesh saar ji,
thank you for the wise crack answer. but i don't have the time to run around the service centre to fix my phone.
im not sure what the actual reasons are for hard bricking a phone
A phone that gets stuck in bootloop but can still switch into odin download mode is not actual brick IMO
in the past, i have successful placed several windows and linux OS's on one bootable dvd. I guess what im trying to say is that im not familiar with the mechanisms of an android OS.
broadways said:
alkesh saar ji,
thank you for the wise crack answer. but i don't have the time to run around the service centre to fix my phone.
im not sure what the actual reasons are for hard bricking a phone
A phone that gets stuck in bootloop but can still switch into odin download mode is not actual brick IMO
in the past, i have successful placed several windows and linux OS's on one bootable dvd. I guess what im trying to say is that im not familiar with the mechanisms of an android OS.
Click to expand...
Click to collapse
If you want to try then do as I said....
Wait why you are using odin method you can simply push apk via rootex or adb
Globally recognised and certified NOOB
Do you mean adb install method?
After each time i flash stock, i root and remove things i don't need from system(youtube, maps etc)
Then i install my imp apps on system(by removing sd) using adb install
Then i shift dalvik to system
I'm trying to automate my work. I don't think i can do dalvik shift in an odin package but I think I can do the apps add/remove thing.
What do you think?
broadways said:
Do you mean adb install method?
After each time i flash stock, i root and remove things i don't need from system(youtube, maps etc)
Then i install my imp apps on system(by removing sd) using adb install
Then i shift dalvik to system
I'm trying to automate my work. I don't think i can do dalvik shift in an odin package but I think I can do the apps add/remove thing.
What do you think?
Click to expand...
Click to collapse
Do simplest method use root explorer to push apps to system and set their permission rw-r--r--
Globally recognised and certified NOOB
I prefer automation.
I use batch "rm" commands in adb shell to remove apps from "system/app"
And I use adb install batch command file to install all apps in android.
The order of automation:
1) Flashing rom
2) Rooting
3) Removing unwanted app from system
4) Installing apps on system
5) Unrooting
Whole process takes around 15-20 minutes and much of it is done through batch files.
What I want now is to add/remove the apps in the pda.tar flashable file itself.
If I can achieve this, my time will be reduced from 15-20 minutes to 3-5 minutes.
What is the result? Have u flashed it?
Sent from my GT-S5360 using xda premium
ok guys, so first, i want to apologize for my bad english. im not very good when it comes to writing and talking.
let's go; what we are going to do is flash the ROM with aan included ROOT, with the posibility of wiping our device.
I remind you that: **I'M NOT RESPONSIBLE FOR ANY DAMAGE TO YOUR DEVICE OR YOUR COMPUTER.**
**I RECOMMEND CHARGING YOUR BATTERY TO 100%**
**I ALSO RECOMMEND YOU TO MAKE A COPY OF ALL YOUR DATA**
YOU WILL MISS YOUR GARANTY IF YOU ROOT YOUR DEVICE**
First step: DOWNLOAD THE ROM Through this link and place it in your desktop.
2. you will also have to download ODIN 3
3.in Developer options, activate the USB Debugging option (Settings --> Developer options --> USB Debugging
Ok, you have to start ODIN and you have to get your device in Downloading Mode. (you will do this by shuting it off. and then pressing *VOLUME DOWN KEY*+*HOME KEY*+*POWER KEY*. when you do that you should press the volume up key) When you are in Downloading mode you should connect your device to your PC.
4. Once synchronized, with Odin, you have to select "OPEN" where it says PDA. select the archive you downloaded before. (the one with the name *I8190XXALK6_I8190XEFALK1_HOME_ROOTED.tar.md5*) (you have to uncompress that item before using it)
5. then you press start in Odin, and wait 'til the instalation finishes. the your device should reboot and odin should show a message saying PASS!
6. then you should be able to boot your device like you do normally.
EXTRA STEPS JUST IF YOU HAVE ANY ERROR
1. if you cant boot, you will need to WIPE your device instaling this archive and use it like in step 4 through the PDA button.
2. if you still have any problem, you should install this following step 4.
how your device should look like
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any problem or suggestion, please comment and thank.
This will install an older December rom! I'm afraid it's a step back, and bad advice.
Most countries have moved on from the LL2 rom in that file.
The instructions also mention the LK6 rom, which is even older, and not attached above.
this is avicoh first rooted rom and it was posted here on the forum long ago. I dont know why u reposted, to be honest i wayted for u to post but thought u come up with another solution that doesnt include Odin.
Best regards,
Yeah this isn't anything new, I and everyone here thought there was some kind of new ROOTING method. The Rom is already Rooted.
Sent from my GT-I8190 using xda premium
This has been covered before in the correct forum. Read before posting.
Posted in the wrong topic, my apologies to mod's.
Hello,
I'm on the new side with flashing in such and need to know what file is run in Odin on the PDA line? The videos always show a MD5 file but I don't see one in the zip file I downloaded. How would I go about creating this file type? The remaining steps of the process seen easy.
Thanks, in advance
Bruce
Gladyscoleman said:
You can install a application which played all type of video files like "MX Player"
Click to expand...
Click to collapse
I'm somewhat confused here. Are you saying that I must install some program in order to make a MD5 file. Maybe it would be easier if I just knew what file to run on the PDA line. Is it the BOOT.IMG file? I would like to run this new KK software.
Thank you!
Bruce
tss01 said:
I'm somewhat confused here. Are you saying that I must install some program in order to make a MD5 file. Maybe it would be easier if I just knew what file to run on the PDA line. Is it the BOOT.IMG file? I would like to run this new KK software.
Thank you!
Bruce
Click to expand...
Click to collapse
Okay in this screen shot there's the Odex rom and then the deodexed rom. Last is the firmware.
After you have flashed either one of the Odex or Deodexed roms in Safestrap 3.65 stock slot and remember to wipe the stock slot first.
So after the rom is flashed the don't reboot system but reboot to download mode and open up odin.
Prior to doing all this download the firmware to your computer. Once downloaded extract the the file that shows the as tar. After having odin open click on the PA and put that file in there and let it run its course checking the file. Then when it's done hit start.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here's a pic off my pc of the file that goes in AP slot for Odin.
Odin will run MD5 check on it automatically and say it's valid. Then from there just have you phone in download mode and hooked up to pc and hit start.
not sure if you have seen this tutorial or not.
How To Install Kit Kat 4.4.2 Verizon Note 3 With …: http://youtu.be/zYrquBtAS1o
Hey everyone i tried to search but found no step by step guide to use mobile odin to flash firmwares on samsung devices. Here i will try to make each step as elaborate as possible so fasten your seat belts and here we go...!!!
I will be using my galxy note 10.1 for refrence
First of all download appropriate stock firmware file from
http://www.sammobile.com/
Copy it to your phone storage or external card i preferably use ecxternal card
then get your self mobile odin from following link from playstore
https://play.google.com/store/apps/details?id=eu.chainfire.mobileodin.pro&hl=en
After installation is complete click mobile odin application icon in app drawer as shown below
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After opening it will ask for root permissions as shown
After Giving root permissions it can go in 2 directions it may ask u to download a file to be able to flash in recovery or it may proceed . If it is asking to install a file u will be presented with a download option for which wifi enabling is required as shown
And it will start downloading immediatley
Now after download is Complete u will be presented with main menu window it is scroll able and provide basic options as selecting individual modem, csc etc or selecting a file
View attachment 2815248
Scroll and find option "Open File" select this option and choose ur stock firmware file location and then select firmware file
View attachment 2815249
View attachment 2815250
View attachment 2815253
After selecting proper firmware file you will be presented with a summary of ehich partiions are selected for this flash Click ok
After that as i have shown in screenshot with different coloured arrows select ur prefrences. Red ones are for rooting the firmware after flashing it, blue arrow is for mobile odin to be injected in the new frmware, green ones are for wiping options u must select both of these, at the end click yellow one to start the flash operation
View attachment 2815255
Final screenshot show after flash options whther u want to boot normally or to recovery
View attachment 2815256
Flashin will take some time after flashin is complete open up recovery while using power+up button during boot up and wipe everything and then after booting up your new rom is flashed voilaaaa.......
Thank you for this, but just in case one of you have flashed the n8000 bootloader on your n8010, and Mobile Odin sees your device as an n8000, you might need to manually download the latest version for the n8010, found in this thread here: http://forum.xda-developers.com/showthread.php?t=1347899
Sent from my GT-N8013 using Tapatalk
electrikjesus said:
Thank you for this, but just in case one of you have flashed the n8000 bootloader on your n8010, and Mobile Odin sees your device as an n8000, you might need to manually download the latest version for the n8010, found in this thread here: http://forum.xda-developers.com/showthread.php?t=1347899
Sent from my GT-N8013 using Tapatalk
Click to expand...
Click to collapse
thanks bro